Peer shared server event notification system and methods

• US 20090282123A1
• Filed: 05/09/2008
• Published: 11/12/2009
• Est. Priority Date: 05/09/2008
• Status: Abandoned Application

• Current Assignee: Funambol Incorporated
• Original Assignee: Funambol Incorporated
• Inventors: Fornari, Stefano
• Application Number:
  US12/151,831
• Publication Number:
  US 20090282123A1
• Time in Patent Office: Days
• US Class Current: 709/207
• CPC Class Codes: H04L 12/1836 with heterogeneous network architecture
• CPC Class Codes: H04L 12/189 in combination with wireless systems selective distribution or broadcast in wireless communication networks H04W4/06
• CPC Class Codes: H04L 61/2567 for reachability, e.g. inquiring the address of a correspondent behind a NAT server

Abstract

Peer-communicated notices of requested actions are distributed to mobile devices on routing incompatible networks. A peer management server receives action requests for mobile devices communicated from a plurality of routing incompatible networks. In response to an action request, as received from a first mobile device, a set of one or more peer-shared notices are determined for delivery to a set of second mobile devices coupled to the same routing incompatible network. Selection of the deliverable notices is dependent on a policy identifier associated with the first mobile device. The set of notices are sent to said first mobile device for relay distribution to said set of second mobile devices utilizing the communications channel preferably as established by the first mobile device in communicating the action request. Delivery confirmation of individual peer relayed notices is preferably obtained upon receipt of an action request from the corresponding second mobile devices.

Claims

1. A method, implemented by computer, of communicating notices of requested actions to mobile devices on routing incompatible networks, said method comprising the steps of:

a) receiving, by a peer management server, action requests for mobile devices communicated from a plurality of routing incompatible networks;

b) determining, by said peer management server in response to a first action request from a first mobile device coupled to a first routing incompatible network, a set of notices for delivery to a set of second mobile devices coupled to said first routing incompatible network dependent on an identifier of said first mobile device;

c) sending said set of notices to said first mobile device for relay distribution to said set of second mobile devices; and

d) confirming delivery of a notice, of said set of notices, upon receipt of a second action request from a corresponding mobile device, of said set of second mobile devices.

2. The method of claim 1 wherein said first action request is received through a communications channel established between said first mobile device and said peer management server, wherein said first action request is transmitted to said peer management server to perform a defined operation, and wherein said step of sending provides for the sending of said set of notices to said first mobile device through said communications channel independent of said defined operation.

3. The method of claim 2 further comprising the step of establishing notices of requested actions for distribution to said plurality of routing incompatible networks, said step of establishing including associating notices of requested actions with respective said routing incompatible networks pending selection, in said step of determining, for inclusion in said set of notices.

4. The method of claim 3 wherein said step of determining includes evaluating, by a policy evaluation engine, defined criteria for determining said set of notices for deliver to said set of second mobile devices.

5. The method of claim 4 wherein said defined criteria conditionally includes technical and community policies and wherein said defined criteria are associated with mobile device identifiers.

6. The method of claim 5 wherein said community policies are qualified by community policies

7. A peer-management server system enabling collaborative interoperation among a plurality of mobile devices accessible through a plurality of routing incompatible networks managed through network operator servers, said peer-management server system comprising:

a) a pending notice queue providing for storage of notice messages representing collaborative application events;

b) a mobile device monitor responsive to connections initiated by a plurality of mobile devices, said mobile device monitor being operative to determine mobile device connection data from connections with said plurality of mobile devices, said mobile device monitor providing for the storage of said mobile device connection data in a data store; and

c) a connection processor, coupled to said pending notice queue and said data store, operative in response to a connection from a predetermined mobile device to select a notice message from said pending notice queue for peer-relay through said predetermined mobile device.

8. The peer-management server system of claim 7 wherein said connection processor includes a notice message propagation policy evaluation engine, wherein said data store further provides for storage of respective policies for said plurality of mobile devices, wherein each said policy defines a plurality of propagation constraints determinative of participation availability for the peer-relay of notice messages, and wherein said notice message propagation policy evaluation engine is operative to determine a propagation path, subject to said pluralities of propagation constraints, to a predetermined mobile device identified by said notice message beginning through a connected one of said plurality of mobile devices.

9. The peer-management server system of claim 8 wherein said connection processor monitors, through connections from said plurality of mobile devices, for notice message delivery, wherein on indication of notice message delivery, said connection processor removes said notice message from said pending notice queue.

10. The peer-management server system of claim 9 wherein said indication is a connection from said predetermined mobile device within a predetermined period of time, wherein in the absence of said indication, said connection processor is operative to re-select said notice message from said pending notice queue.

11. The peer-management server system of claim 10 wherein each of said plurality of mobile devices implement optionally implements local propagation constraints determinative of participation in the peer-relay of notice messages.

12. The peer-management server system of claim 11 wherein said mobile device connection data includes frequency of participation as a peer-relay, success rate in the peer-relay delivery of notice messages to other of said plurality of mobile devices, local protocols available for use in the peer-relay of notice messages, and cost factors related to peer-relay of notice messages, and wherein said connection processor is operative to evaluate said mobile device connection data in determining a peer-relay delivery path for said notice message that balances overall load on said plurality of mobile devices while optimizing the successful delivery rate of peer-relayed notice messages.

13. The peer-management server system of claim 12 wherein said mobile device monitor determines mobile device connection data, including a network address for each of said plurality of mobile devices, independent of said network operator servers, wherein said peer-relay delivery path, including a set of mobile device network addresses, is provided with said notice message.

14. A method, implemented by computer, of enabling collaborative interoperation of mobile devices connected within a plurality of mutually routing incompatible networks, said method comprising the steps of:

a) accumulating, in a peer-management server external to said plurality of mutually routing incompatible networks, connection data for each of a plurality of mobile devices, wherein said connection data is respectively determined by said peer-management server in response to connections from said plurality of mobile devices to said peer-management server;

b) maintaining, in said peer-management server, a plurality of server-based participation policies, associated with respective connection data, for said plurality of mobile devices, each said participation policy including propagation controls determinative, for said peer-management server, of the participation availability of said plurality of mobile devices in the peer-relay of notice messages; and

c) delivering, by said peer-management server, a notice message generated in response to a shared-application operation performed by a first mobile device, wherein said step of delivering is performed by;

i) first determining a first predetermined mobile device of said plurality of mobile devices to receive said notice message;

ii) second determining a predetermined one of said routing incompatible networks through which said predetermined mobile device connects;

iii) waiting for a connection from a second predetermined mobile device of plurality of mobile devices to connect to said peer-management server from said predetermined one of said routing incompatible networks;

iv) third determining, dependent on respective said server-based participation policies, a peer-relay delivery path through said second predetermined mobile device to said first predetermined mobile device; and

v) providing said notice message to said second predetermined mobile device for peer-relay to said first predetermined mobile device.

15. The method of claim 14 wherein said peer-management server is operative to determine and update said connection data with the network addresses of the respective ones of said plurality of mobile devices, and wherein network addresses are provided with said notice message for each of said mobile devices in said peer-relay delivery path.

16. The method of claim 15 wherein said plurality of mobile devices report a status of participation in the peer-relay of notice messages and wherein, in said third determining step, the participation success rate of said plurality of mobile devices is considered in determining said peer-relay delivery path.

17. The method of claim 16 wherein said server-based participation policies define controls on the frequency of participation as a peer-relay, local protocols available for use in the peer-relay of notice messages, and cost factors and cost controls related to peer-relay of notice messages, and, optionally, identified subgroups of said plurality of mobile devices allowed for the peer-relay of notice messages, and wherein, in said third determining step, said server-based participation policies are considered in determining said peer-relay delivery path.

18. The method of claim 17 wherein said notice message identifies said first predetermined mobile device and wherein, in response to receipt of said notice message by said first predetermined mobile device, said first predetermined mobile device establishes a connection with said peer-management server.

19. The method of claim 18 further comprising the step of evaluating, local to each of said plurality of mobile devices, respective local participation policies, wherein said respective local participation policies are selectively determinative, independent of said server-based participation policies, of whether a corresponding one of said plurality of mobile devices will accept receipt of notice messages for peer-relay.

20. The method of claim 19 wherein said local participation policies include criteria defining the timing of participation in the peer-relay of notice messages and battery power remaining threshold.