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 .
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 6/12/2025 was filed after the mailing date of the application on 6/12/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.
Allowable Subject Matter
Claims 4, 13 and 18 are objected to as being dependent upon a rejected base claim, 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 § 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-3, 5-12, 14-17 and 19-20 are rejected under 35 U.S.C. 103 as being unpatentable over Jannink (US Patent Pub. 2017/0155737) in view of Adams (US Patent 9,275,210).
As per claims 1, 10 and 16: Jannink discloses a method comprising:
receiving a request to identify a user (Paragraph 42; identify a user's most salient activity patterns);
receiving user data from a computing device, wherein the user data contains usage data or computing device metadata, wherein the usage data is indicative of a user's pattern of usage of an input device, wherein the pattern of usage is based on a combination of one or more input device usage amount, usage frequency, or usage type (Paragraph 42; create a user pattern profile for each user. For example, in an embodiment a user pattern engine at server 106a can create a user pattern profile based on the metadata collected from user interactions with presented content together with lists from multiple sources, including the user's curated content list, the related users' lists and lists from external content sources), and
wherein the computing device metadata includes a time of day information, active applications, a user security profile, log file entries, or system information (Paragraph 63; source (e.g., self-created, influencer created, system created), a description, location, timeframe and any relevant user and system metadata such as completion status);
generating, using a machine learning engine, a user profile based on the user data, wherein the user profile is unique to the user (claim 1; generating, by a computer system, a user pattern profile based on the user data; scoring, by the computer system, available content items based on the user pattern profile and the contextual data);
analyzing the user profile (claim 1); determining, using the machine learning engine, an identity of the user based on the analyzing of the user profile (claim 1; generating, by the computer system, a sorted list of content items from the available content items based on the scoring; and presenting, by the computer system at the client device, the sorted list of content items);
Jannink does not specifically disclose determining a security policy based on the identity of the user; and executing a security procedure based on the security policy (see Adams, claim 1; where N is based on a level of access to said device as defined in said security policy, the determining from said received data the first location on the key, and the determining whether the identity of the user inputting the received data corresponds to the user profile, said security policy again modified when the identity of the user inputting the received data no longer matches the user profile).
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 Jannink and Adams in it’s entirety, to modify the technique of Jannink for reduce the rate of license validation requests to less than a threshold value by adopting Vantalon's teaching for contact the CA server to access the media if the initial rights and license exceed those provided during the bridge operation. The motivation would have been to improve software license management.
As per claims 2, 11 and 17: The method of claim 1, wherein determining the identity of the user further comprises:
receiving, from the machine learning engine, the user profile generated based on the user data (Paragraph 35);
comparing the user profile to a series of known user profiles, wherein the comparing determines that the user profile matches a known user profile; and
determining, based on said comparing, the identity of the user (Paragraph 35; ranking engine combines user profile information (e.g. from user profile database 116) with API source information (e.g. from content database 114) to create information sets to present to the user via client device 102a-n. A discovery ranking engine may generate information lists or sets including one or more items ranked by the ranking engine. Information lists or sets can include user curated content or items retrieved from external information sources).
As per claims 3 and 12: The method of claim 1: wherein the user data is collected using a rational agent locally installed on the computing device, and
wherein the rational agent is configured to monitor usage of the computing device (Paragraph 53; User interaction with the application as well as contextual data received at the client device (e.g. location and sensor input such as temperature, speed and orientation) are constantly monitored by the application).
As per claim 5: The method of claim 1 further comprising:
determining changes in the user's pattern of usage of the input device (Paragraph 42);
predicting changes to the usage data based on the changes in the user's pattern of usage of the input device (Paragraph 42; create a user pattern profile for each user. For example, in an embodiment a user pattern engine at server 106a can create a user pattern profile based on the metadata collected from user interactions with presented content together with lists from multiple sources, including the user's curated content list, the related users' lists and lists from external content sources); and
updating a known user profile based on the predicted changes to the usage data (claim 10; creating a new or updating an existing user pattern profile based on the inferred user preference).
As per claims 6 and 20: The method of claim 1, wherein the user data further includes:
third-party data, telemetry data, command line inputs, usernames, or customer designations (Paragraph 31; the functionalities of the platform can be provided from servers 106a-b to the users through third-party applications (e.g., through the use of an application programming interface (API))).
As per claims 7 and 14: The method of claim 1 further comprising: determining the user profile corresponds to an unknown user identity; and denying an authentication request (see adams; wireless device 100 (and user identification module 220) may rely upon other authentication technology such as smart cards and proximity authenticators to determine the identity of the user of wireless device 100. Persons of skill in the relevant art are well versed in implementing such systems).
As per claim 8: The method of claim 1 further comprising:
receiving a request to identify an authenticated user; determining the authenticated user corresponds to an unknown user identity; and revoking a security privilege of the authenticated user (see adams; wireless device 100 (and user identification module 220) may rely upon other authentication technology such as smart cards and proximity authenticators to determine the identity of the user of wireless device 100. Persons of skill in the relevant art are well versed in implementing such systems).
As per claims 9, 15 and 19: The method of claim 1, wherein the input device is a keyboard, computer mouse, touchscreen, or computer trackpad (Paragraph 32; Typical input mechanism on client devices 102A-N can include a touch screen display (including a single-touch (e.g., resistive) type or a multi-touch (e.g., capacitive) type), gesture control sensors, a physical keypad, a mouse, motion detectors (e.g., accelerometer), light sensors, temperature sensor, proximity sensor, device orientation detector (e.g., compass, gyroscope, or GPS), and so forth).
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
Prosecution Insights