Fault-tolerant signaling in a Long Term Evolution (LTE) network architecture is disclosed. A method can comprise initiating a primary signaling path to a signaling server device; in response to the initiating, establishing an alternate signaling path to a web application server device, wherein a call session is established over the primary signaling path; monitoring the primary signaling path for a session failure; and in response to the session failure, switching the call session from using the primary signaling path to using the alternate signaling path.

TECHNICAL FIELD

The disclosed subject matter relates to providing fault-tolerant signaling in a LTE network architecture.

BACKGROUND

Voice over Long Term Evolution (VoLTE) is a standard for high-speed wireless communication for mobile phones and data terminals. It is based on the Internet Protocol Multimedia Subsystem (IMS) network with specific profiles for control and media planes of voice service on Long Term Evolution (LTE). This approach results in the voice service being delivered as data flows within a LTE data bearer. This means there generally is no dependency on the legacy circuit switched voice network.

Web Real-Time Communication (WebRTC) provides web browser and mobile applications with real-time communication (RTC) via application programming interfaces (APIs). It allows audio and video communication to work inside web pages by allowing direct peer to peer communication.

DETAILED DESCRIPTION

The subject application leverages WebRTC technology to provide an additional and/or alternative signaling path beyond the infrastructure provided by the current LTE based IMS network architecture. Disclosed embodiments can be used, for example, by key government officials during national emergencies to provide a robust signaling architecture for LTE user equipment devices by engineering a recovery path signaling path for VoLTE and conversational video end user devices. The disclosure provides that a device, in response to detecting a call setup failure (e.g., a failure in the underlying IMS architecture), can initiate and maintain communications between calling and receiving parties (e.g., calling and receiving end user devices) by using alternative/backup non-IMS signaling infrastructures and alternative/backup data paths. The goal that the subject disclosure seeks to achieve is to provide end user devices with ultra-reliable voice and video sessions.

While the subject application was initially designed to provide a backup/alternative signaling to IMS during severe network stress conditions, the disclosure can find general utility and applicability by typically all LTE enabled devices at any time.

As described, the subject application discloses a first device (e.g., a first user equipment (UE) device) that initiates a communication session (e.g., a media flow representing at least voice data, audio data, video data, and/or general data (overhead data, text data, . . . ) with a second device (e.g., a second user equipment (UE) device). For ease of exposition the first device can be referred to as the calling device (or calling party) and the second device can be referred to as the receiving device (or receiving party). In order to initiate and/or establish the communication session (e.g., a voice over long term evolution (VoLTE) communication session) between the calling device and the receiving device, the calling device can establish/initiate a communication session with a signaling server device (e.g., a base station device such as an evolved NodeB (eNodeB) device) using one or more establishment protocols. As will be appreciated by those with ordinary skill, without limitation or loss of generality, the signaling server device can be a member of a grouping of similarly configured signaling server devices; the grouping of signaling server devices and/or other groupings of affiliated devices can comprise a network topology.

The signaling server device, in response to recognizing that the calling device seeks to initiate and establish communication with the receiving device can facilitate communication with the receiving device using an appropriate establishment protocol(s). Once a communication session has been established, the calling device and the receiving device can thereafter communicate via a “signaling path” established through the functionalities and facilities provided by the signaling server device. The signaling part can also be referred to as an IMS signaling path.

The foregoing signaling path (e.g., primary signaling path), in times of network stress and the like, can be subject to failure. For example, problems with initiating and/or establishing the signaling path between the first and second devices can arise when a calling party initially attempts to establish a communication session with the signaling server device, for example where contact with the signaling server device from the first device becomes inoperable because of a network failure. Further problems can arise when the signaling server device attempts to establish a communication session with the receiving device, once again because of a failure due to a wider network failure. Additional problems can also manifest themselves once the signaling path has been established between the calling party and receiving party (e.g. in mid communication session between the calling party and the receiving party).

In order to alleviate, mitigate, and/or obviate the aforementioned possible signaling path failures, the subject application discloses that when the first device attempts to initiate a signaling path with the second device, simultaneously and/or in near contemporaneity with and in response to the first device initiating the communication session with the second device (e.g., via the facilities and functionalities of the signaling server device), a web application server device, using functionalities and facilities associated with WebRTC, can also be contacted by the first device. The web application server device through use of the functionalities and functionalities provided by WebRTC in conjunction with a controlling wrapper application can establish a secondary signaling path between the first device and the second device. The secondary signaling path can become fully operable in response to a determination that there is a failure with regard to the primary signaling path. The secondary signaling path can become fully operational without users of either the first device or the second device becoming aware of the switch over between the primary signaling path and the secondary signaling path; or if indication of the switch over between the primary signaling path and the secondary signaling path deemed necessary, such indication can, for example, be provided by an imperceptible “click” sound. The secondary signaling path can also be referred to as a non-IMS signaling path or as an alternative signaling path.

The disclosed systems and methods, in accordance with various embodiments, provide a system, apparatus, or device comprising: a processor, and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations. The operations can comprise detecting initiation of a primary signaling path to a signaling server device; initiating an alternate signaling path to a web application server device based on the detecting, wherein a call session is established over the primary signaling path; monitoring the primary signaling path for a session failure; and as a function of the session failure, switching the call session from using the primary signaling path to using the alternate signaling path.

Additional operations can comprise collecting calling information data representative of the primary signaling path, establishing the alternate signaling path using the calling information data, and as a function of the monitoring, initiating a failure timer. Further operations can include based on the initiating the alternate signaling path, further initiating a call establishment service request to the web application server device, and in response to the call session being established via the primary signaling path, facilitating canceling of the call establishment service request.

In accordance with the foregoing, the system, apparatus, or device can be a first device, and the signaling server device can be a second device of a group of network devices that operate using internet protocol multimedia core network subsystem signaling. Additionally, and/or alternatively, the web application server device can be a second device of a group of network devices that operate using alternate signaling other than internet protocol multimedia core network subsystem signaling.

In accordance with additional and/or alternative embodiments, the disclosure further describes a system, apparatus, or device comprising: a processor, and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations. The operations can comprise detecting initiation of a primary signaling path to a signaling server device, wherein a call session is established via the primary signaling path; based on the detecting, initiating an alternate signaling path, as an alternative to the primary signaling path, to a web application server device; monitoring the primary signaling path for a session failure of the call session; and as a function of the session failure, switching the call session from using the primary signaling path to using the alternate signaling path.

Additional operations can comprise collecting, from a user device initiating the call session, calling information data representative of the primary signaling path; initiating the alternate signaling path using the calling information data; and as a function of the monitoring, initiating a failure timer that is used to determine, as a function of an elapse of time as measured by the failure timer, that the session failure has occurred. Further operations can comprise based on the alternate signaling path having been initiated, further initiating a call establishment service request to the web application server device; and in response to the call session being determined to have been established via the primary signaling path, facilitating canceling of the call establishment service request.

In accordance with the foregoing, the system, apparatus, or device can a first device, and the signaling server device can be a second device of a group of network devices that operate using internet protocol multimedia core network subsystem signaling; and the web application server device can be a second device of a group of network devices that operate using alternate signaling other than internet protocol multimedia core network subsystem signaling.

In accordance with further embodiments, the subject disclosure describes a method, comprising a series of acts that can include: initiating, by a device comprising a processor, a primary signaling path to a signaling server device; in response to the initiating, establishing, by the device, an alternate signaling path to a web application server device, wherein a call session is established over the primary signaling path; monitoring, by the device, the primary signaling path for a session failure; and in response to the session failure, switching, by the device, the call session from using the primary signaling path to using the alternate signaling path.

Further acts can comprise: in response to initiating the primary signaling path, collecting, by the device, calling information data representative of the primary signaling path; establishing, by the device, the alternate signaling path using the calling information data; and initiating, by the device, a countdown timer in response to establishing the alternate signaling path; Additional acts can include: in response to initiating the alternate signaling path, further initiating, by the device, a call establishment service request to the web application server device; and in response to detecting a success in establishing the call session, facilitating, by the device, canceling the call establishment service request.

In accordance with the foregoing, the signaling server device can be a first device of a network of devices that provide a voice over long term evolution core network service, and the web application server device can be a second device of the network of devices that provide a voice over internet protocol network service.

In accordance with additional embodiments, the subject disclosure describes a method, comprising a series of acts that can include: initiating, by a device comprising a processor, a primary signaling path to a signaling server device; in response to the initiating, establishing, by the device, an alternate signaling path to a web application server device, wherein a call session is established using the primary signaling path, and wherein the alternate signaling path is an alternative path to the primary signaling path; monitoring, by the device, the primary signaling path for a failure of the call session; and in response to the failure of the call session, switching, by the device, the call session from using the primary signaling path to using the alternate signaling path.

Further acts performed by the method can comprise: in response to initiating the primary signaling path, collecting, by the device, calling information data representative of the primary signaling path, wherein the calling information data is received from a user device; establishing the alternate signaling path using the calling information data; and initiating, by the device, a countdown timer in response to the establishing of the alternate signaling path. Additional acts can comprise: in response to the establishing of the alternate signaling path, initiating, by the device, a call establishment service request to the web application server device; and in response to detecting a success in establishing the call session, facilitating, by the device, canceling the call establishment service request.

In accordance with the foregoing, the signaling server device can be a first device of a network of devices that provide a voice over long term evolution core network service; and the web application server device can be a second device of the network of devices that provide a voice over internet protocol network service.

In accordance with still further embodiments, the subject disclosure describes a machine readable storage medium, a computer readable storage device, or non-transitory machine readable media comprising instructions that, in response to execution, cause a computing system comprising at least one processor to perform operations. The operations can include: establishing a primary signaling path to a signaling server device; in response to the establishing, initiating creation of an alternate signaling path to a web application server device, wherein a call session is established over the primary signaling path; monitoring the primary signaling path for a session failure; and in response to the session failure, switching the call session from using the primary signaling path to using the alternate signaling path. Additional operations can include initiating, to the web application server device, a call establishment need service request, and in response to detecting success in establishing the call session, facilitating cancelation of the call establishment need service request.

In accordance with the foregoing, the signaling server device enables a voice over long term evolution core network service, and the web application server device enables a voice over internet protocol network service.

In accordance with yet further embodiments, the subject disclosure describes a machine readable storage medium, a computer readable storage device, or non-tangible machine readable media comprising instructions that, in response to execution, cause a computing device comprising at least one processor to perform operations. The operations can comprise: establishing a primary signaling path to a signaling server device; in response to the establishing, initiating creation of an alternate signaling path to a web application server device, wherein a call session is established via the primary signaling path; monitoring the primary signaling path for failure of the call session; and in response to the failure, switching the call session from using the primary signaling path to using the alternate signaling path. Additional operations can comprise initiating, to the web application server device, a call establishment need service request, and in response to detecting success in establishing the call session, facilitating cancelation of the call establishment need service request.

Now with reference to the Figures,FIG. 1illustrates a system100that in accordance with various embodiments provides for fault-tolerant signaling in a LTE network architecture. System100can include a surveillance engine102and fault engine104that can each be coupled to a processor106, memory108, and storage110. Each of surveillance engine102and fault engine104can be in communication with processor106for facilitating operation of computer or machine executable instructions and/or components by each of surveillance engine102and fault engine104, memory108, for storing data and/or the computer or machine executable instructions and/or components, and storage110for providing longer term storage of data and/or machine and/or computer readable instructions. Additionally, system100can also receive input112for use, manipulation, and/or transformation by each of surveillance engine102and fault engine104to produce one or more useful, concrete, and tangible result, and/or transform one or more articles to different states or things. Further, system100can also generate and output the useful, concrete, and tangible results and/or the transformed one or more articles produced by each of surveillance engine102and fault engine104and output as output114.

System100, for purposes of elucidation, can be any type of mechanism, machine, device, facility, apparatus, and/or instrument that includes a processor and/or is capable of effective and/or operative communication with a wired and/or wireless network topology. Mechanisms, machines, apparatuses, devices, facilities, and/or instruments that can comprise system100can include tablet computing devices, handheld devices, server class computing machines and/or databases, laptop computers, notebook computers, desktop computers, cell phones, smart phones, consumer appliances and/or instrumentation, industrial devices and/or components, hand-held devices, personal digital assistants, multimedia Internet enabled phones, multimedia players, and the like.

System100(e.g., surveillance engine102and/or fault engine104) can receive (as input112) data representative of an initiation request to initiate and establish a communication session (e.g., a primary signaling path) between a first device and a second device. The initiation request can comprise data representative of information associated with calling party information (e.g., unique originating identifier (calling party's telephone number), quality of service (QoS) data, and the like) and receiving party information (e.g., unique destination identifier (receiving party's telephone number), etc.). The data representative of information associated with calling party information and receiving party information can be used, for instance, by a signaling service device to establish a communications session (e.g., IMS signaling path) between the calling party in the receiving party.

In response to receiving the data representative of information associated with calling party information and receiving party information, system100can determine whether IMS network infrastructure is operational, for example, system100can establish whether or not there are hard failures associated with the wider IMS network architecture. Further, system100can also trigger high level interrupts and/or watchdog timers (or generic timers configured to be: watchdog timers; countdown timers—timers that count down (decrease) from a first value to a second value; count-up timers—timers that count up (increase) from a first value to a second value; and the like). System100, as a function of, in response to, or based on, high level interrupts being triggered and/or input from the watchdog timers can further ascertain whether an IMS signaling path between the first device and the second device has been established via a device of groups of devices that can comprise the wider IMS network architecture. For example, where time, as determined by a watchdog timer, has reached a threshold value and the signaling path between the first device and the second device has not been established, system100can determine that there has been a failure with the underlying IMS network infrastructure. Where system100determines that a signaling path has been established between the first device and the second device, system100can determine that a communication session between the first device and the second device is in session.

Simultaneously, or in near contemporaneity, with receiving data representative of an initiation request to initiate and establish the communication session (e.g., the primary signaling path) between a first device and a second device, system100(e.g., surveillance engine102and/or fault engine104) can also initiate processes needed to establish a secondary signaling path (a non-IMS signaling path) from the first device to the second device. It should be appreciated that the secondary signaling path is generally, without limitation or loss of generality and for the purposes of this disclosure, only used when there are problems with initiating, establishing, and/or maintaining the primary signaling path (e.g., the IMS signaling path) between the first device and the second device. System100in order to initiate and establish the secondary signaling path from the first device to the second device can collect the calling information included in the initiation request (e.g., calling party information—unique originating identifier (calling party's telephone number) quality of service (QoS) data, security data and the like; and receiving party information—unique destination identifier (receiving party's telephone number), etc.) and initiate a wrapper application process that together with aspects included with WebRTC can contact the web application server device. As has been noted above, the secondary signaling path is a non-IMS signaling path that becomes operational in response to a determination that there has been a failure with regard to the primary IMS signaling path.

System100in response to the determination that there has been a failure with regard to the primary IMS signaling path between the first device and the second device, can initiate the secondary signaling path between the first device and the second device. Additionally, system100can determine whether a request to establish the secondary signaling path has been successful, and thereafter system100can apply the call attributes that can have been extant in regard to the primary IMS signaling path between the first device and the second device (e.g., QoS data, Codex data, security data, etc.)

FIG. 2illustrates system100, now represented as system200, that in accordance with various embodiments provides for fault-tolerant signaling in a LTE network architecture. In this depiction, system200can comprise surveillance engine102and fault engine104that can be communicatively coupled to processor106, memory108, and storage110. Additionally, communicatively coupled to surveillance engine102can be detection component202. Surveillance engine102in conjunction with detection component202can detect when a voice over long term evolution (VoLTE) session or a conventional video call session is being initiated, for example, by a first device attempting to establish a VoLTE session and/or a conventional video call session with a second device.

In regard to first device and second device, these devices can be any type of mechanism, machine, device, facility, apparatus, and/or instrument that includes a processor and/or is capable of effective and/or operative communication with a wired and/or wireless network topology. Mechanisms, machines, apparatuses, devices, facilities, and/or instruments that can comprise first device and/or second device can include, tablet computing devices, handheld devices, server class computing machines and/or databases, laptop computers, notebook computers, desktop computers, cell phones, smart phones, consumer appliances and/or instrumentation, industrial devices and/or components, hand-held devices, personal digital assistants, multimedia Internet enabled phones, multimedia players, devices associated with satellite technologies, devices included in stationary vehicles and/or vehicles in motion, devices associated with aeronautical vehicles, robotic devices, and the like.

FIG. 3provides additional illustration of system100, now represented as system300, that in accordance with various embodiments provides for fault-tolerant signaling in a LTE network architecture. As illustrated, system300can comprise detection component202operatively coupled to surveillance engine102, fault engine104, processor106, memory108, and storage110. Further, as illustrated system300can comprise determination component302that, in conjunction with detection component202and surveillance engine102, and as a function of detection component202having detected that a first device is attempting to establish a VoLTE session and/or a conventional video call session with a second device, can determine whether the IMS network infrastructure is operational. For instance, determination component302can establish whether or not there are hard failures associated with the wider IMS network architecture.

FIG. 4provides additional depiction of system100, now represented as system400, that in accordance with various embodiments provides for fault-tolerant signaling in a LTE network architecture. In this instance, system400can comprise trigger component402that can operate in collaboration with determination component302, detection component202, and surveillance engine102to trigger high level interrupts and/or watchdog timers. The watchdog timers associated with trigger component402can be generic timers that can be configured to be watchdog timers; countdown timers—timers that count down (decrease) from a first threshold value to a second threshold value; count up timers—timers that count up (increase) from a first threshold value to a second threshold value; and the like.

FIG. 5provides further depiction of system100, now represented as system500, that in accordance with various embodiments provides for fault-tolerant signaling in a LTE network architecture. System500illustrates a service component502that in conjunction with trigger component402, determination component302, detection component202, and surveillance engine102, and in response to, based on, and/or as a function of high level interrupts being triggered and/or input from the watchdog timers, can further determine whether an IMS signaling path between the first device and the second device has been established via the functionalities and functionalities associated with the wider IMS networking architecture(s) provided by one or more mobile networking operator (MNO). For instance, where time, as determined by a watchdog timer, has reached a threshold value in the signaling path from the first device to the second device has not been established, trigger component402in concert with service component502can determine that there has been a failure with the underlying IMS network infrastructure. Where trigger component402and service component502determine that there has been a failure to establish an IMS signaling path between the first device and the second device, and in response to the aforementioned determination (e.g., failure to establish an IMS signaling path between the first and the second devices), service component502can also cancel a service request that can have been initiated initially in order to establish the IMS signaling path between the first device and the second device, and, as will be discussed subsequently in connection with fault engine104and initiation component802, service component502can commence establishing a secondary/alternate signaling path (a non-IMS signaling path) between the first device and the second device.

FIG. 6provides yet further illustration of system100, now represented as system600, that in accordance with various embodiments provides for fault-tolerant signaling in a LTE network architecture. In regard to system600, system600can comprise collection component602that can operate in concert with service component502, trigger component402, determination component302, detection component202, and surveillance engine102can collect the calling information included with the initiation request from the first device (e.g., calling party information—unique originating identifier (e.g., subscriber number associated with the first device), quality of service (QoS) data associated with the first device, security data (e.g., public cryptographic key(s)) associated with the first device, and receiving party information—unique destination identifier (e.g., subscriber number associated with the second device), QoS data associated with the second device, security data associated with the second device, and the like. The calling information included with the initiation request from the first device attempting to establish a signaling path to the second device, it should be noted, will generally be the same information that will be used to establish the non-IMS signaling path.

FIG. 7provides still further depiction of system100, now represented as system700, that in accordance with various embodiments provides for fault-tolerant signaling in a LTE network architecture. System700as depicted can comprise collaboration component702that in conjunction with the functionalities and facilities provided by collection component602, service component502, trigger component402, determination component302, detection component202, and surveillance engine102can initiate a wrapper application process that together with aspects included with the WebRTC can contact a web application server device in order to establish a secondary/alternate signaling path between the first device and the second device. As will be appreciated by those having ordinary skill in the art, the Web application server device can establish the secondary/alternate signaling path based on information supplied by collection component602. The secondary/alternate signaling path, as will also be appreciated by those having skill in the art, will be a non-IMS signaling path between the first device and the second device, thereby circumventing any issues that might be preventing the establishment of a IMS signaling path. The non-IMS signaling path can be distinct and separate, and thereby provide a redundancy, to the IMS signaling path. The non-IMS signaling path therefore provides for fault-tolerance signaling in a LTE network architecture environment.

FIG. 8provides further illustration of system100, now represented as system800, that in accordance with various embodiments provides for fault-tolerant signaling in a LTE network architecture. System800can comprise surveillance engine102and fault engine104that can be communicatively coupled to processor106, memory108, and storage110. Additionally, system800also can comprise collaboration component702, collection component602, service component502, trigger component402, determination component302, and detection component202that can be communicatively coupled to surveillance engine102. Communicatively coupled to fault engine104can be initiation component802. Fault engine104in collaboration with initiation component802, in response to detection component202having received data representative of an initiation request to initiate and establish a communication session (e.g. a primary signaling path) between a first device and a second device, can initiate, simultaneously or in near contemporaneity, processes and/or procedures needed to initiate (though not necessarily establish) and maintain in a state of hibernation or stasis, a secondary signaling path from the first device to the second device. As has been noted above, the secondary signaling path (e.g., the non-IMS signaling path) is typically, without limitation or loss of generality, only used when there are problems with instantiating and/or maintaining a primary signaling path (e.g., the IMS signaling path) between the first device and the second device. Thus, if and when a failure to establish or maintain a primary signaling path between the first device and the second device is detected by service component502, for example, an indication by service component502can be sent to initiation component802, at which time and in response to the indication directed by service component502initiation component802can bring the initiated secondary signaling path out of the state of hibernation or stasis and establish the secondary signaling path from the first device to the second device.

FIG. 9provides further depiction of system100, now represented as system900, that in accordance with various embodiments provides for fault-tolerant signaling in a LTE network architecture. System900can comprise fault engine104communicatively and operatively coupled to initiation component802and query component902, wherein fault engine104, initiation component802, and query component902in collaboration can determine whether the secondary signaling path between the first device and the second device has been established successfully. In instances where the secondary signaling path has not been, or cannot be, successfully established between the first device and the second device, this circumstance can be due to a generalized networking failure associated with the non-IMS networking infrastructure, and as such a signaling path (e.g., IMS-signaling path and non-IMS signaling path) is unavailable and not communication can be established between the first device and the second device.

FIG. 10provides additional depiction of system100, now represented as system1000, that in accordance with various embodiments provides for fault-tolerant signaling in a LTE network architecture. System1000can comprise fault engine104that can be in operative communication with initiation component802, query component902and application component1002. In this instance, fault engine104, initiation component802, query component902, and application component1000in collaboration with one another can apply respective attribute data representing QoS attributes, security attributes, Codex data, etc. for each of the first device and the second can be applied to the established secondary signaling path (e.g., non-IMS signaling path) and a communication session between the first device and the second device can take place.

In view of the example system(s) described above, example method(s) that can be implemented in accordance with the disclosed subject matter can be better appreciated with reference to flowchart inFIG. 11. For purposes of simplicity of explanation, example method disclosed herein is presented and described as a series of acts; however, it is to be understood and appreciated that the disclosure is not limited by the order of acts, as some acts may occur in different orders and/or concurrently with other acts from that shown and described herein. For example, one or more example methods disclosed herein could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, interaction diagram(s) may represent methods in accordance with the disclosed subject matter when disparate entities enact disparate portions of the methods. Furthermore, not all illustrated acts may be required to implement a described example method in accordance with the subject specification. Further yet, the disclosed example method can be implemented in combination with one or more other methods, to accomplish one or more aspects herein described. It should be further appreciated that the example method disclosed throughout the subject specification are capable of being stored on an article of manufacture (e.g., a computer-readable medium) to allow transporting and transferring such methods to computers for execution, and thus implementation, by a processor or for storage in a memory.

FIG. 11illustrates a method1100that provides for fault-tolerant signaling in a LTE network architecture. Method1100can commence at act1102where an initiation of a primary signaling path to a signaling service device can be detected. At1104, as a function of the detection of the initiation of the primary signaling path to the signaling server device, an alternative signaling path to a web application server device can be initiated. At1106the primary signaling path can be monitored for a session failure representative of a call session. At1108in response to determining that a session failure has occurred, switching the call session from using the primary signaling path to using the alternate signaling path.

It should be realized and appreciated by those of ordinary skill, the foregoing non-limiting example use application(s) are merely illustrations of a use to which the disclosed and described solution can be applied and thus are provided solely for the purposes of exposition. The described and disclosed subject matter is therefore not limited to the foregoing example application(s), but can find applicability in other more generalized circumstances and use applications.

FIG. 12presents an example embodiment1200of a mobile network platform1210that can implement and exploit one or more aspects of the disclosed subject matter described herein. Generally, wireless network platform1210can include components, e.g., nodes, gateways, interfaces, servers, or disparate platforms, that facilitate both packet-switched (PS) (e.g., internet protocol (IP), frame relay, asynchronous transfer mode (ATM)) and circuit-switched (CS) traffic (e.g., voice and data), as well as control generation for networked wireless telecommunication. As a non-limiting example, wireless network platform1210can be included in telecommunications carrier networks, and can be considered carrier-side components as discussed elsewhere herein. Mobile network platform1210includes CS gateway node(s)1212which can interface CS traffic received from legacy networks like telephony network(s)1240(e.g., public switched telephone network (PSTN), or public land mobile network (PLMN)) or a signaling system #7 (SS7) network1270. Circuit switched gateway node(s)1212can authorize and authenticate traffic (e.g., voice) arising from such networks. Additionally, CS gateway node(s)1212can access mobility, or roaming, data generated through SS7 network1260; for instance, mobility data stored in a visited location register (VLR), which can reside in memory1230. Moreover, CS gateway node(s)1212interfaces CS-based traffic and signaling and PS gateway node(s)1218. As an example, in a 3GPP UMTS network, CS gateway node(s)1212can be realized at least in part in gateway GPRS support node(s) (GGSN). It should be appreciated that functionality and specific operation of CS gateway node(s)1212, PS gateway node(s)1218, and serving node(s)1216, is provided and dictated by radio technology(ies) utilized by mobile network platform1210for telecommunication.

In addition to receiving and processing CS-switched traffic and signaling, PS gateway node(s)1218can authorize and authenticate PS-based data sessions with served mobile devices. Data sessions can include traffic, or content(s), exchanged with networks external to the wireless network platform1210, like wide area network(s) (WANs)1250, enterprise network(s)1270, and service network(s)1280, which can be embodied in local area network(s) (LANs), can also be interfaced with mobile network platform1210through PS gateway node(s)1218. It is to be noted that WANs1250and enterprise network(s)1270can embody, at least in part, a service network(s) like IP multimedia subsystem (IMS). Based on radio technology layer(s) available in technology resource(s)1217, packet-switched gateway node(s)1218can generate packet data protocol contexts when a data session is established; other data structures that facilitate routing of packetized data also can be generated. To that end, in an aspect, PS gateway node(s)1218can include a tunnel interface (e.g., tunnel termination gateway (TTG) in 3GPP UMTS network(s) (not shown)) which can facilitate packetized communication with disparate wireless network(s), such as Wi-Fi networks.

In embodiment1200, wireless network platform1210also includes serving node(s)1216that, based upon available radio technology layer(s) within technology resource(s)1217, convey the various packetized flows of data streams received through PS gateway node(s)1218. It is to be noted that for technology resource(s)1217that rely primarily on CS communication, server node(s) can deliver traffic without reliance on PS gateway node(s)1218; for example, server node(s) can embody at least in part a mobile switching center. As an example, in a 3GPP UMTS network, serving node(s)1216can be embodied in serving GPRS support node(s) (SGSN).

For radio technologies that exploit packetized communication, server(s)1214in wireless network platform1210can execute numerous applications that can generate multiple disparate packetized data streams or flows, and manage (e.g., schedule, queue, format . . . ) such flows. Such application(s) can include add-on features to standard services (for example, provisioning, billing, customer support . . . ) provided by wireless network platform1210. Data streams (e.g., content(s) that are part of a voice call or data session) can be conveyed to PS gateway node(s)1218for authorization/authentication and initiation of a data session, and to serving node(s)1216for communication thereafter. In addition to application server, server(s)1214can include utility server(s), a utility server can include a provisioning server, an operations and maintenance server, a security server that can implement at least in part a certificate authority and firewalls as well as other security mechanisms, and the like. In an aspect, security server(s) secure communication served through wireless network platform1210to ensure network's operation and data integrity in addition to authorization and authentication procedures that CS gateway node(s)1212and PS gateway node(s)1218can enact. Moreover, provisioning server(s) can provision services from external network(s) like networks operated by a disparate service provider; for instance, WAN1250or Global Positioning System (GPS) network(s) (not shown). Provisioning server(s) can also provision coverage through networks associated to wireless network platform1210(e.g., deployed and operated by the same service provider), such as femto-cell network(s) (not shown) that enhance wireless service coverage within indoor confined spaces and offload radio access network resources in order to enhance subscriber service experience within a home or business environment by way of UE1275.

It is to be noted that server(s)1214can include one or more processors configured to confer at least in part the functionality of macro network platform1210. To that end, the one or more processor can execute code instructions stored in memory1230, for example. It is should be appreciated that server(s)1214can include a content manager1215, which operates in substantially the same manner as described hereinbefore.

In example embodiment1200, memory1230can store information related to operation of wireless network platform1210. Other operational information can include provisioning information of mobile devices served through wireless platform network1210, subscriber databases; application intelligence, pricing schemes, e.g., promotional rates, flat-rate programs, couponing campaigns; technical specification(s) consistent with telecommunication protocols for operation of disparate radio, or wireless, technology layers; and so forth. Memory1230can also store information from at least one of telephony network(s)1240, WAN1250, enterprise network(s)1270, or SS7 network1260. In an aspect, memory1230can be, for example, accessed as part of a data store component or as a remotely connected memory store.

FIG. 13illustrates a block diagram of a computing system1300operable to execute the disclosed systems and methods in accordance with an embodiment. Computer1312, which can be, for example, part of the hardware of system130, includes a processing unit1314, a system memory1316, and a system bus1318. System bus1318couples system components including, but not limited to, system memory1316to processing unit1314. Processing unit1314can be any of various available processors. Dual microprocessors and other multiprocessor architectures also can be employed as processing unit1314.

System bus1318can be any of several types of bus structure(s) including a memory bus or a memory controller, a peripheral bus or an external bus, and/or a local bus using any variety of available bus architectures including, but not limited to, Industrial Standard Architecture (ISA), Micro-Channel Architecture (MSA), Extended ISA (EISA), Intelligent Drive Electronics, VESA Local Bus (VLB), Peripheral Component Interconnect (PCI), Card Bus, Universal Serial Bus (USB), Advanced Graphics Port (AGP), Personal Computer Memory Card International Association bus (PCMCIA), Firewire (IEEE 1194), and Small Computer Systems Interface (SCSI).

System memory1316can include volatile memory1320and nonvolatile memory1322. A basic input/output system (BIOS), containing routines to transfer information between elements within computer1312, such as during start-up, can be stored in nonvolatile memory1322. By way of illustration, and not limitation, nonvolatile memory1322can include ROM, PROM, EPROM, EEPROM, or flash memory. Volatile memory1320includes RAM, which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as SRAM, dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM).

Computer-readable storage media can be any available storage media that can be accessed by the computer and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable instructions, program modules, structured data, or unstructured data. Computer-readable storage media can include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other tangible media which can be used to store desired information. In this regard, the term “tangible” herein as may be applied to storage, memory or computer-readable media, is to be understood to exclude only propagating intangible signals per se as a modifier and does not relinquish coverage of all standard storage, memory or computer-readable media that are not only propagating intangible signals per se. In an aspect, tangible media can include non-transitory media wherein the term “non-transitory” herein as may be applied to storage, memory or computer-readable media, is to be understood to exclude only propagating transitory signals per se as a modifier and does not relinquish coverage of all standard storage, memory or computer-readable media that are not only propagating transitory signals per se. For the avoidance of doubt, the term “computer-readable storage device” is used and defined herein to exclude transitory media. Computer-readable storage media can be accessed by one or more local or remote computing devices, e.g., via access requests, queries or other data retrieval protocols, for a variety of operations with respect to the information stored by the medium.

It can be noted thatFIG. 13describes software that acts as an intermediary between users and computer resources described in suitable operating environment1300. Such software includes an operating system1328. Operating system1328, which can be stored on disk storage1324, acts to control and allocate resources of computer system1312. System applications1330take advantage of the management of resources by operating system1328through program modules1332and program data1334stored either in system memory1316or on disk storage1324. It is to be noted that the disclosed subject matter can be implemented with various operating systems or combinations of operating systems.

A user can enter commands or information into computer1312through input device(s)1336. As an example, mobile device and/or portable device can include a user interface embodied in a touch sensitive display panel allowing a user to interact with computer1312. Input devices1336include, but are not limited to, a pointing device such as a mouse, trackball, stylus, touch pad, keyboard, microphone, joystick, game pad, satellite dish, scanner, TV tuner card, digital camera, digital video camera, web camera, cell phone, smartphone, tablet computer, etc. These and other input devices connect to processing unit1314through system bus1318by way of interface port(s)1338. Interface port(s)1338include, for example, a serial port, a parallel port, a game port, a universal serial bus (USB), an infrared port, a Bluetooth port, an IP port, or a logical port associated with a wireless service, etc. Output device(s)1340use some of the same type of ports as input device(s)1336.

Thus, for example, a USB port can be used to provide input to computer1312and to output information from computer1312to an output device1340. Output adapter1342is provided to illustrate that there are some output devices1340like monitors, speakers, and printers, among other output devices1340, which use special adapters. Output adapters1342include, by way of illustration and not limitation, video and sound cards that provide means of connection between output device1340and system bus1318. It should be noted that other devices and/or systems of devices provide both input and output capabilities such as remote computer(s)1344.

Computer1312can operate in a networked environment using logical connections to one or more remote computers, such as remote computer(s)1344. Remote computer(s)1344can be a personal computer, a server, a router, a network PC, cloud storage, cloud service, a workstation, a microprocessor based appliance, a peer device, or other common network node and the like, and typically includes many or all of the elements described relative to computer1312.

For purposes of brevity, only a memory storage device1346is illustrated with remote computer(s)1344. Remote computer(s)1344is logically connected to computer1312through a network interface1348and then physically connected by way of communication connection1350. Network interface1348encompasses wire and/or wireless communication networks such as local-area networks (LAN) and wide-area networks (WAN). LAN technologies include Fiber Distributed Data Interface (FDDI), Copper Distributed Data Interface (CDDI), Ethernet, Token Ring and the like. WAN technologies include, but are not limited to, point-to-point links, circuit-switching networks like Integrated Services Digital Networks (ISDN) and variations thereon, packet switching networks, and Digital Subscriber Lines (DSL). As noted below, wireless technologies may be used in addition to or in place of the foregoing.

Communication connection(s)1350refer(s) to hardware/software employed to connect network interface1348to bus1318. While communication connection1350is shown for illustrative clarity inside computer1312, it can also be external to computer1312. The hardware/software for connection to network interface1348can include, for example, internal and external technologies such as modems, including regular telephone grade modems, cable modems and DSL modems, ISDN adapters, and Ethernet cards.

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,” subscriber station,” “subscriber equipment,” “access terminal,” “terminal,” “handset,” and similar terminology, refer to a wireless device utilized by a subscriber or user of a wireless communication service to receive or convey data, control, voice, video, sound, gaming, or substantially any data-stream or signaling-stream. The foregoing terms are utilized interchangeably in the subject specification and related drawings. Likewise, the terms “access point (AP),” “base station,” “NodeB,” “evolved Node B (eNodeB),” “home Node B (HNB),” “home access point (HAP),” “cell device,” “sector,” “cell,” and the like, are utilized interchangeably in the subject application, and refer to a wireless network component or appliance that serves and receives data, control, voice, video, sound, gaming, or substantially any data-stream or signaling-stream to and from a set of subscriber stations or provider enabled devices. Data and signaling streams can include packetized or frame-based flows.

Aspects, features, or advantages of the subject matter can be exploited in substantially any, or any, wired, broadcast, wireless telecommunication, radio technology or network, or combinations thereof. Non-limiting examples of such technologies or networks include Geocast technology; broadcast technologies (e.g., sub-Hz, ELF, VLF, LF, MF, HF, VHF, UHF, SHF, THz broadcasts, etc.); Ethernet; X.25; powerline-type networking (e.g., PowerLine AV Ethernet, etc.); femto-cell technology; Wi-Fi; Worldwide Interoperability for Microwave Access (WiMAX); Enhanced General Packet Radio Service (Enhanced GPRS); Third Generation Partnership Project (3GPP or 3G) Long Term Evolution (LTE); 3GPP Universal Mobile Telecommunications System (UMTS) or 3GPP UMTS; Third Generation Partnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB); High Speed Packet Access (HSPA); High Speed Downlink Packet Access (HSDPA); High Speed Uplink Packet Access (HSUPA); GSM Enhanced Data Rates for GSM Evolution (EDGE) Radio Access Network (RAN) or GERAN; UMTS Terrestrial Radio Access Network (UTRAN); or LTE Advanced.