METHOD AND ARRANGEMENT FOR HANDLING RESOURCE DATA

• US 20110252141A1
• Filed: 12/19/2008
• Published: 10/13/2011
• Est. Priority Date: 12/19/2008
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Klein, Mikael, Boberg, Christer, Lindgren, Anders, Lassborn, Sofie
• Granted Patent: US 9,392,070 B2
• Time in Patent Office: Days
• US Class Current: 709/226
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• 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: H04W 48/02 Access restriction performed under specific conditions

Abstract

A method and arrangement in a notification server (300) for controlling notifications with resource data to a subscribing client (A). When a subscription request is received (3:1) from the client for notifications with selected resource data of one or more resources, the access network currently used by the client is determined based on network related information, e.g. obtained from the received subscription request. The delivery of notifications (3:5) is then controlled based on the determined current network.

Claims

1. A method in a notification server for controlling notifications with resource data to a subscribing client (A), comprising the following steps:

receiving a subscription request from the client for notifications with selected resource data of one or more resources,

determining the access network currently used by the client, and

controlling the delivery of notifications with resource data to the client based on the determined current network, wherein the delivery of notifications is controlled by applying a notification rule selected based on the determined current network from network depending notification rules that have been defined for the client.

2. The method according to claim 1, wherein no notifications are delivered if the client is roaming in a visited network, and all upcoming notifications are delivered if the client is present in his/her home network.

3. The method according to claim 1, wherein said notification rule is defined by means of a delivery filter.

4. The method according to claim 3, wherein the delivery filter allows delivery of at least one of:

notifications with a certain type of resource data, notifications not exceeding a maximum data amount, notifications for one or more specific resources, and notifications at certain times of day, week or season.

5. The method according to claim 1, wherein different notification rules are applied depending on a time-out or TTL parameter in the subscription request.

6. The method according to claim 1, wherein the notification rule includes a rate limitation such that the frequency of notifications does not exceed a predefined limit.

7. The method according to claim 1, wherein the notification rule dictates that empty notifications devoid of resource data are sent to the client.

8. The method according to claim 1, wherein the currently used network is determined based on network related information of the client obtained from any of:

said received subscription request, a publish message from the client, a third party registration request received from a session control node serving the client, and a SIP message from the client including INVITE, MESSAGE or OPTIONS.

9. The method according to claim 8, wherein the currently used network is determined from a PANI (P-Access-Network-Info) header in the subscription request, or from a P-Visited-Network-ID header in the registration request.

10. The method according to claim 8, wherein the network related information includes any of the parameters MNC (Mobile Network Code) and MCC (Mobile Country Code).

11. An arrangement in a notification server for controlling notifications with resource data to a subscribing client (A), comprising:

a resource data receiver adapted to collect and store resource data (RD) in a database,

a subscription manager adapted to receive a subscription request (S) from the client for notifications with selected resource data of one or more resources, and to determine the access network currently used by the client, and

a notification sender adapted to control the delivery of notifications (N) with resource data to the client based on the determined current network by applying a notification rule selected based on the determined current network from network depending notification rules that have been defined for the client.

12. The arrangement according to claim 11, wherein the notification sender is further adapted to deliver no notifications if the client is roaming in a visited network, and to deliver all upcoming notifications if the client is present in his/her home network.

13. The arrangement according to claim 11, wherein said notification rule is defined by means of a delivery filter.

14. The arrangement according to claim 13, wherein the delivery filter allows delivery of at least one of:

notifications with a certain type of resource data, notifications not exceeding a maximum data amount, notifications for one or more specific resources, and notifications at certain times of day, week or season.

15. The arrangement according to claim 11, further adapted to apply different notification rules depending on a time-out or TTL parameter in the subscription request.

16. The arrangement according to claim 11, wherein the notification rule includes a rate limitation such that the frequency of notifications does not exceed a predefined limit.

17. The arrangement according to claim 11, wherein the notification rule dictates that empty notifications devoid of resource data are sent to the client.

18. The arrangement according to claim 11, wherein the subscription manager is further adapted to determine the currently used network based on network related information of the client obtained from any of:

said received subscription request, a publish message from the client, a third party registration request received from a session control node serving the client, and a SIP message from the client including INVITE, MESSAGE or OPTIONS.

19. The arrangement according to claim 18, wherein the subscription manager is further adapted to determine the currently used network from a PANI (P-Access-Network-Info) header in the subscription request, or from a P-Visited-Network-ID header in the registration request.

20. The arrangement according to claim 18, wherein the network related information includes any of the parameters MNC (Mobile Network Code) and MCC (Mobile Country Code).