Prosecution Insights
Last updated: April 19, 2026
Application No. 18/065,950

PHYSICAL DOWNLINK CONTROL CHANNEL MONITORING

Non-Final OA §103
Filed
Dec 14, 2022
Examiner
LINDENBAUM, ALAN LOUIS
Art Unit
2413
Tech Center
2400 — Computer Networks
Assignee
Qualcomm Incorporated
OA Round
3 (Non-Final)
48%
Grant Probability
Moderate
3-4
OA Rounds
3y 7m
To Grant
64%
With Interview

Examiner Intelligence

Grants 48% of resolved cases
48%
Career Allow Rate
204 granted / 421 resolved
-9.5% vs TC avg
Strong +16% interview lift
Without
With
+15.8%
Interview Lift
resolved cases with interview
Typical timeline
3y 7m
Avg Prosecution
69 currently pending
Career history
490
Total Applications
across all art units

Statute-Specific Performance

§101
2.2%
-37.8% vs TC avg
§103
56.7%
+16.7% vs TC avg
§102
20.4%
-19.6% vs TC avg
§112
17.5%
-22.5% vs TC avg
Black line = Tech Center average estimate • Based on career data from 421 resolved cases

Office Action

§103
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. 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. Claim(s) 1-3, 5-6, 8-9, 11, 13, 15-18, 20-21, 23-24, 26, 28, 30-31 and 33 and 35-38 is/are rejected under 35 U.S.C. 103 as being unpatentable over Dalsgaard et al. (US 2015/0009832) in view of Murray et al. (US 2022/0191793). Regarding claim 1, Dalsgaard discloses a method of wireless communication performed by a user equipment (UE) (Dalsgaard, paragraph [0002], 3GPP communication systems, UE, E-UTRAN), comprising: receiving configuration information associated with connected mode discontinuous reception (CDRX) communications (Dalsgaard, paragraph [0006], connected mode DRX configured by the network, DRX configuration), wherein the configuration information configures the UE to indicate whether the UE is to perform physical downlink control channel (PDCCH) monitoring after transmitting a buffer status report (Dalsgaard, paragraph [0006], connected mode DRX configured by the network, DRX configuration; paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0039], monitor the PDCCH according to the selected set of DRX parameters; paragraph [0047], transition between PDCCH monitoring states can be based on updating the limit of the buffer size; paragraph [0048], buffer status report transmitted when the buffer changes so significantly that the change has impact on the PDCCH monitoring and the UE wants that change to take effect; paragraph [0055], instantaneous buffer status configured to permit the network device to determine monitoring of the downlink channel in active time); transmitting a buffer status report having a buffer status value that is greater than zero (Dalsgaard, paragraph [0045], buffer status report can hold information concerning the amount of data pending); if a latency requirement of data flow associated with the buffer status report satisfies a latency threshold (Dalsgaard, paragraph [0025], data flow needs impact UE active time to adjust PDCCH monitoring requirements; paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0038], determine whether to use DRX parameter set 1 or set 2 based on threshold for amount of data expected to be transmitted in a time window), initiating an active state of the UE and performing physical downlink control channel (PDCCH) monitoring after transmitting the buffer status report (Dalsgaard, paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0039], monitor the PDCCH according to the selected set of DRX parameters; paragraph [0047], transition between PDCCH monitoring states can be based on updating the limit of the buffer size; paragraph [0048], buffer status report transmitted when the buffer changes so significantly that the change has impact on the PDCCH monitoring and the UE wants that change to take effect; paragraph [0055], instantaneous buffer status configured to permit the network device to determine monitoring of the downlink channel in active time); and if the latency requirement does not satisfy the latency threshold, waiting for a next active state of the UE to perform PDCCH monitoring after transmitting the buffer status report (Dalsgaard, paragraph [0025], data flow needs impact PDCCH monitoring requirements; paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0038], determine whether to use DRX parameter set 1 or set 2 based on threshold for amount of data expected to be transmitted in a time window). Although Dalsgaard discloses all of the claim limitations, in order to facilitate prosecution, the Examiner includes the Murray reference, which more explicitly discloses modifying the time when an active state (on-duration) is initiated. Murray discloses a method of wireless communication performed by a user equipment (UE) (Murray, paragraph [0002], wireless communications system with UE; paragraph [0032], WTRU’s, base stations, wireless communications), comprising: receiving configuration information associated with connected mode discontinuous reception (CDRX) communications (Murray, paragraph [0005], receive DRX configurations; paragraph [0127], for C-DRX, configuration is provided by the network via RRC signaling to control the UE’s PDCCH monitoring activity), wherein the configuration information configures the UE with one or more logical channel groups (LCGs) (Murray, paragraph [0193], logical channel group (LCG)) to indicate whether the UE is to perform physical downlink control channel (PDCCH) monitoring after transmitting a buffer status report (Murray, paragraph [0127], for C-DRX, configuration is provided by the network via RRC signaling to control the UE’s PDCCH monitoring activity; paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; paragraph [0193], use BSR to inform the base station of the traffic pattern type, link between BSR and traffic pattern/type through association of logical channel group (LCG) to traffic pattern/type, traffic pattern/type may be implicitly derived by the UE from the LCG configuration; paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time); transmitting a buffer status report having a buffer status value that is greater than zero (Murray, paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; paragraph [0193], use BSR to information the base station of the traffic pattern type; paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time); and if a latency requirement of data flow associated with the buffer status report satisfies a latency threshold and if the UE is configured with a LCG, initiating an active state of the UE and performing physical downlink control channel (PDCCH) monitoring after transmitting the buffer status report (Murray, paragraph [0030], requirements for data rate and latency; paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; paragraph [0193], use BSR to inform the base station of the traffic pattern type, link between BSR and traffic pattern/type through association of logical channel group (LCG) to traffic pattern/type, traffic pattern/type may be implicitly derived by the UE from the LCG configuration; paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time; paragraph [0213], delay tolerance); and if the latency requirement does not satisfy the latency threshold (Murray, paragraph [0030], requirements for data rate and latency; paragraph [0213], delay tolerance), waiting for a next active state of the UE to perform PDCCH monitoring after transmitting the buffer status report (Murray, paragraph [0193], use BSR to inform the base station of the traffic pattern type, link between BSR and traffic pattern/type through association of logical channel group (LCG) to traffic pattern/type, traffic pattern/type may be implicitly derived by the UE from the LCG configuration; paragraph [0210], for some UE traffic, the UE could wait until the next DRX cycle or until other high priority data becomes available for UL transmission). It would have been obvious to a person of ordinary skill in the art, before the effective filing date of the claimed invention, to modifying the time when an active state (on-duration) is initiated, in the invention of Dalsgaard. The motivation to combine the references would have been to receive an uplink grant sooner to reduce latency (Murray, paragraph [0126], minimize impact on latency). Regarding claim 2, Dalsgaard in view of Murray discloses the method of claim 1, wherein initiating the active state of the UE comprises switching from an inactive state of the UE to the active state of the UE (Dalsgaard, paragraph [0047], transition between PDCCH monitoring states can be based on updating the limit of the buffer size; paragraph [0055], instantaneous buffer status configured to permit the network device to determine monitoring of the downlink channel in active time) (Murray, paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; paragraph [0193], use BSR to information the base station of the traffic pattern type; paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time). Regarding claim 3, Dalsgaard in view of Murray discloses the 3. The method of claim 1, wherein the configuration information indicates for the UE to initiate the active state of the UE and to perform the PDCCH monitoring based at least in part on transmitting the buffer status report (Dalsgaard, paragraph [0006], connected mode DRX configured by the network, DRX configuration; paragraph [0047], transition between PDCCH monitoring states can be based on updating the limit of the buffer size; paragraph [0055], instantaneous buffer status configured to permit the network device to determine monitoring of the downlink channel in active time) (Murray, paragraph [0127], for C-DRX, configuration is provided by the network via RRC signaling to control the UE’s PDCCH monitoring activity; paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; paragraph [0193], use BSR to information the base station of the traffic pattern type; paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time). Regarding claim 5, Dalsgaard in view of Murray discloses the method of claim 1, wherein performing the PDCCH monitoring is associated with the data flow (Dalsgaard, paragraph [0025], data flow needs impact PDCCH monitoring requirements). Regarding claim 6, Dalsgaard in view of Murray discloses the method of claim 1, further comprising waiting a time period to transmit data associated with another data flow based at least in part on the other data flow having a latency requirement that does not satisfy the latency threshold (Murray, paragraph [0210], for some UE traffic, the UE could wait until the next DRX cycle or until other high priority data becomes available for UL transmission). Regarding claim 7, Dalsgaard in view of Murray discloses the method of claim 1, wherein the UE is configured with one or more logical channel groups (Murray, paragraph [0193], logical channel group (LCG)). Regarding claim 8, Dalsgaard in view of Murray discloses the method of claim 1, wherein transmitting the buffer status report comprises transmitting the buffer status report while operating in a CDRX communication mode of the UE (Dalsgaard, paragraph [0006], connected mode DRX configured by the network, DRX configuration; paragraph [0045], buffer status report can hold information concerning the amount of data pending). Regarding claim 9, Dalsgaard in view of Murray discloses the method of claim 1, wherein the CDRX communications are reality communications (Murray, paragraph [0030], augmented reality, virtual reality). Regarding claim 11, Dalsgaard discloses a method of wireless communication performed by a network node (Dalsgaard, paragraph [0002], 3GPP communication systems, UE, E-UTRAN), comprising: transmitting configuration information associated with connected mode discontinuous reception (CDRX) communications (Dalsgaard, paragraph [0006], connected mode DRX configured by the network, DRX configuration), wherein the configuration information configures the UE) to indicate whether the UE is to perform physical downlink control channel (PDCCH) monitoring after transmitting a buffer status report (Dalsgaard, paragraph [0006], connected mode DRX configured by the network, DRX configuration; paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0039], monitor the PDCCH according to the selected set of DRX parameters; paragraph [0047], transition between PDCCH monitoring states can be based on updating the limit of the buffer size; paragraph [0048], buffer status report transmitted when the buffer changes so significantly that the change has impact on the PDCCH monitoring and the UE wants that change to take effect; paragraph [0055], instantaneous buffer status configured to permit the network device to determine monitoring of the downlink channel in active time); receiving a buffer status report having a buffer status value that is greater than zero (Dalsgaard, paragraph [0045], buffer status report can hold information concerning the amount of data pending); transmitting a physical downlink control channel (PDCCH) communication based at least in part on receiving the buffer status report (Dalsgaard, paragraph [0006], connected mode DRX configured by the network, DRX configuration; paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0039], monitor the PDCCH according to the selected set of DRX parameters), wherein the configuration information indicates for the UE to: if a latency requirement of data flow associated with the buffer status report satisfies a latency threshold (Dalsgaard, paragraph [0025], data flow needs impact UE active time to adjust PDCCH monitoring requirements; paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0038], determine whether to use DRX parameter set 1 or set 2 based on threshold for amount of data expected to be transmitted in a time window), initiate an active state of the UE and performing physical downlink control channel (PDCCH) monitoring after transmitting the buffer status report (Dalsgaard, paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0039], monitor the PDCCH according to the selected set of DRX parameters; paragraph [0047], transition between PDCCH monitoring states can be based on updating the limit of the buffer size; paragraph [0048], buffer status report transmitted when the buffer changes so significantly that the change has impact on the PDCCH monitoring and the UE wants that change to take effect; paragraph [0055], instantaneous buffer status configured to permit the network device to determine monitoring of the downlink channel in active time); and if the latency requirement does not satisfy the latency threshold, wait for a next active state of the UE to perform PDCCH monitoring after transmitting the buffer status report (Dalsgaard, paragraph [0025], data flow needs impact PDCCH monitoring requirements; paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0038], determine whether to use DRX parameter set 1 or set 2 based on threshold for amount of data expected to be transmitted in a time window). Although Dalsgaard discloses all of the claim limitations, in order to facilitate prosecution, the Examiner includes the Murray reference, which more explicitly discloses modifying the time when an active state (on-duration) is initiated. Murray discloses a method of wireless communication performed by a user equipment (UE) (Murray, paragraph [0002], wireless communications system with UE; paragraph [0032], WTRU’s, base stations, wireless communications), comprising: transmitting configuration information associated with connected mode discontinuous reception (CDRX) communications (Murray, paragraph [0005], receive DRX configurations; paragraph [0127], for C-DRX, configuration is provided by the network via RRC signaling to control the UE’s PDCCH monitoring activity), wherein the configuration information configures the UE with one or more logical channel groups (LCGs) (Murray, paragraph [0193], logical channel group (LCG)) to indicate whether the UE is to perform physical downlink control channel (PDCCH) monitoring after transmitting a buffer status report (Murray, paragraph [0127], for C-DRX, configuration is provided by the network via RRC signaling to control the UE’s PDCCH monitoring activity; paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; paragraph [0193], use BSR to inform the base station of the traffic pattern type, link between BSR and traffic pattern/type through association of ] logical channel group (LCG) to traffic pattern/type, traffic pattern/type may be implicitly derived by the UE from the LCG configuration; paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time); receiving a buffer status report having a buffer status value that is greater than zero (Murray, paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; paragraph [0193], use BSR to information the base station of the traffic pattern type; paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time); and transmitting a physical downlink control channel (PDCCH) communication based at least in part on receiving the buffer status report (Murray, paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; paragraph [0193], use BSR to information the base station of the traffic pattern type; paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time; paragraph [0205], transmission of PDCCH), wherein the configuration information indicates for the UE to: if a latency requirement of data flow associated with the buffer status report satisfies a latency threshold and if the UE is configured with a LCG, initiate an active state of the UE and performing physical downlink control channel (PDCCH) monitoring after transmitting the buffer status report (Murray, paragraph [0030], requirements for data rate and latency; paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; paragraph [0193], use BSR to inform the base station of the traffic pattern type, link between BSR and traffic pattern/type through association of ] logical channel group (LCG) to traffic pattern/type, traffic pattern/type may be implicitly derived by the UE from the LCG configuration; paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time; paragraph [0213], delay tolerance); and if the latency requirement does not satisfy the latency threshold (Murray, paragraph [0030], requirements for data rate and latency; paragraph [0213], delay tolerance), wait for a next active state of the UE to perform PDCCH monitoring after transmitting the buffer status report (Murray, paragraph [0193], use BSR to inform the base station of the traffic pattern type, link between BSR and traffic pattern/type through association of ] logical channel group (LCG) to traffic pattern/type, traffic pattern/type may be implicitly derived by the UE from the LCG configuration; paragraph [0210], for some UE traffic, the UE could wait until the next DRX cycle or until other high priority data becomes available for UL transmission). It would have been obvious to a person of ordinary skill in the art, before the effective filing date of the claimed invention, to modifying the time when an active state (on-duration) is initiated, in the invention of Dalsgaard. The motivation to combine the references would have been to receive an uplink grant sooner to reduce latency (Murray, paragraph [0126], minimize impact on latency). Claim 13 are rejected under substantially the same rationale as claim 1. Regarding claim 15, Dalsgaard in view of Murray discloses the method of claim 11, further comprising: receiving a buffer status report from another UE that is configured with one or more other logical channel groups that are not configured with configuration information that indicates to perform PDCCH monitoring based at least in part on transmitting the buffer status report (Dalsgaard, paragraph [0006], connected mode DRX configured by the network, DRX configuration; paragraph [0047], transition between PDCCH monitoring states can be based on updating the limit of the buffer size; paragraph [0055], instantaneous buffer status configured to permit the network device to determine monitoring of the downlink channel in active time) (Murray, paragraph [0127], for C-DRX, configuration is provided by the network via RRC signaling to control the UE’s PDCCH monitoring activity; paragraph [0136], legacy DRX; paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; paragraph [0193], use BSR to inform the base station of the traffic pattern type, link between BSR and traffic pattern/type through association of ] logical channel group (LCG) to traffic pattern/type, traffic pattern/type may be implicitly derived by the UE from the LCG configuration; paragraph [0193], logical channel group (LCG); paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time); and refraining from transmitting the PDCCH communication to the other UE based at least in part on the other UE being configured with the one or more other logical channel groups (Murray, paragraph [0193], use BSR to inform the base station of the traffic pattern type, link between BSR and traffic pattern/type through association of ] logical channel group (LCG) to traffic pattern/type, traffic pattern/type may be implicitly derived by the UE from the LCG configuration; paragraph [0210], for some UE traffic, the UE could wait until the next DRX cycle or until other high priority data becomes available for UL transmission). Regarding claim 16, Dalsgaard discloses a method of wireless communication performed by a user equipment (UE) (Dalsgaard, paragraph [0002], 3GPP communication systems, UE, E-UTRAN), comprising: receiving configuration information associated with physical downlink control channel (PDCCH) monitoring (Dalsgaard, paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0039], monitor the PDCCH according to the selected set of DRX parameters; paragraph [0047], transition between PDCCH monitoring states can be based on updating the limit of the buffer size; paragraph [0048], buffer status report transmitted when the buffer changes so significantly that the change has impact on the PDCCH monitoring and the UE wants that change to take effect; paragraph [0055], instantaneous buffer status configured to permit the network device to determine monitoring of the downlink channel in active time), wherein the configuration information configures the UE) to indicate whether the UE is to perform physical downlink control channel (PDCCH) monitoring after transmitting a buffer status report (Dalsgaard, paragraph [0006], connected mode DRX configured by the network, DRX configuration; paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0039], monitor the PDCCH according to the selected set of DRX parameters; paragraph [0047], transition between PDCCH monitoring states can be based on updating the limit of the buffer size; paragraph [0048], buffer status report transmitted when the buffer changes so significantly that the change has impact on the PDCCH monitoring and the UE wants that change to take effect; paragraph [0055], instantaneous buffer status configured to permit the network device to determine monitoring of the downlink channel in active time); transmitting a buffer status report having a buffer status value that is greater than zero (Dalsgaard, paragraph [0045], buffer status report can hold information concerning the amount of data pending); if a latency requirement of data flow associated with the buffer status report satisfies a latency threshold (Dalsgaard, paragraph [0025], data flow needs impact UE active time to adjust PDCCH monitoring requirements; paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0038], determine whether to use DRX parameter set 1 or set 2 based on threshold for amount of data expected to be transmitted in a time window initiate an active state of the UE and performing physical downlink control channel (PDCCH) monitoring after transmitting the buffer status report (Dalsgaard, paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0039], monitor the PDCCH according to the selected set of DRX parameters; paragraph [0047], transition between PDCCH monitoring states can be based on updating the limit of the buffer size; paragraph [0048], buffer status report transmitted when the buffer changes so significantly that the change has impact on the PDCCH monitoring and the UE wants that change to take effect; paragraph [0055], instantaneous buffer status configured to permit the network device to determine monitoring of the downlink channel in active time); and if the latency requirement does not satisfy the latency threshold, waiting for a next active state of the UE to perform PDCCH monitoring after transmitting the buffer status report (Dalsgaard, paragraph [0025], data flow needs impact PDCCH monitoring requirements; paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0038], determine whether to use DRX parameter set 1 or set 2 based on threshold for amount of data expected to be transmitted in a time window). Dalsgaard does not explicitly disclose PDCCH skipping. Murray discloses a method of wireless communication performed by a user equipment (UE) (Murray, paragraph [0002], wireless communications system with UE; paragraph [0032], WTRU’s, base stations, wireless communications), comprising: receiving configuration information associated with physical downlink control channel (PDCCH) skipping (Murray, paragraph [0005], receive DRX configurations; paragraph [0127], for C-DRX, configuration is provided by the network via RRC signaling to control the UE’s PDCCH monitoring activity; paragraph [0140], DCI-based PDCCH monitoring skipping), wherein the configuration information configures the UE with one or more logical channel groups (LCGs) (Murray, paragraph [0193], logical channel group (LCG)) to indicate whether the UE is to perform physical downlink control channel (PDCCH) monitoring after transmitting a buffer status report (Murray, paragraph [0127], for C-DRX, configuration is provided by the network via RRC signaling to control the UE’s PDCCH monitoring activity; paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; paragraph [0193], use BSR to inform the base station of the traffic pattern type, link between BSR and traffic pattern/type through association of ] logical channel group (LCG) to traffic pattern/type, traffic pattern/type may be implicitly derived by the UE from the LCG configuration; paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time); transmitting a buffer status report having a buffer status value that is greater than zero (Murray, paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; paragraph [0193], use BSR to information the base station of the traffic pattern type; paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time); and if a latency requirement of data flow associated with the buffer status report satisfies a latency threshold and if the UE is configured with a LCG, initiate an active state of the UE and performing physical downlink control channel (PDCCH) monitoring after transmitting the buffer status report (Murray, paragraph [0030], requirements for data rate and latency; paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; paragraph [0193], use BSR to inform the base station of the traffic pattern type, link between BSR and traffic pattern/type through association of ] logical channel group (LCG) to traffic pattern/type, traffic pattern/type may be implicitly derived by the UE from the LCG configuration; paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time; paragraph [0213], delay tolerance); and if the latency requirement does not satisfy the latency threshold (Murray, paragraph [0030], requirements for data rate and latency; paragraph [0213], delay tolerance), waiting for a next active state of the UE to perform PDCCH monitoring after transmitting the buffer status report (Murray, paragraph [0193], use BSR to inform the base station of the traffic pattern type, link between BSR and traffic pattern/type through association of ] logical channel group (LCG) to traffic pattern/type, traffic pattern/type may be implicitly derived by the UE from the LCG configuration; paragraph [0210], for some UE traffic, the UE could wait until the next DRX cycle or until other high priority data becomes available for UL transmission). It would have been obvious to a person of ordinary skill in the art, before the effective filing date of the claimed invention, to use PDCCH skipping, in the invention of Dalsgaard. The motivation to combine the references would have been to reduce power consumption. Claims 17-18 and 20-21 are rejected under substantially the same rationale as claims 3, 3, 5 and 6, respectively. Regarding claim 23, Dalsgaard in view of Murray discloses the method of claim 16, wherein transmitting the buffer status report comprises transmitting the buffer status report while operating in a PDCCH skipping mode of the UE (Murray, paragraph [0140], DCI-based PDCCH monitoring skipping). Claims 24 are rejected under substantially the same rationale as claims 9, respectively. Regarding claim 26, Dalsgaard discloses a method of wireless communication performed by a network node (Dalsgaard, paragraph [0002], 3GPP communication systems, UE, E-UTRAN), comprising: transmitting configuration information associated with physical downlink control channel (PDCCH) monitoring (Dalsgaard, paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0039], monitor the PDCCH according to the selected set of DRX parameters; paragraph [0047], transition between PDCCH monitoring states can be based on updating the limit of the buffer size; paragraph [0048], buffer status report transmitted when the buffer changes so significantly that the change has impact on the PDCCH monitoring and the UE wants that change to take effect; paragraph [0055], instantaneous buffer status configured to permit the network device to determine monitoring of the downlink channel in active time), wherein the configuration information configures the UE) to indicate whether the UE is to perform physical downlink control channel (PDCCH) monitoring after transmitting a buffer status report (Dalsgaard, paragraph [0006], connected mode DRX configured by the network, DRX configuration; paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0039], monitor the PDCCH according to the selected set of DRX parameters; paragraph [0047], transition between PDCCH monitoring states can be based on updating the limit of the buffer size; paragraph [0048], buffer status report transmitted when the buffer changes so significantly that the change has impact on the PDCCH monitoring and the UE wants that change to take effect; paragraph [0055], instantaneous buffer status configured to permit the network device to determine monitoring of the downlink channel in active time); receiving a buffer status report having a buffer status value that is greater than zero (Dalsgaard, paragraph [0045], buffer status report can hold information concerning the amount of data pending); transmitting a physical downlink control channel (PDCCH) communication based at least in part on receiving the buffer status report (Dalsgaard, paragraph [0006], connected mode DRX configured by the network, DRX configuration; paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0039], monitor the PDCCH according to the selected set of DRX parameters;, wherein the configuration information indicates for the UE to: if a latency requirement of data flow associated with the buffer status report satisfies a latency threshold (Dalsgaard, paragraph [0025], data flow needs impact UE active time to adjust PDCCH monitoring requirements; paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0038], determine whether to use DRX parameter set 1 or set 2 based on threshold for amount of data expected to be transmitted in a time window), performing physical downlink control channel (PDCCH) monitoring after transmitting the buffer status report (Dalsgaard, paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0039], monitor the PDCCH according to the selected set of DRX parameters; paragraph [0047], transition between PDCCH monitoring states can be based on updating the limit of the buffer size; paragraph [0048], buffer status report transmitted when the buffer changes so significantly that the change has impact on the PDCCH monitoring and the UE wants that change to take effect; paragraph [0055], instantaneous buffer status configured to permit the network device to determine monitoring of the downlink channel in active time); and if the latency requirement does not satisfy the latency threshold, waiting for a next active state of the UE to perform PDCCH monitoring after transmitting the buffer status report (Dalsgaard, paragraph [0025], data flow needs impact PDCCH monitoring requirements; paragraph [0032], status of the buffer status report influences the on-duration; paragraph [0038], determine whether to use DRX parameter set 1 or set 2 based on threshold for amount of data expected to be transmitted in a time window). Dalsgaard does not explicitly disclose PDCCH skipping. Murray discloses a method of wireless communication performed by a user equipment (UE) (Murray, paragraph [0002], wireless communications system with UE; paragraph [0032], WTRU’s, base stations, wireless communications), comprising: transmitting configuration information associated with physical downlink control channel (PDCCH) skipping (Murray, paragraph [0005], receive DRX configurations; paragraph [0127], for C-DRX, configuration is provided by the network via RRC signaling to control the UE’s PDCCH monitoring activity; paragraph [0140], DCI-based PDCCH monitoring skipping), wherein the configuration information configures the UE with one or more logical channel groups (LCGs) (Murray, paragraph [0193], logical channel group (LCG)) to indicate whether the UE is to perform physical downlink control channel (PDCCH) monitoring after transmitting a buffer status report (Murray, paragraph [0127], for C-DRX, configuration is provided by the network via RRC signaling to control the UE’s PDCCH monitoring activity; paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; paragraph [0193], use BSR to inform the base station of the traffic pattern type, link between BSR and traffic pattern/type through association of logical channel group (LCG) to traffic pattern/type, traffic pattern/type may be implicitly derived by the UE from the LCG configuration; paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time); receiving a buffer status report having a buffer status value that is greater than zero (Murray, paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; paragraph [0193], use BSR to information the base station of the traffic pattern type; paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time); and transmitting a physical downlink control channel (PDCCH) communication based at least in part on receiving the buffer status report (Murray, paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; paragraph [0193], use BSR to information the base station of the traffic pattern type; paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time; paragraph [0205], transmission of PDCCH); if a latency requirement of data flow associated with the buffer status report satisfies a latency threshold and if the UE is configured with a LCG, performing physical downlink control channel (PDCCH) monitoring after transmitting the buffer status report (Murray, paragraph [0030], requirements for data rate and latency; paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; paragraph [0193], use BSR to inform the base station of the traffic pattern type, link between BSR and traffic pattern/type through association of ] logical channel group (LCG) to traffic pattern/type, traffic pattern/type may be implicitly derived by the UE from the LCG configuration; paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time; paragraph [0213], delay tolerance); and if the latency requirement does not satisfy the latency threshold (Murray, paragraph [0030], requirements for data rate and latency; paragraph [0213], delay tolerance), waiting for a next active state of the UE to perform PDCCH monitoring after transmitting the buffer status report (Murray, paragraph [0193], use BSR to inform the base station of the traffic pattern type, link between BSR and traffic pattern/type through association of ] logical channel group (LCG) to traffic pattern/type, traffic pattern/type may be implicitly derived by the UE from the LCG configuration; paragraph [0210], for some UE traffic, the UE could wait until the next DRX cycle or until other high priority data becomes available for UL transmission). It would have been obvious to a person of ordinary skill in the art, before the effective filing date of the claimed invention, to use PDCCH skipping, in the invention of Dalsgaard. The motivation to combine the references would have been to reduce power consumption. Claims 28 and 30 are rejected under substantially the same rationale as claims 16 and 15, respectively. Claims 31 and 33 are rejected under substantially the same rationale as claim 9. Claims 35-36 are rejected under substantially the same rationale as claims 3 and 8, respectively. Claims 37-38 are rejected under substantially the same rationale as claims 3 and 8, respectively. Claim(s) 2, 10, 32 and 34 is/are rejected under 35 U.S.C. 103 as being unpatentable over Dalsgaard et al. (US 2015/0009832) in view of Murray et al. (US 2022/0191793), and further in view of Tsai et al. (US 2022/0078881). Regarding claim 10, Dalsgaard in view of Murray discloses the method of claim 1, wherein the CDRX communications are associated with a configured grant (Dalsgaard, paragraph [0039], uplink or downlink grant) (Murray, paragraph [0121], uplink grant) that does not require a hybrid automatic repeat request retransmission timer (a person of ordinary skill in the art, at the time of the invention, would have known that a HARQ timer is not required for all wireless communications). Although Dalsgaard in view of Murray discloses all of the claim limitations; in order to facilitate prosecution, the Examiner includes the Tsai reference, which more explicitly discloses a configured grant that does not require a hybrid automatic repeat request retransmission timer. Tsai discloses that CDRX communications (Tsai, paragraph [0082], RRC connected DRX) are associated with a configured grant (Tsai, paragraph [0039], uplink or downlink grant) that does not require a hybrid automatic repeat request retransmission timer (Tsai, paragraph [0009], no timer for HARQ process in a case that HARQ retransmissions for the HARQ process is disabled). It would have been obvious to a person of ordinary skill in the art, before the effective filing date of the claimed invention, to use a configured grant that does not require a hybrid automatic repeat request retransmission timer, in the invention of Dalsgaard. The motivation to combine the references would have been to conserve wireless resources. Claims 25, 32 and 34 is rejected under substantially the same rationale as claim 10. Response to Arguments Applicant's arguments filed October 29, 2025 have been fully considered but they are not persuasive. Applicant asserts that the claims are patentable because Dalsgaard and Murray allegedly do not condition initiating an active state or performing PDCCH monitoring based on whether the UE is configured with an LCG. However, this is incorrect. Murray discloses, for example in paragraph [0127], for C-DRX, configuration is provided by the network via RRC signaling to control the UE’s PDCCH monitoring activity; and in paragraph [0159], tie BSR signaling to traffic pattern type, UE autonomously select a certain PDCCH monitoring pattern which traffic type/pattern is selected; and in paragraph [0193], use BSR to inform the base station of the traffic pattern type, link between BSR and traffic pattern/type through association of logical channel group (LCG) to traffic pattern/type, traffic pattern/type may be implicitly derived by the UE from the LCG configuration; paragraph [0195], UE may adapt the DRX active time to shorten the DRX inactive time. Accordingly, in Murray, if the UE is configured with an LCG that is associated with PDCCH monitoring pattern, the UE selects a PDCCH monitoring pattern and adapts the DRX active time to that PDCCH monitoring pattern based on the UE’s configuration with that LCG. This is the same scenario that is disclosed in paragraph [0115] of Applicant’s Specification, upon which the claim language is based. Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to ALAN LOUIS LINDENBAUM whose telephone number is (571)270-3858. The examiner can normally be reached Monday through Friday 9:00 AM to 5:00 PM 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, Nishant Divecha can be reached at (571) 270-3125. 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. /ALAN L LINDENBAUM/Examiner, Art Unit 2466 /Nishant Divecha/Supervisory Patent Examiner, Art Unit 2419
Read full office action

Prosecution Timeline

Dec 14, 2022
Application Filed
May 13, 2025
Non-Final Rejection — §103
Jul 08, 2025
Interview Requested
Jul 28, 2025
Examiner Interview Summary
Jul 28, 2025
Applicant Interview (Telephonic)
Aug 05, 2025
Response Filed
Aug 28, 2025
Final Rejection — §103
Oct 01, 2025
Interview Requested
Oct 21, 2025
Applicant Interview (Telephonic)
Oct 21, 2025
Examiner Interview Summary
Oct 29, 2025
Response after Non-Final Action
Nov 18, 2025
Request for Continued Examination
Nov 26, 2025
Response after Non-Final Action
Jan 30, 2026
Non-Final Rejection — §103
Mar 26, 2026
Interview Requested
Apr 15, 2026
Applicant Interview (Telephonic)
Apr 15, 2026
Examiner Interview Summary

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12603845
Device-Assisted Services for Protecting Network Capacity
2y 5m to grant Granted Apr 14, 2026
Patent 12557092
Data Scheduling in High Frequency
2y 5m to grant Granted Feb 17, 2026
Patent 12526661
Radio Link Monitoring for Sidelink Communications
2y 5m to grant Granted Jan 13, 2026
Patent 12483974
METHOD AND APPARATUS FOR REDUCED CAPABILITY TERMINAL TO ACCESS A CELL IN MOBILE WIRELESS COMMUNICATION SYSTEM
2y 5m to grant Granted Nov 25, 2025
Patent 12396051
METHOD AND APPARATUS FOR FAILURE RECOVERY IN WIRELESS COMMUNICATION SYSTEM
2y 5m to grant Granted Aug 19, 2025
Study what changed to get past this examiner. Based on 5 most recent grants.

AI Strategy Recommendation

Get an AI-powered prosecution strategy using examiner precedents, rejection analysis, and claim mapping.
Powered by AI — typically takes 5-10 seconds

Prosecution Projections

3-4
Expected OA Rounds
48%
Grant Probability
64%
With Interview (+15.8%)
3y 7m
Median Time to Grant
High
PTA Risk
Based on 421 resolved cases by this examiner. Grant probability derived from career allow rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month