Communication optimization via updated communication parameters

Abstract

Embodiments are described herein for updating communication parameter sets between a peripheral medical monitoring device and a central medical monitoring device. The central medical monitoring device may identify a triggering event for updating a communication parameter set related to RF communications between the peripheral medical monitoring device and the central medical monitoring device. The central medical monitoring device may collect system specification information related to at least one of the peripheral medical monitoring device or the central medical monitoring device and transmit a request for the updated communication parameter set that includes at least a portion of the system specification information. The central medical monitoring device may receive a response comprising the updated communication parameter set that is compatible with the at least the peripheral medical monitoring device or the central medical monitoring device having the at least the portion of the system specification information.

Description

Matter No. P38818-WOCOMMUNICATION OPTIMIZATION VIA UPDATED COMMUNICATION PARAMETERSBACKGROUND

[0001] People with medical conditions or other health-related conditions often need to monitor events to maintain their health. For example, a person with diabetes often needs to monitor their current glucose level regularly to make sure their glucose level does not go too high or too low. These people may perform continuous monitoring to determine whether applied therapeutic interventions are having the intended effect, or if additional interventions are needed to help treat their condition.

[0002] Individuals with medical conditions may use a number of devices to help them monitor their current condition and / or events that may occur over the course of a day.Individuals often use their mobile devices to monitor their current condition. In one example, a person with diabetes may use their mobile device (e.g., in combination with other sensor devices) to monitor their current blood glucose levels, insulin dosing information, information related to carbohydrate intake, and / or other information that may be helpful in treatment of the diabetic condition.

[0003] In order to view information related to a current condition on a mobile device, the mobile device may receive information from other monitoring devices. For example, the mobile device may receive current blood glucose levels from a blood glucose monitoring device and / or a continuous glucose monitor. These devices may communicate via a communication medium, such as a wireless RF communication signal.

[0004] Each mobile device may have a preferred set of RF communication parameter sets. For example, RF communication protocols, such as the BLUETOOTH communication protocol or BLUETOOTH low energy (BLE) communication protocol for example, may be implemented by different mobile devices to communicate via the wireless RF communication signal with other devices. The RF communication parameter sets may depend on specific information related to the mobile device, such as the mobile device’s hardware operating system type, hardware operating system version, and / or other specific constraints related to the specific mobile device. Since there is a large variety of mobile devices that may be implemented forMatter No. P38818-WO communicating with different monitoring devices, each with its own particular communication parameter set, it can be difficult to determine a proper parameter set for being implemented with a particular medical monitoring device.SUMMARY

[0005] Embodiments are described herein for updating communication parameter sets between a peripheral medical monitoring device and a central medical monitoring device. For example, a central medical monitoring device may include a mobile device. The central medical monitoring device may identify a triggering event for updating a communication parameter set related to RF communications between the peripheral medical monitoring device and the central medical monitoring device. The RF communication may comprise a Bluetooth Low Energy (BLE) connection configured to communicate via a BLE communication protocol. The central medical monitoring device may collect system specification information related to at least one of the peripheral medical monitoring device or the central medical monitoring device. The system specification information may comprise at least one of hardware specifications or software specifications related to at least one of the peripheral medical monitoring device or the central medical monitoring device.

[0006] The triggering event for updating a communication parameter set related to RF communications between the peripheral medical monitoring device and the central medical monitoring device may include an establishment of the RF communication between the peripheral medical monitoring device and the central medical monitoring device. The triggering event may include an indication of completion of initialization of the peripheral medical monitoring device. The triggering event may include an indication of receipt of a medical device data from the peripheral medical monitoring device. The triggering event may include an indication of an update to an operating system on the central medical monitoring device, The triggering event may include an indication of an interruption to RF communication connectivity via the RF communication medium for a period of time. The triggering event may include an indication that a period of time has elapsed since checking for the updated communication parameter set.

[0007] The system specification information may include a type of the peripheral medical monitoring device with which the central medical monitoring device is enablingMatter No. P38818-WO communication. The system specification information may include a model of the peripheral medical monitoring device with which the central medical monitoring device is enabling communication. The system specification information may include a version of hardware installed on the peripheral medical monitoring device with which the central medical monitoring device is enabling communication. The system specification information may include a version of software installed on the peripheral medical monitoring device with which the central medical monitoring device is enabling communication. The system specification information may include a type of the central medical monitoring device. The system specification information may include a model of the central medical monitoring device. The system specification information may include a version of hardware installed on the central medical monitoring device. The system specification information may include a version of software installed on the central medical monitoring device.

[0008] The central medical monitoring device may transmit, to a communication parameter reconfiguration subsystem at a remote computing device, a request for the updated communication parameter set related to the RF communications between the peripheral medical monitoring device and the central medical monitoring device. The request may include at least a portion of the system specification information related to at least one of the peripheral medical monitoring device or the central medical monitoring device.

[0009] The central medical monitoring device may receive, in response to the request for the updated communication parameter set, a response comprising the updated communication parameter set that is compatible with the at least the peripheral medical monitoring device or the central medical monitoring device having the at least the portion of the system specification information. The response may indicate at least a threshold level of compatibility between the at least the portion of the system specification information and the updated communication parameter set for improving the RF communications by at least a threshold. The at least the threshold level of compatibility may be determined based on at least a threshold amount of system specification information received in the request being identified as being compatible with the at least the portion of the system specification information stored with the updated communication parameter set.

[0010] The response may indicate that the communication parameter reconfiguration subsystem comprises the updated communication parameter set corresponding to the at least theMatter No. P38818-WO portion of the system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device. The updated communication parameter set comprise one of a connection interval or timeout, a minimum connection interval, a maximum connection interval, a peripheral latency, a supervision timeout, an advertisement interval, an advertisement count, or an advertisement repetition time. The updated communication parameter set may be configured to affect power consumption on the at least one of the peripheral medical monitoring device or the central medical monitoring device, a data transfer speed between the peripheral medical monitoring device and the central medical monitoring device, and / or a stability of connection between the peripheral medical monitoring device and the central medical monitoring device. For example, the updated communication parameter set may balance power consumption, data transfer, and / or stability of connection by maintaining two or more of these parameters above a threshold. The central medical monitoring device may transmit the updated communication parameter set to the peripheral medical monitoring device to configure the peripheral medical monitoring device for communication with the central medical monitoring device using the updated communication parameter set.

[0011] In response to transmitting the request for an updated communication parameter set, the central medical monitoring device may receive a second response that indicates that the updated communication parameter set is unavailable at the communication parameter reconfiguration subsystem for the at least the portion of the system specification information related to at least one of the peripheral medical monitoring device or the central medical monitoring device. The central medical monitoring device may transmit, based on the second response that indicates the updated communication parameter set is unavailable, a default communication parameter set to the peripheral medical monitoring device that is compatible with multiple types of peripheral medical monitoring devices and multiple types of central medical monitoring devices. The central medical monitoring device may receive a notification that the updated communication parameter set is available at the communication parameter reconfiguration subsystem for the at least the portion of the system specification information related to at least one of the peripheral medical monitoring device or the central medical monitoring device. The central medical monitoring device may send a request for the updated communication parameter set after receiving the notification that the updated communication parameter set is available at the communication parameter reconfiguration subsystem.Matter No. P38818-WO

[0012] The central medical monitoring device may receive, from the peripheral medical monitoring device, a rejection of the updated communication parameter set. Based on the rejection, the central medical monitoring device and / or the peripheral medical monitoring device may revert to the default communication parameter set for performing communication between the peripheral medical monitoring device and the central medical monitoring device. Prior to sending the request for the updated communication parameter set, the central medical monitoring device may check a local storage to identify whether the communication parameter set has been previously downloaded and shared with the peripheral medical monitoring device.

[0013] The central medical monitoring device may be configured to communicate with the peripheral medical monitoring device on a first communication link. The central medical monitoring device may be configured to communicate on a second communication link with the remote computing device operating the communication parameter reconfiguration subsystem. The first communication link and the second communication link use at least one of a different communication spectrum or protocol.

[0014] Prior to transmitting the request for the updated communication parameter set to the communication parameter reconfiguration subsystem, the central medical monitoring device may determine that the central medical monitoring device is unable to communicate with the remote computing device and utilize a condensed updated communication parameter set stored locally at the central medical monitoring device for updating the communication parameters at the peripheral medical monitoring device. The condensed updated communication parameter set may include less parameters than the updated communication parameter set.

[0015] The remote computing device may receive, from the central medical monitoring device, the request for the updated communication parameter set related to the RF communication between the peripheral medical monitoring device and the central medical monitoring device. The request may include the at least the portion of system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device. The remote computing device may determine, at a communication parameter reconfiguration subsystem, an availability of the updated communication parameter set corresponding to the at least the portion of system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device. The remote computing device may transmit, in response to the request for the updatedMatter No. P38818-WO communication parameter set, a response comprising the updated communication parameter set that is compatible with the at least the peripheral medical monitoring device or the central medical monitoring device having the at least the portion of the system specification information.

[0016] The remote computing device may determine the availability of the updated communication parameter set by determining at least a threshold level of compatibility between the updated communication parameter set and the at least the portion of the system specification information for improving the RF communications by at least a threshold.

[0017] Prior to receiving the request, the remote computing device may determine, at the communication parameter reconfiguration subsystem, an unavailability of the updated communication parameter set corresponding to the at least the portion of system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device. The remote computing device may store an indication of the unavailability of the updated communication parameter set corresponding to the at least the portion of system specification information. The remote computing device may transmit, to the central medical monitoring device, a response indicating the unavailability of the updated communication parameter set corresponding to the at least the portion of system specification information. The remote computing device may receive updates to communication parameter sets for different peripheral medical monitoring devices and central medical monitoring devices and determine the availability of the updated communication parameter set based on the updates to the communication parameter sets for different peripheral medical monitoring devices and central medical monitoring devices and the indication of the prior unavailability of the updated communication parameter set corresponding to the at least the portion of system specification information. The remote computing device may transmit, to the central medical monitoring device, a notification that the updated communication parameter set is available at the remote configuration subsystem.BRIEF DESCRIPTION OF THE DRAWINGS

[0018] FIGs. 1 A and IB are perspective views of representative systems in a user environment.

[0019] FIG. 1C is a sequence flow diagram illustrating an example process for updating one or more communication parameter sets at one or more devices in a system.Matter No. P38818-WO

[0020] FIG. 2 is a sequence flow diagram illustrating an example process for updating one or more communication parameter sets at one or more devices in a system.

[0021] FIGs. 3A and 3B show sequence flow diagrams for example processes for establishing a dedicated connection between a peripheral medical monitoring device and a central medical monitoring device and enabling updates of communication parameter sets for performing communications therebetween.

[0022] FIG. 4 shows a flowchart of an example process for updating a communication parameter set for performing communications between a central medical monitoring device and a peripheral medical monitoring device.

[0023] FIG. 5 shows a flowchart of an example process for determining an updated communication parameter set for performing communications between a central medical monitoring device and a peripheral medical monitoring device.

[0024] FIG. 6 is a block diagram of an example computing device.

[0025] FIG. 7 is a block diagram of an example continuous monitoring device.

[0026] FIG. 8 is a block diagram of an example blood glucose meter (BGM) device.DETAILED DESCRIPTION

[0027] FIG. 1A is a perspective view of a representative system 101 in a user environment. As shown in FIG. 1A, a user 100 may be a person with a medical condition. For example, the user 100 may be a person with diabetes or a person with another medical condition. The user 100 may use one or more medical monitoring devices to help monitor and / or treat the medical condition. For example, the user 100 may use one or more medical monitoring devices to help monitor an analyte levels and / or treat the medical condition.

[0028] In one example, the medical condition may include a diabetic condition. The diabetic condition may include a metabolic syndrome, pre-diabetes, type 1 diabetes, type 2 diabetes, and / or gestational diabetes. The user 100 may be in an extreme diabetic state, such as hypoglycemia or hyperglycemia, when the blood glucose level of the user 100 is above or below a threshold blood glucose level. The user 100 may use a medical monitoring device, such as a glucose monitoring device, to monitor blood glucose levels or other analyte levels for monitoring and / or treating a medical condition.Matter No. P38818-WO

[0029] A glucose monitoring device may include any device that detects and reports a level of glucose in the blood of the user, either through direct measurement of the blood or through an indirect detection process. A blood glucose level is also referred to as a blood sugar level. Examples of glucose monitoring devices include, but are not strictly limited to, continuous glucose monitoring devices, flash glucose monitoring devices, and blood glucose meters that provide a single measurement of blood glucose levels from a blood sample in a “spot” monitoring process. A blood glucose treatment device may include any device that treats a diabetic condition of the user, either through direct treatment into the blood or through an indirect treatment process or by providing information to allow for treatment.

[0030] In some embodiments, the blood glucose monitoring device and / or blood glucose treatment device is a pen device 103. The pen device 103 may include any injector pen capable of monitoring and / or managing insulin delivery. Example pen devices may communicate with an external device, such as the mobile device 104 and / or a remote computing device 122, to determine insulin levels, calculate doses, track doses, deliver insulin, and / or provide other information such as notifications or alerts. In some examples, pen devices may periodically communicate data indicating the blood glucose levels of the user 100 to an external device, such as a mobile device 104, for computing or storing the blood glucose levels of the user 100.

[0031] In some embodiments, the glucose monitoring device is a continuous glucose monitor (CGM) 102. The CGM 102 includes a subcutaneous sensor that is used to sense and monitor the amount of glucose in interstitial fluid of the user 100. The CGM 102 includes a transmitting device that is located directly over the sensor that wirelessly powers the data transfer from the sensor. The CGM 102 periodically communicates data indicating the blood glucose levels of the user 100 to an external device, such as a mobile device 104, for computing or storing the blood glucose levels of the user 100.

[0032] Some embodiments of the mobile device 104 operate as a CGM controller device. Though the mobile device 104 is provided as an example of a device with which the CGM 102 communicates, the CGM 102 may communicate with other dedicated CGM controller devices for providing similar functionality that is described herein for the mobile device 104. In some cases, the CGM 102 processes the blood glucose data to provide an amount of glucose in interstitial fluid of the user 100. In some cases, the CGM 102 provides the blood glucose data to the mobile device 104 and / or pen device 103, and the mobile device 104 and / or pen device 103Matter No. P38818-WO processes the blood glucose data to manage the diabetic condition and provide treatment notifications as described herein.

[0033] In some embodiments, the blood glucose monitoring device is a flash glucose monitor (FGM) 111. The FGM 111 includes a subcutaneous sensor that is used to sense and monitor the amount of glucose in interstitial fluid of the user 100. A separate reader device, such as the mobile device 104, pen device 103, or another reader device, receives the blood glucose data from the sensor of the FGM 111 when the device is within range, such as but not limited to the RF range, of the sensor. The FGM 111 transmits an instantaneous blood glucose level or a graphical trend of the blood glucose level to the reader device for display. The mobile device 104 processes the blood glucose data to manage the diabetic condition and provide treatment notifications as described herein.

[0034] In some embodiments, the user 100 uses a blood glucose meter (BGM) 106 as a blood glucose monitoring device to monitor blood glucose levels. The BGM 106 includes a port 108 that receives a blood glucose measurement strip 110. The user 100 deposits a sample of blood on the blood glucose measurement strip 110. The BGM 106 analyzes the sample and measure the blood glucose level in the sample. The blood glucose level measured from the sample is displayed on a display 112 of the BGM 106 or communicated to an external device, such as the mobile device 104. The mobile device 104 processes the blood glucose data to manage the diabetic condition and provide treatment notifications as described herein.

[0035] The blood glucose level measured by the pen device 103 or BGM 106 or computed using data received from the CGM 102 or FGM 111, is used to treat the diabetic condition of the user 100. The mobile device 104 communicates with the CGM 102, FGM 111, the BGM 106, and / or pen device 103 using wired or wireless communications that are transmitted and received between devices on a wired or wireless communication medium. The mobile device 104 may also, or alternatively, receive data from a monitoring device (e.g., the CGM 102, FGM 111, the BGM 106, and / or pen device 103) indirectly via one or more other devices (e.g., a remote computing device 122 or another computing device). For example, a monitoring device may be capable of communicating data to one or more intermediate computing device for storing data thereon for being transmitted to and / or requested by the mobile device 104. The mobile device 104, the CGM 102, a CGM controller, the BGM 106, the FGM 111, or pen device 103 may be collectively referred to as user devices or computingMatter No. P38818-WO devices. The mobile device 104 communicates with the CGM 102, the FGM 11 1, the BGM 106, and / or pen device 103 using the same or different wired or wireless protocols. For example, the mobile device 104 communicates with the CGM 102, FGM 111, the BGM 106, and / or pen device 103 using BLUETOOTH®, BLUETOOTH® low energy (BLE), near field communication (NFC), THREAD®, WIFI®, ZIGBEE®, WI-MAX®, a cellular communication protocol, a proprietary wireless communication protocol, or another radio frequency (RF) communication protocol.

[0036] Though various blood glucose monitoring devices (e.g., pen device 103, CGM 102, BGM 106, FGM 111, and / or another blood glucose monitoring device) are provided as examples of medical monitoring devices, other medical monitoring devices may be implemented for measuring and / or monitoring other medical conditions of the user 100. For example, other medical monitoring devices may be implemented to monitor any other medical conditions based on analyte levels of the user 100 and / or communications between connected devices may similarly utilize one or more embodiments described herein.

[0037] The medical monitoring devices may be resource-restricted devices, as compared to other computing devices in the system 101, such as the mobile device 104 and / or the remote computing device 122. One or more of the medical monitoring devices may be hardware and / or software restricted devices. For example, the medical monitoring devices may be battery powered or power-restricted devices. These devices may operate in sleep / wake states for battery conservation. One or more of the medical monitoring devices may be restricted in processing power and / or memory capacity when compared to other computing devices in the system. As such, the user 100 may implement the one or more of the medical monitoring devices along with other computing devices, such as the mobile device 104 and / or the remote computing device 122, for managing and / or treating their medical condition.

[0038] The mobile device 104 may establish a connection to one or more medical monitoring devices (e.g., pen device 103, CGM 102, BGM 106, FGM 111, and / or another medical monitoring device) at a time. For example, the mobile device may establish a connection via a wired or wireless communication medium with one or more blood glucose monitoring devices. The connection may be established via a wired or a wireless communication link. The wireless communication link may be established using a defined RF communication spectrum and / or protocol, such as BLUETOOTH®, BLE, NFC, THREAD®, WIFI®,Matter No. P38818-WOZIGBEE®, WI-MAX®, or another RF communication protocol. The connection may be established and / or communications maybe performed according to one or more communication parameter sets that define parameters for performing communication, as described herein. The mobile device 104 may transmit and / or receive data via the one or more established connections for assisting in monitoring and / or treating the diabetic condition. The connection between devices may be initiated by the transmission and / or receipt of a connection request message from one of the devices via a communication medium. Another device may transmit a connection response message in response to the connection request message via the communication medium. The devices may detect that the connection has been established based on the exchange of the connection request / connection response messages and / or subsequent messages, such as acknowledgement messages, messages for establishing secure communications, or other subsequent messages (e.g, depending on the communication protocol).

[0039] The mobile device 104 may receive data from other devices and / or input from the user 100 via a user interface for being provided on a display. The mobile device 104 may receive input via hard buttons or soft buttons provided on the display. In response to the data that is received at the mobile device 104, the mobile device may provide output to the user 100 in the form of visual output on the display, audio output via a speaker, haptic feedback via vibrations, and / or other output to the user.

[0040] The mobile device 104 may be a connected smart device and / or may be in communication with other connected smart devices. Example connected smart devices may include a wearable device. The connected smart device may be an armband (e.g., a smart watch, such as an APPLE® watch, a FITBIT® armband, or other device capable of being worn on the arm of the user 100), a ring, glasses (e.g., GOOGLE® GLASS™), a headset (e.g., BLUETOOTH® headset), clothing (e.g., shirts, gloves, etc.), or another wearable device capable of being worn by the user 100. The connected smart device may be a wearable device or other device capable of monitoring the heart rate of the user 100, such as a heart rate monitor. The connected smart device may include a device capable of monitoring a wake / sleep state of the user, such as a wearable device, a heart rate monitor, a smart bed, or another device.

[0041] In one example, the mobile device 104 may provide data received from one or more medical monitoring devices to the remote computing device 122, via the network 120. The mobile device 104 may receive data from the remote computing device 122.Matter No. P38818-WO

[0042] The mobile device 104 may provide information to the user 100 about the user’s medical condition. For example, the mobile device 104 may provide blood glucose levels, meal- related information, exercise-related information, treatment notifications, and / or graphs and other graphical user interfaces, such as alerts or notifications, for display.

[0043] The mobile device 104 may communicate with other devices directly via a wired communication and / or a short-range wireless communication (e.g., WI-FI®, BLUETOOTH®, BLE, NFC, and / or another suitable short-range wireless communication). The mobile device 104 may communicate with remote computing device(s) 122 via a wired or wireless communication link. For example, the mobile device may communicate with the remote computing device(s) 122 on a communication link via a network 120 (e.g., using a WI-FI® network, a cellular network, a WI-MAX® network, or another wired or wireless network). The network 120 is a wired or wireless network. The network 120 is used to communicate over the Internet to other devices. The wired or wireless communication link with which the mobile device 104 communicates with the remote computing device(s) 122 may be different than the wired or wireless communication link with which the mobile device communicates with the one or more medical monitoring devices. For example, the communication links may include a different defined RF communication spectrum and / or protocol.

[0044] The mobile device 104 may communicate with the remote computing device(s) 122 to generate user interfaces for display on the mobile device 104, perform remote computation, send and / or receive data, or to otherwise control a remote computing device 122. For example, the mobile device 104 may provide a user interface via an application (e. ., a web browser or other local application) that is generated locally for providing access to locally stored data or data from a remote computing device 122. The mobile device 104 may also operate as an intervening communication device for data or control instructions transmitted between a medical monitoring device e.g., the pen device 103, CGM 102, BGM 106, FGM 111, and / or another medical monitoring device) and the remote computing device 122.

[0045] The mobile device 104 may communicate with one or more medical monitoring devices, such as the pen device 103, CGM 102, BGM 106, FGM 111, and / or another medical monitoring device in order to allow the user 100 to treat the medical condition. For example, the mobile device 104 may receive analyte levels (e.g., blood glucose levels and / or other analyte levels) and / or other data related to the medical condition of the user 100 from one orMatter No. P38818-WO more medical monitoring devices. The medical monitoring devices may provide data to the mobile device 104 in response to the analyte levels or other medical data reaching a predefined threshold or coming within a predefined level of a predefined threshold.

[0046] The mobile device 104 may provide notifications to the user 100 in response to the data that is collected from the medical monitoring devices and / or in response to an indication to notify the user 100 based on the data related to the medical condition. The mobile device 104 may provide notifications via one or more notification types. For example, the notifications may be provided via a visual notification on a graphical user interface displayed on the mobile device 104, a visual notification provided via a light emitting diode (LED), an audible notification provided via a speaker or other audio device on the mobile device 104, a tactile or vibratory notification on the mobile device 104, and / or another notification type provided via the mobile device 104 or another device in the user environment. The notifications may be provided to the user 100 via an application (e.g., a medical application, such as a diabetes-related application, an exercise-related application, a nutrition or mealtime-related application, another health-related application, or another type of application) residing locally thereon and / or via one or more remote computing devices 122. For example, one or more remote computing devices 122 may be implemented to execute the application for providing a graphical user interface with the notifications for providing the information related to the medical condition of the user 100 and / or treatment thereof.

[0047] The mobile device 104 may operate as a central medical monitoring device, as the mobile device 104 may be configured with applications and / or other software for managing the medical condition of the user, communicating with multiple devices for sending / receiving data for managing the medical condition, and / or performing other functionality central to the management of the medical condition of the user 100. The one or more medical monitoring devices may operate as peripheral devices or peripheral medical monitoring devices capable of connecting to the mobile device 104 for transmitting data and / or receiving instructions that may allow the user 100 to monitor and / or treat their medical condition. The mobile device 104 may receive data from the one or more peripheral medical monitoring devices for being displayed to the user 100 and / or for being communicated to the remote computing device 122. Peripheral devices may also, or alternatively, be referred to as slave devices.Matter No. P38818-WO

[0048] The mobile device 104 and the one or more peripheral medical monitoring devices may communicate with one another via the RF communications using a communication parameter set. For example, devices communicating via RF communication protocols that are used for RF communications, such as BLUETOOTH® or BLE, NFC, THREAD®, WIFI®, ZIGBEE®, WI-MAX®, a proprietary wireless communication protocol, or another RF communication protocol may utilize a communication parameter set for performing communications. The communication parameter set may include parameters, such as a connection interval or timeout, peripheral latency (e.g., slave latency), a supervision timeout, an advertisement interval, an advertisement count, an advertisement repetition time, and / or one or more other communication parameters. The connection interval or timeout may include an amount of time between two connection events. The connection interval or timeout may include a minimum connection interval or a maximum connection interval. The connection interval may range from a number of milliseconds to a number of seconds. A peripheral latency (e.g., slave latency) may allow a peripheral device, such as a peripheral medical device operating on battery power or in sleep / wake states, to skip waking up for a period of time (e.g., a number of connection events) when the peripheral device fails to have data to be transmitted. The supervision timeout may define the time for devices to wait for data transfer before assuming the connection was lost. The advertisement interval may be a period of time between advertisement packets, which may be sent periodically (e.g., on each advertising channel). The advertisement messages may be sent periodically as broadcast messages with identifying information from the broadcasting device. A minimum and / or maximum advertisement interval may be used to decide the interval. The advertisement count may identify a number of advertisement messages (e.g., including repetition messages) received from a device within a period of time, which may indicate the quality of the communications between the devices. An advertisement repetition time may include a period of time between advertisement messages, which may also indicate a quality of the communications between devices.

[0049] The parameters of the communication parameter set may be configured for improvement in communication quality (e.g., latency, communication success rate, and / or other communication quality parameters), efficient use of battery power (e.g., for devices operating in sleep / wake states, transmit power for communications, etc.), reduced memory and / or processing resources, and / or efficient use of other device resources. Different values of the parameters inMatter No. P38818-WO the communication parameter set may affect power consumption on a device, data transfer speeds between devices, and / or stability of a connection between devices.

[0050] FIG. IB shows an example representative system 101a, which may include a subset of the devices of the representative system 101 shown in FIG. 1A. As shown in FIG. IB, the mobile device 104 and a peripheral medical monitoring device 102a (e.g., pen device 103, CGM 102, BGM 106, FGM 111, and / or another medical monitoring device) may be configured with respective communication parameter sets 132a, 132b that are used by each of the devices when performing RF communications. The communication parameter sets 132a, 132b may have the same or overlapping parameter values for performing efficient communications. When the values of the parameters in the communication parameter sets 132a, 132b configured on each device are out of alignment, or are out of alignment by a larger margin, communications between the devices may degrade and / or resources on a given device may be inefficiently leveraged. As various mobile devices may be implemented as a central medical monitoring device for communicating with peripheral medical monitoring devices, different mobile devices may have different preferred communication parameter sets for communicating via the RF communications. The preferred communication parameter set used by the mobile device 104 may depend on the hardware and / or software installed on the mobile device 104. For example, the operating system version, vendor specific hardware and / or software constraints, and / or other hardware / software configurations may influence the values of the communication parameter set 132b that is stored on and implemented by the mobile device 104. In implementing short-range or low-power RF communications, such as BLE, NFC, or other short-range or low-power RF communications, the parameters in the communication parameter sets being used by devices for communication may need to be more precisely configured due to the low-power nature of the communications.

[0051] The variation in the preferred communication parameter sets amongst mobile devices may make it challenging for peripheral medical monitoring devices to determine an appropriate communication parameter set for being implemented thereon. Additionally, as the user 100 may select the mobile device 104 as a central device for operating software applications and interacting with various other peripheral devices, including peripheral medical monitoring devices via RF communications, the communication parameter set 132b configured on the mobile device 104 may take priority over the communication parameter set of other peripheralMatter No. P38818-WO devices, such as the communication parameter set 132a of the peripheral medical monitoring device 102a, in the communication setup. As such, the mobile device 104 may be preprogrammed with a preferred communication parameter set 132b, which may dictate the parameter set used by the peripheral medical monitoring device 102a and / or other peripheral devices. However, the peripheral medical monitoring device 102a may be configured to communicate with different mobile devices. As such, it may be challenging to pre-program the peripheral medical monitoring device 102a with a communication parameter set 132a that is compatible with each mobile device, or other central medical monitoring device, to enable efficient and robust RF communications between devices.

[0052] Additionally, the peripheral medical monitoring device 102a may be preprogrammed during development with the communication parameter set 132a for communicating via the RF communications with mobile devices. The pre-programmed communication parameter set 132a may become outdated as time goes on and performance criteria for the peripheral medical monitoring device 102a may be degraded and fail to meet a certain threshold. The outdated communication parameter set 132a may require updates for establishing updated communication parameter sets, such as by updating software / firmware on the peripheral medical monitoring devices, reprogramming software / firmware, and / or performing other updates anytime performance criteria (e.g., performance criteria related to hardware, software, and / or communication performance) is below the threshold. This may require relatively regular updating of the peripheral medical monitoring device 102a to maintain a certain level of quality in RF communications with mobile devices, or other central medical monitoring devices, particularly as additional devices continue to be manufactured for user consumption at such a high rate.

[0053] The communication parameter sets 132a, 132b may be directly negotiated between the mobile device 104, or another central medical monitoring device, and the peripheral medical monitoring device 102a. However, there may be a fixed number or subset of available communication parameter sets that may be implemented without updates and / or improvements over relatively shorter thresholds of time. For example, certain communication parameter sets may be required to be updated each time an updated operating system becomes available on the mobile device 104, or another central medical monitoring device, and / or the peripheral medical monitoring device. Due to potential hardware and / or software restrictions (e.g., powerMatter No. P38818-WO restrictions, memory restrictions, and / or processing restrictions) on some peripheral medical monitoring devices, the frequency of the updates may be difficult to manage. Additionally, the communication parameter set may not be determined by the peripheral medical monitoring device 102a or the mobile device 104 alone, but may be require testing and communication steps between the devices or with other devices to establish the communication parameter set. An optimum set or range of communication parameter sets may be identified through testing and stored as optimized communication parameter sets.

[0054] The peripheral medical device 102a may be measuring and transmitting vital medical data being used to monitor and manage a medical condition (e.g., diabetes) having extreme states (e.g., an extreme diabetic state, such as hypoglycemia or hyperglycemia). The peripheral medical device 102a may also, or alternatively, be administering forms of treatment to the user 100 for treating the medical condition in response to communications received from the mobile device 104, or another central control device. Thus, the communications between the peripheral medical device 102a and the mobile device 104, or other central control device, may affect the health of the user 100. As a result, reliable communication between the peripheral medical device 102a and the mobile device 104, or other central control device, is critical. For similar reasons, battery power and life expectancy thresholds of the peripheral medical device 102a are important considerations.

[0055] As illustrated in FIG. IB, the peripheral medical device 102a and / or the mobile device 104, or another central medical monitoring device, may be obtain and / or implement communication parameters from a remote computing device 122 that may improve the communications between the devices. The remote computing device 122 may comprise a communication parameter reconfiguration subsystem 135 that may be implemented to reconfigure or update one or more of the communication parameter sets 132a, 132b. The communication parameter reconfiguration subsystem 135 may have access to communication parameter sets 132c, which may include the communication parameter sets 132a, 132b and / or include one or more additional communication parameter sets. The communication parameter sets 132c may be stored in a library or datastore 124. The communication parameter reconfiguration subsystem 135 may be implemented as hardware, software, or a combination of both hardware and software. The communication parameter reconfiguration subsystem 135 may be implemented on a single device, such as the remote computing device 122, the mobile deviceMatter No. P38818-WO104, or the peripheral medical monitoring device 102a. In another example, the communication parameter reconfiguration subsystem 135 may be distributed across multiple devices. The communication parameter reconfiguration subsystem 135 may be implemented as computerexecutable instructions stored in memory on one or more computing devices for being executed to reconfigure communication parameter sets between devices.

[0056] FIG. 1C is a sequence flow diagram illustrating an example process 140 for updating one or more communication parameter sets at one or more devices in the system 101a. One or more portions of the process 140 may be implemented by one or more subsystems on one or more devices in the system. Each subsystem may include hardware and / or software for performing as described herein. For example, one or more portions of the process 140 may be performed by one or more the communication parameter reconfiguration subsystems 135 residing on one or more of the devices in the system 101a. One or more portions of the process 140 may be performed by client subsystems operating at a peripheral medical monitoring device 102a and / or a mobile device 104, or another central medical monitoring device. The client subsystem may include software, such as an application (e.g., a medical application, such as a diabetes-related application, an exercise-related application, a nutrition or mealtime-related application, another health-related application, or another type of application). Though the process 140 may illustrate a sequence of steps or events in a particular order, the sequence of steps or events may be performed in another order.

[0057] As shown in FIG. 1C, the mobile device 104 may collect system specification information, at 142, related to the peripheral medical monitoring device 102a and / or the mobile device 104 itself. The system specification information may be collected from the peripheral medical monitoring device 102a after connection to the peripheral medical monitoring device 102a has been established. The system specification information may include hardware specifications and / or software specifications related to the peripheral medical monitoring device 102a and / or the medical monitoring device 104. The system specification information may include a type of the peripheral medical monitoring device 102a (e.g., pen device 103, CGM 102, BGM 106, FGM 111, and / or another medical monitoring device). The system specification information may include a manufacturer and / or model of the peripheral medical monitoring device 102a. The system specification information may include a version of hardware and / or software installed on the peripheral medical monitoring device 102a. The system specificationMatter No. P38818-WO information may include a type of the mobile device 104 (e.g., cellular phone, tablet, laptop computer, wearable device, or another type of mobile device). The system specification information may include a manufacturer and / or model of the of the mobile device 104. The system specification information may include a version of hardware and / or software installed on the mobile device 104. The system specification information may include a version of a client application (e.g., a medical application, such as a diabetes-related application, an exercise-related application, a nutrition or mealtime-related application, another health-related application, or another type of application) and / or operating system installed on and / or operating on the peripheral medical monitoring device 102a and / or the mobile device 104.

[0058] At 144, the mobile device 104 may identify a triggering event for updating a communication parameter set related to the RF communications between the peripheral medical monitoring device and the mobile device 104. The triggering event may be detected in response to establishment of the RF communication between the peripheral medical monitoring device 102a and the mobile device 104. The triggering event may be detected in response to establishment of RF communication between the mobile device 104 and the remote computing device 122. The triggering event may be detected in response to an indication of completion of initialization of the peripheral medical monitoring device. The initialization may include an establishment of the of RF communication with initial (e.g., unoptimized) parameters at the mobile device 104 and / or the remote computing device 122, establishment of security levels at the mobile device 104 and / or the remote computing device 122, and / or a readiness to accept optimized communication parameters at the mobile device 104 and / or the remote computing device 122. The triggering event may be detected in response to an indication of receipt of a data (e.g., medical device data, such as analyte values) from the peripheral medical monitoring device 102a. The triggering event may be detected in response to an indication of an update to an operating system and / or other software applications on the mobile device 104 and / or the peripheral medical monitoring device 102a. The triggering event may be detected in response to an indication of an interruption to RF communication connectivity via the RF communication medium or a communication fault for a period of time. The triggering event may be detected in response to a threshold number of communication faults, such as lost connections, device connection / pairing failures, timeout failures, and / or other communication faults. The triggering event may be detected in response to an indication that a period of time has elapsed sinceMatter No. P38818-WO checking for an updated communication parameter set. The triggering event may be detected in response to a request from the peripheral medical monitoring device 102a and / or the remote computing device 122. Though the process 140 shows the mobile device 140 detecting a triggering event at 144 after collecting system specification information at 142, the mobile device 104 may collect the system specification information at 142 after detecting the triggering event at 144.

[0059] After detecting a triggering event at 144, the mobile device 104 may transmit a request at 146 to the remote computing device 122 for an updated communication parameter set related to the RF communications between the peripheral medical monitoring device 102a and the mobile device 104. For example, the mobile device 104 may establish a connection with the remote computing device 122 on a wired or wireless communication link. The mobile device 104 may attempt to contact an external application programming interface (API) of the remote computing device 122. The request at 146 may be sent via the API. The request may include at least a portion of the system specification information related to the peripheral medical monitoring device 102 and / or the mobile device 104. The request may be sent at 146 with authorization information (e.g., user and / or password information) and / or an API key for authorizing the mobile device 104 to access the communication parameter sets. The remote computing device 122 may be operating the communication parameter reconfiguration subsystem 135 and / or have access to (c. ., via a library or datastore) communication parameter sets for configuring communications between peripheral medical monitoring devices and mobile devices. The request at 146 may include system specification information limited to the mobile device 104, as the system specification information that is stored at the remote computing device 122 may include information related to mobile devices for known peripheral medical monitoring devices. In another example, the request at 146 may include system specification information limited to the peripheral medical monitoring device 102a, as the system specification information that is stored at the remote computing device 122 may include information related to peripheral medical monitoring devices for known mobile devices. However, as described herein, the request 146 may include system specification information for the peripheral medical monitoring device 102a and / or the mobile device 104. The request at 146 may include device and / or user specific information that may be used for authenticating and / or authorizing the access to the communication parameter sets.Matter No. P38818-WO

[0060] Prior to transmitting the request at 146, the mobile device 104 may check a local storage (e.g., memory) to identify whether a communication parameter set has been previously downloaded and / or shared with the peripheral medical monitoring device 102a. The mobile device 104 may check the local storage to identify whether the communication parameter set has been previously downloaded and / or shared (e.g, within a predefined period of time) with the peripheral medical monitoring device 102a to prevent a request from being transmitted and / or a response to be transmitted when the communication parameter set was previously downloaded and / or shared. This may reduce network communications and / or processing of messages when the communication parameter set was previously downloaded and / or shared.

[0061] If the mobile device 104 previously downloaded and / or shared an updated communication parameter set (c.g., within a predefined period of time), the mobile device 104 may fail to send the request at 146. Failing to send the request at 146 may reduce network communications. If the mobile device 104 has not downloaded and / or shared the updated communication parameter set (c.g., within a predefined period of time), the mobile device 104 may collect the system specification information and / or send the request at 146. In one example, the predefined period of time for enabling download and / or sharing of the communication parameter set may enable load balancing at the remote computing device 122 for requests from several devices within a period of time.

[0062] The remote computing device 122 may receive the request at 146 with authorization information and / or an API key and confirm the authorization information and / or API key for accessing the updated communication parameter sets. At 148, the remote computing device 122 may identify a compatible communication parameter set. The compatibility may be determined based on the at least one portion of the system specification information related to the peripheral medical monitoring device 102 and / or the mobile device 104. The remote computing device 122 may determine the level of compatibility (e.g., in terms of percentage and / or amount of compatible system specification information) for a communication parameter set based on the received system specification information. A threshold level of compatibility may be determined by a threshold amount of information in the received system specification information being matched with the system specification stored with the corresponding communication parameter set e.g., 100%, 80%, 70%, etc. agreement in system specification information) or agreement between a threshold number of prioritized or required parameters inMatter No. P38818-WO the system specification information. For example, the system specification information that is received at the remote computing device 122 may include the same device type, model, and / or application version of the mobile device 104 that is stored for a communication parameter set, but not the same operating system for the mobile device 104. This threshold level of information being met may still indicate a qualified level of compatibility that may result in an improvement over a prior or default communication parameter set.

[0063] The communication parameter reconfiguration subsystem 135 at the remote computing device 122 may identify the compatible set of communication parameters. The remote computing device 122 may transmit the compatible set of communication parameters at 150 to the mobile device 104. The mobile device 104 may transmit the compatible set of communication parameters to the peripheral medical monitoring device 102. The message transmitted at 150 may indicate that the updated communication parameter set corresponding to at least the portion of the system specification information related to the peripheral medical monitoring device 102a and / or the mobile device 104 comprises at least the threshold level of compatibility. The message transmitted at 150 may indicate that there is at least the threshold level of the system specification information that matches the corresponding system specification information for the updated communication parameter set for improving hardware, software, and / or communication performance by at least a threshold. The message 150 may include an explicit value indicating a level of compatibility, or the receipt of the message 150 may implicitly indicate the level of compatibility has been evaluated by the remote computing device 122.

[0064] The remote computing device 122 may have stored thereon information that is used to determine a level of compatibility of the communication parameter sets with different peripheral medical monitoring devices and / or mobile devices. For example, the compatibility of the parameters in the communication parameter sets may be tested and validated and system specification information for compatible peripheral medical monitoring devices and mobile devices, or other central medical monitoring devices, may be stored with the communication parameter sets. As these communication parameter sets may be tested and validated using device hardware and / or software without being downloaded to the actual peripheral medical monitoring device 102 and / or the mobile device 104, the updated communication parameter sets may be established without interfering with device communications during use for monitoringMatter No. P38818-WO the medical conditions of the user. The communication parameter sets may be updated for upgrading communication parameters without having to download a new software application or firmware for monitoring the medical condition of the user. For example, as mobile devices, or other medical monitoring devices, have hardware (e.g., manufacturers and / or models) and / or firmware / software (e. ., applications and / or operating systems) that is released, testing of the hardware and / or firmware / software with the spectrum of peripheral medical monitoring device firmware / software versions available can be undertaken to identify the communication parameter sets to be uploaded to the respective library or datastore at the remote computing device 122. The communication parameters may be updated dynamically during the runtime.Deprecation / deletion of older parameter sets can also be performed when communication parameter sets are no longer applicable to device combinations.

[0065] The updated communication parameter set may include updated values of one or more parameters, which may affect power consumption on the peripheral medical monitoring device 102a and / or the mobile device 104, a data transfer speed between the peripheral medical monitoring device 102a and the mobile device 104, and / or a stability of connection between the peripheral medical monitoring device 102a and the mobile device 104. The mobile device 104 may reconfigure the communication parameter set at 154 based on the updated communication parameter set received at 150. The peripheral medical monitoring device 102a may reconfigure the communication parameter set at 156 based on the updated communication parameter set received at 152. The peripheral medical monitoring device 102a and / or the mobile device 104 may use the updated communication parameter set for communications. The updated communication parameter set may comprise one of an updated connection interval or timeout, an updated minimum connection interval, an updated maximum connection interval, an updated peripheral latency, an updated supervision timeout, an updated advertisement interval, an updated advertisement count, an updated advertisement repetition time, and / or another updated communication parameter. The updated parameters of the communication parameter set may be configured for improvement in communication quality (e.g., latency, communication success rate, and / or other communication quality parameters), efficient use of battery power (e.g., for devices operating in sleep / wake states, transmit power for communications, etc.), and / or efficient use of other device resources. In another example, if the mobile device 104 determines that a received updated communication parameter set includes the same parameter values as a priorMatter No. P38818-WO communication parameter set sent to the peripheral medical monitoring device 102a, the mobile device 104 may prevent the received communication parameter sets from being downloaded and / or shared with the peripheral medical monitoring device 102a.

[0066] The communication parameter sets stored at the remote computing device 122 may be updated in response to communication parameter sets for new peripheral medical monitoring device types and / or models that were not previously stored at the remote computing device 122. The communication parameter sets stored at the remote computing device 122 may be updated in response to communication parameter sets for new types and / or models mobile devices, or other central medical monitoring devices, that were not previously stored at the remote computing device 122. The communication parameter sets stored at the remote computing device 122 may be updated to include parameters that have been tested and validated for improving hardware, software, and / or communication performance at types and / or models of peripheral medical monitoring devices and / or mobile devices, or other central medical monitoring devices. The updated parameters may be tested and validated for improving specific parameters in the parameter set, such as the connection interval or timeout, the peripheral latency (e.g., slave latency), the supervision timeout, the advertisement interval, the advertisement count, the advertisement repetition time, and / or another communication parameter. The updated parameters may be configured for improvement in communication quality (e.g., latency, communication success rate, and / or other communication quality parameters), efficient use of battery power (e.g, for devices operating in sleep / wake states, transmit power for communications, etc.), and / or efficient use of other device resources at types and / or models of peripheral medical monitoring devices and / or mobile devices, or other central medical monitoring devices.

[0067] In response to transmitting the request at 146, the mobile device 104 may receive a response that indicates that the updated communication parameter set is unavailable at the communication parameter reconfiguration subsystem 135 at the remote computing device 122 for at least the portion of the system specification information related to the peripheral medical monitoring device and / or the mobile device 104, or at least a threshold portion of the system specification information (e.g., to allow for compatibility). The request at 146 may include information indicating one or more of the current parameters operating at the mobile device 104 and / or the peripheral medical monitoring device 102a. For example, each communicationMatter No. P38818-WO parameter set may include a unique identifier that may be used for identifying the values of the parameters in the parameter set, and / or each parameter may have a unique identifier that may be communicated along with the value of the parameter in the parameter set. The communication parameter sets stored at the remote computing device 122 may also each include a respective unique identifier that may be used for identifying the values of the parameters in the parameter set, and / or each parameter in a communication parameter set may have a unique identifier that may be communicated along with the value of the parameter in the parameter set. The communication parameter reconfiguration subsystem 135 at the remote computing device 122 may determine from the system specification information and / or known information about the communication parameter sets currently operating at the peripheral device 102a and / or the mobile device 104 that there are no updated communication parameter sets for the devices. The remote computing device 122 may not have a compatible communication parameter set stored for one or more of the devices, or the devices may be operating on the most up-to-date communication parameter set.

[0068] If the mobile device 104 receives a response that indicates there are no updated communication parameter sets at the remote computing device 122, the mobile device 104 may allow the devices to continue operating on current communication parameter sets or the mobile device 104 may transmit a default communication parameter set to the peripheral medical monitoring device 102. The default communication parameter set may be a communication parameter set stored at the mobile device 104 that is compatible with multiple types of peripheral medical monitoring devices and multiple types of mobile devices, or other central medical monitoring devices. The default communication parameter set may be received from the remote computing device 122 in response to the request 146, or may already be pre-stored at the mobile device 104 and / or the peripheral medical monitoring device 102a for being utilized.

[0069] The mobile device 104 may receive notifications from the remote computing device 122 that updated communication parameter sets are available at the remote computing device 122. For example, after sending a request 146 and receiving a response that the remote computing device 122 fails to have an updated communication parameter set available based on the system specification information related to the peripheral medical monitoring device and / or the mobile device, the remote computing device 122 may store the system specificationMatter No. P38818-WO information and send a notification to the mobile device when there is an updated communication parameter set available for the corresponding system specification information.

[0070] The peripheral medical monitoring device 102a and / or the mobile device 104 may perform a local evaluation of whether to use the updated communication parameter set that is received. For example, the peripheral medical monitoring device 102a and / or the medical monitoring device 102a may compare the parameter values in the currently stored communication parameter set and / or predefined criteria for one or more parameters. For example, the peripheral medical monitoring device 102a and / or the medical monitoring device 102a may have predefined criteria for operating values for one or more parameters, such as the connection interval or timeout, the peripheral latency (e.g., slave latency), the supervision timeout, the advertisement interval, the advertisement count, the advertisement repetition time, and / or one or more other communication parameters. The peripheral medical monitoring device 102a and / or the mobile device 104 may reject the use of the updated communication parameter set and revert back to a prior communication parameter set or a default communication parameter set. If the mobile device 104 rejects the updated communication parameter set, the mobile device 104 may fail to send the updated communication parameter set to the peripheral medical monitoring device 102a. If the updated communication parameter set is already sent at 152, a subsequent message may be sent to the peripheral medical monitoring device 102a to indicate to revert to another communication parameter set. If the updated communication parameter set is rejected by the peripheral medical monitoring device 102a, the peripheral medical monitoring device 102a may send a message to the mobile device 104 and each device may revert to another communication parameter set.

[0071] Prior to transmitting the request at 146 for the updated communication parameter set, the mobile device 104 may determine that it is unable to communicate with the remote computing device 122. If the mobile device 104 is unable to communicate with the remote computing device 122 for obtaining updated communication parameters, the mobile device 104 may utilize a condensed updated communication parameter set stored locally at the mobile device 104. The condensed updated communication parameter set may be used for updating the communication parameters at the peripheral medical monitoring device 102a. The condensed updated communication parameter set may include less parameters than the updated communication parameter set. For example, the condensed updated communication parameterMatter No. P38818-WO set may include a subset of one or more of an updated connection interval or timeout, an updated minimum connection interval, an updated maximum connection interval, an updated peripheral latency, an updated supervision timeout, an updated advertisement interval, an updated advertisement count, an updated advertisement repetition time, and / or another updated communication parameter. The updated condensed communication parameter set may be compatible with one or more devices than the full updated communication parameter set (e.g, certain higher-level hardware and / or software, such as models or operating systems). The condensed communication parameter set may still be an improvement over a default communication parameter set. For example, the condensed communication parameter set may be configured for improvement in communication quality (e.g, latency, communication success rate, and / or other communication quality parameters), efficient use of battery power (e.g, for devices operating in sleep / wake states, transmit power for communications, e.tc and / or efficient use of other device resources. However, the condensed communication parameter set may provide a first level improvement in quality and / or quantity of improvements, while the full updated communication parameter set may provide a second level improvement in terms of quality and / or quantity of improvements. During development of firmware and / or software for different types of devices, different communication parameter sets may be created that may be used as condensed communication parameter sets for devices having specific corresponding hardware and / or software.

[0072] FIG. 2 is a sequence flow diagram illustrating an example process 200 for updating one or more communication parameter sets at one or more devices in a system. One or more portions of the process may be implemented by a central medical monitoring device 104a and / or a remote computing device 122a. An example central medical monitoring device 104a may include a mobile device, but other types of central medical monitoring devices may be implemented. The central medical monitoring device 104a may implement a client subsystem for sending requests for updated communication parameter sets and / or receiving responses to the requests. The client subsystem may include software and / or hardware operating on the central medical monitoring device 104a. The software may include an application (e.g, a medical application, such as a diabetes-related application, an exercise-related application, a nutrition or mealtime-related application, another health-related application, or another type of application). The client subsystem may include a portion of communication parameter reconfigurationMatter No. P38818-WO subsystem or may be a separate subsystem. The remote computing device 122a may include a communication parameter reconfiguration subsystem 135a for receiving requests for updated communication parameter sets and determining proper responses. The communication parameter reconfiguration subsystem 135a may include software and / or hardware operating on the remote computing device 122a. The communication parameter reconfiguration subsystem 135a may have access to communication parameter sets, which may be stored in a library or datastore. The central medical monitoring device 104a and / or the remote computing device 122a may have stored thereon in memory computer-executable instructions for implementing one or more portions of the process 200. Though the process 200 may illustrate a sequence of steps or events in a particular order, the sequence of steps or events may be performed in another order.

[0073] As shown in FIG. 2, the central medical monitoring device 104a may initiate the process 200 at 202. At 204, the central medical monitoring device 104a may send a request for an updated communication parameter set. The request may be sent in response to a triggering event. The request may include system specification information related to a peripheral medical monitoring device with which the central medical monitoring device 104a may be in communication and / or the central device 104 itself. The system specification information may include hardware specifications and / or software specifications related to the peripheral medical monitoring device and / or the medical monitoring device 104a. The system specification information may include a type, a manufacturer, and / or a model of the peripheral medical monitoring device. The system specification information may include a type, a manufacturer, and / or a model of the of the central medical monitoring device 104a. The system specification information may include a version of hardware and / or software installed on the peripheral medical monitoring device and / or the central medical monitoring device 104a.

[0074] As shown in FIG. 2, the remote computing device 122a may receive the request comprising the system specification information related to the peripheral medical monitoring device and / or the central medical monitoring device 104a at 206. At 208, the communication parameter reconfiguration subsystem 135a operating at the remote computing device 122a may check the system specification information related to the peripheral medical monitoring device and / or the central medical monitoring device 104a against the corresponding system specification information for the communication parameter sets with which it has access. For example, the communication parameter sets may be stored in a library or datastore withMatter No. P38818-WO corresponding system specification information. If the communication parameter reconfiguration subsystem 135a finds an updated communication parameter set that corresponds to the system specification information, or at least a threshold amount of the system specification information, related to the peripheral medical monitoring device and / or the central medical monitoring device 104a at 210, the communication parameter reconfiguration subsystem 135a may send the updated communication parameter set to the central medical monitoring device 104a at 214.

[0075] If the communication parameter reconfiguration subsystem 135a fails to find a matching communication parameter set that is compatible with the corresponding system specification information at 210, the communication parameter reconfiguration subsystem 135a may send a response code at 212 to the central medical monitoring device 104a with an indication that an updated communication parameter set failed to be identified for the corresponding system specification information. The response code may indicate for the central medical monitoring device 104a and / or the peripheral medical monitoring device with which it is communicating to revert to using a prior or default communication parameter set (e.g., until a compatible updating communication parameter set is available). The communication parameter reconfiguration subsystem 135a operating at the remote computing device 122a may store an indication of a failed request by the specific central medical monitoring device 104a. The indication may be stored with a unique identifier of the central medical monitoring device 104a and / or the peripheral medical monitoring device. The indication may be stored with the system specification information of the of the central medical monitoring device 104a and / or the peripheral medical monitoring device (e.g., including an identifier of one or more subsystems operating thereon). When a compatible updated communication parameter set is available, the communication parameter reconfiguration subsystem 135a operating at the remote computing device 122a may send a notification to the central medical monitoring device 104a that the updated communication parameter set is available and initiate a request for the updated communication parameter set, or push the updated communication parameter set to the central medical monitoring device 104a. In another example, if an exact match of each of the communication parameters in a communication parameter set fails to be found for the received system specification information, the communication parameter reconfiguration subsystem 135a may detect an agreement of a threshold level of compatibility based on the received systemMatter No. P38818-WO specification information. The communication parameter reconfiguration subsystem 135a may identify a threshold amount of system configuration information matches the stored system configuration information for a corresponding communication parameter set (e.g., 100%, 80%, 70%, etc. agreement in system specification information) or agreement between a threshold number of prioritized or required parameters in the system specification information. For example, the system specification information that is received at the remote computing device 122a may include the same device type, model, and / or application version of the central medical monitoring device 104a that is stored for a communication parameter set, but not the same operating system for the central medical monitoring device 104a. This threshold level of information being met may still indicate a qualified level of compatibility that may result in an improvement over a prior or default communication parameter set.

[0076] At 216, the remote computing device 122a may send an error response. The error response may be sent after a timeout period without identifying an updated communication parameter set, an acceptable updated communication parameter set suitable for the hardware and / or software / firmware of the peripheral medical monitoring device and / or the central medical monitoring device 104a, the central medical monitoring device 104a and / or the peripheral medical monitoring device is currently downloading an updated communication parameter set, and / or a predefined period of time has not expired since the central medical monitoring device 104a previously received an updated communication parameter set. The central medical monitoring device 104a may receive the response at 218 from the remote computing device 122a. When the response includes an updated communication parameter set, the updated communication parameter set may be sent to the peripheral medical monitoring device. The process 200 may finish at 220.

[0077] The communication parameter sets may be adjusted one or more times during the lifetime of the peripheral medical monitoring device and / or the central medical monitoring device 104a. For example, whenever a triggering event is detected, a request for an updated communication parameter set may be sent to the remote computing device 122a. The triggering event may include an establishment of connection between devices, an update to an operating system or other software / firmware on a device, identification of a threshold number of communication faults between the devices, receipt of data, an expiration of a period of time, aMatter No. P38818-WO request to update the communication parameter set, initialization of one or more devices, and / or other triggering events, as described herein.

[0078] When a communication parameter set is being used by a peripheral medical monitoring device and a central medical monitoring device and there is at least a threshold number of communication faults that are identified has having occurred (e.g., lost connections, device connection / pairing failures, timeout failures, and / or other communication faults), the communication faults may be tracked by one or more devices. For example, the central medical monitoring device, and / or the remote computing device (e.g., at the communication parameter reconfiguration subsystem) may be alerted of the communication faults and store an indication of the communication faults for a given communication parameter set and the corresponding system specification information in memory. When the communication faults reach a threshold, remote computing device (e.g., at the communication parameter reconfiguration subsystem) may flag the communication parameter set for being assessed with the devices identified in the system specification information. The combination of peripheral medical monitoring device and the hardware / software of the medical monitoring device may be further tested, and the communication parameter set may be validated or discarded for the given devices. Another communication parameter set may be stored for the identified system specification information that may resolve the prior communication faults.

[0079] Various forms of wireless communication are described herein for which communication parameter sets may be utilized and / or updated. Different forms of wireless communication may be implemented using wireless spectrum and / or protocols defined by different wireless communication types and / or standards. In one example, a central medical monitoring device may establish a BLUETOOTH® or BLE connection for performing communications with one or more peripheral devices, such as a peripheral medical monitoring device. The BLUETOOTH® or BLE connection may utilize the 2.4GHz unlicensed ISM frequency band. Though the central medical monitoring device may establish a BLUETOOTH® or BLE connection with multiple peripheral devices, each peripheral device may establish a dedicated connection with a single central device at a time.

[0080] FIGs. 3A and 3B show sequence flow diagrams for example processes 300, 350, respectively, for establishing a dedicated connection between a peripheral medical monitoring device 102b and a central medical monitoring device 104b and enabling updates ofMatter No. P38818-WO communication parameter sets for performing communications therebetween. One or more portions of the processes 300, 350 may be implemented by one or more subsystems, such as a client subsystem and / or a communication parameter reconfiguration subsystems, operating on one or more devices in the system. Each subsystem may include hardware and / or software for performing as described herein. Each subsystem may be implemented as computer-executable instructions stored in memory on one or more computing devices for being executed to establish a connection and reconfigure communication parameter sets between devices. Though the processes 300, 350 may each illustrate a sequence of steps or events in a particular order, the sequence of steps or events may be performed in another order.

[0081] As shown in FIG. 3 A, when a peripheral medical monitoring device 102b that wants to assume the peripheral role and is ready to connect to a central medical monitoring device 104b, the peripheral medical monitoring device 102b may enter an advertising state at 301 and begin broadcasting advertising messages at 302a, 302b on one or more advertising channels. The advertising state may be entered in response to input (e.g, a button press) from a user or receipt of a message from another device. The central medical monitoring device 104b may assume the role as the central device by entering a scanning state at 304 and listening on the advertising channels for advertising messages. The scanning state may be entered in response to input (e.g, a button press) from a user or receipt of a message from another device. When the scanning state of the central medical monitoring device 104b coincides with the advertising by the peripheral medical monitoring device 102b on the advertising channels, the central medical monitoring device 104b may discover the peripheral medical monitoring device 102b. When an advertising message (e.g, advertising message 302b) is detected by the central medical monitoring device 104b, the central medical monitoring device 104b may initiate a connection to the peripheral medical monitoring device 102b by sending a connection request packet at 306. The connection request message 306 may include an initial communication parameter set that includes the parameters for communicating between the peripheral medical monitoring device 102b and the central medical monitoring device 104b. The central medical monitoring device 104b may be in charge of managing the connection and may establish preferred communication parameters in the initial communication parameter set. Though the advertising state is described as being entered into at the peripheral medical monitoring device 102b and the scanning state is described as being entered into at the central medical monitoring device 104b, either or bothMatter No. P38818-WO devices may enter either state for discovering one another and / or establishing the connection. For example, the peripheral medical monitoring device 102b and the central medical monitoring device 104b may each enter into advertising and scanning states, such that the peripheral medical monitoring device 102b and the central medical monitoring device 104b may find each other and process requests comprising additional information for pairing and establishing a communication parameter set. Once initialization and / or pairing has completed, the peripheral medical monitoring device 102b and the central medical monitoring device 104b may form a connection may be established and a bond may be created, such that the information from the pairing process is stored on the devices so that the pairing process does not have to be repeated each time the devices connect or reconnect.

[0082] A connection may be established between the peripheral medical monitoring device 102b and the central medical monitoring device 104b at 308 that uses the communication parameters in the communication parameter set. The peripheral medical monitoring device 102b and the central medical monitoring device 104b may communicate data packets via the connection. The connection at 308 may be a link layer connection establishment, for example. The link layer may be directly above the BLUETOOTH® or BLE physical layer on which communications may be performed.

[0083] FIG. 3B shows a sequence flow diagram for an example process 350 for enabling updates of the communication parameter set for performing communications between the peripheral medical monitoring device 102b and the central medical monitoring device 104b. As shown in FIG. 3B, the connection may be established on the link layer at 308. The peripheral medical monitoring device 102b may be capable of communicating on the link layer via a link layer peripheral entity 356 (or link layer slave entity). The central medical monitoring device 104b may be capable of communicating on the link layer via a link layer master entity 352. The link layer master entity 352 and the link layer peripheral entity 356 may each comprise a link layer state machine configured to enter different states. The different states may include a scanning or advertising state, a standby state, and / or a connected state. The peripheral medical monitoring device 102b may enter the advertising state to transmit advertising messages. The central medical monitoring device 104b may enter the scanning state to scan advertising frequencies for identifying advertising messages. Upon establishing the connection between the two devices at 308, each device may enter the connected state.Matter No. P38818-WO

[0084] The peripheral medical monitoring device 102b and the central medical monitoring device 104b may include other layers in the protocol stack for initiating transmission of and / or receiving information. For example, each device may include a Generic Attribute Profde (GATT) layer. The GATT layer may sit above the link layer and below the application layer. The GATT layer may establish and govern how to exchange data over the BLUETOOTH® or BLE connection. The GATT layer entities, Logical Link Control and Adaptation Protocol (L2CAP) entities, and / or link layer entities may use the communication parameters in the configured communication parameter set to transmit messages via the connection. The central medical monitoring device 104b may include a GATT client 354. The GATT client 354 may be an entity that may be used by a client subsystem or client application (e.g., a medical application, such as a diabetes-related application, an exercise-related application, a nutrition or mealtime-related application, another health-related application, or another type of application) operating at the central medical monitoring device 104b to send and / or receive data over the established connection. The peripheral medical monitoring device 102b may include a GATT server 358. The GATT server 358 may be an entity that may be used by a client subsystem or client application operating at the peripheral medical monitoring device 102b to send and / or receive data over the established connection. The GATT server 358 may store data locally and provides data access methods to the GATT client 354 paired via the established connection. The GATT client 354 may access data on the GATT server 358, paired via the established connection, using defined operations, such as read, write, notify, and / or indicate operations.

[0085] The GATT layer entities may implement services that enable the control of the communication parameters of the peripheral medical monitoring device 102b. For example, the GATT layer entities may implement a reconnection configuration service to enable the control of the communication parameters at the peripheral medical monitoring device 102b. The GATT client 354 may send a write reconnection configuration control point (RCCP) message 310 to execute a supported procedure on the GATT server 358 for updating the communication parameter set at the peripheral medical monitoring device. The write RCCP message 310 may include the updated communication parameter set for performing communications on the established connection. The write RCCP message 310 may be transmitted via the link layer (e.g., using the link layer mater entity 352 and the link layer peripheral entity 356) to the GATTMatter No. P38818-WO server 358 at the peripheral medical monitoring device 102b. The write RCCP message 310 with the updated communication parameter set may operate as a proposal to the peripheral medical monitoring device 102b for updating the communication parameter set for communications performed via the established connection.

[0086] In response to receiving the write RCCP message 310, the GATT server 358 may send an RCCP indication proposal accepted message 312 when the proposed communication parameter set is accepted. The indication proposal accepted message 312 may be transmitted via the link layer (e.g., using the link layer mater entity 352 and the link layer peripheral entity 356) to the GATT client 354 at the central medical monitoring device 104b. The indication proposal accepted message 312 may inform the central medical monitoring device 104b to use the proposed updated communication parameters for communications going forward. The GATT server 358 may send a connection update message 314 with one or more updated communication parameters to the link layer peripheral entity 356 for using during link layer communications. The link layer master entity 352 at the central medical monitoring device 104b and / or the link layer peripheral entity 356 at the peripheral medical monitoring device 102b may update one or more of the communication parameters from the communication parameter set at 316 for performing link layer communications. The GATT server 358 may indicate the RCCP with the client parameter indication message 318. A client parameter indication message may be sent from the GATT server 358 each time the reconnection configuration sets or updates the communication parameters in the communication parameter set. The client parameter indication message 318 may be transmitted via the link layer (e.g., using the link layer mater entity 352 and the link layer peripheral entity 356) to the GATT client 354 at the central medical monitoring device 104b.

[0087] Though the process 350 illustrates the peripheral medical monitoring device 102b accepting the proposed updated communication parameters, the peripheral medical monitoring device 102b may reject the proposed updated communication parameters in the proposed communication parameter set. In that case, the GATT server 358 may send an indication proposal reject message in response to the write RCCP message 310 via the link layer. In order to accept or reject the proposed updated communication parameters in the communication parameter set, the GATT server 358 at the peripheral medical monitoring device 102b may look at predefined parameters to determine whether the proposed updated communication parametersMatter No. P38818-WO fall within the predefined parameters stored thereon. For example, the GATT server 358 at the peripheral medical monitoring device 102b may determine that the proposed communication parameters have timing or periods of time that are less than predefined thresholds established to allow the peripheral medical monitoring device 102b to properly process or respond to messages. The GATT server 358 at the peripheral medical monitoring device 102b may determine that the proposed communication parameters require more battery power, greater processing power, and / or greater memory than may be defined by predefined thresholds. The GATT server 358 at the peripheral medical monitoring device 102b may also, or alternatively, determine whether the proposed updated communication parameters improve communication, memory, processing, and / or other functionality at the peripheral medical monitoring device 102b when compared to prior or default communication parameters. For example, the GATT server 358 at the peripheral medical monitoring device 102b may determine whether the proposed communication parameters will reduce latency on communications, improve communication timing, use less memory, and / or improve other device functionality, as described herein. If the proposed communication parameters are rejected by the peripheral medical monitoring device 102b, the peripheral medical monitoring device 102b may send a rejection message and the devices may revert to prior or default communication parameter sets, as described herein.

[0088] FIG. 4 shows a flowchart of an example process 400 for updating a communication parameter set for performing communications between a central medical monitoring device and a peripheral medical monitoring device. One or more portions of the process 400 may be performed by one or more computing devices. For example, the one or more portions of the process 400 may be performed by one or more mobile devices, one or peripheral medical monitoring devices, one or more remote computing devices, and / or one or more other computing devices. One or more portions of the process 400 may be performed locally on a mobile device, or another central medical monitoring device, operating one or more client subsystems (e.g., including client applications, such as a diabetes-related application, an exercise-related application, a nutrition or mealtime-related application, another health-related application, or another type of application) and / or a communication parameter reconfiguration subsystem. One or more portions of the process 400 may be stored in memory as computer- readable or machine-readable instructions that may be executed by a processor of the one or more computing devices. Though portions of the process 400 may be described herein as beingMatter No. P38818-WO performed by a particular computing device, the process 400 may be performed by another computing device or distributed across multiple computing devices, such as one or more mobile devices, remote computing devices, peripheral medical monitoring devices, and / or one or more other devices.

[0089] As shown in FIG. 4, a triggering event may be identified at 402 for updating a communication parameter set that is used for performing RF communications with a peripheral medical monitoring device. For example, a central medical monitoring device, such as a mobile device, may communicate with the peripheral medical monitoring device via RF communication protocols that are used for RF communications, such as BLUETOOTH® or BLUETOOTH® low energy (BLE), near field communication (NFC), THREAD®, WIFI®, ZIGBEE®, WIMAX®, a proprietary wireless communication protocol, or another RF communication protocol may utilize a communication parameter set for performing communications. The communication parameter set may include parameters, such as a connection interval or timeout, peripheral latency (e.g, slave latency), a supervision timeout, an advertisement interval, an advertisement count, an advertisement repetition time, and / or one or more other communication parameters.

[0090] System specification information may be collected at 404 that is related to the peripheral medical monitoring device and / or the central medical monitoring device. The system specification information may include at least one of hardware specifications or software specifications related to the peripheral medical monitoring device and / or the central medical monitoring device. The system specification information may include a type, a manufacturer, and / or a model of the peripheral medical monitoring device. The system specification information may include a type, a manufacturer, and / or a model of the of the central medical monitoring device. The system specification information may include a version of hardware and / or software installed on the peripheral medical monitoring device and / or the central medical monitoring device. The system specification information may be collected in response to the triggering event, or may be collected prior to the triggering event.

[0091] At 406, a request for the updated communication parameter set related to the RF communications between the peripheral medical monitoring device and the central medical monitoring device may be transmitted a remote computing device (e.g, and / or a communication reconfiguration subsystem thereon). The request may comprise at least a portion of the systemMatter No. P38818-WO specification information related to the peripheral medical monitoring device and / or the central medical monitoring device. At 408, if there is an updated communication parameter set available that correspond to the system specification information, or at least mee a threshold level of compatibility for the system specification information, the updated communication parameter set may be received at 410. The updated communication parameter set may be determined to be compatible with at least a portion of the system specification information in the received request. For example, the system specification information that is transmitted in the request may include a percentage or predefined number of the same parameters that are stored in a library or datastore of potential updated communication parameter sets. The updated communication parameter set being received may indicate that at least the threshold amount of the system specification information was met for compatibility. The updated communication parameter set may be configured to affect power consumption on the peripheral medical monitoring device and / or the central medical monitoring device, a data transfer speed between the peripheral medical monitoring device and the central medical monitoring device, or a stability of connection between the peripheral medical monitoring device and the central medical monitoring device. The updated communication parameter set may be transmitted to the peripheral medical monitoring device at 412 to configure the peripheral medical monitoring device for communication with the central medical monitoring device using the updated communication parameter set.

[0092] If an updated communication parameter set is unavailable at 408, an indication may be received at 414 that the communication parameter set is unavailable that corresponds to the system configuration information, or at least a threshold amount of the system configuration information. A subsequent notification may be received when an updated communication parameter set is available that corresponds to the system configuration information, or at least a threshold amount of the system configuration information.

[0093] FIG. 5 shows a flowchart of an example process for determining an updated communication parameter set for performing communications between a central medical monitoring device and a peripheral medical monitoring device. One or more portions of the process 500 may be performed by one or more computing devices. For example, the one or more portions of the process 500 may be performed by one or more remote computing devices and / or one or more other computing devices. One or more portions of the process 500 may beMatter No. P38818-WO performed at a remote computing device operating one or communication parameter reconfiguration subsystems. One or more portions of the process 500 may be stored in memory as computer-readable or machine-readable instructions that may be executed by a processor of the one or more computing devices. Though portions of the process 500 may be described herein as being performed by a particular computing device, the process 500 may be performed by another computing device or distributed across multiple computing devices.

[0094] As shown in FIG. 5, a request for an updated communication parameter set may be received at 502. For example, the request may be received from a central medical monitoring device for an updated communication parameter set for communicating with a peripheral medical monitoring device. The request may include system specification information related to the peripheral medical monitoring device and / or the central medical monitoring device. The system specification information may include at least one of hardware specifications or software specifications related to the peripheral medical monitoring device and / or the central medical monitoring device.

[0095] The availability of a compatible updated communication parameter set may be determined at 504. For example, one or more portions of the system specification information may be evaluated against system specification information stored in memory with each of the potential updated communication parameter sets. A determination may be made at 506 as to whether there is an available updated communication parameter set that correspond to the system specification information, or at least meets a threshold level of compatibility for the system specification information. If there is an available updated communication parameter set that correspond to the system specification information, or at least meets a threshold level of compatibility for the system specification information, the updated communication parameter set may be transmitted at 508 to the central medical monitoring device.

[0096] If an updated communication parameter set is unavailable at 506, an indication may be transmitted at 512 to the central medical monitoring device that the communication parameter set is unavailable that corresponds to the system configuration information, or at least a threshold amount of the system configuration information. A subsequent notification may be transmitted to the central medical monitoring device when an updated communication parameter set is available that corresponds to the system configuration information, or at least a threshold amount of the system configuration information.Matter No. P38818-WO

[0097] FIG. 6 is a block diagram of an example computing device 600. The computing device 600 may be a mobile computing device, such as a tablet, a cellular phone, a wearable device, a medical monitoring device, such as an analyte monitoring device, a remote computing device, or another computing device, for example. As shown in FIG. 6, the computing device 600 may include a processor 602 for controlling the functionality of the computing device 600. The processor 602 may include one or more circuits, such as general-purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application specific integrated circuits (ASICs), or the like. The processor 602 may perform signal coding, data processing, power control, image processing, input / output processing, or any other functionality that enables the computing device 600 to perform as described herein.

[0098] The processor 602 may store information in or retrieves information from the memory 616. The memory 616 includes a non-removable memory or a removable memory. The non-removable memory includes random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of non-removable memory storage. The removable memory includes a subscriber identity module (SIM) card, a memory stick, a memory card (e.g., a digital camera memory card), or any other type of removable memory. The processor 602 may access the memory 616 for executable instructions or other information that is used by the computing device 600. For example, the memory 616 may include computer-readable or machine-readable instructions that may be executed by the processor 602 for performing one or more methods, processes, or procedures, or portions thereof, as described herein.

[0099] The computing device 600 may include a camera 606 that is in communication with the processor 602. The camera 606 may be a digital camera or other optical device capable of generating images or videos (e.g., image sequences) for being captured at the computing device 600. The camera 606 may include a lighting device capable of flashing to in response to signals from the processor 602.

[0100] The computing device 600 may include one or more communication circuits 618. The processor 602 may be in electrical communication with the communication circuit 618 for sending or receiving information. The communication circuit 618 may be capable of performing wired and / or wireless communications. For example, the communication circuit 618 may include one or more radio frequency (RF) transceivers for transmitting and receiving RF signalsMatter No. P38818-WO(e g., BLUETOOTH®, BLE, NFC, WIFI®, WLMAX®, cellular, or other RF signals) via an antenna, or other communications module capable of performing wireless communications. In some embodiments, one or more communication circuits 618 are capable of performing infrared (IR) communications.

[0101] The processor 602 may be in electrical communication with a keypad 624 for providing input to the processor 602. The keypad 624 may include one or more keys for receiving input from a user. The keypad 624 may include hard or soft keys for which the function of the keys changes as a user performs selections.

[0102] Other input into the processor 602 may be provided by one or more sensors 626. The sensors 626 include a motion sensor, a proximity sensor, a heartrate monitoring sensor, an accelerometer, a gyroscope, and / or another sensor on the computing device 600. The motion sensor may transmit infrared signals or use image processing to sense movement. The proximity sensor may transmit infrared signals to detect when an object is within a predefined proximity. The heartrate monitoring sensor may implement photoplethysmography to detect the amount of blood flow in the user. The heartrate monitoring sensor may include one or more LED or photodiodes to detect the amount of blood flow in the user. The heartrate monitoring sensor may implement infrared technology to detect the amount of blood flow in the user. The heartrate monitoring sensor may take an electrocardiogram (ECG) and detect information about the user’s heartrate from the ECG. The accelerometer may measure the non-gravitational acceleration of the computing device 800 in a given direction. The accelerometer may respond to vibrations associated with movement in a given direction. The measurements from the accelerometer may be used by the processor 602 to determine the magnitude or direction of the relative movement of the computing device 600, or the user’s relative position (e.g., standing, sitting, or lying down). The gyroscope may be used to determine the orientation of the computing device 600.

[0103] The processor 602 may be in electrical communication with or generate images on a display 620 for providing information to a user. The communication between the display 620 and the processor 602 may be a two-way communication, as the display 620 may include a touch screen module capable of receiving information from a user and providing such information to the processor 602. For example, the display 620 may provide soft buttons for selection by a user that are recognized by the touch screen module and provided to the processor 602 as input.Matter No. P38818-WO

[0104] The processor 602 may be in electrical communication with or control a speaker 608. The speaker 608 may provide an audible sound (e.g., tone, beep, or buzz) in response to a triggering event detected by the processor 602.

[0105] The computing device 600 may include an electric motor 610 that is in electrical communication with or controlled by the processor 602. The electric motor 610 may rotate and causes the computing device 600 to vibrate (e.g., to indicate a notification) or provide haptic feedback in response to a triggering event detected by the processor 602.

[0106] The processor 602 may be in electrical communication with or receive information from a microphone 614. For example, the processor 602 may receive audio signals via the microphone 614.

[0107] The computing device 600 may include a global positioning system (GPS) circuit 604. The GPS circuit 604 may be capable of receiving GPS information. The processor 602 may be capable of determining the GPS coordinates (e.g., latitude and longitude) of the computing device 600 based on the GPS information received via the GPS circuit.

[0108] The computing device 600 may include a visual indicator, such as one or more light-emitting diodes (LEDs) 612. In some embodiments, one or more LEDs 612 are illuminated or flashed to provide an alert or communicate other information to the user (e.g., low battery or turning on of the device).

[0109] FIG. 7 is a block diagram of an example continuous monitoring device 700. In some embodiments, the continuous monitoring device 700 is a CGM or FGM, for example. The continuous monitoring device 700 may include a subcutaneous sensor 726 that is used to sense and monitor the amount of glucose in interstitial fluid of the user. Data is transmitted from the sensor 726 to a transmitting device 704. When the continuous monitoring device 700 is a CGM, the transmitting device 704 is located directly over the sensor 726 and wirelessly powers the data transfer from the sensor 726 via power supply 720. When the continuous monitoring device 700 is an FGM, the transmitting device 704 is a mobile device or other reader device that instantaneously receives the information from the sensor 726 when the device is within the RF range of the sensor 726.

[0110] The transmitting device 704 receives data communications from the sensor 726 via a communication circuit 718. The communication circuit 718 may be in electrical communication with a processor 702. The processor 702 may include one or more circuits, suchMatter No. P38818-WO as general -purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application specific integrated circuits (ASICs), or the like. The processor 702 may perform signal coding, data processing, power control, input / output processing, or any other functionality that enables the transmitting device 704 to perform as described herein.

[0111] The transmitting device 704 may include another communication circuit 716 for communicating with other devices. The processor 702 may be in electrical communication with the communication circuit 716 for sending or receiving information. The communication circuits 716, 718 are capable of performing wired or wireless communications. For example, the communication circuits 716, 718 may include one or more radio frequency (RF) transceivers for transmitting and receiving RF signals (e g., BLUETOOTH®, BLE, near field communication (NFC), WIFI®, WLMAX®, cellular, or other RF signals) via an antenna, or other communications module capable of performing wireless communications. The communication circuits 716, 718 may communicate using the same RF protocol or a different RF protocol.

[0112] The processor 702 may store information in or retrieve information from the memory 712. The memory 712 may include a non-removable memory or a removable memory. The non-removable memory may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of non-removable memory storage. The removable memory may include a subscriber identity module (SIM) card, a memory stick, a memory card (e.g, a digital camera memory card), or any other type of removable memory. For example, the memory 712 may include computer-readable or machine-readable instructions that may be executed by the processor 702 for performing one or more methods, processes, or procedures, or portions thereof, as described herein. The processor 702 may access the memory 712 for executable instructions or other information that is used by the transmitting device 704. The processor 702 is in electrical communication with one or more input keys 724 for providing input to the processor 702.

[0113] The processor 702 may be in electrical communication with or control a speaker 714. The speaker 714 may provide an audible sound (e.g, tone, beep, or buzz) in response to a triggering event detected by the processor 702.

[0114] The continuous monitoring device 700 may include an electric motor 710 that is in electrical communication with or controlled by the processor 702. The electric motor 710 mayMatter No. P38818-WO rotate and causes the continuous monitoring device 700 to vibrate e.g., to indicate a notification) or provide haptic feedback in response to a triggering event detected by the processor 702. The electric motor 710 may provide an alert to supplement the audible alarm or replace the audible alarm provided by the speaker 714.

[0115] FIG. 8 is a block diagram of an example blood glucose meter (BGM) device 800. As shown in FIG. 8, the BGM device 800 may include a processor 802 for controlling the functionality of the BGM device 800. The processor 802 may include one or more circuits, such as general-purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application specific integrated circuits (ASICs), or the like. The processor 802 may perform signal coding, data processing, power control, image processing, input / output processing, and / or any other functionality that enables the BGM device 800 to perform as described herein.

[0116] The processor 802 may store information in or retrieve information from the memory 816. The memory 816 may include a non-removable memory or a removable memory. The non-removable memory may include random-access memory (RAM), read-only memory (ROM), a hard disk, and / or any other type of non-removable memory storage. The removable memory may include a subscriber identity module (SIM) card, a memory stick, a memory card (e.g., a digital camera memory card), and / or any other type of removable memory. The memory 816 may include computer-readable or machine-readable instructions that may be executed by the processor 802 for performing one or more methods, processes, or procedures, or portions thereof, as described herein. The processor 802 may access the memory 816 for executable instructions or other information that is used by the BGM device 800.

[0117] The BGM device 800 may include one or more communication circuits 818. The processor 802 may be in electrical communication with the communication circuit 818 for sending or receiving information. The communication circuit 818 may be capable of performing wired and / or wireless communications. For example, the communication circuit 818 may include one or more radio frequency (RF) transceivers for transmitting and receiving RF signals (e.g., BLUETOOTH®, BLE, near field communication (NFC), WIFI®, WI-MAX®, cellular, or other RF signals) via an antenna, or other communications module capable of performing wireless communications. In some embodiments, one or more communication circuits 818 may be capable of performing infrared (IR) communications.Matter No. P38818-WO

[0118] The processor 802 may be in electrical communication with a keypad 824 for providing input to the processor 802. The keypad 824 may include one or more keys for receiving input from a user. The keypad 824 may include hard or soft keys for which the function of the keys changes as a user performs selections.

[0119] Other input into the processor 802 may be provided by the BGM sensor module 804. The BGM sensor module 804 may include a blood glucose measuring engine that may analyze blood samples provided by a patient on a blood glucose measurement strip and measure the amount of blood glucose in the samples.

[0120] The processor 802 may be in electrical communication with or generate images on a display 806 for providing information to a user. The communication between the display 806 and the processor 802 may be a two-way communication, as the display 806 may include a touch screen module capable of receiving information from a user and providing such information to the processor 802. For example, the display 806 may provide soft buttons for selection by a user that are recognized by the touch screen module and provided to the processor 802 as input.

[0121] The processor 802 may be in electrical communication with or control a speaker 808. The speaker 808 may provide an audible sound (e. , tone, beep, or buzz) in response to a triggering event detected by the processor 802.

[0122] The BGM device 800 may include an electric motor 810 that is in electrical communication with or controlled by the processor 802. The electric motor 810 may rotate and cause the BGM device 800 to vibrate (e.g., to indicate an notification) or provide haptic feedback in response to a triggering event detected by the processor 802. The electric motor 810 may provide an alert to supplement the audible alarm or replace the audible alarm provided by the speaker 808.

[0123] The processor 802 may be in electrical communication with or receive information from a microphone 822. For example, the processor 802 may receive audio signals via the microphone 822.

[0124] The BGM device 800 may include a visual indicator, such as one or more one or more light-emitting diodes (LEDs) 828. In some embodiments, one or more LEDs 828 are illuminated or flashed to provide an alert or communicate other information to the user (e.g., low battery or turning on of the device).Matter No. P38818-WO

[0125] Although features, elements, and functions are described above in particular combinations, a feature, element, or function is used alone or in any combination with the other features, elements, or functions. Various presently unforeseen or unanticipated alternatives, modifications, variations, or improvements may be subsequently made that are also intended to be encompassed by the following claims.

[0126] The methods described herein are implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a randomaccess memory (RAM), removable disks, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).

Claims

Matter No. P38818-WOCLAIMSWhat is claimed is:

1. A method comprising: identifying, at a central medical monitoring device, a triggering event for updating a communication parameter set related to RF communications between a peripheral medical monitoring device and the central medical monitoring device; collecting system specification information related to at least one of the peripheral medical monitoring device or the central medical monitoring device, wherein the system specification information comprises at least one of hardware specifications or software specifications related to the at least one of the peripheral medical monitoring device or the central medical monitoring device; transmitting, to a communication parameter reconfiguration subsystem at a remote computing device, a request for the updated communication parameter set related to the RF communications between the peripheral medical monitoring device and the central medical monitoring device, wherein the request comprises at least a portion of the system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device; receiving, in response to the request for the updated communication parameter set, a response comprising the updated communication parameter set that is compatible with the at least the peripheral medical monitoring device or the central medical monitoring device having the at least the portion of the system specification information, wherein the response indicates that the communication parameter reconfiguration subsystem comprises the updated communication parameter set corresponding to the at least the portion of the system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device, and wherein the updated communication parameter set is configured to affect at least one of power consumption on the at least one of the peripheral medical monitoring device or the central medical monitoring device, a data transfer speed between the peripheral medical monitoring device and the central medical monitoring device, or a stability ofMatter No. P38818-WO connection between the peripheral medical monitoring device and the central medical monitoring device; and transmitting the updated communication parameter set to the peripheral medical monitoring device to configure the peripheral medical monitoring device for communication with the central medical monitoring device using the updated communication parameter set.

2. The method of claim 1, wherein the RF communication comprises a Bluetooth Low Energy (BLE) connection configured to communicate via a BLE communication protocol.

3. The method of claim 2, wherein the updated communication parameter set comprise one of a connection interval or timeout, a minimum connection interval, a maximum connection interval, a peripheral latency, a supervision timeout, an advertisement interval, an advertisement count, or an advertisement repetition time.

4. The method of claim 1, wherein the request comprises a first request, wherein the response comprises a first response, the method further comprising: prior to transmitting the first request, transmitting to the communication parameter reconfiguration subsystem a second request for the updated communication parameter set related to the RF communications between the peripheral medical monitoring device and the central medical monitoring device, wherein the second request comprises the at least the portion of the system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device; and receiving a second response that indicates that the updated communication parameter set is unavailable at the communication parameter reconfiguration subsystem for the at least the portion of the system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device.

5. The method of claim 4, further comprising: transmitting, based on the second response that indicates the updated communication parameter set is unavailable, a default communication parameter set to the peripheral medicalMatter No. P38818-WO monitoring device that is compatible with multiple types of peripheral medical monitoring devices and multiple types of central medical monitoring devices.

6. The method of claim 5, further comprising: after receiving the second response indicating that the updated communication parameter set is unavailable at the communication parameter reconfiguration subsystem, receiving a notification that the updated communication parameter set is available at the communication parameter reconfiguration subsystem for the at least the portion of the system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device, and wherein the first request is sent after receiving the notification that the updated communication parameter set is available at the communication parameter reconfiguration subsystem.

7. The method of claim 5, wherein the receipt of the first response to the first request for the updated communication parameter set indicates at least a threshold level of compatibility between the at least the portion of the system specification information and the updated communication parameter set for improving the RF communications by at least a threshold.

8. The method of claim 7, wherein the at least the threshold level of compatibility is determined based on at least a threshold amount of the system specification information in the request being identified as corresponding to the at least the portion of the system specification information stored with the updated communication parameter set for improving the RF communications.

9. The method of claim 5, further comprising: receiving, from the peripheral medical monitoring device, a rejection of the updated communication parameter set; and reverting to the default communication parameter set for performing communication between the peripheral medical monitoring device and the central medical monitoring device.

10. The method of claim 1, further comprising:Matter No. P38818-WO prior to sending the request for the updated communication parameter set, checking a local storage of the central medical monitoring device to identify whether the communication parameter set has been previously downloaded and shared with the peripheral medical monitoring device, wherein the request for the updated communication parameter set is sent when the communication parameter set has not been previously downloaded and shared with the peripheral medical monitoring device11. The method of claim 1, wherein the triggering event comprises at least one of: an establishment of the RF communication between the peripheral medical monitoring device and the central medical monitoring device; an indication of completion of initialization of the peripheral medical monitoring device; an indication of receipt of a medical device data from the peripheral medical monitoring device; an indication of an update to an operating system on the central medical monitoring device; an indication of an interruption to RF communication connectivity via the RF communication medium for a period of time; or an indication that a period of time has elapsed since checking for the updated communication parameter set.

12. The method of claim 1, wherein the system specification information comprises at least one of a type of the peripheral medical monitoring device with which the central medical monitoring device is enabling communication, a model of the peripheral medical monitoring device with which the central medical monitoring device is enabling communication, a version of hardware installed on the peripheral medical monitoring device with which the central medical monitoring device is enabling communication, a version of software installed on the peripheral medical monitoring device with which the central medical monitoring device is enabling communication, a type of the central medical monitoring device, a model of the central medical monitoring device, a version of hardware installed on the central medical monitoring device, or a version of software installed on the central medical monitoring device.Matter No. P38818-WO13. The method of claim 1, wherein the central medical monitoring device is configured to communicate with the peripheral medical monitoring device on a first communication link, and wherein the central medical monitoring device is configured to communicate on a second communication link with the remote computing device operating the communication parameter reconfiguration subsystem, wherein the first communication link and the second communication link use at least one of a different communication spectrum or protocol.

14. The method of claim 13, further comprising: prior to transmitting the request for the updated communication parameter set to the communication parameter reconfiguration subsystem, determining that the central medical monitoring device is unable to communicate on the second communication link with the remote computing device; and utilize a condensed updated communication parameter set stored locally at the central medical monitoring device for updating the communication parameters at the peripheral medical monitoring device, wherein the condensed updated communication parameter set comprise less parameters than the updated communication parameter set.

15. A central medical monitoring device comprising: at least one communication circuit; and a processor configured to: identify a triggering event for updating a communication parameter set related to RF communications between a peripheral medical monitoring device and the central medical monitoring device; collect system specification information related to at least one of the peripheral medical monitoring device or the central medical monitoring device, wherein the system specification information comprises at least one of hardware specifications or software specifications related to the at least one of the peripheral medical monitoring device or the central medical monitoring device; transmit, via the at least one communication circuit to a communication parameter reconfiguration subsystem at a remote computing device, a request for the updated communication parameter set related to the RF communications between the peripheralMatter No. P38818-WO medical monitoring device and the central medical monitoring device, wherein the request comprises at least a portion of the system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device; receive, in response to the request for the updated communication parameter set, a response comprising the updated communication parameter set that is compatible with the at least the peripheral medical monitoring device or the central medical monitoring device having the at least the portion of the system specification information, wherein the response indicates that the communication parameter reconfiguration subsystem comprises the updated communication parameter set corresponding to the at least the portion of the system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device, and wherein the updated communication parameter set is configured to affect at least one of power consumption on the at least one of the peripheral medical monitoring device or the central medical monitoring device, a data transfer speed between the peripheral medical monitoring device and the central medical monitoring device, or a stability of connection between the peripheral medical monitoring device and the central medical monitoring device; and transmit, via the at least one communication circuit, the updated communication parameter set to the peripheral medical monitoring device to configure the peripheral medical monitoring device for communication with the central medical monitoring device using the updated communication parameter set.

16. The central medical monitoring device of claim 15, wherein the RF communication comprises a Bluetooth Low Energy (BLE) connection configured to communicate via a BLE communication protocol.

17. The central medical monitoring device of claim 16, wherein the updated communication parameter set comprise one of a connection interval or timeout, a minimum connection interval, a maximum connection interval, a peripheral latency, a supervision timeout, an advertisement interval, an advertisement count, or an advertisement repetition time.Matter No. P38818-WO18. The central medical monitoring device of claim 15, wherein the request comprises a first request, wherein the response comprises a first response, the processor being further configured to: prior to transmitting the first request, transmit, via the at least one communication circuit to the communication parameter reconfiguration subsystem, a second request for the updated communication parameter set related to the RF communications between the peripheral medical monitoring device and the central medical monitoring device, wherein the second request comprises the at least the portion of the system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device; and receive a second response that indicates that the updated communication parameter set is unavailable at the communication parameter reconfiguration subsystem for the at least the portion of the system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device.

19. The central medical monitoring device of claim 18, the processor being further configured to: transmit, via the at least one communication circuit based on the second response that indicates the updated communication parameter set is unavailable, a default communication parameter set to the peripheral medical monitoring device that is compatible with multiple types of peripheral medical monitoring devices and multiple types of central medical monitoring devices.

20. The central medical monitoring device of claim 19, the processor being further configured to: after receiving the second response indicating that the updated communication parameter set is unavailable at the communication parameter reconfiguration subsystem, receive a notification that the updated communication parameter set is available at the communication parameter reconfiguration subsystem for the at least the portion of the system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device, and wherein the processor is configured to send the first request afterMatter No. P38818-WO receiving the notification that the updated communication parameter set is available at the communication parameter reconfiguration subsystem.

21. The central medical monitoring device of claim 19, wherein the receipt of the first response to the first request for the updated communication parameter set indicates at least a threshold level of compatibility between the at least the portion of the system specification information and the updated communication parameter set for improving the RF communications by at least a threshold.

22. The central medical monitoring device of claim 21, wherein the processor is configured to determine the at least the threshold level of compatibility based on at least a threshold amount of the system specification information in the request being identified as corresponding to the at least the portion of the system specification information stored with the updated communication parameter set for improving the RF communications.

23. The central medical monitoring device of claim 19, wherein the processor is further configured to: receive, from the peripheral medical monitoring device, a rejection of the updated communication parameter set; and revert to the default communication parameter set for performing communication between the peripheral medical monitoring device and the central medical monitoring device.

24. The central medical monitoring device of claim 15, wherein the processor is further configured to: prior to sending the request for the updated communication parameter set, check a local storage of the central medical monitoring device to identify whether the communication parameter set has been previously downloaded and shared with the peripheral medical monitoring device, wherein the processor is configured to send the request for the updated communication parameter set when the communication parameter set has not been previously downloaded and shared with the peripheral medical monitoring device.Matter No. P38818-WO25. The central medical monitoring device of claim 15, wherein the triggering event comprises at least one of: an establishment of the RF communication between the peripheral medical monitoring device and the central medical monitoring device; an indication of completion of initialization of the peripheral medical monitoring device; an indication of receipt of a medical device data from the peripheral medical monitoring device; an indication of an update to an operating system on the central medical monitoring device; an indication of an interruption to RF communication connectivity via the RF communication medium for a period of time; or an indication that a period of time has elapsed since checking for the updated communication parameter set.

26. The central medical monitoring device of claim 15, wherein the system specification information comprises at least one of a type of the peripheral medical monitoring device with which the central medical monitoring device is enabling communication, a model of the peripheral medical monitoring device with which the central medical monitoring device is enabling communication, a version of hardware installed on the peripheral medical monitoring device with which the central medical monitoring device is enabling communication, a version of software installed on the peripheral medical monitoring device with which the central medical monitoring device is enabling communication, a type of the central medical monitoring device, a model of the central medical monitoring device, a version of hardware installed on the central medical monitoring device, or a version of software installed on the central medical monitoring device.

27. The central medical monitoring device of claim 15, wherein the at least one communication circuit comprises a first communication circuit configured to communicate with the peripheral medical monitoring device on a first communication link and a second communication circuit configured to communicate on a second communication link with the remote computing device operating the communication parameter reconfiguration subsystem,Matter No. P38818-WO wherein the first communication link and the second communication link use at least one of a different communication spectrum or protocol.

28. The central medical monitoring device of claim 27, wherein the processor is configured to: prior to being configured to transmit the request for the updated communication parameter set to the communication parameter reconfiguration subsystem, determine that the central medical monitoring device is unable to communicate on the second communication link with the remote computing device; and utilize a condensed updated communication parameter set stored locally at the central medical monitoring device for updating the communication parameters at the peripheral medical monitoring device, wherein the condensed updated communication parameter set comprises less parameters than the updated communication parameter set.

29. At least one computer-readable storage medium having instructions stored thereon that are configured to, when executed by at least one processor, cause the at least one processor to: identify a triggering event for updating a communication parameter set related to RF communications between a peripheral medical monitoring device and a central medical monitoring device; collect system specification information related to at least one of the peripheral medical monitoring device or the central medical monitoring device, wherein the system specification information comprises at least one of hardware specifications or software specifications related to the at least one of the peripheral medical monitoring device or the central medical monitoring device; transmit, to a communication parameter reconfiguration subsystem at a remote computing device, a request for the updated communication parameter set related to the RF communications between the peripheral medical monitoring device and the central medical monitoring device, wherein the request comprises at least a portion of the system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device;Matter No. P38818-WO receive, in response to the request for the updated communication parameter set, a response comprising the updated communication parameter set that is compatible with the at least the peripheral medical monitoring device or the central medical monitoring device having the at least the portion of the system specification information, wherein the response indicates that the communication parameter reconfiguration subsystem comprises the updated communication parameter set corresponding to the at least the portion of the system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device, and wherein the updated communication parameter set is configured to affect at least one of power consumption on the at least one of the peripheral medical monitoring device or the central medical monitoring device, a data transfer speed between the peripheral medical monitoring device and the central medical monitoring device, or a stability of connection between the peripheral medical monitoring device and the central medical monitoring device; and transmit the updated communication parameter set to the peripheral medical monitoring device to configure the peripheral medical monitoring device for communication with the central medical monitoring device using the updated communication parameter set.

30. The at least one computer-readable storage medium of claim 29, wherein the RF communication comprises a Bluetooth Low Energy (BLE) connection configured to communicate via a BLE communication protocol.

31. The at least one computer-readable storage medium of claim 30, wherein the updated communication parameter set comprise one of a connection interval or timeout, a minimum connection interval, a maximum connection interval, a peripheral latency, a supervision timeout, an advertisement interval, an advertisement count, or an advertisement repetition time.

32. The at least one computer-readable storage medium of claim 29, wherein the request comprises a first request, wherein the response comprises a first response, wherein the instructions are further configured to cause the at least one processor to: prior to transmitting the first request, transmit to the communication parameter reconfiguration subsystem a second request for the updated communication parameter set relatedMatter No. P38818-WO to the RF communications between the peripheral medical monitoring device and the central medical monitoring device, wherein the second request comprises the at least the portion of the system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device; and receive a second response that indicates that the updated communication parameter set is unavailable at the communication parameter reconfiguration subsystem for the at least the portion of the system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device.

33. The at least one computer-readable storage medium of claim 32, wherein the instructions are further configured to cause the at least one processor to: transmit, based on the second response that indicates the updated communication parameter set is unavailable, a default communication parameter set to the peripheral medical monitoring device that is compatible with multiple types of peripheral medical monitoring devices and multiple types of central medical monitoring devices.

34. The at least one computer-readable storage medium of claim 33, wherein the instructions are further configured to cause the at least one processor to: after receipt of the second response indicating that the updated communication parameter set is unavailable at the communication parameter reconfiguration subsystem, receive a notification that the updated communication parameter set is available at the communication parameter reconfiguration subsystem for the at least the portion of the system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device, and wherein the instructions are further configured to cause the at least one processor to send the first request after receipt of the notification that the updated communication parameter set is available at the communication parameter reconfiguration subsystem.

35. The at least one computer-readable storage medium of claim 33, wherein the receipt of the first response to the first request for the updated communication parameter set indicates at least a threshold level of compatibility between the at least the portion of the systemMatter No. P38818-WO specification information and the updated communication parameter set for improving the RF communications by at least a threshold.

36. The at least one computer-readable storage medium of claim 35, wherein the instructions are further configured to cause the at least one processor to determine the at least the threshold level of compatibility based on at least a threshold amount of the system specification information in the request being identified as corresponding to the at least the portion of the system specification information stored with the updated communication parameter set for improving the RF communications.

37. The at least one computer-readable storage medium of claim 33, wherein the instructions are further configured to cause the at least one processor to: receive, from the peripheral medical monitoring device, a rejection of the updated communication parameter set; and revert to the default communication parameter set for performing communication between the peripheral medical monitoring device and the central medical monitoring device.

38. The at least one computer-readable storage medium of claim 29, wherein the instructions are further configured to cause the at least one processor to: prior to sending the request for the updated communication parameter set, check a local storage of the central medical monitoring device to identify whether the communication parameter set has been previously downloaded and shared with the peripheral medical monitoring device, wherein the instructions are further configured to cause the at least one processor to send the request for the updated communication parameter set when the communication parameter set has not been previously downloaded and shared with the peripheral medical monitoring device.

39. The at least one computer-readable storage medium of claim 29, wherein the triggering event comprises at least one of: an establishment of the RF communication between the peripheral medical monitoring device and the central medical monitoring device;Matter No. P38818-WO an indication of completion of initialization of the peripheral medical monitoring device; an indication of receipt of a medical device data from the peripheral medical monitoring device; an indication of an update to an operating system on the central medical monitoring device; an indication of an interruption to RF communication connectivity via the RF communication medium for a period of time; or an indication that a period of time has elapsed since checking for the updated communication parameter set.

40. The at least one computer-readable storage medium of claim 29, wherein the system specification information comprises at least one of a type of the peripheral medical monitoring device with which the central medical monitoring device is enabling communication, a model of the peripheral medical monitoring device with which the central medical monitoring device is enabling communication, a version of hardware installed on the peripheral medical monitoring device with which the central medical monitoring device is enabling communication, a version of software installed on the peripheral medical monitoring device with which the central medical monitoring device is enabling communication, a type of the central medical monitoring device, a model of the central medical monitoring device, a version of hardware installed on the central medical monitoring device, or a version of software installed on the central medical monitoring device.

41. The at least one computer-readable storage medium of claim 29, wherein the instructions are configured to cause the central medical monitoring device to communicate with the peripheral medical monitoring device on a first communication link, and wherein the instructions are configured to cause the central medical monitoring device to communicate with the remote computing device operating the communication parameter reconfiguration subsystem on a second communication link, wherein the first communication link and the second communication link use at least one of a different communication spectrum or protocol.Matter No. P38818-WO42. The at least one computer-readable storage medium of claim 27, wherein the instructions are further configured to cause the at least one processor to: prior to being configured to transmit the request for the updated communication parameter set to the communication parameter reconfiguration subsystem, determine that the central medical monitoring device is unable to communicate on the second communication link with the remote computing device; and utilize a condensed updated communication parameter set stored locally at the central medical monitoring device for updating the communication parameters at the peripheral medical monitoring device, wherein the condensed updated communication parameter set comprises less parameters than the updated communication parameter set.

43. A method comprising: receiving, from a central medical monitoring device, a request for an updated communication parameter set related to the RF communication between a peripheral medical monitoring device and the central medical monitoring device, wherein the request comprises at least a portion of system specification information related to at least one of the peripheral medical monitoring device or the central medical monitoring device, and wherein the system specification information comprises at least one of hardware specifications or software specifications related to at least one of the peripheral medical monitoring device or the central medical monitoring device; determining, at a communication parameter reconfiguration subsystem at a remote computing device, an availability of the updated communication parameter set corresponding to the at least the portion of system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device; and transmitting, in response to the request for the updated communication parameter set, a response comprising the updated communication parameter set that is compatible with the at least the peripheral medical monitoring device or the central medical monitoring device having the at least the portion of the system specification information, and wherein the updated communication parameter set is configured to affect at least one of a power consumption on the at least one of the peripheral medical monitoring device or the central medical monitoring device, a data transfer speed between the peripheral medical monitoring device or the centralMatter No. P38818-WO medical monitoring device, or a stability of connection between the peripheral medical monitoring device or the central medical monitoring device.

44. The method of claim 43, wherein the determining the availability of the updated communication parameter set comprises: determining at least a threshold level of compatibility between the updated communication parameter set and the at least the portion of the system specification information for improving the RF communications by at least a threshold.

45. The method of claim 44, wherein the at least the threshold level of compatibility is determined based on at least a threshold amount of the system specification information in the request being identified as corresponding to the at least the portion of the system specification information stored with the updated communication parameter set for improving the RF communications.

46. The method of claim 43, wherein the request comprises a first request, and wherein the response comprises a first response, the method further comprising: prior to receiving the first request, receiving a second request from the central medical monitoring device for the updated communication parameter set related to the RF communications between the peripheral medical monitoring device and the central medical monitoring device, wherein the second request comprises the at least the portion of the system specification information related to at least one of the peripheral medical monitoring device or the central medical monitoring device; determining, at the communication parameter reconfiguration subsystem, an unavailability of the updated communication parameter set corresponding to the at least the portion of system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device; storing an indication of the unavailability of the updated communication parameter set corresponding to the at least the portion of system specification information;Matter No. P38818-WO transmitting, to the central medical monitoring device, a second response indicating the unavailability of the updated communication parameter set corresponding to the at least the portion of system specification information; receiving updates to communication parameter sets for different peripheral medical monitoring devices and central medical monitoring devices, and wherein the determining of the availability of the updated communication parameter set is based on the updates to the communication parameter sets for different peripheral medical monitoring devices and central medical monitoring devices and the indication of the prior unavailability of the updated communication parameter set corresponding to the at least the portion of system specification information; transmitting, to the central medical monitoring device, a notification that the updated communication parameter set is available at the communication parameter reconfiguration subsystem, and wherein the first request is received after the notification is transmitted.

47. A computing device comprising: at least one communication circuit; and at lest one processor configured to: receive, from a central medical monitoring device, a request for an updated communication parameter set related to the RF communication between a peripheral medical monitoring device and the central medical monitoring device, wherein the request comprises at least a portion of system specification information related to at least one of the peripheral medical monitoring device or the central medical monitoring device, and wherein the system specification information comprises at least one of hardware specifications or software specifications related to at least one of the peripheral medical monitoring device or the central medical monitoring device; determine, at a communication parameter reconfiguration subsystem, an availability of the updated communication parameter set corresponding to the at least the portion of system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device; and transmit, via the at least one communication circuit in response to the request for the updated communication parameter set, a response comprising the updatedMatter No. P38818-WO communication parameter set that is compatible with the at least the peripheral medical monitoring device or the central medical monitoring device having the at least the portion of the system specification information, and wherein the updated communication parameter set is configured to affect at least one of a power consumption on the at least one of the peripheral medical monitoring device or the central medical monitoring device, a data transfer speed between the peripheral medical monitoring device or the central medical monitoring device, or a stability of connection between the peripheral medical monitoring device or the central medical monitoring device.

48. The computing device of claim 47, wherein the at least one processor being configured to determine the availability of the updated communication parameter set comprises the at least one processor being configured to: determine at least a threshold level of compatibility between the updated communication parameter set and the at least the portion of the system specification information for improving the RF communications by at least a threshold.

49. The computing device of claim 48, wherein the at least the threshold level of compatibility is determined based on at least a threshold amount of the system specification information in the request being identified as corresponding to the at least the portion of the system specification information stored with the updated communication parameter set for improving the RF communications.

50. The computing device of claim 47, wherein the request comprises a first request, and wherein the response comprises a first response, the at least one processor being further configured to: prior to receiving the first request, receive a second request from the central medical monitoring device for the updated communication parameter set related to the RF communications between the peripheral medical monitoring device and the central medical monitoring device, wherein the second request comprises the at least the portion of the system specification information related to at least one of the peripheral medical monitoring device or the central medical monitoring device;Matter No. P38818-WO determine, at the communication parameter reconfiguration subsystem, an unavailability of the updated communication parameter set corresponding to the at least the portion of system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device; store an indication of the unavailability of the updated communication parameter set corresponding to the at least the portion of system specification information; transmit, via the at least one communication circuit to the central medical monitoring device, a second response indicating the unavailability of the updated communication parameter set corresponding to the at least the portion of system specification information; receive updates to communication parameter sets for different peripheral medical monitoring devices and central medical monitoring devices, and wherein the at least one processor is configured to determine the availability of the updated communication parameter set based on the updates to the communication parameter sets for different peripheral medical monitoring devices and central medical monitoring devices and the indication of the prior unavailability of the updated communication parameter set corresponding to the at least the portion of system specification information; transmit, via the at least one communication circuit to the central medical monitoring device, a notification that the updated communication parameter set is available at the communication parameter reconfiguration subsystem, and wherein the at least one processor is configured to receive the first request after the notification is transmitted.

51. At least one computer-readable storage medium having instructions stored thereon that are configured to, when executed by at least one processor, cause the at least one processor to: receive, from a central medical monitoring device, a request for an updated communication parameter set related to the RF communication between a peripheral medical monitoring device and the central medical monitoring device, wherein the request comprises at least a portion of system specification information related to at least one of the peripheral medical monitoring device or the central medical monitoring device, and wherein the system specification information comprises at least one of hardware specifications or software specifications related to at least one of the peripheral medical monitoring device or the central medical monitoring device;Matter No. P38818-WO determine an availability of the updated communication parameter set corresponding to the at least the portion of system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device; and transmit, in response to the request for the updated communication parameter set, a response comprising the updated communication parameter set that is compatible with the at least the peripheral medical monitoring device or the central medical monitoring device having the at least the portion of the system specification information, and wherein the updated communication parameter set is configured to affect at least one of a power consumption on the at least one of the peripheral medical monitoring device or the central medical monitoring device, a data transfer speed between the peripheral medical monitoring device or the central medical monitoring device, or a stability of connection between the peripheral medical monitoring device or the central medical monitoring device.

52. The at least one computer-readable storage medium of claim 51, wherein the instructions being configured to cause the at least one processor to determine the availability of the updated communication parameter set comprises the instructions being configured to cause at least one processor to: determine at least a threshold level of compatibility between the updated communication parameter set and the at least the portion of the system specification information for improving the RF communications by at least a threshold.

53. The at least one computer-readable storage medium of claim 52, wherein the instructions are further configured to cause the at least one processor to determine the at least the threshold level of compatibility based on at least a threshold amount of the system specification information in the request being identified as corresponding to the at least the portion of the system specification information stored with the updated communication parameter set for improving the RF communications.

54. The at least one computer-readable storage medium of claim 51, wherein the request comprises a first request, and wherein the response comprises a first response, wherein the instructions are further configured to cause the at least one processor to:Matter No. P38818-WO prior to receiving the first request, receive a second request from the central medical monitoring device for the updated communication parameter set related to the RF communications between the peripheral medical monitoring device and the central medical monitoring device, wherein the second request comprises the at least the portion of the system specification information related to at least one of the peripheral medical monitoring device or the central medical monitoring device; determine an unavailability of the updated communication parameter set corresponding to the at least the portion of system specification information related to the at least one of the peripheral medical monitoring device or the central medical monitoring device; store an indication of the unavailability of the updated communication parameter set corresponding to the at least the portion of system specification information; transmit, to the central medical monitoring device, a second response indicating the unavailability of the updated communication parameter set corresponding to the at least the portion of system specification information; receive updates to communication parameter sets for different peripheral medical monitoring devices and central medical monitoring devices, and wherein the instructions are further configured to cause the at least one processor to determine the availability of the updated communication parameter set based on the updates to the communication parameter sets for different peripheral medical monitoring devices and central medical monitoring devices and the indication of the prior unavailability of the updated communication parameter set corresponding to the at least the portion of system specification information; and transmit, to the central medical monitoring device, a notification that the updated communication parameter set is available at the communication parameter reconfiguration subsystem, and wherein the instructions are further configured to cause the at least one processor receive the first request after the notification is transmitted.

Images