Dynamic bundling of uplink data sessions based upon network signaling conditions and application interactivity states

Concepts and technologies are described herein for dynamic bundling of uplink data sessions based upon network signaling conditions and application interactivity states. According to one aspect disclosed herein, a mobile device can receive signaling load information from a base station. The mobile device can determine a characteristic of an uplink data flow request. The mobile device can determine whether the uplink data flow request should be bundled based, at least in part, upon the signaling load information and the characteristic of the uplink data flow request.

BACKGROUND

In recent years, mobile telecommunications carriers have experienced a dramatic increase in traffic on their networks, and this trend will likely continue. This increase in traffic has been caused in part by the increased adoption of smartphones and other devices that rely on mobile telecommunications networks, and the migration of many customers from utilizing landline telecommunication services to utilizing mobile telecommunication services for their communications needs. To meet the demands of higher traffic and to improve the end user experience, mobile telecommunications carriers are examining mechanisms by which to improve network efficiency, network capacity, and the end user experience, while keeping operational costs at a level conducive to maintaining competitive rates for the services they provide.

SUMMARY

Concepts and technologies are described herein for dynamic bundling of uplink data sessions based upon network signaling conditions and application interactivity states. According to one aspect disclosed herein, a mobile device can receive signaling load information from a base station. The mobile device can determine a characteristic of an uplink data flow request. The mobile device can determine whether the uplink data flow request should be bundled based, at least in part, upon the signaling load information and the characteristic of the uplink data flow request.

In some embodiments, the mobile device can receive the signaling load information from the base station via a cell broadcast message. The cell broadcast message can include a system information block (“SIB”). The cell broadcast message alternatively can include a short messaging service (“SMS”) message.

In some embodiments, the characteristic of the uplink data flow request includes an interactive characteristic or a non-interactive characteristic. In these embodiments, the mobile device can determine that the uplink data flow request should not be bundled if the characteristic of the uplink data flow request includes an interactive characteristic. The mobile device can determine that the uplink data flow request should be bundled if the characteristic of the uplink data flow request includes a non-interactive characteristic. The mobile device can send, to the base station, the uplink data flow request in an uplink bundle that includes a further uplink data flow request.

In some embodiments, the mobile device can determine whether a cell associated with the base station is congested based upon the signaling load information. If the mobile device determines that the cell associated with the base station is congested based upon the signaling load information, the mobile device can determine whether the uplink data flow request is associated with an interactive application. If the mobile device determines that the uplink data flow request is associated with an interactive application, the mobile device can send the uplink data flow request to the base station. If the mobile device determines that the uplink data flow request is associated with a non-interactive application, the mobile device can send the uplink data flow request to a bundle cache and initiate a bundle timer. If the mobile device determines that the uplink data flow request is associated with a non-interactive application, the mobile device also can determine whether the bundle timer has expired. If the mobile device determines that the bundle timer has expired, the mobile device can reset the bundle timer and can send the uplink data flow request to the base station. If the mobile device determines that the bundle timer has not expired, the mobile device can determine whether a new user request has been received. If the mobile device determines that a new user request has not been received, the mobile device can send, to the base station, an uplink bundle that includes a further uplink data flow request included in the bundle cache to the base station. If the mobile device determines that a new user request has been received, the mobile device can reset the bundle timer and can send the uplink data flow request to the base station.

DETAILED DESCRIPTION

Wireless data traffic has been growing at a very fast pace and the trend is still continuing. Beyond data traffic volume growth, there has been an even more aggressive growth in data signaling load. Among all the signaling messages/procedures on cellular networks, radio access network (“RAN”) signaling procedures have caused the most growth and impact. This is due to complicated radio resource sharing techniques required to conserve resources occupied by various users and services.

The majority of RAN signaling events are for connection setup and state transitions (also known as “channel switching”). Whenever there is data to be sent, a mobile device (also known as user equipment (“UE”), or “handset”) can send a request to a base station requesting resources to handle the data. Once the data payload is sent or received, multiple “inactivity” timers can start at the base station, which controls the admission and channel switching of each mobile device the base station serves, and upon expiration will transition the mobile device from connected mode to idle mode. The transition from connected mode to idle mode constitutes channel switching. To achieve resource efficiency, such timers can be set to short values (cumulatively, approximately 12-16 seconds). For this reason, a mobile device is often quickly moved to an idle state after completion of a current data session (e.g., a download or an upload).

Modern mobile devices, such as smartphones, allow users to download and use many data applications simultaneously. However, each data application can operate independently from a radio network perspective. In today's mobile device design, there is no intelligence to bundle closely spaced data payloads. Small packets, which may be stacked and sent in one single connection, are instead sent individually. As a result, a substantial amount of signaling events are generated, which leads to increased base station processing load, which in turn, might result in decreased performance and perceived network quality.

Concepts and technologies are described herein for dynamic bundling of uplink data sessions based upon network signaling conditions and application interactivity states. According to one aspect disclosed herein, a mobile device utilizes network signaling load information to adaptively and selectively bundle uplink data flow requests.

In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments or examples. Referring now to the drawings, in which like numerals represent like elements throughout the several figures, example aspects of traffic steering across radio access technologies and radio frequencies utilizing cell broadcast messages will be presented.

Referring now toFIG. 1, aspects of an illustrative operating environment100for various concepts disclosed herein will be described. It should be understood that the operating environment100and the various components thereof have been greatly simplified for purposes of discussion. Accordingly, additional or alternative components of the operating environment100can be made available without departing from the embodiments described herein.

The operating environment100shown inFIG. 1includes a mobile device102that is configured to connect to and communicate with one or more radio access networks (“RANs”) for voice and/or data communications between the mobile device102and one or more other mobile devices, computers, servers, networking devices, and/or other networks (not shown). The mobile device102is also configured to receive a cell broadcast message104from one or more RANs. The cell broadcast message104can include information regarding network signaling load conditions of one or more RANs to which the mobile device102is capable of connecting.

In the illustrated example, the mobile device102receives the cell broadcast message104including signaling load information106collected by a base station108that is operating within a cell110of a RAN. As used herein, a “signaling load” refers to a load created by one or more signaling operations between one or more of RANs and the mobile device102via one or more signaling bearers. Moreover, a “signaling load” specifically excludes any traffic load associated with one or more traffic bearers. For example, an LTE RAN base station can monitor and report the utilization of physical uplink and downlink control channels (“PUCCH” and “PDCCH”) according to the percentage of time these resources are idle and available over a specified time interval.

In some embodiments, the signaling load information106includes historic network signaling load information. As used herein, “historic network signaling load information” can include signaling load information obtained based upon network signaling load experienced by the base station108in the past or otherwise in non-real-time. In some embodiments, historic network signaling load information is utilized by the mobile device102to identify one or more network signaling load trends over a specified period of time. This trending network signaling load information can be useful to the mobile device102to predict times during which network signaling load is favorable or not to support communications between the mobile device102and one or more RANs.

In some other embodiments, the signaling load information106includes current network signaling load information. As used herein, “current network signaling load data” can include network signaling load data that is obtained based upon a network signaling load experienced by the base station108in real-time or near real-time. Real-time, in this context, is the actual time during which a network signaling load is experienced by the base station108. Near real-time, in this context, is the actual time during which a network signaling load is experienced by the base station108plus a delay on the order of seconds, minutes, or any order of magnitude thereof, for example.

What constitutes near-real time network signaling load information versus historic network signaling load information can be defined by a service provider that provides service via the base station108. It should be understood that real-time network signaling load information associated with a real-time network signaling load of the base station108, and near real-time network signaling load information associated with a near real-time network signaling load of the base station108might be received by the mobile device102with delay caused by latency and/or other network phenomena. Moreover, this delay may increase with the additional time needed to generate the cell broadcast message104including the signaling load information106, and to send the cell broadcast message104to the mobile device102.

As used herein, a “cell” refers to a geographical area that is served by one or more base stations operating within a RAN. As used herein, a “base station” refers to a radio receiver and/or transmitter (collectively, transceiver) that is/are configured to provide a radio/air interface by which one or more mobile devices, such as the mobile device102, can connect to a network. Accordingly, a base station is intended to encompass one or more base transceiver stations (“BTSs”), one or more Node Bs, one or more eNodeBs, and/or other networking nodes that are capable of providing a radio/air interface regardless of the technologies utilized to do so. A base station can be in communication with one or more antennas (not shown), each of which may be configured in accordance with any antenna design specifications to provide a physical interface for receiving and transmitting radio waves to/from a network.

The mobile device102may be a cellular phone, a feature phone, a smartphone, a mobile computing device, a tablet computing device, a portable television, a portable video game console, or any other computing device that is configured to connect to and communicate with one or more RANs via one or more radio access components112. In some embodiments, the mobile device102includes an integrated or external radio access component that facilitates wireless communication with one or more RANs. The radio access component may be a cellular telephone that is in wired or wireless communication with the mobile device102to facilitate a tethered data connection to one or more RANs. Alternatively, the access component includes a wireless transceiver configured to send data to and receive data from one or more RANs and a universal serial bus (“USB”) or another communication interface for connection to the mobile device102so as to enable tethering. In any case, the mobile device102can wirelessly communicate with one or more RANs over a radio/air interface in accordance with one or more radio access technologies (“RATs”). The mobile device102may also initiate, receive, and/or maintain voice calls with one or more other voice-enabled telecommunications devices such as other mobile devices or landline devices (not shown). The mobile device102may also exchange Short Message Service (“SMS”) messages, Multimedia Message Service (“MMS”) messages, email, and/or other messages with other devices (not shown).

As used herein, a RAN may operate in accordance with one or more mobile telecommunications standards including, but not limited to, Global System for Mobile communications (“GSM”), Code Division Multiple Access (“CDMA”) ONE, CDMA2000, Universal Mobile Telecommunications System (“UMTS”), Long-Term Evolution (“LTE”), Worldwide Interoperability for Microwave Access (“WiMAX”), other 802.XX technologies, and/or the like. A RAN can utilize various channel access methods (which may or may not be used by the aforementioned standards) including, but not limited to, Time Division Multiple Access (“TDMA”), Frequency Division Multiple Access (“FDMA”), Single Carrier FDMA (“SC-FDMA”), CDMA, wideband CDMA (“W-CDMA”), Orthogonal Frequency Division Multiplexing (“OFDM”), Space Division Multiple Access (“SDMA”), and/or the like to provide a radio/air interface to the mobile device102. Data communications can be provided in part by a RAN using General Packet Radio Service (“GPRS”), Enhanced Data rates for Global Evolution (“EDGE”), the High-Speed Packet Access (“HSPA”) protocol family including High-Speed Downlink Packet Access (“HSDPA”), Enhanced Uplink (“EUL”) or otherwise termed High-Speed Uplink Packet Access (“HSUPA”), Evolved HSPA (“HSPA+”), LTE, and/or various other current and future wireless data access technologies. Moreover, a RAN may be a GSM RAN (“GRAN”), a GSM EDGE RAN (“GERAN”), a UMTS Terrestrial Radio Access Network (“UTRAN”), an E-UTRAN, any combination thereof, and/or the like.

A RAN can be part of one or more mobile telecommunications networks. As used herein, a mobile telecommunications network includes one or more RANs and a wireless wide area network (“WWAN”), which may, in turn, include one or more core networks such as a circuit-switched core network (“CS CN”), a packet-switched core network (“PS CN”), and/or an IP multimedia subsystem (“IMS”) core network. The WWAN can utilize one or more mobile telecommunications technologies, such as those described above, to provide voice and/or data services via one or more RANs to one or more radio components of one or more mobile devices, such as the radio access component(s)112of mobile device102. Moreover, a mobile telecommunications network can provide a connection to an internet or other WAN so that the mobile device102can access internet content such as websites, streaming media, online video games, downloadable content, and the like.

As mentioned above, the cell110may be part of the same RAN or any number of different RANs. In some instances, the mobile device102is capable of simultaneous connection to the cell110. As such, in some embodiments, the mobile device102is a multi-mode device. The cell110can be any shape and can have any dimensions. Thus, the illustrated embodiment should be understood as being illustrative, and should not be construed as being limiting in any way.

The cell broadcast message104can include any message that is capable of being sent to the mobile device102from a base station over a radio/air interface. The cell broadcast message104can be sent to the mobile device102using any physical, transport, and/or logical channels. These channel types are generally known and therefore are not described in greater detail herein.

In some embodiments, the cell broadcast message104is or includes a System Information Block (“SIB”). In some other embodiments, the cell broadcast message104is included in a SIB that contains other information. The SIB may be a new SIB configured to include signaling load information such as the signaling load information106. Alternatively, the SIB may be an existing SIB that has been modified to include signaling load information.

In some embodiments, the cell broadcast message104is an SMS message. In these embodiments, the base station108can send the cell broadcast message104to the mobile device102, and potentially to one or more other mobile devices that are connected to the base station108or otherwise operating within the cell110, via SMS Cell Broadcast (“SMS-CB”). Alternatively, in these embodiments, the base station108can send the cell broadcast message104to the mobile device102via SMS Peer-to-Peer (“SMPP”). The cell broadcast message104may be sent to the mobile device102via other messaging services including, but not limited to, MMS, Wireless Application Protocol (“WAP”) push message, Unstructured Supplementary Service Data (“USSD”), or any combination thereof. It should be understood that network elements, such as Short Message Service Centers (“SMSCs”), Multimedia Message Service Centers (“MMSCs”), WAP servers, USSD servers, and the like, that support the aforementioned messaging services are not illustrated merely for ease of description, however, these and/or other network elements can be utilized to support the aforementioned delivery methods of the cell broadcast message104. In the illustrated example, the mobile device102receives the cell broadcast message104from the base station108. Alternatively or additionally, the mobile device102can receive one or more cell broadcast messages from any number of base stations (other base stations not illustrated).

The illustrated mobile device102also includes an operating system114, one or more applications116, an application monitoring engine118, and a selective bundling decision engine120. The operating system114is a program for controlling the operation of the mobile device102. The operating system114can include a member of the SYMBIAN OS family of operating systems from SYMBIAN LIMITED, a member of the WINDOWS MOBILE OS and/or WINDOWS PHONE OS families of operating systems from MICROSOFT CORPORATION, a member of the PALM WEBOS family of operating systems from HEWLETT PACKARD CORPORATION, a member of the BLACKBERRY OS family of operating systems from RESEARCH IN MOTION LIMITED, a member of the IOS family of operating systems from APPLE INC., a member of the ANDROID OS family of operating systems from GOOGLE INC., and/or other operating systems. These operating systems are merely illustrative of some contemplated operating systems that may be used in accordance with various embodiments of the concepts and technologies described herein and therefore should not be construed as being limiting in any way.

The application(s)116can execute on top of the operating system114. The application(s)116can include, for example, one or more presence applications, one or more visual voice mail applications, one or more messaging applications, one or more text-to-speech and/or speech-to-text applications, one or more add-ons, one or more plug-ins, one or more email applications, one or more music applications, one or more video applications, one or more camera applications, one or more location-based service applications, one or more power conservation applications, one or more game applications, one or more productivity applications, one or more entertainment applications, one or more enterprise applications, any other application that is capable of uploading data packets to the base station108, combinations thereof, and the like.

The application monitoring engine118monitors operations performed, at least in part, by the application(s)116to determine characteristics of data sessions created by or otherwise utilized by the application(s)116. In other words, the application monitoring engine118can determine whether the application(s)116exhibit interactive or non-interactive characteristics. The application monitoring engine118can monitor user input to and uplink data flow requests by the application(s)116. The application monitoring engine118can categorize an uplink data flow request according to a level of interactivity considering the user input(s) that preceded the data flow request. For example, if an uplink data flow request closely follows user input (e.g., <100 milliseconds after the user input), then the application monitoring engine118can determine the uplink data flow request to be interactive. If, for example, audio and/or video playback by one or more of the application(s)116is in progress, then the application monitoring engine118can determine the uplink data flow request to be interactive. If, for example, an uplink data flow request does not closely follow user input (e.g., >100 milliseconds after the user input) or the uplink data flow request does not include audio and/or video playback, then the application monitoring engine118can determine the uplink data flow request to be non-interactive.

An application can be considered “interactive” if, for example, a user has requested something via the application and the user is waiting for a response from the application. An application can be considered “interactive” if, for example, an uplink request is associated/correlated with an input user interface activity (e.g., in-hand sensing, touchscreen or microphone input) and an output user interface (e.g., display or speaker) is in a “ready for output” state like display or speaker on.

An application can be considered “non-interactive” if, for example, the application has requested something autonomously without any user input or user awareness. The uplink request is associated/correlated with a mechanized activity (e.g. email synch request, location report, and/or the like when the mobile device102is not in-hand) and the output user interface (e.g., display or speaker) is in a “dormant” state like display off or speaker off. In this case, the user is not aware of or waiting for data so the request can be bundled.

In some embodiments, the application monitoring engine118can categorize uplink data flow request based, at least in part, upon the type of application that generated the data flow request. The application type can be defined by policy or pre-configured rules. For example, uplink data flow requests generated by a voice application can be categorized as interactive, whereas uplink data flow requests generated by a web browser can be categorized as non-interactive. It should be understood that the application monitoring engine118can categorize an uplink data flow request based upon other interactive and non-interactive characteristics, historic categorization, policies, rules, and the like.

The selective bundling decision engine120can receive uplink data flow requests and associated categorizations from the application monitoring engine118. The selective bundling decision engine120can determine whether the uplink data flow requests should be bundled in an uplink bundle122. The selective bundling decision engine120can bundle two or more data flow requests when the signaling load information106included in the cell broadcast message104indicates that the network signaling load of the RAN associated with the base station108is congested. The selective bundling decision engine120can bundle uplink data flow requests that are categorized as non-interactive, and can provide the uplink bundle122that includes two or more bundled uplink data flow requests to the base station108.

For non-interactive applications, the time between user input and the start of data flow is an indication that the user is not interacting with the mobile device102, the user is not waiting for data, and the user is not likely to provide further input. In this case, the selective bundling decision engine120can withhold uplink data flow requests for a pre-defined time period, which is monitored by a bundling timer, to allow other uplink data flow requests to stack up in a queue. In some embodiments, the selective bundling decision engine120can bundle uplink data flow request based upon Quality of Service (“QoS”) and/or Class of Service (“CoS”) parameters. The bundling timer can be adjusted according to network signaling load conditions. The bundling timer can be set per QoS/CoS or a group of QoS/CoS parameters. Additional details regarding operations of the selective bundling decision engine120are described below with reference toFIG. 3.

It should be understood that some implementations of the operating environment100may include additional functionality or include less functionality than described above. Thus, the illustrated embodiment should be understood as being illustrative, and should not be construed as being limiting in any way.

Turning now toFIG. 2, a flow diagram illustrating aspects of a method200for dynamic bundling of uplink data sessions based upon network signaling conditions and application interactivity states will be described, according to an illustrative embodiment. It should be understood that the operations of the illustrative methods disclosed herein are not necessarily presented in any particular order and that performance of some or all of the operations in an alternative order(s) is possible and is contemplated. The operations have been presented in the demonstrated order for ease of description and illustration. Operations may be combined, separated, added, omitted, modified, and/or performed simultaneously or in another order without departing from the scope of the subject disclosure.

The method200includes operations performed by the base station108and the mobile device102. The method200is described with additional reference toFIG. 1. The method200begins and proceeds to operation202, where the base station108collects the signaling load information106. The signaling load information106can include signaling utilization information associated with the utilization of signaling resources available to the base station108. In some embodiments, the base station108collects signaling utilization information, and then calculates a composite signaling load level of the base station108for inclusion in the cell broadcast message104. A composite signaling load level can be calculated utilizing any signaling load calculation method, which, for example, may be selected by or for a service provider operating the base station108based upon the needs of the service provider.

From operation202, the method200proceeds to operation204, where the base station108generates the cell broadcast message104including at least a portion of the signaling load information106collected at operation202. From operation204, the method200proceeds to operation206, where the base station108sends the cell broadcast message104to one or more mobile devices, including the mobile device102.

From operation206, the method200proceeds to operation208, where the mobile device102receives the cell broadcast message104from the base station108. From operation208, the method200proceeds to operation210, where the mobile device102executes, via one or more processors (best shown inFIG. 5), the application monitoring engine118to monitor one or more of the applications116and to determine characteristics of one or more uplink data flow requests performed by the application(s)116.

From operation210, the method200proceeds to operation212, where the mobile device102executes, via one or more processors, the selective bundling decision engine120to determine whether two or more of the uplink data flow requests for which the application monitoring engine118determined, at operation210, characteristics should be bundled. The method300described below with reference toFIG. 3provides example operations that can be performed by the selecting bundling decision engine120at operation212. From operation212, the method200proceeds to operation214, where the method200may end.

Turning now toFIG. 3, a flow diagram illustrating aspects of a method300for dynamic bundling of uplink data sessions based upon network signaling conditions and application interactivity states will be described, according to an illustrative embodiment. The method300is described from the perspective of the mobile device102executing, via one or more processors, the selective bundling decision engine120. As such, the method300is described with additional reference toFIG. 1.

The method300begins and proceeds to operation302, where the mobile device102receives an uplink data flow request from one of the applications116. From operation302, the method300proceeds to operation304, where the mobile device102determines, based upon the signaling load information106included in the cell broadcast message104, whether the cell110is congested. If the mobile device102determines that the cell110is not congested, the method300proceeds to operation306. At operation306, the mobile device102sends the uplink data flow request to the base station108. From operation306, the method300proceeds to operation308, where the method300may end.

If, however, the mobile device102determines, at operation304, that the cell110is congested, the method300proceeds to operation310, where the mobile device102determines whether the application that provided the uplink data flow request is interactive. If the mobile device102determines that the application is interactive, the method300proceeds to operation306. At operation306, the mobile device102sends the uplink data flow request to the base station108. From operation306, the method300proceeds to operation308, where the method300may end. If, however, the mobile device102determines, at operation310, that the application is not interactive, the method300proceeds to operation312. At operation312, the mobile device102sends the uplink data flow request to a bundle cache. Also at operation312, the mobile device102initiates a bundle timer for the bundle cache.

From operation312, the method300proceeds to operation314, where the mobile device102determines whether the bundle timer has expired. If the mobile device102determines that the bundle timer has expired, the method300proceeds to operation316. At operation316, the mobile device102resets the bundle timer. From operation316, the method300proceeds to operation306, where the mobile device102sends the uplink data flow request to the base station108. From operation306, the method300proceeds to operation308, where the method300may end.

If, however, the mobile device102determines, at operation314, that the bundle timer has not expired, the method300proceeds to operation318. At operation318, the mobile device102determines whether a new user request has been received. In some embodiments, the new user request can include any input provided by a user. In some other embodiments, one or more types of user requests can be flagged for resetting the bundle timer. In these embodiments, if a new user request is received but the new user request is not one of the flagged user request types, then the method300can proceed as if no new user request has been received. If the mobile device102determines, at operation318, that a new user request has been received, the method300proceeds to operation316. At operation316, the mobile device102resets the bundle timer. From operation316, the method300proceeds to operation306, where the mobile device102sends the uplink data flow request to the base station108. From operation306, the method300proceeds to operation308, where the method300may end.

If, however, the mobile device102determines, at operation318, that a new user request has not been received, the method300proceeds to operation320. At operation320, the mobile device102sends the uplink bundle122, including the uplink data flow request and any additional uplink data flow requests available in the bundle cache, to the base station108. From operation320, the method300proceeds to operation308, where the method300may end.

FIG. 4is a block diagram illustrating a computer system400configured to provide the functionality in accordance with various embodiments of the concepts and technologies disclosed herein. In some implementations, the mobile device102and/or the base station108can utilize an architecture that is the same as or similar to the architecture of the computer system400. It should be understood, however, that modification to the architecture may be made to facilitate certain interactions among elements described herein.

The computer system400includes a processing unit402, a memory404, one or more user interface devices406, one or more input/output (“I/O”) devices408, and one or more network devices410, each of which is operatively connected to a system bus412. The bus412enables bi-directional communication between the processing unit402, the memory404, the user interface devices406, the I/O devices408, and the network devices410.

The processing unit402may be a standard central processor that performs arithmetic and logical operations, a more specific purpose programmable logic controller (“PLC”), a programmable gate array, a system-on-a-chip, or other type of processor known to those skilled in the art and suitable for controlling the operation of the server computer. Processing units are generally known, and therefore are not described in further detail herein.

The memory404communicates with the processing unit402via the system bus412. In some embodiments, the memory404is operatively connected to a memory controller (not shown) that enables communication with the processing unit402via the system bus412. The memory404includes an operating system414and one or more program modules416. The operating system414can include, but is not limited to, members of the WINDOWS, WINDOWS CE, and/or WINDOWS MOBILE families of operating systems from MICROSOFT CORPORATION, the LINUX family of operating systems, the SYMBIAN family of operating systems from SYMBIAN LIMITED, the BREW family of operating systems from QUALCOMM CORPORATION, the MAC OS, iOS, and/or LEOPARD families of operating systems from APPLE CORPORATION, the FREEBSD family of operating systems, the SOLARIS family of operating systems from ORACLE CORPORATION, other operating systems, and the like.

The program modules416may include various software and/or program modules to perform the various operations described herein. The program modules416can include the application(s)116, the application monitoring engine118, and/or the selective bundling decision engine120in embodiments that the mobile device102is configured like the computer system400. The program modules416and/or other programs can be embodied in computer-readable media containing instructions that, when executed by the processing unit402, perform one or more of the methods200,300, or at least a portion thereof, described in detail above with respect toFIGS. 2 and 3. According to embodiments, the program modules416may be embodied in hardware, software, firmware, or any combination thereof. Although not shown inFIG. 4, it should be understood that the memory404also can be configured to store the cell broadcast message104, the signaling load information106, one or more bundle caches, the uplink bundle122, and/or other data, if desired.

The user interface devices406may include one or more devices with which a user accesses the computer system400. The user interface devices406may include, but are not limited to, computers, servers, personal digital assistants, cellular phones, or any suitable computing devices. The I/O devices408enable a user to interface with the program modules416. In one embodiment, the I/O devices408are operatively connected to an I/O controller (not shown) that enables communication with the processing unit402via the system bus412. The I/O devices408may include one or more input devices, such as, but not limited to, a keyboard, a mouse, or an electronic stylus. Further, the I/O devices408may include one or more output devices, such as, but not limited to, a display screen or a printer.

The network devices410enable the computer system400to communicate with other networks or remote systems via a network418, which can include at least one base station such as the base station108and at least one cell such as the cell110. Examples of the network devices410include, but are not limited to, a modem, a radio frequency (“RF”) or infrared (“IR”) transceiver, a telephonic interface, a bridge, a router, or a network card. The network418may include a wireless network such as, but not limited to, a wireless local area network (“WLAN”), a wireless wide area network (“WWAN”), a wireless personal area network (“WPAN”) such as provided via BLUETOOTH technology, a wireless metropolitan area network (“WMAN”) such as a WiMAX network or metropolitan cellular network. Alternatively, the network418may be a wired network such as, but not limited to, a wide area network (“WAN”), a wired LAN such as provided via Ethernet, a wired personal area network n (“PAN”), or a wired metropolitan area network (“MAN”).

Turning now toFIG. 5, an illustrative mobile device500and components thereof will be described. In some embodiments, the mobile device102described above with reference toFIG. 1can be configured as and/or can have an architecture similar or identical to the mobile device500described herein inFIG. 5. It should be understood, however, that the mobile device102may or may not include the functionality described herein with reference toFIG. 5. While connections are not shown between the various components illustrated inFIG. 5, it should be understood that some, none, or all of the components illustrated inFIG. 5can be configured to interact with one other to carry out various device functions. In some embodiments, the components are arranged so as to communicate via one or more busses (not shown). Thus, it should be understood thatFIG. 5and the following description are intended to provide a general understanding of a suitable environment in which various aspects of embodiments can be implemented, and should not be construed as being limiting in any way.

As illustrated inFIG. 5, the mobile device500can include a display502for displaying data. According to various embodiments, the display502can be configured to display various graphical user interface (“GUI”) elements, text, images, video, advertisements, prompts, virtual keypads and/or keyboards, messaging data, notification messages, metadata, internet content, device status, time, date, calendar data, device preferences, map and location data, combinations thereof, and the like. The mobile device500also can include a processor504and a memory or other data storage device (“memory”)506. The processor504can be configured to process data and/or can execute computer-executable instructions stored in the memory506. The computer-executable instructions executed by the processor504can include, for example, an operating system508(e.g., the operating system114), one or more applications510(e.g., the application(s)116, the application monitoring engine118, and the selective bundling decision engine120), other computer-executable instructions stored in a memory506, or the like. In some embodiments, the applications510also can include a UI application (not illustrated inFIG. 5).

The UI application can be executed by the processor504to aid a user in entering content, viewing account information, answering/initiating calls, entering/deleting data, entering and setting user IDs and passwords for device access, configuring settings, manipulating address book content and/or settings, multimode interaction, interacting with other applications510, and otherwise facilitating user interaction with the operating system508, the applications510, and/or other types or instances of data512that can be stored at the mobile device500. The data512can include, for example, the cell broadcast message104, the signaling load information106, one or more bundle caches, the uplink bundle122, and/or other data, if desired.

According to various embodiments, the applications510can include, for example, presence applications, visual voice mail applications, messaging applications, text-to-speech and speech-to-text applications, add-ons, plug-ins, email applications, music applications, video applications, camera applications, location-based service applications, power conservation applications, game applications, productivity applications, entertainment applications, enterprise applications, combinations thereof, and the like. The applications510, the data512, and/or portions thereof can be stored in the memory506and/or in a firmware514, and can be executed by the processor504. The firmware514also can store code for execution during device power up and power down operations. It can be appreciated that the firmware514can be stored in a volatile or non-volatile data storage device including, but not limited to, the memory506and/or a portion thereof.

The mobile device500also can include an input/output (“I/O”) interface516. The I/O interface516can be configured to support the input/output of data such as location information, user information, organization information, presence status information, user IDs, passwords, and application initiation (start-up) requests. In some embodiments, the I/O interface516can include a hardwire connection such as USB port, a mini-USB port, a micro-USB port, an audio jack, a PS2 port, an IEEE 1394 (“FIREWIRE”) port, a serial port, a parallel port, an Ethernet (RJ45) port, an RJ11 port, a proprietary port, combinations thereof, or the like. In some embodiments, the mobile device500can be configured to synchronize with another device to transfer content to and/or from the mobile device500. In some embodiments, the mobile device500can be configured to receive updates to one or more of the applications510via the I/O interface516, though this is not necessarily the case. In some embodiments, the I/O interface516accepts I/O devices such as keyboards, keypads, mice, interface tethers, printers, plotters, external storage, touch/multi-touch screens, touch pads, trackballs, joysticks, microphones, remote control devices, displays, projectors, medical equipment (e.g., stethoscopes, heart monitors, and other health metric monitors), modems, routers, external power sources, docking stations, combinations thereof, and the like. It should be appreciated that the I/O interface516may be used for communications between the mobile device500and a network device or local device.

The mobile device500also can include a communications component518. The communications component518can be configured to interface with the processor504to facilitate wired and/or wireless communications with one or more networks described above herein. In some embodiments, other networks include networks that utilize non-cellular wireless technologies such as WI-FI or WIMAX. In some embodiments, the communications component518includes a multimode communications subsystem for facilitating communications via the cellular network and one or more other networks.

The communications component518, in some embodiments, includes one or more transceivers. The one or more transceivers, if included, can be configured to communicate over the same and/or different wireless technology standards with respect to one another. For example, in some embodiments one or more of the transceivers of the communications component518may be configured to communicate using GSM, CDMA, CDMAONE, CDMA2000, LTE, and various other 2G, 2.5G, 3G, 4G, and greater generation technology standards. Moreover, the communications component518may facilitate communications over various channel access methods (which may or may not be used by the aforementioned standards) including, but not limited to, TDMA, FDMA, W-CDMA, OFDM, SDMA, and the like.

In addition, the communications component518may facilitate data communications using GPRS, EDGE, the HSPA protocol family, including HSDPA, EUL, or otherwise termed HSUPA, HSPA+, and various other current and future wireless data access standards. In the illustrated embodiment, the communications component518can include a first transceiver (“TxRx”)520A that can operate in a first communications mode (e.g., GSM). The communications component518also can include an Nthtransceiver (“TxRx”)520N that can operate in a second communications mode relative to the first transceiver520A (e.g., UMTS). While two transceivers520A-N (hereinafter collectively and/or generically referred to as “transceivers520”) are shown inFIG. 5, it should be appreciated that less than two, two, and/or more than two transceivers520can be included in the communications component518.

The communications component518also can include an alternative transceiver (“Alt TxRx”)522for supporting other types and/or standards of communications. According to various contemplated embodiments, the alternative transceiver522can communicate using various communications technologies such as, for example, WI-FI, WIMAX, BLUETOOTH, infrared, infrared data association (“IRDA”), NFC, other RF technologies, combinations thereof, and the like.

In some embodiments, the communications component518also can facilitate reception from terrestrial radio networks, digital satellite radio networks, internet-based radio service networks, combinations thereof, and the like. The communications component518can process data from a network such as the Internet, an intranet, a broadband network, a WI-FI hotspot, an Internet service provider (“ISP”), a digital subscriber line (“DSL”) provider, a broadband provider, combinations thereof, or the like.

The mobile device500also can include one or more sensors524. The sensors524can include temperature sensors, light sensors, air quality sensors, movement sensors, orientation sensors, noise sensors, proximity sensors, or the like. As such, it should be understood that the sensors524can include, but are not limited to, accelerometers, magnetometers, gyroscopes, infrared sensors, noise sensors, microphones, combinations thereof, or the like. Additionally, audio capabilities for the mobile device500may be provided by an audio I/O component526. The audio I/O component526of the mobile device500can include one or more speakers for the output of audio signals, one or more microphones for the collection and/or input of audio signals, and/or other audio input and/or output devices.

The illustrated mobile device500also can include a subscriber identity module (“SIM”) system528. The SIM system528can include a universal SIM (“USIM”), a universal integrated circuit card (“UICC”) and/or other identity devices. The SIM system528can include and/or can be connected to or inserted into an interface such as a slot interface530. In some embodiments, the slot interface530can be configured to accept insertion of other identity cards or modules for accessing various types of networks. Additionally, or alternatively, the slot interface530can be configured to accept multiple subscriber identity cards. Because other devices and/or modules for identifying users and/or the mobile device500are contemplated, it should be understood that these embodiments are illustrative, and should not be construed as being limiting in any way.

The mobile device500also can include an image capture and processing system532(“image system”). The image system532can be configured to capture or otherwise obtain photos, videos, and/or other visual information. As such, the image system532can include cameras, lenses, charge-coupled devices (“CCDs”), combinations thereof, or the like. The mobile device500may also include a video system534. The video system534can be configured to capture, process, record, modify, and/or store video content. Photos and videos obtained using the image system532and the video system534, respectively, may be added as message content to an MMS message, email message, and sent to another mobile device. The video and/or photo content also can be shared with other devices via various types of data transfers via wired and/or wireless communication devices as described herein.

The mobile device500also can include one or more location components536. The location components536can be configured to send and/or receive signals to determine a geographic location of the mobile device500. According to various embodiments, the location components536can send and/or receive signals from GPS devices, A-GPS devices, WI-FI/WIMAX and/or cellular network triangulation data, combinations thereof, and the like. The location component536also can be configured to communicate with the communications component518to retrieve triangulation data for determining a location of the mobile device500. In some embodiments, the location component536can interface with cellular network nodes, telephone lines, satellites, location transmitters and/or beacons, wireless network transmitters and receivers, combinations thereof, and the like. In some embodiments, the location component536can include and/or can communicate with one or more of the sensors524such as a compass, an accelerometer, and/or a gyroscope to determine the orientation of the mobile device500. Using the location component536, the mobile device500can generate and/or receive data to identify its geographic location, or to transmit data used by other devices to determine the location of the mobile device500. The location component536may include multiple components for determining the location and/or orientation of the mobile device500.

The illustrated mobile device500also can include a power source538. The power source538can include one or more batteries, power supplies, power cells, and/or other power subsystems including alternating current (“AC”) and/or direct current (“DC”) power devices. The power source538also can interface with an external power system or charging equipment via a power I/O component540. Because the mobile device500can include additional and/or alternative components, the above embodiment should be understood as being illustrative of one possible operating environment for various embodiments of the concepts and technologies described herein. The described embodiment of the mobile device500is illustrative, and should not be construed as being limiting in any way.

Turning now toFIG. 6, additional details of a network600are illustrated, according to an illustrative embodiment. The network600includes a cellular network602, a packet data network604, for example, the Internet, and a circuit switched network606, for example, a publicly switched telephone network (“PSTN”). The cellular network602includes various components such as, but not limited to, BTSs, Node-B's or e-Node-B's, base station controllers (“BSCs”), radio network controllers (“RNCs”), mobile switching centers (“MSCs”), mobile management entities (“MMEs”), short message service centers (“SMSCs”), multimedia messaging service centers (“MMSCs”), home location registers (“HLRs”), home subscriber servers (“HSSs”), visitor location registers (“VLRs”), charging platforms, billing platforms, voicemail platforms, GPRS core network components, location service nodes, an IP Multimedia Subsystem (“IMS”), and the like. The cellular network602also includes radios and nodes for receiving and transmitting voice, data, and combinations thereof to and from radio transceivers, networks, the packet data network604, and the circuit switched network606. In some embodiments, the cellular network602includes the base station108and the cell110.

A mobile communications device608, such as, for example, a cellular telephone, a user equipment, a mobile terminal, a PDA, a laptop computer, a handheld computer, the mobile device102, and combinations thereof, can be operatively connected to the cellular network602. The cellular network602can be configured as a 2G GSM network and can provide data communications via GPRS and/or EDGE. Additionally, or alternatively, the cellular network602can be configured as a 3G UMTS network and can provide data communications via the HSPA protocol family, for example, HSDPA, EUL (also referred to as HSUPA), and HSPA+. The cellular network602also is compatible with 4G mobile communications standards such as LTE, or the like, as well as evolved and future mobile standards.

The packet data network604includes various devices, for example, servers, computers, databases, and other devices in communication with one another, as is generally known. The packet data network604devices are accessible via one or more network links. The servers often store various files that are provided to a requesting device such as, for example, a computer, a terminal, a smartphone, or the like. Typically, the requesting device includes software (a “browser”) for executing a web page in a format readable by the browser or other software. Other files and/or data may be accessible via “links” in the retrieved files, as is generally known. In some embodiments, the packet data network604includes or is in communication with the Internet. The circuit switched network606includes various hardware and software for providing circuit switched communications. The circuit switched network606may include, or may be, what is often referred to as a plain old telephone system (POTS). The functionality of a circuit switched network606or other circuit-switched network are generally known and will not be described herein in detail.

The illustrated cellular network602is shown in communication with the packet data network604and a circuit switched network606, though it should be appreciated that this is not necessarily the case. One or more Internet-capable devices610, for example, the mobile device102, a PC, a laptop, a portable device, or another suitable device, can communicate with one or more cellular networks602, and devices connected thereto, through the packet data network604. It also should be appreciated that the Internet-capable device610can communicate with the packet data network604through the circuit switched network606, the cellular network602, and/or via other networks (not illustrated).

As illustrated, a communications device612, for example, a telephone, facsimile machine, modem, computer, the mobile device102, or the like, can be in communication with the circuit switched network606, and therethrough to the packet data network604and/or the cellular network602. It should be appreciated that the communications device612can be an Internet-capable device, and can be substantially similar to the Internet-capable device610. In the specification, the network600is used to refer broadly to any combination of the networks602,604,606. It should be appreciated that substantially all of the functionality described with reference to the network600can be performed by the cellular network602, the packet data network604, and/or the circuit switched network606, alone or in combination with other networks, network elements, and the like.