This invention pertains to mobile networks.
Today's mobile network operator (MNO) keeps a detailed user record in its database. Those records can be used to control a mobile user's ability to access the mobile network and the capabilities available to the user when using the mobile network. For example, user account information can be used to determine if the user can access the mobile network and at what usage level. User device information can be used to determine, for example, if the content the user wishes to access is to be blocked (blacklisted), prioritized, authorized during only a certain period of time, or balanced with other content from other users. These actions are called “policies;” policies govern how user traffic behaves in the network. Policy governance is not simply restricted to mobile networks. Landline and WiFi networks make use of polices as well.
A mobile user (hereinafter “subscriber”) will often have an account with one mobile network operator and “visit” another network operated by an MNO with which they have no account. This happens frequently in the mobile network community and is referred to as “roaming.”
In a roaming scenario, a subscriber is attempting to use their mobile phone in an operator's network (3G or LTE) other than the network (3G or LTE) with whom the subscriber holds an account. The account-related network is referred to as the “Home” network or more formally as the “Home Public Land Mobile Network” or “HPLMN”. When roaming, the subscriber is located in an area served by a visited network, known formally as the “Visited Public Land Mobile Network” or “VPLMN”.
Referring now to
The roaming subscriber's data is sent, across GPRS roaming exchange (GRX) 106, from visited network 104 to home network 102, where the traffic is allowed onto the Internet via internet service provider (ISP) 108. Data traffic 112 is then brought back through home network 102 to visited network 104 and to roaming subscriber 110.
Data roaming is very expensive and creates long latencies, leading to a very unsatisfactory experience. As a result, most subscribers turn off the data-roaming options on their phone and use WiFi instead. That subscriber behavior deprives the mobile operators of significant revenue. In order to address this trend, MNOs need to create a lower-cost solution, which will also attract more subscribers.
In order to reduce the data path latency created by subscriber traffic needing to traverse the GRX 106 network, the industry has a concept known as Local Break Out (LBO). With LBO, depicted in
Optionally, the HPLMN's Online Charging System (OCS) can be used to conduct real-time policy across the network to the VPLMN's PCEF/PGW. Both the S9 (PCRF) and Gy (OCS) interfaces can be accommodated in any given solution, although only one of them would be used for PCEF/PGW control at any given time.
This arrangement enables HPLMN 102 to maintain policy on subscriber 110 and track their usage 112 while the subscriber roams in the VPLMN, using the VPLMN's access to ISP 109. The HPLMN control's the subscriber's policy and therefore can settle the payments with the subscriber, some of which payments go back to VPLMN 104. This arrangement, however, is typically prohibitively expensive to the subscriber and the connection is often of inferior quality. This solution also involves close cooperation between the HPLMN and VPLMN in terms of policy interoperability, signaling interoperability and payments. Often times, the signaling supported by each operator is different as different operator's use different vendor's equipment and support custom variants to enable the particular operator's network.
The present invention provides architectures and methods that enable a Home network to control and enforce its policies realizing similar benefits to LBO from quality of service and cost savings perspective, but in a manner that is much easier and more cost effective to deploy, operate, and support. These architectures and methods are improvements of the “Local Break Out” arrangement.
The Figures and description provided herein depict various embodiments of an “exchange” that provides connectivity between multiple “home” mobile voice/data telecommunications networks and multiple “visited” mobile voice/data telecommunications networks.
Embodiments of the exchange comprise a data processing system, including processors for executing machine-executable commands, processor-accessible storage, transceivers for receiving and transmitting data, controllers, routers, and the like. All elements of the exchange are known to those skilled in the art, but organized in new ways that afford functionality heretofore unavailable and unknown.
Many of the important elements of mobile telecommunications networks, and of the various embodiments of the exchange that is subject of the invention, are implemented as software, i.e., processor-executable instructions. It is conventional in the telecommunications arts to refer to such software as functional elements, and that convention is adopted herein. Of course, all such software is running on processors located in servers, gateways, controllers, routers, etc. Those skilled in the art will be familiar with all such functional elements and understand the functionality thereof and the manner in which they interact with other elements of data networks (e.g., the Internet) and wireless telecommunications networks.
To maintain a focus on what is germane to the invention, and as will be appreciated by those skilled in the art, only a few of the many hardware and software elements that comprise the mobile voice/data telecommunications networks are depicted in the drawings.
In
In many networks, the PCEF is contained within the Operator's Packet Gateway (PGW/GGSN) router, but that function can be segregated and lies instead outside the router on the Internet side of the Packet Gateway.
In any policy-based model, the Gx interface is the Standards-based signaling path between a PCRF and a PCEF. More importantly, exchange 206 can map this Gx information to every Packet Gateway of every Visited Network with whom the Home network has a partnering relationship.
Exchange 206 comprises a Diameter Signal Controller (DSC) including Interworking function (IWF), Diameter Edge Agent (DEA), and Diameter Routing Agent (DRA) functionality, as are well-known in the art. The IWF, DEA, and DRA are specialized software, in the form of processor-executable instructions, executed by the DSC.
Exchange 206 adapts the Gx interface message content from the home networks and delivers it to each Packet Gateway for each VPLMN. Thus, when a HPLMN subscriber visits a VPLMN, the policies that control that subscriber's account will be delivered from the HPLMN's PCRF via Exchange 206 to the VPLMN's PCEF. The VPLMN's PCEF then routes the subscriber's data traffic to, for example, the Internet, just as if the subscriber were ‘homed’ to the visited network.
Thus, similar to the prior-art LBO, data for the roaming subscriber does not have to be backhauled to the home network. However, unlike the prior-art LBO, the close cooperation between the HPLMN and VPLMN in terms of policy interoperability, signaling interoperability and payments are avoided due to the ability of exchange 206 to the use of standard Gx interface.
Although two VPLMNs are depicted in
In this embodiment, exchange 206 receives information from the home networks over the Gy interface rather than the Gx interface. That is, the HPLMN's Online Charging System (OCS) is used to map information, in real time, via exchange 206, to the VPLMN's PCEF. A difference between this embodiment and the one depicted in
Thus, Gy, DIAMETER-based Protocol signaling output from OCS 310A of HPLMN 202A is mapped, via exchange 206, to the Policy Charging and Enforcement Function (PCEF) running on router 205A in VPLMN 204A and to the PCEF running on router 205B in VPLMN 204B. And the signaling output from OCS 310B of HPLMN 202B is mapped, via Gy exchange 306, to the Policy Charging and Enforcement Function (PCEF) running on router 205A in VPLMN 204A and to the PCEF running on router 205B in VPLMN 204B.
The VPLMNs then directly access a desired data service, such as ISPs 208A or 208B, to provide the requested content to the roaming subscriber 110A or 1106.
Once again, exchange 206 uses a Diameter Signal Controller (DSC) including Interworking function (IWF), Diameter Edge Agent (DEA), and Diameter Routing Agent (DRA) functionality.
In the third embodiment, rather than relying on the HPLMN to have a PCRF server or OCS, a PCRF server(s) or OCS is provided locally in exchange 406. In this embodiment, the exchange comprises plural PCRF or OCS instances, wherein a specific instance of the PCRF or OCS is allocated to each HPLMN using the exchange. This effectively provides a centralized policy controller for more advanced operations, enabling, for example, a group of mobile network operators to use a common control point for exchanging roaming policy.
This embodiment requires that the provisioning system of each HPLMN using exchange 406 accesses its private instance of a PCRF server or OCS in the exchange, establish subscriber data entries, create policies, and assign those policies to the subscribers who enter a visited network. Thus, for example, provisioning system 410A of HPLMN 202A accesses, over a provisioning interface, PCRF or OCS 414(A) and provisioning system 410B of HPLMN 202B accesses, over a provisioning interface, PCRF or OCS 414(B).
Either a Gx or Gy interface is used between the PCRF or OCS instances in exchange 406 and the PCEF (e.g., 205A, 205B, etc.) of visited networks (e.g., VPLMNs 204A, 204B, etc.). Since only a single PCRF or OCS instance is needed to enable a single HPLMN, each instance can be used to generate Gx or Gy for each of the VPLMNs.
The VPLMNs then directly access a desired data service, such as ISPs 208A or 208B, to provide the requested content to the roaming subscriber 110A or 1108.
As in the previous embodiments, this embodiment enables a single HPLMN to control roaming policy in an arbitrary number, N, of visited networks (VPLMNs) and contemplates a plurality of HPLMNs each controlling their roaming policy in any number of visited networks.
This embodiment of an improved LBO architecture and method enables, in addition to any other capabilities and benefits:
Exchange 506 is effectively an extension of the home network (HPLMN) into regions that are in proximity to an HPLMN's outbound roamers. Exchange 506 is not necessarily located adjacent to the visited or home Mobile operator. Rather, it is advantageously positioned in regionally local data centers to optimize its ability to pull traffic from multiple visited networks within that region and provides what can be referred to as Regional Breakout (RBO). Exchange 506 may support multiple HPLMNs, and HPLMNs may be supported by multiple exchanges 506.
Traffic is routed between exchange 506 and visited networks based on network routing instructions received from each HPLMN. Within exchange 506, the traffic associated with outbound roamers of a specific HPLMN, traverses PGW/GGSN/PCEF instance(s) dedicated to that HPLMN as it is broken out to an internet service provider (ISP) local to that region. The PGW/GGSN/PCEF instance(s) interact with other HPLMN subsystems (e.g., PCRF, OCS, etc.) to apply the HPLMN's Policy Control and Charging capabilities.
For example, instance of PCRF or OCS 514(A) receives traffic/instructions from provisioning system 410A of HPLMN 202A. The traffic/instructions traverses instance of PGW/GGSN/PCEF 516(A). Data traffic obtained via ISP 208A is routed via PGW/GGSN/PCEF 516(A) to VPLMN 204A and then to subscriber 110A. HPLMN 202A, via instances PCRF or OCS 514(A) and PGW/GGSN/PCEF 516(A) can also route to VPLMN 204B. Similarly, HPLMN 202B can route to either VPLMN 202A or VPLMN 202B via instances PCRF or OCS 514(B) and PGW/GGSN/PCEF 516(B).
Exchange 606, depicted in
For example, instance of PGW/GGSN/PCEF/PCRF 618A receives traffic/instructions from hPCRF or hOCS 610A of HPLMN 202A. The traffic/instructions traverses instance of PGW/GGSN/PCEF/PCRF 618(A). Data traffic obtained via ISP 208A is routed via PGW/GGSN/PCEF/PCRF 618(A) to VPLMN 204A and then to subscriber 110A. HPLMN 202A can also route to VPLMN 204B. Similarly, HPLMN 202B can route to either VPLMN 202A or VPLMN 202B via its instance of PGW/GGSN/PCEF/PCRF 618(B).
This embodiment of an improved LBO architecture and method enables/requires, in addition to any other capabilities and benefits:
This case claims priority of U.S. Provisional Patent Application Ser. No. 61/943,450, filed Feb. 23, 2014, and which is incorporated by reference herein.
Number | Date | Country | |
---|---|---|---|
61943450 | Feb 2014 | US |