CTNF 19/085,075 CTNF 89480 Notice of Pre-AIA or AIA Status 07-03-aia AIA 15-10-aia The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA. Detailed action 1. Status of Claims: Claims 1-20 are pending in this Office Action. Information Disclosure Statement 2. The information disclosure statement (IDS) submitted on 06/27/2025 and 10/24/2025 are in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner. Priority 3. The examiner acknowledges this application is a continuation of United States Patent Application No. 17/785,938, filed December 17, 2019, which is the United States national phase of International Application No. PCT/US2019/066841, filed December 17, 2019, the disclosures of which are hereby incorporated by reference in their entireties. Double Patenting 08-33 AIA The non-statutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper time-wise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A non-statutory double patenting rejection is appropriate where the claims at issue are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg , 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman , 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi , 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum , 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel , 422 F.2d 438, 164 USPQ 619 (CCPA 1970); and In re Thorington , 418 F.2d 528, 163 USPQ 644 (CCPA 1969). A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on a non-statutory double patenting ground provided the reference application or patent either is shown to be commonly owned with this application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b). The USPTO internet Web site contains terminal disclaimer forms which may be used. Please visit http://www.uspto.gov/forms/. The filing date of the application will determine what form should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to http://www.uspto.gov/patents/process/file/efs/guidance/eTD-info-I.jsp. 4. Claim 1 of the instant application 19/085,075 is rejected on the ground of non-statutory double patenting as being unpatentable over claims 1 of US Patent 12,289,306. Although the claims at issue are not identical, they are not patentably distinct from each other because following observation is made: Instant Application (19/085,075) US Patent 12,289,306 (bold means difference) 1. A computer-implemented method, comprising: generating, with a mobile device application on a mobile device, a real-time mobile device application profile associated with the mobile device; receiving, with at least one processor, the real-time mobile device application profile generated by the mobile device; determining, with at least one processor, whether there is an anomaly between the real-time mobile device application profile and a historical mobile device application profile associated with the mobile device; wherein determining whether there is an anomaly comprises: comparing the real-time mobile device application profile to the historical mobile device application profile; and performing, with at least one processor, a remedial action associated with a transaction based on determining that there is an anomaly between the real-time mobile device application profile and the historical mobile device application profile, wherein performing the remedial action associated with the transaction comprises: foregoing processing of the transaction based on determining that there is an anomaly between the real-time mobile device application profile and the historical mobile device application profile associated with the mobile device. 1. A computer-implemented method, comprising: generating, with a mobile device application on a mobile device, a real-time mobile device application profile associated with the mobile device, wherein the real-time mobile device application profile comprises at least one of the following: data associated with memory usage of one or more mobile device applications on the mobile device; data associated with total usage of the one or more mobile device applications on the device; data associated with one or more times of a day that a user interacts with the one or more mobile device applications on the mobile device; data associated with installation of the one or more mobile device applications on the mobile device; or any combination thereof; receiving, with at least one processor, the real-time mobile device application profile generated by the mobile device; determining, with at least one processor, whether there is an anomaly between the real-time mobile device application profile and a historical mobile device application profile associated with the mobile device, wherein the historical mobile device application profile comprises at least one of the following: historical data associated with memory usage of one or more mobile device applications on the mobile device; historical data associated with total usage of the one or more mobile device applications on the mobile device; historical data associated with one or more times of a day that a user interacts with the one or more mobile device applications on the mobile device; historical data associated with installation of the one or more mobile device applications on the mobile device; or any combination thereof; wherein determining whether there is an anomaly comprises: comparing the real-time mobile device application profile to the historical mobile device application profile; and performing, with at least one processor, a remedial action associated with a transaction based on determining that there is an anomaly between the real-time mobile device application profile and the historical mobile device application profile, wherein performing the remedial action associated with the transaction comprises: transmitting one or more messages to one or more devices involved in the transaction, the one or more messages including data associated with an indication that an anomaly was detected, and foregoing processing of the transaction based on determining that there is an anomaly between the real-time mobile device application profile and the historical mobile device application profile associated with the mobile device. As demonstrated, for example the independent claim 1 of US Patent 12,289,306 discloses the features of the independent claim 1 of 19/085,075 while the claims are broader in scope and anticipate the claimed invention in the parent. Thus, it would have been obvious to one of ordinary skill in the art having the claims 1 of 19/085,075 to modify the claims to achieve the features of claims of US Patent 12,289,306. Similar double patenting rejection will apply for the dependent claims are rejected based on their dependency. Claim Rejections - 35 USC § 102 07-06 AIA 15-10-15 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. 07-07-aia AIA 07-07 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 – 07-08-aia AIA (a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention. 07-15 AIA 5. Claim s 1-20 are rejected under 35 U.S.C. 102 ( a) (1 ) as being anticipated by US 2011/0225417 issued to Maharajh et al. (Maharajh) . As per claim 1, Maharajh teaches a computer-implemented method, comprising: generating, with a mobile device application on a mobile device, a real-time mobile device application profile associated with the mobile device (Maharajh: ¶ 0033, ¶ 0037 to ¶ 0038, ¶ 0493 to ¶ 0496, ¶ 0512, ¶ 0527 – storing a software application profile, wherein the profile is based at least in part on estimated times that it takes a software application to perform various functions; the consumption profile may be updated in real-time; the user profile may include user preferences and historical user information; mobile media platform 100 may include a consumption profile 102 which may include a device profile 2502, user profile 2504, network profile 2508, encoding profile 2510 and content profile; and each individual application of a consumption profile 102 may represent an individual usage session with factors associated with it such as location, user preferences, time of day, available network bandwidth, and the like) ; receiving, with at least one processor, the real-time mobile device application profile generated by the mobile device (Maharajh: ¶ 0465, ¶ 0493 to ¶ 0496 – user launches the portable media application, or digital locker application for the first lime after downloading it to his or her mobile device. The portable media application searches for user profile information on the local application folder on the device; If the digital locker application finds a user profile, containing user details, the digital locker application authenticates the user; consumption profile 102 may interact with and be implemented within a distributed architecture) ; determining, with at least one processor, whether there is an anomaly between the real-time mobile device application profile and a historical mobile device application profile associated with the mobile device (Maharajh: ¶ 0380 to ¶ 0385, ¶ 0418 to ¶0423, ¶ 0493 to ¶ 0496, ¶ 0507 – In the event a mobile device application is compromised by decompilation/recompilation, the signatures in the application will differ from those previously calculated. This difference will manifest as an error in decryption at some indeterminate time in the downstream decoding process that should result in undefined behavior; consumption profile 102 may encompass a location profile including current and historical and future predicted location information and location intelligence 148. The consumption profile 102 may encompass current and historical and future predicted date-time and content restrictions profiles and/or information"; "Because the platform may only ingest content that is compatible (or can be adapted to be compatible) with currently applied consumption profiles 102, different content may begin being ingested when a suitable consumption profile 102 is applied) ; wherein determining whether there is an anomaly comprises: comparing the real-time mobile device application profile to the historical mobile device application profile (Maharajh: ¶ 0029 - in response to a subsequent video play request from the mobile communication facility relating to the video, causing a time of day representing the then current time of day to be determined, forming a second play time. The method then compares the first and second play times to assess a likelihood of whether a clock on the mobile communication facility has been manipulated in such a way as to permit the playing of the video when a rights management rule would otherwise not have permitted the playing of the video. The method further comprises causing a remedial action to be implemented in response to a positive indication of improper manipulation) ; and performing, with at least one processor, a remedial action associated with a transaction based on determining that there is an anomaly between the real-time mobile device application profile and the historical mobile device application profile , wherein performing the remedial action associated with the transaction comprises: foregoing processing of the transaction based on determining that there is an anomaly between the real-time mobile device application profile and the historical mobile device application profile associated with the mobile device (Maharajh: ¶ 0493 to ¶ 0496, ¶ 0507 to ¶ 0512, ¶ 0754 to ¶ 0755 – a consumption profile 102 may impact the security 168 aspects of the platform, including authentication, authorization, passwords, purchase verification, access control, biometric identification on the mobile device, encryption, access security and the like. In embodiments, a consumption profile 102 may impact the billing aspects of the platform, including collection, pricing, billing, mediation, settlement, reporting and the like; consumption profile 102 may allow for characteristics, such as device characteristics, network characteristics and the like, rules, such as operator rules and the like, user preferences and the like, location characteristics and the like, date-time characteristics, content restrictions and the like to be applied; consumption profile 102 may impact delivery. Delivery may be optimized for mobile consumption as may be determined from the consumption profile 102. Optimizing factors may be based on a consumption profile 102 such as factors that vary for each individual application of a consumption profile 102. Each individual application of a consumption profile 102 may represent an individual usage session with factors associated with it such as location, user preferences, time of day, available network bandwidth, and the like. Other factors associated with a consumption profile 102 that affect delivery include device playback capabilities, device content delivery mechanism support, content digital rights management regime, content characteristics, and the like) . As per claim 2, Maharajh taches the computer-implemented method of claim 1, further comprising: receiving a request for a transaction associated with a two-factor authentication protocol; and transmitting data associated with an authentication parameter to the mobile device based on receiving the request for the transaction associated with the two-factor authentication protocol (Maharajh: ¶ 0035, ¶ 0370 to ¶ 0371 – evaluates the authenticity of a token that is sent from a device to a host to ensure that a set of authentication credentials to facilitate access to protected content are usable by a single device; Login consists of two phases. The first is a challenge request which is used to retrieve a challenge keyword. This keyword is combined with the shared secret and hashed using MD5 and then sent in the second phase to the server where the challenge response is validated) . As per claim 3, Maharajh taches the computer-implemented method of claim 2, wherein generating the real-time mobile device application profile associated with the mobile device comprises: generating the real-time mobile device application profile associated with the mobile device based on receiving the data associated with the authentication parameter by the mobile device (Maharajh: ¶ 0465 – the user launches the portable media application, or digital locker application for the first time after downloading it to his or her mobile device. The portable media application searches for user profile information on the local application folder on the device. A returning user may also select the "do not save my password" option and be presented with the login screen, just as a new user would. The login screen provides an option to register a new user. If the digital locker application finds a user profile, containing user details, the digital locker application authenticates the user and launches the digital locker home screen) . As per claim 4, Maharajh taches the computer-implemented method of claim 1, wherein generating the real-time mobile device application profile associated with the mobile device comprises: generating the real-time mobile device application profile associated with the mobile device based on based on one or more mobile device applications that are installed on the mobile device during a time period (Maharajh: ¶ 0032 – one function may also be altered to produce a new estimated time to obfuscate the ability of a third party to predict the estimated time. Alteration of the function may also be done after the software application has been installed on a system) . As per claim 5, Maharajh taches the computer-implemented method of claim 1, further comprising: generating the historical mobile device application profile associated with the mobile device, wherein the historical mobile device application profile comprises: data associated with memory usage of one or more mobile device applications on the mobile device during a time interval; data associated with total usage of the one or more mobile device applications on the mobile device during a time interval; data associated with one or more times of a day that a user interacts with the one or more mobile device applications on the mobile device during a time interval; data associated with installation of the one or more mobile device applications on the mobile device during a time interval; or any combination thereof (Maharajh: ¶ 0037 – the consumption profile may be updated in real-time or the consumption profile may be updated at set intervals) . As per claim 6, Maharajh taches the computer-implemented method of claim 5, further comprising: transmitting data associated with the one or more mobile device applications on the mobile device at a recurring time interval via an application programming interface (API) (Maharajh: ¶ 0462 – the user interface layer of the digital locker may be a client application that utilizes virtual libraries, widgets created for use within the system, or a secure web application programming interface (API)) . As per claim 7, Maharajh taches the computer-implemented method of claim 1, further comprising: receiving a request for a transaction associated with a two-factor authentication protocol, wherein the request comprises data associated with a device identifier of the mobile device; and transmitting a profile request to the mobile device based on receiving the request for the transaction associated with the two-factor authentication protocol, wherein generating the real-time mobile device application profile associated with the mobile device comprises: generating the real-time mobile device application profile associated with the mobile device based on receiving the profile request (Maharajh: claim 2 – causing a plurality of virtual-machine instructions to be interpreted for indications of a mobile device's hardware identification information, forming a plurality of hardware instruction interpretations; combining each of the plurality of hardware instruction interpretations and hashing the combination, forming a quasi-hardware device ID; basing a unique encryption process on at least two factors: the quasi-hardware device ID, and an understanding of what prior encryption process was used in a previous media delivery to the mobile device such that the unique encryption process is different than the prior encryption process) . As per claim 8, Maharajh taches a system, comprising: at least one processor (Maharajh: ¶ 0990 – methods and systems described herein may be deployed in part or in whole through a machine that executes computer software, program codes, and/or instructions on a processor) programmed or configured to: generate, with a mobile device application on a mobile device, a real- time mobile device application profile associated with the mobile device (Maharajh: ¶ 0033, ¶ 0037 to ¶ 0038, ¶ 0493 to ¶ 0496, ¶ 0512, ¶ 0527 – storing a software application profile, wherein the profile is based at least in part on estimated times that it takes a software application to perform various functions; the consumption profile may be updated in real-time; the user profile may include user preferences and historical user information; mobile media platform 100 may include a consumption profile 102 which may include a device profile 2502, user profile 2504, network profile 2508, encoding profile 2510 and content profile; and each individual application of a consumption profile 102 may represent an individual usage session with factors associated with it such as location, user preferences, time of day, available network bandwidth, and the like) ; receive the real-time mobile device application profile by the mobile device (Maharajh: ¶ 0465, ¶ 0493 to ¶ 0496 – user launches the portable media application, or digital locker application for the first lime after downloading it to his or her mobile device. The portable media application searches for user profile information on the local application folder on the device; If the digital locker application finds a user profile, containing user details, the digital locker application authenticates the user; consumption profile 102 may interact with and be implemented within a distributed architecture) ; generate a historical mobile device application profile associated with the mobile device (Maharajh: ¶ 0037 – the consumption profile may be updated in real-time or the consumption profile may be updated at set intervals) ; determine whether there is an anomaly between the real-time mobile device application profile and the historical mobile device application profile associated with the mobile device (Maharajh: ¶ 0380 to ¶ 0385, ¶ 0418 to ¶0423, ¶ 0493 to ¶ 0496, ¶ 0507 – In the event a mobile device application is compromised by decompilation/recompilation, the signatures in the application will differ from those previously calculated. This difference will manifest as an error in decryption at some indeterminate time in the downstream decoding process that should result in undefined behavior; consumption profile 102 may encompass a location profile including current and historical and future predicted location information and location intelligence 148. The consumption profile 102 may encompass current and historical and future predicted date-time and content restrictions profiles and/or information"; "Because the platform may only ingest content that is compatible (or can be adapted to be compatible) with currently applied consumption profiles 102, different content may begin being ingested when a suitable consumption profile 102 is applied) , wherein the one or more instructions that cause the at least one processor to determine whether there is an anomaly, cause the at least one processor to: compare the real-time mobile device application profile to the historical mobile device application profile (Maharajh: ¶ 0029 - in response to a subsequent video play request from the mobile communication facility relating to the video, causing a time of day representing the then current time of day to be determined, forming a second play time. The method then compares the first and second play times to assess a likelihood of whether a clock on the mobile communication facility has been manipulated in such a way as to permit the playing of the video when a rights management rule would otherwise not have permitted the playing of the video. The method further comprises causing a remedial action to be implemented in response to a positive indication of improper manipulation) ; and perform a remedial action associated with a transaction based on determining that there is an anomaly between the real-time mobile device application profile and the historical mobile device application profile, wherein, when performing the remedial action associated with the transaction, the at least one processor is programmed or configured to: forego processing of the transaction based on determining that there is an anomaly between the real-time mobile device application profile and the historical mobile device application profile associated with the mobile device (Maharajh: ¶ 0493 to ¶ 0496, ¶ 0507 to ¶ 0512, ¶ 0754 to ¶ 0755 – a consumption profile 102 may impact the security 168 aspects of the platform, including authentication, authorization, passwords, purchase verification, access control, biometric identification on the mobile device, encryption, access security and the like. In embodiments, a consumption profile 102 may impact the billing aspects of the platform, including collection, pricing, billing, mediation, settlement, reporting and the like; consumption profile 102 may allow for characteristics, such as device characteristics, network characteristics and the like, rules, such as operator rules and the like, user preferences and the like, location characteristics and the like, date-time characteristics, content restrictions and the like to be applied; consumption profile 102 may impact delivery. Delivery may be optimized for mobile consumption as may be determined from the consumption profile 102. Optimizing factors may be based on a consumption profile 102 such as factors that vary for each individual application of a consumption profile 102. Each individual application of a consumption profile 102 may represent an individual usage session with factors associated with it such as location, user preferences, time of day, available network bandwidth, and the like. Other factors associated with a consumption profile 102 that affect delivery include device playback capabilities, device content delivery mechanism support, content digital rights management regime, content characteristics, and the like) . As per claim 9, the claim resembles claim 2 and is rejected under the same rationale. As per claim 10, the claim resembles claim 4 and is rejected under the same rationale. As per claim 11, Maharajh teaches the system of claim 10, wherein, when generating the real-time mobile device application profile associated with the mobile device, the at least one processor is programmed or configured to: generate the real-time mobile device application profile associated with the mobile device based on receiving the request for a transaction associated with the two- factor authentication protocol (Maharajh: ¶ 0035, ¶ 0370 to ¶ 0371 – evaluates the authenticity of a token that is sent from a device to a host to ensure that a set of authentication credentials to facilitate access to protected content are usable by a single device; Login consists of two phases. The first is a challenge request which is used to retrieve a challenge keyword. This keyword is combined with the shared secret and hashed using MD5 and then sent in the second phase to the server where the challenge response is validated) . As per claim 12, the claim resembles claim 6 and is rejected under the same rationale. As per claim 13, the claim resembles claim 7 and is rejected under the same rationale. As per claim 14, Maharajh teaches a computer program product comprising at least one non- transitory computer-readable medium including one or more instructions that, when executed by at least one processor (Maharajh: ¶ 0994 – one or more of memories, processors, computer readable media, storage media, ports (physical and virtual), communication devices, and interfaces capable of accessing other clients, servers, machines, and devices through a wired or a wireless medium, and the like) , cause the at least one processor to: generate, with a mobile device application on a mobile device, a real-time mobile device application profile associated with the mobile device (Maharajh: ¶ 0033, ¶ 0037 to ¶ 0038, ¶ 0493 to ¶ 0496, ¶ 0512, ¶ 0527 – storing a software application profile, wherein the profile is based at least in part on estimated times that it takes a software application to perform various functions; the consumption profile may be updated in real-time; the user profile may include user preferences and historical user information; mobile media platform 100 may include a consumption profile 102 which may include a device profile 2502, user profile 2504, network profile 2508, encoding profile 2510 and content profile; and each individual application of a consumption profile 102 may represent an individual usage session with factors associated with it such as location, user preferences, time of day, available network bandwidth, and the like) ; receive the real-time mobile device application profile by the mobile device (Maharajh: ¶ 0465, ¶ 0493 to ¶ 0496 – user launches the portable media application, or digital locker application for the first lime after downloading it to his or her mobile device. The portable media application searches for user profile information on the local application folder on the device; If the digital locker application finds a user profile, containing user details, the digital locker application authenticates the user; consumption profile 102 may interact with and be implemented within a distributed architecture) ; determine whether there is an anomaly between the real-time mobile device application profile and a historical mobile device application profile associated with the mobile device (Maharajh: ¶ 0380 to ¶ 0385, ¶ 0418 to ¶0423, ¶ 0493 to ¶ 0496, ¶ 0507 – In the event a mobile device application is compromised by decompilation/recompilation, the signatures in the application will differ from those previously calculated. This difference will manifest as an error in decryption at some indeterminate time in the downstream decoding process that should result in undefined behavior; consumption profile 102 may encompass a location profile including current and historical and future predicted location information and location intelligence 148. The consumption profile 102 may encompass current and historical and future predicted date- time and content restrictions profiles and/or information"; "Because the platform may only ingest content that is compatible (or can be adapted to be compatible) with currently applied consumption profiles 102, different content may begin being ingested when a suitable consumption profile 102 is applied) ; wherein the one or more instructions that cause the at least one processor to determine whether there is an anomaly, cause the at least one processor to: compare the real-time mobile device application profile to the historical mobile device application profile (Maharajh: ¶ 0029 - in response to a subsequent video play request from the mobile communication facility relating to the video, causing a time of day representing the then current time of day to be determined, forming a second play time. The method then compares the first and second play times to assess a likelihood of whether a clock on the mobile communication facility has been manipulated in such a way as to permit the playing of the video when a rights management rule would otherwise not have permitted the playing of the video. The method further comprises causing a remedial action to be implemented in response to a positive indication of improper manipulation) ; and perform a remedial action associated with a transaction based on determining that there is an anomaly between the real-time mobile device application profile and the historical mobile device application profile, wherein, the one or more instructions that cause the at least one processor to perform the remedial action associated with the transaction, cause the at least one processor to: forego processing of the transaction based on determining that there is an anomaly between the real-time mobile device application profile and the historical mobile device application profile associated with the mobile device (Maharajh: ¶ 0493 to ¶ 0496, ¶ 0507 to ¶ 0512, ¶ 0754 to ¶ 0755 – a consumption profile 102 may impact the security 168 aspects of the platform, including authentication, authorization, passwords, purchase verification, access control, biometric identification on the mobile device, encryption, access security and the like. In embodiments, a consumption profile 102 may impact the billing aspects of the platform, including collection, pricing, billing, mediation, settlement, reporting and the like; consumption profile 102 may allow for characteristics, such as device characteristics, network characteristics and the like, rules, such as operator rules and the like, user preferences and the like, location characteristics and the like, date-time characteristics, content restrictions and the like to be applied; consumption profile 102 may impact delivery. Delivery may be optimized for mobile consumption as may be determined from the consumption profile 102. Optimizing factors may be based on a consumption profile 102 such as factors that vary for each individual application of a consumption profile 102. Each individual application of a consumption profile 102 may represent an individual usage session with factors associated with it such as location, user preferences, time of day, available network bandwidth, and the like. Other factors associated with a consumption profile 102 that affect delivery include device playback capabilities, device content delivery mechanism support, content digital rights management regime, content characteristics, and the like) . As per claim 15, the claim resembles claim 2 and is rejected under the same rationale. As per claim 16, the claim resembles claim 3 and is rejected under the same rationale. As per claim 17, the claim resembles claim 4 and is rejected under the same rationale. As per claim 18, the claim resembles claim 5 and is rejected under the same rationale. As per claim 19, the claim resembles claim 6 and is rejected under the same rationale. As per claim 20, the claim resembles claim 7 and is rejected under the same rationale. Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to SM AZIZUR RAHMAN whose telephone number is (571) 270-7360. The examiner can normally be reached on M-F Telework; If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Ali Shayanfar can be reached on 571-270-1050. 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. /SM A RAHMAN/Primary Examiner, Art Unit 2434 Application/Control Number: 19/085,075 Page 2 Art Unit: 2434 Application/Control Number: 19/085,075 Page 3 Art Unit: 2434 Application/Control Number: 19/085,075 Page 4 Art Unit: 2434 Application/Control Number: 19/085,075 Page 5 Art Unit: 2434 Application/Control Number: 19/085,075 Page 6 Art Unit: 2434 Application/Control Number: 19/085,075 Page 7 Art Unit: 2434 Application/Control Number: 19/085,075 Page 8 Art Unit: 2434 Application/Control Number: 19/085,075 Page 9 Art Unit: 2434 Application/Control Number: 19/085,075 Page 10 Art Unit: 2434 Application/Control Number: 19/085,075 Page 11 Art Unit: 2434 Application/Control Number: 19/085,075 Page 12 Art Unit: 2434 Application/Control Number: 19/085,075 Page 13 Art Unit: 2434 Application/Control Number: 19/085,075 Page 14 Art Unit: 2434 Application/Control Number: 19/085,075 Page 15 Art Unit: 2434 Application/Control Number: 19/085,075 Page 16 Art Unit: 2434 Application/Control Number: 19/085,075 Page 17 Art Unit: 2434 Application/Control Number: 19/085,075 Page 18 Art Unit: 2434
Prosecution Insights