# US 2012/0084286 A1 · Method and apparatus for group coordination of calendar events

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

- Number: US 2012/0084286 A1
- Document ID: US20120084286A1
- Status: Published application
- Kind: A1
- Application number: 12/895,243
- Filed: 2010-09-30
- Published: 2012-04-05
- Earliest claimed: 2010-09-30
- Assignees: Verizon Patent and Licensing Inc.
- Inventors: Paul Hubner; Kristopher Pate; Steven T. Archer; Robert A. Clavenna
- Web page: https://patentgrep.com/patent/US20120084286A1

## CPC

- 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

An approach for managing calendar information received from a plurality of data sources is described. Calendar information associated respectively with a plurality of data sources is retrieved by a calendar management platform. For each of the data sources, metadata specifying a contributor of the corresponding calendar information and for relating distribution of the calendar information is determined. Based on the first and second metadata, a data view for the calendar information is generated.

## Claims

### Claim 1

A method comprising:
retrieving calendar information associated respectively with a plurality of data sources;
for each of the data sources, determining, from the calendar information, first metadata specifying a contributor of the corresponding calendar information;
for each of the data sources, determining, from the calendar information, a second metadata relating to distribution of the calendar information; and
generating a data view for the calendar information based on the first metadata and the second metadata.

### Claim 2 (depends on 1)

A method according to claim 1, wherein the data sources correspond respectively to a plurality of devices configured to execute a plurality of calendar applications for outputting the calendar information.

### Claim 3 (depends on 2)

A method according to claim 2, further comprising:
initiating transmission of the data view to the corresponding devices.

### Claim 4 (depends on 2)

A method according to claim 2, wherein one of the calendar applications is different from another one of the calendar applications.

### Claim 5 (depends on 1)

A method according to claim 1, wherein the first metadata specifies a role of the contributor, an owner of the calendar information, or a combination thereof.

### Claim 6 (depends on 1)

A method according to claim 1, further comprising:
for each of the data sources, determining, from the calendar information, a third metadata specifying a filter for a type of event to output to a user group according to the distribution.

### Claim 7 (depends on 1)

A method according to claim 1, further comprising:
receiving a request to subscribe to a calendar service for receiving the data view; and
receiving information relating to one or more devices configured to output the calendar information.

### Claim 8 (depends on 1)

A method according to claim 1, wherein the calendar information includes a plurality of calendar events, the method further comprising:
tagging the calendar events for classification into one of a plurality of user groups.

### Claim 9

An apparatus comprising:
at least one processor; and
at least one memory including computer program code for one or more programs,
the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following,
retrieve calendar information associated respectively with a plurality of data sources,
for each of the data sources, determine, from the calendar information, first metadata specifying a contributor of the corresponding calendar information,
for each of the data sources, determine, from the calendar information, a second metadata relating to distribution of the calendar information, and
generate a data view for the calendar information based on the first metadata and the second metadata.

### Claim 10 (depends on 9)

An apparatus according to claim 9, wherein the data sources correspond respectively to a plurality of devices configured to execute a plurality of calendar applications for outputting the calendar information.

### Claim 11 (depends on 10)

An apparatus according to claim 10, wherein the apparatus is further caused to:
initiate transmission of the data view to the corresponding devices.

### Claim 12 (depends on 10)

An apparatus according to claim 10, wherein one of the calendar applications is different from another one of the calendar applications.

### Claim 13 (depends on 9)

An apparatus according to claim 9, wherein the first metadata specifies role of the contributor, an owner of the calendar information, or a combination thereof.

### Claim 14 (depends on 9)

An apparatus according to claim 9, wherein the apparatus is further caused to:
for each of the data sources, determine, from the calendar information, a third metadata specifying a filter for a type of event to output to a user group according to the distribution.

### Claim 15 (depends on 9)

An apparatus according to claim 9, wherein the apparatus is further caused to:
receive a request to subscribe to a calendar service for receiving the data view; and
receive information relating to one or more devices configured to output the calendar information.

### Claim 16 (depends on 9)

An apparatus according to claim 9, wherein the calendar information includes a plurality of calendar events, and the apparatus is further caused to:
tag the calendar events for classification into one of a plurality of user groups.

### Claim 17

A system comprising:
one or more platforms configured to provide a cloud-based calendar service, each of the platforms being configured to,
retrieve calendar information associated respectively with a plurality of data sources,
for each of the data sources, determine, from the calendar information, first metadata specifying a contributor of the corresponding calendar information,
for each of the data sources, determine, from the calendar information, a second metadata relating to distribution of the calendar information, and
generate a data view for the calendar information based on the first metadata and the second metadata.

### Claim 18 (depends on 17)

A system according to claim 17, wherein the data sources correspond respectively to a plurality of devices configured to execute a plurality of calendar applications for outputting the calendar information.

### Claim 19 (depends on 17)

A system according to claim 17, wherein the first metadata specifies role of the contributor, an owner of the calendar information, or a combination thereof.

### Claim 20 (depends on 17)

A system according to claim 17, each of the platforms being configured to, for each of the data sources, determine, from the calendar information, a third metadata specifying a filter for a type of event to output to a user group according to the distribution.
