System and method for signaling through data storage

Description

TECHNICAL FIELD

This invention relates generally to the communication field, and more specifically to a new and useful system and method for signaling through data storage in the communication field.

BACKGROUND

The explosion of mobile devices hasn't replaced other types of devices from use. Instead, today's world increasingly sees users with many devices, using them interchangeably to accomplish tasks. On the way to work users check email and chat rooms on mobile phones, and then at work users transition to laptops to continue working. When users enter a conference room, they may transition again to a different machine, but in modern apps the expect context to be maintained across those devices. Building out applications with such robust multi-modal accessibility is challenging and time consuming process. Additionally, many new applications depend on establishing various forms of communication, often real-time messaging communication. However, building such technical solutions is complicated and time consuming. Thus, there is a need in the communication field to create a new and useful system and method for signaling through data storage. This invention provides such a new and useful system and method.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a schematic representation of a system, in accordance with embodiments;

FIG. 2 is a communication flow diagram of data synchronization between multiple clients, in accordance with embodiments;

FIG. 3 is a schematic representation of the technology layers employed in a system, in accordance with embodiments;

FIG. 4 is a flow diagram representation of a method, in accordance with embodiments;

FIGS. 5A-5C are schematic representations of systems, in accordance with embodiments;

FIG. 6 is a sequence diagram representation of a method, in accordance with embodiments;

FIGS. 7A-7B are a sequence diagram representations of a method, in accordance with embodiments;

FIG. 8 is a sequence diagram representation of a method, in accordance with embodiments;

FIG. 9 is an architecture diagram of a data synchronization system, in accordance with embodiments; and

FIG. 10 is an architecture diagram of an application system, in accordance with embodiments.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following description of preferred embodiments of the invention is not intended to limit the invention to these preferred embodiments, but rather to enable any person skilled in the art to make and use this invention.

1. System for Signaling Through Data

As shown in FIG. 1, in some embodiments, a system 100 for signaling through data storage of a preferred embodiment includes a cloud data synchronization system 101 that creates a data synchronization instance 110 to coordinate state management of a set of client devices (devices 131 and 132) with client data synchronization modules (121 and 122). The system 100 functions to provide an alternative approach to signaling between client devices (client devices 131, 132). In some implementations, the system 100 enables an approach to signaling that involves a client (131, 132) accessing a locally stored state representation object (141, 142). In some implementations, the data synchronization instance 110 of the system 100 then synchronizes the state representation object (141, 142) between clients (131, 132). In some implementations, the system 100 is implemented in part through a highly available, cloud-based state management system that handles the ingestion of objects and provides the capability to distribute objects to interested parties. The system 100 can remove much of the complexity and cost of an application developer goes through in building a product with client-managed state. The system 100 may additionally address some of the potential challenges of client-managed state machines such as consistency and flexibility in updating the client.

As shown in the embodiment of FIG. 1, the cloud data synchronization system 101 includes the data synchronization instance 110, and a resolution system 112. The data synchronization instance 110 includes a reference state representation object 111. The client device 131 includes a client data synchronization module 121 and a client application 161. The client device 131 also includes a local state representation object 141 and application logic 151. The client device 132 includes a client data synchronization module 122 and a client application 162. The client device 132 also includes a local state representation object 142 and application logic 152.

As shown in an exemplary application of the system 100 in FIG. 2, a client application (161 of the client device 131) writes data to the state representation object 141. The data represents how the client application 161 wants to update the state. In some implementations, the client application 161 adds a message to a chat conversation. In some implementations, the client application 161 writes directly to the state representation object 141 or uses a framework (such as an application framework). The system 100 automatically synchronizes the desired state changes through the cloud data synchronization system 101. If the desired state change conflicts with the reference state representation object 111, the conflicts are resolved. Then the cloud data synchronization system 101 synchronizes the updated state to a set of clients (132) that are subscribed to updates to that state representation object 111. The set of clients (132) then updates their state to reflect the synchronized update of their local state representation objects (142).

The cloud data synchronization system 101 functions to provide a network accessible resource to manage data synchronization. The cloud data synchronization system 101 can serve as the source of truth concerning state information. Clients (131, 132) synchronize with the cloud data synchronization system 101 rather than resolving various updates from multiple clients to determine their own state. In some implementations, the cloud data synchronization system 101 is hosted in a cloud-based, distributed computing infrastructure. In some implementations, the cloud data synchronization system 101 is hosted on any suitable computing infrastructure. In some implementations, the cloud data synchronization system 101 is accessible over the internet, a local network, or any suitable data connection. In some implementations, the data synchronization system 101 is implemented ad-hoc between multiple clients, where a master client device may run a client-based implementation of the data synchronization system.

In some implementations, the cloud data synchronization system 101 is part of a multi-tenant system wherein multiple and distinct entities can build applications and/or services utilizing the system 101 while sharing common computing resources. In some implementations, the multi-tenant cloud data synchronization system includes an accounting system that partitions usage and configuration by accounts and optionally sub-accounts of parent accounts. For example, an application developer can build a data synchronization solution for a first mobile application, and a second developer can build a data synchronization solution for a different and distinct mobile application. Authentication, configuration, usage, data, billing, and/or other properties of the system can be kept distinct. In some implementations, the system 101 is implemented as a single-tenant system.

In some implementations, the cloud data synchronization system 101 includes a data synchronization storage system, which functions to store data, records, and other information that relates to data synchronization instances (e.g., 110).

In some implementations, the cloud data synchronization system 101 includes at least one programmatic interface. In some implementations, the programmatic interface includes an API. In some implementations, the API is a RESTful API but may alternatively be any suitable API such as SOAP or custom protocol. The RESTful API works according to an application layer request and response model. An application layer request and response model may use an HTTP-based protocol (HTTP or HTTPS), SPDY, or any suitable application layer protocol. Herein, HTTP may be used, but should not be interpreted as being limited to the HTTP protocol. HTTP requests (or any suitable request communication) to the communication platform preferably observe the principles of a RESTful design. RESTful is understood in this document to describe a Representational State Transfer architecture as is known in the art. The RESTful HTTP requests are preferably stateless, thus each message communicated contains all necessary information for processing the request and generating a response. The API service can include various resources, which act as endpoints that can act as a mechanism for specifying requested information or requesting particular actions. The resources can be expressed as URI's or resource paths. The RESTful API resources can additionally be responsive to different types of HTTP methods such as GET, Put, POST and/or DELETE. In some implementations, the data synchronization instances (e.g., 110), aspects of the data synchronization instances, and/or other aspects can be manipulated and accessed as RESTful API resources. In some implementations, the programmatic interface includes a client interface, which enables clients or other devices to interface with the cloud data synchronization system 101. In some implementations, the client interface is a restricted or private API or any suitable programmatic interface. In some implementations, client devices use the public API using a client SDK, library, or native implementation. In some implementations, the system 101 includes an administration user interface. An account or subaccount holder can use the administration user interface to manage data synchronization and state management.

The data synchronization instance 110 functions to encapsulate and characterize the management of data synchronization between clients (e.g., 131, 132). In some implementations, the data synchronization instance 110 is preferably accessible through the programmatic interface(s). In some implementations, a data synchronization instance is uniquely mapped to a session state. In some implementations, an application uses multiple data synchronization sessions, which correspond to multiple, different communication sessions, threads, or channels. For example, an IP messaging application can use a different data synchronization instance for each chat thread.

In some implementations, a data synchronization instance includes option configuration. In some implementations, various options enable control over data handling, access permissions, validation rules, and/or other forms of customization. In some implementations, data handling enables various rules to be enforced related to how the data is stored such as setting how data is stored geographically, how long data is persisted, and/or other suitable options. In some implementations, permissions are set on how the data synchronization instance can be accessed and/or modified. For example, access permissions can be set so that a first set of entities is permitted to edit state while a second set of clients can only access the state. In some implementations, the data synchronization instance 110 manages the state representation object 111 that is synchronized between clients. In some implementation, the state representation object (111, 141, 142) is stored and/or represented in any suitable form. In some implementations, the state representation object (111, 141, 142) is a text-based document that expresses information through a suitable data structure object. In some implementations, the state representation object (111, 141, 142) is one of JSON, plain text, SML, base64 encoded items, or any suitable document type. In some implementations, the state representation object (111, 141, 142) uses key value stores to characterize various properties of the state. In some implementations, standardized protocol/syntax is expected for a state representation object (111, 141, 142). In some implementations, a subset of basic keys and values are required, recommended, and/or optional. For example, a state representation object can follow a basic pattern for indicating how state updates are time stamped and/or prioritized so that conflicts are resolved. In some implementations, at least a portion of the state representation object (111, 141, 142) is highly customized to adapt to the particular application and/or use case. For example, various keys and hierarchical data structures can be used to represent an application's particular state.

In some implementations, the cloud data synchronization system 101 includes a resolution system 112, which functions to process state updates to a data synchronization instance and resolve inconsistencies. In some implementations, a set of rules and/or heuristics are built into the resolution system 112 so that inconsistent state updates made from various clients can be resolved. In some implementations, the resolved state and/or any suitable resolution alerts is communicated to clients (131, 132) through the state representation object (111, 141, 142).

The client data synchronization modules 121, 122 function to act as a client tool for interacting with the data representation object. In some implementations, the client data synchronization modules 121, 122 operate as a component of an application or service on a client device (131, 132). In some implementations, a client device (e.g., 131, 132) is at least one of a phone, a wearable computer, a personal computer, a browser, an IoT device, and/or any suitable computing device. In some implementations, client data synchronization model (121, 122) is part of an SDK, a library, or any development tool. In some implementations, client data synchronization model (121, 122) is provided for a variety of popular device clients (e.g. Android, iPhone, in-browser JavaScript) and server clients (e.g. NodeJS, Ruby on Rails, Java . . . ) languages/platforms. From the developer perspective, a set of tools is provided for interacting with a local state representation object. The synchronization of the state representation object (141, 142) is transparent to the application (161, 162).

The system 100 can be usable without any knowledge of underlying storage, retrieval, and synchronization mechanisms. The system 100 and in particular the data synchronization elements described above can be used with additional technology layers to further power application functionality as shown in FIG. 3. In some embodiments, the system 300 of FIG. 3 is similar to the system 100 of FIG. 1.

In some implementations, the system 331 is similar to the client device 131 of FIG. 1. In some implementations, the cloud data synchronization system 310 is similar to the cloud data synchronization system 101 of FIG. 1.

In some implementations, the system 331 includes an application layer 351 that operates on top of the data synchronization layer 321. In some implementations, the application layer 351 is customized for business logic and functionality specific to the use case. In some implementations, the application layer 351 is an IP messaging layer. In some implementations, as part of an IP messaging layer, a client SDK or library is provided that interfaces with a state representation object 341 to support general IP messaging operations. In some implementations, the application 361 uses the IP messaging layer 351 to create channels, add members, and/or send/read messages. During these operations, the IP messaging layer 351 uses the data synchronization layer 321 to update and read from the data representation object 341 and simultaneously the data representation object 341 is synchronized to various clients as part of a data synchronization instance. In some implementations, the application layer 351 is an IoT (internet of things) device management layer. In some implementations, common IoT tasks and operations are represented in a higher-level abstraction layer that utilizes the underlying data synchronization layer to coordinate operation of multiple IoT devices.

In some implementations, the system 331 includes a connectivity layer 351 that is used by the data synchronization layer 321 to coordinate communication with the cloud 310 and client devices. In some implementations, the connectivity layer 351 is a notification layer that enables push notifications. In some implementations, the connectivity layer 351 is a polling layer that manages how clients and the cloud 310 periodically request updates.

In some implementations, the data synchronization layer 311 is similar to the data synchronization layer 321. In some implementations, the data synchronization layer 311 is similar to the data synchronization instance 110 of FIG. 1. In some implementations, the data synchronization layer 311 is constructed to update and read from a reference data representation object of the cloud data synchronization system 310. In some implementations, the data synchronization layer 311 is constructed to synchronize the reference data representation object of the cloud data synchronization system 310 to various clients as part of a data synchronization instance of the system 310. In some implementations, the data synchronization layer 311 is constructed to update and read from a reference data representation object of the cloud data synchronization system 310, and simultaneously synchronize the reference data representation object of the cloud data synchronization system 310 to various clients as part of a data synchronization instance of the system 310.

In some implementations, the data synchronization instance of the system 310 is similar to the data synchronization instance 110 of FIG. 1.

In some implementations, the reference data representation object of the cloud data synchronization system 310 is similar to the reference state representation object 111 of FIG. 1.

In some implementations, the connectivity layer 312 of the system 310 is similar to the connectivity layer 351. In some implementations, the connectivity layer 312 is used by the data synchronization layer 311 to coordinate communication with the client devices (331). In some implementations, the connectivity layer 312 is a notification layer that enables push notifications. In some implementations, the connectivity layer 312 is a polling layer that manages how clients and the cloud 310 periodically request updates.

2. Method for Signaling Through Data Synchronization

As shown in FIG. 4, a method 400 for signaling through data synchronization of a preferred embodiment can include configuring a data synchronization instance S110, storing a state representation object S120, synchronizing the state representation object S130, and updating the state representation object of a second client S140. The method 400 functions to use synchronization of documents that characterize application state to facilitate communication between a set of client devices (e.g., 131, 132). The method 400 provides an alternative approach to communicating between clients (e.g., 131, 132).

The method 400 can be used in a variety of scenarios. In some implementations, in a first scenario, the method 400 is used to synchronize multiple devices (e.g., 131, 132) of a single account. For example, a mobile phone application and a desktop browser version of some service can be made to be eventually consistence by building on top of the data synchronization layer (e.g., 321). In some implementations, in a second scenario, the method 400 is used in synchronizing communication between multiple devices (e.g., 131, 132) of different accounts. For example, a chat program and the state of the chat can be synchronized between two accounts using the method 400. The state representation object is preferably updated in substantially real-time such that real-time communication can be conveyed. In some implementations, the state representation object of a client device (e.g., 141, 142 of FIG. 1, 341 of FIG. 3) is updated in substantially real-time such that real-time communication can be conveyed. In some implementations, the state representation object of the cloud data synchronization system (e.g., 111 of FIG. 1) is updated in substantially real-time such that real-time communication can be conveyed.

In some embodiments, the method 400 is implemented by a system substantially similar the system 100. In some embodiments, the method 400 is implemented by a system substantially similar the system 300. In some embodiments, the method 400 is implemented by any suitable system. In some implementations, the method 400 is implemented by a system similar to the system 300, and the method 400 is used in combination with an application layer (similar to 351) where the synchronization of state is used to provide an IP messaging framework. In some implementations, the method 400 is implemented by a system similar to the system 300, and the method 400 is used in combination with an application layer (similar to 351) where the synchronization of state is used to provide an IoT device management framework. In some implementations, the method 400 is implemented by a system similar to the system 300, and the method 400 is used in combination with an application layer (similar to 351) where the synchronization of state is used to provide any suitable application framework. In some implementations, the method 400 is used with a connectivity layer (similar to 351, 312) to facilitate how notifications and information is relayed between clients and/or the cloud system.

Block S110, which includes configuring a data synchronization instance (e.g., 110 of FIG. 1), functions to establish resource through which data can be synchronized. In some implementations, configuring a data synchronization instance includes creating the data synchronization instance and setting any customization of the instance. In some implementations, a data synchronization instance is created by an account (of the cloud data synchronization system) prior to when data synchronization capabilities are required, which may be in anticipation of usage by an account or when an account submits a request to begin some task that will utilize data synchronization. In some implementations, a data synchronization instance is created through an administrator user interface. In some implementations, a data synchronization instance is created through a programmatic interface (e.g., REST API). In some implementations, a data synchronization instance is created through a client application request (which may use a private or public programmatic interface). In some implementations, a data synchronization instance is identifiable. In some implementations, a unique identifier is automatically generated during creation. In some implementations, a friendly name is used. In some implementations, the friendly name (and the identifier) is scoped globally within at least one of the platform, within an account or subaccount scope, or with any suitable scope. In some implementations, clients use the identifier when addressing state updates and synchronization. Clients using the same identifier will share information through their respective state representation objects (e.g., 141, 142). In some implementations, a single data synchronization instance (e.g., 110) is used to characterize multiple state representation objects (e.g., 111). This architecture may be used so that various customization options can be simply controlled and managed through a single data synchronization instance (e.g., 110). In some implementations, a data synchronization instance (e.g., 110) is used for the synchronization of a single state representation object (e.g., 111).

In some implementations, setting customization of the instance (e.g., 110) customizes various options of the data synchronization instance (e.g., 110). In some implementations, setting customization includes setting geographic data storage options. In some implementations, geographic data storage options determine which region or regions are used for storing data. In some implementations, the geographic data storage options provide a blacklist of countries, regions, or locations where data should not be stored. In some implementations, setting customization includes setting data encryption settings. In some implementations, data encryption is managed on the edge clients. In some implementations, data encryption options are enabled in association with the data synchronization instance (e.g., 110). In some implementations, setting customization includes setting permissions of the data synchronization instance (e.g., 110), which functions to provide an access control list to enforce policy on interactions with the data synchronization instance. In some implementations, the permissions define the read permissions, write permissions, and/or other management permissions. In some implementations, permissions are set by at least one of account, device identity, device properties, and/or any suitable rule. For example, one account may only have read access permissions and so clients of that account can be driven by the state of the data synchronization instance but may not be able to alter state.

Block S120, which includes storing a state representation object, functions to use a local object (e.g., 141, 142) as a conduit for implying state update requests with connected clients (e.g., 131, 132). In some implementations, storing a state representation object includes storing a reference state representation object (e.g., 111 of FIG. 1) at the cloud data synchronization system (e.g., 101, 310). In some implementations, storing a state representation object includes storing a reference state representation object (e.g., 111 of FIG. 1) of a data synchronization instance (e.g., 110) of the cloud data synchronization system (e.g., 101, 310). In some implementations, the state representation object (e.g., 141, 142) is stored locally within a client device (e.g., 131, 132). For example, an application may store and maintain a local representation of the state representation object. In some implementations, the method 400 includes providing a client data synchronization module (e.g., 121, 122 of FIG. 1), which functions to provide a tool for interacting with a state representation object (e.g., 141, 142). In some implementations, manipulation of the state representation object (e.g., 141, 142) through the client data synchronization module (e.g., 121, 122) allows the state representation object (e.g., 141, 142) to be updated in a controlled and consistent manner. In some implementations, updated state information is added to the state representation object (e.g., 141, 142) along with supporting meta data. For example, a timestamp synchronized to a reference clock can be added to updated information to facilitate resolving conflicts. However, alternative approaches may enable direct manipulation of the state representation object. In some implementations, actions taken to the state representation object (e.g., 141, 142) are performed without consideration of synchronizing state.

In some implementations, a local state representation object (e.g., 141, 142) is stored for each client application (e.g., 161, 162). In some implementations, a state representation object is stored in the cloud data synchronization system (e.g., 101, 310). In some implementations, the cloud data synchronization system (e.g., 101, 310) includes a single reference source of truth representation (e.g., 111). In some implementations, the cloud data synchronization system (e.g., 101, 310) includes various instances of the state representation object, which depend on the reference source. In some implementations, a local state representation object (e.g., 141, 142) is created in association with an identifier of a data synchronization instance (e.g., 110). State representation objects of other client instances (e.g., 132, 134 of FIG. 2) that use a corresponding identifier will also be synchronized with the reference representation object (e.g., 111). In some implementations, local storage of the state representation object (e.g., 141, 142) functions to provide recovery during connectivity interruption. If a client device loses network access, the application can continue to update state. Updates made while offline are eventually resolved when connectivity is re-established.

In some implementations, the method 400 includes providing an application layer (e.g., 151, 152 of FIG. 1, 351 of FIG. 3) to interface with the state representation object (e.g., 141, 142, 341), which functions to abstract management of the state representation object into a set of application-specific interactions. In some implementations, an application-specific SDK or library is provided that utilizes a state representation object (e.g., 141, 142, 341). In some implementations, an IP messaging application layer (e.g., 351) provides higher-level business level to the management of chat channels, channel participants, and message history. From the developer perspective, instructions are made to create and join a chat channel and to add a message. Instructions are transformed into state updates that are characterized in the state representation object. In some implementations the application layers includes at least one of an IoT device management layer, a video conferencing layer, a customer service layer, a gaming layer, and/or any suitable application layer.

Block S130, which includes synchronizing the state representation object, functions to coordinate communication of state updates. Changes to the local state representation object (e.g., 141, 142, 341) are detected within the client (e.g., 131, 132, 331) and then uploaded to the cloud data synchronization system (e.g., 101, 310). Similarly, outside changes to a state representation object (e.g., 142) by another client (e.g., 132) are transferred and applied to the local version (e.g., 141) on the client (e.g., 131). In some implementations, updates are transmitted to the remote cloud system (e.g., 101, 310) in response to a change. In some implementations, a minimum time since the last update is enforced to limit the number of notifications transmitted to the cloud system (e.g., 101, 310). In some implementations, updates are transmitted periodically. In some implementations, the cloud system (e.g., 101, 310) requests updates from the client (e.g., 131, 132, 331). In other words, the cloud system (e.g., 101, 310) polls the clients (e.g., 131, 132, 331) for updates. Any suitable approach may be used in how and when updates are synchronized between clients and the cloud system. Synchronizing the state representation object additionally includes distributing state information updates to a client (e.g., 131, 132, 331). In some implementations, updates are transmitted back to the clients (e.g., 131, 132) in response to updates made to the reference representation (e.g., 111) of state information in the cloud (e.g., 110). In some implementations, the updates are transferred and handled through the client data synchronization module (e.g., 121, 122) in block S140 such that the end application logic (e.g., 151, 152, 162, 162) built by the developer does not need to process incoming updates—the updates are automatically synchronized. For example, if the client is a user application, the view of the application can be reactive to changes in the state representation object such that any synchronized updates can be automatically reflected in the state of the user application.

In some implementations, the full state representation object is transferred between the clients and cloud system. In some implementations, the differences or partial representations are transmitted to reduce the amount of data transferred during each update. In some implementations, synchronizing the state representation object includes the cloud system (e.g., 101, 310) tracking the version of state representation for associated clients. The version information can be used to determine which clients need updates.

In some implementations, the method 400 includes providing a connectivity layer (e.g., 351), which functions to provide a framework that manages how the information and alerts are transmitted between the clients and the cloud system. In some implementations, the connectivity layer (e.g., 351) uses any suitable communication transport layer such as a HTTP-based protocol (HTTP or HTTPS), SPDY, or any suitable transport protocol. In some implementations, the connectivity layer (e.g., 351) facilitates push notifications where updates can be actively pushed or transmitted to appropriate entities. In some implementations, in the case of sending an update from the cloud system to a client, the update is accompanied by a notification such as a push notification displayed within the operating system of the client device. In some implementations, the connectivity layer specifies a polling process in which the clients and/or the cloud system poll for updates.

In some implementations, synchronizing the state representation object includes resolving conflicts. In some implementations, the cloud system receives updated state information from a plurality of clients. In some implementations, updates to the state representation may conflict with updates from one or more other clients. For example, if one client made changes during a temporary lack of connectivity, those changes could be in conflict with changes made by other clients. In some implementations, the cloud system processes the various updates from clients and determines a resolution that incorporates the changes into a single state representation. In some implementations, time based prioritization of updates are used. In some implementations, rules are defined on how particular updates are prioritized and resolved. In some implementations, rules are pre-configured as part of the configuration of a data synchronization instance. In some implementations, resolving conflicts includes retrieving resolution guidance from an outside source. For example, a configured callback URI can be messaged over HTTP/S with relevant information. In some implementations, the relevant information includes current reference state information and the conflicting state updates. In some implementations, the system of the callback URI sends a response that includes instructions on how to resolve the conflict.

Block S140, which includes updating the operational state of a second client based on the state representation object, functions to make an application or service react to synchronized changes to the state representation object. In some implementations, a client data synchronization module (e.g., 121, 122) includes a framework for signaling when the state representation object (e.g., 141, 142) was updated. In some implementations, how the state representation object (e.g., 141, 142) was updated is communicated. In some implementations, the application logic (e.g., 151, 152) is built to automatically respond to changes in the state representation object (e.g., 141, 142).

The use of synchronized state representation data can provide an alternative to request response signaling in a communication application. All the state information that is to be communicated between clients is preferably represented within the state representation object (e.g., 141, 142), and so inbound communications or state changes are communicated through the state representation object (e.g., 141, 142) as opposed to signaling messages transmitted through some protocol.

As one exemplary use case, the method for signaling through data synchronization can be applied to a messaging application. In some implementations, the messaging application is designed using a data synchronization and IP messaging framework that facilitates the use of a data representation object (e.g., 141, 142, 341) in synchronization with a cloud system (e.g., 101, 310). In some implementations, a first client application (e.g., 161) creates a new chat channel to communicate with the other channels. In some implementations, a data synchronization instance (e.g., 110) is created and a set of client applications preferably joins the data synchronization instance. In some implementations, a local data representation object (e.g., 141, 142, 341) or file is established on each of the client devices (e.g., 131, 132, 331). In some implementations, the state of the local data representation object (e.g., 141, 142) represents the properties of the channel such as channel name, members, channel permissions, and/or other settings. These channel properties are synchronized across all the local data representation objects. Then a client application will post a new message. That client will add the new message as an element in the state representation object, and the state representation object will be synchronized with the cloud system. The cloud system will update the reference version of the state representation object and transmit the updated information to the other clients. In some implementations, the clients update their display to represent the new message. In some implementations, subsequent messages, media, and/or other channel interactions is communicated using the state representation object.

3. Application Platform Systems

FIGS. 5A-C are schematic representations of application platform systems 501-503, in accordance with embodiments. In some implementations, the state objects of FIGS. 5A-C (e.g., 521-526, 551-554, 561-568, 591) are files. In some implementations, the state objects of FIGS. 5A-C (e.g., 521-526, 551-554, 561-568, 591) are files stored in a file system. In some implementations, the state objects of FIGS. 5A-C (e.g., 521-526, 551-554, 561-568, 591) are text files. In some implementations, the state objects of FIGS. 5A-C (e.g., 521-526, 551-554, 561-568, 591) are human-readable files. In some implementations, the state objects of FIGS. 5A-C (e.g., 521-526, 551-554, 561-568, 591) are XML files.

FIG. 5A

In some implementations, the application platform system 501 of FIG. 5A provides a service of the application server system 531 to client systems 511 and 512. In some implementations, the service of the application server system 531 is a communication service that provides for communication between the client system 511 and the client system 512. In some implementations, the service of the application server system 531 is a communication service that provides a chat session for communication between the client system 511 and the client system 512.

The application platform system 501 includes the client systems 511 and 512, the DSS 520, and the application server system 531.

The client system 511 includes a local client API state object 523 and a local communication state object 561. In some implementations, the local communication state object 561 is a chat channel state object. The client system 512 includes a local client API state object 524 and a local communication state object 562. In some implementations, the local communication state object 562 is a chat channel state object.

The DSS 520 includes a data synchronization instance 541 for an account of the DSS (“Account A”). The data synchronization instance 541 includes a reference API state object 521, a reference API state object 522, and a reference communication state object 551. In some implementations, the reference communication state object 551 is a chat channel state object.

The application server system 531 includes a local server API state object 525, a local server API state object 526, and a local communication state object 563. In some implementations, the local communication state object 563 is a chat channel state object.

In some implementations, the local communication state objects 561, 562 and 563 are synchronized with the reference communication state object 551. In some implementations, the local client API state object 523 and the local server API state object 525 are synchronized with the reference API state object 521. In some implementations, the local client API state object 524 and the local server API state object 526 are synchronized with the reference API state object 522. In some implementations, the local client API state object 523, the local server API state object 525, and the reference API state object 521 provide communication between the client system 511 and the application server system 531. In some implementations, the local client API state object 523, the local server API state object 525, and the reference API state object 521 provide communication of API requests and API responses of an API of the application server system 531 between the client system 511 and the application server system 531.

In some implementations, the local client API state object 524, the local server API state object 526, and the reference API state object 522 provide communication between the client system 512 and the application server system 531. In some implementations, the local client API state object 524, the local server API state object 526, and the reference API state object 522 provide communication of API requests and API responses of an API of the application server system 531 between the client system 512 and the application server system 531.

In some implementations, the state objects 523, 521 and 525 include API request data and API response data communicated between the client system 511 and the application server system 531. In some implementations, the state objects 524, 522 and 526 include API request data and API response data communicated between the client system 512 and the application server system 531. In some implementations, API request data includes at least one of: create new chat API request data, join chat request data, add participant request data, send message to chat request data. In some implementations, API response data includes at least one of: create new chat API response data, join chat response data, add participant response data, send message to chat response data.

In some implementations, create new chat API request data includes at least one of chat title and chat description. In some implementations, create new chat API response data includes at least one of request execution status, an identifier of a reference state object (e.g., 551) for the created chat, and a unique identifier of the chat channel.

In some implementations, join chat request data includes at least the unique identifier of the chat channel. In some implementations, join chat response data includes at least one of request execution status and an identifier of a reference state object (e.g., 551) for the joined chat.

In some implementations, add participant request data includes at least one of the unique identifier of the chat channel and a username of a participant to be added to the chat channel. In some implementations, add participant response data includes at least one of request execution status and an identifier of a reference state object (e.g., 551) for the chat.

In some implementations, send message to chat request data includes at least one of the unique identifier of the chat channel and a chat message. In some implementations, send message to chat response data includes at least one of request execution status and a unique identifier of the sent chat message.

In some implementations, the local communication state objects 561, 562 and 563 and the reference communication state object 551 provide communication between the client system 511 and the client system 512. In some implementations, the local communication state objects 561, 562 and 563 and the reference communication state object 551 provide chat channel communication between the client system 511 and the client system 512.

In some implementations, the state objects 561, 562, 563 and 551 include message data communicated between the client system 511 and the client system 512. In some implementations, the state objects 561, 562, 563 and 551 include chat channel state data for a chat channel in which the client system 511 and the client system 512 participate. In some implementations, the chat channel state includes chat messages of the chat channel. In some implementations, the chat channel state includes at least one of chat identifier, chat title, chat description, list of chat messages and their properties (e.g., sender, time stamp, read status), list of chat participants and their properties (e.g., role).

In some implementations, the client systems 511 and 512, the data synchronization instance 541, and the application server system 531 are associated with a first DSS account (e.g., “Account A”) of a plurality of accounts managed by an account system (not shown) of the DSS 520. In some implementations, the client systems 511 and 512, and the application server system 531 are systems of an account holder of a first DSS account (e.g., “Account A”) of a plurality of accounts managed by an account system (not shown) of the DSS 520. In some implementations, the client systems 511 and 512, and the application server system 531 are external to the DSS 520.

In some implementations, the client systems 511 and 512 are similar to the client systems 131 and 132 of FIG. 1. In some implementations, the client systems 511 and 512 are similar to the client system 331 of FIG. 3. In some implementations, the state objects 561, 562, 563, and 523-526 are similar to the state objects 141 and 142 of FIG. 1. In some implementations, the state objects 561, 562, 563, and 523-526 are similar to the state object 341FIG. 3. In some implementations, the state objects 521, 522 and 551 are similar to the state object 111 of FIG. 1. In some implementations, the DSS 520 is similar to the cloud data synchronization system 101 of FIG. 1. In some implementations, the DSS 520 is similar to the cloud data synchronization system 310 of FIG. 3. In some implementations, the data synchronization instance 541 is similar to the data synchronization instance 110 of FIG. 1. In some implementations, the DSS 520 includes a resolution system similar to the resolution system 112 of FIG. 1. In some implementations, the application server system 531 is similar to the client devices 131 and 132 of FIG. 1. In some implementations, the application server system 531 is similar to the client device 331 of FIG. 3.

In some implementations, a first set of one or more data synchronization instances for the DSS account of the application server system 531 manages the reference communication state objects of the DSS account of the application server system 531, and a second set of one or more data synchronization instances for the DSS account of the application server system 531 manages the reference API state objects of the DSS account of the application server system 531. In some implementations, each state object of the DSS account of the application server system 531 is managed by a different data synchronization instance for the DSS account of the application server system 531.

In some implementations, the application server system 531 provides a plurality of communication channels, the application server system 531 includes a local communication state object (similar to 563) for each communication channel, and the DSS 520 includes a reference communication state object (similar to 551) for each communication channel. In some implementations, each communication channel is a chat channel. In some implementations, each reference communication state object for the DSS account of the application server system 531 is managed by a single data synchronization instance for the DSS account of the application server system 531. In some implementations, a plurality of data synchronization instances for the DSS account of the application server system 531 manage the plurality of reference communication state objects for the DSS account of the application server system 531.

FIG. 5B

In some implementations, the application platform system 502 of FIG. 5B provides a service of the application server system 532 to client systems 513 and 514. In some implementations, the service of the application server system 532 is a cloud service, and the DSS 520 provides request/response communication between the client system 513 and the application server 532, and between the client system 514 and the application server 532.

The application platform system 502 includes the client systems 513 and 514, the DSS 520, and the application server system 532.

The client system 513 includes a local client API state object 564. The client system 514 includes a local client API state object 565.

The DSS 520 includes a data synchronization instance 542 for an account of the DSS (“Account B”). The data synchronization instance 542 includes a reference API state object 552 and a reference API state object 553.

The application server system 532 includes a local server API state object 566, and a local server API state object 591.

In some implementations, the local client API state object 564 and the local server API state object 566 are synchronized with the reference API state object 552. In some implementations, the local client API state object 565 and the local server API state object 591 are synchronized with the reference API state object 553.

In some implementations, the local client API state object 564, the local server API state object 566, and the reference API state object 552 provide communication between the client system 513 and the application server system 532. In some implementations, the local client API state object 564, the local server API state object 566, and the reference API state object 552 provide communication of API requests and API responses of an API of the application server system 532 between the client system 513 and the application server system 532.

In some implementations, the local client API state object 565, the local server API state object 591, and the reference API state object 553 provide communication between the client system 514 and the application server system 532. In some implementations, the local client API state object 565, the local server API state object 591, and the reference API state object 553 provide communication of API requests and API responses of an API of the application server system 532 between the client system 514 and the application server system 532.

In some implementations, the state objects 552, 564 and 566 include API request data and API response data communicated between the client system 513 and the application server system 532. In some implementations, the state objects 553, 565 and 591 include API request data and API response data communicated between the client system 514 and the application server system 532.

In some implementations, the client systems 513 and 514, the data synchronization instance 542, and the application server system 532 are associated with a second DSS account (e.g., “Account B”) of a plurality of accounts managed by an account system (not shown) of the DSS 520. In some implementations, the client systems 513 and 514, and the application server system 532 are systems of an account holder of a second DSS account (e.g., “Account B”) of a plurality of accounts managed by an account system (not shown) of the DSS 520. In some implementations, the client systems 513 and 514, and the application server system 532 are external to the DSS 520.

In some implementations, the client systems 513 and 514 are similar to the client systems 131 and 132 of FIG. 1. In some implementations, the client systems 513 and 514 are similar to the client system 331 of FIG. 3. In some implementations, the state objects 564, 565, 566 and 591 are similar to the state objects 141 and 142 of FIG. 1. In some implementations, the state objects 564, 565, 566 and 591 are similar to the state object 341FIG. 3. In some implementations, the state objects 552 and 553 are similar to the state object 111 of FIG. 1. In some implementations, the data synchronization instance 542 is similar to the data synchronization instance 541. In some implementations, the application server system 532 is similar to the application server system 531.

In some implementations, the DSS 520 manages reference API state objects for a plurality of DSS accounts. In some implementations, the DSS 520 manages reference API state objects for a plurality of DSS accounts, and each DSS account is associated with at least one application server system that communicates API requests and responses of an API of the application server system with at least one client system by synchronizing local API state objects with the reference API state object managed by the DSS.

In some implementations, a plurality of client systems (e.g., the client system 513 and another client system, not shown) are constructed to synchronize their respective local client API state objects (e.g., 564) with the same reference API state object (e.g., 552). In some implementations, a first device (e.g., a mobile phone) used by a first user communicates with the application server system 532 via the DSS 520, and the DSS 520 stores the application state of the communication in the reference API state object 552 of the DSS; when the first user transitions to a second device (e.g., a laptop), the second device used by the first user accesses the reference API state object 552 of the DSS to obtain the user's application state. In this manner, application state can be maintained across a plurality of devices used by a user.

FIG. 5C

In some implementations, the application platform system 503 of FIG. 5C provides communication between the client system 515 and the client system 516. In some implementations, the application platform system 503 of FIG. 5C provides peer-to-peer communication between the client system 515 and the client system 516. In some implementations, the application platform system 503 of FIG. 5C provides ad-hoc communication between the client system 515 and the client system 516. In some implementations, the application platform system 503 of FIG. 5C provides communication between the client system 515 and the client system 516, and the client system 515 and the client system 516 are both IoT devices. In some implementations, the application platform system 503 of FIG. 5C provides communication between the client system 515 and the client system 516, and the client system 515 and the client system 516 are both IoT devices each including an IoT management layer module.

The application platform system 503 includes the client systems 515 and 516, and the DSS 520.

The client system 515 includes a local communication state object 567. In some implementations, the local communication state object 567 is a chat channel state object. The client system 516 includes a local communication state object 568. In some implementations, the local communication state object 568 is a chat channel state object.

The DSS 520 includes a data synchronization instance 543 for an account of the DSS (“Account C”). The data synchronization instance 543 includes a reference communication state object 554. In some implementations, the reference communication state object 554 is a chat channel state object.

In some implementations, the local communication state objects 567 and 568 are synchronized with the reference communication state object 554.

In some implementations, the local communication state objects 567 and 568, and the reference communication state object 554 provide communication between the client system 515 and the client system 516. In some implementations, the local communication state objects 567 and 568, and the reference communication state object 554 provide chat channel communication between the client system 515 and the client system 516.

In some implementations, the client systems 515 and 516, and the data synchronization instance 543 are associated with a third DSS account (e.g., “Account C”) of a plurality of accounts managed by an account system (not shown) of the DSS 520. In some implementations, the client systems 515 and 516 are systems of an account holder of a third DSS account (e.g., “Account C”) of a plurality of accounts managed by an account system (not shown) of the DSS 520. In some implementations, the client systems 515 and 516 are external to the DSS 520.

In some implementations, the client systems 515 and 516 are similar to the client systems 131 and 132 of FIG. 1. In some implementations, the client systems 515 and 516 are similar to the client system 331 of FIG. 3. In some implementations, the state objects 567 and 568 are similar to the state objects 141 and 142 of FIG. 1. In some implementations, the state objects 567 and 568 are similar to the state object 341FIG. 3. In some implementations, the state object 554 is similar to the state object 111 of FIG. 1. In some implementations, the DSS 520 is similar to the cloud data synchronization system 101 of FIG. 1. In some implementations, the DSS 520 is similar to the cloud data synchronization system 310 of FIG. 3. In some implementations, the data synchronization instance 543 is similar to the data synchronization instance 110 of FIG. 1. In some implementations, the DSS 520 includes a resolution system similar to the resolution system 112 of FIG. 1.

In some implementations, the DSS 520 manages reference communication state objects for a plurality of DSS accounts.

4. Application Platform Methods

FIG. 6

The method 600 of FIG. 6 is performed at an application platform system (e.g., 501-503 of FIGS. 5A-5C). In some implementations, the application platform system includes a first application system 610 (e.g., one of 511-516 and 531-532 of FIGS. 5A-C), a second application system 620 (e.g., a different one of 511-516 and 531-532 of FIGS. 5A-C), and a multi-tenant data synchronization system (DSS) 630 (e.g., 520 of FIG. 5). In some implementations, the first application system 610 is similar to at least one of 131 and 132 of FIG. 1, 331 of FIG. 3, and 511-516 and 531-532 of FIGS. 5A-C, and the second application system 620 is similar to at least one of 131 and 132 of FIG. 1, 331 of FIG. 3, and 511-516 and 531-532 of FIGS. 5A-C. In some implementations, the DSS 630 is similar to at least one of the cloud data synchronization system 101 of FIG. 1, the cloud data synchronization system 310 of FIG. 2, and the DSS 520 of FIGS. 5A-C.

In some embodiments, the method 600 includes: the DSS 630 configuring a first data synchronization instance (e.g., 541, 542, 543) for a first account of the DSS (e.g., “Account A”, “Account B”, “Account C”), responsive to a request provided by a system of the first account, wherein the first data synchronization instance manages a first reference state representation object (e.g., 521, 522, 551-554) for the first account at the DSS (process S601); the first application system 610 storing a first local state representation object (e.g., 523-526, 561-568, 591) that corresponds to the first reference state representation object of the DSS, wherein the first application system is constructed to receive first reference state representation object update notifications provided by the DSS (process S602); the second application system 620 storing a second local state representation object (e.g., 523-526, 561-568, 591) that corresponds to the first reference state representation object of the DSS, wherein the second application system is constructed to receive first reference state representation object update notifications provided by the DSS (process S603); the first application system 610 transforming a first application instruction of the first application system into a first state update, and modifying the first local state representation object to include the first state update (process S604); the first application system 610 providing at least the first state update of the modified first local state representation object to the DSS via a first local state representation object update notification (process S605); responsive to the first state update, the DSS 630 determining whether to modify the first reference state representation object of the DSS to include the first state update (process S606); responsive to a determination by the DSS to modify the first reference state representation object to include the first state update, the DSS 630 modifying the first reference state representation object to include the first state update (process S607); the DSS 630 providing at least the first state update to the second application system via a first reference state representation object update notification (process S608); and responsive to the first state update, the second application system 620 modifying the second local state representation object to include the first state update (process S609). The first application system 610 and the second application system 620 communicate by using the DSS.

In some embodiments, the method 600 includes: the second application system transforming a second application instruction of the second application system into a second state update, and modifying the second local state representation object to include the second state update; and the second application system providing at least the second state update of the modified second local state representation object to the DSS. The DSS determining whether to modify the first state representation object of the DSS to include the first state update includes: the DSS determining whether the first state update conflicts with the second state update; and responsive to a determination that the first state update conflicts with the second state update, the DSS resolving the conflict between the first state update and the second state update.

In some embodiments, the first application system is a client system (e.g., 511-516) that includes a first client application (e.g., 161, 162 of FIG. 1, 361 of FIG. 3), and the second application system is a client system (e.g., a different one of 511-516) that includes a second client application. In some embodiments, first client application and the second client application are chat client applications of a chat service provided by the system (e.g., 531) of the first account (e.g., “Account A”), the first application instruction is a chat client application instruction, and the chat service (e.g., a chat service of the server system 531) is constructed to receive first reference state representation object update notifications. In some embodiments, the chat client application instruction includes at least one of: an instruction to add a message to a chat channel, and an instruction to add a participant to a chat channel.

In some embodiments, the first application system is an application server system (e.g., 531-532) that includes a first application server, the first application server system is the system that provides the request to configure the first data synchronization instance (e.g., 541, 542) for the first account, the second application system is a client system (e.g., 511-514) that includes a first client application, and the first client application and the first application server communicate via the DSS 520.

In some embodiments, the first application system is a client system (e.g., 511-514) that includes a first client application, the second application system is an application server system (e.g., 531-532) that includes a first application server, at least one of the application server system and the client system is the system that provides the request to configure the first data synchronization instance (e.g., 541, 542) for the first account, and the first client application and the first application server communicate via the DSS 520. In some embodiments, the method 600 includes: the application server system (e.g., 531-532) determining whether the first state update corresponds to a command of the first application server; and responsive to a determination by application server system (e.g., 531-532) that the first state update corresponds to a command of the first application server, the application server system (e.g., 531-532) executing the command and providing a response to the client system via the DSS 520.

In some embodiments, the system of the first account provides the request to configure the first data synchronization instance via at least one of an administrator user interface and a programmatic interface. In some embodiments, the system of the first account is at least one of the first application system and the second application system.

In some embodiments, the DSS 520 configuring the first data synchronization instance (the process S601) includes: the DSS 520 configuring at least one option of the first data synchronization instance (e.g., 541-543), and the at least one option includes at least one of: a geographic data storage option, a data encryption setting, and a permission of the data synchronization instance.

In some embodiments, the first application system stores the first local state representation object (e.g., 523-526, 561-568 and 591) responsive to at least one of: a communication provided by the second application system, a communication provided by the DSS 520, a communication provided by the system of the first account, and an application instruction of a first application of the first application system.

In some embodiments, the first application system storing the first local state representation object (e.g., 523-526, 561-568 and 591) includes: storing the first local state representation object in association with an identifier of the first data synchronization instance (e.g., 541-543), and the second application system storing the second local state representation object includes: storing the second local state representation object in association with the identifier of the first data synchronization instance (e.g., 54-543). In some implementations, the first application system receives the identifier of the first data synchronization instance from at least one of: the second application system, the DSS 520, the system of the first account, and an application instruction of a first application of the first application system. In some implementations, the second application system receives the identifier of the first data synchronization instance from at least one of: the first application system, the DSS 520, the system of the first account, and an application instruction of a second application of the second application system.

In some embodiments, the first application system storing the first local state representation object includes: storing the first local state representation object (e.g., 523-526, 561-568 and 591) in association with an identifier of the first state representation object (e.g., one of 521, 522, 551-554) of the DSS 520, and the second application system storing the second local state representation object includes: storing the second local state representation object in association with the identifier of the first state representation object (e.g., one of 521, 522, 551-554) of the DSS 520.

In some implementations, the first application system receives the identifier of the first state representation object from at least one of: the second application system, the DSS 520, the system of the first account, and an application instruction of a first application of the first application system. In some implementations, the second application system receives the identifier of the first state representation object from at least one of: the first application system, the DSS 520, the system of the first account, and an application instruction of a second application of the second application system.

In some embodiments, the first application system is constructed to receive first reference state representation object update notifications provided by the DSS 520 via a push notification module (e.g., 351 of FIG. 3) of the first application system, and the second application system is constructed to receive first reference state representation object update notifications provided by the DSS 520 via a push notification module (e.g., 351 of FIG. 3) of the second application system. In some embodiments, the first application system is constructed to subscribe to first reference state representation object update notifications provided by the DSS 520 via the push notification module of the first application system, and the second application system is constructed to subscribe to first reference state representation object update notifications provided by the DSS 520 via the push notification module of the second application system.

In some implementations, the first application system is constructed to receive first reference state representation object update notifications provided by the DSS 520 via a polling module of the first application system that periodically requests first reference state representation object update notifications from the DSS, and the second application system is constructed to receive first reference state representation object update notifications provided by the DSS via a polling module of the second application system that periodically requests first reference state representation object update notifications from the DSS.

In some implementations, the DSS is external to each of the first application system and the second application system.

FIG. 7

The method 700 of FIGS. 7A-B is performed at a chat system. In some implementations, the application platform system 501 of FIG. 5A is a chat system, and the method 700 is performed by the application platform system 501. In some implementations, the application platform system 501 includes a first chat client system (e.g., 511 of FIG. 5A), a second chat client system (e.g., 512 of FIG. 5A), a multi-tenant data synchronization system (DSS) (e.g., 520 of FIG. 5A), and a chat application server system (e.g., the application server system 531 of FIG. 5A).

In some embodiments, the method 700 includes: the first chat client system 511 transforming a first chat client application instruction to join a first chat channel into a first request state update (process S701); the system 511 modifying a first local application programming interface (API) state object 523 stored at the first chat client system 511 to include the first request state update (process S702); the system 511 providing the first request state update to the DSS 520 via a first local API state update notification (process S703); the second chat client system 512 transforming a second chat client application instruction to join the first chat channel into a second request state update (process S704); the system 512 modifying a second local API state object 524 stored at the second chat client system 512 to include the second request state update (process S705); the system 512 providing the second request state update to the DSS via a second local API state update notification (process S706); the DSS 520 modifying a first reference API state object 521 stored at the DSS 520 to include the first request state update (process S707); the DSS 520 providing the first request state update to the chat application server system 531 via a first reference API state update notification (process S708); the DSS 520 modifying a second reference API state object 522 stored at the DSS 520 to include the second request state update (process S709); the DSS 520 providing the second request state update to the chat application server system 531 via a second reference API state update notification (process S710); the chat application server system 531 modifying a first local API state object 525 stored at the chat application server system 531 to include the first request state update (process S711); the system 531 processing the first request state update by updating first chat channel state of the first chat channel to include a user of the first chat client application (of the system 511) as a participant of the first chat channel (process S712); the system 531 modifying the first local API state object 525 stored at the chat application server system 531 to include a first response state update that includes an identifier for a first reference chat channel state object 551, wherein the first reference chat channel state object 551 includes the first chat channel state (process S713); the system 531 providing the first response state update to the DSS 520 via a third local API state update notification (process S714); the system 531 modifying a second local API state object 526 stored at the chat application server system 531 to include the second request state update (process S715); the system 531 processing the second request state update by updating first chat channel state of the first chat channel to include a user of the second chat client application (of the system 512) as a participant of the first chat channel (process S716); the system 531 modifying the second local API state object 526 stored at the chat application server system 531 to include a second response state update that includes the identifier for the first reference chat channel state object 551 (process S717); the system 531 providing the second response state update to the DSS 520 via a fourth local API state update notification (process S718); the DSS 520 modifying the first reference API state object 521 stored at the DSS 520 to include the first response state update (process S719); the DSS 520 providing the first response state update to the first chat client system 511 via a third reference API state update notification (process S720); the DSS 520 modifying the second reference API state object 522 stored at the DSS 520 to include the second response state update (process S721); the DSS 520 providing the second response state update to the second chat client system 512 via a fourth reference API state update notification (process S722); the first chat client system 511 storing a first local chat channel state object 561 in association with the identifier for the first reference chat channel state object 551 (process S723); and the second chat client system 512 storing a second local chat channel state object 562 in association with the identifier for the first reference chat channel state object 551 (process S724). The first chat client system 511 sends a message via the first chat channel by modifying the first local chat channel state object 561 which is synchronized with the second local chat channel state object 562 via the first reference chat channel state object 551. The second chat client system 512 sends a message via the first chat channel by modifying the second local chat channel state object 562 which is synchronized with the first local chat channel state object 561 via the first reference chat channel state object 551.

In some embodiments, the first chat client system 511, the second chat client system 512, the chat application server system 531, the first reference chat channel state object 551, the first local chat channel state object 561, the second local chat channel state object 562, the first reference API state object 521, the second reference API state object 522, the first local API state object 523, the second local API state object 524, the first local API state object 525, and the a second local API state object 526 are associated with a first DSS account (e.g., “Account A”) managed by an account system of the DSS 520.

In some implementations, the DSS 520 is constructed to resolve conflicting updates to the first reference chat channel state object 551 received from the first chat client system 511 and the second chat client system 512. In some implementations, the DSS is constructed to resolve conflicting updates to the first reference chat channel state object 551 received from the first chat client system 511 and the second chat client system 512 by using a resolution system similar to the resolution system 112 of FIG. 1.

FIG. 8

The method 800 of FIG. 8 is performed at an application platform system (e.g., 501-502 of FIGS. 5A-5B). In some implementations, the application platform system includes a first client system (e.g., 513 of FIG. 5B), a multi-tenant data synchronization system (DSS) (e.g., 520 of FIG. 5B), and a first application server system (e.g., 532 of FIG. 5B).

In some embodiments, the method 800 includes: the first client system 513 transforming a first application instruction of a first client application (e.g., an application similar to at least one of 161 and 162 of FIG. 1, and 361 of FIG. 3) of the first client system 513 into a first request state update (process S801); the system 513 modifying a first local client application programming interface (API) state object 564 stored at the first client system to include the first request state update (process S802); the system 513 providing the first request state update to the DSS 520 via a first local client API state update notification (process S803); the DSS 520 modifying a first reference API state object 552 stored at the DSS 520 to include the first request state update (process S804); the DSS 520 providing the first request state update to a first application server system 532 of the application platform system via a first reference API state update notification (process S8005); the first application server system 532 modifying a first local server API state object 566 stored at the first application server system 532 to include the first request state update (process S806); the first application server system 532 processing the first request state update by updating first application state at the first application server system 532 for the first client application and generating first response data (process S807); the first application server system 532 modifying the first local server API state object 566 to include the generated first response data (process S808); the first application server system 532 providing the first response data to the DSS 520 via a first local server API state update notification (process S809); the DSS 520 modifying the first reference API state object 552 stored at the DSS 520 to include the first response data (process S810); and the DSS 520 providing the first response data to the first client system 513 via a second reference API state update notification (process S811).

In some embodiments, the first local client API state object 564 and the first local server API state object 566 are synchronized with the first reference API state object 552, and the first client system 513 and the first application server system 532 communicate by using the DSS 520. In some embodiments, the first local client API state object 564, the first reference API state object 552, and the first local server API state object 566 are associated with a first DSS account (e.g., “Account B”) of a plurality of accounts managed by an account system (not shown) of the DSS 520. In some embodiments, the first client system 513 and the first application server system 532 are systems of an account holder of the first DSS account (e.g., “Account B”).

In some implementations, the DSS 520 is external to each of the first client system 513 and the first application server system 532. In some implementations, the first client system 513 transforms the first state response update into an application callback of the first client application of the first client system 513.

5. System Architecture

Data Synchronization System

FIG. 9 is an architecture diagram of a data synchronization system (e.g., 101 of FIG. 1, 310 of FIG. 3, and 520 of FIGS. 5A-C) according to an implementation in which the system is implemented by a server device. In some implementations, the system is implemented by a plurality of devices. In some implementations, the system 900 is similar to the system 101 of FIG. 1. In some implementations, the system 900 is similar to the system 310 of FIG. 3. In some implementations, the system 900 is similar to the system 520 of FIGS. 5A-C.

The bus 901 interfaces with the processors 901A-901N, the main memory (e.g., a random access memory (RAM)) 922, a read only memory (ROM) 904, a processor-readable storage medium 905, and a network device 911. In some implementations, the system 900 includes at least one of a display device and a user input device.

The processors 901A-901N may take many forms, such as ARM processors, X86 processors, and the like.

In some implementations, the system (e.g., 520) includes at least one of a central processing unit (processor) and a multi-processor unit (MPU).

The processors 901A-901N and the main memory 922 form a processing unit 999. In some embodiments, the processing unit includes one or more processors communicatively coupled to one or more of a RAM, ROM, and machine-readable storage medium; the one or more processors of the processing unit receive instructions stored by the one or more of a RAM, ROM, and machine-readable storage medium via a bus; and the one or more processors execute the received instructions. In some embodiments, the processing unit is an ASIC (Application-Specific Integrated Circuit). In some embodiments, the processing unit is a SoC (System-on-Chip). In some embodiments, the processing unit includes one or more data synchronization instances.

The network adapter device 911 provides one or more wired or wireless interfaces for exchanging data and commands between the system (e.g., 520) and other devices, such as an external system (e.g., 511-516, 531, 532). Such wired and wireless interfaces include, for example, a universal serial bus (USB) interface, Bluetooth interface, Wi-Fi interface, Ethernet interface, near field communication (NFC) interface, and the like.

Machine-executable instructions in software programs (such as an operating system, application programs, and device drivers) are loaded into the memory 922 (of the processing unit 999) from the processor-readable storage medium 905, the ROM 904 or any other storage location. During execution of these software programs, the respective machine-executable instructions are accessed by at least one of processors 901A-901N (of the processing unit 999) via the bus 901, and then executed by at least one of processors 901A-901N. Data used by the software programs are also stored in the memory 922, and such data is accessed by at least one of processors 901A-901N during execution of the machine-executable instructions of the software programs. The processor-readable storage medium 905 is one of (or a combination of two or more of) a hard drive, a flash drive, a DVD, a CD, an optical disk, a floppy disk, a flash storage, a solid state drive, a ROM, an EEPROM, an electronic circuit, a semiconductor memory device, and the like. The processor-readable storage medium 905 includes machine-executable instructions (and related data) for an operating system 912, software programs 913, and device drivers 914. The processor-readable storage medium 905 includes machine-executable instructions (and related data) for at least one data synchronization instance (e.g., 541-543). In some implementations, the processor-readable storage medium 905 includes instructions (and related data) for at least one of a notification module (e.g., 312 of FIG. 3) and a resolution system (e.g., 112 of FIG. 1).

Application System

FIG. 10 is an architecture diagram of an application system 1000 (e.g., one of 131, 132 of FIG. 1, 331 of FIG. 3, 511-516 of FIGS. 5A-C, and one of 531-532 of FIGS. 5A-B) according to an implementation in which the application system is implemented by a computing device. In some implementations, the application system is implemented by a plurality of devices.

The bus 1001 interfaces with the processors 1001A-1001N, the main memory (e.g., a random access memory (RAM)) 1022, a read only memory (ROM) 1004, a processor-readable storage medium 1005, and a network device 1011. In some implementations, the external system includes a display device and a user input device.

The processors 1001A-1001N may take many forms, such as ARM processors, X86 processors, and the like.

In some implementations, the computing device 1000 includes at least one of a central processing unit (processor) and a multi-processor unit (MPU).

The processors 1001A-1001N and the main memory 1022 form a processing unit 1099. In some embodiments, the processing unit includes one or more processors communicatively coupled to one or more of a RAM, ROM, and machine-readable storage medium; the one or more processors of the processing unit receive instructions stored by the one or more of a RAM, ROM, and machine-readable storage medium via a bus; and the one or more processors execute the received instructions. In some embodiments, the processing unit is an ASIC (Application-Specific Integrated Circuit). In some embodiments, the processing unit is a SoC (System-on-Chip).

The network adapter device 1011 provides one or more wired or wireless interfaces for exchanging data and commands between the application system and other devices, such as the system DSS 520 of FIGS. 5A-B. Such wired and wireless interfaces include, for example, a universal serial bus (USB) interface, Bluetooth interface, Wi-Fi interface, Ethernet interface, near field communication (NFC) interface, and the like.

Machine-executable instructions in software programs (such as an operating system, application programs, and device drivers) are loaded into the memory 1022 (of the processing unit 1099) from the processor-readable storage medium 1005, the ROM 1004 or any other storage location. During execution of these software programs, the respective machine-executable instructions are accessed by at least one of processors 1001A-1001N (of the processing unit 1099) via the bus 1001, and then executed by at least one of processors 1001A-1001N. Data used by the software programs are also stored in the memory 1022, and such data is accessed by at least one of processors 1001A-1001N during execution of the machine-executable instructions of the software programs. The processor-readable storage medium 1005 is one of (or a combination of two or more of) a hard drive, a flash drive, a DVD, a CD, an optical disk, a floppy disk, a flash storage, a solid state drive, a ROM, an EEPROM, an electronic circuit, a semiconductor memory device, and the like. The processor-readable storage medium 1005 includes machine-executable instructions (and related data) for an operating system 1012, software programs 1013, and device drivers 1014. In some implementations in which the application system 1000 is a client system, the processor-readable storage medium 1005 includes machine-executable instructions (and related data) for at least one of a client application, a client data synchronization module, an application layer module, an IP messaging module, an IoT device management module, a notification module, and a connectivity layer module. In some implementations in which the application system 1000 is a client system, the processor-readable storage medium 1005 includes at least one local state object.

In some implementations in which the application system 1000 is an application server system, the processor-readable storage medium 1005 includes machine-executable instructions (and related data) for at least one of a server application, a data synchronization module, a server application layer module, a notification module, and a connectivity layer module. In some implementations in which the application system 1000 is an application server system, the processor-readable storage medium 1005 includes at least one local state object.

6. Machines

The system and method of the preferred embodiment and variations thereof can be embodied and/or implemented at least in part as a machine configured to receive a computer-readable medium storing computer-readable instructions. The instructions are preferably executed by computer-executable components preferably integrated with the media intelligence platform. The computer-readable medium can be stored on any suitable computer-readable media such as RAMs, ROMs, flash memory, EEPROMs, optical devices (CD or DVD), hard drives, floppy drives, or any suitable device. The computer-executable component is preferably a general or application specific processor, but any suitable dedicated hardware or hardware/firmware combination device can alternatively or additionally execute the instructions.

7. Conclusion

As a person skilled in the art will recognize from the previous detailed description and from the figures and claims, modifications and changes can be made to the preferred embodiments of the invention without departing from the scope of this invention defined in the following claims.

Claims

1. A method comprising: receiving, by a data synchronization system (DSS), a first Application Programming Interface (API) state update message directed to a data synchronization instance corresponding to a first account of the DSS, the first API state update message received from a first client and identifying an update to a first local API state object maintained by the first client, the data synchronization instance being a resource of the DSS that was generated for the first account to facilitate data synchronization, the first API state update message being directed to the data synchronization by including a unique identifier that is assigned to the data synchronization instance;updating an API reference state object maintained by the DSS based on the first API state update message, the API reference state object corresponding to the first account of the DSS; andtransmitting a second API state update message to a second client that is subscribed to the data synchronization instance, the second API state update message identifying an update to the API reference state object, the second client updating a second local API state object maintained by the second client based on second API state update message.
2. The method of claim 1, wherein the update to first local API state object indicates a modification made to an active chat communication on the first client.
3. The method of claim 2, wherein the first local API state object corresponds to the active chat communication.
4. The method of claim 3, wherein the second client is engaged in the active chat communication, the second API state update indicating the modification made to the active chat communication on the first client.
5. The method of claim 3, wherein the second local API state object maintained by the second client corresponds to the active chat communication that is on the second client.
6. The method of claim 3, further comprising: receiving, from the second client, a third API state update message directed to the data synchronization instance corresponding to the first account, the third API state updated message identifying a second update to the second local API state object maintained by the second client, the third API state update message identifying a modification made to the active chat communication on the second client; andupdating the API reference state object based on the second API state update message.
7. The method of claim 1, further comprising: transmitting a fourth API state update message to the first client, the fourth API state update message identifying a second update to the second local API state object maintained by the second client, the first client updating the first local API state object maintained by the first client based on fourth API state update message.
8. A data synchronization system (DSS) comprising: one or more computer processors; andone or more computer-readable mediums storing instructions that, when executed by the one or more computer processors, cause the DSS to perform operations comprising:receiving a first Application Programming Interface (API) state update message directed to a data synchronization instance corresponding to a first account of the DSS, the first API state update message received from a first client and identifying an update to a first local API state object maintained by the first client, the data synchronization instance being a resource of the DSS that was generated for the first account to facilitate data synchronization, the first API state update message being directed to the data synchronization by including a unique identifier that is assigned to the data synchronization instance;updating an API reference state object maintained by the DSS based on the first API state update message, the API reference state object corresponding to the first account of the DSS; andtransmitting a second API state update message to a second client that is subscribed to the data synchronization instance, the second API state update message identifying an update to the API reference state object, the second client updating a second local API state object maintained by the second client based on second API state update message.
9. The DSS of claim 8, wherein the update to first local API state object indicates a modification made to an active chat communication on the first client.
10. The DSS of claim 9, wherein the first local API state object corresponds to the active chat communication.
11. The DSS of claim 10, wherein the second client is engaged in the active chat communication, the second API state update indicating the modification made to the active chat communication on the first client.
12. The DSS of claim 10, wherein the second local API state object maintained by the second client corresponds to the active chat communication that is on the second client.
13. The DSS of claim 10, the operations further comprising: receiving, from the second client, a third API state update message directed to the data synchronization instance corresponding to the first account, the third API state updated message identifying a second update to the second local API state object maintained by the second client, the third API state update message identifying a modification made to the active chat communication on the second client; andupdating the API reference state object based on the second API state update message.
14. The DSS of claim 8, the operations further comprising: transmitting a fourth API state update message to the first client, the fourth API state update message identifying a second update to the second local API state object maintained by the second client, the first client updating the first local API state object maintained by the first client based on fourth API state update message.
15. A non-transitory computer-readable medium storing instructions that, when executed by one or more computer processors of a data synchronization system (DSS), cause the DSS to perform operations comprising: receiving a first Application Programming Interface (API) state update message directed to a data synchronization instance corresponding to a first account of the DSS, the first API state update message received from a first client and identifying an update to a first local API state object maintained by the first client, the data synchronization instance being a resource of the DSS that was generated for the first account to facilitate data synchronization, the first API state update message being directed to the data synchronization by including a unique identifier that is assigned to the data synchronization instance;updating an API reference state object maintained by the DSS based on the first API state update message, the API reference state object corresponding to the first account of the DSS; andtransmitting a second API state update message to a second client that is subscribed to the data synchronization instance, the second API state update message identifying an update to the API reference state object, the second client updating a second local API state object maintained by the second client based on second API state update message.
16. The non-transitory computer-readable medium of claim 15, wherein the update to first local API state object indicates a modification made to an active chat communication on the first client.
17. The non-transitory computer-readable medium of claim 16, wherein the first local API state object corresponds to the active chat communication and the second client is engaged in the active chat communication, the second API state update indicating the modification made to the active chat communication on the first client.
18. The non-transitory computer-readable medium of claim 17, wherein the second local API state object maintained by the second client corresponds to the active chat communication that is on the second client.
19. The non-transitory computer-readable medium of claim 17, the operations further comprising: receiving, from the second client, a third API state update message directed to the data synchronization instance corresponding to the first account, the third API state updated message identifying a second update to the second local API state object maintained by the second client, the third API state update message identifying a modification made to the active chat communication on the second client; andupdating the API reference state object based on the second API state update message.
20. The non-transitory computer-readable medium of claim 15, the operations further comprising: transmitting a fourth API state update message to the first client, the fourth API state update message identifying a second update to the second local API state object maintained by the second client, the first client updating the first local API state object maintained by the first client based on fourth API state update message.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 15/914,401, filed 7 May 2018, which is a continuation of U.S. patent application Ser. No. 15/154,700, filed 13 May 2016, which claims the benefit of U.S. Provisional Application Ser. No. 62/265,557, filed on 10 Dec. 2015, U.S. Provisional Application Ser. No. 62/163,270, filed on 18 May 2015, U.S. Provisional Application Ser. No. 62/161,724, filed on 14 May 2015, and U.S. Provisional Application Ser. No. 62/161,719, filed on 14 May 2015, all of which are incorporated in their entirety by this reference.

US Referenced Citations (780)

Number	Name	Date	Kind
5274700	Gechter et al.	Dec 1993	A
5526416	Dezonno et al.	Jun 1996	A
5581608	Jreij et al.	Dec 1996	A
5598457	Foladare et al.	Jan 1997	A
5867495	Elliott et al.	Feb 1999	A
5934181	Adamczewski	Aug 1999	A
5978465	Corduroy et al.	Nov 1999	A
6026440	Shrader et al.	Feb 2000	A
6034946	Roginsky et al.	Mar 2000	A
6094681	Shaffer et al.	Jul 2000	A
6138143	Gigliotti et al.	Oct 2000	A
6185565	Meubus et al.	Feb 2001	B1
6192123	Grunsted et al.	Feb 2001	B1
6206564	Adamczewski	Mar 2001	B1
6223287	Douglas et al.	Apr 2001	B1
6232979	Shochet	May 2001	B1
6269336	Ladd et al.	Jul 2001	B1
6317137	Rosasco	Nov 2001	B1
6363065	Thornton et al.	Mar 2002	B1
6373836	Deryugin et al.	Apr 2002	B1
6425012	Trovato et al.	Jul 2002	B1
6426995	Kim et al.	Jul 2002	B1
6430175	Echols et al.	Aug 2002	B1
6434528	Sanders	Aug 2002	B1
6445694	Swartz	Sep 2002	B1
6445776	Shank et al.	Sep 2002	B1
6459913	Cloutier	Oct 2002	B2
6463414	Su et al.	Oct 2002	B1
6493558	Bernhart et al.	Dec 2002	B1
6496500	Nance et al.	Dec 2002	B2
6501739	Cohen	Dec 2002	B1
6501832	Saylor et al.	Dec 2002	B1
6507875	Mellen-Garnett et al.	Jan 2003	B1
6571245	Huang et al.	May 2003	B2
6574216	Farris et al.	Jun 2003	B1
6577721	Vainio et al.	Jun 2003	B1
6600736	Ball et al.	Jul 2003	B1
6606596	Zirngibl et al.	Aug 2003	B1
6614783	Sonesh et al.	Sep 2003	B1
6625258	Ram et al.	Sep 2003	B1
6625576	Kochanski et al.	Sep 2003	B2
6636504	Albers et al.	Oct 2003	B1
6662231	Drosset et al.	Dec 2003	B1
6704785	Koo et al.	Mar 2004	B1
6707889	Saylor et al.	Mar 2004	B1
6711129	Bauer et al.	Mar 2004	B1
6711249	Weissman et al.	Mar 2004	B2
6738738	Henton	May 2004	B2
6757365	Bogard	Jun 2004	B1
6765997	Zirngibl et al.	Jul 2004	B1
6768788	Langseth et al.	Jul 2004	B1
6771955	Imura et al.	Aug 2004	B2
6778653	Kallas et al.	Aug 2004	B1
6785266	Swartz	Aug 2004	B2
6788768	Saylor et al.	Sep 2004	B1
6792086	Saylor et al.	Sep 2004	B1
6792093	Barak et al.	Sep 2004	B2
6798867	Zirngibl et al.	Sep 2004	B1
6807529	Johnson et al.	Oct 2004	B2
6807574	Partovi et al.	Oct 2004	B1
6819667	Brusilovsky et al.	Nov 2004	B1
6820260	Flockhart et al.	Nov 2004	B1
6829334	Zirngibl et al.	Dec 2004	B1
6831966	Tegan et al.	Dec 2004	B1
6834265	Balasuriya	Dec 2004	B2
6836537	Zirngibl et al.	Dec 2004	B1
6842767	Partovi et al.	Jan 2005	B1
6850603	Eberle et al.	Feb 2005	B1
6870830	Schuster et al.	Mar 2005	B1
6873952	Bailey et al.	Mar 2005	B1
6874084	Dobner et al.	Mar 2005	B1
6885737	Gao et al.	Apr 2005	B1
6888929	Saylor et al.	May 2005	B1
6895084	Saylor et al.	May 2005	B1
6898567	Balasuriya	May 2005	B2
6912581	Johnson et al.	Jun 2005	B2
6922411	Taylor	Jul 2005	B1
6928469	Duursma et al.	Aug 2005	B1
6931405	El-shimi et al.	Aug 2005	B2
6937699	Schuster et al.	Aug 2005	B1
6940953	Eberle et al.	Sep 2005	B1
6941268	Porter et al.	Sep 2005	B2
6947417	Laursen et al.	Sep 2005	B2
6947988	Saleh et al.	Sep 2005	B1
6961330	Cattan et al.	Nov 2005	B1
6964012	Zirngibl et al.	Nov 2005	B1
6970915	Partovi et al.	Nov 2005	B1
6977992	Zirngibl et al.	Dec 2005	B2
6981041	Araujo et al.	Dec 2005	B2
6985862	Strom et al.	Jan 2006	B2
6999576	Sacra	Feb 2006	B2
7003464	Ferrans et al.	Feb 2006	B2
7006606	Cohen et al.	Feb 2006	B1
7010586	Allavarpu et al.	Mar 2006	B1
7020685	Chen et al.	Mar 2006	B1
7039165	Saylor et al.	May 2006	B1
7058042	Bontempi et al.	Jun 2006	B2
7058181	Wright et al.	Jun 2006	B2
7062709	Cheung	Jun 2006	B2
7065637	Nanja	Jun 2006	B1
7076037	Gonen et al.	Jul 2006	B1
7076428	Anastasakos et al.	Jul 2006	B2
7089310	Ellerman et al.	Aug 2006	B1
7099442	Da Palma et al.	Aug 2006	B2
7103003	Brueckheimer et al.	Sep 2006	B2
7103171	Annadata et al.	Sep 2006	B1
7106844	Holland	Sep 2006	B1
7111163	Haney	Sep 2006	B1
7136932	Schneider	Nov 2006	B1
7140004	Kunins et al.	Nov 2006	B1
7143039	Stifelman et al.	Nov 2006	B1
7197331	Anastasakos et al.	Mar 2007	B2
7197461	Eberle et al.	Mar 2007	B1
7197462	Takagi et al.	Mar 2007	B2
7197544	Wang et al.	Mar 2007	B2
D540074	Peters	Apr 2007	S
7225232	Elberse	May 2007	B2
7227849	Rasanen	Jun 2007	B1
7245611	Narasimhan et al.	Jul 2007	B2
7260208	Cavalcanti	Aug 2007	B2
7266181	Zirngibl et al.	Sep 2007	B1
7269557	Bailey et al.	Sep 2007	B1
7272212	Eberle et al.	Sep 2007	B2
7272564	Phillips et al.	Sep 2007	B2
7277851	Henton	Oct 2007	B1
7283515	Fowler	Oct 2007	B2
7283519	Girard	Oct 2007	B2
7286521	Jackson et al.	Oct 2007	B1
7287248	Adeeb	Oct 2007	B1
7289453	Riedel et al.	Oct 2007	B2
7296739	Mo et al.	Nov 2007	B1
7298732	Cho	Nov 2007	B2
7298834	Homeier et al.	Nov 2007	B1
7308085	Weissman	Dec 2007	B2
7308408	Stifelman et al.	Dec 2007	B1
7324633	Gao et al.	Jan 2008	B2
7324942	Mahowald et al.	Jan 2008	B1
7328263	Sadjadi	Feb 2008	B1
7330463	Bradd et al.	Feb 2008	B1
7330890	Partovi et al.	Feb 2008	B1
7340040	Saylor et al.	Mar 2008	B1
7349714	Lee et al.	Mar 2008	B2
7369865	Gabriel et al.	May 2008	B2
7373660	Guichard et al.	May 2008	B1
7376223	Taylor et al.	May 2008	B2
7376586	Partovi et al.	May 2008	B1
7376733	Connelly et al.	May 2008	B2
7376740	Porter et al.	May 2008	B1
7412525	Cafarella et al.	Aug 2008	B2
7418090	Reding et al.	Aug 2008	B2
7428302	Zirngibl et al.	Sep 2008	B2
7440898	Eberle et al.	Oct 2008	B1
7447299	Partovi et al.	Nov 2008	B1
7454459	Kapoor et al.	Nov 2008	B1
7457249	Baldwin et al.	Nov 2008	B2
7457397	Saylor et al.	Nov 2008	B1
7473872	Takimoto	Jan 2009	B2
7486780	Zirngibl et al.	Feb 2009	B2
7496054	Taylor	Feb 2009	B2
7496188	Saha et al.	Feb 2009	B2
7496651	Joshi	Feb 2009	B1
7500249	Kampe et al.	Mar 2009	B2
7505951	Thompson et al.	Mar 2009	B2
7519359	Chiarulli et al.	Apr 2009	B2
7522711	Stein et al.	Apr 2009	B1
7536454	Balasuriya	May 2009	B2
7542761	Sarkar	Jun 2009	B2
7552054	Stifelman et al.	Jun 2009	B1
7571226	Partovi et al.	Aug 2009	B1
7606868	Le et al.	Oct 2009	B1
7613287	Stifelman et al.	Nov 2009	B1
7623648	Oppenheim et al.	Nov 2009	B1
7630900	Strom	Dec 2009	B1
7631310	Henzinger	Dec 2009	B1
7644000	Strom	Jan 2010	B1
7657433	Chang	Feb 2010	B1
7657434	Thompson et al.	Feb 2010	B2
7668157	Weintraub et al.	Feb 2010	B2
7672275	Yajnik et al.	Mar 2010	B2
7672295	Andhare et al.	Mar 2010	B1
7675857	Chesson	Mar 2010	B1
7676221	Roundtree et al.	Mar 2010	B2
7685280	Berry et al.	Mar 2010	B2
7685298	Day et al.	Mar 2010	B2
7715547	Ibbotson et al.	May 2010	B2
7716293	Kasuga et al.	May 2010	B2
7742499	Erskine et al.	Jun 2010	B1
7779065	Gupta et al.	Aug 2010	B2
7809125	Brunson et al.	Oct 2010	B2
7809791	Schwartz et al.	Oct 2010	B2
7875836	Imura et al.	Jan 2011	B2
7882253	Pardo-Castellote et al.	Feb 2011	B2
7920866	Bosch et al.	Apr 2011	B2
7926099	Chakravarty et al.	Apr 2011	B1
7929562	Petrovykh	Apr 2011	B2
7936867	Hill et al.	May 2011	B1
7949111	Harlow et al.	May 2011	B2
7962644	Ezerzer et al.	Jun 2011	B1
7979555	Rothstein et al.	Jul 2011	B2
7992120	Wang et al.	Aug 2011	B1
8023425	Raleigh	Sep 2011	B2
8024785	Andress et al.	Sep 2011	B2
8045689	Provenzale et al.	Oct 2011	B2
8046378	Zhuge et al.	Oct 2011	B1
8046823	Begen et al.	Oct 2011	B1
8069096	Ballaro et al.	Nov 2011	B1
8078483	Hirose et al.	Dec 2011	B1
8081744	Sylvain	Dec 2011	B2
8081958	Soderstrom et al.	Dec 2011	B2
8103725	Gupta et al.	Jan 2012	B2
8126128	Hicks, III et al.	Feb 2012	B1
8126129	Mcguire	Feb 2012	B1
8130750	Hester	Mar 2012	B2
8130917	Helbling et al.	Mar 2012	B2
8139730	Da Palma et al.	Mar 2012	B2
8145212	Lopresti et al.	Mar 2012	B2
8149716	Ramanathan et al.	Apr 2012	B2
8150918	Edelman et al.	Apr 2012	B1
8156213	Deng et al.	Apr 2012	B1
8165116	Ku et al.	Apr 2012	B2
8166185	Samuel et al.	Apr 2012	B2
8169936	Koren et al.	May 2012	B2
8175007	Jain et al.	May 2012	B2
8185619	Maiocco et al.	May 2012	B1
8196133	Kakumani et al.	Jun 2012	B2
8204479	Vendrow et al.	Jun 2012	B2
8214868	Hamilton et al.	Jul 2012	B2
8218457	Malhotra et al.	Jul 2012	B2
8233611	Zettner	Jul 2012	B1
8238533	Blackwell et al.	Aug 2012	B2
8243889	Taylor et al.	Aug 2012	B2
8249552	Gailloux et al.	Aug 2012	B1
8266327	Kumar et al.	Sep 2012	B2
8295272	Boni et al.	Oct 2012	B2
8301117	Keast et al.	Oct 2012	B2
8306021	Lawson et al.	Nov 2012	B2
8315198	Corneille et al.	Nov 2012	B2
8315369	Lawson et al.	Nov 2012	B2
8315620	Williamson et al.	Nov 2012	B1
8319816	Swanson et al.	Nov 2012	B1
8326805	Arous et al.	Dec 2012	B1
8335852	Hokimoto	Dec 2012	B2
8346630	Mckeown	Jan 2013	B1
8355394	Taylor et al.	Jan 2013	B2
8411669	Chen et al.	Apr 2013	B2
8413247	Hudis et al.	Apr 2013	B2
8417817	Jacobs	Apr 2013	B1
8429827	Wetzel	Apr 2013	B1
8438315	Tao et al.	May 2013	B1
8462670	Chien	Jun 2013	B2
8467502	Sureka et al.	Jun 2013	B2
8477926	Jasper et al.	Jul 2013	B2
8503639	Reding et al.	Aug 2013	B2
8503650	Reding et al.	Aug 2013	B2
8504818	Rao et al.	Aug 2013	B2
8509068	Begall et al.	Aug 2013	B2
8532686	Schmidt et al.	Sep 2013	B2
8533857	Tuchman et al.	Sep 2013	B2
8542805	Agranovsky et al.	Sep 2013	B2
8543665	Ansari et al.	Sep 2013	B2
8547962	Ramachandran et al.	Oct 2013	B2
8549047	Beechuk et al.	Oct 2013	B2
8565117	Hilt et al.	Oct 2013	B2
8572391	Golan et al.	Oct 2013	B2
8576712	Sabat et al.	Nov 2013	B2
8577803	Chatterjee et al.	Nov 2013	B2
8582450	Robesky	Nov 2013	B1
8582737	Lawson et al.	Nov 2013	B2
8594626	Woodson et al.	Nov 2013	B1
8601136	Fahlgren et al.	Dec 2013	B1
8611338	Lawson et al.	Dec 2013	B2
8613102	Nath	Dec 2013	B2
8621598	Lai et al.	Dec 2013	B2
8649268	Lawson et al.	Feb 2014	B2
8656452	Li et al.	Feb 2014	B2
8667056	Proulx et al.	Mar 2014	B1
8675493	Buddhikot et al.	Mar 2014	B2
8688147	Nguyen et al.	Apr 2014	B2
8695077	Gerhard et al.	Apr 2014	B1
8713693	Shanabrook et al.	Apr 2014	B2
8728656	Takahashi et al.	May 2014	B2
8751801	Harris et al.	Jun 2014	B2
8755376	Lawson et al.	Jun 2014	B2
8767925	Sureka et al.	Jul 2014	B2
8781975	Bennett et al.	Jul 2014	B2
8797920	Parreira	Aug 2014	B2
8806024	Toba Francis et al.	Aug 2014	B1
8819133	Wang	Aug 2014	B2
8825746	Ravichandran et al.	Sep 2014	B2
8837465	Lawson et al.	Sep 2014	B2
8838707	Lawson et al.	Sep 2014	B2
8843596	Goel et al.	Sep 2014	B2
8855271	Brock et al.	Oct 2014	B2
8861510	Fritz	Oct 2014	B1
8879547	Maes	Nov 2014	B2
8903938	Vermeulen et al.	Dec 2014	B2
8918848	Sharma et al.	Dec 2014	B2
8924489	Bleau et al.	Dec 2014	B2
8938053	Cooke et al.	Jan 2015	B2
8948356	Nowack et al.	Feb 2015	B2
8954591	Ganesan et al.	Feb 2015	B2
8964726	Lawson et al.	Feb 2015	B2
8990610	Bostick et al.	Mar 2015	B2
9014664	Kim et al.	Apr 2015	B2
9015702	Bhat	Apr 2015	B2
9031223	Smith et al.	May 2015	B2
9071677	Aggarwal et al.	Jun 2015	B2
9137127	Nowack et al.	Sep 2015	B2
9141682	Adoc, Jr. et al.	Sep 2015	B1
9161296	Parsons et al.	Oct 2015	B2
9177007	Winters et al.	Nov 2015	B2
9204281	Ramprasad et al.	Dec 2015	B2
9210275	Lawson et al.	Dec 2015	B2
9231894	Dietz	Jan 2016	B1
9306982	Lawson et al.	Apr 2016	B2
9307094	Nowack et al.	Apr 2016	B2
9325624	Malatack et al.	Apr 2016	B2
9338190	Eng et al.	May 2016	B2
9344573	Wolthuis et al.	May 2016	B2
9356916	Kravitz et al.	May 2016	B2
9378337	Kuhr	Jun 2016	B2
9398622	Lawson et al.	Jul 2016	B2
9456008	Lawson et al.	Sep 2016	B2
9456339	Hildner et al.	Sep 2016	B1
9460169	Hinton et al.	Oct 2016	B2
9596274	Lawson et al.	Mar 2017	B2
9628624	Wolthuis et al.	Apr 2017	B2
9632875	Raichstein et al.	Apr 2017	B2
9634995	Binder	Apr 2017	B2
9948703	Olivier et al.	Apr 2018	B2
20010038624	Greenberg et al.	Nov 2001	A1
20010043684	Guedalia et al.	Nov 2001	A1
20010051996	Cooper et al.	Dec 2001	A1
20020006124	Jimenez et al.	Jan 2002	A1
20020006125	Josse et al.	Jan 2002	A1
20020006193	Rodenbusch et al.	Jan 2002	A1
20020025819	Cetusic et al.	Feb 2002	A1
20020057777	Saito et al.	May 2002	A1
20020064267	Martin et al.	May 2002	A1
20020067823	Walker et al.	Jun 2002	A1
20020077833	Arons et al.	Jun 2002	A1
20020126813	Partovi et al.	Sep 2002	A1
20020133587	Ensel et al.	Sep 2002	A1
20020136391	Armstrong et al.	Sep 2002	A1
20020165957	Devoe et al.	Nov 2002	A1
20020176378	Hamilton et al.	Nov 2002	A1
20020184361	Eden	Dec 2002	A1
20020198941	Gavrilescu et al.	Dec 2002	A1
20030006137	Wei et al.	Jan 2003	A1
20030012356	Zino et al.	Jan 2003	A1
20030014665	Anderson et al.	Jan 2003	A1
20030018830	Chen et al.	Jan 2003	A1
20030023672	Vaysman	Jan 2003	A1
20030026426	Wright et al.	Feb 2003	A1
20030046366	Pardikar et al.	Mar 2003	A1
20030051037	Sundaram et al.	Mar 2003	A1
20030058884	Kallner et al.	Mar 2003	A1
20030059020	Meyerson et al.	Mar 2003	A1
20030060188	Gidron et al.	Mar 2003	A1
20030061317	Brown et al.	Mar 2003	A1
20030061404	Atwal et al.	Mar 2003	A1
20030088421	Maes et al.	May 2003	A1
20030097330	Hillmer et al.	May 2003	A1
20030097447	Johnston	May 2003	A1
20030097639	Niyogi et al.	May 2003	A1
20030103620	Brown et al.	Jun 2003	A1
20030123640	Roelle et al.	Jul 2003	A1
20030149721	Alfonso-nogueiro et al.	Aug 2003	A1
20030162506	Toshimitsu et al.	Aug 2003	A1
20030167333	Kumar et al.	Sep 2003	A1
20030195950	Huang et al.	Oct 2003	A1
20030195990	Greenblat et al.	Oct 2003	A1
20030196076	Zabarski et al.	Oct 2003	A1
20030204616	Billhartz et al.	Oct 2003	A1
20030211842	Kempf et al.	Nov 2003	A1
20030231647	Petrovykh	Dec 2003	A1
20030233276	Pearlman et al.	Dec 2003	A1
20040008635	Nelson et al.	Jan 2004	A1
20040011690	Marfino et al.	Jan 2004	A1
20040044953	Watkins et al.	Mar 2004	A1
20040052349	Creamer et al.	Mar 2004	A1
20040071275	Bowater et al.	Apr 2004	A1
20040101122	Da Palma et al.	May 2004	A1
20040102182	Reith et al.	May 2004	A1
20040117788	Karaoguz et al.	Jun 2004	A1
20040136324	Steinberg et al.	Jul 2004	A1
20040165569	Sweatman et al.	Aug 2004	A1
20040172482	Weissman et al.	Sep 2004	A1
20040199572	Hunt et al.	Oct 2004	A1
20040205101	Radhakrishnan	Oct 2004	A1
20040205689	Ellens et al.	Oct 2004	A1
20040213400	Golitsin et al.	Oct 2004	A1
20040216058	Chavers et al.	Oct 2004	A1
20040218748	Fisher	Nov 2004	A1
20040228469	Andrews et al.	Nov 2004	A1
20040236696	Aoki et al.	Nov 2004	A1
20040240649	Goel	Dec 2004	A1
20050005109	Castaldi et al.	Jan 2005	A1
20050005200	Matenda et al.	Jan 2005	A1
20050010483	Ling	Jan 2005	A1
20050015505	Kruis et al.	Jan 2005	A1
20050021626	Prajapat et al.	Jan 2005	A1
20050025303	Hostetler, Jr.	Feb 2005	A1
20050038772	Colrain	Feb 2005	A1
20050043952	Sharma et al.	Feb 2005	A1
20050047579	Salame	Mar 2005	A1
20050060411	Coulombe et al.	Mar 2005	A1
20050083907	Fishler	Apr 2005	A1
20050091336	Dehamer et al.	Apr 2005	A1
20050091572	Gavrilescu et al.	Apr 2005	A1
20050108770	Karaoguz et al.	May 2005	A1
20050125251	Berger et al.	Jun 2005	A1
20050125739	Thompson et al.	Jun 2005	A1
20050128961	Miloslavsky et al.	Jun 2005	A1
20050135578	Ress et al.	Jun 2005	A1
20050141500	Bhandari et al.	Jun 2005	A1
20050147088	Bao et al.	Jul 2005	A1
20050177635	Schmidt et al.	Aug 2005	A1
20050181835	Lau et al.	Aug 2005	A1
20050198292	Duursma et al.	Sep 2005	A1
20050228680	Malik	Oct 2005	A1
20050238153	Chevalier	Oct 2005	A1
20050240659	Taylor	Oct 2005	A1
20050243977	Creamer et al.	Nov 2005	A1
20050246176	Creamer et al.	Nov 2005	A1
20050289222	Sahim	Dec 2005	A1
20060008065	Longman et al.	Jan 2006	A1
20060008073	Yoshizawa et al.	Jan 2006	A1
20060008256	Khedouri et al.	Jan 2006	A1
20060015467	Morken et al.	Jan 2006	A1
20060021004	Moran et al.	Jan 2006	A1
20060023676	Whitmore et al.	Feb 2006	A1
20060047666	Bedi et al.	Mar 2006	A1
20060067506	Flockhart et al.	Mar 2006	A1
20060080415	Tu	Apr 2006	A1
20060098624	Morgan et al.	May 2006	A1
20060129638	Deakin	Jun 2006	A1
20060143007	Koh et al.	Jun 2006	A1
20060146792	Ramachandran et al.	Jul 2006	A1
20060146802	Baldwin et al.	Jul 2006	A1
20060168334	Potti et al.	Jul 2006	A1
20060203979	Jennings	Sep 2006	A1
20060209695	Archer, Jr. et al.	Sep 2006	A1
20060212865	Vincent et al.	Sep 2006	A1
20060215824	Mitby et al.	Sep 2006	A1
20060217823	Hussey	Sep 2006	A1
20060217978	Mitby et al.	Sep 2006	A1
20060222166	Ramakrishna et al.	Oct 2006	A1
20060235715	Abrams et al.	Oct 2006	A1
20060256816	Yarlagadda et al.	Nov 2006	A1
20060262915	Marascio et al.	Nov 2006	A1
20060270386	Yu et al.	Nov 2006	A1
20060285489	Francisco et al.	Dec 2006	A1
20070002744	Mewhinney et al.	Jan 2007	A1
20070036143	Alt et al.	Feb 2007	A1
20070038499	Margulies et al.	Feb 2007	A1
20070043681	Morgan et al.	Feb 2007	A1
20070050306	McQueen	Mar 2007	A1
20070064672	Raghav et al.	Mar 2007	A1
20070070906	Thakur	Mar 2007	A1
20070070980	Phelps et al.	Mar 2007	A1
20070071223	Lee et al.	Mar 2007	A1
20070074174	Thornton	Mar 2007	A1
20070088836	Tai et al.	Apr 2007	A1
20070091907	Seshadri et al.	Apr 2007	A1
20070107048	Halls et al.	May 2007	A1
20070112574	Greene	May 2007	A1
20070116191	Bermudez et al.	May 2007	A1
20070121651	Casey et al.	May 2007	A1
20070127691	Lert	Jun 2007	A1
20070127703	Siminoff	Jun 2007	A1
20070130260	Weintraub et al.	Jun 2007	A1
20070133771	Stifelman et al.	Jun 2007	A1
20070147351	Dietrich et al.	Jun 2007	A1
20070149166	Turcotte et al.	Jun 2007	A1
20070153711	Dykas et al.	Jul 2007	A1
20070167170	Fitchett et al.	Jul 2007	A1
20070192629	Saito	Aug 2007	A1
20070201448	Baird et al.	Aug 2007	A1
20070208862	Fox et al.	Sep 2007	A1
20070232284	Mason et al.	Oct 2007	A1
20070239761	Baio et al.	Oct 2007	A1
20070242626	Altberg et al.	Oct 2007	A1
20070255828	Paradise	Nov 2007	A1
20070265073	Novi et al.	Nov 2007	A1
20070286180	Marquette et al.	Dec 2007	A1
20070291734	Bhatia et al.	Dec 2007	A1
20070291905	Halliday et al.	Dec 2007	A1
20070293200	Roundtree et al.	Dec 2007	A1
20070295803	Levine et al.	Dec 2007	A1
20080005275	Overton et al.	Jan 2008	A1
20080025320	Bangalore et al.	Jan 2008	A1
20080037715	Prozeniuk et al.	Feb 2008	A1
20080037746	Dufrene et al.	Feb 2008	A1
20080040484	Yardley	Feb 2008	A1
20080049617	Grice et al.	Feb 2008	A1
20080052395	Wright et al.	Feb 2008	A1
20080091843	Kulkarni	Apr 2008	A1
20080101571	Harlow et al.	May 2008	A1
20080104348	Kabzinski et al.	May 2008	A1
20080120702	Hokimoto	May 2008	A1
20080123559	Haviv et al.	May 2008	A1
20080134049	Gupta et al.	Jun 2008	A1
20080139166	Agarwal et al.	Jun 2008	A1
20080146268	Gandhi et al.	Jun 2008	A1
20080152101	Griggs	Jun 2008	A1
20080154601	Stifelman et al.	Jun 2008	A1
20080155029	Helbling et al.	Jun 2008	A1
20080162482	Ahern et al.	Jul 2008	A1
20080165708	Moore et al.	Jul 2008	A1
20080172404	Cohen	Jul 2008	A1
20080177883	Hanai et al.	Jul 2008	A1
20080192736	Jabri et al.	Aug 2008	A1
20080201426	Darcie	Aug 2008	A1
20080209050	Li	Aug 2008	A1
20080212945	Khedouri et al.	Sep 2008	A1
20080222656	Lyman	Sep 2008	A1
20080229421	Hudis et al.	Sep 2008	A1
20080232574	Baluja et al.	Sep 2008	A1
20080235230	Maes	Sep 2008	A1
20080256224	Kaji et al.	Oct 2008	A1
20080275741	Loeffen	Nov 2008	A1
20080307436	Hamilton	Dec 2008	A1
20080310599	Purnadi et al.	Dec 2008	A1
20080313318	Vermeulen et al.	Dec 2008	A1
20080316931	Qiu et al.	Dec 2008	A1
20080317222	Griggs et al.	Dec 2008	A1
20080317232	Couse et al.	Dec 2008	A1
20080317233	Rey et al.	Dec 2008	A1
20090046838	Andreasson	Feb 2009	A1
20090052437	Taylor et al.	Feb 2009	A1
20090052641	Taylor et al.	Feb 2009	A1
20090059894	Jackson et al.	Mar 2009	A1
20090063502	Coimbatore et al.	Mar 2009	A1
20090074159	Goldfarb et al.	Mar 2009	A1
20090075684	Cheng et al.	Mar 2009	A1
20090083155	Tudor et al.	Mar 2009	A1
20090089165	Sweeney	Apr 2009	A1
20090089352	Davis et al.	Apr 2009	A1
20090089699	Saha et al.	Apr 2009	A1
20090093250	Jackson et al.	Apr 2009	A1
20090094674	Schwartz et al.	Apr 2009	A1
20090125608	Werth et al.	May 2009	A1
20090129573	Gavan et al.	May 2009	A1
20090136011	Goel	May 2009	A1
20090170496	Bourque	Jul 2009	A1
20090171659	Pearce et al.	Jul 2009	A1
20090171669	Engelsma et al.	Jul 2009	A1
20090171752	Galvin et al.	Jul 2009	A1
20090182896	Patterson et al.	Jul 2009	A1
20090193433	Maes	Jul 2009	A1
20090216835	Jain et al.	Aug 2009	A1
20090217293	Wolber et al.	Aug 2009	A1
20090022131	Chen et al.	Sep 2009	A1
20090220057	Waters	Sep 2009	A1
20090222341	Belwadi et al.	Sep 2009	A1
20090225748	Taylor	Sep 2009	A1
20090225763	Forsberg et al.	Sep 2009	A1
20090228868	Drukman et al.	Sep 2009	A1
20090232289	Drucker et al.	Sep 2009	A1
20090234965	Viveganandhan et al.	Sep 2009	A1
20090235349	Lai et al.	Sep 2009	A1
20090241135	Wong et al.	Sep 2009	A1
20090252159	Lawson et al.	Oct 2009	A1
20090276771	Nickolov et al.	Nov 2009	A1
20090288012	Hertel et al.	Nov 2009	A1
20090288165	Qiu et al.	Nov 2009	A1
20090300194	Ogasawara	Dec 2009	A1
20090316687	Kruppa	Dec 2009	A1
20090318112	Vasten	Dec 2009	A1
20100027531	Kurashima	Feb 2010	A1
20100037204	Lin et al.	Feb 2010	A1
20100054142	Moiso et al.	Mar 2010	A1
20100070424	Monk	Mar 2010	A1
20100071053	Ansari et al.	Mar 2010	A1
20100082513	Liu	Apr 2010	A1
20100087215	Gu et al.	Apr 2010	A1
20100088187	Courtney et al.	Apr 2010	A1
20100088698	Krishnamurthy	Apr 2010	A1
20100094758	Chamberlain et al.	Apr 2010	A1
20100103845	Ulupinar et al.	Apr 2010	A1
20100107222	Glasser	Apr 2010	A1
20100115041	Hawkins et al.	May 2010	A1
20100138501	Clinton et al.	Jun 2010	A1
20100142516	Lawson et al.	Jun 2010	A1
20100150139	Lawson et al.	Jun 2010	A1
20100167689	Sepehri-Nik et al.	Jul 2010	A1
20100188979	Thubert et al.	Jul 2010	A1
20100191915	Spencer	Jul 2010	A1
20100208881	Kawamura	Aug 2010	A1
20100217837	Ansari et al.	Aug 2010	A1
20100217982	Brown et al.	Aug 2010	A1
20100232594	Lawson et al.	Sep 2010	A1
20100235539	Carter et al.	Sep 2010	A1
20100250946	Korte et al.	Sep 2010	A1
20100251329	Wei	Sep 2010	A1
20100251340	Martin et al.	Sep 2010	A1
20100265825	Blair et al.	Oct 2010	A1
20100029191	Sanding et al.	Nov 2010	A1
20100281108	Cohen	Nov 2010	A1
20100299437	Moore	Nov 2010	A1
20100312919	Lee et al.	Dec 2010	A1
20100332852	Vembu et al.	Dec 2010	A1
20110026516	Roberts et al.	Feb 2011	A1
20110029882	Jaisinghani	Feb 2011	A1
20110029981	Jaisinghani	Feb 2011	A1
20110053555	Cai et al.	Mar 2011	A1
20110078278	Cui et al.	Mar 2011	A1
20110081008	Lawson et al.	Apr 2011	A1
20110083069	Paul et al.	Apr 2011	A1
20110083179	Lawson et al.	Apr 2011	A1
20110093516	Geng et al.	Apr 2011	A1
20110096673	Stevenson et al.	Apr 2011	A1
20110110366	Moore et al.	May 2011	A1
20110014981	Koren et al.	Jun 2011	A1
20110131293	Mori	Jun 2011	A1
20110138453	Verma et al.	Jun 2011	A1
20110143714	Keast et al.	Jun 2011	A1
20110145049	Hertel et al.	Jun 2011	A1
20110149950	Petit-Huguenin et al.	Jun 2011	A1
20110151884	Zhao	Jun 2011	A1
20110158235	Senga	Jun 2011	A1
20110167172	Roach et al.	Jul 2011	A1
20110170505	Rajasekar et al.	Jul 2011	A1
20110176537	Lawson et al.	Jul 2011	A1
20110179126	Wetherell et al.	Jul 2011	A1
20110211679	Mezhibovsky et al.	Sep 2011	A1
20110251921	Kassaei et al.	Oct 2011	A1
20110253693	Lyons et al.	Oct 2011	A1
20110255675	Jasper et al.	Oct 2011	A1
20110258432	Rao et al.	Oct 2011	A1
20110265168	Lucovsky et al.	Oct 2011	A1
20110265172	Sharma	Oct 2011	A1
20110267985	Wilkinson et al.	Nov 2011	A1
20110274111	Narasappa et al.	Nov 2011	A1
20110276892	Jensen-Horne et al.	Nov 2011	A1
20110276951	Jain	Nov 2011	A1
20110280390	Lawson et al.	Nov 2011	A1
20110283259	Lawson et al.	Nov 2011	A1
20110289126	Aikas et al.	Nov 2011	A1
20110289162	Furlong et al.	Nov 2011	A1
20110299672	Chiu et al.	Dec 2011	A1
20110302479	Movida et al.	Dec 2011	A1
20110310902	Xu	Dec 2011	A1
20110313950	Nuggehalli et al.	Dec 2011	A1
20110320449	Gudlavenkatasiva	Dec 2011	A1
20110320550	Lawson et al.	Dec 2011	A1
20120000903	Baarman et al.	Jan 2012	A1
20120011274	Moreman	Jan 2012	A1
20120017222	May	Jan 2012	A1
20120023531	Meuninck et al.	Jan 2012	A1
20120023544	Li et al.	Jan 2012	A1
20120027228	Rijken et al.	Feb 2012	A1
20120028602	Lisi et al.	Feb 2012	A1
20120036574	Heithcock et al.	Feb 2012	A1
20120039202	Song	Feb 2012	A1
20120059709	Lieberman et al.	Mar 2012	A1
20120079066	Li et al.	Mar 2012	A1
20120083266	Vanswol et al.	Apr 2012	A1
20120089572	Raichstein et al.	Apr 2012	A1
20120094637	Jeyaseelan et al.	Apr 2012	A1
20120101952	Raleigh et al.	Apr 2012	A1
20120110564	Ran et al.	May 2012	A1
20120114112	Rauschenberger et al.	May 2012	A1
20120149404	Beattie et al.	Jun 2012	A1
20120166488	Kaushik et al.	Jun 2012	A1
20120017361	Bleau et al.	Jul 2012	A1
20120170726	Schwartz	Jul 2012	A1
20120174095	Natchadalingam et al.	Jul 2012	A1
20120179646	Hinton et al.	Jul 2012	A1
20120179907	Byrd et al.	Jul 2012	A1
20120180021	Byrd et al.	Jul 2012	A1
20120180029	Hill et al.	Jul 2012	A1
20120185561	Klein et al.	Jul 2012	A1
20120198004	Watte	Aug 2012	A1
20120201238	Lawson et al.	Aug 2012	A1
20120208495	Lawson et al.	Aug 2012	A1
20120221603	Kothule et al.	Aug 2012	A1
20120226579	Ha et al.	Sep 2012	A1
20120239757	Firstenberg et al.	Sep 2012	A1
20120240226	Li	Sep 2012	A1
20120246273	Bornstein et al.	Sep 2012	A1
20120254108	Wedewer	Oct 2012	A1
20120254828	Aiylam et al.	Oct 2012	A1
20120281536	Gell et al.	Nov 2012	A1
20120288082	Segall	Nov 2012	A1
20120290706	Lin et al.	Nov 2012	A1
20120304245	Lawson et al.	Nov 2012	A1
20120304275	Ji et al.	Nov 2012	A1
20120316809	Egolf et al.	Dec 2012	A1
20120321058	Eng et al.	Dec 2012	A1
20120321070	Smith et al.	Dec 2012	A1
20130029629	Lindholm et al.	Jan 2013	A1
20130031158	Salsburg	Jan 2013	A1
20130031613	Shanabrook et al.	Jan 2013	A1
20130036476	Roever et al.	Feb 2013	A1
20130047232	Tuchman et al.	Feb 2013	A1
20130054517	Beechuk et al.	Feb 2013	A1
20130054684	Brazier et al.	Feb 2013	A1
20130058262	Parreira	Mar 2013	A1
20130067232	Cheung et al.	Mar 2013	A1
20130067448	Sannidhanam et al.	Mar 2013	A1
20130097298	Ting et al.	Apr 2013	A1
20130110658	Lyman	May 2013	A1
20130132573	Lindblom	May 2013	A1
20130139148	Berg et al.	May 2013	A1
20130156024	Burg	Jun 2013	A1
20130166580	Maharajh et al.	Jun 2013	A1
20130179942	Caplis et al.	Jul 2013	A1
20130201909	Bosch et al.	Aug 2013	A1
20130204786	Mattes et al.	Aug 2013	A1
20130212603	Cooke et al.	Aug 2013	A1
20130244632	Spence et al.	Sep 2013	A1
20130268676	Martins et al.	Oct 2013	A1
20130325934	Fausak et al.	Dec 2013	A1
20130328997	Desai	Dec 2013	A1
20130336472	Fahlgren et al.	Dec 2013	A1
20140013400	Warshavsky et al.	Jan 2014	A1
20140025503	Meyer et al.	Jan 2014	A1
20140058806	Guenette et al.	Feb 2014	A1
20140064467	Lawson et al.	Mar 2014	A1
20140072115	Makagon et al.	Mar 2014	A1
20140073291	Hildner et al.	Mar 2014	A1
20140095624	Quan	Apr 2014	A1
20140095625	Quan	Apr 2014	A1
20140095627	Romagnino	Apr 2014	A1
20140101058	Castel et al.	Apr 2014	A1
20140105372	Nowack et al.	Apr 2014	A1
20140106704	Cooke et al.	Apr 2014	A1
20140122600	Kim et al.	May 2014	A1
20140123187	Reisman	May 2014	A1
20140126715	Lum et al.	May 2014	A1
20140129363	Lorah et al.	May 2014	A1
20140153565	Lawson et al.	Jun 2014	A1
20140185490	Holm et al.	Jul 2014	A1
20140254600	Shibata et al.	Sep 2014	A1
20140258481	Lundell	Sep 2014	A1
20140269333	Boerjesson	Sep 2014	A1
20140274086	Boerjesson et al.	Sep 2014	A1
20140282473	Saraf et al.	Sep 2014	A1
20140289391	Balaji et al.	Sep 2014	A1
20140304054	Orun et al.	Oct 2014	A1
20140317640	Harm et al.	Oct 2014	A1
20140037251	Fausak et al.	Dec 2014	A1
20140355600	Lawson et al.	Dec 2014	A1
20140372508	Fausak et al.	Dec 2014	A1
20140372509	Fausak et al.	Dec 2014	A1
20140373098	Fausak et al.	Dec 2014	A1
20140379670	Kuhr	Dec 2014	A1
20150004932	Kim et al.	Jan 2015	A1
20150004933	Kim et al.	Jan 2015	A1
20150023251	Giakoumelis et al.	Jan 2015	A1
20150026477	Malatack et al.	Jan 2015	A1
20150066865	Yara et al.	Mar 2015	A1
20150081918	Nowack et al.	Mar 2015	A1
20150082378	Collison	Mar 2015	A1
20150100634	He et al.	Apr 2015	A1
20150119050	Liao et al.	Apr 2015	A1
20150181631	Lee et al.	Jun 2015	A1
20150189014	Grunenberger	Jul 2015	A1
20150236905	Bellan et al.	Aug 2015	A1
20150281294	Nur et al.	Oct 2015	A1
20150365480	Soto et al.	Dec 2015	A1
20150370788	Bareket	Dec 2015	A1
20160011758	Dornbush et al.	Jan 2016	A1
20160077693	Meyer et al.	Mar 2016	A1
20160112475	Lawson et al.	Apr 2016	A1
20160112521	Lawson et al.	Apr 2016	A1
20160119291	Zollinger et al.	Apr 2016	A1
20160127254	Kumar et al.	May 2016	A1
20160149956	Birnbaum et al.	May 2016	A1
20160162172	Rathod	Jun 2016	A1
20160205519	Patel et al.	Jul 2016	A1
20160226937	Patel et al.	Aug 2016	A1
20160226979	Lancaster et al.	Aug 2016	A1
20160234391	Wolthuis et al.	Aug 2016	A1
20160239770	Batabyal et al.	Aug 2016	A1
20160335074	Olivier et al.	Nov 2016	A1
20170339283	Chaudhary et al.	Nov 2017	A1
20180213028	Olivier et al.	Jul 2018	A1

Foreign Referenced Citations (20)

Number	Date	Country
1684587	Mar 1971	DE
0282126	Sep 1988	EP
1464418	Oct 2004	EP
1522922	Apr 2005	EP
1770586	Apr 2007	EP
2053869	Apr 2009	EP
2134107	Sep 1999	ES
10294788	Nov 1998	JP
2004166000	Jun 2004	JP
2004220118	Aug 2004	JP
2006319914	Nov 2006	JP
WO-9732448	Sep 1997	WO
WO-2002087804	Nov 2002	WO
WO-2006037492	Apr 2006	WO
WO-2009018489	Feb 2009	WO
WO-2009124223	Oct 2009	WO
WO-2010037064	Apr 2010	WO
WO-2010040010	Apr 2010	WO
WO-2010101935	Sep 2010	WO
WO-201 1091085	Jul 2011	WO

Non-Patent Literature Citations (23)

Entry
Pravin, “Advantages of Application Server”, Dec. 15, 2009, http://data-centers.in/advantages-of-application-server/, pp. 1-4 (Year: 2009).
“Aepona's API Monetization Platform Wins Best of 4G Awards for Mobile Cloud Enabler”, 4G World 2012 Conference & Expo, [Online]. [Accessed Nov. 5, 2015]. Retrieved from the Internet: <URL: https://www.realwire.com/releases/%20Aeponas-API-Monetization>, (Oct. 30, 2012), 4 pgs.
“U.S. Appl. No. 15/154,700, Corrected of Allowance dated Mar. 22, 2018”, 6 pgs.
“U.S. Appl. No. 15/154,700, Examiner Interview Summary dated Nov. 3, 2017”, 3 pgs.
“U.S. Appl. No. 15/154,700, Non Final Office Action dated Jul. 26, 2017”, 27 pgs.
“U.S. Appl. No. 15/154,700, Notice of Allowance dated Dec. 8, 2017”, 9 pgs.
“U.S. Appl. No. 15/154,700, Response filed Oct. 26, 2017 to Non Final Office Action dated Jul. 26, 2017”, 11 pgs.
“U.S. Appl. No. 15/914,401, Non Final Office Action dated Jun. 13, 2019”, 15 pgs.
“U.S. Appl. No. 15/914,401, Notice of Allowance dated Nov. 7, 2019”, 8 pgs.
“U.S. Appl. No. 15/914,401, Preliminary Amendment filed May 28, 2019”, 10 pgs.
“U.S. Appl. No. 15/914,401, Response filed Sep. 16, 2019 to Non-Final Office Action dated Jun. 13, 2019”, 14 pgs.
“Archive Microsoft Office 365 Email \| Retain Unified Archiving”, GWAVA, Inc., Montreal, Canada, [Online] Retrieved from the internet: <http://www.gwava.com/Retain/Retain for_Office_365.php>, (2015), 4 pgs.
“Complaint for Patent Infringement”, Telinit Technologies, LLC v. Twilio Inc 2:12-cv-663, (Oct. 12, 2012), 17 pgs.
“Ethernet to Token ring Bridge”, Black Box Corporation, [Online] Retrieved from the internet: <http://blackboxcanada.com/resource/files/productdetails/17044.pdf>, (Oct. 1999), 2 pgs.
“Twilio Cloud Communications—APIs for Voice, VoIP, and Text Messaging”, Twilio, [Online] Retrieved from the internet: <http://www.twilio.com/docs/api/rest/call-feedback>, (Jun. 24, 2015), 8 pgs.
Abu-Lebdeh, et al., “A 3GPP Evolved Packet Core-Based Architecture for QoS-Enabled Mobile Video Surveillance Applications”, 2012 Third International Conference on the Network of the Future {NOF), (Nov. 21-23, 2012), 1-6.
Barakovic, Sabina, et al., “Survey and Challenges of QoE Management Issues in Wireless Networks”, Hindawi Publishing Corporation, (2012), 1-29.
Berners-Lee, T., “RFC 3986: Uniform Resource Identifier (URI): Generic Syntax”, The Internet Society, [Online]. Retrieved from the Internet: <URL: http://tools.ietf.org/html/rfc3986>, (Jan. 2005), 57 pgs.
Kim, Hwa-Jong, et al., “In-Service Feedback QoE Framework”, 2010 Third International Conference on Communication Theory. Reliability and Quality of Service, (2010), 135-138.
Matos, et al., “Quality of Experience-based Routing in Multi-Service Wireless Mesh Networks”, Realizing Advanced Video Optimized Wireless Networks. IEEE, (2012), 7060-7065.
Mu, Mu, et al., “Quality Evaluation in Peer-to-Peer IPTV Services”, Data Traffic and Monitoring Analysis, LNCS 7754, 302-319, (2013), 18 pgs.
Subramanya, et al., “Digital Signatures”, IEEE Potentials, (Mar./Apr. 2006), 5-8.
Tran, et al., “User to User adaptive routing based on QoE”, ICNS 2011: The Seventh International Conference on Networking and Services, (2011), 170-177.

Related Publications (1)

	Number	Date	Country
	20200137147 A1	Apr 2020	US

Provisional Applications (4)

Number	Date	Country
62265557	Dec 2015	US
62163270	May 2015	US
62161724	May 2015	US
62161719	May 2015	US

Continuations (2)

	Number	Date	Country
Parent	15914401	May 2018	US
Child	16730626		US
Parent	15154700	May 2016	US
Child	15914401		US

System and method for signaling through data storage

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

International Classifications

Disclaimer

Abstract