EP2681952B1 - Backhaul link assisted indoor spectrum use enforcement solution for mban services - Google Patents

Backhaul link assisted indoor spectrum use enforcement solution for mban services Download PDF

Info

Publication number
EP2681952B1
EP2681952B1 EP12708945.6A EP12708945A EP2681952B1 EP 2681952 B1 EP2681952 B1 EP 2681952B1 EP 12708945 A EP12708945 A EP 12708945A EP 2681952 B1 EP2681952 B1 EP 2681952B1
Authority
EP
European Patent Office
Prior art keywords
mban
hub device
facility
devices
healthcare facility
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
EP12708945.6A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP2681952A1 (en
Inventor
Dong Wang
Monisha Ghosh
Delroy Smith
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Koninklijke Philips NV
Original Assignee
Koninklijke Philips NV
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 Koninklijke Philips NV filed Critical Koninklijke Philips NV
Publication of EP2681952A1 publication Critical patent/EP2681952A1/en
Application granted granted Critical
Publication of EP2681952B1 publication Critical patent/EP2681952B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/021—Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00—Measuring for diagnostic purposes; Identification of persons
    • A61B5/0002—Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network
    • A61B5/0015—Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network characterised by features of the telemetry system
    • A61B5/002—Monitoring the patient using a local or closed circuit, e.g. in a room or building
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00—Measuring for diagnostic purposes; Identification of persons
    • A61B5/0002—Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network
    • A61B5/0015—Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network characterised by features of the telemetry system
    • A61B5/0022—Monitoring a patient using a global network, e.g. telephone networks, internet
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00—Measuring for diagnostic purposes; Identification of persons
    • A61B5/0002—Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network
    • A61B5/0015—Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network characterised by features of the telemetry system
    • A61B5/0024—Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network characterised by features of the telemetry system for multiple sensor units attached to the patient, e.g. using a body or personal area network
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
    • G16H40/63—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for local operation
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
    • G16H40/67—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/04—Access restriction performed under specific conditions based on user or terminal location or mobility data, e.g. moving direction, speed
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00—Measuring for diagnostic purposes; Identification of persons
    • A61B5/02—Detecting, measuring or recording pulse, heart rate, blood pressure or blood flow; Combined pulse/heart-rate/blood pressure determination; Evaluating a cardiovascular condition not otherwise provided for, e.g. using combinations of techniques provided for in this group with electrocardiography or electroauscultation; Heart catheters for measuring blood pressure
    • A61B5/024—Detecting, measuring or recording pulse rate or heart rate
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00—Measuring for diagnostic purposes; Identification of persons
    • A61B5/08—Detecting, measuring or recording devices for evaluating the respiratory organs
    • A61B5/0816—Measuring devices for examining respiratory frequency
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00—Measuring for diagnostic purposes; Identification of persons
    • A61B5/24—Detecting, measuring or recording bioelectric or biomagnetic signals of the body or parts thereof
    • A61B5/316—Modalities, i.e. specific diagnostic methods
    • A61B5/318—Heart-related electrical modalities, e.g. electrocardiography [ECG]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/18—Network planning tools
    • H04W16/20—Network planning tools for indoor coverage or short range network deployment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks

Definitions

  • the present application relates to medical monitoring and clinical data devices for monitoring the physiological condition of a patient. It finds particular application in the restriction and enforcement of an MBAN spectrum for MBAN services and applications.
  • MBANs provide low-cost wireless patient monitoring (PM) without the inconvenience and safety hazards posed by wired connections, which can trip medical personnel or can become detached so as to lose medical data.
  • PM wireless patient monitoring
  • multiple low cost sensors are attached at different locations on or around a patient, and these sensors take readings of patient physiological information such as patient temperature, pulse, blood glucose level, electrocardiographic (ECG) data, or so forth.
  • ECG electrocardiographic
  • the sensors are coordinated by at least one proximate hub or gateway device to form the MBAN.
  • the hub or gateway device communicates with the sensors using embedded short-range wireless communication radios for example conforming with an IEEE 802.15.4 (Zigbee) short-range wireless communication protocol. Information collected by the sensors is transmitted to the hub or gateway device through the short-range wireless communication of the MBAN, thus eliminating the need for cables.
  • the hub or gateway device communicates the collected patient data to a central patient monitoring (PM) station via a wired or wireless longer-range link for centralized processing, display and storage.
  • the longer-range network may, for example, include wired Ethernet and/or a wireless protocol such as Wi-Fi or some proprietary wireless network protocol.
  • the PM station may, for example, include an electronic patient record database, display devices located at a nurse's station or elsewhere in the medical facility, or so forth.
  • MBAN monitoring acquires patient physiological parameters.
  • the acquired data may range from important (for example, in the case of monitoring of a healthy patient undergoing a fitness regimen) to life-critical (for example, in the case of a critically ill patient in an intensive care unit).
  • life-critical for example, in the case of a critically ill patient in an intensive care unit.
  • the current spectrum allocations and regulations for medical wireless connectivity do not meet the strict requirements of MBAN, including medical-grade link robustness, ultra low-power consumption and low-cost, due to either limited bandwidth or uncontrolled interference.
  • Short-range wireless communication networks tend to be susceptible to interference.
  • the spatially distributed nature and typically ad hoc formation of short-range networks can lead to substantial spatial overlap of different short range networks.
  • the number of short-range communication channels allocated for short range communication systems is also typically restricted by government regulation, network type, or other factors.
  • the combination of overlapping short-range networks and limited spectral space (or number of channels) can result in collisions between transmissions of different short range networks.
  • These networks can also be susceptible to radio frequency interference from other sources, including sources that are not similar to short-range network systems.
  • the MBAN spectrum could only be used by MBAN devices while they are located within healthcare facilities. If an MBAN device is outside the healthcare facility, the MBAN device could only transmit outside the MBAN spectrum. This means that an MBAN device can transmit within the MBAN spectrum only within the healthcare facility and the MBAN devices must switch to a new channel outside the MBAN spectrum to communicate when the MBAN devices are outside the healthcare facility. To accomplish this, enforcement mechanisms are needed and would be integrated in the future MBAN systems to guarantee the compliance with the MBAN regulations.
  • the simplest in-facility spectrum use enforcement would be manual administration.
  • a nurse or other healthcare staff will manually enable the hub device to use the MBAN spectrum.
  • a healthcare staff When a patient is going to move outside the healthcare facility, for example, due to discharge from hospital, a healthcare staff will manually disable and prohibit the hub device from operating in the MBAN spectrum.
  • the manually enable/disable operations could be implemented by manually entering a passcode on the hub device or connect the hub device with a specific device (for example, plug a USB key on the hub device) and a program running on the hub device or the specific device could automatically enable/disable the MBAN spectrum access of the hub device.
  • WO2008/103915 A1 a wireless medical monitoring system and medical monitoring devices adapted to communicate using a plurality of wireless protocols and networks are presented. For each transmission of data, a wireless protocol or network is selected based on the properties of the available protocols and networks and the nature of the data that is to be transmitted. Thus, the medical system and devices can move seamlessly from one context and location to another.
  • US 2006/0143292A discloses a wireless communication network in which a node uses node location information to determine whether to give a new candidate node access to the network.
  • the present application provides a new and improved system and method for access point assisted MBAN spectrum use enforcement for MBAN services which overcomes the above-referenced problems and others.
  • the invention is defined in the claims.
  • a medical system includes one or more MBAN devices configured to acquire and communicate patient data.
  • One or more medical body area network (MBAN) systems include the one or more MBAN devices configured to communicate the patient data with a hub device via short-range wireless communication. The communication of the patient data via the short-range wireless communication being within a predefined spectrum.
  • the hub device is configured to receive patient data communicated from the one or more MBAN devices, communicate with a central monitoring station via a longer range communication and one or more access points (AP), and determine the location of the MBAN system in reference to a healthcare facility.
  • the one or more MBAN devices are inhibited from transmitting within the predefined spectrum when the MBAN hub device is located outside the healthcare facility.
  • a method includes collecting patient data by one or more medical body area network (MBAN) devices, determining a location of an MBAN system, communicating the collected patient data from the one or more MBAN devices through the MBAN system to a hub device via short-range wireless communication, wherein the communication via short-range wireless communication within a predefined spectrum is permitted only within a healthcare facility; and communicating the collected patient data from the hub device to a central monitoring station via longer range wireless communication through the one or more APs and determines the location of the MBAN system from the one or more APs.
  • MBAN medical body area network
  • Another advantage resides in the use of access point information to determine whether an MBAN system is within or outside a healthcare facility to control use of the MBAN spectrum.
  • Another advantage resides in improved healthcare workflow efficiency, safety, and clinical outcome.
  • the invention may take form in various components and arrangements of components, and in various steps and arrangements of steps.
  • the drawings are only for purposes of illustrating the preferred examples and are not to be construed as limiting the invention.
  • each medical body area network (MBAN) 10 of a plurality of MBANs includes a plurality of MBAN devices 12, 14 and a corresponding hub device 16.
  • the MBAN devices 12, 14 communicate with the corresponding hub device 16 via a short-range wireless communication protocol.
  • the MBAN 10 is also sometimes referred to in the relevant literature by other equivalent terms, such as a body area network (BAN), a body sensor network (BSN), a personal area network (PAN), a mobile ad hoc network (MANET), or so forth - the term medical body area network (MBAN) 10 is to be understood as encompassing these various alternative terms.
  • the illustrative MBANs 10 includes two illustrative MBAN devices 12, 14 and a corresponding hub devices 16; however, the number of MBAN devices and hub devices can be one, two, three, four, five, six, or more, and moreover the number of MBAN devices may in some examples increase or decrease in an ad hoc fashion as MBAN devices are added or removed from the network to add or remove medical monitoring capability.
  • the MBAN devices 12, 14 include one or more sensors 20 that acquire patient data including physiological parameters such as heart rate, respiration rate, electrocardiographic (ECG) data, or so forth; however, it is also contemplated for one or more of the MBAN devices to perform other functions such as controlled delivery of a therapeutic drug via a skin patch or intravenous connection, performing cardiac pacemaking functionality, or so forth.
  • Other MBAN devices can be associated with a patient, and not all of the above-mentioned MBAN devices have to be associated with a patient at any given time.
  • a single MBAN device may perform one or more functions.
  • the illustrative MBAN devices 12, 14 are disposed on the exterior of an associated patient; however, more generally the MBAN devices may be disposed on the patient, or in the patient (for example, a MBAN device may take the form of an implanted device), or proximate to the patient within the communication range of the short-range communication protocol (for example, a MBAN device may take the form of a device mounted on an intravenous infusion pump (not shown) mounted on a pole that is kept near the patient, and in this case the monitored patient data may include information such as the intravenous fluid flow rate).
  • MBAN devices 12, 14 are typically low-power devices (to keep the battery or other electrical power supply small) and may have limited on-board data storage or data buffering.
  • the MBAN devices 12, 14 should be in continuous or nearly continuous short-range wireless communication with the corresponding hub device 16 in order to expeditiously convey acquired patient data to the corresponding hub device 16 without overflowing its data buffer.
  • the short-range wireless communication range is diagrammatically indicated by the dotted line used to delineate the MBAN system 10.
  • the short-range wireless communication is typically two-way, so that the MBAN devices 12, 14 can communicate information (e.g., patient data, MBAN device status, or so forth) to the corresponding hub device 16; and the corresponding hub device 16 can communicate information (e.g., commands, control data in the case of a therapeutic MBAN device, or so forth) to the MBAN devices 12, 14.
  • the illustrative hub device is a waist-mounted device which facilitates carrying a longer, heavier battery and other hardware for longer range transmissions; however, the hub device can be otherwise mounted to the patient, for example as a wrist device, adhesively glued device, or so forth. It is also contemplated for the hub device to be mounted elsewhere proximate to the patent, such as being integrated with an intravenous infusion pump (not shown) mounted on a pole that is kept near the patient.
  • the patient data acquired from the sensors 20 is concurrently transmitted to a controller 22 in the corresponding MBAN device.
  • the MBAN devices 12, 14 serve as a gathering point for the patient data acquired by the sensors 20 and provide temporary storage of the patient data in a memory 24.
  • the MBAN devices 12, 14 also include a communication unit 26 for transmitting the patient data via short-range wireless communication protocol to the corresponding hub device 16.
  • the communication unit 26 include a transceiver (not shown) to transmit the patient data and information, received by the controller 22, and receive information, from the hub device 16.
  • the short-range wireless communication protocol preferably has a relatively short operational range of a few tens of meters, a few meters, or less, and in some examples suitably employs an IEEE 802.15.4 (Zigbee) short-range wireless communication protocol or a variant thereof, or a BluetoothTM short-range wireless communication protocol or a variant thereof.
  • Zigbee IEEE 802.15.4
  • BluetoothTM and Zigbee are suitable examples for the short-range wireless communication
  • other short-range communication protocols, including proprietary communication protocols are also contemplated.
  • the short-range communication protocol should have a sufficient range for the hub device 16 to communicate reliably with all MBAN devices 12, 14 of the MBAN system 10.
  • the short-range wireless communication protocol between the MBAN devices 12, 14 and the corresponding hub device 16 and in some examples between MBAN devices operate in a frequency spectrum of around 2.3-2.5 GHz.
  • an MBAN spectrum is specifically allocated for the communication of the patient data, for example, the 2360-2400 MHz band discussed above.
  • the reliability requirements make the MBAN spectrum preferable for patient data transmission to other available spectrum.
  • the MBAN devices 12, 14 are secondary users of the spectrum. In order to protect primary users, operation of MBAN devices 12, 14 in the MBAN spectrum is prohibited unless the MBAN devices 12, 14 are authorized to operate in the MBAN network.
  • MBAN operations in the MBAN spectrum are limited to healthcare facilities only, meaning the MBAN devices 12, 14 are only allowed to transmit in the MBAN spectrum only when they are located within a healthcare facility.
  • the MBAN devices are required switch to a new channel outside the MBAN spectrum to transmit data. For example, the MBAN devices are only allowed to transmit patient data over the MBAN spectrum when the MBAN device is within the healthcare facility.
  • the hub device 16 coordinates operation of its MBAN system 10 over the MBAN spectrum to receive the patient data acquired by the sensors 20 of the MBAN devices 12, 14 and transmit the collected patient data from the MBAN 10 via a longer range communication protocol to a central monitoring station 34.
  • the patient data acquired from the sensors 20 is concurrently transmitted from the MBAN devices 12, 14 to a short range communication device 28 in the corresponding hub device 16.
  • the hub device 16 serves as a gathering point for the patient data acquired by the sensors 20 of all the MBAN device 12, 14 in the MBAN network, e.g. all of the MBAN devices associated with one patient, and provides temporary storage of the patient data in a memory 30.
  • the hub device 16 also includes a longer communication unit 32 for transmitting the patient data via a longer range wireless communication protocol to the central monitoring station 34.
  • a controller 33 of the MBAN hub 16 controls communication with the MBAN devices 12, 14, collection and handling of the patient data, retransmission of the patient data to the central monitoring station 34, setting up the network, associating new MBAN devices, disassociating removed MBAN devices, and the like.
  • the longer communication unit 32 of the hub device 16 also includes a transceiver which provides the longer-range communication capability to communicate data off the MBAN system 10.
  • the hub device 16 wirelessly communicates with a central monitoring station 34 through an access point (AP) 36 of a hospital network 42.
  • the illustrative AP 36 is a wireless access point that communicates wirelessly with the hub device 16.
  • the hospital network 42 also includes additional access points, such as illustrative access points AP 38 and AP 40 that are distributed throughout the hospital or other medical facility.
  • a central monitoring station is diagrammatically indicated, which is in wireless communication with the AP 24.
  • APs 36, 36, 40 cover different areas of the healthcare facility and their coverage areas could overlap with each other to provide seamlessly roaming service.
  • the positions of APs are fixed and known and can be used to determine the location of the MBAN hub device 16, particularly whether the patient is located within or outside the healthcare facility. Location can be determined in various ways, such as a GPS in the MBAN hub, triangulation between the closest APs, calculating and projecting a trajectory from previously contacted APs, and the like.
  • information about the AP is communicated to the MBAN hub device 16.
  • the information includes the identification of the AP, classification of the AP, location of the AP, the identification of the hospital network of which the AP is connected, and the like.
  • the MBAN hub device 16 utilizes this information to determine whether it is authorized to operate in the MBAN spectrum.
  • the central monitoring station 34 includes a controller 44 for receiving the patient data from many hub devices.
  • the central monitoring station 34 also includes a display monitor 46 that may, for example, be used to display medical data for the patient that are acquired by the MBAN system 10 and communicated to the central monitoring station 34 via the AP 38 of the hospital network 42.
  • the central monitoring station 34 also communicates with an electronic patient records sub-system 48 in which patient data and records for all current and past patients is stored. Communication between the central monitoring stations and the electronic patient records sub-system 48 is communicated via AP 40 of the hospital network 42.
  • the longer-range wireless communication is suitably a WiFi communication link conforming with an IEEE 802.11 wireless communication protocol or a variant thereof.
  • the longer-range communication can be a wired communication such as a wired Ethernet link (in which case the hospital networks include at least one cable providing the wired longer range communication link).
  • WMTS wireless medical telemetry system
  • the longer range communication is longer range as compared with the short-range communication between the MBAN devices 12, 14 and the corresponding hub device 16.
  • the short-range communication range may be of order ameter , a few meters, or at most perhaps a few tens of meters.
  • the longer range communication can be long enough to encompass a substantial portion or all of the hospital or other medical facility whether directly or via a plurality of AP to a hospital network.
  • the hub device 16 includes a battery or other power source sufficient to operate the longer-range communication transceiver.
  • the hub device 16 also typically includes sufficient on-board storage so that it can buffer a substantial amount of patient data in the event that communication with the hospital network 34 is interrupted for some time interval.
  • the IEEE 802.11 or other wireless communication protocol employed by the hospital network 34 provides for the wireless communication.
  • the patient is typically as lying in a bed, more generally it is contemplated for the patient to be ambulatory and to variously move throughout the hospital or healthcare facility.
  • the MBAN system 10 including the MBAN devices 12, 14 and the hub device 16 move together with the patient.
  • the MBAN devices 12, 14 communicate with the hub device 16 via the short-range wireless communication.
  • various pairs or groups of the MBAN devices 12, 14 to also intercommunicate directly (that is, without using the hub devices 16, 18 as an intermediary) via the short-range wireless communication. This may be useful, for example, to coordinate the activities of two or more MBAN devices in time.
  • the hub devices 16, 18 may provide additional functionality - for example, the hub devices 16, 18 may also be a MBAN device that includes one or more sensors for measuring physiological parameters.
  • the single hub devices 16, 18 is illustrated, it is contemplated for the coordinating functionality (e.g. data collection from the MBAN devices 12, 14 and offloading of the collected data via the longer range wireless communication) to be embodied by two or more MBAN devices that cooperatively perform the coordinating tasks.
  • FIGURE 1 only one MBAN system 10 is illustrated in detail.
  • the hospital or other medical facility includes a plurality of patients, each having his or her own MBAN system.
  • the number of MBAN systems may be, by way of some illustrative examples: the hundreds, thousands, tens of thousands, or more depending on the size of the medical facility. Indeed, it is even contemplated for a single patient to have two or more different, independently or cooperatively operating MBAN systems (not illustrated).
  • various MBAN systems of different patients can be expected to come into close proximity with one another, such that the ranges of the respective MBAN system short-range wireless communications overlap.
  • the MBAN devices 12, 14, MBAN hub 16, MBAN system 10, and central monitoring station 34 include at least one processor, for example a microprocessor or other software controlled device configured to execute MBAN software for performing the operations described in further detail below.
  • the MBAN software is carried on tangible memory or a computer readable medium for execution by the processor.
  • Types of non-transitory computer readable media include memory such as a hard disk drive, CD-ROM, DVD-ROM, internet servers, and the like.
  • Other implementations of the processor are also contemplated.
  • Display controllers, Application Specific Integrated Circuits (ASICs), FPGAs, and microcontrollers are illustrative examples of other types of component which may be implemented to provide functions of the processor. Examples may be implemented using software for execution by a processor, hardware, or some combination thereof.
  • MBAN hub device 16 include transceivers that associate with the APs 36, 38, 40 to provide connection to hospital network 42. The positions and coverage areas of the APs are fixed and known.
  • a MBAN hub device 16 is associated with an AP 36, 38, 40, information about the AP 36, 38, 40 is communicated to the MBAN hub device to determine the location of the MBAN hub device 16.
  • the MBAN hub device 16 uses the AP information to determine if the MBAN hub device's 16 current location is in-facility, out-facility, or unknown, and make a decision whether it is allowed to operate in the MBAN spectrum.
  • the APs are classified into three different AP types including inner APs, exterior APs, and entrance APs respectively.
  • the healthcare facility includes a healthcare facility border 100 and a healthcare entrance area 102. If an AP coverage includes the entrance area 102, e.g. front door lobby, back door, other exits, balcony, and the like, the AP is classified as an entrance AP.
  • AP3 is an entrance AP because it covers an entrance area of the healthcare facility.
  • an AP has a coverage area that extends outside healthcare facility boundary 100 (or in other words, if an MBAN hub device can successfully connect to an AP even if the MBAN hub is outside healthcare facility), then the AP is classified as an exterior AP.
  • API, AP2, and AP4 are exterior APs since part of their coverage areas are outside healthcare facility.
  • the coverage area of an AP is completely within healthcare facility (or in other words, an MBAN hub device cannot successfully connect to the AP if the hub device is outside healthcare facility)
  • the AP is classified as inner AP.
  • AP5-AP12 in Figure 2 are classified as inner APs.
  • the MBAN hub devices include in-facility status parameters to indicate their location or status.
  • the in-facility status parameters include three values: Indoor, Outdoor, and Unknown.
  • the in-facility status parameter of the MBAN hub device will be set based on the classification of the AP the hub connects to. For example, when an MBAN hub device starts to operate, the parameter is set to the default value "Unknown" or manually set by healthcare staff. If an MBAN hub device connects to an Entrance AP, the MBAN hub device parameter will be set to "Outdoor”. If an MBAN hub device connects to an inner AP, the MBAN hub device parameter will be set to "Indoor”.
  • the MBAN hub device parameter will keep unchanged. If an MBAN hub loses its connection to the AP, the MBAN hub device parameter will be reset to the default value "Unknown”.
  • the MBAN hub device continuously or periodically checks the classification of the AP to which it is connected and updates its in-facility status parameter accordingly. The above proposed scheme only uses AP information to determine the in-facility status of an MBAN hub device and does not require any extra hardware components.
  • the MBAN hub device and its associated MBAN devices are treated as if they are located within healthcare facility and are allowed to communicate within the MBAN spectrum.
  • the MBAN hub device and its MBAN devices are treated as if they are located outside healthcare facility and are not allowed to operate in the MBAN spectrum. If an MBAN hub device is operating within the MBAN spectrum and the parameter of the MBAN hub device is changed to "Outdoor” or "Unknown”, the MBAN hub device will stop transmissions within MBAN spectrum.
  • the MBAN hub device also includes an AP signal strength indicator (SSI) measured at the MBAN hub device or AP.
  • SSI indicates the strength of signal from the connected AP.
  • the SSI and the AP classification are used by the MBAN hub device to determine the in-facility status of an MBAN.
  • the in-facility status parameter is set the default value "Unknown” or manually set by healthcare staff. If an MBAN hub device connects to an Entrance AP and the SSI is less than a predetermined entrance boundary signal strength, the MBAN hub device parameter is set to "Outdoor".
  • the in-facility status parameter of the MBAN hub device When a MBAN hub device connects to an Entrance AP, the in-facility status parameter of the MBAN hub device will be set to "Indoor” if the SSI is greater than or equal to the predetermined entrance boundary signal strength,. If an MBAN hub device connects to an inner AP, the MBAN hub device parameter is set to "Indoor”. If an MBAN hub device connects to an exterior AP and the SSI is less than a predetermined exterior boundary signal strength, the MBAN hub device parameter keeps unchanged. When the MBAN hub device connects to an exterior AP, the MBAN hub device in-facility status parameter is set to "Indoor", if the SSI is greater than or equal to the predetermined exterior boundary signal strength.
  • the SSI related criteria could be implemented either at MBAN hub device side or at AP side.
  • Each of the exterior and entrance APs may have its own predetermined boundary signal strength parameters to optimize performance.
  • the enhanced criteria would allow more in-facility areas to possibly use the MBAN spectrum and therefore improve spectrum usage efficiency. For example, in FIGURE 3 , if an MBAN is connecting with AP3 and in the circle 104, which is the region that has SSI is greater than or equal to the predetermined entrance boundary signal strength, the MBAN hub device will be treated as "Indoor” and allowed to operate in the MBAN spectrum.
  • the MBAN Once the MBAN has left the hospital network area and started communicating on the non-MBAN spectrum, it can be re-authorized to use the MBAN spectrum using any of various network formation techniques.
  • the hospital network can use the communications on the non-MBAN spectrum to establish "Indoor" location criteria.
  • the MBAN hub device can listen for beacon signals on the MBAN spectrum to tell if it is within range and to go through a re-introduction protocol.
  • neighbor AP information is utilized to determine MBAN in-facility status.
  • the MBAN hub device utilized both the connected AP information and neighboring AP information to track the movement of the MBAN hub device and determine the location of the MBAN hub device.
  • the parameter is set to the default value "Unknown” or manually set by healthcare staff. If an MBAN connects to an Indoor AP, then its parameter is set to "Indoor”. If an MBAN connects to an Entrance AP, then its parameter is set to "Indoor”, if the SSI is greater than or equal to the predetermined entrance boundary signal strength.
  • the MBAN hub device parameter is set to "Indoor”. Otherwise the MBAN hub device parameter is set to "Outdoor” when an MBAN connects to an Entrance AP. If an MBAN connects to an Exterior AP, then its parameter is set to "Indoor”, if the SSI is greater than or equal to the predetermined exterior boundary signal strength.
  • the MBAN hub parameter's current value is "Outdoor” and the SSI is less than the predetermined exterior boundary signal strength but the MBAN hub device finds at least one neighbor "Indoor” AP and the SSI from the neighbor AP is greater than or equal to the predetermined neighbor boundary signal strength, the MBAN hub parameter is set to "Indoor” when the MBAN hub device connects to an Exterior AP. If the parameter's current value is "Outdoor” and the SSI is less than the predetermined exterior boundary signal strength and the MBAN hub does NOT find any neighbor "Indoor” AP from which the SSI is greater than or equal to the predetermined neighbor boundary signal strength, the MBAN hub parameter will remain “Outdoor” when the MBAN connects to an Exterior AP.
  • the MBAN hub device parameter If the MBAN hub device parameter's current value is "Unknown” and the MBAN hub find a neighbor "Indoor” AP and the SSI from that neighbor AP is greater than or equal to the predetermined neighbor boundary signal strength, the MBAN hub device parameter will be set to "Indoor” if an MBAN connects to an Exterior AP. Otherwise the MBAN hub device parameter keeps unchanged if an MBAN connects to an Exterior AP. More sophisticated solutions could be possible by using the observed neighbor APs and their SSI information, the associated AP and its SSI to characterize entrance areas and/or inner areas. In such case, the criteria can be specifically designed for individual AP.
  • FIGURE 4 illustrates the operation of the MBAN system.
  • patient data is collected by one or more medical body area network (MBAN) devices.
  • MBAN medical body area network
  • the in-facility status of an MBAN system is determined.
  • the collected patient data is communicated from the one or more MBAN devices through the MBAN system to a hub device via short-range wireless communication, the communication via short-range wireless communication within a predefined spectrum is permitted only within a healthcare facility.
  • the collected patient data is communicated from the hub device to a central monitoring station via longer range wireless communication through the one or more APs.
  • AP information is communicated between the hub device and the one or more APs connected to the hub device.
  • a step 210 it is determined whether the in-facility status of the MBAN system is indoor, outdoor or unknown based on AP information.
  • the predefined spectrum is communicated in response to the in-facility status of the MBAN system being classified as Indoor.
  • a step 214 communication is prohibited within the predefined spectrum in response to the in-facility status of the MBAN system being classified as Outdoor or Unknown.

Landscapes

  • Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Biomedical Technology (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Medical Informatics (AREA)
  • Public Health (AREA)
  • General Health & Medical Sciences (AREA)
  • Physics & Mathematics (AREA)
  • Molecular Biology (AREA)
  • Veterinary Medicine (AREA)
  • Animal Behavior & Ethology (AREA)
  • Surgery (AREA)
  • Biophysics (AREA)
  • Pathology (AREA)
  • Heart & Thoracic Surgery (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Primary Health Care (AREA)
  • General Business, Economics & Management (AREA)
  • Epidemiology (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Measuring And Recording Apparatus For Diagnosis (AREA)
  • Telephonic Communication Services (AREA)
EP12708945.6A 2011-03-01 2012-02-24 Backhaul link assisted indoor spectrum use enforcement solution for mban services Active EP2681952B1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201161447829P 2011-03-01 2011-03-01
PCT/IB2012/050853 WO2012117320A1 (en) 2011-03-01 2012-02-24 Backhaul link assisted indoor spectrum use enforcement solution for mban services

Publications (2)

Publication Number Publication Date
EP2681952A1 EP2681952A1 (en) 2014-01-08
EP2681952B1 true EP2681952B1 (en) 2019-02-13

Family

ID=45833481

Family Applications (1)

Application Number Title Priority Date Filing Date
EP12708945.6A Active EP2681952B1 (en) 2011-03-01 2012-02-24 Backhaul link assisted indoor spectrum use enforcement solution for mban services

Country Status (7)

Country Link
US (1) US9232352B2 (zh)
EP (1) EP2681952B1 (zh)
JP (1) JP6097227B2 (zh)
CN (1) CN103503521B (zh)
BR (1) BR112013021971A2 (zh)
RU (1) RU2596875C2 (zh)
WO (1) WO2012117320A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4169439A4 (en) * 2020-06-19 2023-07-19 Shenzhen Mindray Bio-Medical Electronics Co., Ltd. WIRELESS MEDICAL DEVICE, CENTRAL MONITORING STATION, AND WIRELESS MEDICAL MONITORING SYSTEM AND METHOD

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9186071B2 (en) 2012-01-27 2015-11-17 Qualcomm Incorporated Unlocking a body area network
JP2014112819A (ja) * 2012-10-30 2014-06-19 Yokogawa Electric Corp 無線機器、入出力ユニット、無線ユニット、及び無線機器の設定方法
US9554353B2 (en) 2013-05-07 2017-01-24 Qualcomm Incorporated Location based use of the DSRC spectrum
CN104243519B (zh) * 2013-06-17 2019-04-26 中兴通讯股份有限公司 基于无线体域网的人体生理特征监测方法和系统
DE102014212650B4 (de) * 2014-06-30 2018-02-15 Trumpf Medizin Systeme Gmbh + Co. Kg Medizingerätesystem und Verfahren zur Ortung von Medizingeräten und mobilen Steuerungseinheiten des Medizingerätesystems
US10362466B2 (en) * 2014-07-07 2019-07-23 Ascensia Diabetes Care Holdings Ag Methods and apparatus for improved low energy data communications
JP2016042271A (ja) * 2014-08-18 2016-03-31 Ntn株式会社 携帯型診断用データ測定送信装置
GB2525463B (en) * 2014-12-31 2017-11-15 Gen Electric A wireless medical body area network and a method for managing wireless devices for the same
US10420151B2 (en) * 2015-03-30 2019-09-17 Afero, Inc. Apparatus and method for intermediary device data collection
US10463253B2 (en) 2016-05-13 2019-11-05 General Electric Company Interface for two-part wearable patient monitoring device
US10357171B2 (en) 2016-07-08 2019-07-23 General Electric Company Adjustable ECG sensor and related method
US10588529B2 (en) 2016-07-08 2020-03-17 General Electric Company ECG monitoring system and method
US10237389B2 (en) 2016-07-20 2019-03-19 Dexcom, Inc. System and method for wireless communication of glucose data
US10944534B2 (en) * 2016-09-30 2021-03-09 Hewlett Packard Enterprise Development Lp Identifying doorway access points
US10307073B2 (en) 2016-12-21 2019-06-04 General Electric Company ECG sensor with capacitive defibrillation protection
US11547355B2 (en) 2016-12-21 2023-01-10 General Electric Company Capacitive leadwire for physiological patient monitoring
US10517488B2 (en) 2016-12-21 2019-12-31 General Electric Company Patient monitoring system and leadset having multiple capacitive patient connectors and a single galvanic patient connector
EP3585254B1 (en) 2017-02-24 2024-03-20 Masimo Corporation Medical device cable and method of sharing data between connected medical devices
WO2018156809A1 (en) 2017-02-24 2018-08-30 Masimo Corporation Augmented reality system for displaying patient data
JP7159208B2 (ja) 2017-05-08 2022-10-24 マシモ・コーポレイション ドングルを使用することによって医療システムをネットワークコントローラとペアリングするためのシステム
US10537252B2 (en) 2017-05-25 2020-01-21 General Electric Company Radio frequency mapping using mobile monitoring devices
US10306407B2 (en) * 2017-06-27 2019-05-28 General Electric Company Automatic frequency band selection using infrastructure-enabled beaconing
US10813169B2 (en) 2018-03-22 2020-10-20 GoTenna, Inc. Mesh network deployment kit
US10357174B1 (en) 2018-03-29 2019-07-23 General Electric Company Adjustable leadwire device for patient physiological monitoring and methods for making the same
US11278243B2 (en) 2018-05-16 2022-03-22 General Electric Company Repositionable surface electrodes
CN109121090B (zh) * 2018-08-31 2020-06-16 浙江口碑网络技术有限公司 店铺电子围栏建立方法及装置
CN114095951B (zh) * 2020-08-24 2023-09-05 中国移动通信集团终端有限公司 数据传输方法、装置、系统及计算机存储介质

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7606936B2 (en) 1998-05-29 2009-10-20 Research In Motion Limited System and method for redirecting data to a wireless device over a plurality of communication paths
US7154398B2 (en) * 2003-01-06 2006-12-26 Chen Thomas C H Wireless communication and global location enabled intelligent health monitoring system
US7411491B2 (en) * 2003-06-06 2008-08-12 Koninklijke Philips Electronics N.V. Method of controlling wireless data transmission by switching between short-range and long-range radio technologies
WO2004112325A1 (en) 2003-06-17 2004-12-23 Koninklijke Philips Electronics, N.V. Coordinating radio resource usage in unlicensed frequency bands
US8768322B2 (en) * 2004-02-13 2014-07-01 Sprint Spectrum L.P. Method and system for triggering events in a radio network
US20060009697A1 (en) * 2004-04-07 2006-01-12 Triage Wireless, Inc. Wireless, internet-based system for measuring vital signs from a plurality of patients in a hospital or medical clinic
CN101438270B (zh) 2004-10-29 2010-11-17 探空气球无线公司 构建位置信标数据库的方法和位置信标服务器
US20060143292A1 (en) * 2004-12-28 2006-06-29 Taubenheim David B Location-based network access
JP4885463B2 (ja) * 2005-03-03 2012-02-29 株式会社日立製作所 センサネットワークシステム、センサデータの処理方法及びプログラム
US20080058614A1 (en) * 2005-09-20 2008-03-06 Triage Wireless, Inc. Wireless, internet-based system for measuring vital signs from a plurality of patients in a hospital or medical clinic
US8442607B2 (en) 2006-09-07 2013-05-14 Sotera Wireless, Inc. Hand-held vital signs monitor
US20080228045A1 (en) * 2007-02-23 2008-09-18 Tia Gao Multiprotocol Wireless Medical Monitors and Systems
US7737850B2 (en) 2007-07-31 2010-06-15 Symbol Technologies, Inc. Methods and apparatus for locationing emergency personnel
US8416710B2 (en) 2009-03-30 2013-04-09 At&T Mobility Ii Llc Indoor competitive survey of wireless networks
JP2010268381A (ja) * 2009-05-18 2010-11-25 Japan Radio Co Ltd ゲート通過検知システム
US8405502B2 (en) * 2009-06-10 2013-03-26 Qualcomm Incorporated Identification and connectivity gateway wristband for hospital and medical applications

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4169439A4 (en) * 2020-06-19 2023-07-19 Shenzhen Mindray Bio-Medical Electronics Co., Ltd. WIRELESS MEDICAL DEVICE, CENTRAL MONITORING STATION, AND WIRELESS MEDICAL MONITORING SYSTEM AND METHOD

Also Published As

Publication number Publication date
US9232352B2 (en) 2016-01-05
RU2013143957A (ru) 2015-04-10
EP2681952A1 (en) 2014-01-08
JP2014510476A (ja) 2014-04-24
BR112013021971A2 (pt) 2018-06-26
RU2596875C2 (ru) 2016-09-10
US20130337842A1 (en) 2013-12-19
JP6097227B2 (ja) 2017-03-15
WO2012117320A1 (en) 2012-09-07
CN103503521A (zh) 2014-01-08
CN103503521B (zh) 2017-05-31

Similar Documents

Publication Publication Date Title
EP2681952B1 (en) Backhaul link assisted indoor spectrum use enforcement solution for mban services
US9992685B2 (en) Medical body area network (MBAN) with key-based control of spectrum usage
US9781724B2 (en) Method to use auxiliary channel to achieve fast and power-efficient association in wireless networks
US9380586B2 (en) MBAN channel use regulation scheme and adaptive channelization for IEEE 802.15.4J standardization
US9609521B2 (en) Medical body area network (MBAN) with automatic in-facility spectrum use enforcement
US9094781B2 (en) Spectrum reallocation with prioritized schedule
EP2556697B1 (en) Centralized dynamic channel allocation for medical body area networks

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20131001

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20170621

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602012056616

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0048180000

Ipc: A61B0005000000

RIC1 Information provided on ipc code assigned before grant

Ipc: A61B 5/0402 20060101ALN20180718BHEP

Ipc: H04W 48/04 20090101ALI20180718BHEP

Ipc: A61B 5/08 20060101ALN20180718BHEP

Ipc: G06F 19/00 20110101ALI20180718BHEP

Ipc: G16H 40/63 20180101ALI20180718BHEP

Ipc: A61B 5/024 20060101ALN20180718BHEP

Ipc: A61B 5/00 20060101AFI20180718BHEP

Ipc: H04W 4/021 20180101ALI20180718BHEP

Ipc: H04W 84/18 20090101ALN20180718BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20180831

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 1095742

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190215

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602012056616

Country of ref document: DE

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20190213

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190513

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190613

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190613

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190514

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190513

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1095742

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190213

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190224

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602012056616

Country of ref document: DE

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20190228

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190228

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190228

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

26N No opposition filed

Effective date: 20191114

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190224

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20200226

Year of fee payment: 9

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190224

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20200225

Year of fee payment: 9

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20120224

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20210224

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210224

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190213

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240228

Year of fee payment: 13