WO2017039565A1

WO2017039565A1 - Acdc enhancements for lte and umts

Info

Publication number: WO2017039565A1
Application number: PCT/US2015/000364
Authority: WO
Inventors: Geethika KANKIPATI; Hyung-Nam Choi; Nirmala SAAHITHYAN; Leena RUPESH
Original assignee: Intel IP Corporation
Priority date: 2015-08-31
Filing date: 2015-12-24
Publication date: 2017-03-09

Abstract

Application-specific congestion control for data communication (ACDC) enhancements for long-term evolution (LTE) and universal mobile telecommunications system (UMTS) technologies are described. User equipment may include a memory device to store a plurality of application parameters. Each application parameter may associate an application with an ACDC category of a first plurality of ACDC categories. The UE may include a processing device, operatively coupled to the memory device. The processing device may receive a system information block (SIB) referencing a second plurality of ACDC categories and a default ACDC access control parameter associated with a default ACDC category. In view of the application parameters, the processing device may determine that an application executing on the UE is not associated with any category referenced by the SIB and process a network access request by the application based on the default ACDC access control parameter associated with a default ACDC category.

Description

ACDC ENHANCEMENTS FOR LTE AND UMTS

Priority Claim

[0001] This application claims the benefit of priority under 35 U.S.C. § 119(e) to U.S. Provisional Patent Application No. 62/212,460, entitled "ACDC ENHANCEMENTS FOR LTE AND UMTS," filed August 31, 2015, which is hereby incorporated herein by reference in its entirety.

Background

[0002] The disclosure relates to the field of wireless communications, including control of network access by user equipment to reduce network congestion.

Brief Description of the Drawings

[0003] Various embodiments of the present disclosure will be understood more fully from the detailed description given below and from the accompanying drawings of various embodiments of the invention.

[0004] FIG. 1 is a block diagram illustrating components of an electronic device implementing aspects of the disclosure, according to an embodiment.

[0005] FIG. 2 is a block diagram illustrating components of a network, according to an embodiment.

[0006] FIG. 3 illustrates a flowchart of an example method of performing application specific congestion control for data communication, according to an embodiment.

[0007] FIG. 4 illustrates a flowchart of an example method of performing application specific congestion control for data communication, according to an embodiment.

[0008] FIG. 5 illustrates a communication timing diagram that illustrates an example of application specific congestion control for data communication, according to an embodiment.

Description of Embodiments

[0009] Application specific congestion control for data communication (ACDC) is an access control mechanism employed by long-term evolution (LTE) and universal mobile telecommunications system (UMTS) technologies. ACDC controls the new access attempts from user equipment (UE) in idle mode based on operator-defined application categories. In congestion situations, certain applications are prioritized based on the operator defined categories. For example, disaster or emergency situations may generate more network congestion due to increased activity by UEs in the emergency area, additional UEs entering the area, or reduced network capacity due to damage to network components. In such circumstances, certain applications such as disaster message board (DMB) service or disaster voice messaging service may be prioritized, while other applications may be partially or completely barred from attempting to access the network.

[0010] In certain implementations, a Home Public Land Mobile Network (HPLMN) operator may configure a number of ACDC categories to which applications are associated to and for which the ACDC access control mechanism in idle mode is applied. The categories may be prioritized according to the expected barring levels. For example, the HPLMN operator may configure the UE with particular applications associated with particular ACDC categories. Those applications that should be restricted the least are placed in the highest category, while those applications that should be restricted the most are placed in the lowest categories. Other applications may fall into intermediate categories. According to the stage 1 specification for ACDC implementation, the number of categories configured in the UE should be greater than or equal to 4. However, operators may implement any number of additional categories.

[0011] The network may broadcast a system information block (SIB) to the UEs. The SIB may include ACDC access control parameters defining barring information for ACDC categories used by the network. Under normal operating conditions, the SIB may indicate to UEs to disable ACDC access controls. However, during periods of high congestion, such as during emergency, disaster, or unexpected events, the SIB may enable ACDC access controls. The ACDC access control parameters may include barring information of each ACDC category used by the network. The barring rate for each category may define the probability that an access attempt by an application will be barred by the UE. For each access request by an application, the UE determines an assigned ACDC category for the application and an associated barring rate received from the SIB. The UE then performs an ACDC check with the given barring rate to determine if the access attempt is allowed. For example, if the barring rate is set at 60% for an ACDC category assigned to the application, then the UE may bar an access attempt by the application with a 60% probability. Thus the UE may randomly deny an access attempt according to the barring rate for the ACDC category.

[0012] In some embodiments, high priority applications may include those that are relevant to emergency situations. For example, in an emergency situation, a DMB application may allow an UE to post a message indicating the safety of an associated user. Therefore, the DMB application may be assigned to the highest priority category and provided with the lowest barring rate. On the other hand, a video streaming application may consume significant network resources, but may not be prioritized in an emergency situation. Therefore, the video streaming application may be assigned to the lowest priority category and provided with the highest barring rate.

[0013] In practice, the case may happen that the number of ACDC categories configured in the SIB may differ from the number of categories configured in one or more UEs. For example, an UE may include application parameters that associate applications with ACDC categories. The application parameters may be set by the UE's HPLMN. However, a different Public Land Mobile Network may map applications to ACDC categories differently and may include a different number of ACDC categories. A roaming UE associated with one HPLMN may receive a SIB broadcast by another PLMN with ACDC access control parameters for a different number of categories than are defined by the application parameters on the UE. Any applications executing on the UE that are assigned to a category that does not have a matching category in the ACDC access control parameters sent over the SIB may be set to use the barring information for the lowest ACDC category broadcast by the serving network. Furthermore, some applications executing on the UE may not be assigned to a category and may also be set to use the barring information for the lowest ACDC category broadcast by the serving network.

[0014] Using this approach, UEs treat applications which are uncategorized or having no matching ACDC category with equal priority as the operator defined applications mapped to the lowest priority ACDC category. Hence, the operator defined applications mapped to the lowest ACDC category will be impacted by such unknown applications and the operator has no mechanism to selectively control the barring of such uncategorized applications and applications with non-matching ACDC categories.

[0015] Furthermore, in some implementations, the network does not control the ability of applications to request the network to prolong an established connection. For example, in UMTS, a UE may set a "follow-on request pending" indicator in an "ATTACH REQUEST" message or a "ROUTING AREA UPDATE REQUEST" message to prolong a connection if there are additional access requests pending. The follow-on-request pending indicator may request a prolonged connection after a general packet radio service (GPRS) attach procedure or routing area update procedure. Based on the follow-on request pending indicator provided from a UE, the network may prolong the connection for additional network access. However, the follow-on request pending indicator may be initiated for a low priority application. In such circumstances, a low priority application may add to the congestion on a network because ACDC only limits new access attempts in idle mode. [0016] Similarly, in LTE networks, a UE may set an "active" flag in a TRACKING AREA UPDATE REQUEST message. The UE may set the active flag when there is pending user data for uplink or for proximity-based services (ProSe) direct discovery or ProSe direct communication. In response to the active flag, the network may prolong a signaling connection after a TRACKING AREA UPDATE REQUEST is completed. The UE in connected mode may then establish network access for low priority applications during periods of high congestion.

[0017] The embodiments described herein address the above noted deficiencies by enhancing ACDC operations for LTE and UMTS applications. For example, some embodiments disclosed herein may relate to processes or techniques for handling

uncategorized applications or applications with non-matching ACDC categories in a SIB. For example, a default ACDC category may be introduced for use by the UE for uncategorized applications or applications that do not match any ACDC category in a SIB. Furthermore, in some embodiments, the UE camped on a UMTS network cell may apply ACDC categories to determine when to set a "follow-on request pending" indicator in an ATTACH REQUEST message and a ROUTING AREA UPDATE REQUEST message. In some embodiments, a UE camped on an LTE network may apply ACDC categories to determine how to set an "active" flag in TRACKING AREA UPDATE REQUEST message.

[0018] In some embodiments, an ACDC enabled evolved Node-B (eNB) in an LTE network or radio network controller (RNC) in a UMTS network may introduce a default ACDC category to control the barring of uncategorized applications and applications that do not match the ACDC categories broadcast in a SIB, thus allowing the operator of the serving network with the ability to differentiate between uncategorized applications, applications with no matching ACDC category on the UE, and applications which are mapped to the lowest ACDC category. For example, a network may broadcast a set of ACDC control parameters for a plurality of ACDC categories used by the network. The network may also include a default ACDC access control parameter for UEs to use for applications that are uncategorized or that don't match one of the broadcast categories. For example, a UE may execute an application that has not been categorized by an operator associated with the UE. Instead of treating the application as belonging to the lowest ACDC category, the UE may processes a service request for the application according to a default ACDC access parameter associated with a default ACDC category. Similarly, a UE may have a different number of ACDC categories compared to those provided in a SIB. For example, the SIB may include ACDC access control parameters for four ACDC categories, but the UE may have applications assigned to six ACDC categories. Therefore, there may be some applications assigned to ACDC categories that do not match an ACDC category in the ACDC access control parameters. Instead of using the ACDC access control parameter for the lowest priority ACDC category in the SIB, the UE may use a default ACDC access control parameter associated with a default ACDC category for applications assigned to ACDC categories that do not match an ACDC category associated with the ACDC access control parameters broadcast in a SIB. Utilizing the default ACDC access control parameter associated with the default ACDC category may enable a network operator to limit the effect of uncategorized applications on applications assigned to the lowest category of the ACDC access control parameters. In some embodiments, the network may provide one default ACDC category for uncategorized applications, and a second default ACDC category for applications having a non-matching ACDC category.

[0019] In some embodiments, the UE may apply ACDC categories while in connected mode to limit low priority applications from prolonging signaling connections. While the UE is in a connected mode, if an application generates a network service request then the UE may perform an ACDC check to determine if the application is allowed to request the network to prolong the signaling connection. For example, the UE may perform an ACDC check using the same ACDC access control parameters used during idle mode operation of the UE to determine if an access attempt is allowed. If the UE determines that the access attempt is allowed, it may include a request to prolong a signaling connection in a message to the network.

[0020] In some embodiments, the UE may use the same set of ACDC access control parameters for idle and connected mode ACDC checks. In some embodiments, the UE may use one set of ACDC access control parameters for idle mode ACDC checks, and may use another set of ACDC access control parameters for ACDC checks while in connected mode. This may enable a network operator to provide different barring rates to different ACDC categories in idle mode and connected mode. For example, the highest priority ACDC category in connected mode may have a different barring rate than the highest priority category in idle mode. Furthermore, in some embodiments, some applications may be assigned to different ACDC categories in idle mode and connected mode. For example, the UE may include a plurality of applications parameters associating applications with ACDC categories while the UE is in idle mode. The UE may also include a second plurality of application parameters associating applications with ACDC categories while the UE is in connected mode. In some embodiments, the UE may associate applications with different ACDC categories in idle mode and connected mode, and the ACDC access control parameters may have different barring rates for idle mode and connected mode.

[0021] In a UMTS cell, a UE may set a follow-on request pending indicator in an ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message to request prolonging a signaling connection. An ATTACH REQUEST message may be sent by a UE to establish a packet switched (PS) domain connection to a network. The UE may use the ATTACH REQUEST to establish a connection to the network enabling the UE to

communicate packets across the network. A ROUTING AREA UPDATE REQUEST message may be sent periodically to determine the current routing area of the UE or in response to determining that the UE has migrated from one routing area to another routing area. A routing area may be a group of cells in a geographic area which are controlled by Node-B's (NBs) that form a subdivision of the network to track UEs. When preparing to transmit a ROUTING AREA UPDATE REQUEST or ATTACH REQUEST, the UE may determine if there is a pending network access request from any applications. If there is a pending network access request, the UE may include a follow-on request pending indicator in the message. A UE may set a follow-on request indicator by setting a bit in the message to a ' Γ. For example, the message may include a particular bit that is associated with a follow-on request pending indicator. If the bit is set to 0, then the message does not include a follow-on request, however, if the bit is set to 1, then the message does include a follow-on request. In some embodiments, the follow-on request pending indicator may be sent in a message in a different manner. In response to receiving the follow-on request pending indicator, the network may keep the connection with the UE. However, maintaining a signaling connection in response to a follow-on request pending indicator generated by low priority applications may increase the congestion in the network.

[0022] As an example scenario, a UE may have ACDC enabled, and allow an application to initiate a signaling connection to the network and send an ATTACH REQUEST message. Because there is a network service request from an application, the UE may include a follow- on request pending indicator in the message. If the network accepts the request and allows the UE to remain in connected mode in the PS domain, low priority applications on the UE may use the network because ACDC doesn't apply to the UE in connected mode. The low priority applications may then utilize network resources that could be reserved for higher priority applications. Thus, low priority applications may increase network congestion by initiating a network connection while the UE is in connected mode.

[0023] To reduce congestion from low priority applications, the UE may perform an ACDC check with respect to an application-initiated service request before setting a follow-on request pending indicator in a message being transmitted to a RNC. For example, the UE operating in the connected mode may determine an ACDC access control parameter for an application requesting service. If the ACDC access control parameter includes a barring rate, the UE may use the barring rate to determine whether to allow the service request. If the service request is allowed, the UE may include a follow-on request pending indicator with the message. However, if the service request is not allowed, the message may be transmitted by the UE without a follow-on request pending indicator. If the application requesting service is a low priority application, it may continue to request service, but the UE may not include the follow-on request pending indicator. Then, the network may release the PS signaling connection and the UE may return to idle mode.

[0024] In an LTE cell, a UE may set an active flag in TRACKING AREA UPDATE REQUEST message. A tracking area may be one or more cells in a geographic area and may include one or more eNB's. The UE may send a TRACKING AREA UPDATE REQUEST message when the UE is powered on, when the UE is attempting to establish a new connection, when the UE lost a connection, when the UE detects that it has changed tracking areas, or in other circumstances. When preparing to send a TRACKING AREA UPDATE REQUEST message, the UE may set an active flag if there is a pending network service request from an application. If the UE sends a TRACKING AREA UPDATE REQUEST message with the active flag set, the network may not release the signaling connection after the tracking area update. This may increase the congestion on the network by maintaining a signaling connection based on an active flag set in response to a low priority application.

[0025] To reduce this congestion, the UE may perform an ACDC check to an application- initiated network service request before setting an active flag in a TRACKING AREA UPDATE REQUEST message being transmitted to an eNB. For example, the UE operating in the connected mode may determine an ACDC access control parameter for an application requesting service while the UE is in connected mode. If the ACDC access control parameter includes a barring rate, the UE may use the barring rate to determine whether to allow the service request. If the service request is allowed, the UE may set the active flag in the TRACKING AREA UPDATE REQUEST message. For example, a UE may set an active flag by setting a bit in the tracking area update message to a 1. For example, the message may include a particular bit that is associated with an active flag. If the bit is set to 0, then the message does not include an active flag, however, if the bit is set to 1, then the message does include an active flag. In some embodiments, the active flag may be sent in a message in a different manner. However, if the service request is not allowed, the message may be transmitted by the UE without setting the active flag. If the application requesting service is a low priority application, it may continue to request service, but the UE may not include the active flag. Then, the network may release the signaling connection and the UE may return to idle mode.

[0026] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of the claimed invention. However, various aspects of the disclosed embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail.

[0027] As used herein, the term "circuitry" may refer to, be part of, or include

an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor

(shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware.

[0028] Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software. Figure 1 illustrates, for one embodiment, example components of a UE device 100. In some embodiments, the UE device 100 may include application circuitry 102, baseband circuitry 104, Radio Frequency (RF) circuitry 106, front- end module (FEM) circuitry 108 and one or more antennas 1 10, coupled together at least as shown. [0029] The application circuitry 102 may include one or more application processors. For example, the application circuitry 102 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with and/or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

[0030] The baseband circuitry 104 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 104 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 106 and to generate baseband signals for a transmit signal path of the RF circuitry 106. Baseband processing circuity 104 may interface with the application circuitry 102 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 106. For example, in some embodiments, the baseband circuitry 104 may include a second generation (2G) baseband processor 104a, third generation (3G) baseband processor 104b, fourth generation (4G) baseband processor 104c, and/or other baseband processor(s) 104d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 104 (e.g., one or more of baseband processors 104a-d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 106. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 104 may include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 104 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of

modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[0031] In some embodiments, the baseband circuitry 104 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements. A central processing unit (CPU) 104e of the baseband circuitry 104 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP, NAS and/or RRC layers. In some embodiments, the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 104f. The audio DSP(s) 104f may include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 104 and the application circuitry 102 may be implemented together such as, for example, on a system on a chip (SoC).

[0032] In some embodiments, the baseband circuitry 104 may provide for

communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 104 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 104 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0033] RF circuitry 106 may enable communication with wireless networks

using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 106 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 106 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 108 and provide baseband signals to the baseband circuitry 104. RF circuitry 106 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 104 and provide RF output signals to the FEM circuitry 108 for transmission.

[0034] In some embodiments, the RF circuitry 106 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 106 may include mixer circuitry 106a, amplifier circuitry 106b and filter circuitry 106c. The transmit signal path of the RF circuitry 106 may include filter circuitry 106c and mixer circuitry 106a. RF circuitry 106 may also include synthesizer circuitry 106d for synthesizing a frequency for use by the mixer circuitry 106a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 106a of the receive signal path may be configured to down- convert RF signals received from the FEM circuitry 108 based on the synthesized frequency provided by synthesizer circuitry 106d. The amplifier circuitry 106b may be configured to amplify the down-converted signals and the filter circuitry 106c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down- converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 104 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 106a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0035] In some embodiments, the mixer circuitry 106a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 106d to generate RF output signals for the FEM circuitry 108. The baseband signals may be provided by the baseband circuitry 104 and may be filtered by filter circuitry 106c. The filter circuitry 106c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

[0036] In some embodiments, the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively. In some embodiments, the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a may be arranged for direct downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a of the transmit signal path may be configured for super-heterodyne operation.

[0037] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 106 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 104 may include a digital baseband interface to communicate with the RF circuitry 106. [0038] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0039] In some embodiments, the synthesizer circuitry 106d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 106d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0040] The synthesizer circuitry 106d may be configured to synthesize an output frequency for use by the mixer circuitry 106a of the RF circuitry 106 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 106d may be a fractional N/N+l synthesizer.

[0041] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 104 or the applications processor 102 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 102.

[0042] Synthesizer circuitry 106d of the RF circuitry 106 may include a divider, a delay- locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0043] In some embodiments, synthesizer circuitry 106d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fi.o)- In some embodiments, the RF circuitry 106 may include an IQ/poIar converter.

[0044] FEM circuitry 108 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1 10, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 106 for further processing. FEM circuitry 108 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 106 for transmission by one or more of the one or more antennas 110.

[0045] In some embodiments, the FEM circuitry 108 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 106). The transmit signal path of the FEM circuitry 108 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 106), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1 10).

[0046] In some embodiments, the UE device 100 may include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I O) interface.

[0047] Figure 2 illustrates some example network environment 200 according to an embodiment. For example, the network environment 200 may include a network operator 210, an evolved Node-B (eNB) or radio network controller (RNC) 220 and a plurality of user equipment (UE) units 230. If the network environment 200 illustrated in Figure 2, is implemented with UMTS technologies, then eNB or RNC 220 may be an RNC. If the network environment 200 is implemented with LTE technologies, then the eNB or RNC 220 may be an eNB. In other network environments, other network components may perform operations similar to those discussed with reference to eNB or RNC 220 in Figure 2.

[0048] The network operator 210 may direct the eNB or RNC 220 to activate or deactivate ACDC for UEs serviced by the eNB or RNC 220. The eNB or RNC 220 may determine barring rates for particular ACDC categories based on one or more network parameters monitored by the eNB or RNC 220. The network operator 210 may communicate with the eNB or RNC 220 through a wireless or hardwired communication. The network operator 210 may provide additional control data to the eNB or RNC 220. In addition, the network operator 210 may communicate with a plurality of eNBs or RNCs in a larger network environment. In some embodiments, the network operator may communicate with one or more Node-B's (NBs) through one or more RNCs. In an LTE network, the network operator 210 may be an evolved packet core (EPC) element, while in a UMTS network, the network operator 210 may be a core network element. In some embodiments, the network operator 210 may be other network elements.

[0049] The eNB or RNC 220 establishes network communications with the UE 230. The communications may be established based on LTE, UMTS, or other network standards. The eNB or RNC 220 may enable UE 230 to connect to packet switched network components or circuit switched network components. As shown in Figure 2, the eNB 220 may include a network performance monitor 212, a broadcast system 214, and an ACDC control system 216. The eNB or RNC 220 may receive access request from UE 230, periodically provide system information over a broadcast, and maintain connection information between the eNB or RNC 220 and various UE 230. In some embodiments, the eNB or RNC 220 may include application circuitry to execute one or more applications operating on the eNB or RNC 220, baseband circuitry to process baseband signals received from a receive signal path of RF circuitry and to generate baseband signals for a transmit signal path of RF circuitry, and RF circuitry to enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. The eNB or RNC 220 may include one or more antennas for transmitting and receiving RF transmissions and a front end module circuitry having a receive signal path to operate on RF signals received from one or more antennas. The front end module circuitry may also include a transmit signal path to amplify signals for transmission provided by the RF circuitry for transmission by one or more of the one or more antennas. In some embodiments, a RNC may provide communications to a NB having RF circuitry and a front end module to send and receive transmissions from UE 230. As shown in Figure 2, the eNB or RNC 220 may include processing devices 213, memory devices 215, and RF circuitry 217. The processing device 213 may include one or more central processing units and may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP, NAS and/or RRC layers. The processing device 213 may execute one or more applications on the eNB or RNC 220, perform operations as part of baseband circuitry of the eNB or RNC 220 as described with reference to Figure 1 , or perform other operations. The processing devices 215 may be coupled with and/or may include memory device 215, and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system. The memory device 215 may also store data for use by applications such as parameters provided by network operator 210 and parameters to be provided to UE 230. The eNB or RNC 220 may also include RF circuitry 217 enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 217 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 217 may include a receive signal path which may include circuitry to down- convert RF signals received from the FEM circuitry and provide baseband signals to the baseband circuitry or processing device 213. RF circuitry 217 may also include a transmit signal path which may include circuitry to up-convert signals and provide RF output signals to the FEM circuitry 108 for transmission. In some embodiments, the RF circuitry 217 may operate as described with reference to RF circuitry 106 in Figure 1. In some embodiments, the eNB or RNC 220 may include one or more of the components described with reference to Figure 1 above, such as application circuitry 102, baseband circuitry 104, RF circuitry 106, or FEM circuitry 108.

[0050] The network performance monitor 212 may monitor a variety of network performance parameters. The parameters may be based on access to the network by user equipment 230, other eNBs or RNCs, or overall network performance as may be provided by a network operator 210. Some example performance statistics may include the percentage of random access channel resources occupied by access attempts from UEs 230, the ratio of access attempts that are unserved based on collisions, packet queuing delays, eNB receiver noise ratios, or other performance measurements that may indicate the level of congestion and performance of the network. The network performance monitor 212 may provide statistics to other components of the. eNB or RNC 220 and/or to other network elements or the network operator 210.

[0051] The ACDC control system 216 may implement a control algorithm that generates one or more sets of ACDC access control parameters based on statistics received from the network performance monitor 212. The control algorithms may be prescribed by the network operator 210. For example, the network operator 210 may send a transmission including control data that directs the eNB or RNC 220 to generate ACDC access control parameters. In addition, the ACDC control system may determine whether ACDC control is enabled on the eNB or RNC 220. For example, in the absence of indications of the network congestion, the network operator 210 or the ACDC control system 216 may disable ACDC in the eNB or RNC 220. If the ACDC control system 216 determines that a change in the network performance statistic indicates an increase in network congestion, the ACDC control system 216 may increase a barring rate for at least one ACDC category.

[0052] The broadcast system 214 may generate and broadcast network information, such as a SIB, to UEs 230. For example, some SIBs may include one or more sets of ACDC access control parameters. For example, a SIB may include ACDC access control parameters generated by ACDC control system 216 in response to network performance monitor 212. The broadcast system 214 may send the SIB over a dedicated logical channel to ensure it reaches UEs 230. In some embodiments, an RNC may transmit information in a broadcast to UEs through the use of a separate NB. In addition to broadcasting ACDC parameters, the SIB may include additional information about the network, a RNC, a NB, or eNB such as transmit power information, channel bandwidth, scheduling information, neighboring cell information, communication standards, or other information necessary to connect to the network or to improve the efficiency or quality of communications.

[0053] The UE 230 may include circuitry as described with reference to Figure 1 above. The UE 230 may execute various application that request network services to communicate with a network. In addition, the UE 230 may provide information to the eNB or RNC 220 including the identity and capability of the UE 230. In some embodiments, the UE may be capable of performing ACDC operations as disclosed herein. The UE may receive a SIB broadcast from the eNB or RNC 220 that includes ACDC access control parameters. The UE may use the ACDC access control parameters to limit the access attempts sent by the UE for applications associated with particular ACDC categories or to limit requests to prolong a network connection by applications associated with particular ACDC categories.

[0054] Figure 3 illustrates an example method of processing an application-initiated network service request by a UE, according to an embodiment. Beginning in block 310, a UE receives a SIB broadcast by an eNB or a NB and containing a variety of information about network operations. The SIB may include a set of ACDC access control parameters associated with ACDC categories and may include a default ACDC access control parameter associated with a default ACDC category. The default ACDC access control parameter may be applied for applications that are uncategorized in the UE or are associated with an ACDC category that is not referenced by the ACDC access control parameters associated with ACDC categories in a SIB. The ACDC categories referenced by the ACDC access control parameters may be set by a network operator that operates the eNB or a NB. [0055] In block 320, the UE receives a network access request from an application executing on the UE. For example, an application may request to upload data to a network address or download data from a network address. Whether uploading or downloading information, the network access request may generate an access attempt by the UE to connect to a data network through an eNB or RNC. However, the UE may perform an ACDC check to determine if the application is allowed to send an access request to the network.

[0056] In block 330, the UE determines that the application is not associated with any of the ACDC categories in the plurality of ACDC categories referenced in the SIB. For example, the application may be uncategorized or may be associated with a category that does not match one of the categories referenced in the SIB. To determine if an ACDC category is associated with a category referenced in the SIB, the UE may reference a set of application parameters. The application parameters may map applications on the UE to ACDC categories used by a HPLMN of the UE. For example, the UE may have an internal mapping of applications executing on the UE to a set of ACDC categories used by the UE. Some applications executing on the UE may not be assigned to any category by the UE's application parameters. For example, a new application, a legacy application, or an application that is uncommon may not have been assigned to a category by a network operator. If an application is not assigned to a category, then it is not associated with any of the categories referenced in the SIB. In some embodiments, there may be applications mapped by an application parameter to an ACDC category that does not match one of the categories referenced by the SIB. For example, the UE may be provisioned with a greater number of ACDC categories than referenced by the SIB. Therefore, an application executing on the UE may be associated with an ACDC category, but that category may not have an associated ACDC access control parameter from the SIB.

[0057] In order to determine if the access attempt is allowed, the UE may apply a default ACDC access control parameter associated with a default ACDC category to the network access request in block 340. For example, an application that is uncategorized or associated with a category that doesn't match an ACDC access control parameter referenced in an SIB may be treated based on a barring rate of a default ACDC access control parameter associated with a default ACDC category. In order to perform an ACDC check, the UE may access a barring rate from the default ACDC access control parameter associated with the default ACDC category. The UE may then bar the network service request with a probability defined in the barring rate. [0058] One example scenario where a default ACDC access control parameter associated with a default ACDC category is used as discussed with reference to Figure 3 is where the UE and the network (e.g., a cell where the UE is camped) are provisioned with a different number of ACDC categories. For example, the network may send a SIB with 4 categories (e.g., ACDC Category 1 , ACDC Category 2, ACDC Category 3, ACDC Category 4), and the UE may have application parameters associating applications with 6 categories (e.g., ACDC Category 1, ACDC Category 2, ACDC Category 3, ACDC Category 4, ACDC Category 5, ACDC Category 6). In some systems, applications in the UE associated with ACDC

Category 5 or ACDC Category 6 may be treated with the same priority as applications in ACDC Category 4 (e.g., the lowest priority category in the SIB). However, in order to prevent interference of applications assigned to ACDC Category 5 or ACDC Category 6 with applications assigned to ACDC category 4, the UE may use a default ACDC category. Thus, applications assigned to ACDC Category 5 or ACDC Category 6 in the UE and uncategorized applications are barred according to the default ACDC access control parameter associated with a default ACDC category. In some embodiments, a network operator may set a barring rate to block all access attempts from such unknown applications. In some embodiments, if the UE is able to use a default ACDC category, but the SIB doesn't provide a barring rate for a default ACDC category, then the UE may map such applications to the lowest priority ACDC category in the SIB.

[0059] Figure 4 illustrates a method of processing a network service request to determine whether to send a request to prolong a signaling connection, according to an embodiment. Beginning in block 410, a UE receives a SIB. The SIB may have been broadcast by an eNB or a RNC through an NB and contain a variety of information about network operations. The SIB may include a plurality of ACDC access control parameters associated with ACDC categories. In some embodiments, the SIB may include a default ACDC access control parameter associated with a default ACDC category as discussed with reference to Figure 3. The ACDC categories may be set by a network operator that operates the eNB or RNC.

Depending on the network operator, the ACDC categories may vary. In some embodiments, a SIB may include multiple distinct sets of ACDC access control parameters. For example, the SIB may include one set of ACDC access control parameters for use by the UE during an idle mode, and a second set of ACDC access control parameters for use by the UE during a connected mode. In some embodiments, the UE may receive the SIB at the radio resource control (RRC) layer and pass the ACDC access control parameters to the non-access stratum (NAS) layer. The UE may then store the ACDC parameters and the related application parameters mapping applications to ACDC categories for use by the NAS layer.

[0060] In block 420, the UE receives a network access request from an application executing on the UE while the UE is in connected mode. For example, an application may request to upload data to a network address or download information from a network address. Whether uploading or downloading information, the UE may recognize that the network access request is in a queue and generate a request to prolong a data signaling connection. Before sending a request to prolong a data signaling connection with a message, the UE may perform an ACDC check to determine whether to send the request.

[0061] In block 430, the UE determines an ACDC category for the application requesting network service. In some embodiments, the UE may include a single set of application parameters associating applications with ACDC categories. However, in some embodiments, the UE may have more than one set of applications parameters. For example, a UE may have one set of application parameters for use in idle mode and a second set of application parameters for use in connected mode. In some embodiments, the UE may have additional sets of application parameters for additional operational modes or circumstances. In block 430, the UE is in connected mode, and will use a set of connected mode application parameters if available. If there is no set of connected mode application parameters, the UE may use a set of application parameters for use in idle mode to determine an ACDC category for the application. In certain situations, the application parameters may not associate the application with an ACDC category and the UE may assign the application to a default ACDC category as described with reference to Figure 3.

[0062] In block 440, the UE determines an ACDC access control parameter for the application based on the ACDC category. In some embodiments, a SIB may provide a single set of ACDC access control parameters that are meant to limit access attempts for various categories of applications while the UE is in idle mode. In some embodiments, a SIB may also send a single set of ACDC access control parameters intended to be used by the UE in both idle and connected modes. In some embodiments, the SIB may include separate sets of ACDC access control parameters for the UE to use in connected mode and idle mode. For example, a set of connected mode ACDC parameters may reference a different number of ACDC categories or may set different barring rates compared to a set of idle mode ACDC categories. If the UE determines that the SIB includes connected mode ACDC access control parameters, the UE may determine a barring rate for the network service request based on the applications category. If the UE determines that the SIB does not include connected mode parameters, the UE may determine a barring rate based for the network service request on the idle mode ACDC access control parameters.

[0063] In block 450, the UE determines, in view of the plurality of application parameters and the plurality of ACDC access control parameters, that the application's service request is allowed. For example, the UE may determine that the application is allowed to access a network associated with an eNB or RNC over the existing signaling connection. For example, the UE may determine based on a barring rate in an ACDC access control parameter of an ACDC category associated with the application whether to request to prolong a signaling connection. In order to perform an ACDC check, the UE may apply the determined barring rate to bar the network service request with a probability defined in the barring rate.

[0064] In block 460, the UE may then determine whether to include a request to prolong a network connection based on the results of the ACDC check. If the UE determines during the ACDC check that the network access is allowed, the UE may generate a network connection message with a request to prolong a signaling connection in block 470. If the UE determines during the ACDC check that the network access is not allowed, the UE may generate a network connection message without a request to prolong a signaling connection in block 475. For example, in a UMTS cell the UE may generate an ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message with a follow-on request pending indicator. In an LTE cell, the UE may generate a TRACKING AREA UPDATE REQUEST message including an active flag to prolong the signaling connection. In block 480, the UE transmits the network connection message to the network with or without the request to prolong a signaling connection as determined in the previous processes.

[0065] In some embodiments, the processes described in blocks 420-460 of Figure 4 may be performed in the NAS layer of the UE. For example, the NAS layer may check the ACDC category of the application in a higher layer that initiated the network service request. The NAS layer may then check if the access is allowed for the pending application by applying the ACDC barring information for idle or connected mode corresponding to the ACDC category of the application. Depending on the outcome of the ACDC check, the NAS layer may generate an ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message with or without a follow-on request pending indicator. Therefore, in some embodiments an ACDC barring check for PS signaling operations, such as setting a follow-on request pending indicator (or an active flag in LTE systems) is performed in the NAS layer. In some embodiments, additional or different ACDC barring checks may be implemented for PS data is performed in the RRC level. This may enable additional access control over applications that have an RRC connection established with the network. Additionally, in the connected mode ACDC a network operator may control the ACDC barring per RRC state. Thus, the UE can perform ACDC barring checks for PS data in the RRC layer as it is aware of the RRC state and ACDC configuration received in system information broadcast.

[0066] One example scenario where an ACDC access control parameter may be used as discussed with reference to Figure 4 is where a UE in a UMTS cell performs an additional check related to ACDC barring before setting a follow-on request pending indicator in an ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message. In some embodiments, the UE may use idle mode ACDC access control parameters to control the setting of the follow-on request pending indicator. In the case that there is a pending service request initiated by an application, the UE may set the follow-on request pending indicator only if access is allowed per the barring information received for the corresponding ACDC category. If the idle mode ACDC access control parameters prohibit the

corresponding application from setting the follow-on request pending indicator in an

ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message for PS domain, the UE may transmit the message without the follow-on request pending indicator. For example, a low priority application may be mapped to the lowest priority idle mode ACDC category and the idle mode ACDC access control parameters may set a high barring rate. Therefore, the low priority application may not be able to initiate a network service with a follow-on request pending indicator. On the other hand, if the network service request is allowed by the ACDC access control parameters, then the UE may set the follow-on request pending indicator and transmit the ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message. If the follow-on request pending indicator is not set in ATTACH REQUEST message or ROUTING AREA UPDATE REQUEST message, the network may release the PS signaling connection and move the UE to idle mode. This may reduce network congestion generated by low priority applications maintaining a connection with follow-on request pending indicators.

[0067] In some embodiments, the UE in a UMTS may receive separate ACDC access control parameters for connected mode ACDC access control to control the setting of the follow-on request pending indicator. In the case that there is a pending service request initiated by an application, the UE may set the follow-on request pending indicator only if access is allowed based on an ACDC check using the barring information received for the corresponding ACDC category. If the connected mode ACDC access control parameters prohibit the corresponding application from setting the follow-on request pending indicator in an ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message for PS domain, the UE may transmit the message without the follow-on request pending indicator. For example, a low priority application may be mapped to a low priority connected mode ACDC category and the connected mode ACDC access control parameters and set a high barring rate. Therefore, the low priority application may not be able to initiate a network service with a follow-on request pending indicator. On the other hand, if the network service request is allowed by the connected mode ACDC access control parameters, then the UE may set the follow-on request pending indicator and transmit the ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message. If the follow-on request pending indicator is not set in ATTACH REQUEST message or ROUTING AREA UPDATE

REQUEST message, the network may release the PS signaling connection and move the UE to idle mode. This may reduce network congestion generated by low priority applications maintaining a connection with follow-on request pending indicators.

[0068] Another example scenario where an ACDC access control parameter may be used as discussed with reference to Figure 4 is where an UE in an LTE cell performs an additional check related to ACDC barring before setting an active flag in a TRACKING AREA

UPDATE REQUEST message. In some embodiments, the UE may use ACDC access control parameters for idle mode ACDC access control in order to control the setting of the active flag. For example, the UE may only set the active flag for a pending user application for which there is a pending service request if the access is allowed according to an idle mode ACDC access control parameter for the idle mode ACDC category associated with the application.

[0069] In some embodiments, the UE in an LTE cell may receive separate ACDC access control parameters for connected mode ACDC access control. In some embodiments, the UE may use ACDC access control parameters for connected mode ACDC access control in order to control the setting of the active flag. For example, the UE may only set the active flag for a pending user application for which there is a pending service request if the access is allowed according to a connected mode ACDC access control parameter for the connected mode ACDC category associated with the application. [0070] Figure 5 is a communication timing diagram that illustrates an example of ACDC control of request to prolong a signaling connection, according to an embodiment. The timing diagram shows communications between a UE 510 and a network 520. In an LTE network, the network 520 may include an eNB, an evolved packet core (EPC) element, and/or other elements of an LTE network. Various communications illustrated in the timing diagram may be processed by one or more elements of the LTE network. In a UMTS network, the network 520 may include a NB, an RNC, a core network element, or other elements of a UMTS network. Various communications illustrated in the timing diagram may be processed by one or more elements of the UMTS network. In some embodiments, the network 520 may include other elements associated with other network configurations. At a first time, the UE 510 has an application category mapping 515. The application category mapping may include a plurality of application parameters associating applications with ACDC categories. For example, the application parameters may define a number of categories, and may include a list of applications assigned to each category. In some embodiments, there may be additional set of application parameters applicable for additional modes of operation of the UE. For example, different sets of application parameters may be used for a UE in an idle mode or various connected modes. In a communication from the network 520, the UE 510 receives a SIB 525. The network may communicate the SIB 525 as a broadcast message to UEs in the network cell (e.g., UE 510). The SIB 525 may include a plurality of ACDC access control parameters. The ACDC access control parameters may define barring rates for applications associated with various ACDC categories. At some time after a SIB 525 is received at the UE 510 containing ACDC access control parameters, an application generates a network service request 530. In the case that the service request from the application 530 is generated during a connection for another network service, the UE 510 may optionally set a follow-on request pending indicator in an ATTACH REQUEST message to the network. For example, as shown in Figure 5, an RRC connection 540 is established. Prior to sending an ATTACH REQUEST, the UE 510 may determine whether to include a follow-on request pending indicator. The UE 510 may perform an ACDC check 545 to determine if access is allowed for the application. For example the UE 510 may perform an ACDC check as described with reference to Figures 3 and 4. If the UE 510 determines that the application access is not allowed, it may continue with the communications illustrated in block 550A. If the UE 510 determines that the network service access is allowed, it may continue with the

communications illustrated in block 550B. [0071 ] In communications block 550A, the UE 510 sends an ATTACH REQUEST 555 A to the network without a follow-on request pending indicator. The UE and the network may then proceed through a series of authentication and ciphering communications 560A to setup NAS security between the UE 510 and the network 520. After completion of the

authentication and ciphering communications 560A, the UE 510 and network 520 may securely deliver packets as protected encrypted messages. The network 520 may then send an attach accept message 565 A to the UE 510 confirming that the connection to the network 520 is complete. At some point in time after the application that initiated the network service access has completed its use of the network, the RRC connection may be released by the network 520 and the UE 510 may return to idle operation in communications 570.

[0072] In communications block 550B, the UE 510 sends an ATTACH REQUEST 555B to the network 520 with a follow-on request pending indicator. The UE 510 and network 520 continue with authentication and ciphering communications 560B as described above. After a secure communication is established, the network 520 sends an attach accept message 565B, but due to the follow-on request pending indication, the network 520 includes a follow-on proceed indication. The follow-on proceed indication enables the application to access network services. The UE may then continue to send a service request 575, to the network 520 for the application. After additional authentication and ciphering communications 580, the network 520 may establish radio bearers for the application and packet data protocol context activation through communications 585 to enable communication from the application executing on the UE 510 to the network 520.

[0073] The timing diagram of Figure 5 is directed toward a UE operating in a UMTS cell and makes reference to an attach message. The UE may perform similar communication, including setting a follow-on request pending indication for a ROUTING AREA UPDATE REQUEST. In addition, while the communications may vary, a UE in an LTE cell may also perform similar communications for setting an active flag for a pending network service request while the UE is in a connected mode.

[0074] While the present disclosure describes a number of embodiments, those skilled in the art will appreciate numerous modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of this present disclosure.

[0075] The following examples pertain to further embodiments of the disclosure. [0076] Example 1 is a UE comprising: a memory device to store a plurality of application parameters, each application parameter of the plurality of application parameters associating an application with an application-specific congestion control for data communication (ACDC) category of a first plurality of ACDC categories; and a processing device, operatively coupled to the memory device, the processing device to: receive a system information block (SIB) referencing a second plurality of ACDC categories and a default ACDC access control parameter associated with a default ACDC category; determine, in view of the plurality of application parameters, that an application executing on the UE is not associated with any category referenced by the SIB; and process a network access request by the application based on the default ACDC access control parameter associated with the default ACDC category.

[0077] In Example 2, in the UE of Example 1 or any of the Examples described herein, the plurality of application parameters associating applications with ACDC categories do not associate the application to any category in the first plurality of ACDC categories.

[0078] In Example 3, in the UE of Example 1 or any of the Examples described herein, the first plurality of ACDC categories has an ACDC category that is not in the second plurality of ACDC categories, and wherein an application parameter associates the application with the ACDC category.

[0079] In Example 4, in the UE of Example 1 or any of the Examples described herein, to process the network access request, the processing device is to: determine a barring rate for the default ACDC category based on the associated default ACDC access control parameter; and apply the barring rate to the network access request.

[0080] In Example 5, in the UE of Example 1 or any of the Examples described herein, the UE further comprises radio frequency circuitry to transmit an access request to an eNB in accordance with long-term evolution radio access technology.

[0081] In Example 6, in the UE of Example 1 or any of the Examples described herein, the UE further comprising radio frequency circuitry to transmit an access request to an RNC in accordance with universal mobile telecommunications system technology.

[0082] In Example 7, in the UE of Example 1 or any of the Examples described herein, the UE further comprises application circuitry to execute the application.

[0083] Example 8, is an apparatus of a UE comprising: a memory device to store a plurality of application parameters, each application parameter of the plurality of application parameters associating an application with an application-specific congestion control for data communication (ACDC) category of a plurality of ACDC categories; a processing device, operatively coupled to the memory device, the processing device to: receive a system information block (SIB) from a radio network controller (RNC), wherein the SIB is transmit through a Node-B (NB) and comprises a plurality of access control parameters associated with the plurality of ACDC categories; receive, in a connected mode of operation, a service request from an application; determine, in view of the plurality of application parameters and the plurality of ACDC access control parameters, that the application is allowed to access, over a signaling connection, a network associated with the RNC; and generate a message including a follow-on request pending indicator to prolong the signaling connection.

[0084] In Example 9, in the apparatus of the UE of Example 8 or any of the Examples described herein, further comprises radio frequency circuitry to transmit the message.

[0085] In Example 10, in the apparatus of the UE of Example 8 or any of the Examples described herein, the message comprises an ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message.

[0086] In Example 11 , in the apparatus of the UE of Example 8 or any of the Examples described herein, to determine that the application is allowed to access the network, the processing device is to: determine an ACDC category associated with the application;

determine a barring rate for the ACDC category based on the ACDC access control parameters; and apply the barring rate to the service request.

[0087] In Example 12, in the apparatus of the UE of Example 8 or any of the Examples described herein, to determine that the application is allowed to access the network, the processing device is to: determine that the application is not associated with any of the plurality of ACDC categories; determine a barring rate for a default ACDC category based on a default ACDC access control parameter; and apply the barring rate of the default ACDC access control parameter to the service request to determine that the access attempt is allowed.

[0088] In Example 13, in the apparatus of the UE of Example 8 or any of the Examples described herein, the plurality of ACDC access control parameters define a first set of barring rates for the connected mode of operation and a second set of barring rates for an idle mode of operation, wherein to determine that the application is allowed to access the network, the processing device is to apply the first set of barring rates.

[0089] Example 14 is a UE comprising: a memory device to store a plurality of application parameters, each application parameter of the plurality of application parameters associating an application with an application-specific congestion control for data communication (ACDC) category of a plurality of ACDC categories; a processing device, operatively coupled to the memory device, the processing device to: receive a system information block (SIB) from an evolved Node-B (eNB), wherein the SIB comprises a plurality of ACDC access control parameters associated with the plurality of ACDC categories; receive, in a connected mode of operation, a service request from an application;

determine, in view of the plurality of application parameters and the plurality of ACDC access control parameters, that the application is allowed to access, over a signaling connection, a network associated with the eNB; and generate a TRACKING AREA UPDATE REQUEST message including an active flag to prolong the signaling connection.

[0090] In Example 15, in the apparatus of the UE of Example 14 or any of the Examples described herein, the UE further comprises radio frequency circuitry to transmit the

TRACKING AREA UPDATE REQUEST message.

[00 1] In Example 16, in the apparatus of the UE of Example 14 or any of the Examples described herein, to determine that the application is allowed to access the network, the processing device is to: determine an ACDC category associated with the application;

[0092] In Example 17, in the apparatus of the UE of Example 14 or any of the Examples described herein, wherein to determine that the application is allowed to access the network the processing device is to: determine that the application is not associated with any of the plurality of ACDC categories; determine a barring rate for a default ACDC category based on a default ACDC access control parameter; and apply the barring rate of the default ACDC access control parameter associated with the default ACDC category to the service request to determine that the access attempt is allowed.

[0093] In Example 18, in the apparatus of the UE of Example 14 or any of the Examples described herein, the plurality of ACDC access control parameters define a first set of barring rates for the connected mode of operation and a second set of barring rates for an idle mode of operation, wherein to determine that the application is allowed to access the network, the processing device is to apply the first set of barring rates.

[0094] Example 19 is an application specific congestion control for data communication (ACDC) enabled radio network controller (RNC) comprising: a processing device to: generate a first plurality of ACDC access control parameters associated with a plurality of ACDC categories, wherein the first plurality of ACDC access control parameters are to be used by user equipment (UE) in idle mode to determine whether an access attempt is allowed;

generate a second plurality of ACDC access control parameters associated with the plurality of ACDC categories, wherein the second plurality of ACDC access control parameters are to be used by the UE in connected mode to determine whether to include a follow-on request pending indicator in an ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message; and generate a system information block (SIB) comprising the first plurality of ACDC access control parameters and the second plurality of ACDC access control parameters; and radio frequency circuitry coupled with the processing device, the radio frequency circuitry to transmit the SIB to the UE.

[0095] In Example 20, in the RNC of Example 19 or any of the Examples described herein, the processing device is further to receive control data from a network operator that directs the processing device to generate the first plurality of ACDC access control parameters and the second plurality of ACDC access control parameters.

[0096] In Example 21 , in the RNC of Example 19 or any of the Examples described herein, the processing device is further to: detect a change in a congestion level of the network; and modify a barring rate associated with at least one of the second plurality of ACDC access control parameters.

[0097] Example 22 is an apparatus of an application specific congestion control for data communication (ACDC) enabled evolved Node-B (eNB) comprising: a processing device to: generate a first plurality of ACDC access control parameters associated with a first plurality of ACDC categories, wherein the first plurality of ACDC access control parameters are to be used by a user equipment (UE) in idle mode to determine if an access attempt is allowed; generate a second plurality of ACDC access control parameters associated with a second plurality of ACDC categories, wherein the second plurality of ACDC access control parameters are to be used by the UE in connected mode to determine whether to set an active flag in a TRACKING AREA UPDATE REQUEST message; and generate a system information block (SIB) comprising the first plurality of ACDC access control parameters and the second plurality of ACDC access control parameters; and radio frequency circuitry coupled with the processing device, the radio frequency circuitry to transmit the SIB to the UE.

[0098] In Example 23, in the apparatus of the ACDC enabled eNB of Example 22 or any of the Examples described herein, the processing device is further to receive control data from a network operator that directs the processing device to generate the first plurality of ACDC access control parameters and the second plurality of ACDC access control parameters.

[0099] In Example 24, in the apparatus of the ACDC enabled eNB of Example 22 or any of the Examples described herein, the processing device is further to: detect a change in a congestion level of the network; and modify a barring rate associated with at least one of the second plurality of ACDC access control parameters.

[00100] Example 25 is an application specific congestion control for data communication (ACDC) enabled system comprising: a processing device to: determine a plurality of ACDC access control parameters associated with a plurality of ACDC categories; determine a default ACDC access control parameter associated with a default ACDC category, wherein the default ACDC access control parameter is to be used by a user equipment (UE) to determine whether an access attempt by an application that is not associated with any of the ACDC categories is allowed; and generate a system information block (SIB) comprising the plurality of ACDC access control parameters and the default ACDC access control parameter associated with the default ACDC category; and radio frequency circuitry coupled with the processing device, the radio frequency circuitry to transmit the SIB to the UE.

[00101] In Example 26, in the ACDC enabled system of Example 25 or any of the Examples described herein, the processing device is further to receive control data from a network operator that directs the processing device to generate the plurality of ACDC access control parameters.

[00102] In Example 27, in the ACDC enabled system of Example 25 or any of the Examples described herein, the processing device is further to: detect a change of a level of network congestion; and modify a barring rate for an ACDC category of the plurality of ACDC categories.

[00103] In Example 28, in the ACDC enabled system of Example 25 or any of the Examples described herein, the radio frequency circuitry operates in accordance with long-term evolution radio access technology.

[00104] In Example 29, in the ACDC enabled system of Example 25 or any of the Examples described herein, the radio frequency circuitry operates in accordance with universal mobile telecommunications system technology.

[00105] Example 30 is a method comprising: storing, by a user equipment (UE), a plurality of application parameters, each application parameter of the plurality of application parameters associating an application with an application-specific congestion control for data communication (ACDC) category of a first plurality of ACDC categories; receiving a system information block (SIB) referencing a second plurality of ACDC categories and a default ACDC access control parameter associated with a default ACDC category; determining, in view of the plurality of application parameters, that an application executing on the UE is not associated with any category referenced by the SIB; and processing a network access request by the application based on the default ACDC access control parameter associated with the default ACDC category.

[00106] In Example 31, in the method of Example 30 or any of the Examples described herein, the plurality of application parameters do not associate the application to any category in the first plurality of ACDC categories.

[00107] In Example 32, in the method of Example 30 or any of the Examples described herein, the first plurality of ACDC categories has an ACDC category that is not in the second plurality of ACDC categories, and wherein an application parameter associates the application with the ACDC category.

[00108] In Example 33, in the method of Example 30 or any of the Examples described herein, processing the network access request comprises: determining a barring rate for the default ACDC category based on the associated default ACDC access control parameter; and applying the barring rate to the network access request.

[00109] In Example 34, the method of Example 30 or any of the Examples described herein, further comprises transmitting, using radio frequency circuitry, an access request to an eNB in accordance with long-term evolution radio access technology.

[00110] In Example 35, the method of Example 30 or any of the Examples described herein, further comprises transmitting, using radio frequency circuitry, an access request to an RNC in accordance with universal mobile telecommunications system technology.

[0011 1] In Example 36, the method of Example 30 or any of the Examples described herein, further comprises executing, by the processing device, the application on the UE.

[00112] Example 37 is a method comprising: storing, by a user equipment (UE) a plurality of application parameters, each application parameter of the plurality of application parameters associating an application with an application-specific congestion control for data

communication (ACDC) category of a plurality of ACDC categories; receiving a system information block (SIB) from a radio network controller (RNC), wherein the SIB is transmit through a Node-B (NB) and comprises a plurality of access control parameters associated with the plurality of ACDC categories; receiving, in a connected mode of operation, a service request from an application; determining, in view of the plurality of application parameters and the plurality of ACDC access control parameters, that the application is allowed to access, over a signaling connection, a network associated with the RNC; and generating a message including a follow-on request pending indicator to prolong the signaling connection.

[00113] In Example 38, the method of Example 37 or any of the Examples described herein, further comprises transmitting the message using radio frequency circuitry.

[00114] In Example 39, in the method of Example 37 or any of the Examples described herein, the message comprises an ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message.

[001 15] In Example 40, in the method of Example 37 or any of the Examples described herein, further comprises determining that the application is allowed to access the network comprises: determining an ACDC category associated with the application; determining a barring rate for the ACDC category based on the ACDC access control parameters; and applying the barring rate to the service request.

[00116] In Example 41, in the method of Example 37 or any of the Examples described herein, determining that the application is allowed to access the network comprises:

determining that the application is not associated with any of the plurality of ACDC categories; determining a barring rate for a default ACDC category based on a default ACDC access control parameter; and applying the barring rate of the default ACDC access control parameter to the service request to determine that the access attempt is allowed.

[00117] In Example 42, in the method of Example 37 or any of the Examples described herein, the plurality of ACDC access control parameters define a first set of barring rates for the connected mode of operation and a second set of barring rates for an idle mode of operation, wherein determining that the application is allowed to access the network comprises applying the first set of barring rates.

[00118] Example 43 is a method comprising: storing, by a user equipment (UE) a plurality of application parameters, each application parameter of the plurality of application parameters associating an application with an application-specific congestion control for data

communication (ACDC) category of a plurality of ACDC categories; receiving a system information block (SIB) from an evolved Node-B (eNB), wherein the SIB comprises a plurality of ACDC access control parameters associated with the plurality of ACDC categories; receiving, in a connected mode of operation, a service request from an application; determining, in view of the plurality of application parameters and the plurality of ACDC access control parameters, that the application is allowed to access, over a signaling connection, a network associated with the eNB; and generating a TRACKING AREA

UPDATE REQUEST message including an active flag to prolong the signaling connection.

[001 19] In Example 44, the method of Example 43 or any of the Examples described herein, further comprises transmitting the TRACKING AREA UPDATE REQUEST message using radio frequency circuitry.

[00120] In Example 45, in the method of Example 43 or any of the Examples described herein, determining that the application is allowed to access the network comprises:

determining an ACDC category associated with the application; determining a barring rate for the ACDC category based on the ACDC access control parameters; and applying the barring rate to the service request.

[00121] In Example 46, in the method of Example 43 or any of the Examples described herein, determining that the application is allowed to access the network comprises:

determining that the application is not associated with any of the plurality of ACDC categories; determining a barring rate for a default ACDC category based on a default ACDC access control parameter; and applying the barring rate of the default ACDC access control parameter associated with the default ACDC category to the service request to determine that the access attempt is allowed.

[00122] In Example 47, in the method of Example 43 or any of the Examples described herein, the plurality of ACDC access control parameters define a first set of barring rates for the connected mode of operation and a second set of barring rates for an idle mode of operation, wherein determining that the application is allowed to access the network, comprises applying the first set of barring rates.

[00123] Example 48 is a method comprising: generating, by a processing device, a first plurality of ACDC access control parameters associated with a plurality of ACDC categories, wherein the first plurality of ACDC access control parameters are to be used by user equipment (UE) in idle mode to determine whether an access attempt is allowed; generating, by the processing device, a second plurality of ACDC access control parameters associated with the plurality of ACDC categories, wherein the second plurality of ACDC access control parameters are to be used by the UE in connected mode to determine whether to include a follow-on request pending indicator in an ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message; and generating, by the processing device, a system information block (SIB) comprising the first plurality of ACDC access control parameters and the second plurality of ACDC access control parameters; and transmitting, by radio frequency circuitry coupled with the processing device, the SIB to the UE.

[00124] In Example 49, the method of Example 48 further comprises receiving control data from a network operator that directs the processing device to generate the first plurality of ACDC access control parameters and the second plurality of ACDC access control parameters.

[00125] In Example 50, the method of Example 48 or any of the Examples described herein, further detecting a change in a congestion level of the network; and modifying a barring rate associated with at least one of the second plurality of ACDC access control parameters.

[00126] Example 51 is a method comprising: generating, by a processing device, a first plurality of ACDC access control parameters associated with a first plurality of ACDC categories, wherein the first plurality of ACDC access control parameters are to be used by a user equipment (UE) in idle mode to determine if an access attempt is allowed; generating, by the processing device, a second plurality of ACDC access control parameters associated with a second plurality of ACDC categories, wherein the second plurality of ACDC access control parameters are to be used by the UE in connected mode to determine whether to set an active flag in a TRACKING AREA UPDATE REQUEST message; and generating, by the processing device, a system information block (SIB) comprising the first plurality of ACDC access control parameters and the second plurality of ACDC access control parameters; and transmitting, by radio frequency circuitry coupled with the processing device, the SIB to the UE.

[00127] In Example 52, the method of Example 51 or any of the Examples described herein, further comprises receiving control data from a network operator that directs the processing device to generate the first plurality of ACDC access control parameters and the second plurality of ACDC access control parameters.

[00128] In Example 53, the method of Example 51 or any of the Examples described herein, further comprises detecting a change in a congestion level of the network; and modifying a barring rate associated with at least one of the second plurality of ACDC access control parameters. [00129] Example 54 is a method comprising: determining, by a processing device, a plurality of ACDC access control parameters associated with a plurality of ACDC categories; determining, by the processing device, a default ACDC access control parameter associated with a default ACDC category, wherein the default ACDC access control parameter is to be used by a user equipment (UE) to determine whether an access attempt by an application that is not associated with any of the ACDC categories is allowed; and generating, by the processing device, a system information block (SIB) comprising the plurality of ACDC access control parameters and the default ACDC access control parameter associated with the default ACDC category; and transmitting, by radio frequency circuitry coupled with the processing device, the SIB to the UE.

[00130] In Example 55, the method of Example 54 or any of the Examples described herein, further comprises receiving control data from a network operator that directs the processing device to generate the plurality of ACDC access control parameters.

[00131] In Example 56, the method of Example 54 or any of the Examples described herein, further comprises detecting a change of a level of network congestion; and modifying a barring rate for an ACDC category of the plurality of ACDC categories.

[00132] In Example 57, in the method of Example 54 or any of the Examples described herein, transmitting the SIB is performed in accordance with long-term evolution radio access technology.

[00133] In Example 58, in the method of Example 54 or any of the Examples described herein, transmitting the SIB is performed in accordance with universal mobile

telecommunications system technology.

[00134] Example 59 is a machine readable medium including code, when executed, to cause a machine to perform the method of any one of Examples 30 to 58.

[00135] Example 60 is an apparatus comprising means for performing the method of any one of claims 30 to 58

[00136] Example 61 is an apparatus comprising a processor configured to perform the method of any one of claims 30 to 58.

[00137] Example 62 is an apparatus comprising: means for storing, by a user equipment (UE) a plurality of application parameters, each application parameter of the plurality of application parameters associating an application with an application-specific congestion control for data communication (ACDC) category of a plurality of ACDC categories; means for receiving a system information block (SIB) from an evolved Node-B (eNB), wherein the SIB comprises a plurality of ACDC access control parameters associated with the plurality of ACDC categories; means for receiving, in a connected mode of operation, a service request from an application; means for determining, in view of the plurality of application parameters and the plurality of ACDC access control parameters, that the application is allowed to access, over a signaling connection, a network associated with the eNB; means for generating a TRACKING AREA UPDATE REQUEST message including an active flag to prolong the signaling connection; and means for transmitting the TRACKING AREA UPDATE REQUEST message using radio frequency circuitry.

[00138] In Example 63, in the apparatus of claim 62 or any of the Examples described herein, means for determining that the application is allowed to access the network comprises: means for determining an ACDC category associated with the application; means for determining a barring rate for the ACDC category based on the ACDC access control parameters; and applying the barring rate to the service request.

[00139] In Example 64, in the apparatus of claim 62 or any of the Examples described herein, wherein means for determining that the application is allowed to access the network comprise: means for determining that the application is not associated with any of the plurality of ACDC categories; means for determining a barring rate for a default ACDC category based on a default ACDC access control parameter; and means for applying the barring rate of the default ACDC access control parameter associated with the default ACDC category to the service request to determine that the access attempt is allowed.

[00140] In Example 65, in the apparatus of Example 62 or any of the Examples described herein, the plurality of ACDC access control parameters define a first set of barring rates for the connected mode of operation and a second set of barring rates for an idle mode of operation, wherein means for determining that the application is allowed to access the network, comprises means for applying the first set of barring rates.

[00141] In the description herein, numerous specific details are set forth, such as examples of specific types of processors and system configurations, specific hardware structures, specific architectural and micro architectural details, specific register configurations, specific instruction types, specific system components, specific measurements/heights, specific processor pipeline stages and operation etc. in order to provide a thorough understanding of the present disclosure. It will be apparent, however, that these specific details need not be employed to practice the present invention. In other instances, well known components or methods, such as specific and alternative processor architectures, specific logic circuits/code for described algorithms, specific firmware code, specific interconnect operation, specific logic configurations, specific manufacturing techniques and materials, specific compiler implementations, specific expression of algorithms in code, specific power down and gating techniques/logic and other specific operational details of computer system have not been described in detail in order to avoid unnecessarily obscuring the present invention.

[00142] Instructions used to program logic to perform embodiments of the disclosure can be stored within a memory in the system, such as DRAM, cache, flash memory, or other storage. Furthermore, the instructions can be distributed via a network or by way of other computer readable media. Thus a machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), but is not limited to, floppy diskettes, optical disks, Compact Disc, Read-Only Memory (CD-ROMs), and magneto-optical disks, Read-Only Memory (ROMs), Random Access Memory (RAM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic or optical cards, flash memory, or a tangible, machine-readable storage used in the transmission of information over the Internet via electrical, optical, acoustical or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.). Accordingly, the computer-readable medium includes any type of tangible machine-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer).

[00143] A module as used herein refers to any combination of hardware, software, and/or firmware. As an example, a module includes hardware, such as a micro-controller, associated with a non-transitory medium to store code adapted to be executed by the micro-controller. Therefore, reference to a module, in one embodiment, refers to the hardware, which is specifically configured to recognize and/or execute the code to be held on a non-transitory medium. Furthermore, in another embodiment, use of a module refers to the non-transitory medium including the code, which is specifically adapted to be executed by the

microcontroller to perform predetermined operations. And as can be inferred, in yet another embodiment, the term module (in this example) may refer to the combination of the microcontroller and the non-transitory medium. Often module boundaries that are illustrated as separate commonly vary and potentially overlap. For example, a first and a second module may share hardware, software, firmware, or a combination thereof, while potentially retaining some independent hardware, software, or firmware. In one embodiment, use of the term logic includes hardware, such as transistors, registers, or other hardware, such as programmable logic devices.

[00144] Use of the phrase 'configured to,' in one embodiment, refers to arranging, putting together, manufacturing, offering to sell, importing and/or designing an apparatus, hardware, logic, or element to perform a designated or determined task. In this example, an apparatus or element thereof that is not operating is still 'configured to' perform a designated task if it is designed, coupled, and/or interconnected to perform said designated task. As a purely illustrative example, a logic gate may provide a 0 or a 1 during operation. But a logic gate 'configured to' provide an enable signal to a clock does not include every potential logic gate that may provide a 1 or 0. Instead, the logic gate is one coupled in some manner that during operation the 1 or 0 output is to enable the clock. Note once again that use of the term

'configured to' does not require operation, but instead focuses on the latent state of an apparatus, hardware, and/or element, where in the latent state the apparatus, hardware, and/or element is designed to perform a particular task when the apparatus, hardware, and/or element is operating.

[00145] Furthermore, use of the phrases 'to,' 'capable of/to,' and or Operable to,' in one embodiment, refers to some apparatus, logic, hardware, and/or element designed in such a way to enable use of the apparatus, logic, hardware, and/or element in a specified manner. Note as above that use of to, capable to, or operable to, in one embodiment, refers to the latent state of an apparatus, logic, hardware, and/or element, where the apparatus, logic, hardware, and/or element is not operating but is designed in such a manner to enable use of an apparatus in a specified manner.

[00146] The embodiments of methods, hardware, software, firmware or code set forth above may be implemented via instructions or code stored on a machine-accessible, machine readable, computer accessible, or computer readable medium which are executable by a processing element. A non-transitory machine-accessible/readable medium includes any mechanism that provides (i.e., stores and/or transmits) information in a form readable by a machine, such as a computer or electronic system. For example, a non-transitory machine- accessible medium includes random-access memory (RAM), such as static RAM (SRAM) or dynamic RAM (DRAM); ROM; magnetic or optical storage medium; flash memory devices; electrical storage devices; optical storage devices; acoustical storage devices; other form of storage devices for holding information received from transitory (propagated) signals (e.g., carrier waves, infrared signals, digital signals); etc., which are to be distinguished from the non-transitory mediums that may receive information there from.

[00147] Instructions used to program logic to perform embodiments of the invention may be stored within a memory in the system, such as DRAM, cache, flash memory, or other storage. Furthermore, the instructions can be distributed via a network or by way of other computer readable media. Thus a machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), but is not limited to, floppy diskettes, optical disks, Compact Disc, Read-Only Memory (CD-ROMs), and magneto-optical disks, Read-Only Memory (ROMs), Random Access Memory (RAM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic or optical cards, flash memory, or a tangible, machine-readable storage used in the transmission of information over the Internet via electrical, optical, acoustical or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.). Accordingly, the computer-readable medium includes any type of tangible machine-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer)

[00148] Reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" on "in some embodiments" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[00149] In the foregoing specification, a detailed description has been given with reference to specific exemplary embodiments. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the disclosure as set forth in the appended claims. The specification and drawings are,

accordingly, to be regarded in an illustrative sense rather than a restrictive sense. Furthermore, the foregoing use of embodiment and other exemplarily language does not necessarily refer to the same embodiment or the same example, but may refer to different and distinct

embodiments, as well as potentially the same embodiment.

[00150] Some portions of the detailed description are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical

manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers or the like. The blocks described herein can be hardware, software, firmware or a combination thereof.

[00151] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as "defining," "receiving," "determining," "issuing," "linking," "associating," "obtaining," "authenticating," "prohibiting," "executing," "requesting," "communicating," or the like, refer to the actions and processes of a computing system, or similar electronic computing device, that

manipulates and transforms data represented as physical (e.g., electronic) quantities within the computing system's registers and memories into other data similarly represented as physical quantities within the computing system memories or registers or other such information storage, transmission or display devices.

[00152] The words "example" or "exemplary" are used herein to mean serving as an example, instance or illustration. Any aspect or design described herein as "example' or "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs. Rather, use of the words "example" or "exemplary" is intended to present concepts in a concrete fashion. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or." That is, unless specified otherwise, or clear from context, "X includes A or B" is intended to mean any of the natural inclusive permutations. That is, if X includes A; X includes B; or X includes both A and B, then "X includes A or B" is satisfied under any of the foregoing instances. In addition, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more" unless specified otherwise or clear from context to be directed to a singular form.

Moreover, use of the term "an embodiment" or "one embodiment" or "an implementation" or "one implementation" throughout is not intended to mean the same embodiment or implementation unless described as such. Also, the terms "first," "second," "third," "fourth," etc. as used herein are meant as labels to distinguish among different elements and may not necessarily have an ordinal meaning according to their numerical designation.

Claims

Claims What is claimed is:

1. A user equipment (UE) comprising:

a memory device to store a plurality of application parameters, each application parameter of the plurality of application parameters associating an application with an application-specific congestion control for data communication (ACDC) category of a first plurality of ACDC categories; and

a processing device, operatively coupled to the memory device, the processing device to:

receive a system information block (SIB) referencing a second plurality of ACDC categories and a default ACDC access control parameter associated with a default ACDC category;

determine, in view of the plurality of application parameters, that an application executing on the UE is not associated with any category referenced by the SIB; and

process a network access request by the application based on the default ACDC access control parameter associated with the default ACDC category.

2. The UE of claim 1, wherein the plurality of application parameters associating applications with ACDC categories do not associate the application to any category in the first plurality of ACDC categories.

3. The UE of claim 1 , wherein the first plurality of ACDC categories has an ACDC category that is not in the second plurality of ACDC categories, and wherein an application parameter associates the application with the ACDC category.

4. The UE of claim 1, 2 or 3, wherein to process the network access request, the processing device is to:

determine a barring rate for the default ACDC category based on the associated default ACDC access control parameter; and

apply the barring rate to the network access request.

5. The UE of claim 1, further comprising radio frequency circuitry to transmit an access request to an eNB in accordance with long-term evolution radio access technology.

6. The UE of claim 1 , further comprising radio frequency circuitry to transmit an access request to an RNC in accordance with universal mobile telecommunications system technology.

7. The UE of claim 1, 2 or 3 further comprising application circuitry to execute the application.

8. An apparatus of a user equipment (UE) comprising:

a memory device to store a plurality of application parameters, each application parameter of the plurality of application parameters associating an application with an application-specific congestion control for data communication (ACDC) category of a plurality of ACDC categories;

process a system information block (SIB) received at the UE from a radio network controller (RNC), wherein the SIB is transmit through a Node-B (NB) and comprises a plurality of access control parameters associated with the plurality of ACDC categories;

receive, in a connected mode of operation, a service request from an application;

determine, in view of the plurality of application parameters and the plurality of ACDC access control parameters, that the application is allowed to access, over a signaling connection, a network associated with the RNC; and

generate a message including a follow-on request pending indicator to prolong the signaling connection.

9. The apparatus of the UE of claim 8, further comprising radio frequency circuitry to transmit the message.

10. The apparatus of the UE of claim 8, wherein the message comprises an ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message.

1 1. The apparatus of the UE of claim 8, 9 or 10 wherein to determine that the application is allowed to access the network, the processing device is to:

determine an ACDC category associated with the application;

determine a barring rate for the ACDC category based on the ACDC access control parameters; and

apply the barring rate to the service request.

12. The apparatus of the UE of claim 8, 9 or 10 wherein to determine that the application is allowed to access the network, the processing device is to:

determine that the application is not associated with any of the plurality of ACDC categories;

determine a barring rate for a default ACDC category based on a default ACDC access control parameter; and

apply the barring rate of the default ACDC access control parameter to the service request to determine that the access attempt is allowed.

13. The apparatus of the UE of claim 8, 9 or 10 wherein the plurality of ACDC access control parameters define a first set of barring rates for the connected mode of operation and a second set of barring rates for an idle mode of operation, wherein to determine that the application is allowed to access the network, the processing device is to apply the first set of barring rates.

14. An apparatus of a user equipment (UE) comprising:

process a system information block (SIB) received at the UE from an evolved Node-B (eNB), wherein the SIB comprises a plurality of ACDC access control parameters associated with the plurality of ACDC categories;

receive, in a connected mode of operation, a service request from an application; determine, in view of the plurality of application parameters and the plurality of ACDC access control parameters, that the application is allowed to access, over a signaling connection, a network associated with the eNB; and

generate a TRACKING AREA UPDATE REQUEST message including an active flag to prolong the signaling connection.

15. The apparatus of the UE of claim 14, further comprising radio frequency circuitry to transmit the TRACKING AREA UPDATE REQUEST message.

16. The apparatus of the UE of claim 14 or 15 wherein to determine that the application is allowed to access the network, the processing device is to:

determine an ACDC category associated with the application;

apply the barring rate to the service request.

17. The apparatus of the UE of claim 14 or 15 wherein to determine that the application is allowed to access the network the processing device is to:

aPPly the barring rate of the default ACDC access control parameter associated with the default ACDC category to the service request to determine that the access attempt is allowed.

18. The apparatus of the UE of claim 14 or 15 wherein the plurality of ACDC access control parameters define a first set of barring rates for the connected mode of operation and a second set of barring rates for an idle mode of operation, wherein to determine that the application is allowed to access the network, the processing device is to apply the first set of barring rates.

19. An application specific congestion control for data communication (ACDC) enabled radio network controller (RNC) comprising:

a processing device to: generate a first plurality of ACDC access control parameters associated with a plurality of ACDC categories, wherein the first plurality of ACDC access control parameters are to be used by user equipment (UE) in idle mode to determine whether an access attempt is allowed;

generate a second plurality of ACDC access control parameters associated with the plurality of ACDC categories, wherein the second plurality of ACDC access control parameters are to be used by the UE in connected mode to determine whether to include a follow-on request pending indicator in an ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message; and

generate a system information block (SIB) comprising the first plurality of ACDC access control parameters and the second plurality of ACDC access control parameters; and

radio frequency circuitry coupled with the processing device, the radio frequency circuitry to transmit the SIB to the UE.

20. The RNC of claim 19, wherein the processing device is further to receive control data from a network operator that directs the processing device to generate the first plurality of ACDC access control parameters and the second plurality of ACDC access control parameters.

21. The RNC of claim 19 or 20, wherein the processing device is further to:

detect a change in a congestion level of the network; and

modify a barring rate associated with at least one of the second plurality of ACDC access control parameters.

22. An apparatus of an application specific congestion control for data communication (ACDC) enabled evolved Node-B (eNB) comprising:

a processing device to:

generate a first plurality of ACDC access control parameters associated with a first plurality of ACDC categories, wherein the first plurality of ACDC access control parameters are to be used by a user equipment (UE) in idle mode to determine if an access attempt is allowed;

generate a second plurality of ACDC access control parameters associated with a second plurality of ACDC categories, wherein the second plurality of ACDC access control parameters are to be used by the UE in connected mode to determine whether to set an active flag in a TRACKING AREA UPDATE REQUEST message; and generate a system information block (SIB) comprising the first plurality of ACDC access control parameters and the second plurality of ACDC access control parameters; and

23. The apparatus of the ACDC enabled eNB of claim 22, wherein the processing device is further to receive control data from a network operator that directs the processing device to generate the first plurality of ACDC access control parameters and the second plurality of ACDC access control parameters.

24. The apparatus of the ACDC enabled eNB of claim 22 or 23, wherein the processing device is further to:

detect a change in a congestion level of the network; and

25. An application specific congestion control for data communication (ACDC) enabled system comprising:

a processing device to:

determine a plurality of ACDC access control parameters associated with a plurality of ACDC categories;

determine a default ACDC access control parameter associated with a default ACDC category, wherein the default ACDC access control parameter is to be used by a user equipment (UE) to determine whether an access attempt by an application that is not associated with any of the ACDC categories is allowed; and

generate a system information block (SIB) comprising the plurality of ACDC access control parameters and the default ACDC access control parameter associated with the default ACDC category; and

26. The system of claim 25, wherein the processing device is further to receive control data from a network operator that directs the processing device to generate the plurality of ACDC access control parameters.

27. The system of claim 25, wherein the processing device is further to:

detect a change of a level of network congestion; and

modify a barring rate for an ACDC category of the plurality of ACDC categories.

28. The system of claim 25, 26 or 27 wherein the radio frequency circuitry operates in accordance with long-term evolution radio access technology.

29. The system of claim 25, 26, or 27 wherein the radio frequency circuitry operates in accordance with universal mobile telecommunications system technology.