METHOD OF REDUCING SIZE OF PRESENCE MESSAGES

• US 20100274844A1
• Filed: 12/04/2007
• Published: 10/28/2010
• Est. Priority Date: 12/04/2007
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Boberg, Christer, Lindgren, Anders
• Granted Patent: US 9,591,129 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• 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: H04M 3/42365 Presence services providing information on the willingness to communicate or the ability to communicate in terms of media capability or network connectivity
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04M 7/0093 signalling arrangements in networks

Abstract

A method in a communication network of delivering messages associated with an information exchange service. A message, to be delivered between two entities is interrogated to determining if the data content has already been delivered to the terminating entity. If the data content has not already been delivered to the second entity, the message is transmitted to the second entity unchanged, while the message is modified, so that the modified message comprises a data identifier, identifying the data content, but no data content. The modified message is then transmitted to the terminating entity, and the data identifier is cached together with the associated data content when a successful transmission of the message has been verified. The suggested versioning mechanism enables transmission of messages with a reduced size.

Claims

1. A method in a communication network of delivering messages associated with an information exchange service between a first entity and a second entity, said method comprising the following steps, executed by the first entity:

processing a message associated with an information exchange service, said message comprising data content and a request for versioning, wherein versioning comprises associating each version of data content of a message with a data identifier, identifying said version,

determining if the data content has already been delivered to the second entity, and

transmitting said message unchanged to the second entity in case said data content has not already been delivered to the second entity, or

transmitting a modified message to the second entity in case the data content has already been delivered to the second entity, said modified message comprising a data identifier but no data content.

2. A method according to claim 1, wherein said first entity is a server and said second entity is a client.

3. A method according to claim 2, wherein said message is a SIP notification.

4. A method according to claim 3, further comprising the following step, to be executed prior to said processing step:

receiving a request for an information exchange service from the second entity, said request indicating that versioning is required.

5. A method according to claim 1, wherein said first entity is a client and said second entity is a server.

6. A method according to claim 5, wherein said message is a SIP publication.

7. A method according to claim 1, wherein said determining step comprises interrogating a cache.

8. A method according to claim 1, wherein said data identifier is inserted into said message at the first entity.

9. A method according to claim 1, wherein said data identifier is provided from the second entity.

10. A method according to claim 9, wherein said data identifier is provided to the first entity in a response message, said response message indicating successful delivery of said message.

20. A method according to claim 1, claims, wherein said data content and said associated data identifier are stored in a cache of said first entity subsequent to receiving a response message, verifying that said message has been successfully delivered to and stored at a cache of said second entity.

21. A method according to claim 20, wherein a first response message comprises an indication of the total capacity of the cache of said second entity.

22. A method according to claim 20, wherein each response message comprises an indication of the remaining capacity of the cache of said second entity.

23. A method according to claim 1, wherein said data identifier is a version number or a unique identity.

24. A method according to claim 1, wherein said data identifier is an Etag.

11. A method in a communication network of handling messages associated with an information exchange service at a first entity, wherein said messages are delivered from a second entity to said first entity, said method comprising the following steps:

receiving a message associated with the requested information exchange service, said message comprising a request for versioning, wherein versioning comprises associating each version of data content of a message with a data identifier, identifying said version,

determining if said message comprises data content,

retrieving a data identifier associated with the data content and storing said data content together with said data identifier, in case said message comprises data content, or

providing the message with stored data content, associated with a data identifier, said data identifier being retrieved from the message, in case said message does not comprise any data content, and

processing the message.

12. A method according to claim 11, wherein said first entity is a client and said second entity is a server.

13. A method according to claim 12, wherein said message is a SIP notification.

14. A method according to claim 13, further comprising the following step, to be executed prior to said receiving step:

forwarding a request for an information exchange service to the second entity, said request indicating that versioning is required.

15. A method according to claim 11, wherein said first entity is a server and said second entity is a client.

16. A method according to claim 15, wherein said message is a SIP publication.

17. A method according to claim 11, wherein said retrieving step comprises retrieving said data identifier from the first entity.

18. A method according to claim 17, wherein said data identifier is forwarded from the first entity to the second entity in a response message, said response message indicating a successful delivery of said message.

19. A method according to claim 11, wherein said retrieving step comprises retrieving the data identifier from the message, said data identifier being inserted into said message at the second entity.

25. A first entity of delivering messages associated with an information exchange service to a second entity, said first entity comprising:

a processing unit for processing a message associated with the requested information exchange service, said message comprising data content and a request for versioning, wherein versioning comprises associating each version of data content of a message with a data identifier, identifying said version,

a versioning unit for determining if the data content has already been delivered to the client, and

a communication unit for transmitting the message unchanged to the client in case said data content has not already been delivered to said client, or for transmitting a modified message to the client in case said data content has already been delivered to said client, said modified message comprising a data identifier but no data content.

26. A first entity according to claim 25, wherein said first entity is a server and said second entity is a client.

27. A first entity according to claim 26, wherein said communication unit further comprises:

a receiver for receiving a request for an information exchange service from the second entity, said request indicating that versioning is required.

28. A first entity according to claim 26, wherein said versioning unit is adapted to interrogate a cache in order to determine if said data content has already been delivered to said first entity.

29. A first entity according to claim 25, wherein said first entity is a client and said second entity is a server.

30. A first entity of handling messages associated with an information exchange service, wherein said messages are received from a second entity, said method comprising the following steps:

a communication unit for receiving a message from the second entity, said message comprising a request for versioning, wherein versioning comprises associating each version of data content of a message with a data identifier, identifying said version,

a versioning unit for determining if said message comprises data content, said versioning unit being adapted to retrieve a data identifier associated with the data content and to cache said data content together with said data identifier, in case said message comprises data content, or to provide the message with stored data content associated with a data identifier, after having retrieved said data identifier from the message, in case said message does not comprise any data content, and

a processing unit for processing the message.

31. A first entity according to claim 30, wherein said versioning unit is connected to a cache, said versioning unit being adapted to cache data content and an associated data identifier in response to a successfully delivered or received message.

32. A first entity according to claim 30, wherein said first entity is a server and said second entity is a client.

33. A first entity according to claim 30, wherein said first entity is a client and said second entity is a server.