Omnichannel approach to application sharing across different devices

• US 10,298,678 B2
• Filed: 02/17/2014
• Issued: 05/21/2019
• Est. Priority Date: 02/17/2014
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Castro, Paul C., Pistoia, Marco, Ponzo, John
• Primary Examiner(s): Meky, Moustafa M
• Assistant Examiner(s): Islam, Sm Z
• Application Number:
  US14/181,770
• Publication Number:
  US 20150237128A1
• Time in Patent Office: 1,919 Days
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal

Abstract

A group of remote devices executing an omnichannel application are coordinated from a network node. An omnichannel mediator coordinates formation of at least two of said remote devices into an omnichannel cloudlet. A component manager controls which of a plurality of components of said omnichannel application should optimally be placed on which individual devices of said omnichannel cloudlet and how data should flow to individual devices of said omnichannel cloudlet. A replication optimizer optimally coordinates data replication for the group of remote device.

Claims

1. A method comprising:

implementing, at a replication optimizer running on at least one hardware processor in a network node, an endpoint binding that is connected to network interfaces of said network node;

obtaining, at said replication optimizer via said endpoint binding, a request from a first remote device to join a group of remote devices executing an omnichannel application and including said network node, said request including a common key identifying said group of remote devices executing said omnichannel application;

adding said first remote device, by an omnichannel mediator and a link manager implemented at said replication optimizer, to said group of remote devices executing said omnichannel application;

updating a topology of said group of remote devices executing said omnichannel application by defining links between said remote devices to obtain an updated group topology;

establishing, at said omnichannel mediator, application configuration policies and a data replication plan for said group of remote devices executing said omnichannel application, based on said updated group topology;

obtaining, at said replication optimizer running on at least one hardware processor in a network node, an indication from one device of said group of remote devices executing said omnichannel application, that a data update has occurred for said omnichannel application on said one device of said group of remote devices executing said omnichannel application;

sending, from said replication optimizer running on at least one hardware processor in a network node, to said group of remote devices executing said omnichannel application, at least one of;

(i) said data replication plan; and

(ii) instructions in accordance with said data replication plan;

to specify how said data update for said omnichannel application on said one device of said group of remote devices executing said omnichannel application is to be propagated to remaining devices of said group of remote devices executing said omnichannel application; and

side-loading said data update directly from said one device of said group of remote devices to at least one other device of said group of remote devices, in accordance with said data replication plan.

2. The method of claim 1, wherein said step of establishing said data replication plan for said group of remote devices executing said omnichannel application, based on said updated group topology, comprises establishing said plan to reduce use of metered networks during said propagation of said data update to remaining devices of said group of remote devices executing said omnichannel application.

3. The method of claim 1, wherein said step of establishing said data replication plan for said group of remote devices executing said omnichannel application, based on said updated group topology, comprises establishing said plan to reduce energy cost during said propagation of said data update to remaining devices of said group of remote devices executing said omnichannel application.

4. The method of claim 1, wherein said step of establishing said data replication plan for said group of remote devices executing said omnichannel application, based on said updated group topology, comprises establishing said plan to consider priority of data updated during said data update.

5. The method of claim 1, further comprising advising said remaining devices of said group of remote devices executing said omnichannel application of said data update prior to said propagation of said data update to said remaining devices of said group of remote devices executing said omnichannel application.

6. The method of claim 1, further comprising providing a system, wherein the system comprises distinct software modules, each of the distinct software modules being embodied on a computer-readable storage medium, and wherein the distinct software modules comprise a group registry module, a topology monitor module, a replication planner module;

an event module; and

an instruction propagation module;

wherein;

said obtaining of said request from said first remote device to join said group of remote devices is carried out by said group registry module executing on at least one hardware processor;

said adding of aid first remote device to said group of remote devices executing said omnichannel application is carried out by said group registry module executing on said at least one hardware processor;

said updating of said topology of said group of remote devices is carried out by said topology monitor module executing on said at least one hardware processor;

said establishing of said data replication plan for said group of remote devices executing said omnichannel application is carried out by said replication planner module executing on said at least one hardware processor;

said obtaining of said indication that said data update has occurred is carried out by said event module executing on said at least one hardware processor; and

said sending of said at least one of;

(i) said data replication plan; and

(ii) said instructions in accordance with said data replication plan;

is carried out by said instruction propagation module executing on said at least one hardware processor.