WO2020178036A1 - Gestion de communication de dispositif dans des systèmes de surveillance d'activité d'utilisateur - Google Patents

Gestion de communication de dispositif dans des systèmes de surveillance d'activité d'utilisateur Download PDF

Info

Publication number
WO2020178036A1
WO2020178036A1 PCT/EP2020/054487 EP2020054487W WO2020178036A1 WO 2020178036 A1 WO2020178036 A1 WO 2020178036A1 EP 2020054487 W EP2020054487 W EP 2020054487W WO 2020178036 A1 WO2020178036 A1 WO 2020178036A1
Authority
WO
WIPO (PCT)
Prior art keywords
activity monitoring
monitoring device
controller
devices
pairing
Prior art date
Application number
PCT/EP2020/054487
Other languages
English (en)
Inventor
Johannes DAGEVOS VAN RIJ
Allan Kenneth Frazer Grugeon HUNT
Original Assignee
T.J.Smith And Nephew,Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by T.J.Smith And Nephew,Limited filed Critical T.J.Smith And Nephew,Limited
Publication of WO2020178036A1 publication Critical patent/WO2020178036A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/50Secure pairing of devices
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61BDIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00Measuring for diagnostic purposes; Identification of persons
    • A61B5/103Detecting, measuring or recording devices for testing the shape, pattern, colour, size or movement of the body or parts thereof, for diagnostic purposes
    • A61B5/11Measuring movement of the entire body or parts thereof, e.g. head or hand tremor, mobility of a limb
    • A61B5/1113Local tracking of patients, e.g. in a hospital or private home
    • A61B5/1114Tracking parts of the body
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61BDIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00Measuring for diagnostic purposes; Identification of persons
    • A61B5/44Detecting, measuring or recording for evaluating the integumentary system, e.g. skin, hair or nails
    • A61B5/441Skin evaluation, e.g. for skin disorder diagnosis
    • A61B5/447Skin evaluation, e.g. for skin disorder diagnosis specially adapted for aiding the prevention of ulcer or pressure sore development, i.e. before the ulcer or sore has developed
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61BDIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00Measuring for diagnostic purposes; Identification of persons
    • A61B5/48Other medical applications
    • A61B5/4842Monitoring progression or stage of a disease
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61BDIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00Measuring for diagnostic purposes; Identification of persons
    • A61B5/68Arrangements of detecting, measuring or recording means, e.g. sensors, in relation to patient
    • A61B5/6801Arrangements of detecting, measuring or recording means, e.g. sensors, in relation to patient specially adapted to be attached to or worn on the body surface
    • A61B5/6802Sensor mounted on worn items
    • A61B5/6812Orthopaedic devices
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61BDIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B2562/00Details of sensors; Constructional details of sensor housings or probes; Accessories for sensors
    • A61B2562/02Details of sensors specially adapted for in-vivo measurements
    • A61B2562/0219Inertial sensors, e.g. accelerometers, gyroscopes, tilt switches
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61BDIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B2562/00Details of sensors; Constructional details of sensor housings or probes; Accessories for sensors
    • A61B2562/04Arrangements of multiple sensors of the same type
    • A61B2562/043Arrangements of multiple sensors of the same type in a linear array

Definitions

  • Embodiments of the present disclosure relate to apparatuses, systems, and methods for managing communication between user activity monitoring devices and other devices.
  • Pressure ulcers which may also be known as pressure sores, bedsores, or decubitus ulcers, are injuries to skin and underlying tissue resulting from prolonged pressure on the skin, soft tissue, muscle, or bone above capillary filling pressure (approximately 32 mmHg).
  • DFU diabetic foot ulcer
  • Prior art approaches and systems provide little or no information regarding an individual’s lifestyle and compliance with the offloading devices. Gaining insight into the individual’s lifestyle can be important for the prevention and healing of pressure ulcers. However, because of these limitations, the prevention and healing of pressure ulcers using prior art approaches and systems may be delayed or, worse yet, worsened leading to prolonged discomfort, hospitalization, or even surgery. SUMMARY
  • a user activity monitoring device includes a housing, a motion sensor, a communication interface, and a controller.
  • the motion sensor can generate motion data responsive to a motion of the housing.
  • the controller can communicate and pair with a threshold number of a plurality of devices via the communication interface, prevent pairing with more than the threshold number of the plurality of devices via the communication interface, and transmit via the communication interface the motion data to one or more of the plurality of devices to which the controller is paired.
  • the user activity monitoring device of the preceding paragraph can include one or more of the following features:
  • the threshold number can be three.
  • the controller can add to a whitelist the plurality of devices to which the controller is paired.
  • the controller can disable discovery of the communication interface to prevent pairing with more than the threshold number of the plurality of devices via the communication interface.
  • the controller can disable a pairing functionality to prevent pairing with more than the threshold number of the plurality of devices via the communication interface.
  • the controller can transition from a first operation mode to a second operation mode responsive to the controller being paired with the threshold number of the plurality of devices.
  • the controller can transmit via the communication interface the motion data to the plurality of devices to which the controller is paired.
  • the user activity monitoring device can include a user input element, and the controller can pair with a first device of the plurality of devices responsive to a user input received via the user input element.
  • the controller can receive a pair request from a first device of the plurality of devices via the communication interface and initiate a pairing process for the first device responsive to the pair request.
  • the controller can exchange a shared key to pair with a first device of the plurality of devices.
  • the communication interface can communicate with the plurality of devices via a BluetoothTM protocol.
  • the communication interface can wirelessly communicate with the plurality of devices.
  • a method of operating a user activity monitoring device can include: generating motion data responsive to a motion of a housing; communicating and pairing, by a controller, with a threshold number of a plurality of devices via a communication interface supported by the housing; preventing pairing, by the controller, with more than the threshold number of the plurality of devices via the communication interface; and transmitting via the communication interface the motion data to one or more of the plurality of devices to which the controller is paired.
  • the method of the preceding paragraph can include one or more of the following features:
  • the threshold number can be three.
  • the method can further include adding to a whitelist the plurality of devices to which the controller is paired.
  • the preventing pairing can include disabling discovery of the communication interface.
  • the preventing pairing can include disabling a pairing functionality of the controller.
  • the method can further include transitioning from a first operation mode to a second operation mode responsive to the controller being paired with the threshold number of the plurality of devices.
  • Figure 1 illustrates a user activity monitoring system that includes an example activity monitoring device
  • Figure 2 illustrates an example computing environment that includes the activity monitoring device of Figure 1 ;
  • Figure 3 illustrates example components of the activity monitoring device of Figure 1;
  • Figures 4 and 5 illustrate example processes for operating and pairing with the activity monitoring device of Figure 1;
  • Figure 6 illustrates an example state diagram of mode transitions implementable by the activity monitoring device of Figure 1;
  • Figure 7 illustrates an example computer system usable to construct one or more of the devices or systems within the computing environment of Figure 2.
  • Activities of a user may be desirably monitored by an activity monitoring device for a variety of reasons, including wound prevention and monitoring.
  • the activities of a user can be monitored when the user may be prone to or already have a wound, such as a pressure ulcer.
  • Information gathered by the activity monitoring device about the activities of the user can be helpful for assisting with prevention or treatment of the pressure ulcer.
  • information gathered by the activity monitoring device about the activities can be useful for checking compliance with a treatment regimen.
  • any reference to a wound herein can refer to a wound on a human or animal body, and any reference to a body herein can refer to a human or animal body.
  • the disclosed technology may relate to preventing or minimizing damage to physiological tissue or living tissue, or to the treatment of damaged tissue (for example, a wound as described herein).
  • wound may include an injury to living tissue may be caused by a cut, blow, or other impact, typically one in which the skin is cut or broken.
  • a wound may be a chronic or acute injury. Acute wounds occur as a result of surgery or trauma. They move through the stages of healing within a predicted timeframe. Chronic wounds typically begin as acute wounds. The acute wound can become a chronic wound when it does not follow the healing stages resulting in a lengthened recovery. It is believed that the transition from acute to chronic wound can be due to a patient being immuno-compromised.
  • Chronic wounds may include for example: venous ulcers (such as those that occur in the legs), which account for the majority of chronic wounds and mostly affect the elderly, diabetic ulcers (for example, foot or ankle ulcers), peripheral arterial disease, pressure ulcers, or epidermolysis bullosa (EB).
  • venous ulcers such as those that occur in the legs
  • diabetic ulcers for example, foot or ankle ulcers
  • peripheral arterial disease for example, pressure ulcers, or epidermolysis bullosa (EB).
  • EB epidermolysis bullosa
  • wounds include, but are not limited to, abdominal wounds or other large or incisional wounds, either as a result of surgery, trauma, sterniotomies, fasciotomies, or other conditions, dehisced wounds, acute wounds, chronic wounds, subacute and dehisced wounds, traumatic wounds, flaps and skin grafts, lacerations, abrasions, contusions, bums, diabetic ulcers, pressure ulcers, stoma, surgical wounds, trauma and venous ulcers or the like.
  • Wounds may include a deep tissue injury.
  • Deep tissue injury is a term proposed by the National Pressure Ulcer Advisory Panel (NPUAP) to describe a unique form of pressure ulcers. These ulcers have been described by clinicians for many years with terms such as purple pressure ulcers, ulcers that are likely to deteriorate and bruises on bony prominences.
  • NPUAP National Pressure Ulcer Advisory Panel
  • Wound may also include tissue at risk of becoming a wound as discussed herein.
  • tissue at risk may include tissue over a bony protuberance (at risk of deep tissue injury/insult) or pre-surgical tissue (for example, knee tissue) that may has the potential to be cut (for example, for joint replacement/surgical alteration/reconstruction).
  • Some aspects relate to methods of monitoring or treating a wound with the technology disclosed herein in conjunction with one or more of the following: advanced footwear, turning a patient, offloading (such as, offloading diabetic foot ulcers), treatment of infection, systemix, antimicrobial, antibiotics, surgery, removal of tissue, affecting blood flow, physiotherapy, exercise, bathing, nutrition, hydration, nerve stimulation, ultrasound, electrostimulation, oxygen therapy, microwave therapy, active agents ozone, antibiotics, antimicrobials, or the like.
  • offloading such as, offloading diabetic foot ulcers
  • treatment of infection systemix
  • antimicrobial antibiotics
  • surgery removal of tissue, affecting blood flow, physiotherapy, exercise, bathing, nutrition, hydration, nerve stimulation, ultrasound, electrostimulation, oxygen therapy, microwave therapy, active agents ozone, antibiotics, antimicrobials, or the like.
  • a wound may be treated using topical negative pressure or traditional advanced wound care, which is not aided by the using of applied negative pressure (may also be referred to as non-negative pressure therapy).
  • the present disclosure may refer to pressure ulcers, foot ulcers, or the like
  • the systems and methods disclosed herein can be used for preventing, monitoring, or treating any type of skin injury or wound, such as a venous leg ulcer.
  • Figure 1 illustrates a user activity monitoring system 100 including an activity monitoring device 120 attached to a body part 110
  • the activity monitoring device 120 can be attached to the body part 110 using a strap, adhesive, or other coupling mechanism and may be worn on or supported by the body.
  • the body part 110 can be a leg of a user that includes a knee 112 and a foot 114.
  • the activity monitoring device 120 can be supported by the body part 110 at a position between the knee 112 and the foot 114, such as proximate to the knee 112. In other aspects, the activity monitoring device 120 can be supported by another part of the body part 110, such as above the knee 112 or elsewhere.
  • the activity monitoring device 120 can monitor and record activities (for instance, walking, jumping, sitting, laying down, running, squatting, or standing) of the body part 110, such as from a position, movement, or orientation of the activity monitoring device 120 or one or more other sensors of the activity monitoring device 120.
  • the activity monitoring device 120 can, for example, be used for loading monitoring of loading of the foot 114.
  • multiple body parts can be monitored by the activity monitoring device 120, and different sensors can be used for monitoring different body parts.
  • the body part 110 is shown wearing and being partly covered by an orthopedic device 130 (sometimes referred to as an offloading device).
  • the orthopedic device 130 can support the body part 110 and reduce a pressure on the foot 114 when the user may be standing or engaging in other activities.
  • a compliance monitoring device 132 can be attached to the orthopedic device 130.
  • the compliance monitoring device 132 can be the same as or similar to the activity monitoring device 120 and monitor and record activities of the orthopedic device 130.
  • the compliance monitoring device 132 can be supported by the orthopedic device 130 using a strap, adhesive, or other coupling mechanism.
  • the compliance monitoring device 132 can be attached to an inner surface or outer surface of the orthopedic device 130.
  • the compliance monitoring device 132 may be attached to an orthopedic device that is not worn by the patient (for example, a cane or a walker).
  • the activity monitoring device 120 can be worn regardless of whether the orthopedic device 130 may be worn.
  • the user activity monitoring system 100 can additionally or alternatively include one or more of the activity monitoring device 120 or the compliance monitoring device 132 at other positions, such as at a position supported by the orthopedic device 130, an other part of the body part 110, another device not worn such as a cane or a walker, or elsewhere.
  • the one or more additional or alternative of the activity monitoring device 120 or the compliance monitoring device 132 can be the same as or similar to the activity monitoring device 120 may monitor and record activities of the orthopedic device 130, the another part of the body part 110, or the body.
  • Figure 2 illustrates a computing environment 200 that includes the activity monitoring device 120.
  • the computing environment 200 shows the activity monitoring device 120 in communication with an initial configuration device 220, a test configuration device 230, and a user operation device 240, as well as the initial configuration device 220, the test configuration device 230, and the user operation device 240, in communication with a device management system 260 via a network 250.
  • the initial configuration device 220 and the test configuration device 230 can, for example, be operated by a manufacturer of the activity monitoring device 120, such as during a setup or configuration process for the activity monitoring device 120, and may be a device such as a smart phone, a tablet computer, or a desktop computer.
  • the user operation device 240 can be operated by a user of the activity monitoring device 120 and permit the user to use the user operation device 240 to collect, process, review, or transmit the data gathered by the activity monitoring device 120.
  • the user operation device 240 may be a device such as a smart phone, a tablet computer, or a desktop computer.
  • the device management system 260 may be a server.
  • the activity monitoring device 120 can include a pairing control 210.
  • the pairing control 210 can be a program that manages or restricts pairing between the activity monitoring device 120 and other devices, such as the initial configuration device 220, the test configuration device 230, and the user operation device 240.
  • Pairing in addition to having its ordinary meaning, can refer to processes of introducing two devices and exchanging information between the two devices so that the two devices may securely communicate or more easily communicate in the future. Pairing can take place over and enable communication via a communication channel, such as over air via electromagnetic waves and according to a BluetoothTM protocol like BluetoothTM Low Energy or another protocol, over a conductor via electrical communication, among other possibilities.
  • the pairing control 210 can limit a number of devices to which the activity monitoring device 120 may be paired to a threshold number of devices (such as two, three, four, five, six, or more devices) to prevent the activity monitoring device 120 from accidently or by a security breach pairing to an unintended or unauthorized device.
  • the pairing control 210 can limit the pairing to three total devices, which may be the initial configuration device 220, the test configuration device 230, and the user operation device 240.
  • the pairing control 210 can prevent further pairings, for example, by disabling discovery of a communication interface of the activity monitoring device 120 or disabling a pairing functionality of the activity monitoring device 120.
  • the pairing control 210 can control or track pairing to other devices by adding communication identifiers corresponding to the other devices to a whitelist maintained by the pairing control 210.
  • the initial configuration device 220 can include a pairing program 222.
  • the pairing program 222 can run on the initial configuration device 220 and enable the initial configuration device 220 to initiate pairing with the activity monitoring device 120 and pair with (sometimes referred to as bond with) the activity monitoring device 120. Once paired, the initial configuration device 220 and the activity monitoring device 120 can communicate data or commands between one another.
  • the pairing program 222 of the initial configuration device 220 can permit the initial configuration device 220 to communicate with a pairing management system 262 of the device management system 260, such as to provide a communication identifier and an optical code for the activity monitoring device 120.
  • the communication identifier can be a network identifier, such as a media access control (MAC) address, that may be used to communicate with the activity monitoring device 120.
  • the communication identifier can be assigned to the activity monitoring device 120 (or a component thereof like a controller or communication interface) at manufacture.
  • the optical code can be an identifier for the activity monitoring device 120 that may uniquely identify the activity monitoring device 120 from other activity monitoring devices or compliance monitoring devices.
  • the optical code may be presented in the form of a machine-readable optical label, such as a QR code or bar code, that may be decoded by the initial configuration device 220 to determine the optical code.
  • the optical code can be assigned to the activity monitoring device 120 at manufacture by a manufacturer of the activity monitoring device 120.
  • the pairing management system 262 may store the communication identifier and the optical code in association with one another in a data storage 266.
  • the pairing management system 262 can subsequently look up the communication identifier using the optical code and thereby provide the communication identifier to one or more devices, such as the test configuration device 230 or the user operation device 240, responsive to a request that includes the optical code from the one or more devices.
  • the test configuration device 230 can include a pairing program 232.
  • the pairing program 232 can run on the test configuration device 230 and enable the test configuration device 230 to initiate pairing with the activity monitoring device 120 and pair with the activity monitoring device 120. Once paired, the test configuration device 230 and the activity monitoring device 120 can communicate data or commands between one another.
  • the pairing program 232 of the test configuration device 230 can permit the test configuration device 230 to communicate with the pairing management system 262, such as to provide the optical code for the activity monitoring device 120 and request the communication identifier for the activity monitoring device 120. Once the pairing program 232, the pairing program 232 may be able to initiate pairing with the activity monitoring device 120 using the communication identifier.
  • the pairing management system 262 can track the number of different devices that request the communication identifier associated with the optical code.
  • the pairing management system 262 may be configured to not provide the communication identifier to more than a threshold number of different devices (such as, two, three, four, five, six, or more devices) to limit a number of different devices that may pair with the activity monitoring device 120.
  • the pairing management system 262 may, in some implementations, provide the communication identifier associated with the optical code not more than a threshold number of times (such as once, twice, three times, etc.) to each different device, which may prevent an unauthorized device that is pretending to be an authorized device from requesting the communication identifier an additional time.
  • the user operation device 240 can include a pairing program 242.
  • the pairing program 242 can run on the user operation device 240 and enable the user operation device 240 to initiate pairing with the activity monitoring device 120 and pair with the activity monitoring device 120. Once paired, the user operation device 240 and the activity monitoring device 120 can communicate data or commands between one another. For example, the activity monitoring device 120 may begin to transmit data gathered by the activity monitoring device 120 (such as motion data, alarms, monitored loading or positioning, or changes to a monitoring or therapy program) to the user operation device 240.
  • data gathered by the activity monitoring device 120 such as motion data, alarms, monitored loading or positioning, or changes to a monitoring or therapy program
  • the pairing program 242 of the user operation device 240 can permit the user operation device 240 to communicate with the pairing management system 262, such as to provide the optical code for the activity monitoring device 120 and request the communication identifier for the activity monitoring device 120. Once the pairing program 242, the pairing program 242 may be able to initiate pairing with the activity monitoring device 120 using the communication identifier. Moreover, the pairing program 242 of the user operation device 240 can cause the user operation device 240 transmit the data gathered by the activity monitoring device 120— before or after processing by the user operation device 240— to a data processing system 264 of the device management system 260.
  • the user operation device 240 can be operated by the user of the activity monitoring device 120 and permit the user to use the user operation device 240 to collect, process, present, store, or transmit the data gathered by the activity monitoring device 120.
  • the data processing system 264 can collect, process, present, store (such as in the data storage 266), or transmit the data gathered by the activity monitoring device 120 and received from the user operation device 240.
  • the data processing system 264 can process the data to identify events of interest, such as events that may indicate excessive pressure being placed on the body part 110, and may share the events of interest with the user operation device 240 or another device (not shown), such as a caregiver operation device that a caregiver may use to monitor and support the user.
  • the network 250 is shown as one connected network, the network 250 can be subdivided into one or more separate networks which may not directly communicate with one another.
  • the device management system 260 can communicate with the initial configuration device 220 via a separate and different network from the network that the user operation device 240 uses to communicate with the activity monitoring device 120.
  • FIG. 3 illustrates example components of the activity monitoring device 120.
  • the activity monitoring device 120 can include a housing 300, a controller 302, a memory device 304, a user interface 306, a power source 308, one or more sensors 310, and a communication interface 312 that may communicate, such as electrically, with one another.
  • the power source 308 can provide power to one or more components of the activity monitoring device 120.
  • the housing 300 can be composed of a top portion and a bottom portion that are sealed together, and the top portion or the bottom portion can be hard or soft.
  • the housing 300 can be flexible and have a mechanical structure and design features that provide for a shouldered key way alignment of components within the housing 300.
  • the housing 300 can support a circuit board on its inside and on which one or more components of the activity monitoring device 120 may be positioned.
  • the housing 300 can be made by stereolithography (SLA) or polyjet from photopolymer 3D printing material or by 3D printing from an engineering resin with a shorehardness of 80A.
  • the housing 300 can include an elastomer, a thermoplastic elastomer, or be constructed by injection molding.
  • the molded parts of the housing 300 can be made from liquid silicone rubber in white.
  • An adhesive for example, one for attaching plastics and elastomeric materials
  • An adhesive can be used to glue the top and bottom portions of the housing 300 together, and a wide range of other adhesives (for example, cyanoacrylates, silicones, epoxies, hydrogels, hydrocolloids, sealant systems) or other techniques (for example use of double sided adhesive tapes, ultrasonic welding, staking etc.) can be used.
  • other adhesives for example, cyanoacrylates, silicones, epoxies, hydrogels, hydrocolloids, sealant systems
  • other techniques for example use of double sided adhesive tapes, ultrasonic welding, staking etc.
  • the controller 302 can control operations of one or more other components (for instance, the memory device 304, the user interface 306, the power source 308, the one or more sensors 310, or the communication interface 312) of the activity monitoring device 120 according at least to instructions stored in the memory device 304.
  • the controller 302 can, for instance, control monitoring of loading of the body part 110 with a weight of the body or positioning of the body part 110 and record data indicative of loading of the body part 110 or positioning of the body part 110 to the memory device 304.
  • the pairing control 210 may be stored in the memory device 304 and run by the controller 302.
  • the user interface 306 can include one or more output elements, such as visual feedback devices (for example, light emitting diodes), haptic feedback devices, or audio devices (for example, speakers), that provide user outputs to a user.
  • the one or more output elements can convey status information to the user like whether the activity monitoring device 120 is successfully functioning or has successfully configured communication with another device.
  • the user interface 306 can include one or more input elements, such as buttons, switches, dials, touch pads, microphones, or touch screens, for receiving user inputs for configuring the activity monitoring device 120.
  • the user interface 306 may have no more than one user input element, such as a button, for receiving user inputs to activate and deactivate the activity monitoring device 120 or performing one or more other functions.
  • the one or more sensors 310 can be used to detect and monitor a motion of the activity monitoring device 120 or other characteristics of or around the activity monitoring device 120.
  • the one or more sensors 310 can be used to detect and monitor activities of the user of the activity monitoring device 120 that include, for instance, a loading or positioning of the body part 110.
  • the one or more sensors 310 can include one or more accelerometers, gyroscopes, magnetometers, impedance sensors, thermistors, pressure sensors, or optical sensors, among other types of sensors.
  • the one or more sensors 310 can be positioned proximate to the body part 110 or may be remote from the body part 110 yet usable to monitor characteristics of the body part 110.
  • the communication interface 312 can be used to communicate with other devices, including the initial configuration device 220, the test configuration device 230, and the user operation device 240, such as wirelessly via radio waves and according to a BluetoothTM protocol like BluetoothTM Low Energy or another protocol.
  • the communication interface 312 can, for example, communicate and pair with other devices and transmit device usage or sensor data like alarms, monitored loading or positioning, or changes to a monitoring or therapy program performed by the activity monitoring device 120 to the other devices.
  • the communication interface 312 can be used to receive data, including commands, from the other devices.
  • the communication interface 312 can permit communication with (for example, transfer of data to or processing commands from) another device once a communication channel has been configured for communication with the another device (for example, by device pairing).
  • Figure 4 illustrates an initialization process 400 for operating and pairing the initial configuration device 220 and the activity monitoring device 120.
  • the initialization process 400 is described in the context of the computing environment 200, but may instead be implemented in other components or systems described herein, or by other computing systems not shown.
  • the initialization process 400 can advantageously, in certain aspects, facilitate association of a communication identifier and an optical code at the pairing management system 262, as well as enable pairing of the initial configuration device 220 with the activity monitoring device 120 in a manner that may be secure and relatively easy for a user.
  • the initial configuration device 220 can obtain a communication identifier and an optical code for the activity monitoring device 120.
  • the communication identifier and the optical code can be presented on or within a housing or component of the activity monitoring device 120 or in documentation associated with the activity monitoring device 120.
  • the communication identifier and the optical code are described in greater detail elsewhere in this disclosure.
  • the initial configuration device 220 can obtain the communication identifier or the optical code, for example, by manual user input to the initial configuration device 220 or optical character recognition from an image of the communication identifier or the machine-readable optical label, such as an image captured by an image sensor of the initial configuration device 220.
  • the initial configuration device 220 can transmit the communication identifier and the optical code to the device management system 260 via the network 250.
  • the pairing management system 262 may, in turn, store the communication identifier and the optical code in association with one another in the data storage 266.
  • the pairing management system 262 can subsequently look up the communication identifier based on the association when provided the optical identifier by one or more devices (such as the test configuration device 230 or the user operation device 240), and the pairing management system 262 can provide the communication identifier to the one of more devices.
  • the initial configuration device 220 can initiate pairing with the activity monitoring device 120.
  • the initial configuration device 220 can initiate pairing, for instance, by transmitting a pair request to the activity monitoring device 120.
  • the initial configuration device 220 and the activity monitoring device 120 can detect pair confirmation actions that may indicate an authorization for the initial configuration device 220 and the activity monitoring device 120 to pair with one another.
  • the pair confirmation actions can be detected from a user input to the initial configuration device 220 (such as via a touchscreen of the initial configuration device 220) and a user input to the activity monitoring device 120 (such as via depression of a button of the activity monitoring device 120). Additionally or alternatively, the initial configuration device 220 and the activity monitoring device 120 may detect other pair confirmation information, such as a geographic location or a time at which a pair request is received or transmitted, to determine whether to permit pairing.
  • the initial configuration device 220 and the activity monitoring device 120 can bond with one another.
  • the initial configuration device 220 and the activity monitoring device 120 can, for instance, bond by exchanging one or more keys (such as a shared key like an Identity Resolution Key) and storing the one more keys at the initial configuration device 220 (such as in a local memory device) and the activity monitoring device 120 (such as in the memory device 304).
  • the one a more keys can permit future communications between the initial configuration device 220 and the activity monitoring device 120.
  • the one or more keys may be used to decode (sometimes referred to as resolve) an encoded communication identifier (sometimes referred to as an unresolved communication identifier) for the initial configuration device 220 or the activity monitoring device 120 so that the initial configuration device 220 or the activity monitoring device 120 may recognize that the encoded communication identifier corresponds to the initial configuration device 220 or the activity monitoring device 120.
  • decode sometimes referred to as resolve
  • an encoded communication identifier sometimes referred to as an unresolved communication identifier
  • FIG. 5 illustrates a setup process 500 for operating and pairing the activity monitoring device 120 and another device, such as the test configuration device 230 or the user operation device 240.
  • the setup process 500 is described in the context of the computing environment 200, but may instead be implemented in other components or systems described herein, or by other computing systems not shown.
  • the setup process 500 can advantageously, in certain aspects, facilitate pairing of the test configuration device 230 or the user operation device 240 with the activity monitoring device 120 in a manner that may be secure and relatively easy for a user.
  • the another device can the optical code for the activity monitoring device 120.
  • the optical code can be presented on or within a housing or component of the activity monitoring device 120 or in documentation associated with the activity monitoring device 120.
  • the optical code may be presented in the form of a machine- readable optical label, such as a QR code or bar code, that may be decoded by the another device to determine the optical code.
  • the another device can obtain the optical code, for example, by manual user input to the another device or optical character recognition from an image of the machine-readable optical label, such as an image captured by an image sensor of the another device.
  • the another device can request the communication identifier from the device management system 260.
  • the another device can, for example, transmit a request with the optical code to the device management system via the network 250.
  • the pairing management system 262 may, in turn, look up the communication identifier based on the association between the optical code and the communication identifier, and the pairing management system 262 can transmit the communication identifier to the another device.
  • the communication identifier is described in greater detail elsewhere in this disclosure.
  • the communication identifier can be the same as the communication identifier provided to the pairing management system 262 by the initial configuration device 220 at block 420.
  • the another device can initiate pairing with the activity monitoring device 120.
  • the another device can initiate pairing, for instance by transmitting a pair request to the activity monitoring device 120.
  • the another device and the activity monitoring device 120 can detect pair confirmation actions that may indicate an authorization for the another device and the activity monitoring device 120 to pair with one another.
  • the pair confirmation actions can be detected from a user input to the another device (such as via a touchscreen of the another device) and a user input to the activity monitoring device 120 (such as via depression of a button of the activity monitoring device 120). Additionally or alternatively, the another device and the activity monitoring device 120 may detect other pair confirmation information, such as a geographic location or a time at which a pair request is received or transmitted, to determine whether to permit pairing.
  • the another device and the activity monitoring device 120 can bond with one another.
  • the another device and the activity monitoring device 120 can, for instance, bond by exchanging one or more keys (such as a shared key like an Identity Resolution Key) and storing the one more keys at the another device (such as in a local memory device) and the activity monitoring device 120 (such as in the memory device 304).
  • the one a more keys can permit future communications between the another device and the activity monitoring device 120.
  • the one or more keys may be used to decode an encoded communication identifier for the another device or the activity monitoring device 120 so that the another device or the activity monitoring device 120 may recognize that the encoded communication identifier corresponds to the another device or the activity monitoring device 120.
  • Figure 6 illustrates a state diagram 600 of mode transitions that may be implemented by the activity monitoring device 120.
  • the state diagram 600 can illustrate how the activity monitoring device 120 can transition between communication or processing modes (sometimes referred to as operation modes) responsive to the activity monitoring device 120 pairing with a threshold number of devices.
  • the activity monitoring device 120 can advantageously, in certain aspects, transition from a less secure mode to a more secure mode or transition from a less restrictive mode to a more restrictive mode upon pairing with the threshold number of devices, so that the activity monitoring device 120 may be better able to withstand security threats or unintentional settings changes (such as once the activity monitoring device 120 pairs with the user operation device 240).
  • the activity monitoring device 120 can be in a first communication/processing mode.
  • the first communication/processing mode can be a mode in which the activity monitoring device 120 is permitted to pair with new devices (for instance, because a pairing disabled setting at the activity monitoring device 120 may be inactive).
  • the first communication/processing mode can be a mode in which the activity monitoring device 120 broadcasts its communication identifier to neighboring devices without encoding the communication identifier (for example, BluetoothTM LE Privacy disabled). The broadcasting of the communication identifier without encoding can facilitate easier pairing with the activity monitoring device 120, but may also permit unauthorized devices to monitor, pair with, or communicate with the activity monitoring device 120.
  • the first communication/processing mode can be a mode in which the activity monitoring device 120 performs debug or configuration operations (for instance, initialization operations, communication configurations, device setting changes, or troubleshooting of errors) and may not be a mode in which the activity monitoring device 120 performs end-user operations (for instance, monitoring or recording data generated by the one or more sensors 310 or communicating the data to another device via the communication interface 312).
  • debug or configuration operations for instance, initialization operations, communication configurations, device setting changes, or troubleshooting of errors
  • end-user operations for instance, monitoring or recording data generated by the one or more sensors 310 or communicating the data to another device via the communication interface 312).
  • the activity monitoring device 120 may not transition from the first communication/processing mode responsive to the activity monitoring device 120 pairing with its first new device (Device 1).
  • the first new device may, for example, be the first device that the activity monitoring device 120 paired with since the manufacture of the activity monitoring device 120 or a last memory reset or communication settings reset of the activity monitoring device 120.
  • the activity monitoring device 120 may not transition from the first communication/processing mode responsive to the activity monitoring device pairing with its first N-l new devices (Devices 1, ..., N-l).
  • the first N-l new devices may, for example, be the first N-l devices that the activity monitoring device 120 paired with since the manufacture of the activity monitoring device 120 or a last memory reset or communication settings reset of the activity monitoring device 120.
  • the activity monitoring device 120 may, however, transition from the first communication/processing mode at state 610 to the second communication/processing mode at state 620 responsive to the activity monitoring device pairing with its Nth new device (Device N).
  • the second communication/processing mode can be a mode in which the activity monitoring device 120 is not permitted to pair with new devices (for instance, because a pairing disabled setting at the activity monitoring device 120 may be active).
  • the second communication/processing mode can be a mode in which the activity monitoring device 120 broadcasts an encoded communication identifier to neighboring devices rather than its communication identifier (for example, BluetoothTM LE Privacy enabled).
  • the broadcasting of the encoded communication identifier can enhance the security of communications because the encoded communication identifier may not be directly used to communicate with the activity monitoring device 120 or may change over time making the activity monitoring device 120 difficult to track based on the encoded communication identifier.
  • the encoded communication identifier may nonetheless be used by devices that previously paired with the activity monitoring device 120 to continue to communicate with the activity monitoring device 120.
  • the second communication/processing mode can be a mode in which the activity monitoring device 120 performs end-user operations (for instance, monitoring or recording data generated by the one or more sensors 310 or communicating the data to another device via the communication interface 312) rather than debug or configuration operations (for instance, initialization operations, communication configurations, device setting changes, or troubleshooting of errors).
  • end-user operations for instance, monitoring or recording data generated by the one or more sensors 310 or communicating the data to another device via the communication interface 312
  • debug or configuration operations for instance, initialization operations, communication configurations, device setting changes, or troubleshooting of errors.
  • the value of N in the state diagram 600 may be three, so the activity monitoring device 120 remains in the first communication/processing mode until the activity monitoring device 120 pairs with its third new device.
  • the activity monitoring device 120 can, for instance, pair with the initial configuration device 220, the test configuration device 230, and the user operation device 240 and then transition to the second communication/processing mode.
  • the initial configuration device 220 or the test configuration device 230 may still be usable to retrieve data from the activity monitoring device 120 while no additional or new devices may be usable to pair and communicate with the activity monitoring device 120.
  • such a design may be desirable because a hacker device may be unable to communicate with the activity monitoring device 120 and yet leave an available pairing slot at the activity monitoring device 120 for a user to pair the activity monitoring device 120 and use the activity monitoring device 120 normally.
  • the value of N in the state diagram 600 may be two, four, five, six or more, so the activity monitoring device 120 remains in the first communication/processing mode until the activity monitoring device 120 pairs with its second, fourth, fifth, sixth, or additional new device, respectively.
  • the state diagram 600 may include one or more additional states (such as one, two, three, or more states) corresponding to one or more additional communication/processing modes.
  • the one or more additional states to be transitioned to responsive to the activity monitoring device 120 pairing with an additional new device, such as a N+lth new device (Device N+l), a N+2th new device (Device N+2), etc.
  • the state diagram 600 illustrates that the activity monitoring device 120 transitions from the first communication/processing mode at state 610 to the second communication/processing mode at state 620 after pairing with at least two new devices
  • the activity monitoring device 120 may transition from the first communication/processing mode to the second communication/processing mode responsive to pairing with its first new device.
  • the first communication/processing mode and the second communication/processing mode, as well as one or more additional communication/processing modes, are described as including particular example communication or processing features in connection with the state diagram 600.
  • the first communication/processing mode, the second communication/processing mode, or one or more additional communication/processing modes may include additional or alternative communication or processing features.
  • Figure 7 illustrates a computer system 700 usable to construct one or more of the devices (for instance, the initial configuration device 220, the test configuration device 230, or the user operation device 240), systems (for instance, the device management system 260, the pairing management system 262, or the data processing system 264), servers, or the like within the computing environment 200 of Figure 2.
  • the devices for instance, the initial configuration device 220, the test configuration device 230, or the user operation device 240
  • systems for instance, the device management system 260, the pairing management system 262, or the data processing system 264
  • servers or the like within the computing environment 200 of Figure 2.
  • the computer system 700 can include (i) a processor(s) (CPUs) 710, (ii) an input/output device(s) 720 configured to allow users to input and output information and interact with the computer system 700 as well as transfer and receive data or capture data with one or more sensors like an image sensor, (iii) a read only memory device(s) (ROMs) 730 or equivalents to provide nonvolatile storage of data or programs, (iv) a display(s) 750 such as a computer monitor or other display device, (v) a network connection(s) 740 and a network interface(s) 742 configured to allow the computer system 700 to connect to other systems, servers, or portable devices, as well as a memory space(s) 760 and a database(s) 790.
  • a processor(s) (CPUs) 710 the central processing unit
  • an input/output device(s) 720 configured to allow users to input and output information and interact with the computer system 700 as well as transfer and receive data or capture data with
  • the database(s) 790 may be further divided or distributed as sub-database(s) 790A-790N, with the sub-database(s) 790A-790N storing feature or function specific information associated with a particular feature or function.
  • the various components shown in Figure 7 may be incorporated in a computer(s) 770. It is noted that the various components shown in Figure 7, including the database(s) 790, may typically be included as part of the computer(s) 770, however, they may be external to the computer(s) 770. For example, the database(s) 790 may be external to the computer(s) 770 and may be part of a separate database computer system or networked database system. In some instances, the computer system 700 may be a computing device like a desktop computer, mobile phone, or a server.
  • the memory space(s) 760 may include DRAM, SRAM, FLASH, hard disk drives, or other memory storage devices, such as a media drive(s) 780, configured to store an operating system(s) 762, an application program(s) 764, and data 768, and the memory space(s) 760 may be shared with, distributed with or overlap with the memory storage capacity of the database(s) 790.
  • the memory space(s) 760 may include the database(s) 790, or the database(s) 790 may include the data 768 as shown in the memory space(s) 760.
  • the data stored in the memory space(s) 760 or the database(s) 790 may include information, such as motion data, pairing program information, data processing routines, or other types of data described herein.
  • One or more user inputs described in this disclosure may be received using one or more different mechanisms.
  • user interface controls may be selected by a user using one or more input options, such as a mouse, touch screen input, or keyboard input, among other user interface input options.
  • the user interface controls selected by the user can include one or more of buttons, dropdown boxes, select boxes, text boxes, check boxes, slider controls, or other user interface controls.
  • certain features are described in context of controlling of pairing, features of the disclosure can apply to control of communication permissions in types of system communications other than pairing.
  • a hardware processor can include electrical circuitry or digital logic circuitry configured to process computer-executable instructions.
  • a processor includes an FPGA or other programmable device that performs logic operations without processing computer- executable instructions.
  • a processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • a computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within an appliance, to name a few.
  • a software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD- ROM, or any other form of non-transitory computer-readable storage medium, media, or physical computer storage known in the art.
  • An example storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor.
  • the storage medium can be volatile or nonvolatile.
  • the processor and the storage medium can reside in an ASIC.
  • Conditional language used herein such as, among others,“can,”“might,” “may,”“e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements or states. Thus, such conditional language is not generally intended to imply that features, elements or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements or states are included or are to be performed in any particular embodiment.
  • the terms“comprising,”“including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth.
  • the term“or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term“or” means one, some, or all of the elements in the list.
  • the term“each,” as used herein, in addition to having its ordinary meaning, can mean any subset of a set of elements to which the term“each” is applied.
  • the terms“approximately”,“about”, “generally,” and“substantially” may refer to an amount that is within less than 10% of, within less than 5% of, within less than 1% of, within less than 0.1% of, and within less than 0.01% of the stated amount.
  • the terms“generally parallel” and“substantially parallel” refer to a value, amount, or characteristic that departs from exactly parallel by less than or equal to 15 degrees, 10 degrees, 5 degrees, 3 degrees, 1 degree, or 0.1 degree.

Abstract

L'invention concerne un dispositif de surveillance d'activité d'utilisateur qui comprend un boîtier, un capteur de mouvement, une interface de communication et un dispositif de commande. Le capteur de mouvement peut générer des données de mouvement en réponse à un mouvement du boîtier. Le contrôleur peut communiquer et apparier avec un nombre seuil de multiples dispositifs par l'intermédiaire de l'interface de communication, empêcher l'appariement avec plus que le nombre seuil de multiples dispositifs par l'intermédiaire de l'interface de communication, et transmettre, par l'intermédiaire de l'interface de communication, les données de mouvement à un ou plusieurs des multiples dispositifs auxquels le dispositif de commande est apparié.
PCT/EP2020/054487 2019-03-01 2020-02-20 Gestion de communication de dispositif dans des systèmes de surveillance d'activité d'utilisateur WO2020178036A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GBGB1902766.3A GB201902766D0 (en) 2019-03-01 2019-03-01 Device communicatio management in user activity monitoring systems
GB1902766.3 2019-03-01

Publications (1)

Publication Number Publication Date
WO2020178036A1 true WO2020178036A1 (fr) 2020-09-10

Family

ID=66377307

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2020/054487 WO2020178036A1 (fr) 2019-03-01 2020-02-20 Gestion de communication de dispositif dans des systèmes de surveillance d'activité d'utilisateur

Country Status (2)

Country Link
GB (1) GB201902766D0 (fr)
WO (1) WO2020178036A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2597203B (en) * 2019-05-01 2023-11-01 Smith & Nephew Communication and user interface control in user activity monitoring systems

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014207294A1 (fr) * 2013-09-13 2014-12-31 Polar Electro Oy Système de surveillance de l'activité physique
US20170011210A1 (en) * 2014-02-21 2017-01-12 Samsung Electronics Co., Ltd. Electronic device

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014207294A1 (fr) * 2013-09-13 2014-12-31 Polar Electro Oy Système de surveillance de l'activité physique
US20170011210A1 (en) * 2014-02-21 2017-01-12 Samsung Electronics Co., Ltd. Electronic device

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SACHIN ABHYANKAR ET AL: "On the application of traffic engineering over bluetooth ad hoc networks", PROCEEDINGS 6TH. ACM INTERNATIONAL WORKSHOP ON MODELING, ANALYSIS AND SIMULATION OF WIRELESS AND MOBILE SYSTEMS. ACM MSWIM 2003. SAN DIEGO, CA, SEPT. 19, 2003; [ACM INTERNATIONAL WORKSHOP ON MODELING, ANALYSIS AND SIMULATION OF WIRELESS AND MOBILE SY, 19 September 2003 (2003-09-19), pages 116 - 123, XP058304569, ISBN: 978-1-58113-766-8, DOI: 10.1145/940991.941011 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2597203B (en) * 2019-05-01 2023-11-01 Smith & Nephew Communication and user interface control in user activity monitoring systems

Also Published As

Publication number Publication date
GB201902766D0 (en) 2019-04-17

Similar Documents

Publication Publication Date Title
US20240031813A1 (en) Device communication management in user activity monitoring systems
US10945679B2 (en) Modular monitoring smart bed
EP2769298B1 (fr) Configuration automatique sécurisée d'équipement par une reproduction
WO2020234429A2 (fr) Systèmes et procédés de surveillance et de traitement d'ulcères de pied diabétique
Krasner Managing wound pain in patients with vacuum-assisted closure devices.
US20220176722A1 (en) Design rules for sensor integrated substrates
US20220218271A1 (en) Communication and user interface control in user activity monitoring systems
WO2016073777A1 (fr) Système de détection portable de télémédecine pour la gestion de troubles veineux chroniques
WO2019238927A1 (fr) Boîtier et montage de dispositif dans des systèmes de surveillance d'activité d'utilisateur
WO2020178036A1 (fr) Gestion de communication de dispositif dans des systèmes de surveillance d'activité d'utilisateur
US20190282738A1 (en) Pressure wound therapy status indication via external device
US20240115191A1 (en) Diabetic foot analysis apparatus, and diabetic foot management system
WO2023031045A1 (fr) Dispositif de restriction
US20230102670A1 (en) Low complexity load monitor
WO2023094397A1 (fr) Gestion de communication de dispositif dans des systèmes de surveillance d'activité d'utilisateur
Mccluskey Wear it well
US20240100232A1 (en) Dialysis system having remote monitoring and control
US20220257851A1 (en) Sensor sheet with digital distributed data acquisition for wound monitoring and treatment
JP2024514652A (ja) 創傷療法および治療のためのインテリジェント使い捨て装置
WO2023031032A1 (fr) Appareil et procédé permettant d'obtenir un contrôle urinaire
AU2022336957A1 (en) Apparatus and method for obtaining urinary control
AU2022338977A1 (en) Restriction device
CN116098607A (zh) 移动监护系统、装置和监测病人运动情况的方法
CN108053879A (zh) 智能辅助诊疗平台

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20706247

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20706247

Country of ref document: EP

Kind code of ref document: A1