Congestion Control in a Telecommunications Network

FIELD OF THE INVENTION

0001Generally, the invention relates to a method and tele-communications network configured for controlling congestion in a network. More specifically, the invention relates to congestion control in a network used for machine-to-machine communications.

BACKGROUND OF THE INVENTION

0002Telecommunications networks that provide wireless access (e.g. GSM, UMTS, WiMax, LTE) have developed tremendously over the past years. In such networks, voice and data services can be provided to terminals having a high mobility, i.e. the communication terminals are not bound to a particular location and are freely movable through the area covered by the network. A gateway node of the telecommunications network enables connection to a further network, for example a network based on IP such as the internet.

0003The availability of such a telecommunications network connected to the further network has resulted in demands for further services, including services that relate to so-called machine-to-machine (M2M) services. M2M applications typically involve hundreds, thousands or millions of communication modules which each act as a communication terminal to the telecommunication network. An example involves the electronic reading of e.g. ‘smart’ electricity meters at the homes of a large customer base over the telecommunications network from a server connected to the further network. Other examples include sensors, meters, vending or coffee machines etc. that can be equipped with communication modules that allow reporting status information to a data processing centre over the telecommunications network. Such devices may also be monitored by the server. The data processing centre may e.g. store the data and/or provide a schedule for maintenance people to repair or refill a machine, meter, sensor etc.

0004A characteristic of some of the M2M applications is that the exchange of data with the server is infrequent, for example once every day or so for a smart electricity meter.

0005Typically, there exists an agreement between the operator of the telecommunications network and the owner/operator of the server or data processing centre about the communication parameters applicable for bearers of each of the communication terminals. As an example, such communication parameters e.g. relate to the QoS class and to the maximum bit rate that is allowed for a bearer in the telecommunications network used for supporting a data session between a particular communication terminal and the server or data processing centre. As an example, in GPRS or UMTS telecommunications networks the communication parameters are comprised in a PDP Context for the communication terminal. In other networks, e.g. LTE networks or cable networks, the communication parameters are provided in similar contexts.

0006It is generally known that communication parameters can be controlled using policy and charging control (PCC) architectures. An example of such a PCC architecture is described in 3GPP TS 23.203. Policy control is a known process in communication networks, whereby a policy control entity indicates to a policy enforcement entity e.g. how to control bearer resources of e.g. an IP Connectivity Access Network (IP-CAN) bearer. Such IP-CAN bearers may include bearers in GPRS or UMTS communication networks, EPS bearers in LTE communication networks, DOCSIS service flows in cable communication networks etc. Policy control may be used for controlling QoS characteristics in a telecommunications network.

0007Even though the traffic generated by each of the communication terminals is within the agreed limits as specified in the communication parameters (e.g. PDP Context) for a bearer, and even though such limits are strictly enforced in case a terminal would, intentionally or unintentionally, violate a limit, congestion may occur. For example, when a large number of electricity meters, each infrequently exchanging data with the server, attempt to exchange data with the server at a same moment, the connection between the telecommunication network and the server in the further network may be overloaded or congestion may occur in other parts of the telecommunications network. Overload may occur in either or both the uplink and downlink direction, i.e. data transmitted from the terminals towards the server or transmitted from the server towards the communication terminals, respectively.

0008Currently, the operator of the telecommunications network has no means to efficiently prevent such overload and has no suitable means to control congestion when it occurs.

0009U.S. Pat. No. 6,865,185 discloses a method and system for queuing traffic in a wireless network includes receiving a stream of packets for transmission in the wireless network. Each packet includes a flow identifier and is assigned to one of the plurality of virtual groups based on the flow identifier. The virtual groups include discrete transmission resources. Each packet is queued in an assigned virtual group for transmission in the wireless network.

0010Clearly, there exists a need in the art for more flexible congestion control methods.

SUMMARY OF THE INVENTION

0011A method for congestion control in a telecommunications network is disclosed. The telecommunications network supports one or more active data sessions between a server and at least a first and second communication terminal by providing at least a first and a second bearer for these terminals.

0012The at least first and second communication terminal are assigned to a group for which a common group identifier is or has been stored. Further, a first individual congestion parameter for the first bearer and a second individual congestion parameter for the second bearer of the first and second communication terminal are or have been stored. A group load indicator is defined for the group of terminals corresponding to the common group identifier. The group load indicator is monitored and compared with a group load condition for the group of the at least first and second communication terminals corresponding to the common group identifier. Congestion is controlled by adjusting at least one of the first individual congestion parameter of the first bearer and the second individual congestion parameter of the second bearer when said group load indicator satisfies the group load condition.

0013The method can be used in one or more (gateway) node(s) of the telecommunications network.

0014A computer program for performing the method and a carrier containing such a computer program are also disclosed. Portions of the program may be distributed through the telecommunications network to perform distributed functions.

0015Furthermore, a telecommunications network is disclosed that is configured for enabling data sessions between a server and at least a first and a second communication terminal by providing at least a first and a second bearer. A first storage node of the telecommunications network stores a common group identifier assigned to a group comprising the at least first and second communication terminal. A second storage node, possibly being the same node as the first storage node, stores a first individual congestion parameter for the first bearer and a second congestion parameter for the second bearer for the first and second communication terminals, respectively. A monitoring module is provided that is configured for monitoring in the telecommunications network a group load indicator for the group of the at least first and second communication terminal corresponding to the common group identifier. Also, an analyser is provided that is configured for comparing the group load indicator with a group load condition for the group of the at least first and second communication terminal corresponding to the common group identifier. Finally, the telecommunications network comprises a congestion controller configured for controlling congestion by adjusting at least one of the first individual congestion parameter of the first bearer and the second individual congestion parameter of the second bearer when said group load indicator satisfies the group load condition.

0016It should be appreciated that the disclosed method and telecommunications network may control congestion occurring in the telecommunications network itself and/or in the further network(s) provided between the telecommunications network and the server.

0017It should also be appreciated that the monitoring step for monitoring the group load indicator and the comparing step for comparing the monitored group load indicator with the group load condition are not necessarily two individual subsequent steps, but may e.g. be integrated in a single step.

0018Also, usually a communication terminal uses a single bearer in the telecommunications network for supporting one or more data sessions between the communication terminal and the server. The common group identifier may then relate to the communication terminal, which corresponds one-to-one with the bearer. However, in a case where communication terminals use more than one bearer, group identifiers may be assigned on a per-bearer basis, such that a single communication terminal can be assigned to several groups.

0019The individual congestion parameters of the bearers of the terminals of the group are congestion-related communication parameters of the contexts (e.g. PDP Contexts) of individual terminals of the group. An example of such a congestion parameter comprises a (maximum) bit rate that is agreed for the bearer. The group load indicator relates to the actually measured load at a particular point in time or during a time interval for the group of terminals. As an example, the group load indicator is a measure of the actual bit rate used by the terminals, which bit rate is monitored in the telecommunications network. The group load condition is a condition that, when satisfies, triggers the adjustment of congestion parameters of the individual bearers of the terminals of the group. As an example, the group load condition comprises a bit rate threshold for the group. When the monitored actual bit rate of the terminals exceed the group bit rate threshold, the agreed congestion parameters for the bearers of (at least one or some of) the individual terminals are adjusted. The adjusted congestion parameters are then enforced and congestion is avoided or reduced.

0020The detection that the group load condition is satisfied does not necessarily mean that actual congestion has occurred. The group load condition may be defined such that the adjustment of the individual congestion parameters is triggered before a congestion state would occur. As an example, selecting a lower threshold value as a group load condition may prevent congestion rather than only to resolve it with a higher threshold value.

0021Actions to resolve congestion may comprise other actions than downwardly adjusting the individual maximum bit rates for the individual terminals, including the modifying of QoS attributes of one or more of the terminals. As an alternative, additional capacity can be (temporarily) assigned to the terminals of the group.

0022The disclosed method and telecommunications network allow, in addition to defining (values of) congestion related parameters for individual communication terminals, to define a group load condition for the communication terminals belonging to the group identified by the common group identifier. By monitoring the group load indicator of the group of terminals, the group load condition allows the operator of the telecommunications network, to anticipate congestion by comparing the group load indicator with the group load condition and to act by adjusting the individual congestion parameters of the terminals in the group and enforce these in order to avoid or to relieve congestion caused by terminals of the group.

0023As an example, the operator of the telecommunications network may define a group bit rate threshold for a group of communication terminals. When the group bit rate exceeds the group bit rate threshold, the operator of the telecommunications network is able to decrease the agreed bit rates of individual communication terminals in order to relieve the congestion in the telecommunications network.

0024The embodiment of claim <b>2</b> allows congestion control for terminals requesting access to the telecommunications network. A terminal requesting access to the telecommunications network and been assigned to a defined group for which a congestion condition is satisfied will be faced with an adjusted individual congestion parameter for his established bearer in order to avoid or limit congestion that could occur by granting the new terminal access to the network with an unadjusted parameter value.

0025The embodiment of claim <b>3</b> provides the advantage of timing the adjustment of the individual congestion parameters on the basis of the most recent data exchange time.

0026The embodiment of claim <b>4</b> enables retrieval of the common group identifier to which a particular terminal belongs on the basis of individual identifiers of this terminal. As such, the common group identifier remains unknown to the terminal. Examples of individual terminal identifiers include IMSI, a terminal number, an application number etc.

0027The embodiment of claim <b>5</b> defines that bit rate is an important parameter for congestion control.

0028The embodiment of claim <b>6</b> provides flexibility for the owner/operator of the M2M server by enabling assigning of communication terminals to one or more groups and (temporarily) adjusting individual congestion parameters of one or more communication terminals within a group. The owner/operator of the server may flexibly adjust the (value of the) congestion parameters of one or more individual terminals within the group as long as the group congestion condition for aggregated communication terminals is not met.

0029The embodiment of claim <b>7</b> allows assigning of a single communication terminal to multiple groups and to apply different corresponding group load conditions to these groups.

0030The embodiment of claim <b>8</b> allows for a gradual adjustment (e.g. stepwise) of the congestion threshold parameters of individual communication terminals of a particular group.

0031The terminals for which the congestion parameters will be or have been adjusted, should advantageously be informed (e.g. via a signaling message) of an adjustment of the bearer characteristics, e.g. to reduce the maximum bit rate to the data transmission in the uplink direction, as defined in the embodiment of claim <b>9</b>. The terminals of the group for which the congestion parameters are not adjusted need not be informed.

0032When such adjustment information is to be communicated to a considerable number of communication terminals, this may result in considerable signaling traffic in the network. The embodiments of claims <b>10</b> and <b>13</b> make use of the common group identifier. From the common group identifier, the individual communication terminals of the group for which the message is intended can be derived at a suitable place (lower) in the telecommunications infrastructure.

0033The embodiment of claim <b>11</b>, further reducing signaling traffic in the telecommunications network, defines that the information comprising the common group identifier is broadcast in one or more parts of the telecommunications network and is received by the communication terminals belonging to the group. In this embodiment, the communication terminals possess or have been informed of the common group identifier and use this information to retrieve the adjustment information message from the broadcast.

0034Hereinafter, embodiments of the invention will be described in further detail. It should be appreciated, however, that these embodiments may not be construed as limiting the scope of protection for the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

0035In the drawings:

0036<figref idref="DRAWINGS">FIG. 1</figref> is a schematic illustration of a prior art telecommunications network connecting communication terminals to a server over a further network;

0037<figref idref="DRAWINGS">FIG. 2</figref> is a schematic illustration of a prior art policy and charging control (PCC) architecture to be used in the telecommunications network of <figref idref="DRAWINGS">FIG. 1</figref>;

0038<figref idref="DRAWINGS">FIGS. 3A and 3B</figref> depict an individual subscription record and a group record according to an embodiment of the invention;

0039<figref idref="DRAWINGS">FIG. 4</figref> is a schematic illustration of a telecommunication network according to an embodiment of the invention;

0040<figref idref="DRAWINGS">FIGS. 5A and 5B</figref> depict an individual PCC rule and a group rule according to an embodiment of the invention to be used in a congestion control method performed in the telecommunications network of <figref idref="DRAWINGS">FIG. 4</figref> in combination with the records of <figref idref="DRAWINGS">FIGS. 3A and 3B</figref>;

0041<figref idref="DRAWINGS">FIGS. 6A and 6B</figref> depict signal flow charts showing embodiment of provisioning of a telecommunications node by the server;

0042<figref idref="DRAWINGS">FIGS. 7A-7C</figref> depict schematic diagrams illustrating bit rate usage together with bit rate usage limits and a signal flow chart illustrating a method for congestion control according to an embodiment of the invention;

0043<figref idref="DRAWINGS">FIG. 8</figref> depicts a signal flow chart showing an embodiment of a GGSN-initiated group PDP context modification procedure;

0044<figref idref="DRAWINGS">FIG. 9</figref> depicts a schematic illustration of a telecommunications network including a cell broadcast centre; and

0045<figref idref="DRAWINGS">FIG. 10</figref> depicts a signal flow chart showing an embodiment of a GGSN-initiated group PDP context modification procedure using cell broadcast technology.

DETAILED DESCRIPTION OF THE DRAWINGS

0046<figref idref="DRAWINGS">FIG. 1</figref> shows a schematic illustration of a telecommunications network <b>1</b>. The telecommunications network <b>1</b> allows data sessions between a server <b>2</b> and a terminal <b>3</b> over a packet data network <b>4</b>, wherein access of the terminal to the telecommunications network <b>1</b> is wireless.

0047In the telecommunications network of <figref idref="DRAWINGS">FIG. 1</figref>, three generations of telecommunications networks are schematically depicted together for purposes of brevity. A more detailed description of the architecture and overview can be found in 3GPP TS 23.002 which is included in the present application by reference in its entirety.

0048The lower branch of <figref idref="DRAWINGS">FIG. 1</figref> represents a GPRS or UMTS telecommunications network comprising a Gateway GPRS Support Node (GGSN), a Serving GPRS Support Node (SGSN) and a Radio Access Network (RAN or UTRAN). For a GSM/EDGE radio access network (GERAN), the RAN comprises a Base Station Controller (BSC) connected to a plurality of Base Station Transceivers (BTSs), both not shown. For a UMTS radio access network (UTRAN), the RAN comprises a Radio Network Controller (RNC) connected to a plurality of NodeBs), also not shown. The GGSN and the SGSN are conventionally connected to a Home Location Register (HLR) that contains subscription information of the terminals <b>3</b>.

0049The upper branch in <figref idref="DRAWINGS">FIG. 1</figref> represents a next generation telecommunications network, commonly indicated as Long Term Evolution (LTE) or Evolved Packet System (EPS). Such a network comprises a PDN Gateway (P-GW) and a Serving Gateway (S-GW). The E-UTRAN of the EPS comprises evolved NodeBs (eNodeBs or eNBs) providing wireless access for a terminal <b>3</b> that is connected to the S-GW via a packet network. The S-GW is connected to a Home Subscriber Server HSS and a Mobility Management Entity MME for signaling purposes. The HSS includes a subscription profile repository SPR.

0050Further information of the general architecture of a EPS network can be found in 3GPP TS 23.401.

0051Of course, architectures other than defined by 3GGP, e.g. WiMAx or cable networks, can also be used within the context of the present invention.

0052Whereas the invention as defined in the appended claims is generally applicable to such networks, a more detailed description will be provided below for a GPRS/UMTS network.

0053For such a network, the SGSN typically controls the connection between the telecommunications network <b>1</b> and the terminal <b>3</b>. It should be appreciated that the telecommunications network <b>1</b> generally comprises a plurality of SGSNs, wherein each of the SGSNs is connected typically to several BSCs/RNCs to provide a packet service for terminals <b>3</b> via several base stations/NodeBs.

0054The GGSN is connected to the packet data network <b>4</b>, e.g. the internet, a corporate network or a network of another operator. On the other side, the GGSN is connected to one or more SGSNs.

0055The GGSN is configured for receiving a data unit for the terminal <b>3</b> from the server <b>2</b> over the network <b>4</b> (downlink) and for transmitting a data unit to the server <b>2</b> received from the terminal <b>3</b> (uplink).

0056In an M2M environment, a single server <b>2</b> normally is used for communication with a large number of terminals <b>3</b>. Individual terminals <b>3</b> can be identified by individual identifiers, such as an IP address, an IMSI or another terminal identifier.

0057<figref idref="DRAWINGS">FIG. 2</figref> shows a policy and charging control (PCC) architecture, known from 3GGP TS 23.203 which is included in the present application by reference in its entirety, that can be included in a GPRS, UMTS, LTE or other type of telecommunication network <b>1</b>.

0058The central element in the PCC architecture of <figref idref="DRAWINGS">FIG. 2</figref> is the policy and charging rules function PCRF. The PCRF takes policy decisions related to quality of service (QoS) and charging treatment of service data sessions in an IP Connectivity Access Network (IP-CAN). An IP-CAN is a network capable of supporting IP-CAN bearers over which data sessions may be defined. IP-CAN bearers are IP transmission paths defined by e.g. capacity, delay, bit error rate.

0059In its decisions, the PCRF takes into account subscription information received from the SPR over the Sp interface and information on the capabilities of the IP-CAN. The PCRF formats its policy decisions in so-called PCC rules. PCC rules are sets of information enabling the detection of a service data flow and providing parameters for policy control and/or charging control. Such a PCC rule contains among others information to detect a service data flow (e.g. the 5-tuple source/destination IP address, source/destination port number, protocol) and information on the required QoS and charging treatment for the service data flow. It also includes a maximum bit rate authorized for the service data flow, separately for uplink and downlink. PCC rules may be predefined or dynamically provisioned at establishment and may then be re-defined during the lifetime of an IP-CAN session.

0060The PCRF communicates its decisions, formatted as so-called PCC rules, towards the Policy and Charging Enforcement Function (PCEF) over the Gx interface. Furthermore, the PCRF informs the PCEF on network events at whose occurrence it wants to be notified.

0061The PCEF encompasses service flow detection, policy enforcement and flow based charging functionalities. These functions are performed according to PCC rules either received from the PCRF (dynamic PCC rules) or predefined in the PCEF itself (predefined PCC rules). Furthermore the PCEF informs the PCRF over the Gx interface on network events requiring notification towards the PCRF. The PCEF is located in a Gateway Node (e.g. the GGSN or the P-GW in <figref idref="DRAWINGS">FIG. 1</figref>), that connects the IP-CAN to the external Packet Data Network <b>4</b>. The network <b>4</b>, connected to the server <b>2</b>, can be any network or combination of networks to support the communication between the gateway of telecommunications network <b>1</b> and the server <b>2</b>, for example a dedicated line (copper or fibre-optic cable connecting the gateway to the server <b>2</b>), a backbone IP network, etc.

0062The SPR contains all subscription information needed for making subscription-based policy decisions by the PCRF for individual communication terminals <b>3</b> based on an individual subscriber identifier, such as IMSI. The subscription information is requested by the PCRF over the Sp interface. The SPR may also notify the PCRF when the subscription information has been changed. The SPR does not necessarily result in a duplication of subscription information in the network. The SPR may for instance contain the HSS or HLR.

0063As shown in <figref idref="DRAWINGS">FIG. 1</figref>, a group G of terminals <b>3</b> can be connected or connectable to the telecommunications network <b>1</b> in order to have a data session with the server <b>2</b> over the telecommunications network and the packet network <b>4</b>. In order to identify such a group of terminals <b>3</b>, in an aspect of the present invention, the HLR and/or SPR may store a common group identifier in relation with a group record in addition to individual subscription records containing the above-mentioned subscription information for individual terminals <b>3</b>.

0064<figref idref="DRAWINGS">FIGS. 3A and 3B</figref> illustrate an individual subscription record and a group record. The individual subscription record contains subscription information for each terminal <b>3</b> individually. The individual subscription record contains for example the individual subscription identifier, the individual QoS and charging policies, which may include a maximum bit rate for the uplink and downlink direction (possibly different for uplink and downlink), a guaranteed bit rate for the uplink and the downlink, other congestion control related information and/or other subscription information.

0065The group record contains for example the group identifier, information related to the entire group, such as the group load condition, the congestion parameter adjustment policies and a list of identifiers of communication terminals or bearers which belong to the group. The individual subscription records for communication terminals <b>3</b> in a group G and the group record are linked via the group identifier and the individual subscription identifiers, i.e. the group record for group G has a common group identifier and a list of identifiers of communication terminals <b>3</b> or bearers which belong to the group G. An individual subscription record for a communication terminal in group G may contain also a group identifier of the group G to which the terminal <b>3</b> is assigned. The inclusion of the group identifier in the individual subscription records may be advantageous in cases wherein the communication terminals require information on the group G to which they are assigned. An example thereof is provided below, where the common group identifier is included in a broadcast signal. Communication terminals <b>3</b> requiring information regarding the group to which they are assigned are then able to retrieve (select) the information from the broadcast signal that is relevant for the group.

0066It should be appreciated that a single communication terminal <b>3</b> can be assigned to more than one group.

0067There are no particular requirements to the formation of groups. Groups may e.g. (partially) overlap or be disjunct in their group members. Also a hierarchical structure may be used, wherein subgroups within a group G are created (e.g. all terminals served from a specific SGSN/S-GW). Neither is it required that all terminals are included in a group. In the context of congestion control, the formation of groups is expected to be guided by an assessment where congestion may be expected to occur.

0068The provision of a group record for a group of communication terminals <b>3</b> enables various new and inventive methods in the telecommunications network <b>1</b>. Examples include efficient message transmission to the group of communication terminals <b>3</b>, access control for the group of communication terminals <b>3</b> and flexibility regarding congestion control.

0069The combination of these examples will now be described in further detail.

0070<figref idref="DRAWINGS">FIG. 4</figref> shows a telecommunications network <b>1</b> comprising a PCC* architecture modified with respect to the PCC architecture of <figref idref="DRAWINGS">FIG. 2</figref> as will be described below in further detail. A first and second communication terminal <b>3</b>A, <b>3</b>B, belonging to a group G communicate with a server <b>2</b> (e.g. for smart electricity metering in the home to provide the server <b>2</b> with metering data).

0071IP-CAN bearers A<b>1</b> and B<b>1</b> (in this case defined by PDP Contexts) are established between terminals <b>3</b>A, <b>3</b>B and the gateway (here the GGSN) of the telecommunications network. Data transported via such an IP-CAN bearer receives the QoS treatment associated with the IP-CAN bearer. The data sessions A<b>2</b>, B<b>2</b> between the terminals <b>3</b>A, <b>3</b>B and the server <b>2</b> are supported by the IP-CAN bearers A<b>1</b>, B<b>1</b> in the telecommunications network and further supported via network <b>4</b>.

0072To ensure that the bearers A<b>1</b> and B<b>1</b> get the appropriate QoS characteristics, at bearer establishment the PCEF* consults the PCRF* via interface Gx*. The PCRF* in its turn consults the SPR* via interface Sp* on relevant subscription information. The PCRF* takes a policy decision and informs the PCEF* via interface Gx*. The PCEF* enforces these decisions.

0073As mentioned above, the group information for terminals <b>3</b>A, <b>3</b>B according to an aspect of the invention can be used to advantage for more efficient congestion control by the telecommunications network <b>1</b>.

0074In an aspect of the invention, the provisioning interfaces Px and/or Py are defined allowing communication between the server <b>2</b> and the SPR* and/or the PCRF* as will be described further below with reference to <figref idref="DRAWINGS">FIGS. 6A and 6B</figref>.

0075A group record, as illustrated in <figref idref="DRAWINGS">FIG. 3B</figref>, applies to multiple communication terminals <b>3</b>A, <b>3</b>B that have a data session A<b>2</b>-B<b>2</b> with the server <b>2</b> supported by bearers A<b>1</b>-B<b>1</b>, respectively. Group records are contained in the SPR*. The group information in the group record contains, for example, a bit rate threshold value that relates to the aggregate bit rate over all bearers A<b>1</b>, B<b>1</b> of the terminals <b>3</b>A, <b>3</b>B in the group G. The sum of the maximum bit rate values of all individual subscriptions of the terminals <b>3</b>A, <b>3</b>B or of all bearers A<b>1</b>, B<b>1</b> of the terminals <b>3</b>A, <b>3</b>B in the group G may be greater than the bit rate threshold value specified for the group G to profit from the statistical effect that it is highly unlikely that all communication terminals <b>3</b> in the group G will simultaneously exchange data with server <b>2</b> at the maximum bit rate specified in the individual subscription records.

0076The group record, as illustrated in <figref idref="DRAWINGS">FIG. 3B</figref>, may contain a group identifier, an identification of individual subscription IDs (e.g. IMSIs) of the terminals or bearers in the group and information related to the group such as the above-mentioned aggregate bit rate threshold for the group G.

0077The group record may also result in adding an identification of the group identification in the individual subscriptions that fall within the group. An individual subscription can be contained in multiple group subscriptions.

0078The policy decisions taken by PCRF* per individual communication terminal <b>3</b>A, <b>3</b>B are communicated via interface Gx* to a PCEF*. PCEF* enforces these decisions.

0079When a group load condition is satisfied, for example when the above-mentioned aggregate bit rate threshold specified in the group information for the group G is exceeded, the PCRF* is notified by the PCEF* and the PCRF* adjusts the individual policy decisions resulting in the modification of at least one of the bearers of the active terminals <b>3</b>A, <b>3</b>B in the group G. The PCRF* provides the PCEF* via interface Gx* with adjusted individual policy decisions. This may e.g. result in a downscaling of the maximum bit rate specified for bearers A<b>1</b> and/or B<b>1</b> and a decrease of the user data bit rate that is exchanged in the data sessions A<b>2</b> and/or B<b>2</b> between terminals <b>3</b>A, <b>3</b>B and the server <b>2</b>.

0080It should be noted that the detection of satisfying a group load condition and reporting the event to PCRF* may also be performed by other entities than the PCEF*, including entities at locations different from the PCEF* location (e.g. in SGSN/S-GW or at the interface connecting a GGSN/P-GW to SGSN/S-GW), as will be described further with reference to <figref idref="DRAWINGS">FIG. 8</figref>.

0081In addition to the PCEF* just notifying the PCRF* about a congestion load condition being satisfied, it may include additional information with the congestion load condition fulfilled notification. The PCRF* may also request the PCEF* to monitor and report additional information. An example of additional information which may be monitored and reported by the PCEF* is a list of identifiers identifying one or more of the bearers (or data sessions or terminals) over which in the recent past data has been exchanged. The additional data may aid the PCRF* in making adjustments to its policy decisions and also to prioritise the bearers (or data sessions or terminals) to which the adjusted PCC rules should apply first, thus aiming at a more direct effect on resolving the congestion.

0082<figref idref="DRAWINGS">FIGS. 5A and 5B</figref> illustrate examples of an individual PCC rule and a group rule. Though the group rule differs from a common PCC rule, both are referred to as PCC rule in this description. The PCEF* receives those PCC rules from the PCRF* to enforce or implement them. As illustrated, the individual PCC rules contain information identifying the individual PCC rule, information used by the PCEF* to detect the related IP flow and information on the required QoS and Charging treatment, including for example the enforcement of a maximum bit rate for downlink and uplink, a guaranteed bit rate for downlink and uplink, an IP DiffServ DSCP marking and other congestion related information.

0083A group rule (<figref idref="DRAWINGS">FIG. 5B</figref>) similarly contains information identifying the group rule, information used by the PCEF* to detect the IP flow for the group (which may be aggregated from the individual flow detection information specified in the individual PCC rules for the bearers in the group) and in particular the group load condition.

0084In an alternative embodiment (indicated by the dashed line in <figref idref="DRAWINGS">FIG. 5B</figref>, a group rule may contain the PCC rule IDs for the terminals/bearers in the group, which information may serve to specify the flow detection for the terminals/bearers in the group.

0085As already mentioned in the summary of the invention, the disclosed method and system provide flexibility for the owner/operator of the server <b>2</b>. Interaction between the server <b>2</b> and the SPR* over the Px provisioning interface, as illustrated in <figref idref="DRAWINGS">FIG. 6A</figref>, may e.g. result in the creation of a group record, the adaptation of this record, the adjustment of congestion threshold parameters for the individual terminals <b>3</b>, the adjustment of other information in the group record, such as how to adjust the active bearers in the group once a group load condition is satisfied (see group record of <figref idref="DRAWINGS">FIG. 3B</figref>), etc. As illustrated in <figref idref="DRAWINGS">FIG. 6B</figref>, the PCRF* may also interact with the server <b>2</b> via a policy input request to retrieve information via a policy input provisioning message on how to adjust the active bearers in the group. Alternatively, the server may push this information to the PCRF*. The information may, of course, also be retrieved from the SPR* over the interface Sp*. Further, using e.g. the Px interface, further information on subgroups within a group and/or information regarding how (e.g. to which level(s)) and/or in which sequence to adjust the individual congestion related parameters can be contained in the group record and/or the individual subscription record.

0086<figref idref="DRAWINGS">FIGS. 7A and 7B</figref> provide a first example of a method of controlling congestion in the telecommunications network <b>1</b> using the PCC* architecture of <figref idref="DRAWINGS">FIG. 4</figref>.

0087<figref idref="DRAWINGS">FIG. 7A</figref> shows an example of the usage of active terminals <b>3</b>A-<b>3</b>D that triggers an interaction from the PCEF* with the PCRF*. Terminals <b>3</b>A-<b>3</b>D have been assigned a common group identifier and thus belong to the same group G. The individual congestion parameters, here the subscribed maximum bit rate MBR, is 40 for terminals <b>3</b>A, <b>3</b>B and <b>20</b> for terminals <b>3</b>C and <b>3</b>D. All terminals <b>3</b>A-<b>3</b>D have bearers established enabling active data sessions in the GPRS network <b>1</b> of <figref idref="DRAWINGS">FIG. 1</figref>. The group load condition GLC<b>1</b> is defined as that congestion should be notified when the aggregate bit rate monitored for the group exceeds a value of 80. The PCEF* has accordingly been instructed by the PCRF* and monitors a group load indicator, e.g. the aggregate bit rate for the group G. As an example, assume that the actually used bit rate of terminals <b>3</b>A, <b>3</b>B is only 30, terminal <b>3</b>C only 10 and terminal <b>3</b>D only 5, as indicated by the hatched bars. Then, PCEF* may monitor a group load indicator with a value of 75, which does not satisfy the group load condition. In an alternative implementation, PCEF* may detect the group load condition in a more direct way, without explicitly determining a value for the aggregate bit rate for the group, e.g. by comparing the aggregate bit rate for the group with a reference rate such as in a token bucket or similar set to a bit rate of 80. In yet an alternative implementation, PCEF* may monitor the bit rate for each communication terminal <b>3</b> separately, for example as part of existing PCC rules, and sum the values related to each of the terminals in the group G to yield a group load indicator for group G.

0088When the PCEF* monitors that the group load congestion GLC<b>1</b> is satisfied (resulting e.g. from an increase in the bit rate of terminal <b>3</b>D from 5 to 20 (illustrated in <figref idref="DRAWINGS">FIG. 7A</figref> by an upwardly pointing arrow for terminal <b>3</b>D), the fulfillment of the group load condition GLC<b>1</b> triggers the PCEF* to notify this condition to the PCRF*. The PCEF* may, optionally, provide additional information regarding the severity of the situation, allowing the PCRF* to take this into account.

0089The PCRF* adjusts the individual PCC rule for at least one of the communication terminals in group G. An adjustment may relate, for example, to downscaling the maximum bit rate. In <figref idref="DRAWINGS">FIG. 7A</figref> the values for the maximum bit rate (MBR) of the communication terminals <b>3</b>A-<b>3</b>D are illustrated as MBR_A- MBR_D. In this example, the PCRF* decides to downscale the maximum bit rate parameter for communication terminals <b>3</b>A and <b>3</b>B, i.e. the value of MBR_Aand MBR_B, from 40 to 20. The PCEF*, after receiving updated PCC rule(s) from the PCRF*, adjusts the individual congestion parameters of the MBR_A- MBR_Dof the bearers (in this example, only MBR_Aand MBR_Bneed to be adjusted) as shown by the downwardly pointing arrows for MBR_Aand MBR_B. The related terminals <b>3</b>A and <b>3</b>B will reduce their bit rate to 20 or less. In case a terminal would fail to comply to the adjusted data session communication parameter, such as MBR, this will be enforced by PCEF* in the usual way. In this example, the individual congestion parameters (MBR) are now all set to a value 20. The telecommunications network <b>1</b> will now not deliver a bit rate of more than 80 and group load condition GLC<b>1</b> is no longer satisfied.

0090A downward adjustment of an individual congestion parameter value may, for example, be performed to a predetermined lower value, or by subtracting a predetermined value from the current parameter value or may be performed by taking a fraction (e.g. 70%) of the current parameter value. The downward adjustment of the parameter value may thus be different within a group.

0091The PCEF* may notify the PCRF* when the aggregate bit rate returns within the limits again. The PCRF* may also instruct PCEF* to apply a predetermined hysteresis before notifying congestion condition expiration.

0092An upward adjustment of the individual congestion parameters, such as the maximum bit rate values MBR, may be performed stepwise, with “feedback” from the PCEF*, for example after every step. The size of the upward adjustments and their distribution amongst the IP-CAN bearers or terminals <b>3</b>A-<b>3</b>D is decided by the PCRF*. As an example, the distribution may be predefined in the group record stored in the SPR*, or the PCRF* may consult the server <b>2</b> via provisioning interface Py as illustrated in <figref idref="DRAWINGS">FIG. 6B</figref> or an upward adjustment may be requested by a communication terminal and then subject to approval from the PCRF* in the usual way.

0093It should be appreciated that the adjustment of the individual congestion parameters, either a downward adjustment of an upward adjustment, may be performed according to various policies as exemplified above. The congestion parameter adjustment policies for a group may be comprised in a group record, as schematically indicated in <figref idref="DRAWINGS">FIG. 3B</figref>.

0094As illustrated in <figref idref="DRAWINGS">FIG. 7A</figref>, a second group load condition GLC<b>2</b> may be defined that functions as a lower trigger level for triggering the PCEF* to notify the PCRF*. When group load condition GLC<b>2</b> is no longer satisfied, the PCRF* may decide on scaling up one or more of its previously set PCC rules for terminals <b>3</b>A-<b>3</b>D in the group G that could benefit from a somewhat higher bit rate.

0095<figref idref="DRAWINGS">FIG. 7B</figref> provides a schematic flow chart of the communication between the PCEF* and the PCRF* in the above-described example for uplink traffic.

0096In step <b>1</b>, PCEF* establishes that group load condition GLC<b>1</b> or GLC<b>2</b> is satisfied. In the present example, the PCEF* detects that the aggregate bit rate of the communication terminals <b>3</b> in group G exceeds a predetermined value at a particular point in time.

0097In step <b>2</b>, the PCEF* notifies the PCRF* on the fact that the group load condition GLC<b>1</b> is satisfied.

0098In step <b>3</b>, a new policy decision is made by the PCRF*, for example a decision to scale down the maximum bit rate parameters (MBR) for the PCC rules and, consequently, for the bearers of terminals <b>3</b>A and <b>3</b>B of the group G. The information which bearers and/or which parameters should be adapted is determined by the congestion parameter adjustment policy or is e.g. obtained from the SPR* or from the server <b>2</b> as illustrated in <figref idref="DRAWINGS">FIG. 6A</figref> as described above.

0099In step <b>4</b>, the PCEF* is informed of the adjusted individual PCC rules, illustrated in <figref idref="DRAWINGS">FIG. 5A</figref>, for terminals <b>3</b>A and <b>3</b>B. Updated group rules may also be provided to the PCEF* when the operator of the telecommunications network <b>1</b> may e.g. desire to adapt the group load condition GLC<b>1</b> and/or GLC<b>2</b>.

0100In step <b>5</b>, the IP-CAN bearers of the relevant communication terminals (in this example: for terminal <b>3</b>A and for terminal <b>3</b>B) are modified according to the adjusted PCC rule for that communication terminal. Each of the involved terminals (in this example: terminals <b>3</b>A and <b>3</b>B) is informed about the adjusted value of the individual congestion parameters (in this example with a downscaled value of the MBR) and the terminal will act accordingly.

0101While these messages may be sent to each of the terminals (in this example: terminals <b>3</b>A and <b>3</b>B) separately from the gateway GGSN, it may be advantageous to use the group identifier of the group G and send a group update request to a network node further downstream in the telecommunications network <b>1</b> in order to adjust the data session communication parameters (e.g. PDP Context and IP-CAN bearer) of the communication terminals in the group G. This will explained in further detail below with reference to <figref idref="DRAWINGS">FIGS. 8</figref> ff.

0102In step <b>6</b>, the PCEF* enforces the new individual PCC rules, using the adjusted PCC rules for (in this example) terminals <b>3</b>A and <b>3</b>B.

0103Finally, in step <b>7</b>, the PCEF* informs the PCRF* on the successful adjustment of the IP-CAN bearers and, possibly, about the establishment of an adjusted group load condition.

0104Of course, the process may be repeated from step <b>1</b> for additional notifications related to a same (possibly adjusted) group load condition or other such conditions and/or may be repeated from step <b>3</b>, for example to further downwardly adjust individual congestion parameters when an earlier downward adjustment has not yet sufficiently resolved the congestion or to instruct an upward adjustment when PCRF* decides so.

0105When the PCRF* is notified about a congestion condition, the PCRF* may, in addition to adjusting a congestion parameter of the bearer(s), also decide to make adjustments to its policy to authorise QoS resources to additional bearers which may be requested to be established or to additional data sessions which may request to become active in the group. This is illustrated in <figref idref="DRAWINGS">FIG. 7C</figref> for terminal <b>3</b>E. For example, the PCRF* may decide to also adjust the maximum bit rate that may be authorised to additional bearers or sessions in group G from a value of e.g. 40 to a value of e.g. 10. When the additional terminal <b>3</b>E in group G were to request to establish a bearer with an MBR_Eof e.g. 40, the PCRF* will take a policy decision. In this case, the PCRF* will not grant the requested MBR_Eof 40, which would otherwise be allowed, but it will issue a PCC rule with an MBR_Eof 10, shown by the downwardly pointing arrow for terminal <b>3</b>E.

0106As mentioned above, the availability of a group record and the common group identifier can be used to advantage both in combination with the congestion control method and system as described above and for other purposes as described in the co-pending application “Information transmission in a machine-to-machine telecommunications network” of the applicant filed on the same date, which is included in the present application by reference in its entirety.

0107Generally, the common group identifier can be used to adjust the IP-CAN bearers, such as a PDP Context or a parameter of the IP-CAN, of a large number of communication terminals. Currently, a network-initiated modification of a particular PDP Context is supported by most modern telecommunications network technologies. The current techniques involve signaling between at least a network node and each of the communication terminals.

0108In the known method, modification of the PDP context of the bearers of each of the involved communication terminals induces a signaling load proportional to the number of IP-CAN bearers (normally, the number of terminals). In other words, IPCAN bearer modification messages take place on a per-bearer basis. PDP context modification procedures are e.g. described in 3GPP TS 23.060. In addition, the load inherently peaks when a modification is initiated for a considerable number of communication terminals, as may e.g. be necessary in the above-mentioned method and system for congestion control wherein the communication terminals <b>3</b> of the group G need to be informed on the adjustment of the PCC rules for uplink traffic. This peak is also observed for the processing load of the involved network elements.

0109The common group identifier of communication terminals may be used to reduce the signaling load in the network when initiating adjustment of individual congestion parameters for the bearers of a considerable number of communication terminals. Also, the peak in signaling load and the processing load in the network elements can be reduced in this manner.

0110As an example, an IP-CAN bearer group modification procedure can be used that comprises the IP-CAN bearer modifications of the individual communication terminals <b>3</b>. (Sub)groups are identified by common (sub)group identifiers in a HLR or HSS/SPR and communication terminals can be assigned to one or more of these groups.

0111Such a group modification procedure can e.g. be initiated in a network node as the GGSN/P-GW or the SGSN/S-GW upon detection of a trigger for such modification (see the earlier embodiment of satisfying the congestion load condition).

0112<figref idref="DRAWINGS">FIG. 8</figref> is an embodiment of a GGSN-initiated group PDP context modification procedure for a group G comprising communication terminals <b>3</b>A-<b>3</b>Z.

0113In the first step after a trigger (not shown), the GGSN sends a Group Update PDP Context Request to one or more SGSNs. This message contains e.g. a common group identifier as obtained from the group record stored in the HLR/SPR* or HSS/SPR*. The message also contains the QoS Requested parameter indicating the desired QoS profile for each of the bearers in the group G. Considerable efficiency is gained here, since only one request is transmitted from the GGSN to the SGSN as opposed to the prior art procedure wherein update requests are required for each bearer individually. The Group Update PDP Context Request may contain the IP-CAN bearer adjustment for the above-described congestion control method and telecommunications network <b>1</b>.

0114The SGSN derives the involved communication terminals <b>3</b>A-<b>3</b>Z from the Group Update PDP Context Request received from the GGSN by interacting with the HLR using the common group identifier. The information on the individual communication terminals <b>3</b>A-<b>3</b>Z (i.e. the individual identifiers thereof) may be retrieved from the HLR and/or stored at the SGSN after retrieval.

0115The SGSN sends in step <b>2</b> a Modify PDP Context Request message to each terminal <b>3</b>A-<b>3</b>Z comprising, amongst other information, the newly negotiated QoS. The newly negotiated QoS may have been restricted further by the SGSN.

0116Each terminal <b>3</b>A-<b>3</b>Z may acknowledge the PDP Context Modification Request of step <b>2</b> by returning to the SGSN a Modify PDP Context Accept message. If a terminal <b>3</b>A-<b>3</b>Z does not accept the newly negotiated QoS, it may instead de-activate the PDP context with a terminal-initiated PDP Context Deactivation procedure. The SGSN may then follow a terminal-initiated PDP Context Deactivation procedure (not shown).

0117At least in UMTS networks, a PDP Context modification also involves a RAB (Radio Access Bearer) modification. RAB modifications are performed immediately after a Modify PDP Context Request (step <b>2</b>) or after a Modify PDP Context Accept (step <b>3</b>) in step <b>4</b> for each individual communication terminal <b>3</b>A-<b>3</b>Z. Alternatively, the RAB modification is performed after receiving the Modify PDP Context Accept of step <b>3</b> for each of the terminals.

0118Upon receipt of the Modify PDP Context Accept messages from all terminals <b>3</b>A-<b>3</b>Z, or upon completion of all the RAB modification procedures (for UMTS networks), the SGSN returns a Group Update PDP Context Response message to the GGSN. This message contains e.g. the same common group identifier as contained in the Group Update PDP Context request received from the GGSN. In signaling message exchange it is also possible to use a transaction identifier, which value is assigned by the GGSN and the GGSN includes in the request of step <b>1</b> and which value the SGSN includes in its response in step <b>5</b>, possibly as an alternative for the group identifier.

0119A group PDP Context modification as shown in <figref idref="DRAWINGS">FIG. 8</figref> may also be initiated by an SGSN, for example, when the SGSN or an associated entity detects a congestion load condition as described earlier. In such a situation, the SGSN may advantageously immediately initiate a group PDP Context Modification, rather then only reporting the congestion condition to another network node (to e.g. the GGSN or to the PCEF*) and having other network entities initiating appropriate action. In this case it is assumed that a group has been defined wherein all data sessions (communication terminals) belonging to the group are under control of the SGSN. Then, a similar procedure can be followed as described for <figref idref="DRAWINGS">FIG. 8</figref>, where the interactions with the GGSN in the first and the last step of <figref idref="DRAWINGS">FIG. 8</figref> are omitted. However, during or after completion of the modification, the SGSN notifies the GGSN about the modification, for which notification the common group identifier for that SGSN-oriented group may advantageously be used. Also, the SGSN may send a Group Update PDP Context Request to the GGSN and the GGSN may respond with a related response message to the SGSN in order to take information (e.g. limitations) available at the GGSN into account.

0120It should be appreciated that the procedure for group PDP Context modification as described with reference to <figref idref="DRAWINGS">FIG. 8</figref> is not limited to modifications relating to congestion control and is not limited to modification of individual congestion parameters that may effect congestion resolution or relief. The procedure may also be used advantageously at other occasions where multiple PDP Contexts or similar contexts in other types of networks are to be modified and the procedure may also be used for other parameters, such as modification of the Access Point Name (APN), modification of the QoS class, modification of the DiffServ DSCP marking to be applied, etc.

0121It may be useful in particular cases to broadcast messages to a group of communication terminals. These messages contain the common group identifier and may e.g. contain information relating to congestion control or to other information relevant for a group G of communication terminals <b>3</b>. In such cases, the communication terminals <b>3</b> should have (access to) the common group identifier in order to retrieve (select) the information from the broadcast. This information relating to the common group identifier may e.g. be obtained during an attach procedure to the telecommunications network <b>1</b>, wherein the common group identifier(s) can be retrieved from the individual subscription record (see <figref idref="DRAWINGS">FIG. 3A</figref>) and transmitted to the terminal. The common group identifier(s) may also be stored or preprogrammed in (a module of) the communication terminal <b>3</b>.

0122The broadcast embodiments may apply a cell broadcast centre CBC, known as such. Various architectures are possible, e.g. where the CBC is connected to a plurality of SGSNs/S-GWs and/or to a plurality of GGSNs/PG-W, as displayed in <figref idref="DRAWINGS">FIG. 9</figref>. Again, the message transmission may be initiated either by a SGSN or by a GGSN. Cell broadcast services are specified in 3GPP TS 23.041.

0123<figref idref="DRAWINGS">FIG. 10</figref> shows a flow chart for modifying the PDP Context of a group G of terminals <b>3</b>A-<b>3</b>Z, wherein the GGSN initiates the group update PDP context request, when triggered (step <b>1</b>) to modify the PDP context as described previously and the CBC is controlled by the SGSN.

0124The GGSN sends in step <b>2</b> a Group Update PDP Context Request to one or more SGSNs. This request contains at least the common group identifier for the group G of communication terminals <b>3</b>A-<b>3</b>Z that has to be modified and (a) parameter(s) indicating the desired QoS for the bearers of the communication terminals <b>3</b>A-<b>3</b>Z in the group G. In order to ensure that all relevant SGSNs receive this request the GGSN may follow different approaches. One approach is that the GGSN sends the request to all SGSNs it connects to. Another approach is that the GGSN derives the relevant SGSNs (by consulting the HLR/HSS) and sends the request to the relevant SGSNs only. Yet another approach is that the GGSN, for each group, sets up a multicast group on which messages may be multi-casted. Then, the SGSN, when a PDP Context is set up for a terminal belonging to a certain group G, informs the GGSN that it subscribes to receiving all messages transmitted on the multicast group associated with group G. In the event of a group Update PDP Request, the GGSN only needs to insert a single message on the multicast group associated with group G to ensure that all relevant SGSNs (which all are subscribed to that group) receive the message.

0125The SGSN uses a broadcast or multicast technology to inform the communication terminals <b>3</b>A-<b>3</b>Z in the group G on the update PDP context group request. More specifically, in this embodiment, Cell Broadcast (CB) is used. The SGSN acts a Cell Broadcast Entity (CBE) (see 3GPP TS 23.041). It defines the geographical areas, known as cell broadcast areas, in which the messages should be broadcasted. This could be all cells that are associated with the SGSN. In step <b>3</b>, the SGSN sends a CB message Request to the CBC. This CB message contains the Modify PDP Context Group Request parameter, the common group identifier for the group G and (a) parameter(s) indicating the requested QoS for the PDP contexts in the group G.

0126In step <b>4</b><i>a</i>, the CBC transfers the CB message in Write-Replace messages to the RAN i.e. to one or more BSCs/RNCs according to the (defined) cell broadcast area. In turn the RAN, via an SMS Broadcast Request, requests to broadcast the CB message in the defined areas in step <b>4</b><i>b</i>. The CB message contains also the common group identifier for group G. Each communication terminal receiving the broadcast message is then able to determine whether or not the received message is destined for that terminal. That is the case when at least one of the group identifiers in a received message matches at least one of the terminal's group identifiers. A communication terminal with a group identifier ID_Gfor group G, will thus recognise that a received broadcast message that comprises group identifier ID_Gis destined for that terminal as shown in step <b>4</b><i>b </i>of <figref idref="DRAWINGS">FIG. 10</figref> and other terminals which received this message may ignore this message as irrelevant (not shown in <figref idref="DRAWINGS">FIG. 10</figref>). Alternatively, when multiple cell broadcast channels are available, the group identifier may determine to which of the channels the communication terminals should be tuned. In response to the Write-Replace the RAN sends a Report-Success, in step <b>4</b><i>c. </i>The broadcast of messages in this step <b>4</b> is according to the specification of Cell Broadcast Services, refer to 3GPP TS 23.041.

0127After having received all the Report-Success messages from the RAN i.e. from all the involved BSCs/RNCs, the CBC sends a CB message Report to the SGSN in step <b>5</b>. Also, the communication terminals <b>3</b>A-<b>3</b>Z, having received the CB message and having recognised the message as destined for it, in step <b>4</b><i>b </i>accept the modification requests in steps <b>6</b><i>a</i>-<b>6</b><i>z. </i>Each of them sends an ordinary Modify PDP Accept message (eventually including an identification of the group G of the communication terminals <b>3</b>A-<b>3</b>Z to which the PDP context belongs) to the SGSN. As indicated before, it is also common to use a transaction identifier, which value could be assigned by the SGSN and the SGSN includes it in the group Modify PDP Context request in the CB message request of step <b>3</b> and which value each of the terminals <b>3</b>A-<b>3</b>Z includes in its response in step <b>6</b><i>a</i>-<i>z. </i>

0128In steps <b>7</b><i>a</i>-<b>7</b><i>z, </i>Radio Access Bearer (RAB) modification is performed for each of the terminals <b>3</b>A-<b>3</b>Z individually after receiving the Modify PDP Context Accept messages <b>6</b><i>a</i>-<b>6</b><i>z </i>for an individual terminal. Again, these steps <b>7</b>a-<b>7</b><i>z </i>may also be performed after receiving all individual Modify PDP Context Accept messages (steps <b>6</b><i>a</i>-<b>6</b><i>z</i>).

0129Upon handling of the Modify PDP Context procedures from all communication terminals <b>3</b>A-<b>3</b>Z in the group G, the SGSN returns a Group Update PDP Context Response message to the GGSN in step <b>8</b>. This message contains at least the common group identifier for the group G. As indicated before, it is also common to use a transaction identifier, which value is assigned by the GGSN and the GGSN includes in the group Update PDP Context Request of step <b>2</b> and which value the SGSN includes in its response in step <b>8</b>.

0130Finally, the GGSN may inform the entity that triggered the group-wise modification of the PDP contexts on the outcome of the PDP context modification (step <b>9</b>).

0131As already noted, other variants of the embodiment of <figref idref="DRAWINGS">FIG. 10</figref> are possible. As an example, the GGSN may be triggering the CBC to send the modification requests to the communication terminals <b>3</b>A-<b>3</b>Z in the group G. The cell broadcast interaction will then be between the GGSN and the CBC instead of between the SGSN and the CBC. Step <b>2</b> will then be an information message from the GGSN to the SGSN also including the notification that the GGSN will act as a Cell Broadcast Entity (CBE).

0132In another envisaged embodiment, the SGSN (instead of the GGSN) will be triggered to initiate the modification for the group G of communication terminals <b>3</b>A-<b>3</b>Z. The SGSN may then send a Group Update PDP Context Request to the GGSN and the GGSN may return a Group Update PDP Context Response message to the SGSN.

0133In still another embodiment, the SGSN is triggered to initiate the modification of the group G of communication terminals <b>3</b>A-<b>3</b>Z (like in the previous embodiment), but the GGSN will act as the CBE. The SGSN, internally triggered, sends a Group Update PDP Context Request to the GGSN. The GGSN returns a Group Update PDP Context Response Message to the SGSN. The Cell Broadcast interaction occurs between the GGSN and the CBC and the GGSN informs the SGSN that it will act as the CBE.