DETAILED ACTION
1. The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
2. Claims 1-20 are pending. Claims 1, 17 and 20 are independent.
3. Two IDS’es submitted on 5/6/2025 and 1/28/2026 have been considered.
Claim Objections
4. Claims 6-8 are objected to as being dependent upon a rejected base claims but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims.
Claim Rejections - 35 USC § 102
5. 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.
6. 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.
7. Claim 1-5 and 9-20 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Jain (US PG. Pub 2021/0092036).
As regarding claims 1, 17 and 20, Jain discloses A system, comprising:
a processor [para. 41 and 43]; and
a memory operatively coupled with the processor, wherein the memory comprises processor-executable instructions which, when executed by the processor, cause the processor [para. 41 and 43] to:
obtain information corresponding to each of a plurality of encrypted transport protocol packets transferred between a client endpoint and a server endpoint via a transport protocol connection in a network, wherein the plurality of encrypted transport protocol packets comprises requests transferred from the client endpoint to the server endpoint and responses transferred from the server endpoint to the client endpoint [para. 4, 8 and 51; monitoring network even encrypted traffic involves obtaining requests from client and responses from server using HTTPS or QUIC];
determine, based on the obtained information, a set of features from each of the plurality of encrypted transport protocol packets within the transport protocol connection [para. 51 and 53; determining object-level data from the encrypted network traffic];
analyze the determined set of features and associated network traffic [para. 51-58; analyzing data, e.g. request/response size or time, from network traffic];
generate a set of attributes based on the analyzed set of features and the associated network traffic [para. 51-58; analyzing data, e.g. request/response size or time, from network traffic]; and
transmit the generated set of attributes to a match engine to generate request-response pairs [para. 53 and 58; generating request-response pair based on matching time metric data].
As regarding claims 2 and 18, Jain further discloses The system of claim 1, wherein the processor is to analyze the determined set of features by associating the requests with corresponding responses [para. 51-58; analyzing data, e.g. request/response size or time, from network traffic].
As regarding claims 3 and 19, Jain further discloses The system of claim 2, wherein the processor is to associate the requests with the corresponding responses by:
identifying the requests transferred from the client endpoint to the server endpoint in the transport protocol connection; estimating the responses transferred from the server endpoint to the client endpoint in the transport protocol connection; and matching, via the match engine, each request with a corresponding response to generate request-response pairs [para. 51-58; analyzing data, e.g. request/response size or time, from network traffic to generate request-response pair based on matching time metric data].
As regarding claim 4, Jain further discloses The system of claim 3, wherein the processor is to match each request with the corresponding response based on network-dependent constraints of at least one feature in the set of features [para. 52-53 and 58; generating request-response pair based on matching time metric data].
As regarding claim 5, Jain further discloses The system of claim 2, wherein the processor is to detect multiplexing of the requests by the client endpoint and the responses by the server endpoint, and wherein the processor is to associate the requests with the corresponding responses by matching, via the match engine, a number of the requests and a number of the responses as a group to generate a super request-response pair [para. 52-53; grouping number of objects].
As regarding claim 9, Jain further discloses The system of claim 1, wherein the set of attributes comprises attributes associated with individual messages in the transport protocol connection [para. 51-58; time data associated with requests and responses].
As regarding claim 10, Jain further discloses The system of claim 1, wherein the set of attributes comprises attributes associated with the transport protocol connection [para. 51-58; time data associated with requests and responses].
As regarding claim 11, Jain further discloses The system of claim 1, wherein the set of attributes comprises attributes associated with an application utilizing the transport protocol connection [para. 63; attributes associated with video streaming application].
As regarding claim 12, Jain further discloses The system of claim 5, wherein in case of multiplexing of the requests and the responses, the set of attributes for each grouped request-response pair comprises attributes associated with the plurality of requests and responses in the grouped request-response pair [para. 52-53; grouping number of objects].
As regarding claim 13, Jain further discloses The system of claim 1, wherein the transport protocol connection is a Quick User Datagram Protocol (UDP) Internet Connection (QUIC) between the client endpoint and the server endpoint, and wherein the plurality of encrypted transport protocol packets comprises hypertext transfer protocol (HTTP) packets [para. 51].
As regarding claim 14, Jain further discloses The system of claim 1, wherein the processor is to generate the request-response pairs for each of online estimation and offline estimation [para. 52-53].
As regarding claim 15, Jain further discloses The system of claim 1, wherein the processor is to automatically determine maximum transfer size and round-trip time for the associated network traffic to generate the set of attributes [para. 70].
As regarding claim 16, Jain further discloses The system of claim 1, wherein the processor is to generate the set of attributes for one or more applications comprising at least one of video traffic, interactive web traffic, and bulk file upload and downlink traffic [para. 63; attributes associated with video streaming application].
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to THONG P TRUONG whose telephone number is (571)270-7905. The examiner can normally be reached on M-F 8:30AM - 5:30PM.
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, Jeffrey Pwu can be reached on 57127267986798. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/THONG TRUONG/
Examiner, Art Unit 2433
/JEFFREY C PWU/Supervisory Patent Examiner, Art Unit 2433
Prosecution Insights