Method, apparatus and system for private patient monitoring network
By deploying pluggable radio adapters on the existing network infrastructure of healthcare facilities and establishing end-to-end data paths, the high cost and security requirements of healthcare facilities when expanding private networks are solved, and safe and low latency are achieved network communication.
Patent Information
- Application Number
- CN202380029328.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-23
- Filing Date
- 2023-03-23
- Publication Date
- 2024-11-08
AI Technical Summary
Healthcare facilities require significant upfront capital expenditures when expanding private network solutions, and existing network infrastructure cannot meet the needs of high security and low latency.
By deploying pluggable radio adapters on existing network infrastructure, using multiple communication radio frequency ranges for data relay, establishing end-to-end data paths to support communication between terminal devices and back-end systems, and achieving a secure and private network Solution.
Deploying secure and private networks without the need for dedicated network infrastructure reduces scaling costs and provides high security and low latency network communication.
Smart Images

Figure CN118923202A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to private patient monitoring networks, and more particularly to methods, devices, and systems for establishing a private patient monitoring network over an existing network infrastructure. Background Art
[0002] A key aspect of a large healthcare ecosystem includes maintaining a stable and reliable network infrastructure that connects the different, discrete and / or mobile tools within the healthcare ecosystem. For example, in order to take advantage of new technologies, many hospitals have invested significant resources to build a hospital-wide wireless local area network ("WLAN") infrastructure for communication between medical devices, patient monitors, hospital workstations, patient information backend systems, etc. However, healthcare facilities may be required to invest resources to deploy one or more private network solutions in addition to their existing network infrastructure, which may require significant upfront capital expenditures to scale to the appropriate size of the corresponding healthcare facility and / or ecosystem. Summary of the invention
[0003] In general, the present disclosure relates to devices, systems and methods related to private patient monitoring networks. More specifically, the present disclosure relates to devices for establishing a private patient monitoring network on an existing network infrastructure, systems including such a private patient monitoring network, and methods for establishing such a network infrastructure.
[0004] According to an embodiment of the present disclosure, a pluggable radio adapter for use in a private patient monitoring network system is provided. In various aspects, the pluggable radio adapter may include: at least a first communication radio configured to send and receive data within a first radio frequency ("RF") range; a radio controller operably connected to at least the first communication radio, wherein the radio controller is configured to process and relay data through the pluggable radio adapter; and a device interface operably connected to the radio controller, wherein the device interface is configured to operably connect the pluggable radio adapter to an associated network access point and relay data between the pluggable radio adapter and the associated network access point.
[0005] In one aspect, the pluggable radio adapter may further include at least a second communication radio operably connected to the radio controller and configured to transmit and receive data within a second RF range, wherein the second RF range is different than the first RF range.
[0006] In one aspect, the pluggable radio adapter may further include at least a third communication radio operably connected to the radio controller and configured to transmit and receive data within a third RF range, wherein the third RF range is different than the first RF range and the second RF range.
[0007] In one aspect, the first RF range can be from about 1.395 GHz to about 1.4 GHz, from about 1.427 GHz to about 1.432 GHz, and / or from about 1.39 GHz to about 1.395 GHz, from about 1.432 GHz to about 1.435 GHz, the second RF range can be from about 2.402 GHz to about 2.48 GHz, and the third RF range can be from about 2.36 GHz to about 2.4 GHz or from about 2483.5 MHz to about 2500 MHz.
[0008] In one aspect, at least the first RF range can be within one of the following ranges: about 608 MHz to about 614 MHz; about 1390 MHz to about 1395 MHz; about 1395 MHz to about 1400 MHz; about 1427 MHz to about 1432 MHz; and / or about 1432 MHz to about 1435 MHz.
[0009] In one aspect, the radio controller may be configured to relay data from at least the first communication radio through the device interface and to the associated network access point as serial data.
[0010] In one aspect, the associated network access point may be a wireless local area network access point.
[0011] According to another embodiment of the present disclosure, a private patient monitoring network system is provided. The system may include: a network infrastructure including a plurality of network access points; and a plurality of pluggable radio adapters, wherein each pluggable radio adapter (302) is operably connected to a corresponding network access point. Each pluggable radio adapter may include: at least a first communication radio configured to send and receive data within a first radio frequency ("RF") range; a radio controller operably connected to at least the first communication radio, wherein the radio controller is configured to process and relay data through the pluggable radio adapter; and a device interface operably connecting the pluggable radio adapter to the corresponding network access point, wherein the device interface is configured to relay data between the pluggable radio adapter and the corresponding network access point.
[0012] In one aspect, the private patient monitoring network system may further include: a patient monitoring backend system operatively connected to a network infrastructure of the private patient monitoring network system; and one or more terminal devices wirelessly communicating with one or more of the plurality of network access points. Each terminal device may be configured to send and receive data from the one or more network access points within at least a first RF range of a pluggable radio adapter connected to each of the one or more network access points.
[0013] In one aspect, the radio controller of each pluggable radio adapter may be configured to relay data from at least the first communication radio through the device interface of the pluggable radio adapter and to the corresponding network access point as serial data.
[0014] In one aspect, each pluggable radio adapter may further include: a second communication radio operably connected to the radio controller and configured to send and receive data within a second RF range, wherein the second RF range is different from the first RF range; and a third communication radio operably connected to the radio controller and configured to send and receive data within a third RF range, wherein the third RF range is different from the first RF range and the second RF range.
[0015] In one aspect, each of the plurality of network access points may include: at least one processor; a network interface; an input / output ("I / O") interface operable to connect a corresponding pluggable radio adapter to the network access point; and a computer-readable memory storing a radio adapter component. The radio adapter component may include instructions that, when executed by the at least one processor, cause the network access point to perform one or more of the following operations: establish an end-to-end data path between at least one terminal device and a backend system, wherein the end-to-end data path includes at least a first wireless communication link between the terminal device and the network access point, and a second communication link between the network access point and the backend system, the first communication link using a network protocol corresponding to a first RF range, and the second communication link using at least one of an IEEE 802.3 network protocol and an IEEE 802.11 network protocol; receive data from the at least one terminal device using the pluggable radio adapter via the first communication link of the established end-to-end data path; and send the data received from the at least one terminal device to the backend device via the second communication link of the established end-to-end data path using the network interface.
[0016] According to yet another embodiment of the present disclosure, a method of establishing a private patient monitoring network system is provided. The method may include: (a) providing a network infrastructure including a plurality of network access points; (b) connecting a plurality of pluggable radio adapters to the plurality of network access points, wherein each pluggable radio adapter includes: (i) a first communication radio configured to send and receive data within a first radio frequency ("RF") range; (ii) a radio controller operably connected to the first communication radio, wherein the radio controller is configured to process and relay data through the pluggable radio adapter; and (iii) a device interface operably connecting the pluggable radio adapter to a corresponding network access point, the device interface being configured to relay data between the pluggable radio adapter and the corresponding network access point; and (c) establishing at least one end-to-end data path between at least one terminal device and a backend system, wherein the end-to-end data path includes at least a first communication link between the terminal device and the corresponding network access point, and a second communication link between the network access point and the backend system, the first communication link using a network protocol corresponding to the first RF range, and the second communication link using at least one of an IEEE 802.3 network protocol and an IEEE 802.11 network protocol.
[0017] In one aspect, the first RF range can be within one of the following ranges: about 608 MHz to about 614 MHz; about 1390 MHz to about 1395 MHz; about 1395 MHz to about 1400 MHz; about 1427 MHz to about 1432 MHz; and / or about 1432 MHz to about 1435 MHz.
[0018] In one aspect, a radio adapter component may be executed on each of the plurality of network access points, wherein the radio adapter component operates an adapter management component instance within a network access point host container on the network access point.
[0019] These and other aspects of the various embodiments will be apparent from and elucidated with reference to the embodiments described hereinafter. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] In the drawings, like reference numerals generally refer to like parts throughout the different views. Furthermore, the drawings are not necessarily drawn to scale, emphasis instead generally being placed upon illustrating the principles of the various embodiments.
[0021] Figure 1 is a schematic block diagram illustrating a private network solution for patient monitoring according to some aspects of the present disclosure.
[0022] Figure 2 is another schematic block diagram illustrating a private network solution for patient monitoring according to some aspects of the present disclosure.
[0023] Figure 3 is a schematic block diagram illustrating a private patient monitoring network system according to aspects of the present disclosure.
[0024] Figure 4A is a schematic diagram of a pluggable radio adapter shown in accordance with aspects of the present disclosure.
[0025] Figure 4B is a schematic diagram of a pluggable radio adapter illustrating additional aspects of the present disclosure.
[0026] Figure 5 is a block diagram of a network access point including a radio adapter assembly shown in accordance with aspects of the present disclosure.
[0027] Figure 6 is a schematic block diagram of a software interface between a multi-radio pluggable adapter and a network access point host, according to aspects of the present disclosure.
[0028] Figure 7 is a schematic block diagram of a networking access point host software instance for accessing a pluggable radio adapter, according to aspects of the present disclosure.
[0029] Figure 8 is a flow chart illustrating a method of establishing a private patient monitoring network system according to aspects of the present disclosure. DETAILED DESCRIPTION
[0030] The present disclosure relates to apparatus for establishing a private patient monitoring network on an existing network infrastructure, a system including such a private patient monitoring network, and a method of establishing such a network infrastructure.
[0031] In conventional approaches, healthcare facilities (such as hospitals) may deploy private network solutions that require dedicated access points and access point controllers that interface with the hospital's existing network infrastructure (e.g., the hospital's local area network). Private network solutions may be extremely desirable because they have the ability to deliver highly secure, low-latency network and endpoint solutions that are currently unavailable using many traditional networks. However, establishing such private network solutions typically requires a large amount of upfront capital expenditure to scale the private network solution to an appropriate size, despite having invested resources to build its existing network infrastructure. According to aspects of the present disclosure, the devices, systems, and methods described herein allow for the deployment of secure and private network solutions that do not have their own dedicated network infrastructure by leveraging a healthcare facility's existing network installation.
[0032] Now go to Figure 1 , a schematic block diagram of a private network system 100 utilizing a dedicated private network infrastructure 102 is shown.
[0033] As shown, the dedicated private network 102 includes multiple dedicated nodes 104 (also referred to as access points or APs) that can be installed on different buildings, wings, floors, and spaces across the healthcare facility. Each dedicated node / access point 104 within the dedicated private network 102 will be associated with a dedicated node controller 106 (also referred to as an access point controller (APC)). Each access point controller 106 can manage multiple access points 104. As shown, the APs 104 and APCs 106 can be connected to the facility's existing network infrastructure 108A.
[0034] Typically, the hospital's existing network infrastructure 108A may be a local area network ("LAN") that facilitates data communications via network protocols such as IEEE 802.3 and IEEE 802.11 network protocols. In an embodiment, the existing network infrastructure 108A may also be connected to one or more back-end systems, such as a back-end system 110 for patient monitoring and data collection. In an embodiment, the back-end system 110 may be a centralized patient information center, such as Philips Information Center (also known as PIIC iX).
[0035] One or more end-user devices 112 may be configured to connect to one access point 104 at a time via a dedicated private communication link. That is, each access point 104 within the dedicated private network 102 may include a dedicated radio frequency ("RF") transceiver for connecting with one or more end-user devices 112 utilizing the same dedicated RF communication technology.
[0036] In a specific example, the end-user device 112 may be one or more types of patient monitors, including but not limited to Philips Patient Monitor. For example, the end-user device 112 may be a wearable and / or wireless patient monitor, such as a Philips MX40.
[0037] In an embodiment, communications between the terminal device 112 and the dedicated private network 102 (i.e., access point 104) may operate over a protected ~1.4 GHz wireless medical telemetry service ("WMTS") and adjacent spectrum (e.g., the TerreStar E-WMTS spectrum, which includes from about 1.39 GHz to about 1.395 GHz and from about 1.432 GHz to about 1.435 GHz). In other embodiments, communications between the terminal device 112 and the dedicated private network 102 (i.e., access point 104) may operate within a ~2.4 GHz and / or medical body area network ("MBAN") spectrum (e.g., from about 2.36 GHz to about 2.4 GHz, or from about 2.4835 GHz to about 2.5 GHz).
[0038] The dedicated private network 102 and the existing network infrastructure 108A together constitute a patient monitoring network system, which uses an IP-based routing protocol to utilize access points 104 and access point controllers 106 to implement an end-to-end data path between a backend system 110 and an end-user device 112 to forward data from the end device 112 to the backend system 110.
[0039] refer to Figure 2 , showing a schematic block diagram of a private network system 100 utilizing a dedicated private network infrastructure 102 in addition to an existing network infrastructure 108A.
[0040] In certain aspects, the existing network infrastructure 108A may include a wired or Ethernet LAN, a wireless LAN ("WLAN"), or a combination thereof. The existing network infrastructure 108A may be embodied differently as known in the art, but generally includes a combination of a modem 202, a switch 204, and a WLAN access point 206A operatively connected to one another. It should be understood that the private network system 100 and the existing network infrastructure 108A may include one or more security features, such as a firewall 212, in various forms (i.e., having one or more physical and / or digital components). In an embodiment, the WLAN access point 206A may be configured to include such security features.
[0041] The network access point 206A may be primarily configured to connect with one or more user devices 208, such as computers, laptops, workstations, tablets, mobile phones, etc. By connecting with the WLAN access point 206A, the user devices 208 may connect to a communication network 210, such as the Internet.
[0042] In an embodiment, the existing network infrastructure 108A can facilitate communication between one or more user devices 208 and one or more backend systems 110 (such as a remote backend system 110A accessible via the communication network 210 or a local backend system 110B directly accessible via the existing network 108A). As used herein, the term "remote ... system" refers to an electronic system located outside the existing network 108A, whether the device is physical or virtual in nature (e.g., a physical system 110A or a virtual machine 110C). Conversely, the term "local ... system" refers to an electronic system located on-site to the existing network 108A, whether the device is physical or virtual in nature (e.g., a physical system 110B or a virtual machine 110D).
[0043] Thus, in addition to the existing network infrastructure 108A, the private network system 100 includes a dedicated private network infrastructure 102 that is built separately from the existing network infrastructure 108A. However, building such a dedicated private network 102 to a scale that is useful within most healthcare ecosystems requires significant planning and cost.
[0044] Thus, described herein is a pluggable radio adapter 302 that uses an existing network infrastructure 108B (eg, a hospital-wide WLAN network infrastructure) as a hosted network infrastructure to deploy a private patient monitoring network system 300 .
[0045] refer to Figure 3 , a private patient monitoring network system 300 according to certain aspects of the present disclosure is shown. As shown, the private patient monitoring network system 300 may include a local area network 108B, which may be an existing network infrastructure (e.g., the existing network 108A) as described above, wherein the local area network 108B includes a plurality of wireless local area network (“WLAN”) access points 206B configured to operably receive pluggable radio adapters 302. By using the existing WLAN infrastructure 108A, 108B, an end-to-end data path may be established to support communication between the terminal device 112 and the backend system 110 (e.g., the backend systems 110A-110D).
[0046] Further references Figure 4A and Figure 4B, illustrates such a pluggable radio adapter 302 according to a particular embodiment of the present disclosure. In one embodiment, the pluggable radio adapter 302A, 302B may include at least a first communication radio 304, a radio controller 306 operatively connected to at least the first communication radio 304, and a device interface 308 that operatively connects the pluggable radio adapter 302A, 302B to a corresponding WLAN access point 206B. In further embodiments, the pluggable radio adapter 302A, 302B may include a peripheral interface 310. In further embodiments, the pluggable radio adapter 302B may include at least a second communication radio 312 configured to operate within a second RF range, including at least a third communication radio 314 configured to operate within a third RF range. Each of these components is discussed in more detail below.
[0047] According to certain embodiments of the present disclosure, the pluggable radio adapter 302 may include a single communication radio 304 (e.g., the pluggable radio adapter 302A). In other embodiments, the pluggable radio adapter 302 may include two or more communication radios 304, 312, 314 (e.g., the pluggable radio adapter 302B). Each of the one or more communication radios 304, 312, 314 of the pluggable radio adapter 302A, 302B may be configured to send and receive data within a predefined portion of the RF spectrum (i.e., within a specific RF range). For example, each of the communication radios 304, 312, 314 may facilitate wireless communication between the terminal device 112 and the pluggable radio adapter 302A, 302B via a wireless communication link based on a network protocol corresponding to the specific RF range employed. To achieve this, each communication radio 304, 312, 314 includes hardware and circuitry, such as an antenna, configured to radiate and / or receive radio waves at a specified frequency.
[0048] In some aspects, at least the first communication radio 304 can be configured to send and receive data within a first radio frequency ("RF") range. In some embodiments, the first RF range can include one or more of the following ranges: from about 608 MHz to about 614 MHz; from about 1390 MHz to about 1395 MHz; from about 1395 MHz to about 1400 MHz; from about 1427 MHz to about 1432 MHz; and / or from about 1432 MHz to about 1435 MHz.
[0049] In further aspects, at least the second communication radio 312 can be configured to send and receive data within a second RF range that is different from the first RF range of the first communication radio 304. In some embodiments, the second RF range can be from about 2.402 GHz to about 2.48 GHz. In other embodiments, the second RF range can be from about 608 MHz to about 614 MHz, or from about 1395 MHz to about 1400 MHz, or from about 1427 MHz to about 1432 MHz. In a specific embodiment, the second communication radio 312 can be a Bluetooth radio.
[0050] In other aspects, at least the third communication radio 314 can be configured to send and receive data within a third RF range different from the first RF range and the second RF range. In some embodiments, the third RF range can be from about 2.36 GHz to about 2.4 GHz, or from about 2483.5 MHz to about 2500 MHz, depending on geographic and other considerations. In other embodiments, the third RF range can be from about 608 MHz to about 614 MHz, from about 1395 MHz to about 1400 MHz, from about 1427 MHz to about 1432 MHz. In an embodiment, one or more of the RF ranges may include the TerreStar E-WMTS spectrum (e.g., from about 1390 MHz to about 1395 MHz, from about 1432 MHz to about 1435 MHz). In a specific embodiment, the third communication radio 314 can be a medical body area network (MBAN) radio.
[0051] According to certain embodiments of the present disclosure, the pluggable radio adapter 302 may include a radio controller 306 operatively connected to the communication radios 304, 312, 314. In one aspect, the radio controller 306 may be configured to process and relay data through the pluggable radio adapters 302A, 302B.
[0052] More specifically, the radio controller 306 may be operable to run protocol stack firmware that, when plugged into a corresponding WLAN access point 206B, exposes the pluggable radio adapters 302A, 302B to an adapter management component (530) of the corresponding WLAN access point 206B (discussed further below).
[0053] In some embodiments, the radio controller 306 may be a field programmable gate array ("FPGA") that is specifically programmed to facilitate communication through the pluggable radio adapters 302A, 302B using one or more specific communication radios 304, 312, 314. An FPGA may include programmable logic components, referred to as "logic blocks," and programmable interconnects that may be programmed after being manufactured by a customer or designer to implement one or more features required to operate the pluggable radio adapter 302. FPGA logic blocks may be programmed to perform operations of basic logic gates or more complex combinational operators, and typically include memory elements, which may be individual circuit flip-flops or more complex memory blocks. In other embodiments, the radio controller 306 may be a microcontroller containing one or more processors, a memory that stores instructions for operating the pluggable radio adapters 302A, 302B, and an input / output interface capable of connecting to peripheral devices (e.g., communication radios 304, 312, 314).
[0054] According to certain embodiments of the present disclosure, each pluggable radio adapter 302 may include a device interface 308 operatively connected to the radio controller 306 and configured to operatively connect the pluggable radio adapter 302 to a corresponding network access point 206B.
[0055] In certain embodiments, the device interface 308 can expose the pluggable radio adapter 302 to the corresponding network access point 206B as a universal asynchronous receiver-transmitter ("UART") or serial device so that the adapter management component 530 (in the case of the corresponding network access point 206B) Figure 5 ) can use a standard serial protocol to control the communication radios 304, 312, 314. In various aspects, if the pluggable radio adapter 302 contains multiple communication radios 304, 312, 314 (e.g., adapter 302B), each radio 304, 312, 314 within the adapter 302B can be attached to the network access point 206B via the device interface 308 as a separate serial device.
[0056] According to some embodiments of the present disclosure, each pluggable radio adapter 302 may also include a peripheral interface 310 that connects the pluggable radio adapter 302 to an interface of the network access point 206B. The peripheral interface 310 contains conductive circuits / paths that facilitate the transfer of data from the pluggable radio adapter 302 to the network access point 206B. In one aspect, the peripheral interface 310 may be a USB interface that connects the pluggable radio adapter 302 to a host USB interface of the network access point 206B. In specific aspects, the peripheral interface 310 may include a USB 2.0 interface, a USB 3.0 interface, a USB Type A interface, a USB Type B interface, a micro USB interface, a USB Type C interface, a Thunderbolt interface, and the like.
[0057] According to various aspects of the present disclosure, the pluggable radio adapter 302 may be disposed within a device housing 316 having a form factor of a USB device. In other words, the device housing 316 may enclose the components of the pluggable radio adapter 302 described herein and have the following dimensions: a length of less than about 10 cm, a width of less than about 5 cm, and a height of less than about 5 cm, including a length of less than about 5 cm, a width of less than about 3 cm, and a height of less than about 3 cm.
[0058] Now go to Figure 5 , additional features of the network access point 206B of the private patient monitoring network system 300 are shown according to certain aspects of the present disclosure. In an embodiment, the network access point 206B may include at least one processor 502 (also referred to as a central processing unit or CPU), a machine-readable memory 504, an interface bus 506, all of which may be interconnected and / or communicate via a system bus 508 comprising conductive circuit paths, and instructions (e.g., machine-readable signals) may travel through the conductive circuit paths to achieve communications, tasks, storage, etc. The network access point 206B may be connected to a power source 510, which may include an internal power source and / or an external power source.
[0059] In an embodiment, at least one processor 502 may include a high-speed data processor sufficient to run program components, which may include various special processing units as known in the art. The general-purpose processor may be a microprocessor, or may also be any conventional processor, controller, microcontroller or state machine. In some embodiments, one or more features described herein may be implemented on components such as application specific integrated circuits ("ASICs"), digital signal processors ("DSPs"), field programmable gate arrays ("FPGAs"), or similar electronic devices.
[0060] In an embodiment, the interface bus 506 may include: an input / output interface 512 configured to connect the network access point 206B to one or more peripheral devices (e.g., the pluggable radio adapter 302 via a serial data protocol); a network interface 514 configured to connect the network access point 206B to the communication network 210 (e.g., using a network protocol such as IEEE 802.3 and / or 802.11); and / or a storage interface 516 configured to accept, communicate and / or connect to a plurality of machine-readable storage devices (e.g., storage device 518, removable storage devices, etc.).
[0061] In various aspects, the input / output (“I / O”) interface 512 can accept, communicate, or otherwise connect input devices and can employ connection protocols such as, but not limited to, IEEE 1394a-b, serial, universal serial bus (“USB”), etc. In particular embodiments, the I / O interface 512 of the network access point 206B operatively connects the network access point 206B to a corresponding pluggable radio adapter 302.
[0062] In various aspects, the network interface 514 operatively connects the network access point 206B to the communication network 210, which may include direct interconnections, the Internet, a local area network ("LAN"), a metropolitan area network ("MAN"), a wide area network ("WAN"), a wired or Ethernet connection, a wireless connection, and similar types of communication networks, including combinations thereof. In some embodiments, one or more user devices (e.g., user device 208) may connect to the network access point 206B via the communication network 210 and the network interface 514.
[0063] In embodiments, memory 504 may variously be embodied in one or more forms of machine-accessible and machine-readable memory, including various types of storage devices 518, random access memory 520, and read-only memory 522. In various aspects, storage devices 518 may include non-transitory storage media, magnetic disk storage, optical disk storage, storage device arrays, solid-state memory devices, and the like, including combinations thereof.
[0064] like Figure 5 As shown, memory 504 may include a radio adapter component 524, which includes a collection of programs and / or database components and / or data. Depending on the specific implementation, radio adapter component 524 may include software components, hardware components, and / or some combination of both hardware components and software components.
[0065] In particular embodiments, radio adapter component 524 may include, but is not limited to, instructions 526 having a network component 528 , an adapter management component 530 , a RESTful application programming interface (“API”) component 542 , and / or an operating system component 534 .
[0066] The foregoing components may be incorporated into, loaded from, loaded onto, or otherwise operably available to or operably obtainable from the radio adapter component 524. Similarly, the radio adapter component 524 may be incorporated into, loaded from, loaded onto, or otherwise operably available to or operably obtainable from the network access point 206B. For example, while the program components may be stored in the local storage device 518, they may also be loaded and / or stored in other storage, such as a remote cloud storage facility accessible via a communication network (e.g., the communication network 210).
[0067] The operating system component 534 may be an executable program component that facilitates the operation of the network access point 206 B. Typically, the operating system component 534 may facilitate access to I / O, network, and storage interfaces, and may communicate with other components of the system.
[0068] The network component 528 may be a stored program component executed by at least one processor, such as the at least one processor 502 of the network access point 206B. In particular, the network component 528 may facilitate communications to and from the network access point 206B via the network interface 514 in accordance with standard network protocols, such as IEEE 802.3, 802.11, etc.
[0069] More specifically, the network component 528 may negotiate communications through the existing network infrastructure 108B to connect one or more peripheral devices to, for example, a backend system 110 of the private patient monitoring network system 300. In other words, the network component 528 is responsible for establishing a communication link between the network access point 206B and one or more backend systems 110. As described above, the communication link may include a wired communication link, a wireless communication link, or a combination thereof.
[0070] The adapter management component 530 may be a stored program component that is executed by at least one processor, such as at least one processor 502 of the network access point 206B. In certain embodiments, the adapter management component 530 is configured to run on the network access point 206B and manage the corresponding pluggable radio adapter 302 in both the control plane and the data plane. In some embodiments, the pluggable radio adapter 302 may be exposed to the network access point 206B as a UART or serial device through the adapter management component 530, so that the adapter management component 530 may control the communication radio 304, 312, 314 of the corresponding pluggable radio adapter 302 using a standard serial data protocol.
[0071] In an embodiment, the adapter management component 530 can operate the network access point 206B using multiple instances 536, 538, 540 to separately manage each radio interface of the pluggable radio adapter 302 in both the control plane and the data plane. For example, as described above, the pluggable radio adapter 302 can be exposed to the network access point 206B through a separate UART or serial interface so that each communication radio 304, 312, 314 can be attached to the network access point 206B as a separate serial device.
[0072] In certain aspects, the radio adapter component 524 of the network access point 206B can support a container-based software environment. Figure 6 As shown, within the network access point 206B host container 600, the adapter management component 530 can run within separate container instances 536, 538, 540 for each radio 304, 312, 314, respectively, where each radio 304, 312, 314 is attached to the host container 600 as a separate serial device.
[0073] In further aspects, the adapter management component 530 may include a Linux BlueZ based software stack for a Bluetooth LE radio that manages the Bluetooth LE radio in both the control plane and the data plane (e.g., in some embodiments, the communication radio 312). In some aspects, the adapter management component 530 may also include an MBAN software stack for an MBAN radio (e.g., an IEEE 802.15.4 radio operating at MBAN frequencies, with an OpenThread stack in the upper layers for end-to-end IPv6 mesh networking).
[0074] In an embodiment, the network access point 206B does not have container hosting capabilities. In such an embodiment, the network access point 206B may include a RESTful API component 542 configured to send and receive data received via the pluggable radio adapter 302. Thus, in such an embodiment, one or more portions of the adapter management component 530 may be run from a virtual machine server in the existing network 108B.
[0075] For example, Figure 7 As shown, the adapter management component 530 does not operate in the network access point 206B, but rather operates in a virtual machine server 700 in the existing network 108B, where it creates a pool 702 of host access point instances 704, 706, 708 (i.e., instances of the adapter management component 530) for each pluggable radio adapter 302. Each pluggable radio adapter 302 can be assigned a host access point instance 704, 706, 708, which can use the RESTful network API to read data from and / or write data to the corresponding pluggable radio adapter 302. On each network access point 206B, the corresponding pluggable radio adapter 302 can be connected as a serial device, with a RESTful API 542 running, which maintains a receiver queue 710 and a transmitter queue 712 for received and transmitted data, respectively.
[0076] Also disclosed herein is a method 800 for establishing a private patient monitoring network system 300. Figure 8 , a method 800 of establishing a private patient monitoring network system 300 according to certain aspects of the present disclosure is shown.
[0077] At step 802, method 800 may include providing or acquiring an existing network infrastructure 108A, 108B including a plurality of network access points 206A, 206B. In an embodiment, the provided network infrastructure 108A, 108B may be a local area network, and the plurality of network access points 206A, 206B may include wireless local area network access points.
[0078] At step 804, the method 800 may include connecting the plurality of pluggable radio adapters 302 to the plurality of network access points 206A, 206B. In other words, a single pluggable radio adapter 302 may be connected to a single corresponding network access point 206A, 206B of the plurality of network access points 206A, 206B.
[0079] As described above, each of the pluggable radio adapters 302 may include: at least a first communication radio 304, which is configured to send and receive data within a first radio frequency (“RF”) range; a radio controller 306, which is operably connected to the first communication radio 304, wherein the radio controller 306 is configured to process and relay data through the pluggable radio adapter 302; and a device interface 308, which operably connects the pluggable radio adapter 302 to the corresponding network access point 206B, and the device interface 308 is configured to relay data between the pluggable radio adapter 302 and the corresponding network access point 206B.
[0080] At step 806, the method 800 may include establishing at least one end-to-end data path between at least one patient monitor 112 and the patient monitoring backend system 110. In an embodiment, the end-to-end data path may include at least a first communication link between the patient monitor 112 and a corresponding pluggable radio adapter 302 connected to the network access point 206B.
[0081] In some embodiments, the first communication link may be a wireless communication link created with the first communication radio 304 of the pluggable radio adapter 302A, 302B using a network protocol corresponding to the first RF range of the first communication radio 304. In other embodiments, the first communication link may also be a wireless communication link created with the second communication radio 312 of the pluggable radio adapter 302B using a network protocol corresponding to the second RF range of the second communication radio 312. In further embodiments, the first communication link may be a wireless communication link created with the third communication radio 314 of the pluggable radio adapter 302B using a network protocol corresponding to the third RF range of the third communication radio 314.
[0082] Although three communication radios 304, 312, 314 are explicitly described herein, the pluggable radio adapter 302 may include additional communication radios corresponding to different bands of the RF spectrum as desired.
[0083] The end-to-end data path may also include at least a second communication link between the network access point 206B connected to the corresponding pluggable radio adapter 302 and the patient monitoring backend system 110. In a particular embodiment, the second communication link includes a wired communication link, a wireless communication, or a combination thereof. In some embodiments, at least a portion of the second communication link is a wireless connection and is created using an IEEE 802.11 network protocol with the network interface 514 of the network access point 206B. In an embodiment, at least a portion of the second communication link is a wired connection and is created using an IEEE 802.3 network protocol with the network interface 514 of the network access point 206B. However, as described herein and / or known in the art, other components and devices, whether wired or wireless, including various virtual machines and firewalls may be employed.
[0084] In an embodiment, the method 800 may include step 808, wherein data is received by the network access point 206B from at least one end device 112 (e.g., a patient monitor, etc.) using the connected pluggable radio adapter 302. In other words, step 808 includes receiving data from at least one end device 112 (e.g., a patient monitor, etc.) at the network access point 206B using a network protocol corresponding to an RF range specific to one or more communication radios 304, 312, 314 present in the pluggable radio adapter 302. In an embodiment, the data is sent from the end device 112 to the network access point 206B via a first communication link of an end-to-end data path established using the pluggable network adapter 302.
[0085] In an embodiment, the method 800 may further include step 810, wherein the data received from the at least one terminal device 112 in step 808 is then sent to the at least one backend system 110. In some embodiments, as described above, the data is sent using the network interface 514. More specifically, the data is sent from the network access point 206B to the backend system 110 via the second communication link of the end-to-end data path established in step 806.
[0086] It should be understood that all combinations of the foregoing concepts and additional concepts discussed in more detail below (provided such concepts are not mutually inconsistent) are considered part of the inventive subject matter disclosed herein. In particular, all combinations of the claimed subject matter appearing at the end of this disclosure are considered part of the inventive subject matter disclosed herein. It should also be understood that terms explicitly adopted herein that may also appear in any disclosure incorporated by reference should be given the meaning most consistent with the specific concepts disclosed herein.
[0087] All definitions, as defined and used herein, should be understood to control over dictionary definitions, definitions in documents incorporated by reference, and / or ordinary meanings of the defined terms.
[0088] Unless expressly indicated to the contrary, the indefinite articles "a" and "an" as used herein in the specification and claims should be understood to mean "at least one".
[0089] As used herein in the specification and claims, the phrase "and / or" should be understood to mean "either or both" of the elements so combined, i.e., elements that are present together in some cases and separately in other cases. Multiple elements listed with "and / or" should be interpreted in the same manner, i.e., "one or more" of the elements so combined. In addition to the elements specifically identified by the "and / or" clause, other elements may optionally be present, whether related or unrelated to those elements specifically identified.
[0090] As used herein in the specification and claims, "or" should be understood to have the same meaning as "and / or" as defined above. For example, when separating the items in a list, "or" or "and / or" should be understood to include, that is, include at least one of a plurality of elements or a list of elements, but also include more than one, and optionally include additional unlisted items. Only explicitly indicate the opposite terms, such as "only one of" or "exactly one of", or when used in the claims, "consisting of..." refers to including exactly one element in a plurality of elements or a list of elements. Usually, when there is an exclusive term (such as "either", "one of", "only one of" or "exactly one of") in front, the term "or" as used herein should only be understood to indicate an exclusive alternative (that is, "one or the other but not both").
[0091] As used herein in the specification and claims, the phrase "at least one" when referring to a list of one or more elements should be understood to mean at least one element selected from any one or more elements in the list of elements, but does not necessarily include at least one of each element specifically listed in the list of elements, nor does it exclude any combination of elements in the list of elements. This definition also allows that elements other than the elements specifically identified in the list of elements referred to by the phrase "at least one" may optionally be present, whether related or unrelated to those elements specifically identified.
[0092] In the claims and in the above description, all transitional phrases such as "comprising", "including", "with", "having", "containing", "involving", "having", "including", etc. should be understood as open-ended, that is, meaning including but not limited to. Only the transitional phrases "consisting of" and "consisting essentially of" shall be closed or semi-closed transitional phrases, respectively.
[0093] It should also be understood that in any method claimed herein that includes more than one step or action, the order of the method steps or actions is not necessarily limited to the order in which the method steps or actions are recited unless explicitly indicated to the contrary.
[0094] The above examples of the described subject matter can be implemented in any of a variety of ways. For example, some aspects can be implemented using hardware, software, or a combination thereof. When any aspect is implemented at least in part in software, the software code can be run on any suitable processor or set of processors, whether provided in a single device or computer or distributed between multiple devices / computers.
[0095] The present disclosure may be a system, method and / or computer program product at any possible level of technical detail integration. The computer program product may include a computer-readable storage medium (or media) having computer-readable program instructions thereon for causing a processor to perform various aspects of the present disclosure.
[0096] A computer-readable storage medium may be a tangible device that can hold and store instructions for use by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of computer-readable storage media includes the following: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disk read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device (such as a punch card or a raised structure in a groove with instructions recorded thereon), and any suitable combination of the foregoing. The computer-readable storage medium used herein should not be interpreted as being essentially a temporary signal, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagated through a waveguide or other transmission medium (e.g., a light pulse passing through a fiber optic cable), or an electrical signal sent through a wire.
[0097] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to a corresponding computing / processing device, or downloaded to an external computer or external storage device via a network (e.g., the Internet, a local area network, a broadband area network, and / or a wireless network). The network can include copper transmission cables, optical transmission fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions to be stored in a computer-readable storage medium in the corresponding computing / processing device.
[0098] The computer-readable program instructions for performing the operation of the present disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, configuration data of an integrated circuit system, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages (such as Smalltalk, C++, etc.) and process programming languages (such as "C" programming languages or similar programming languages). The computer-readable program instructions may be run entirely on the user's computer, partially on the user's computer, run as an independent software package, partially on the user's computer and partially on a remote computer or run entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network (including a local area network (LAN) or a wide area network (WAN)), or an external computer may be connected (for example, using an Internet service provider via the Internet). In some examples, the electronic circuit system including, for example, a programmable logic circuit system, a field programmable gate array (FPGA) or a programmable logic array (PLA) may be run by using the state information of the computer-readable program instructions to personalize the electronic circuit system to run the computer-readable program instructions so as to perform various aspects of the present disclosure.
[0099] Various aspects of the present disclosure are described herein with reference to flowcharts and / or block diagrams of methods, devices (systems) and computer program products according to examples of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of boxes in the flowchart and / or block diagram can be implemented by computer-readable program instructions.
[0100] Computer-readable program instructions may be provided to a processor of a special-purpose computer or other programmable data processing device to produce a machine, such that instructions executed via the processor of the computer or other programmable data processing device create units for implementing the functions / actions specified in the flowchart and / or block diagram boxes. These computer-readable program instructions may also be stored in a computer-readable storage medium, which may direct a computer, a programmable data processing device, and / or other equipment to operate in a particular manner, such that a computer-readable storage medium having instructions stored therein includes an article of manufacture, which includes instructions for implementing various aspects of the functions / actions specified in the flowchart and / or block diagram or box.
[0101] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device, so that a series of operational steps are performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, so that the instructions running on the computer, other programmable apparatus, or other device implement the functions / actions specified in the flowchart and / or block diagram.
[0102] The flow chart and block diagram in the accompanying drawings show the architecture, function and operation of the possible implementation of the system, method and computer program product according to various examples of the present disclosure. In this regard, each frame in the flow chart or block diagram can represent a module, segment or part of an instruction, which includes one or more executable instructions for realizing the specified logical function. In some alternative implementations, the functions mentioned in the frame can occur in the order indicated in the figure. For example, the two frames shown in succession can actually be run simultaneously in essence, or the frame can sometimes be run in reverse order, depending on the function involved. It will also be noted that each frame of the block diagram and / or flow chart and the combination of the frames in the block diagram and / or flow chart can be realized by a dedicated hardware-based system that performs a specified function or action or performs a combination of special hardware and computer instructions.
[0103] Other implementations are within the scope of the following claims and other claims to which the applicant may be entitled.
[0104] Although several inventive embodiments have been described and illustrated herein, a person of ordinary skill in the art will readily conceive of various other units and / or structures for performing the functions and / or obtaining the results and / or one or more advantages described herein, and each of such variations and / or modifications is considered to be within the scope of the inventive embodiments described herein. More generally, it will be readily understood by those skilled in the art that all parameters, dimensions, materials, and configurations described herein are meant to be exemplary, and that actual parameters, dimensions, materials, and / or configurations will depend on one or more specific applications for which the present invention is taught. Those skilled in the art will recognize, or be able to determine many equivalents of the specific inventive embodiments described herein using no more than routine experiments. Therefore, it should be understood that the foregoing embodiments are presented only as examples, and within the scope of the appended claims and their equivalents, embodiments of the present invention may be practiced in a manner different from that specifically described and claimed. Inventive embodiments of the present disclosure relate to each individual feature, system, article, material, kit, and / or method described herein. In addition, if such features, systems, articles, materials, kits, and / or methods are not inconsistent with each other, any combination of two or more such features, systems, articles, materials, kits, and / or methods is included within the scope of the invention of the present disclosure.
Claims
1. A pluggable radio adapter (302) for a private patient monitoring network system (300), the adapter (302) include: at least a first communication radio (304, 312, 314) configured to transmit and receive data within a first radio frequency ("RF") range; a radio controller (306) operably connected to at least the first communication radio (304, 312, 314), wherein the radio controller (306) is configured to process and relay data through the pluggable radio adapter (302); and A device interface (308) operably connected to the radio controller (306), wherein the device interface (308) is configured to operably connect the pluggable radio adapter (302) to an associated network access point (206A, 206B) and relay data between the pluggable radio adapter (302) and the associated network access point (206A, 206B).
2. The pluggable radio adapter (302) of claim 1, further comprising: include: At least a second communication radio (304, 312, 314) operably connected to the radio controller (306) and configured to transmit and receive data within a second RF range, wherein the second RF range is different from the first RF range.
3. The pluggable radio adapter (302) of claim 2, further comprising: include: At least a third communication radio (304, 312, 314) operably connected to the radio controller (306) and configured to transmit and receive data within a third RF range, wherein the third RF range is different from the first RF range and the second RF range.
4. The pluggable radio adapter according to claim 3, in, The first RF range is from about 1.395 GHz to about 1.4 GHz, from about 1.427 GHz to about 1.432 GHz, and / or from about 1.39 GHz to about 1.395 GHz, from about 1.432 GHz to about 1.435 GHz, the second RF range is from about 2.402 GHz to about 2.48 GHz, and the third RF range is from about 2.36 GHz to about 2.4 GHz or from about 2483.5 MHz to about 2500 MHz.
5. The pluggable radio adapter (302) according to any one of claims 1 to 4, in, At least the first RF range is within one of the following ranges: about 608 MHz to about 614 MHz; about 1390 MHz to about 1395 MHz; about 1395 MHz to about 1400 MHz; about 1427 MHz to about 1432 MHz; and / or about 1432 MHz to about 1435 MHz.
6. The pluggable radio adapter (302) according to any one of claims 1 to 5, in, The radio controller (306) is configured to relay data from at least the first communication radio (304, 312, 314) through the device interface (308) and to the associated network access point (206A, 206B) as serial data.
7. The pluggable radio adapter (302) according to any one of claims 1 to 6, in, The associated network access points (206A, 206B) are wireless local area network access points.
8. A private patient monitoring network system (300), the system (300) include: A network infrastructure (108A, 108B) including a plurality of network access points (206A, 206B); A plurality of pluggable radio adapters (302), each pluggable radio adapter (302) being operatively connected to a corresponding network access point (206A, 206B), wherein each pluggable radio adapter (302) comprises: at least a first communication radio (304, 312, 314) configured to transmit and receive data within a first radio frequency ("RF") range; a radio controller (306) operably connected to at least the first communication radio (304, 312, 314), wherein the radio controller (306) is configured to process and relay data through the pluggable radio adapter (302); and A device interface (308) operatively connects the pluggable radio adapter (302) to the corresponding network access point (206A, 206B), the device interface (308) being configured to relay data between the pluggable radio adapter (302) and the corresponding network access point (206A, 206B).
9. The system (300) according to claim 8, further comprising: include: a patient monitoring backend system (110) operatively connected to the network infrastructure (108A, 108B) of the private patient monitoring network system (300); and One or more terminal devices (112) in wireless communication with one or more of the plurality of network access points (206A, 206B), each terminal device (112) being configured to send and receive data from the one or more network access points (206A, 206B) within at least the first RF range of the pluggable radio adapter (302) connected to each of the one or more network access points (206A, 206B).
10. The system (300) according to claim 8 or 9, in, The radio controller (306) of each pluggable radio adapter (302) is configured to relay data from at least the first communication radio (304, 312, 314) through the device interface (308) of the pluggable radio adapter (302) and to the corresponding network access point (206A, 206B) as serial data.
11. The system (300) according to any one of claims 8 to 10, in, Each pluggable radio adapter (302, 302B) further includes: a second communication radio (304, 312, 314) operably connected to the radio controller (306) and configured to transmit and receive data within a second RF range, wherein the second RF range is different from the first RF range; and A third communication radio (304, 312, 314) operably connected to the radio controller (306) and configured to transmit and receive data within a third RF range, wherein the third RF range is different from the first RF range and the second RF range.
12. The system (300) according to any one of claims 8 to 11, in, Each network access point (206A, 206B) of the plurality of network access points (206A, 206B) comprises: at least one processor (502); Network interface (514); an input / output ("I / O") interface (512) that operatively connects a corresponding pluggable radio adapter (302) to the network access point (206A, 206B); and a computer readable memory (504) storing a radio adapter component (524), the radio adapter component (524) including instructions that, when executed by the at least one processor, cause the network access point (206A, 206B) to perform one or more of the following operations: Establishing an end-to-end data path between at least one terminal device (112) and a backend system (110), wherein the end-to-end data path comprises at least a first wireless communication link between the terminal device (112) and the network access point (206A, 206B), and a second communication link between the network access point (206A, 206B) and the backend system (110), the first communication link using a network protocol corresponding to the first RF range, and the second communication link using at least one of an IEEE 802.3 network protocol and an IEEE 802.11 network protocol; receiving data from the at least one terminal device (112) using the pluggable radio adapter (302) via the first communication link of the established end-to-end data path; and The data received from the at least one terminal device (112) is sent to the backend device (110) using the network interface (514) via the second communication link of the established end-to-end data path.
13. A method (800) for establishing a private patient monitoring network system (300), the method (800) include: Providing (802) a network infrastructure (108A, 108B) including a plurality of network access points (206A, 206B); Connecting (804) a plurality of pluggable radio adapters (302) to the plurality of network access points (206A, 206B), wherein each pluggable radio adapter (302) comprises: a first communication radio (304) configured to transmit and receive data within a first radio frequency ("RF") range; a radio controller (306) operably connected to the first communication radio (304), wherein the radio controller (306) is configured to process and relay data through the pluggable radio adapter (302); and a device interface (308) operatively connecting the pluggable radio adapter (302) to a corresponding network access point (206A, 206B), the device interface (308) being configured to relay data between the pluggable radio adapter (302) and the corresponding network access point (206A, 206B); and At least one end-to-end data path is established (806) between at least one terminal device (112) and a backend system (110), wherein the end-to-end data path includes at least a first communication link between the terminal device (112) and a corresponding network access point (206A, 206B), and a second communication link between the network access point (206A, 206B) and the backend system (110), the first communication link uses a network protocol corresponding to the first RF range, and the second communication link uses at least one of an IEEE 802.3 network protocol and an IEEE 802.11 network protocol.
14. The method (800) according to claim 13, in, The first RF range is within one of the following ranges: about 608 MHz to about 614 MHz; about 1390 MHz to about 1395 MHz; about 1395 MHz to about 1400 MHz; about 1427 MHz to about 1432 MHz; and / or about 1432 MHz to about 1435 MHz.
15. The method according to claim 13 or 14, in, A radio adapter component (524) is run on each of the plurality of network access points (206A, 206B), the radio adapter component operating an adapter management component (530) instance within a network access point host container (600) on the network access point (206A, 206B).
