DETAILED ACTION
The following is a final office action in response to applicant’s amendment filed on 04/16/2026 for response of the office action mailed on 01/16/2026. Interdependent claims 1, 8 and 16 are amended. No claims are cancelled. Therefore, claims 1-20 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.
Claims 1-14 and 16-20 are rejected under 35 U.S.C. 103 as being unpatentable over Alireza Babaei (2021/0259040), Babaei, in view of Zhang et al. (2021/0235407), Zhang hereinafter.
Re. claims 1 and 16, Babaei teaches a method for determining a timing advance (TA) (Fig.29/Fig.31 &¶0285-¶0286/¶0295), and a terminal device (Fig. 15), comprising: a transceiver (Fig. 15, 1516) configured to receive first indication information from a network device, wherein the first indication information comprising a radio network temporary identifier (RNTI) of a timing advance command (TAC) (Fig. 31 & ¶0295 – a wireless device in a radio resource control (RRC) inactive state may receive paging information via a paging channel. The paging information may indicate scheduling information for receiving a timing advance value. For example, the paging information may comprise a field indicating the scheduling information. For example, the paging information may indicate a control resource set and/or search space for receiving a downlink assignment of a downlink packet, wherein the downlink packet may comprise the timing advance value. For example, the paging information may comprise the configuration parameters of the control resource set and/or the search space for receiving the scheduling information/downlink assignment for receiving a downlink packet comprising the timing advance value. The wireless device may receive the paging information via the paging channel and may determine the paging information and/or scheduling information associated with the wireless device and included in the received paging information based on a wireless device identifier/RNTI associated with the wireless device. …. the downlink packet may comprise a timing advance command MAC CE comprising the timing advance value. Also, see ¶0400-¶0402 & ¶0418);
Yet, Babaei does not expressly teach a processor coupled to the transceiver and configured to determine a Timing Advance (TA) of the terminal device in the non-connected state based on the first indication information.
However, in the analogous art, Zhang explicitly discloses a processor (Fig. 9, 940) coupled to the transceiver (Fig. 9, 920) and configured to determine a Timing Advance (TA) of the terminal device in the non-connected state based on the first indication information (Fig. 3/ Fig. 5/Fig. 14-17 & Abstract - A user equipment (UE) may be configured with a set of parameters to determine a valid timing advance (TA) to transmit data using preconfigured uplink resources (PUR) during an idle or inactive mode. In some cases, the parameters are one or more TA commands and one or more conditions associated with each TA command. The UE may identify the current condition of the UE and determine whether the current condition of the UE matches one of indicated conditions. The UE may select a TA command based on finding a match and use the TA command to transmit an uplink PUR transmission. Also, see step 1410 in Fig. 14 & step 1510 in Fig. 15, also, see ¶0011/¶0174, claim 3).
Therefore, it would have been obvious to one of the ordinary skills in the art before the effective filling date of the claimed invention to combine Babaei’s invention of a mechanism for wireless device and wireless network in inactive state in a wireless communication system to include Zhang’s invention of timing advance command implementations mechanism for preconfigured uplink resource transmissions in a wireless communication system, because it provides an efficient mechanism for mitigating power consumption and transmission delay in the wireless communication system.(¶0002-¶0005, Zhang)
Re. claims 2 and 17, Babaei and Zhang teach claims 1 and 16.
Babaei further teaches receiving, by the terminal device in the non-connected state. second indication information from the network device, the second indication information indicating a candidate time-frequency location of a physical downlink control channel (PDCCH). (Fig. 7/Fig. 17-46 & ¶0227- RRCRelease message may be used to command the release of an RRC connection or the suspension of the RRC connection. A suspendconfig IE in the RRCRelease message may indicate configuration for the RRC_INACTIVE state. The suspendconfig may comprise a plurality of parameters comprising a full-RNTI, a short-RNTI, a ran-PagingCycle, a ran-NotificationAreaInfo and a t380. The ran-PagingCycle may indicate a UE specific cycle for RAN-initiated paging. Fig. 7/Fig. 17-46 & ¶0228 - an IE SearchSpace may define how/where to search for PDCCH candidates. A search space may be associated with a ControlResourceSet. In an example, a parameter common may indicate that a search space is common search space (CSS) and may indicate DCI formats to monitor. A parameter controlResourceSetId may indicate the CORESET applicable for the SearchSpace. … The parameter monitoringSlotPeriodicityAndOffset may indicate slots for PDCCH Monitoring configured as periodicity and offset. The parameter monitoringSymbolsWithinSlot may indicate the first symbol(s) for PDCCH monitoring in the slots configured for PDCCH monitoring. Fig. 7/Fig. 17-46 & ¶0230 - The IE PDCCH-Config may be used to configure UE specific PDCCH parameters such as control resource sets (CORESET), search spaces and additional parameters for acquiring the PDCCH. In an example, a parameter controlResourceSetToAddModList may indicate a list of UE specifically configured Control Resource Sets (CORESETs) to be used by the wireless device. In an example, an IE PDCCH-ConfigCommon may be used to configure cell specific PDCCH parameters provided in SIB as well as in dedicated signaling. In an example, an IE ControlResourceSet may be used to configure a time/frequency control resource set (CORESET) in which to search for downlink control information).
Re. claims 3 and 18, Babaei and Zhang teach claims 1 and 16.
Babaei further teaches wherein the first indication information is carried in a radio resource control release (RRC Release) message or a paging message. (Fig. 31 & ¶0295 – a wireless device in a radio resource control (RRC) inactive state may receive paging information via a paging channel. The paging information may indicate scheduling information for receiving a timing advance value. For example, the paging information may comprise a field indicating the scheduling information. For example, the paging information may indicate a control resource set and/or search space for receiving a downlink assignment of a downlink packet, wherein the downlink packet may comprise the timing advance value. For example, the paging information may comprise the configuration parameters of the control resource set and/or the search space for receiving the scheduling information/downlink assignment for receiving a downlink packet comprising the timing advance value. The wireless device may receive the paging information via the paging channel and may determine the paging information and/or scheduling information associated with the wireless device and included in the received paging information based on a wireless device identifier/RNTI associated with the wireless device.).
Re. claims 4 and 19, Babaei and Zhang teach claim teach claims 2 and 17.
Babaei further teaches wherein the second indication information is carried in a radio resource control release (RRC Release) message or a paging message. (Fig. 7/Fig. 17-46 & ¶0227- RRCRelease message may be used to command the release of an RRC connection or the suspension of the RRC connection. A suspendconfig IE in the RRCRelease message may indicate configuration for the RRC_INACTIVE state. The suspendconfig may comprise a plurality of parameters comprising a full-RNTI, a short-RNTI, a ran-PagingCycle, a ran-NotificationAreaInfo and a t380. The ran-PagingCycle may indicate a UE specific cycle for RAN-initiated paging. Fig. 7/Fig. 17-46 & ¶0228 - an IE SearchSpace may define how/where to search for PDCCH candidates. A search space may be associated with a ControlResourceSet. In an example, a parameter common may indicate that a search space is common search space (CSS) and may indicate DCI formats to monitor. A parameter controlResourceSetId may indicate the CORESET applicable for the SearchSpace. … The parameter monitoringSlotPeriodicityAndOffset may indicate slots for PDCCH Monitoring configured as periodicity and offset. The parameter monitoringSymbolsWithinSlot may indicate the first symbol(s) for PDCCH monitoring in the slots configured for PDCCH monitoring. Fig. 7/Fig. 17-46 & ¶0230 - The IE PDCCH-Config may be used to configure UE specific PDCCH parameters such as control resource sets (CORESET), search spaces and additional parameters for acquiring the PDCCH. In an example, a parameter controlResourceSetToAddModList may indicate a list of UE specifically configured Control Resource Sets (CORESETs) to be used by the wireless device. In an example, an IE PDCCH-ConfigCommon may be used to configure cell specific PDCCH parameters provided in SIB as well as in dedicated signaling. In an example, an IE ControlResourceSet may be used to configure a time/frequency control resource set (CORESET) in which to search for downlink control information).
Re. claims 5 and 20, Babaei and Zhang teach claims 2 and 17.
Babaei further teaches wherein the second indication information comprises a control resource set identifier and a search space identifier. (Fig. 7/Fig. 17-46 & ¶0228 - an IE SearchSpace may define how/where to search for PDCCH candidates. A search space may be associated with a ControlResourceSet. In an example, a parameter common may indicate that a search space is common search space (CSS) and may indicate DCI formats to monitor. A parameter controlResourceSetId may indicate the CORESET applicable for the SearchSpace. … The parameter monitoringSlotPeriodicityAndOffset may indicate slots for PDCCH Monitoring configured as periodicity and offset. The parameter monitoringSymbolsWithinSlot may indicate the first symbol(s) for PDCCH monitoring in the slots configured for PDCCH monitoring…. The parameter searchSpaceId may identity the search space. Fig. 7/Fig. 17-46 & ¶0229 - an IE SearchSpaceId may be used to identify Search Spaces. Fig. 7/Fig. 17-46 & ¶0230 - The IE PDCCH-Config may be used to configure UE specific PDCCH parameters such as control resource sets (CORESET), search spaces and additional parameters for acquiring the PDCCH. In an example, a parameter controlResourceSetToAddModList may indicate a list of UE specifically configured Control Resource Sets (CORESETs) to be used by the wireless device. In an example, an IE PDCCH-ConfigCommon may be used to configure cell specific PDCCH parameters provided in SIB as well as in dedicated signaling. …., an IE ControlResourceSet may be used to configure a time/frequency control resource set (CORESET) in which to search for downlink control information… a ControlResourceSetId IE may indicate a short identity, used to identify a control resource set within a serving cell.).
Re. claim 6, Babaei and Zhang teach claim 2.
Babaei further teaches receiving, by the terminal device, a periodic timing advance command (TAC) from the network device based on the first indication information and the second indication information (Fig. 42-43 & ¶0342 - a wireless device may receive first configuration parameters of a downlink semi-persistent scheduling (SPS) configuration. The downlink SPS configuration may be for receiving timing advance values for uplink transmissions during an RRC_INACTIVE state. For example, the first configuration parameters may comprise a parameter indicating that the downlink SPS configuration is for wireless device operation during the RRC_INACTIVE state and/or for receiving timing advance values during an RRC_INACTIVE state. Fig. 42-43 & ¶0343 - RRC release message or the suspend config IE in the RRC release message may comprise the first configuration parameters of the downlink SPS configuration and/or the second configuration parameters of the uplink configured grant configuration. Fig. 42-43 & ¶0344 - The wireless device may receive timing advance values, during the RRC_INACTIVE state, based on the first configuration parameters. The wireless device may receive downlink packets based on the first configuration parameters and via the downlink SPS resources, wherein the downlink packets may comprise the timing advance values. For example, the wireless device may receive timing advance command MAC CEs indicating the timing advance values, wherein the timing advance MAC CEs are multiplexed in the downlink packets. The first configuration parameters may comprise a first periodicity parameter. The wireless device may activate a plurality of downlink assignments based on the first periodicity parameter. For example, the wireless device may determine time occasions of the plurality of downlink assignments based on the first periodicity parameter. Fig. 42-43 & ¶0345 - The wireless device may transmit uplink packets, during the RRC_INACTIVE state, based on the second configuration parameters and based on the received timing advance values. The second configuration parameters may comprise a second periodicity parameter. The wireless device may determine a plurality of pre-configured/configured grant resources based on the second periodicity parameter.);
Yet, Babaei does not expressly teach wherein the determining, by the terminal device, the TA of the terminal device in the non-connected state comprises: determining, by the terminal device, the TA of the terminal device based on the periodic TAC.
However, in the analogous art, Zhang explicitly discloses wherein the determining, by the terminal device, the TA of the terminal device in the non-connected state comprises: determining, by the terminal device, the TA of the terminal device based on the periodic TAC. (Fig. 3/ Fig. 5/Fig. 14-17 & Abstract - A user equipment (UE) may be configured with a set of parameters to determine a valid timing advance (TA) to transmit data using preconfigured uplink resources (PUR) during an idle or inactive mode. In some cases, the parameters are one or more TA commands and one or more conditions associated with each TA command. The UE may identify the current condition of the UE and determine whether the current condition of the UE matches one of indicated conditions. The UE may select a TA command based on finding a match and use the TA command to transmit an uplink PUR transmission. Also, see step 1410 in Fig. 14 & step 1510 in Fig. 15, also, see ¶0011/¶0174, claim 3).
Therefore, it would have been obvious to one of the ordinary skills in the art before the effective filling date of the claimed invention to combine Babaei’s invention of a mechanism for wireless device and wireless network in inactive state in a wireless communication system to include Zhang’s invention of timing advance command implementations mechanism for preconfigured uplink resource transmissions in a wireless communication system, because it provides an efficient mechanism for mitigating power consumption and transmission delay in the wireless communication system.(¶0002-¶0005, Zhang)
Re. claim 7, Babaei and Zhang teach claim 1.
Babaei further teaches parsing, by the terminal device based on the radio network temporary identifier (RNTI) of the timing advance command (TAC), downlink control information (DCI) that carries the TAC; receiving, by the terminal device, the TAC periodically delivered by the network device based on the DCI and the timing advance command sending period; (Fig. 26-Fig. 29 & ¶0285 - a wireless device may be in an RRC_INACTIVE state. The wireless device may receive a plurality of timing advance values via a control channel (e.g., PDCCH). In an example, the wireless device may receive downlink control information (i.e., DCI) comprising/indicating the plurality of timing advance values. In an example, the plurality of timing advance values may be for a plurality of wireless devices. The wireless device may receive the downlink control information via the downlink control channel (e.g., PDCCH). In an example, the downlink control information may be a common/group common downlink control information. The wireless device may receive the downlink control information via a common search space. The downlink control information (i.e., DCI) comprising the plurality of timing advance values may be associated with a wireless device identifier/RNTI. For example, a CRC of the downlink control information comprising the plurality of timing advance values may be scrambled with the wireless device identifier/RNTI. The wireless device may receive configuration parameters comprising the wireless device identifier/RNTI. For example, the wireless device may receive an RRC release message indicating transitioning of the wireless device from RRC_CONNECTED to RRC_INACTIVE wherein the RRC release message or a suspend config IE of the RRC release message may indicate the wireless device identifier/RNTI. The suspend config IE may comprise configuration parameters for wireless device operation during the RRC_INACTIVE state. Fig. 7/Fig. 17-46 & ¶0344 - The wireless device may receive timing advance values, during the RRC_INACTIVE state, based on the first configuration parameters. The wireless device may receive downlink packets based on the first configuration parameters and via the downlink SPS resources, wherein the downlink packets may comprise the timing advance values. For example, the wireless device may receive timing advance command MAC CEs indicating the timing advance values, wherein the timing advance MAC CEs are multiplexed in the downlink packets. The first configuration parameters may comprise a first periodicity parameter. The wireless device may activate a plurality of downlink assignments based on the first periodicity parameter. For example, the wireless device may determine time occasions of the plurality of downlink assignments based on the first periodicity parameter).
Yet, Babaei does not expressly teach wherein the determining, by the terminal device, the TA of the terminal device in the non-connected state based on the first indication information comprises: determining, by the terminal device, the TA of the terminal device based on the TAC.
However, in the analogous art, Zhang explicitly discloses wherein the determining, by the terminal device, the TA of the terminal device in the non-connected state based on the first indication information comprises: determining, by the terminal device, the TA of the terminal device based on the TAC. (Fig. 3/ Fig. 5/Fig. 14-17 & Abstract - A user equipment (UE) may be configured with a set of parameters to determine a valid timing advance (TA) to transmit data using preconfigured uplink resources (PUR) during an idle or inactive mode. In some cases, the parameters are one or more TA commands and one or more conditions associated with each TA command. The UE may identify the current condition of the UE and determine whether the current condition of the UE matches one of indicated conditions. The UE may select a TA command based on finding a match and use the TA command to transmit an uplink PUR transmission. Also, see step 1410 in Fig. 14 & step 1510 in Fig. 15, also, see ¶0011/¶0174, claim 3).
Therefore, it would have been obvious to one of the ordinary skills in the art before the effective filling date of the claimed invention to combine Babaei’s invention of a mechanism for wireless device and wireless network in inactive state in a wireless communication system to include Zhang’s invention of timing advance command implementations mechanism for preconfigured uplink resource transmissions in a wireless communication system, because it provides an efficient mechanism for mitigating power consumption and transmission delay in the wireless communication system.(¶0002-¶0005, Zhang)
Re. claim 8, Babaei teaches a method for determining a timing advance (TA) (Fig.29/Fig.31 &¶0285-¶0286/¶0295), comprising: sending, by a network device (Fig. 31, Base Station), first indication information to a terminal device in a non- connected state , the first indication information comprising a radio network temporary identifier (RNTI) of a timing advance command (TAC) (Fig. 31 & ¶0295 – a wireless device in a radio resource control (RRC) inactive state may receive paging information via a paging channel. The paging information may indicate scheduling information for receiving a timing advance value. For example, the paging information may comprise a field indicating the scheduling information. For example, the paging information may indicate a control resource set and/or search space for receiving a downlink assignment of a downlink packet, wherein the downlink packet may comprise the timing advance value. For example, the paging information may comprise the configuration parameters of the control resource set and/or the search space for receiving the scheduling information/downlink assignment for receiving a downlink packet comprising the timing advance value. The wireless device may receive the paging information via the paging channel and may determine the paging information and/or scheduling information associated with the wireless device and included in the received paging information based on a wireless device identifier/RNTI associated with the wireless device. …. the downlink packet may comprise a timing advance command MAC CE comprising the timing advance value.)
Yet, Babaei does not expressly teach the first indication information is used by the terminal device to determine a Timing Advance (TA) of the terminal device in the non-connected state.
However, in the analogous art, Zhang explicitly discloses the first indication information is used by the terminal device to determine a Timing Advance TA of the terminal device in the non-connected state. (Fig. 3/ Fig. 5/Fig. 14-17 & Abstract - A user equipment (UE) may be configured with a set of parameters to determine a valid timing advance (TA) to transmit data using preconfigured uplink resources (PUR) during an idle or inactive mode. In some cases, the parameters are one or more TA commands and one or more conditions associated with each TA command. The UE may identify the current condition of the UE and determine whether the current condition of the UE matches one of indicated conditions. The UE may select a TA command based on finding a match and use the TA command to transmit an uplink PUR transmission. Also, see step 1410 in Fig. 14 & step 1510 in Fig. 15, also, see ¶0011/¶0174, claim 3).
Therefore, it would have been obvious to one of the ordinary skills in the art before the effective filling date of the claimed invention to combine Babaei’s invention of a mechanism for wireless device and wireless network in inactive state in a wireless communication system to include Zhang’s invention of timing advance command implementations mechanism for preconfigured uplink resource transmissions in a wireless communication system, because it provides an efficient mechanism for mitigating power consumption and transmission delay in the wireless communication system.(¶0002-¶0005, Zhang)
Re. claim 9, Babaei and Zhang teach claim 8.
Babaei further teaches sending, by the network device, second indication information to the terminal device in the non-connected state, the second indication information indicating a candidate time-frequency location of a physical downlink control channel (PDCCH). (Fig. 7/Fig. 17-46 & ¶0227- RRCRelease message may be used to command the release of an RRC connection or the suspension of the RRC connection. A suspendconfig IE in the RRCRelease message may indicate configuration for the RRC_INACTIVE state. The suspendconfig may comprise a plurality of parameters comprising a full-RNTI, a short-RNTI, a ran-PagingCycle, a ran-NotificationAreaInfo and a t380. The ran-PagingCycle may indicate a UE specific cycle for RAN-initiated paging. Fig. 7/Fig. 17-46 & ¶0228 - an IE SearchSpace may define how/where to search for PDCCH candidates. A search space may be associated with a ControlResourceSet. In an example, a parameter common may indicate that a search space is common search space (CSS) and may indicate DCI formats to monitor. A parameter controlResourceSetId may indicate the CORESET applicable for the SearchSpace. … The parameter monitoringSlotPeriodicityAndOffset may indicate slots for PDCCH Monitoring configured as periodicity and offset. The parameter monitoringSymbolsWithinSlot may indicate the first symbol(s) for PDCCH monitoring in the slots configured for PDCCH monitoring. Fig. 7/Fig. 17-46 & ¶0230 - The IE PDCCH-Config may be used to configure UE specific PDCCH parameters such as control resource sets (CORESET), search spaces and additional parameters for acquiring the PDCCH. In an example, a parameter controlResourceSetToAddModList may indicate a list of UE specifically configured Control Resource Sets (CORESETs) to be used by the wireless device. In an example, an IE PDCCH-ConfigCommon may be used to configure cell specific PDCCH parameters provided in SIB as well as in dedicated signaling. In an example, an IE ControlResourceSet may be used to configure a time/frequency control resource set (CORESET) in which to search for downlink control information).
Re. claim 10, Babaei and Zhang teach claim 8.
Babaei further teaches wherein the first indication information is carried in a radio resource control release (RRC Release) message or a paging message. (Fig. 31 & ¶0295 – a wireless device in a radio resource control (RRC) inactive state may receive paging information via a paging channel. The paging information may indicate scheduling information for receiving a timing advance value. For example, the paging information may comprise a field indicating the scheduling information. For example, the paging information may indicate a control resource set and/or search space for receiving a downlink assignment of a downlink packet, wherein the downlink packet may comprise the timing advance value. For example, the paging information may comprise the configuration parameters of the control resource set and/or the search space for receiving the scheduling information/downlink assignment for receiving a downlink packet comprising the timing advance value. The wireless device may receive the paging information via the paging channel and may determine the paging information and/or scheduling information associated with the wireless device and included in the received paging information based on a wireless device identifier/RNTI associated with the wireless device. …. the downlink packet may comprise a timing advance command MAC CE comprising the timing advance value).
Re. claim 11, Babaei and Zhang teach claim 9.
Babaei further teaches wherein the second indication information is carried in a radio resource control release (RRC Release) message or a paging message. (Fig. 7/Fig. 17-46 & ¶0227- RRCRelease message may be used to command the release of an RRC connection or the suspension of the RRC connection. A suspendconfig IE in the RRCRelease message may indicate configuration for the RRC_INACTIVE state. The suspendconfig may comprise a plurality of parameters comprising a full-RNTI, a short-RNTI, a ran-PagingCycle, a ran-NotificationAreaInfo and a t380. The ran-PagingCycle may indicate a UE specific cycle for RAN-initiated paging. Fig. 7/Fig. 17-46 & ¶0228 - an IE SearchSpace may define how/where to search for PDCCH candidates. A search space may be associated with a ControlResourceSet. In an example, a parameter common may indicate that a search space is common search space (CSS) and may indicate DCI formats to monitor. A parameter controlResourceSetId may indicate the CORESET applicable for the SearchSpace. … The parameter monitoringSlotPeriodicityAndOffset may indicate slots for PDCCH Monitoring configured as periodicity and offset. The parameter monitoringSymbolsWithinSlot may indicate the first symbol(s) for PDCCH monitoring in the slots configured for PDCCH monitoring. Fig. 7/Fig. 17-46 & ¶0230 - The IE PDCCH-Config may be used to configure UE specific PDCCH parameters such as control resource sets (CORESET), search spaces and additional parameters for acquiring the PDCCH. In an example, a parameter controlResourceSetToAddModList may indicate a list of UE specifically configured Control Resource Sets (CORESETs) to be used by the wireless device. In an example, an IE PDCCH-ConfigCommon may be used to configure cell specific PDCCH parameters provided in SIB as well as in dedicated signaling. In an example, an IE ControlResourceSet may be used to configure a time/frequency control resource set (CORESET) in which to search for downlink control information).
Re. claim 12, Babaei and Zhang teach claim 9.
Babaei further teaches wherein the second indication information comprises a control resource set identifier and a search space identifier. (Fig. 7/Fig. 17-46 & ¶0228 - an IE SearchSpace may define how/where to search for PDCCH candidates. A search space may be associated with a ControlResourceSet. In an example, a parameter common may indicate that a search space is common search space (CSS) and may indicate DCI formats to monitor. A parameter controlResourceSetId may indicate the CORESET applicable for the SearchSpace. … The parameter monitoringSlotPeriodicityAndOffset may indicate slots for PDCCH Monitoring configured as periodicity and offset. The parameter monitoringSymbolsWithinSlot may indicate the first symbol(s) for PDCCH monitoring in the slots configured for PDCCH monitoring…. The parameter searchSpaceId may identity the search space. Fig. 7/Fig. 17-46 & ¶0229 - an IE SearchSpaceId may be used to identify Search Spaces. Fig. 7/Fig. 17-46 & ¶0230 - The IE PDCCH-Config may be used to configure UE specific PDCCH parameters such as control resource sets (CORESET), search spaces and additional parameters for acquiring the PDCCH. In an example, a parameter controlResourceSetToAddModList may indicate a list of UE specifically configured Control Resource Sets (CORESETs) to be used by the wireless device. In an example, an IE PDCCH-ConfigCommon may be used to configure cell specific PDCCH parameters provided in SIB as well as in dedicated signaling. …., an IE ControlResourceSet may be used to configure a time/frequency control resource set (CORESET) in which to search for downlink control information… a ControlResourceSetId IE may indicate a short identity, used to identify a control resource set within a serving cell.)
Re. claim 13, Babaei and Zhang teach claim 9.
Babaei further teaches periodically sending, by the network device, the timing advance command (TAC) to the terminal device in the non-connected state (Fig. 42-43 & ¶0342 - a wireless device may receive first configuration parameters of a downlink semi-persistent scheduling (SPS) configuration. The downlink SPS configuration may be for receiving timing advance values for uplink transmissions during an RRC_INACTIVE state. For example, the first configuration parameters may comprise a parameter indicating that the downlink SPS configuration is for wireless device operation during the RRC_INACTIVE state and/or for receiving timing advance values during an RRC_INACTIVE state. Fig. 42-43 & ¶0343 - RRC release message or the suspend config IE in the RRC release message may comprise the first configuration parameters of the downlink SPS configuration and/or the second configuration parameters of the uplink configured grant configuration. Fig. 42-43 & ¶0344 - The wireless device may receive timing advance values, during the RRC_INACTIVE state, based on the first configuration parameters. The wireless device may receive downlink packets based on the first configuration parameters and via the downlink SPS resources, wherein the downlink packets may comprise the timing advance values. For example, the wireless device may receive timing advance command MAC CEs indicating the timing advance values, wherein the timing advance MAC CEs are multiplexed in the downlink packets. The first configuration parameters may comprise a first periodicity parameter. The wireless device may activate a plurality of downlink assignments based on the first periodicity parameter. For example, the wireless device may determine time occasions of the plurality of downlink assignments based on the first periodicity parameter. Fig. 42-43 & ¶0345 - The wireless device may transmit uplink packets, during the RRC_INACTIVE state, based on the second configuration parameters and based on the received timing advance values. The second configuration parameters may comprise a second periodicity parameter. The wireless device may determine a plurality of pre-configured/configured grant resources based on the second periodicity parameter).
Re. claim 14, Babaei and Zhang teach claim 10.
Babaei further teaches wherein the RRC Release message or the paging message further comprises time-frequency resource configuration information of a sounding reference signal (SRS). (Fig. 1-63 & ¶0319 - a wireless device may receive sounding reference signal (SRS) configuration parameters. The SRS configuration parameters may comprise first configuration parameters for SRS transmission while the wireless device is in an RRC_CONENCTED state and second configuration parameters for SRS transmission during an RRC_INACTIVE state. The wireless device may transmit SRS signals during the RRC_CONNECTED state using the first configuration parameters and may transmit SRS signals during the RRC_INACTIVE state use the second configuration parameters. Fig. 1-63 & ¶0320 - The wireless device may receive an RRC release message indicating transitioning from the RRC_CONNECTED state to the RRC_INACTIVE state and/or suspending an RRC connection for the wireless device. For example, the RRC release message may comprise a suspend config IE indicating the transition from the RRC_CONNECTED state to the RRC_INACTIVE state. The wireless device may transition from the RRC_CONNECTED state to the RRC_INACTIVE state based on the receiving the RRC release message. In an example, the suspend config IE may comprise second configuration parameters for SRS transmission during the RRC_INACTIVE state. Fig. 1-63 & ¶0322 - the second configuration parameters may comprise second parameters indicating second resources (e.g., second timing, second comb structure, etc.) for transmitting second SRS signals, during the RRC_INACTIVE state.)
Claim 15 is rejected under 35 U.S.C. 103 as being unpatentable over Babaei, in view of Zhang, further in view of Wang et al. (2022/0399976), Wang hereinafter
Re. claim 15, Babaei and Zhang teach claim 14.
Yet, Babaei and Zhang do not expressly teach performing, by the network device, related measurement on the SRS sent by the terminal device in the non-connected state to obtain a measurement result the measurement result assisting in positioning of the terminal device in the non-connected state.
However, in the analogous art, Wang explicitly discloses performing, by the network device, related measurement on the SRS sent by the terminal device in the non-connected state to obtain a measurement result the measurement result assisting in positioning of the terminal device in the non-connected state. (Fig. 1-13 & ¶0006: ¶0007 - provides a method for sending an SRS, applied to a terminal and including: sending a sounding reference signal SRS for positioning based on discontinuous reception DRX-related target information and/or a radio resource control RRC status. Fig. 1-13 & ¶0016 - where the third information includes at least one of the following: configuration information of an SRS for positioning and RRC state indicator information; and the third information is used to determine whether the terminal sends or does not send the SRS in an RRC non-connected state; Fig. 1-13 & ¶0205 - location management device may be implicitly notified to cancel, reconfigure, or re-request measurement on the SRS by the neighboring cell. That is, when the RRC connection state information in the RRC state indicator information indicates that the terminal is in an RRC idle state or an RRC inactive state, the location management device is implicitly notified to cancel, reconfigure, or re-request measurement on the SRS by the neighboring cell. Fig. 1-13 & ¶0272: ¶0274 - Step 125: The terminal sends an SRS for positioning based on DRX-related target information. Step 126: The location management device requests the neighboring cell by using the NRPPA to report a measurement result of the SRS. Step 127: The location management device requests the serving cell by using the NRPPA to report a measurement result of the SRS.)
Therefore, it would have been obvious to one of the ordinary skills in the art before the effective filling date of the claimed invention to combine Babaei’s invention of a mechanism for wireless device and wireless network in inactive state in a wireless communication system and Zhang’s invention of timing advance command implementations mechanism for preconfigured uplink resource transmissions in a wireless communication system to include Wang’s invention of a mechanism for sending an SRS (Sounding reference signal) for positioning based on RRC status in new radio (NR)/5G wireless communication system, because it provides an efficient mechanism in sending SRS (Sounding reference signal) measurement results with the help of neighboring cells of serving cells of a wireless device when the wireless device remains in RRC_INACTIVE state, improves radio resource utilization with signaling overhead for core network, thereby, improves latency sensitive application for small data transmission in the new radio (NR)/5G wireless communication system .(¶0002-¶0008, Wang)
Response to Arguments
Applicant's arguments filed on 04/16/2026 have been fully considered but they are not persuasive.
Regarding remarks in pages 8-9 for independent claims 1 and 16, the applicant argues that Babaei fails to teach the claimed limitation “receive first indication information from a network device, wherein the first indication information comprising a radio network temporary identifier (RNTI) of a timing advance command (TAC)”.
The applicant further asserts, “The rejection in the Office Action appears to conflate the ''wireless device identifier/RNTI'' in Babaei, which is used to find a paging record and/or DCI, as being equivalent to the claimed RNTI of a timing advance command (TAC). The Office Action then supplies Zhang to supply any remaining ''determine TA'' functionality (see Office Action, pages 7-10).”, contues in arguing, “Independent claim 1 requires a first indication information that includes a TAC-specific RNTI (i.e., a RNTI designed for the purpose of identifying and/or unscrambling timing advance command signaling), and not merely a RNTI for a UE identity (such as an inactive RNTI (I-RNTI) that is used for paging or generally addressing a UE. It should be understood that an ''RNTI of a TAC'' is a control channel addressing and/or scrambling identifier for TAC signaling itself. In contrast, Babaei's cited passages only describe using a UE identifier RNTI to select a paging record or to associate a received DCI with the UE (see Babaei at paragraphs [0290]-[0297]). Without a TAC-specific RNTI being included in the first indication information, Babaei cannot disclose the receiving limitation.”. See page 8 of remarks as submitted on 04/16/2026.
The applicant further contends, “Babaei's discussion of paging identifiers and general PDCCH/SearchSpace concepts never discloses sending or receiving any TAC-RNTI (or any TAC-addressing RNTI) as first indication information. Instead, Babaei repeatedly relies on a wireless device identifier/RNTI for paging association. The wireless device identifier/RNTI of Babaei does not read on the present claims. Babaei does not disclose receiving, by a terminal device in a non-connected state, first indication information from a network device, the first indication information comprising a radio network temporary identifier (RNTI) of a timing advance command (TAC).”. See page 9 of remarks as submitted on 04/16/2026.
Examiner respectfully disagrees with the applicant. For example, Babaei discloses that wireless device may receive an RRC release message comprising the configuration parameters. In an example, a suspend config in an RRC release message may comprise the configuration parameters. Babaei further discloses that a wireless device, in a radio resource control (RRC) inactive state, may receive paging information via a paging channel, the paging information indicating a timing advance value for the wireless device….. the wireless device may receive configuration parameters comprising a wireless device identity/RNTI, wherein: the paging information comprises a paging record comprising the wireless device identity/RNTI; and the paging record comprises/indicates the timing advance value. In an example, the wireless device may receive an RRC release message comprising the configuration parameters. … the RRC release message may comprise a suspend config information element comprising a parameter indicating the wireless device identity/RNTI. In an example, the wireless device identity may be a full wireless device identity/RNTI. In an example, the wireless device identity may be a short wireless device identity/RNTI.
In other words, in RRC In active state (i.e., non-connected mode, see at least Fig. 30-31), the wireless device receives the timing advance value both in paging information via a paging channel along with wireless device identity/RNTI <the RNTI may either be a full wireless device identity/RNTI or a short wireless device identity/RNTI, interpreted as a RNTI-TAC, as because, the received RNTI is associated with timing advanced value (a TAC specific RNTI, timing advance command MAC CE comprising the timing advance value, see ¶0295), which is used by the wireless device in transmitting an uplink packet via a configured grant resource and based on the timing advance value, see ¶0401 & Fig. 30> or the wireless device receives RRC release message, contains suspend config IE comprising a parameter indicating the wireless device identity/RNTI, which may either be a full wireless device identity/RNTI or a short wireless device identity/RNTI, interpreted as a RNTI-TAC, for reasons as explained supra.
In fact, the aforesaid disclosure for receiving a RNTI-TAC (i.e., wireless device identity/RNTI, which may either be a full wireless device identity/RNTI or a short wireless device identity/RNTI as explained supra) by a wireless device either in paging information via a paging channel, or in RRC release message in RRC In active state (i.e., non-connected mode/state, as shown in at least Fig. 30-31) by Babaei, are very similar inventive concept as claimed and disclosed by the instant application, at least in ¶0012-¶0014, for example, the instant application recites, “the first indication information is carried in an RRC Release message or a paging message. … the terminal device in the non-connected state can obtain the first indication information from the RRC Release message or the paging message, so that TA calculation of the terminal device in the non-connected state is implemented, the second indication information is carried in the RRC Release message or the paging message.”. Moreover, SuspendConfig field of RRC release message contains related to TAC-RNTI as per instant application at least in ¶0178, similarly, Babaei discloses that RRC release message may comprise a suspend config information element comprising one or more configuration parameters for the RRC inactive state. … the suspend config information element may comprise one or more wireless device identifiers (e.g., one or more radio network temporary identifiers). …. the one or more identifiers/RNTIs may comprise a full inactive state RNTI and a short inactive state RNTI. As explained supra, the RNTI <which is defined in suspend config IE, as received by the wireless device in RRC release message in RRC inactive > may either be a full wireless device identity/RNTI or a short wireless device identity/RNTI, interpreted as a RNTI-TAC, as because, the received RNTI is associated with timing advanced value (a TAC specific RNTI, timing advance command MAC CE comprising the timing advance value, see ¶0295), which is used by the wireless device in transmitting an uplink packet via a configured grant resource and based on the timing advance value, see ¶0401 & Fig. 30, quite a contrast to applicant’s argument at least at pages 8-9 of remarks as submitted on 04/16/2026.
Regarding arguments in page 9 for motivation to combine Zhang's reference with the reference of Babaei:
In response of applicant’s argument that Zhang’s reference would not be an obvious combination with the teachings of Babae so as to suggest applicants' invention. The Examiner would like to point out the following statement as identified by court “It is not required that the prior art disclose or suggest the properties newly-discovered by an applicant in order for there to be a prima facie case of obviousness. See In re Dillon, 919 F.2d 688, 16 USPQ2d 1897, 1905 (Fed. Cir. 1990). Moreover, as long as some motivation or suggestion to combine the references is provided by the prior art taken as a whole, the law does not require that the references be combined for the reasons contemplated by the inventor. See In re Beattie, 974 F.2d 1309, 24 USPQ2d 1040 (Fed. Cir. 1992); In re Kronig, 539 F.2d 1300, 190 USPQ 425 (CCPA 1976) and In re Wilder, 429 F.2d 447, 166 USPQ 545 (CCPA 1970)”. In this case, the suggestion to combine the references, is provided by Zhang, as because, Zhang provides an efficient mechanism for mitigating power consumption and transmission delay in the wireless communication system.(¶0002-¶0005, Zhang)
Similar, arguments are applicable to independent claim 8.
For these reasons, it is maintained that independent claims 1 and 16 are rejected under 35 U.S.C. 103 as being unpatentable over Babaei, in view of, Zhang.
For similar reasons, it is maintained that independent claim 8 is rejected under 35 U.S.C. 103 as being unpatentable over Babaei, in view of, Zhang.
As all other dependent claims depend either directly or indirectly from the independent claims 1, 8 and 16, similar rationale also applies to all respective dependent claims.
Conclusion
THIS ACTION IS MADE FINAL. 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