METHOD FOR MANAGING THE REPORTING OF THE PRESENCE OF A TERMINAL WITHIN A COMMUNICATIONS NETWORK

Abstract

A method is disclosed of managing the reporting of the presence of a communications terminal in a communication network including a control rules application entity able to implement a presence reporting mechanism and a credits management entity configured to transmit a request for subscription to the presence reporting mechanism to the control rules application entity. The method includes verifying, during the establishment of a communication session between the terminal and a packet communication network, involving a control entity providing control rules to the control rules application entity, that the control entity is configured to trigger a subscription to the presence reporting mechanism with the control rules application entity. When the control entity is configured to trigger a subscription to the presence reporting mechanism, an indicator of intervention of the presence reporting mechanism is dispatched to the credits management entity, to inhibit a subscription to the mechanism by the credits management entity.

Claims

1. A method for managing the reporting of the presence of a communications terminal within a communications network comprising a control rules application entity, configured to implement a mechanism for reporting the presence of the terminal within a presence reporting area of the network, and a credit management entity configured for transmitting a request for subscription to the mechanism for reporting the presence of the terminal to the control rules application entity, the method comprising: verifying, during a phase for establishing a communication session between the terminal and a packet communications network, involving a control entity supplying control rules to the control rules application entity, that the control entity is configured for triggering a subscription to the mechanism for reporting the presence of the terminal to the control rules application entity, and when the control entity is configured for triggering a subscription to the mechanism for reporting the presence of the terminal, dispatching to the credit management entity an indicator of support of the presence reporting mechanism by the control entity, configured to inhibit a subscription to the mechanism by the credit management entity.

2. The method as claimed in claim 1, wherein the verification comprises verifying that at least one of the rules supplied by the control entity comprises a presence reporting area identifier associated with the communication session.

3. The method as claimed in claim 1, further comprising establishing a control session, at the moment of establishment of the communication session, between the control entity and the control rules application entity, and a negotiation of functions supported by the control entity and control rules application entity, the verification being carried out when the control session is established, and comprising verifying that at least one of the functions comprises a parameter indicating that the control entity is configured for triggering a subscription to the presence reporting mechanism.

4. The method as claimed in claim 1, further comprising, when the control entity and the credit management entity are respectively configured for triggering a subscription to the mechanism for reporting the presence of the terminal within a first presence reporting area of the network and within a second presence reporting area of the network: dispatching an identifier of the first presence reporting area to the credit management entity; and verifying by the credit management entity that the identifier of the first area is identical to an identifier of the second presence reporting area, the subscription of the credit management entity to the mechanism for reporting the presence of the terminal being inhibited when the first and second presence reporting areas are not verified as identical.

5. A control entity, configured to implement a mechanism for reporting the presence of a communications terminal within a presence reporting area of a communications network, the control entity configured to: establish a control session with a control rules application entity; supply control rules to the control rules application entity; verify, during a phase for establishing a communication session between the terminal and a packet communications network, that the control entity is configured for triggering a subscription to the mechanism for reporting the presence of the terminal to the control rules application entity; and when the control entity is configured for triggering a subscription to the mechanism for reporting the presence of the terminal, dispatch to a credit management entity an indicator of support of the presence reporting mechanism by the control entity, designed to inhibit a subscription of the credit management entity to the mechanism.

6. The entity as claimed in claim 5, further configured to, when a control session is established with the control rules application entity, negotiate functions supported by the control entity and control rules application entity, and verify, when the control session is established, that at least one of the functions comprises a parameter indicating that the control entity is configured for triggering a subscription to the presence reporting mechanism.

7. A control rules application entity, configured to: establish a control session with a control entity designed to implement a mechanism for reporting the presence of a communications terminal within a presence reporting area of a communications network; receive control rules from the control entity, a request for subscription to the presence reporting mechanism from the control entity, and an indicator of support of the presence reporting mechanism by the control entity, configured to inhibit a subscription to the mechanism by a credit management entity; dispatch the indicator of support to the credit management entity.

8. The entity as claimed in claim 7, further configured to, when a control session is established with the control entity, negotiate functions supported by the control rules application entity and control entity, at least one of the functions comprising a parameter indicating that the control entity is configured for triggering a subscription to the presence reporting mechanism.

9. A system for managing the reporting of the presence of a communications terminal within a presence reporting area of a communications network, comprising: the control entity of claim 5; a rules application entity; and an entity configured to control a credit associated with the communication session, the rules application entity configured to: establish a control session with the control entity; receive, from the control entity, control rules, a request for subscription to the presence reporting mechanism, and an indicator of support of the presence reporting mechanism, configured to inhibit a subscription to the mechanism by the credit management entity; and dispatch the indicator of support to the credit management entity.

10. A control entity, having stored thereon program code instructions which, when the program code instructions are executed by a processor of the control entity, cause the control entity to perform the method of claim 1.

11. A rules application entity, having stored thereon program code instructions which, when the program code instructions are executed by a processor of the rules application entity, cause the rules application entity to perform the method of claim 1.

12. A non-transitory computer-readable medium having stored thereone instructions, which when executed by a processor of a control entity, cause the control entity to perform the method of claim 1.

13. A non-transitory computer-readable medium having stored thereone instructions, which when executed by a processor of a rules application entity, cause the rules application entity to perform the method of claim 1.

Description

[0056] The invention will be better understood with the aid of the following description of particular embodiments, with reference to the appended drawings in which, aside from FIG. 1 already commented relating to the prior art:

[0057] FIG. 2 shows steps of a method for managing the reporting of the presence of a terminal in a communications network according to the prior art;

[0058] FIGS. 3a to 3c show steps of a reporting management method according to a first particular embodiment;

[0059] FIG. 4 shows steps of a reporting management method according to a second particular embodiment;

[0060] FIG. 5 shows a rules application entity according to one particular embodiment;

[0061] FIG. 6 shows a control entity according to one particular embodiment.

[0062] FIG. 2 shows a system 3 for managing the reporting of the presence of a terminal 4 within a presence reporting area of a communications network 5. This communications network 5 is, by way of example, an EPS (for “Evolved Packet System”) network. The terminal 4 accesses the communications network 5 via a mobile access network 1.

[0063] The system 3 more particularly allows a change of location, with respect to a presence reporting area, of the terminal 4 to be reported, for which terminal a communication session is established with a packet communications network 2. The change of location corresponds to an input or to an output of the terminal 4 in the presence reporting area associated with the terminal 4. This reporting area is typically a geographical area defined by one or more cells of the mobile network 1.

[0064] The system 3 is integrated into a PCC architecture and comprises a control entity 20, a rules application entity 10 and a credit management entity 30. The control entity 20 is for example a PCRF entity, the rules application entity 10 a PCEF entity and the credit management entity 30 an OCS entity such as described in the specification document “TS 23.203”. In the embodiment described, the PCEF entity is furthermore a module of an interconnection gateway P-GW (for “Packet Data Network-Gateway”).

[0065] Such as previously described, the control entity 20 collects information associated with the network, with a subscriber, or else associated with an application. The control entity 20 adapts and controls the usage of the network resources according to services required by the subscriber and to his/her subscriber profile, and sends for this purpose PCC control rules to the rules application entity 10.

[0066] When a communication session is opened between the terminal 4 and the packet communications network 2, the control rules application entity 10 opens a control session with the control entity 20 in order to obtain the control rules to be applied to the communication session. The rules application entity 10 transmits the features requested for the communication session to the control entity 20. Depending on these features and on the information that it has collected such as previously mentioned, the control entity 20 determines the control rules (quality of service, pricing, etc.) to be applied for the various services transported by the communication session and sends them to the rules application entity 10. In particular, if the control entity 20 determines that the terminal 4 is for example associated with a provision of services associated with a location of the terminal 4 within a particular geographical area, it sends a request to the rules application entity 10 for subscription to a mechanism for reporting the presence of the terminal 4 within a presence reporting area corresponding to this geographical area. The control entity 20 thus requests to be notified by the rules application entity 10 of the changes in location of the terminal 4 when the latter enters or exits from this presence reporting area. Similarly, when the rules application entity 10 determines, depending on control rules obtained from the control entity 20, that it is necessary to open a session with the credit management entity 30, the latter is also able to subscribe to the presence reporting mechanism, in order to be notified by the rules application entity 10 of the changes in location of the terminal 4 when the latter enters or exits from this presence reporting area.

[0067] The request for subscription to the presence reporting mechanism is subsequently transmitted to an entity for managing mobility 40, called MME (for “Mobility Management Entity”). The mobility management entity 40 is responsible for the management of the mobility procedures within the communications network 5. It notably stores the request for subscription to the presence reporting mechanism and associates it with the communication session. Each time that the terminal 4 enters or exits from the presence reporting area associated with it, the mobility management entity 40 updates the location of the terminal 4 and updates the communication session. The rules application entity 10 is thus informed of the new location of the terminal 4 and, in turn, informs the entities of the communications network 5 having subscribed to the mechanism for reporting the presence of the terminal 4. The rules application entity 10 is thus able to relay the information reporting the presence of the terminal 4 to the control entity 20 or else to the credit management entity 30.

[0068] The communications between the various entities are provided by means of interfaces defined by the 3GPP standards group, notably the interface Gy between the rules application entity 10 and the credit management entity 30, and the interface Gx between the rules application entity 10 and the control entity 20.

[0069] The system 3 has been described in an EPC communications network; it may however readily be adapted to other network architectures. By way of example, in one embodiment where the communications network is a UMTS (for “Universal Mobile Telecommunications System”) network, the system is adapted by implementing the rules application entity 10 in a GGSN (for “Gateway GPRS Support Node”) interconnection gateway. Alternatively, the rules application entity 10 may also be implemented by a dedicated device.

[0070] FIG. 3a shows steps of a reporting management method according to a first particular embodiment.

[0071] In a similar manner as for the reporting management method of the prior art described in relation with FIG. 1, the reporting management method is implemented by a PCEF rules application entity 10, a PCRF rules control entity 20 and a credit management entity OCS 30. The method is implemented over two phases: an HC phase corresponding to a time slot referred to as “off-peak hours” during which no request for subscription to a mechanism for reporting the presence of the terminal is generated by the control entity 20, and an HP phase corresponding to a time slot referred to as “peak hours” during which the PCRF control entity 20 subscribes to the mechanism for reporting the presence of the terminal. By way of example, the HC phase corresponds to the time slot going from 23 h to 20 h, and the HP phase corresponds to the time slot going from 20 h to 23 h. These time slots are for example predefined by the operator of the communications network.

[0072] The first HC phase comprises the steps E1 to E8. The PCEF rules application entity 10, PCRF rules control entity 20 and credit management entity OCS 30 communicate with one another using for example the communications protocol Diameter.

[0073] During a step E1, a PCEF rules application entity 10 receives a request for establishing a communication session. The communication session is an IP CAN session between a terminal identified by an IPv4 or IPv6 address and a packet communications network identified by an APN identifier.

[0074] During a step E2, the PCEF rules application entity 10 sends a CCR-I (for “Credit Control Request-Initial”) message to a PCRF rules control entity 20 in order to obtain PCC control rules to be applied. The obtaining of the PCC control rules is initiated by the PCEF rules application entity 10 according to a mode known as “PULL”.

[0075] In a step E3, the PCRF rules control entity 20 verifies, when the communication session is established between the terminal and the packet communications network, that it is configured for triggering a subscription to a mechanism for reporting the presence of the terminal to the PCEF rules application entity 10. For this purpose, the PCRF rules control entity 20 verifies that at least one of the control rules that it supplies comprises a presence reporting area identifier associated with the communication session.

[0076] During a step E4, after having verified that it is configured for triggering a subscription to the mechanism for reporting the presence of the terminal, the PCRF control entity 20 sends to the PCEF rules application entity 10 a CCA-I reply message comprising the PCC control rules and an indicator PRASupported of support of the presence reporting mechanism. This indicator is more particularly designed to inhibit a subscription to the mechanism for reporting the presence of the terminal by the credit management entity 30. In the embodiment described in relation with FIG. 3a, this indicator has the value 1 which indicates that the control entity 20 supports the presence reporting mechanism and is able to subscribe to this mechanism.

[0077] During a step E5, the PCEF rules application entity 10 stores the control rules locally and applies them.

[0078] During a step E6, the PCEF rules application entity 10 sends a response for the attention of the terminal in order to indicate to it that the communication session IP CAN is established.

[0079] During a step E7, the PCEF rules application entity 10 determines by means of the rules obtained at the step E4 that a session with the credit management entity 30 is to be opened. The PCEF rules application entity 10 then sends a CCR-I message comprising the indicator PRASupported to the credit management entity OCS 30. The credit management entity OCS 30 receives the CCR-I message and determines that, although no mechanism for reporting the presence of the terminal has been activated owing to the absence of a presence reporting area identifier in the CCR-I message, the PCRF rules control entity 20 nevertheless supports the reporting mechanism for the terminal, and that a subscription to this mechanism is planned by the PCRF rules control entity 20.

[0080] During a step E8, the credit management entity 30 having determined that a subscription of the PCRF rules control entity 20 to the presence reporting mechanism is already planned, does not send any request for subscription to the mechanism for reporting the presence of the terminal. The credit management entity OCS 30 thus sends a CCA-I reply message indicating no presence reporting area identifier for the terminal. The subscription to the presence reporting mechanism by the PCRF rules control entity 20 is thus anticipated in order to avoid the presence reporting area conflict described previously in relation with FIG. 1. The reply message is, by way of example, sent at 19h55 just before the end of the off-peak hours HC phase.

[0081] When the peak hours HP phase begins at 20 hrs, the PCRF rules control entity 20 can once more subscribe to the mechanism for reporting the presence of the terminal. One of the rules obtained by the PCEF rules application entity 10, at the step E3, indicates to the latter entity to send a request to the PCRF rules control entity 20 in order to obtain an update of the control rules to be applied. For this purpose, during a step E9, the PCEF rules application entity 10 sends a CCR-I message to the PCRF control entity 20 in order to obtain the new PCC control rules to be applied.

[0082] In a step E3′, the PCRF rules control entity 20 repeats the step for verification that it is configured for triggering a subscription to a mechanism for reporting the presence of the terminal to the PCEF rules application entity 10.

[0083] During a step E10, subsequent to this verification, the PCRF rules control entity 20 responds to the rules application entity 10 by dispatching a CCA-I reply message. Since this reply is generated during the peak hours HP phase, a set of parameters of the PCRF control entity 20 (e.g. control rule applied locally by the PCRF control entity 20) indicates to the latter entity to subscribe to the subscription mechanism for reporting the presence of the terminal. For this purpose, the CCA-I message sent comprises the new PCC control rules to be applied during the HP phase, together with an identifier PRApcf-Id of the presence reporting area for the terminal for which the PCRF control entity 20 wishes to subscribe to the presence reporting mechanism. The reply message furthermore comprises the indicator PRASupported. The PCEF rules application entity 10 may then determine, on the one hand, that the PCRF rules control entity 20 supports the presence reporting mechanism and, on the other hand, that the PCRF entity 10 is requesting a subscription to this mechanism for the presence reporting area with identifier PRAperf-Id. The PCEF rules application entity 10 thus receives a unique presence reporting area identifier PRApcf-Id. The presence reporting area conflict for the terminal described in relation with FIG. 1 is thus avoided.

[0084] FIG. 3b describes an embodiment similar to that described in relation with FIG. 3a. The steps E1 to E3, E5, E6, and E9 to E10 are identical to those described previously in relation with FIG. 3a. In this embodiment, the PCRF rules control entity 20 may subscribe to the mechanism for reporting the presence of the terminal during the off-peak hours HC phase.

[0085] Following the verification step E3, where the PCRF rules control entity 20 verifies that it is configured for triggering a subscription to a mechanism for reporting the presence of the terminal to the PCEF rules application entity 10, the PCRF rules control entity 20 triggers a subscription to the mechanism for reporting the presence of the terminal within a presence reporting area of the communications network. For this purpose, during a step E4, it sends to the credit management entity OCS 30, in addition to the indicator PRASupported of support of the presence reporting mechanism, an identifier PRAperf-Id of the presence reporting area for which it wishes to subscribe to the mechanism for reporting the presence of the terminal.

[0086] In a step E7, when the indicator of support of the presence reporting mechanism PRASupported is transmitted to the credit management entity OCS 30, the identifier PRAperf-Id is also sent with the CCR-I message. The credit management entity OCS 30 is thus informed of the presence reporting area for which the PCRF control entity 20 has subscribed to the presence reporting mechanism.

[0087] In a step G1, the credit management entity OCS 30 verifies that the identifier PRAperf-Id is identical to an identifier PRAocs-Id of a second presence reporting area parameterized in the credit management entity OCS 30. The identifier PRAocs-Id identifies, more particularly, a second presence reporting area for which a subscription of the credit management entity OCS 30 to the mechanism for reporting the presence of the terminal is parameterized. Since the identifiers PRAperf-Id and PRAocs-Id are not identical, the subscription of the credit management entity OCS 30 to the mechanism for reporting the presence of the terminal is inhibited.

[0088] During a step E8, since the subscription of the credit management entity OCS 30 to the mechanism for reporting the presence of the terminal has been inhibited, the credit management entity OCS 30 sends a CCA-I reply message not comprising a presence reporting area identifier for the terminal.

[0089] When the peak hours HP phase begins at 20 hrs, the PCRF rules control entity 20 may thus subscribe to the mechanism for reporting the presence of the terminal without causing any presence reporting area conflict. The subscription is carried out such as previously described in relation with FIG. 3a.

[0090] This embodiment thus has the advantage for the credit management entity of being able to avoid a presence reporting area conflict while at the same time authorizing a subscription of the credit management entity OCS 30 to the presence reporting mechanism when the presence reporting area for which the subscription is requested is identical to that subscribed by the PCRF control entity 20.

[0091] FIG. 3c describes the case where the mechanism for reporting the presence of the terminal is not supported by the PCRF rules control entity 20, under identical scheduling conditions respectively corresponding to the HC and HP phases.

[0092] During the verification step E3, the PCRF rules control entity 20 does not determine any configuration relating to the triggering of a subscription to a mechanism for reporting the presence of the terminal to the PCEF rules application entity 10. Then, at the step E4, the PCRF rules control entity 20 sends an indicator PRASupported valued at 0, indicating that the mechanism for reporting the presence of the terminal is not supported by the PCRF rules control entity 20.

[0093] During the step E7, this indicator is relayed by the PCEF rules application entity 10 to the credit management entity OCS 30. The latter is thus explicitly informed of the absence of support of the mechanism for reporting the presence of the terminal by the PCRF rules control entity 20.

[0094] During the step E8, the credit management entity OCS 30 may then subscribe to the mechanism for reporting the presence of the terminal by dispatching to the PCEF rules application entity 10 a CCA-I message comprising an identifier PRAocs-Id of presence reporting area, defined locally to the credit management entity OCS 30. The credit management entity OCS 30 is thus free to subscribe to the presence reporting mechanism, the latter mechanism not being supported by the PCRF rules control entity 20.

[0095] The others steps of the method implemented during the peak hours HP phase are identical to the embodiments described previously except for the fact that the support indicator PRASupported is valued at 0 in order to indicate that the mechanism for reporting the presence of the terminal is not supported by the PCRF rules control entity 20.

[0096] FIG. 4 shows steps of a reporting management method according to a second particular embodiment. As previously, the reporting management method is implemented by a PCEF rules application entity 10, a PCRF rules control entity 20 and a credit management entity OCS 30.

[0097] During a step F1, a PCEF rules application entity 10 receives a request for establishing a communication session between a terminal identified by an IPv4 or IPv6 address and a packet communications network identified by an APN identifier.

[0098] During the steps F2 and F3, the PCEF rules application entity 10 negotiates with the PCRF control entity 20 functions supported by each of the two entities. During this negotiation happening during the establishment of a control session between the PCEF rules application entity 10 and the PCRF rules control entity 20, the PCEF rules application entity 10 and PCRF rules control entity 20 respectively exchange with each other the functions that they support in a CCR-I message and in a CCA-I message. The PCEF rules application entity 10 then verifies that at least one of the functions negotiated comprises a parameter indicating that the PCRF control entity 20 is configured for triggering a subscription to the presence reporting mechanism. The CCA-I message furthermore comprises PCC control rules supplied by the PCRF rules control entity 20 to the PCEF rules application entity 10.

[0099] During a step F4, the PCEF rules application entity 10 stores the PCC control rules locally and applies them.

[0100] During a step F5, the PCEF rules application entity 10 sends a response for the attention of the terminal in order to indicate to it that the communication session IP CAN is established.

[0101] During a step F6, the PCEF rules application entity 10 determines by means of the rules obtained at the step E4 that a session with the credit management entity OCS 30 is to be opened. The PCEF rules application entity 10 then sends a CCR-I message comprising an indicator PRASupported to the credit management entity OCS 30. The credit management entity OCS 30 receives the CCR-I message and determines that, although no mechanism for reporting the presence of the terminal has been activated owing to the absence of a presence reporting area identifier in the CCR-I message, the PCRF rules control entity 20 nevertheless supports the reporting mechanism for the terminal, and that a subscription to this mechanism is planned by the PCRF rules control entity 20.

[0102] During a step F7, the credit management entity OCS 30 sends a CCA-I reply message not comprising any presence reporting area identifier, the subscription to the mechanism for reporting the presence of the terminal by the credit management entity OCS 30 being inhibited.

[0103] FIG. 5 shows a control rules application entity 10 according to one particular embodiment. The control rules application entity 10 comprises:

[0104] a connection module 100, arranged for establishing a control session with a control entity 20 designed to implement a mechanism for reporting the presence of a terminal within a presence reporting area of a communications network;

[0105] a receiver module 110, arranged for receiving control rules from the control entity 20, a request for subscription to the presence reporting mechanism from the control entity 20, and an indicator of support by the control entity 20 of the presence reporting mechanism, designed to inhibit a subscription to this mechanism by a credit management entity;

[0106] a dispatching module 120, arranged for dispatching the support indicator to the credit management entity.

[0107] In another embodiment, the control rules application entity 10 furthermore comprises a functions negotiation module 130, activated when a control session is established with the control entity 20, arranged for negotiating functions supported by the control rules application entity 10 and control entity 20, at least one of the functions comprising a parameter indicating that the control entity 20 is configured for triggering a subscription to the presence reporting mechanism.

[0108] FIG. 6 shows a control entity 20 according to one particular embodiment. The control entity 20 is designed to implement a mechanism for reporting the presence of a terminal within a presence reporting area of a communications network. It comprises:

[0109] a connection module 200, arranged for establishing a control session with a control rules application entity 10;

[0110] a supply module 210, arranged for supplying control rules to the control rules application entity 10;

[0111] a verification module 220, arranged for verifying, during a phase for establishing a communication session between the terminal and a packet communications network, that the control entity 20 is configured for triggering a subscription to the mechanism for reporting the presence of the terminal to the control rules application entity 10;

[0112] a dispatching module 230, activated when the control entity 20 is configured for triggering a subscription to the mechanism for reporting the presence of the terminal, and arranged for dispatching to a credit management entity 30 an indicator of support of the presence reporting mechanism by the control entity 20, designed to inhibit a subscription of the credit management entity 30 to said mechanism.

[0113] In another embodiment, the control entity 30 furthermore comprises a functions negotiation module 240, activated when a control session is established with the control rules application entity 10, arranged for negotiating functions supported by the control entity 20 and control rules application entity 10, the verification module 220 being furthermore arranged for verifying, when the control session is established, that at least one of the functions comprises a parameter indicating that said control entity 20 is configured for triggering a subscription to the presence reporting mechanism.

[0114] The invention is implemented by means of software and/or hardware components. In this respect, the term “module” may correspond in this document either to a software component or to a hardware component or to an assembly of hardware and/or software components, designed to implement a function or a set of functions, according to what has been previously described for the module in question.

[0115] A software component corresponds to one or more computer programs, one or more sub-programs of a program or, more generally speaking, to any element of a program or of a software application. Such a software component is stored in a memory then loaded and executed by a data processor of a physical entity and is capable of accessing the hardware resources of this physical entity (memories, recording media, communications buses, input/output electronic modules, user interfaces, etc.).

[0116] In the same way, a hardware component corresponds to any element of a hardware assembly. This may be a hardware component, programmable or otherwise, with or without integrated processor for the execution of software. This is for example an integrated circuit, a smart card, an electronic module for the execution of firmware, etc.

In one particular embodiment, the modules 100, 110, 120, and 130 are arranged for implementing the method for managing the reporting of the presence of a terminal previously described. These are preferably software modules comprising software instructions for executing the steps of the method for managing the reporting of the presence of a terminal previously described, implemented by a control rules application entity.

[0117] The invention therefore also relates to: [0118] a program for a control rules application entity, comprising program code instructions designed to control the execution of the steps of the method for managing the reporting of the presence of a terminal previously described, when said program is executed by said control rules application entity; [0119] a recording medium readable by a control rules application entity on which the program for a control rules application entity is recorded.

[0120] Similarly, the modules 200, 210, 220, 230 and 240 are arranged for implementing the method for managing the reporting of the presence of a terminal previously described. These are preferably software modules comprising software instructions for executing the steps of the method for managing the reporting of the presence of a terminal previously described, implemented by a control entity. The invention therefore also relates to: [0121] a program for a control entity, comprising program code instructions designed to control the execution of the steps of the method for managing the reporting of the presence of a terminal previously described, when said program is executed by said control entity; [0122] a recording medium readable by a control entity on which the program for a control entity is recorded.

[0123] The software modules may be stored in or transmitted by a data medium. The latter may be a hardware storage medium, for example a CD-ROM, a magnetic diskette or a hard disk, or else a dispatching medium such as an electrical, optical or radio signal, or a telecommunications network.