Event handling
US-2015046933-A1 · Feb 12, 2015 · US
US2017293648A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2017293648-A1 |
| Application number | US-201615094395-A |
| Country | US |
| Kind code | A1 |
| Filing date | Apr 8, 2016 |
| Priority date | Apr 8, 2016 |
| Publication date | Oct 12, 2017 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Apparatus and methods are provided for enabling a sensor device to receive and transmit updates effectively via one or more rules applied to a plurality of event records for transmission by an event management server. In one exemplary embodiment, the event management server manages the plurality of event records (such as records of deletions or updates to a user's profile or goals), via an event suppression application. The event suppression application ensures that event records are not redundantly provided to the sensor device and/or irrelevant records (such as those which no longer contain the most up-to-date information) are not provided to the sensor device. Hence, only the most relevant event records are provided and that those which are not relevant are ignored (not transmitted). In this manner, the sensor device may operate more efficiently to receive only the most relevant transmissions.
Opening claim text (preview).
What is claimed is: 1 . A method of managing a number of event records to be communicated between one or more user devices and a device configured to obtain event data relating to a plurality of users, said method comprising: accessing a list of pending event records at a server entity; determining whether a first one of said pending event records comprises a most recent event of an event record type associated to a single one of said plurality of users; when it is determined that said first one of said pending event records comprises said most recent event of said event record type associated to said single user, transmitting said first one of said pending event records to said device configured to obtain said event data; when it is determined that said first one of said pending event records does not comprise said most recent event of said event record type associated to said single user, omitting to transmit said first one of said pending event records to said device configured to obtain said event data; and performing said acts of determining and transmitting or omitting for each additional event record listed in said list of pending event records. 2 . The method of claim 1 , further comprising determining whether said first one of said pending event records comprises a recognized event type. 3 . The method of claim 2 , wherein when said first one of said pending event records does not comprise a recognized event type, said method further comprises transmitting said first one of said pending event records to said device configured to obtain said event data. 4 . The method of claim 3 , wherein when said first one of said pending event records does not comprise a recognized event type, said method further comprises marking said first one of said pending event records as having been evaluated. 5 . The method of claim 1 , wherein when it is determined that said first one of said pending event records comprises said most recent event of said event record type associated to said first user profile, or when it is determined that said first one of said pending event records does not comprise said most recent event of said event record type associated to said first user profile, said method further comprising marking said first one of said pending event records as having been evaluated. 6 . The method of claim 1 , further comprising determining whether said first one of said pending event records comprises a record indicating a profile deletion associated to said first user profile; and when it is determined that said first one of said pending event records comprises a record indicating said profile deletion associated to said first user profile, omitting to transmit other ones of said pending event records associated to said first profile to said device configured to obtain said event data. 7 . The method of claim 1 , further comprising ending a transmission session when it is determined that no further event records are listed in said list of pending event records. 8 . A server apparatus for management of transmission of a plurality of records relating to a respective plurality of events entered at one or more user devices to at least one health-monitoring device, said server apparatus comprising: at least one interface configured to enable communication with said at least one health-monitoring device; a storage entity; and a processor configured to communicate to said storage entity, and said at least one interface, said processor configured to execute a plurality of health-monitoring computer programs and at least one event management computer program thereon, said event management computer program comprising a plurality of instructions which are configured to, when executed by said processor, cause said server apparatus to: access a plurality of previously unevaluated event records; determine whether a first one of said plurality of previously unevaluated event records comprises a most temporally recent event of an event record type associated to a first user profile within said plurality of said previously unevaluated event records; transmit said first one of said plurality of previously unevaluated event records to said at least one health-monitoring device when it is determined that said first one of said plurality of previously unevaluated event records comprises said most temporally recent event of said event record type associated to said first user profile within said plurality of said previously unevaluated event records; and not transmit said first one of said plurality of previously unevaluated event records to said at least one health-monitoring device when it is determined that said first one of said plurality of previously unevaluated event records does not comprise said most temporally recent event of said event record type associated to said first user profile. 9 . The server apparatus of claim 8 , wherein said determination, transmission and non-transmission occur for each of said plurality of previously unevaluated event records. 10 . The server apparatus of claim 8 , wherein said plurality of instructions are further configured to, when executed by said processor, cause said server apparatus to: determine whether said first one of said plurality of previously unevaluated event records comprises a recognized event type; and when said first one of said plurality of previously unevaluated event records does not comprise said recognized event type, transmit said first one of said plurality of previously unevaluated event records to said at least one health-monitoring device. 11 . The server apparatus of claim 10 , wherein said recognized event type comprises at least one of: a profile-related update, a profile deletion, a goal-related update, and/or a goal deletion. 12 . The server apparatus of claim 10 , wherein said plurality of instructions are further configured to, when executed by said processor, cause said server apparatus to: when said first one of said plurality of previously unevaluated event records does not comprise said recognized event type, place a marker on said first one of said plurality of previously unevaluated event records as having been evaluated. 13 . The server apparatus of claim 8 , wherein said plurality of instructions are further configured to, when executed by said processor, cause said server apparatus to place a marker on said first one of said plurality of previously unevaluated event records as having been evaluated. 14 . The server apparatus of claim 13 , wherein said plurality of instructions are further configured to, when executed by said processor, cause said server apparatus to determine based on a presence of said marker on each of said plurality of previously unevaluated event records that no further event records are pending, and end a transmission session. 15 . The server apparatus of claim 8 , wherein said plurality of instructions are further configured to, when executed by said processor, cause said server apparatus to: when it is determined that said first one of said plurality of previously unevaluated event records comprises a record indicating a profile deletion associated to said first user profile, not transmit any other ones of said plurality of previously unevaluated event records associated to said first profile to said at least one health-monitoring device. 16 . A non-transitory, computer readable medium comprising a plurality of instructions which are configured to, when executed: collect at a server entity a plurality of event records representative of a respective plurality of events ente
using timestamps · CPC title
relating to physical therapies or activities, e.g. physiotherapy, acupressure or exercising · CPC title
for remote operation · CPC title
Monitoring athletic performances, e.g. for determining the work of a user on an exercise apparatus, the completed jogging or cycling distance · CPC title
Indicating or scoring devices for games or players {, or for other sports activities} · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.