US20140045486A1 - Cooperative mobility management in a mobile data network with data breakout at the edge - Google Patents

Abstract

A TCP context is transferred to a Gi Optimizer to provide cooperative mobility management in a mobile data network with a breakout system. The breakout system includes an Iub Optimizer at the MIOP@NodeB, and the Gi Optimizer at the MIOP@Core. When a MIOP@NodeB detects a mobility event for a broken out user equipment (UE), the Iub optimizer in the MIOP@NodeB coordinates with the Gi optimizer to transfer the TCP/UDP connection established between the UE and the IuB Optimizer to the Gi Optimizer. After the transfer, the UE is served by the Gi Optimizer. The transfer of the TCP/UDP connection to the Gi optimizer may require tunnel stitching at the MIOP@RNC depending on the PDP context state and the RRC state of the UE.

Description

BACKGROUND
• 1. Technical Field
• This disclosure generally relates to mobile data systems, and more specifically relates to cooperative mobility management with a breakout system that supports data breakout at the edge of a mobile data network.
• 2. Background Art
• Mobile phones have evolved into “smart phones” that allow a user not only to make a call, but also to access data, such as e-mails, the internet, etc. Mobile phone networks have evolved as well to provide the data services that new mobile devices require. For example, 3G networks cover most of the United States, and allow users high-speed wireless data access on their mobile devices. In addition, phones are not the only devices that can access mobile data networks. Many mobile phone companies provide equipment and services that allow a subscriber to plug a mobile access card into a Universal Serial Bus (USB) port on a laptop computer, and provide wireless internet to the laptop computer through the mobile data network. In addition, some newer mobile phones allow the mobile phone to function as a wireless hotspot, which supports connecting several laptop computers or other wireless devices to the mobile phone, which in turn provides data services via the mobile data network. As time marches on, the amount of data served on mobile data networks will continue to rise exponentially.
• Mobile data networks include very expensive hardware and software, so upgrading the capability of existing networks is not an easy thing to do. It is not economically feasible for a mobile network provider to simply replace all older equipment with new equipment due to the expense of replacing the equipment. To facilitate additional capacity on mobile networks, a new “edge server” or “breakout system” is being developed by International Business Machines Corporation (IBM). The breakout system or edge server is also referred to as a Mobile Internet Optimization Platform (MIOP). The MIOP entity corresponding to each basestation is referred to as a MIOP@NodeB. The MIOP@NodeB performs at the edge processing of offloaded data streams such as internet data streams while passing through the voice streams to the backend of the network. As used herein, the term “breakout system” in general means a system that connects between two computer systems on a data network and passes on some of the data on the data network between the two systems while breaking out for local processing other data streams normally flowing between the two computer systems on the data network. The term breakout system could broadly be construed as a network processing device or mechanism capable of routing all or part of the network traffic on a network data path between two other nodes through itself.
• In a typical mobile data network, a user equipment (UE) such as a cell phone connects wirelessly to equipment at the basestation referred to as a NodeB. In the traditional mobile network the NodeB connects the UE to a radio network controller (RNC) which connects to a GPRS support node (SGSN). The SGSN is connected to a Gateway GPRS Support Node (GGSN) which provides connectivity to the internet via an operators service node (OSN). After a UE attaches to the mobile data network and opens a packet data protocol (PDP) session, the mobile data network establishes a tunnel between the GGSN and the UE. A mobility event is when the user moves the UE to a new location serviced by an adjacent NodeB or cell. When the UE moves from one NodeB to the next cell served by a second NodeB, the RNC and the GPRS support nodes work together to move the connection and switch the traffic to the new cell and the second NodeB. A transmission control protocol (TCP) or user datagram protocol (UDP) connection to the UE established before the mobility event will not be impacted since the TCP/UDP sockets were created on the UE and on the OSN or internet server such that the IP routing will not be affected.
BRIEF SUMMARY
• In a mobile data network with a breakout system, a UE connection to the internet may be broken out at the edge of the mobile data network with the MIOP@NodeB to provide internet traffic that is optimized locally. In this case, the TCP/UDP connection is established between the UE and an IuB optimizer in the MIOP@NodeB. When a mobility event occurs the TCP/UDP connection will be disrupted and likely negatively impact the subscriber's quality of experience with the internet services.
• The claims and disclosure herein provide mechanisms and methods for cooperative mobility management in a mobile data network with a breakout system. A TCP context is transferred to a Gi Optimizer to provide cooperative mobility management in a mobile data network with a breakout system. The breakout system includes an Iub Optimizer at the MIOP@NodeB, and the Gi Optimizer at the MIOP@Core. When a MIOP@NodeB detects a mobility event for a broken out UE, the Iub optimizer in the MIOP@NodeB coordinates with the Gi optimizer to transfer the TCP/UDP connection established between the UE and the IuB Optimizer to the Gi Optimizer. After the transfer, the UE is served by the Gi Optimizer. The transfer of the TCP/UDP connection to the Gi optimizer may require tunnel stitching at the MIOP@RNC depending on the PDP context state and the radio resource control (RRC) state of the UE.
• The foregoing and other features and advantages will be apparent from the following more particular description, as illustrated in the accompanying drawings.
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)
• The disclosure will be described in conjunction with the appended drawings, where like designations denote like elements, and:
• FIG. 1 is a block diagram of a prior art mobile data network;
• FIG. 2 is a block diagram of a mobile data network that includes first, second and third service mechanisms that all communicate via an overlay network;
• FIG. 3 is a block diagram of one possible implementation for parts of the mobile data network shown inFIG. 2 to illustrate the overlay network;
• FIG. 4 is a block diagram of the MIOP@NodeB shown inFIG. 2, which includes a first service mechanism;
• FIG. 5 is a block diagram of the MIOP@RNC shown inFIG. 2, which includes a second service mechanism;
• FIG. 6 is a block diagram of the MIOP@Core shown inFIG. 2, which includes a third service mechanism;
• FIG. 7 is a block diagram of a management mechanism coupled to the overlay network that manages the functions of MIOP@NodeB, MIOP@RNC, and MIOP@Core;
• FIG. 8 is a flow diagram of a method performed by MIOP@NodeB shown inFIGS. 2 and 4;
• FIG. 9 is a block diagram showing breakout criteria MIOP@RNC may use in making a decision of whether or not to break out data;
• FIG. 10 is a flow diagram of a method for the MIOP@NodeB and MIOP@RNC to determine when to break out data;
• FIG. 11 is a flow diagram of a method for the first service mechanism in MIOP@NodeB to selectively break out data when break out for a specified subscriber session has been authorized;
• FIG. 12 is a flow diagram of a method for determining when to run MIOP services for a specified subscriber session;
• FIGS. 13-15 are flow diagrams that each show communications between MIOP components when MIOP services are running; and
• FIG. 16 is a flow diagram of a method for managing and adjusting the MIOP components;
• FIG. 17 is a block diagram of one specific implementation for MIOP@NodeB and MIOP@RNC;
• FIGS. 18 and 19 show a flow diagram of a first method for the specific implementation shown inFIG. 17;
• FIG. 20 is a flow diagram of a second method for the specific implementation shown inFIG. 17;
• FIG. 21 is a flow diagram of a third method for the specific implementation shown inFIG. 17;
• FIG. 22 is a flow diagram of a method for the specific implementation shown inFIG. 17 to process a data request that results in a cache miss at MIOP@NodeB;
• FIG. 23 is a flow diagram of a method for the specific implementation shown inFIG. 17 to process a data request that results in a cache hit at MIOP@NodeB;
• FIG. 24 is a block diagram of one specific hardware architecture for MIOP@NodeB;
• FIG. 25 is a block diagram of the system controller shown inFIG. 24;
• FIG. 26 is a block diagram of the service processor shown inFIG. 24;
• FIG. 27 is a block diagram of the security subsystem shown inFIG. 24;
• FIG. 28 is a block diagram of the telco breakout system shown inFIG. 24;
• FIG. 29 is a block diagram of theedge application mechanism2530 shown inFIG. 25 that performs multiple services at the edge of a mobile data network based on data broken-out at the edge of the mobile data network;
• FIG. 30A is a block diagram of a mobile data network that includes a push mechanism;
• FIG. 30B is a block diagram of a mobile data network that illustrates address translation at the MIOP@NodeB;
• FIG. 31 is a flow diagram of a method for a supporting a push data service on a breakout system for a UE with a PDP context in a preserved state;
• FIG. 32 is a flow diagram of a method for implementingstep3110 in the flow diagram ofFIG. 31;
• FIG. 33 is a flow diagram of a method for implementingstep3150 in the flow diagram ofFIG. 31;
• FIG. 34 is a flow diagram that further illustrates the method in the flow diagram inFIGS. 31-33;
• FIG. 35 is a block diagram of a RLC context according to the prior art;
• FIG. 36 is a block diagram of abreakout system3600 utilizing the RLC reset command when the ciphering context is out of synchronization;
• FIG. 37 is a block diagram to illustrate features of the RLC data structures; and
• FIG. 38 is a flow diagram of a method abreakout system3600 utilizing the RLC reset command when the ciphering context is out of synchronization.
• FIG. 39 is a block diagram of a mobile data network that provides cooperative mobility management;
• FIG. 40 is a block diagram to illustrate additional details of cooperative mobility management in a mobile data network;
• FIG. 41 is a block diagram of a mobile data network that illustrates address translation at the MIOP@Core and stitching of tunnels for mobility management;
• FIG. 42 is a flow diagram of a method for cooperative mobility management in a mobile data network with a breakout system;
• FIG. 43 is a flow diagram of a method for implementingstep4220 in the flow diagram ofFIG. 42.
• FIG. 44 is a flow diagram of a first method for implementingstep4240 in the flow diagram ofFIG. 42;
• FIG. 45 is a flow diagram of a second method for implementingstep4240 in the flow diagram ofFIG. 42; and
• FIG. 46 is a flow diagram of a method for implementingsteps4412 and4518 in the flow diagrams ofFIG. 44 andFIG. 45 respectively.
DETAILED DESCRIPTION
• The claims and disclosure herein provide mechanisms and methods for cooperative mobility management in a mobile data network with a breakout system. A TCP context is transferred to a Gi Optimizer to provide cooperative mobility management in a mobile data network with a breakout system. The breakout system includes an Iub Optimizer at the MIOP@NodeB, and the Gi Optimizer at the MIOP@Core. When a MIOP@NodeB detects a mobility event for a broken out UE, the Iub optimizer in the MIOP@NodeB coordinates with the Gi optimizer to transfer the TCP/UDP connection established between the UE and the IuB Optimizer to the Gi Optimizer. After the transfer, the UE is served by the Gi Optimizer. The transfer of the TCP/UDP connection to the Gi optimizer may require tunnel stitching at the MIOP@RNC depending on the PDP context state and the RRC state of the UE.
• Referring toFIG. 1, a prior artmobile data network100 is shown.Mobile data network100 is representative of known 3G networks. Themobile data network100 preferably includes a radio access network (RAN), a core network, and an external network, as shown inFIG. 1. The radio access network includes thetower120,basestation122 with itscorresponding NodeB130, and a radio interface on a radio network controller (RNC)140. The core network includes a network interface on theradio network controller140, the servingnode150,gateway node160 and operator service network170 (as part of the mobile data network). The external network includes any suitable network. One suitable example for an external network is theinternet180, as shown in the specific example inFIG. 1.
• Inmobile data network100,user equipment110 communicates via radio waves to atower120.User equipment110 may include any device capable of connecting to a mobile data network, including a mobile phone, a tablet computer, a mobile access card coupled to a laptop computer, etc. Thetower120 communicates via network connection to abasestation122. Eachbasestation122 includes aNodeB130, which communicates with thetower120 and theradio network controller140. Note there is a fan-out that is not represented inFIG. 1. Typically there are tens of thousands oftowers120. Eachtower120 typically has acorresponding base station122 with aNodeB130 that communicates with the tower. However, network communications with the tens of thousands ofbase stations130 are performed by hundreds ofradio network controllers140. Thus, eachradio network controller140 can servicemany NodeBs130 inbasestations122. There may also be other items in the network between thebasestation130 and theradio network controller140 that are not shown inFIG. 1, such as concentrators (points of concentration) or RAN aggregators that support communications with many basestations.
• Theradio network controller140 communicates with the servingnode150. In a typical 3G network, the servingnode150 is an SGSN, which is short for Service GPRS Support Node, where GPRS stands for general packet radio service. The servingnode150 mediates access to network resources on behalf of mobile subscribers and implements the packet scheduling policy between different classes of quality of service. It is also responsible for establishing the Packet Data Protocol (PDP) context with thegateway node160 for a given subscriber session. The servingnode150 is responsible for the delivery of data packets from and to the basestations within its geographical service area. The tasks of the servingnode150 include packet routing and transfer, mobility management (attach/detach and location management), logical link management, and authentication and charging functions. The servingnode150 stores location information and user profiles of all subscribers registered with the servingnode150. Functions the servingnode150 typically performs include GPRS tunneling protocol (GTP) tunneling of packets, performing mobility management as user equipment moves from one basestation to the next, and billing user data.
• In a typical 3G network, thegateway node160 is a GGSN, which is short for gateway GPRS support node. Thegateway node160 is responsible for the interworking between the core network and external networks. From the viewpoint of theexternal networks180,gateway node160 is a router to a sub-network, because thegateway node160 “hides” the core network infrastructure from the external network. When thegateway node160 receives data from an external network (such as internet180) addressed to a specific subscriber, it forwards the data to the servingnode150 serving the subscriber. For inactive subscribers paging is initiated. Thegateway node160 also handles routing packets originated from theuser equipment110 to the appropriate external network. As anchor point thegateway node160 supports the mobility of theuser equipment110. In essence, thegateway node160 maintains routing necessary to tunnel the network packets to the servingnode150 that services aparticular user equipment110.
• Thegateway node160 converts the packets coming from the servingnode150 into the appropriate packet data protocol (PDP) format (e.g., IP or X.25) and sends them out on the corresponding external network. In the other direction, PDP addresses of incoming data packets from theexternal network180 are converted to the address of the subscriber'suser equipment110. The readdressed packets are sent to the responsible servingnode150. For this purpose, thegateway node160 stores the current serving node address of the subscriber and his or her profile. Thegateway node160 is responsible for IP address assignment and is the default router for the subscriber'suser equipment110. Thegateway node160 also performs authentication, charging and subscriber policy functions. One example of a subscriber policy function is “fair use” bandwidth limiting and blocking of particular traffic types such as peer to peer traffic. Another example of a subscriber policy function is degradation to a 2G service level for a prepaid subscriber when the prepaid balance is zero.
• A next hop router located in the operator service network (OSN)170 receives messages from thegateway node160, and routes the traffic either to theoperator service network170 or via an internet service provider (ISP) towards theinternet180. Theoperator service network170 typically includes business logic that determines how the subscriber can use themobile data network100. The business logic that provides services to subscribers may be referred to as a “walled garden”, which refers to a closed or exclusive set of services provided for subscribers, including a carrier's control over applications, content and media on user equipment.
• Devices using mobile data networks often need to access an external network, such as theinternet180. As shown inFIG. 1, when a subscriber enters a request for data from the internet, that request is passed from theuser equipment110 to tower120, toNodeB130 inbasestation122, toradio network controller140, to servingnode150, togateway node160, tooperator service network170, and tointernet180. When the requested data is delivered, the data traverses the entire network from theinternet180 to theuser equipment110. The capabilities of knownmobile data networks100 are taxed by the ever-increasing volume of data being exchanged betweenuser equipment110 and theinternet180 because all data between the two have to traverse the entire network.
• Some efforts have been made to offload internet traffic to reduce the backhaul on the mobile data network. For example, some mobile data networks include a node called a HomeNodeB that is part of the radio access network. Many homes have access to high-speed Internet, such as Direct Subscriber Line (DSL), cable television, wireless, etc. For example, in a home with a DSL connection, the HomeNodeB takes advantage of the DSL connection by routing Internet traffic to and from the user equipment directly to the DSL connection, instead of routing the Internet traffic through the mobile data network. While this may be an effective way to offload Internet traffic to reduce backhaul, the HomeNodeB architecture makes it difficult to provide many mobile network services such as lawful interception, mobility, and charging consistently with the 3G or 4G mobile data network.
• Referring toFIG. 2, amobile data network200 includes mechanisms that provide various services for the mobile data network in a way that is transparent to most of the existing equipment in the mobile data network.FIG. 2 showsuser equipment110,tower120,NodeB130,radio network controller140, servingnode150,gateway node160,operator service node170, andinternet180, the same as shown inFIG. 1. The additions to themobile data network200 when compared with the prior artmobile data network100 inFIG. 1 include the addition of three components that may provide mobile network services in the mobile data network, along with a network management mechanism to manage the three components. The mobile network services are performed by what is called herein a Mobile Internet Optimization Platform (MIOP), and the mobile network services performed by the Mobile Internet Optimization Platform are referred to herein as MIOP services. The three MIOP components that provide these mobile network services are shown inFIG. 2 asMIOP@NodeB210,MIOP@RNC220 andMIOP@Core230. A network management system shown asMIOP@NMS240 manages the overall solution by: 1) managing the function of the threeMIOP components210,220 and230; 2) determining which MIOP@NodeBs in the system aggregate to which MIOP@RNCs via the overlay network for performance, fault and configuration management; and 3) monitoring performance of the MIOP@NodeBs to dynamically change and configure the mobile network services. TheMIOP@NodeB210,MIOP@RNC220,MIOP@Core230,MIOP@NMS240, and theoverlay network250, and any subset of these, and are referred to herein as MIOP components.
• The mobile network services provided byMIOP@NodeB210,MIOP@RNC220, andMIOP@Core230 include any suitable services on the mobile data network, such as data optimizations, RAN-aware services, subscriber-aware services, edge-based application serving, edge-based analytics, etc. All mobile network services performed by all ofMIOP@NodeB210,MIOP@RNC220, andMIOP@Core230 are included in the term MIOP services as used herein. In addition to the services being offer in theMIOP components MIOP@NodeB210,MIOP@RNC220, andMIOP@Core230, the various MIOP services could also be provided in a cloud based manner.
• MIOP@NodeB210 includes a first service mechanism and is referred to as the “edge” based portion of the MIOP solution.MIOP@NodeB210 resides in the radio access network and has the ability to intercept all traffic to and from theNodeB130.MIOP@NodeB210 preferably resides in thebase station222 shown by the dotted box inFIG. 2. Thus, all data to and from theNodeB130 to and from theradio network controller140 is routed throughMIOP@NodeB210. MIOP@NodeB performs what is referred to herein as breakout of data on the intercepted data stream. MIOP@NodeB monitors the signaling traffic between NodeB and RNC and on connection setup intercepts in particular the setup of the transport layer (allocation of the UDP Port, IP address or AAL2 channel). For registered sessions thebreakout mechanism410 will be configured in a way that all traffic belonging to this UDP Port, IP address to AAL2 channel will be forwarded to an data offload function.MIOP@NodeB210 thus performs breakout of data by defining a previously-existing path in the radio access network for non-broken out data, by defining a new second data path that did not previously exist in the radio access network for broken out data, identifying data received from a corresponding NodeB as data to be broken out, sending the data to be broken out on the second data path, and forwarding other data that is not broken out on the first data path. The signaling received byMIOP@NodeB210 fromNodeB130 is forwarded toRNC140 on the existing network connection toRNC140, even though the data traffic is broken out. Thus,RNC140 sees the signaling traffic and knows the subscriber session is active, but does not see the user data that is broken out byMIOP@NodeB210. MIOP@NodeB thus performs two distinct functions depending on the monitored data packets: 1) forward the data packets toRNC140 for signaling traffic and user data that is not broken out (including voice calls); and 2) re-route the data packets for user data that is broken out.
• OnceMIOP@NodeB210 breaks out user data it can perform any suitable service based on the traffic type of the broken out data. Because the services performed byMIOP@NodeB210 are performed in the radio access network (e.g., at the basestation222), theMIOP@NodeB210 can service theuser equipment110 much more quickly than can theradio network controller140. In addition, by having aMIOP@NodeB210 that is dedicated to aparticular NodeB130, one MIOP@NodeB only needs to service those subscribers that are currently connected via a single NodeB. The radio network controller, in contrast, which typically services dozens or even hundreds of basestations, must service all the subscribers accessing all basestations it controls from a remote location. As a result, MIOP@NodeB is in a much better position to provide services that will improve the quality of service and experience for subscribers than is the radio network controller.
• Breaking out data in the radio access network byMIOP@NodeB210 allows for many different types of services to be performed in the radio access network. These services may include optimizations that are similar to optimizations provided by known industry solutions between radio network controllers and the serving node. However, moving these optimizations to the edge of the mobile data network will not only greatly improve the quality of service for subscribers, but will also provide a foundation for applying new types of services at the edge of the mobile data network, such as terminating machine-to-machine (MTM) traffic at the edge (e.g., in the basestation), hosting applications at the edge, and performing analytics at the edge.
• MIOP@RNC220 includes a second service mechanism inmobile data network200.MIOP@RNC220 monitors all communication between theradio network controller140 and servingnode150. The monitored communications are all communications to and from the radio network controller and the rest of the core network.MIOP@RNC220 may provide one or more services for the mobile data network.MIOP@RNC220 preferably makes the decision of whether or not to allow breakout of data. IfMIOP@RNC220 decides to breakout data for a given subscriber session, it may send a message toMIOP@NodeB210 authorizing breakout byMIOP@NodeB210, or may decide to breakout the data atMIOP@RNC220, depending on the configured breakout decision criteria and selected radio channel. Because messages to and from the core network establishing the PDP context for a given subscriber session are monitored byMIOP@RNC220, the decision of whether or not to breakout data resides in theMIOP@RNC220.
• MIOP@Core230 includes a third service mechanism in themobile data network200.MIOP@Core230 may include all the same services asMIOP@RNC220, or any suitable subset of those services. If the decision is made not to provide services atMIOP@NodeB210 orMIOP@RNC220, these same services plus more sophisticated services can be performed atMIOP@Core230. Thus,mobile data network200 provides flexibility by allowing a decision to be made of where to perform which services. BecauseMIOP@NodeB210,MIOP@RNC220 andMIOP@Core230 preferably include some of the same services, the services between components may interact (e.g., MIOP@NodeB and MIOP@Core may interact to optimize TCP traffic between them), or the services may be distributed across the mobile data network (e.g., MIOP@NodeB performs breakout and provides services for high-speed traffic, MIOP@RNC performs breakout and provides services for low-speed traffic, and MIOP@Core provides services for non-broken out traffic). The MIOP system architecture thus provides a very powerful and flexible solution, allowing dynamic configuring and reconfiguring on the fly of which services are performed by the MIOP components and where. In addition, these services may be implemented taking advantage of existing infrastructure in a mobile data network.
• MIOP@NMS240 is a network management system that monitors and controls the functions ofMIOP@NodeB210,MIOP@RNC220, andMIOP@Core230.MIOP@NMS240 preferably includes MIOP internal real-time or near real-time performance data monitoring to determine if historical or additional regional dynamic changes are needed to improve services on themobile data network200.MIOP@NMS240 provides a user interface that allows a system administrator to operate and to configure how theMIOP components210,220 and230 function.
• Theoverlay network250 allowsMIOP@NodeB210,MIOP@RNC220,MIOP@Core230, andMIOP@NMS240 to communicate with each other. Theoverlay network250 is preferably a virtual private network primarily on an existing physical network in the mobile data network. Thus, whileoverlay network250 is shown inFIG. 2 separate from other physical network connections, this representation inFIG. 2 is a logical representation.
• FIG. 3 shows one suitable implementation of a physical network and the overlay network in a sample mobile data system. The existing physical network in the mobile data network before the addition of theMIOP@NodeB210,MIOP@RNC220, andMIOP@Core230 is shown by the solid lines with arrows. This specific example inFIG. 3 includes many NodeBs, shown inFIG. 1 as130A,130B,130C, . . . ,130N. Some of the NodeBs have a corresponding MIOP@NodeB.FIG. 3 illustrates that MIOP@NodeBs (such as210A and210N) can be placed in a basestation with its corresponding NodeB, or can be placed upstream in the network after a point of concentration (such as210A after POC3310).FIG. 3 also illustrates that a single MIOP@NodeB such asMIOP@NodeB1210A can service two different NodeBs, such asNodeB1130A andNodeB2130B. Part of the overlay network is shown by the dotted lines betweenMIOP@NodeB1210A and second point ofconcentration POC2320, betweenMIOP@NodeB3210C andPOC3315, betweenMIOP@NodeBN210N andPOC3315, and betweenPOC3315 andPOC2320. Note the overlay network in the radio access network portion is a virtual private network that is implemented on the existing physical network connections. The overlay network allows theMIOP@NodeBs210A,210C and210N to communicate with each other directly, which makes some services possible in themobile data network200 that were previously impossible.FIG. 3 showsMIOP@NodeB1210A connected to a second point ofconcentration POC2320. The broken arrows coming in from above atPOC2320 represent connections to other NodeBs, and could also include connections to other MIOP@NodeBs. Similarly,POC2320 is connected to a third point ofconcentration POC1330, with possibly other NodeBs or MIOP@NodeBs connected to POC1. TheRNC140 is shown connected toPOC1330, and to afirst router RT1340 in the core network. Therouter RT1340 is also connected to theSGSN150. While not shown inFIG. 3 for the sake of simplicity, it is understood that SGSN inFIG. 3 is also connected to the upstream core components shown inFIG. 2, includingGGSN160,OSN170 andinternet180.
• As shown inFIG. 3, the overlay network from the NodeBs toPOC1330 is a virtual private network implemented on existing physical network connections. However, the overlay network requires asecond router RT2350, which is connected via aphysical network connection360 toPOC1330, and is connected viaphysical network connection370 toMIOP@RNC220. Thissecond router RT2350 may be a separate router, or may be a router implemented withinMIOP@RNC220.MIOP@RNC220 is also connected torouter RT1340 via aphysical network connection380, and is also connected toMIOP@Core230.Physical connection380 inFIG. 3 is shown in a line with short dots because it is not part of the pre-existing physical network before adding the MIOP components (arrows with solid lines) and is not part of the overlay network (arrows with long dots). Note the connection fromMIOP@RNC220 toMIOP@Core230 is via existing physical networks in the core network.
• We can see from the configuration of the physical network and overlay network inFIG. 3 that minimal changes are needed to the existing mobile data network to install the MIOP components. The most that must be added is onenew router350 and three newphysical network connections360,370 and380. Once thenew router350 and newphysical network connections360,370 and380 are installed, therouter350 and MIOP components are appropriately configured, and the existing equipment in the mobile data network is configured to support the overlay network, the operation of the MIOP components is completely transparent to existing network equipment.
• As can be seen inFIG. 3, data on the overlay network is defined on existing physical networks from the NodeBs to POC1. From POC1 the overlay network is onconnection360 toRT2350, and onconnection370 toMIOP@RNC220. Thus, whenMIOP@NodeB210 inFIG. 2 needs to send a message toMIOP@RNC220, the message is sent by sending packets via a virtual private network on the physical network connections to POC1, then toRT2350, then toMIOP@RNC220. Virtual private networks are well-known in the art, so they are not discussed in more detail here.
• Referring toFIG. 4,MIOP@NodeB210 preferably includes abreakout mechanism410, anedge service mechanism430, and anoverlay network mechanism440. Thebreakout mechanism410 determinesbreakout preconditions420 that, when satisfied, allow breakout to occur at this edge location.Breakout mechanism410 inMIOP@NodeB210 communicates with thebreakout mechanism510 inMIOP@RNC220 shown inFIG. 5 to reach a breakout decision. Thebreakout mechanism410, after receiving a message fromMIOP@RNC220 authorizing breakout on connection setup intercepts in particular the setup of the transport layer (allocation of the UDP Port, IP address or AAL2 channel). For authorized sessions thebreakout mechanism410 will be configured in a way that all traffic belonging to this UDP Port, IP address to AAL2 channel will be forwarded to a data offload function. For traffic that should not be broken out, thebreakout mechanism410 sends the data on the original data path in the radio access network. In essence,MIOP@NodeB210 intercepts all communications to and from thebasestation130, and can perform services “at the edge”, meaning at the edge of the radio access network that is close to theuser equipment110. By performing services at the edge, the services to subscribers may be increased or optimizes without requiring hardware changes to existing equipment in the mobile data network.
• Thebreakout mechanism410 preferably includesbreakout preconditions420 that specify one or more criterion that must be satisfied before breakout of data is allowed. One suitable example of breakout preconditions is the speed of the channel. In one possible implementation, only high-speed channels will be broken out atMIOP@NodeB210. Thus,breakout preconditions420 could specify that subscribers on high-speed channels may be broken out, while subscribers on low-speed channels are not broken out atMIOP@NodeB210. When thebreakout preconditions420 are satisfied, theMIOP@NodeB210 registers the subscriber session withMIOP@RNC220. This is shown inmethod800 inFIG. 8.MIOP@NodeB210 intercepts and monitors network traffic to and from NodeB (basestation) (step810). When the traffic does not satisfy the breakout preconditions (step820=NO),method800 returns to step810. When the traffic satisfies the breakout conditions (step820=YES),MIOP@NodeB210 sends a message toMIOP@RNC220 on theoverlay network250 to register the subscriber session for breakout (step830). With the subscriber session registered withMIOP@RNC220, theMIOP@RNC220 will determine whether or not to breakout data for the subscriber session, and where the breakout is done, as explained in more detail below.
• Referring back toFIG. 4,MIOP@NodeB210 also includes anedge service mechanism430. Theedge service mechanism430 provides one or more services for themobile data network200. Theedge service mechanism430 may include any suitable service for the mobile data network including without limitation caching of data, data or video compression techniques, push-based services, charging, application serving, analytics, security, data filtering, new revenue-producing services, etc. The edge service mechanism is the first of three service mechanisms in the MIOP components. While thebreakout mechanism410 andedge service mechanism430 are shown as separate entities inFIG. 4, the first service mechanism could include bothbreakout mechanism410 andedge service mechanism430.
• MIOP@NodeB210 also includes anoverlay network mechanism440. Theoverlay network mechanism440 provides a connection to theoverlay network250 inFIG. 2, thereby allowingMIOP@NodeB210 to communicate withMIOP@RNC220,MIOP@Core230, andMIOP@NMS240. As stated above, theoverlay network250 is preferably a virtual private network primarily on an existing physical network in themobile data network200.
• Referring toFIG. 5,MIOP@RNC220 preferably includes abreakout mechanism510, anRNC service mechanism540, anoverlay network mechanism550, andbusiness intelligence560.Breakout mechanism510 includesbreakout criteria520 that specifies one or more criterion that, when satisfied, allows breakout of data.Subscriber registration mechanism530 receives messages fromMIOP@NodeB210, and registers subscriber sessions for which thebreakout preconditions420 inMIOP@NodeB210 are satisfied. When thebreakout mechanism510 determines thebreakout criteria520 is satisfied, thebreakout mechanism510 will then determine where the breakout should occur. When the breakout can occur atMIOP@NodeB210, theMIOP@RNC220 sends a message toMIOP@NodeB210 on theoverlay network250 authorizing breakout atMIOP@NodeB210. When the breakout should occur atMIOP@RNC220, thebreakout mechanism510 inMIOP@RNC220 performs the breakout as well for the traffic remaining then). This is shown in more detail inmethod1000 inFIG. 10. MIOP@RNC monitors network traffic between theradio network controller140 and the serving node150 (step1010). When the traffic does not satisfy the breakout criteria (step1020=NO),method1000 loops back tostep1010. When the network traffic satisfies the breakout criteria (step1020=YES), thebreakout mechanism510 determines whether the subscriber session is registered for breakout (step1030). A subscriber session is registered for breakout when theMIOP@NodeB210 determined the traffic satisfied the breakout preconditions and registered the subscriber session for breakout, as shown inFIG. 8. Returning toFIG. 10, when the subscriber is registered for breakout (step1030=YES),MIOP@RNC220 sends a message via theoverlay network250 toMIOP@NodeB210 authorizing breakout of traffic for the subscriber session (step1040).MIOP@NodeB210 may then breakout traffic for the subscriber session (step1050). When the subscriber is not registered for breakout (step1030=NO),method1000 checks to see if MIOP@RNC is going to do breakout (step1060). If not (step1060=NO),method1000 is done. When MIOP@RNC is going to do breakout (step1060=YES), the traffic is then broken out at MIOP@RNC (step1070).
• In one specific example, the breakout preconditions specify only high-speed channels are broken out atMIOP@NodeB210, and when the breakout preconditions are satisfied, the subscriber session is registered for breakout, as shown inFIG. 8.FIG. 10 illustrates that even when the breakout preconditions are not satisfied, breakout can still be performed atMIOP@RNC220. Thus, even if the subscriber session is on a low-speed channel, if all the other breakout criteria are satisfied, breakout of the low-speed channel may be performed atMIOP@RNC220. Themobile data network200 thus provides great flexibility in determining when to do breakout and where.
• Referring back toFIG. 5, theRNC service mechanism540 provides one or more services for the mobile data network.RNC service mechanism540 is the second of three service mechanisms in the MIOP components. TheRNC service mechanism540 may include any suitable service for the mobile data network, including without limitation caching of data, data or video compression techniques, push-based services, charging, application serving, analytics, security, data filtering, new revenue-producing services, etc.
• While thebreakout mechanism510 andRNC service mechanism540 are shown as separate entities inFIG. 5, the second service mechanism could include bothbreakout mechanism510 andRNC service mechanism540. Theoverlay network mechanism550 is similar to theoverlay network mechanism440 inFIG. 4, providing a logical network connection to the other MIOP components on theoverlay network250 inFIG. 2.MIOP@RNC220 also includesbusiness intelligence560, which includes:
• 1) historical subscriber information received from the mobile data network over time, such as mobility and location, volumes, traffic types, equipment used, etc.
• 2) network awareness, including NodeB load states, service area code, channel type, number of times channel type switching occurred for a PDP session, serving cell ID, how many cells and their IDs are in the active set, PDP context type, PDP sessions per subscriber, session duration, data consumption, list of Uniform Resource Locators (URLs) browsed for user classification, top URL browsed, first time or repeat user, entry point/referral URLs for a given site, session tracking, etc.
• 3) association of flow control procedures between NodeB and RNC to subscribers.
• Thebusiness intelligence560 may be instrumented by theRNC service mechanism540 to determine when and what types of MIOP services to perform for a given subscriber. For example, services for a subscriber on a mobile phone may differ when compared to services for a subscriber using a laptop computer to access the mobile data network. In another example, voice over internet protocol (VOIP) session could have the data broken out.
• Referring toFIG. 6, theMIOP@Core230 includes acore service mechanism610 and anoverlay network mechanism620.Core service mechanism610 provides one or more services for the mobile data network.Core service mechanism610 is the third of three service mechanisms in the MIOP components. Thecore service mechanism610 may include any suitable service for the mobile data network, including without limitation caching of data, data or video compression techniques, push-based services, charging, application serving, analytics, security, data filtering, new revenue-producing services, etc. In one specific implementation, theMIOP@Core230 is an optional component, because all needed services could be performed atMIOP@NodeB210 andMIOP@RNC220. In an alternative implementation,MIOP@Core230 performs some services, while MIOP@RNC performs others or none. Theoverlay network mechanism620 is similar to theoverlay network mechanisms440 inFIGS. 4 and 550 inFIG. 5, providing a logical network connection to the other MIOP components on theoverlay network250 inFIG. 2.
• Referring toFIG. 7, theMIOP@NMS240 is a network management system that monitors and manages performance of themobile data network200, and controls the function ofMIOP@NodeB210,MIOP@RNC220, andMIOP@Core230.MIOP@NMS240 preferably includes anetwork monitoring mechanism710, aperformance management mechanism720, asecurity management mechanism730, and aconfiguration management mechanism740. Thenetwork monitoring mechanism710 monitors network conditions, such as alarms, in themobile data network200. Theperformance management mechanism720 can enable, disable or refine certain services by supporting the execution of services in real-time or near real-time, such as services that gather information to assess customer satisfaction. Thesecurity management mechanism730 manages security issues in the mobile data network, such as intrusion detection or additional data privacy. Theconfiguration management mechanism740 controls and manages the configuration ofMIOP@NodeB210,MIOP@RNC220, andMIOP@Core230 in a way that allows them to dynamically adapt to any suitable criteria, including data received from the network monitoring mechanism, time of day, information received frombusiness intelligence560, etc.
• FIG. 9 shows samplebreakout criteria520 shown inFIG. 5 and used instep1020 inFIG. 10. Suitablebreakout criteria520 includes access point name, user equipment identifier, user equipment type, quality of service, subscriber ID, mobile country code, and mobile network code. For example,breakout criteria520 could specify to perform MIOP services for the operator's subscribers, and not to perform MIOP services for roamers. In another example, thebreakout criteria520 could specify to break out only video requests. A static breakout decision will be performed during PDP Context Activation. Based on IP flows (e.g. shallow packet inspection of the IP 5 tuple) only specific IP flows maybe identified and broken out dynamically within that PDP session (e.g., VOIP traffic), as discussed in more detail below with respect toFIG. 11.Breakout criteria520 expressly extends to any suitable criteria for making the breakout decision.
• Referring again toFIG. 10, when the traffic satisfies the breakout criteria (step1020=YES), and the subscriber session is registered for breakout (step1030=YES), MIOP@RNC sends a message to MIOP@NodeB authorizing breakout of traffic for this subscriber session (step1040). In response, MIOP@NodeB begins decrypting the bearer, examining the signaling and user IP traffic tunneled through it and may breakout the traffic for this subscriber session (step1050). Note, however, MIOP@NodeB may still decide not to breakout all traffic based on other criteria, such as type of IP request the destination of the traffic or the ISO Layer 7 Application of the decrypted user traffic. Determination of the Application may be performed simply by inspection of the IP 5-tuple or optionally via inspection at layer 7 using Deep Packet Inspection (DPI) techniques. This is shown in the specific example inFIG. 11.Method1050 inFIG. 10 is one suitable implementation ofstep1050 inFIG. 10. MIOP@NodeB monitors IP requests from the subscriber (step1110). When the user traffic IP request matches a specified type criteria (step1120=YES), the IP session is broken out for the subscriber (step1130). When the IP request does not match a specified criteria type (step1120=NO), no breakout is performed. For example, let's assume that IP requests to access video over the RTP layer 7 Application Protocol are broken out so the video data may be cached inMIOP@NodeB210, but other requests, such as Google searches, are not. The MIOP@NodeB monitors the IP requests from the subscriber (step1110), and when the subscriber session IP request carries RTP traffic is for a video file (step1120=YES), the IP session is broken out (step1130). Otherwise, the IP session is not broken out at MIOP@NodeB. This is one simple example to illustrate additional flexibility and intelligence within MIOP@NodeB that may determine whether or not to perform breakout for a given subscriber session at the MIOP@NodeB after being authorized by MIOP@RNC to perform breakout for that subscriber session. Any suitable criteria could be used to determine what to breakout and when at MIOP@NodeB once MIOP@NodeB has been authorized for breakout instep1040 inFIG. 10.
• Referring toFIG. 12,method1200 shows a method for determining when to run MIOP services. The Packet Data Protocol (PDP) activation context for a subscriber is monitored (step1210). A PDP context is established whenuser equipment110 connects to tower120 and the subscriber runs an application that triggers the PDP activation procedure. The core network will determine the subscriber, and perhaps corresponding user equipment. When MIOP services are allowed (step1220=YES), services for this subscriber session are run (step1230) upon the arrival of data from the subscriber. When MIOP services are not allowed (step1220=NO), no MIOP services are run. In one simple example, MIOP services in the mobile data network are allowed for authorized subscribers, but are not allowed for subscribers from a different wireless company that are roaming.
• MIOP services may require communicating between MIOP components on the overlay network. Referring toFIG. 13, amethod1300 shows communications by MIOP@NodeB when MIOP services are running (step1310). When the edge service mechanism requires communication with MIOP@RNC (step1320=YES), MIOP@NodeB exchanges messages with MIOP@RNC over the overlay network (step1330). When the edge service mechanism requires communication with MIOP@Core (step1340=YES), MIOP@NodeB exchanges messages with MIOP@Core over the overlay network (step1350). The overlay network thus allows the various MIOP components to communicate with each other when MIOP services are running.
• FIG. 14 shows amethod1400 that shows communications by MIOP@RNC when MIOP services are running (step1410). When the RNC service mechanism requires communication with MIOP@NodeB (step1420=YES), MIOP@RNC exchanges messages with MIOP@NodeB over the overlay network (step1430). When the RNC service mechanism requires communication with MIOP@Core (step1440=YES), MIOP@RNC exchanges messages with MIOP@Core over the overlay network (step1450).
• FIG. 15 shows amethod1500 that shows communications by MIOP@Core when MIOP services are running (step1510). When the core service mechanism requires communication with MIOP@NodeB (step1520=YES), MIOP@Core exchanges messages with MIOP@NodeB over the overlay network (step1530) relayed via MIOP@RNC. When the core service mechanism requires communication with MIOP@RNC (step1540=YES), MIOP@Core exchanges messages with MIOP@RNC over the overlay network (step1550).
• FIG. 16 shows amethod1600 that is preferably performed byMIOP@NMS240 inFIGS. 2 and 7. The performance and efficiency of the MIOP components that perform MIOP services are monitored (step1610). The MIOP components that perform MIOP services may includeMIOP@NodeB210,MIOP@RNC220, andMIOP@Core230, assuming all of these components are present in themobile data network200. When performance may be improved (step1620=YES), the performance of the MIOP components is adjusted (if implemented and applicable) by sending one or more network messages via the overlay network (step1630). Note also a human operator could also manually reconfigure the MIOP components to be more efficient.
• Referring toFIG. 17, implementations forMIOP@NodeB210 andMIOP@RNC220 are shown by way of example. Other implementations are possible within the scope of the disclosure and claims herein.User equipment110 is connected toNodeB130. Note theantenna120 shown inFIG. 2 is not shown inFIG. 17, but is understood to be present to enable the communication betweenuser equipment110 andNodeB130.MIOP@NodeB210 includes anedge cache mechanism1730, which is one suitable example ofedge service mechanism430 inFIG. 4.MIOP@NodeB210 includes an interface referred to herein as IuB Data Offload Gateway (IuB DOGW)1710. TheIuB DOGW1710 communicates on the Iub interface connection between the RNC and NodeB of a mobile data network. Thisgateway1710 implements thebreakout mechanism410 according to one or more specifiedbreakout preconditions420 shown inFIG. 4.IuB DOGW1710 includes aswitching application1740, anoffload data handler1750, and anRNC channel handler1760. Theswitching application1740 is responsible for monitoring data packets received fromNodeB130, forwards according to it configuration the broken out data packets to the offload data handler, relays the non-broken out data packets and control system flows to theRNC140 via the original connections in the RAN. While switchingapplication1740 is shown as two separate boxes inFIG. 17, this is done to visually indicate theswitching application1740 performs switching on two different interfaces, the network interface and overlay network interface, but theswitching application1740 is preferably a single entity.
• When a breakout decision is made andMIOP@RNC220 sends a message toMIOP@NodeB210 authorizing breakout (seestep1040 inFIG. 10), when MIOP@NodeB decides to breakout specified user data, the specified user data received by theswitching application1740 fromNodeB130 is broken out, which means theswitching application1740 routes the specified user data to theoffload data handler1750 so the broken out data is routed to the data path defined for breakout data. Theoffload data handler1750 may send the data to theedge cache mechanism1730 for processing, which can route the data directly toMIOP@RNC220 via the overlay network, as shown by the path with arrows going fromNodeB130 toMIOP@RNC220.
• User data that is not broken out and signaling traffic is routed directly back by theswitching application1740 to RNC. In this manner, non-broken out data and signaling traffic passes through theIuB DOGW1710 toRNC140, while broken out data is routed by theIuB DOGW1710 to a different destination. Note thatedge cache mechanism1730 may send messages toMIOP@RNC220 as shown inFIG. 17, but the broken out messages themselves are not sent toMIOP@RNC220.
• MIOP@RNC220 includes an interface referred to herein as IuPS data offload gateway (IuPS DOGW)1770.IuPS DOGW1770 forwards all signaling and non-broken out data traffic fromRNC140 toSGSN150 via the GTP tunnel.IuPS DOGW1770 includes thebreakout mechanism510,breakout criteria520 andsubscriber registration mechanism530 shown inFIG. 5 and discussed above with reference toFIG. 5.IuPS DOGW1770 may exchange messages withIuB DOGW1710 via the overlay network to perform any needed service inMIOP@NodeB210 orMIOP@RNC220. For the specific implementation shown inFIG. 17, while theIuPS DOGW1770 inMIOP@RNC220 does not include an offload data handler, theIuPS DOGW1770 could include an offload data handler and switching application similar to those shown inMIOP@NodeB210 whenMIOP@RNC220 also needs to perform breakout of data.
• TheIuPS DOGW1770 includes anRNC channel handler1780. TheRNC channel handlers1760 inMIOP@NodeB210 and1780 inMIOP@RNC220 monitor data traffic to and fromRNC140 related to a broken out subscriber session and provide a keep-alive channel maintenance mechanism.
• Specific methods are shown inFIGS. 18-21 that illustrate how the specific implementation inFIG. 17 could be used.FIGS. 18 and 19 show amethod1800 for setting up breakout of data. The UE sends a connection request to the RNC (step1810). The RNC sets up a radio link via NodeB (step1815). The RNC then sets up a network connection with NodeB (step1820). The UE and SGSN then communicate for the attach and authentication procedure (step1825). IuB DOGW detects the leading message in the attach and authentication procedure, and registers the subscriber session with IuPS DOGW when preconditions are fulfilled (e.g. UE is capable to carry high speed traffic) (step1830). During the attach and authentication procedure, IuPS DOGW monitors the security context sent from SGSN to RNC (step1835). IuPS DOGW then sends keys to IuB DOGW (step1840). These keys are needed to decipher (decrypt) the upcoming signaling and uplink user data and to cipher (encrypt) the downlink user data. UE then requests PDP context activation to SGSN (step1845). In response, SGSN sets up a network tunnel to RNC (step1850). IuPS DOGW monitors network tunnel setup from SGSN to RNC and makes a decision breakout=YES (step1855). IuPS DOGW sends a message to IuB DOGW indicating breakout=YES (step1860). Continuing onFIG. 19, SGSN sends a Radio Access Bearer (RAB) assignment request to UE (step1865). IuPS DOGW detects the RAB assignment request from SGSN to UE and replaces the SGSN transport address with IuPS DOGW transport address (step1870). IuPS DOGW sends a message to MIOP@Core indicating breakout=YES (step1875). RNC communicates with NodeB and UE to (re) configure signaling and data radio bearer (step1880). RNC acknowledges to SGSN when RAB assignment is complete (step1885). SGSN accepts PDP context activation by sending a message to UE (step1890). UE and SGSN may then exchange data for the PDP context (step1895).
• Referring toFIG. 20, amethod2000 begins by establishing a PDP context (step2010).Method1800 inFIGS. 18 and 19 include the detailed steps for establishing a PDP context. When breakout=YES, RAB assignment requests from SGSN to RNC are monitored by IuPS DOGW (step2020). IuPS DOGW modifies any RAB assignment requests from SGSN to RNC to replace the SGSN transport address in the RAB assignment request with the IuPS DOGW transport address (step2030) in case of matching breakout criteria during PDP context activation procedure. The switching application on IuB DOGW is configured upon the RAN transport layer setup to identify based on IP addresses and ports the broken out traffic and forwards this traffic to the Offload data handler1765, and forwards non-broken out traffic and control system data flows to the RNC (step2040).
• Referring toFIG. 21, amethod2100 begins when NodeB sends data towards RNC (step2110). The switching application in IuB DOGW redirects the broken out traffic to the edge service mechanism (step2120), such asedge cache mechanism1730 inFIG. 17. The switching application also forwards non-broken out data and signaling data to the RNC (step2130) via the original RAN connections. The RNC can still receive data for non-broken out traffic from MIOP@NodeB when breakout=YES (step2140). The RNC then sends non-broken out traffic from MIOP@NodeB from UE when breakout=YES to IuPS DOGW transport address specified in RAB assignment request (step2150).
• A simple example is now provided for the specific implementation inFIG. 17 to show how data can be cached and delivered byMIOP@NodeB210. Referring toFIG. 22,method2200 represents steps performed in the implementation inFIG. 17 for a cache miss. UE sends a data request to NodeB (step2210). NodeB sends the data request to IuB DOGW (step2215). We assume the requested data meets the offload criteria at MIOP@NodeB (step2220), which means MIOP@NodeB has been authorized to perform breakout and has determined this requested data should be broken out. IuB DOGW sends the data request to the edge cache mechanism (step2225). We assume the data is not present in the edge cache mechanism, so due to the cache miss, the edge cache mechanism sends the data request back to IuB DOGW (step2230). IuB DOGW then forwards the data request to MIOP@RNC via the overlay network (step2235). In the worst case the content is not cached on MIOP@RNC or MIOP@Core, MIOP@RNC routes the data request to via the overlay network to the MIOP@Core, which passes the data request up the line to the internet, which delivers the requested data to MIOP@Core, which delivers the requested data via the overlay network to MIOP@RNC (step2240). IuPS DOGW then sends the requested data to IuB DOGW (step2245). IuB DOGW then sends the requested data to the edge cache mechanism (step2250). The edge cache mechanism caches the requested data (step2255). The edge cache mechanism sends the requested data to IuB DOGW (step2260). The offload data handler in IuB DOGW sends the requested data to NodeB (step2265). NodeB then sends the requested data to UE (step2270). At this point,method2200 is done.
• Method2300 inFIG. 23 shows the steps performed for a cache hit in the specific implementation inFIG. 17. The UE sends the data request to NodeB (step2310). NodeB sends the data request to IuB DOGW (step2320). The requested data meets the offload criteria at MIOP@NodeB (step2330). IuB DOGW sends the data request to the edge cache mechanism (step2340). Due to a cache hit, the edge cache mechanism sends the requested data from the cache to IuB DOGW (step2350). The offload data handler in IuB DOGW sends the requested data to NodeB (step2360). Node B then sends the requested data to UE (step2370).Method2300 shows a great advantage in caching data at MIOP@NodeB. With data cached at MIOP@NodeB, the data may be delivered to the user equipment without any backhaul on the core network. The result is reduced network congestion in the core network while improving quality of service to the subscriber.
• The methods shown inFIGS. 18-23 provide detailed steps for the specific implementation inFIG. 17. Other implementations may have detailed steps that are different than those shown inFIGS. 18-23. These are shown by way of example, and are not limiting of the disclosure and claims herein.
• The architecture of the MIOP system allows services to be layered or nested. For example, the MIOP system could determine to do breakout of high-speed channels at MIOP@NodeB, and to do breakout of low-speed channels at MIOP@RNC. In another example, MIOP@NodeB may have a cache, MIOP@RNC may also have a cache, and MIOP@Core may also have a cache. If there is a cache miss at MIOP@NodeB, the cache in MIOP@RNC could be checked, followed by checking the cache in MIOP@Core. Thus, decisions can be dynamically made according to varying conditions of what data to cache and where.
• To support the MIOP services that are possible with themobile data network200 shown inFIG. 2, the preferred configuration ofMIOP@NodeB210 is a combination of hardware and software. The preferred configuration ofMIOP@RNC220 is also a combination of hardware and software. The preferred configuration ofMIOP@Core230 is software only, and can be run on any suitable hardware in the core network. The preferred configuration ofMIOP@NMS240 is software only, and can also be run on any suitable hardware in the core network.
• In the most preferred implementation, the various functions ofMIOP@NodeB210,MIOP@RNC220,MIOP@Core230, andMIOP@NMS240 are performed in a manner that is nearly transparent to existing equipment in the mobile data network. Thus, the components in prior artmobile data network100 that are also shown in themobile data network200 inFIG. 2 have no knowledge of the existence of the various MIOP components, with the exception of existing routers that may need to be updated with routing entries corresponding to the MIOP components. The MIOP services are provided by the MIOP components in a way that requires no changes to hardware and only minor changes to software (i.e., new router entries) in any existing equipment in the mobile data network, thereby making the operation of the MIOP components transparent to the existing equipment once the MIOP components are installed and configured. The result is a system for upgrading existing mobile data networks as shown inFIG. 1 in a way that does not require extensive hardware or software changes to the existing equipment. The MIOP services herein can thus be performed without requiring significant capital expenditures to replace or reprogram existing equipment.
• Referring toFIG. 24, one suitable hardware architecture forMIOP@NodeB2410 is shown.MIOP@NodeB2410 is one specific implementation forMIOP@NodeB210 shown inFIGS. 2,4 and17.MIOP@NodeB2410 is one suitable example of a breakout component that may be incorporated into an existing mobile data network. The specific architecture was developed based on a balance between needed function and cost. The hardware components shown inFIG. 24 may be common off-the-shelf components. They are interconnected and programmed in a way to provided needed function while keeping the cost low by using off-the-shelf components. The hardware components shown inFIG. 24 include asystem controller2412, aservice processor2420, asecurity subsystem2430, and atelco breakout subsystem2450. In one suitable implementation forMIOP@NodeB2410 shown inFIG. 24, thesystem controller2412 is an x86 system. Theservice processor2420 is an IBM Integrated Management Module version 2 (IMMv2). Thesecurity subsystem2430 includes an ATMEL processor and a non-volatile memory such as a battery-backed RAM for holding keys. Thetelco breakout system2450 performs the breakout functions forMIOP@NodeB2410. In this specific implementation, the x86 and IMMv2 are both on a motherboard that includes a Peripheral Component Interconnect Express (PCIe) slot. A riser card plugged into the PCIe slot on the motherboard includes thesecurity subsystem2430, along with two PCIe slots for thetelco breakout system2450. Thetelco breakout system2450 may include a telco card and a breakout card that performs breakout as described in detail above with respect toFIG. 17.
• One suitable x86 processor that could serve assystem controller2412 is the Intel Xeon E3-1220 processor. Onesuitable service processor2420 is an IBM Renassas SH7757, but other known service processors could be used. One suitable processor for thesecurity subsystem2430 is an ATMEL processor UC3L064, and one suitable non-volatile memory for thesecurity subsystem2430 is a DS3645 battery-backed RAM from Maxim. One suitable processor for thetelco breakout subsystem2450 is the Cavium Octeon II CN63XX.
• Various functions of theMIOP@NodeB2410 shown inFIG. 24 are divided amongst the different components. Referring toFIG. 25, thesystem controller2412 implements anappliance mechanism2510, aplatform services mechanism2520, and an edgeapplication serving mechanism2530. Theappliance mechanism2510 provides an interface to MIOP@NodeB that hides the underlying hardware and software architecture by providing an interface that allows configuring and using MIOP@NodeB without knowing the details of the underlying hardware and software. Theplatform services mechanism2520 provides messaging support between the components in MIOP@NodeB, allows managing the configuration of the hardware and software in MIOP@NodeB, and monitors the health of the components in MIOP@NodeB. The edgeapplication serving mechanism2530 allows software applications to run within MIOP@NodeB that perform one or more mobile network services at the edge of the mobile data network in response to broken-out data received from user equipment or sent to user equipment. In the most preferred implementation, the data broken out and operated on by MIOP@NodeB is Internet Protocol (IP) data requests received from the user equipment and IP data sent to the user equipment. The edgeapplication service mechanism2530 may serve both applications provided by the provider of the mobile data network, and may also serve third party applications as well. The edgeapplication serving mechanism2530 provides a plurality of mobile network services to user equipment at the edge of the mobile data network in a way that is mostly transparent to existing equipment in the mobile data network.
• Referring toFIG. 26, theservice processor2420 includes a thermal monitor/control mechanism2610, ahardware monitor2620, a fail-to-wire control mechanism2630, akey mechanism2640, a system controller monitor/reset mechanism2650, and a display/indicator mechanism2660. The thermal monitor/control mechanism2610 monitors temperatures and activates controls to address thermal conditions. For example, thethermal monitor2610 monitors temperature within the MIOP@NodeB enclosure, and activates one or more fans within the enclosure when the temperature exceeds some threshold. In addition, the thermal monitor/control mechanism2610 may also monitor temperature in the basestation external to the MIOP@NodeB enclosure, and may control environmental systems that heat and cool the basestation itself external to the MIOP@NodeB enclosure. Thehardware monitor2620 monitors hardware for errors. Examples of hardware that could be monitored withhardware monitor2620 include CPUs, memory, power supplies, etc. Thehardware monitor2620 could monitor any of the hardware withinMIOP@NodeB2410.
• The fail-to-wire control mechanism2630 is used to switch a fail-to-wire switch to a first operational state when MIOP@NodeB is fully functional that causes data between the upstream computer system and the downstream computer system to be processed byMIOP@NodeB2410, and to a second failed state that causes data to be passed directly between the upstream computer system and the downstream computer system without being processed byMIOP@NodeB2410. Thekey mechanism2640 provides an interface for accessing thesecurity subsystem2430. The system controller monitor/reset mechanism2650 monitors the state of thesystem controller2412, and resets thesystem controller2412 when needed. The display/indicator mechanism2660 activates a display and indicators on the front panel of the MIOP@NodeB to provide a visual indication of the status of MIOP@NodeB.
• Referring toFIG. 27, thesecurity subsystem2430 includes akey storage2702 that is a non-volatile storage for keys, such as a battery-backed RAM. Thesecurity subsystem2430 further includes akey mechanism2710 and atamper detection mechanism2720.Key mechanism2710 stores keys to the non-volatilekey storage2702 and retrieves keys from the non-volatilekey storage2702. Any suitable keys could be stored in thekey storage2702. Thesecurity subsystem2430 controls access to the keys stored inkey storage2702 usingkey mechanism2710. Thetamper detection mechanism2720 detects physical tampering of MIOP@NodeB, and performs functions to protect sensitive information within MIOP@NodeB when physical tampering is detected. The enclosure for MIOP@NodeB includes tamper switches that are triggered if an unauthorized person tries to open the box. In response, the tamper detection mechanism may take any suitable action, including actions to protect sensitive information, such as not allowing MIOP@NodeB to boot the next time, erasing keys inkey storage2702, and actions to sound an alarm that the tampering has occurred.
• Referring toFIG. 28, thetelco breakout system2450 includes atelco card2802, abreakout mechanism2810, and anoverlay network mechanism2820.Telco card2802 is any suitable card for handling network communications in the radio access network.Breakout mechanism2810 is one specific implementation forbreakout mechanism410 shown inFIG. 4.Breakout mechanism2810 performs the breakout functions as described in detail above. Thebreakout mechanism2810 interrupts the connection between the NodeB and the next upstream component in the radio access network, such as the RNC, as shown inFIG. 2. Non-broken out data from the upstream component is simply passed through MIOP@NodeB to the NodeB. Non-broken out data from the NodeB is simply passed through MIOP@NodeB to the upstream component. Note the path for non-broken out data is the traditional path for data in the mobile data network before the MIOP components were added. Broken-out data is intercepted by MIOP@NodeB, and may be appropriate processed at MIOP@NodeB, or may be routed to an upstream component via a different data path, such as to MIOP@RNC via the overlay network. Thetelco breakout system2450 includes anoverlay network mechanism2820 that allowsMIOP@NodeB2410 to communicate via the overlay network. For example,MIOP@NodeB2410 could useoverlay network mechanism2820 to communicate withMIOP@RNC220 or to communicate with other MIOP@NodeBs.
• Theedge application mechanism2530 may provide many different mobile network services. Examples of some of these services are shown inFIG. 29. This specific implementation foredge application mechanism2530 includes anedge caching mechanism2910, a push-basedservice mechanism2920, a third party edgeapplication serving mechanism2930, ananalytics mechanism2940, afiltering mechanism2950, a revenue-producingservice mechanism2960, and acharging mechanism2970. Theedge caching mechanism2910 is one suitable implementation ofedge cache mechanism1730 shown inFIG. 17, and includes the functions described above with respect toFIG. 17. The push-basedservice mechanism2920 provides support for any suitable push-based service, whether currently known or developed in the future. Examples of known push-based services include without limitation incoming text messages, incoming e-mail, instant messaging, peer-to-peer file transfers, etc.
• The third party edgeapplication serving mechanism2930 allows running third party applications that provide mobile network services at the edge of the mobile data network. The capability provided by the third party edgeapplication serving mechanism2930 opens up new ways to generate revenue in the mobile data network. The operator of the mobile data network may generate revenue both from third parties that offer edge applications and from subscribers who purchase or use edge applications. Third party applications for user equipment has become a very profitable business. By also providing third party applications that can run at the edge of the mobile data network, the experience of the user can be enhanced. For example, face recognition software is very compute-intensive. If the user were to download an application to the user equipment to perform face recognition in digital photographs, the performance of the user equipment could suffer. Instead, the user could subscribe to or purchase a third party application that runs at the edge of the mobile data network (executed by the third party edge application serving mechanism2930) that performs face recognition. This would allow a subscriber to upload a photo and have the hardware resources in MIOP@NodeB perform the face recognition instead of performing the face recognition on the user equipment. We see from this simple example it is possible to perform a large number of different functions at the edge of the mobile data network that were previously performed in the user equipment or upstream in the mobile data network. By providing applications at the edge of the mobile data network, the quality of service for subscribers increases.
• Theanalytics mechanism2940 performs analysis of broken-out data. The results of the analysis may be used for any suitable purpose or in any suitable way. For example, theanalytics mechanism2940 could analyze IP traffic on MIOP@NodeB, and use the results of the analysis to more intelligently cache IP data byedge caching mechanism2910. In addition, theanalytics mechanism2940 makes other revenue-producing services possible. For example, theanalytics mechanism2940 could track IP traffic and provide advertisements targeted to user equipment in a particular geographic area served by the basestation. Because data is being broken out at MIOP@NodeB, theanalytics mechanism2940 may perform any suitable analysis on the broken out data for any suitable purpose.
• Thefiltering mechanism2950 allows filtering content delivered to the user equipment by MIOP@NodeB. For example, thefiltering mechanism2950 could block access to adult websites by minors. This could be done, for example, via an application on the user equipment or via a third party edge application that would inform MIOP@NodeB of access restrictions, which thefiltering mechanism2950 could enforce. Thefiltering mechanism2950 could also filter data delivered to the user equipment based on preferences specified by the user. For example, if the subscriber is an economist and wants news feeds regarding economic issues, and does not want to read news stories relating to elections or politics, the subscriber could specify to exclude all stories that include the word “election” or “politics” in the headline. Of course, many other types of filtering could be performed by thefiltering mechanism2950. Thefiltering mechanism2950 preferably performs any suitable data filtering function or functions, whether currently known or developed in the future.
• The revenue-producingservice mechanism2960 provides new opportunities for the provider of the mobile data network to generate revenue based on the various functions MIOP@NodeB provides. An example was given above where theanalytics mechanism2940 can perform analysis of data broken out by MIOP@NodeB, and this analysis could be provided by the revenue-producingservice mechanism2960 to interested parties for a price, thereby providing a new way to generate revenue in the mobile data network. Revenue-producingservice mechanism2960 broadly encompasses any way to generate revenue in the mobile data network based on the specific services provided by any of the MIOP components.
• Thecharging mechanism2970 provides a way for MIOP@NodeB to inform the upstream components in the mobile data network when the subscriber accesses data that should incur a charge. Because data may be provided to the subscriber directly by MIOP@NodeB without that data flowing through the normal channels in the mobile data network, thecharging mechanism2970 provides a way for MIOP@NodeB to charge the subscriber for services provided by MIOP@NodeB of which the core network is not aware. Thecharging mechanism2970 tracks the activity of the user that should incur a charge, then informs a charging application in the core network that is responsible for charging the subscriber of the charges that should be billed.
• The hardware architecture of MIOP@NodeB shown inFIGS. 24-29 allows MIOP@NodeB to function in a way that is mostly transparent to existing equipment in the mobile data network. For example, if an IP request from user equipment may be satisfied from data held in a cache byedge caching mechanism2910, the data may be delivered directly to the user equipment by MIOP@NodeB without traversing the entire mobile data network to reach the Internet to retrieve the needed data. This can greatly improve the quality of service for subscribers by performing so many useful functions at the edge of the mobile data network. The core network will have no idea that MIOP@NodeB handled the data request, which means the backhaul on the mobile data network is significantly reduced. The MIOP components disclosed herein thus provide a way to significantly improve performance in a mobile data network by adding the MIOP components to an existing mobile data network without affecting most of the functions that already existed in the mobile data network.
• FIG. 30A is a block diagram of a mobile data network that includes a push mechanism3010 (parts A-C) to support push based services at the edge of a mobile data network. The push mechanism3010 is preferably a software entity with portions of the mechanism residing on the MIOP@NodeB210 (3010A), the MIOP@RNC220 (3010B), and the MIOP@Core230 (3010C). Thepush mechanism3010A at the MIOP@NodeB is described above at the push-basedservice mechanism2920. In the following description some functions of the push mechanism will be described as taking place on one or more of the MIOP components. Where a location is not specified, the functions of the push mechanism may take place on any one of the MIOP components where it would be most convenient. TheMIOP@NodeB210 includes anIP address pool3012 as described further below.
• FIG. 30B is a block diagram similar toFIG. 30A and illustrates address translation at the MIOP@NodeB in a mobile data network.FIG. 30B shows the same basic blocks of the mobile data network shown inFIG. 30A except theSGSN150 andGGSN160 have been combined into asingle block XGSN150/160 and theOSN170 is not shown for simplicity. Themobile network path3014 is shown connecting the components from theUE110 to theinternet180. The MIOP components (MIOP@NodeB210,MIOP@RNC220 and MIOP@Core230) are connected to each other and to theinternet180 by theoverlay network250. For broken outuser traffic3016,address translation3018 occurs at theMIOP@NodeB210. For a broken out PDP session, theMIOP@NodeB210 will translate the GGSN provided UE IP Address (used by the UE as source IP address in user data packets) into the MIOP assigned UE IP Address. This process is called network address translation (NAT). The originalGGSN IP address3022 assigned to the UE is used to communicate with the UE by theMIOP@NodeB210 through theNodeB130. The MIOP assignedUE address3020 is used upstream from theMIOP@NodeB210 and visible within theinternet180, meaning that it is the address the internet will use to push data to the UE. The MIOP assigned UE IP address is referred herein as a translated or a ‘NATed’ IP Address.
• Before sending UE data packets to an external Push function through theOSN170, the PDP address in the packets received from the UE is replaced with the NATed IP address from an address pool3012 (FIG. 30A) being managed by the MIOP@NodeB communicating with the UE. The push function sees this NATed IP address in the packets received from the internet push service and reverse NATs to the original GGSN IP address before sending the packets down to the UE as the destination address. This downlink packet is received by theMIOP@RNC220 from the internet via theOSN170 at theMIOP@Core230. In a normal scenario, when the data bearers (mobile network connections) are established for this PDP context, the data will be forwarded to MIOP@NodeB to be injected on the Iub interface if the PDP context was offloaded (broken out) at MIOP@NodeB. However if the PDP context has gone into the preserved state due to UE inactivity, there is no dedicated bearer associated with that PDP context in the network to carry the push data and the received push data cannot be delivered to the UE since MIOP nodes are not active entities as far as the signaling in the mobile data network is concerned, i.e. they cannot trigger any signaling procedure to establish a data bearer. In this scenario for an offloaded data session (PDP context), the push mechanism triggers a paging procedure from the SGSN to establish a data bearer to send the push data to the UE. The push mechanism3010 initiates a paging request on the mobile data network to trigger a service request to establish communication with the user equipment in order to push the data to the user equipment from the breakout system as described further below.
• FIG. 31 is a flow diagram of amethod3100 for supporting a push data service on a breakout system for a UE with a PDP context in a preserved state. The steps of this flow diagram are primarily performed by the push function3010 (parts A-C) described above or other entities in the mobile data network in response to functions performed by the push function3010. First, offload a PDP context with a UE (break out) at the MIOP@NodeB, which is then placed into a preserved state by the network due to subscriber inactivity (step3110). Receive push data from an internet push service through the OSN170 (FIG. 30A) (step3120). Determine if the received push data is for UE with PDP context in a preserved state (step3130). If the received push data is not for UE with PDP context in a preserved state (step3130=no) then send the push data normally (pass through data path at the MIOP@NodeB) (step3140). If the received push data is for UE with PDP context in a preserved state (step3130=yes) then trigger a mobile network paging procedure from the SGSN to establish a data bearer to download the push data to the UE (step3150). Next, the core network performs a paging procedure to setup a data bearer (step3160). The MIOP push mechanism the sends push data to the UE on the data bearer (step3170). The method is then done.
• FIG. 32 is a flow diagram of amethod3110 for implementingstep3110 in the flow diagram ofFIG. 31. The steps of this flow diagram are performed by the push function3010 (parts A-C) and other entities in the mobile data network as described above formethod3100. Establish a PDP context with a UE and offload (break out) at MIOP@NodeB (step3210). The broken out PDP context is placed into a preserved state by the mobile data network, for example when the UE goes into an idle state (step3220). On the Iub DOGW, release the radio resource control (RRC) connection data, delete the UE context data, but maintain the allocated NAT IP address (step3230). The method is done.
• FIG. 33 is a flow diagram of amethod3300 for implementingsteps3150 through3370 in the flow diagram ofFIG. 31. The steps of this flow diagram are performed by the push function3010 (parts A-C) and other entities in the mobile data network as described above formethod3100. At the MIOP@RNC, forward received push data to the Iub DOGW and also a copy to the GGSN via the OSN after replacing the NATed MIOP IP address with the original GGSN provided UE IP address (Step3310). At the MIOP@NodeB, buffer push data until an “Initiate Data Flow Indication” from the Iub DOGW arrives (Step3312). The GGSN sends push data packets to SGSN, which initiates the paging request (Step3314). Triggered by the paging request the UE establishes a radio resource control (RRC) connection between itself and the RNC (Step3316). UE sends a “Service Request” message to the SGSN and upon establishment of the Signaling Connection and the receipt of the NAS “Service Request” message the Iub DOGW registers the UE with the MIOP@RNC (Step3318). The initiation of the “Service Request” results in the establishment of a RAB connection in the network for this PDP context (Step3320). When the data path is established, MIOP@RNC sends the NATed IP address (allocated by the Iub DOGW during a previous registration) to the Iub DOGW for this PDP context and the Iub DOGW correlates it with the UE and the new RAB connection (Step3322). Iub DOGW sends “Initiate Data Flow Indication” to the push mechanism at the MIOP@NodeB (Step3324). After the data path is setup, the push mechanism at the MIOP@NodeB starts downloading push data to the UE (Step3326). The DL data initially buffered at MIOP@NodeB would be the first set of packets to be forwarded towards the UE through the NodeB (Step3328). As a result ofstep3314, the GGSN/SGSN forwards the same push data packets to the UE but these duplicate DL packets from the SGSN for the UE are dropped by the IuPS DOGW (step3330) to prevent the UE from getting the same push data twice. This is continued until the RAB is re-established. The method is then done.
• Method3300 illustrates the initial flow of push data to the UE. The duplicate data that is sent by the GGSN/SGSN is dropped by thepush mechanism3010B. The entire push data may not all be buffered at thepush mechanism3010A. Push data that is received after the RAB is setup is forwarded by the MIOP@RNC to thepush mechanism3010A and then sent to the UE.
• FIG. 34 is a flow diagram that further illustrates the method in the flow diagrams inFIGS. 31-33.FIG. 34 provides a graphical format that shows the source and destination of control signals and data flows described inFIGS. 31-33. InFIG. 34, control signals are shown in solid lines and data flows are shown in dotted lines. The right side ofFIG. 34 supplies the step numbers inFIGS. 31-33 that correspond to the flow lines to the left of the step numbers. The entities that are the source and destination of the data and control are shown at the top and include: user equipment (UE)110,Iub DOGW1710,push mechanism3010A at the MIOP@NodeB,RNC140,push mechanism3010B at the MIOP@RNC,push mechanism3010C at the MIOP@Core, theGGSN150 andSGSN160. Note that actions by theMIOP@RNC210 include functions performed by theIuPS DOGW1770 inFIG. 17, and the functions by the push mechanism may include some of the native MIOP functions but shown as functions of the push mechanism for simplicity.
• In the prior art, communication between theRNC140 and theUE110 is accomplished over radio channels using radio link control (RLC) protocol. Communication between theRNC140 and the UE using RLC relies on an RLC context recognized at each location to control the communication. An RLC context is the RLC protocols that are used to communicate between the RLC entities over the radio interface including the RLC protocol data units (PDUs), control and status.FIG. 35 describes the data structure of anRLC context3500 according to the prior art. The table inFIG. 35 shows afield name3510, afield description3512 and thesize3514 in bytes for each field in an RLC context.
• FIG. 36 is a block diagram of abreakout system3600 utilizing the RLC reset command when the ciphering context is out of synchronization.FIG. 36 is similar to that shown inFIG. 17. Thebreakout system3600 inFIG. 36 includes some of the same structure as described above with reference toFIG. 17. With reference toFIG. 36 additional details of the breakout system will be described including the features of the RLC reset by the breakout system as claimed herein. As described above, theMIOP@NodeB210 includes an interface referred to herein as IuB Data Offload Gateway (IuB DOGW)1710. TheIuB DOGW1710 communicates on the Iub interface connection between the RNC and NodeB of a mobile data network. Thisgateway1710 implements thebreakout mechanism410 according to one or more specifiedbreakout preconditions420 shown inFIG. 4. The switching application described above with reference toFIG. 17 is not shown here for simplicity.
• Again referring toFIG. 36, theIuB DOGW1710 communicates on the Iub interface connection between theRNC140 andNodeB210 of a mobile data network. TheIuB DOGW1710 includes two RLC entities, theRNC channel handler1760 and theoffload data handler1750. An RLC entity is a hardware structure that is capable of supporting UMTS Radio Link Protocol (RLC) communications as known in the prior art. Theoffload data handler1750 is an RLC entity that supports RLC communication between the UE and the MIOP@NodeB. TheRNC channel handler1760 is an RLC entity that supports RLC communication between theMIOP@NodeB210 and theRNC140. If communication to theUE110 is scheduled on a high speed channel,MIOP@NB210 is operating two different traffic streams using these two RLC entities. The first data traffic stream is optimized (e.g. cached) subscriber traffic between the UE and MIOP@NodeB. A second data stream is between theMIOP@NodeB210 andRNC140. These two data streams or data flows are processed by these twodifferent RLC entities1750,1760. Since these two RLC entities are not directly synchronized, they may drift apart and become out of synchronization which will cause errors and reduced quality of experience for the user.
• This second data stream between theMIOP@NodeB210 and theRNC140 includes maintenance data or random data that is sent over this data path in order to keep the connections alive with the backend. Amaintenance data handler3518 is used to provide the maintenance data to theRNC channel handler1760 to keep the RNC from shutting down or degrading the high speed connection to a low speed connection.Communication line3624 represents communication from theRNC140 to theUE110 that is not broken out through the MIOP@NodeB. This communication line is physically passing through theIuB DOGW1710 but is being passed through by theswitching application1740 shown inFIG. 17.
• FIG. 37 illustrates additional features of theRLC data structures3620,3622 introduced inFIG. 36.RLC data structures3620,3622 are hardware structures in the RLC entity to support communication on the radio channels. AnRLC data structure3620,3622 includes atransmission queue3710, aretransmission queue3712, and a service data unit (SDU)queue3714. The IuB DOGW1710 (FIG. 37) may use the RLC data structures as described herein to perform the RLC reset and to determine when the reset should be done.
• As introduced above, theMIOP@NodeB210 is operating two different traffic flows using the twoRLC entities1750,1760. These two traffic flows are not inherently synchronized because they are separate RLC communication paths. However, the MIOP@NodeB needs to keep them in synchronization to insure that the ciphering contexts are in synchronization for data sent over the communication link3624 (FIG. 36) between the RNC and the UE. The MIOP@NodeB monitors thesequence number3718 in the RLC data structures of theoffload data hander1750 and thesimilar sequence number3718 in the RLC data structures of theRNC channel handler1760 to determine if they become unsynchronized. If they become unsynchronized, the MIOP@NodeB can issue a RLC reset to the UE and to the RNC to bring them into synchronization again. By triggering an RLC Reset procedure towards the RNC on the one hand and the UE on the other hand, the Iub DOGW is able to ensure that the ciphering contexts at the RNC and the UE are synchronized very quickly so the UE and the RNC can continue to exchange data packets successfully over the established radio bearers after RLC Reset for a better user experience. Conversely, if the IuB DOGW does not perform the reset and the communication continues the RNC itself may trigger an RLC Reset to bring the ciphering contexts in sync, however due to the delay this may result in a diminished quality of experience for the user.
• The IuB DOGW1710 (FIG. 36) may also monitor the RLC data structures to determine when the communication is moved from a low to high frequency channel by monitoring the low to highfrequency channel command3716 on theSDU queue3714. When the channel is moved from the low to high frequency channel the ciphering context becomes unsynchronized. Thus, by monitoring this command the IuB DOGW can increase the quality of experience by performing a reset in both directions when this command is detected. The IuB DOGW initiates an RLC reset towards the UE and the RNC by using the Reset and Reset ACK protocol data unit (PDU)3720 in theSDU queue3714 of theoffload data handler1750 and theRNC channel handler1760.
• FIG. 38 is a flow diagram of amethod3800 for the breakout system to utilize a RLC reset command synchronization during breakout in a mobile data network with a breakout system. The steps of this flow diagram are preferably performed by the Iub DOGW and other entities in the mobile data network as described herein. The MIOP@NodeB breaks out a data session to the UE as described herein (step3810). The MIOP@NodeB intercepts and monitors network traffic to/from the NodeB associated with the UE (step3820). If the sequence numbers of the two RLC entities at the MIOP@NodeB are out of sync (step3830=yes) then the MIOP@NodeB performs a RLC reset towards the UE and towards the RNC (step3850). If the sequence numbers are not out of sync (3830=no) then if the communication to the UE is moved to a high frequency channel (step3840=yes) then the MIOP@NodeB performs a RLC reset towards the UE and towards the RNC (step3850) and return tostep3820. If the communication has not moved to a high frequency channel (step3840=no) then continue to intercept and monitor network traffic (return to step3820).
• FIG. 39 is a block diagram of a mobile data network with a breakout system that provides cooperative mobility management. Themobile data network200 shown inFIG. 39 is similar to that shown inFIG. 2 except that inFIG. 39 the mobile data network is shown with twoantennas120A,120B, twoNodeBs130A,130B and the associatedMIOP@NodeBs210A,210B to illustrate a mobility event. It is assumed for this example that the twoNodeBs130A and130B are in adjacent cells. For the illustrated example, a mobility event occurs when theUE110 moves from the vicinity of theSource NodeB130A to the vicinity of theTarget NodeB130B as indicated by thearrow3910. Thesystem200 will handle the mobility event depending on the status of the communication between the UE and the system as described further below. As described herein, mobility management is supported by an optimizer in each of the MIOP platforms also referred to as service mechanisms in the claims. Thesource MIOP@NodeB210A has anIub Optimizer3912A and thetarget MIOP@NodeB210B has anIub Optimizer3912B. TheMIOP@RNC220 has anRNC Optimizer3914 and theMIOP@Core230 has aGi Optimizer3916. TheGi Optimizer3916 takes its name from the Gi interface (not shown) of the mobile data network. The other components are the same as those described above with reference toFIG. 30 andFIG. 2. The optimizers are preferably software entities with portions residing on the MIOP platforms. In the following description some functions of the optimizers will be described as taking place on one or more of the MIOP components. Where a location is not specified, the functions of the optimizer may take place on any one of the MIOP components where it would be most convenient.
• FIG. 40 is a block diagram that further illustrates cooperative mobility management in a mobile data network by showing addition detail of some of the blocks illustrated inFIG. 39. As discussed above, the system includes anIub Optimizer3912A at thesource MIOP@NodeB210A, and aGi Optimizer3916 at theMIOP@Core230. When a MIOP@NodeB detects a mobility event for a broken out UE, theIub optimizer3912A coordinates with theGi optimizer3916 to transfer the TCP/UDP connection established between the UE and theIuB Optimizer3912A to theGi Optimizer3916. This transfer is described further below. The transfer of the TCP/UDP connection to the Gi optimizer may require tunnel stitching at the MIOP@RNC depending on the PDP context state and the RRC state of the UE as described below.
• Again referring toFIG. 40, theUE110 has anapplication4010 with aTCP context4012. There is a matchingTCP context4014 for this application stored with the Iub Optimizer4012A at thesource MIOP@NodeB210A that is used to maintain the offloadeddata flow4016. The offloaded data flow is between the UE and theinternet180 through theSource MIOP@NodeB210A, theMIOP@RNC220, and theMIOP@Core230. After a mobility event is detected as described above, theTCP context4014 for the UE is transferred4010 from theIub Optimizer3912A to theGi Optimizer3916. Subsequently to transferring the TCP context,data flow4016 to the UE is served by theGi Optimizer3916. TheApplication4010 may include an application context or related data that is sent with the TCP context. For example, in a file transfer protocol (FTP) the byte count of the bytes transferred could be sent so the file transfer would not need to be restarted in case of a failure.
• FIG. 40 further illustrates management of radio link control (RLC) context for cooperative mobility management in a mobile data network. TheUE110 has aRLC context4020. TheSource MIOP@NodeB210A has acorresponding RLC context4022 for the UE and aRLC context4024 corresponding to theRLC context4026 in theRNC140. Ciphering between theUE110 and theRNC140 is maintained by theMIOP@NodeB210A with theseRLC contexts4022 and4024. When the TCP context is transferred4010 to theGi Optimizer3916 the data will flow from the GI Optimizer via theRNC140 to theUE110 transparent to the MIOP@NodeB. Thus the RCL contexts stored in the MIOP@NodeB will no longer be valid causing the ciphering context to go out of sync. An RLC reset procedure is used to resynchronize the ciphering context between theUE110 and theRNC140 after the transfer for a PDP context in the active state. A UE's PDP context is in a preserved state if the UE is inactive. Mobility may occur with the PDP context in a preserved or active state. If the system detects mobility with a preserved state by the PDP context becoming active at another NodeB, the system can transfer the TCP context to the Gi Optimizer but does not need to perform the RLC reset.
• FIG. 41 is a block diagram of a mobile data network that illustrates address translation at the MIOP@Core and stitching of tunnels for mobility management. Prior to the mobility event, address translation is used for broken outuser traffic3016 as described above with reference toFIG. 30. As described above, for a broken out PDP session, theMIOP@NodeB210 will translate the GGSN provided UE IP Address into the MIOP assigned UE IP Address. The originalGGSN IP address3022 assigned to the UE is used to communicate with the UE by theMIOP@NodeB210 through theNodeB130. The MIOP assignedUE address3020 is used upstream from theMIOP@NodeB210 and visible within theinternet180. In order to minimize the negative effects to established IP sessions when the xGSN are in path again, after the TCP context is transferred to the Gi Optimizer theMIOP@Core230 translates the GGSN assignedUE address4114 to the NATed IP address as shown at4110 inFIG. 41. The tunnels may also be stitched4120 if needed as described below.
• Again referring toFIG. 41, transferring the TCP context as described above may requireGTP tunnel stitching4120 at the MIOP@RNC depending on the PDP context (active or passive) and the UE RRC state (connected or idle). For example, when the PDP context is in the active state and the UE is in the RRC connected mode and a mobility event occurs, the MIOP@RNC stitches together the GTP tunnel. Stitching the GTP tunnel means that the MIOP@RNC sets up forwarding data received from the RNC to the SGSN and vise versa. This tunnel stitching is described in the flow with reference toFIG. 44.
• FIG. 41 further illustrates the TCP connections that will be transferred to support mobility management as described herein. Prior to the TCP connection transfer, the connections appear as shown for the broken outtraffic3016. Afirst connection4122A connects theUE110 to theMIOP@NodeB210. Thisfirst connection4122A uses anIP address3022 assigned by the GGSN as described above. Thesecond connection4124B connects theMIOP@NodeB210 to a network resource on theinternet180. Thesecond connection4124A uses anaddress3020 that is assigned by the MIOP system.Address translation3018 is performed at the MIOP@NodeB between these connections as described above. For a broken out context as described above, thefirst connection4122A allows theUE110 to receive data from the MIOP@NodeB that is cached, or if requested data is not available, the MIOP@NodeB may access the needed data over thesecond connection4124A. After the TCP transfer, the two connections are as shown at4110 at the bottom ofFIG. 41. Now thefirst connection4122B connects theUE110 to theMIOP@Core230 and thesecond connection4124B connects theMIOP@Core230 to theinternet180. The addresses are now Nated4118 at theMIOP@Core230 as described above.
• To support mobility, the connections between the UE and the Iub Optimizer is moved to the MIOP@Core as described herein. To move the connections, the TCP context is moved from the MIOP@NodeB to the MIOP@Core. An example of additional steps needed for transferring the TCP context will now be described. First, it is preferable to block all subsequent receives to the connection. This allows the optimizers to establish a know state at the time of the TCP context transfer. The Iub optimizer then reads in all data received in the socket buffer associated with the connection so that the data can be forwarded to the new connection. Next, the Iub optimizer invokes a kernel software module to determine the socket details for the connection. The details of the connection may include the TCP state, IP address, and port number. The Iub Optimizer sends the socket details to the Gi Optimizer at the MIOP@Core. The Gi Optimizer creates a new socket at the Gi Optimizer with the socket details. The Gi Optimizer then reinstates all the data buffers to the new socket with data from the previous connection. Transferring the TCP context is further described below with reference toFIG. 46.
• FIG. 42 is a flow diagram of amethod4200 for cooperative mobility management in a mobile data network with a breakout system. The steps of this flow diagram are performed by the Iub Optimizer and the Gi Optimizer and other entities in the mobile data network as described herein. Establish a PDP context with a UE and offload (break out) at MIOP@NodeB (step4210). The broken out PDP context optionally is then placed into a preserved state by the mobile data network, for example when the UE goes into an idle state (step4220). Detect a mobility event by monitoring 3G signaling (step4230). Transfer a TCP context to the Gi optimizer at the MIOP@Core (step4240). The method is done.
• FIG. 43 is a flow diagram of onepossible method4220 for implementingstep4220 in the flow diagram ofFIG. 42. The steps of this flow diagram are performed by the Iub Optimizer and the Gi Optimizer and other entities in the mobile data network as described herein. Place the UE into a RRC idle state and the broken out PDP context into a preserved state by the mobile data network, for example when the UE goes into an idle state (step4310). Release resources related to the PDP context at the MIOP@NodeB except the NAT IP address (step4312). Maintain the context and resource information at the MIOP@RNC (step4314). Place the NAT IP address at the MIOP@NodeB into a frozen state, where the address is not to be reused for newly broken out PDP contexts until the original PDP context is deactivated (step4316). The UE moves to another cell (mobility event) while in the RRC idle state (step4318). The UE initiates a data transfer procedure again for the preserved PDP context through invocation of 3G signaling by establishing a RRC connection and issuing a network access server (NAS) Service Request (step4320). The method is done.
• FIG. 44 is a flow diagram of afirst method4240A for implementingstep4240 in the flow diagram ofFIG. 42. The example shown inFIG. 44 is for a PDP context in the active state and the UE in the RRC connected mode as the UE moves to an adjacent node connected to the same RNC. The steps of this flow diagram are performed by the Iub Optimizer and the Gi Optimizer and other entities in the mobile data network as described herein. Upon detection of the mobility event, the MIOP@NodeB sends a TCP context transfer message to the source Iub Optimizer (step4410). The Iub Optimizer transfers all TCP contexts for the UE to the Gi Optimizer appropriate for handling contexts with this UE (application contexts may also be sent) (step4412). After the TCP context transfer the Gi Optimizer starts receiving packets from the UE (step4414). The source MIOP@NodeB stops sending maintenance data in uplink for the broken out PDP context (step4416). The source MIOP@NodeB deregisters the UE with the MIOP@RNC (step4418). The MIOP@RNC stops sending maintenance data in the down link for the broken out TCP context (step4420). The source MIOP@NodeB triggers a RLC reset procedure towards both the RNC and the UE to reestablish the ciphering context (step4422). The MIOP@RNC stitches the GTP tunnel so that data being received from the RNC can be forward to the SGSN and vise versa (step4424). The Gi Optimizer continues to serve the broken out TCP context belonging to the UE after the mobility event (step4426). The method is done.
• FIG. 45 is a flow diagram of asecond method4240B for implementingstep4240 in the flow diagram ofFIG. 42. The example shown inFIG. 45 is for a PDP context in the preserved state and the RRC connection to the UE has been released as the UE moves to an adjacent node connected to the same RNC. The steps of this flow diagram are performed by the Iub Optimizer and the Gi Optimizer and other entities in the mobile data network as described herein. The MIOP@NodeB determines that the UE of the mobility event is in a broken out and preserved PDP context (step4510). Upon detection of the mobility event, the MIOP@RNC sends a TCP context plus application context transfer message to the source MIOP@NodeB (step4512). The source MIOP@NodeB sends a TCP context transfer message to the source Iub Optimizer (Application contexts may also be sent) (step4514). The source MIOP@NodeB frees the allocated NAT IP address (step4516). The Iub Optimizer transfers all application and TCP contexts for the UE to the Gi Optimizer appropriate for handling contexts with this UE (step4518). After the TCP context transfer, the Gi Optimizer starts receiving packets from the UE and continues to serve the broken out TCP context belonging to the UE (step4520). The method is done.
• FIG. 46 is a flow diagram of onepossible method4600 for implementingstep4412 inFIG. 44 andstep4518 inFIG. 45 to transfer the TCP context to the MIOP@Core. The steps of this flow diagram are performed by the Iub Optimizer and the Gi Optimizer and other entities in the mobile data network as described herein. First, block all receives to establish a know state at the time of the TCP context transfer (step4610). Then read in all data received in the socket buffer associated with a connection prior to the TCP context transfer (step4620). Invoke a kernel software module to determine the socket details for this connection (detail such as TCP state, IP address, and port number) (step4630). Send the socket details to the Gi Optimizer at the MIOP@Core (step4640). Create a new socket at the Gi Optimizer with the socket details (step4650). Then reinstate all the data buffers to the socket with data from the previous connection (step4660). The method is then done.
• In the above examples, the mobility event resulted in the UE moving to a new target NodeB that was connected to the same RNC as the source NodeB. Thus the UE remains anchored to the same RNC before and after the mobility event. This is referred to herein as intra-RNC. In contrast, inter-RNC occurs where the mobility event results in the UE anchored to a different RNC after the mobility event. For inter-RNC there are two primary situations: same MIOP@RNC and different MIOP@RNC.
• Same MIOP@RNC. If the same breakout group of MIOP components handle the source and target RNC then the handling is essentially has described for the intra-RNC examples above. In case of different Breakout groups in MIOP@RNC handles the source and target RNC the handling for preserved PDP Context involves explicit TCP Context Transfer signaling request from the new Breakout Group to the old Breakout group. On receiving the signaling request, the Old BO Group initiates transfer of TCP Context from old Iub Optimizer to the Gi Optimizer and cleans up the preserved PDP Context from the Iub DO GW and IuPS DO GW. The new Breakout Group shall locate the old Breakout Group based on the Old RAI present in the Routing Area Update Request through pre-configured database with mapping between RAI and Overlay IP address of Breakout Groups/MIOP@RNC.
• Different MIOP@RNC. For UE in connected RRC mode, the source MIOP@RNC shall detect the mobility event and cleanup the context following transfer of TCP Context to the Iub Optimizer. For UE in idle RRC mode, the target MIOP@RNC breakout group, on receiving routing area update request, shall request source MIOP@RNC handling the contexts (based on old RAI) to transfer TCP context and cleanup the preserved resources. In case source MIOP@RNC did not offload the session or does not have the context, the transfer request shall be responded with a corresponding status and cause of the error.
• Themobile data network200 disclosed herein includes MIOP components that provide a variety of different services that are not possible in prior artmobile data network100. In the most preferred implementation, the MIOP components do not affect voice traffic in the mobile data network. In addition to performing optimizations that will enhance performance in the form of improved download speeds, lower latency for access, or improved quality of experience in viewing multimedia on the mobile data network, the MIOP architecture also provides additional capabilities that may produce new revenue-generating activities for the carrier. For example, analytics may be performed on subscriber sessions that allow targeting specific subscribers with additional services from the carrier to generate additional revenue. For example, subscribers congregating for a live music event may be sent promotions on paid for media related to that event. In another example, subscribers getting off a train may be sent a coupon promoting a particular shuttle company as they walk up the platform towards the street curb. Also, premium web content in the form of video or other multimedia may be served from local storage and the subscriber would pay for the additional content and quality of service.
• While the mobile data network inFIG. 2 and discussed herein is in the context of a 3G mobile data network, the disclosure and claims herein expressly extend to other networks as well, including Long Term Evolution (LTE) networks, flat RAN networks, and code division multiple access (CDMA) networks.
• As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
• Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
• A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
• Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
• Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language, Streams Processing language, or similar programming languages. Java is a registered trademark of Oracle America, Inc. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
• Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
• These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
• The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
• The methods disclosed herein may be performed as part of providing a web-based service. Such a service could include, for example, offering the method to online users in exchange for payment.
• As described herein, a TCP context is transferred to a Gi Optimizer to provide cooperative mobility management in a mobile data network with a breakout system. When a MIOP@NodeB detects a mobility event for a broken out UE, the Iub optimizer in the MIOP@NodeB coordinates with the Gi optimizer to transfer the TCP/UDP connection established between the UE and the IuB Optimizer to the Gi Optimizer. After the transfer, the UE is served by the Gi Optimizer. The transfer of the TCP context overcomes disruption of the UE connection to help insure a high quality user experience when accessing internet services from the breakout system.
• One skilled in the art will appreciate that many variations are possible within the scope of the claims. Thus, while the disclosure is particularly shown and described above, it will be understood by those skilled in the art that these and other changes in form and details may be made therein without departing from the spirit and scope of the claims.

Claims (7)

1. A mobile data network comprising:

a plurality of basestations, each basestation communicating with a corresponding antenna that transmits and receives radio signals to and from user equipment, wherein the plurality of basestations are part of a radio access network that communicates with a core network in the mobile data network, each basestation comprising:

a first service mechanism that defines an existing first data path in the radio access network for non-broken out data, defines a second data path for broken out data, identifies first data corresponding to a user equipment (UE) received from a corresponding basestation as data to be broken out, sends the first data on the second data path, and forwards other data that is not broken out on the first data path, wherein the first service mechanism establishes a packet data protocol (PDP) context with the UE for the broken out data, wherein the first service mechanism includes a first optimizer and a transmission control protocol (TCP) context for an application in the UE that is broken out on the second data path;

a second service mechanism in the mobile data network that communicates with the first service mechanism on an overlay network, wherein the second service mechanism includes a second optimizer; and

wherein the first optimizer and the second optimizer coordinate to transfer the TCP context to the second optimizer in response to detecting a mobility event of the UE to allow the second optimizer to serve the UE after the mobility event.

2. The mobile data network ofclaim 1 wherein the first service mechanism places the PDP context that is broken out into a preserved state by:

placing the UE into a radio resource control (RRC) idle state and the PDP context into a preserved state;

releasing resources related to the PDP context at the first service mechanism except a network address translation (NAT) internet protocol (IP) address;

maintaining the context and resource information at the first service mechanism;

placing the NAT IP address at the first mechanism into a frozen state;

the UE moves to an adjacent cell to create a mobility event while in the RRC idle state; and

the UE initiating data transfer procedure again for the preserved PDP context through invocation of 3G signaling by establishing a RRC connection and issuing a network access server (NAS) Service Request.

3. The mobile data network ofclaim 1 wherein the first optimizer and the second optimizer coordinate to transfer the TCP context to the second optimizer by performing the steps of:

upon detection of the mobility event, the first service mechanism sending a TCP application context transfer message to the first optimizer;

the first optimizer transferring the TCP context for the UE to the second optimizer;

the second optimizer starting to receive packets from the UE;

the first service mechanism stopping the sending of maintenance data in uplink for the broken out PDP context;

the first service mechanism deregistering the UE with a third service mechanism connected to a radio network controller (RNC);

the third service mechanism stopping the sending of maintenance data in a down link for the broken out TCP context;

the first service mechanism triggering a radio link control (RLC) reset procedure towards both the RNC and the UE to reestablish a ciphering context;

the third service mechanism stitching a data tunnel so that data being received from the RNC can be forward to GPRS support node (SGSN) and data received from the SGSN can be forwarded to the RNC; and

the second optimizer continuing to serve the broken out TCP context belonging to the UE.

4. The mobile data network ofclaim 3 wherein the step of the first optimizer transferring the TCP context for the UE to the second optimizer comprises the steps of:

blocking all receives to establish a know state at the time of the TCP context transfer;

reading in all data received in a socket buffer associated with a connection for the TCP context in the first service mechanism;

invoking a kernel software module to determine socket details for a connection prior to the TCP context transfer;

sending the socket details to the second optimizer;

creating a new socket at the second optimizer with the socket details; and

reinstating all data buffers to the new socket with data from the connection prior to the TCP context transfer.

5. The mobile data network ofclaim 1 wherein the second service mechanism is located in a core network of the mobile data network.

6. The mobile data network ofclaim 1 wherein transferring the TCP context includes application context data for a state of an application.

7-14. (canceled)

Images