Friendly Names for Stored CPM Conversation Histories

• US 20150032828A1
• Filed: 07/26/2013
• Published: 01/29/2015
• Est. Priority Date: 07/26/2013
• Status: Abandoned Application

• Current Assignee: Blackberry Limited
• Original Assignee: Blackberry Limited
• Inventors: rdgh, Zoltn
• Application Number:
  US13/952,365
• Publication Number:
  US 20150032828A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 67/00 Network arrangements or protocols for supporting network services or applications user-to-user messaging H04L51/00; network arrangements, protocols or services for supporting real-time applications in data packet communications networks H04L65/00
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor

Abstract

A method is provided for providing a meaningful representation for a conversation that occurs according to an OMA CPM protocol. The method comprises generating a friendly name for the conversation, wherein the friendly name comprises a string of characters that form a meaningful expression to a conversation participant, and associating the friendly name with the conversation.

Claims

1. A method for identifying a conversation that occurs according to an Open Mobile Alliance (OMA) Converged IP (Internet Protocol) Messaging (CPM) protocol, the method comprising:

generating a friendly name for the conversation, wherein the friendly name comprises a string of characters that form a meaningful expression to a conversation participant; and

associating the friendly name with the conversation.

2. The method of claim 1, wherein the friendly name is generated by an OMA Participating Function (PF).

3. The method of claim 2, wherein the PF generates the friendly name based on information extracted from a CPM Conversation History.

4. The method of claim 2, wherein the PF maps the friendly name to an OMA Conversation-ID when the conversation is recorded into an OMA Message Storage Server.

5. The method of claim 4, wherein, before the PF attempts to record the conversation, the PF determines whether a CPM Conversation History folder associated with the conversation exists and whether the CPM Conversation History folder has a friendly name, and wherein, when the CPM Conversation History folder does not have a friendly name, the PF generates a friendly name and assigns the friendly name to the CPM Conversation History folder.

6. The method of claim 1, wherein the friendly name is generated by one of:

a CPM client;

a functional component of the OMA CPM Enabler other than the PF; and

an entity external to OMA CPM protocols.

7. The method of claim 6, wherein the friendly name is generated by the CPM client when the CPM client encounters a CPM Conversation History without a friendly name, and wherein the CPM client takes measures to ensure that a race condition does not occur in the generation of the friendly name.

8. The method of claim 1, wherein the friendly name is stored as a mailbox extension for a corresponding CPM Conversation History folder via the use of an Internet Message Access Protocol (IMAP) metadata extension.

9. The method of claim 8, wherein the metadata extension is one of:

a registered mailbox entry; and

a newly defined mailbox entry.

10. The method of claim 9, wherein, when the metadata extension is a registered mailbox entry, the metadata extension is the /shared/comment registration.

11. The method of claim 1, wherein all devices of a single user use the same friendly name for the same conversation.

12. The method of claim 11, wherein the user is allowed to modify the friendly name, and wherein, responsive to the modification, all of the user'"'"'s devices are synchronized with modified friendly name.

13. An Open Mobile Alliance (OMA) Converged IP (Internet Protocol) Messaging (CPM) Participating Function (PF), the PF comprising:

a processor configured such that the PF generates a friendly name for a CPM based conversation, wherein the friendly name comprises a string of characters that form a meaningful expression to a conversation participant, and the processor further configured such that the PF associates the friendly name with the conversation.

14. The PF of claim 13, wherein the PF generates the friendly name based on information extracted from a CPM Conversation History.

15. The PF of claim 13, wherein the PF maps the friendly name to an OMA Conversation-ID when the conversation is recorded into an OMA Message Storage Server.

16. The PF of claim 15, wherein, before the PF attempts to record the conversation, the PF determines whether a CPM Conversation History folder associated with the conversation exists and whether the CPM Conversation History folder has a friendly name, and wherein, when the CPM Conversation History folder does not have a friendly name, the PF generates a friendly name and assigns the friendly name to the CPM Conversation History folder.

17. The PF of claim 13, wherein the friendly name is stored as a mailbox extension for a corresponding CPM Conversation History folder via the use of an Internet Message Access Protocol (IMAP) metadata extension.

18. The PF of claim 17, wherein the metadata extension is one of:

a registered mailbox entry;

or

a newly defined mailbox entry,

and wherein, when the metadata extension is a registered mailbox entry, the metadata extension is the /shared/comment registration.

19. An Open Mobile Alliance (OMA) Converged IP (Internet Protocol) Messaging (CPM) client, the client comprising:

a processor configured such that the client generates a friendly name for a CPM-based conversation, wherein the friendly name comprises a string of characters that form a meaningful expression to a conversation participant, and the processor further configured such that the client associates the friendly name with the conversation.

20. The client of claim 19, wherein the friendly name is generated by the client when the client encounters a CPM Conversation History without a friendly name, and wherein the client takes measures to ensure that a race condition does not occur in the generation of the friendly name.