WO2014003750A1

WO2014003750A1 - Usage monitoring for groups of devices

Info

Publication number: WO2014003750A1
Application number: PCT/US2012/044520
Authority: WO
Inventors: Devaki Chandramouli; Rainer Liebhart
Original assignee: Nokia Siemens Networks Oy
Current assignee: Nokia Solutions and Networks Oy
Priority date: 2012-06-28
Filing date: 2012-06-28
Publication date: 2014-01-03
Anticipated expiration: 2014-12-28

Description

TITLE:

Usage Monitoring for Groups of Devices

BACKGROUND:

Field:

[0001] Communication systems, such as an evolved packet system, may benefit from usage monitoring. In particular, certain communication systems in which groups of related user equipment are deployed may benefit from a monitoring of groups of devices.

Description of the Related Art:

[0002] The evolved packet system (EPS), the successor of general packet radio system (GPRS), provides radio interfaces and packet core network functions for broadband wireless data access. EPS core network functions include the mobility management entity (MME), the packet data network gateway (PDN- GW) and the Serving Gateway (S-GW). An example of an evolved packet core architecture is illustrated in Figure 1 and is described by third generation partnership project (3GPP) technical specification (TS) 23.401, which is incorporated herein by reference in its entirety. A common packet domain core network can be used for both radio access networks (RANs), the global system for mobile communication (GSM) enhanced data rates for GSM evolution (EDGE) radio access network (GERAN) and the universal terrestrial radio access network (UTRAN). This common core network (CN) can provide general packet radio service (GPRS) services.

[0003] Figure 2 illustrates an overall policy charging and control (PCC) architecture, including roaming with home routed access, when subscription profile repository (SPR) is used. The PCC architecture can extend the architecture of an internet protocol connectivity access network (IP-CAN), where the policy and charging enforcement function (PCEF) is a functional entity in the Gateway node implementing the IP access to the PDN.

[0004] As shown in Figure 2, a home policy and charging rules function (H- PCRF) is connected to the PCEF, residing in a gateway, over Gx. The PCEF is connected to an offline charging system (OFCS) over Gz. The PCEF is connected to service data flow based credit control function in an online charging system (OCS) over Gy. The OCS is, in turn, connected to the H- PCRF over Sy. Rx connects the H-PCRF to an application server (AF), while Sp connects the H-PCRF to the SPR. A visited PCRF (V-PCRF), in a visited public land mobile network (VPLMN) can be connected to the H-PCRF, in the home public land mobile network (HPLMN) via S9. The V-PCRF may also be connected to a bearer binding and event reporting function (BBERF) over Gxx.

[0005] Conventionally, groups of devices are located under the same P- GW/gateway GPRS support node (GGSN). Usage monitoring can then be performed by a single P-GW/GGSN for a single device, with all devices connected to the same P-GW/GGSN. P-GW/GGSN can exemplify gateway nodes in general.

SUMMARY:

[0006] According to certain embodiments, a method includes determining that a group is connected to a plurality of gateway nodes, wherein the group comprises a plurality of user equipment. The method also includes monitoring data usage of user equipments of the group, based on the determination.

[0007] In certain embodiments, a method includes determining that a user equipment is associated with a group. The method also includes selecting a common policy and charging rules function for user equipment based on the association with the group.

[0008] An apparatus, according to certain embodiments, includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to determine that a group is connected to a plurality of gateway nodes, wherein the group comprises a plurality of user equipment. The at least one memory and the computer program code are also configured to, with the at least one processor, cause the apparatus at least to monitor data usage of user equipments of the group, based on the determination.

[0009] An apparatus, in certain embodiments, includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to determine that a user equipment is associated with a group. The at least one memory and the computer program code are also configured to, with the at least one processor, cause the apparatus at least to select a common policy and charging rules function for user equipment based on the association with the group.

[0010] In certain embodiments, an apparatus includes determining means for determining that a group is connected to a plurality of gateway nodes, wherein the group comprises a plurality of user equipment. The apparatus also includes monitoring means for monitoring data usage of user equipments of the group, based on the determination.

[0011] According to certain embodiments, an apparatus includes determining means for determining that a user equipment is associated with a group. The apparatus also includes selecting means for selecting a common policy and charging rules function for user equipment based on the association with the group.

[0012] A non-transitory computer readable medium is, in certain embodiments, encoded with instructions that, when executed in hardware, perform a process. The process includes determining that a group is connected to a plurality of gateway nodes, wherein the group comprises a plurality of user equipment. The process also includes monitoring data usage of user equipments of the group, based on the determination.

[0013] A non-transitory computer readable medium is, according to certain embodiments, encoded with instructions that, when executed in hardware, perform a process. The process includes determining that a user equipment is associated with a group. The process also includes selecting a common policy and charging rules function for user equipment based on the association with the group.

BRIEF DESCRIPTION OF THE DRAWINGS:

[0014] For proper understanding of the invention, reference should be made to the accompanying drawings, wherein:

[0015] Figure 1 illustrates an evolved packet core architecture.

[0016] Figure 2 illustrates an overall policy charging and control (PCC) architecture, including roaming with home routed access, when subscription profile repository (SPR) is used.

[0017] Figure 3 illustrates notification of a selected PCRF to a AAA server, according to certain embodiments.

[0018] Figure 4 illustrates a AAA server providing a selected PCRF to a P- GW/GGSN, according to certain embodiments.

[0019] Figure 5 illustrates notification of a selected PCRF to a home subscriber server, according to certain embodiments.

[0020] Figure 6 illustrates an HSS providing a selected PCRF to a P- GW/GGSN, according to certain embodiments.

[0021] Figure 7 illustrates time based monitoring at the P-GW/GGSN, according to certain embodiments.

[0022] Figure 8 illustrates monitoring based on equal allocation of bandwidth at the P-GW/GGSN, according to certain embodiments.

[0023] Figure 9 illustrates monitoring based on differentiated allocation of bandwidth based on number of users connected at the P-GW/GGSN.

[0024] Figure 10 illustrates a method according to certain embodiments.

[0025] Figure 11 illustrates another method according to certain embodiments.

[0026] Figure 12 illustrates a system according to certain embodiments. DETAILED DESCRIPTION:

[0027] When the networks experience user plane congestion that disrupts the services for normal users connected to the network, mobile network operators may desire to identify the source of the problem. For example, operators may desire to pinpoint the application that is actually causing the user plane congestion in the network so the appropriate vendor can be notified and action be taken. This may require monitoring the data usage of all the devices running the given application.

[0028] In certain cases, it may be valuable for the network to provide the ability to monitor the data usage by a group of devices. For example, this may be valuable when subscribers have signed up for a family data plan, such as 2GB of data usage to be shared by a family of three people: Bob, Alice and Pinto. Support for group-based usage monitoring may enable group based charging, such as pre-paid / post-paid charging for this family.

[0029] Likewise, group based monitoring may be useful when devices running similar applications are grouped, and an operator may desire to monitor the data generated by this application so the behavior can be characterized and any misbehaving application can be tracked and charged appropriately. Moreover, such monitoring may be valuable in a case where a service provider has subscribed for thousands of devices, for example smart meters, and charging is based on data generated by groups of these devices.

[0030] By avoiding locating a big group of devices under the same P- GW/GGSN, user plane congestion may be reduced. For example, devices in a group can be spread out amongst different P-GW/GGSN(s), depending on their location. Hence, certain embodiments perform usage monitoring when the users and/or devices within a group are connected to different P- GW/GGSN(s).

[0031] Certain embodiments, therefore, provide an approach for usage monitoring of a group of devices when they are connected to different P- GW/GGSN(s). This feature can give operators the ability to monitor data usage for a group of devices, thereby giving the devices the ability to take appropriate action when the usage has exceeded, as well as to charge and inform users accordingly.

[0032] Analytically, certain embodiments can be viewed in terms of two aspects. A first aspect is the selection of a common PCRF for all the devices in the group, irrespective of how many different GGSN/P-GW(s) are used. A second aspect is a procedure for the PCRF to perform usage monitoring when the devices are connected to different P-GW/GGSN(s).

[0033] Selecting a common PCRF for all devices in the group can be valuable, because this selection can give the ability for the application server, or monitoring server, referred to as AF in Figure 2, to register with a single PCRF via Rx interface to monitor data usage for a group of devices.

[0034] There can be at least two alternatives to ensure that a common PCRF is selected for all devices within the group.

[0035] Figure 3 illustrates notification of selected PCRF to an authentication, authorization and accounting (AAA) server, according to certain embodiments. According to a first option, when a new PDN connection is established, a P-GW/GGSN authenticates and authorizes the user with a AAA server (or alternatively with a home subscriber server (HSS)), if this is required. The authentication server checks that the user can be accepted and is allowed to use the selected service. When the first user equipment that belongs to a certain group establishes the first PDN connection, the P-GW/GGSN selects the PCRF and, as shown at 1 in Figure 3, informs the selected PCRF to the AAA server / HSS along with the group identifier in the access request message and the AAA server / HSS stores this information <Group ID, selected PCRF> upon determining that the authorization is successful, based on receiving an access accept at 2.

[0036] Figure 4 illustrates a AAA server providing a selected PCRF to a P- GW/GGSN. When subsequent PDN connections are being established for an user equipment that already has a PDN connection established or a first PDN connection is being established for other user equipments in the group, then the P-GW/GGSN can perform authentication and authorization of the user with AAA / HSS server without selecting a PCRF but can include the group identifier in the access request message, at 1. In the authorization response / access accept at 2, the AAA server can indicate the selected PCRF for the given group. If the selected PCRF is returned in the response message, P- GW/GGSN can select the same PCRF for the user and can establish a Gx session accordingly.

[0037] Figure 5 illustrates notification of a selected PCRF to a home subscriber server. According to a second option, upon receiving a create session request message at 1, a P-GW/GGSN can inform the MME/SGSN, via the S-GW, in a create session response message, at 2, with the selected PCRF for the given group. At 3, the MME/SGSN can notify the HSS with the selected PCRF for the given group ID, when it provides information on the selected P-GW/GGSN for the user equipment. HSS stores this information <Group ID, selected PCRF>.

[0038] Figure 6 illustrates an HSS providing a selected PCRF to a P- GW/GGSN. For subsequent PDN connection establishments for user equipment in the group, when the subscription information is downloaded to the MME/SGSN, if HSS has the selected PCRF information for the given Group ID available, the HSS can also provide that to the MME/SGSN at 1, after retrieving it at la. The MME/SGSN can then include this in the create session request message, at 2, to the P-GW/GGSN whenever PDN connection is being established. Thus, at 2b, the P-GW/GGSN can determine that the procedure to perform selection of a new PCRF need not be executed. Particularly, if the selected PCRF is included in the create session request message, the P-GW/GGSN does not need to select a new PCRF but can instead select the PCRF, sent in the create session request message, and can establish Gx session accordingly, at 3.

[0039] Various procedures can be used to allocate shared bandwidth and monitor data usage. For example, the AF can register with the PCRF for notification about when the data usage for a group of users exceeds a certain threshold (T). Since the users within a group may be connected to different P- GW(s)/GGSN(s), the PCRF can apply various intelligent means to monitor the data usage.

[0040] For example, in a first option the PCRF can register for time based monitoring with the P-GW / GGSN(s) where the users in the group are connected and can aggregate the output at the PCRF. The PCRF can then report to the AF based on the outcome.

[0041] Moreover, in a second option the PCRF can allocate equal bandwidth to all P-GW/GGSN(s) where the users in the group are connected and can register with the P-GW/GGSN to report when the allocated bandwidth level reduces to a certain minimum threshold (Tmin).

[0042] In a third option, the PCRF can allocate bandwidth to each P- GW/GGSN depending on the number of users connected to the respective P- GW/GGSN at any given time (e.g. allocate relatively more bandwidth to a certain P-GW / GGSN when this P-GW / GGSN serves more users), and can register with the P-GW/GGSN to report when the allocated bandwidth level reduces to a certain minimum threshold (Tmin).

[0043] Figure 7 illustrates time based monitoring at the P-GW/GGSN. This alternative involves, at 1, the PCRF registering with the P-GW/GGSN(s), where the users in the group are connected, for periodic monitoring of data usage. The P-GW/GGSN then can monitor, at la, the data usage for a group of user equipments and can, at 2, report the aggregated data usage to PCRF periodically (period = t).

[0044] The PCRF can obtain the aggregated data usage from all the P- GW/GGSN(s) and can compare the total with the threshold (T) provided by the AF. If the total is equal to or exceeds the threshold (T), then the PCRF can report it to the AF; otherwise, the PCRF may store the latest report and take no further action. [0045] Figure 8 illustrates monitoring based on equal allocation of bandwidth at the P-GW/GGSN. This alternative can involve the PCRF allocating bandwidth equally amongst all the P-GW/GGSN(s) where the users in the group are connected. At 1, the PCRF can register with the P-GW/GGSN(s) to monitor the data usage and to report when the threshold reaches minimum level (Tmin). This minimum level can be assigned at the P-GW/GGSN for the ongoing user plane traffic. This can be administered in various ways by the PCRF.

[0046] For example, at 2 the P-GW/GGSN can report to the PCRF that the P- GW/GGSN has reached Tmin. The PCRF can then, at 3, query all the other P- GW/GGSN(s) for the remaining bandwidth allocated. Alternatively, the PCRF can also hold some budget of the available threshold and grant a part of this budget to the P-GW/GGSN as long as budget is still available. This alternative can be performed by the PCRF even when a user connected to the P-GW/GGSN that has not yet been allocated any budget.

[0047] At 4, the other P-GW/GGSN(s) can retain the minimum threshold for ongoing user plane traffic and can report only the remaining bandwidth to the PCRF.

[0048] Then, at 4b, the PCRF accumulates the reported bandwidth and evenly divides the bandwidth amongst all P-GW/GGSN(s) including both the reporting P-GW/GGSN, at 5, and the other P-GW/GGSN(s) at 6.

[0049] Steps 2-4b can be repeated until PCRF determines there is no more bandwidth to be allocated at the P-GW/GGSN. Upon determining that the PCRF has no more bandwidth to be allocated, the PCRF can report to the AF that the group of users has exceeded the set threshold (T).

[0050] As used in Figure 8, Tdiv = Threshold (T) / number of P-GW/GGSN where users in the group are connected. Likewise, Tcurrent is the difference between current data usage level for the group at the P-GW/GGSN and Tmin (i.e. Tcurrent = current data usage level for the group at the P-GW/GGSN - Tmin). [0051] Figure 9 illustrates monitoring based on differentiated allocation of bandwidth based on number of users connected at the P-GW/GGSN. This alternative is similar to the alternative of Figure 8, except that this alternative involves the PCRF allocating bandwidth based on the number of users connected to the P-GW/GGSN(s). At 1, the PCRF registers with the P- GW/GGSN(s) to monitor the data usage and report when the threshold reaches minimum level (Tmin). This minimum level can be assigned at the P- GW/GGSN for the ongoing user plane traffic. When the first P-GW/GGSN reaches a Tmin threshold, at 2, P-GW/GGSN reports to the PCRF that it has reached Tmin. Then, at 3, the PCRF queries all the other P-GW/GGSN for the remaining bandwidth allocated. Alternatively the PCRF can also hold some budget of the available threshold and grant a part of this budget to the P- GW/GGSN as long as budget is still available.

[0052] At 4, the other P-GW/GGSN(s) can retain the minimum threshold for ongoing user plane traffic and can report only the remaining bandwidth to the PCRF. Then, at 4b, the PCRF can accumulate the reported bandwidth and can divide the bandwidth based on the number of users connected to the P- GW/GGSN. For example, if more users are connected to a P-GW/GGSN, then more bandwidth may be allocated to the P-GW/GGSN. The PCRF may also use logic that takes user behavior into account. For example, users sending/receiving a lot of data can be granted more budget, in terms of allocation amount.

[0053] Steps 2-4b can be repeated until the PCRF determines there is no more bandwidth to be allocated at the P-GW/GGSN. Upon determining that the PCRF has no more bandwidth to be allocated, the PCRF can report to the AF that the group of users has exceeded the set threshold (T).

[0054] As used in Figure 9, Tusers = Threshold (T) / number of users currently connected to the P-GW/GGSN. Likewise, Tcurrent is the difference between current data usage level for the group at the P-GW/GGSN and Tmin (i.e. Tcurrent = current data usage level for the group at the P-GW/GGSN - Tmin). [0055] The value for minimum threshold (Tmin) can be chosen in such a way that P-GW/GGSN is able to allocate bandwidth when the notifications / signaling messages are in progress between P-GW/GGSN and PCRF regarding the data usage. Moreover, the period (t) can be determined such that it is not too frequent (which causes processing overhead) at the same time it is not very infrequent (which causes the data usage to be exceeded significantly), thereby ensuring balancing processing overhead and data usage by the system.

[0056] Various modifications to the above alternatives can be used. For example, to ensure that the same PCRF is selected for all members in the group, the identity of the PCRF can also be stored in the SPR or another database (DB) within the mobile network operator (MNO) domain. Similar procedures to those described above (figure 3 to 6) could then apply for notifying the SPR / DB about a selected PCRF and retrieving the PCRF for subsequent connection requests / connection requests from other user equipments in the group. In some deployments, the SPR may be collocated with the HSS/AAA.

[0057] Moreover, the OCS could also maintain the allocated bandwidth for a group of users. This may be beneficial if users are being charged differently based on a usage threshold. Similar logic to that discussed above (figure 7 - 9) can apply even when the OCS maintains the allocated bandwidth. For example, the OCS could register with the PCRF for notification when the threshold exceeds or OCS could directly register with the PCEF (P- GW/GGSN) and follow any of the procedures described for figures 7 - 9.

[0058] Certain embodiments of the present invention may provide the ability for the operator to monitor data usage for a group of devices which can enable several use cases, as described above. Besides that, the proposed approach can be implemented in all RATs, for example, E-UTRAN, UTRAN, and GERAN.

[0059] Figure 10 illustrates a method according to certain embodiments. The method of Figure 10 may be performed by, for example, a single policy and charging rules function. As shown in Figure 10, the method can include, at 1010, determining that a group is connected to a plurality of gateway nodes, wherein the group comprises a plurality of user equipment. The gateway nodes may be, for example, P-GW/GGSN(s). The method can also include, at 1020, monitoring data usage of user equipments of the group, based on the determination. The monitoring of the group comprises a single policy and charging rules function monitoring the devices of the group.

[0060] The method can further include taking an action selected from, at 1030, charging of users associated with the group or, at 1035, informing users associated with the group, when the monitored data usage exceeds a predetermined threshold, such as a pre-paid or subscription amount.

[0061] The monitoring can include at least one of, at 1040, registering for time based monitoring with the plurality of nodes or, 1045, registering for data threshold based reporting. In the case of allocation threshold based reporting, the allocation threshold can be uniform for all gateway nodes or is based on a number of group members served by a respective gateway node or the data usage pattern of group members.

[0062] The method can further include, at 1050, determining that an allocation is exceeded for a first gateway node and, at 1055, rebalancing allocation amongst the plurality of gateway nodes based on the determination that the allocation is exceeded.

[0063] The method can additionally include, at 1060, reporting to an application server that requested the monitoring, when the monitoring indicates that the data usage has reduced an available data usage below a threshold. Moreover, the method can also include, at 1070, storing, in a subscription profile repository, an identifier of a policy and charging rules function corresponding to the group. Further, the method can include, at 1080, maintaining an allocated bandwidth of the group in an online charging system.

[0064] Figure 1 1 illustrates another method according to certain embodiments. The method can be performed by, for example, a gateway. As shown in Figure 1 1, the method can include, at 1 110, determining that a user equipment is associated with a group. The method also includes, at 1120, selecting a common policy and charging rules function for user equipment based on the association with the group. The selecting can include, at 1130, a gateway node selecting a policy and charging rules function for a first member of the group. The selecting can include, at 1140, an authentication server or a home subscriber server storing the selected policy and charging rules function for the group and the gateway node retrieving the stored policy and charging rules function for a second or subsequent member of the group.

[0065] Figure 12 illustrates a system according to certain embodiments of the invention. In one embodiment, a system may include multiple devices, such as, for example, PCRF 1210, a first P-GW/GGSN (P-GW/GGSN-I) 1220, and other P-GW/GGSN 1230. Each of these devices may include at least one processor, respectively indicated as 1214, 1224, and 1234. At least one memory is provided in each device, and indicated as 1215, 1225, and 1235, respectively. The memory may include computer program instructions or computer code contained therein. Transceivers 1216, 1226, and 1236 are provided, and each device may also include an antenna, respectively illustrated as 1217, 1227, and 1237. Other configurations of these devices, for example, may be provided. For example, PCRF 1210, P-GW/GGSN-I 1220, and other P-GW/GGSN 1230 may be configured for wired communication, rather than wireless communication, and in such a case antennas 1217, 1227, and 1237 would illustrate any form of communication hardware, without requiring a conventional antenna.

[0066] Transceivers 1216, 1226, and 1236 can each, independently, be a transmitter, a receiver, or both a transmitter and a receiver, or a unit or device that is configured both for transmission and reception.

[0067] Processors 1214, 1224, and 1234 can be embodied by any computational or data processing device, such as a central processing unit (CPU), application specific integrated circuit (ASIC), or comparable device. The processors can be implemented as a single controller, or a plurality of controllers or processors.

[0068] Memories 1215, 1225, and 1235 can independently be any suitable storage device, such as a non-transitory computer-readable medium. A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory can be used. The memories can be combined on a single integrated circuit as the processor, or may be separate therefrom. Furthermore, the computer program instructions stored in the memory and which may be processed by the processors can be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.

[0069] The memory and the computer program instructions can be configured, with the processor for the particular device, to cause a hardware apparatus such as PCRF 1210, P-GW/GGSN-I 1220, and other P-GW/GGSN 1230, to perform any of the processes described above (see, for example, Figures 3-11). Therefore, in certain embodiments, a non-transitory computer-readable medium can be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain embodiments of the invention can be performed entirely in hardware.

[0070] Furthermore, although Figure 12 illustrates a system including a PCRF, P-GW/GGSN-I, and other P-GW/GGSN, embodiments of the invention may be applicable to other configurations, and configurations involving additional elements, as illustrated herein, for example in Figures 1-6.

[0071] One having ordinary skill in the art will readily understand that the invention as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the invention has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the invention. In order to determine the metes and bounds of the invention, therefore, reference should be made to the appended claims.

[0072] Glossary

[0073] PCRF - Policy and Charging Rules function

[0074] P-GW - Packet Data Network Gateway

[0075] GGSN - Gateway GPRS Support Node

[0076] OCS - Online charging system

[0077] MME - Mobility Management Entity

[0078] SGSN - Serving GPRS Support Node

[0079] SPR - Subscription Profile Repository

[0080] AAA - Authentication, Authorization and Accounting

[0081 ] HSS - Home Subscriber Server

Claims

WE CLAIM:

1. A method, comprising:

determining that a group is connected to a plurality of gateway nodes, wherein the group comprises a plurality of user equipment; and

monitoring data usage of user equipments of the group, based on the determination.

2. The method of claim 1, further comprising:

taking an action selected from charging of users associated with the group or informing users associated with the group, when the monitored data usage exceeds a predetermined threshold.

3. The method of claim 1 or claim 2, wherein the monitoring the group comprises a single policy and charging rules function monitoring the group.

4. The method of any of claims 1-3, wherein the monitoring comprises at least one of registering for time based monitoring with the plurality of nodes or registering for data threshold based reporting.

5. The method of claim 4, wherein the allocation threshold is uniform for all gateway nodes or is based on a number of group members served by a respective gateway node or the data usage pattern of group members.

6. The method of claim 4 or claim 5, further comprising:

determining that an allocation is exceeded for a first gateway node; and rebalancing allocation amongst the plurality of gateway nodes based on the determination that the allocation is exceeded.

7. The method of any of claims 4-6, further comprising:

determining that a user equipment is connected to a second gateway that does not have a budget allocation; and

rebalancing allocation amongst the plurality of gateway nodes, including the second node, based on the determination that the second gateway node did not have a budget allocation.

8. The method of any of claims 1-7, further comprising:

reporting to an application server that requested the monitoring, when the monitoring indicates that the data usage has reduced an available data usage below a threshold.

9. The method of any of claims 1-8, further comprising:

storing, in a subscription profile repository, an authentication, authorization and accounting server or a home subscriber server, an identifier of a policy and charging rules function corresponding to the group.

10. The method of claim 9, wherein the identifier comprises an address of the policy and charging rules function.

11. The method of claim 10, further comprising:

delivering the address of the policy and charging rules function to the home subscriber server via a serving node.

12. The method of claim 11, further comprising:

receiving a subsequent request;

obtaining the address of the policy and charging rules function by the serving node from the home subscriber server, wherein the serving node selects the gateway and forwards the address of the policy and charging rules function to the gateway.

13. The method of any of claims 1-12, further comprising: maintaining an allocated bandwidth of the group in an online charging system.

14. A method, comprising:

determining that a user equipment is associated with a group; and selecting a common policy and charging rules function for user equipment based on the association with the group.

15. The method of claim 14, wherein the selecting comprises a gateway node selecting a policy and charging rules function for a first member of the group.

16. The method of claim 14 or claim 15, wherein the selecting comprises an authentication server or a home subscriber server selecting the policy and charging rules function for a second or subsequent member of the group.

17. An apparatus, comprising:

at least one processor; and

at least one memory including computer program code,

wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to determine that a group is connected to a plurality of gateway nodes, wherein the group comprises a plurality of user equipments; and

monitor data usage of user equipments of the group, based on the determination.

18. The apparatus of claim 17, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to take an action selected from charging of users associated with the group or informing users associated with the group, when the monitored data usage exceeds a predetermined threshold.

19. The apparatus of claim 17 or claim 18, wherein the monitoring the group comprises a single policy and charging rules function monitoring the group.

20. The apparatus of any of claims 17-19, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to monitor by registering for time based monitoring with the plurality of nodes or registering for data threshold based reporting.

21. The apparatus of claim 20, wherein the allocation threshold is uniform for all gateway nodes or is based on a number of group members served by a respective gateway node or the data usage pattern of group members.

22. The apparatus of claim 20 or claim 21, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to

determine that an allocation is exceeded for a first gateway node; and rebalance allocation amongst the plurality of gateway nodes based on the determination that the allocation is exceeded.

23. The apparatus of any of claims 20-22, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to

determine that a user equipment is connected to a second gateway that does not have a budget allocation; and rebalance allocation amongst the plurality of gateway nodes, including the second node, based on the determination that the second gateway node did not have a budget allocation.

24. The apparatus of any of claims 17-23, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to report to an application server that requested the monitoring, when the monitoring indicates that the data usage has reduced an available data usage below a threshold.

25. The apparatus of any of claims 17-24, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to store, in a subscription profile repository, an authentication, authorization and accounting server or a home subscriber server,, an identifier of a policy and charging rules function corresponding to the group.

26. The apparatus of claim 25, wherein the identifier comprises an address of the policy and charging rules function.

27. The apparatus of claim 26, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to deliver the address of the policy and charging rules function to the home subscriber server via a serving node.

28. The apparatus of claim 27, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to receive a subsequent request and obtain the address of the policy and charging rules function by the serving node from the home subscriber server, wherein the serving node selects the gateway and forwards the address of the policy and charging rules function to the gateway.

29. The apparatus of any of claims 17-28, further comprising:

maintaining an allocated bandwidth of the group in an online charging system.

30. An apparatus, comprising:

at least one processor; and

at least one memory including computer program code,

wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to determine that a user equipment is associated with a group; and select a common policy and charging rules function for user equipment based on the association with the group.

31. The apparatus of claim 30, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to selecting by a gateway node selecting a policy and charging rules function for a first member of the group.

32. The apparatus of claim 30 or claim 31, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to select by an authentication server or a home subscriber server selecting the policy and charging rules function for a second or subsequent member of the group.

33. An apparatus, comprising:

determining means for determining that a group is connected to a plurality of gateway nodes, wherein the group comprises a plurality of user equipment; and monitoring means for monitoring data usage of user equipments of the group, based on the determination.

34. The apparatus of claim 33, further comprising:

response means for taking an action selected from charging of users associated with the group or informing users associated with the group, when the monitored data usage exceeds a predetermined threshold.

35. The apparatus of claim 33 or claim 34, wherein the monitoring the group comprises a single policy and charging rules function monitoring the group.

36. The apparatus of any of any of claims 33-35, wherein the monitoring comprises at least one of registering for time based monitoring with the plurality of nodes or registering for data threshold based reporting.

37. The apparatus of claim 36, wherein the allocation threshold is uniform for all gateway nodes or is based on a number of group members served by a respective gateway node or the data usage pattern of group members.

38. The apparatus of claim 36 or claim 37, further comprising:

determining means for determining that an allocation is exceeded for a first gateway node; and

rebalancing means for rebalancing allocation amongst the plurality of gateway nodes based on the determination that the allocation is exceeded.

39. The apparatus of any of claims 36-38, further comprising:

determining means for determining that a user equipment is connected to a second gateway that does not have a budget allocation; and rebalancing means for rebalancing allocation amongst the plurality of gateway nodes, including the second node, based on the determination that the second gateway node did not have a budget allocation.

40. The apparatus of any of claims 33-39, further comprising:

reporting means for reporting to an application server that requested the monitoring, when the monitoring indicates that the data usage has reduced an available data usage below a threshold.

41. The apparatus of any of claims 33-40, further comprising:

storing means for storing, in a subscription profile repository, an authentication, authorization and accounting server or a home subscriber server, an identifier of a policy and charging rules function corresponding to the group.

42. The apparatus of claim 41, wherein the identifier comprises an address of the policy and charging rules function.

42. The apparatus of claim 42, further comprising:

delivering means for delivering the address of the policy and charging rules function to the home subscriber server via a serving node.

44. The method of claim 43, further comprising:

receiving means for receiving a subsequent request;

obtaining means for obtaining the address of the policy and charging rules function by the serving node from the home subscriber server, wherein the serving node selects the gateway and forwards the address of the policy and charging rules function to the gateway.

45. The apparatus of any of claims 33-44, further comprising: maintaining means for maintaining an allocated bandwidth of the group in an online charging system.

46. An apparatus, comprising:

determining means for determining that a user equipment is associated with a group; and

selecting means for selecting a common policy and charging rules function for user equipment based on the association with the group.

47. The apparatus of claim 46, wherein the selecting comprises a gateway node selecting a policy and charging rules function for a first member of the group.

48. The apparatus of claim 46 or claim 47, wherein the selecting comprises an authentication server or a home subscriber server selecting the policy and charging rules function for a second or subsequent member of the group.

49. A non-transitory computer readable medium encoded with instructions that, when executed in hardware, perform a process, the process comprising the method of any of claims 1-16.