Flow generator for continuous positive airway pressure systems
By introducing readable and writable near-field communication tags and a combined hardware processor into the respiratory therapy device, the complexity of setting up medical devices has been solved, the setup process has been simplified, and the convenience and accuracy of setting up have been improved for patients.
Patent Information
- Application Number
- CN202520981083.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Utility models(China)
- Current Assignee / Owner
- Priority Date
- 2024-05-17
- Filing Date
- 2025-05-16
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2035-05-16
AI Technical Summary
The complexity of setting up and using medical devices leads to frustration for both patients and healthcare professionals, especially in home settings, and may result in patients not using valuable therapeutic devices.
A respiratory therapy device is provided, equipped with a readable and writable near-field communication tag that allows access to setup information when the device is not powered on, and enables a simplified setup process by combining the NFC tag and display screen with hardware components such as a processor, memory, and blower.
By simplifying the setup process, the convenience and effectiveness of patients using medical devices at home are improved, ensuring the accuracy and safety of setup and reducing the difficulty and frustration of setup.
Smart Images

Figure CN224958436U_ABST
Abstract
Description
[0001] Cross-reference to related applications
[0002] This application claims priority to U.S. Provisional Application No. 63 / 649,254, filed May 17, 2024, the entire contents of which are incorporated herein by reference.
[0003] Technical Overview
[0004] The technology described herein relates to the setup and / or use of medical devices. More specifically, the technology described herein relates to medical devices comprising respiratory therapy systems and components within such systems. The technology described herein relates to the setup and / or interaction of such systems in relation to providing respiratory therapy. Background Technology
[0005] Medical devices can be complex instruments that require specialized knowledge (e.g., from a physician or other medical professional) to set up and use. However, medical professionals may not always be able to help patients set up or otherwise use such devices. This is especially true when individuals use medical devices at home. The difficulty of setting them up can sometimes be frustrating for both patients and medical professionals. In fact, it can even lead patients to not use the medical device—even if such a device could provide valuable treatment.
[0006] Therefore, it should be understood that people are constantly seeking new and improved technologies, systems, and processes. Utility Model Content
[0007] In some example embodiments, a respiratory therapy (RPT) device is provided, which includes a readable and / or writable near-field communication tag. The tag can be accessed when the RPT device is not powered on and / or while the RPT device is still in its packaged state.
[0008] On one hand, a flow generator for a continuous positive airway pressure (CPAP) system is provided, the flow generator comprising: a housing including at least one hardware processor coupled to a memory; and an outlet coupled to a blower configured to deliver pressurized air to a patient via an air duct, the flow generator further comprising: a display screen disposed in the housing and coupled to the at least one hardware processor; and a near-field communication (NFC) tag including an antenna and electronics electrically connected to the antenna and the at least one hardware processor, wherein the area of the antenna of the NFC tag is equal to or greater than 50% of the area of the display screen.
[0009] On the other hand, a flow generator for a continuous positive airway pressure (CPAP) system is provided, the flow generator comprising: a housing including at least one hardware processor coupled to a memory; and an outlet coupled to a blower configured to deliver pressurized air to a patient via an air duct, the flow generator further comprising: a display screen disposed in the housing and coupled to the at least one hardware processor; and a near-field communication (NFC) tag including an antenna and electronics electrically connected to the antenna and the at least one hardware processor, wherein the antenna includes a substrate and one or more coils disposed on the substrate, wherein the antenna includes a first side, a second side, a third side, and a fourth side, wherein the first side of the antenna is at a first distance from the first side of the display screen, and the second side of the antenna is at a second distance from the second side of the display screen, and the first distance is greater than the second distance.
[0010] In another aspect, a flow generator for a continuous positive airway pressure (CPAP) system is provided, the flow generator comprising: a housing including at least one hardware processor coupled to a memory; and an outlet coupled to a blower configured to deliver pressurized air to a patient via an air duct, the flow generator further comprising: a display screen disposed in the housing and coupled to the at least one hardware processor; and a near-field communication (NFC) tag including an antenna and electronics electrically connected to the antenna and the at least one hardware processor, wherein the antenna of the NFC tag is disposed on a substrate, the substrate being layered below the display screen.
[0011] In some example embodiments, the respiratory therapy device includes one or more transceivers for implementing communication technologies. These communication technologies may include near field communication (NFC), short-range communication (e.g., Bluetooth, Bluetooth Low Energy, etc.), and local area network communication (e.g., Wi-Fi). Different communication technologies can be used to implement different (or the same) functions of the respiratory therapy device. For example, data about the treatment provided can be transmitted via Wi-Fi to an external service that can process the data using, for example, machine learning to provide insights into the treatment provided. As another example, a short-range communication channel can be established to allow a patient to use a mobile device (e.g., a telephone) to control one or more operating conditions (e.g., pressure, ramp time, etc.) of the respiratory therapy device.
[0012] In some example embodiments, the respiratory therapy device includes an NFC tag (“tag”) with memory and an antenna. The tag’s memory can be configured to ensure the authenticity and integrity of settings stored on the tag (which may include prescription data). In some examples, the stored settings are prescription data. In some examples, the memory can be configured to prevent (e.g., via NFC) reading of the settings stored on the tag. In some examples, the NFC tag can block or refuse the application of settings from another device and / or prevent the reuse of already applied settings (e.g., old settings). The memory areas of the NFC tag writable by the RPT device can be configured to be locked from the RF side to prevent tampering, disallowing write access to these memory areas via NFC. In some examples, the antenna of the NFC tag (e.g., substantially) is located behind a display panel provided in the respiratory therapy device.
[0013] This utility model summary introduces several concepts, which will be further described below in the detailed embodiments. This utility model summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter; rather, it is intended to provide an overview of the subject matter described herein. Therefore, it should be understood that the above features are merely examples, and other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description
[0014] These features and advantages, as well as other features and advantages, will be better and more fully understood by referring to the following detailed description of exemplary, non-limiting, illustrative embodiments in conjunction with the accompanying drawings, wherein:
[0015] Figure 1 It is an architectural diagram that includes a respiratory therapy system and other devices used in some examples;
[0016] Figure 2A This illustrates how packaging is done according to some embodiments. Figure 1 Block diagram of the respiratory therapy device in the middle;
[0017] Figure 2B It is a flowchart of an example process for preparing a respiratory therapy device for use by a patient, based on some examples;
[0018] Figure 3 This is a signal diagram illustrating the initial setup of a respiratory therapy device based on some examples;
[0019] Figure 4 It is based on some examples that can be implemented on a computing device. Figure 1 Functional block diagram of example components included in an RPT application;
[0020] Figure 5 Based on some examples, it can be used for Figure 4 An example of a graphical user interface provided on the display of a computing device for an RPT application;
[0021] Figure 6 Example computing devices are shown that can be used in some embodiments to implement the features described herein;
[0022] Figure 7A It is a perspective view based on some examples of respiratory therapy devices with displays, and Figure 7B and Figure 7C It is based on some examples from Figure 7A A magnified view of the display screen, including components of the NFC tag;
[0023] Figure 8 This is a block diagram illustrating the memory architecture of an NFC tag based on some examples;
[0024] Figure 9A This is a flowchart illustrating, based on some examples, the process of securely storing settings into an NFC tag; and
[0025] Figure 9B This is a flowchart based on some examples for reading settings stored in an NFC tag. Detailed Implementation
[0026] In the following description, specific details, such as particular nodes, functional entities, technologies, protocols, etc., are set forth for purposes of explanation and not limitation, in order to provide an understanding of the described technologies. It will be apparent to those skilled in the art that other embodiments may be practiced in addition to the specific details described below. In other instances, detailed descriptions of well-known methods, apparatuses, technologies, etc., have been omitted to avoid obscuring the description with unnecessary detail.
[0027] In this specific embodiment, chapters are used merely to give the reader an idea of the general subject of each chapter; as shown below, descriptions of many features span multiple chapters, and headings should not be interpreted as affecting the meaning of the descriptions included in any chapter.
[0028] Some reference numerals are used repeatedly in multiple figures to refer to the same element; for example, Figure 1 The RPT application 122 shown first in the text also combines Figure 3 and Figure 4 Use references and descriptions.
[0029] Overview
[0030] In some examples, techniques are provided for writing settings to an NFC tag provided in the RPT device. In some examples, techniques are provided for reading settings from such an NFC tag in order to load those settings into the memory of the RPT device. In some examples, NFC communication is facilitated via an NFC antenna provided behind a display panel disposed within the housing of the RPT device. This antenna can be positioned to allow data to be written to / read from the NFC's memory while the RPT device is included in packaging (e.g., for delivery to a patient). In some examples, techniques are provided for protecting the data stored in the memory of the NFC tag.
[0031] In many places in this document, software (e.g., modules, software engines, services, and applications (e.g., RPT applications, lightweight applications, etc.) and actions performed by the software (e.g., functions) are described. This is done for ease of description; it should be understood that whenever any action is described in this document as being performed by software, that action is actually performed by underlying hardware elements (such as processors and memory devices) according to instructions including that software. In some embodiments, such functionality may be provided in the form of firmware and / or hardware-specific implementations. The following... Figure 6 More details about this are provided in the description.
[0032] Figure 1 Description
[0033] Figure 1 It is an architectural diagram that includes a respiratory therapy system and other devices used in some examples.
[0034] The respiratory therapy system includes a respiratory therapy (RPT) device 110 for providing respiratory therapy to a patient 100. In some examples, the RPT device 110 may include or may be a flow generator for providing respiratory therapy as discussed herein.
[0035] Respiratory therapy can include respiratory pressure therapy, which involves supplying air to the airway inlet at a controlled target pressure that is nominally positive relative to atmosphere throughout the patient's respiratory cycle. Respiratory pressure therapy can include positive airway pressure (PAP) therapy, continuous positive airway pressure (CPAP) therapy, bilevel therapy, noninvasive ventilation (NIV), invasive ventilation (IV), and high-flow therapy (HFT). This type of therapy differs from negative pressure therapy, which may include, for example, canister ventilators or thoracic respirators.
[0036] The respiratory therapy system includes an RPT device 110 for supplying airflow to a patient 100 via an air circuit (not shown) and a patient interface (not shown). The RPT device 110 may include a pressure generator (not shown), an air filter (not shown), a humidifier (not shown), and / or other components necessary for providing respiratory therapy to the patient. The RPT device 110 may also include a hardware processor 112, a memory 114, a power supply 116, a tag 118, and a communication module 119. In some examples (e.g., as combined with...) Figure 7A As discussed above, the RPT device 110 may also include a display device and an associated display screen.
[0037] Hardware processor 112 can be configured to control the operation of the RPT device. In some examples, hardware processor 112 may be referred to herein as a "controller" or "microcontroller". The hardware processor can be configured to control or cause operational characteristics of the RPT device and / or other RPT components of the respiratory therapy system. As an illustrative example, hardware processor 112 can be configured to control a pressure generator to regulate the pressure of the airflow delivered to the patient. As another example, hardware processor 112 can be configured to control messages communicated to the patient regarding respiratory therapy (e.g., which may be delivered to the patient via RPT application 122). An example of hardware processor 112 is processor 602. A non-limiting illustrative example of hardware processor 112 is a 32-bit ARM processor—e.g., the STM32H5 from STMicroelectronics.
[0038] Memory 114 may be electronic memory, such as flash memory / NAND or other non-transitory memory, and is configured to store settings and parameters for the operation of RPT device 110. In some examples, the controller may include both processor 112 and memory 114. An example of memory 114 is memory device 604.
[0039] Power supply 116 is configured to supply power to the electrical components of the RPT device. In some examples, power supply 116 may be connected to, for example, an AC power source. In some examples, the power source may include a battery or other local power source.
[0040] Tag 118 may be a Near Field Communication (NFC) tag that allows wireless data transfer between the tag and another device (e.g., computing device 120 or another device). Tag 118 may include a copper coil, a microchip or integrated circuit, and memory for data storage. In some examples, the tag may include a microcontroller unit that includes memory, a hardware processor, and communication circuitry. In some examples, tag 118 may be a dynamic NFC tag (e.g., Type 5).
[0041] In some examples, tag 118 may be electrically connected to processor 112 and / or memory 114, such that when processor 112 is powered on (e.g., via power supply 116), processor 112 can access data stored in the non-transitory memory of tag 118. In some examples, when RPT device 110 is being initialized and / or set up (e.g., first activated by a user), it can read settings from the memory of tag 118. In some examples, data read from the tag of RPT device 110 may be used, for example, to facilitate the establishment of other wireless connections (e.g., Bluetooth, Wi-Fi, etc.) or to read prescription data. In some examples, and as discussed in more detail below, tag 118 may be queried by a clinician (e.g., using another computing device, such as a mobile device), who can then write settings (which may include configuration settings, prescription settings, etc.) to tag 118. Data written by the clinician can be read at a later point in time (e.g., when the RPT device is being set up by a user).
[0042] Depending on the examples, different configurations of tag 118 and its memory can be implemented. In some examples, tag 118 is a write-once, read-many tag. For example, once a clinician writes prescription data to tag 118, the tag may no longer be writable. In some examples, writing and / or reading from tag 118 may include performing authentication and / or authorization to read and / or write to the tag.
[0043] In some examples, the RPT device 110 may include another NFC reader / writer that provides NFC communication between the tag 118 and the processor 112 (via the included NFC reader / writer). Such an arrangement may allow the tag to be positioned, for example, away from other electrical components of the RPT device (e.g., electrically isolated from such other electrical components). Such an arrangement may also allow the tag to be positioned near the housing of the RPT device 110, thereby allowing NFC communication to be performed between a computing device (e.g., computing device 120) and the tag 118 included in the RPT device—even if the RPT device is packaged within an outer packaging (e.g., combined with…). Figure 2A (As discussed).
[0044] In any case, tag 118 can be read and / or written by processor 112 using wired communication (e.g., from processor 112) or wireless communication (e.g., NFC communication technology).
[0045] Different types of tags can be used for tag 118. In some examples, the tag can be any of type 1 to type 5 NFC tags. In some examples, tag 118 can be a passive RFID tag. In some examples, tag 118 can be an active RFID tag (e.g., having its own power source). In some examples, tag 118 can combine NFC and RFID functionality, along with corresponding antennas for the RFID and NFC operating frequencies, into the same integrated circuit. In some examples, tag 118 can include non-transitory memory that can be accessed by both RFID and NFC. In some examples, separate non-transitory memories are provided for RFID and NFC respectively. In some examples, tag 118 can be any of the following: 1) an unpowered NFC tag; 2) an unpowered dynamic NFC tag (which may include an onboard microcontroller); and / or a powered NFC reader / writer.
[0046] Communication module 119 may include a transceiver for processing wireless and / or wired communications to / from RPT device 110. In some examples, communication module 119 may include a transceiver for performing 802.11x communications (e.g., Wi-Fi). In some examples, communication module 119 may include a transceiver for performing Bluetooth communications. In some examples, communication module 119 may include an NFC reader / writer for providing a sensing field to enable communication with an NFC tag (e.g., via inductive coupling). In some examples, communication module 119 may include a cellular transceiver for communicating via 2G / 3G / 4G, etc. In some examples, communication module 119 may include multiple different transceivers. In some examples, different transceivers may share circuitry (e.g., a Wi-Fi transceiver and a Bluetooth transceiver may share circuitry to implement the respective wireless communication technologies). An example of communication module 119 is or includes network interface device 606.
[0047] In some examples, one or more communication standards or network protocols may be implemented using communication module 119 and / or RPT device 110. For example, RPT device 110 may implement the Matter communication standard and / or Thread networking protocol to facilitate data exchange between other devices, such as device 140 on a local area network.
[0048] Typically, and in conjunction with certain example embodiments, the RPT device 110 and its communication module 119 can support different types of communication technologies. Specifically, the communication module 119 can use different communication technologies to communicate over different distances. The different communication technologies that the communication module 119 can provide include: near-field communication, short-range communication, local area communication, and / or wide-area communication.
[0049] Near-field communication (NFC) includes communication technologies that can operate over distances of one foot or less. Such technologies can include NFC and RFID, among others.
[0050] Short-range communication technologies include those that can operate within a range of up to approximately 10 meters. Short-range communication technologies can include Bluetooth and other similar technologies. In some instances, short-range communication technologies can be advantageous because they can provide peer-to-peer connectivity between two devices without relying on another device (e.g., wireless access points, as is the case with Wi-Fi networks).
[0051] Local area communication includes communication technologies that can operate within a range of up to approximately 100 meters. Local area communication may include 802.11x and its variants.
[0052] Wide area communication includes communication technologies that operate over distances of several kilometers and may include communication technologies such as cellular 2G, 3G, or 4G.
[0053] Therefore, RPT device 110 can support a variety of communication technologies to allow for the execution of different types of devices and / or different types of communication.
[0054] RPT device 110 can communicate with computing device 120, which is independent of RPT device 110. Examples of computing device 120 include smartphones, tablets, laptops, or personal computers. RPT application 122 can be installed on the computing device. As discussed in more detail herein, RPT application 122 can have multiple separate modules, processes, or applications providing different functionalities. Examples of computing device 120 can be combined with... Figure 6 The computing device 600 under discussion.
[0055] The computing device 120 can be configured to communicate with the RPT device 110 using one or more communication channels. These include short-range wireless communication (e.g., via Bluetooth), near-field wireless communication (e.g., via NFC), and local wireless communication (e.g., 802.11). Local wireless communication can be provided via a local Wi-Fi network 150, which is provided via, for example, a wireless access point 130.
[0056] The computing device 120 can also communicate with external services 160 via a cellular connection and / or via a Wi-Fi connection provided by a wireless access point 130.
[0057] In some examples, the additional device 140 may connect to a local Wi-Fi network 150 and communicate with the RPT device 110 and / or the computing device 120. In some examples, communication may be direct (e.g., from one or more other devices 140 to the RPT device 110). In other examples, the RPT application 122 may receive messages from any of the other devices 140 and then generate a message to be conveyed to the RPT device 110. An exemplary example of another device may be a smart assistant device. It should be noted that in some examples, the functionality provided via the other device 140 may be provided via other applications installed and operating with the computing device 120.
[0058] RPT device 110 can be configured (via communication module 119) to connect to a local Wi-Fi network 150. This then allows a connection to be established between RPT device 110 and an external service 160, which may be provided via cloud-based computing resources or a dedicated server, etc. In some examples, data generated by RPT device 110 may be provided to the external service daily (e.g., nightly). The information provided may be offered at a relatively high resolution and may include, for example, sequential respiratory data on how RPT device 110 operates in conjunction with the delivery of treatment to a patient.
[0059] In some examples, external service 160 may include additional data processing that can be performed based on data communicated from RPT device 110. Examples of such data processing may include performing inference on a trained machine learning model, training the machine learning model, and other processing. Data processing performed by external service 160 can be used to generate customized recommendations, data, and / or insights that can help individual patients use the RPT device. In some examples, such processing or feedback may be fully or semi-automated, enabling feedback to be provided immediately, hourly, nightly, or weekly.
[0060] External services 160 can also grant access to authorized personnel (e.g., the patient's clinician 170) to review data and provide customized insights to the patient.
[0061] Figure 2A and Figure 2B Description: Preparation of the RPT device
[0062] As discussed herein, the RPT device 110 may be equipped with a tag 118. In some example embodiments, the tag 118 may be located within the RPT device to allow reading and / or writing of the tag under various conditions. For example, the communication range of NFC may be approximately 4 cm or 5 cm. In some cases, longer communication distances may exist (e.g., up to approximately 10 cm, or under certain conditions, 20 cm). For technical considerations of operating with an NFC tag, the tag may be positioned on the RPT device 110 to allow reading and / or writing of the tag while the RPT device is, for example, packaged in an outer packaging.
[0063] As an illustrative example, the RPT device 110 may be packaged in an outer packaging (e.g., cardboard, plastic, cloth, etc.) provided by the manufacturer of the RPT device 100. Figure 2A This is a block diagram illustrating, according to some examples, how the RPT device 110 can be positioned within the outer packaging 200. For example... Figure 2A As shown, tag 118 can be positioned to enable reading and / or writing of the tag while RPT device 110 is held within outer packaging 200.
[0064] In some examples, the outer packaging 200 may include an indicator 202 disposed on the outer portion of the outer packaging. The indicator 202 may be an image indicator, graphic indicator, or other visual indicator used to inform a user where an NFC reader / writer (e.g., a mobile device with NFC functionality) can be located to activate the NFC tag 118 located within the RPT device 110, which remains enclosed within the outer packaging. In some examples, the distance 204 between the tag 118 and the indicator 202 may be designed to be 5 cm, 4 cm, or 3 cm or less. In some examples, an audible confirmation or audible indicator may be provided.
[0065] Figure 2B This is a flowchart of an example process for preparing an RPT device 110 for use by a patient, based on some examples.
[0066] At 250, the RPT device 110 is manufactured and / or otherwise prepared by the manufacturer. Part of this process may include mounting or providing a tag 118 corresponding to the RPT device 110. In some examples, the tag 118 may be located within the housing of the RPT device 110. In some examples, the tag 118 may be set within a mold for the housing. In some examples, the tag 118 may be mounted into a USB-A or USB-C port (or other type of data port, such as an SD or mini SD port) provided on the housing. For example, the tag 118 may be included in a dongle that may be installed into the port during manufacturing. In some examples, the tag 118 may be set on the outer surface of the housing. In some examples, the tag may be set as part of a PCB board or a system-on-a-chip (SoC) housed within the RPT device. In some examples, the tag 118 may be set in or behind a display screen included with the RPT device. In some examples, the display may be used to output graphics or animations, etc., to instruct a user to tap their NFC reader / writer (e.g., a mobile device) onto the screen.
[0067] As part of the processing performed at point 250, a tag located in the RPT device can be configured. For example, the manufacturer can load configuration data about the RPT device onto the tag. This can include model information of the RPT device, compatible part information, and other data that can be used by clinicians, end users, shippers, or other parties who can interact with the RPT device in packaged or unpackaged form. In some examples, the data written to the tag may include a link for downloading RPT application 122 and / or its lightweight application. In some examples, the data written here may also include details / data that facilitate short-range wireless connectivity (e.g., Bluetooth).
[0068] At position 252, the manufactured RPT device (e.g., such as...) can be... Figure 2A (As shown) is packaged within an outer packaging for shipping the RPT device. The RPT device 110 may be located within the outer packaging such that the label 118 bearing the RPT device is proximate to the outer surface of the outer packaging. The outer packaging may include external indicators (e.g., NFC target area), such as... Figure 2A As shown. The RPT device 110 can be positioned such that the tag 118 is located near an NFC indicator on the outer packaging. As noted herein, the presence of an external indicator can help users (e.g., clinicians or patients) read / write NFC tags without opening the outer packaging.
[0069] At point 254, the RPT device is provided (e.g., transported / delivered) to the clinician.
[0070] At point 256, clinicians can bring the NFC reader / writer near the tag while the RPT device remains in its outer packaging. It should be noted that NFC tag activation can be performed without powering other components of the RPT device (e.g., without connecting power supply 116 to a power source).
[0071] At point 258, an NFC communication channel can be established between an NFC reader / writer used by a clinician and a tag with an RPT device (e.g., via an RF field generated by an NFC reader / writer that is enabled).
[0072] At point 260, clinicians can use a computing device to write data to the NFC tag of the RPT device included in the outer packaging. The data written to the tag may include, for example, prescription data, one or more set pressures, inspiratory pressure, expiratory pressure, climate control settings, ramp settings, patient comfort settings (such as settings for automatic start / stop of treatment), selected treatment mode (e.g., among multiple possible treatment modes), reminder settings (e.g., when to contact the clinician), settings regarding when or how often a survey can be sent to the patient, flow curve settings, EPR (expiratory pressure release) settings, RPT component settings (e.g., patient interface, humidifier, air duct, etc.), transaction date, clinician contact information, welcome message, patient name, emojis, or other settings data regarding how to set up / configure the RPT device (or other device) for a given patient.
[0073] In some examples, settings written to the tag (such as prescription data) can be encrypted to allow RPT device settings to be securely applied to the tag. In some examples, writing data to the NFC tag may require an appropriate encryption key (e.g., so that only authorized users can write data to the NFC tag). In some examples, cryptography can be used to encrypt the data written to the NFC tag, where a decryption key is used to decrypt data provided to the patient via, for example, RPT application 122. In some examples, a portion of the data stored on the NFC tag can be encrypted (e.g., patient-specific data), while non-patient-specific data (e.g., data used for settings) can be left unencrypted (or encrypted in a different way).
[0074] In some examples, the data written on the tag may include a public-key cryptographic signature. This can be a cryptographic hash of some or all of the data written / stored on the tag. This can be used to verify the correctness and / or origin of the data. In some examples, the signature may be stored / obtained from one or more external services, such as critical servers provided within a cloud-based computing infrastructure.
[0075] In some examples, public-key cryptography can be used to encrypt the data written to the tag. The public key can be retrieved from the RPT device and / or from, for example, an external service (e.g., a remotely accessible server / cloud computing resource). The private key, which can then be provided to clinicians and / or users for decrypting the data (or for obtaining the key to decrypt the data), can be provided as part of, for example, an RPT application.
[0076] Once the data is written to the tag, an NFC reader may display a confirmation message indicating that the device settings have been successfully written and the device is ready to use when powered on.
[0077] At point 262, the RPT device 110, still in its packaged state, is delivered to the patient. Advantageously, the settings for the RPT device 110 can be written to the tag 118 without requiring, for example, a clinician to unpack, set up / configure the device, and then repackage it. Instead, the clinician can interact with the tag via NFC and transmit settings and other data to the tag 118. These settings and other data can then be used when the patient sets up or otherwise uses the RPT device at home.
[0078] In some embodiments, the actions discussed in conjunction with those of a clinician can be performed by a patient or other user (e.g., a caregiver). For example, a patient or other user can load prescription settings in the manner discussed herein.
[0079] Figure 3 Description: RPT device setup
[0080] Figure 3 This is a signal diagram illustrating the setup of a respiratory therapy device 110 according to some examples.
[0081] At 302 (receiving a packaged device), the user can receive an RPT device provided by a clinician.
[0082] At point 304 (where the user brings the device into the range of the NFC tag), the user places the mobile device 300 (which can be connected to...) within range of the NFC tag. Figure 1 The computing device 120 (same or similar) is brought into the range of the NFC tag set on the RPT device 110. For example, the outer packaging of the RPT device may include a “start here” or similar graphic to prompt the patient to use their mobile device to scan or activate the NFC tag included in the RPT device 110.
[0083] At 306 (Using a mobile device to activate an NFC tag), when a mobile device is brought into the range of an NFC tag of the RPT device, the RF field generated by the mobile device can activate the tag included in the RPT device.
[0084] At 308 (transmitting the activation code / link to the mobile device), the memory on tag 118 is read using the sensing field generated by the NFC reader / writer of mobile device 300, and the activation link or code is transmitted to mobile device 300. In some examples, the activation link or code may use techniques for app clips for iOS devices and / or instant apps for Android devices. In some examples, the data transmitted from the tag may include a lightweight app. In other words, the entire lightweight app may be provided (e.g., in the absence of external internet access), rather than transmitting a link to download the lightweight app. In some examples, additional data may be read from and transmitted from the tag, such as data used to establish a short-range communication channel (e.g., via Bluetooth). In some examples, an NDEF (NFC Data Exchange Format) URI is provided. In some examples, the URI or other data may include arguments / parameters, such as Bluetooth (or Bluetooth Low Energy) pairing data.
[0085] The mobile device 300 obtains an activation link or code (to acquire the lightweight application) at 310, and the mobile device 300 then uses the activation link or code to acquire the lightweight application from the download server 390 (which may be an example of an external service 160).
[0086] A lightweight application is an application that allows users to use some of the features of a larger application. In some examples, a lightweight application can be smaller than, for example, about 10 megabytes (e.g., less than 5MB or less than 1MB). This contrasts with a larger application, which may be hundreds of megabytes (or gigabytes). A lightweight application can provide a subset of the features of a larger application. For example, an application may include features A, B, C, and D. The lightweight component of the application may only provide feature A.
[0087] Next, at 312 (where the user follows automatically provided setup instructions from a lightweight application), the mobile device 300 executes the lightweight application, which presents instructions to the user at 314 for unpacking and setting up the RPT device 110.
[0088] At 314 (unpacking and powering on the RPT device), the RPT device 110 is powered on (e.g., for the first time by a user). After power-on, the processor 112 included in the RPT device 110 can read and retrieve data from the memory of the tag 118. For example, the processor 112 can read settings or configuration data that has been written to the tag. This information may have been written by the manufacturer and / or clinician (e.g., at 260). In some examples, the data read from the tag can be decrypted and / or verified (e.g., using public-key cryptography).
[0089] At 316 (Automatically configure the RPT device using stored data from the tag), one or more settings of the RPT device can then be automatically configured using data read from the tag.
[0090] Examples of configurable settings include any of those settings written to the label by a clinician, including, for example, setting pressure, inspiratory pressure, expiratory pressure, climate control settings, flow profile settings, EPR (expiratory pressure release) settings, and mask flow profile settings to suit a mask packaged with the RPT device (or otherwise used by the patient).
[0091] In some examples, data loaded from the tag can automatically configure one or more settings or operating parameters of the RPT device at startup. In other examples, data from the tag can be loaded and used or stored (e.g., to memory 114) for later use (e.g., when treatment begins).
[0092] Another aspect of configuring RPT device 110 can be (e.g., automatically) configuring RPT device 110 for short-range communication with mobile device 300. For example, pairing mobile device 300 with RPT device 110 for Bluetooth connection.
[0093] At 318 (transmitting short-range wireless channel data via NFC), data for establishing a short-range communication channel between mobile device 300 and RPT device 110 can be transmitted via NFC and tag 118. At 320 (storing short-range wireless information in the tag), the transmitted short-range wireless information is stored together with tag 118 and then read by processor 112 (at 322 (reading short-range wireless setup data from the tag)) as part of, for example, a configuration process. Using the setup data, the short-range wireless communication channel is established at 324 (establishing the short-range wireless communication channel). It should be understood that the establishment of the short-range wireless communication channel can be performed (e.g., via Bluetooth) using multiple different messages exchanged between RPT device 110 and mobile device 300.
[0094] It should be noted that in some examples, short-range wireless setup communication can be performed in conjunction with the activation code / link communication at 308. In some examples, short-range connectivity information can be provided if the RPT device is powered on when the NFC tag is activated. If the RPT device is not powered on at that time, short-range communication information may not be provided. Alternatively, short-range communication information can be provided (e.g., at 308), and then stored for future use, and then automatically used when the RPT device is powered on (and the short-range transceiver is powered on). For example, a short-range communication channel can be automatically established during 312, while the user is setting up the RPT device.
[0095] In any case, once a short-range wireless communication channel is established, the mobile device 300 can use it to allow further communication between the mobile device 300 and the RPT device 110. It should be noted that the range of short-range wireless can be at least one (or more) orders of magnitude greater than the range of NFC communication. Furthermore, the data transmission rate of short-range wireless can also be higher.
[0096] At step 326 (Acquiring the RPT mobile application), the mobile device 300 can also acquire the RPT application 122, of which the lightweight application is part, from the download server 390. The process of downloading (and installing) the RPT application 122 on the mobile device 300 can be performed while the user follows instructions provided by the lightweight application. In other words, the RPT application 122 can be downloaded and installed as part of a background process executed by the mobile device 300.
[0097] Once the full RPT application 122 is installed, its functionality can then be used in place of the lightweight application only. In some examples, any configuration data or other information provided or obtained by the user while using the lightweight application can be transformed or passed to the full RPT application 122. This is possible because the lightweight application is part of the RPT application 122.
[0098] Once the complete RPT application 122 is installed or otherwise made available, additional setup options that the user can follow can then be provided at 328 (Perform Additional Setup). This can include, for example, videos on how to connect the RPT device 110 to other respiratory components (e.g., patient interface, humidifier, air duct, etc.). In some examples, the setup information displayed to the user as part of the RPT application 122 can be controlled or based on configuration data stored in the NFC tag 118. In other words, in addition to information about the RPT device 110, the tag 118 can also store data about other components of the RPT system (e.g., humidifier, patient interface, etc.). Such information can determine, for example, setup videos or tutorials downloaded / provided to the user via the RPT application 122.
[0099] Another part of configuring or setting up the RPT device 110 may include configuring the RPT device 110 to connect to the user's local Wi-Fi network 150. More specifically, this may involve automatically configuring the RPT device to connect to the wireless access point 130 using a Wi-Fi connection (e.g., 802.11x). Connecting the RPT device 110 to the local wireless network may then allow the RPT device 110 to communicate directly (e.g., without relying on the mobile device 300 as an intermediary) with the external service 160 (e.g., external service 392).
[0100] Configuring the RPT device 110 to connect to the local wireless network can be done using a set short-range wireless communication channel and / or via NFC. At 330 (transmitting data for local network wireless setup via short-range wireless), connection details for connecting to the local wireless network can be communicated from the mobile device 300 to the RPT device 110. This data may include, for example, the SSID and security key for accessing the local Wi-Fi network. In some examples, the SSID and security key can be transmitted by allowing the user to select them using their mobile device.
[0101] The RPT device 110 can receive Wi-Fi configuration data at 332 (Automatic Setup of Local Network Wireless). The RPT device 110 can then use the provided data and credentials to connect to the designated local wireless network. In some examples, the RPT device can provide a list of available wireless networks to a mobile device (e.g., as reported by the communication module 119), which can then display the list to a user for selection. The selected wireless network can then be relayed back to the RPT device 110, which can then attempt to connect to the indicated wireless network.
[0102] In some example implementations, a short-range communication channel can be used to transmit data about a wireless network to a mobile device 300, which can then display the information in an RPT application (e.g., on the display screen of the mobile device 300). Therefore, such implementations can allow displaying connection status, errors, feedback, or other aspects related to, for example, connecting to a Wi-Fi network, to the user.
[0103] In some examples, the RPT application and the mobile device can perform the functions of the RPT device's display—even if the RPT device does not include a display, for example, in its housing. In other words, and in conjunction with some examples, the mobile device (via the RPT application) can operate as the display of the RPT device 110 to provide information to the user. As discussed in conjunction with the examples herein, in addition to serving as a central point for displaying information about the RPT device, the RPT application can also serve as a central control point for the RPT device.
[0104] At point 336 (Establishing a connection to an external service), once connected to the local Wi-Fi network, RPT device 110 can attempt to connect (and connect to) an external service 392 (e.g., a healthcare portal / service accessible to clinician 170). For example, RPT device 110 can use a wireless adapter provided by communication module 119 to open a TCP socket connection, etc.
[0105] At 334 (Additional Settings / Controls), the mobile device 300 can perform additional settings and / or controls between the mobile device and the RPT device. Examples of additional controls may include controlling the pressure, humidity, or other settings of the RPT device 110—including turning the power on and off. Figure 5 An illustrative example of a graphical user interface and functions that can be controlled for an RPT device is shown.
[0106] It should be understood that the execution can be adjusted. Figure 3 The sequence of any or all operations within the operation. As an illustrative example, data for establishing a short-range communication channel can be provided at 306 / 308. In other words, when the RPT device is first powered on, it can attempt to establish a short-range communication channel based on information written to the NFC tag 118 when the RPT device is not powered on. When the RPT device 10 is powered on, it can then automatically connect to the mobile device 300 via short-range communication. This allows for more flexible communication while allowing initial activation using NFC at 306 / 308.
[0107] Figures 4 to 5 Description: RPT application
[0108] Figure 4 It is based on some examples that can be implemented on a computing device. Figure 1 Functional block diagram of example components included in RPT application 122.
[0109] As discussed herein, a lightweight application 400 can be initially provided to the mobile device during the setup of the RPT device (e.g., in conjunction with...). Figure 3 (The same or similar to the discussion in 310).
[0110] The lightweight application 400 may be one of several different modules or functions provided by the demanding RPT application 122. Other application modules may include, for example, a control module 402, an analysis module 404, and an integration module 406. The supplementary module 408 may include, for example, an ordering or resupply module for facilitating the ordering of additional supplies for the system being used by the patient. In some examples, this may include facilitating payment, etc. The supplementary module 408 may also include test modes that allow the user to familiarize themselves with respiratory therapy. The supplementary module 408 may also include a troubleshooting module that includes additional functionality for troubleshooting problems that the patient may encounter during treatment (e.g., mask leakage, etc.). Other modules may be included as needed.
[0111] The control module 402 can be configured to provide users with the ability to control the RPT device 110 using the RPT application 122. Figure 5 The graphical user interface shown is an exemplary example of a GUI 500 that can be generated by the control module 402.
[0112] The GUI 500 may include a graphic 502 of the RPT device 110. This graphic may vary depending on the type and / or operating state of the RPT device 110. Power control 504 may be included, allowing the user to switch the on / off state of the RPT device. It should be noted that in some examples, the RPT device 110 may also include a physical on / off switch that can be activated by the user.
[0113] The GUI 500 also includes various humidity options 506, which can be used to control the humidity level of the RPT device 110. The user can also select the ramp time 508. Selecting any of 504, 506, and 508 may result in the generation of a message and its transmission to the RPT device to change the operating state of the RPT device based on input provided to it.
[0114] In some examples, GUI 500 includes a status indicator 510 that indicates: 1) whether the RPT application is connected to the RPT device; and 2) the connection type. In other words, different indicators at 510 can be used to show the connection type and whether the connection to the RPT device 110 is a Wi-Fi connection, a Bluetooth connection, an NFC connection, no connection, or some other connection.
[0115] Analysis module 404 may include additional data analysis, which may include performing analysis on respiratory data from RPT device 110 and / or communicating with external service 160. Analysis may be performed on a computing device executing RPT application 122, or it may be performed by external service 160, which may then provide the results back to RPT application 122 for subsequent display to the user. In some examples, the analysis may include artificial intelligence and machine learning data processing.
[0116] Integration module 406 can handle interfacing with other devices 140 and services. As an example, integration module 406 can implement different standards. For instance, integration module 406 can implement the Matter connectivity standard, which provides interoperability between different types of devices. Therefore, this integration module can allow other “smart” devices connected to the local Wi-Fi network to communicate with RPT device 110 and / or RPT application 122. This can allow, for example, a user to interact with one or more other devices 140 (e.g., a smart home assistant), which can then communicate with RPT device 110 and / or RPT application 122. For example, a user can ask a smart home assistant when the filter in the RPT device should be replaced. This question can be routed from the smart home assistant to RPT device 110 and / or RPT application 122 (e.g., integration module 406), which can then determine when the filter should be replaced. The response can then be relayed back to the smart home assistant, which can then use its speaker to provide an audible answer. This functionality can be achieved by placing other devices 140 and RPT device 110 and / or RPT application 122 on the same local Wi-Fi network so that these devices can communicate with each other.
[0117] In some example embodiments, RPT application 122 may use multiple different communication channels to enable communication between RPT application 122 (e.g., mobile device 300) and RPT device 110. Additionally, the RPT device may establish another communication channel with an external service 160 that does not rely on or use the RPT application. The different communication channels may include a first communication channel 410, a second communication channel 412, and a third communication channel 414. In some examples, each of these communication channels may use a different communication technology. For example, the first communication channel 410 may use NFC, the second communication channel may use Bluetooth (or other short-range communication), and the third communication channel may use Wi-Fi (in addition to other communication infrastructure between the local Wi-Fi network and the physical location of the given service 160). In some examples, the second communication channel may be implemented using Bluetooth (or other short-range communication), Wi-Fi, or both. For example, RPT application 122 may use Bluetooth to send some messages to RPT device 110 and use Wi-Fi to send other messages to the RPT device. In some examples, the first communication channel may be implemented using Bluetooth (or other short-range communication), NFC, or both.
[0118] In some examples, once the second communication channel is established, it can then be used to perform functions provided via the lightweight application 400.
[0119] Therefore, the techniques described herein can allow seamless communication between the processor (e.g., MCU) of the RPT device and the mobile application (e.g., via the provided NFC tag, mobile application, and other hardware in and outside the RPT device). Consequently, such techniques can facilitate more advanced encryption and authentication methods as needed—potentially relying on cloud-based authentication via the mobile device and the application on it to access / control the functionality of the RPT device.
[0120] Figures 7A to 7C Description: RPT device with NFC antenna
[0121] Figure 7A This is a perspective view of an RPT device 700 with a display screen, based on some examples, and Figure 7B and Figure 7C It comes from Figure 7A An enlarged view of the display screen shown in the RPT device.
[0122] RPT device 700 includes a housing and is an example of RPT device 110, and may include or be RPT device 110, and / or vice versa. Therefore, RPT device 700 may include any or all of the components of RPT device 110. RPT device 700 may be configured to generate an airflow for delivery to a patient's airway (e.g., via a pressure generator, such as a blower), such as for treating one or more respiratory conditions described herein. RPT device 700 may include mechanical, pneumatic, and / or electrical components and is configured to execute one or more algorithms.
[0123] Air can be supplied to the patient via a pneumatic path, which may include any or all of an inlet air filter, an inlet silencer, a pressure generator (e.g., a blower) configured to supply air at positive pressure, and an outlet silencer and / or a water tank (if humidification is required). In some examples, the pneumatic path may include one or more sensors, such as pressure sensors and flow sensors. In some examples, the pneumatic path may also include an anti-backflow valve to prevent water from the humidifier from overflowing back into the electrical components of the RPT device 700.
[0124] The RPT device 700 includes an outlet (not shown) disposed in the housing, which is configured to connect to an air duct, thereby allowing pressurized air to be delivered to the patient's airway via a patient interface. This outlet may be located on the side of the RPT device opposite to the side including the display panel 725.
[0125] The housing of the RPT device includes a display device 725. The display device 725 may be disposed in a cavity, aperture, or other formed area of the housing of the RPT device 700. The display device 725 includes a display screen 702 (which may also be referred to as a display panel in some examples) and a structural frame 701 (which may also be referred to as a bezel in some examples) (e.g., Figure 7B and Figure 7C (as shown) and display electronics (e.g., to control the display screen 702). The display electronics can be disposed on a printed circuit board (PCB) located behind the display screen 702.
[0126] The display screen 702 can be designed in a square or rectangular shape, with a height of 722 and a width of 720. In other examples, other types of shape factors for the display screen (e.g., circular, polygonal, etc.) can be used. The display screen 702 includes a first side (A), a second side (B), a third side (C), and a fourth side (D). The first and second sides are opposite to each other and extend within a vertical direction (along the height 722) of the RPT device 700. The third and fourth sides are opposite to each other and extend along the longitudinal direction (along the width 720) of the RPT device 700.
[0127] A structural frame 701 is provided to secure the display screen 702 to the housing of the RPT device 700. The structural frame 701 is configured to allow the display device 725 to be mounted within the housing and / or to secure the display device 725 to the housing. In some examples, an area of the structural frame 701 may include electrical or electronic components (e.g., at least some of the electronic components in electronic device 704).
[0128] Other components that may also be included in the display device 725 include, for example, a light source and a touch panel, and may vary depending on the nature of the display technology employed (e.g., LED, OLED, touch, etc.). When the display device includes a touch panel, the display screen of the display device may be referred to as a touch screen display or a touch-enabled display screen.
[0129] The RPT device 700 also includes an NFC tag. An example of an NFC tag is... Figure 1The NFC tag 118 is located behind or stacked with the display 702 as an antenna 706 and an NFC electronic component that acts as the NFC tag. The antenna 706 is part of the NFC tag, and the NFC electronic component can be included in the display electronics (of the display device) as an electronic component 704. The display electronics provide functionality for the display 702, and the NFC electronic component provides functionality for the NFC tag. Therefore, electronic component 704 can provide functionality for both the display device and the NFC tag. In some examples, the NFC electronic component and the display electronics can be provided separately. In some examples, the antenna 706 and / or the NFC electronic component can be integrated into the PCB of the display device. In some examples, the NFC electronic component and the display electronics can share a common PCB, etc. In some examples, the electrical connection (712) from the electronic component to the MCU acts as a shared bus, which provides transmission from the NFC electronic component and the display electronics to the MCU.
[0130] In some examples, display screen 702 includes a user-viewable surface for displaying images, etc., to a person. Antenna 706 may be positioned relative to the user-viewable surface of the display. For example, the antenna may be positioned below display screen 702 and thus visually hidden from external views.
[0131] Electronic device 704 is electrically connected via electrical connection 712 to other electrical components of RPT device 700 (e.g., processor 112, etc.). As described herein (e.g., in conjunction with...). Figures 2A to 5 As discussed, an NFC tag can be provided to allow NFC communication—for example, when the RPT device 700 is powered off. When the RPT device is powered off, data can be stored in the memory of the electronics 704, and then accessed and stored in, for example, memory 114 when the device is powered on (via electrical connection 712).
[0132] When the display screen 702 is mounted within the RPT device 700, all or part of the antenna 706 may be substantially disposed behind or below the display screen 702, the structural frame 701, etc. For example, the antenna 706 may be disposed on a first substrate (e.g., an antenna substrate) stacked below a substrate including the display panel (e.g., a display substrate). In some examples, the display substrate may include the antenna, such that a separate substrate is not required.
[0133] In some examples, the outer boundary of antenna 706 (which may also be the outer boundary periphery or edge) is located within the outer boundary of structural frame 701 (which may also be the outer boundary periphery or edge) and / or the outer boundary of display screen 702 (which may also be the outer boundary periphery or edge). In other words, the antenna can be contained within the space of the housing where display device 725 is located. However, in some examples, some portions of antenna 706 may extend beyond the outer boundary of display screen and enter the boundary area occupied by structural frame 701 (e.g., Figure 7B (As shown). Therefore, various structural arrangements that integrate NFC tags (e.g., antennas) into the RPT device can be provided by combining various embodiments. This integration can allow NFC functionality to be provided in areas of the RPT device including the display device.
[0134] Antenna 706 is electrically connected to the NFC electronics of electronics 704 via a first electrical connection 710A and a second electrical connection 710B. In some examples, the first electrical connection 710A and the second electrical connection 710B are connected to opposite ends of antenna 706 (which may be a loop antenna in some examples). Other types of electrical connections between the antenna and electronics can also be provided in various embodiments.
[0135] In some examples, the antenna 706 can be tuned to operate at 13.56 MHz to provide NFC communication functionality.
[0136] NFC electronic devices may include memory (e.g., an appropriately sized EEPROM, such as 4Kbit, 8Kbit, 16Kbit, 64Kbit, etc.), energy harvesting electronics, capacitors (e.g., tuning capacitors for assisting in the frequency tuning of antenna 706), and other components providing NFC functionality. The NFC electronic devices are configured to provide one or more data transmission interfaces. A first transmission interface is provided via a wireless RF link (e.g., via NFC and antenna 706). A second transmission interface (e.g., which may be I...) 2 (C, etc.) is provided via a wired link 712. The second transmitting interface allows other computing resources (such as the hardware processor of the RPT device) to access the data stored in the memory of the NFC tag. An illustrative example of an NFC tag and the electronics included therein is the ST25DV64K from STMicroelectronics.
[0137] Antenna 706 includes a substrate and one or more coils disposed on the substrate. Various techniques for disposing the coils on the substrate include etching and printing. Antenna 706 may include a first side (along...) Figure 7BThe first side (A), the second side (opposite to the first side and close to the first electrical connection 710A and the second electrical connection 710B), the third side (along C), and the fourth side (opposite to the third side and along D). In some examples, different types of geometry other than rectangles or squares (e.g., polygons, circles, etc.) can be used. In some examples, each of the first, second, third, and fourth sides can be referred to as the first edge, second edge, third edge, and fourth edge of the antenna.
[0138] Figure 7B and Figure 7C Examples illustrate how the antenna 706 can be positioned relative to the display 702 and / or its dimensions can be determined, based on some examples. For example... Figure 7A As shown, antenna 706 can be biased toward a first end of RPT device 700 (e.g., away from the vertical centerline of the RPT device) and / or a first side of the display screen. This positioning can advantageously allow for reading / writing of the NFC tag when it is packaged within an outer package (e.g., 200). It should be noted that the antenna positioning may be related to... Figure 7A / Figure 7B / Figure 7C The positioning shown is reversed. For example, the positioning of antenna 706 can be interchanged with the positioning of electronics 704. In some examples, the antenna can occupy substantially the entire length of one side of the display (e.g., any of A, B, C, and D), while occupying a portion of two other sides, but not any portion of the fourth side. For example, the antenna can be positioned along the entire length of side D, a portion of sides A and B, but not any portion of side C, or other combinations thereof.
[0139] According to various embodiments, the size of antenna 706 can be appropriately adjusted. In some examples, the size of antenna 706 can be set to be equal to or greater than 50% of the area of display screen 702 (referred to herein as the display area), which is called the antenna area. In some examples, the antenna area is at least 60% of the display area. In some examples, the antenna area is between approximately 2 / 3 and approximately 3 / 4 of the display area. In some examples, the antenna area is between 50% and 80% of the display area. In some examples, the antenna area is less than 50% of the display area. In some examples, the width and / or height of antenna 706 can be between 20mm and 40mm. For example, in some examples, the antenna can be set as a 40mm x 40mm antenna, or in other examples, the antenna can be set as a 30mm x 40mm antenna.
[0140] Other areas behind the display 702 (e.g., those areas not occupied by the antenna 706) can be used to accommodate the electronics 704 for the display and / or NFC tag.
[0141] like Figure 7B As illustrated, antenna 706 can be positioned such that its first side extends beyond the first side of display screen 700 and into structural frame 701. Alternatively, as Figure 7C As shown, antenna 706 can be positioned such that its first side extends to but does not exceed the first side of the display screen.
[0142] In some examples, the first side of the antenna is positioned near the first side of the display. Proximity positioning can include positioning where the first side of the antenna extends beyond (e.g., Figure 7B (As shown) The first side of the display (such that the first side of the antenna extends into the bezel), and the first side of the antenna is substantially flush with and / or contained within the first side of the display, etc.
[0143] In some examples, the first side of the antenna is a first distance (e.g., between 0 mm and 5 mm) from the outer edge of the bezel on the first side of the display (and / or the outer edge of the display). In contrast, the second side of the antenna is a second distance 724 (e.g., greater than 5 mm) from the outer edge of the bezel on the second side of the display (and / or the outer edge of the display). Therefore, in some examples, the first distance used to position the antenna is greater than the second distance.
[0144] In some examples, the distances between the third and fourth sides of the antenna and the third and fourth sides of the display are the same or similar. In some examples, the gaps between the third and fourth sides and the outer edges of the bezel (and / or the outer edges of the display) may be, for example, less than 2mm, 3mm, 4mm, or 5mm. In some examples, the gaps to the outer edges of the bezel (and / or the outer edges of the display) may be equidistant for both the third and fourth sides.
[0145] In some examples, the height of antenna 706 (aligned with height 722) may occupy all or substantially all of the height of the space where display screen 702 is located within RPT device 700. For example, the height of the antenna may be at least 90%, 95%, or more of the height of the display screen. In contrast, the width of antenna 706 (aligned with width 720) may occupy up to 50%, 60%, 66%, or 75% of the width of the space where display screen is located within RPT device 700. The remaining space may be substantially occupied by electronics 704 and / or electrical connections 712.
[0146] In some examples, the NFC tag's antenna can be located within the RPT device, excluding the area below the display. In some examples, the RPT device may not include a display (e.g., a displayless RPT device), but may include the NFC tag. In some examples, the antenna may be located on the left side of the RPT device (e.g.,...). Figure 7A(as shown) and / or along the top of the RPT device (when the RPT device is facing the viewer, such as...) Figure 7A (As shown).
[0147] Figure 8 Description: Memory architecture
[0148] Figure 8 This is an example of NFC tags based on some examples (such as...) Figures 7A to 7C A block diagram of the memory architecture of the tag 118 and / or NFC tag described herein. More specifically, an access control architecture is provided to ensure that the correct system (or individual, such as a clinician, etc.) has proper access to the memory of the NFC tag located within the RPT device.
[0149] Memory 800 may be included as part of electronic device 704. Memory 800 may include, for example, 8K of user EEPROM memory and additional system configuration memory. Depending on various examples, other sizes of memory may be used.
[0150] Various memory locations can be provided within the memory of the NFC tag. The memory controller included in the electronics of the NFC tag can control access to the memory 800 and its locations. Different access methods can be provided depending on whether the memory 800 is accessed via a wired connection 820 or a wireless connection 830. More specifically, the MCU 822 (e.g., processor 112) can be configured to access the memory 800 via a wired connection 820 (e.g., via I...). 2 Memory 800 can be accessed via NFC connection 830 (e.g., C, etc.). In contrast, an NFC reader / writer 832 (e.g., computing device 120) can be configured to access memory 800 via NFC connection 830. Furthermore, each memory location can be accessed according to one of the following access modes: 1) read / write; 2) read-only; and 3) write-only. Each memory location of memory 800 can be configured for access depending on which of the wired connection 820 (also referred to as the MCU side) and the wireless connection 830 (also referred to as the RF side) is accessing a given location in memory. Details of various access restrictions will be discussed below for each respective memory location.
[0151] The memory 800 can be divided into multiple different memory locations. This will be discussed below. Figure 8 Each of the memory locations shown.
[0152] Memory location 802 includes data of a URL or URI and a unique identifier (e.g., UID) for a given RPT device and / or its hardware components (e.g., an NFC tag included in an RPT device). Access to memory location 802 via the MCU side is provided in read-write mode. Access to memory location 802 via the RF side is provided in read-only mode. In some examples, the UID may be a MAC address, cellular ID, or other unique identifier that allows a given RPT device to be uniquely identified from other RPT devices (e.g., potentially of the same type). In some examples, the data at memory location 802 includes a URL or URI, and the UID is dynamically retrieved from elsewhere in memory 800 (e.g., from memory location 808). In other examples, the URI is stored as a string that includes the UID. For example, stored as " <url>The string "+UID".
[0153] Memory location 804 may include dynamic enhancement parameters. This may include, for example, Bluetooth pairing data (e.g., BLE pairing parameters), which can be transmitted to the requesting mobile device to establish a Bluetooth connection with RPT device 700. In some examples, this can be achieved from 318. Figure 3 The signal diagram shown accesses and uses memory location 804. In some examples, access to memory location 804 via the MCU side is provided in read-write mode, and access to memory location 804 via the RF side is provided in read-only mode.
[0154] Memory location 806 includes Cyclic Redundancy Check (CRC) data for error detection and / or correction. In some examples, access to memory location 806 via the MCU side is provided in read-write mode, and access to memory location 806 via the RF side is provided in read-only mode. In some examples, atomicity may not be guaranteed when writing to memory 800 from the MCU side. Therefore, CRC data is provided.
[0155] Memory location 808 includes a unique chip identifier. Access to memory location 808 via the MCU side is provided in read-only mode. Access to memory location 808 via the RF side is also provided in read-only mode. In some example embodiments, the unique chip ID may be an identifier for the NFC chip and / or may be used as an identifier for the RPT device. In some examples, this identifier is written to memory location 808 during device manufacturing (e.g., in...). Figure 2B (250 in the memory location). After writing, the memory location will be locked to prevent overwriting. In some examples, memory location 808 may include multiple different unique identifiers. For example, the identifier of the RPT device, the identifier of the NFC tag, the identifier of the Bluetooth transceiver, and the MAC address, etc. All of these identifiers can be stored in memory location 808 to uniquely identify the RPT device (or its components) from other such devices.
[0156] Memory location 810 includes random numbers. Access to memory location 810 via the MCU side is provided in read-write mode. Access to memory location 810 via the RF side is provided in write-only mode. (As in the combination of 9A and...) Figure 9B The random number discussed can be used to protect or ensure the integrity of setup data to be applied to an RPT device. For example, a random number can be used to prevent replay attacks or the reapplication of settings that have already been legally signed, including prescription data (which may be old). In some examples, the use of random numbers provides an extra layer of protection against misuse of setup data. For instance, if another person attempts to tap the RPT device again using NFC and applies the same prescription data (as well as any other data such as a random number, unique ID, signature, etc.), the RPT device can reject the data because the MCU will verify / invalidate the data based on the random number stored therein (e.g., at startup).
[0157] In some examples, the random number can be a monotonic counter (e.g., the number of seconds or milliseconds since a given period). The random number can be written to memory location 810 via NFC communication and / or via a request from the MCU side. In some examples, the random number is generated by any device writing to memory 812 (e.g., computing device 120, processor 112, etc.).
[0158] Memory location 812 includes flow generator settings. Access to memory location 812 via the MCU side is provided in read-only mode. Access to memory location 812 via the RF side is provided in write-only mode. Figure 2B An example of writing traffic generator settings is discussed in connection 260.
[0159] Memory location 814 includes a digital signature. Access to memory location 814 via the MCU side is provided in read-only mode. Access to memory location 814 via the RF side is provided in write-only mode. The digital signature stored here ensures the correct application of the traffic generator settings (e.g., that the settings did not originate from another device or have not been overwritten). The authenticity and integrity of the settings (memory location 812) can be ensured via the digital signature stored here. This digital signature can be generated using public-key cryptography and based on any one or more of the following: 1) a random number—e.g., stored in memory location 810; 2) a unique ID from memory location 808 (or retrieved from elsewhere); 3) the settings data to be stored (e.g., prescription data); and 4) a signing key (e.g., which can be retrieved from a cloud service such as 160). In some examples, alternative and / or additional aspects can be used to generate the signature (e.g., the traffic generator settings or their hash).
[0160] According to various example embodiments, other memory locations may be provided, including those described above with different access restrictions. For example, dynamic tag system configuration data (e.g., tag boot configuration, static settings, passwords, keys, etc.) may be provided in memory locations inaccessible from the RF side. In some examples, additional memory locations may store data access logs to the memory or other events occurring on the NFC tag. These other aspects may be stored in memory 800, which may include both user-accessible memory and system-only accessible memory.
[0161] In some examples, URL / URI data (memory location 802), one or more unique identifiers (memory location 808), and other enhanced parameters (memory location 804) can be publicly read from any NFC reader within the reading range. However, they can remain immutable on the RF side by applying read-only protection implemented by the NFC tag's memory controller. In some examples, specific access control to a given memory location can be enforced using, for example, a security key held by the NFC tag's memory controller.
[0162] Figures 9A to 9B Description: Secretly writing and reading NFC data
[0163] Figure 9A It is a flowchart illustrating the process of writing settings from the RF side into an NFC tag, based on some examples, and Figure 9B This is a flowchart based on some examples for reading settings stored in an NFC tag.
[0164] Go to Figure 9A At step 900, an NFC communication channel is established between the mobile device and the RPT device. Step 900 can be connected with... Figure 2B The same as or similar to 258 in the previous section. An NFC communication channel can be established by placing an NFC reader / writer (e.g., a mobile device) approximately 10 cm (e.g., 7 cm or 8 cm) away from the antenna of an NFC tag located within the RPT device. As discussed herein, this can be done while the RPT device is still in its packaged state, powered off, de-energized, or otherwise not inserted. The NFC communication channel can be established by the NFC tag collecting power from RF transmissions from the NFC reader.
[0165] At 902, once the NFC communication channel is established, one or more unique identifiers are retrieved from memory 800—specifically from memory location 808. Such unique identifiers may have been written to memory during the manufacture of the RPT device (e.g., written to a memory location once).
[0166] At 904, RPT device settings are generated and / or retrieved. In some examples, this can be done by a clinician downloading the settings (e.g., from 160, etc.). Alternatively or additionally, the clinician can use the graphical user interface provided to computing device 120 to specify one or more RPT device settings.
[0167] Once the setup is complete, an encrypted random number (random number) is generated at position 906. As noted above, this random number can be a monotonic counter generated based on time (e.g., the number of seconds since a given period). Depending on the embodiments, other techniques for generating random numbers may also be used. In some examples, the random number may be generated by computing device 120, and in other examples, it may be provided to computing device 120 from, for example, cloud computing infrastructure.
[0168] At position 908, a digital signature is generated. The generation of this digital signature may be based on access to an enterprise security subsystem (e.g., provided in a cloud-based infrastructure) to allow for the generation of a secure signature. For example, the enterprise security subsystem may maintain a signing key used to generate the digital signature. The signature generation may be a function of at least a random number generated at position 906 and a unique identifier of the RPT device at position 902.
[0169] At 910, the RPT device settings, random number and digital signature are written to memory 800 via NFC communication from computing device 120.
[0170] Figure 9A The process shown is merely an example. Alternatively or additionally, other example processes may involve retrieving a unique identifier for the RPT device without first activating the NFC tag. For example, a user can type in or otherwise enter a serial number via a mobile application (or website) on their mobile device (e.g., computing device 120). In some examples, the serial number may be scannable using a QR code or similar provided on the tag of the RPT device. Using the serial number, computing device 120 can retrieve relevant setup data associated with the serial number from, for example, an external service 160. In other words, setup data can be pre-entered in association with a specific traffic generator having the provided serial number. In some examples, setup data may be stored along with, for example, a user account or other identifier. Setup data can be retrieved based on the identifier (as discussed in 904). Once the setup data is retrieved, a random number and a digital signature can be generated.
[0171] Once the setup, digital signature, and random number are ready, the user can be prompted (via a graphical user interface on the user's mobile device) to bring the mobile device within range of the RPT device's NFC tag. In some examples, the RPT device may include an NFC indicator (e.g., an image). When within range, an NFC communication channel can be established, and the RPT device's unique identifier can be retrieved from the NFC tag. The retrieved unique identifier can be used to verify that the communication is for the correct RPT device by comparing the communicated unique identifier with an identifier retrieved based on a QR code, etc. If the two identifiers do not match, the writing process can be terminated (e.g., because the RPT device is not the expected RPT device). However, if the two identifiers match, the setup, signature, and random number can be written to the NFC tag on the RPT device. It should be noted that in this example, the user receives a prompt as soon as the user's mobile device is ready to write data to the NFC tag. Therefore, this allows the user to tap the device more quickly (e.g., hold the NFC reader on the tag) and / or respond more quickly. This is because communication with any external service (e.g., 160) has already been performed, and the data to be written to the tag is already prepared (e.g., once the identifier retrieved from the tag is verified) for writing. In other words, communication with the external system / service 160 can be performed in the background before the user performs NFC communication. Therefore, this can provide the user with a more efficient and / or more effective experience.
[0172] It should be noted that if multiple NFC devices are within range of the reader / writer while communicating via NFC, addressing modes can be used to target known tag IDs and / or other unique identifiers during NFC arbitration and anti-collision cycles (e.g., performed at 900). In some examples, this can also be used to ensure that the correct settings are communicated to the devices for the wires intended for those settings. Thus, for example, in each instance of establishing an NFC communication channel, a unique identifier can be retrieved. For example, this could allow a clinician to bring computing device 120 into range to retrieve a unique identifier. The connection can then be terminated (e.g., due to removing the reader from the NFC tag), and the clinician can proceed with the settings. When ready to write the final settings to the NFC tag, an NFC channel can be established, and a digital signature can be generated using the unique identifier. In some examples, the retrieved unique identifier can be compared with a unique identifier associated with a previously generated RPT device setting. If these identifiers match, the setting is valid. If these identifiers do not match, transmission may be rejected.
[0173] It should be noted that once the settings are written to memory 800, access to these settings (e.g., at memory location 812) is blocked. Therefore, once the RPT device settings are written to memory, they cannot be read from the RF side because the NFC tag's memory controller will block access. This approach enhances the security of the RPT device settings (e.g., including privacy and confidentiality) – especially when the RPT device is transferred from the clinician to the patient.
[0174] However, in some examples, different functionalities can be provided to allow reading RPT device settings from the RF side. For example, in some examples, the RPT device settings stored in the NFC tag can be encrypted.
[0175] Now go to Figure 9B This describes the process of reading settings from an NFC tag. Specifically, once the RPT device is turned on and the settings are applied, the MCU invalidates the settings in the tag, for example, by changing the random number, which in turn invalidates the signature.
[0176] At position 950, power on RPT device 700.
[0177] At point 952, during the startup phase of RPT device 700 (or once the RPT device is started), the RPT device's MCU requests RPT settings, a signature, a unique identifier, and a random number from the NFC tag. (See also...) Figure 8 The discussed method enables access to these memory locations on the MCU side of the NFC tag, and accordingly (e.g., via the use of I...) 2 The wired communication link of C provides data to the MCU.
[0178] At 954, the MCU verifies whether the settings are the current settings by verifying the digital signature. This is done by generating a comparison digital signature using a random number from the NFC tag and a unique identifier stored in the NFC tag. If the newly generated digital signature matches the digital signature retrieved from memory 800, the settings are assumed to be valid.
[0179] It should be noted that if the signature is invalid, the RPT device can provide a notification to the user informing them that the settings for the RPT device have not been loaded.
[0180] However, if the signature is valid, a new random number is generated at 956, and written to the NFC tag at 958 to overwrite the previous random number. In some examples, the random number is generated by the RPT device. However, other devices can also generate the random number, including computing device 120 (e.g., which can communicate with the RPT device via Bluetooth). By overwriting the random number in memory 800 with the new random number, the settings stored therein are invalidated (because the generated digital signature stored in memory 800 will be invalid for the new random number). In some examples, the random number stored on the NFC tag can be deleted from the NFC tag's memory. In other words, 956 and 958 can be replaced with deleting (or overwriting) the existing random number, making it no longer retrieved from the NFC tag's memory. This process allows the settings stored on the NFC tag to be invalidated / removed without deleting them. It should be noted that access to the digital signature and settings is read-only on the MCU side to maintain the integrity of the settings stored thereon.
[0181] At 960, the settings retrieved from memory 800 are applied to the RPT device (e.g., stored in memory 114). In some examples, 960 can be performed before invalidating the random number on the NFC tag.
[0182] At point 962, the patient can then use the RPT device to provide respiratory therapy using the newly loaded settings. It should be noted that... Figure 9B The process shown allows the settings stored on the tag to be automatically loaded into the RPT device with minimal or no user input.
[0183] Figure 6 Description
[0184] Figure 6 This is a block diagram of an example computing device 600 (which may also be referred to as, for example, a "computing device," a "computer system," or a "computing system") according to some embodiments. In some embodiments, the computing device 600 includes one or more of the following: one or more processors 602 (which may be referred to as a "hardware processor" or solely as a "hardware processor"); one or more memory devices 604; one or more network interface devices 606; one or more display interfaces 608; and one or more user input adapters 610. Additionally, in some embodiments, the computing device 600 is connected to or includes a display device 612. Additionally, in some embodiments, the computing device 600 is connected to or includes an input device 614. As will be explained below, these elements (e.g., processor 602, memory device 604, network interface device 606, display interface 608, user input adapter 610, display device 612, input device 614) are hardware devices (e.g., electronic circuitry or combinations of circuitry) configured to perform various functions of the computing device 600. In some embodiments, these components of the computing device 600 may be collectively referred to as computing resources (e.g., resources for executing instructions, including processors (one or more processors 602), storage devices (one or more memory devices 604), and I / O (network interface devices 606, one or more display interfaces 608, and one or more user input adapters 610). In some instances, the term "processing resources" may be used interchangeably with the term "computing resources." In some embodiments, multiple instances of the computing device 600 may be arranged as a distributed computing system.
[0185] In some embodiments, each or any processor in processor 602 is or includes, for example, a single-core or multi-core processor, a microprocessor (e.g., which may be referred to as a central processing unit or CPU), a digital signal processor (DSP), a microprocessor associated with a DSP core, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, and / or a system-on-a-chip (SoC) (e.g., an integrated circuit including a CPU and other hardware components such as memory and networking interfaces). And / or, in some embodiments, each or any processor in processor 602 uses an instruction set architecture such as x86 or an advanced RISC machine (ARM).
[0186] In some embodiments, each or any of the memory devices 604 is or includes random access memory (RAM) (such as dynamic RAM (DRAM) or static RAM (SRAM)), flash memory (e.g., based on NAND or NOR technology), hard disk, magneto-optical media, optical media, cache memory, registers (e.g., storing instructions), or other types of means of means for executing volatile or non-volatile storage of data and / or instructions (e.g., on the processor of the processing system 602 or software executed by the processor of the processing system). Memory devices 604 are examples of non-transitory computer-readable storage media.
[0187] In some embodiments, each network interface device or any network interface device in network interface device 606 includes one or more circuits (such as a baseband processor and / or a wired or wireless transceiver) and implements a first layer, second layer, and / or higher layer for one or more wired communication technologies (such as Ethernet (IEEE 802.3)) and / or wireless communication technologies (such as Bluetooth, WiFi (IEEE 802.11), GSM, CDMA2000, UMTS, LTE, LTE-A Advanced, LTE Pro, 5G New Radio (5G Nr), and / or other short-range, medium-range, and / or long-range wireless communication technologies). The transceiver may include circuitry for both the transmitter and receiver. The transmitter and receiver may share a common housing and may share some or all of the circuitry within that housing to perform transmission and reception. In some embodiments, the transmitter and receiver of the transceiver may not share any common circuitry and / or may be located in the same or separate housings.
[0188] In some embodiments, data is transmitted via an electronic data network. The electronic data network can be wired and / or wireless. It can include both wired and wireless communications. The electronic data network includes specific implementations in which data is transmitted from one computer process space to another, and therefore can include, for example, inter-process communication, pipes, sockets, and communications via direct cables, cross-connect cables, fiber optic channels, and wired and wireless networks. In some examples, network interface device 606 may include ports or other connections that enable such connections and the electronic transmission of data between various components of a distributed computing system.
[0189] In some embodiments, each or any display interface in display interface 608 is or includes one or more circuits that receive data from processor 602, generate corresponding image data based on the received data (e.g., via a discrete GPU, integrated GPU, or CPU performing graphics processing), and / or output the generated image data (e.g., via High Definition Multimedia Interface (HDMI), DisplayPort Interface, Video Graphics Array (VGA) Interface, or Digital Video Interface (DVI)) to display device 612, which displays the image data. Alternatively or additionally, in some embodiments, each or any display interface in display interface 608 is or includes, for example, a video card, video adapter, or graphics processing unit (GPU).
[0190] In some embodiments, each user input adapter or any user input adapter in user input adapter 610 is or includes one or more circuits that receive and process input from one or more user input devices. Figure 6 User input data (not shown) is included in, attached to or otherwise communicates with in the computing device 600, and the one or more circuits output data to the processor 602 based on the received input data. Alternatively or additionally, in some embodiments, each or any user input adapter in the user input adapter 610 is or includes, for example, a PS / 2 interface, a USB interface or a touchscreen controller; and / or the user input adapter 610 facilitates input from the user input device 614 (such as, for example, a keyboard, mouse, touchpad, touchscreen, etc.).
[0191] In some embodiments, the display device 612 may be a liquid crystal display (LCD), a light-emitting diode (LED) display, or other types of display devices. In embodiments where the display device 612 is a component of the computing device 600 (e.g., the computing device and the display device are included in a unified housing), the display device 612 may be a touchscreen display or a non-touchscreen display. In embodiments where the display device 612 is connected to the computing device 600 (e.g., external to the computing device 600 and communicating with the computing device 600 via wired wireless communication technology and / or wireless communication technology), the display device 612 may be, for example, an external monitor, projector, television, display screen, etc.
[0192] The computing device 600 may be coupled to or otherwise communicate with one or more external devices 616. The external device 616 may be another instance of the computing device 600, or it may be a different hardware device. In some examples, the external device may be hosted in a cloud-based computing environment, etc.
[0193] Figure 6 The hardware configurations shown and described above are provided as examples, and the subject matter described herein can be utilized in combination with a variety of different hardware architectures and components. For example, many of the figures in the accompanying drawings of this document show individual function / action blocks; in various embodiments, (a) individual hardware circuits, (b) application-specific integrated circuits (ASICs) specifically configured to perform the described functions / actions, (c) one or more digital signal processors (DSPs) specifically configured to perform the described functions / actions, and (d) the above references can be used. Figure 6 The hardware configuration described herein, (e) the functionality of those blocks is achieved through other hardware arrangements, architectures and configurations, and / or through a combination of the technologies described in (a) through (e).
[0194] Selected terms
[0195] The elements described in this document include actions, features, components, items, attributes, and other terms. Whenever a given element is described in this document as existing in "some embodiments," "various embodiments," "certain embodiments," "certain example embodiments," "some example embodiments," "exemplary embodiments," "example," "instance," or "example instance," or whenever any other similar language is used, it should be understood that the given element exists in at least one embodiment, but not necessarily in all embodiments. Consistent with the foregoing, whenever this document describes an action as "may," "can," or "may" perform an action, when a feature, element, or component is "may," "can," or "may" be included in or applicable to a given context, when a given item is "may," "can," or "may" possess a given attribute, or whenever any similar phrase involving the terms "may," "can," or "may" is used, it should be understood that the given action, feature, element, component, attribute, etc., exists in at least one embodiment, but not necessarily in all embodiments.
[0196] In some instances, terms and symbols may imply specific details that are not required for practicing the described techniques. For example, although the terms "first" and "second" may be used, they are not intended to indicate any order unless otherwise stated, but may be used to distinguish different elements. Furthermore, although process steps in a method may be described or illustrated in sequence, such sequence is not required. Those skilled in the art will recognize that such sequence may be modified and / or its aspects may be performed concurrently or even synchronously.
[0197] Unless the context clearly indicates otherwise and a range of values is provided, it should be understood that every intermediate value (to one-tenth of the lower limit unit) between the upper and lower limits of the range, as well as any other stated or intermediate values within the range, are covered by this technique. The upper and lower limits of these intermediate ranges (which may be independently included in the intermediate range) are also covered by this technique, but are subject to any explicit exclusions within the range. Where the range includes one or both of these limitations, the range excluding any one or both of those included limitations is also included in this technique.
[0198] Furthermore, where one or more values stated herein are implemented as part of this technology, it should be understood that, unless otherwise stated, such values may be approximate, and such values may be used to any suitable significant figure to the extent that a particular implementation of the technology may allow or require. As used herein, the terms "approximate," "substantially," "about," or any similar terms mean + / - 5% to 10% of the stated value.
[0199] Unless otherwise expressly stated, the terms and phrases used in this document and their variations should be interpreted as open-ended rather than restrictive. As examples of the foregoing: "and / or" includes any and all combinations of one or more of the associated listed items (e.g., a and / or b means a, b, or a and b); the singular forms "a," "an," and "described" should be interpreted as meaning "at least one" or "one or more," etc.; the term "example" may be used interchangeably with the term "exemplary" to provide an example of the subject matter under discussion, rather than an exhaustive or restrictive list thereof; the terms "comprising" and "including" (and their other variations and variations) specify the presence of an associated listed element, but do not preclude the presence or addition of one or more other elements; and if an element is described as "optional," such a description should not be construed as indicating the need for other elements not so described.
[0200] As used herein, the term "non-transitory computer-readable storage medium" includes registers, cache memories, ROMs, semiconductor memory devices (such as D-RAM, S-RAM, or other RAMs), magnetic media such as flash memory, hard disks, magneto-optical media, optical media such as CD-ROMs, DVDs, or Blu-ray discs, or other types of volatile or non-volatile storage devices used for non-transitory electronic data storage. The term "non-transitory computer-readable storage medium" does not include transiently propagating electromagnetic signals.
[0201] Unless explicitly stated using the phrases "means for..." or "steps for...", claims are not intended to be understood / interpreted as means plus function. Claim elements intended to be understood / interpreted as means plus function language (if any) will explicitly indicate this intention by stating the phrases "means for..." or "steps for..."; the foregoing applies to claim elements in all types of claims (method claims, device claims, or other types of claims), and, to avoid ambiguity, also to claim elements nested within method claims. Consistent with the preceding statement, no claim element (in any type of claim) should be understood / interpreted using means plus function unless explicitly stated using the phrases "means for..." or "steps for...".
[0202] Whenever this document states that a hardware element (e.g., a processor, network interface, display interface, user input adapter, memory device, or other hardware element) or a combination of hardware elements is "configured to" perform an action, it should be understood that such language specifies the physical state of the hardware element's configuration, not merely its intended use or capabilities. The physical state of the hardware element's configuration fundamentally relates the action described after the phrase "configured to" to the physical characteristics of the hardware element described before the phrase "configured to." In some embodiments, the physical state of the hardware element's configuration may be implemented as an application-specific integrated circuit (ASIC) including one or more electronic circuits arranged to perform the action, or a field-programmable gate array (FPGA) including programmable electronic logic circuits arranged to perform the action, these programmable electronic logic circuits being arranged in series or in parallel to perform the action according to one or more instructions (e.g., via a configuration file of the FPGA). In some embodiments, the physical state of the hardware element's configuration may be specified by storing program code (e.g., instructions in the form of firmware, software, etc.) in a memory device, which, when executed by a hardware processor, causes the hardware element (e.g., via configuration registers, memory, etc.) to perform the action according to the program code.
[0203] Therefore, one (or more) hardware elements can be understood as being configured to perform an action, even if the specified hardware element is not currently performing an action or is not running (e.g., not turned on, not powered on, not used, etc.). Consistent with the foregoing, in any claim type (method claim, device claim, or other type of claim), the phrase "configured to" in a claim should not be understood / interpreted as a means plus a function; this includes claim elements (such as hardware elements) nested within a method claim.
[0204] Other applications of the described topic
[0205] Although process steps or algorithms, etc. (including but not limited to references) Figure 2B and Figure 3 A process may be described or declared in a specific order, but such processes can be configured to operate in a different order. In other words, any sequence or order of steps that may be explicitly described or declared in this document does not necessarily indicate that the steps must be performed in that order; rather, the steps of the process described herein can be performed in any possible order. Furthermore, although described or implied to occur non-simultaneously (e.g., because one step is described after another), some steps may be performed simultaneously (or in parallel). Moreover, the illustration of a process in the accompanying drawings does not imply that the illustrated process excludes other variations and modifications thereof, nor does it imply that the illustrated process or any of its steps are necessary or preferred.
[0206] Although various embodiments have been shown and described in detail, the claims are not limited to any particular embodiment or example. The foregoing description should not be construed as implying that any particular element, step, scope, or function is necessary. All structural and functional equivalents of the elements of the foregoing embodiments known to those skilled in the art are expressly incorporated herein by reference and are intended to be covered. Furthermore, the apparatus or method need not solve every problem that this invention attempts to address, as this invention covers such problems. Any embodiments, features, elements, components, or steps in this document are not intended for public use only.< / url>
Claims
1. A flow generator for a continuous positive airway pressure (CPAP) system, the flow generator comprising: A housing, the housing including at least one hardware processor coupled to a memory; and An outlet, coupled to a blower configured to deliver pressurized air to the patient via an air duct. The flow generator is characterized in that it further includes: A display screen, disposed within the housing and coupled to the at least one hardware processor; and A near-field communication (NFC) tag, the NFC tag including an antenna and electronic components, the electronic components being electrically connected to the antenna and the at least one hardware processor. The area of the antenna of the NFC tag is equal to or greater than 50% of the area of the display screen.
2. The flow generator of claim 1, wherein at least a portion of the antenna extends beyond the area of the display screen.
3. The flow generator according to claim 1, wherein the flow generator further comprises: A structural frame in which the display screen is mounted, the structural frame being integrated with the housing.
4. The flow generator of claim 3, wherein at least a portion of the antenna extends beyond the area of the display screen and into the area of the structural frame.
5. The flow generator of claim 1, wherein the display screen includes a user-facing surface visible to the patient, and the antenna is disposed opposite to the user-facing surface.
6. The flow generator according to claim 5, wherein the antenna is mounted behind the display screen.
7. The flow generator of claim 6, wherein at least a portion of the antenna extends beyond the boundary of the display screen.
8. The flow generator of claim 1, wherein the area of the antenna of the NFC tag is equal to or greater than 60% of the area of the display screen.
9. The flow generator of claim 8, wherein the region of the antenna is between 60% and 80% of the region of the display screen.
10. The flow generator of claim 1, wherein the antenna comprises a substrate and one or more coils disposed on the substrate, wherein the antenna comprises a first side, a second side, a third side, and a fourth side. The first side of the antenna is a first distance away from the first side of the display screen, and the second side of the antenna is a second distance away from the second side of the display screen, wherein the first distance is greater than the second distance.
11. The flow generator of claim 10, wherein the third side of the antenna is located near the third side of the display screen, and the fourth side of the antenna is located near the fourth side of the display screen.
12. The flow generator of claim 11, wherein the third distance between the third side of the antenna and the third side of the display screen is equal to the fourth distance between the fourth side of the antenna and the fourth side of the display screen.
13. The flow generator according to claim 1, wherein the display screen is a touch screen.
14. A flow generator for a continuous positive airway pressure (CPAP) system, the flow generator comprising: A housing, the housing including at least one hardware processor coupled to a memory; and An outlet, coupled to a blower configured to deliver pressurized air to the patient via an air duct. The flow generator is characterized in that it further includes: A display screen, disposed within the housing and coupled to the at least one hardware processor; and A near-field communication (NFC) tag, the NFC tag including an antenna and electronic components, the electronic components being electrically connected to the antenna and the at least one hardware processor. The antenna includes a substrate and one or more coils disposed on the substrate, and the antenna includes a first side, a second side, a third side, and a fourth side. The first side of the antenna is a first distance away from the first side of the display screen, and the second side of the antenna is a second distance away from the second side of the display screen, wherein the first distance is greater than the second distance.
15. A flow generator for a continuous positive airway pressure (CPAP) system, the flow generator comprising: A housing, the housing including at least one hardware processor coupled to a memory; and An outlet, coupled to a blower configured to deliver pressurized air to the patient via an air duct. The flow generator is characterized in that it further includes: A display screen, disposed within the housing and coupled to the at least one hardware processor; and A near-field communication (NFC) tag, the NFC tag including an antenna and electronic components, the electronic components being electrically connected to the antenna and the at least one hardware processor. The antenna of the NFC tag is disposed on a substrate, which is layered below the display screen.
16. The flow generator of claim 14 or 15, wherein at least a portion of the antenna of the NFC tag extends beyond the outer boundary of the display screen and / or enters the boundary region of the structural frame of the display screen.
17. The flow generator according to claim 14 or 15, wherein the area of the antenna of the NFC tag is equal to or greater than 50% of the area of the display screen.
