1. Technical Field
This disclosure generally relates to mobile data systems, and more specifically relates to breakout out of data at the edge of a mobile data network in a way that is transparent to existing equipment in the mobile data network so one or more mobile network services may be performed at the edge of the mobile data network in response to the broken-out data.
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. For example, the next generation wireless network in the United States is the 4G network. Many mobile data network providers are still struggling to get their entire system upgraded to provide 3G data services. Immediately upgrading to 4G equipment is not an economically viable option for most mobile data network providers. In many locations, portions of the mobile data network are connected together by point to point microwave links. These microwave links have limited bandwidth. To significantly boost the throughput of this links requires the microwave links to be replaced with fiber optic cable but this option is very costly.
Mobile network services are performed in a mobile data network in a way that is transparent to most of the existing equipment in the mobile data network. The mobile data network includes a radio access network and a core network. A first service mechanism in the radio access network breaks out data coming from a basestation, and performs one or more mobile network services at the edge of the mobile data network based on the broken out data. These services may include caching of data, data or video compression techniques, push-based services, charging, application serving, analytics, security, data filtering, and new revenue-producing services, as well as others. This architecture allows performing new mobile network services at the edge of a mobile data network within the infrastructure of an existing mobile data network.
The foregoing and other features and advantages will be apparent from the following more particular description, as illustrated in the accompanying drawings.
The disclosure will be described in conjunction with the appended drawings, where like designations denote like elements, and:
The claims and disclosure herein provide mechanisms and methods for performing mobile network services in a mobile data network within the existing infrastructure of the mobile data network.
Referring to
In mobile data network 100, user equipment 110 communicates via radio waves to a tower 120. User equipment 110 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. The tower 120 communicates via network connection to a basestation 122. Each basestation 122 includes a NodeB 130, which communicates with the tower 120 and the radio network controller 140. Note there is a fan-out that is not represented in
The radio network controller 140 communicates with the serving node 150. In a typical 3G network, the serving node 150 is an SGSN, which is short for Service GPRS Support Node, where GPRS stands for general packet radio service. The serving node 150 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 the gateway node 160 for a given subscriber session. The serving node 150 is responsible for the delivery of data packets from and to the basestations within its geographical service area. The tasks of the serving node 150 include packet routing and transfer, mobility management (attach/detach and location management), logical link management, and authentication and charging functions. The serving node 150 stores location information and user profiles of all subscribers registered with the serving node 150. Functions the serving node 150 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, the gateway node 160 is a GGSN, which is short for gateway GPRS support node. The gateway node 160 is responsible for the interworking between the core network and external networks. From the viewpoint of the external networks 180, gateway node 160 is a router to a sub-network, because the gateway node 160 “hides” the core network infrastructure from the external network. When the gateway node 160 receives data from an external network (such as internet 180) addressed to a specific subscriber, it forwards the data to the serving node 150 serving the subscriber. For inactive subscribers paging is initiated. The gateway node 160 also handles routing packets originated from the user equipment 110 to the appropriate external network. As anchor point the gateway node 160 supports the mobility of the user equipment 110. In essence, the gateway node 160 maintains routing necessary to tunnel the network packets to the serving node 150 that services a particular user equipment 110.
The gateway node 160 converts the packets coming from the serving node 150 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 the external network 180 are converted to the address of the subscriber's user equipment 110. The readdressed packets are sent to the responsible serving node 150. For this purpose, the gateway node 160 stores the current serving node address of the subscriber and his or her profile. The gateway node 160 is responsible for IP address assignment and is the default router for the subscriber's user equipment 110. The gateway node 160 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 the gateway node 160, and routes the traffic either to the operator service network 170 or via an internet service provider (ISP) towards the internet 180. The operator service network 170 typically includes business logic that determines how the subscriber can use the mobile data network 100. 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 the internet 180. As shown in
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 to
The mobile network services provided by MIOP@NodeB 210, MIOP@RNC 220, and MIOP@Core 230 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 of MIOP@NodeB 210, MIOP@RNC 220, and MIOP@Core 230 are included in the term MIOP services as used herein. In addition to the services being offer in the MIOP components MIOP@NodeB 210, MIOP@RNC 220, and MIOP@Core 230, the various MIOP services could also be provided in a cloud based manner.
MIOP@NodeB 210 includes a first service mechanism and is referred to as the “edge” based portion of the MIOP solution. MIOP@NodeB 210 resides in the radio access network and has the ability to intercept all traffic to and from the NodeB 130. MIOP@NodeB 210 preferably resides in the base station 222 shown by the dotted box in
Once MIOP@NodeB 210 breaks out user data it can perform any suitable service based on the traffic type of the broken out data. Because the services performed by MIOP@NodeB 210 are performed in the radio access network (e.g., at the basestation 222), the MIOP@NodeB 210 can service the user equipment 110 much more quickly than can the radio network controller 140. In addition, by having a MIOP@NodeB 210 that is dedicated to a particular NodeB 130, 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 by MIOP@NodeB 210 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@RNC 220 includes a second service mechanism in mobile data network 200. MIOP@RNC 220 monitors all communication between the radio network controller 140 and serving node 150. The monitored communications are all communications to and from the radio network controller and the rest of the core network. MIOP@RNC 220 may provide one or more services for the mobile data network. MIOP@RNC 220 preferably makes the decision of whether or not to allow breakout of data. If MIOP@RNC 220 decides to breakout data for a given subscriber session, it may send a message to MIOP@NodeB 210 authorizing breakout by MIOP@NodeB 210, or may decide to breakout the data at MIOP@RNC 220, 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 by MIOP@RNC 220, the decision of whether or not to breakout data resides in the MIOP@RNC 220.
MIOP@Core 230 includes a third service mechanism in the mobile data network 200. MIOP@Core 230 may include all the same services as MIOP@RNC 220, or any suitable subset of those services. If the decision is made not to provide services at MIOP@NodeB 210 or MIOP@RNC 220, these same services plus more sophisticated services can be performed at MIOP@Core 230. Thus, mobile data network 200 provides flexibility by allowing a decision to be made of where to perform which services. Because MIOP@NodeB 210, MIOP@RNC 220 and MIOP@Core 230 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@NMS 240 is a network management system that monitors and controls the functions of MIOP@NodeB 210, MIOP@RNC 220, and MIOP@Core 230. MIOP@NMS 240 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 the mobile data network 200. MIOP@NMS 240 provides a user interface that allows a system administrator to operate and to configure how the MIOP components 210, 220 and 230 function.
The overlay network 250 allows MIOP@NodeB 210, MIOP@RNC 220, MIOP@Core 230, and MIOP@NMS 240 to communicate with each other. The overlay network 250 is preferably a virtual private network primarily on an existing physical network in the mobile data network. Thus, while overlay network 250 is shown in
As shown in
We can see from the configuration of the physical network and overlay network in
As can be seen in
Referring to
The breakout mechanism 410 preferably includes breakout preconditions 420 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 at MIOP@NodeB 210. Thus, breakout preconditions 420 could specify that subscribers on high-speed channels may be broken out, while subscribers on low-speed channels are not broken out at MIOP@NodeB 210. When the breakout preconditions 420 are satisfied, the MIOP@NodeB 210 registers the subscriber session with MIOP@RNC 220. This is shown in method 800 in
Referring back to
MIOP@NodeB 210 also includes an overlay network mechanism 440. The overlay network mechanism 440 provides a connection to the overlay network 250 in
Referring to
In one specific example, the breakout preconditions specify only high-speed channels are broken out at MIOP@NodeB 210, and when the breakout preconditions are satisfied, the subscriber session is registered for breakout, as shown in
Referring back to
While the breakout mechanism 510 and RNC service mechanism 540 are shown as separate entities in
The business intelligence 560 may be instrumented by the RNC service mechanism 540 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 to
Referring to
Referring again to
Referring to
MIOP services may require communicating between MIOP components on the overlay network. Referring to
Referring to
When a breakout decision is made and MIOP@RNC 220 sends a message to MIOP@NodeB 210 authorizing breakout (see step 1040 in
User data that is not broken out and signaling traffic is routed directly back by the switching application 1740 to RNC. In this manner, non-broken out data and signaling traffic passes through the IuB DOGW 1710 to RNC 140, while broken out data is routed by the IuB DOGW 1710 to a different destination. Note that edge cache mechanism 1730 may send messages to MIOP@RNC 220 as shown in
MIOP@RNC 220 includes an interface referred to herein as IuPS data offload gateway (IuPS DOGW) 1770. IuPS DO GW 1770 forwards all signaling and non-broken out data traffic from RNC 140 to SGSN 150 via the GTP tunnel. IuPS DOGW 1770 includes the breakout mechanism 510, breakout criteria 520 and subscriber registration mechanism 530 shown in
The IuPS DOGW 1770 includes an RNC channel handler 1780. The RNC channel handlers 1760 in MIOP@NodeB 210 and 1780 in MIOP@RNC 220 monitor data traffic to and from RNC 140 related to a broken out subscriber session and provide a keep-alive channel maintenance mechanism.
Specific methods are shown in
Referring to
Referring to
A simple example is now provided for the specific implementation in
Method 2300 in
The methods shown in
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 the mobile data network 200 shown in
In the most preferred implementation, the various functions of MIOP@NodeB 210, MIOP@RNC 220, MIOP@Core 230, and MIOP@NMS 240 are performed in a manner that is nearly transparent to existing equipment in the mobile data network. Thus, the components in prior art mobile data network 100 that are also shown in the mobile data network 200 in
Referring to
One suitable x86 processor that could serve as system controller 2412 is the Intel Xeon E3-1220 processor. One suitable service processor 2420 is an IBM Renassas SH7757, but other known service processors could be used. One suitable processor for the security subsystem 2430 is an ATMEL processor UC3L064, and one suitable non-volatile memory for the security subsystem 2430 is a DS3645 battery-backed RAM from Maxim. One suitable processor for the telco breakout subsystem 2450 is the Cavium Octeon II CN63XX.
Various functions of the MIOP@NodeB 2410 shown in
Referring to
The fail-to-wire control mechanism 2630 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 by MIOP@NodeB 2410, 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 by MIOP@NodeB 2410. The key mechanism 2640 provides an interface for accessing the security subsystem 2430. The system controller monitor/reset mechanism 2650 monitors the state of the system controller 2412, and resets the system controller 2412 when needed. The display/indicator mechanism 2660 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 to
Referring to
The edge application mechanism 2530 may provide many different mobile network services. Examples of some of these services are shown in
The third party edge application serving mechanism 2930 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 edge application serving mechanism 2930 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 mechanism 2930) 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.
The analytics mechanism 2940 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, the analytics mechanism 2940 could analyze IP traffic on MIOP@NodeB, and use the results of the analysis to more intelligently cache IP data by edge caching mechanism 2910. In addition, the analytics mechanism 2940 makes other revenue-producing services possible. For example, the analytics mechanism 2940 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, the analytics mechanism 2940 may perform any suitable analysis on the broken out data for any suitable purpose.
The filtering mechanism 2950 allows filtering content delivered to the user equipment by MIOP@NodeB. For example, the filtering mechanism 2950 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 the filtering mechanism 2950 could enforce. The filtering mechanism 2950 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 the filtering mechanism 2950. The filtering mechanism 2950 preferably performs any suitable data filtering function or functions, whether currently known or developed in the future.
The revenue-producing service mechanism 2960 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 the analytics mechanism 2940 can perform analysis of data broken out by MIOP@NodeB, and this analysis could be provided by the revenue-producing service mechanism 2960 to interested parties for a price, thereby providing a new way to generate revenue in the mobile data network. Revenue-producing service mechanism 2960 broadly encompasses any way to generate revenue in the mobile data network based on the specific services provided by any of the MIOP components.
The charging mechanism 2970 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, the charging mechanism 2970 provides a way for MIOP@NodeB to charge the subscriber for services provided by MIOP@NodeB of which the core network is not aware. The charging mechanism 2970 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 in
The mobile data network 200 disclosed herein includes MIOP components that provide a variety of different services that are not possible in prior art mobile data network 100. 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 in
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. 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.
The disclosure and claims are directed to a mobile data network that includes service mechanisms and methods for performing services in the mobile data network. A first service mechanism in the radio access network breaks out data coming from a basestation, and performs one or more mobile network services at the edge of the mobile data network based on the broken out data. These services may include caching of data, data or video compression techniques, push-based services, charging, application serving, analytics, security, data filtering, and new revenue-producing services, as well as others. This architecture allows performing new mobile network services at the edge of a mobile data network within the infrastructure of an existing mobile data network.
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.
Number | Name | Date | Kind |
---|---|---|---|
5287506 | Whiteside | Feb 1994 | A |
5390324 | Burckhartt et al. | Feb 1995 | A |
5490134 | Fernandes et al. | Feb 1996 | A |
5708776 | Kikinis | Jan 1998 | A |
6496811 | Bodnar | Dec 2002 | B1 |
6519461 | Andersson et al. | Feb 2003 | B1 |
6882624 | Ma | Apr 2005 | B1 |
6977899 | Matragi et al. | Dec 2005 | B1 |
7058691 | Yu et al. | Jun 2006 | B1 |
7284035 | Yu et al. | Oct 2007 | B2 |
7380119 | Bade et al. | May 2008 | B2 |
7676223 | Das et al. | Mar 2010 | B2 |
7711122 | Allen et al. | May 2010 | B2 |
7724707 | Foster et al. | May 2010 | B2 |
7747239 | Sennett et al. | Jun 2010 | B1 |
7849267 | Lam et al. | Dec 2010 | B2 |
7852838 | Miller et al. | Dec 2010 | B2 |
7873350 | McDaniel et al. | Jan 2011 | B1 |
7916649 | Buvaneswari et al. | Mar 2011 | B2 |
7941136 | Reed et al. | May 2011 | B2 |
7979733 | Erdtmann et al. | Jul 2011 | B2 |
7991699 | Walmsley | Aug 2011 | B2 |
8023491 | Gruber | Sep 2011 | B2 |
8032764 | Shankar et al. | Oct 2011 | B2 |
8046423 | Haywood et al. | Oct 2011 | B2 |
8050657 | Hollander | Nov 2011 | B2 |
8161285 | Ellison et al. | Apr 2012 | B2 |
8191116 | Gazzard | May 2012 | B1 |
8254294 | Vesterinen | Aug 2012 | B2 |
8286157 | Drissi et al. | Oct 2012 | B2 |
8363665 | Lim et al. | Jan 2013 | B2 |
8392496 | Linden et al. | Mar 2013 | B2 |
8432871 | Sarnaik et al. | Apr 2013 | B1 |
8452957 | Pourzandi et al. | May 2013 | B2 |
8457636 | Liu et al. | Jun 2013 | B2 |
8462696 | Vesterinen et al. | Jun 2013 | B2 |
8462770 | Kant et al. | Jun 2013 | B2 |
8477785 | Kant et al. | Jul 2013 | B2 |
8479271 | Berg et al. | Jul 2013 | B1 |
8503393 | Vesterinen | Aug 2013 | B2 |
8520615 | Mehta et al. | Aug 2013 | B2 |
8538433 | Kekki et al. | Sep 2013 | B2 |
8543660 | Roberts et al. | Sep 2013 | B2 |
20020162059 | McNeely et al. | Oct 2002 | A1 |
20030095540 | Mulligan et al. | May 2003 | A1 |
20030200453 | Foster et al. | Oct 2003 | A1 |
20040001439 | Jones | Jan 2004 | A1 |
20040146027 | Shinozaki et al. | Jul 2004 | A1 |
20050041584 | Lau et al. | Feb 2005 | A1 |
20050216519 | Mayo et al. | Sep 2005 | A1 |
20050246521 | Bade et al. | Nov 2005 | A1 |
20050266799 | Hara et al. | Dec 2005 | A1 |
20060155988 | Hunter et al. | Jul 2006 | A1 |
20070026906 | Macfarlane et al. | Feb 2007 | A1 |
20070060167 | Damnjanovic et al. | Mar 2007 | A1 |
20070079120 | Bade et al. | Apr 2007 | A1 |
20070086485 | Vega-Garcia et al. | Apr 2007 | A1 |
20070127443 | Spencer et al. | Jun 2007 | A1 |
20070280149 | Takahashi et al. | Dec 2007 | A1 |
20080005121 | Lam et al. | Jan 2008 | A1 |
20080065809 | Eichenberger | Mar 2008 | A1 |
20080092235 | Comlekoglu | Apr 2008 | A1 |
20080137541 | Agarwal et al. | Jun 2008 | A1 |
20080159148 | Morinaga et al. | Jul 2008 | A1 |
20080178176 | Berger et al. | Jul 2008 | A1 |
20080244569 | Challener et al. | Oct 2008 | A1 |
20080267128 | Bennett et al. | Oct 2008 | A1 |
20080270603 | Berger et al. | Oct 2008 | A1 |
20080293413 | Sharif-Ahmadi et al. | Nov 2008 | A1 |
20090046661 | Casati et al. | Feb 2009 | A1 |
20090122712 | Sharif-Ahmadi et al. | May 2009 | A1 |
20090204803 | Cox et al. | Aug 2009 | A1 |
20090205028 | Smeets et al. | Aug 2009 | A1 |
20090219864 | Parolari | Sep 2009 | A1 |
20090232015 | Domschitz et al. | Sep 2009 | A1 |
20090249053 | Zimmer et al. | Oct 2009 | A1 |
20090307487 | Movva et al. | Dec 2009 | A1 |
20100057883 | Cao et al. | Mar 2010 | A1 |
20100067485 | Rezaiifar et al. | Mar 2010 | A1 |
20100082984 | Ellison et al. | Apr 2010 | A1 |
20100103923 | Nosley et al. | Apr 2010 | A1 |
20100130170 | Liu et al. | May 2010 | A1 |
20100211686 | Poikselka | Aug 2010 | A1 |
20100246585 | Mantri et al. | Sep 2010 | A1 |
20100281251 | Arauz Rosado | Nov 2010 | A1 |
20100325194 | Williamson et al. | Dec 2010 | A1 |
20110070906 | Chami et al. | Mar 2011 | A1 |
20110075675 | Koodli et al. | Mar 2011 | A1 |
20110076985 | Chami et al. | Mar 2011 | A1 |
20110093913 | Wohlert et al. | Apr 2011 | A1 |
20110093952 | Kumar et al. | Apr 2011 | A1 |
20110103310 | Stojanovski et al. | May 2011 | A1 |
20110103557 | Shah et al. | May 2011 | A1 |
20110119740 | Grayson et al. | May 2011 | A1 |
20110134982 | Reinhardt | Jun 2011 | A1 |
20110159895 | Arzelier et al. | Jun 2011 | A1 |
20110176531 | Rune et al. | Jul 2011 | A1 |
20110191330 | Barve et al. | Aug 2011 | A1 |
20110202646 | Bhatia et al. | Aug 2011 | A1 |
20110213953 | Challener et al. | Sep 2011 | A1 |
20110235595 | Mehta et al. | Sep 2011 | A1 |
20120023568 | Cha et al. | Jan 2012 | A1 |
20120046058 | Vesterinen et al. | Feb 2012 | A1 |
20120084261 | Parab | Apr 2012 | A1 |
20120131096 | Bugenhagen | May 2012 | A1 |
20120184258 | Kovvali et al. | Jul 2012 | A1 |
20120184284 | Moisio et al. | Jul 2012 | A1 |
20120188895 | Punz et al. | Jul 2012 | A1 |
20120224578 | Mih Ly et al. | Sep 2012 | A1 |
20120229254 | Nowottnick | Sep 2012 | A1 |
20120243432 | Liebsch et al. | Sep 2012 | A1 |
20120244861 | Agarwal et al. | Sep 2012 | A1 |
20120254543 | Sintorn et al. | Oct 2012 | A1 |
20120269162 | Vesterinen et al. | Oct 2012 | A1 |
20120304233 | Roberts et al. | Nov 2012 | A1 |
20120324236 | Srivastava et al. | Dec 2012 | A1 |
20130029708 | Fox et al. | Jan 2013 | A1 |
20130031204 | Graham et al. | Jan 2013 | A1 |
20130097674 | Jindal et al. | Apr 2013 | A1 |
20130121159 | Anthony et al. | May 2013 | A1 |
20130121324 | Kalmbach et al. | May 2013 | A1 |
20130122856 | Kalmbach et al. | May 2013 | A1 |
20130155873 | Berg et al. | Jun 2013 | A1 |
20130157619 | Di Luoffo et al. | Jun 2013 | A1 |
20130157702 | Di Luoffo et al. | Jun 2013 | A1 |
20130160085 | Berg et al. | Jun 2013 | A1 |
20130163413 | Berg et al. | Jun 2013 | A1 |
20130166625 | Swaminathan et al. | Jun 2013 | A1 |
20130208580 | Berg et al. | Aug 2013 | A1 |
20130208674 | Berg et al. | Aug 2013 | A1 |
Number | Date | Country |
---|---|---|
03041279 | May 2003 | WO |
WO03041279 | May 2003 | WO |
2011018235 | Feb 2011 | WO |
2011021875 | Feb 2011 | WO |
WO2011182351 | Feb 2011 | WO |
2011091861 | Aug 2011 | WO |
2011101131 | Aug 2011 | WO |
Entry |
---|
Kundalkar et al., “LIPA: Local IP Access via Home Node B”, Nov. 13, 2009. |
Opengear Quad-Band GSM/UMTS/HSPA Cellular Appliance Gains PTCRB Certification, Oct. 20, 2010. |
PSE 3G VAS Genie, www.mirial.com, Sep. 21, 2011. |
UMTS/HSDPA connection with UTM-1 Edge Appliance an T-D1 SIM, http://cpshared.com/forums/showthread.php?t=153, Sep. 21, 2011. |
Pending U.S. Patent Application entitled “Mobile Network Services in a Mobile Data Network”, U.S. Appl. No. 13/233,812, filed Sep. 15, 2011 by Bruce O. Anthony, Jr. et al. |
Darwin Information Typing Architecture, http://en.wikipedia.org/wiki/Darwin—Information—Typing—Architecture, Oct. 25, 2011. |
Failover, http://en.wikipedia.org/w/index.php?title=Failover&oldid=457289935, Oct. 25, 2011. |
Integrated Management Module User's Guide, Third Edition, Feb. 2010. |
Inheritance (object-oriented programming), http://en.wikipedia.org/wiki/Inheritance—(object-oriented—programming), Oct. 25, 2011. |
Addressing the Physical Security of Encryption Keys, Maxim Application Note 4185, Feb. 21, 2008. |
Maxim DS5250 High-Speed Secure Microcontroller, Datasheet, Jul. 18, 2003. |
Security Policy: Key Management Facility Crypto Card (KMF CC), Motorola, Feb. 7, 2011. |
Valicore vCoreServer:Authenitcation & Key Management Appliance, Valicore Technologies, Sep. 28, 2011. |
Curiac, Daniel-Ioan, et al., Combined Malicious Node Discovery and Self-Destruction Technique for Wireless Sensor Networks, 2009, IEEE, Third International Conference on Sensor Technologies and Applications, 436-441. |
Oishi, Kazuomi et al., Self Destructive Tamper Response for Software Protection, Mar. 22-24, 2011, ASIACCS '11, ACM, 490-496. |
Cisco IronPort Products and Technology, http://cisco.com/web/about/ac49/ac0/ac1/ac259/ironport.html, Jan. 18, 2012. |
International Search Report and Written Opinion of the ISA dated Feb. 22, 2013—International Application No. PCT/EP2012/071486. |
Kundalkar et al., “LIPA: Local IP Access via Home Node B,” downloaded Oct. 18, 2011. |
“Opengear Quad-Band GSM/UMTS/HSPA Cellular Appliance Gains PTCRB Certification,” Press Release Oct. 20, 2011. |
“PSE 3G VAS Genie,” http://www.mirial.com/products/PSE—VAS—Genie.html, printed Oct. 18, 2011. |
“UMTS / HSDPA connection with UTM-1 Edge Appliance an T-D1 SIM Card,” CPShared, printed Sep. 21, 2011. |
William F. Berg et al., U.S. Appl. No. 13/355,250, entitled “Distributed Control of a Fail-To-Wire Switch for a Network Communication Link,” filed Jan. 20, 2012. |
William F. Berg et al., U.S. Appl. No. 13/297,807, entitled “Data Breakout Appliance at the Edge of a Mobile Data Network,” filed Nov. 16, 2011. |
International Search Report and Written Opinion of the ISA dated Dec. 17, 2012—International Application No. PCT/US2012/058221. |
International Search Report and Written Opinion of the ISA dated Mar. 19, 2013—International Application No. PCT/EP2012/071490. |
Number | Date | Country | |
---|---|---|---|
20130121159 A1 | May 2013 | US |