METHOD AND SYSTEM FOR ADDING AN ASPECT TRIGGER TO AN ASPECT

• US 20090299941A1
• Filed: 05/29/2009
• Published: 12/03/2009
• Est. Priority Date: 05/29/2008
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Severino, Clara, Martin-Cocher, Gaelle Christine, Petronijevic, Dejan, McColgan, Brian Edward Anthony
• Granted Patent: US 8,600,923 B2
• Time in Patent Office: Days
• US Class Current: 706/47
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring

Abstract

A method within a computing execution environment for adding an aspect trigger for an aspect, an aspect being an application level abstraction relevant to a source or service, along with the execution environment, where the method includes defining service aspects; inserting or encapsulating the service aspects as named aspects into an abstraction layer in the computing execution environment; and associating the named aspects with the aspect trigger, wherein the abstraction layer is configured to associate aspect triggers for a plurality of client applications.

Claims

1. A method within a computing execution environment for adding an aspect trigger for an aspect, an aspect being an application level abstraction relevant to at least one of a consumer, a source or service, the method comprising:

defining service aspects;

inserting or encapsulating the service aspects as named aspects into an abstraction layer in the computing execution environment; and

associating the named aspects with the aspect trigger,

wherein the abstraction layer is configured to associate aspect triggers for a plurality of client applications.

2. The method of claim 1, wherein the abstraction layer is a server.

3. The method of claim 1, wherein at least one of the named aspects and associated aspect triggers relate to at least one of presence, location or generic aspects or a computed or combined indication of presence, location or generic aspects.

4. The method of claim 1 wherein the aspect trigger is unique for a given application or service.

5. The method of claim 1 wherein the named aspects are common across many applications or services.

6. The method of claim 1 wherein the abstraction layer contains a plurality of aspect triggers.

7. The method of claim 1 wherein the abstraction layer defines additional aspect triggers.

8. The method of claim 1 further comprising:

establishing rules to provide a sequence of steps or logic to compute aspects or aspect triggers.

9. The method of claim 8 wherein the aspect triggers are created or based on rules used to create the named aspect.

10. The method of claim 8 whereby rules are defined using a web services business process execution language.

11. The method of claim 8 wherein the rules incorporate thresholds.

12. The method of claim 8 wherein the rules are encapsulated as a function or procedure.

13. The method of claim 12 wherein the functions or procedures are combined as a library or component for use by the abstraction layer in the computation of other aspect triggers.

14. The method of claim 1 wherein the aspect triggers are part of a component library within the abstraction layer.

15. The method of claim 14 wherein aspect triggers or rules from the component library may be invoked in the calculation of another aspect trigger.

16. The method of claim 1 further comprising performing an action when an aspect trigger fires.

17. The method of claim 16 wherein the action is one of sending a default notification, applying a rules, applying a set of logical steps, or opening a communication session.

18. The method of claim 17 wherein the action is a short message service notification or an open mobile alliance session initiation protocol push notification.

19. The method of claim 16 wherein the action occurs asynchronously.

20. The method of claim 18 wherein the action indicates at least one of a presentity address, aspect change and application routing indicator.

21. The method of claim 1 further comprising providing an administrative interface to establish aspect triggers on behalf of an application or service.

22. The method of claim 1 wherein an aspect trigger is at least one of:

a. an onOpt-in aspect trigger whereby the aspect trigger is invoked when a presentity is determined to have opted in for a given communication service;

b. an onOpt-out aspect trigger whereby the aspect trigger is invoked when a presentity is determined to have opted out for a given communication service;

c. an onUnreachable aspect trigger whereby the aspect trigger is invoked when a presentity is not reachable;

d. an onReachable aspect trigger whereby the aspect trigger is invoked when a presentity is reachable;

e. an onNearby aspect trigger whereby the aspect trigger is invoked when a presentity is nearby;

f. an onOutOf Range aspect trigger whereby the aspect trigger is invoked when a presentity has moved out of a specified range for a given service or application;

g. an on-is-ineligible-session-participant aspect trigger whereby the aspect trigger is invoked when a presentity is unreachable and ineligible for a given service or application;

h. an on-is-eligible-session-participant aspect trigger whereby the aspect trigger is invoked when a presentity is reachable and eligible for a given service or application;

i. an on-pending-subscription aspect trigger whereby the aspect trigger is invoked when a presentity has one or more subscriptions in a pending state;

j. an on-update-note aspect trigger whereby the aspect trigger is invoked when a presentity adds or updates a personal note;

k. an on-activity-update trigger whereby the aspect trigger is invoked when a presentity adds or updates an activity;

l. an on-registration-active or an on-registration-terminated trigger whereby the aspect trigger is invoked when a presentity is registered or unregistered from a given communications service;

m. an on-location-change trigger whereby the aspect trigger is invoked when a presentity is determined to have changed location;

n. an on-icon-change trigger whereby the aspect trigger is invoked when a presentity has changed his or her icon;

o. an on-mood-change trigger whereby the aspect trigger is invoked when a presentity has changed his or her mood;

p. an onNetworkAvailable or onNetworkUnavailable trigger whereby the aspect trigger is invoked when a presentity device is detected to be network available or unavailable;

q. an on-icon-metadata-change trigger whereby the aspect trigger is invoked when icon metadata changes for a given presentity;

r. an on-relative-service-preference-change trigger whereby the aspect trigger is invoked when a relative service preference for a presentity has changed;

s. an on-session-involved or an on-session-uninvolved trigger whereby the aspect trigger is invoked when a presentity is currently participating or not participating in an associated session of a given communications service;

t. an on-session-count-change trigger whereby the aspect trigger is invoked when a total number of communications sessions a presentity is involved with change;

u. an on-timezone-change trigger whereby the aspect trigger is invoked when a presentity is determined to have changed timezones;

v. an on-personal-interest-change trigger whereby the aspect trigger is invoked when a presentity is determined to have changed his or her personal interests;

w. an on-barred-active trigger whereby the aspect trigger is invoked when a presentity is barred for the given communications service; and

x. an on-barred-terminated trigger whereby the aspect trigger is invoked when a presentity is un-barred from a given communications service.

23. An execution environment comprising:

applications, said applications requiring aspects for execution;

an abstraction layer having application aspects, an aspect being an application level abstraction relevant to at least one of a consumer, a source or service; and

aspect triggers adapted to be invoked when a condition for an aspect is satisfied.

24. The execution environment of claim 23 wherein said aspect triggers are associated with a given application or service.

25. The execution environment of claim 23, wherein said aspect triggers are associated with a given user, group identity or given data.

26. The execution environment of claim 24 wherein said aspects are associated with a given user, group identity or given data.