WO2012120427A1 - Spectrum reallocation with prioritized schedule - Google Patents
Spectrum reallocation with prioritized schedule Download PDFInfo
- Publication number
- WO2012120427A1 WO2012120427A1 PCT/IB2012/051004 IB2012051004W WO2012120427A1 WO 2012120427 A1 WO2012120427 A1 WO 2012120427A1 IB 2012051004 W IB2012051004 W IB 2012051004W WO 2012120427 A1 WO2012120427 A1 WO 2012120427A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mban
- spectrum
- channel
- hub device
- devices
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
-
- 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/14—Spectrum sharing arrangements between different networks
-
- 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
- H04W84/22—Self-organising networks, e.g. ad-hoc networks or sensor networks with access to wired 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 use of a prioritized schedule for spectrum reallocation.
- 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.
- Frequency spectrum regulation policies try to increase the spectrum use efficiency.
- One way to increase efficiency is to allocate an opportunistic spectrum specifically for MBAN applications and services as secondary users of a spectrum that has been previously allocated to other services on a primary basis.
- the basic idea of an opportunistic spectrum is to allow secondary users to opportunistically utilize the spectrum that has been previously allocated to primary users as long as such secondary users do not introduce harmful interference to the primary users.
- MBAN spectrum 2360-2400 MHz band
- Similar proposals have been made or are expected to be made in other countries.
- the wide bandwidth, interference- free and good propagation properties of the MBAN spectrum would meet the strict requirements for medical-grade connectivity.
- the secondary user would have to protect the primary user in that spectrum.
- secondary users are often required to provide appropriate mechanisms to vacate the spectrum of the primary user when the primary user wants to use the spectrum.
- enforcement mechanisms are needed.
- the present application proposes to integrate a mechanism in the MBAN systems to guarantee compliance with the MBAN regulations.
- the simplest spectrum reallocation mechanism includes sending and receiving reallocation requests through a network connection. For example, once a MBAN coordinator receives a spectrum request from the primary user, the MBAN coordinator sends a spectrum reallocation request to backhaul access points (APs) through the hospital network connection. In response to receiving the reallocation requests from the MBAN coordinator, the backhaul AP broadcasts the request to all the MBAN hub devices that are connected to the backhaul AP via backhaul links. The MBAN hub device then disables the channels within the MBAN spectrum requested by the primary user. If the MBAN hub device is operating within the reallocated MBAN channel, the MBAN hub device initiates a dynamic channel selection to pick a new channel other than the reallocated spectrum.
- APs backhaul access points
- a MBAN hub device selects a new MBAN channel, it transmits a channel switch command to its corresponding MBAN devices within its MBAN network to move the MBAN network to the new channel. Once all the MBAN networks finish their channel switch operations, the MBAN spectrum requested by the primary user is vacated and ready for the primary use.
- this solution has performance issues due to the acuity level and quality of service requirements and the potential number of MBAN networks within a healthcare facility. For example, a situation may occur where two MBAN networks exist, MBAN A operating on Channel 1 and MBAN B operating on Channel 2. MBAN A bears a high-acuity service and MBAN B bears a low-acuity service.
- Channels 1 and 2 are within the reallocated MBAN spectrum and Channels 3 and 4 are both idle and outside the reallocated MBAN spectrum and Channel 3 has better quality (i.e. less in- band noise-plus-interference floor) than Channel 4.
- the MBAN coordinator transmits spectrum reallocations requests from the backhaul AP to the MBAN hub devices of MBAN A and B (referred to as Hub A and Hub B respectively).
- Hub A and Hub B performs channel scanning and dynamic channel selection operations independently (i.e. in a distributive way).
- MBAN B may initiate dynamic channel selection earlier than MBAN A and choose Channel 3 as its new channel due to the channel's better quality. If MBAN A initiates dynamic channel selection, Channel 4 is the only available channel and MBAN A will be left to operate on Channel 4, which has a worse quality compared to Channel 3, even though it has a higher acuity level than MBAN B. This may degrade the quality of service of performance of MBAN A.
- the present application provides a new and improved system and method for spectrum reallocation which overcomes the above-referenced problems and others.
- a medical system includes one or more medical body area network (MBAN) systems.
- MBAN medical body area network
- Each MBAN system including one or more MBAN devices which acquire and communicate patient data via a hub device via a short-range wireless communication channel. The communication of the patient data via the short-range wireless communication channel within a predefined spectra. One of the spectra being a spectrum belonging to a third party primary user.
- the hub device receives patient data communicated from the one or more MBAN devices and communicates with a central monitoring station via a longer range communication.
- the hub device reallocates to other spectra based on a priority of an acuity level of services communicated by each hub device.
- a method includes collecting patient data by one or more medical body area network (MBAN) devices, communicating the collected patient data from the one or more MBAN devices through the MBAN system to the hub device via a short-range wireless communication channel, the communication of the patient data via the short-range wireless communication channel being within a predefined spectra, one of the spectra being a spectrum belonging to a third party primary user, communicating the collected patient data from the hub device to a central monitoring station via longer range wireless communication; receiving a spectrum reallocation request from a MBAN coordinator requesting the third party primary user spectrum; and reallocating the MBAN system to other spectra based on a priority of an acuity level of services communicated by each hub device
- MBAN medical body area network
- Another advantage resides in the reduced or eliminated likelihood of loss of critical medical data acquired by an MBAN system.
- 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 embodiments and are not to be construed as limiting the invention.
- FIGURE 1 diagrammatically illustrates a medical body area network (MBAN) system in accordance with the present application.
- MBAN medical body area network
- FIGURE 2 diagrammatically illustrates a prioritized contention window procedure in accordance with the present application.
- FIGURE 3 is a flowchart diagram of the operation of the MBAN system in accordance with the present application.
- 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 embodiments 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 embodiments suitably employs an IEEE 802.15.4 (Zigbee) short-range wireless communication protocol or a variant thereof, or a Bluetooth TM short-range wireless communication protocol or a variant thereof.
- Zigbee IEEE 802.15.4
- Bluetooth TM and Zigbee are suitable embodiments 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 embodiments between MBAN devices operate in a frequency spectrum of around 2.3-2.5 GHz.
- an opportunistic MBAN spectrum is specifically allocated for the communication of the patient data, for example, in the 2360-2400 MHz band discussed above.
- the MBAN devices 12, 14 are secondary users of the spectrum or can use it on a secondary basis meaning the MBAN systems would have to yield to the primary users in that spectrum and vacate the spectrum.
- secondary users need mechanisms, such as spectrum reallocation procedures that enable secondary users to vacate the spectrum quickly when requested by primary users while continuing their services with minimum disturbance.
- first spectrum reallocation procedure secondary users are prioritized based on the services they bear and those with high priority are scheduled to reallocate before those with a lower priority so that they have better chances to acquire channels with better quality to continue their services.
- second spectrum reallocation procedure secondary users are sequentially scheduled to reallocate so that multiple secondary users do not to switch to the same channel which would decrease transmission collisions and degrade communication quality.
- each active MBAN network is assigned a priority based on the acuity level of its MBAN service by an MBAN coordinator 36. For example, life-critical MBAN services are assigned the highest priority level while wellbeing MBAN services without real-time monitoring may have the lowest priority level.
- the MBAN coordinator 36 determines the acuity level of all active MBAN networks and assigns a priority level for each of the MBAN networks according to its corresponding acuity level. The MBAN networks with higher priority levels will have precedent over MBAN networks with lower priority levels during the spectrum reallocation procedure.
- the MBAN devices 12, 14, the hub device 16, the hospital, or the like register the MBAN network with the MBAN coordinator 36.
- the MBAN coordinator 36 includes a controller 38 which receives the MBAN network registration and assigns a priority level to the MBAN network.
- the MBAN coordinator also includes a prioritizing unit 40 which determines the priority level of the active MBAN networks. Specifically, the prioritizing unit 40 receives information relating to the MBAN services performed by each of the active MBAN networks. The prioritizing unit 40 then determines the acuity level for all active MBAN networks and assigns a priority level for each of the MBAN networks according to their corresponding acuity level.
- the MBAN coordinator 36 can be a government regulatory entity, the FCC, a regional regulatory entity, the hospital in which the MBAN system is located, and the like. Assignment of the priority level could be part of administrative process conducted by a healthcare professional to start an MBAN network.
- Both the hub device 16 of the MBAN network and the access point (AP) that connects to that hub device 16 store the priority information of the MBAN network.
- Each AP or hub device 16 maintains a priority table, which includes three fields: an active MBAN network ID, which uniquely identifies each active MBAN network; a priority level, which indicates the acuity level of its MBAN service; and a current MBAN channel, which indicates the current MBAN channel used by each MBAN. The higher the acuity level, the higher the priority level.
- 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 transmits 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 range 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 a central monitoring station 34, receiving acknowledgements, setting up the network, associating new MBAN devices, disassociating removed MBAN devices, and the like.
- the longer range communication unit 32 of the hub device 16 also includes a transceiver which provides the longer-range communication capability to communicate data from the MBAN system 10.
- the hub device 16 wirelessly communicates with a central monitoring station 34 through an AP 50 of a hospital network 42.
- the illustrative AP 50 is a wireless access point that communicates wirelessly with the hub device 16.
- Both the hub device 16 of the MBAN network and the AP 50 that connects to that hub device 16 stores the priority table of the MBAN network.
- the hospital network 42 also includes additional access points, such as illustrative access points AP 52 and AP 54 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 52.
- Different APs 50-54 cover different areas of the healthcare facility and their coverage areas could overlap with each other to provide seamlessly roaming service.
- information about the AP and the MBAN network is communicated to the MBAN hub device 16.
- the information includes the active MBAN network ID, the priority level, and the current MBAN channel.
- 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 50 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 APs 42, 54 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 has longer range as compared with the short-ranger communication between the MBAN devices 12, 14 and the corresponding hub device 16.
- the short-range communication range may be of order a meter, 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 the plurality of APs to the 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 42 is interrupted for some time interval.
- the IEEE 802.11 or other wireless communication protocol employed by the hospital network 42 provides for the wireless communication.
- the patient may be confined to a bed, more generally it is contemplated that the patient may be ambulatory and moving around 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 may 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.
- the hub devices 16, 18 may also be a MBAN device that includes one or more sensors for measuring physiological parameters.
- an MBAN system can have two or more hubs that cooperatively perform the task of coordinating functionality (e.g. data collection from the MBAN devices 12, 14 and offloading the collected data via the longer range wireless communication).
- MBAN system 10 In illustrative FIGURE 1, only one MBAN system 10 is illustrated in detail. However, it will be appreciated that more generally the hospital or other medical facility includes a plurality of patients, each having his or her own MBAN system. More generally, 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). In this environment, 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, the MBAN hub 16, the MBAN system 10, the MBAN coordinator, and the central monitoring station 34 in the illustrative embodiment 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.
- Embodiments may be implemented using software for execution by a processor, hardware, or some combination thereof.
- the MBAN spectrum is an opportunistic spectrum that allows secondary users to opportunistically utilize the spectrum that has been previously allocated to primary users if such secondary uses do not introduce harmful interference to primary users.
- Each active MBAN network is assigned a priority based on the acuity level of its MBAN service.
- Each backhaul AP maintains a priority table, as shown below, which includes the active MBAN network ID, the priority level, and the current MBAN channel.
- a backhaul AP 50-52 receives a spectrum reallocation request from a primary user through the MBAN coordinator 36, it broadcasts a spectrum reallocation request command to the hub devices 16 that are connected to it through its backhaul links.
- a spectrum reallocation request command includes the following parameters: the frequency range of the requested spectrum or a list of the MBAN channels that are located within the requested spectrum that should be vacated, the spectrum reallocation deadline before which an MBAN hub should change spectrum channels to a new channel outside the requested spectrum if its currently used channel is within the requested spectrum, and a contention window table which has the following format.
- a prioritized contention window procedure begins at a time 100 at which an MB AN hub receives a spectrum reallocation request from the primary user.
- a Li contention window 102 is opened for MBANs with the highest priority level.
- the Li contention window starts at a time TS(Li) 104 and remains open for a Li window contention length TS(Li) + TL(Li) 106.
- a second L 2 contention window 108 is opened for MBANs with the next highest priority level.
- the second L 2 contention window starts at a time TS(L 2 ) 110 and remains open for a L 2 window contention length TS(L 2 ) + TL(L 2 ) 112.
- a third L 3 contention window 114 is opened for MBANs with the third highest priority level.
- the third L 3 contention window starts at a time TS(Ls) 116 and remains open for an L 3 window contention length TS(Ls) + TL(Ls) 118.
- contention windows are opened progressively for any remaining priority levels.
- the contention window table is an ordered table in the sense that for two records in the table with priority level of Lj and L 2 , respectively, TS(L 2 ) > TS(Z;) + TL(Z;) if Li > L2 .
- the contention window Li will end before the start of the contention window L 2 .
- the contention window length of a priority level Li can be optimized by the AP to minimize the collision probability (i.e.
- the probability that multiple MBANs with the same priority level Li select and switch to a same channel) while maintaining a reasonable response time For example, if an AP knows there is only one MBAN with a priority level Li that currently operates within the requested spectrum, it sets the contention window length of level Li to 0. If an AP knows there are many MBANs with priority level Li and a channel switching operation is scheduled to occur, the AP uses a large contention window length for level Li to reduce the potential contention probability.
- the start time TS(Li) can be selected to provide enough time for MBANs with priority levels higher than Li_i to finish their channel switching operations.
- Each hub device 16 maintains an MB AN channel status table 29 to indicate whether an MBAN channel is disabled or not.
- the hub device 16 updates its channel status table to disable the MBAN channels within the reallocated spectrum. Through the channel status table update operation, the MBAN channels within the reallocated spectrum are excluded from consideration in future dynamic channel selection operations and the future use of those channels are disabled. If one of the MBAN networks 10 is currently using an MBAN channel within the reallocated spectrum the MBAN network may continue its MBAN communications on its current channel for a predetermined time period.
- the hub devices also concurrently check to determine if its current channel is in the reallocated spectrum upon reception of a spectrum reallocation request.
- the hub device If the hub device is not operating on a reallocated channel, it sends an acknowledgment (ACK) to its backhaul AP to confirm the completion of its spectrum reallocation operation. If the hub device is operating in the reallocated channel, it starts a timer 31 with the predetermined expiration time set as the spectrum reallocation deadline parameter received within the command. Once this timer has timed out, the hub device automatically initiates a dynamic channel selection operation to select a new channel from the list of enabled MBAN channel and switches to the new channel to continue MBAN operations. Each hub device that currently operate within the reallocated spectrum determine its proper contention window from the contention window table [TS(L a ), TS(L a ) + TL(L a )], where L a is the priority level of the hub device.
- TS(L a ), TS(L a ) + TL(L a ) where L a is the priority level of the hub device.
- a hub device finishes its channel switching operation, it sends a spectrum reallocation confirmation with its new MBAN channel information to its AP and disables its spectrum reallocation timer.
- the MBAN networks with the high priority have a higher probability of obtaining a higher quality new channel compared to low priority MBAN networks because the higher priority MBAN networks start dynamic channel selection and channel switch operation earlier.
- the AP broadcasts a spectrum reallocation command with a contention window table, which has two records for a higher priority level 5 and a lower priority level 1, respectively and TS(1) > TS(5) + TL(5).
- a contention window table which has two records for a higher priority level 5 and a lower priority level 1, respectively and TS(1) > TS(5) + TL(5).
- priority level 5 only MBAN A operates in the reallocated spectrum and performs a channel switch and the AP sets a reallocated start timer TL(5) to 0 to reduce the response time.
- MBAN A looks up the time TS(5) in the contention window table. MBAN then starts the dynamic channel selection operation at the time TS(5) and selects Channel 3 as its new channel because it has a better quality. The MBAN A then switches to Channel 3 to continue its operation.
- the MBAN A After finishing its channel switch operation, the MBAN A sends a confirmation to its AP.
- MBAN B receives the command, it looks up TS(1) as its spectrum reallocation time in the contention window table. At TS(1), the MBAN B starts its dynamic channel selection operation. Since Channel 3 is occupied by MBAN A (since TS(1) > TS(5)) at TS(1), the MBAN B selects Channel 4 and performs channel switching to move to Channel 4 to continue its operations.
- an AP receives a spectrum reallocation request through the MBAN coordinator 36, the AP broadcasts a spectrum reallocation notification to the hub devices that are connected to it through backhaul links, which may be either wired or wireless.
- the purpose of the notification is to inform all the MBAN networks to avoid switching to a new channel that is located within the reallocated spectrum.
- the notification includes a frequency range of the reallocated spectrum or a list of the MBAN channels that are located within the reallocated spectrum that should be disabled and a spectrum reallocation deadline by which each MBAN hub should have moved its network to a new channel outside the reallocated spectrum if its currently used channel is within the reallocated spectrum, and the like.
- Each hub device maintains an MBAN channel status table 29 to indicate whether an MBAN channel is disabled or not.
- the MBAN hub device updates its channel status table to disable the MBAN channels within the requested spectrum. Through the channel status table update operation, the MBAN channels within the reallocated spectrum are excluded from consideration in future dynamic channel selection operations and the future use of those channels is disabled. It is worth pointing out that an MBAN network that is currently using an MBAN channel within the reallocated spectrum continues its MBAN communications on its current channel and no channel switching is triggered by the mere notification.
- the hub device checks if its current channel is in the reallocated spectrum. If the hub device is operating in the reallocated spectrum, it starts a timer 31 with the spectrum reallocation deadline parameter received within the notification set as the timer expiration time.
- the hub device automatically initiates a dynamic channel selection operation to select a new channel from the list of currently enabled MBAN channels and switches to the selected new channel to continue MBAN operations.
- the hub device then sends an acknowledgment (ACK) to its AP to confirm the reception of and compliance with the notification.
- ACK acknowledgment
- the AP tries to receive ACKs from all its hub devices for a predefined period. If the AP receives all the ACKs from the hub devices connected to it, a spectrum reallocation command is transmitted to the next lower priority hub(s).
- the AP retransmits the notification to those hub devices who's ACKs are missing and the AP retransmits Nj (predefined value) times. If ACKs remain missing, the AP generates warning messages to request staff intervention.
- the AP transmits spectrum reallocation commands to its hub devices to vacate the reallocated spectrum based on the MBAN priority level.
- the spectrum reallocation command includes the MBAN priority level.
- the AP first broadcasts a spectrum reallocation command including a priority level parameter to the highest priority level (P). If a hub device is currently operating on a channel outside the reallocated spectrum, it removes the reallocated spectrum from its enabled channels list and sends a confirmation. If this hub device is currently operating on a channel within the reallocated spectrum, it compares the priority level parameter with its own priority level.
- the hub device If the hub device has a priority level higher or equal to the priority level parameter, the hub device initiates the dynamic channel selection operation to select a new channel from the list of enabled channels (outside the allocated spectrum) and performs the channel switching operation.
- the MBAN hub device finishes its channel switching operation, it sends the spectrum reallocation confirmation with its new MBAN channel information to its AP.
- the AP receives all the expected confirmations from the hub devices (those have a priority level of P), it broadcasts a spectrum reallocation command with the priority parameter set to the next highest priority level, unless there are no MBANs with such priority level operating in the reallocated spectrum. This procedure continues with the descending order of the priority levels. For example, the backhaul AP first broadcasts a spectrum reallocation command with the priority level parameter of 5.
- the MBAN B Since the MBAN B (with a priority level of 1) has a lower priority level (1 ⁇ 5), it ignores the command once receiving it. Once the available MBAN A (with a priority level of 5) receives such command, it starts the dynamic channel selection operation and selects Channel 3 as its new channel because it has a better quality. The MBAN A then switches to Channel 3 to continue its operation. After receiving the confirmation from MBAN A, the AP broadcasts a series of spectrum reallocation command for levels 4, 3, 2, and finally for the priority level 1. Once the MBAN B receives this command (with priority level parameter of 1), it determines its own priority level is equal to the priority level parameter and then starts the dynamic channel selection operation. Since Channel 3 has already been used by MBAN A, it selects the next best channel, Channel 4 in this example, and performs channel switching to move to Channel 4 to continue its operation.
- a contention window length parameter can be included in the spectrum reallocation command. If an MBAN hub device has a priority level that matches the priority level of the spectrum reallocation command, the MBAN randomly picks up a time t within the contention window defined by that spectrum reallocation command and initiates its dynamic channel selection and channel switch operation at time t.
- FIGURE 3 illustrates 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 collected patient data is communicated from the one or more MBAN devices through the MBAN system to the hub device via a short-range wireless communication channel.
- the communication of the patient data via the short-range wireless communication channel being within a predefined spectra where one of the spectra is a spectrum belonging to a third party primary user.
- the collected patient data is communicated from the hub device to a central monitoring station via longer range wireless communication.
- a spectrum reallocation request is received from a MBAN coordinator requesting the third party primary user spectrum.
- the MBAN system is reallocated to a channel outside the requested spectrum in a reallocation window corresponding to an assigned priority level.
- the requested spectrum is disabled within a predetermined time period upon reception of the spectrum reallocation request.
- the spectrum reallocation request is transmitted to hub devices of one or more MBAN systems.
- the MBAN system is reallocated to other spectra based on a priority of an acuity level of services communicated by each hub device.
- the MBAN system is prioritized in relation to other MBAN systems based on the acuity level of service provided by the MBAN system.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/003,104 US9094781B2 (en) | 2011-03-10 | 2012-03-02 | Spectrum reallocation with prioritized schedule |
JP2013557201A JP6027031B2 (en) | 2011-03-10 | 2012-03-02 | Spectral reallocation by prioritized schedule |
CN201280012587.7A CN103430611B (en) | 2011-03-10 | 2012-03-02 | Spectrum with priority rating scheme is redistributed |
BR112013022764A BR112013022764A2 (en) | 2011-03-10 | 2012-03-02 | medical system and method |
EP20120713325 EP2684413B1 (en) | 2011-03-10 | 2012-03-02 | Spectrum reallocation with prioritized schedule |
RU2013145309/07A RU2588590C2 (en) | 2011-03-10 | 2012-03-02 | Redistribution of spectrum by means of priority |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201161451355P | 2011-03-10 | 2011-03-10 | |
US61/451,355 | 2011-03-10 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012120427A1 true WO2012120427A1 (en) | 2012-09-13 |
Family
ID=45937464
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/IB2012/051004 WO2012120427A1 (en) | 2011-03-10 | 2012-03-02 | Spectrum reallocation with prioritized schedule |
Country Status (7)
Country | Link |
---|---|
US (1) | US9094781B2 (en) |
EP (1) | EP2684413B1 (en) |
JP (1) | JP6027031B2 (en) |
CN (1) | CN103430611B (en) |
BR (1) | BR112013022764A2 (en) |
RU (1) | RU2588590C2 (en) |
WO (1) | WO2012120427A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014207624A3 (en) * | 2013-06-28 | 2015-03-26 | Koninklijke Philips N.V. | Mban channel management scheme using patient acuity information |
GB2525463A (en) * | 2014-12-31 | 2015-10-28 | Gen Electric | A wireless medical body area network and a method for managing wireless devices for the same |
Families Citing this family (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5581975B2 (en) * | 2010-07-07 | 2014-09-03 | ソニー株式会社 | COMMUNICATION CONTROL DEVICE, COMMUNICATION CONTROL METHOD, COMMUNICATION SYSTEM, AND COMMUNICATION DEVICE |
US9307343B2 (en) * | 2011-04-12 | 2016-04-05 | Lg Electronics Inc. | Method of initializing a channel in a medical body area network |
US20130210345A1 (en) * | 2012-02-15 | 2013-08-15 | Curtis Ling | Method and system for broadband near field communication utilizing full spectrum capture |
US10362372B2 (en) * | 2013-12-30 | 2019-07-23 | General Electric Company | System and method of selecting wireless spectrum and protocol based on patient acuity |
WO2015145283A1 (en) * | 2014-03-25 | 2015-10-01 | Koninklijke Philips N.V. | Multi-channel communication scheme for medical body area network (mban) to meet duty cycle regulation |
GB2529672B (en) * | 2014-08-28 | 2016-10-12 | Canon Kk | Method and device for data communication in a network |
GB2533791B (en) * | 2014-12-30 | 2018-09-26 | Gen Electric | Wireless medical body area network and method to associate wireless devices therewith |
GB2550576B (en) * | 2016-05-23 | 2018-06-13 | Gen Electric | Method and apparatus for tracking a device |
US10524270B2 (en) * | 2017-03-06 | 2019-12-31 | Hewlett Packard Enterprise Development Lp | Contention-based resource allocation |
US10892995B2 (en) * | 2017-12-28 | 2021-01-12 | Ethicon Llc | Surgical network determination of prioritization of communication, interaction, or processing based on system or device needs |
JP7281039B2 (en) | 2018-02-19 | 2023-05-25 | 公立大学法人広島市立大学 | Body area network communication method |
US10813169B2 (en) | 2018-03-22 | 2020-10-20 | GoTenna, Inc. | Mesh network deployment kit |
US10531308B1 (en) * | 2018-09-12 | 2020-01-07 | Motorola Solutions, Inc. | Dynamically assigning priority for shared spectrum communication systems |
WO2021102247A1 (en) | 2019-11-20 | 2021-05-27 | Andro Computational Solutions | Real time spectrum access policy based governance |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1863303A1 (en) * | 2006-05-30 | 2007-12-05 | NTT DoCoMo, Inc. | Method and apparatus of dynamic spectrum allocation in coexisting heterogeneous wireless networks |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2043507B1 (en) * | 2006-07-19 | 2020-08-26 | Cross Technology Solutions AB | Mobile apparatus, method and system for processing blood sugar affecting factors |
JP4881816B2 (en) * | 2007-08-22 | 2012-02-22 | 日本電信電話株式会社 | Channel assignment method, radio communication system, and management station apparatus |
WO2009049407A2 (en) | 2007-10-15 | 2009-04-23 | Sennet Communications | Methods of traffic prioritization in cognitive radio communications |
US8040815B2 (en) * | 2007-11-28 | 2011-10-18 | Motorola Solutions, Inc. | Spectrum coordination controller |
US8780882B2 (en) | 2008-01-16 | 2014-07-15 | Stmicroelectronics, Inc. | On-demand spectrum contention for inter-cell spectrum sharing in cognitive radio networks |
US8681709B2 (en) * | 2008-03-27 | 2014-03-25 | At&T Mobility Ii Llc | Dynamic allocation of communications resources |
US8300792B2 (en) * | 2008-05-14 | 2012-10-30 | At&T Mobility Ii Llc | Changing assigned priority of active voice or data session |
EP2227063B1 (en) * | 2009-03-04 | 2012-03-14 | Fujitsu Limited | Improvements to wireless sensor networks |
US8451789B2 (en) * | 2010-06-15 | 2013-05-28 | Nokia Corporation | Method to request resources in TV white spaces type environment |
US8711721B2 (en) * | 2010-07-15 | 2014-04-29 | Rivada Networks Llc | Methods and systems for dynamic spectrum arbitrage |
US8412247B2 (en) * | 2010-09-03 | 2013-04-02 | Nokia Corporation | Method for generating a coexistence value to define fair resource share between secondary networks |
US8385286B2 (en) * | 2010-09-03 | 2013-02-26 | Nokia Corporation | Resource sharing between secondary networks |
US20120182887A1 (en) * | 2011-01-14 | 2012-07-19 | Jari Junell | Resource allocation using subsets |
US8363602B2 (en) * | 2011-01-14 | 2013-01-29 | Nokia Corporation | Method, apparatus and computer program product for resource allocation of coexistent secondary networks |
CN102624465B (en) * | 2011-01-30 | 2016-01-20 | 中兴通讯股份有限公司 | The method and system that a kind of perception of cognitive radio is auxiliary |
-
2012
- 2012-03-02 RU RU2013145309/07A patent/RU2588590C2/en not_active IP Right Cessation
- 2012-03-02 CN CN201280012587.7A patent/CN103430611B/en not_active Expired - Fee Related
- 2012-03-02 WO PCT/IB2012/051004 patent/WO2012120427A1/en active Application Filing
- 2012-03-02 BR BR112013022764A patent/BR112013022764A2/en not_active Application Discontinuation
- 2012-03-02 US US14/003,104 patent/US9094781B2/en not_active Expired - Fee Related
- 2012-03-02 JP JP2013557201A patent/JP6027031B2/en not_active Expired - Fee Related
- 2012-03-02 EP EP20120713325 patent/EP2684413B1/en not_active Not-in-force
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1863303A1 (en) * | 2006-05-30 | 2007-12-05 | NTT DoCoMo, Inc. | Method and apparatus of dynamic spectrum allocation in coexisting heterogeneous wireless networks |
Non-Patent Citations (3)
Title |
---|
DELROY SMITH: "PHILIPS HEALTHCARE SYSTEMS REPLY COMMENTS; Amendment of the Commission's Rules to Provide Spectrum for the Operation of Medical Body Area Networks; ET Docket No. 08-59", 4 November 2009 (2009-11-04), pages 1 - 50, XP055002419, Retrieved from the Internet <URL:http://fjallfoss.fcc.gov/ecfs/document/view?id=7020244837> [retrieved on 20110708] * |
NIWAT THEPVILOJANAPONG ET AL.: "Resource Allocation for Coexisting ZigBee-Based Personal Area Networks", SEVENTH INTERNATIONAL CONFERENCE ON NETWORKING, pages 36 - 45 |
NIWAT THEPVILOJANAPONG ET AL: "Resource Allocation for Coexisting ZigBee-Based Personal Area Networks", NETWORKING, 2008. ICN 2008. SEVENTH INTERNATIONAL CONFERENCE ON, IEEE, PISCATAWAY, NJ, USA, 13 April 2008 (2008-04-13), pages 36 - 45, XP031246472, ISBN: 978-0-7695-3106-9 * |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014207624A3 (en) * | 2013-06-28 | 2015-03-26 | Koninklijke Philips N.V. | Mban channel management scheme using patient acuity information |
CN105340314A (en) * | 2013-06-28 | 2016-02-17 | 皇家飞利浦有限公司 | MBAN channel management scheme using patient acuity information |
US20160135206A1 (en) * | 2013-06-28 | 2016-05-12 | Koninklijke Philips N.V. | Mban channel management scheme using patient acuity information |
JP2016525241A (en) * | 2013-06-28 | 2016-08-22 | コーニンクレッカ フィリップス エヌ ヴェKoninklijke Philips N.V. | MBAN channel management scheme using patient urgency information (ACUITY INFORMATION) |
US10154506B2 (en) | 2013-06-28 | 2018-12-11 | Koninklijke Philips N.V. | MBAN channel management scheme using patient acuity information |
GB2525463A (en) * | 2014-12-31 | 2015-10-28 | Gen Electric | A wireless medical body area network and a method for managing wireless devices for the same |
WO2016108964A1 (en) * | 2014-12-31 | 2016-07-07 | General Electric Company | A wireless medical body area network and a method for managing wireless devices for the same |
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 |
AU2015372506B2 (en) * | 2014-12-31 | 2018-12-13 | General Electric Company | A wireless medical body area network and a method for managing wireless devices for the same |
US10608886B2 (en) | 2014-12-31 | 2020-03-31 | General Electric Company | Wireless medical body area network and a method for managing wireless devices for the same |
Also Published As
Publication number | Publication date |
---|---|
CN103430611B (en) | 2017-07-14 |
US9094781B2 (en) | 2015-07-28 |
US20130337749A1 (en) | 2013-12-19 |
JP2014512734A (en) | 2014-05-22 |
EP2684413A1 (en) | 2014-01-15 |
RU2013145309A (en) | 2015-04-20 |
EP2684413B1 (en) | 2015-05-13 |
CN103430611A (en) | 2013-12-04 |
JP6027031B2 (en) | 2016-11-16 |
RU2588590C2 (en) | 2016-07-10 |
BR112013022764A2 (en) | 2016-12-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9094781B2 (en) | Spectrum reallocation with prioritized schedule | |
US9781724B2 (en) | Method to use auxiliary channel to achieve fast and power-efficient association in wireless networks | |
EP2556697B1 (en) | Centralized dynamic channel allocation for medical body area networks | |
US9380586B2 (en) | MBAN channel use regulation scheme and adaptive channelization for IEEE 802.15.4J standardization | |
US9992685B2 (en) | Medical body area network (MBAN) with key-based control of spectrum usage | |
US9232352B2 (en) | Backhaul link assisted indoor spectrum use enforcement solution for MBAN services | |
JP5785606B2 (en) | Medical Body Area Network (MBAN) with automatic use of spectrum in facilities |
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: 12713325 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2012713325 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2013557201 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14003104 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2013145309 Country of ref document: RU Kind code of ref document: A |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112013022764 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112013022764 Country of ref document: BR Kind code of ref document: A2 Effective date: 20130905 |