Prosecution Insights
Last updated: July 17, 2026
Application No. 18/769,684

DATA PROCESSING METHOD AND DEVICE

Non-Final OA §102
Filed
Jul 11, 2024
Priority
Jul 12, 2023 — RE 10-2023-0090499 +1 more
Examiner
FOLLANSBEE, KEITH TRAN-DANH
Art Unit
Tech Center
Assignee
KT Corporation
OA Round
1 (Non-Final)
63%
Grant Probability
Moderate
1-2
OA Rounds
1y 3m
Est. Remaining
81%
With Interview

Examiner Intelligence

Grants 63% of resolved cases
63%
Career Allowance Rate
55 granted / 87 resolved
+3.2% vs TC avg
Strong +18% interview lift
Without
With
+17.5%
Interview Lift
resolved cases with interview
Typical timeline
3y 3m
Avg Prosecution
26 currently pending
Career history
134
Total Applications
across all art units

Statute-Specific Performance

§101
0.4%
-39.6% vs TC avg
§103
96.9%
+56.9% vs TC avg
§102
1.0%
-39.0% vs TC avg
§112
1.2%
-38.8% vs TC avg
Black line = Tech Center average estimate • Based on career data from 87 resolved cases

Office Action

§102
DETAILED ACTION 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 § 102 In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status. The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action: A person shall be entitled to a patent unless – (a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention. Claim(s) 1-20 is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Shrivastava et al. (US20240334237 herein after Shriv). Regarding claim 1, Shriv teaches A method for processing data by a user equipment (UE), the method comprising: receiving higher layer signaling ([0080] “ The FIG. 1 depicts a wireless communication network that comprises a user equipment (101) and a network apparatus (103). The UE (101) and the network apparatus (103) communicates with each other to handle the PSI based packet discarding for XR applications”) including packet data convergence protocol (PDCP) configuration information for performing a protocol data unit (PDU) Set-based discard operation ([0097-0098] “the transmitting PDCP entity (200) is configured with multiple discard timer values for different PSI values for the PDU sets and starts the respective timer with the appropriate discard timer value based on the PSI of the PDU set received from the higher layer and is associated with… n an embodiment, a higher value of discard timer is configured for a higher PSI value (more importance) for the PDU set”; receiving a medium access control (MAC) control element that indicates activation of a service data unit (SDU) discard operation based on PDU Set importance ([0104] “the PSI value …the UE (101) is informed or signaled by the network for a congestion situation in a broadcast signaling message like system information block or a dedicated signaling message like a RRC message, a MAC control element or a downlink control information, DCI signaling, [0134-136] “XRDiscardThresholdPdus are Number of PDUs to be discarded when congestion based discard is activated and is ongoing. XRDiscardThresholdBytes …XRCongestionTimer is a Timer which is started when congestion is detected and when running, the PSI based discard is performed at PDCP. Upon expiry, the PSI based discard is deactivated”, (Examiner’s Note: congestion == discard operation, since when congestion is determine discard occurs)); and controlling a PDCP entity to start a PDU Set importance-based discard timer when the SDU discard operation based on the PDU Set importance is activated ([0104] “the PSI value …the UE (101) is informed or signaled by the network for a congestion situation in a broadcast signaling message like system information block or a dedicated signaling message like a RRC message, a MAC control element or a downlink control information, DCI signaling, [0134-136] “XRDiscardThresholdPdus are Number of PDUs to be discarded when congestion based discard is activated and is ongoing. XRDiscardThresholdBytes …XRCongestionTimer is a Timer which is started when congestion is detected and when running, the PSI based discard is performed at PDCP. Upon expiry, the PSI based discard is deactivated”, (Examiner’s Note: congestion == discard operation, since when congestion is determine discard occurs)) and when a PDCP SDU belonging to the PDU Set importance of a preset criterion is received from a higher layer ([0034] “ the method includes starting, by the transmitting PDCP entity, the first discard timer for low importance upon reception of the PDCP SDU belonging to a low importance PDU set from the upper layer. Further, the method includes starting, by the transmitting PDCP entity, the second discard timer upon reception of the PDCP SDU not belonging to a low importance PDU set from the upper layer”), where the PDU Set importance-based discard timer is configured in association with the PDCP SDU ([0034] “ the method includes starting, by the transmitting PDCP entity, the first discard timer for low importance upon reception of the PDCP SDU belonging to a low importance PDU set from the upper layer. Further, the method includes starting, by the transmitting PDCP entity, the second discard timer upon reception of the PDCP SDU not belonging to a low importance PDU set from the upper layer”). Regarding claim 2, Shriv teaches wherein the PDCP configuration information includes information for instructing to perform the PDU Set-based discard operation and information about the PDU Set importance-based discard timer ([0024] “receive configuration message including information of a first discard timer for low importance, a second discard timer, and a PDU set discard parameter, wherein the first discard timer is configured shorter than the second discard timer, obtain at least one packet data convergence protocol (PDCP) service data unit (SDU) from at least one upper layer, and perform, for the at least one PDCP SDU, a transmit operation including a PDCP SDU discard based on the first discard timer, the second discard timer, and the PDU set discard parameter”). Regarding claim 3, Shriv teaches wherein: the PDU Set importance-based discard timer is indicated through an information element distinguished from a PDCP discard timer ([0104] “the PSI value …the UE (101) is informed or signaled by the network for a congestion situation in a broadcast signaling message like system information block or a dedicated signaling message like a RRC message, a MAC control element or a downlink control information, DCI signaling); and a value of the PDU Set importance-based discard timer is set to a value that is equal to or greater than 0 and less than a value of the PDCP discard timer ([0033] “the duration of the first discard timer for low importance is less than the duration of the second discard timer and is configured in XR radio bearer configuration message by a RRC signaling message”, [0014] “The PSI based discard timer has shorter value than normal discard timer”). Regarding claim 4, Shriv teaches wherein the SDU discard operation based on the PDU Set importance is deactivated ([0124] “when configured (or deconfigured) with pdcp-duplication, activates (or deactivates) the PDCP duplication for XR RB from the first PDCP SDU of the PDU set”) after receiving an RRC reconfiguration message ([0131] “the configurations for XR bearers are carried in RRCReconfiguration message as part of PDCP configuration or separately as part of XRBearerConfigurations”). Regarding claim 5, Shriv teaches wherein the MAC control element ([0104] “the PSI value for the PDU set is only utilized based on the congestion status e.g., when the transmitting PDCP entity (200) determines a congestion situation or the UE (101) is informed or signaled by the network for a congestion situation in a broadcast signaling message like system information block or a dedicated signaling message like a RRC message, a MAC control element or a downlink control information, DCI signaling”) includes a field for indicating activation or deactivation of the SDU discard operation based on the PDU Set importance ([0049] “PDCP entity for handling a PDU set importance (PSI) while packet discarding for extended reality (XR) in wireless communication network. The transmitting PDCP entity comprises a processor and a packet discard handler communicatively coupled to the processor. The packet discard handler configures a first discard timer for low importance, a second discard timer, and a PDU set integrated handling indication (PSIHI) represented by PDU set discard parameter configuration based on received XR radio bearer configuration message”). Regarding claim 6, Shriv teaches wherein the controlling includes controlling the PDCP entity to discard all PDCP SDUs included in a PDU Set where the PDCP SDU belongs, together with a PDCP data PDU when the PDU Set importance-based discard timer expires ([0050 ]” Further, discard the at least one PDU set, when the first discard timer for low importance of the at least one PDCP SDU of the at least one PDU set expires”). Regarding claim 7, Shriv teaches wherein the controlling includes, when receiving a PDCP SDU to be included in the PDU Set where the PDCP SDU belongs from the higher layer ([0036] “includes receiving, by the transmitting PDCP entity, a request for discard of PDU set from the upper layers”), controlling the PDCP entity to discard the received PDCP SDU ([0050] “Further, discard the at least one PDU set, when the first discard timer for low importance of the at least one PDCP SDU of the at least one PDU set expires or when a PDCP status report is received from the receiving PDCP entity”). Regarding claim 8, Shriv teaches wherein the controlling includes controlling to initiate a PDCP discard timer associated with a corresponding PDCP SDU when the SDU discard operation based on the PDU Set importance is in an inactive state or when the PDU Set importance-based discard timer is not configured ([0101] “ is configured with and/or utilizes a single timer (e.g., the first discardTimer or a XRdiscardTimer) for a PDU set when the relevant QoS flow is configured with a PDU set integrated handling indication (PSIHI) set as TRUE. Otherwise, if the PSIHI for the QoS flow is set as FALSE, the transmitting PDCP entity (200) is configured with and/or utilizes a legacy timer (e.g., the second discardTimer) for each SDU of the PDU set for the relevant QoS flow”). Regarding claim 9, Shriv teaches A method for controlling UE to process data by a base station, the method comprising: configuring packet data convergence protocol (PDCP) configuration information for performing a protocol data unit (PDU) Set-based discard operation ([0097-0098] “the transmitting PDCP entity (200) is configured with multiple discard timer values for different PSI values for the PDU sets and starts the respective timer with the appropriate discard timer value based on the PSI of the PDU set received from the higher layer and is associated with… n an embodiment, a higher value of discard timer is configured for a higher PSI value (more importance) for the PDU set”); transmitting higher layer signaling including the PDCP configuration information to a user equipment (UE) ([0097-0098] “the transmitting PDCP entity (200) is configured with multiple discard timer values for different PSI values for the PDU sets and starts the respective timer with the appropriate discard timer value based on the PSI of the PDU set received from the higher layer and is associated with… n an embodiment, a higher value of discard timer is configured for a higher PSI value (more importance) for the PDU set”, [0094] “the transmitting PDCP entity (200) of the UE (101) is provided with PDU set importance (PSI) value for at least one PDU set in the uplink direction by the upper layer”); and transmitting a medium access control (MAC) control element that indicates activation of a service data unit (SDU) discard operation based on a PDU Set importance to the UE ([0104] “the PSI value …the UE (101) is informed or signaled by the network for a congestion situation in a broadcast signaling message like system information block or a dedicated signaling message like a RRC message, a MAC control element or a downlink control information, DCI signaling, [0134-136] “XRDiscardThresholdPdus are Number of PDUs to be discarded when congestion based discard is activated and is ongoing. XRDiscardThresholdBytes …XRCongestionTimer is a Timer which is started when congestion is detected and when running, the PSI based discard is performed at PDCP”), wherein when the SDU discard operation based on the PDU Set importance is activated and when a PDCP SDU belonging to the PDU Set importance of a preset criterion is received from a higher layer ([0024] “receive configuration message including information of a first discard timer for low importance, a second discard timer, and a PDU set discard parameter, wherein the first discard timer is configured shorter than the second discard timer, obtain at least one packet data convergence protocol (PDCP) service data unit (SDU) from at least one upper layer, and perform, for the at least one PDCP SDU, a transmit operation including a PDCP SDU discard based on the first discard timer, the second discard timer, and the PDU set discard parameter”), the UE starts a PDU Set importance-based discard timer configured in connection with the PDCP SDU in a PDCP entity [0134-136] “XRDiscardThresholdPdus are Number of PDUs to be discarded when congestion based discard is activated and is ongoing. XRDiscardThresholdBytes …XRCongestionTimer is a Timer which is started when congestion is detected and when running, the PSI based discard is performed at PDCP”). Regarding claim 10, Shriv teaches wherein the PDCP configuration information includes information for instructing to perform the PDU Set-based discard operation and information about the PDU Set importance-based discard timer ([0024] “receive configuration message including information of a first discard timer for low importance, a second discard timer, and a PDU set discard parameter, wherein the first discard timer is configured shorter than the second discard timer, obtain at least one packet data convergence protocol (PDCP) service data unit (SDU) from at least one upper layer, and perform, for the at least one PDCP SDU, a transmit operation including a PDCP SDU discard based on the first discard timer, the second discard timer, and the PDU set discard parameter”). Regarding claim 11, Shriv teaches wherein: the PDU Set importance-based discard timer is indicated through an information element distinguished from a PDCP discard timer ([0104] “the PSI value …the UE (101) is informed or signaled by the network for a congestion situation in a broadcast signaling message like system information block or a dedicated signaling message like a RRC message, a MAC control element or a downlink control information, DCI signaling), and a value of the PDU Set importance-based discard timer is set to a value that is equal to or greater than 0 and less than a value of the PDCP discard timer([0033] “the duration of the first discard timer for low importance is less than the duration of the second discard timer and is configured in XR radio bearer configuration message by a RRC signaling message”, [0014] “The PSI based discard timer has shorter value than normal discard timer”). Regarding claim 12, Shriv teaches wherein the MAC control element ([0104] “the PSI value for the PDU set is only utilized based on the congestion status e.g., when the transmitting PDCP entity (200) determines a congestion situation or the UE (101) is informed or signaled by the network for a congestion situation in a broadcast signaling message like system information block or a dedicated signaling message like a RRC message, a MAC control element or a downlink control information, DCI signaling”) includes a field for indicating activation or deactivation of the SDU discard operation based on the PDU Set importance ([0049] “PDCP entity for handling a PDU set importance (PSI) while packet discarding for extended reality (XR) in wireless communication network. The transmitting PDCP entity comprises a processor and a packet discard handler communicatively coupled to the processor. The packet discard handler configures a first discard timer for low importance, a second discard timer, and a PDU set integrated handling indication (PSIHI) represented by PDU set discard parameter configuration based on received XR radio bearer configuration message”). Regarding claim 13, Shriv teaches A user equipment (UE) for processing data, comprising: a receiver configured to receive higher layer signaling ([0080] “ The FIG. 1 depicts a wireless communication network that comprises a user equipment (101) and a network apparatus (103). The UE (101) and the network apparatus (103) communicates with each other to handle the PSI based packet discarding for XR applications”) including packet data convergence protocol (PDCP) configuration information for configuring to perform a protocol data unit (PDU) Set-based discard operation ([0097-0098] “the transmitting PDCP entity (200) is configured with multiple discard timer values for different PSI values for the PDU sets and starts the respective timer with the appropriate discard timer value based on the PSI of the PDU set received from the higher layer and is associated with… n an embodiment, a higher value of discard timer is configured for a higher PSI value (more importance) for the PDU set”) and receiving a medium access control (MAC) control element indicating activation of a service data unit (SDU) discard operation based on PDU Set importance ([0104] “the PSI value …the UE (101) is informed or signaled by the network for a congestion situation in a broadcast signaling message like system information block or a dedicated signaling message like a RRC message, a MAC control element or a downlink control information, DCI signaling, [0134-136] “XRDiscardThresholdPdus are Number of PDUs to be discarded when congestion based discard is activated and is ongoing. XRDiscardThresholdBytes …XRCongestionTimer is a Timer which is started when congestion is detected and when running, the PSI based discard is performed at PDCP. Upon expiry, the PSI based discard is deactivated”, (Examiner’s Note: congestion == discard operation, since when congestion is determine discard occurs)); and a controller configured to control a PDCP entity to start a PDU Set importance-based discard timer when the SDU discard operation based on the PDU Set importance is activated ([0104] “the PSI value …the UE (101) is informed or signaled by the network for a congestion situation in a broadcast signaling message like system information block or a dedicated signaling message like a RRC message, a MAC control element or a downlink control information, DCI signaling, [0134-136] “XRDiscardThresholdPdus are Number of PDUs to be discarded when congestion based discard is activated and is ongoing. XRDiscardThresholdBytes …XRCongestionTimer is a Timer which is started when congestion is detected and when running, the PSI based discard is performed at PDCP. Upon expiry, the PSI based discard is deactivated”, (Examiner’s Note: congestion == discard operation, since when congestion is determine discard occurs)) and when a PDCP SDU belonging to the PDU Set importance of a preset criterion is received from a higher layer ([0034] “ the method includes starting, by the transmitting PDCP entity, the first discard timer for low importance upon reception of the PDCP SDU belonging to a low importance PDU set from the upper layer. Further, the method includes starting, by the transmitting PDCP entity, the second discard timer upon reception of the PDCP SDU not belonging to a low importance PDU set from the upper layer”), where the PDU Set importance-based discard timer is configured in associated with the PDCP SDU ([0034] “ the method includes starting, by the transmitting PDCP entity, the first discard timer for low importance upon reception of the PDCP SDU belonging to a low importance PDU set from the upper layer. Further, the method includes starting, by the transmitting PDCP entity, the second discard timer upon reception of the PDCP SDU not belonging to a low importance PDU set from the upper layer”). Regarding claim 14, Shriv teaches wherein the PDCP configuration information includes information for instructing to perform the PDU Set-based discard operation and information about the PDU Set importance-based discard timer ([0024] “receive configuration message including information of a first discard timer for low importance, a second discard timer, and a PDU set discard parameter, wherein the first discard timer is configured shorter than the second discard timer, obtain at least one packet data convergence protocol (PDCP) service data unit (SDU) from at least one upper layer, and perform, for the at least one PDCP SDU, a transmit operation including a PDCP SDU discard based on the first discard timer, the second discard timer, and the PDU set discard parameter”). Regarding claim 15, Shriv teaches wherein: the PDU Set importance-based discard timer is indicated through an information element distinguished from a PDCP discard timer ([0104] “the PSI value …the UE (101) is informed or signaled by the network for a congestion situation in a broadcast signaling message like system information block or a dedicated signaling message like a RRC message, a MAC control element or a downlink control information, DCI signaling), and a value of the PDU Set importance-based discard timer is set to a value that is equal to or greater than 0 and less than a value of the PDCP discard timer timer ([0033] “the duration of the first discard timer for low importance is less than the duration of the second discard timer and is configured in XR radio bearer configuration message by a RRC signaling message”, [0014] “The PSI based discard timer has shorter value than normal discard timer”). Regarding claim 16, Shriv teaches wherein the SDU discard operation based on the PDU Set importance is deactivated ([0124] “when configured (or deconfigured) with pdcp-duplication, activates (or deactivates) the PDCP duplication for XR RB from the first PDCP SDU of the PDU set”) after receiving an RRC reconfiguration message ([0131] “the configurations for XR bearers are carried in RRCReconfiguration message as part of PDCP configuration or separately as part of XRBearerConfigurations”). Regarding claim 17, Shriv teaches wherein the MAC control element ([0104] “the PSI value for the PDU set is only utilized based on the congestion status e.g., when the transmitting PDCP entity (200) determines a congestion situation or the UE (101) is informed or signaled by the network for a congestion situation in a broadcast signaling message like system information block or a dedicated signaling message like a RRC message, a MAC control element or a downlink control information, DCI signaling”) includes a field for indicating activation or deactivation of the SDU discard operation based on the PDU Set importance ([0049] “PDCP entity for handling a PDU set importance (PSI) while packet discarding for extended reality (XR) in wireless communication network. The transmitting PDCP entity comprises a processor and a packet discard handler communicatively coupled to the processor. The packet discard handler configures a first discard timer for low importance, a second discard timer, and a PDU set integrated handling indication (PSIHI) represented by PDU set discard parameter configuration based on received XR radio bearer configuration message”). Regarding claim 18, Shriv wherein the controller controls the PDCP entity to discard all PDCP SDUs included in a PDU Set where the PDCP SDU belongs, together with a PDCP data PDU when the PDU Set importance-based discard timer expires ([0050 ]” Further, discard the at least one PDU set, when the first discard timer for low importance of the at least one PDCP SDU of the at least one PDU set expires”). Regarding claim 19, Shriv teaches wherein the controller, when receiving a PDCP SDU to be included in the PDU Set where the PDCP SDU belongs from the higher layer ([0036] “includes receiving, by the transmitting PDCP entity, a request for discard of PDU set from the upper layers”), controls the PDCP entity to discard the received PDCP SDU ([0050] “Further, discard the at least one PDU set, when the first discard timer for low importance of the at least one PDCP SDU of the at least one PDU set expires or when a PDCP status report is received from the receiving PDCP entity”). Regarding claim 20, Shriv teaches wherein the controller controls to initiate a PDCP discard timer associated with a PDCP SDU when the SDU discard operation based on the PDU Set importance is in an inactive state, or the PDU Set importance-based discard timer is not configured ([0101] “ is configured with and/or utilizes a single timer (e.g., the first discardTimer or a XRdiscardTimer) for a PDU set when the relevant QoS flow is configured with a PDU set integrated handling indication (PSIHI) set as TRUE. Otherwise, if the PSIHI for the QoS flow is set as FALSE, the transmitting PDCP entity (200) is configured with and/or utilizes a legacy timer (e.g., the second discardTimer) for each SDU of the PDU set for the relevant QoS flow”). Conclusion The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Yu et al. (US20240049047) is about priority configured based on importance of PDU set for discard operation. Any inquiry concerning this communication or earlier communications from the examiner should be directed to KEITH TRAN-DANH FOLLANSBEE whose telephone number is (571)272-3071. The examiner can normally be reached 10am -6 pm M-Th. 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, Derrick Ferris can be reached at 571-272-3123. 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. /K.T.F./Examiner, Art Unit 2411 /DERRICK W FERRIS/Supervisory Patent Examiner, Art Unit 2411
Read full office action

Prosecution Timeline

Jul 11, 2024
Application Filed
Jun 16, 2026
Non-Final Rejection mailed — §102 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12683894
Flexible Ethernet over wireless links
6y 10m to grant Granted Jul 14, 2026
Patent 12647206
Application-Based Multi-Band Transmission
6y 7m to grant Granted Jun 02, 2026
Patent 12627593
OPTIMIZING MESHNET CONNECTIONS IN A MESH NETWORK
4y 1m to grant Granted May 12, 2026
Patent 12603684
METHOD AND DEVICE FOR COMMUNICATION
3y 9m to grant Granted Apr 14, 2026
Patent 12513029
CARRIER FREQUENCY TRACKING METHOD, SIGNAL TRANSMISSION METHOD, AND RELATED APPARATUS
3y 4m to grant Granted Dec 30, 2025
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

1-2
Expected OA Rounds
63%
Grant Probability
81%
With Interview (+17.5%)
3y 3m (~1y 3m remaining)
Median Time to Grant
Low
PTA Risk
Based on 87 resolved cases by this examiner. Grant probability derived from career allowance 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