System, apparatus, and method for processing wireless communication in a specimen monitoring environment

Abstract

To provide an analyte monitoring system, device, and method which can maintain compliance with wireless protocol requirements to resolve issues that may arise when wireless communication is executed according to a protocol with timing requirements that do not consider processing and other delays that may exist in the analyte monitoring system.SOLUTION: Example embodiments of systems, devices, and methods are described for communication in an analyte monitoring system in accordance with an applicable communication protocol. A first device of the system may transmit a command to a second device of the system and the second device may encounter a processing delay in preparing data responsive to the command. The second device may transmit dummy data to the first device in order to maintain compliance with the communication protocol until such time that the second device is ready to transmit data responsive to the command. Numerous different embodiments for incorporating and / or accommodating the presence of dummy data in a communication hierarchy are provided.SELECTED DRAWING: Figure 4C

Description

Related Applications

[0005] , , , , ,

[0004] ,

[0003] ,

[0001] This application claims the priority and benefit of U.S. Provisional Patent Application No. 62 / 836,059, filed on April 18, 2019, the entire disclosure of which is incorporated herein by reference. Further, this application is a divisional application of Japanese Patent Application No. 2021-560956, filed on April 17, 2020.

Technical Field

[0002] The present subject matter generally relates to systems, apparatuses, and methods for maintaining compliance with timing requirements of communication protocols.

Background Art

[0003] The detection and / or monitoring of analyte levels, such as glucose, ketones, lactate, hemoglobin A1C, etc., can be extremely important for the health of individuals suffering from diabetes. Diabetic patients generally monitor their glucose levels and confirm that they are clinically maintained within a safe range, and this information can also be used to determine whether insulin is needed to lower the glucose level in the body and / or when it is needed, or when additional glucose is needed to raise the glucose level in the body.

[0004] Increasing clinical data shows a strong correlation between the frequency of glucose monitoring and glycemic control. Despite such a correlation, many individuals diagnosed with a diabetic condition do not monitor their glucose levels as frequently as they should due to a combination of factors including convenience, test discretion, pain associated with glucose testing, and cost. [[ID=​Sample monitoring systems have been developed to help individuals monitor glucose and / or other sample levels more frequently. These systems typically use devices that are placed inside or on the patient's body and have sensors that continuously or repeatedly measure the patient's glucose levels over the sensor's lifespan. This device can wirelessly communicate the measured information to other devices, usually smart devices, calculators, or other types of glucose information readers. Wireless communication increases the convenience and ease of use of the system. However, problems arise when wireless communication is performed according to protocols with timing requirements that do not take into account processing and other delays that may exist within the sample monitoring system. [Overview of the Initiative] [Problems that the invention aims to solve]

[0006] For these and other reasons, there is a need for specimen monitoring systems, devices, and methods that can maintain compliance with wireless protocol requirements. [Means for solving the problem]

[0007] Embodiments of systems, apparatus, and methods for communication in accordance with applicable communication protocols within a specimen monitoring system are described herein. In many embodiments, a first apparatus of the system can transmit a command to a second apparatus of the system, which may face processing delays in preparing data in response to the command. In these or other cases, the second apparatus can transmit dummy data to the first apparatus to maintain compliance with the communication protocol until the second apparatus is able to transmit data in response to the command. Numerous different embodiments for incorporating and / or accepting the presence of dummy data within the communication hierarchy are presented.

[0008] Other systems, apparatus, methods, features, and advantages of the subject matter described herein will become apparent to those skilled in the art by considering the following figures and detailed description. All such additional systems, methods, features, and advantages are included in the description, are within the scope of the subject matter described herein, and are intended to be protected by the appended claims. Unless otherwise expressly stated in the claims, these features of the embodiments should never be construed as limiting the appended claims. [Brief explanation of the drawing]

[0009] Details regarding both the structure and operation of the subject matter described in this book may become clear by examining the accompanying diagrams. In the diagrams, similar symbols refer to similar parts. The parts in the diagrams are not necessarily to a fixed scale, and the emphasis is on illustrating the principles of the subject matter. Furthermore, all diagrams are intended to convey concepts, and relative size, shape, and other detailed attributes may be illustrated in a general manner, not strictly or precisely. [Figure 1] This is a block diagram illustrating an embodiment of an in vivo specimen monitoring system. [Figure 2] This is a block diagram illustrating an embodiment of the reading device. [Figure 3A] This is a block diagram illustrating an embodiment of a device worn on the body. [Figure 3B] This is a block diagram illustrating an embodiment of a device worn on the body. [Figure 4A] This is a flowchart illustrating an example of a communication method within a specimen monitoring system. [Figure 4B] This is a flowchart illustrating an example of a communication method within a specimen monitoring system. [Figure 4C] This is a flowchart illustrating an example of a communication method within a specimen monitoring system. [Figure 4D] This is a flowchart illustrating an example of a communication method within a specimen monitoring system. [Figure 5A] This is an information flow diagram illustrating the communication methods within the specimen monitoring system. [Figure 5B] This is an information flow diagram illustrating the communication methods within the specimen monitoring system. [Modes for carrying out the invention]

[0010] Before describing the subject matter in detail, it should be understood that this disclosure is not limited to the specific embodiments described and, therefore, may vary. It should also be understood that the terminology used herein is for the purpose of describing only specific embodiments and is not intended to limit them. The scope of this disclosure is limited only by the appended claims.

[0011] Generally, embodiments of this disclosure are used in conjunction with systems, apparatus, and methods for detecting at least one specimen in a body fluid (e.g., in the interstitial fluid (ISF) or blood subcutaneously, or in the dermal fluid of the dermis), such as glucose. Accordingly, many embodiments include in vivo specimen sensors that are structurally configured such that at least a portion thereof is located or can be located within the user's body in order to obtain information about at least one specimen of the body. However, embodiments disclosed herein may be used in conjunction with in vivo specimen monitoring systems having in vitro capabilities, as well as purely in vitro or in vitro specimen monitoring systems that include entirely non-invasive systems.

[0012] Furthermore, the embodiments described in this document may be used in conjunction with devices that detect biometric measurements other than specimen data, such as heart rate, blood pressure, body temperature, sweating, and intraocular pressure. The embodiments described in this document may be used in conjunction with devices that detect only movement and / or activity levels, or detect them in combination with any other measurement. Therefore, the embodiments described in this document are not limited to medical applications and may be used in conjunction with other non-medical systems that utilize RF communication between devices.

[0013] Before describing the embodiments in detail, it is desirable to first describe examples of devices that may be present in, for example, an in vivo sample monitoring system and examples of their operation. All of these can be used in conjunction with the embodiments described herein.

[0014] Embodiment of a specimen monitoring system In vivo monitoring systems may include sensors that come into contact with a user's bodily fluids within the body and detect the level of a sample within them. The sensor may be part of an OBD (On-Board Device) that includes electronic circuits and a power supply that enable and control sample detection while attached to the user's body. Devices attached to the body and their variations may also be called “sensor devices,” “body-attached electronic devices,” “sensor control devices,” or “sensor communication devices.” As used in this document, these terms are not limited to devices with in vivo sample sensors but encompass devices with other types of extra vivo sensors, whether biometric (e.g., optical sample sensors, heart rate sensors, temperature sensors, etc.) or non-biometric. The term “body-attached” includes devices directly attached to the body (e.g., attached to the skin), devices entirely inside the body (e.g., fully implanted devices), devices very close to the body such as wearable devices (e.g., glasses, watches, bracelets or neckbands or necklaces), or pocket devices.

[0015] An in vivo monitoring system may also include one or more readers that read information about levels detected from devices attached to the body. These readers can process the detected sample information and / or display it to the user in any number of forms. These devices and their variations may be called “portable readers,” “readers,” “portable electronic devices” (or handhelds), “portable data processing” devices, “information receivers,” “receiving” devices (or simply receivers), “relay” devices, or “remote” devices, etc.

[0016] In vivo sample monitoring systems can be distinguished into in vitro systems, which come into contact with biological samples outside the body, and extra vivo systems, which are entirely outside the body but acquire information about the body or substances within the body without extracting biological samples from the body. In vitro systems may include instruments having ports for receiving sample test pieces containing the user's bodily fluids. The bodily fluids can be analyzed to determine the user's sample level. As described above, the embodiments described herein can be used with in vivo systems, extra vivo systems, in vitro systems, and combinations thereof.

[0017] The embodiments described in this book can be used to monitor and / or process information regarding one or more different specimens of any number. Specimens that can be monitored include, but are not limited to, acetylcholine, amylase, bilirubin, cholesterol, chorionic gonadotropin, glycosylated hemoglobin (HbA1c), creatine kinase (e.g., CK-MB), creatine, creatinine, DNA, fructosamine, glucose, glucose derivatives, glutamine, growth hormone, hormones, ketones, ketone bodies, lactate, peroxide, prostate-specific antigen, prothrombin, RNA, thyroid-stimulating hormone, and troponin. The concentrations of drugs, such as antibiotics (e.g., gentamicin, vancomycin, etc.), digitoxin, digoxin, abused drugs, theophylline, and warfarin may also be monitored. In embodiments where two or more specimens are monitored, the specimens may be monitored simultaneously or at different times.

[0018] Embodiments of an in-vivo specimen monitoring system can include a device attached to one or more bodies, one or more reading devices, and one or more computer systems that are highly interconnected and capable of communicating. FIG. 1 is an exemplary block diagram depicting an embodiment of an in-vivo specimen monitoring system 100, and the monitoring system 100 includes a body-attached device (OBD) 102, a first reading device 120-1, a second reading device 120-2, a local or remote computer system 170, and a reliable computer system 180 (e.g., a server) that are each configured to communicate through a communication network 190. References to the reading device 120 in this book refer to both the reading devices 120-1 and 120-2.

[0019] The OBD 102 can communicate with the reading device 120 through two or more wireless communication paths, links, or channels 141 and 142 that can be one-way or two-way. The links 141 and 142 are constituted by communication circuits and one or more antennas present in the OBD 102 and the reading device 120. In some embodiments, the ability of the devices 102 and 120 to communicate through an additional wired communication path, such as a universal serial bus (USB) cable (not shown), can be implemented.

[0020] Wireless communication link 141 can have various embodiments. In some embodiments, communication link 141 uses near-field electromagnetic induction for communication. Such links are sometimes called near-proximity communication because they require the transmitting and receiving devices to be relatively very close compared to far-field (or transition zone) communication. Communication using electromagnetic induction occurs typically within one wavelength distance, and more typically within two wavelength distances between the transmitting and receiving devices. In many embodiments, communication by electromagnetic induction occurs only within a range of 12 inches (30.48 cm) or less, depending on the transmission frequency and power, etc. Examples include the Near Field Communication (NFC) protocol, which is a plurality of protocols (or specifications) that define operating parameters, modulation methods, encoding, transfer speeds, frame formats, and command definitions for NFC devices. Some examples of NFC devices operate at 13.56 megahertz (MHz). A non-exhaustive list of examples of these protocols is as follows: ECMA-340, ECMA-352, ISO / IEC 14443, ISO / IEC 15693, ISO / IEC 18000-3, ISO / IEC 18092, and ISO / IEC 21481, all of which are incorporated herein by reference in their entirety. Examples also include Radio Frequency Identification (RFID) protocols.

[0021] Response communication using electromagnetic induction can be generated passively. In that case, the power carried by the transmission from the first device is captured by the second device that receives it and is used to power the transmission of the response from the second device to the first device. Response communication using electromagnetic induction can be generated actively. In that case, the second device that receives it uses only the power from its own power source or in combination with the power obtained from the received transmission to power the transmission of the response communication to the first device.

[0022] A transmission from the reader 120 to the OBD 102, such as a request for sample data, prompts the OBD 102 to respond by transmitting sample data obtained from its own measurement, such as a sensor 104. The process of transmitting from the reader 120 to the OBD 102 and receiving a response from the OBD 102 may be called a “scan” or “scanning” operation of the OBD 102. In many embodiments, the OBD 102 is configured as a passive device, and power from the transmission from the reader 120 received via link 141 is taken and used to power the transmission of response communications from the OBD 102 to the reader 120. This may be called “passive scanning.” In such embodiments, the OBD 102 can power the transmission without using power from its own internal power source (e.g., a coin cell battery). In other embodiments, the OBD 102 may be configured as an active device. In this case, power from the transmission from the reader 120 received via link 141 is either taken in or not taken in, and the power used to transmit the response communication from the OBD 102 to the reader 120 is generated all or partly by the power supply inside the OBD 102. This may be called "active scanning".

[0023] Wireless communication link 142 utilizes communication protocols other than those used by link 141 and relies primarily on the longer-distance far-field characteristics of electromagnetic transmission. In this case, transmission does not occur solely through inductive coupling. Link 142 can communicate over the same near-field and much longer distances as link 141. Link 142 can also have various embodiments. To constitute link 142, the OBD 102 and reader 120 may comprise communication circuits and one or more antennas configured to communicate using standardized or proprietary protocols and formats. For example, link 142 may be configured using Bluetooth® (e.g., Conventional Bluetooth® or Bluetooth® Low Energy (BLE)) frequencies and protocols. Link 142 may also be configured using other protocols in other frequency bands, including communication protocols existing as of the filing date or subsequent filing dates, such as the ultra-high frequency (UHF) band (e.g., 450-470 MHz) and proprietary protocols, various frequency Wi-Fi protocols, and other proprietary protocols. While both links 141 and 142 can utilize various protocols and frequencies, for ease of distinction, they are referred to in this document as NFC link 141 and Bluetooth® (BT) link 142. In some embodiments, NFC link 141 is used to activate and power up a body-worn device 102, while sample data is communicated only through BT link 142.

[0024] The OBD102 may be configured to communicate with multiple readers 120 through separate instances of links 141 and 142. This is illustrated in Figure 1 by the presence of a first reader 120-1 that can communicate with the OBD102 via NFC link 141-1 and BT link 142-1, and a second reader 120-2 that can communicate with the OBD102 via NFC link 141-2 and BT link 142-2. Additional readers 120 may also be present.

[0025] The reader 120 can communicate with multiple OBD 102s. For example, each reader 120 can communicate with a first OBD 102 attached to the user's body for the duration of the first OBD's operating life, after which the OBD 102 is discarded and replaced with a second OBD 102, and the same reader 120 can communicate again. In some embodiments, a particular reader 120 can communicate simultaneously with multiple OBD 102s attached to the same or different users.

[0026] The reader 120 can also communicate with other devices via wired, wireless, or combined communication. Figure 1 shows a reader 120-1 communicating with a computer system 170 (e.g., a local or remote computer system) via a communication link, path, or channel 171, and with a network 190 such as the Internet or the cloud via a communication link, path, or channel 191 (reader 120-2 can also communicate in a similar manner to these devices, but their connections are not shown for the sake of illustration). Reader 120-1 can communicate with a trusted computer system 180 via network 190 using link 191. The trusted computer system 180 can communicate with computer system 170 via a communication link, path, or channel 192. For example, the trusted computer system 180 may be a server that provides sample analysis software to reader 120-1 and / or computer system 170 in the form of a downloadable software application or app, or as a web page accessible via an internet browser.

[0027] Communication links 171, 191, and 192 may be wireless, wired, or both; they may be one-way or two-way; and they may be part of a telecommunications network, such as a Wi-Fi network, a local area network (LAN), a wide area network (WAN), the Internet, or other data network. In some cases, communication paths 171 and 172 may be at least partially the same path (for example, when communicating via Wi-Fi). All communications through various paths may be encrypted, and OBD 102, reader 120-1, reader 120-2, computer system 170, and trusted computer system 180 may be configured to encrypt and decrypt these transmitted and received communications, respectively.

[0028] Variations of apparatus 102 and 120 and other components of the in vivo specimen monitoring system suitable for use in conjunction with the embodiments of the systems, apparatus, and methods described herein are described in U.S. Patent Application Publication No. 2011 / 0213225 (225), which is incorporated herein by reference in its entirety.

[0029] Referring again to Figure 1, the OBD 102 may include a housing 103 that houses the sample monitoring circuit and power supply. In this embodiment, the sample monitoring circuit extends through an adhesive patch 105 and is electrically coupled to a sample sensor 104 that protrudes from the housing 103. The adhesive patch 105 includes at least one adhesive layer (not shown) for attachment to the skin surface of the user's body and an optional second adhesive layer on the opposite side for attachment to the housing 103. Other forms of attachment to the body and / or the housing 103 may be used in addition to or instead of the adhesive.

[0030] The specimen sensor 104 is fitted to be inserted at least partially into the user's body and may be used with a specimen monitoring circuit to fluidly contact the user's bodily fluids (e.g., ISF, dermal fluid, or blood) and measure the user's specimen-related data. The sensor 104 and any associated sensor electronic circuits may be attached to the body in any desired manner. For example, an inserter (not shown) may be used to insert all or part of the specimen sensor 104 through the outer surface of the user's skin and into contact with the user's bodily fluids. In this case, the inserter may also attach the OBD 102 with an adhesive patch 105 to the skin. In other embodiments, the inserter may first position the sensor 104, and then associated electronic circuits (e.g., a wireless transmission circuit and / or a data processing circuit) may be coupled to the sensor 104 by hand or instrument. Examples of inserters are described in U.S. Patent Publications No. 2008 / 0009692, 2011 / 0319729, 2015 / 0018639, 2015 / 0025345, and 2015 / 0173661. All of these are incorporated herein by reference.

[0031] After collecting raw analog data from the user's body, the OBD102 can optionally apply analog signal adjustments to the data and convert the analog data into a digital format of the adjusted raw data. In some embodiments, this digital raw data can be encoded for transmission to another device, such as a reader 120. The reader 120 processes the digital raw data according to an algorithm into a final format representing the user's measured biometric volume (e.g., a format suitable for display to the user). The data processed according to the algorithm can then be formatted or graphically processed for digital display to the user. In other embodiments, the OBD102 itself can process and encode the digital raw data according to an algorithm into a final format representing the user's measured biometric volume (e.g., sample level) and wirelessly transmit the data to the reader 120. The reader 120 can format or graphically process the received data for digital display to the user. In other embodiments, the OBD102 can graphically process the data so that the final format can be displayed and display the data on the OBD102's display or transmit it to the reader 120. In some embodiments, the system (e.g., integrated into a diabetes monitoring system) uses the final form of biometric data (before graphical processing) for display to the user without further processing. In some embodiments, the OBD 102 and reader 120 transmit the raw digital data to another computer system for algorithmic processing and display. The transmission of these various forms of data may occur through either or both of links 141 and 142.

[0032] Each reader 120 in system 100 may include a display 122 for outputting information to the user and receiving input from the user, and one or more optional input components 121, such as buttons, actuators, touch sensor switches, capacitive switches, pressure sensor switches, jog wheels, etc., for inputting data, commands, or controlling the operation of the reader 120. In some embodiments, the display 122 and input components 121 may be integrated into a single component, such as a touchscreen user interface. In this case, the display can detect the presence and location of physical contact on the display. In some embodiments, the input component 121 of the reader 120 may include a microphone, and the reader 120 may include software configured to analyze the voice input received from the microphone so that the function and operation of the reader 120 are controlled by voice commands. In some embodiments, the output component of the reader 120 may include a speaker (not shown) for outputting information as an audio signal. Similar voice response components, such as a speaker, microphone, and software routines for generating, processing, and storing voice drive signals, may be included in OBD 102.

[0033] The reader 120 may also include one or more data communication ports 123 for wired data communication with an external device such as a computer system 170 or an OBD 102. Example data communication ports include all types of USB ports, RS-232 ports, Ethernet ports, Firewire ports, or other similar data communication ports configured to connect to a suitable data cable, and may include all types of serial or parallel connectors. The reader 120 may also include an integrated or attachable in-tube glucose meter and an in-tube test piece port (not shown) for receiving in-tube glucose test pieces for performing in-tube blood glucose measurements.

[0034] The reader 120 can display measured biometric data received wirelessly from the OBD 102 and may be configured to output alarms, warnings, glucose values, etc., which may be visual, audible, tactile, or any combination thereof. Further details and other display embodiments are described, for example, in U.S. Patent Application Publication No. 2011 / 0193704, which is incorporated herein by reference.

[0035] The reader 120 may function as a data conduit or relay for transferring measured data from the OBD 102 to a computer system 170 or a trusted computer system 180. In one embodiment, the data received from the OBD 102 may be stored (permanently or temporarily) in one or more memories of the reader 120 before being uploaded to systems 170, 180, or network 190.

[0036] The computer system 170 may be a personal computer, server terminal, laptop computer, tablet, or other suitable data processing device. The computer system 170 may be (or may include) software for data management and analysis and communication with components within the specimen monitoring system 100. The computer system 170 may be used by a user or healthcare professional to display and / or analyze biometric data measured by the OBD 102. In some embodiments, the OBD 102 can communicate biometric data to the computer system 170 directly or indirectly via an internet connection (and optionally without first transmitting to the reader 120) without the intermediary of a reader 120 or similar device. The operation and use of the computer system 170 are further described in Publication 225, which is incorporated herein by reference. The specimen monitoring system 100 may also be configured to operate with a data processing module (not shown) as described in Publication 225.

[0037] A trusted computer system 180 is owned by the manufacturer or distributor of the OBD102 via a physically or substantially secure connection and may be used as a server to perform authentication of the OBD102 for the secure storage of the user's biometric data and / or to provide a data analysis program (e.g., accessible via a web browser) for analyzing the user's measurement data.

[0038] Embodiment of a reading device The reader 120 may be a specially manufactured reader designed to interface with the OBD 102. The reader 120 may also be, but is not limited to, a mobile communication device such as a mobile phone, including a Wi-Fi or internet-enabled smartphone, tablet, or personal digital assistant (PDA). The reader 120 may also be configured as a portable smart wearable electronic device such as smart glasses, a smartwatch, or a bracelet.

[0039] Figure 2 is a block diagram of an embodiment of the reading device 120 (for example, a dedicated reader, a smartphone, etc.). Here, the reading device 120 includes an input component 121, a display 122, a processor or processing circuit 206 having a memory 203, a first communication circuit 241 coupled to a first antenna 251, a second communication circuit 242 coupled to an optional second antenna 252, a memory 210, a power supply 216, and a power management circuit 218.

[0040] The reader 120 is implemented through a high degree of interconnection, with the power supply 216 coupled to each component shown in Figure 2. These components that communicate or receive data, information, or commands (e.g., processor 206, memory 203, memory 210, power management circuit 218, input component 121, indicator 122, first communication circuit 241, and second communication circuit 242) may be communicably coupled to all other such components, for example, via one or more communication connections or bus 220. Figure 2 is a simplified diagram of typical hardware and functions present in a dedicated reader, and those skilled in the art will readily recognize that other hardware and functions (e.g., encoders and decoders, drive circuits, glue logic, Global Positioning System (GPS) circuits, crystal oscillators, phase-locked loops (PLLs), etc.) may also be included.

[0041] The first communication circuit 241 and antenna 251 are configured for communication (transmitting and / or receiving) over communication link 141, and the second communication circuit 242 and antenna 252 are configured for communication over communication link 142. In some embodiments, antennas 251 and 252 may be a single shared antenna (e.g., capable of transmitting and receiving via NFC and BT frequencies). Communication circuits 241 and 242 may be implemented as one or more chips and / or components (e.g., transmitters, receivers, transceivers, encoders, decoders, and / or other communication circuits) that perform functions for communication over communication links 141 and 142, respectively.

[0042] Antennas 251 and 252 may be configured as required by the application and communication protocol. Antennas 251 and 252 may have the same or different configurations and may be, for example, printed circuit board (PCB) wiring antennas, ceramic antennas, or discrete metal antennas. Antennas 251 and 252 may be configured as unipolar antennas, dipole antennas, F-type antennas, loop antennas, etc.

[0043] The processor 206 may include one or more processors, microprocessors, controllers, and / or microcontrollers (each of which may be distributed (and partially) across individual chips or multiple different chips), where the processor 206 includes mounted memory 203. The processor 206 may interface with communication circuits 241 and 242 and perform other functions that enable analog-to-digital conversion, encoding and decoding, digital signal processing, and conversion of data signals into a format suitable for supplying to the communication circuits 241 and 242 (which may then wirelessly transmit those signals) (e.g., in-phase and quadrature). The processor 206 may also interface with communication circuits 241 and 242 and perform the inverse functions necessary to receive wireless transmissions and convert them into digital data or information.

[0044] The processor 206 can execute software instructions stored in memory 203 or 210. These instructions allow the processor 206 to send signals to communication circuits 241 and 242, read and process received signals, read input from input component 121, display data or information on display 122, read input from display 122 (in the case of a touchscreen), process data or information received from other devices (e.g., sample data, calibration information, synchronization information received from OBD 102), and perform tasks to maintain synchronization with OBD 102.

[0045] Memory 210 may be shared by one or more of the various functional units within the reader 120, or distributed among two or more of them (for example, as separate memories on different chips). Memory 210 may also be a separate chip itself. Memories 203 and 210 are persistent and may be volatile memory (e.g., RAM) and / or non-volatile memory (e.g., ROM, flash memory, F-RAM).

[0046] The power supply 216 may include one or more batteries, which may be rechargeable or disposable. The power management circuit 218 may regulate battery charging, monitor the use of the power supply 216, increase output, perform DC conversion, etc.

[0047] The reader 120 may include or integrate a drug delivery device (e.g., insulin) to share a common housing. An example of a drug delivery device may include a drug pump (e.g., a wearable pump for delivering basal and bolus insulin) having a cannula that is inside the body and allows for infusion over multiple hours or days. When combined with a drug pump, the reader 120 may include a drug storage unit, a pump connectable to a transfer tube, and an infusion cannula. The pump can infuse the drug from the storage unit into the body of a diabetic patient through the cannula inserted via a tube. Another example of a drug delivery device that may be included in (or integrated with) the reader 120 includes a portable injector (e.g., an insulin pen) that is inserted into the skin and then removed each time. When combined with a portable injector, the reader 120 may include a needle, a cartridge containing the drug, an interface for controlling the amount of drug delivered, and an actuator to initiate the infusion. This device can be used repeatedly until the drug is depleted. Once the drug is depleted, the combined device may be discarded or the cartridge replaced with a new one. In this case, the combination device can be reused repeatedly. The needle can be replaced after each injection.

[0048] This combination device can function as part of a closed-loop system (e.g., an artificial pancreas system that does not require user intervention for operation), part of a semi-closed-loop system (e.g., an insulin loop system that occasionally requires user intervention for operation, such as confirming changes in dosage), or as an open-loop system. For example, the sample level of a diabetic patient can be repeatedly and automatically monitored by the OBD102, the obtained sample level can be communicated to the reader 120, and an appropriate drug dosage to control the diabetic patient's sample level can be automatically determined and delivered to the diabetic patient's body. Software instructions for controlling the pump and the amount of insulin delivered can be stored in the memory 203 and / or 210 of the reader 120 and executed by the processing circuit 206. These instructions can also cause the calculation of drug delivery amount and duration (e.g., bolus infusion and / or basal infusion profile) based on sample level measurements obtained directly or indirectly from the OBD102. In some embodiments, the OBD102 can determine the drug dosage and communicate it to the reader 120.

[0049] Embodiment of a device worn on the body Figure 3A is a block diagram illustrating an embodiment of the OBD102 having a sample sensor 104 and a sensor electronic circuit (including a sample monitoring circuit). The sensor electronic circuit can be implemented on one or more semiconductor chips, such as application-specific integrated circuits (ASICs), off-the-shelf (OTS) chips, or programmable devices (e.g., PGAs, FPGAs). The OBD102 comprises a high-level functional unit including an analog front-end (AFE) 302, a power management (or control) circuit 304, a processor or processing circuit 306, a memory 308, a first communication circuit 341, and a second communication circuit 342. In this embodiment, both the AFE 302 and the processor 306 are used as sample monitoring circuits, but in other embodiments, either circuit (or the other circuit) may perform the sample monitoring function.

[0050] The OBD102 is implemented through a highly interconnected system, with the power supply 312 coupled to the components shown in Figure 3A. These components that communicate or receive data, information, or commands (e.g., AFE302, power management circuit 304, processor 306, memory 308, first communication circuit 341, and second communication circuit 342) may be communicatively coupled to all other such components, for example, via one or more communication connections or bus 320. Figure 3A is a simplified diagram of typical hardware and functions present in the OBD102, and those skilled in the art will readily recognize that other hardware and functions (e.g., encoders / decoders, drive circuits, glue logic, crystal oscillators, phase-locked loops (PLLs)) may also be included.

[0051] Communication circuits 341 and 342 may be coupled to on-chip or off-chip antennas 351 and 352, respectively. The first communication circuit 341 and antenna 351 are configured for communication (transmit and / or receive) over communication link 141, and the second communication circuit 342 and antenna 352 are configured for communication over communication link 142. In some embodiments, antennas 351 and 352 may be a single shared antenna (e.g., capable of transmitting and receiving via NFC and BT frequencies). Communication circuits 341 and 342 may be implemented as one or more components (e.g., transmitters, receivers, transceivers, passive circuits, encoders, decoders, and / or other communication circuits) that perform functions for communication over communication links 141 and 142.

[0052] In some embodiments, but not limited to, the communication circuit 341 passively generates and propagates a response transmission to the second device (e.g., when link 141 is an NFC link) using only the power obtained from a transmission received from a second device (e.g., reader 120). In these and other embodiments, the communication circuit 342 actively generates and propagates a transmission to the second device using power from the OBD power supply 312. The active communication circuit 342 allows the OBD 102 to generate transmissions spontaneously (e.g., without receiving requests, polling signals, timing signals, etc., from the second device) and when prompted by another device.

[0053] The processor 306 may include one or more processors, microprocessors, controllers, and / or microcontrollers (each of which may be distributed (and partially distributed) across individual chips or multiple different chips). The processor 306 may interface with the communication circuits 341 and 342 and perform other functions that enable analog-to-digital conversion, encoding and decoding, digital signal processing, and conversion of data signals into a format suitable for supplying to the communication circuits 341 and 342 (which may then wirelessly transmit those signals) (e.g., in-phase and quadrature). The processor 306 may also interface with the communication circuits 341 and 342 and perform the inverse functions necessary to receive wireless transmissions and convert them into digital data or information.

[0054] The processor 306 can execute software instructions stored in memory 308. These instructions allow the processor 306 to cause communication circuits 341 and 342 to transmit communications generated by the processor 306, read and process received transmissions, adjust the timing of the timing circuit 310, collect temperature information from the temperature sensor, record and / or process measurements from the sample sensor 104, monitor the collected sample data to determine actual or possible alarm conditions, generate alarm instruction transmissions and send them to the communication circuit 342, process data or information received from other devices (e.g., the reader 120), and perform tasks to maintain synchronization with the reader 120.

[0055] Memory 308 may be shared by various components within the OBD 102 or distributed among two or more of them. Memory 308 may also be a separate chip itself. Memory 308 may be persistent, volatile, and / or non-volatile memory. The OBD 102 may include an optional temperature (or other environmental factor) sensor (not shown) and a power supply 312, which may be a coin cell battery or the like. The AFE 302 interfaces with the in vivo sample sensor 104 to receive measurement data, convert it to digital format, and output it to the processor 306. In some embodiments, the processor 306 can process the data in any manner described elsewhere in this document. This data may then be supplied to communication circuits 341 and 342 via antennas 351 and 352 for transmission to, for example, a reader 120 (not shown). The reader 120 requires minimal further processing by a resident software application to display the data. Antennas 351 and 352 may be configured as required by the application and communication protocol. Antennas 351 and 352 may have the same or different configurations and may be, for example, printed circuit board (PCB) wiring antennas, ceramic antennas, or discrete metal antennas. Antennas 351 and 352 may be configured as unipolar antennas, dipole antennas, F-type antennas, loop antennas, etc.

[0056] Figure 3B is a block diagram illustrating another embodiment of the OBD102, where the OBD102 includes two semiconductor chips 301 and 361. Chip 301 is an ASIC including an AFE 302 and a communication circuit 341 for the NFC link 141. Chip 361 is a chip including a processor 306, memory 308, a communication circuit 342 for the BT link 142, and a power management circuit 304. The communication interface 320 can be configured in any desired way. In one embodiment, chip 361 is a Bluetooth® or BLE wireless chip, and the communication interface 320 is a serial interface such as a Serial Peripheral Interface (SPI). In other embodiments, the interface 320 is a parallel interface.

[0057] Figures 3A and 3B illustrate embodiments of the OBD102 capable of forming multiple communication links 141 and 142, but all embodiments described in this document can be implemented using an embodiment of the OBD102 capable of forming only one communication link.

[0058] Communication embodiment that compensates for processing delay Communication received by OBD102 may include one or more commands to cause OBD102 to operate. These operations may include, for example, connecting or disconnecting power to the internal circuitry, transitioning from a zero-power or low-power state to a relatively higher power state, activating sensor 104 (e.g., by applying a bias voltage to one or more electrodes), performing sample data measurement, reading data stored in memory 308 (e.g., measured sample data, data identifying OBD102 (e.g., software version, serial number, etc.)), performing diagnostics, or setting up Bluetooth® pairing. These commands may be initiated by the user or automatically transmitted by the transmitter as part of a software routine. Commands may be defined by applicable standards or may be custom commands requesting a custom response.

[0059] The received communication often requests a reply from the reader 120. If the command is sent via the NFC link 141, the transmitting device is very close to the OBD 102. Otherwise, the transmitting device is within range of the OBD 102. For ease of explanation, the transmitting device is described in this document as the reader 120.

[0060] After receiving one or more commands, the OBD102 uses its internal hardware, software, or a combination thereof to generate a response for transmission to the reader 120. In some embodiments, as part of the process of gathering the information necessary to generate the response, the OBD102 may communicate with other devices attached to or near the user's body, or even with other devices at a distance. The amount of time required for the OBD102 to generate the response depends on several factors, such as the amount of processing required to generate the response, the speed of the hardware and / or software responsible for generating the response, and the amount of data required for the response.

[0061] Some communication protocols have timing constraints or requirements that a receiving device allocates a finite amount of time to respond. These protocols can be industry standard protocols or custom protocols. For example, in an embodiment where communication transmitted over NFC link 141 conforms to the ISO 15693 standard, the communication must be transmitted within the maximum amount of time that the standard allocates for the receiving device to respond. For example, most NFC commands, including Read Multiple Block commands, Read Single Block commands, custom commands, and proprietary commands, must be responded to within a set time limit. For example, ISO 15693 specifies that a command must be responded to within 323 microseconds (μs) from the time the receiving device receives the command. Other standards may set other time limits, and the ISO 15693 standard may be revised to assign different time limits.

[0062] In some cases, the OBD102 may require more time than the set time limit to generate and transmit a response. This processing delay may result in a violation of the set time limit and non-compliance with the standard. This may present a specific problem, as if the reader 120 is a commercially available smartphone, the smartphone may treat this violation as an error or malfunction and prevent the completion of communication.

[0063] Embodiments disclosed herein can compensate for this processing delay and maintain compliance by transmitting one or more responses containing dummy data. The dummy data is transmitted to maintain compliance but is not data that responds to the command in whole or in part. This data may be a predetermined bit sequence programmed into the reader or understood by the reader as representing dummy data. Alternatively, this data may be pseudorandom data generated according to an algorithm or a code representing dummy data so that it is understood as pseudorandom data when decoded by the reader. In another embodiment, this data may be predetermined or random and its status as dummy data may be indicated, for example, by a flag located in the payload header. Thus, the reader 120 can discard the data after recognizing the presence of the flag.

[0064] Figure 4A is a flowchart illustrating an embodiment of communication method 400 by a receiving device, described here as OBD102. In 402, OBD102 receives a transmission containing a command from a transmitting device, such as a reader 120. In 404, OBD102 processes the received command. This may include any steps necessary to decode, decode, and / or verify the received command, as well as any steps necessary to generate information or data (response data) in response to the command for transmission to the reader 120. In this embodiment, it is assumed that step 404 requires more time than allocated by the communication protocol to send a response to the reader 120. Therefore, in 406, OBD102 sends dummy data as a response to the reader 120. This is done before the end of the set time limit for the response to maintain compliance. The set time limit is reset, and a new (second) period for the response begins. Before the end of the second period, OBD102 sends another response, including the response data if available. If the response data is not ready, OBD102 can send dummy data to the reader 120 again, resetting the set time limit, and OBD102 repeats this until the response data is ready for transmission. In 408, the response data is sent to the reader 120 in one or more parts depending on the payload size and protocol constraints, and the end of the response may be indicated by sending an end-of-frame (EOF) column or similar to the reader 120.

[0065] Figure 4B is a flowchart illustrating an embodiment of a communication method 420 by a transmitting device, which is described here as a reading device 120. At 422, the reading device 120 sends a command to the OBD 102. At 424, the reading device 120 receives a response from the OBD 102 within the time allocated by the communication protocol. At 426, the reading device 120 reads the received response and determines whether it is dummy data or response data. In embodiments where the dummy data is a predetermined sequence or code (e.g., AAAA, FFFF, etc.), this determination may be made by comparing the received response with a known predetermined sequence or code to determine whether it matches the dummy data. If the received response does not match and meets other criteria for valid data (e.g., satisfies cyclic redundancy check, is in proper format, etc.), the received response may be determined to be response data. In embodiments where dummy data is generated by other methods, such as a dummy data algorithm, or indicated as dummy data by a flag in the header, the reader 120 can apply an appropriate method to check whether the received response is dummy data or response data.

[0066] If the received response is response data, the reader 120 processes the data accordingly in step 428. This may include storing the response data, displaying the response data to the user, communicating the response data to another device, or any number of other operations that are obvious to those skilled in the art. If the received response is dummy data, method 420 returns and may wait for another response in step 424. The dummy data may be discarded or ignored by the reader 120. The process of receiving a response in step 424 and determining in step 426 whether the received response is dummy data or response data can be repeated indefinitely until response data is received, or until the total time for the completion of sequential communication is reached, or the system 100 times out, or another event occurs that terminates method 420.

[0067] Figure 4C is a flowchart illustrating another embodiment of communication method 440 by a transmitting device, described here as a reader 120. In 442, the reader 120 sends a command to the OBD 102. In 444, the reader 120 receives N sequential responses from the OBD 102. Each sequential response is within a time allocated by the communication protocol. For example, if the protocol sets a time limit of 1 millisecond, each sequential response is received within 1 millisecond of the previous response. In this embodiment, the reader 120 does not individually determine whether all received responses are dummy data or response data, but is programmed to recognize the appropriate number of responses to be received in order to form a complete set of responses for communication from the OBD 102. For example, the reader 120 may be programmed to recognize or expect that a certain command XYZ that the reader 120 sent to the OBD 102 should result in the receipt of E individual responses from the OBD 102, where E is 1 or greater. In 446, the reader 120 determines whether the number of received responses N is equal to the expected number of responses E. If so, the reader 120 treats the E responses as response data (assuming the responses satisfy all other verification criteria) and can act accordingly in 448 (e.g., store the data, display the data, etc.).

[0068] If the number of responses N received is greater than the expected number of responses E, in step 450 the reader 120 may treat the first N min E (NE) responses as dummy data. This may include ignoring or discarding the first (NE) responses. This may also optionally include reading the first (NE) responses and verifying whether each is dummy data according to the dummy data criteria of the individual embodiment, such as comparing it to a known dummy data code or referring to a dummy data flag. Since E responses remain, the reader 120 may proceed to step 448 and again treat the remaining E responses as response data, assuming that other verification criteria are met, and act accordingly.

[0069] Figure 4D is a flowchart of another embodiment of method 460 of communication between a transmitting device and a receiving device, described here as a reader 120 and an OBD 102, respectively. In 462, the reader 120 sends a command to the OBD 102, and in 464, the OBD 102 receives it and begins processing. In this embodiment, the OBD 102 is programmed to send a predetermined number of P dummy data responses to the reader 120 before sending the response data in the P+1 (and subsequent) responses. The predetermined number of dummy data responses is determined based on the expected amount of time required for the OBD to generate the response data. This predetermined number may be determined and verified by testing during the system development process. For example, if the set response duration is 1 millisecond (ms) and the maximum time required for the OBD 102 to generate the response data is calculated to be 4.2 ms, then the predetermined number P may be set to 4, and the OBD 102 may be programmed to send four responses, each containing dummy data, and begin sending the response data in the fifth response. Similarly, the reader 120 can be programmed to expect four responses, each containing dummy data, before receiving response data in the fifth response.

[0070] Referring to Figure 4D, at 466, OBD102 sends N responses to the reader 120, which receives them at 468. At 470, the reader 120 may treat the first P responses as dummy data and the remaining N minus P (NP) responses as response data. This may include ignoring or discarding the first P responses. It may also optionally include reading the first P responses and verifying that they are dummy data. The reader 120 may read the P+1-th response as the first response containing the response data. Assuming that the response data satisfies the other verification criteria, the reader 120 may process the response data accordingly as described in this document.

[0071] In some embodiments, the system 100 may be configured such that different commands have a different number of predetermined responses (used based on different processing times for different commands). For example, a first command may correspond to three predetermined dummy data responses, and a second command may correspond to four predetermined dummy data responses, and so on. In these embodiments, both the reader and the body-worn device are preferably programmed to know and use an appropriate number of predetermined responses for each command, and the body-worn device may be programmed to read a received command, determine an appropriate number of predetermined responses, and transmit in response to that command. Such a configuration allows for more efficient use of communication bandwidth.

[0072] The embodiments described with respect to Figures 4A–4D are implemented in systems where the time to process an received command may exceed the time allocated for the response by the protocol or standard. These embodiments can be used with any system where such extensive processing delays may occur, regardless of the reason for the processing delay. The following embodiments are intended to serve as non-exhaustive examples of configurations or situations in which processing delays may exceed the allocated time, and many other examples are possible and within the scope of the subject matter described herein.

[0073] Referring again to the embodiment in Figure 3B where link 141 is an NFC link, in one example, some NFC communications received by communication circuit 341 may be processed and responded to directly by ASIC 301 without coordination with chip 361. However, some commands may require a response generated by a more robust entity, such as processor 306. In those examples, ASIC 301 may forward the relevant portion of the received communication to chip 361 for response generation. Chip 361 then generates response data and, when available, may output that response data to ASIC 301 to be sent as one or more responses from OBD 102 via NFC link 141.

[0074] The reader 120 may be programmed or configured to recognize a response in which the payload contains byte values ​​(e.g., AAAA, FFFF) that match a predetermined payload as dummy data, ignore these responses (e.g., do not store them in memory), and continue monitoring the NFC link 141 to request the transmission of a response containing payload data other than dummy data.

[0075] Figure 5A is an information flow diagram illustrating an embodiment 500 for handling wireless communication in order to avoid violating the set time limit for responses. This embodiment 500 is described in the context of an OBD102 configured similarly to Figure 3B, but is not limited thereto. The arrows in Figure 5A illustrate wireless transmission from the reader 120 to the chip 301 of the OBD102 and wireless transmission back to the reader 120, and internal wired communication from the chip 301 to the chip 361 in the OBD102 and back. The wired communication may be conducted through an interface 320 configured as, for example, SPI.

[0076] At 501, a custom command is transmitted from the reader 120 and received by the chip 301 of the OBD 102. At 502, the received custom command (e.g., the relevant part or information representing the received command) is then transferred from chip 301 to chip 361 via interface 320. Chip 361 then begins the process of reading the command at 507 and generating and outputting appropriate response data. This may include executing an algorithm, retrieving data from memory, and / or performing other functions.

[0077] Simultaneously, chip 301 prepares for response transmission by using the circuitry on chip 301 (e.g., ASIC circuitry). In 503, chip 301 transmits a response, including a Frame Start (SOF) indicator, to the reader 120 via link 141. Any flags (in 504) and / or other parameters (in 505) (which can be easily determined) for the response packet header are also returned to the reader 120 within the set time limit for response transmission.

[0078] As the set time limit approaches its end, assuming that chip 361 has not yet generated a response to the custom command, at 506 chip 301 sends dummy data to the reader 120. This process continues, with a payload containing dummy data being sent to the reader 120 before each subsequent time limit expires. This loop may continue repeatedly until 508 chip 361 outputs a response data payload to chip 301. Upon recognition of the receipt of the response data payload by chip 301, chip 301 instructs the reader 120 to send this response data payload (completing the transmission using as many consecutive response packets as necessary and permitted). At 510 chip 301 sends an error detection bit (e.g., cyclic redundancy check (CRC)), followed at 511 by an end-of-frame (EOF) indicator.

[0079] Figure 5B is an information flow diagram illustrating an embodiment 550 for handling wireless communication in order to avoid response time limit violations. This embodiment 550 is described in the context of an OBD102 configured similarly to Figure 3B, but is not limited to this embodiment 550.

[0080] In 551, the custom command is sent from the reader 120 and received by the chip 301 of the OBD 102. In 552, the chip 301 requests information from the chip 361 necessary to formulate the response data. For example, the requested information could be random numbers generated by a random number generator in the chip 361 to encrypt the response data before sending it back to the reader 120. In 553, the chip 361 processes the requested information and in 554 provides it to the chip 301. In 555, the chip 301 receives the requested information from the chip 361 and in 556 begins processing the response data. In other embodiments, dummy data may also be encrypted before transmission.

[0081] Simultaneously, chip 301 prepares to send a response by using the circuitry on chip 301 (e.g., ASIC circuitry). At 556, chip 301 sends a response, including a Frame Start (SOF) indicator, to the reader 120 via link 141. Any flags (at 558) and / or other parameters (at 560) (which can be easily determined) for the response packet header are also sent back to the reader 120 within the set time limit for sending the response.

[0082] As the set time limit approaches its end, assuming that chip 361 has not yet generated a response to the custom command, at 562 chip 301 sends dummy data to the reader 120. This process continues, with a payload containing dummy data being sent to the reader 120 before each subsequent time limit expires. This loop may continue repeatedly until 563 chip 301 has completed processing (e.g., generating and encrypting the response data) and the response data is ready to be sent. Next, at 564 chip 301 causes this response data payload to be sent to the reader 120 (completing the transmission using as many consecutive response packet transmissions as necessary and allowed). At 566 chip 301 sends an error detection bit (e.g., cyclic redundancy check (CRC)), followed at 568 by an end-of-frame (EOF) indicator.

[0083] In addition to the differences described above, in any and all embodiments described herein, a response containing dummy data may be a response that contains only dummy data in the payload portion of the response. This may be indicated by a flag in the header portion of a bit string or data frame contained within the payload that corresponds to a predetermined code (e.g., AAAA, FFFF, ABCD, etc.) (indicating that the data in the payload is dummy data or contains only dummy data).

[0084] Various aspects of this subject matter are described below, with an emphasis on the interrelationships and interchangeability of the embodiments described above, and by reconsidering and / or supplementing the embodiments described above. In other words, unless otherwise stated or logically unlikely, emphasis is placed on the fact that each feature of the embodiments is combinable with each and all other features.

[0085] In many embodiments, a communication method is provided within a specimen monitoring system including a body-worn device and a reader. The method includes wirelessly receiving a command from a reader using a body-worn device, wirelessly transmitting at least one first response containing dummy data to the reader, and wirelessly transmitting at least one second response containing data in response to the command to the reader.

[0086] In some embodiments, the method further includes processing a received command while transmitting at least one first response to a reader. Processing a received command may include generating data in response to the command and encrypting the data in response to the command. At least one second response transmitted to the reader may include encrypted data in response to the command. At least one first response transmitted to the reader may include encrypted dummy data.

[0087] In some embodiments, the method includes determining whether data in response to a command can be transmitted before the end of the set response time limit. If the method determines that data in response to a command cannot be transmitted before the end of the set response time limit, it may further include sending a first response to the reader. If the method determines that data in response to a command can be transmitted before the end of the set response time limit, it may further include sending a second response to the reader.

[0088] In some embodiments, the method may further include transmitting a plurality of first responses to a reader. Each first response contains dummy data and is transmitted before the end of a set response time limit.

[0089] In some embodiments, dummy data may be a predetermined code, indicated by a flag in the header of at least one first response, or be pseudo-random data.

[0090] In some embodiments, the method may further include generating dummy data according to a dummy data algorithm.

[0091] In some embodiments, the device worn on the body may include a first semiconductor device and a second semiconductor device communicatively coupled to the first semiconductor device via a communication interface. The communication interface may be a serial peripheral interface. The method may further include sending a request for response data from the first semiconductor device to the second semiconductor device via the communication interface, the second semiconductor device generating the response data, and sending the response data from the second semiconductor device to the first semiconductor device via the communication interface before transmitting at least one second response to a reader. The first semiconductor device may be configured to format data according to a Near Field Communication (NFC) protocol. The second semiconductor device may be configured to format data according to a Bluetooth® communication protocol.

[0092] In some embodiments, the method may further include processing a received command and wirelessly transmitting at least one third response to the reader before wirelessly transmitting at least one first response to the reader. The at least one third response may include at least one of a frame start indicator, a flag, or a communication parameter. The method may further include wirelessly transmitting at least one fourth response after wirelessly transmitting at least one second response. The at least one fourth response may include error detection information or a frame end indicator.

[0093] In some embodiments, wireless communication between a device worn on the body and a reader follows a Near Field Communication (NFC) protocol.

[0094] In many embodiments, a body-worn device for a specimen monitoring system is provided. The body-worn device includes a communication circuit configured to wirelessly receive commands and wirelessly transmit one or more responses, and a processing circuit configured to generate dummy data and data in response to commands, wherein the body-worn device is configured to wirelessly transmit at least one first response containing dummy data and at least one second response containing data in response to commands.

[0095] In some embodiments, a device worn on the body may be configured such that a processing circuit processes a received command while a communication circuit transmits at least one first response. The processing circuit may be configured to encrypt data in response to a command and output the encrypted response data to the communication circuit. The processing circuit may be configured to encrypt dummy data and output the encrypted dummy data to the communication circuit.

[0096] In some embodiments, a device worn on the body may be configured to determine whether data responding to a command can be sent before the end of a set response time limit.

[0097] In some embodiments, the processing circuit may be configured to send a first response after determining that data in response to a command cannot be sent, and before the end of the set response time limit.

[0098] In some embodiments, the processing circuit may be configured to send a second response after determining that data in response to a command is available for transmission, and before the end of the set response time limit.

[0099] In some embodiments, a device worn on the body may be configured to transmit multiple first responses. Each first response contains dummy data and is transmitted before the end of a set time limit for the response.

[0100] In some embodiments, dummy data may be a predetermined code, indicated by a flag in the header of at least one first response, pseudo-random data, or generated according to a dummy data algorithm.

[0101] In some embodiments, the device worn on the body may include a first semiconductor device and a second semiconductor device that is communicatively coupled to the first semiconductor device via a communication interface. The communication interface may be a serial peripheral interface. A first portion of the processing circuit may be located within the first semiconductor device, and a second portion of the processing circuit may be located within the second semiconductor device. The first semiconductor device may be configured to output a request to the second semiconductor device via the communication interface for response data. The second semiconductor device may be configured to generate response data and output that response data to the first semiconductor device via the communication interface. The first semiconductor device may be configured to format data according to a Near Field Communication (NFC) protocol. The second semiconductor device may be configured to format data according to a Bluetooth® communication protocol.

[0102] In some embodiments, the communication circuit is configured to receive and transmit wirelessly according to a Near Field Communication (NFC) protocol.

[0103] In some embodiments, the processing circuit is communicatively coupled to a memory, which stores a number of instructions executed by the processing circuit.

[0104] In many embodiments, a communication method is provided within a specimen monitoring system including a body-worn device and a reader. The method includes wirelessly transmitting a command from the reader to the body-worn device, wirelessly receiving at least one first response containing dummy data from the body-worn device, and wirelessly receiving at least one second response containing data responding to the command from the body-worn device.

[0105] In some embodiments, the method may further include a reader determining whether each of at least one first response contains dummy data.

[0106] In some embodiments, the method may further include a reader determining whether each of at least one second response contains data in response to a command.

[0107] In some embodiments, the method may further include processing data in response to a command by a reader. Processing data in response to a command may include storing the data in response to the command or displaying the data in response to the command.

[0108] In some embodiments, the method may further include a reader determining whether the total number N of received responses (at least one first response and at least one second response) is greater than the expected number E of responses. The method may further include the reader treating the first (NE) responses as dummy data, and the reader treating the remaining E responses as containing data in response to a command. The method may further include the reader reading the first (NE) responses and confirming that those responses contain dummy data. The method may further include the reader decoding at least one second response received. The method may further include the reader decoding at least one first response received. The dummy data may be a predetermined code, indicated by a flag in the header of at least one first response, pseudo-random data, or generated according to a dummy data algorithm.

[0109] In some embodiments, the reader communicates with a device attached to the body.

[0110] In some embodiments, the reader wirelessly receives and transmits data in accordance with the Near Field Communication (NFC) protocol. The method may further include wirelessly receiving data from a device worn on the body in accordance with the Bluetooth® protocol.

[0111] In many embodiments, a reader for a sample monitoring system is provided. The reader includes a communication circuit configured to wirelessly transmit a command and wirelessly receive one or more responses, and a processing circuit configured to determine whether each received response contains dummy data or data in response to a command.

[0112] In some embodiments, the processing circuit is configured to process data in response to a command.

[0113] In some embodiments, the processing circuit is configured to store or display data in response to a command.

[0114] In some embodiments, the processing circuit is configured to ignore or discard dummy data.

[0115] In some embodiments, the processing circuit is configured to decode each received response.

[0116] In some embodiments, dummy data may be a predetermined code, indicated by a flag in the header of at least one first response, pseudo-random data, or generated according to a dummy data algorithm.

[0117] In some embodiments, the reader is configured to communicate with a device worn on the body.

[0118] In some embodiments, the communication circuit is configured to transmit and receive wirelessly according to the Near Field Communication (NFC) protocol. The communication circuit is a first communication circuit, and the reader includes a second communication circuit configured to transmit and receive wirelessly according to the Bluetooth® protocol.

[0119] In some embodiments, the processing circuit is communicatively coupled to a memory, which stores a number of instructions that can be executed by the processing circuit.

[0120] In many embodiments, a reader for a sample monitoring system is provided. The reader includes a communication circuit configured to wirelessly transmit commands and wirelessly receive one or more responses, and a processing circuit configured to determine whether the total number N of received responses is greater than the expected number E of responses.

[0121] In some embodiments, the processing circuit may be configured to treat the first (NE) responses as dummy data and the remaining E responses as containing data in response to a command. The processing circuit may be configured to read the first (NE) responses and verify that they contain dummy data. The processing circuit may be configured to process the data in response to a command. The processing circuit may be configured to store or display the data in response to a command. The processing circuit may be configured to ignore or discard the first (NE) responses without verifying that the first (NE) responses contain dummy data. The processing circuit may be configured to decode each received response.

[0122] In some embodiments, dummy data may be a predetermined code, indicated by a flag in the header of at least one first response, pseudo-random data, or generated according to a dummy data algorithm.

[0123] In some embodiments, the reader is configured to communicate with a device worn on the body.

[0124] In some embodiments, the communication circuit is configured to transmit and receive wirelessly according to the Near Field Communication (NFC) protocol. The communication circuit is a first communication circuit, and the reader may include a second communication circuit configured to transmit and receive wirelessly according to the Bluetooth® protocol.

[0125] In many embodiments, a communication method is provided within a specimen monitoring system including a body-worn device and a reader. The method includes wirelessly receiving a command from a reader via a body-worn device, wirelessly transmitting a predetermined number of P first responses from the body-worn device to the reader, each first response containing dummy data, and wirelessly transmitting at least one second response from the body-worn device to the reader, each second response containing data in response to the command.

[0126] In some embodiments, the method may further include processing the received command while transmitting a predetermined number of first responses to a reader.

[0127] In some embodiments, processing an incoming command may include generating data in response to the command and encrypting the data in response to the command. At least one second response sent to the reader may include encrypted data in response to the command. Each of a predetermined number of first responses sent to the reader may include encrypted dummy data.

[0128] In some embodiments, the method further includes counting the number of responses received from a device attached to the body by a reader. The method may further include treating the P+1th response as containing data in response to a command. The method may further include not verifying that the first P received responses contain dummy data.

[0129] In some embodiments, the method may further include reading a command received by a body-worn device and wirelessly transmitting a predetermined number of P first responses corresponding to the received command. The received command is one of a plurality of commands, and the reader and the body-worn device are programmed to identify a precise number of predetermined responses based on that command.

[0130] In some embodiments, wireless communication between a device worn on the body and a reader follows a Near Field Communication (NFC) protocol.

[0131] In many embodiments, a specimen monitoring system is provided. The specimen monitoring system comprises a body-worn device including a communication circuit and a processing circuit, and a reading device including a communication circuit and a processing circuit. The body-worn device is configured to wirelessly receive a command from the reading device, to wirelessly transmit a predetermined number of P first responses to the reading device, each first response containing dummy data, and to wirelessly transmit at least one second response to the reading device containing data responding to the command.

[0132] In some embodiments, a device worn on the body is configured to process a received command while transmitting a predetermined number of first responses to a reader. The processing circuit of the device worn on the body may be configured to generate data in response to the command and to encrypt the data in response to the command. The processing circuit of the device worn on the body may be configured to encrypt dummy data and to transmit the encrypted dummy data.

[0133] In some embodiments, the processing circuit of the reader may be configured to count the number of responses received from a device attached to the body. The processing circuit of the reader may be configured to treat the P+1th response as containing data in response to a command. The processing circuit of the reader may be configured to ignore or discard the first P received responses without verifying that each of the first P received responses contains dummy data.

[0134] In some embodiments, the processing circuit of a body-worn device is configured to read a received command and wirelessly transmit a predetermined number of P first responses corresponding to the received command.

[0135] In some embodiments, the received command is one of several commands, and the reader and the body-worn device are programmed to identify a precise number of predetermined responses based on that command.

[0136] In some embodiments, the communication circuit of a device worn on the body and the communication circuit of a reader are configured to communicate according to a Near Field Communication (NFC) protocol.

[0137] In many embodiments, a method for communication within a specimen monitoring system including a body-worn device and a reader is provided. The method includes: receiving a transmission from a reader in the body-worn device that includes a custom command and is formatted according to a first communication protocol; communicating the custom command from a first semiconductor chip in the body-worn device to a second semiconductor chip in the body-worn device; causing the body-worn device to transmit a first data payload, including dummy data, from the body-worn device to the reader within a set response time limit according to the first communication protocol; communicating a response data payload from the second semiconductor chip to the first semiconductor chip; and transmitting the response data payload from the body-worn device to the reader, wherein the first semiconductor chip includes a communication circuit adapted for communication according to the first communication protocol, and the second semiconductor chip includes a processor.

[0138] For each and all embodiments of the methods described herein, systems and apparatus capable of carrying out each of these embodiments are included within the scope of this disclosure. For example, embodiments of OBDs are disclosed, and these apparatuses may have one or more sensors, specimen monitoring circuits (e.g., analog circuits), memory (e.g., for storing command sets), power supply, communication circuits, transmitters, receivers, processors, and / or controllers (e.g., for executing commands). These can or can enable the execution of any and all method steps. These OBD embodiments may be used to carry out the steps of any and all of the methods described herein that are performed by the OBD.

[0139] In all of the above embodiments, the actions performed by the body-worn device may be performed or made to be performed by a processing circuit of the body-worn device that executes one or more instructions stored in the memory of the body-worn device. Similarly, in all of the above embodiments, the actions performed by the reader may be performed or made to be performed by a processing circuit of the reader that executes one or more instructions stored in the memory of the reader.

[0140] The computer program instructions for performing the operations described in this book may be stored in any persistent memory described herein and executed by a processing circuit communicatively coupled thereto. The computer program instructions may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, JavaScript, Smalltalk, C++, C#, Transact-SQL, XML, and PHP, and traditional procedural programming languages ​​such as C or similar programming languages. The program instructions may be executed entirely or partially on the user's computer as a standalone software package, or partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or wide area network (WAN), or the connection may be to an external computer (e.g., via the Internet using an Internet service provider).

[0141] Furthermore, all features, elements, components, functions, and steps described in any embodiment provided herein are intended to be freely combined and substituted with those of any other embodiment. If a feature, element, component, function, or step is described in relation to only one embodiment, it should be understood that, unless otherwise stated, that feature, element, component, function, or step can be used with all other embodiments described herein. Therefore, this paragraph serves as prior art and support for introducing claims that combine features, elements, components, functions, and steps of multiple different embodiments, or replace features, elements, components, functions, and steps of one embodiment with those of another embodiment, even if such combinations or substitutions are not explicitly stated in the specific examples of this description. Given that a person skilled in the art would readily recognize that all such combinations and substitutions are permissible, it is clearly acknowledged that specifying all possible combinations and substitutions would be an undue burden.

[0142] To the extent that the embodiments disclosed herein include or operate with memory, storage devices, and / or computer-readable media, such memory, storage devices, and / or computer-readable media are persistent. Therefore, if memory, storage devices, and / or computer-readable media are included in one or more claims, such memory, storage devices, and / or computer-readable media are simply persistent.

[0143] As used herein and in the appended claims, unless the context clearly indicates otherwise, the English singular forms "a," "an," and "the" refer to a plurality of objects.

[0144] While the embodiments can take on various variations and alternative forms, specific examples of these are illustrated and described in detail herein. However, these embodiments are not limited to the specific forms disclosed; rather, they should be understood to include all variations, equivalents, and alternatives contained within the gist of this disclosure. Furthermore, any feature, function, step, or element of an embodiment may be described or added to the claims, and negative limitations may be described that define the scope of the claims by features, functions, steps, or elements that are not within that scope.

[0145] Preferred embodiments of the present invention are described below in separate sections.

[0146] Embodiment 1 A communication method within a specimen monitoring system equipped with a device attached to the body and a reading device, The steps include: receiving a command wirelessly from the reading device using the device attached to the body; The steps include wirelessly transmitting at least one first response containing dummy data to the reading device, The steps include: wirelessly transmitting to the reader at least one second response containing data in response to the command; A method that includes this.

[0147] Embodiment 2 The method according to Embodiment 1, further comprising the step of processing the received command while transmitting the at least one first response to the reader.

[0148] Embodiment 3 The step of processing the received command is: The steps include generating the data in response to the command, The steps include: encrypting the data in response to the command; The method according to Embodiment 2, including the method described in Embodiment 2.

[0149] Embodiment 4 The method according to Embodiment 3, wherein the at least one second response transmitted to the reader includes data in response to the command in an encrypted form.

[0150] Embodiment 5 The method according to Embodiment 4, wherein the at least one first response transmitted to the reader includes dummy data in an encrypted form.

[0151] Embodiment 6 The method according to Embodiment 1, further comprising the step of determining whether it is possible to send data in response to the command before the end of the set time limit for the response.

[0152] Embodiment 7 The method according to Embodiment 6, further comprising the step of sending a first response to the reader if it is determined that data to respond to the command cannot be sent before the end of the set time limit for the response.

[0153] Embodiment 8 The method according to Embodiment 6, further comprising the step of sending a second response to the reader if it is determined that data responding to the command can be sent before the end of the set time limit for the response.

[0154] Embodiment 9 The method according to Embodiment 1, further comprising the step of transmitting a plurality of first responses to the reading device, wherein each first response includes dummy data and is transmitted before the end of a set time limit for the responses.

[0155] Embodiment 10 The method according to Embodiment 1, wherein the dummy data is a predetermined code.

[0156] Embodiment 11 The method according to Embodiment 1, wherein the dummy data is indicated by a flag in the header of the at least one first response.

[0157] Embodiment 12 The method according to Embodiment 1, wherein the dummy data is pseudo-random data.

[0158] Embodiment 13 The method according to Embodiment 1, further comprising the step of generating the dummy data according to a dummy data algorithm.

[0159] Embodiment 14 The method according to Embodiment 1, wherein the device attached to the body comprises a first semiconductor device and a second semiconductor device that is communicatively coupled to the first semiconductor device via a communication interface.

[0160] Embodiment 15 The method according to embodiment 14, wherein the communication interface is a serial peripheral device interface.

[0161] Embodiment 16 The steps include: outputting a request for response data from the first semiconductor device to the second semiconductor device via the communication interface; The steps include generating the response data using the second semiconductor device, The steps include outputting the response data from the second semiconductor device to the first semiconductor device via the communication interface before transmitting the at least one second response to the reader, and The method according to Embodiment 14, further comprising the following:

[0162] Embodiment 17 The method according to embodiment 14, wherein the first semiconductor device is configured to format data according to a near-field communication (NFC) protocol.

[0163] Embodiment 18 The method according to Embodiment 14, wherein the second semiconductor device is configured to format data according to the Bluetooth® communication protocol.

[0164] Embodiment 19 The steps include processing the received command, The steps include: transmitting at least one third response wirelessly to the reader before wirelessly transmitting at least one first response to the reader; The method according to Embodiment 1, further comprising the following:

[0165] Embodiment 20 The method according to Embodiment 19, wherein the at least one third response includes at least one of a frame start indicator, a flag, or a communication parameter.

[0166] Embodiment 21 The method according to embodiment 19, further comprising the step of wirelessly transmitting at least one fourth response after wirelessly transmitting at least one second response.

[0167] Embodiment 22 The method according to embodiment 21, wherein the at least one fourth response includes error detection information or a frame end indicator.

[0168] Embodiment 23 The method according to any one of embodiments 1 to 22, wherein the wireless communication between the body-attached device and the reader device follows the Near Field Communication (NFC) protocol.

[0169] Embodiment 24 A device attached to the body for a specimen monitoring system, A communication circuit configured to wirelessly receive commands and wirelessly transmit one or more responses, A processing circuit configured to generate dummy data and data in response to the command. Equipped with, A device to be attached to a body, configured to wirelessly transmit at least one first response containing the dummy data and at least one second response containing data in response to the command.

[0170] Embodiment 25 The device attached to the body is the device according to embodiment 24, wherein the communication circuit is configured to transmit the at least one first response while the processing circuit processes the received command.

[0171] Embodiment 26 The apparatus according to embodiment 25, wherein the processing circuit is configured to encrypt data in response to the command and output the encrypted response data to the communication circuit.

[0172] Embodiment 27 The apparatus according to embodiment 26, wherein the processing circuit is configured to encrypt the dummy data and output the encrypted dummy data to the communication circuit.

[0173] Embodiment 28 The apparatus according to embodiment 24, configured to determine whether data responding to the command can be transmitted before the end of the set time limit for the response.

[0174] Embodiment 29 The apparatus according to embodiment 24, wherein the processing circuit is configured to send the first response before the end of the set response time limit after determining that it is not possible to send data in response to the command.

[0175] Embodiment 30 The apparatus according to embodiment 24, wherein the processing circuit is configured to send the second response before the end of the set response time limit after determining that data in response to the command can be transmitted.

[0176] Embodiment 31 The apparatus according to Embodiment 24, configured to transmit multiple first responses, each first response containing dummy data and transmitted before the end of a set time limit for the response.

[0177] Embodiment 32 The apparatus according to Embodiment 24, wherein the dummy data is a predetermined code, indicated by a flag in the header of the at least one first response, is pseudo-random data, or is generated according to a dummy data algorithm.

[0178] Embodiment 33 The apparatus to be attached to the body comprises a first semiconductor device and a second semiconductor device that is communicatively coupled to the first semiconductor device via a communication interface, as described in Embodiment 24.

[0179] Embodiment 34 The apparatus according to embodiment 33, wherein the communication interface is a serial peripheral device interface.

[0180] Embodiment 35 The apparatus according to embodiment 33, wherein the first part of the processing circuit is located in the first semiconductor device, and the second part of the processing circuit is located in the second semiconductor device.

[0181] Embodiment 36 The apparatus according to embodiment 35, wherein the first semiconductor device is configured to output a request to the second semiconductor device for response data via the communication interface.

[0182] Embodiment 37 The apparatus according to embodiment 36, wherein the second semiconductor device is configured to generate the response data and output the response data to the first semiconductor device through the communication interface.

[0183] Embodiment 38 The apparatus according to any one of embodiments 33 to 37, wherein the first semiconductor device is configured to format data according to the Near Field Communication (NFC) protocol.

[0184] Embodiment 39 The apparatus according to embodiment 38, wherein the second semiconductor device is configured to format data according to the Bluetooth® communication protocol.

[0185] Embodiment 40 The apparatus according to any one of embodiments 24 to 39, wherein the communication circuit is configured to wirelessly receive and transmit according to the Near Field Communication (NFC) protocol.

[0186] Embodiment 41 The apparatus according to any one of embodiments 24 to 40, wherein the processing circuit is communicably coupled to a memory, and the memory stores a plurality of instructions that can be executed by the processing circuit.

[0187] Embodiment 42 A communication method within a specimen monitoring system equipped with a device attached to the body and a reading device, The steps include: wirelessly transmitting a command to the device attached to the body using the aforementioned reading device; The steps include: receiving wirelessly at least one first response containing dummy data from a device attached to the body; The steps include: wirelessly receiving at least one second response containing data in response to the command from a device attached to the body; A method that includes this.

[0188] Embodiment 43 The method according to embodiment 42, further comprising the step of determining whether each of the at least one first response contains dummy data using the reading device.

[0189] Embodiment 44 The method according to embodiment 42, further comprising the step of determining whether each of the at least one second response contains data in response to the command, using the reading device.

[0190] Embodiment 45 The method according to embodiment 44, further comprising the step of processing data in response to the command by the reading device.

[0191] Embodiment 46 The method according to embodiment 45, wherein the step of processing data in response to the command includes the step of storing the data in response to the command or displaying the data in response to the command.

[0192] Embodiment 47 The method according to embodiment 42, further comprising the step of determining by the reading device whether the total number N of at least one first response and at least one second response received is greater than the expected number E of responses.

[0193] Embodiment 48 The method according to Embodiment 47, further comprising the steps of: treating the first (NE) responses as dummy data by the reading device; and treating the remaining E responses as containing data in response to the command by the reading device.

[0194] Embodiment 49 The method according to embodiment 48, further comprising the step of reading the first (NE) responses with the reading device and confirming that those responses contain dummy data.

[0195] Embodiment 50 The method according to any one of embodiments 42 to 49, further comprising the step of decoding the at least one received second response with the reading device.

[0196] Embodiment 51 The method according to embodiment 50, further comprising the step of decoding the at least one received first response with the reading device.

[0197] Embodiment 52 The method according to any one of embodiments 42 to 51, wherein the dummy data is a predetermined code, indicated by a flag in the header of the at least one first response, is pseudo-random data, or is generated according to a dummy data algorithm.

[0198] Embodiment 53 The reading device communicates with a device attached to the body, according to any one of embodiments 42 to 52.

[0199] Embodiment 54 The method according to any one of embodiments 42 to 53, wherein the reader wirelessly receives and transmits according to the Near Field Communication (NFC) protocol.

[0200] Embodiment 55 The method according to Embodiment 54, further comprising the step of wirelessly receiving data from a device worn on the body in accordance with the Bluetooth® protocol.

[0201] Embodiment 56 A reader for a specimen monitoring system, A communication circuit configured to wirelessly transmit commands and wirelessly receive one or more responses, A processing circuit configured to determine whether each received response contains dummy data or data in response to the command. A reading device equipped with [a specific feature].

[0202] Embodiment 57 The apparatus according to embodiment 56, wherein the processing circuit is configured to process data in response to the command.

[0203] Embodiment 58 The apparatus according to embodiment 56, wherein the processing circuit is configured to store or display data in response to the command.

[0204] Embodiment 59 The apparatus according to embodiment 56, wherein the processing circuit is configured to ignore or discard the dummy data.

[0205] Embodiment 60 The apparatus according to any one of embodiments 56 to 59, wherein the processing circuit is configured to decode each received response.

[0206] Embodiment 61 The apparatus according to Embodiment 56, wherein the dummy data is a predetermined code, indicated by a flag in the header of the at least one first response, is pseudo-random data, or is generated according to a dummy data algorithm.

[0207] Embodiment 62 The device according to any one of embodiments 56 to 61, wherein the reading device is configured to communicate with a device attached to the body.

[0208] Embodiment 63 The apparatus according to any one of embodiments 56 to 61, wherein the communication circuit is configured to wirelessly transmit and receive in accordance with the Near Field Communication (NFC) protocol.

[0209] Embodiment 64 The apparatus according to embodiment 63, wherein the communication circuit is a first communication circuit, and the reader device comprises a second communication circuit configured to wirelessly transmit and receive in accordance with the Bluetooth® protocol.

[0210] Embodiment 65 The apparatus according to any one of embodiments 56 to 64, wherein the processing circuit is communicably coupled to a memory, and the memory stores a plurality of instructions that can be executed by the processing circuit.

[0211] Embodiment 66 A reader for a specimen monitoring system, A communication circuit configured to wirelessly transmit commands and wirelessly receive one or more responses, A processing circuit configured to determine whether the total number N of received responses is greater than the expected number E of responses, A reading device equipped with [a specific feature].

[0212] Embodiment 67 The apparatus according to embodiment 66, wherein the processing circuit is configured to treat the first (NE) responses as dummy data and the remaining E responses as containing data in response to the command.

[0213] Embodiment 68 The apparatus according to embodiment 67, wherein the processing circuit is configured to read the first (NE) responses and to confirm that those responses contain dummy data.

[0214] Embodiment 69 The apparatus according to embodiment 67, wherein the processing circuit is configured to process data in response to the command.

[0215] Embodiment 70 The apparatus according to embodiment 67, wherein the processing circuit is configured to store or display data in response to the command.

[0216] Embodiment 71 The apparatus according to embodiment 67, wherein the processing circuit is configured to ignore or discard the first (NE) responses without confirming that the first (NE) responses contain dummy data.

[0217] Embodiment 72 The apparatus according to any one of embodiments 66 to 71, wherein the processing circuit is configured to decode each received response.

[0218] Embodiment 73 The apparatus according to Embodiment 67, wherein the dummy data is a predetermined code, indicated by a flag in the header of the at least one first response, is pseudo-random data, or is generated according to a dummy data algorithm.

[0219] Embodiment 74 The device according to any one of embodiments 66 to 73, wherein the reading device is configured to communicate with a device attached to the body.

[0220] Embodiment 75 The apparatus according to any one of embodiments 66 to 74, wherein the communication circuit is configured to wirelessly transmit and receive in accordance with the Near Field Communication (NFC) protocol.

[0221] Embodiment 76 The apparatus according to embodiment 75, wherein the communication circuit is a first communication circuit, and the reading device comprises a second communication circuit configured to wirelessly transmit and receive in accordance with the Bluetooth® protocol.

[0222] Embodiment 77 A communication method within a specimen monitoring system equipped with a device attached to the body and a reading device, The steps include: receiving a command wirelessly from the reading device using the device attached to the body; The steps include: wirelessly transmitting a predetermined number of P first responses, each containing dummy data, from the device attached to the body to the reading device; The steps include: wirelessly transmitting at least one second response containing data in response to the command from the device that attaches the body to the reading device; A method that includes this.

[0223] Embodiment 78 The method according to embodiment 77, further comprising the step of processing the received command while transmitting a predetermined number of first responses to the reading device.

[0224] Embodiment 79 The step of processing the received command is: The steps include generating the data in response to the command, The steps include: encrypting the data in response to the command; The method according to embodiment 78, including the method described in embodiment 78.

[0225] Embodiment 80 The method according to embodiment 79, wherein the at least one second response transmitted to the reader includes data in response to the command in an encrypted form.

[0226] Embodiment 81 The method according to embodiment 80, wherein each of the predetermined number of first responses transmitted to the reader includes dummy data in an encrypted form.

[0227] Embodiment 82 The method according to embodiment 77, further comprising the step of counting the number of responses received from the device attached to the body by the reading device.

[0228] Embodiment 83 The method according to embodiment 82, further comprising the step of treating the P+1th response as containing data in response to the command.

[0229] Embodiment 84 The method according to embodiment 83, further comprising not verifying that the first P received responses contain dummy data.

[0230] Embodiment 85 The method according to embodiment 77, further comprising the step of reading the received command by a device attached to the body and wirelessly transmitting a predetermined number of P first responses corresponding to the received command.

[0231] Embodiment 86 The method according to Embodiment 85, wherein the received command is one of a plurality of commands, and the reading device and the body attachment device are programmed to identify a precise number of predetermined responses based on the command.

[0232] Embodiment 87 The method according to any one of embodiments 77 to 86, wherein the wireless communication between the device attached to the body and the reader follows the Near Field Communication (NFC) protocol.

[0233] Embodiment 88 A specimen monitoring system, A device to be attached to the body, including a communication circuit and a processing circuit, A reading device including a communication circuit and a processing circuit Equipped with, The device attached to the body is configured to wirelessly receive a command from the reading device, to wirelessly transmit a predetermined number of P first responses, each containing dummy data, to the reading device, and to wirelessly transmit at least one second response, each containing data in response to the command, to the reading device.

[0234] Embodiment 89 The system according to embodiment 88, wherein the device attached to the body is configured to process the received command while transmitting a predetermined number of first responses to the reading device.

[0235] Embodiment 90 The system according to embodiment 89, wherein the processing circuit of the device attached to the body is configured to generate data in response to the command and to encrypt the data in response to the command.

[0236] Embodiment 91 The system according to embodiment 90, wherein the processing circuit of the device attached to the body is configured to encrypt the dummy data and transmit the dummy data in an encrypted form.

[0237] Embodiment 92 The system according to embodiment 88, wherein the processing circuit of the reading device is configured to count the number of responses received from the device attached to the body.

[0238] Embodiment 93 The system according to embodiment 92, wherein the processing circuit of the reading device is configured to treat the P+1th response as containing data in response to the command.

[0239] Embodiment 94 The system according to embodiment 93, wherein the processing circuit of the reading device is configured to ignore or discard the first P received responses without confirming that each of the first P received responses contains dummy data.

[0240] Embodiment 95 The system according to embodiment 88, wherein the processing circuit of the device attached to the body is configured to read the received command and to wirelessly transmit a predetermined number of P first responses corresponding to the received command.

[0241] Embodiment 96 The received command is one of a plurality of commands, and the reading device and the device attached to the body are programmed to identify an accurate number of predetermined responses based on the command, the system according to Embodiment 88.

[0242] Embodiment 97 The communication circuit of the device attached to the body and the communication circuit of the reading device are each configured to communicate according to a Near Field Communication (NFC) protocol, the system according to any one of Embodiments 88 to 96.

[0243] Embodiment 98 A communication method in a specimen monitoring system including a device attached to the body and a reading device, Receiving, by the device attached to the body, a transmission including a custom command from the reading device and formatted according to a first communication protocol; Communicating the custom command from a first semiconductor chip of the device attached to the body to a second semiconductor chip of the device attached to the body, wherein the first semiconductor chip includes a communication circuit adapted to communication according to a first communication protocol, and the second semiconductor chip includes a processor; Causing the device attached to the body to transmit a first data payload including dummy data to the reading device according to the first communication protocol within a response setting limit time; Communicating a response data payload from the second semiconductor chip to the first semiconductor chip; Causing the device attached to the body to transmit the response data payload to the reading device; and a method including the above.

Explanation of Reference Numerals

[0244] 100 Specimen monitoring system 102 Device attached to the body (OBD) 103 Housing 104 Specimen sensor 105 Adhesive patch 120 Reading device 121 Input Components 122 Display 123 Data communication port 141, 142 Wireless communication links 170 Computer Systems 171, 191, 192 Communication Links 180 Reliable Computer Systems 190 Communication Networks 203, 210 memory 206 processors 216 Power supply 218 Power management circuit 241 First Communication Circuit 242 Second Communication Circuit 302 Analog Front End

Claims

1. A reader for a specimen monitoring system, A communication circuit configured to wirelessly transmit commands and wirelessly receive one or more responses, A processing circuit configured to determine whether the total number N of received responses is greater than the expected number E of responses, treat the first (N-E) responses as dummy data, and treat the remaining E responses as containing data that responds to the command. A reading device equipped with [a specific feature].

2. The apparatus according to claim 1, wherein the processing circuit is configured to read the first (N-E) responses and to confirm that those responses contain dummy data.

3. The apparatus according to claim 1, wherein the processing circuit is configured to process data in response to the command.

4. The apparatus according to claim 1, wherein the processing circuit is configured to store or display data in response to the command.

5. The apparatus according to claim 1, wherein the processing circuit is configured to ignore or discard the first (N-E) responses without confirming that the first (N-E) responses contain dummy data.

6. The apparatus according to any one of claims 1 to 5, wherein the processing circuit is configured to decode each received response.

7. The apparatus according to claim 1, wherein the dummy data is a predetermined code, indicated by a flag in the header of one or more responses, is pseudo-random data, or is generated according to a dummy data algorithm.

8. The apparatus according to any one of claims 1 to 7, wherein the reading device is configured to communicate with a device attached to the body.

9. The apparatus according to any one of claims 1 to 8, wherein the communication circuit is configured to transmit and receive wirelessly in accordance with a near-field communication (NFC) protocol.

10. The apparatus according to claim 9, wherein the communication circuit is a first communication circuit, and the reading device comprises a second communication circuit configured to wirelessly transmit and receive in accordance with a wireless communication protocol.

Images