Prosecution Insights
Last updated: November 20, 2026
Application No. 19/125,386

METHOD AND SYSTEM FOR PRIVACY-AWARE PACKET PROCESSING

Non-Final OA §103
Filed
Apr 29, 2025
Priority
Nov 04, 2022 — nonprovisional of PCTIB2022060645
Examiner
BROWN, ANTHONY D
Art Unit
2408
Tech Center
2400 — Computer Networks
Assignee
Telefonaktiebolaget LM Ericsson
OA Round
1 (Non-Final)
86%
Grant Probability
Favorable
1-2
OA Rounds
1y 1m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 86% — above average
86%
Career Allowance Rate
752 granted / 880 resolved
+27.5% vs TC avg
Moderate +15% lift
Without
With
+14.7%
Interview Lift
resolved cases with interview
Typical timeline
2y 8m
Avg Prosecution
22 currently pending
Career history
912
Total Applications
across all art units

Statute-Specific Performance

§101
15.6%
-24.4% vs TC avg
§103
51.1%
+11.1% vs TC avg
§102
17.4%
-22.6% vs TC avg
§112
5.5%
-34.5% vs TC avg
Black line = Tech Center average estimate • Based on career data from 880 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 . Examiner Remarks Claims 3 and 11-12 are canceled. Information Disclosure Statement The information disclosure statement (IDS) submitted on 4/29/2025 was filed after the mailing date of the application on 4/29/2025. The submission is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner. The information disclosure statement (IDS) submitted on 5/20/2026 was filed after the mailing date of the application on 4/29/2025. The submission is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner. Claim Rejections - 35 USC § 103 In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status. The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action: A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. Claim(s) 1-2, 4-10, 13-23 are rejected under 35 U.S.C. 103 as being unpatentable over Patil (US Patent Pub. 2020/0236086) in view of Kiley (US Patent Pub. 20130325935). As per claims 1, 13 and 23: (Currently Amended) Patil discloses a method to be implemented in a first electronic device to enhance privacy in a network, comprising (see abstract): determining whether a first packet supports privacy preservation based on a first packet header of the first packet (Paragraph 54; deep packet inspection may be performed to facilitate score evaluation by SDN manager 184. For example, deep packet inspection may be performed using agent 151 and/or hypervisor-A 114A to inspect operations performed by VM1 131 operated by user 191 and report related event information to SDN manager 182); causing the one or more operations to be performed on the first packet, wherein the one or more operations to be performed on the first packet comprise a privacy preservation operation including implementation of a first privacy preservation protocol for the first packet in the network to comply with the first level of data sharing privilege (Paragraph 38; SDN manager 184 generates and sends control information to instruct host-A 110A to apply firewall rules 281-286 using DFW engine 118A based on score=100 assigned to user 191. Host-A 110A stores firewall rules 281-286 and apply them to packets originating from source IP address=IP1 associated with VM1 131 operated by user 191). Patel does not specifically disclose identifying one or more operations to be performed on the first packet corresponding to a first privacy policy of the first packet based on the first packet upon determining that the first packet supports privacy preservation, the first privacy policy indicating a first level of data sharing privilege mapped to a first setting configured for a first user (See Kiley; claim 1; a HyperText Transport Protocol (HTTP) request is generated by a user agent running on an Internet-enabled device. The HTTP request includes multiple HTTP header fields complying with Request for Comments (RFC) 2616. Each of the HTTP header fields includes a name-value pair having a name separated from a value by a colon. The value of the name-value pair of an HTTP header field is set based on a privacy setting or a data sharing setting that was established based on input received from an end user of the Internet-enabled device. A web server is directed by the user agent to return content tailored in accordance with the privacy setting or the data sharing setting by transmitting the HTTP request to the web server). Therefore, it 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, having the teachings of Patil and Kiley in it’s entirety, to modify the technique of Patil for stores firewall rules and apply them to packets by adopting Kiley's teaching for where user configured privacy settings and data sharing preference dictate how communication fields are structured. The motivation would have been to improve privacy in a network. As per claims 2 and 14: (Currently Amended) The combination of Patil and Kiley discloses the method of claim 1, wherein a first set of bits in the first packet header of the first packet is used to determine that the first packet supports privacy preservation, and wherein a second set of bits in the corresponding payload of the first packet indicates the first privacy preservation protocol (See Patil; Paragraph 15; The term “packet” may refer generally to a group of bits that can be transported together, and may be in another form, such as “frame,” “message,” “segment,” etc. The term “traffic” or “flow” may refer generally to multiple packets) (claim 1; wherein the value of the name-value pair of an HTTP header field of the plurality of HTTP header fields is set based on a privacy setting or a data sharing setting that was established based on input received from an end user of the Internet-enabled device; and directing, by the user agent, a web server to return content tailored in accordance with the privacy setting or the data sharing setting by transmitting the HTTP request to the web server). As per claim 4: (Currently Amended) The combination of Patil and Kiley discloses the method of claim 1, wherein identifying the one or more operations to be performed on the first packet comprises decrypting the first packet received from a second electronic device that inserts a plurality of bits mapped to the first privacy policy into the first packet (See Kiley; Paragraph 104; the encryption/decryption controller 314 contains the current encryption and decryption libraries). As per claim 5: (Original) The combination of Patil and Kiley discloses the method of claim 4, wherein the second electronic device further encrypts a portion of the first packet to prevent the portion of the first packet to be decrypted by the first electronic device (See Kiley; Paragraph 156; a header of the augmented HTTP request 820 is shown after being received and decrypted by a server). As per claims 6 and 16: (Currently Amended) The combination of Patil and Kiley discloses the method of any of claim 1, wherein implementing the first privacy preservation protocol comprises forwarding the first packet to a plurality of electronic devices that are qualified to implement the first privacy preservation protocol (See Kiley; claim 1; a HyperText Transport Protocol (HTTP) request is generated by a user agent running on an Internet-enabled device. The HTTP request includes multiple HTTP header fields complying with Request for Comments (RFC) 2616. Each of the HTTP header fields includes a name-value pair having a name separated from a value by a colon. The value of the name-value pair of an HTTP header field is set based on a privacy setting or a data sharing setting that was established based on input received from an end user of the Internet-enabled device. A web server is directed by the user agent to return content tailored in accordance with the privacy setting or the data sharing setting by transmitting the HTTP request to the web server). As per claims 7 and 17: (Currently Amended) The combination of Patil and Kiley discloses the method of any of claim 1, wherein the one or more operations further comprise removing information that the first user has no privilege to share (See Patil; Paragraph 25; completely trusting user 191/192 once they have been authenticated, a score that reflects the trustworthiness associated with user 191/192 may be dynamically adjusted to restrict access). As per claims 8 and 18: (Currently Amended) The combination of Patil and Kiley discloses the method of claim 1, further comprising: determining that a second packet includes no bits that indicate a privacy policy; and inserting a plurality of bits that indicate a second level of data sharing privilege into the second packet based on the second level of data sharing privilege mapped to a second setting configured for a second user (See Kiley; claim 1; a HyperText Transport Protocol (HTTP) request is generated by a user agent running on an Internet-enabled device. The HTTP request includes multiple HTTP header fields complying with Request for Comments (RFC) 2616. Each of the HTTP header fields includes a name-value pair having a name separated from a value by a colon. The value of the name-value pair of an HTTP header field is set based on a privacy setting or a data sharing setting that was established based on input received from an end user of the Internet-enabled device. A web server is directed by the user agent to return content tailored in accordance with the privacy setting or the data sharing setting by transmitting the HTTP request to the web server). As per claims 9 and 19: (Original) The combination of Patil and Kiley discloses the method of claim 8, wherein the plurality of bits indicates a second privacy preservation protocol to be implemented in the network to comply with the second level of data sharing privilege (See Patil; Paragraph 15; The term “packet” may refer generally to a group of bits that can be transported together, and may be in another form, such as “frame,” “message,” “segment,” etc. The term “traffic” or “flow” may refer generally to multiple packets) (claim 1; wherein the value of the name-value pair of an HTTP header field of the plurality of HTTP header fields is set based on a privacy setting or a data sharing setting that was established based on input received from an end user of the Internet-enabled device; and directing, by the user agent, a web server to return content tailored in accordance with the privacy setting or the data sharing setting by transmitting the HTTP request to the web server). As per claims 10 and 20: (Currently Amended) The method of claim 1, further comprising: identifying one or more operations to be performed on a third packet corresponding to a third privacy policy of the third packet based on the third packet, the third privacy policy indicating a third level of data sharing privilege mapped to a third setting configured for a third user (See Patil; Paragraph 25; data center security may be improved by using a “score-based” approach to dynamically evaluate whether to allow or block access by user 191/192 to a particular resource. Instead of completely trusting user 191/192 once they have been authenticated), wherein the one or more operations are to audit one or more privacy preservation operations that have performed on the third packet (See Patil; Paragraph 25; a score that reflects the trustworthiness associated with user 191/192 may be dynamically adjusted to restrict access); and indicating that the third packet complies with the third privacy policy upon determining that the one or more privacy preservation operations on the third packet are in compliance with the third privacy policy (See Patil; Paragraph 25). As per claim 15: (Original) The electronic device of claim 14, wherein the second set of bits are set for the first privacy policy of the first packet based on a selection table with entries each mapping to a privacy policy (See Patil; Paragraph 16; Forwarding tables 116A-B may each include entries that collectively implement the respective logical switches. Further, logical DRs that provide logical layer-3 connectivity may be implemented collectively by DR instances 117A-B and represented internally using routing tables (not shown) at respective DR instances 117A-B. The routing tables may each include entries that collectively implement the respective logical DRs). As per claim 21: (Currently Amended) The electronic device of claim 20, wherein the indication is inserted into packet header of the third packet (See Patil; Paragraph 25; data center security may be improved by using a “score-based” approach to dynamically evaluate whether to allow or block access by user 191/192 to a particular resource. Instead of completely trusting user 191/192 once they have been authenticated). As per claim 22: (Original) The electronic device of claim 20, wherein the third packet is discarded upon determining that the one or more privacy preservation operations on the third packet have violated the third privacy policy (See Patil; Paragraph 25; a score that reflects the trustworthiness associated with user 191/192 may be dynamically adjusted to restrict access). Relevant Prior Art References The following prior art is cited as being of interest to the claimed invention but has not been applied in any of the current rejections. Cebere et al.- US Patent Publication 2022/0140996- the prior art teaches techniques for privacy-preserving domain name service. Meaburn et al.- US Patent Pub. 2021/0194879 - the prior art teaches techniques for domain name security. Norum et al.- US Patent Pub. 2017/0093802 - the prior art teaches techniques for improving confidence that received resource records are from a trusted source. Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to ANTHONY D BROWN whose telephone number is (571)270-1472. The examiner can normally be reached 730-330pm. 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, Linglan Edwards can be reached at 5712705440. 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. /ANTHONY D BROWN/Primary Examiner, Art Unit 2408
Read full office action

Prosecution Timeline

Apr 29, 2025
Application Filed
Sep 16, 2026
Non-Final Rejection mailed — §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12803804
METHOD FOR DATA COMPRESSION AND ENCRYPTION
1y 7m to grant Granted Nov 17, 2026
Patent 12786240
PEER-TO-PEER NETWORK ROUTING BASED ON NETWORK DEVICE SECURITY CAPABILITIES
2y 4m to grant Granted Nov 03, 2026
Patent 12785972
SYSTEMS AND METHODS FOR IMPLEMENTING COMPUTER TRANSMISSION SECURITY PROTOCOL
1y 2m to grant Granted Nov 03, 2026
Patent 12769819
METHOD, APPARATUS AND COMPUTER PROGRAM
2y 4m to grant Granted Oct 20, 2026
Patent 12764150
CONDITIONAL EGRESS IP ADDRESS ASSIGNMENT AND SCORING FOR DELIVERY OF LOCALIZED CONTENT
2y 0m to grant Granted Oct 13, 2026
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
86%
Grant Probability
99%
With Interview (+14.7%)
2y 8m (~1y 1m remaining)
Median Time to Grant
Low
PTA Risk
Based on 880 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