Adaptive and selective bundling of downlink paging messages

Concepts and technologies are described herein for adaptive and selective bundling of downlink paging messages. According to one aspect disclosed herein, a mobility management entity (“MME”) can determine whether to delay a paging procedure to deliver a downlink paging message to a mobile device served by the MME. If the MME determines that the paging procedure to deliver the downlink paging message to the mobile device should be delayed, then the MME can store the downlink paging message in a bundling cache. If the MME determines that the paging procedure to deliver the downlink paging message to the mobile device should not be delayed, then the MME can initiate the paging procedure.

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 adaptive and selective bundling of downlink paging messages. According to one aspect disclosed herein, a mobility management entity (“MME”) can determine whether to delay a paging procedure to deliver a downlink paging message to a mobile device served by the MME. If the MME determines that the paging procedure to deliver the downlink paging message to the mobile device should be delayed, then the MME can store the downlink paging message in a bundling cache. If the MME determines that the paging procedure to deliver the downlink paging message to the mobile device should not be delayed, then the MME can initiate the paging procedure.

In some embodiments, the MME can determine whether a data flow associated with the mobile device is delay sensitive. If the MME determines that the data flow associated with the mobile device is delay sensitive, then the MME can determine that the paging procedure to deliver the downlink paging message to the mobile device should not be delayed, and in response, the MME can initiate the paging procedure without delay and without storing the downlink paging message in the bundling cache. If the MME determines that the data flow associated with the mobile device is not delay sensitive, then the MME can determine that the paging procedure to deliver the downlink paging message to the mobile device should be delayed.

In some embodiments, the MME can determine a quality of service (“QoS”) category for the data flow associated with the mobile device. The MME can determine whether the data flow associated with the mobile device is delay sensitive based upon the QoS category.

In some embodiments, the MME can initiate a bundle timer for the bundling cache. The MME can determine whether the bundle timer has expired. If the MME determines that the bundle timer has expired, then the MME can determine that the paging procedure to deliver the downlink paging message to the mobile device should not be further delayed and, in response, the MME can initiate the paging procedure to deliver the downlink paging message stored in the bundling cache to the mobile device. If the MME determines that the bundle timer has not expired, then the MME can determine that the paging procedure to deliver the downlink paging message to the mobile device should be further delayed and, in response, the MME can allow storage of a further downlink paging message in the bundling cache.

In some embodiments, the MME can calculate a signaling load experienced by a cell that is serving the mobile device. The MME can determine whether the cell that is serving the mobile device is congested based upon the signaling load. If the MME determines that the cell that is serving the mobile device is not congested, then the MME can determine that the paging procedure to deliver the downlink paging message to the mobile device should not be delayed and, in response, the MME can initiate the paging procedure without delay and without storing the downlink paging message in the bundling cache. If the MME determines that the cell that is serving the mobile device is congested, then the MME can determine that the paging procedure to deliver the downlink paging message to the mobile device should be delayed.

In some embodiments, the MME can receive a current device bundling state from the mobile device. The MME can determine whether the current device bundling state is set to conserve resources. If the MME determines that the current device bundling state is not set to conserve resources, then the MME can determine that the paging procedure to deliver the downlink paging message to the mobile device should not be delayed and, in response, the MME can initiate the paging procedure without delay and without storing the downlink paging message in the bundling cache. If the MME determines that the current device bundling state is set to conserve resources, then the MME can determine that the paging procedure to deliver the downlink paging message to the mobile device should be delayed.

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”). Paging information is utilized for network-initiated connection setup. In Long-Term Evolution (“LTE”) networks, when a mobile device (also known as user equipment (“UE”), or “handset”) is in radio resource control (“RRC”) idle mode (“RRC_IDLE”), and whenever data is to be sent downlink to the mobile device, a packet data network (“PDN”) gateway (“PGW”) sends the data to a serving gateway (“SGW”). The SGW generates a downlink notification message and sends the downlink notification message to a mobility management entity (“MME”). The MME triggers a paging procedure.

When a mobile device is in the idle mode state, the MME knows the location of the mobile device on a per tracking area (“TA”) basis, instead of at the cell level. For this reason, the MME pages all base stations within a TA and informs (e.g., via an S1AP paging message in LTE) the base stations to broadcast paging messages to the impacted tracking area(s). The base station receives the S1AP paging message from the MME and constructs an RRC paging message.

The mobile device wakes up on every paging occasion. The paging occasion is a function of the discontinuous reception (“DRX”) cycle. The mobile device searches the paging radio network temporary identifier (“P-RNTI”) within the physical downlink control channel (“PDCCH”). If the mobile device detects a group identity used for the P-RNTI, when the mobile device wakes up, and finds the mobile device's identity, the mobile device proceeds to decode the RRC paging message and triggers the random access procedure (“RAC”) followed by establishing the RRC connection. If the mobile device does not find the mobile device's identity in the paging message, the mobile device goes back to sleep based upon the DRX cycle.

Concepts and technologies are described herein for dynamic bundling of downlink packet flow paging messages. The concepts and technologies disclosed herein reduce the amount of paging and therefore reduce the radio access network (“RAN”) signaling events via bundling downlink packet flow paging messages based upon a last known bundling state of mobile devices.

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 illustrated operating environment100includes a mobile device102that is in communication with an evolved packet core (“EPC”)104via an evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (“E-UTRAN”)106. In the illustrated embodiment, the EPC104includes a mobility management entity (“MME”)108and one or more other EPC functions110.

The mobile device102may be a cellular telephone, a feature phone, a smartphone, a mobile computing device, a portable television, a portable video game console, other computing device, or any other user equipment (“UE”) that is configured to communicate with one or more one or more RANs, such as the E-UTRAN106, via one or more radio access components112. As such, the radio access component(s)112can include at least one transceiver that is compatible with Long-Term Evolution (“LTE”) to enable communications with the E-UTRAN106. The radio access component(s)112can include one or more other transceivers to enable communications with other access networks including, but not limited to, access networks that operate in accordance with Global System for Mobile communications (“GSM”), Code Division Multiple Access (“CDMA”) ONE, CDMA2000, and various other Third Generation Partnership Project (“3GPP”). Moreover, the other transceiver(s) may facilitate communications over 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”), Wideband CDMA (“W-CDMA”), Orthogonal Frequency-Division Multiplexing (“OFDM”), Space-Division Multiple Access (“SDMA”), and the like. The radio access component(s)112also can include one or more transceivers to enable communications with WI-MAX and/or WI-FI networks.

The MME108performs signal handling operations related to mobility and security for access to the E-UTRAN106. The MME108can track and page the mobile device102when the mobile device102is in idle mode. The illustrated MME108includes a selective bundling decision engine114and a downlink paging message bundling cache116. Alternatively, the MME108can be in communication with one or more computing systems and/or devices that can execute, via one or more processors, the selective bundling decision engine114and/or provide one or more computer-readable storage mediums for the downlink paging message bundling cache116.

The selective bundling decision engine114can be executed by one or more processors of the MME108to determine whether two or more downlink paging messages should be bundled in the downlink paging message bundling cache116. The selective bundling decision engine114can bundle two or more downlink paging messages.

In some embodiments, the selective bundling decision engine114can receive a current device bundling state118from the mobile device102and/or one or more other mobile devices (not shown) located in the same cell (e.g., a cell served by an eNodeB119). The selective bundling decision engine114can determine whether downlink paging messages directed to the mobile device102and/or other mobile devices (not shown) operating within a TA served by the MME108should be bundled. The current device bundling state118can identify the mobile device102being in a state in which communications should be performed in real-time for best latency to facilitate operations being performed by the mobile device102. The current device bundling state118can identify the mobile device102being in a state in which communications should be bundled to conserve resources. The current device bundling state118, in some embodiments, is included in an SLAP initial paging message generated by the mobile device102and sent to the MME108.

If the current device bundling state is “bundle to conserve UE resources”, then the MME108can bundle pages for the mobile device102no matter the signaling load at the eNodeB119. In this manner, the MME108can correlate with the UE DRX cycle for battery conservation. Each eNodeB119within a TA can report PDCCH, PUCCH and paging channel occupancy back to the MME108according to a set interval. If the MME108detects that a significant distribution of eNodeBs119, within the same TA, have high paging channel occupancy, then network resource conservation is desired, and thus driving even longer bundling timers for the mobile device102in the bundle to conserve UE resources state.

Signaling load also can be detected within the MME108. For example, any processor cycles the MME108has available for paging can be indicative of the signaling load. In this case, the load at the MME108(in addition to the load at the eNodeB119) can be used to determine network signaling load (not just RAN signaling load). Moreover, the combination of UE bundling state and network signaling load can be used to determine the length of bundling timers on a per-UE basis. If the UE bundling state for the mobile device102is “bundle to conserve UE resources” and the network load is high (e.g., based upon a threshold defined for “high”), then the longest bundling timers can be used for the mobile device102, and thus conserving network and UE resources. If the MME108is the network signaling load bottleneck (e.g., low MME processor cycles available for paging), then the MME108can choose to bundle pages in order to flatten the aggregate peak paging load over time. In this case, the UE bundling state can be used to determine which UE to bundle to conserve MME processor resources.

The selective bundling decision engine114, in some embodiments, can collect data from the EPC104, such as from one or more of the other EPC functions110, and can calculate, utilizing the data, a signaling load of the E-UTRAN106. An illustrative method in which the selective bundling decision engine114collects data from the EPC104and utilizes the data to calculate the signaling load of the E-UTRAN106is described below with reference toFIG. 2.

The selective bundling decision engine114can selectively bundle downlink paging messages if the last known device bundling state, such as the current device bundling state118last received by the MME108, is to bundle to conserve resources and the quality of service (“QoS”) category on an associated data flow indicates that the data flow is not delay sensitive according to QoS class identifier (“QCI”) class attributes. While the mobile device102is in the bundle to conserve resources state, as identified in the last known device bundling state, the selective bundling decision engine114can cache messages associated with certain QCIs for a defined bundling interval. Upon expiration of the bundling timer, the MME108can initiate a paging procedure and can send a downlink paging bundle120that includes at least a portion of the messages stored in the downlink paging message bundling cache116. While the mobile device102is in the real-time for best latency state, the MME108can initiate the paging procedure without delay and bundling.

The other EPC functions110of the EPC104can include a serving gateway (“SGW”), a packet data network (“PDN”) gateway (“PGW”), and a home subscriber server (“HSS”). The SGW can transport Internet Protocol (“IP”) data traffic between the mobile device102and one or more external networks, including, for example, an IP multimedia subsystem (“IMS”) network. The SGW connects the E-UTRAN106to the EPC104to allow IP data communications between the mobile device102and the EPC104. The SGW also performs operations to facilitate handover among eNodeBs, such as the eNodeB119, within the E-UTRAN106and between other LTE and 3GPP access networks. The SGW is in communication with the PDN gateway.

The PDN gateway interconnects the EPC104and external IP networks (i.e., PDNs—not shown). The PDN gateway routes IP packets to and from the PDNs. The PDN gateway also performs operations such as IP address/IP prefix allocation, policy control, and charging. In some implementations, the PDN gateway and the SGW are combined.

The HSS is a database that contains user/subscriber information. The HSS also performs operations to support mobility management, call and session setup, user authentication, and access authorization.

The illustrated mobile device102also includes an operating system122, one or more applications124, a bundling state decision engine126, and/or device bundling states128-128N. The operating system122is a program for controlling the operation of the mobile device102. The operating system122can 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)124can execute on top of the operating system122. The application(s)124can 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, combinations thereof, and the like.

The bundling state decision engine126can monitor operations performed, at least in part, by the application(s)124to determine characteristics of data sessions created by or otherwise utilized by the application(s)124. In other words, the bundling state decision engine126can determine whether the application(s)124exhibit interactive or non-interactive characteristics. The bundling state decision engine126can monitor user input to and data flow requests by the application(s)124. The bundling state decision engine126can categorize a 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 bundling state decision engine126can 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)124is in progress, then the bundling state decision engine126can 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 bundling state decision engine126can determine the uplink data flow request to be non-interactive. Interactive characteristics can cause the bundling state decision engine126to associate the mobile device102with the “real-time for best latency device” bundling state. Non-interactive characteristics can cause the bundling state decision engine126to associate the mobile device102with the “bundle to conserve resources” bundling state.

In addition to QoS class, the network can look for a correlation between downlink page requests, and if found, preceding uplink requests from the mobile device102. If the downlink page request follows an uplink request within a pre-defined time period, then the downlink flow is determined to be in response to an interactive user request. If there was no uplink request within the pre-defined time period, then the downlink page request is likely some non-interactive push application which can benefit from bundling without negatively impacting end user latency and experience.

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 adaptively and selectively bundling downlink paging messages 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 MME108via execution, by one or more processors, of the selective bundling decision engine114. The method200is described with additional reference toFIG. 1. The method200begins and proceeds to operation202, where the MME108receives the current device bundling state118from the mobile device102. From operation202, the method200proceeds to operation204, where the MME108calculates a signaling load. In some embodiments, each eNodeB, such as the eNodeB119, operating within the E-UTRAN106within a TA can report PDCCH, PUCCH, and/or paging channel occupancy back to the MME108according to a set interval. The MME108can utilize PDCCH, PUCCH, and/or paging channel occupancy to calculate or estimate signaling load at operation204.

From operation204, the method200proceeds to operation206, where the MME108determines, based upon the signaling load calculated at operation204, whether the serving cell of the mobile device102is congested. If the MME108determines that the serving cell of the mobile device102is not congested, the method200proceeds to operation208, where the MME108initiates a paging procedure without bundling and delay. From operation208, the method200proceeds to operation210. The method200may end at operation210.

If, however, the MME108determines, at operation206, that the serving cell of the mobile device102is congested, the method200proceeds to operation212, where the MME108determines if the current device bundling state118is set to conserve resources. If the MME108determines that the current device bundling state118is not set to conserve resources, the method200proceeds to operation208, where the MME108initiates a paging procedure without bundling and delay. From operation208, the method200proceeds to operation210. The method200may end at operation210.

If, however, the MME108determines, at operation212, that the current device bundling state118is set to conserve resources, the method200proceeds to operation214, where the MME108determines a QoS category for an associated data flow. From operation214, the method200proceeds to operation216, where the MME108determines if the QoS category determined at operation214is indicative of the data flow being delay sensitive. If the MME108determines, at operation216, that the QoS category determined at operation214is indicative of the data flow being delay sensitive, the method200proceeds to operation208, where the MME108initiates a paging procedure without bundling and delay. From operation208, the method200proceeds to operation210. The method200may end at operation210.

If, however, the MME108determines, at operation216, that the QoS category determined at operation214is not indicative of the data flow being delay sensitive, the method200proceeds to operation218, where the MME108stores one or more downlink paging messages in the downlink paging message bundling cache116. Also, the first time operation218is executed by the MME108, the MME108can initiate a bundle timer for the downlink paging message bundling cache116.

From operation218, the method200proceeds to operation220, where the MME108determines whether the bundle timer for the downlink paging message bundling cache116has expired. If the MME108determines that the bundle timer has not expired, the method200proceeds back to operation218, where the MME108continues to store one or more downlink paging messages in the downlink paging message bundling cache116. If, however, the MME108determines that the bundle timer has expired, the method200proceeds to operation222. At operation222, the MME108initiates a paging procedure to deliver the downlink paging message(s) stored in the downlink paging message bundling cache116to the mobile device102. Also at operation222, the MME108can reset the bundle timer. From operation222, the method200proceeds to operation210, where the method200may end.

FIG. 3is a block diagram illustrating a computer system300configured to provide the functionality in accordance with various embodiments of the concepts and technologies disclosed herein. In some implementations, the mobile device102, MME108, one or more of the other EPC functions110, and/or the eNodeB119can utilize an architecture that is the same as or similar to the architecture of the computer system300. It should be understood, however, that modification to the architecture may be made to facilitate certain interactions among elements described herein.

The computer system300includes a processing unit302, a memory304, one or more user interface devices306, one or more input/output (“I/O”) devices308, and one or more network devices310, each of which is operatively connected to a system bus312. The bus312enables bi-directional communication between the processing unit302, the memory304, the user interface devices306, the I/O devices308, and the network devices310.

The processing unit302may 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 memory304communicates with the processing unit302via the system bus312. In some embodiments, the memory304is operatively connected to a memory controller (not shown) that enables communication with the processing unit302via the system bus312. The memory304includes an operating system313and one or more program modules316. The operating system313can 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 modules316may include various software and/or program modules to perform the various operations described herein. The program modules316can include the application(s)124and the bundling state decision engine126in embodiments that the mobile device102is configured like the computer system300. The program modules316can include the selective bundling decision engine114in embodiments that the MME108is configured like the computer system300. The program modules316and/or other programs can be embodied in computer-readable media containing instructions that, when executed by the processing unit302, perform one or more of the methods200, or at least a portion thereof, described in detail above with respect toFIG. 2. According to embodiments, the program modules316may be embodied in hardware, software, firmware, or any combination thereof. Although not shown inFIG. 3, it should be understood that the memory304, in embodiments that the mobile device102is configured like the computer system300, also can be configured to store the device bundling states128-128N, and/or other data. Although not shown inFIG. 3, it should be understood that the memory304, in embodiments that the MME108is configured like the computer system300, also can be configured to store the downlink paging message bundling cache116, and/or other data.

The user interface devices306may include one or more devices with which a user accesses the computer system300. The user interface devices306may include, but are not limited to, computers, servers, personal digital assistants, cellular phones, or any suitable computing devices. The I/O devices308enable a user to interface with the program modules316. In one embodiment, the I/O devices308are operatively connected to an I/O controller (not shown) that enables communication with the processing unit302via the system bus312. The I/O devices308may include one or more input devices, such as, but not limited to, a keyboard, a mouse, or an electronic stylus. Further, the I/O devices308may include one or more output devices, such as, but not limited to, a display screen or a printer.

The network devices310enable the computer system300to communicate with other networks or remote systems via a network318, which can include, for example, the EPC104and the E-UTRAN106. Examples of the network devices310include, 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 network318may 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 network318may 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 (“PAN”), or a wired metropolitan area network (“MAN”).

Turning now toFIG. 4, an illustrative mobile device400and 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 device400described herein inFIG. 4. It should be understood, however, that the mobile device102may or may not include the functionality described herein with reference toFIG. 4. While connections are not shown between the various components illustrated inFIG. 4, it should be understood that some, none, or all of the components illustrated inFIG. 4can 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. 4and 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. 4, the mobile device400can include a display402for displaying data. According to various embodiments, the display402can 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 device400also can include a processor404and a memory or other data storage device (“memory”)406. The processor404can be configured to process data and/or can execute computer-executable instructions stored in the memory406. The computer-executable instructions executed by the processor404can include, for example, an operating system408(e.g., the operating system122), one or more applications410(e.g., the application(s)124and the bundling state decision engine126), other computer-executable instructions stored in a memory406, or the like. In some embodiments, the applications410also can include a UI application (not illustrated inFIG. 4).

The UI application can be executed by the processor404to 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 applications410, and otherwise facilitating user interaction with the operating system408, the applications410, and/or other types or instances of data412that can be stored at the mobile device400. The data412can include, for example, the device bundling states128-128N, the current device bundling state118, the downlink paging bundle120, and/or other data, if desired.

According to various embodiments, the applications410can 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 applications410, the data412, and/or portions thereof can be stored in the memory406and/or in a firmware414, and can be executed by the processor404. The firmware414also can store code for execution during device power up and power down operations. It can be appreciated that the firmware414can be stored in a volatile or non-volatile data storage device including, but not limited to, the memory406and/or a portion thereof.

The mobile device400also can include an input/output (“I/O”) interface416. The I/O interface416can 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 interface416can 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 (RJ44) port, an RJ11 port, a proprietary port, combinations thereof, or the like. In some embodiments, the mobile device400can be configured to synchronize with another device to transfer content to and/or from the mobile device400. In some embodiments, the mobile device400can be configured to receive updates to one or more of the applications410via the I/O interface416, though this is not necessarily the case. In some embodiments, the I/O interface416accepts 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 interface416may be used for communications between the mobile device400and a network device or local device.

The mobile device400also can include a communications component418. The communications component418can be configured to interface with the processor404to 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 component418includes a multimode communications subsystem for facilitating communications via the cellular network and one or more other networks.

The communications component418, 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 component418may be configured to communicate using GSM, CDMA, CDMAONE, CDMA2000, LTE, and various other 2G, 2.4G, 3G, 4G, and greater generation technology standards. Moreover, the communications component418may 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 component418may 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 component418can include a first transceiver (“TxRx”)420A that can operate in a first communications mode (e.g., GSM). The communications component418also can include an Nthtransceiver (“TxRx”)420N that can operate in a second communications mode relative to the first transceiver420A (e.g., UMTS). While two transceivers420A-N (hereinafter collectively and/or generically referred to as “transceivers420”) are shown inFIG. 4, it should be appreciated that less than two, two, and/or more than two transceivers420can be included in the communications component418.

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

In some embodiments, the communications component418also can facilitate reception from terrestrial radio networks, digital satellite radio networks, internet-based radio service networks, combinations thereof, and the like. The communications component418can 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 device400also can include one or more sensors424. The sensors424can 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 sensors424can 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 device400may be provided by an audio I/O component426. The audio I/O component426of the mobile device400can 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 device400also can include a subscriber identity module (“SIM”) system428. The SIM system428can include a universal SIM (“USIM”), a universal integrated circuit card (“UICC”) and/or other identity devices. The SIM system428can include and/or can be connected to or inserted into an interface such as a slot interface430. In some embodiments, the slot interface430can be configured to accept insertion of other identity cards or modules for accessing various types of networks. Additionally, or alternatively, the slot interface430can be configured to accept multiple subscriber identity cards. Because other devices and/or modules for identifying users and/or the mobile device400are contemplated, it should be understood that these embodiments are illustrative, and should not be construed as being limiting in any way.

The mobile device400also can include an image capture and processing system432(“image system”). The image system432can be configured to capture or otherwise obtain photos, videos, and/or other visual information. As such, the image system432can include cameras, lenses, charge-coupled devices (“CCDs”), combinations thereof, or the like. The mobile device400may also include a video system434. The video system434can be configured to capture, process, record, modify, and/or store video content. Photos and videos obtained using the image system432and the video system434, 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 device400also can include one or more location components436. The location components436can be configured to send and/or receive signals to determine a geographic location of the mobile device400. According to various embodiments, the location components436can 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 component436also can be configured to communicate with the communications component418to retrieve triangulation data for determining a location of the mobile device400. In some embodiments, the location component436can 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 component436can include and/or can communicate with one or more of the sensors424such as a compass, an accelerometer, and/or a gyroscope to determine the orientation of the mobile device400. Using the location component436, the mobile device400can 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 device400. The location component436may include multiple components for determining the location and/or orientation of the mobile device400.

The illustrated mobile device400also can include a power source438. The power source438can 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 source438also can interface with an external power system or charging equipment via a power I/O component440. Because the mobile device400can 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 device400is illustrative, and should not be construed as being limiting in any way.

Turning now toFIG. 5, additional details of a network500are illustrated, according to an illustrative embodiment. The network500includes a cellular network502, a packet data network504, for example, the Internet, and a circuit switched network506, for example, a publicly switched telephone network (“PSTN”). The cellular network502includes various components such as, but not limited to, RANs (e.g., the E-UTRAN106), BTSs, NodeBs or eNodeBs (e.g., the eNodeB119), base station controllers (“BSCs”), radio network controllers (“RNCs”), mobile switching centers (“MSCs”), MMEs (e.g., the MME108), 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”), the EPC104, the other EPC functions110, and the like. The cellular network502also includes radios and nodes for receiving and transmitting voice, data, and combinations thereof to and from radio transceivers, networks, the packet data network504, and the circuit switched network506.

A mobile communications device508, 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 network502. The cellular network502can be configured as a 2G GSM network and can provide data communications via GPRS and/or EDGE. Additionally, or alternatively, the cellular network502can 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 network502also is compatible with 4G mobile communications standards such as LTE, or the like, as well as evolved and future mobile standards.

The packet data network504includes various devices, for example, servers, computers, databases, and other devices in communication with another, as is generally known. The packet data network504devices 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 network504includes or is in communication with the Internet. The circuit switched network506includes various hardware and software for providing circuit switched communications. The circuit switched network506may include, or may be, what is often referred to as a plain old telephone system (POTS). The functionality of a circuit switched network506or other circuit-switched network are generally known and will not be described herein in detail.

The illustrated cellular network502is shown in communication with the packet data network504and a circuit switched network506, though it should be appreciated that this is not necessarily the case. One or more Internet-capable devices510, for example, the mobile device102, a PC, a laptop, a portable device, or another suitable device, can communicate with one or more cellular networks502, and devices connected thereto, through the packet data network504. It also should be appreciated that the Internet-capable device510can communicate with the packet data network504through the circuit switched network506, the cellular network502, and/or via other networks (not illustrated).

As illustrated, a communications device512, for example, a telephone, facsimile machine, modem, computer, the mobile device102, or the like, can be in communication with the circuit switched network506, and therethrough to the packet data network504and/or the cellular network502. It should be appreciated that the communications device512can be an Internet-capable device, and can be substantially similar to the Internet-capable device510. In the specification, the network500is used to refer broadly to any combination of the networks502,504,506. It should be appreciated that substantially all of the functionality described with reference to the network500can be performed by the cellular network502, the packet data network504, and/or the circuit switched network506, alone or in combination with other networks, network elements, and the like.

Based on the foregoing, it should be appreciated that concepts and technologies directed to adaptive and selective bundling of downlink paging messages have been disclosed herein. Although the subject matter presented herein has been described in language specific to computer structural features, methodological and transformative acts, specific computing machinery, and computer-readable media, it is to be understood that the concepts and technologies disclosed herein are not necessarily limited to the specific features, acts, or media described herein. Rather, the specific features, acts and mediums are disclosed as example forms of implementing the concepts and technologies disclosed herein.