Signaling-less dynamic call setup and teardown by utilizing observed session state information

A system and methodology that facilitates signaling-less call setup and teardown by employing observed Quality of Experience (QoE) and resource demands is provided. Moreover, the system provides an environment for supersonic treatment of observed QoE and Quality of Service (QoS) demands for mobile applications. Specifically, a monitoring component is employed to determine session state information associated with a traffic flow, which includes observed QoE and resource demand data. The session state information is stored in a shared memory location and can be analyzed to modify and/or create a network policy for the traffic flow. The network policy is applied to one or more traffic flows to minimize signaling exchanges between a communication network and a mobile station.

TECHNICAL FIELD

The subject disclosure relates to wireless communications and, more particularly, to facilitating dynamic call setup and/or teardown based on an observed Quality of Experience (QoE) and/or resource demand.

BACKGROUND

Advances in wireless telecommunications are rapidly increasing the utilization of mobile devices that handle communication of media and data between users and providers. Typically, mobile devices have connected to mobile networks, such as a wireless wide area network (WWAN) employing a wireless connection (e.g. 2G/3G/3.5G/4G). Traditionally, voice services over wireless networks were provided by circuit-switched (CS) systems wherein a dedicated channel was used for each voice call. Although CS systems provide a guaranteed Quality of Service (QoS) in terms of end-to-end (ETE) delay for the voice traffic, the network is inefficiently utilized. This is because resources for the dedicated channel are always reserved, even when communication is not carried out over the channel.

In particular, traditional CS networks enable opening a circuit between participants at the beginning of a call and allocating the total bandwidth on that circuit to the participants for the duration of the call. If the participants need less bandwidth, the operator cannot share the allocated bandwidth with other users, or if they need more bandwidth, the operator is unable to provide additional bandwidth. As wireless communications evolve, packet-switched (PS) networks have been developed that provide operators extra flexibility to optimize coverage, call quality and data speed. PS networks typically stream one or more packets (voice and/or data) to/from the user, by a route, which is determined based on an algorithm. Thus, the network operator can prioritize different types of packets according to user demand. However, the PS network imposes a ‘best-effort’ constraint on packet delivery. For example, the PS network employs best efforts to deliver packets to their destination on time, but the PS network cannot guarantee their arrival schedule.

In addition, the wireless environment and the mobility of users present additional challenges to packet delivery. For example, radio channel conditions between a device and the network can usually vary and the channel can become better or worse over time. Thus, a constant Quality of Service (QoS) is difficult to maintain over time. The traditional signaling approach provides a significant overhead with signaling exchanges among the networks and devices. Accordingly, call setup and treatment is delayed and is not optimum. Further, for advanced data services in mobile communications, such as, but not limited to, email, streaming and/or video communication, the conventional systems do not provide significant QoS support, leading to inefficient utilization of network resources.

SUMMARY

The systems and methods disclosed herein, in one aspect thereof, can facilitate dynamic adjustment of one or more traffic flows based in part on observed Quality of Experience (QoE) information and/or resource demand in a packet switched communication network. Typically, the system can observe conditions associated with a traffic flow and determine session state information for the flow. As an example, the session state information can include, but is not limited to, a session name associated with the flow, a mode of operation, a Quality of Experience (QoE) factor, observed QoE value, resource requirements, observed network states, etc. Further, the system can store the determined session state information in a shared database. The shared database can reside at source (e.g. UE, application), within network, within an external entity, and/or can be distributed. According to an embodiment, the stored information can be accessed by most any monitoring tool, which can update the stored information. According to another embodiment, the stored information can be pulled by most any scheduling tool and/or application, which can utilize the stored session state information to make policy decisions.

In accordance with another aspect, a scheduling component can be employed that can facilitate policy decisions based on an analysis of the information stored in the shared database. The policy decisions can include updating an existing policy and/or creating a new policy. In one aspect, the scheduling component can dynamically apply the updated or new policy to a flow or a group of flows based on the analysis. Moreover, updating the policy can include, but is not limited to, updating a Quality of Service (QoS) class for the flow or the group of flows, updating a mode of operation (e.g., setting an idle mode), applying back pressure on a set of flows when congestion is observed, updating amount of resources allocated to the flow, etc.

Yet another aspect of the disclosed subject matter relates to a method that can be employed to facilitate dynamic adjustment of a network policy and efficient end-to-end (ETE) resource utilization based on observed QoE data. Typically, session state data associated with a traffic flow (e.g., audio, video, data, multimedia, etc.) can be monitored and stored in a shared database. The session state data can include, but is not limited to, observed QOE, network state dynamics, resource demands, and/or user/application/service provider preferences. In one aspect, the session state data can be pulled from the shared database for example, periodically, dynamically, based on network provider and/or user preferences, based on a network policy, etc. Moreover, the pulled session state data can be analyzed and a network policy can be updated based on the analysis. Further, the updated network policy can be applied to a set of traffic flows to minimize signaling between the communication network and mobile stations.

DETAILED DESCRIPTION

One or more embodiments are now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments. It may be evident, however, that the various embodiments can be practiced without these specific details, e.g., without applying to any particular networked environment or standard. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing the embodiments in additional detail.

Moreover, terms like “user equipment,” “mobile station,” “mobile,” subscriber station,” “access terminal,” “terminal,” “handset,” “end device,” “mobile device,” 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,” “base station,” “Node B,” “evolved Node B,” “home Node B (HNB),” 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 from a set of subscriber stations. Data and signaling streams can be packetized or frame-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” and the like are employed interchangeably throughout the subject specification, unless context warrants particular distinction(s) among the terms. It should be appreciated that such terms can refer to human entities or automated components supported through artificial intelligence (e.g., a capacity to make inference based on complex mathematical formalisms), which can provide simulated vision, sound recognition and so forth.

Traditional wireless communication systems employ a significant amount of signaling during call setup and teardown. The overhead associated with the signaling leads to delayed (and/or not optimum) application flows. The systems and methods disclosed herein provide an ability to treat application flows in optimum manner instead of utilizing massive signaling overhead. In one example, end devices, for example, user equipment (UE), can update their session state information at a source in a distributed shared memory virtual address. The session state information can include observed Quality of Experience (QoE) data, which can be collectively utilized by a scheduler in the network to update and/or modify a flow, a service provider policy, etc. Accordingly, signaling overhead can be reduced and updates and/or adjustments to a QoE and/or Quality of Service (QoS) matrices can be performed with simple updates to the matrices.

Aspects, features, or advantages of the subject innovation can be exploited in substantially any wireless communication technology; e.g., Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), Enhanced General Packet Radio Service (Enhanced GPRS), Third Generation Partnership Project (3GPP) Long Term Evolution (LTE), Third Generation Partnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB), High Speed Packet Access (HSPA), or Zigbee. Additionally, substantially all aspects of the subject innovation can be exploited in legacy telecommunication technologies.

Referring initially toFIG. 1, there illustrated is an example system100that facilitates storage of observed session state information associated with a traffic flow in a wireless communication network, in accordance with an aspect of the subject system. Typically, system100can include a monitoring component102that can be utilized to observe conditions associated with a traffic flow. It can be appreciated that the traffic can include, but is not limited to, voice, video, and/or data traffic. In one aspect, the monitoring component102can determine session state information associated with the traffic flow. As an example, the session state information can include, but is not limited to, a session name, a mode of operation, data indicating whether a Quality of Experience (QoE) factor is enabled or disabled, observed QoE, resource requirements, observed network states, etc.

According to an aspect, the observed QoE can be determined by monitoring the traffic flow and analyzing various factors, such as, the number of good packets received by a user equipment (UE), a rate of receiving good packets, delay, jitter, bandwidth, frame rate, packet loss, and/or most any information associated with an application on the UE. However, observed QoE determination is not limited to the aforementioned factors and observed QoE can be determined based on location of UE, GPS data, user satisfaction, content of data delivered, etc. In one example, application specific QoE contract can be location specific, such as, but not limited to, inside a building versus outside the building, in dense metro areas, etc.

In one embodiment, the monitoring component102can reside within a UE. In this case, the monitoring component102can observe QoE at the UE. For example, the monitoring component102can determine that the UE is not receiving packets at a specific rate that is suitable for communication and/or providing user satisfaction, and/or can determine that “X” number of packets were dropped, an/or can determine user satisfaction based on explicit user input and/or user satisfaction can be inferred, etc. In an additional or alternate embodiment, the monitoring component102can reside within the communication network, for example the core network. In this case, the monitoring component102can apply one or more policies, for example, set by a service provider, to determine a QoE observed by a UE. Further, an application (e.g. at the source) can also facilitate determination of observed QoE, session state information, resource utilization information, and/or the like. In one aspect, the monitoring component102can determine observed QoE based on determination of various parameters, such as, but not limited to, bandwidth, delay, jitter, packet loss, frame rate, content of data, location specifics, etc. For example, an application specific QoE contract can be location specific, such as, based on location of UE (e.g., inside or outside a building, in a dense metro area, etc.). In one example, the set of parameters for QoE determination can be specified by the UE, application and/or network.

Furthermore, the system100can include a shared database104that can be updated by the monitoring component102. The shared database104can reside at source (e.g., UE), within network, within an external entity, and/or can be distributed. In particular, the shared database104can include mutual and/or shared memory locations, which can be updated by an application, a network, and/or a UE, with session state information and can reside completely or partially in a source, an application, the network or a UE. In one aspect, the shared database104can be accessed by most any monitoring tool, such as monitoring component102, which can write to the memory. Additionally, most any tool and/or application can utilize shared locks to concurrently and/or simultaneously read the stored data and utilize the stored session state data to make a policy decision.

In one aspect, when the shared database104is within a UE, information from the shared database104can be pulled by the communication network in an aggregated form, periodically, dynamically, in real-time, etc. In another aspect, when the shared database104is within the communication network, the session state information can be stored in the shared database104by a sample caching mechanism that can run in the background. Specifically, the shared database104can maintain session state information, which can include observed QoE and resource specifications for each flow within the communication network. The monitoring component102can update the stored information for each flow based on the observations. Observed QoE and network state dynamics can also be stored in the shared database104.

In an aspect, the monitoring component102can change, update and/or modify the session states stored in the shared database104within specified boundaries, for example, bandwidth can trotter between 0-1 Meg, delay can be bounded between 100 ms and 200 ms, jitter can be set to specific range, observed QOE can be updated, network resource requirements can be specified, enforced polices can be set, UE location can be set (e.g., indoor, outdoor, home, work, vehicular, etc.). According to an embodiment, the information stored in shared database104, including observed QoE and/or resource requirements can be utilized by a scheduler or application with a core network, to adjust the Quality of Service (QoS) support associated with the flow based in part the observed QoE. Further, the scheduler can also update routes, schedules and/or network policies based on the observed QoE and/or resource requirements.

Referring toFIG. 2, there illustrated is an example system200that can be employed for signaling-less dynamic call setup and teardown in accordance with an aspect of the subject disclosure. It can be appreciated that the monitoring component102and shared database104can include respective functionality, as more fully described herein, for example, with regard to system100.

According to an aspect, the monitoring component102and/or shared database104can reside within a UE and/or a communication network. Typically, the UE as disclosed herein can include most any communication device employed by a subscriber, such as, but not limited to, a cellular phone, a personal digital assistant (PDA), a laptop, a personal computer, a media player, a gaming console, and the like. Moreover, the UE can access the communication network via most any radio technology. It can be appreciated that the communication network can include most any radio environment, such as, but not limited to, Universal Mobile Telecommunications System (UMTS), Global System for Mobile communications (GSM), LTE, WiFi, WiMAX, CDMA, etc.

As described previously, the monitoring component102can observe and determine session state information associated with a traffic flow between the communication network and the UE. Specifically, the monitoring component102can determine an observed QoE for a traffic flow, based on various factors, such as but not limited to, packet delivery rate, dropped packet rate, frame rate, UE preferences, network preferences, application preferences, user input, delay, jitter, bandwidth, location specifics, etc. Further, the monitoring component102can store the determined information within shared database104. In one aspect, the information stored in the shared database104can include, observed QoE202, resource demands204, and/or, user and/or application preferences206. For example, the monitoring component102can calculate an observed QoE that is experienced by an end user and can also determine whether additional network resources can help improve QoE, for example beyond a specified threshold. The observed QoE202and resource demands204data can be stored by the monitoring component102in the shared database104. Further, user and/or application (or device) preferences (e.g., a user can set a preference in an application on the UE to receive a notification or alert each time an email is received) can be stored within104.

System200further includes a scheduling component208that facilitates policy decisions based on an analysis of the information stored in shared database104that can adjust the traffic flow. In one aspect, the scheduling component208can apply one or more policies for a flow or a group of flows depending on analysis. As an example, the scheduling component208can update the QoS class, update the mode of operation (e.g., set an idle mode), apply backpressure on as set of flows when congestion is observed (e.g., by the monitoring component102), etc., for the flow or group of flows. Typically, the observed QoE associated with a flow can continuously vary because of the wireless & mobile nature of communications. For example, when a UE is in motion, the signal strength can change and observed QoE can change. System200can facilitate observing the QoE (e.g., by the monitoring component102) and accordingly adapting one or more flows (e.g., by the scheduling component208).

Referring now toFIG. 3, there illustrated is an example system300that can be employed to facilitate dynamic adjustment of one or more traffic flows based in part on observed QoE information, according to an aspect of the subject disclosure. It can be appreciated that the monitoring component102, shared database104and scheduling component208can include respective functionality, as more fully described herein, for example, with regard to systems100and200. In one aspect, the monitoring component102and shared database104can be located within a UE302. However, the subject application is not so limited and as noted previously, the monitoring component102and the shared database104can reside completely, partially, or be distributed between, UE302, network304, an application or a third party entity (not shown).

Additionally, UE302can be, but is not required to be, for instance, a communication device, a multi-mode device, a dual-mode device, a dual-mode cellular/IP device, a mobile communication device, a cellular device that connects to a fixed IP network, a smartphone, a gaming device, a home media center, a portable media player, a satellite phone, a desktop device, a cellular phone, a portable gaming device, a mobile phone, a portable music player, a portable device, a laptop, a personal digital assistant, or a handheld or combinations thereof that can employ most any wireless mobile communication technology to communicate with network304.

System300can typically include an aggregation component306that can be utilized to aggregate information stored within the shared database104. It can be appreciated that although the aggregation component306is illustrated to reside within the UE302, the aggregation component306can reside at most any location, such as, but not limited to, within the network304, the scheduling component208, and/or at a third party entity (not shown). In one aspect, the aggregation component306can analyze the information in the shared database104and select data that can be delivered to the scheduling component, in a manner such that signaling is reduced. As an example, the aggregation component306can identify essential information associated with a traffic flow, which can be utilized by the scheduling component208to make policy decisions. Further, the aggregation component306can also aggregate information associated with multiple flows and/or can sample the data associated with multiple flows from the shared database104. Typically, the multiple flows can belong to a specific category, as explained in detail infra.

The scheduling component208can utilize the aggregated information to create or update a policy associated with the traffic flow and/or with the multiple traffic flows. According to an aspect, a data pulling component308can be utilized to pull data from the aggregation component306. In one example, the pulling component308can pull data depending on a service provider preference, such as, but not limited to, periodically or in real time. Typically, a network operator can determine a time period for pulling data or the time period can be automatically determined, for example, when the network is idle or when available bandwidth is greater than a threshold. In one aspect, the scheduling component208can update one or more policies, such as, a policy that determines allocation of resources, flow routes, QoS support, etc. based on an analysis of the received data. Moreover, an Internet Protocol (IP) architecture can be enhanced with real time source and/or network initiated session state updates. In particular, a simple trigger protocol can be employed (e.g., by the data pulling component308) to synch up the state changes from the shared database104with the network and vise versa. In one aspect, the data pulling component308can sample data from different UEs for aggregation treatment and the scheduling component208can modify one or more policies associated with disparate UEs based on the aggregation data. Additionally, the data pulling component308can pull the session state updates every interval and avoid massive signal processing performed in conventional systems. Accordingly, a faster steady state can be achieved by pulling session state information from the end devices and signaling exchanges among the networks and devices can be minimized. In addition, dynamic and QoS/QoE adaptation can be achieved in a distributed fashion and signaling overhead can be reduced, for example, by 10-100 folds.

FIG. 4illustrates an example system400that provides a shared memory space, which can store session state information associated with a traffic flow that can be utilized to dynamically adjust one or more network policies in accordance with the subject innovation. It can be appreciated that the shared database104, scheduling component208, UE302, and network304can include respective functionality, as more fully described herein, for example, with regard to systems100,200and300. Further, monitoring component1(402) and monitoring component2(404) can be substantially similar to monitoring component102as more fully disclosed herein, for example, with regard to systems100,200and300, and can include functionality thereof.

The shared database104included in system400can be updated by monitoring component1402and/or monitoring component2404. It can be appreciated that although the shared database104is depicted to reside on the network304, the shared database can be located on the UE302, at a third party entity, on a disparate network, and/or can be distributed. Moreover, monitoring component1402can determine session state information associated with a traffic flow based on various factors, such as, but not limited to, the communication received at the UE302, the location of the UE302, motion of the UE302, user input, etc. Further, the UE302can allocate a session state memory area when a call is initiated or terminated, and can update the session state dynamics including the observed application QoE. According to one aspect, the determined information can be aggregated (e.g., by an aggregation component306) and can be pulled by the network and stored within the shared database104, for example, periodically, dynamically, or based on a specified policy.

Additionally or alternately, the monitoring component2404can also determine session state information associated with the traffic flow (and/or disparate traffic flows) and update the shared database104. As an example, monitoring component2404can be located most anywhere in the network304and can determine session state information associated with a traffic flow based on most any proxy monitoring mechanism. For example, session state information associated with a flow can be determined based on a policy defined by a network operator, content delivery time, amount of data exchanged, etc. In one aspect, the monitoring component2404can classify traffic flows within network304into multiple categories and can sample data associated with a subset of flows in each category. Moreover, the sampled data can be stored in the shared database104. In one aspect, monitoring component2404can be useful for monitoring traffic flows and determining session state information for the traffic flows to UEs that do not include a monitoring component (not shown).

According to an embodiment, the scheduling component208can retrieve data associated with the traffic flow (and/or the subset of traffic flows) from the shared database104and can analyze the retrieved information. Based on the analysis, the scheduling component208can create a new network policy and/or update/delete an existing network policy associated with the traffic flow and/or a set of disparate traffic flows (e.g., that belong to the same category as the traffic flow). In one aspect, a network policy store406can be employed that stores network policies associated with traffic flows in network304. The network policy store406can be updated by the scheduling component208based on an analysis of the data from shared database104. As an example, the scheduling component208can update a policy that facilitates allocation of resources, flow routes, QoS support, etc. associated with the traffic flows. Typically, the network policy store406can include, and is not limited to, both volatile and nonvolatile memory, removable and non-removable memory.

Consider an example, wherein, the shared database104can store one or more user preferences. Typically, applications (e.g. on UE302) can decide what type of features the application can employ and/or decide the signaling between the application and network304. Oftentimes, these decisions can increase network traffic and lead to network performance issues. For example, a user can set a preference via UE302to receive a notification from an email server when the user gets an email. However, when the volume of emails is large, the network304can easily get overloaded. In this example scenario, the scheduling component208can determine and/or modify a policy within the network policy store406that can be enforced, such that the signaling is minimized and congestion and/or network overload can be avoided. As an example, the scheduling component208can create/modify a policy, which can ensure that signals from the email server can be aggregated, such that, a notification can be sent to the UE302when the network304is idle, or periodically, or after “X” number of signals are received, (where “X” can be most any natural number from 1 to infinity), etc.

In another example scenario, an application can get aggressive when information is not properly received at the UE302through the network304. Moreover, aggressive applications can retransmit signals too often, resulting in network congestion. The scheduling component208can create/modify a policy, which can ensure that the application is notified of the current network status. Further, information stored in shared database104, for example, observed QoE data, can be visible to both the application and the network304. Accordingly, based on an analysis of the stored information, the scheduling component208can facilitate adjusting network policies to apply backpressure, adjust bandwidth allocation, and/or request the application to back off when the network is busy. According to an aspect, the shared database104provides the scheduling component208a view of UE behavior, which facilitates enhanced and optimized end-to-end (ETE) QOS and QOE treatment. The scheduling component208can enable the networks304and router nodes to drive their route updates from the UEs in their domains. In one aspect, the scheduling component208can interact independently based on its aggregation view of the session state information collected for ETE treatment.

FIG. 5illustrates a system500that employs an artificial intelligence (AI) component502, which facilitates automating one or more features in accordance with the subject innovation. It can be appreciated that the shared database104, scheduling component208, monitoring component2404, network policy store406, and network304can include respective functionality, as more fully described herein, for example, with regard to systems100,200,300and400. The subject innovation (e.g., in connection with monitoring and/or analysis) can employ various AI-based schemes for carrying out various aspects thereof. For example, a process for determining an update to a policy stored in the network policy store406can be facilitated via an automatic classifier system and process.

A classifier is a function that maps an input attribute vector, x=(x1, x2, x3, x4, xn), to a confidence that the input belongs to a class, that is, f(x)=confidence(class). Such classification can employ a probabilistic and/or statistical-based analysis (e.g., factoring into the analysis utilities and costs) to prognose or infer an action that a user desires to be automatically performed. In the case of wireless communication systems, for example, attributes can be derived from information stored in the shared database104and the classes can be categories or areas of interest (e.g., levels of priorities).

As will be readily appreciated from the subject specification, the subject innovation can employ classifiers that are explicitly trained (e.g., via a generic training data) as well as implicitly trained (e.g., via observing user behavior, receiving extrinsic information). For example, SVM's are configured via a learning or training phase within a classifier constructor and feature selection module. Thus, the classifier(s) can be used to automatically learn and perform a number of functions, including but not limited to determining according to a predetermined criteria when the shared database can be updated, when and how a network policy can be updated/created/deleted, etc. The criteria can include, but is not limited to, observed QoE, resource demands, historical patterns, UE behavior, user preferences, service provider preferences and/or policies, location of the UE, motion of the UE, network status, etc.

Referring now toFIG. 6, illustrated is an example methodology600that can be utilized to facilitate minimizing signaling exchanges among networks and mobile devices, during communication setup and/or teardown. At602, session state information associated with a traffic flow can be determined. As an example, the session state information can include, but is not limited to, a session name associated with the flow, a mode of operation, a QoE factor that indicates whether QoE is enabled or disabled, an observed QoE, resource demand, an observed network state, etc. Further, it can be appreciated that the session state information can be determined by monitoring and/or observing the traffic flow, location and/or motion of the mobile device, user preferences, network provider preferences, and the like. Specifically, the monitoring and/or observing can be performed on the network side, mobile device side and/or by a third party entity. Moreover, the session state information can be stored in the shared memory location by employing a sample caching mechanism that can run in the background.

At604, a shared memory location can be updated with the determined session state information. The shared memory location can be read by one or more decision making tool that can update a policy, modify allocation of resources, and/or adjust a route based on an analysis of the stored information. According to one aspect, the session state information can be pulled, for example, by the network in an aggregated form, periodically, dynamically, in real-time, when network is idle, etc.

FIG. 7illustrates an example methodology700that facilitates dynamically adjusting one or more network policies and increasing ETE resource utilization based on observed QoE data, in accordance with an aspect of the subject specification. At702, session state data associated with a traffic flow (e.g., audio, video, data, multimedia, etc.) can be received. In one aspect, the session state data can be pulled from an end device, and/or a shared database for example, periodically, dynamically, based on network provider and/or user preferences, based on a network policy, etc. The session state data can include, but is not limited to, observed QoE, network state dynamics, resource demands, and/or user/application/service provider preferences. As an example, the observed QoE can be determined based on determining various parameters associated with the traffic flow, such as, but not limited to, packet delivery rate, dropped packet rate, frame rate, UE preferences, network preferences, application preferences, user input, delay, jitter, bandwidth, location specifics, etc. Typically, the application and/or network can agree on a QoE parameter set.

At704, the received session state data can be analyzed. Further, at706one or more network policies can be updated based on the analysis. Furthermore, at708, the one or more updated policies can be applied to a set of traffic flows to minimize signaling between the communication network and end device. For example, a QoS class for a flow or group of flows can be updated, a mode of operation (e.g., set an idle mode) can be set and/or changed, resource allocation can be changed, backpressure can be applied (when congestion is observed), etc.

FIG. 8illustrates an example methodology800that facilitates mitigating signal exchange and processing during dynamic call setup and/or teardown based on an observed Quality of Experience (QoE) and/or resource demands, according to an aspect of the subject disclosure. At802, communication sessions can be categorized. In one aspect, sessions with one or more common or similar properties can be grouped in the same category. At804, QoE and/or resource demand DATA can be sampled in each category. Specifically, an observed QoE and/or resource demand associated with one or more sample sessions can be determined. More specifically, the sampled data can be analyzed and a network policy can be created and/or adjusted based on the analysis. At806, the network policy can be applied to a set of sessions in the category. For example, data, including observed QoE and/or resource demand, associated with a particular session (e.g., session number 7), can be determined and a policy can be updated based on an analysis of the data. The updated policy can be applied to set of sessions (e.g., session numbers 7, 12, and 22) and/or all the sessions in the category.

FIG. 9illustrates an exemplary UMTS network900that facilitates dynamic call setup and/or teardown based on session state information in accordance with the subject innovation. The architecture is based on the 3GPP (Third Generation Partnership Project) Release 99 specification. However, it is to be understood that the subject innovation can be applied to any UMTS telecommunications architecture, including by way of example, Release 5 (R5) and, R5 and Release 6 (R6) 3GPP standards. UMTS offers teleservices (e.g., speech and/or SMS-Short Message Service) and bearer services, which provide the capability for information transfer between access points. Negotiation and renegotiation of the characteristics of a bearer service can be performed at session or connection establishment, and during an ongoing session or connection. Both connection oriented and connectionless services can be offered for point-to-point and point-to-multipoint communications.

The following frequencies 1885-2025 MHz and 2110-2200 MHz can be allocated for UMTS use. However, the innovative aspects described herein can also be applied to other frequency bands. Bearer services can have different QoS (quality-of-service) parameters for maximum transfer delay, delay variation and bit error rate. Offered data rate targets are: 144 kbps satellite and rural outdoor; 384 kbps urban outdoor; and 2048 kbps indoor and low range outdoor.

UMTS network services can have different QoS classes for four types of traffic: conversational class (e.g., voice, video telephony, video gaming); streaming class (e.g., multimedia, video on demand, webcast); interactive class (e.g., web browsing, network gaming, database access); and background class (e.g., email, SMS, downloading). UMTS can also support have a virtual home environment, which is a concept for portability across network boundaries and between terminals in a personal service environment. Personal service environment means that users are consistently presented with the same personalized features, user interface customization and services in whatever network or terminal, wherever the user may be located. UMTS also includes network security and location based services.

The UMTS network900can consist of three interacting domains; a user equipment (UE) domain902, a UMTS Terrestrial Radio Access Network (UTRAN) domain904, and a core network (CN) domain906. The UTRAN domain904is also referred to as the access network domain and the CN906is referred to as the core network domain, the both of which comprise an infrastructure domain.

The UE domain902includes a USIM (user services identity module) domain and an ME (mobile equipment) domain. User equipment is the equipment used by the user to access UMTS services. In the UE domain902, the UMTS IC card is the USIM908, which has the same physical characteristics as GSM SIM (subscriber identity module) card. The USIM interfaces to ME910via a Cu reference point. Functions of the USIM include: support of one USIM application (and optionally, more than one); support of one or more user profiles on the USIM; update of USIM specific information over the air; security functions; user authentication; optional inclusion of payment methods; and optional secure downloading of new applications.

UE terminals work as an air interface counter part for Node-B devices of the access network and have many different types of identities. Following are some of the UMTS identity types, which are taken directly from GSM specifications: international mobile subscriber identity (IMSI); temporary mobile subscriber identity (TMSI); packet temporary mobile subscriber identity (P-TMSI); temporary logical link identity (TLLI); mobile station ISDN (MSISDN); international mobile station equipment identity (IMEI); and international mobile station equipment identity and software version number (IMEISV).

A UMTS mobile station (MS) can operate in one of three modes of operation. A PS/CS mode of operation is where the MS is attached to both the PS (packet-switched) domain and CS (circuit-switched) domain, and the MS is capable of simultaneously operating PS services and CS services. A PS mode of operation is where the MS is attached to the PS domain only, and can only operate services of the PS domain. However, this does not prevent CS-like services from being offered over the PS domain (e.g., VoIP). In a third CS mode of operation, the MS is attached to the CS domain only, and can only operate services of the CS domain.

The UTRAN904provides the air interface access method for the UE domain902. The reference point between the UE domain and the infrastructure domain is the Uu UMTS radio interface. The access network domain provides the physical entities that manage resources of the access network and facilitates access to the core network domain. In UMTS terminology, a base station of the access network domain is referred as a Node-B device912, and control equipment for Node-B devices is called a radio network controller (RNC)914. The interface between the Node-B device and the RNC914is the IuB interface. The interface between two RNCs is called the Iur interface. According to an aspect, the adaptive R99 CS and CS over HSPA Link diversity that facilitates enhanced coverage and capacity, described in detail supra, can be implemented in the UTRAN904.

The functions of Node-B devices include: air interface transmission/reception; modulation and demodulation; CDMA (Code Division Multiple Access) physical channel coding; micro diversity; error handing; and closed loop power control. The functions of the RNC include: radio resource control; admission control; channel allocation; power control settings; handover control; macro diversity; ciphering; segmentation and reassembly; broadcast signaling; and open loop power control.

Wideband CDMA (WCDMA) technology was selected for UTRAN air interface. UMTS WCDMA is a direct sequence CDMA system where user data is multiplied with quasi-random bits derived from WCDMA spreading codes. In UMTS, in addition to channelization, codes are used for synchronization and scrambling. WCDMA has two basic modes of operation: frequency division duplex (FDD) and time division duplex (TDD).

The Core Network is divided in circuit-switched and packet-switched domains. Some of the circuit-switched elements are a mobile services switching center (MSC) and visitor location register (VLR)916and gateway MSC (GMSC)918. Packet-switched elements include a serving GPRS support node (SGSN)920and gateway GPRS support node (GGSN)922. Some network elements such as an EIR (equipment identity register) (not shown), HLR (home location register)924, VLR and AuC (authentication center) (not shown) can be shared by both domains.

A function of the CN902is to provide switching, routing and transit for user traffic. The CN902also contains the databases and network management functions. The basic CN architecture for UMTS is based on the GSM network with GPRS (general packet radio service) capability. All equipment is modified for UMTS operation and services. The radio access network has several interfaces that can be configured and dimensioned. The CN906interfaces to the radio access domain via an Iu interface. An Iu-CS (circuit-switched) reference point interfaces an RNC of the access network to the MSC/VLR entity916of the CN906for voice from/to the MSC/VLR916. An Iu-PS (packet-switched) reference point interfaces an RNC of the access network to the SGSN entity920of the CN906for data from/to the SGSN920.

In the CN906, a Gs interface is provided between the MSC/VLR916and the SGSN. A Gn interface is provided between the SGSN920and the GGSN922. A D interface is provided between the MSC/VLR916and the HLR924, and the HLR924and the GMSC918. A Gr interface is provided between the SGSN920and the HLR924. A Gc interface is provided between the GGSN922and the HLR924.

The CN906provides the interface from the UE domain902to external networks926such as the Internet928via a Gi interface from the GGSN922, and other networks930via the GMSC918, which can include a PLMN (public land mobile network), PSTN (public switched telephone network) and ISDN (integrated service digital network) networks.

Asynchronous Transfer Mode (ATM) is defined for UMTS core transmission. ATM Adaptation Layer type 2 (AAL2) handles circuit-switched connection, and packet connection protocol AAL5 is designed for data delivery.

The architecture of the CN906can change when new services and features are introduced. Number Portability Database (NPDB), for example, can be used to enable a user to change the network while keeping their old phone number. A gateway location register (GLR) can be employed to optimize the subscriber handling between network boundaries. Additionally, the MSC/VLR and SGSN can merge to become a UMTS MSC.

Summarizing the UMTS frequencies, 1920-1980 MHz and 2130-2170 MHz are employed for FDD and WCDMA. Paired uplink and downlink channel spacing can be 5 MHz and raster is 200 kHz. An operator can use 3-4 channels (2×15 MHz or 2×20 MHz) to build a high-speed, high-capacity network. Frequencies 1900-1920 MHz and 2010-2025 MHz are for TDD and TD/CDMA. Unpaired channel spacing can be 5 MHz and raster is 200 kHz. Transmit and receive are not separated in frequency. Frequencies 1980-2010 MHz and 2170-2200 MHz are employed for satellite uplink and downlink.

The illustrated aspects of the specification can also be practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

A monitor1044or other type of display device is also connected to the system bus1008via an interface, such as a video adapter1046. In addition to the monitor1044, a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.

When used in a LAN networking environment, the computer1002is connected to the local network1052through a wired and/or wireless communication network interface or adapter1056. The adapter1056can facilitate wired or wireless communication to the LAN1052, which can also include a wireless access point disposed thereon for communicating with the wireless adapter1056.

When used in a WAN networking environment, the computer1002can include a modem1058, or is connected to a communications server on the WAN1054, or has other means for establishing communications over the WAN1054, such as by way of the Internet. The modem1058, which can be internal or external and a wired or wireless device, is connected to the system bus1008via the serial port interface1042. In a networked environment, program modules depicted relative to the computer1002, or portions thereof, can be stored in the remote memory/storage device1050. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.

In the subject specification, terms such as “data store,” data storage,” “database,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components, or computer-readable storage media, described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.