Proactive uplink aggregate maximum bit rate enforcement

A system and method for enforcing uplink aggregate maximum bit rate (AMBR) at a network gateway is provided. In one embodiment, a network gateway may inform one or more network access nodes that are sending data to the network gateway that a total data flow rate on a plurality of bearers from the one or more network access nodes to the network gateway exceeds a first threshold. Responsive to being informed that the total data flow rate exceeds the first threshold, the one or more network access nodes take an action to decrease the data flow rate from a plurality of user equipment that are sending data to the one or more network access nodes.

BACKGROUND

Easily transportable devices with wireless telecommunications capabilities, such as mobile telephones, personal digital assistants, handheld computers, and similar devices, will be referred to herein as user equipment (UE). The term “UE” may refer to a device and its associated Universal Integrated Circuit Card (UICC) that includes a Subscriber Identity Module (SIM) application, a Universal Subscriber Identity Module (USIM) application, or a Removable User Identity Module (R-UIM) application or may refer to the device itself without such a card. The term “UE” may also refer to devices that have similar capabilities but that are not transportable, such as a desktop computer or a set-top box. A connection between a UE and some other element in a telecommunications network might promote a voice call, a file transfer, or some other type of data exchange, any of which can be referred to as a call or a session.

Some UEs communicate in a circuit switched mode, wherein a dedicated communication path exists between two devices. For the duration of a call or session, all data exchanged between the two devices travels along the single path. Some UEs have the capability to communicate in a packet switched mode, wherein a data stream representing a portion of a call or session is divided into packets that are given unique identifiers. The packets might then be transmitted from a source to a destination along different paths and might arrive at the destination at different times. Upon reaching the destination, the packets are reassembled into their original sequence based on the identifiers.

Communications that take place via circuit switching can be said to occur in the circuit switched domain and communications that take place via packet switching can be said to occur in the packet switched domain. Within each domain, several different types of networks, protocols, or technologies can be used. In some cases, the same network, protocol, or technology can be used in both domains. The wireless communication networks may be based on Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiplexing (OFDM), or some other multiple access scheme. A CDMA-based network may implement one or more standards such as 3GPP2 IS-2000 (commonly referred to as CDMA 1x), 3GPP2 IS-856 (commonly referred to as CDMA 1xEV-DO), or 3GPP UMTS (Universal Mobile Telecommunications System). The modes of access for UMTS are referred to as Universal Terrestrial Radio Access (UTRA). A TDMA-based network may implement one or more standards such as 3 GPP Global System for Mobile Communications (GSM) or 3GPP General Packet Radio Service (GPRS).

GSM is an example of a wireless network standard that uses only the circuit switching mode. Examples of wireless network standards that use only packet switching include GPRS, CDMA 1x EV-DO, Worldwide Interoperability for Microwave Access (WiMax), and Wireless Local Area Network (WLAN), which might comply with Institute of Electrical and Electronics Engineers (IEEE) standards such as 802.16, 802.16e, 802.11a, 802.11b, 802.11g, 802.11n, and similar standards. Examples of wireless network standards that may use both circuit switching and packet switching modes include CDMA 1x and UMTS. The IP (Internet Protocol) Multimedia Subsystem (IMS) is a packet switched technology that allows multimedia content to be transmitted between UEs.

In traditional wireless telecommunications systems, transmission equipment in a base station transmits signals throughout a geographical region known as a cell. As technology has evolved, more advanced equipment has been introduced that can provide services that were not possible previously. This advanced equipment might include, for example, an enhanced node B (ENB) rather than a base station or other systems and devices that are more highly evolved than the equivalent equipment in a traditional wireless telecommunications system. Such advanced or next generation equipment may be referred to herein as long-term evolution (LTE) equipment, and a packet-based network that uses such equipment can be referred to as an evolved packet system (EPS).

DETAILED DESCRIPTION

According to one embodiment, a method is provided for enforcing uplink aggregate maximum bit rate (AMBR) at a network gateway. The method comprises sending a data flow rate overflow message to one or more network access nodes when a total data flow rate from the one or more network access nodes to the network gateway exceeds a first threshold related to the AMBR.

In another embodiment, a method is provided for enforcing uplink aggregate maximum bit rate in one or more network access nodes. The method comprises receiving a data flow rate overflow message from a network gateway at one or more of the network access nodes. The method further comprises one or more of the network access nodes taking action to decrease the data flow rate from at least one user equipment that is sending data to the one or more network access nodes.

In another embodiment, a system is provided for preventing a total data flow rate to a single network gateway from exceeding an aggregate maximum bit rate (AMBR) applicable to the network gateway. The system comprises a processor in the network gateway configured to inform one or more network access nodes that are sending data from a plurality of user equipment to the network gateway that the total data flow rate exceeds a first threshold related to the AMBR.

In another embodiment, a system is provided for reducing a total data flow rate to a single network gateway to reduce the likelihood of exceeding an aggregate maximum bit rate applicable to the network gateway. The system comprises a processor related to a network access node configured, responsive to receiving a message from the network gateway that the total data flow rate exceeds a first threshold, to decrease the data flow rate to the network gateway.

FIG. 1illustrates an exemplary wireless telecommunications system100according to an embodiment of the disclosure. It should be noted that some of the lines connecting the components inFIG. 1might represent bearer connections and some of the lines might represent signaling connections. Traditionally, different styles of lines are used to represent the different types of connections. However, for the sake of clarity in the drawing, the different types of connections inFIG. 1are represented by the same style of line. Also, other connections that are not shown might exist between the components inFIG. 1.

The system100includes a UE110that can connect to a packet data network (PDN)160. Although only one UE110and one PDN160are shown, a plurality of UEs110could be present, each of which could connect to a plurality of PDNs160. The PDN160might be an Internet-based network or might be another type of network that can provide packet-based data. The PDN160can allow access to packet-based services, such as World Wide Web pages, multimedia broadcast/multicast services, and other data packet-based services. To access the PDN160, the UE110might establish one or more radio bearer connections115with an ENB120, a base station, or a similar component. While only one ENB120is shown, multiple ENBs120could be present, and multiple UEs110could connect to each of them.

The UE110may connect, via the ENB120, to a serving gateway140, which can also be referred to as a mobile access gateway (MAG). The serving gateway140terminates the user plane interface of the radio access portions of the system100. The UE110may also connect, via the ENB120, to a mobility management entity (MME)130, which then connects to the serving gateway140. The MME130terminates the control plane interface of the radio access portions of the system100.

The serving gateway140forwards packets to the PDN160via a PDN gateway150. While a single PDN gateway150is shown providing access to a single PDN160, a plurality of PDN gateways150might be present, each of which could connect to a plurality of ENBs120, and each of which could provide access to a plurality of PDNs160. The serving gateway140, the PDN gateway150, and the PDN160communicate via one or more core bearers135. There is a one-to-one correspondence between the radio bearers115and the core bearers135. That is, for each connection the UE110has to the PDN gateway150, there is also a connection to the ENB120.

A home subscriber server (HSS)170, an authentication/authorization accounting (AAA) server, or a similar component, can connect to the MME130(and other core network entities) and can store data related to services available to the UE110, billing policies for the UE110, and similar UE profile data. If dynamic policy and charge control (PCC) rules are deployed in the system100, a policy control and charging rules function (PCRF)180, or a similar component, might be present. The PCRF180can connect to the serving gateway140, the PDN gateway150, and/or the PDN160, and can store policies related to the connections between the ENB120and the PDN gateway150.

The UE110might connect to a plurality of PDN gateways150concurrently via the ENB120, the serving gateway140, and a plurality of radio bearer connections115and a plurality of core bearer connections135. This could provide the UE110with fast access to multiple PDNs160. For example, the UE110might use a first radio bearer115and a first core bearer135to connect to a first PDN160in order to access the World Wide Web and use a second radio bearer115and second core bearer135to connect to a second PDN160in order to access a video download. The use of such concurrent bearers could allow the user to quickly switch between the two PDNs160. Based on the UEs' quality of service (QoS) profiles, the radio bearers115and core bearers135might conform to a set of QoS requirements, such as a guaranteed bit rate, a maximum bit rate, a packet delay budget, a packet loss rate, and other parameters of data transfer quality.

Bearer traffic can be classified into two categories: Guaranteed Bit Rate (GBR) and non-Guaranteed Bit Rate (non-GBR). On a GBR bearer, a specified bandwidth is reserved and remains available as long as the bearer remains in place. A GBR bearer might be established for services with strict bandwidth requirements, such as streaming video. Services such as email that have more flexible bandwidth requirements might use non-GBR bearers, for which a specified bandwidth is not reserved.

For non-GBR bearers, QoS can be enforced by a QoS Class Indicator (QCI), an Allocation and Retention Priority (ARP), and an Aggregate Maximum Bit Rate (AMBR). The QCI, ARP, and AMBR are typically stored in the UE's QoS profile. When the UE110attaches to a network, the MME130can retrieve these parameters from the HSS170and send them to the ENB120for QoS enforcement on uplinks and to the PDN gateway150or the PCRF180for QoS enforcement on downlinks. The AMBR can be considered a total bandwidth available to be shared among all the non-GBR radio bearers115between the UE110and the ENB120or among all the non-GBR core bearers135between the UE110and the PDN160. The same AMBR is used by the radio bearers115and the core bearers135.

An AMBR can be defined for one UE110connected to one ENB120and/or one PDN160, for one UE110connected to a plurality of ENBs120and/or a plurality of PDNs160, for a plurality of UEs110connected to one ENB120and/or one PDN160, or for a plurality of UEs110connected to a plurality of ENBs120and/or a plurality of PDNs160. A single UE110can utilize the total AMBR if there is only a single radio bearer115between the UE110and the ENB120or a single core bearer135between the UE110and the PDN160. If the UE110is connected to multiple active radio bearers115or multiple active core bearers135, the bearers share the AMBR. A plurality of bearers might share an AMBR equally or each might receive a different proportion of an AMBR.

FIG. 2illustrates a simplified version of the system100ofFIG. 1. In this example, a first UE1101connects to a first ENB1201via a first non-GBR bearer2101and a second non-GBR bearer2102. A second UE1102connects to the first ENB1201via a third non-GBR bearer2103and a fourth non-GBR bearer2104. A third UE1103connects to a second ENB1202via a fifth non-GBR bearer2105. The first bearer2101, the second bearer2102, and the third bearer2103continue from the first ENB1201to a first PDN gateway1501. The fourth bearer2104continues from the first ENB1201to a second PDN gateway1502. The fifth bearer2105continues from the second ENB1202to the second PDN gateway1502. In other cases, other numbers of these components could be present and the components could be connected in other manners.

In example ofFIG. 2, AMBRs are specified for the bearers210on a per-PDN gateway150basis. That is, the AMBR is the total allowed non-GBR traffic for a single PDN gateway150, and a different AMBR could apply to the total traffic to or from each of the PDN gateways150. For example, a first AMBR2201could apply to data on the bearers2101,2102, and2103connected to the first PDN gateway1501, and a second AMBR2202could apply to data on the bearers2104and2105connected to the second PDN gateway1502. For downlink traffic, the first PDN gateway1501can ensure that the total downlink data flows on bearers2101,2102, and2103do not exceed the first AMBR2201, and the second PDN gateway1502can ensure that the total downlink data flows on bearers2104and2105do not exceed the second AMBR2202.

For uplink traffic, the data flow rates on each of the bearers210are controlled by the ENBs120. A single ENB120can ensure that the total non-GBR data flow rate on one or more bearers210between itself and a single PDN gateway150does not exceed the AMBR applicable to that PDN gateway150. For example, the first ENB1201can ensure that the total uplink data flows on bearers2101,2102, and2103to the first PDN gateway1501do not exceed the first AMBR2201and can also ensure that the uplink data flow on bearer2104to the second PDN gateway1502does not exceed the second AMBR2202. The second ENB1202can ensure that the uplink data flow on bearer2105to the second PDN gateway1502does not exceed the second AMBR2202.

However, neither of the ENBs120has information on non-GBR traffic flow rates from its peer ENB120to the PDN gateways150. One of the ENBs120could send data to one of the PDN gateways150at a flow rate that is a significant portion of the AMBR for that PDN gateway150without being aware that the other ENB120is also sending data to the same PDN gateway150. Therefore, when bearers210from different ENBs120carry data at a relatively high flow rate to a single PDN gateway150, the total data flow on the bearers210could exceed the AMBR for that PDN gateway150.

This is illustrated inFIG. 2by bearers2104and2105from the first ENB1201and the second ENB1202, respectively. The total uplink data flow into the second PDN gateway1502is the combination of the data flows on bearers2104and2105and is limited to the second AMBR2202. However, since the first ENB1201has no knowledge of the data flow on bearer2105from the second ENB1202, and the second ENB1202has no knowledge of the data flow on bearer2104from the first ENB1201, each of the ENBs120might assume that the full second AMBR2202is available to it. This might cause the first ENB1201to attempt to place a data flow up to the second AMBR2202on bearer2104, and might concurrently cause the second ENB1202to attempt to place a data flow up to the second AMBR2202on bearer2105. If the total data flow that the first ENB1201and the second ENB1202concurrently attempt to place on bearers2104and2105exceeds the second AMBR2202, an overflow condition could exist.

In addition, the total data flow that the first ENB1201and the second ENB1202concurrently attempt to place on bearers2104and2105might approach, but not exceed, the second AMBR2202. In such a case, data traffic congestion may limit the available bandwidth at the second PDN gateway1502. Such a condition will be referred to herein as a pseudo-overflow.

An overflow or pseudo-overflow could cause the second PDN gateway1502to drop or delay data packets sent over bearers2104and/or2105. The dropping of packets could lead to a waste of resources since the dropped packets would need to be retransmitted. Currently, the second PDN gateway1502might handle such an overflow or pseudo-overflow using a standard Internet Protocol (IP) flow control mechanism. With such a mechanism, bearers210with high traffic rates will experience larger delays or more packet dropping than bearers210with low traffic rates. As a result, the transport or application layer of one or more of the senders (the second UE1102and the third UE1103in this case) will correspondingly adjust the rate at which the sender sends data. However, the IP flow control-based method may respond slowly to the AMBR overflow or pseudo-overflow at the PDN gateway1502. Moreover, the waste associated with packet retransmission due to packet dropping at the second PDN gateway1502still might not be avoided. Further, significant radio resources may be wasted in this case due to the packet dropping in the core network.

In an embodiment, a proactive uplink AMBR rate enforcement procedure is provided in which the ENBs120can make use of overall system information on non-GBR traffic to prevent uplink traffic from exceeding an AMBR. As result, AMBR overflow or pseudo-overflow issues at the PDN gateways150can be avoided or alleviated. When one of the PDN gateways150receives total non-GBR traffic that exceeds a first threshold, the PDN gateway150sends a message to one or more of the ENBs120from which it is receiving traffic informing the ENBs120that it is receiving excessive traffic. The first threshold might be the AMBR for that PDN gateway150or might be a portion of the AMBR (e.g., 95% of the configured AMBR). The message can be referred to as an “AMBR Overflow Indication (Congestion)” message. In some cases, the PDN gateway150sends the message to all of the ENBs120from which it is receiving traffic, and in some cases, the PDN gateway150sends the message to only one or only a portion of the ENBs120from which it is receiving traffic.

The ENBs120that receive the AMBR Overflow Indication (Congestion) message can then notify the UEs110under their control to decrease the UEs' traffic to the UEs' respective ENBs120. In some embodiments, the ENBs can inform their respective UEs110to slow down the uplink traffic from the UEs110to the ENBs120. In other embodiments, the ENBs120can instruct the UEs110to modify the manner in which the UEs110handle the buffering of uplink traffic to the ENBs120. In still other embodiments, the ENBs120might buffer the data from the UEs110and decrease the forwarding rate of the data to the PDN gateway150. The procedure for adjusting the uplink data flow rate can be implementation-dependent.

As a result of the actions taken by the ENBs120upon receiving the AMBR Overflow Indication (Congestion) messages, the total traffic to the PDN gateway150that was in an overflow or pseudo-overflow condition might decrease. When the non-GBR traffic to one of the PDN gateways150that previously had traffic above the first threshold falls below a second threshold, the overflow or pseudo-overflow condition can be defined to no longer exist on that PDN gateway150. To prevent frequent oscillation between an overflow or pseudo-overflow condition and a non-overflow condition, the second threshold can be set at an appropriate level below the first threshold. For example, if the first threshold is 95% of the AMBR, the second threshold might be set at 90% of the AMBR.

In an embodiment, when an overflow or pseudo-overflow no longer exists on one of the PDN gateways150, the PDN gateway150can send a message to the ENBs120that are sending data to the PDN gateway150. The message, which might be referred to as an “AMBR Overflow Indication (Cleared)” message, can inform the ENBs120that the actions that the ENBs120took to decrease their UEs' traffic to the ENBs120can be terminated. To avoid a “ping-pong” effect, the ENBs120may not increase the UE's traffic immediately after the reception of the “AMBR Overflow Indication (Cleared)” message and may increase the traffic through a slow, step-by-step procedure.

In an alternative embodiment, the PDN gateway150does not send the AMBR Overflow Indication (Cleared) message to the ENBs120. Instead, after a defined period of time has elapsed since the ENBs120received the AMBR Overflow Indication (Congestion) message, the ENBs120can allow the uplink non-GBR traffic from the UEs110to the PUN gateway150to increase in a slow, step-by-step manner. The increase can continue until the AMBR of the PDN gateway150is reached or until the ENBs120receive another AMBR Overflow Indication (Congestion) message from the PDN gateway150.

FIG. 3illustrates an embodiment of a method300for proactive uplink AMBR rate enforcement. At block260, when the total data flow rate on a plurality of bearers from a plurality of ENBs to a single PDN gateway exceeds a threshold, the PDN gateway informs the ENBs of an overflow condition. At block270, upon being informed of the overflow condition, the ENBs take actions to decrease the data flow rate from the UEs that are sending data to the ENBs.

The signaling of the AMBR overflow or pseudo-overflow status from the PDN gateway150to the ENB120can be implemented through a modification of a known procedure for PDN gateway-initiated bearer modification. A call flow diagram for a PDN gateway-initiated bearer modification procedure that includes signaling related to AMBR overflow or pseudo-overflow status is depicted inFIG. 4.

At event301, if dynamic PCC is deployed, the PCRF180sends a PCC Decision Provision message to the PDN gateway150. If dynamic PCC is not deployed, the PDN gateway150may apply local QoS policy. At event302, the PDN gateway150uses the QoS policy to determine that a service data flow is to be aggregated to or removed from an active bearer. The PDN gateway150generates an uplink traffic flow template (TFT) and updates the bearer QoS to match the aggregated set of service data flows. When AMBR overflow or pseudo-overflow occurs, the PDN gateway150sends an Update Bearer Request message containing an AMBR overflow indication to the serving gateway140.

At event303, the serving gateway140sends the Update Bearer Request message with the AMBR overflow indication to the MME130. At event304, the MME130builds a Session Management Configuration that includes the AMBR overflow indication. The MME130then sends a Bearer Modify Request message with the Session Management Configuration to the ENB120.

At event305, the ENB120maps the modified bearer QoS to the radio bearer QoS. The ENB120then sends a Radio Bearer Modify Request message containing the Session Management Configuration to the UE110. The UE110can store the information it receives in the Session Management Configuration for use when accessing via Evolved UTRAN or GERAN or UTRAN. At event306, the UE110acknowledges the radio bearer modification to the ENB120with a Radio Bearer Modify Response (Session Management Response) message. Events305and306are optional since the ENB120is not required to notify the UE110with regard to the AMBR overflow status.

At event307, the ENB120acknowledges the bearer modification to the MME130with a Bearer Modify Response message. With this message, the ENB120indicates whether the requested bearer QoS could be allocated or not. At event308, the MME130acknowledges the bearer modification to the serving gateway140by sending an Update Bearer Response message. At event309, the serving gateway140acknowledges the bearer modification to the PDN gateway150by sending an Update Bearer Response message. At event310, if the bearer modification procedure was triggered by a PCC Decision Provision message from the PCRF180at event301, the PDN gateway150indicates to the PCRF180whether or not the requested PCC decision (QoS policy) could be enforced by sending a Provision Acknowledgement message to the PCRF180. Additional related information is available in 3rdGeneration Partnership Project (3GPP) Technical Specification (TS) 23.401 which is incorporated herein by reference for all purposes.

FIG. 5illustrates a wireless communications system including an embodiment of the UE110. The UE110is operable for implementing aspects of the disclosure, but the disclosure should not be limited to these implementations. Though illustrated as a mobile phone, the UE110may take various forms including a wireless handset, a pager, a personal digital assistant (PDA), a portable computer, a tablet computer, or a laptop computer. Many suitable devices combine some or all of these functions. In some embodiments of the disclosure, the UE110is not a general purpose computing device like a portable, laptop or tablet computer, but rather is a special-purpose communications device such as a mobile phone, a wireless handset, a pager, a PDA, or a telecommunications device installed in a vehicle. In another embodiment, the UE110may be a portable, laptop or other computing device. The UE110may support specialized activities such as gaming, inventory control, job control, and/or task management functions, and so on.

The UE110includes a display402. The UE110also includes a touch-sensitive surface, a keyboard or other input keys generally referred as404for input by a user. The keyboard may be a full or reduced alphanumeric keyboard such as QWERTY, Dvorak, AZERTY, and sequential types, or a traditional numeric keypad with alphabet letters associated with a telephone keypad. The input keys may include a trackwheel, an exit or escape key, a trackball, and other navigational or functional keys, which may be inwardly depressed to provide further input function. The UE110may present options for the user to select, controls for the user to actuate, and/or cursors or other indicators for the user to direct.

The UE110may further accept data entry from the user, including numbers to dial or various parameter values for configuring the operation of the UE110. The UE110may further execute one or more software or firmware applications in response to user commands. These applications may configure the UE110to perform various customized functions in response to user interaction. Additionally, the UE110may be programmed and/or configured over-the-air, for example from a wireless base station, a wireless access point, or a peer UE110.

Among the various applications executable by the UE110are a web browser, which enables the display402to show a web page. The web page may be obtained via wireless communications with a wireless network access node, a cell tower, a peer UE110, or any other wireless communication network or system400. The network400is coupled to a wired network408, such as the Internet. Via the wireless link and the wired network, the UE110has access to information on various servers, such as a server410. The server410may provide content that may be shown on the display402. Alternately, the UE110may access the network400through a peer UE110acting as an intermediary, in a relay type or hop type of connection.

FIG. 6shows a block diagram of the UE110. While a variety of known components of UEs110are depicted, in an embodiment a subset of the listed components and/or additional components not listed may be included in the UE110. The UE110includes a digital signal processor (DSP)502and a memory504. As shown, the UE110may further include an antenna and front end unit506, a radio frequency (RF) transceiver508, an analog baseband processing unit510, a microphone512, an earpiece speaker514, a headset port516, an input/output interface518, a removable memory card520, a universal serial bus (USB) port522, a short range wireless communication sub-system524, an alert526, a keypad528, a liquid crystal display (LCD), which may include a touch sensitive surface530, an LCD controller532, a charge-coupled device (CCD) camera534, a camera controller536, and a global positioning system (GPS) sensor538. In an embodiment, the UE110may include another kind of display that does not provide a touch sensitive screen. In an embodiment, the DSP502may communicate directly with the memory504without passing through the input/output interface518.

The antenna and front end unit506may be provided to convert between wireless signals and electrical signals, enabling the UE110to send and receive information from a cellular network or some other available wireless communications network or from a peer UE110. In an embodiment, the antenna and front end unit506may include multiple antennas to support beam forming and/or multiple input multiple output (MIMO) operations. As is known to those skilled in the art, MIMO operations may provide spatial diversity which can be used to overcome difficult channel conditions and/or increase channel throughput. The antenna and front end unit506may include antenna tuning and/or impedance matching components, RF power amplifiers, and/or low noise amplifiers.

The RF transceiver508provides frequency shifting, converting received RF signals to baseband and converting baseband transmit signals to RF. In some descriptions a radio transceiver or RF transceiver may be understood to include other signal processing functionality such as modulation/demodulation, coding/decoding, interleaving/deinterleaving, spreading/despreading, inverse fast Fourier transforming (IFFT)/fast Fourier transforming (FFT), cyclic prefix appending/removal, and other signal processing functions. For the purposes of clarity, the description here separates the description of this signal processing from the RF and/or radio stage and conceptually allocates that signal processing to the analog baseband processing unit510and/or the DSP502or other central processing unit. In some embodiments, the RF Transceiver508, portions of the Antenna and Front End506, and the analog baseband processing unit510may be combined in one or more processing units and/or application specific integrated circuits (ASICs).

The analog baseband processing unit510may provide various analog processing of inputs and outputs, for example analog processing of inputs from the microphone512and the headset516and outputs to the earpiece514and the headset516. To that end, the analog baseband processing unit510may have ports for connecting to the built-in microphone512and the earpiece speaker514that enable the UE110to be used as a cell phone. The analog baseband processing unit510may further include a port for connecting to a headset or other hands-free microphone and speaker configuration. The analog baseband processing unit510may provide digital-to-analog conversion in one signal direction and analog-to-digital conversion in the opposing signal direction. In some embodiments, at least some of the functionality of the analog baseband processing unit510may be provided by digital processing components, for example by the DSP502or by other central processing units.

The DSP502may communicate with a wireless network via the analog baseband processing unit510. In some embodiments, the communication may provide Internet connectivity, enabling a user to gain access to content on the Internet and to send and receive e-mail or text messages. The input output interface518interconnects the DSP502and various memories and interfaces. The memory504and the removable memory card520may provide software and data to configure the operation of the DSP502. Among the interfaces may be the USB interface522and the short range wireless communication sub-system524. The USB interface522may be used to charge the UE110and may also enable the UE110to function as a peripheral device to exchange information with a personal computer or other computer system. The short range wireless communication sub-system524may include an infrared port, a Bluetooth interface, an IEEE 802.11 compliant wireless interface, or any other short range wireless communication sub-system, which may enable the UE110to communicate wirelessly with other nearby mobile devices and/or wireless base stations.

The input/output interface518may further connect the DSP502to the alert526that, when triggered, causes the UE110to provide a notice to the user, for example, by ringing, playing a melody, or vibrating. The alert526may serve as a mechanism for alerting the user to any of various events such as an incoming call, a new text message, and an appointment reminder by silently vibrating, or by playing a specific pre-assigned melody for a particular caller.

The keypad528couples to the DSP502via the interface518to provide one mechanism for the user to make selections, enter information, and otherwise provide input to the UE110. The keyboard528may be a full or reduced alphanumeric keyboard such as QWERTY, Dvorak, AZERTY and sequential types, or a traditional numeric keypad with alphabet letters associated with a telephone keypad. The input keys may include a trackwheel, an exit or escape key, a trackball, and other navigational or functional keys, which may be inwardly depressed to provide further input function. Another input mechanism may be the LCD530, which may include touch screen capability and also display text and/or graphics to the user. The LCD controller532couples the DSP502to the LCD530.

The CCD camera534, if equipped, enables the UE110to take digital pictures. The DSP502communicates with the CCD camera534via the camera controller536. In another embodiment, a camera operating according to a technology other than Charge Coupled Device cameras may be employed. The GPS sensor538is coupled to the DSP502to decode global positioning system signals, thereby enabling the UE110to determine its position. Various other peripherals may also be included to provide additional functions, e.g., radio and television reception.

FIG. 7illustrates a software environment602that may be implemented by the DSP502. The DSP502executes operating system drivers604that provide a platform from which the rest of the software operates. The operating system drivers604provide drivers for the UE hardware with standardized interfaces that are accessible to application software. The operating system drivers604include application management services (“AMS”)606that transfer control between applications running on the UE110. Also shown inFIG. 7are a web browser application608, a media player application610, and Java applets612. The web browser application608configures the UE110to operate as a web browser, allowing a user to enter information into forms and select links to retrieve and view web pages. The media player application610configures the UE110to retrieve and play audio or audiovisual media. The Java applets612configure the UE110to provide games, utilities, and other functionality. A component614might provide functionality related to AMBR enforcement.

The components ofFIG. 1may include any general-purpose computer with sufficient processing power, memory resources, and network throughput capability to handle the necessary workload placed upon it.FIG. 8illustrates a typical, general-purpose computer system suitable for implementing one or more embodiments disclosed herein. The computer system1300includes a processor1332(which may be referred to as a central processor unit or CPU) that is in communication with memory devices including secondary storage1338, read only memory (ROM)1336, random access memory (RAM)1334, input/output (I/O) devices1340, and network connectivity devices1312. The processor1332may be implemented as one or more CPU chips.

The secondary storage1338is typically comprised of one or more disk drives or tape drives and is used for non-volatile storage of data and as an over-flow data storage device if RAM1334is not large enough to hold all working data. Secondary storage1338may be used to store programs which are loaded into RAM1334when such programs are selected for execution. The ROM1336is used to store instructions and perhaps data which are read during program execution. ROM1336is a non-volatile memory device which typically has a small memory capacity relative to the larger memory capacity of secondary storage. The RAM1334is used to store volatile data and perhaps to store instructions. Access to both ROM1336and RAM1334is typically faster than to secondary storage1338.

The network connectivity devices1312may take the form of modems, modem banks, ethernet cards, universal serial bus (USB) interface cards, serial interfaces, token ring cards, fiber distributed data interface (FDDI) cards, wireless local area network (WLAN) cards, radio transceiver cards such as code division multiple access (CDMA) and/or global system for mobile communications (GSM) radio transceiver cards, and other well-known network devices. These network connectivity devices1312may enable the processor1332to communicate with an Internet or one or more intranets. With such a network connection, it is contemplated that the processor1332might receive information from the network, or might output information to the network in the course of performing the above-described method steps. The network connectivity devices1312may also include one or more transmitter and receivers for wirelessly or otherwise transmitting and receiving signal as are well know to one of ordinary skill in the art.

The processor1332executes instructions, codes, computer programs, scripts which it accesses from hard disk, floppy disk, optical disk (these various disk based systems may all be considered secondary storage1338), ROM1336, RAM1334, or the network connectivity devices1312. While only one processor1332is shown, multiple processors may be present. Thus, while instructions may be discussed as executed by a processor, the instructions may be executed simultaneously, serially, or otherwise executed by one or multiple processors.

The following are incorporated herein by reference for all purposes: 3rdGeneration Partnership Project (3GPP) Technical Specification (TS) 23.401, 3GPP S2-081514, and 3GPP S2-081100.