Modeling radio access networks

Abstract

A method, a computer program product and a device, the method is for evaluating a state of a radio access network (RAN), and may include parsing control plane massages that are exchanged between the RAN and a core network that is coupled to the RAN; and determining, by an edge bandwidth manager, a current state of the RAN based on the control plane massages.

Claims

1. A method for evaluating a state of a radio access network (RAN), the method comprising: parsing, by a parser of an edge bandwidth manager, control plane messages that are exchanged between the RAN and a core network that is coupled to the RAN; determining, by an edge bandwidth management module of the edge bandwidth manager, a current state of the RAN based on the control plane messages; wherein the edge bandwidth manager does not belong to the RAN and does not belong to the core network; wherein the determining comprises detecting by the edge bandwidth manager a potential congestion situation at a target cell of the RAN in response to a detection of users transitioning from an idle mode to active mode and an estimation that the transitioning will cause congestion; and detecting by the edge bandwidth manager a potential congestion situation at a target cell of the RAN in response to a number of users being handed over from one cell to the target cell, wherein the detecting occurs before the users move to the target cell wherein the number of users exceeds two; and wherein the edge bandwidth management module is a computer that is configured to execute instructions stored on a non-transitory computer readable medium.

2. The method according to claim 1, wherein the core network comprises a Serving Gateway (SGW) and a Mobility Management Entity (MME), wherein the RAN comprises an enhanced node B (eNodeB); and wherein the method comprises intercepting control plane messages that are exchanged between the eNodeB and the MME and the control plane messages that are exchanged between user equipment (UE) and the MME.

3. The method according to claim 1, comprising receiving the control plane messages from a backhaul aggregator router or switch.

4. The method according to claim 1, wherein the determining of the current state of the RAN comprises determining, about at least one cell of the RAN, the following parameters: cell identifier (ID); routing Area Code; Radio Network Controller (RNC) ID; NodeB ID; total number of active users; total number of idle users; total number of packet data protocol (PDP) contexts; maximum downlink bandwidth; maximum uplink bandwidth; aggregate downlink bandwidth in use; and aggregate uplink bandwidth in use.

5. The method according to claim 1, comprising determining, about at least one session of at least one user of the RAN, the following parameters: International Mobile Subscriber Identity (IMSI); Pseudo Temporary Mobile Subscriber Identity (P-TMSI); International Mobile station Equipment Identity (IMEI); User Equipment (UE) Internet Protocol (IP) address; Access Point Name (APN); Network layer Service Access Point Identifier (NSAPI) location information; negotiated quality of service (QoS); Mobile Station international Public Switched Telephone Network (PSTN) or Integrated Services Digital Network (ISDN) number; General Packet Radio Services Tunneling Protocol (GPRS) tunnel information; aggregate downlink bandwidth in use and aggregate uplink bandwidth in use.

6. The method according to claim 1, comprising requesting, by the edge bandwidth manager from a RAN entity to re-allocate a user between cells in response to a detection of the potential congestion situation.

7. A computer program product that comprises a non-transitory computer readable medium that stores instructions for: parsing control plane messages that are exchanged between a Radio Access Network (RAN) and a core network that is coupled to the RAN; and determining, by an edge bandwidth manager that does not belong to the RAN and does not belong to the core network, a current state of the RAN based on the control plane messages; wherein the determining comprises detecting by the edge bandwidth manager a potential congestion situation at a target cell of the RAN in response to a detection of users transitioning from an idle mode to active mode and an estimation that the transitioning will cause congestion; and detecting by the edge bandwidth manager a potential congestion situation at a target cell of the RAN in response to a number of users being handed over from one cell to the target cell, wherein the detecting occurs before the users move to the target cell wherein the number of users exceeds two.

8. The computer program product according to claim 7, wherein the core network comprises a Serving Gateway (SGW) and a Mobility Management Entity (MME), wherein the RAN comprises an enhanced node B (eNodeB); and wherein the non-transitory computer readable medium stores instructions for intercepting control plane messages that are exchanged between the eNodeB and either one of the SGW and the MME.

9. The computer program product according to claim 7, wherein the non-transitory computer readable medium stores instructions for receiving the control plane messages from a backhaul aggregator server or switch.

10. The computer program product according to claim 7, wherein the non-transitory computer readable medium stores instructions for determining, about at least one cell of the RAN, the following parameters: cell identifier (ID); routing Area Code; Radio Network Controller (RNC) ID; NodeB ID; total number of active users; total number of idle users; total number of packet data protocol (PDP) contexts; maximum downlink bandwidth; maximum uplink bandwidth; aggregate downlink bandwidth in use; and aggregate uplink bandwidth in use.

11. The computer program product according to claim 7, wherein the non-transitory computer readable medium stores instructions for determining, about at least one session of at least one user of the RAN, the following parameters: International Mobile Subscriber Identity (IMSI); Pseudo Temporary Mobile Subscriber Identity (P-TMSI); International Mobile station Equipment Identity (IMEI); User Equipment (UE) Internet Protocol (IP) address; Access Point Name (APN); Network layer Service Access Point Identifier (NSAPI) location information; negotiated quality of service (QoS); Mobile Station international Public Switched Telephone Network (PSTN) or Integrated Services Digital Network (ISDN) number; General Packet Radio Services Tunneling Protocol (GPRS) tunnel information; aggregate downlink bandwidth in use and aggregate uplink bandwidth in use.

12. The computer program product according to claim 7, wherein the non-transitory computer readable medium stores instructions for requesting, by the edge bandwidth manager from a RAN entity to re-allocate a user between cells in response to a detection of the potential congestion situation.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof may best be understood by reference to the following detailed description when read with the accompanying drawings in which:

(2) FIG. 1 illustrates a prior art 4G wireless network that is coupled to the Internet;

(3) FIG. 2 illustrates a system and its environment according to an embodiment of the invention;

(4) FIG. 3 illustrates a system and its environment according to an embodiment of the invention;

(5) FIG. 4 illustrates a system and its environment according to an embodiment of the invention;

(6) FIG. 5 illustrates a system and its environment according to an embodiment of the invention;

(7) FIG. 6 illustrates a method according to an embodiment of the invention;

(8) FIG. 7 illustrates a method according to an embodiment of the invention;

(9) FIG. 8 illustrates a system and its environment according to an embodiment of the invention; and

(10) FIG. 9 illustrates a system and its environment according to an embodiment of the invention.

(11) It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements.

DETAILED DESCRIPTION OF THE DRAWINGS

(12) The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference to the following detailed description when read with the accompanying drawings.

(13) It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements.

(14) In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, and components have not been described in detail so as not to obscure the present invention.

(15) The term “modeling” can have its regular meaning and can be interpreted as including generation of information that represents a status of an entity. The status can reflect one or a plurality of parameters and their values. A model of an entity of a Radio Access Network can change over time.

(16) The following abbreviations are being used: APN Access Point Name EBM Edge Bandwidth Manager BSC Base Station Controller eNB eNodeB GGSN Gateway GPRS Support Node GPRS General Packet Radio Services GTP GPRS Tunneling Protocol IMEI International Mobile station Equipment Identity IMSI International Mobile Subscriber Identity ISDN Integrated Services Digital Network MME Mobility Management Entity MS Mobile Station MSISDN MS international PSTN/ISDN number NAS Non-Access Stratum NSAPI Network layer Service Access Point Identifier PCF Packet Control Function PDN Packet Data Network PDSN Packet Data Serving Node P-GW PDN Gateway PSTN Public Switched Telephone network P-TMSI Pseudo Temporary Mobile Subscriber Identity QoS Quality of Service RAC Routing Area Code RAN Radio Access Network RANAP Radio Access Network Application Part RNC Radio Network Controller SGW Serving Gateway SGSN Serving GPRS Support Node TEID Tunnel End Point Identifier UE User Equipment

(17) Existing optimizing solutions have not taken into account the RAN condition before applying optimization techniques. The suggested systems, computer program products and methods can accurately model a Radio Access Network. By taking into account the RAN condition, it is possible to make better decisions on optimizing the data and video traffic. The right optimization tools can be used depending on whether a particular radio cell is underutilized or saturated.

(18) The disclosed systems, computer program products and methods may not disrupt existing network elements in the core network and in the radio network. The Edge Bandwidth Manager (and the control plane probe) may be transparent to the existing network elements. The existing network elements do not have to be upgraded.

(19) The system, edge bandwidth manager, method and computer program product described in this document is related to dynamically managing bandwidth in a 3G or 4G Radio network based on accurately determining the current state of the RAN.

(20) The herein disclosed solutions involve inserting a new network element between the RAN and a core network. The new network element (hereinafter referred to as Edge Bandwidth Manager) conveniently parses all control plane messages between the RAN and the core network to accurately model the RAN, and determines its current state. This includes determining the current bandwidth utilization in the RAN.

(21) According to various embodiments of the invention a system can be provided and may include a probe, arranged to parse control plane massages that are exchanged between a Radio Access Network (RAN) and a core network that is coupled to the RAN; and an edge bandwidth manager arranged to determine a current state of the RAN based on the control plane massages.

(22) According to an embodiment of the invention an edge bandwidth manager is provided and may include a parser, arranged to parse control plane massages that are exchanged between the RAN and a core network that is coupled to the RAN; and an edge bandwidth management entity arranged to determine a current state of the RAN based on the control plane massages. The data plane traffic may also be taken into account to accurately model the RAN and determine the state of the RAN.

(23) The system, edge bandwidth manager, method and computer program product described herein can accurately model a RAN network, so that any optimization solution takes into account the state of the RAN.

(24) It is noted that the proposed systems and methods are applicable to various types of networks, and especially both 3G and 4G networks. In case of 3G networks, the Edge Bandwidth Manager is placed between the Radio Network Controller (RNC) and the Serving GPRS Support Node (SGSN). The interface between the RNC and the SGSN is referred to as the IuPS interface. The Edge Bandwidth Manager parses all IuPS signaling messages between the RNC and the SGSN. This includes RANAP protocol messages between the SGSN and the RNC and the NAS signaling messages between the SGSN and the end User Equipment (UE).

(25) FIG. 2 illustrates Edge Bandwidth Manager (EBM) 140, core network 100 and RAN 190 according to an embodiment of the invention.

(26) EBM 140 may include an interceptor (such as a probe) 144 for intercepting control plane messages, parser 144 for parsing the control plane messages and a edge bandwidth management module 142 for processing the control plane messages in order to evaluate to state of the RAN. EBM 140 is illustrated as being coupled to IuPS 136 interfaces.

(27) It is noted that the EBM 140 may also track after user data sessions and that EBM 140 can also perform various operations in response to the state of the RAN, such as congestion estimation, congestion prevention, and the like.

(28) The EBM 140 may enforce bandwidth management decisions it makes. For example, the EBM 140 models the RAN, and in response to the model it can allocate a target bit rate for each application session. The EBM 140 then tries to enforce the bit rate for the application session using various techniques. The technique used depends on the type of application session. The EBM 140 may control the bit rate on both directions—uplink and downlink. Thus, a stream that is intended to be provided from the core network to the RAN can be compressed, delayed, statistically multiplexed with other streams before it passes towards the RAN. The same applies to streams that are sent from the RAN to the core network. Additionally or alternatively, the EBM 140 can send bit rate allocation values to entities of the core network and/or to entities of the RAN and request these entities to enforce these bit rate allocation values.

(29) The core network 100 is illustrated as including an operator PDN 110 such as the Internet or a private packet data network, GGSN 120 and SGSN 130. The GGSN 120 is coupled between the operator PDN 110 and the SGSN 130.

(30) The RAN 190 includes a RNC 160 that is coupled to multiple base stations 170 that in turn are wirelessly coupled to mobile stations 180.

(31) The EBM 140 can be placed closer to either the SGSN 130 or the RNC 160. There is no restriction on its physical placement. Additionally, the functions of the EBM 140 can be implemented within the SGSN 130 or the RNC 160.

(32) In the case of 4G networks, the EBM 140 can be placed between the eNodeB, the MME/SGW (Serving Gateway).

(33) FIG. 3 illustrates EBM 140 as being coupled to eNodeB 212, ePDG 216, MME 218 and SGW 220.

(34) The EBM 140 parses all S1 messages between the eNodeB 212 and the core network (Internet 230). This includes S1-AP messages between the MME 218 and the eNodeB 212, and the NAS signaling messages between the MME 218 and the UE 210.

(35) The EBM 140 can be placed closer to either the core network nodes like the MME 218 and the SGW 220 or closer to the eNodeB 212. Additionally, the EBM can be implemented within these devices.

(36) The UE 210 is also sometimes called the Mobile Station (MS). It can be any device (including cell phones, laptop modems) that can attach to a 3G or a 4G network.

(37) FIGS. 2 and 3 illustrate in-path configurations according to two embodiments of the invention, in which all traffic between the RAN and the core network passes through the EBM 140.

(38) It is also possible to place the EBM in an out-of-path mode, where the EBM is co-located with an aggregation router/switch on the backhaul link. The aggregation router is configured to send specific packets (or in some cases all packets) to the Edge Bandwidth Manager. Once the EBM is done with parsing the messages, they are sent back to the aggregation router and from there to the original destination. The out-of-path approach has an advantage that if the EBM fails, it does not cause any impact to the rest of the network. An out-of-path approach in a 3G wireless network is shown in FIG. 4.

(39) FIG. 4 illustrates an out-of-path approach for 3G networks, according to an embodiment of the invention. FIG. 4 differs from FIG. 2, by having a backhaul aggregator router or switch 150 coupled between the SGSN 130 and the RNC 160 (instead of the EBM 140 being coupled between these elements) and having the EBM 140 coupled to the backhaul aggregator router or switch 150.

(40) The out-of-path approach can also be achieved using an Optical Bypass Switch or Network Tap.

(41) The out-of-path configuration can also be applied to the 4G wireless network.

(42) According to another embodiment of the invention the EBM may also monitor user plane traffic, both uplink and downlink, between the RAN and the core network.

(43) In case of 3G networks, the EBM monitors the user plane traffic on the Iu-U interface between the RNC and the SGSN or between RNC and the GGSN, in case Direct Tunnel architecture is used. In case of 4G networks, the EBM monitors the user plane traffic on the S1-U interface between the eNodeB and the Serving Gateway.

(44) The EBM at any time maintains an accurate picture of the RAN. On a per radio cell basis, it maintains the following information.

(45) Cell Information: Cell ID, Routing Area Code, RNC ID, NodeB ID, Total number of Active Users, Total number of Idle Users, Total number of PDP contexts, Maximum downlink bandwidth, Maximum uplink bandwidth, Aggregate downlink bandwidth in use, and Aggregate uplink bandwidth in use.

(46) Each piece of information described above may be obtained by parsing the relevant control plane messages and the data plane traffic. For example, in a 3G GSM network, the Cell ID is obtained from the NAS and RANAP messages exchanged on the IuPS interface. The number of active and idle users in a cell is determined based on observing state transitions for each UE in the cell. The bandwidth consumption parameters, is determined by parsing the data plane and figuring out how much bandwidth is being consumed at any point.

(47) A per-radio cell information such as the one described above may be used by the EBM to figure out how much additional capacity is available in the cell. The radio cell is also called a “Sector”. Note that “Cell” and “Sector” are used interchangeably in this document.

(48) A typical base station configuration has three sectors. Six sectors per base station are also possible. It also allows the EBM to predict congestion situations and take corrective actions, thereby preventing congestion in a particular cell. In addition, the information present in the table above can be used to move certain users from a cell which is saturated to another cell that is underutilized, if the user is a location where the two cells overlap.

(49) The per-cell information may be is constantly updated in real-time based on the mobility and other signaling between the RAN and the core network and the data traffic consumed by the users. The per-cell information listed above is not exhaustive.

(50) The EBM also maintains the user session state that may include at least some (or all) of the following parameters: International Mobile Subscriber Identity (IMSI); Pseudo Temporary Mobile Subscriber Identity (P-TMSI); International Mobile station Equipment Identity (IMEI); User Equipment (UE) Internet Protocol (IP) address; Access Point Name (APN); Network layer Service Access Point Identifier (NSAPI) location information; negotiated quality of service (QoS); Mobile Station international Public Switched Telephone Network (PSTN) or Integrated Services Digital Network (ISDN) number; General Packet Radio Services Tunneling Protocol (GPRS) tunnel information; aggregate downlink bandwidth in use and aggregate uplink bandwidth in use.

(51) Each piece of information described in the previous paragraph may be obtained by parsing the relevant control plane messages and the traffic generated by the user. For example, in a 3G GSM network, the subscriber IMSI is obtained by parsing the Attach Request NAS message from the UE to the SGSN. Another example is the APN information that is obtained from the Activate PDP Context Request NAS message sent from the UE to the SGSN.

(52) Per-session information may be is constantly updated in real-time based on the mobility and other signaling between the RAN and the core network and the data traffic consumed by each session. The information listed above is not exhaustive.

(53) As mentioned previously, the EBM constructs per-cell and per-cell information (e.g. as described in Tables 1 and 2) by processing control and user plane traffic between the RAN and the core network.

(54) The following describes in more details a method for constructing this information, according to an embodiment of the invention. 1. When the UE is powered on, it attaches to an SGSN. One of the first messages it sends is the Attach Request message. The subscriber identity and the location information are available in the Attach Request Message. 2. There are subsequent Identity Request and Check procedures, where the subscriber's actual IMSI and the IMEI information is obtained. 3. The session information is obtained when the subscriber sets up a session using the Activate PDP context procedure. This information obtained includes, the user's APN, NSAPI, requested QoS, UE IP address, and etc., 4. The tunnel information for the GTP tunnel between the RNC and the SGSN is obtained by parsing the RANAP messages related to the RAB Assignment procedure. These messages are exchanged between the RNC and the SGSN. 5. The EBM also parses messages related to the UE detaching or tearing down a session.

(55) As users move around in the radio network, the EBM keeps track of which cell each user is at any time, so that it knows accurately how many users are in a particular radio cell.

(56) The following describes how the EBM keeps track of mobility related information, according to an embodiment of the invention: 1. When the UE is about to move into a new routing area (tracking area in case of 4G networks), the EBM parses all messages related to routing area update procedure. This allows the EBM to figure out which cell the user is moving in to at any time. This also allows the EBM to keep track of the current cell the UE is in at any time. 2. When the UE is about to move in to a new location that results in a change of RNC, the EBM parses all inter-RNC handover messages. This allows the EBM to get updated GTP tunnel information and information exchanged between the source RNC and the target RNC. 3. The EBM also parses handover messages related to inter-NodeB handovers, so that it has the current routing area and cell information. 4. The EBM also processes all messages related to location reporting between the RNC and the SGSN.

(57) In addition to processing the control plane messages, the EBM may also monitor how much data traffic (both downlink and uplink) is being sent/consumed by each user on the user plane. By mapping each user's session to a cell, and the downlink and uplink bandwidth associated with each session, the Edge Bandwidth Managers computes the aggregate bandwidth that is being consumed at any time for each cell.

(58) The maximum bandwidth available per cell is configured on the EBM on a per-cell basis. There are a couple of alternate options instead of having to configure the EBM on a per-cell basis. In the first option, the EBM obtains this information from a central database through LDAP or similar mechanism. The central database has information on how much total bandwidth is available per cell. In the second option, the EBM obtains information about the base station, more specifically what frequency it is configured with, how many antennas are installed, etc., and then figures out the total bandwidth available on the cell based on the base station information. The frequency range, and the antenna configuration is used by the EBM to figure out the maximum bandwidth available per cell. Based on the total bandwidth available in a cell and the current bandwidth consumption in the cell, the EBM figures out if a particular cell is saturated or underutilized.

(59) By looking at the mobility patterns, the EBM is also able to predict congestion in a cell before it happens. For example, when it sees a number of users being handed over from one cell to another, it can predict the impact on the target cell before the users move to the target cell. Based on the impact to the target cell, the EBM can start taking corrective actions before the handover event happens. This allows the EBM to predict congestion and prevent it before it happens in any particular cell. Another example is based on idle to active mode transitions. When the EBM sees a user or a number of users transitioning from the idle to active mode, it can predict the impact of the new sessions on the cell and start taking corrective actions if it predicts congestion on the cell.

(60) For 4G networks, the EBM may process the messages corresponding to NAS attach procedure, identity request procedure, S1 GTP tunnel setup messages, inter-eNodeB handovers and tracking area update procedures. This is very similar to what is described above in 3G.

(61) The solution described in this document does not restrict the placement of the EBM. The EBM functionality can be split into a plurality (for example—two) network elements, where the main bandwidth management and RAN assessment function (such as the edge bandwidth management module 142 of FIG. 2) may be centrally located and a control plane probe 144 that monitors RAN related signaling is placed much closer to/or in the radio network. For example, the EBM function can be placed between the GGSN and the operator.

(62) The Gi interface can be used for forwarding packets to external networks, including the Internet. The control plane probe 144 can be placed on the interface between the RAN and the core network—as illustrated in FIG. 5. FIG. 5 illustrates an edge bandwidth management module 142 that is being coupled between the operator PDN 110 and the GGSN 120, while the probe 144 is coupled between the SGSN 130 and the RNC 160.

(63) According to such an embodiment of the invention, the control plane probe 144 parses all signaling messages between the RAN 190 and the core network and provides a summary of the RAN conditions to the Edge Bandwidth Management module 142. It is also possible for the control plane probe to just forward a copy of all control plane messages to the Edge Bandwidth Management module 142. In this case, the control plane messages are actually processed on the Edge Bandwidth Management module to model the RAN 190. The control plane probe 144 does not process these messages. In case of 4G networks, the EBM is placed on the SGi interface between the PGW and the operator services/Internet with the control plane probe on the S1 interface.

(64) When the control plane is placed on the interface between the RAN and the core network, it can be placed either close to the core network nodes like the SGSN, SGW or MME or closer to the RAN network. It can also be placed inside the RAN network between the base stations and the RNC.

(65) The control plane probe shown in FIG. 4 can be also co-located with existing network elements like the MME, the SGSN or the RNC. Then it becomes a software function on the existing network elements.

(66) FIG. 6 illustrates method 500 according to an embodiment of the invention. Method 500 is for evaluating a state of a radio access network (RAN).

(67) Method 500 may start by stage 510 of intercepting or receiving control plane messages that are exchanged between the RAN and a core network that is coupled to the RAN.

(68) Stage 510 may include intercepting the control plane messages or receiving the control messages from another entity (such as an aggregator or a probe) that intercepts the control plane messages. The intercepting is done in a non-intrusive manner in the sense that the control plane messages arrive to their intended destination without being changed.

(69) This is partially illustrated by stages 512 and 514. Stage 512 includes intercepting the control plane messages by a probe and sending the control plane messages from the probe to the edge bandwidth manager. The probe can be include din the edge bandwidth manager, located at the same location, positioned in a remote location, and the like.

(70) Stage 514 includes receiving the control plane messages from an aggregator.

(71) The core network can be a General Packet Radio Service (GPRS) network. Stage 510 may include intercepting control plane messages that are exchanged between a radio network controller (RNC) that is arranged to control the RAN and a Service GPRS Support Node (SGSN).

(72) The core network can be a Serving Gateway (SGW) and a Mobility Management Entity (MME), wherein the RAN comprises an enhanced node B (eNodeB). Stage 510 may include intercepting control plane messages that are exchanged between the eNodeB and either one of the SGW and the MME.

(73) Stage 510 is followed by stage 520 of parsing the control plane massages (that were exchanged between the RAN and the core network).

(74) Stage 520 is followed by stage 530 of determining, by an edge bandwidth manager, a current state of the RAN based on the control plane massages.

(75) FIG. 7 illustrates method 600 according to an embodiment of the invention. Method 600 is for evaluating a state of a radio access network (RAN).

(76) Method 600 may start by stages 510 and 610. Stage 510 may include intercepting or receiving control plane messages that are exchanged between the RAN and a core network that is coupled to the RAN.

(77) Stage 610 may include monitoring user plane traffic that is exchanged between the RAN and the core network.

(78) Stages 510 and 610 are followed by stage 520 of parsing the control plane massages (that were exchanged between the RAN and the core network).

(79) Stage 520 is followed by stage 630 of determining, by an edge bandwidth manager, a current state of the RAN based on the control plane massages and the user plane traffic.

(80) Stage 630 may include stage 631 of determining bandwidth utilization in the RAN.

(81) Stage 631 may include determining the aggregate bandwidth, the available bandwidth or any bandwidth statistics per RAN, per cell, per session, per a group of users and the like.

(82) Stage 630 may include stage 632 of estimating a maximal capacity of a cell based on frequency and hardware information.

(83) Stage 630 may include stage 633 of determining of the current state of the RAN comprises determining, about at least one cell of the RAN, a plurality (for example—at least four parameters) of the following parameters: Cell ID, Routing Area Code, RNC ID, NodeB ID, Total number of Active Users, Total number of Idle Users, Total number of PDP contexts, Maximum downlink bandwidth, Maximum uplink bandwidth, Aggregate downlink bandwidth in use, and Aggregate uplink bandwidth in use.

(84) Stage 630 may include stage 634 of determining, about at least one session of at least one user of the RAN, a plurality (for example—at least four) parameters of the following parameters: IMSI/P-TMSI, IMEI, UE IP Address, IuPS/S1 GTP Tunnel information, APN, NSAPI Location Information, Negotiated QoS, MSISDN, Aggregate downlink bandwidth in use, and Aggregate uplink bandwidth in use

(85) Stage 630 may include stage 635 of detecting a potential congestion situation.

(86) Stage 635 may be followed by stage 640 of re-allocating a user between cells in response to a detection of the potential congestion situation or assisting in the re-allocating of such user. The re-allocating can include requesting a RAN entity (such as a controller) to perform the re-allocation.

(87) According to an embodiment of the invention a computer program product is provided. The computer program product includes a non-transitory computer readable medium that may store instructions for parsing control plane massages that are exchanged between a Radio Access Network (RAN) and a core network that is coupled to the RAN; and determining, by an edge bandwidth manager, a current state of the RAN based on the control plane massages.

(88) The non-transitory computer readable medium may store instructions for at least one of the following: 1. Determining bandwidth utilization in the RAN. 2. Intercepting the control plane messages by a probe and sending the control plane messages from the probe to the edge bandwidth manager. 3. Receiving the control plane messages from an aggregator. 4. Monitoring user plane traffic that is exchanged between the RAN and the core network. 5. Determining, based on the control plane massages and the user traffic plane, a bandwidth utilization of a cell of the RAN. 6. Evaluating an available bandwidth of a cell of the RAN. 7. Detecting a potential congestion situation. 8. Re-allocating a user between cells in response to a detection of the potential congestion situation. 9. Estimating a maximal capacity of a cell based on frequency and hardware information. 10. Determining, about at least one cell of the RAN, multiple (for example—at least four) parameters of the following parameters: cell identifier (ID); routing Area Code; Radio Network Controller (RNC) ID; NodeB ID; total number of active users; total number of idle users; total number of packet data protocol (PDP) contexts; maximum downlink bandwidth; maximum uplink bandwidth; aggregate downlink bandwidth in use; and aggregate uplink bandwidth in use. 11. Determining, about at least one session of at least one user of the RAN, at least four parameters of the following parameters: International Mobile Subscriber Identity (IMSI); Pseudo Temporary Mobile Subscriber Identity (P-TMSI); International Mobile station Equipment Identity (IMEI); User Equipment (UE) Internet Protocol (IP) address; Access Point Name (APN); Network layer Service Access Point Identifier (NSAPI) location information; negotiated quality of service (QoS); Mobile Station international Public Switched Telephone Network (PSTN) or Integrated Services Digital Network (ISDN) number; General Packet Radio Services Tunneling Protocol (GPRS) tunnel information; aggregate downlink bandwidth in use and aggregate uplink bandwidth in use.

(89) The core network can be a General Packet Radio Service (GPRS) network and the non-transitory computer readable medium can store instructions for intercepting control plane messages that are exchanged between a radio network controller (RNC) that is arranged to control the RAN and a Service GPRS Support Node (SGSN).

(90) The core network can be a Serving Gateway (SGW) and a Mobility Management Entity (MME), the RAN comprises an enhanced node B (eNodeB). The non-transitory computer readable medium can store instructions for intercepting control plane messages that are exchanged between the eNodeB and either one of the SGW and the MME.

(91) FIGS. 8 and 9 illustrate EBM 140 in various CDMA 3G networks, according to various embodiments of the invention. The CDMA 3G network includes a Base Station Controller (BSC) 718, a Packet Control Function (PCF) 716, a Packet Data Serving Node (PDSN) 714 and a home agent 710.

(92) FIG. 7 illustrates the EBM 140 as being placed on the A10/A11 interface between the PCF 716 and the PDSN 714. The EBM 140 may parse all the A11 control plane messages exchanged between the PCF 716 and the PDSN 714 to model the RAN that includes the BSC 718 and the base stations controlled by the BSC.

(93) FIG. 8 illustrates the EBM 140 as being placed on the A8/A9 interface between the BSC 718 and the PCF 716. The EBM may parse the A9 control plane messages exchanged between the BSC 718 and the PCF 716.

(94) While certain features of the invention have been illustrated and described herein, many modifications, substitutions, changes, and equivalents will now occur to those of ordinary skill in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention.