# US 2017/0289247 A1 · Systems and methods for synchronizing integrations in a collaboration platform

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

- Number: US 2017/0289247 A1
- Document ID: US20170289247A1
- Status: Published application
- Kind: A1
- Application number: 15/349,739
- Filed: 2016-11-11
- Published: 2017-10-05
- Earliest claimed: 2016-03-31
- Assignees: Atlassian Pty Ltd.
- Applicants: Atlassian Pty Ltd
- Inventors: Julien Hoarau; Michael Oates; Patrick Streule
- Web page: https://patentgrep.com/patent/US20170289247A1

## CPC

- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Described herein is a computer implemented method for operating a collaboration system to synchronize integrations installed on a client device with integrations stored by the collaboration system. The method comprises: receiving a synchronization request from the client device and, for a given integration included in the synchronization request: retrieving a system integration token and comparing a client integration token received in the request with the system integration token. Responsive to determining that the client and system integration tokens do not match, the method further comprises determining the client to be out of date with respect to the given integration and sending an integration update to the client device.

## Claims

### Claim 1

A computer implemented method for operating a collaboration system, the method comprising:
receiving, from a content provider, an initial integration descriptor in respect of an integration;
generating an integration identifier for the integration;
generating an initial integration token for the integration, the initial integration token uniquely identifying the initial version of the integration;
associating, in one or more data structures, the integration identifier with the initial integration descriptor and the initial integration token;
receiving, from a client, an installation request to install the integration in one or more rooms; and
installing the integration in the one or more rooms, wherein installing the integration in the one or more rooms comprises:
identifying, from the installation request, the one or more rooms in which the integration is to be installed;
associating, in the one or more data structures, the integration with each of the one or more rooms identified;
receiving an updated integration descriptor in respect of the integration;
generating an updated integration token for the integration, the updated integration token uniquely identifying the updated version of the integration;
updating the one or more data structures to associate the integration identifier with the updated integration descriptor and the updated integration token;
synchronizing one or more client devices with the updated integration.

### Claim 2 (depends on 1)

The computer implemented method of claim 1, wherein installing the integration further comprises:
identifying one or more members of the one or more rooms identified; and
communicating, to client devices of each of the one or more members identified, the initial integration descriptor.

### Claim 3 (depends on 1)

The computer implemented method of claim 1, wherein the initial integration token is calculated using information in the initial integration descriptor.

### Claim 4 (depends on 1)

The computer implemented method of claim 1, wherein the initial integration descriptor comprises one or more user interface extension descriptors, and wherein the initial integration token is calculated based on the one or more user interface extension descriptors.

### Claim 5 (depends on 1)

The computer implemented method of claim 1, wherein for each of the one or more rooms in which the integration is to be installed the method further comprises:
calculating a room token for the room, the room token uniquely identifying an integration state of the room, the integration state of the room being defined by integrations and versions of those integrations installed in the room; and
associating, in the one or more data structures, the room token with the room.

### Claim 6 (depends on 5)

The computer implemented method of claim 5, wherein the room token for a given room is calculated based on integration tokens of all integrations installed in that given room.

### Claim 7

(canceled)

### Claim 8 (depends on 1)

The computer implemented method of claim 1, wherein synchronizing one or more client devices with the updated integration comprises:
identifying one or more rooms in which the integration is installed;
identifying one or more members of the one or more rooms in which the integration is installed; and
communicating an integration update to client devices of the one or more members identified.

### Claim 9 (depends on 8)

The computer implemented method of claim 8, wherein the one or more members identified are members with client devices that have a current connection with the collaboration system.

### Claim 10 (depends on 1)

The computer implemented method of claim 1, wherein on receiving the updated integration descriptor in respect of the integration the method further comprises:
identifying one or more rooms in which the integration is installed and, for each identified room:
generating an updated room token, the updated room token uniquely identifying an integration state of the room, the integration state of the room being defined by the integrations and versions of those integrations installed in the room; and
updating the one or more data structures to associate the room with the updated room token.

### Claim 11

A collaboration system comprising:
one or more processors;
a communications interface; and
one or more non-transitory computer-readable storage media storing sequences of instructions which, when executed by the one or more processors, cause the one or more processors to:
receive, from a content provider via the communications interface, an initial integration descriptor in respect of an integration;
generate an integration identifier for the integration;
generate an initial integration token for the integration, the initial integration token uniquely identifying the initial version of the integration;
associate, in one or more data structures, the integration identifier with the initial integration descriptor and the initial integration token;
receive, from a client, an installation request to install the integration in one or more rooms; and
install the integration in the one or more rooms, wherein installing the integration in the one or more rooms comprises:
identifying, from the installation request, the one or more rooms in which the integration is to be installed;
associating, in the one or more data structures, the integration with each of the one or more rooms identified;
receive an updated integration descriptor in respect of the integration;
generate an updated integration token for the integration, the updated integration token uniquely identifying the updated version of the integration;
update the one or more data structures to associate the integration identifier with the updated integration descriptor and the updated integration token;
synchronize one or more client devices with the updated integration.

### Claim 12 (depends on 11)

The collaboration system of claim 11, wherein installing the integration further comprises:
identifying one or more members of the one or more rooms identified; and
communicating, to client devices of each of the one or more members identified, the initial integration descriptor.

### Claim 13 (depends on 11)

The collaboration system of claim 11, wherein the initial integration token is calculated using information in the initial integration descriptor.

### Claim 14 (depends on 11)

The collaboration system of claim 11, wherein the initial integration descriptor comprises one or more user interface extension descriptors, and wherein the initial integration token is calculated based on the one or more user interface extension descriptors.

### Claim 15 (depends on 11)

The collaboration system of claim 11, wherein when executed by the one or more processors the sequences of instructions further cause the one or more processors to, for each of the one or more rooms in which the integration is to be installed:
calculate a room token for the room, the room token uniquely identifying an integration state of the room, the integration state of the room being defined by integrations and versions of those integrations installed in the room; and
associate, in the one or more data structures, the room token with the room.

### Claim 16 (depends on 15)

The collaboration system of claim 15, wherein the room token for a given room is calculated based on integration tokens of all integrations installed in that given room.

### Claim 17

(canceled)

### Claim 18 (depends on 11)

The collaboration system of claim 11, wherein synchronizing one or more client devices with the updated integration comprises:
identifying one or more rooms in which the integration is installed;
identifying one or more members of the one or more rooms in which the integration is installed; and
communicating an integration update to client devices of the one or more members identified.

### Claim 19 (depends on 18)

The collaboration system of claim 18, wherein the one or more members identified are members with client devices that have a current connection with the collaboration system.

### Claim 20 (depends on 11)

The collaboration system of claim 11, wherein on receiving the updated integration descriptor in respect of the integration the sequences of instructions further cause the one or more processors to:
identify one or more rooms in which the integration is installed and, for each identified room:
generate an updated room token, the updated room token uniquely identifying an integration state of the room, the integration state of the room being defined by the integrations and versions of those integrations installed in the room; and
update the one or more data structures to associate the room with the updated room token.

### Claim 21

Non-transient computer readable storage comprising instructions which, when executed by a processor, cause the processor to:
receive, from a content provider via the communications interface, an initial integration descriptor in respect of an integration;
generate an integration identifier for the integration;
generate an initial integration token for the integration, the initial integration token uniquely identifying the initial version of the integration;
associate, in one or more data structures, the integration identifier with the initial integration descriptor and the initial integration token;
receive, from a client, an installation request to install the integration in one or more rooms; and
install the integration in the one or more rooms, wherein installing the integration in the one or more rooms comprises:
identifying, from the installation request, the one or more rooms in which the integration is to be installed;
associating, in the one or more data structures, the integration with each of the one or more rooms identified;
receiving an updated integration descriptor in respect of the integration;
generating an updated integration token for the integration, the updated integration token uniquely identifying the updated version of the integration;
updating the one or more data structures to associate the integration identifier with the updated integration descriptor and the updated integration token;
synchronizing one or more client devices with the updated integration.
