# US 8,543,440 B2 · Methods, systems, and computer program products for calendar-based coverage monitoring

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 8,543,440 B2
- Document ID: US8543440B2
- Status: Granted
- Kind: B2
- Application number: 13/525,879
- Filed: 2012-06-18
- Published: 2012-10-11
- Granted: 2013-09-24
- Earliest claimed: 2006-12-22
- Assignees: Scenera Technologies, LLC
- Applicants: Robert J. Sundstrom
- Inventors: Robert J. Sundstrom
- Web page: https://patentgrep.com/patent/US8543440B2

## CPC

- G06Q 10/063118: {Staff planning in a project environment}
- G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q 10/063: Operations research, analysis or management
- G06Q 10/06311: {Scheduling, planning or task assignment for a person or group}
- G06Q 10/109: Time management, e.g. calendars, reminders, meetings or time accounting
- G06Q 10/1093: Calendar-based scheduling for persons or groups
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Methods, systems, and computer program products for calendar-based coverage monitoring are disclosed. According to one aspect, a method includes receiving a coverage rule defining at least one covering entity for performing an activity for a covered entity and at least one period of time during which the multiple covering entities is to perform the activity. Individual calendars for the at least one covering entity are monitored and a change in one of the calendars is detected. It is then determined whether the change causes a threshold criteria to be met, and in response to determining that the change causes the coverage rule to be violated, a coverage warning notification indicating a potential for violation of the coverage rule is automatically generated.

## Claims

### Claim 1

A method for calendar-based coverage monitoring, the method comprising:
receiving a coverage rule defining at least one covering entity for performing an activity for a covered entity and at least one period of time during which the at least one covering entity is to perform the activity;
monitoring individual calendars for the at least one covering entity and detecting a change in at least one of the calendars;
determining whether the change causes a threshold criteria to be met; and
in response to determining that the change causes the threshold criteria to be met, automatically generating a coverage warning notification indicating a potential for violation of the coverage rule,
wherein at least one of the preceding actions is performed on at least one electronic hardware component.

### Claim 2 (depends on 1)

The method of claim 1 further comprising:
determining whether the change causes the coverage rule to be violated; and
in response to determining that the change causes the coverage rule to be violated, automatically generating a notification indicating violation of the coverage rule.

### Claim 3 (depends on 1)

The method of claim 1 wherein receiving a coverage rule includes receiving a coverage rule including one of identification of each of the at least one covering entity, identification of a set including the at least one covering entity, identification of the covered entity, identification of the activity, and information associated with a required number of covering entities for performing the activity for the covered entity.

### Claim 4 (depends on 1)

The method of claim 1 wherein receiving a coverage rule includes receiving a coverage rule defining a minimum number of covering entities for performing the activity during at least one period of time.

### Claim 5 (depends on 1)

The method of claim 1 wherein monitoring individual calendars for the at least one covering entity comprise monitoring individual calendars for each of the at least one covering entity.

### Claim 6 (depends on 1)

The method of claim 1 wherein monitoring individual calendars includes polling for information associated with the individual calendars.

### Claim 7 (depends on 1)

The method of claim 1 wherein monitoring individual calendars includes subscribing to information associated with the individual calendars.

### Claim 8 (depends on 1)

The method of claim 1 wherein monitoring individual calendars includes receiving one of an availability period of time and a non-availability period of time associated with the at least one covering entity, and wherein detecting a change in one of the calendars includes detecting a change to the one of the availability period of time and the non-availability period of time associated with the at least one covering entity.

### Claim 9 (depends on 1)

The method of claim 1 wherein monitoring individual calendars includes monitoring individual calendars until the activity is performed.

### Claim 10 (depends on 1)

The method of claim 1 wherein determining whether the change causes the coverage rule to be violated includes comparing a number of available covering entities after the change for the at least one period of time to the number of covering entities specified by the coverage rule.

### Claim 11 (depends on 1)

The method of claim 1 wherein, in response to determining that the change would cause the number of available covering entities to have a predetermined relationship with respect to the number of covering entities required by the coverage rule, automatically adding a coverage-related calendar event to the at least one of the calendars.

### Claim 12 (depends on 1)

The method of claim 1 comprising determining a coverage rule for a covered entity based on coverage needs of the covered entity by automatically determining coverage needs for a covered entity.

### Claim 13 (depends on 1)

The method of claim 1 comprising receiving calendar information associated with the covered entity and updating the coverage rule based on the calendar information associated with the covered entity.

### Claim 14 (depends on 13)

The method of claim 13 wherein receiving calendar information includes receiving one of event information and a period of time associated with the event information and wherein updating the coverage rule includes updating the coverage rule based on the one of event information and the period of time associated with the event information.

### Claim 15 (depends on 1)

The method of claim 1 comprising determining whether the change would cause a number of available covering entities for the at least one period of time to have a predetermined relationship with respect to the plurality of covering entities required by the coverage rule without violating the coverage rule.

### Claim 16 (depends on 15)

The method of claim 15 wherein, in response to determining that the change would cause the number of available covering entities to have the predetermined relationship, automatically generating a warning notification.

### Claim 17 (depends on 1)

The method of claim 1 further comprising sending the notification to at least one notification recipient.

### Claim 18

A calendar-based coverage monitoring system, the system comprising system components including:
a rule receiver configured to receive a coverage rule defining at least one covering entity for performing an activity for a covered entity and at least one period of time during which the at least one covering entity is to perform the activity; and
a rule monitor configured to:
monitor individual calendars for the at least one covering entity;
detect a change in one of the calendars;
determine whether the change causes a threshold criteria to be met; and
automatically generate a coverage warning notification indicating a potential for violation of the coverage rule in response to determining that the change causes the threshold criteria to be met,
wherein at least one of the system components comprises at least one electronic hardware component.

### Claim 19 (depends on 18)

The system of claim 18 wherein the rule monitor is further configured to: determine whether the change causes the coverage rule to be violated; and automatically generating a notification indicating violation of the coverage rule in response to determining that the change causes the coverage rule to be violated.

### Claim 20 (depends on 18)

The system of claim 18 wherein the rule receiver is configured to receive a coverage rule including one of identification of each of the at least one covering entity, identification of a set of covering entities, identification of the covered entity, identification of the activity, and information associated with a required number of covering entities for performing the activity for the covered entity.

### Claim 21 (depends on 18)

The system of claim 18 wherein the rule monitor is configured to one of poll for and subscribe to information associated with the individual calendars.

### Claim 22 (depends on 18)

The system of claim 18 wherein the rule monitor is configured to monitor individual calendars until the activity is performed.

### Claim 23 (depends on 18)

The system of claim 18 wherein the rule monitor is configured to automatically add a coverage-related calendar event in response to determining that the change would cause the number of available covering entities to have a predetermined relationship with respect to the number of covering entities required by the coverage rule.

### Claim 24 (depends on 18)

The system of claim 18 wherein the rule monitor is configured to determine a coverage rule for a covered entity based on coverage needs of the covered entity by automatically determining coverage needs for a covered entity.

### Claim 25 (depends on 18)

The system of claim 18 wherein the rule monitor is configured to receive calendar information associated with the covered entity and to update the coverage rule based on the calendar information associated with the covered entity.

### Claim 26 (depends on 18)

The system of claim 18 wherein the rule monitor is configured to determine whether the change would cause a number of available covering entities for the at least one period of time to have a predetermined relationship with respect to the plurality of covering entities required by the coverage rule without violating the coverage rule.

### Claim 27 (depends on 26)

The system of claim 26 wherein the rule monitor is configured to automatically generate a warning notification in response to determining that the change would cause the number of available covering entities to have the predetermined relationship with respect to the number of covering entities required by the coverage rule without violating the coverage rule.

### Claim 28 (depends on 18)

The system of claim 18 wherein the rule monitor is configured to automatically determine coverage needs for a covered entity.

### Claim 29 (depends on 18)

The system of claim 18 comprising an availability analysis function configured to analyze calendar information and generate availability information.

### Claim 30 (depends on 18)

The system of claim 18 further comprising an action manager configured to send the notification to at least one notification recipient.

### Claim 31

A calendar-based coverage monitoring system, the system comprising components including:
means for receiving a coverage rule defining at least one covering entity for performing an activity for a covered entity and at least one period of time during which the at least one covering entity is to perform the activity;
means for monitoring individual calendars for the at least one covering entity and detecting a change in one of the calendars;
means for determining whether the change causes a threshold criteria to be met; and
means for automatically generating a coverage warning notification indicating a potential violation of the coverage rule in response to determining that the change causes the threshold criteria to be met,
wherein at least one of the means includes at least one electronic hardware component.

### Claim 32

A computer readable medium containing a computer program, executable by a machine, for determining availability of presentable content via a subscription service, wherein the computer readable medium is not a signal, the computer program comprising executable instructions for:
receiving a coverage rule defining at least one covering entity for performing an activity for a covered entity and at least one period of time during which the at least one covering entity is to perform the activity;
monitoring individual calendars for the at least one covering entity and detecting a change in one of the calendars;
determining whether the change causes a threshold criteria to be met; and
in response to determining that the change causes the a threshold criteria to be met; automatically generating a coverage warning notification indicating a potential for violation of the coverage rule.
