WO2016091944A1 - System to deliver alert messages from at least one critical service running on a monitored target system to a wearable device - Google Patents
System to deliver alert messages from at least one critical service running on a monitored target system to a wearable device Download PDFInfo
- Publication number
- WO2016091944A1 WO2016091944A1 PCT/EP2015/079106 EP2015079106W WO2016091944A1 WO 2016091944 A1 WO2016091944 A1 WO 2016091944A1 EP 2015079106 W EP2015079106 W EP 2015079106W WO 2016091944 A1 WO2016091944 A1 WO 2016091944A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- alert
- messages
- wearable device
- sentinel
- user
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
- H04L63/1408—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
- H04L63/1416—Event detection, e.g. attack signature detection
Abstract
System to deliver alert messages from at least one critical service running on a monitored target system to a wearable device, comprising means for : receiving incoming sentinel messages over a communications network from at least one critical service running on said monitored target system, processing said incoming sentinel messages by comparing the received alert message content with predefined alert conditions stored in a memory, communicating an alert message over a communication network to a wearable device in the case that said sentinel message contains an alert event that matches a predefined alert condition stored in said memory, receiving incoming alert messages on said wearable device over said communication network, and converting said alert messages into at least one haptic signal noticeable by the user on said wearable device.
Description
[DESCRIPTION]
System to deliver alert messages from at least one critical service running on a monitored target system to a wearable device.
FIELD OF THE INVENTION
The present invention relates to the field of administration of complex computer systems used in hospitals and medical institutions , where business critical processes are executed on computer systems .
BACKGROUND OF THE I VENTION
Many businesses depend on IT (information technology) solutions to support their critical business processes . Especially repetitive tasks and tasks in which large amounts of data are involved can nowadays be handled efficiently by computer sys ems . The concerned IT -components may be implemented i different ways and in different technical setups. They range from so-called stand-alone
configurations which are typically used by a single user at a time, to multi-user client-server setups . In the latter type of
configuration, different services or components of the IT-system can be distributed over multiple physical hardware configurations , but will interoperate and be connected to each other via a communication network . In such configurations , different subsystems wi11 operate to provide specialised services for other subsystems or clients . Examples of such services offered by different IT-subsystems are for instance database services , network services, application services , web services , file sharing services , and alike .
An example of such a complex integrated system is an ERP system or - in a hospital context- a hospital management system (HIS) . In such system, it is not uncommon that the different sys ems or subsystems which are serving different purposes are interconnected with each other, and where data transfer between different modules of the subsystems is taken care of by dedicated interface components . These dedicated interfaces are actively translating and transporting data
from one subsystem to another, and have been specifically designed to do so. The use of these interfaces solves the problem of
interoperability or compatibility of the data transfers between the different subsystems and assures the transport of time critical data between the modules .
Technically, the interfaces may be configured to run as independent processes or programs on dedicated computer systems (or hosts ) . Such processes are commonly known as interface processes. It is clear that any of these interface processes can cause business critical problems in case of failure .
An example of such a business critical process in a hospital environment is the transfer of scheduling and admission data for a patient who received an internal referral from one department to another department in the hospital . The interface managing the transfer of these data is essential for the admission and scheduling process insofar that failure to perform this transfer in due time may lead to delays in planning and scheduling, making double inquiries of information from the patient , ... A failure can even lead to critical situations affecting the patients treatment and health.
The result of such configurations is that IT systems become very complex chains of interoperating subsystems , in which various components may become essential for proper operation. It is
therefore of utmost importance that these business critical
processes are implemented in such way that they are operational at all times. Certain strategies for ensuring 24/7 uptime of business critical systems can be implemented using fail-over strategies , redundant configurations and backup techniques described in the art , but do not resolve all issues . Interfaces and critical services may fail after a program crash.
In order for the responsible system administrator to be able to timely intervene in case of a failure of a critical component or service , it is essential that the interfaces and services are permanently monitored.
In the art , various methods are described on how to monitor running computer services or processes , many of them involve the use of so- called sentinel agents , which are active monitoring programs guarding the proper operation of running systems and services. The sen inel agents monitor a set of selected parameters generated by the targeted system or processes to be monitored.
After a successful detection of a critical problem, it is essential that the problem is escalated immediately to the responsible system administrator, and that the relevant alert level is provided to him at that moment, in order to allow him to respond with the
appropriate actions .
This can be achieved by ensuring that the alert message confidently and quickly is delivered to an interface which is available to the adminis rator at the time of the alert . The prerequisites for a successful delivery of the message are the following :
only the critical alerts are delivered to the administrator and that less important ones are filtered out and are not delivered critical alert messages should be noticeable for the
administrator under all circumstances in order to avoid missed alerts
In the art , different solutions to deliver alert messages in a confident way to a user have been described making use of , for instance, handheld communication devices to receive alert
notifications by email , sms or other common communication means . The delivered messages may then contain contextual information about the alert providing relevant information to the system administrator about the problem.
The likelihood that the alert signal is noticed by the user upon receipt of the message can be augmented by means of emitting audible , visual or haptic signals by the handheld device . Audible signals will be effective in quiet environments (where the audible signal or ringtone can be easily noticed by the user) , whereas
visual signals will be successful in conditions where the device is located within the viewing range of the user . Haptic signals will only be effective when the user is in direct contact with the handheld device (and not when the device is for instance stored in a pocket which is not i contact with the users body) .
Another problem encountered with the solutions presented above , is that the augmented alert signal may be very intrusive and disturbing for the administrator or his environment . Imagine a system
delivering very loud alert notifications ; these may be very
disturbing during meetings or other situations .
So , since each of these techniques have their shortcomings , today no good solution exists to ascertain the delivery of critical alert messages to a system adminis rator under all circumstances ,
especially under circumstances when loud or intrusive signals are not acceptable .
SUMMARY OF THE INVENTION
The present invention is beneficial in that the aforementioned delivery success rate for delivering alert messages can be
drastically augmented . The invention provides for a solution to del ver critical alerts in a reliable, but yet non-disturbing or discrete way to a system administrator who is on guard. The above- described aspects are solved by a system as set out in claim 1.
Further advantages and embodiments of the present invention will become apparent from the following description and drawings .
Specific examples and preferred embodiments are set out in the dependent claims .
The present invention provides a system to deliver alert messages from at least one monitored target system (running at least one critical service) to a wearable device . The invention consists of 2 components; the alert notification manager and a wearable device .
The alert notification manager is a processor or a software
application running on a computer system connected to a
communication network . The alert notification manager is configured to perform a number of functions in the system. The alert
notification manager 1) receives the (raw) sentinel messages , 2) analyses them to check whether the sentinel message in question carries a .critical alert , and eventually 3) escalates the alert by sending an alert message to the wearable device over a network.
The embodiments of the systems and methods described herein may be implemented in hardware or software , or a combination of both .
However, preferably, these embodiments are implemented in computer programs executing on programmable computers each comprising at least one module component which comprises at least one
processor (e.g. a microprocessor) , a data storage system ( including volatile and non-volatile memory and/or storage elements) , at least one input device , and at least one output device . For example and without limitation, the programmable computers (referred to here as compu er systems) may be a personal computer, laptop , personal data assistant, and cellular telephone , smart-phone device , tablet computer, and/or wireless device . Program code is applied to input data to perform the functions described herein and generate output information . The output information is applied to one or more output devices , in known fashion .
Each program is preferably implemented in a high level procedural or object oriented programming and/or scripting language to communicate with a computer system. However, the programs can be implemented in assembly or machine language , if desired . In any case , the language may be a compiled or interpreted language . Each such computer program is preferably stored on a storage media or a device (e.g. ROM or magnetic diskette) readable by a general or special purpose programmable computer, for configuring and operating the computer when the storage media or device is read by the computer to perform the procedures described herein . The subject system may also be considered to be implemented as a computer-readable storage medium, configured with a computer program, where the storage medium so
configured causes a computer to operate in a specific and predefined manner to perform the functions described herein .
A first function of the alert notification manager is to receive incoming sentinel input from a target system which runs a critical service or interface and which is to be monitored. The sentinel input consists of all received sentinel messages . The sentinel messages are sent by sentinel agents (which are moni oring the target system) or by monitoring components foreseen in the target system itself (where the target system then acts as it's own sentinel agent) . The sentinel input is being monitored in real time in order to make sure that time critical failures of such a critical service or interface is being detected . The sentinel messages are data messages which are sent over a communication network to which the alert notification manager is also connected. The sentinel messages comprise data about the alert events on the target system, such as the alert level or criticality of the alert, coded
information about the event , data about the record which was processed at the moment of the event ,
The sentinel messages are either sent actively by the sentinel agent or the monitoring component of the target system. In another embodiment the sentinel messages are requested by the alert
notification manager itself , which on regular intervals queries the (passive) sentinel agents and monitoring components for new status messages .
A second function of the alert notification manager is to analyse the content of the received sentinel messages (i.e. data on the alert events ) in real time by comparing the message content against the predefined alert conditions stored in memory of the alert notification manager . Alert events turn into critical alerts when they match any of the. predefined alert conditions . The alert conditions are the rules which determine when an analysed message will be interpreted as a critical alert which needs to be escalated to the system administrator . The list of stored alert conditions can be adapted and configured ( in order to become predefined) by means
of a GUI which is connected to the memory of the alert notification manager .
The GUI is accessible to the system administrator which allows him to determine t e different alert conditions for the escalated alert messages. The GUI may be accessible as a web-enabled service ( such as a html -accessible webpage) or through a dedicated interface . The dedicated interface may be available on the host running the alert notification manager itself, or may be available on a different host through a network enabled interface . The GUI even may be accessible from the wearable device itself .
The third function of the alert notification manager is to transmit the alert message to the wearable device . For this purpose , the alert notification manager comprises a communication module which is configured to send a coded alert message to the wearable device . The coded alert message is sent over a communication network, such as the interne , gsm-network, local LAN or Wifi-network or alike . The coded alert message will comprise data about the destination of the message (the wearable device) , the criticality level of the alert message , and contextual information about the critical event and its origins ( the description of the monitored system) .
In this invention, the wearable device is configured to receive and convert said alert messages into at least one haptic signal
noticeable by the wearer of the wearable device . The haptic signal may be a vibration signal characterized by a certain vibration sequence or intensity . The differences between the haptic messaging schemes can be used to differentiate between different types of alert messages, or for instance alert levels for the respective alert message .
In a different embodiment , the haptic signal characteristics can be specified for each alert message type . In this case , the haptic signal characteristics are s ored in the same memory connected to the alert notification manager for each alert condition.
In again a different embodiment, the alerts messages can be routed to different wearable devices and as such addressing different users under certain circumstances . In this case the specific addressing data are stored in the same memory connected to the alert
notification manager for each alert condi ion.
Addi ionally, the alert messages can be made time-dependent insofar that the alert messages will only be active during certain periods of time of the day. This option allows the alert messages to be routed differently (to address different users) depending on different times of the day. Similarly, the timing data are stored in the same memory connected to the alert notification manager for each alert condition. All of these configuration parameters are then configurable through above mentioned GUI .
Development of wearable computers is accelerating with advances in technologies . Here , wearable computers refer to computers that a user can naturally wear, like clothes , watches , bracelets , glasses , and accessories , and which are in direct contact with the skin of the wearer. Smart-phones or tablet PCs do not have the same
essential features as the wearable devices described above , since they are not necessarily always in contact with the user .
Additionally, wearable computers may achieve better portability than smartphones or table PCs .
In particular, as one kind of wearable computers , a variety of products of a wrist watch, i.e. of a smart watch, through which the user can access a variety of online services , such as, for example , diary, messages , notifications , and stock quotes services , in a wireless manner, has appeared. In the case of the smart watch, the remarkable convenience is that the device is always in physical contact with the wearer of the watc . The wearability of the wearable device ascertains a compelling presence to the user during its use , and ascertains the delivery of a transmi ted alert message to the user in a non-intrusive , or non-disturbing way . This effect cannot be achieved by devices which are not wearable in the
definition that they are not permanently carried in contact with the
body of the user, such as smartphones . The art describes indeed devices (such as smartphones) which are capable of transmitting haptic signals customized for each type of alert , but the fact that smartphones can be mislaid, can be swi ched off , or be placed on a table or something cannot ensure that the haptic signal will be transmitted under all circumstances . For a wearable device, the haptic signal will be transmitted to the user under all
circumstances . Since the wearable device is in constant contact (or which is present in a compelling way) wi h the user, it can ensure that critical messages are transferred to a user .
Optionally, the wearable computer could be configured to require that the user acknowledges the signal ( for instance by only stopping the repetition of the signals by executing a command on the wearable device, for instance by pressing a button, or an icon on the touch sensitive display) . In this case , the wearable computer is fitted with a sensor unit to detect an input signal . This way, it can be ascertained that the message was effectively delivered successfully to the user .
In another embodiment the wearable computer may include a display unit (or screen) to provide additional information at the moment that the alert is delivered to the user. This has the additional advantage that contextual information can be added to the alert message , but this in a way that the display unit (or screen) itself does not attract the attention of the user or people in his direct vicinity . As such, the display of this supplementary contextual information is not accompanied with light flashes or audible signals .
Further advantages and embodiments of the present invention will become apparent from the following description and drawings .
BRIEF DESCRIPTION OF THE DRAWINGS
Fig . 1 is a simplified illustration of a system to deliver time critical alert messages from a monitored target sys em [300] to a wearable device [200] . The system consists of the 2 main components : the alert notification manager [100] and the wearable device [200] , and is configured to monitor the target system [300] which is not part of the system itself , but resides on the same communication network. [400] as the system components [100] and [200] .
Fig . 2 represents a table containing the different alert
configura ions for the different monitored target systems [300] stored in the memory [102] .
Fig . 3 represents a table containing the different alert
configura ions for the different monitored target systems [300] stored in the memory [102] , comprising data for the different patterns of the haptic signals to be generated by the wearable device .
DETAILED DESCRIPTION OF THE INVENTION
In the following detailed description, reference is made in
sufficient detail to the above referenced drawing, allowing those skilled in the art to practice the embodiments explained below. The main embodiment of the present invention provides a system to deliver time critical alert messages from at least one monitored target system (which is running at least one critical service) to a wearable device . The monitored target system [300] is a computer system which hosts a critical service , running process or program [301] . It means that the monitored target system [300] is being monitored because of the fact that i provides the necessary computing resources and
infras ructure to host or run the critical service [301] . The critical service [301] may be an independent running process or service , or may be a service which is a part of computer
applicatio .
The critical running process [301] is assumed to be running under normal operational conditions ; when running, this process or program [301] performs its desired functions and is capable of communicating with the monitoring component [303] or the sentinel agent [302] .
Under normal operational conditions , the critical running process or program can provide and communicate status information to the monitoring component [303] or the sentinel agent [302] , allowing same to analyse the status or condition of said process . This status information may be standard operational or performance parameters of the critical service ( for instance : the number of records being processed, per unit of time) which can be analysed by the monitoring component [303] or the sentinel agent [302] , or may be a status code providing the status directly. In the case that the critical service would be in a failing mode or would not be running ( for instance due to a program or system crash) ; said status information would deviate from the status information available during normal opera ing conditions , or said status information would not be available at all { for instance when the program halted) . These deviations will then be identified as error conditions by the monitoring component [303] or the sentinel agent [302] , and be transferred to the alert notification manager [100] as a sentinel message .
The sen inel agent [302] differs from the monitoring component [303] in that the monitoring component is part of the running critical process/program [301] , and a sentinel agent [302] is not . In the case of a moni oring component , the critical process is fitted to actively provide status information about its performance by itself through its integrated monitoring component . A sentinel agent [302] , on the contrary, is an external program which is implemented and executed as a separate running program or service , which actively monitors a different process (the critical service [301] ) . A sentinel agent has the advantage that it will continue to respond even in case that the critical process fails or crashes , which in this case can continue to provide sentinel messages about the crashed process.
The alert notification manager [100] communicates via a communication module [103] which is configured to receive sentinel messages from at least one monitoring component [303] or sentinel agent [302] . The communication module [ 103 ] transfers the incoming sentinel messages to the processing module [101] , which compares the content of the sentinel messages to the alert conditions stored in the memory [102] of the alert notification manager [100] . In the. case that the processed sentinel message matches one of the stored alert conditions in the memory, the processing module [101] will construct an alert message which will be sent to the wearable device [200] . The message contains addressing data to be able to be sent over a communica ions network to the destination device ; the wearable computer [200J . The alert message optionally contains information about the alert condition, and optionally supplementary contextual information providing more background about the alert condition .
The alert notification manager is a dedicated component which is installed preferably on the internal communication network of the hospital , in order for it to have communication network access to the monitored target systems [300] . The ne work is in many cases an ethernet network, a Wi-Fi network, or alike . The communication between, the alert notification manager [300] and the wearable computer [200] can be done over any wireless communication
technology suitable to reach the wearable computer, such as Wi-Fi, gsm- or cellphone networks , or in some cases even short range wireless communication technologies (near field networks , blue tooth, ...) ...
The alert notification manager [100] can be configured in that the alert configuration can be defined by means of a GUI . An alert configuration is defined by the monitored critical process , the alert condition, optional contextual information and the destination where to sent the alerts to (which may be an individual computer or plural wearable computers at the same time) ( see Figure 2 ) . The contextual information may comprise references to the severity or
urgency level of the alert, or in-depth textual info about the alert just messaged to the wearer in a haptic way .
Additionally, the alert notification manager [100] can be configured to deliver alert messages to different destinations during different periods of the day, allowing to send the alert messages only to the system administrator who is on guard at a certain moment .
The alert configurations stored in memory [102] can be edited by the user via a configura ion GUI [104] which may be accessible via the communication network (web- interface) via network capable device, or , in another embodiment , via the display interface of the targeted wearable computer [200] itself . The advantage of this approach where the alert configurations are stored in a memory of the system (as opposed to in the wearable device itself) is that this enhances the configurabi1ity of the alert characteristics of the stored alert configurations , since they can be managed via the configuration GUI .
The wearable computer [200] of one embodiment of the invention can be a smart watch as disclosed in US Patent 8,854,925. The wearable computer may also be any other wearable computer which is in sufficient direct contact with the skin of the user for haptic signals to be detectable by the wearer at all times (for instance : a vibrating pod or bracelet , implant , ...) , or whose display is
permanently in the field-of -view of the user (such as the "Google glass" (HUD-equipped pair of glasses) ) . The wearable computer in this invention has to be able to convert received alert messages into haptic signals . These haptic signals are typically vibrations produced by a vibrating element (actuator) built in into the wearable computer which can be triggered by an electronic signal . It is of importance in this invent on that the haptic signal is only detectable by the user of the wearable computer itself , in so far that other people in the vicinity of the user would not be disturbed or alerted by the signal delivered to the user . This would have to mean that the haptic signal should not create secondary effects beyond the delivery of the haptic signal itself : a vibrating signal
should not produce audible effects insofar that they could be perceived by other people except for the user himself .
So, the vibra ing signals ' noise level should not exceed the ambient noise level . For that purpose, the intensity settings of the vibration should be adjustable to match the acoustic environment the user situation is in. A very subtle , low intensity vibration setting should be used during a meeting or when the administrator would have to work in the vicinity of a patient , whereas a higher intensity vibration could be selected when the user is in a loud area (such as the staff restaurant during lunch break) . The ambient noise level can be used to adjust the intensity of the haptic signal . The ambient noise level should then be measured by a microphone in the wearable computer, or connected to the wearable computer .
The wearable device of this embodiment is thus able to transform the received alert message into a vibration, drawing the wearer' s attention only . Other types of haptic signals may be considered as well , such as changes in temperature applied to the skin of the wearer .
The haptic signals can be produced in different patterns and/or intensities noticeable by the user . As such, a certain
differentiation can be achieved by delivering a haptic signal for different types of alert messages . The pattern of the haptic signal can be used to uniquely identify a certain incoming alert type, thus providing additional identification information about the alert to the user .
Another embodiment of the invention may provide for a smartphone as an intermediary communication device , in which case the smartphone receives the alert messages sent by the alert notification manager. The smartphone then allows filtering on a broader range of alert messages escalated by the alert notification manager to the
smartphone . The user then can configure the escalated alert messages to the wearable device on his smartphone , offering a greater
flexibility for the user to define the range of alerts he wants to be notified of .
A further embodiment of the invention may provide that the haptic signals are supplemented with visual display messages ( in different colours of screens , using symbols displayed on the screen, or as light flashes ) to provide further contextual information about the alert to the extent that the wearable device is able to produce such signals . The function of these visual display messages is in this case not to transmit the alert or alert message itself to the user, but rather to supply additional information which can be consulted after the user has been notified of the alert by means of the haptic signal or signals .
Again in another embodiment, the alert message is accompanied by a displayed message on the display of the wearable device , requesting an user interaction to be executed by the user of the wearable device , serving as the acknowledgement of the receipt of the alert message by the user . In this case , the wearable device comprises a means to display said acknowledgement request message on its display, and a means to receive the acknowledgement feedback ( such as by receiving a press on a but on on the wearable device, or by a press on a touch sensitive screen of the wearable device) .
Claims
1. System to deliver alert messages from at least one critical service [301] running on a monitored target system [300] to a wearable device [200] , comprising means for :
- receiving incoming sentinel messages over a communications network [400] from at least one critical service [301] running on said moni ored target system,
- processing said incoming sentinel messages by comparing the received alert message content with predefined alert conditions stored in a memory [102] (of the alert notification manager [100] ) ,
- communicating an alert message over a communication network [400] to a wearable device [200] in the case that said sentinel message contains an alert event that matches a predefined alert condition stored in said memory [102] ,
- receiving incoming alert messages on said wearable device [200] over said communicat ion network [400] ,
- converting said alert messages into at least one haptic signal noticeable only by the user of said wearable device [200] .
2. System according to Claim 1, wherein the haptic signal associated with a certain alert condition is delivered to the user of said wearable device [200] in a specific pattern, which is predefined and stored in said memory [102] for each alert condition.
3. System according to Claim 1, wherein the secondary acoustic effects of said haptic signal do not exceed the ambient acoustic level .
4. System according to Claim 1, wherein the haptic signal is adjusted to the ambient acoustic level of the user preventing the generation of perceivable secondary effects of the haptic signal .
5. System according to any of the previous claims , wherein the alert conf igurat ioris can be defined and altered by means of a GUI [104] .
6. System according to any of the previous claims , wherein the wearable computer [200] communicates with a smart phone as
intermediary device to receive the alert messages .
7. System according to any of the previous claims , wherein the haptic messages delivered by the wearable computer are supplemented with visual display messages ( in different colours of screens , or using symbols) to provide further contextual information about the alert .
8. System according to any of the previous claims , wherein the receipt of the alert message by the user has to be acknowledged by performing an action on the wearable device.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP14196956.8 | 2014-12-09 | ||
| EP14196956 | 2014-12-09 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2016091944A1 true WO2016091944A1 (en) | 2016-06-16 |
Family
ID=52144396
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/EP2015/079106 WO2016091944A1 (en) | 2014-12-09 | 2015-12-09 | System to deliver alert messages from at least one critical service running on a monitored target system to a wearable device |
Country Status (1)
| Country | Link |
|---|---|
| WO (1) | WO2016091944A1 (en) |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10261585B2 (en) | 2014-03-27 | 2019-04-16 | Apple Inc. | Adjusting the level of acoustic and haptic output in haptic devices |
| US10372214B1 (en) | 2016-09-07 | 2019-08-06 | Apple Inc. | Adaptable user-selectable input area in an electronic device |
| US10437359B1 (en) | 2017-02-28 | 2019-10-08 | Apple Inc. | Stylus with external magnetic influence |
| US10556252B2 (en) | 2017-09-20 | 2020-02-11 | Apple Inc. | Electronic device having a tuned resonance haptic actuation system |
| US10585480B1 (en) | 2016-05-10 | 2020-03-10 | Apple Inc. | Electronic device with an input device having a haptic engine |
| US10613678B1 (en) | 2018-09-17 | 2020-04-07 | Apple Inc. | Input device with haptic feedback |
| US10649529B1 (en) | 2016-06-28 | 2020-05-12 | Apple Inc. | Modification of user-perceived feedback of an input device using acoustic or haptic output |
| US10768747B2 (en) | 2017-08-31 | 2020-09-08 | Apple Inc. | Haptic realignment cues for touch-input displays |
| US10768738B1 (en) | 2017-09-27 | 2020-09-08 | Apple Inc. | Electronic device having a haptic actuator with magnetic augmentation |
| US10936071B2 (en) | 2018-08-30 | 2021-03-02 | Apple Inc. | Wearable electronic device with haptic rotatable input |
| US10942571B2 (en) | 2018-06-29 | 2021-03-09 | Apple Inc. | Laptop computing device with discrete haptic regions |
| US10966007B1 (en) | 2018-09-25 | 2021-03-30 | Apple Inc. | Haptic output system |
| US11024135B1 (en) | 2020-06-17 | 2021-06-01 | Apple Inc. | Portable electronic device having a haptic button assembly |
| US11054932B2 (en) | 2017-09-06 | 2021-07-06 | Apple Inc. | Electronic device having a touch sensor, force sensor, and haptic actuator in an integrated module |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2002073445A1 (en) * | 2001-03-02 | 2002-09-19 | Computer Associates Think, Inc. | Network management system including a user interface using speech generation and recognition |
| WO2009024557A2 (en) * | 2007-08-22 | 2009-02-26 | International Business Machines Corporation | Apparatus for tonal audio-based monitoring of network alarms |
| US20120286943A1 (en) * | 2011-05-12 | 2012-11-15 | Apple Inc. | Vibration in portable devices |
| US8854925B1 (en) | 2013-04-22 | 2014-10-07 | Lg Electronics Inc. | Smart watch and control method for the same |
-
2015
- 2015-12-09 WO PCT/EP2015/079106 patent/WO2016091944A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2002073445A1 (en) * | 2001-03-02 | 2002-09-19 | Computer Associates Think, Inc. | Network management system including a user interface using speech generation and recognition |
| WO2009024557A2 (en) * | 2007-08-22 | 2009-02-26 | International Business Machines Corporation | Apparatus for tonal audio-based monitoring of network alarms |
| US20120286943A1 (en) * | 2011-05-12 | 2012-11-15 | Apple Inc. | Vibration in portable devices |
| US8854925B1 (en) | 2013-04-22 | 2014-10-07 | Lg Electronics Inc. | Smart watch and control method for the same |
Non-Patent Citations (1)
| Title |
|---|
| MARC SALTZMAN: "Apple Watch For Dummies, Chapter I", 20 July 2015, FOR DUMMIES, article "Tapping With Apple Watch's Haptic Feedback", XP002753162 * |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10261585B2 (en) | 2014-03-27 | 2019-04-16 | Apple Inc. | Adjusting the level of acoustic and haptic output in haptic devices |
| US10585480B1 (en) | 2016-05-10 | 2020-03-10 | Apple Inc. | Electronic device with an input device having a haptic engine |
| US11762470B2 (en) | 2016-05-10 | 2023-09-19 | Apple Inc. | Electronic device with an input device having a haptic engine |
| US10890978B2 (en) | 2016-05-10 | 2021-01-12 | Apple Inc. | Electronic device with an input device having a haptic engine |
| US10649529B1 (en) | 2016-06-28 | 2020-05-12 | Apple Inc. | Modification of user-perceived feedback of an input device using acoustic or haptic output |
| US10372214B1 (en) | 2016-09-07 | 2019-08-06 | Apple Inc. | Adaptable user-selectable input area in an electronic device |
| US10437359B1 (en) | 2017-02-28 | 2019-10-08 | Apple Inc. | Stylus with external magnetic influence |
| US10768747B2 (en) | 2017-08-31 | 2020-09-08 | Apple Inc. | Haptic realignment cues for touch-input displays |
| US11054932B2 (en) | 2017-09-06 | 2021-07-06 | Apple Inc. | Electronic device having a touch sensor, force sensor, and haptic actuator in an integrated module |
| US11460946B2 (en) | 2017-09-06 | 2022-10-04 | Apple Inc. | Electronic device having a touch sensor, force sensor, and haptic actuator in an integrated module |
| US10556252B2 (en) | 2017-09-20 | 2020-02-11 | Apple Inc. | Electronic device having a tuned resonance haptic actuation system |
| US10768738B1 (en) | 2017-09-27 | 2020-09-08 | Apple Inc. | Electronic device having a haptic actuator with magnetic augmentation |
| US10942571B2 (en) | 2018-06-29 | 2021-03-09 | Apple Inc. | Laptop computing device with discrete haptic regions |
| US10936071B2 (en) | 2018-08-30 | 2021-03-02 | Apple Inc. | Wearable electronic device with haptic rotatable input |
| US10613678B1 (en) | 2018-09-17 | 2020-04-07 | Apple Inc. | Input device with haptic feedback |
| US10966007B1 (en) | 2018-09-25 | 2021-03-30 | Apple Inc. | Haptic output system |
| US11805345B2 (en) | 2018-09-25 | 2023-10-31 | Apple Inc. | Haptic output system |
| US11024135B1 (en) | 2020-06-17 | 2021-06-01 | Apple Inc. | Portable electronic device having a haptic button assembly |
| US11756392B2 (en) | 2020-06-17 | 2023-09-12 | Apple Inc. | Portable electronic device having a haptic button assembly |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2016091944A1 (en) | System to deliver alert messages from at least one critical service running on a monitored target system to a wearable device | |
| US10861596B2 (en) | Workflow and resource management system with integrated bi-directional communications | |
| US11363953B2 (en) | Methods and systems for managing medical anomalies | |
| JP5860901B2 (en) | System and method for delivering meaningful clinical alerts | |
| US7671733B2 (en) | Method and system for medical alarm monitoring, reporting and normalization | |
| CA3002096C (en) | Systems and methods for remote and host monitoring communications | |
| KR101474958B1 (en) | Predictive forwarding of notification data | |
| US11096577B2 (en) | Proactive patient health care inference engines and systems | |
| US10262110B2 (en) | Systems and methods for managing patient devices | |
| US11706304B1 (en) | System for setting and controlling functionalities of mobile devices | |
| EP3010398A1 (en) | Processing status information of a medical device | |
| CA2909965A1 (en) | A method and system for healthcare provider tracking | |
| US20150194032A1 (en) | Wellbeing monitor | |
| US20160117901A1 (en) | Managing the delivery of alert messages by an intelligent event notification system | |
| US20170366627A1 (en) | System for executing action feedback and an action feedback method | |
| KR101817643B1 (en) | Method and system for transceiving message through creating variable group in medical institution | |
| US20210319869A1 (en) | Methods and Systems for Interactive Children's Medication and Wellness Tracking | |
| US20170098045A1 (en) | Location-based automated staff-to-patient assignment system and method | |
| US20190221319A1 (en) | System and method for providing workflow-driven communications in an integrated system | |
| AU2018101088A4 (en) | Dead device medic alert relay | |
| US20230368928A1 (en) | Event-based dynamic patient communication | |
| US9749453B2 (en) | Relaxation of mobile device features restrictions leveraging embedded auditing system | |
| US20230177947A1 (en) | System and method for monitoring the health of a user | |
| US20220203109A1 (en) | Monitoring device and method | |
| US20220045978A1 (en) | Prioritizing Communications On A Communication Device |
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: 15807894 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 15807894 Country of ref document: EP Kind code of ref document: A1 |