Patent Application 18231556 - INTERNET OF THINGS APPLICATION STORE - Rejection
Appearance
Patent Application 18231556 - INTERNET OF THINGS APPLICATION STORE
Title: INTERNET OF THINGS APPLICATION STORE
Application Information
- Invention Title: INTERNET OF THINGS APPLICATION STORE
- Application Number: 18231556
- Submission Date: 2025-05-16T00:00:00.000Z
- Effective Filing Date: 2023-08-08T00:00:00.000Z
- Filing Date: 2023-08-08T00:00:00.000Z
- National Class: 717
- National Sub-Class: 175000
- Examiner Employee Number: 87720
- Art Unit: 2192
- Tech Center: 2100
Rejection Summary
- 102 Rejections: 1
- 103 Rejections: 2
Cited Patents
The following patents were cited in the rejection:
Office Action Text
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 . Status of Claims Claims 1-20 are presented for examination in this application. The application filing date on 08/08/2023. Claims 1, 10 and 19 are independent. Examiner notes (A). Drawings submitted on 08/08/2023 comply with the provisions of 37 CFR 1.121(d), have been fully considered by the Examiner. (B). IDS submitted on 04/03/2024 and 01/07/2025 considered by the Examiner. (C). Limitations have been provided with the Bold fonts in order to distinguish from the cited part of the reference (Italic). (D). Examiner has cited particular columns, line numbers, references, or figures in the references applied to the claims above for the convenience of the applicant. Although the specified citations are representative of the teachings of passages and figures may apply as well. It is respectfully requested from the applicant in preparing responses to fully consider the reference in entirety, as potentially teaching all or part of the claimed invention. See MPEP §§ 2141.02 and 2123. The examiner requests, in response to this Office action, support be shown for language added to any original claims on amendment and any new claims. That is, indicate support for newly added claim language by specifically pointing to page(s) and line number(s) in the specification and/or drawing figure(s). This will assist the examiner in prosecuting the application. When responding to this office action, Applicant is advised to clearly point out the patentable novelty which he or she thinks the claims present, in view of the state of the art disclosed by the references cited or the objections made. He or she must also show how the amendments avoid such references or objections See 37 CFR 1.111 (c). Claim Objections Claims 3-5, 7, 12-14, and 16 are objected to because of the following informalities: Claims 3, 4, 7, 12, 13, and 16, replace all “can” with --to--. Claims 5 and 14, “the digital storefront service” lacks proper antecedent basis. Appropriate correction is required. Claim Rejections - 35 USC § 101 35 U.S.C. 101 reads as follows: Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title. Claims 1-20 are rejected under 35 U.S.C. 101 because the claimed invention is directed to non-statutory subject matter. Step 1: Claims 1-9 are directed to computer implemented methods, claims 10-18 are directed to system, and claims 19 and 20 are directed to a medium and fall within the statutory category of processes. Therefore, “Are the claims to a process, machine, manufacture or composition of matter?” Yes. With Step 1 being directed to a statutory category, the 2019 Interim Eligibility Guidance flowchart is directed to Step 2. Under Step 2A, Prong 1, the limitations “(i) determines a first input or a first output of the selected IoT application, (ii) selectively assigns a first IoT device in a set of IoT devices associated with the user to the first input or the first output,” The BRI of these limitations functions that can be reasonably carried out in the human mind with the aid of pen and paper, through observation, evaluation, judgment, opinion, thus it is reasonable to identify these limitation as reciting a mental process.. Under Step 2A, Prong 2, the additional elements “providing a smart installation service.” merely recite instructions to implement an abstract idea on a generic computer, or merely uses a generic computer or computer components as a tool to perform the abstract idea. The limitations “wherein installing the first instance of the selected IoT application comprises configuring the first instance of the selected IoT application to obtain the first input from the first IoT device or provide the first output to the first IoT device based on the assignment of the first IoT device to the first input or the first output.” merely recite insignificant extra solution activity such as gathering, displaying, updating, transmitting and storing data which does not integrate the judicial exception into a practical application. See MPEP 2106.05(d). Further, the additional element installs a first instance of the selected IoT application on one or more devices that comprise or are communicatively connected to the first IoT device, is merely applying the judicial exception or abstract idea. Therefore, this additional element does not integrate the judicial exception into a practical application. See MPEP 2106.05(f). The additional element in orange merely links the use of the judicial exception to a particular technological environment or field of use, thus does not integrate the judicial exception into a practical application. MPEP 2106.05(h). The additional limitation of “providing, by at least one computer processor, a digital marketplace service that enables a user to browse a plurality of IoT applications and to select one of the IoT applications in the plurality of IoT applications for installation;” merely link the use of the judicial exception to a particular technological environment or field of use, thus does not integrate the judicial exception into a practical application. MPEP 2106.05(h). Under step 2B, the additional elements do not amount to significantly more than the abstract idea. Berkheimer evidence in step 2B additional element under Prong 2 (i.e. A computer-implemented method for implementing an Internet of Things (IoT) application store), as insignificant extra solution activity. Evidence is provided in MPEP 2106.05(d) for generic computer functions such as gathering, displaying, updating, transmitting and storing data. The additional element is identified as insignificant extra solution activity which do not fall under the gathering, displaying, updating, transmitting and storing data, applicant’s spec paragraph 0178, stating its well-understood, routine, conventional activity “Various embodiments may be implemented, for example, using one or more well- known computer systems, such as computer system 1100 shown in FIG. 11”. So, under step 2B, the additional elements of “providing a smart installation service installs a first instance of the selected IoT application on one or more devices that comprise or are communicatively connected to the first IoT device” merely recite generic computer and computer components, and merely applying the abstract idea, respectively, thus do not amount to significantly more than the judicial exception. The limitations in orange merely recite the technological environment or field of use at a high level of generality. As for the limitation in green, the courts have identified functions such as gathering, displaying, updating, transmitting and storing data as well-understood, routine, conventional activity, thus do not amount to significantly more than the judicial exception. See MPEP 2106.05(d). Therefore, none of the additional elements recite an inventive concept, thus, the claimed invention is patent ineligible under 35 USC 101. Claim 10 is rejected for similar reasons as articulated for claim 1 as the additional limitations “A system, comprising: one or more memories; and at least one processor each coupled to at least one of the memories and configured to perform operations comprising: … the first IoT device or provide the first output to the first IoT device based on the assignment of the first IoT device to the first input or the first output.” is a generic computing apparatus that does not allude to a practical application of the abstract idea or amount to significantly more. Independent claim 19 is not patent eligible for the same reasons given for claim 10, wherein the “A non-transitory computer-readable medium having instructions stored thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations, the operations comprising: … wherein installing the first instance of the selected IoT application comprises configuring the first instance of the selected IoT application to obtain the first input from the first IoT device or provide the first output to the first IoT device based on the assignment of the first IoT device to the first input or the first output.” are merely a generic computer component for applying the abstract idea, thus fails to integrate the judicial exception into a practical application, nor an inventive concept. Further dependent claims 2-5, 11-14 and 20, the additional elements of smart installation server, selectively install IoT application on cloud computing environment merely applying the judicial exception or abstract idea. The additional elements are merely reciting instructions to implement an abstract idea on a generic computer, or merely uses a generic computer or computer components as a tool to perform the abstract idea. Therefore, this additional element does not integrate the judicial exception into a practical application. See MPEP 2106.05(f). expand on the abstract idea in its calculation and/or expand on the type of metric value that is used that does not integrate the invention into a practical application of the abstract idea or amount to significantly more. Dependent claims 6-7 and 15-16, under Prong 1, the limitations of determination of change and determines that there are no IoT devices in the set of IoT devices associated with the user are functions that can be reasonably carried out in the human mind with the aid of pen and paper, through observation, evaluation, judgment, opinion, thus it is reasonable to identify these limitation as reciting a mental process. Dependent claims 8-9 and 17-18, the additional elements of virtual deployment and interaction of simulated IoT device[s] are merely recite generic computer and computer components, and merely applying the abstract idea, respectively, thus do not amount to significantly more than the judicial exception. The limitations in orange merely recite the technological environment or field of use at a high level of generality. As for the limitation enabling user to deploy selected IoT application to virtual environment, the courts have identified functions such as gathering, updating, transmitting and storing data as well-understood, routine, conventional activity, thus do not amount to significantly more than the judicial exception. See MPEP 2106.05(d). Therefore, none of the additional elements recite an inventive concept, thus, the claimed invention is patent ineligible under 35 USC 101. 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 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)(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. Claims 1, 3-4, 10, 12-13 and 19 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Arnberg et al (US 2020/0092701 A1). As to claim 1. Arnberg discloses a computer-implemented method for implementing an Internet of Things (IoT) application store, comprising: providing, by at least one computer processor (par. 0307, … electronic devices typically include a set of one or more processors coupled to one or more other components …), a digital marketplace service that enables a user to browse a plurality of IoT applications (par. 0044, an Internet of Things (IoT) platform which may be utilized by developers to design and build new IoT devices and applications [i.e. plurality of IoT applications] … an IoT service through which the IoT hubs and connected IoT devices may be accessed and managed as described below. In addition, one embodiment of the IoT platform includes an IoT app or Web application (e.g., executed on a client device) to access and configured the IoT service, hub and connected devices. Existing online retailers and other Website operators [i.e. digital marketplace service] may leverage the IoT platform described herein to readily provide unique IoT functionality to existing user bases. …) and to select one of the IoT applications in the plurality of IoT applications for installation (par. 0045, … the IoT app [i.e. application] or browser installed on the user's device 135 (or via a desktop or other client computer system) and to web clients (e.g., such as websites 130 subscribing to the IoT service 120. Further, see pars. 0068, 0101 and 0248); and providing a smart installation service that (i) determines a first input or a first output of the selected IoT application (par. 0046, … control commands are provided below. In one embodiment described below, the IoT device 101 is a user input device designed to record user selections and send the user selections to the IoT service 120 and/or Website. … ), (ii) selectively assigns a first IoT device in a set of IoT devices associated with the user to the first input or the first output (par. 0059, In one embodiment, one or more other/alternate I/O devices or sensors 250 may be included on the IoT device 101 based on the particular application for which the IoT device 101 is designed. …), and (iii) installs a first instance of the selected IoT application on one or more devices that comprise or are communicatively connected to the first IoT device, wherein installing the first instance of the selected IoT application (par. 0101, … FIG. 9A, which shows an IoT hub 110 with program code updates 901 that need to be installed on an IoT device 601 (or a group of such IoT devices). … When the mobile device 611 enters the range of the IoT device 601, the intermediary connection logic/application 711 on the mobile device 611 connects with the intermediary/connection logic/application 701 on the IoT device 601 to provide the program code updates to the device. In one embodiment, the IoT device 601 may then enter into an automated update process to install the new program code updates and/or data. Further, see pars. 0248, 0253 and 0270. Examiner Note: any initial app/application is considered a first application) comprises configuring the first instance of the selected IoT application to obtain the first input from the first IoT device(par. 0040, As mentioned, in one embodiment, the IoT platform includes an IoT app or Web application executed on user devices 135 to allow users to access and configure the connected IoT devices 101-105, IoT hub 110, and/or IoT service 120. In one embodiment, the app or web application may be designed by the operator of a Website 130 to provide IoT functionality to its user base. Further par. 0059, FIG. 2 also includes a plurality of input devices or sensors 210 to receive user input and provide the user input to the low power microcontroller, which processes the user input in accordance with the application code 203 and library code 202. In one embodiment, each of the input devices include an LED 209 to provide feedback to the end user. Further, see pars. 009 and 0101). As to claim 3, Arnberg discloses the computer-implemented method wherein the smart installation service selectively assigns the first IoT device to the first input or the first output by: identifying a subset of the set of IoT devices (Fig. 1A, element 101 -105) that includes the first IoT device and from which the first input can be obtained or to which the first output can be provided (par. 0046, The IoT devices 101-105 may be equipped with various types of sensors to collect information about themselves and their surroundings and provide the collected information to the IoT service 120, user devices 135 and/or external Websites 130 via the IoT hub 110. Some of the IoT devices 101-105 may perform a specified function in response to control commands sent through the IoT hub 110. Various specific examples of information collected by the IoT devices 101-105, and control commands are provided below. In one embodiment described below, the IoT device 101 [i.e. first IoT device] is a user input device designed to record user selections and send the user selections to the IoT service 120 and/or Website.); presenting a list of the IoT devices in the subset to the user (par. 0050, FIG. 1B illustrates additional connection options for a plurality of IoT hubs 110-111, 190 In this embodiment a single user may have multiple hubs 110-111 installed onsite at a single user premises 180 (e.g., the user's home or business). This may be done, for example, to extend the wireless range needed to connect all of the IoT devices 101-105. As indicated, if a user has multiple hubs 110, 111 … ); and responsive to a user selection of the first IoT device from the list of IoT devices in the subset, assigning the first IoT device to the first input or the first output (pars. 0046, 0050). As to claim 4. Arnberg discloses the computer-implemented method wherein the smart installation service determines a second input or a second output of the selected IoT application, identifies a second IoT device that is not included in the set of IoT devices associated with the user and from which the second input can be obtained or to which the second output can be provided, and enables the user to obtain the second IoT device (Fig. 1B, pars. 0050 and 0053, a plurality of IoT hubs 110-111, 190 In this embodiment a single user may have multiple hubs 110-111 installed onsite at a single user premises 180 (e.g., the user's home or business). This may be done, for example, to extend the wireless range needed to connect all of the IoT devices 101-105. As indicated, if a user has multiple hubs 110, 111. … an IoT hub 190 installed at a second user premises 181. A virtually unlimited number of such IoT hubs 190 may be installed and configured to collect data from IoT devices 191-192 at user premises around the world. In one embodiment, the two user premises 180-181 may be configured for the same user. For example, one user premises 180 may be the user's primary home and the other user premises 181 may be the user's vacation home. In such a case, the IoT service 120 will logically associate the IoT hubs 110-111, 190 with the user and combine all of the attached IoT devices 101-105, 191-192 under a single comprehensive user interface, accessible via a user device with the installed app 135 … . Examiner Note: the second set of IoT devices 190-192. Any one of IoT device among IoT devices 191-192 considered a second IoT device. Examiner Note: user can obtain/connect/input to any second set IoT device from internet 220 vis the hup 190). As to claim 10, Arnberg discloses a system, comprising: one or more memories (par. 0307, application specific integrated circuits (ASICs) configured to perform certain operations or having a predetermined functionality or software instructions stored in memory embodied in a non-transitory computer readable medium. … In addition, such electronic devices typically include a set of one or more processors coupled to one or more other components, …); and at least one processor each coupled to at least one of the memories and configured to perform operations comprising (par. 0307): For remaining limitations see remarks regarding claim 1. As to claim 12, (the system claim) recites substantially similar limitations to claim 3 (the method claim) and is therefore rejected using the same art and rationale set forth above. As to claim 13, (the system claim) recites substantially similar limitations to claim 4 (the method claim) and is therefore rejected using the same art and rationale set forth above. As to claim 19, Arnberg discloses a non-transitory computer-readable medium having instructions stored thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations, the operations comprising (par. 0307, application specific integrated circuits (ASICs) configured to perform certain operations or having a predetermined functionality or software instructions stored in memory embodied in a non-transitory computer readable medium. … ): For remaining limitations see remarks regarding claim 1. Claim Rejections - 35 USC § 103 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. Claims 2, 11 and 20 are rejected under 35 U.S.C. 103 as being unpatentable over Arnberg et al. (US 2020/0092701) in view of Thummalapalli et al. (US 2019/0306242 A1) . As to claim 2, Arnberg discloses explicitly discloses is the above the computer-implemented method wherein the smart installation service selectively installs the first instance of the selected IoT application a computing device associated with the user, or an IoT device in the set of IoT devices. However, does not explicitly disclose IoT application on one or more of a cloud computing platform, but, Thummalapalli discloses the computer-implemented method(abstract, Techniques for management of Internet of Things (IOT) devices [i.e. set of IoT devices] are disclosed. IOT devices may be manufactured with a pre-installed software development kit (SDK) (e.g., in firmware or other storage). At initial startup time (e.g., after device placement), IOT devices may execute the firmware code as provided by the SDK to connect to a corporate network or other network-based control environment, such as a cloud-based service provider infrastructure. Once connected, IOT devices may participate in enterprise computing applications as a consumer or provider of information). Therefore, it would have been obvious to one of the ordinary skill in the art before the effective filing date of the claimed invention to modify the system disclosed by Arnberg to include method of IoT application on one or more of a cloud computing platform, as disclosed by Thummalapalli, for the purpose of managing Internet of Things (IOT) devices as part of a comprehensive service management infrastructure for an enterprise or organization (see paragraph 0001). Claims 8-9 and 17-18 rejected under 35 U.S.C. 103 as being unpatentable over Arnberg et al. (US 2020/0092701) in view of Brown et el. (US 2021/0301985 A1). As to claim 8, Arnberg does not explicitly disclose the following limitations but, Brown discloses the computer-implemented method of claim 1, further comprising: providing a virtual deployment service that enables the user to deploy a second instance of the selected IoT application to a virtual environment in which the second instance of the selected IoT application interacts with one or more simulated IoT devices (pars. 0075-0077, The computing resource service provider environment 400 may include one or more systems 401 that cooperate to enable deployment of the IoT platform using a customized configuration for a particular user. … deploy, manage, and otherwise interact with the client's IoT platform. In some embodiments, the platform API 412 provides secure access to an IoT management system 414 that includes, or accesses services and data needed to interact with an IoT platform, an IoT application 462, and/or IoT devices 404 that are deployed within or connect to the client's virtual computing environment 406, … The computing resource service provider implements, within its computing environment 400, at least one virtual computing environment 406 in which users may obtain virtual computing resources that enable the users to run programs. … a client's IoT platform may be deployed by installing one or more IoT applications 462 into the client's virtual computing environment 406. An IoT application 462 may be a software program or suite of software programs including program instructions that enable a processor executing the IoT application 462 to communicate with deployed IoT devices 40. Further, par. 0148, … a service person can pull a user's water device configuration from storage in the IoT platform and can simulate pump/device operations based on configuration info, perform diagnostics, and resolve an issue. Examiner Note: any second IoT device among plurality of IoT devices 404 consider second IoT device with a second IoT applicant amount applications 462). Therefore, it would have been obvious to one of the ordinary skill in the art before the effective filing date of the claimed invention to modify the system disclosed by Arnberg to include method of providing a virtual deployment service that enables the user to deploy a second instance of the selected IoT application to a virtual environment in which the second instance of the selected IoT application interacts with one or more simulated IoT devices, as disclosed by Brown, for the purpose of determining, by the server, that the water system simulation mitigates the problem, sending, by the server, a notification to the user device indicating a configuration change of the water device, and performing, by the server, the configuration change by sending an updated device configuration to the water device. (see paragraph 0034). As to claim 9, Brown discloses the computer-implemented method wherein the virtual deployment service further enables the user to connect the second instance of the selected IoT application deployed to the virtual environment to at least one IoT device in the set of IoT devices associated with the user (pars. 0061 and 0076-0077, a user that controls, or provides services for, the IoT devices 110-116 may configure and deploy one or more virtual servers 150 that are allocated the use of certain physical computing resources, such as processor cycles, memory, data storage, etc., of the physical servers 160; the IoT devices 110-116 … The computing resource service provider environment 400 may include one or more systems 401 that cooperate to enable deployment of the IoT platform using a customized configuration for a particular user. … an IoT application 462, and/or IoT devices 404 that are deployed within or connect to the client's virtual computing environment 406, described below. In some embodiments, the IoT management system 414 may access one or more user account data stores 422 that contain user account information and other private information associated with the client's user account. … the IoT application 462 may cause the processor to receive sensor data from the IoT devices 404, process the data to determine whether to take any actions, and then perform any identified action such as reporting the status of connected objects to the client, sending new commands to one or more of the IoT devices 404, storing data (e.g., in an IoT device data store 464), etc. The IoT application may be executed within virtual computing resources allocated to the client's virtual computing environment 406… ). Therefore, it would have been obvious to one of the ordinary skill in the art before the effective filing date of the claimed invention to modify the system disclosed by Arnberg to include method of the computer-implemented method wherein the virtual deployment service further enables the user to connect the second instance of the selected IoT application deployed to the virtual environment to at least one IoT device in the set of IoT devices associated with the user, as disclosed by Brown, for the purpose of users may obtain virtual computing resources that enable the users to run programs, store, retrieve, and process data, access services of the computing resource service provider environment 400, etc. The virtual computing environment 406 may be one of any suitable type and/or configuration of a compute resource virtualization platform implemented on one or more physical computing devices. (see paragraph 0076). As to claim 17, (the system claim) recites substantially similar limitations to claim 8 (the method claim) and is therefore rejected using the same art and rationale set forth above. As to claim 18, (the system claim) recites substantially similar limitations to claim 9 (the method claim) and is therefore rejected using the same art and rationale set forth above. Allowable Subject Matter Claims 5-7 and 14-16, are objected to as being dependent upon a rejected base claims 1 and 10 but would be allowable if rewritten in independent form including all of the limitations of the base claims as well claim 19 and any intervening claims or amended to overcome the rejection(s) under 35 U.S.C. 101, set forth in this Office action. Conclusion Prior arts made of record are considered pertinent to applicant's disclosure. See MPEP § 707.05 (C) For Examples: I. Zhang et al. (US 20160308957 A1) discloses: “Application resource manager 410 may perform operations associated with managing, installing, uninstalling, updating, and/or licensing IoT application 405. In some implementations, application resource manager 410 may be capable of protecting IoT application 405 (e.g., from software piracy activities). Additionally, or alternatively, application resource manager 410 may be capable of managing resources (e.g., one or more virtual IoT device APIs 415, one or more driver APIs 435, one or more hardware components of IoT device 210, etc.) to be concurrently used by a first IoT application 405 and a second IoT application 405 (e.g., when the first IoT application 405 and the second IoT application 405 are being executed at the same time) based on a collaboration list associated with one or more IoT applications 405.” (please see [0041]). II. Kim et al. (US 2014/0201022 A1) discloses: “According to an aspect of an exemplary embodiment, there is provided a method for providing an IoT service, the method including: accessing, by a browser executed in a user's mobile device, a P-platform; providing, by the P-platform, information on IoT devices to the browser; displaying, by the browser, the IoT devices; downloading, by the mobile device, an IoT application of an IoT device selected by the user from among the displayed IoT devices from an S-platform; and executing, by the mobile device, the IoT application and communicating with the IoT device.” and “The downloading may include: transmitting, by the browser, information the IoT device selected by the user from among the displayed IoT devices to the S-platform; transmitting, by the S-platform, a list of IoT applications of the IoT device selected by the user to the browser; displaying, by the browser, the list of IoT applications; and requesting, by the browser, an IoT application selected by the user from the S-platform and downloading the IoT application.” (please see [0010 and 0014). Any inquiry concerning this communication or earlier communications from the examiner should be directed to MOHAMMAD H KABIR whose telephone number is (571)270-1341. The examiner can normally be reached M-F, 8:00 am - 5:00 pm. 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, Sam Sough can be reached at 571-272-6799. 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. /MOHAMMAD H. KABIR/ Examiner Art Unit 2192 /S. SOUGH/spe, art unit 2192