Method, system and apparatus for managing persona-based notifications at a communication device

• US 9,100,497 B2
• Filed: 04/05/2012
• Issued: 08/04/2015
• Est. Priority Date: 04/05/2012
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Preiss, Bruno Richard, Go, Sunning Chun Ning, Lewis, Allan David
• Primary Examiner(s): EDWARDS, LINGLAN E
• Application Number:
  US13/439,964
• Publication Number:
  US 20130268751A1
• Time in Patent Office: 1,216 Days
• Field of Search: 709/223, 709/227, 709/238, 713/155, 726/5
• US Class Current: 1/1
• CPC Class Codes: H04L 41/08 Configuration management of networks or network elements address allocation H04L61/50
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 41/085 Retrieval of network configuration; Tracking network configuration history
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04M 1/72448 with means for adapting the functionality of the device according to specific conditions
• CPC Class Codes: H04M 2250/66 user interface aspects for indicating selection options for a communication line

Abstract

A method, system and apparatus for managing persona-based notifications at a communication device are provided. A port is dynamically assigned to an application on the basis of a persona at a communication device, the application enabled to receive notifications from a given provider. The port is registered with a server to receive the notification. The port is opened to receive notifications associated with the persona for the application from the server.

Claims

1. A method comprising:

in response to a persona being rendered active at a communication device, determining whether any software ports have been previously assigned to an application under the persona at the communication device and, when no software port has been previously assigned, dynamically assigning a software port to the application on the basis of the persona at the communication device, and when the software port has been previously assigned, dynamically assigning the software port to the application on the basis of the persona at the communication device such that the application uses a same software port under the persona each time the persona is rendered active, the application configured to receive notifications from a given provider;

registering the software port with a server to receive the notifications;

when the persona is rendered active at the communication device, opening the software port to receive notifications associated with the persona for the application from the server, wherein the persona is rendered active by receipt of one or more of;

user credentials, log-in credentials, and one or more identifiers unique to the persona at the communication device; and

when the persona is rendered inactive at the communication device, closing the software port such that notifications associated with the persona are not received from the server,

wherein the same application is assigned a plurality of software ports in a one-to-one relationship with each persona at the communication device under which the application is processed.

2. The method of claim 1, wherein the software port is dynamically assigned when the application is first processed at the communication device under the persona, and the software port is static thereafter with regards to the persona.

3. The method of claim 1, wherein registering the software port comprises transmitting an associated port identifier with a provider identifier to the server.

4. The method of claim 1, further comprising registering the software port with the provider to receive the notifications via the server.

5. The method of claim 4, wherein the registering the software port with the provider comprises transmitting a time-sensitive token to the provider comprising an encrypted port identifier associated with the software port.

6. The method of claim 5, further comprising exchanging decryption data for decrypting the encrypted port identifier associated with the software port with the server, such that the time-sensitive token can be transmitted by the provider to the server for decryption and verification, the server thereafter transmitting to the provider the encrypted port identifier associated with the software port, the provider thereafter transmitting the notifications to the server with the encrypted port identifier associated with the software port for delivery to the communication device.

7. A communication device comprising:

a non-volatile memory unit storing an application; and

a processing unit interconnected with a communication interface and the non-volatile memory unit, said processing unit configured to;

in response to a persona being rendered active at a communication device, determine whether any software ports have previously been assigned to an application under the persona at the communication device and, when no software port has been previously assigned, dynamically assign a software port to the application on the basis of the persona at the communication device, and when the software port has been previously assigned, dynamically assigning the software port to the application on the basis of the persona at the communication device such that the application uses a same software port under the persona each time the persona is rendered active, the application configured to receive notifications from a given provider;

register the software port with a server to receive the notifications;

open the software port when the persona is rendered active at the communication device such that notifications associated with the persona for the application are received from the server, the processing unit further configured to render the persona active by receipt of one or more of;

user credentials, log-in credentials, and one or more identifiers unique to the persona at the communication device; and

close the software port when the persona is rendered inactive at the communication device such that notifications associated with the persona are not received from the server,

wherein the processing unit is further configured to assign a plurality of software ports to the same application in a one-to-one relationship with each persona at the communication device under which the application is processed.

8. The communication device of claim 7, wherein the processing unit is further configured to dynamically assign the software port when the application is first processed at the communication device under the persona, and the software port is static thereafter with regards to the persona.

9. The communication device of claim 7, wherein the processing unit is further configured to register the software port by transmitting an associated port identifier with a provider identifier to the server.

10. The communication device of claim 7, wherein the processing unit is further configured to register the software port with the provider to receive the notifications via the server.

11. The communication device of claim 10, wherein the processing unit is further configured to register the software port with the provider by transmitting a time-sensitive token to the provider comprising an encrypted port identifier associated with the software port.

12. The communication device of claim 11, wherein the processing unit is further configured to exchange decryption data for decrypting the encrypted port identifier associated with the software port with the server, such that the time-sensitive token can be transmitted by the provider to the server for decryption and verification, the server thereafter transmitting to the provider the encrypted port identifier associated with the software port, the provider thereafter transmitting the notifications to the server with the encrypted port identifier associated with the software port for delivery to the communication device.

13. A non-transitory computer-readable storage medium storing a computer program, wherein execution of the computer program is for:

in response to a persona being rendered active at a communication device, determining whether any software ports have been previously assigned to an application under the persona at the communication device and, when no software port has been previously assigned, dynamically assigning a software port to the application on the basis of the persona at the communication device, and when the software port has been previously assigned, dynamically assigning the software port to the application on the basis of the persona at the communication device such that the application uses a same software port under the persona each time the persona is rendered active, the application configured to receive notifications from a given provider;

registering the software port with a server to receive the notifications;

when the persona is rendered active at the communication device, opening the software port to receive notifications associated with the persona for the application from the server, wherein the persona is rendered active by receipt of one or more of;

user credentials, log-in credentials, and one or more identifiers unique to the persona at the communication device; and

when the persona is rendered inactive at the communication device, closing the software port such that notifications associated with the persona are not received from the server,

wherein the same application is assigned a plurality of software ports in a one-to-one relationship with each persona at the communication device under which the application is processed.

14. The non-transitory computer-readable storage medium of claim 13, wherein the software port is dynamically assigned when the application is first processed at the communication device under the persona, and the software port is static thereafter with regards to the persona.

15. The non-transitory computer-readable storage medium of claim 13, wherein registering the software port comprises transmitting an associated port identifier with a provider identifier to the server.

16. The non-transitory computer-readable storage medium of claim 13, further comprising registering the software port with the provider to receive the notifications via the server.

17. The non-transitory computer-readable storage medium of claim 16, wherein the registering the software port with the provider comprises transmitting a time-sensitive token to the provider comprising an encrypted port identifier associated with the software port.

18. The non-transitory computer-readable storage medium of claim 17, further comprising exchanging decryption data for decrypting the encrypted port identifier associated with the software port with the server, such that the time-sensitive token can be transmitted by the provider to the server for decryption and verification, the server thereafter transmitting to the provider the encrypted port identifier associated with the software port, the provider thereafter transmitting the notifications to the server with the encrypted port identifier associated with the software port for delivery to the communication device.