Device and method for temporary deactivation of subscriber information

• US 20040157582A1
• Filed: 11/12/2003
• Published: 08/12/2004
• Est. Priority Date: 05/17/2001
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Peglion, Marc, Virtanen, Olavi Kari, Eskelinen, Timo, Paldan, Esko
• Application Number:
  US10/477,394
• Publication Number:
  US 20040157582A1
• Time in Patent Office: Days
• US Class Current: 455/403
• CPC Class Codes: H04W 28/10 Flow control between communication endpoints
• CPC Class Codes: H04W 8/04 Registration at HLR or HSS [Home Subscriber Server]
• CPC Class Codes: H04W 8/12 between location registers or mobility servers
• CPC Class Codes: H04W 8/18 Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Abstract

The invention relates to a method and system for controlling information flow in a communication system comprising at least one subscriber equipment, and a subscriber information database entity which contains subscription-related information for defining the management of packet-based information flow to and/or from respective subscriber equipments. The database entity contains additional information associated to the stored subscription-related information which additional information defines whether stored subscription-related information may or may not be used for actually defining the management of packet-based information flow to and/or from respective subscriber equipments.

Claims

1. Method for controlling information flow in a communication system comprising at least one subscriber equipment and a subscriber information database entity which contains subscription-related information for defining the management of packet-based information flow to and/or from respective subscriber equipments, wherein the database entity contains additional information associated to the stored subscription-related information, said additional information defining whether stored subscription-related information may or may not be used for actually defining the management of packet-based information flow to and/or from respective subscriber equipments.

2. Method according to claim 1, wherein the communication system comprises at least one support node for handling the information flow to and/or from the subscriber equipment.

3. Method according to claim 2, wherein the support node is a GPRS Support Node.

4. Method according to any one of the preceding claims, wherein the subscriber information database entity is a Home Location Register (HLR).

5. Method according to any one of the preceding claims, wherein the subscription-related information concerns one or more PDP Contexts.

6. Method according to any one of the preceding claims, wherein, when said additional information defining that the stored subscription-related information may not be used for actually defining the management of packet-based information flow to and/or from respective subscriber equipments is written into said database entity, the database entity sends a message to a support node storing the subscription-related information, the message commanding the support node to delete the stored subscription-related information.

7. Method according to any one of the preceding claims, wherein, when said additional information defining that the stored subscription-related information may be used for actually defining the management of packet-based information flow to and/or from respective subscriber equipments is written into said database entity, the database entity sends a message to a support node for copying at least part of the subscription-related information stored in the database entity to the support node for subsequent use for defining the management of packet-based information flow to and/or from respective subscriber equipments.

8. Method according to any one of the preceding claims, wherein said additional information defining that the stored subscription-related information may or may not be used for actually defining the management of packet-based information flow to and/or from respective subscriber equipments is written into said database from an operator entity.

9. Method according to any one of the preceding claims, wherein said packet-based information flow is based on GPRS.

10. Method according to any one of the preceding claims, wherein stored subscription-related information which is defined by the associated additional information not to be used for actually defining the management of packet-based information flow to and/or from respective subscriber equipments, is automatically deleted from the database entity after expiry of a predetermined time interval after writing this additional information into the database entity.

11. System for controlling information flow in a communication system comprising at least one subscriber equipment and a subscriber information database entity which contains subscription-related information for defining the management of packet-based information flow to and/or from respective subscriber equipments, wherein the database entity contains additional information associated to the stored subscription-related information, said additional information defining whether stored subscription-related information may or may not be used for actually defining the management of packet-based information flow to and/or from respective subscriber equipments.

12. System according to claim 11, comprising at least one support node for handling the information flow to and/or from the subscriber equipment.

13. System according to claim 12, wherein the support node is a GPRS Support Node.

14. System according to any one of the preceding system claims, wherein the subscriber information database entity is a Home Location Register (HLR).

15. System according to any one of the preceding system claims, wherein the subscription-related information is or concerns one or more PDP Contexts.

16. System according to any one of the preceding system claims, wherein, when said additional information defining that the stored subscription-related information may not be used for actually defining the management of packet-based information flow to and/or from respective subscriber equipments is written into said database entity, the database entity sends a message to a support node storing the subscription-related information, the message commanding the support node to delete the stored subscription-related information.

17. System according to any one of the preceding system claims, wherein, when said additional information defining that the stored subscription-related information may be used for actually defining the management of packet-based information flow to and/or from respective subscriber equipments is written into said database entity, the database entity sends a message to a support node for copying at least part of the subscription-related information stored in the database entity to the support node for subsequent use for defining the management of packet-based information flow to and/or from respective subscriber equipments.

18. System according to any one of the preceding system claims, comprising an operator entity for writing said additional information into said database.

19. System according to any one of the preceding system claims, wherein said packet-based information flow is based on GPRS.

20. System according to any one of the preceding system claims, wherein a timer means is provided in the subscriber information database entity or in an entity cooperating with the database entity, the database entity or cooperating entity being adapted to trigger the timer means when a deactivation of stored subscription-related information takes place, and to delete, after expiry of a predetermined time after deactivation, a deactivated stored subscription-related information from the database entity.

21. Subscriber information database entity, preferably for use in a method according to any one of the preceding method claims, or in a system according to any one of the preceding system claims, said database entity containing subscription-related information for defining the management of packet-based information flow to and/or from subscriber equipments, as well as additional information associated to the stored subscription-related information, said additional information defining whether stored subscription-related information may or may not be used for actually defining the management of packet-based information flow to and/or from respective subscriber equipments.

22. Database entity according to claim 21, wherein the subscriber information database entity is a Home Location Register (HLR).

23. Database entity according to claim 21 or 22, wherein the subscription-related information is or concerns one or more PDP Contexts.

24. Database entity according to any one of the preceding entity claims, wherein, when said additional information defining that the stored subscription-related information may not be used for actually defining the management of packet-based information flow to and/or from respective subscriber equipments is written into said database entity, the database entity is adapted to send a message to a support node storing the subscription-related information, the message commanding the support node to delete the stored subscription-related information.

25. Database entity according to any one of the preceding entity claims, wherein, when said additional information defining that the stored subscription-related information may be used for actually defining the management of packet-based information flow to and/or from respective subscriber equipments is written into said database entity, the database entity is adapted to send a message to a support node for copying at least part of the subscription-related information stored in the database entity to the support node for subsequent use for defining the management of packet-based information flow to and/or from respective subscriber equipments.

26. Database entity according to any one of the preceding entity claims, comprising a timer means, the database entity being adapted to trigger the timer means when a deactivation of stored subscription-related information takes place, and to delete, after expiry of the timer means, a deactivated stored subscription-related information from the database entity.