DETAILED ACTION
The following is a final office action in response to applicant’s amendment filed on 04/06/2026 for response of the office action mailed on 01/14/2026. Interdependent claims 1 and 16 are amended. A new set of claims 19-28 are cancelled. Therefore, claims 1-7 and 16-28 are pending and addressed below.
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 .
Claim Rejections - 35 USC § 103
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.
In 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 factual inquiries set forth in Graham v. John Deere Co., 383 U.S. 1, 148 USPQ 459 (1966), that are applied 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.
Claim 1-2, 4-5, 16-17, 19-20, 22-23 and 26-27 are rejected under 35 U.S.C. 103 as being unpatentable over Chen et al. (2023/0030443), Chen hereinafter, in view of TSAI et. la. (2021/0337625, Provisional application 63/014,648 will be used for the instant application. See PTO-892), TSAI648, hereinafter.
Re. claims 1 and 19, Chen teaches a method (Fig. 1-3 & ¶0048/¶0062/¶0073) performed by a user equipment (UE) (Fig. 3 & ¶0083 - node 300 may be a UE or a BS), and a user equipment (UE) (Fig. 3 & ¶0083 - node 300 may be a UE or a BS) for wireless communication (Fig. 1-3 & ¶0002/¶0003/¶0012/¶0083 ), comprising: at least one memory (Fig. 3, 328); and at least one processor (Fig. 3, 326) coupled with the at least one memory and configured to cause the UE to: receive configured grant (CG) resource configuration information on a plurality of CG resources from a base station (BS) (Fig. 1-3 & ¶0048 - BS may provide configured grants (e.g., pre-configured PUSCH resources, configured grant Type 1 configuration) in dedicated signaling (e.g., in an RRC Release message with a suspend configuration). …. a configured grant, a pre-configured PUSCH resource, and a configured grant Type 1 configuration may be exchangeable. If a UE in the RRC_INACTIVE state is configured with pre-configured PUSCH resources, the UE may be allowed to transmit small data on the pre-configured PUSCH resources in the RRC_INACTIVE state without transitioning to the RRC_CONNECTED state.);determine a value of a timing alignment (TA) timer based on a period of one selected CG resource from the plurality of CG resources (Fig. 1-3 & ¶0062 - UE may determine whether configured grants (e.g., pre-configured PUSCH resources) for small data transmission is valid…… UE may determine the configured grants are valid when the UE is camped on a cell from which the UE receives the RRC release message. …..BS may provide pre-configured PUSCH resources (e.g., configured grant Type 1 configuration) in dedicated signaling (e.g., in an RRC Release message with a suspend configuration) and also a life timer (e.g., a TA timer) for the pre-configured PUSCH resources. For example, the configured grant configuration #1 (for providing PUSCH resources when the UE is in the RRC_INACTIVE state) may be associated with a life timer (e.g., a TA timer). In some implementations, the UE may start a life timer (e.g., a TA timer) for a configured grant after receiving the RRC Release message with the suspend configuration. In one example, a common life timer (e.g., a common TA timer) of one or more configured grants may be provided to the UE. In another example, different life timers (e.g., different TA timers) for different configured grants may be provided. In other examples, a life timer (e.g., a TA timer) may be configured for all pre-configured PUSCH resources. It should be noted that when a life timer (e.g., a TA timer) is running, the associated pre-configured PUSCH resources may be considered as valid. Once the life timer (e.g., the TA timer) expires (or is not running), the UE may consider all pre-configured PUSCH resources as invalid. That is, the UE may not be allowed to use the pre-configured PUSCH resources for small data transmission in the RRC_INACTIVE state. In some implementations, a TA value for a TA timer that is applied for the UE in the RRC_INACTIVE state may be provided in dedicated signaling (e.g., in an RRC Release message with a suspend configuration)….. a UE may be configured with a (absolute) threshold to determine whether the current TA (or the associated configured grant(s)) is valid or not…. a Reference Symbol Received Power (RSRP) threshold may be configured (via dedicated signaling or broadcast system information) to determine whether the current TA (or the associated configured grant(s)) is valid or not. In this case, if the RSRP of the downlink pathloss reference (or the RSRP of the downlink reference signal) is above the threshold, the TA (or the associated configured grant(s)) may be considered as valid and the UE may use the pre-configured PUSCH resources (e.g., the PUSCH resources associated with the downlink reference signal of a Synchronization Signal Block (SSB)) for small data transmission. Fig. 1-3 & ¶0064 - UE may perform small data transmission via the configured grant if at least one of the following criteria or condition(s) is fulfilled …..; (2) configured grant is valid; (3) the UE has a valid TA For example, if the UE is configured with configured grants for small data transmission in the RRC_INACTIVE state and/or is allowed to transmit small data via the configured grants in the RRC_INACTIVE state);
Yet, Chen does not expressly teach transmit data in at least one of the plurality of CG resources if the TA timer is running and the at least one of the plurality of CG resources is valid.
However, in the analogous art, TSAI648 explicitly discloses transmit data in at least one of the plurality of CG resources if the TA timer is running and the at least one of the plurality of CG resources is valid (Page Number: 1 - To realize SDT-configuration, two types of radio resource may be configured to the UE: 1) SDT-CG configuration: (Type 1/Type 2) uplink configured grant (UL-CG configuration (e.g., the locations of physical radio resources on time domain/frequency domain and the periodicity of the uplink configured grant) may be configured in the SDT-configuration. UL-CG configuration contains periodic UL radio resources for the UE to access directly while the UE is staying out of RRC Connected state (e.g., when the UE is in (LTE/NR) RRC_INACTIVE state or in (LTE/NR) RRC_IDLE state). Moreover, one or more UL-CG configurations (wherein each UL-CG configuration may be associated with one unique SDT-CG index in the SDT-configuration) may be configured to the UE in the SDTconfiguration. In this disclosure, the procedure which UE transmits small packet through UL-CG configuration is also called SDT-CG procedure. Page Number: 6 – Timing Advance Timer (TAT) for SDT-CG configuration - one SDT-CG Timing Advance Timer (which is also called as CG-TAT in this disclosure) would be configured for the UE to identify the valid time period of the Configured Grant configured for Small Packet Transmission (SDT). For example, the UE may be allowed to access the SDT-CG configuration for small packet transmission while the CG-TAT is still counting/running, which means the UE is still maintaining a valid UL timing advance (UL-TA) for UL transmission and/or SDT-CG procedure).
Therefore, it would have been obvious to one of the ordinary skill in the art before the effective filling date of the claimed invention to combine Chen’s invention of a system and a method for small data transmission in a wireless communication system to include TSAI648’s invention of Packet Transmission Mechanisms for Inactive User Equipment in a wireless communication system, because it provides an efficient mechanism in enabling a user equipment (UE) for transmitting small packet/data in uplink while the UE is out of Radio Resource Control (RRC) Connected state, for example, the UE moves to RRC inactive state, in turns, improves power consumption and signalling overhead of the wireless communication system. (Page 1/ Page 33, TSAI648).
Re. Claims 4 and 22, Chen and TSAI648 teach claims 1 and 19.
Chen further teaches wherein if the TA timer is expired at a time point in a duration of one CG resource among the plurality of CG resources, a timing advance for the CG resource is defined as one or more of: the timing advance is valid for the CG resource (Fig. 1-3 & ¶0062 -… the UE may start a life timer (e.g., a TA timer) for a configured grant after receiving the RRC Release message with the suspend configuration. In one example, a common life timer (e.g., a common TA timer) of one or more configured grants may be provided to the UE. In another example, different life timers (e.g., different TA timers) for different configured grants may be provided. In other examples, a life timer (e.g., a TA timer) may be configured for all pre-configured PUSCH resources. It should be noted that when a life timer (e.g., a TA timer) is running, the associated pre-configured PUSCH resources may be considered as valid. Examiner interprets that only one of the claimed features to be mapped because of the presence of “as one or more of” and “or” in the limitation); the timing advance is invalid for the CG resource (Fig. 1-3 & ¶0062 -… the UE may start a life timer (e.g., a TA timer) for a configured grant after receiving the RRC Release message with the suspend configuration. In one example, a common life timer (e.g., a common TA timer) of one or more configured grants may be provided to the UE…. Once the life timer (e.g., the TA timer) expires (or is not running), the UE may consider all pre-configured PUSCH resources as invalid. Examiner interprets that only one of the claimed features to be mapped because of the presence of “as one or more of” and “or” in the limitation); the timing advance is valid if a proportion of a part of the CG resource before the time point in the duration of the CG resource is greater or not smaller than a first threshold, or if a proportion of a part of the CG resource after the time point in the duration of the CG resource is smaller or not greater than a second threshold; or the timing advance is valid if the duration of the CG resource is smaller or not greater than a third threshold.
Re. Claims 5 and 23, Chen and TSAI648 teach claims 1 and 19.
Chen further teaches wherein the at least one processor (Fig. 3, 326) is further configured to cause the UE (Fig. 3) to: start the TA timer upon the UE moving to a radio resource control (RRC) inactive mode from a RRC connected mode, upon the UE receiving a RRC release message with a suspend indication (Fig. 1-3 & ¶0062 - BS may provide pre-configured PUSCH resources (e.g., configured grant Type 1 configuration) in dedicated signaling (e.g., in an RRC Release message with a suspend configuration) and also a life timer (e.g., a TA timer) for the pre-configured PUSCH resources. For example, the configured grant configuration #1 (for providing PUSCH resources when the UE is in the RRC_INACTIVE state) may be associated with a life timer (e.g., a TA timer). …. the UE may start a life timer (e.g., a TA timer) for a configured grant after receiving the RRC Release message with the suspend configuration. Examiner interprets that only one of the claimed features to be mapped because of the presence of “or” in the limitation), or upon the UE receiving the CG resource configuration information.
Re. claims 16 and 26, Chen teaches a method (Fig. 1-3 & ¶0048/¶0062/¶0073) performed by a base station (BS) (Fig. 3 & ¶0083 - node 300 may be a UE or a BS), and a base station (BS) (Fig. 3 & ¶0083 - node 300 may be a UE or a BS) for wireless communication (Fig. 1-3 & ¶0002/¶0003/¶0012/¶0083), comprising: at least one memory (Fig. 3, 328); and at least one processor (Fig. 3, 326) with the at least one memory and configured to cause the BS to: transmit configured grant (CG) resource configuration information on a plurality of CG resources to a user equipment (UE) (Fig. 1-3 & ¶0048 - BS may provide configured grants (e.g., pre-configured PUSCH resources, configured grant Type 1 configuration) in dedicated signaling (e.g., in an RRC Release message with a suspend configuration). …. a configured grant, a pre-configured PUSCH resource, and a configured grant Type 1 configuration may be exchangeable. If a UE in the RRC_INACTIVE state is configured with pre-configured PUSCH resources, the UE may be allowed to transmit small data on the pre-configured PUSCH resources in the RRC_INACTIVE state without transitioning to the RRC_CONNECTED state); and the UE having determined a value of a timing alignment (TA) timer based on a period of one selected CG resource from the plurality of CG resources (Fig. 1-3 & ¶0062 - UE may determine whether configured grants (e.g., pre-configured PUSCH resources) for small data transmission is valid…… UE may determine the configured grants are valid when the UE is camped on a cell from which the UE receives the RRC release message. …..BS may provide pre-configured PUSCH resources (e.g., configured grant Type 1 configuration) in dedicated signaling (e.g., in an RRC Release message with a suspend configuration) and also a life timer (e.g., a TA timer) for the pre-configured PUSCH resources. For example, the configured grant configuration #1 (for providing PUSCH resources when the UE is in the RRC_INACTIVE state) may be associated with a life timer (e.g., a TA timer). In some implementations, the UE may start a life timer (e.g., a TA timer) for a configured grant after receiving the RRC Release message with the suspend configuration. In one example, a common life timer (e.g., a common TA timer) of one or more configured grants may be provided to the UE. In another example, different life timers (e.g., different TA timers) for different configured grants may be provided. In other examples, a life timer (e.g., a TA timer) may be configured for all pre-configured PUSCH resources. It should be noted that when a life timer (e.g., a TA timer) is running, the associated pre-configured PUSCH resources may be considered as valid. Once the life timer (e.g., the TA timer) expires (or is not running), the UE may consider all pre-configured PUSCH resources as invalid. That is, the UE may not be allowed to use the pre-configured PUSCH resources for small data transmission in the RRC_INACTIVE state. In some implementations, a TA value for a TA timer that is applied for the UE in the RRC_INACTIVE state may be provided in dedicated signaling (e.g., in an RRC Release message with a suspend configuration)….. a UE may be configured with a (absolute) threshold to determine whether the current TA (or the associated configured grant(s)) is valid or not…. a Reference Symbol Received Power (RSRP) threshold may be configured (via dedicated signaling or broadcast system information) to determine whether the current TA (or the associated configured grant(s)) is valid or not. In this case, if the RSRP of the downlink pathloss reference (or the RSRP of the downlink reference signal) is above the threshold, the TA (or the associated configured grant(s)) may be considered as valid and the UE may use the pre-configured PUSCH resources (e.g., the PUSCH resources associated with the downlink reference signal of a Synchronization Signal Block (SSB)) for small data transmission. Fig. 1-3 & ¶0064 - UE may perform small data transmission via the configured grant if at least one of the following criteria or condition(s) is fulfilled …..; (2) configured grant is valid; (3) the UE has a valid TA For example, if the UE is configured with configured grants for small data transmission in the RRC_INACTIVE state and/or is allowed to transmit small data via the configured grants in the RRC_INACTIVE state;).
Yet, Chen does not expressly teach receive data in at least one of the plurality of CG resources,
However, in the analogous art, TSAI648 explicitly discloses receive data in at least one of the plurality of CG resources (Page Number: 1 - To realize SDT-configuration, two types of radio resource may be configured to the UE: 1) SDT-CG configuration: (Type 1/Type 2) uplink configured grant (UL-CG configuration (e.g., the locations of physical radio resources on time domain/frequency domain and the periodicity of the uplink configured grant) may be configured in the SDT-configuration. UL-CG configuration contains periodic UL radio resources for the UE to access directly while the UE is staying out of RRC Connected state (e.g., when the UE is in (LTE/NR) RRC_INACTIVE state or in (LTE/NR) RRC_IDLE state). Moreover, one or more UL-CG configurations (wherein each UL-CG configuration may be associated with one unique SDT-CG index in the SDT-configuration) may be configured to the UE in the SDTconfiguration. In this disclosure, the procedure which UE transmits small packet through UL-CG configuration is also called SDT-CG procedure. Page Number: 6 – Timing Advance Timer (TAT) for SDT-CG configuration - one SDT-CG Timing Advance Timer (which is also called as CG-TAT in this disclosure) would be configured for the UE to identify the valid time period of the Configured Grant configured for Small Packet Transmission (SDT). For example, the UE may be allowed to access the SDT-CG configuration for small packet transmission while the CG-TAT is still counting/running, which means the UE is still maintaining a valid UL timing advance (UL-TA) for UL transmission and/or SDT-CG procedure),
Therefore, it would have been obvious to one of the ordinary skill in the art before the effective filling date of the claimed invention to combine Chen’s invention of a system and a method for small data transmission in a wireless communication system to include TSAI648’s invention of Packet Transmission Mechanisms for Inactive User Equipment in a wireless communication system, because it provides an efficient mechanism in enabling a user equipment (UE) for transmitting small packet/data in uplink while the UE is out of Radio Resource Control (RRC) Connected state, for example, the UE moves to RRC inactive state, in turns, improves power consumption and signalling overhead of the wireless communication system. (Page 1/ Page 33, TSAI648).
Re. Claims 2, 17, 20 and 27, Chen and TSAI648 teach claims 1, 16, 19 and 26.
Chen further teaches wherein the period of the selected CG resource is one of: a maximum period among periods of the plurality of CG resources; a minimum period among periods of the plurality of CG resources; an average period of periods of the plurality of CG resources; a median period base on the periods of the plurality of CG resources; a value calculated based on the periods of the plurality of CG resources (Fig. 1-3 & ¶0062 - BS may provide pre-configured PUSCH resources (e.g., configured grant Type 1 configuration) in dedicated signaling (e.g., in an RRC Release message with a suspend configuration) and also a life timer (e.g., a TA timer) for the pre-configured PUSCH resources. For example, the configured grant configuration #1 (for providing PUSCH resources when the UE is in the RRC_INACTIVE state) may be associated with a life timer (e.g., a TA timer). In some implementations, the UE may start a life timer (e.g., a TA timer) for a configured grant after receiving the RRC Release message with the suspend configuration. In one example, a common life timer (e.g., a common TA timer) of one or more configured grants may be provided to the UE. In another example, different life timers (e.g., different TA timers) for different configured grants may be provided. In other examples, a life timer (e.g., a TA timer) may be configured for all pre-configured PUSCH resources. It should be noted that when a life timer (e.g., a TA timer) is running, the associated pre-configured PUSCH resources may be considered as valid. Examiner interprets that only one of the claimed features to be mapped because of the presence of “one of” and “or” in the limitation); a period of a certain CG resource (Fig. 1-3 & ¶0062 - BS may provide pre-configured PUSCH resources (e.g., configured grant Type 1 configuration) in dedicated signaling (e.g., in an RRC Release message with a suspend configuration) and also a life timer (e.g., a TA timer) for the pre-configured PUSCH resources. For example, the configured grant configuration #1 (for providing PUSCH resources when the UE is in the RRC_INACTIVE state) may be associated with a life timer (e.g., a TA timer). In some implementations, the UE may start a life timer (e.g., a TA timer) for a configured grant after receiving the RRC Release message with the suspend configuration. In one example, a common life timer (e.g., a common TA timer) of one or more configured grants may be provided to the UE. In another example, different life timers (e.g., different TA timers) for different configured grants may be provided. In other examples, a life timer (e.g., a TA timer) may be configured for all pre-configured PUSCH resources. It should be noted that when a life timer (e.g., a TA timer) is running, the associated pre-configured PUSCH resources may be considered as valid. Examiner interprets that only one of the claimed features to be mapped because of the presence of “one of” and “or” in the limitation) or a dedicated CG resource; a period of a CG resource that can be applied to all data radio bearers (DRBs) for small data transmission (SDT); or a period of a CG resource that can be applied to a dedicated one or more DRBs for SDT.
Claims 3, 18, 21 and 28 are rejected under 35 U.S.C. 103 as being unpatentable over Chen, in view of TSAI648, further in view of Mi et al. (2021/0168746), Mi hereinafter.
Re. Claims 3 and 21, Chen and TSAI648 teach claims 1 and 19.
Yet, Chen and TSAI648 do not expressly teach wherein a value of the TA timer is computed according to the period of one selected CG resource multiplied by N, and wherein a value of N is suggested by the UE and is included in a CG resource configuration request message from the UE to a network.
However, in the analogous art, Mi explicitly discloses wherein a value of the TA timer is computed according to the period of one selected CG resource multiplied by N, and wherein a value of N is suggested by the UE and is included in a CG resource configuration request message from the UE to a network. (Fig. 1-4 & ¶0031 - If the adjustment value is the maximum timing value, the adjustment value is used by the terminal device to adjust the maximum timing value of the TA timer to the adjustment value. If the adjustment value is the multiplicative factor, the adjustment value is used by the terminal device to adjust the maximum timing value of the TA timer to a value obtained by multiplying a current maximum timing value of the TA timer by the multiplicative factor……Fig. 1-4 & ¶0035 - the network device may receive mobility status indication information sent by the terminal device, where the mobility status indication information is used to indicate the network device that the terminal device is in a static state. If the network device sends a second indication message to the terminal device, the second indication message is used to indicate the terminal device to adjust the maximum timing value of the TA timer to the positive infinity.)
Therefore, it would have been obvious to one of the ordinary skill in the art before the effective filling date of the claimed invention to combine Chen’s invention of a system and a method for small data transmission in a wireless communication system and TSAI648’s invention of Packet Transmission Mechanisms for Inactive User Equipment in a wireless communication system to include Mi’s invention of a system and a method for uplink transmission in preconfigured resources by using narrowband internet of things (NB-IoT) devices operating in a wireless communication system, because it provides an efficient mechanism in determining whether TA (Timing Advance) of the NB-iOT devices are valid for the uplink transmission in the a wireless communication system. (¶0012-¶0014, Mi)
Re. Claims 18 and 28, Chen and TSAI648 teach claims 16 and 26.
Yet, Chen and TSAI648 do not expressly teach wherein the at least one processor is further configured to cause the apparatus BS to: receive, from the UE, a CG resource configuration request message including a value of N, a value of the TA timer having been computed by the UE according to the period of one selected CG resource multiplied by N.
However, in the analogous art, Mi explicitly discloses wherein the at least one processor (Fig. 8, 802) is further configured to cause the apparatus BS (Fig. 8) to: receive, from the UE, a CG resource configuration request message including a value of N, a value of the TA timer having been computed by the UE according to the period of one selected CG resource multiplied by N. (Fig. 1-4 & ¶0031 - If the adjustment value is the maximum timing value, the adjustment value is used by the terminal device to adjust the maximum timing value of the TA timer to the adjustment value. If the adjustment value is the multiplicative factor, the adjustment value is used by the terminal device to adjust the maximum timing value of the TA timer to a value obtained by multiplying a current maximum timing value of the TA timer by the multiplicative factor……Fig. 1-4 & ¶0035 - the network device may receive mobility status indication information sent by the terminal device, where the mobility status indication information is used to indicate the network device that the terminal device is in a static state. If the network device sends a second indication message to the terminal device, the second indication message is used to indicate the terminal device to adjust the maximum timing value of the TA timer to the positive infinity.)
Therefore, it would have been obvious to one of the ordinary skill in the art before the effective filling date of the claimed invention to combine Chen’s invention of a system and a method for small data transmission in a wireless communication system and TSAI648’s invention of Packet Transmission Mechanisms for Inactive User Equipment in a wireless communication system to include Mi’s invention of a system and a method for uplink transmission in preconfigured resources by using narrowband internet of things (NB-IoT) devices operating in a wireless communication system, because it provides an efficient mechanism in determining whether TA (Timing Advance) of the NB-iOT devices are valid for the uplink transmission in the a wireless communication system. (¶0012-¶0014, Mi)
Claim 6-7 and 24-25 are rejected under 35 U.S.C. 103 as being unpatentable over Chen, in view of TSAI648, further in view of Liu et al. (2024/0098797), Liu hereinafter.
Re. Claims 6 and 24, Chen and TSAI648 teach claims 1 and 19.
Yet, Chen and TSAI648 do not expressly teach wherein the at least one processor is further configured to cause the UE to: release at least one of the plurality of CG resources if a number of consecutive CG resource occasions have been skipped, wherein the number of consecutive CG resource occasions is beam specific or UE specific.
However, in the analogous art, Liu explicitly discloses wherein the at least one processor (Fig. 19A, 1936) is further configured to cause the UE to: release at least one of the plurality of CG resources if a number of consecutive CG resource occasions have been skipped (Fig. 1-19B & ¶0041 - The method 200 begins at block 210, where the UE defines a counter (e.g., N) with SDT CG resources. The counter is configured by RRC for each UE, for each carrier (i.e., UL and SUL), or for each CG resource. During SDT procedure (i.e., after the SDT request is transmitted), when N consecutive CG occasions are skipped, the UE shall release SDT CG resources depending on the counter configuration at block 220. If the counter is configured for each UE, the UE releases all SDT CG resources configured in the UE.), wherein the number of consecutive CG resource occasions is beam specific or UE specific (Fig. 1-19B & ¶0051 - the configuration entails the association of one CG occasion of one CG resource to one SSB implicitly by supposing that the number of actual transmission SSBs determined by ssb-PositionsInBurst is equal to N or explicitly by configuring M SSB indexes in one CG resource (configured by a list, e.g., SDTConfiguredGrantConfigToAdolModList-r 17). Here, each N continuous CG occasions in one CG resource correspond to N SSBs, starting from the first CG occasion of the CG resource. … The first CG occasion in each M continuous CG occasions corresponds to the first entry of SSB-IndexList, the second CG occasion in each M continuous CG occasions corresponds to the second entry of SSB-IndexList, and so on. For either embodiment, the gNB needs to configure parameters used for beam failure detection and beam failure recovery via RRCRelease with suspendConfig on the same Bandwidth Part (BWP) on which CG resources are configured. Examiner interprets that only one of the claimed features to be mapped because of the presence of “or” in the limitation).
Therefore, it would have been obvious to one of the ordinary skill in the art before the effective filling date of the claimed invention to combine Chen’s invention of a system and a method for small data transmission in a wireless communication system and TSAI648’s invention of Packet Transmission Mechanisms for Inactive User Equipment in a wireless communication system to include Liu’s invention of a system and a method for managing small data transmission in a wireless communication system, because it provides an efficient mechanism in allowing a user equipment (UE) transmitting (periodic and/or non-periodic) small data in RRC-Inactive state without moving to RRC-Connected state, in turns, improves the UE power consumption and signaling overhead of a network in the wireless communication system. (¶0002-¶0004, Liu)
Re. Claims 7 and 25, Chen, TSAI648 and Liu teach claims 6 and 24.
Yet, Chen and TSAI648 do not expressly teach wherein the number of consecutive CG resource occasions is included in a CG resource configuration request message from the UE to the BS.
However, in the analogous art, Liu explicitly discloses wherein the number of consecutive CG resource occasions is included in a CG resource configuration request message from the UE to the BS. (Fig. 1-19B & ¶0041 - The method 200 begins at block 210, where the UE defines a counter (e.g., N) with SDT CG resources. The counter is configured by RRC for each UE, for each carrier (i.e., UL and SUL), or for each CG resource. During SDT procedure (i.e., after the SDT request is transmitted), when N consecutive CG occasions are skipped, the UE shall release SDT CG resources depending on the counter configuration at block 220.)
Therefore, it would have been obvious to one of the ordinary skill in the art before the effective filling date of the claimed invention to combine Chen’s invention of a system and a method for small data transmission in a wireless communication system and TSAI648’s invention of Packet Transmission Mechanisms for Inactive User Equipment in a wireless communication system to include Liu’s invention of a system and a method for managing small data transmission in a wireless communication system, because it provides an efficient mechanism in allowing a user equipment (UE) transmitting (periodic and/or non-periodic) small data in RRC-Inactive state without moving to RRC-Connected state, in turns, improves the UE power consumption and signaling overhead of a network in the wireless communication system. (¶0002-¶0004, Liu)
Response to Arguments
Applicant's arguments filed on 04/06/2026 have been fully considered but they are not persuasive.
Regarding remarks in pages 9-10 for independent claims 1 and 19, applicant argues that Chen fails to teach, ''determine a value of a timing alignment (TA) timer based on a period of one selected CG resource from the plurality of CG resources”.
Examiner respectfully disagrees with the applicant. For example, Chen discloses that a UE may determine whether configured grants (e.g., pre-configured PUSCH resources, that is a plurality of CG resources) for small data transmission is valid…… UE may determine the configured grants <i.e., a plurality of CG resources > are valid when the UE is camped on a cell from which the UE receives the RRC release message. …..BS may provide pre-configured PUSCH resources (e.g., configured grant Type 1 configuration) in dedicated signaling (e.g., in an RRC Release message with a suspend configuration) and also a life timer (e.g., a TA timer) for the pre-configured PUSCH resources. For example, the configured grant configuration #1 (for providing PUSCH resources when the UE is in the RRC_INACTIVE state) may be associated with a life timer (e.g., a TA timer). … the UE may start a life timer (e.g., a TA timer) for a configured grant after receiving the RRC Release message with the suspend configuration. … a common life timer (e.g., a common TA timer) of one or more configured grants <i.e., a plurality of CG resources > may be provided to the UE. ….different life timers (e.g., different TA timers) for different configured grants < i.e., a plurality of CG resources> may be provided. …a life timer (e.g., a TA timer) may be configured for all pre-configured PUSCH resources < i.e., a plurality of CG resources >. It should be noted that when a life timer (e.g., a TA timer) is running, the associated pre-configured PUSCH resources < i.e., a plurality of CG resources > may be considered as valid. Once the life timer (e.g., the TA timer) expires (or is not running), the UE may consider all pre-configured PUSCH resources < i.e., a plurality of CG resources > as invalid. That is, the UE may not be allowed to use the pre-configured PUSCH resources for small data transmission in the RRC_INACTIVE state. …a TA value for a TA timer that is applied for the UE in the RRC_INACTIVE state may be provided in dedicated signaling (e.g., in an RRC Release message with a suspend configuration) ….. a UE may be configured with a (absolute) threshold to determine whether the current TA (or the associated configured grant(s)) is valid or not…. a Reference Symbol Received Power (RSRP) threshold may be configured (via dedicated signaling or broadcast system information) to determine whether the current TA (or the associated configured grant(s)) is valid or not. In this case, if the RSRP of the downlink pathloss reference (or the RSRP of the downlink reference signal) is above the threshold, the TA (or the associated configured grant(s) < i.e., a plurality of CG resources >) may be considered as valid and the UE may use the pre-configured PUSCH resources (e.g., the PUSCH resources associated with the downlink reference signal of a Synchronization Signal Block (SSB)) for small data transmission. See ¶0062 along with Fig. 1-3. Chen discloses that a UE may perform small data transmission via the configured grant if at least one of the following criteria or condition(s) is fulfilled …..; (2) configured grant is valid; (3) the UE has a valid TA For example, if the UE is configured with configured grants for small data transmission in the RRC_INACTIVE state and/or is allowed to transmit small data via the configured grants in the RRC_INACTIVE state. See ¶0064 along with Fig. 1-3.
Moreover, the aforementioned disclosure by Chen, is to perform Small Data Transmission (SDT) Via Configured Grants in RRC_INACTVE state. Chen confirms that configured grant, or pre-configured PUSCH resource or configured grant Type 1 configuration, all are exchangeable for the inventive concept as disclosed by Chen supra. In fact, the inventive concept of Chen is very similar to instant application as recited at least in ¶0058-¶0066, for example, the instant application recites, “Currently, a UE in inactive mode could perform a small data transmission over configured grant type 1 resources….and a work item description (WID) on small data transmission (SDT) in a RRC_INACTIVE state is as follows: ¶0064 - Transmission of UL data on pre-configured PUSCH resources (i.e. reusing the configured grant type 1)—when TA (timing advance) is valid ¶0065 - General procedure for small data transmission over configured grant type 1 resources from INACTIVE state”, quite a contrary to applicant’s remarks at least in pages 9-10 of remarks as submitted on 04/06/2026.
Similar, arguments are applicable to independent claims 16 and 26.
For these reasons, it is maintained that independent claims 1 and 19 are rejected under 35 U.S.C. 103 as being unpatentable over Chen, in view of TSAI648.
For similar reasons, it is maintained that independent claims 16 and 26 are rejected under 35 U.S.C. 103 as being unpatentable over Chen, in view of TSAI648.
As all other dependent claims depend either directly or indirectly from the independent claims 1, 16, 19 and 26, similar rationale also applies to all respective dependent claims.
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 MOHAMMED SHAMSUL CHOWDHURY whose telephone number is (571)272-0485. The examiner can normally be reached on Monday-Thursday 9 AM- 6 PM EST (Friday Var.).
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, Hassan Phillips can be reached on 571-272-3940. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/MOHAMMED S CHOWDHURY/Primary Examiner, Art Unit 2467
Prosecution Insights