Network congestion management service

A method, a device, and a non-transitory storage medium having instructions to attach to a user device, wherein the network device provides wireless access coverage in a cell area or a sector area of a first network; detect whether the network device is in a congested state; generate a message that indicates that the network device is in the congested state when the network device is in the congested state; and transmit the message on a control or signaling channel for receipt by user devices attached to the network device in the cell area or the sector area. The user device scans the control or signaling channel before initiating a session and determines whether the network device is in the congested state. When the network device is in the congested state, the user device performs a switchover to a second network. The user device has multimode capabilities.

BACKGROUND

Due to resource limitations, a wireless node, such as a base station, can experience congestion. For example, when the network load is such that network resource limitations cannot be relieved for an extended period of time, a congested state is reached. However, since the coverage of the radio access technology (e.g., Long Term Evolution (LTE) is still good, a mobile device won't search for another RAT to obtain service. As a result, a mobile device that is attached to the base station may not be able to obtain service. For critical, real-time services, there should be a way for a multi-RAT user device to find a service in the underlying radio access network for alternative services.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

A network may enter a congested state due to resource limitations. For example, in a wireless network, a base station may have certain resource limitations to provide a service. During this time, a mobile device, which is attached to the base station, may not be able to use the base station for service. For example, the mobile device may not be able to place a telephone call via the base station since the base station is in the congested state.

However, a wireless user device, such as a mobile device, may include multiple, wireless communication interfaces that allow the wireless user device to communicate via different technological standards. For example, the wireless user device may have Long Term Evolution (LTE) and Code Division Multiple Access (CDMA) capabilities. Unfortunately, when the base station, such as an evolved Node B (eNB) of the LTE standard, is in a prolonged congested state, the wireless user device does not have information pertaining to the congested state of the eNB and continues to access LTE for a service, since the LTE system shows a very strong coverage (e.g., based on radio link measurement), which may lead to a failure in service. For example, the wireless user device may be denied or blocked from placing a telephone call via the eNB. While the wireless user device may attempt to subsequently place the telephone call via a base station of the CDMA standard due to LTE call origination failure, the user will experience delay before the telephone call can be established. However, a better approach may be for the wireless user device to try the service directly in CDMA without first experiencing a failure by the LTE system.

According to an exemplary embodiment, a wireless node determines when the wireless node is in a congested state. Based on such a determination, according to an exemplary embodiment, the wireless node broadcasts a message that carries information indicating that the wireless node is in the congested state. For example, the wireless node may broadcast the message periodically via a signaling channel or a control channel. According to an exemplary embodiment, the wireless node broadcasts a message that carries information indicating that the wireless node is not in the congested state. That is, the message indicates that a service is available via the wireless node. In this way, the wireless node may toggle between broadcast messages based on the state of the wireless node (i.e., congested or non-congested). According to another embodiment, the wireless node does not broadcast a message that carries information indicating that the wireless node is not in the congested state or changes the content of the same message to indicate a non-congested state.

According to an exemplary embodiment, the wireless user device monitors for a message before invoking a particular service. For example, assume a user of a wireless user device decides to place a telephone call and provides an input, via the wireless user device, to initiate the telephone call. In response, the wireless user device monitors or scans a channel to determine whether the base station is in the congested state for this type of service. For example, the wireless user device may receive a broadcast message, via the channel, indicating that the wireless node is or is not in a congested state for a type of service. According to this example, assume that the wireless user device receives the broadcast message that indicates that the wireless node is in the congested state. According to an exemplary embodiment, based on the receipt of the message, the wireless user device switches from one wireless communication interface used to communicate with the congested base station, to another wireless communication interface. For example, assume the base station is an eNB of an LTE network. The wireless user device switches from an LTE communication interface to another communication interface (e.g., a CDMA communication interface) to place the telephone call. In this way, a call set-up failure with the congested eNB is avoided.

In view of foregoing, quality of service issues stemming from congestion may be minimized. Additionally, in contrast to “network-wide” congestion control mechanisms, the congestion control management service may be implemented at a cell or a sector level (e.g., a portion of a cell), which in turn provides a more granular level of congestion control. Also, in contrast to other congestion control mechanisms that require the wireless user device to perform special operations so as to evaluate and guess the state of the network, the congestion control management service (e.g., using existing service-specific access barring in System Information Block (SIB) type 2 for LTE, and extend user equipment (UE) behavior to its RRC connected mode in addition to RRC idle mode) provides a more definitive solution for managing congestion by transmitting a message indicating its current state.

FIG. 1is a diagram illustrating an exemplary environment100in which exemplary embodiments of a network congestion management service may be implemented. As illustrated, environment100includes a first network105, which includes a network device110, and a second network115, which includes a network device120. As further illustrated, environment100includes a user device150.

Environment100may be implemented to include wireless connections between user device150and networks105and115. A connection may be direct or indirect and may involve an intermediary device and/or an intermediary network not illustrated inFIG. 1. Additionally, the number and the arrangement of connections between user device150and networks105and115are exemplary.

A device may be implemented according to one or multiple network architectures (e.g., a client device, a server device, a peer device, a proxy device, and/or a cloud device). Also, according to other embodiments, one or more functions and/or processes described as being performed by a particular device may be performed by a different device, or some combination of devices. First network105and second network115may share a common service provider. Alternatively, first network105and second network115may each be associated with different service providers.

First network105includes a wireless network that provides access to a service or an asset. First network105may be implemented using various wireless architectures and/or technologies, such as a cellular network, a 3rd Generation (3G) network, a 4th Generation (4G) network, etc. By way of further example, first network105may be implemented to include an LTE network, a Universal Mobile Telecommunications System (UMTS) network, a Global System for Mobile Communications (GSM) network, a Wideband Code Division Multiple Access (WCDMA) network, an Ultra Mobile Broadband (UMB) network, a High-Speed Packet Access (HSPA) network, a Worldwide Interoperability for Microwave Access (WiMAX) network, an Evolution Data Optimized (EV-DO) network, and/or another type of wireless network (e.g., an LTE Advanced network, or future generation wireless network architecture).

Given the wide variety of wireless networks that may be implemented in various embodiments, first network105may include various types of network devices110, such as a base station, a base station controller, an eNB, a serving gateway (SGW), a packet data network gateway (PGW), a mobility management entity (MME), a home node B, a wireless relay node, a pico base station, a base transceiver station, a repeater, a user device gateway, a radio node, an anchor point, a wireless router, a gateway, etc. A network device may support one or multiple access and/or wireless technologies. First network105may include other network devices that pertain to billing, security (e.g., a firewall, an authentication device, etc.), providing a service or an asset, providing access to another network, etc.

According to an exemplary embodiment, a network device110of first network105determines when network device110is in a congested state. For example, network device110may use conventional or well-known techniques to determine a state of congestion. According to an exemplary embodiment, when network device110determines that it is in a congested state, network device110generates and transmits a message that carries information indicating that network device110is in the congested state. According to an exemplary embodiment, network device110broadcasts the messages for receipt by user device150. For example, network device110broadcasts the message periodically during a time period network device110is in the congested state. According to an exemplary embodiment, network device110broadcasts the message on a signaling channel or a control channel.

According to an exemplary embodiment, when network device110determines that it is no longer in a congested state, network device110generates and transmits a message that carries information indicating that network device110is not in a congested state. Network device110may periodically broadcast the message on a signaling channel or a control channel. Alternatively, when network device110determines that it is no longer in a congested state, network device110may take no further action. According to such an embodiment, when user device150monitors or scans the signaling channel or the control channel and determines that no message is to be received, user device150determines that network device110is not in a congested state.

According to an exemplary embodiment, network device110is an wireless access node to first network. For example, network device110may be implemented as a base station. By way of further example, network device110may be implemented as an eNB, a Node B, a base transceiver station, a microcell wireless node, a picocell wireless node, or a femtocell wireless node. Alternatively, network device110may be implemented as a gateway device or an access point that may act as an entry point to first network105in a particular cell or sector. In this way, the network congestion management service may provide a finer granularity of congestion control compared to other network-wide or larger geo-based areas of congestion control.

Second network115includes a wireless network that provides access to a service or an asset. Similar to first network105, second network115may be implemented using various wireless architectures and/or technologies and includes various types of network devices. Network device120is a device similar to network device110. According to an exemplary embodiment, network device110and network device120may be combined into a single device having distinct logic and communication interfaces.

According to an exemplary embodiment, first network105and second network115include different types of wireless access technologies. For example, first network105may include an LTE network and second network115may include a wireless network other than an LTE network. Additionally, although environment100illustrates two networks (i.e., first network105and second network115), according to other embodiments, environment100may include an additional network (e.g., a third network, a fourth network, etc.). The additional network may be of a third type or may be of a type that is redundant relative to first network105or second network115. The use of a third network, a fourth network, etc., may rest on the multimode capabilities of user device150.

User device150includes a device with wireless communicative capabilities. User device150may be a mobile device. For example, user device150may be implemented as a smartphone, a tablet device, a netbook, a vehicular communication system within a vehicle, a computer, a smart television, or some other type of suitable wireless communicative device. According to other embodiments, user device150may be a non-mobile device. For example, user device150may be implemented as a kiosk, a vending machine, a meter device associated with providing a utility (e.g., gas, electric, etc.) or other type of smart device (e.g., a sensor device, etc.). In this regard, user device150may operate with or without an end user. Additionally, user device150may operate to provide machine-to-machine communications, user-to-user communications, etc.

According to an exemplary embodiment, user device150is capable of connecting to first network105and to second network115. For example, user device150includes multiple communication interfaces. The communication interfaces operate according to at least two different communication standards. Depending on the multimode capabilities of user device150, user device150may operate in a single mode at one time or may operate in multiple modes simultaneously. The operation of user device150in the single mode may or may not include the scanning or monitoring of another mode/wireless technology. An exemplary implementation of the network congestion management service is described further below.

FIGS. 2A-2Dare diagrams illustrating an exemplary implementation of an exemplary embodiment of the network congestion management service. Referring toFIG. 2A, an LTE network210includes an eNB215and an MME220. A CDMA network250includes a base station255and a mobile switching center260. It may be assumed, although not illustrated, that other network elements (e.g., a packet data network gateway (PGW), a base station controller, etc.) exist in LTE network210and CDMA250, respectively, but have been omitted for purposes of brevity. A cell211indicates a geographic area serviced by eNB215and BS255. As illustrated, eNB215and base station255resides within cell211. In this regard, eNB215and BS255may be considered co-located. A user device150-1associated with a user205-1may communicate with a user device150-2associated with a user205-2via LTE network210or CDMA network250. It may be assumed that user device150-1has multimode capabilities that include LTE and CDMA wireless technologies. Additionally, although not illustrated, an intermediary network element, a network, etc., may exist between MME220and user device150-2and/or between a mobile switching center (MSC)260and user device150-2. According to this exemplary scenario, assume user device150-1attaches to LTE network210via eNB215. Although not illustrated, user device150-1may register with CDMA network250via BS255.

According to an exemplary implementation, eNB215is configured to detect when a congested state occurs. For example, eNB215may evaluate current load measurements relative to available resources. The loading measurements may be application-specific, service-specific, or may be an overall loading measurement. By way of further example, eNB215may monitor a total number of bearers, a total bit rate, or other types of parameters (e.g., Quality of Service (QoS), Quality Control Indicator (QCI), etc.) that indicate or provide a basis for declaring a congested state. According to this example, assume that eNB215determines that it is in a congested state.

As illustrated inFIG. 2A, eNB215generates and transmits a message that carries information indicating that it is in the congested state. For example, eNB215broadcasts a System Information Block (SIB) message. The SIB message may be a type 2 message and includes a service-specific access class (SSAC) barring parameter. The SSAC barring parameter may apply to cell211or a portion of cell211(e.g., a sector). Additionally, or alternatively, the SSAC barring parameter may be application-specific. Alternatively, for example, eNB215may broadcast a bit, which indicates a congested state, using any suitable message. As previously described, for example, the message is broadcasted using a control channel or a signaling channel. Additionally, as previously described, eNB215periodically broadcasts the message while in the congested state or at least as long as possible while in the congested state (e.g., assuming congestion does not negate such a transmission on the control channel or the signaling channel).

Referring toFIG. 2B, assume user205-1wishes to place a telephone call to user205-2via LTE network210. Although not illustrated, it may be assumed that user device205-2is connected to a network capable of communicating with user device205-1via CDMA network250and LTE network210. Upon receiving an input to initiate the telephone call (or other type of service), user device150-1scans the control channel or the signaling channel that is used for broadcasting the SIB message or other type of message that may carry congestion state information. Upon scanning the channel, user device150-1receives the SIB message or other type of message and determines that eNB215is currently in a congested state and unable to service the telephone call. According to other implementations, user device150-1may scan the control channel or the signaling channel without an application or a service being initiated. For example, user device150-1may scan the control channel or the signaling channel periodically, etc.

Referring toFIG. 2C, in response to determining that eNB215is in the congested state, user device150-1automatically invokes a switchover process, which is a part of the network congestion management service. The switchover process causes user device150-1to place the telephone call via BS255of CDMA network250. For example, user device150-1uses its multimode capabilities and switches from the communication interface that supports the LTE standard to another communication interface that supports the CDMA standard so as to establish the session. According to this example, assume that user device150-1establishes a connection with BS255of CDMA network250and successfully establishes a telephone call with user205-2via user device150-2.

Referring toFIG. 2D, assume that the congested state of eNB215ends during which eNB215detects that there is no longer any congestion. Based on such a determination, eNB215generates and transmits a SIB message or other type of message that indicates there is no congestion. The SIB message or other type of message may be application-specific. According to another exemplary implementation, when eNB215detects that there is no longer any congestion, eNB215does not broadcast any message indicating that congestion has been relieved. However, according to this example, assume that eNB215broadcasts a message. Thereafter, assume user205-1initiates another call to user205-2. Also, assume that user device150-1has already switched back to LTE network210based on a preferred technology setting. In a manner similar to that previously described, user device150-1scans the control channel or the signaling channel that is used for broadcasting the SIB message or other type of message that carries congestion state information. Upon scanning the channel, user device150-1receives the SIB message or other type of message and determines that eNB215is not in a congested state and is able to service the telephone call. Based on this determination, user device150-1places the call via eNB215of LTE network210.

Although the above scenarios have been explained with respect to particular networks (e.g., LTE and CDMA), message (e.g., SIB type 2), and application (e.g., telephone call), according to other implementations, the network congestion management service may be applied to different types of networks, messages, and applications. Additionally, for example, according to other implementations, the congestion state information may be transmitted via a proprietary message or via some other suitable message and/or field of a message. Additionally, or alternatively, a user may initiate a web session (e.g., streaming of a movie, etc.) or some other type of network session that causes user device150to invoke the switchover process based on receiving a message indicating a congested state, as described herein.

As previously described, user device150includes multiple wireless communication interfaces. User device150may operate in a single mode or a dual mode. According to other scenarios, congestion may occur during a session (e.g., a telephone call or another type of session pertaining to a service or an application). During such a scenario, user device150may be configured to scan the channel and initiate a switchover process in a manner similar to that previously described. This may depend on whether the network and user device150both support service continuity via a seamless handover or not. Thus, according to one implementation, a handover from one technology (e.g., LTE) to another (e.g., CDMA) may be initiated assuming both user device150and network device110(e.g., eNB215) support this. Alternatively, according to another implementation, user device150may continue with the session as long as possible. When the session ends, whether prematurely or not, user device150may initiate the switchover process.

FIG. 3is a diagram illustrating exemplary components of a device300that may correspond to one or more of the devices in the environments described herein. For example, device300may correspond to network devices of first network105and second network115, user device150, as well as other network devices described. As illustrated, according to an exemplary embodiment, device300includes a processor305, memory/storage310that stores software315, a communication interface320, an input325, and an output330. According to other embodiments, device300may include fewer components, additional components, different components, and/or a different arrangement of components than those illustrated inFIG. 3and described herein.

Processor305may control the overall operation or a portion of operation(s) performed by device300. Processor305may perform one or multiple operations based on an operating system and/or various applications or programs (e.g., software315). Processor305may access instructions from memory/storage310, from other components of device300, and/or from a source external to device300(e.g., a network, another device, etc.).

Memory/storage310includes one or multiple memories and/or one or multiple other types of storage mediums. For example, memory/storage310may include one or multiple types of memories, such as, random access memory (RAM), dynamic random access memory (DRAM), cache, read only memory (ROM), a programmable read only memory (PROM), a static random access memory (SRAM), a single in-line memory module (SIMM), a phase-change memory (PCM), a dual in-line memory module (DIMM), a flash memory, and/or some other type of memory. Memory/storage310may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid state disk, etc.), a Micro-Electromechanical System (MEMS)-based storage medium, and/or a nanotechnology-based storage medium. Memory/storage310may include drives for reading from and writing to the storage medium.

Memory/storage310may be external to and/or removable from device300, such as, for example, a Universal Serial Bus (USB) memory stick, a dongle, a hard disk, mass storage, off-line storage, or some other type of storing medium (e.g., a compact disk (CD), a digital versatile disk (DVD), a Blu-Ray® disk (BD), etc.). Memory/storage310may store data, software, and/or instructions related to the operation of device300.

Software315includes an application or a computer program that provides a function and/or a process. Software315may include firmware. For example, with reference to user device150, software315may include an application that, when executed by processor315, provides the network congestion management service, as described herein. Additionally, with respect to network device110(e.g., eNB215, etc.), software315may include an application that, when executed by processor315, provides the network congestion management service, as described herein.

Communication interface320permits device300to communicate with other devices, networks, systems, etc. Communication interface320may include one or multiple wireless interfaces and/or wired interfaces. Communication interface320may include one or multiple transmitters and receivers or transceivers. Communication interface320may operate according to a protocol and a communication standard. As previously described, according to an exemplary embodiment, user device150includes multiple communication interfaces320. The multiple communication interfaces320support multiple wireless technologies.

Input325permits an input into device300. For example, input325may include a keyboard, a mouse, a display, a touchscreen, a touchless screen, a button, a switch, an input port, speech recognition logic, and/or some other type of visual, auditory, tactile, etc., input component. Output330permits an output from device300. For example, output330may include a speaker, a display, a touchscreen, a touchless screen, a light, an output port, and/or some other type of visual, auditory, tactile, etc., output component.

Device300may perform a process and/or a function, as described herein, in response to processor305executing software315stored by memory/storage310. By way of example, instructions may be read into memory/storage310from another memory/storage310(not shown) or read from another device (not shown) via communication interface320. The instructions stored by memory/storage310may cause processor305to perform a process described herein. Alternatively, for example, according to other implementations, device300may perform a process described herein based on the operation of hardware (processor305, etc.).

FIGS. 4A and 4Bare flow diagrams illustrating an exemplary process400pertaining to the network congestion management service. Process400is directed to a process previously described above with respect toFIGS. 1, 2A-2Dand elsewhere in this description, in which a wireless node detects when it is congested, and provides congestion state information to a user device. The user device performs a switchover process when the user device wants to establish a session via the wireless node and the wireless node is in the congested state. According to an exemplary embodiment, the wireless node (e.g., a base station, etc.) performs some of the steps described in process400. Additionally, the user device is a multimode device and performs some of the steps described in process400. For example, processor305may execute software315to perform the steps described in process400.

Referring toFIG. 4A, process400may begin with detecting whether a wireless node of a first network is in a congested state (block405). For example, a wireless node (e.g., network device110, eNB215) of a first network (e.g., first network105, LTE network210) detects whether the wireless node is in a congested state. For example, as previously described, the wireless node evaluates current load measurements relative to available resources. The load measurements may be application-specific or may be an overall load measurement.

In block410, when it is determined that the wireless node is not in a congested state (block410-NO), the process400returns to block405. That is, according to this example, the wireless node does not broadcast a message indicating it is not in a congested state. Rather, the wireless node takes no further action other than to continue to monitor its state for congestion.

When it is determined that the wireless node is in a congested state (block410—YES), a message is generated and transmitted on a control or a signaling channel that indicates the wireless node is in a congested state (block415). For example, the wireless node generates a message that carries information indicating that the wireless node is in a congested state. Depending on the wireless standard of the first network, the congestion state information may be carried in various types of messages (e.g., a SIB message, a proprietary message, etc.). The congestion state information may be application-specific or not, may be implemented as a single bit or not, etc. As previously described, the message may be transmitted on a control or a signaling channel. Additionally, the message may be periodically broadcasted within a cell or a sector of a cell during the time the wireless node is in the congested state or as long as possible (e.g., assuming congestion does not negate such a transmission on the control or the signaling channel).

For purposes of description, assume that user device150is attached to first network105and registers and/or is also attached to second network115.

In block420, an indication to establish a session via the first network is received. For example, user device150may attempt to establish a session (e.g., a data session, a voice session, a web session, a streaming session, etc.) with another device (e.g., a user device, a network device). By way of further example, a user may launch an application or provide some input to initiate a session. Alternatively, in a machine-to-machine context, user device150may be configured with a trigger to automatically initiate a session. For example, when user device150is a sensor device or a meter device, user device150may be configured with a trigger to upload data. In this regard, user device150receives an indication that a session is to be established.

In block425, the control channel or the signaling channel is scanned based on receipt of the indication. For example, user device150scans the control channel or the signaling channel before attempting to establish the session via the wireless node of the first network.

Referring toFIG. 4B, in block430, it is determined whether the wireless node is in a congested state. For example, user device150determines whether the wireless node is in the congested state based on scanning the control channel or the signaling channel and interpreting the congestion state information carried in the message. As previously described, according to an exemplary embodiment, the wireless node transmits a message that carries congestion state information indicating whether the wireless node is in a congested state. User device150is able to determine the state of the wireless node based on receiving the message. According to other embodiments, the wireless node may not transmit a message when the wireless node is not in the congested state. According to such an embodiment, user device150is able to determine that the wireless node is not in the congested state by virtue of scanning the control channel or the signaling channel and determining that no message is being broadcasted.

When it is determined that the wireless node is not in the congested state (block430—NO), user device150establishes the session via the wireless node of the first network (block435). For example, user device150establishes a data session, a voice session, a web session, or a streaming session.

When it is determined that the wireless node is in the congested state (block430—YES), user device150invokes a switchover process (block440). For example, user device150uses its multimode capabilities and switches communication interfaces to establish the session via another wireless node of a second network.

In block445, the session is established via the other wireless node of the second network. For example, user device150establishes a data session, a voice session, a web session, or a streaming session via the other wireless node (e.g., network device120, base station255) of the second network (e.g., second network115, CDMA network250).

AlthoughFIGS. 4A and 4Billustrate an exemplary network congestion management process400, according to other embodiments, process400may include additional operations, fewer operations, and/or different operations than those illustrated inFIGS. 4A and 4B, and described herein.

The foregoing description of embodiments provides illustration, but is not intended to be exhaustive or to limit the embodiments to the precise form disclosed. Accordingly, modifications to the embodiments described herein may be possible.

The terms “a,” “an,” and “the” are intended to be interpreted to include one or more items. Further, the phrase “based on” is intended to be interpreted as “based, at least in part, on,” unless explicitly stated otherwise. The term “and/or” is intended to be interpreted to include any and all combinations of one or more of the associated items.

The embodiments described herein may be implemented in many different forms of software and/or firmware executed by hardware. For example, a process or a function may be implemented as “logic” or as a “component.” The logic or the component may include, for example, hardware (e.g., processor305, etc.), or a combination of hardware and software (e.g., software315). The embodiments have been described without reference to the specific software code since the software code can be designed to implement the embodiments based on the description herein and commercially available software design environments/languages.

Additionally, embodiments described herein may be implemented as a non-transitory storage medium that stores data and/or information, such as instructions, program code, data structures, program modules, an application, etc. A non-transitory storage medium includes one or more of the storage mediums described in relation to memory/storage310.

No element, act, or instruction described in the present application should be construed as critical or essential to the embodiments described herein unless explicitly described as such.