Method and communications node for creation and transmission of user specific dictionary for compression and decompression of messages

• US 20080037509A1
• Filed: 06/30/2006
• Published: 02/14/2008
• Est. Priority Date: 06/30/2006
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Foti, George
• Application Number:
  US11/477,638
• Publication Number:
  US 20080037509A1
• Time in Patent Office: Days
• US Class Current: 370/349
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/70 Media network packetisation
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC

Abstract

A method for exchanging compression/decompression dictionaries, and a communications node, which comprises a client module issuing and receiving messages, a compression/decompression module for compression/decompression of messages issued and received by the client module, a first dictionary for use by the compression/decompression module, and a second dictionary for use by the compression/decompression module. When the client module determines a sequence based on which to exchange dictionaries with one or more peers (e.g. a P-CSCF), it creates the first dictionary comprising at least one prioritised type of message and sends the first dictionary to the compression/decompression module, which stores the first dictionary and further sends it to at least the peer node. Still based on said determined sequence, the client module further creates the second dictionary comprising at least one other type of message, sends the second dictionary to the compression/decompression module which stores it and further sends to a peer node.

Claims

1. A method for exchanging dictionaries used for compression and decompression of messages, the method comprising the steps of:

a. determining a sequence based on which to send said dictionaries to one or more peers;

b. based on said determined sequence, creating a first dictionary comprising at least one prioritised type of message that is to be compressed;

c. sending the first dictionary to a SigComp module;

d. storing the first dictionary by the SigComp module;

e. sending the first dictionary by the SigComp module to at least a peer node;

f. based on said determined sequence, creating a second dictionary comprising at least one other type of message that is to be compressed;

g. sending the second dictionary to the SigComp module;

h. storing the second dictionary by the SigComp module; and

i. sending the second dictionary by the SigComp module to a peer node.

2. The method claimed in claim 1, wherein the first and second dictionaries are Session Initiation Protocol (SIP) dictionaries, and the at least one prioritised type of message comprises a SIP INVITE message.

3. The method claimed in claim 1, wherein the first and second dictionaries are Session Initiation Protocol (SIP) dictionaries, and the at least one other type of message comprises a SIP NOTIFY message.

4. The method claimed in claim 1, wherein step b. comprises the steps of:

b.1. creating a message of the prioritized type; and

b.2. including the message of the prioritized type in the first dictionary.

5. The method claimed in claim 1, wherein step f. comprises the steps of:

f.1. creating a message of the other type; and

f.2. including the message of the other type in the second dictionary.

6. The method claimed in claim 1, wherein steps a. through i. are performed responsive to the step of:

j. launching an application client module on a communications node.

7. The method claimed in claim 1, wherein steps a. through i. are performed responsive to the step of:

j. registering a terminal with a communications network.

8. The method claimed in claim 1, wherein the prioritised type of message is a message created by a client module, the first dictionary being specific to the terminal.

9. The method claimed in claim 1, wherein the other type of message is a message created by a client module, the second dictionary being specific to the terminal.

10. A communications node comprising:

a client module that issues and receives messages;

a compression/decompression module for compressing and decompressing the messages issued and received by the client module;

a first dictionary for use by the compression/decompression module in compression and decompression of the messages issued and received by the client module;

a second dictionary for use by the compression/decompression module in compression and decompression the messages issued and received by the client module;

wherein the client module determines a sequence based on which to exchange dictionaries with one or more peers and based on said determined sequence, creates the first dictionary comprising at least one prioritised type of message that is to be compressed and sends the first dictionary to the compression/decompression module, which stores the first dictionary and further sends it to at least a peer node;

further wherein the client module, based on said determined sequence, creates the second dictionary comprising at least one other type of message that is to be compressed, sends the second dictionary to the compression/decompression module which stores it and further sends to a peer node.

11. The communications node claimed in claim 10, wherein the first and second dictionaries are Session Initiation Protocol (SIP) dictionaries, and the at least one prioritised type of message comprises a SIP INVITE message.

12. The communications node claimed in claim 10, wherein the first and second dictionaries are Session Initiation Protocol (SIP) dictionaries, and the at least one other type of message comprises a SIP NOTIFY message.

13. The communications node claimed in claim 10, wherein for creating the first dictionary, the client module creates a message of the prioritized type, and includes the message of the prioritized type in the first dictionary.

14. The communications node claimed in claim 10, wherein for creating the second dictionary, the client module creates a message of the other type, and includes the message of the other type in the second dictionary.

15. The communications node claimed in claim 10, wherein the client module is first launching on a communications node.

16. The communications node claimed in claim 10, wherein the terminal first registers with a communications network.

17. The method claimed in claim 10, wherein the prioritised type of message is a message created by the client module, the first dictionary being specific to the terminal.

18. The method claimed in claim 10, wherein the other type of message is a message created by the client module, the second dictionary being specific to the terminal.