Method and system for specifying, applying and extending application related aspects through policies, rules and/or triggers

• US 8,255,482 B2
• Filed: 12/12/2008
• Issued: 08/28/2012
• Est. Priority Date: 12/14/2007
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: McColgan, Brian Edward Anthony, Martin-Cocher, Gaelle Christine, Shenfield, Michael
• Primary Examiner(s): Lin, Kenny
• Assistant Examiner(s): SMARTH, GERALD A
• Application Number:
  US12/333,784
• Publication Number:
  US 20090157805A1
• Time in Patent Office: 1,355 Days
• Field of Search: 709/217
• US Class Current: 709/217
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• 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: H04L 67/55 Push-based network services
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/029 Location-based management or tracking services
• CPC Class Codes: H04W 4/20 Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel

Abstract

A method and system for the creation of aspects from a service or application, the method defining related service aspects; inserting or encapsulating service aspects as named aspects into an abstraction layer in an execution environment; and associating the named aspects with logic in the abstraction layer to support application or service function points.

Claims

1. A method performed by a server, the method comprising:

receiving a message from a presence client on a user device at the server, the message requesting establishment of a presence context that provides abstracted presence information to the presence client; and

establishing, through communication with a presence server that is adapted to store presence information in the form of raw data and state updates received from presentities, the presence context for an application or a service employed by the user device based on the message, the presence context providing the abstracted presence information for at least one of the service, the application or a class related to said application or said service,

wherein the presence context abstracts presence information by consolidating presence information from the presence server into a presence aspect using at least one of a rule and policy associated with at least one of the service, the application or said class for provision to the presence client on the user device by the server thereby reducing an amount of data to be transferred to the presence client.

2. The method of claim 1 wherein the message includes a service-id attribute that indicates the service to which the application is bound.

3. The method of claim 2 wherein the message further includes a user-id attribute that identifies a user of the user device.

4. The method of claim 2 wherein the service-id attribute indicates at least one of an Instant Message (IM) service and a Push-to-talk over Cellular (PoC) service.

5. The method of claim 1 wherein the presence context is defined by at least one of a policy, a rule and a trigger associated with the service.

6. The method of claim 1 wherein the server is integrated with an application server or an Open Mobile Alliance enabler.

7. The method of claim 6 wherein the application server is at least one of a Push-to-talk over Cellular (PoC) server, an Instant Message (IM) server and the presence server.

8. The method of claim 1 wherein the server is a dedicated server that is distinct from the presence server.

9. The method of claim 1 wherein the message includes a service-id attribute that corresponds to a class of service, the class of service grouping the application or said service with other applications or other services, respectively, based on a mutual characteristic.

10. The method of claim 9 wherein the mutual characteristic is employment of similar or common presence aspects.

11. The method of claim 9 wherein the service-id attribute identifies a policy that at least partially defines the presence context, the policy specifying a treatment of a presence aspect by the server.

12. The method of claim 11 wherein the presence context is further defined by at least one of a rule and a trigger based on the presence aspect.

13. A non-transitory computer-readable medium storing instructions that cause a processor to execute a server configured to perform a method comprising:

receiving a message from a presence client on a user device at the server, the message requesting establishment of a presence context that provides abstracted presence information to the presence client; and

establishing, through communication with a presence server that is adapted to store presence information in the form of raw data and state updates received from presentities, the presence context for an application or a service employed by the user device based on the message, the presence context providing the abstracted presence information for at least one of the service, the application or a class related to said application or said service,

wherein the presence context abstracts presence information by consolidating presence information from the presence server into a presence aspect using at least one of a rule and policy associated with at least one of the service, the application or said class for provision to the presence client on the user device by the server thereby reducing an amount of data to be transferred to the presence client.

14. A network device comprising:

a communication portion configured to receive a message from a presence client on a user device, the message requesting establishment of a presence context that provides abstracted presence information to the presence client; and

a server configured to establish, through communication with a presence server that is adapted to store presence information in the form of raw data and state updates received from presentities, the presence context for an application or a service employed by the user device based on the message, the presence context providing the abstracted presence information for at least one of the service, the application or a class related to said application or said service,

wherein the presence context abstracts presence information by consolidating presence information from the presence server into a presence aspect using at least one of a rule and policy associated with at least one of the service, the application or said class for provision to the presence client on the user device by the server thereby reducing an amount of data to be transferred to the presence client.

15. The network device of claim 14 wherein the message includes a service-id attribute that indicates the service to which the application is bound.

16. The network device of claim 15 wherein the message further includes a user-id attribute that identifies a user of the user device.

17. The network device of claim 15 wherein the service-id attribute indicates at least one of an Instant Message (IM) service and a Push-to-talk over Cellular (PoC) service.

18. The network device of claim 14 wherein the presence context is defined by at least one of a policy, a rule and a trigger associated with the service.

19. The network device of claim 14 wherein the presence server is configured on the network device.

20. The network device of claim 14 wherein the message includes a service-id attribute that corresponds to a class of service, the class of service grouping the application or said service with other applications or other services, respectively, based on a mutual characteristic.

21. The network device of claim 20 wherein the mutual characteristic is employment of similar or common presence aspects.

22. The network device of claim 20 wherein the service-id attribute identifies a policy that at least partially defines the presence context, the policy specifying a treatment of a presence aspect by the server.

23. The network device of claim 22 wherein the presence context is further defined by at least one of a rule and a trigger based on the presence aspect.