Abstract:
A Mobile Control Entity ( 125, 225 ) for a system ( 100, 200 ), arranged to communicate with a first Mobile Gateway ( 110, 210 ) and a Radio Network Control Entity ( 130, 230 ), to receive an instruction from the first Mobile Gateway ( 110, 210 ) to arrange a filter for IP traffic from User Equipments ( 135, 235 ) in the Radio Network Control Entity ( 130, 230 ), to receive data from the first Mobile Gateway ( 110, 210 ) regarding the filter, comprising information on which IP traffic from User Equipments to forward to the first or to a second ( 120, 220 ) Mobile Gateway respectively, to transmit instructions to a second Mobile Gateway ( 120, 220 ) to establish a connection to the Radio Network Control Entity ( 130, 230 ) for IP traffic from User Equipments, and to transmit the instructions and the data regarding the IP traffic filter to the Radio Network Control Entity ( 130, 230 ).

Description:
TECHNICAL FIELD 
       [0001]    The present invention discloses a device and a system for obtaining reduced IP traffic load in a Gateway Node or a transmission network in a wireless access system. 
       BACKGROUND 
       [0002]    Operators of wireless access systems such as, for example, WCDMA or LTE systems have an interest in offloading uplink IP traffic from certain of their Packet Core nodes and/or transmission network such as, for example, a Gateway GPRS Support Node, a GGSN in a WCDMA system. 
         [0003]    One known solution for offloading uplink IP traffic from a node such as a GGSN is to have a so called Traffic Offload Function, a TOF, in the system for diverting certain IP traffic flows from reaching the GGSN in question, and instead letting the TOF direct those IP traffic flows to another node in the system, such as, for example, a secondary or auxiliary GGSN, possibly one with reduced functionality which, however, is enough for the diverted IP traffic flows, as an alternative to which the TOF itself can include such a simplified GGSN functionality. 
         [0004]    Drawbacks to the TOF solution to offloading IP traffic from a node such as a GGSN include User Equipment state handling, Mobility, Quality of Service and charging accuracy. 
       SUMMARY 
       [0005]    It is a purpose of the present invention to provide a solution for offloading IP traffic from a node such as a GGSN in a wireless access system which obviates at least some of the drawbacks mentioned above of previous solutions. 
         [0006]    This purpose is obtained by the present invention in that it discloses a Mobile Control Entity for a wireless access system. The Mobile Control Entity is arranged to communicate with a first Mobile Gateway and a Radio Network Control Entity. The Mobile Control Entity is further arranged to:
       receive an instruction from the first Mobile Gateway that a filter for IP traffic from one or more User Equipments in the system should be arranged in the Radio Network Control Entity,   receive data from the first Mobile Gateway regarding the filter, said data comprising information on which IP traffic from one or more User Equipments that should be forwarded to the first or to a second Mobile Gateway respectively,   transmit instructions to a second Mobile Gateway that it should establish a connection to the Radio Network Control Entity for IP traffic from one or more User Equipments in the system,   transmit the instructions and the data regarding the IP traffic filter to the Radio Network Control Entity.       
 
         [0011]    The invention also discloses a Mobile Control Entity for a wireless access system which is arranged to communicate with a first Mobile Gateway and a Radio Network Control Entity. The Mobile Control Entity is further arranged to:
       receive an instruction from the first Mobile Gateway that a filter for IP traffic from one or more User Equipments in the system should be arranged in a second Mobile Gateway,   receive data from the first Mobile Gateway regarding the filter, said data comprising information on which IP traffic from one or more User Equipments that should be forwarded to the first or within the second Mobile Gateway respectively,   transmit instructions to the second Mobile Gateway that it should establish a connection to the Radio Network Control Entity for IP traffic from one or more User Equipments in the system,   transmit the instructions and the data regarding the IP traffic filter to the second Mobile Gateway.       
 
         [0016]    In one embodiment, the Mobile Control Entity is a Serving GPRS Support Node, an SGSN, for a WCDMA system, for which SGSN:
       The first and second Mobile Gateways are Gateway GPRS Support Nodes, GGSNs,   the Radio Network Control Entity is a Radio Network Controller, an RNC.       
 
         [0019]    In one embodiment, the Mobile Control Entity is a Serving GPRS Support Node, an SGSN, for a WCDMA system, for which SGSN:
       the first and second Mobile Gateways comprise a Packet Data Network Gateway, a PDN GW, and a Serving Gateway, a Serving GW,   the Radio Network Control Entity is an eNodeB.       
 
         [0022]    In one embodiment, the Mobile Control Entity is a Mobility Management Entity, an MME, for an LTE system, for which MME:
       The first and second Mobile Gateways both comprise a PDN GW, Packet Data Network Gateway and at least one of them comprises a serving Gateway,   the Radio Network Control Entity is an eNodeB.       
 
         [0025]    By means of the invention, uplink IP traffic can be “diverted” from first Mobile Gateway, such as a GGSN, and instead directed to a second Mobile Gateway such as an auxiliary GGSN, with a high degree of granularity, i.e. the filter can be per User Equipment, or per service utilized by the User Equipments in the system, or for a certain group of User Equipments, etc. 
         [0026]    The invention also discloses a wireless access system comprising:
       a Mobile Control Entity,   a first Mobile Gateway,   a Radio Network Control Entity,
 
in which wireless access system the Mobile Control Entity is arranged to communicate with the first Mobile Gateway and the Radio Network Control Entity, and the first Mobile Gateway and the Radio Network Control Entity are arranged to communicate with each other. The system also comprises a second Mobile Gateway, and:
   the first Mobile Gateway is arranged to instruct the Mobile Control Entity that a filter for IP traffic from one or more User Equipments in the system should be arranged in the Radio Network Control Entity,   the Mobile Control Entity is arranged to:
           receive an instruction from the first Mobile Gateway that a filter for IP traffic from one or more User Equipments in the system should be arranged in the Radio Network Control Entity,   receive data from the first Mobile Gateway regarding the filter, said data comprising information on which IP traffic from one or more User Equipments that should be forwarded to the first or to the second Mobile Gateway respectively,   transmit instructions to the second Mobile Gateway that it should establish a connection to the Radio Network Control Entity for IP traffic from one or more User Equipments in the system,   transmit the instructions and the data regarding the IP traffic filter to the Radio Network Control Entity.   
           the Radio Network Control Entity is arranged to receive instructions from the Mobile Control Entity that a filter for IP traffic from one or more User Equipments in the system should be arranged in the Radio Network Control Entity, and to carry out the function of said filter, regarding which traffic that should be sent to the first or the second mobile Gateway.       
 
         [0037]    In addition, the invention discloses a wireless access system comprising:
       a Mobile Control Entity,   a first Mobile Gateway,   a Radio Network Control Entity,
 
in which wireless access system the Mobile Control Entity is arranged to communicate with the first Mobile Gateway and the Radio Network Control Entity, and the first Mobile Gateway and the Radio Network Control Entity are arranged to communicate with each other. The system also comprises a second Mobile Gateway, and:
   the first Mobile Gateway is arranged to instruct a second Mobile Gateway that a filter for IP traffic from one or more User Equipments in the system should be arranged in the second Mobile Gateway,   the Mobile Control Entity is arranged to:
           receive an instruction from the first Mobile Gateway that a filter for IP traffic from one or more User Equipments in the system should be arranged in the second Mobile Gateway,   receive data from the first Mobile Gateway regarding the filter, said data comprising information on which IP traffic from one or more User Equipments that should be forwarded to the first Mobile Gateway or be forwarded within the second Mobile Gateway,   transmit instructions to the second Mobile Gateway that it should establish a connection to the Radio Network Control Entity for IP traffic from one or more User Equipments in the system,   transmit the instructions and the data regarding the IP traffic filter to the second Mobile Gateway.   
           the Radio Network Control Entity is arranged to receive instructions from the Mobile Control Entity that a filter for IP traffic from one or more User Equipments in the system should be arranged in the Radio Network Control Entity, and to carry out the function of said filter, regarding which traffic that should be sent to the first or the second mobile Gateway.       
 
         [0048]    In one embodiment, the wireless access system is a WCDMA system, in which:
       the Mobile Control Entity is a Serving GPRS Support Node, an SGSN,   the first and second Mobile Gateways are Gateway GPRS Support Nodes, GGSNs,   the Radio Network Control Entity is a Radio Network Controller, an RNC.       
 
         [0052]    In one embodiment, the wireless access system is a WCDMA system, in which:
       the Mobile Control Entity is a Serving GPRS Support Node, an SGSN,   the first and second Mobile Gateways comprise a Packet Data Network Gateway, a PDN GW, and a Serving Gateway, a Serving GW,   the Radio Network Control Entity is an eNodeB.       
 
         [0056]    In one embodiment, the wireless access system is an LTE system, in which:
       the Mobile Control Entity is a Mobility Management Entity, an MME,   the first and second Mobile Gateways both comprise a PDN GW, Packet Data Network Gateway and at least one of them comprises a serving GW,   the Radio Network Control Entity is an eNodeB.       
 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0060]    The invention will be described in more detail in the following, with reference to the appended drawings, in which 
           [0061]      FIGS. 1-4  show schematic views of a system of the invention, and 
           [0062]      FIGS. 5 and 6  show possible traffic paths, and 
           [0063]      FIGS. 7-9  show call flows in a system of the invention. 
       
    
    
     DETAILED DESCRIPTION 
       [0064]    The invention will mainly be described in the following with reference to a WCDMA system, and hence also mainly with terminology from the WCDMA standard. However, it should be pointed out that the invention can equally well be applied to an LTE system. 
         [0065]      FIG. 1  shows a schematic view of a system  100  in which the invention is applied. The system  100  is a WCDMA system, and comprises a GGSN  110 , a SGSN  125 , an RNC  130  and an Offloading Gateway Node  120 , in  FIG. 1  shown as GGSN′, since the node can, in one embodiment, be a GGSN. In addition, the system comprises an RNC, a Radio Network Controller,  130 , and in one embodiment, the system comprises a node  105  for PCRF, Policy and Charging Rules Function. 
         [0066]    In addition, one User Equipment  135 , UE, is shown in  FIG. 1 . The UE  135  is shown connected to RNC  130  by means of dashed lines, intended to signify that there are additional nodes between the UE  135  and the RNC  130 . 
         [0067]    In  FIG. 2 , an LTE system  200  is shown in which the invention is applied. The LTE system  200  comprises a Mobile Gateway  210  comprising a PDN GW, Packet Data Network Gateway  211  together with a serving GW, Gateway,  212 , an MME, Mobility Management Entity  225 , an eNodeB  230  and an Offloading Mobile Gateway  220 , in  FIG. 2  shown as a combination of a PDN GW′  222  and a Serving GW′,  221 . 
         [0068]    Also, a User Equipment  235 , UE, is shown in  FIG. 2 , attached to the eNodeB  230 . 
         [0069]      FIG. 3  shows a version  300  of the LTE system  200  shown in  FIG. 2 : the difference is that in  FIG. 3  the “Offloading Mobile Gateway”  310  is a combination of a Serving Gateway  212  and a PDN GW′  220 , with the Serving Gateway  212  being connected to the Mobile Gateway  210 , which in this case only needs to comprise the PDN Gateway  211 . In this case, the Serving Gateway  212  performs the filter function, thus obviating the need for a Serving Gateway in the Mobile Gateway  210 . If the Serving Gateway  212  performs the filter function, it can either forward traffic to the Mobile Gateway  210 , i.e. the first Mobile Gateway, or it can forward traffic within itself, i.e. to “its own” PDN GW, i.e. the PDN GW′  220 . 
         [0070]    As mentioned previously, the invention addresses the problem of the local/offload GW, and presents a solution which is able to select a central or local/offload GW on a per bearer (or Service Data Flow) basis. The invention is generically described to fit both for 3G WCDMA/HSPA and for EPC/LTE. The solution assumes 3GDT, 3G Direct Tunnel. 
         [0071]    When a UE initiates a new service with an external AF, Application Function, the AF informs the PCRF, Policy and Charging Rules Function, about the new IP flow. The PCRF informs the GW about the new IP flow and what QoS this IP flow shall have. The GW (its PCEF, Policy and Charging Enforcement Function) decides if there is a need to set up a new bearer or if the IP flow should be added to an existing bearer (which may be modified). 
         [0072]    If a new bearer is set up e.g. for a streaming video, the request for the new bearer shall also include an indication whether this bearer may/should be set up towards an offload GW or not. 
         [0073]    The SGSN/MME receives the request and requests the bearer towards the RAN and secondly sets up the bearer either towards the same GW as all other bearers of this PDP ctxt/PDN connection; or it sets up this bearer specifically towards an offload GW. This can be achieved through reusing the PDN Connection request signaling but the SGSN/MME must also keep track of that this bearer is belonging to the same PDN connection as already exist towards another GW. The PDN Connection set up must in this case also include information that the PDN connection already has an IP address, but that all traffic through this bearer has to be NAT&#39;ed in the offload GW. Note that to the UE, it would still appear as if all bearers belong to the same PDN connection. 
         [0074]      FIG. 4  shows a wireless access system  400  in which the invention is applied, and in which system wireless access  400  there are two possible access oaths after the RNC or SGW, either through the central GW  410  or through the Offload GW  420 . 
         [0075]    The uplink user plane, passing over multiple bearers from the UE, will now take two alternative paths from the RNC/SGW. The traffic transported over non-offloaded bearers are sent to the (central) GW while traffic transported over the offloaded bearers are sent to the Offload GW where the traffic is being NAT:ed. 
         [0076]      FIG. 5  shows how, in the wireless access system  400 , “normal” traffic (Bearer  1 ) is routed through the central GW  410 , whereas “offload traffic” (Bearer  2 ) is routed through the Offload GW  420 , and the IP flows are separated after the RNC  435  (in the case of a 3G system) or after the SGW  435  (in the case of EPC/LTE systems.) Two bearers are shown as incoming to the RNC/SGW  435 , and being separate to there, to be routed either to the central GW  410  or to the Offload GW  420 . 
         [0077]    As an alternative to the bearer initiation from the AF and PCRF, the bearer can also be set up through service flow detection in a separate DPI or TFD 
         [0078]    (Traffic Flow Detection) function which then similar to the AF triggers a request for a certain handling for this IP flow towards the PCRF. The flow from the PCRF and onwards is then the same as if initiated from the AF. 
         [0079]    This means that the decision to do offload is done in the PCRF or the GW (PCEF) based on input from either the AF or the DPI/TFD function. The description in this text describes the case where the first bearer is always set up to the central GW, but it might also be possible to set up the first flow to the Offload GW and to set up further flows to the central GW. The same principles would apply for that case, but requires that the Offload GW is connected to a PCRF or the Offload GW itself takes the decision on selecting certain flows to the central GW. This alternative is not further elaborated in this text. 
         [0080]    To move traffic transported over a bearer that has already been established, e.g. from a centrally routed bearer to an offloaded bearer, the existing bearer procedures can be re-used. The PCRF may e.g. updates the PCC rules in the central GW by e.g. changing a parameter to indicate that the flows should be offloaded. Alternatively, the central GW decides that a flow shall be offloaded. In both cases, the GW initiates bearer modification procedures and includes an indication that the existing bearer shall be offloaded. It may e.g. be a bearer termination procedure containing an indication that the traffic over the bearer shall be offloaded instead. It could also be a bearer modification procedure containing an indication that the flow described by the TFT shall be offloaded. When receiving the request, the MME/SGSN initiates dedicated bearer procedures for the offloaded GW, either creating a new bearer of modifying an existing bearer, to ensure that the flow is transported over to the offloaded bearers. 
         [0081]    Concept of Alternative Solution 
         [0082]    An alternative solution, shown in  FIG. 6 , would be that the Offload GW  420  is “on the path” between the RNC/SGW  430  and the central GW  410 . In this case the Offload GW  420  takes out only the flows that shall be offloaded and the flows that shall be taken to the central GW  410  are forwarded (or re-encapsulated and sent) to the central GW  410 . For this reason, both bearer  1  (non-offloaded, or “normal” traffic) and bearer  2  (off-load traffic) are shown as incoming to the offload GW  420 , and only bearer  1  (non-offloaded) is shown as continuing from the offload GW  420 . 
         [0083]    A potential advantage of this alternative is that the Offload GW  420  can “snoop” the control signaling to the central GW  410 , and thus the dedicated signaling to the offload GW  420  may be reduced. 
         [0084]    Call Flows 
         [0085]    The included call flows in  FIGS. 7-9  show the GPRS architecture, but are in general reusable in EPC/LTE systems as well. In the call flows of  FIGS. 7-9 , the PCRF does not have any interaction with the Offload GW, although cases can also be envisioned where the Offload GW also has an interface to the PCRF. 
         [0086]      FIG. 7  shows the call flows when setting filters for offload traffic already at the Initial PDP ctxt (context) activation. 
         [0087]    “Bubbles”  1 - 3  contain the following comments: 
         [0088]    Bubble  1 : These calls contain indications that certain flows should be offloaded. 
         [0089]    Bubble  2 : This may be handled either through separate signaling to the TIG, broadcast or that the TIG proxy the signaling to the GGSN. TIG is an embodiment of an offload GW, Terminal Internet Gateway. 
         [0090]    Bubble  3 : Download the filter with its parameters. 
         [0091]      FIG. 8  shows the setting of filters for offload at establishment of a new bearer. 
         [0092]    “Bubbles”  4 - 6  contain the following comments: 
         [0093]    Bubble  4 : An indication that certain existing flows shall be offloaded instead of routed to GGSN. The flows are removed from the bearer towards GGSN, and will instead be included in the bearers towards the TIG. 
         [0094]    Bubble  5 : This may be handled either through separate signaling to the TIG, broadcast or that the TIG proxy the signaling to the GGSN 
         [0095]    Bubble  6 : Bearers are created (or modified) towards the TIG to handle the flows that are no longer routed via GGSN. If existing bearers towards the TIG can be re-used, an Update PDP context procedure is used instead of Create PDP Ctxt. 
         [0096]      FIG. 9  shows how flows can be moved from the Central GW (here GGSN) to the Offload GW. 
         [0097]    “Bubbles”  7 - 9  contain the following comments: 
         [0098]    Bubble  7 : An indication that certain existing flows shall be offloaded instead of routed to GGSN. The flows are removed from the bearer towards GGSN and will instead be included in the bearers towards the TIG. 
         [0099]    Bubble  8 : This may be handled either through separate signaling to the TIG, broadcast, or by proxy the signaling to the GGSN from the TIG. 
         [0100]    Bubble  9 : Bearers are created (or modified) towards the TIG to handle the flows that are no longer routed via GGSN. If existing bearers towards the TIG can be re-used, an Update PDP context procedure is used instead of Create PDP Ctxt. 
         [0101]    The invention is not limited to the examples of embodiments described above and shown in the drawings, but may be freely varied within the scope of the appended claims. For example, as an implementation option, the Offload GW may be implemented together with the SGW and possibly also with the RNC as one physical entity. In addition, the filters for IP traffic can also be configured locally in the RNC.