Signaling connection admission control in a wireless network

A method and apparatus are described for determining whether to admit a user equipment (UE) in response to an indicated admission delay. By using a random access procedure, a radio access network (RAN) may receive a radio resource control (RRC) connection request message from the UE that includes an establishment cause indicating the admission delay of the UE. The determination may be based on loading and not on delay. The UE may be in an idle state prior to the RAN receiving the RRC connection request message.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
CROSS REFERENCES TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No. 12/953,684, filed Nov. 24, 2010, which is a continuation of U.S. patent application Ser. No. 12/551,672, filed Sep. 1, 2009, now U.S. Pat. No. 7,865,190, which is a continuation of U.S. patent application Ser. No. 11/974,380, filed Oct. 12, 2007, now U.S. Pat. No. 7,583,970, which is a continuation of U.S. patent application Ser. No. 11/471,454, filed on Jun. 19, 2006, now U.S. Pat. No. 7,283,825, which is a continuation of U.S. patent application Ser. No. 11/042,410 filed Jan. 25, 2005, now U.S. Pat. No. 7,065,366, which is a continuation of U.S. patent application Ser. No. 10/640,291, filed on Aug. 13, 2003, now U.S. Pat. No. 6,868,273, which is a continuation of U.S. patent application Ser. No. 10/264,775, filed on Oct. 4, 2002, which is now U.S. Pat. No. 6,631,269, which claims benefit of U.S. Provisional Application No. 60/382,811, filed on May 23, 2002, which are incorporated by reference as if fully set forth herein.

BACKGROUND OF THE INVENTION

The present invention relates to a wireless network where User Equipment (UE) communicates with a radio access network (RAN).

A control plane may be used for all control signaling between the UE and the RAN. A user plane may be used to transmit and receive all user information. Common resources and dedicated resources are defined in a cell for the uplink and the downlink transmission between UEs and the RAN. For example, a Random Access Channel (RACH) and a Forward Access Channel (FACH) could represent common transport channels for the uplink and the downlink, respectively. The RACH is a contention-based uplink transport channel, where a dynamic persistence level parameter controls the rate at which a UE accesses the RACH.

A UE is said to be in IDLE mode when no connection to the RAN exists, for example, following a power-up of a UE. When a signaling connection is established, i.e. control plane connection, a UE is said to be in CONNECTED mode. Once in connected mode, both control plane signaling and user plane information can be exchanged between the UE and the RAN.

An idle mode UE requests a control plane signaling connection by transmitting a CONNECTION REQUEST message over a common channel, such as the RACH. An establishment cause may be included in the connection request message to inform the RAN of the reason why the UE is requesting the connection. The RAN can admit or reject the UE's request for a signaling connection. In the former case, the UE can be admitted for signaling over common resources (CELL_FACH state) or signaling over dedicated resources (CELL_DCH state). A Call Admission Control (CAC) algorithm may be used to evaluate the allocation of dedicated resources for the uplink and/or downlink transmission between a UE and the RAN.

There is currently, however, no available methods for determining whether a UE should be admitted for a control plane signaling connection and, if admitted, should the UE be admitted for signaling over common resources or dedicated resources. Some current systems simply always admit UEs to common resources regardless of the common resources' level of congestion, thereby arbitrarily increasing congestion and often causing the UE to experience significant delay in the exchange of signaling information.

A method is therefore needed to determine whether a UE should be admitted for control plane signaling and, if admitted, whether the UE should be admitted for signaling over common resources or dedicated resources.

SUMMARY

The invention is a method for admission control of control plane signaling connection requests. The admission control method determines whether to accept or reject a UE for a control plane signaling connection. In the former case, the method determines whether the UE will be admitted for signaling over common resources or dedicated resources. In the latter case, the UE is denied access to the network and remains in its idle state.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a method for admission control of control-plane signaling connection requests in accordance with the preferred embodiment of the invention.

FIG. 2 is a method for evaluating whether a signaling connection will be admitted to common resources in accordance with the preferred embodiment of the invention.

 DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

A flow diagram of the method of the present invention is shown in FIG. 1 and indicated generally with the numeral 10. The method 10 is for controlling control plane signaling connection admission in a wireless network. The method 10 begins when the RAN receives a control plane signaling connection request from an idle UE (step 12). Admission of the signaling connection request is first evaluated for whether the connection should be admitted to common resources (step 14).

Admission to common resources is evaluated based on the predicted condition of uplink and downlink common resources; in terms of the RACH, (or any equivalent uplink common channel), and the FACH, (or similarly any equivalent downlink common channel). The admission to common resources may also be evaluated based on the establishment cause, if available, included in the signaling connection request message. For each possible establishment cause, different conditions of RACH and FACH are defined for admission to common resources.

To evaluate the admission of a signaling connection over common resources (step 14), the method 10 predicts the congestion/performance of common resources for the admitted UE and all other UEs within the cell that are transmitting over common resources. If the predicted conditions fall below predetermined maximum values, the signaling connection request is admitted to common resources. If not, the signaling connection request can be evaluated for admission to dedicated resources in step 15. An admission for a signaling connection over common resources implies that a UE will be in a CELL_FACH state following a connection setup, whereas a UE admitted to dedicated resources pursuant to a low quality signaling connection will be in a CELL_DCH state following a connection setup.

Where admission to common resources has been denied in step 14, the admission to dedicated resources is evaluated (step 15) by invoking the Call Admission Control (CAC) method within the RAN. The CAC evaluates the possibility of allocating dedicated resources for the exchange of information between the RAN and a UE. When the CAC receives a request for resources, it replies by either allocating the requested resources or rejecting the request. If the CAC allocates dedicated resources, the UE is admitted for a signaling connection with the allocated dedicated resources (step 22). Otherwise, the UE is rejected for a signaling connection (step 21).

In a preferred embodiment, the evaluation of admission to dedicated resources (step 15) can be establishment cause specific, if the establishment cause is included in the connection request message. For example, for a low priority establishment cause, the admission to dedicated resources could be rejected without having invoked the CAC. That is, connection requests that have already been rejected for admission to common resources in step 14 and have low priority establishment causes, may be automatically denied admission to dedicated resources and thereby rejected.

Where admission to common resources has been granted in step 14, the access to common resources is characterized as either high quality or low quality in step 16. The characterization may be based on factors such as delay, interference transmission error rate, congestion, throughput or any other factor allowing the classification of high quality or low quality.

The threshold or criteria for classifying the access of a UE as high quality or low quality may vary as a function of the establishment cause. Preferably, a lookup table of thresholds for different establishment causes are defined. For certain establishment causes, the criteria for classifying the access of a UE as high quality should be very broad such that signaling requests containing these establishment causes are always classified as high quality thereby ensuring that dedicated resources will never be requested. Alternatively, for other establishment causes, such as the establishment cause that corresponds to an emergency call, the criteria for classifying the access of a UE as high quality should be very narrow such that signaling requests containing these establishment causes are always classified as low quality, thereby ensuring that they will be evaluated for admission to dedicated resources.

In the high quality case, the UE is immediately admitted for a signaling connection over common resources (step 20). In the low quality case, however, an analysis (step 18) of whether the UE can be admitted to dedicated resources is performed. The analysis (step 18) is performed because although the relevant factors for admission to common resources are considered acceptable, they are nevertheless sub-optimal making it likely that the UE will experience transmission errors or significant access delays. As a result, the admission for signaling connection over dedicated resources is evaluated in step 18.

The evaluation of whether a low quality signaling connection request will be admitted to dedicated resources (step 18) is carried out in the same manner as in step 15, as described above. In the event the UE is not admitted to dedicated resources (step 22), however, it will be admitted for a signaling connection over common resources (step 20).

As mentioned in connection with FIG. 1, step 14 involves an evaluation of whether a UE will be admitted to common resources. A preferred method 50 of evaluating whether a signal connection request will be admitted to common resources is shown in FIG. 2 and indicated generally with numeral 50, where the common resources comprise both the FACH (downlink) and the RACH (uplink), which is a contention-based uplink transport channel.

When evaluating the effect of admission to common resources in terms of the RACH, the method 50 evaluates transmission error rates and (optionally) the corresponding delay in successful RACH access. The first step 52 is to calculate the transmission error rate for accessing the RACH. The transmission error rate for accessing the RACH is observed during frames preceding the connection request and may be calculated using information available at the RAN.

First, the RACH transmission rate and the RACH transmission success rate are calculated by compiling the following information:

    • A history of successful RACH transmissions observed over N frames, where N typically lies in the range of 100.
    • A history of failed RACH transmissions observed over N frames, where N typically lies in the range of 100.

Accordingly, the following information is all or partially available at the RAN:

    • The establishment cause (IE) in the RRC CONNECTION REQUEST MESSAGE
    • The rate of successful RACH transmissions, observed over N frames preceding the connection request where N typically lies in the range of 100.
    • The rate of failed RACH transmissions, observed over N frames preceding the connection request where N typically lies in the range of 100.
    • The dynamic persistence level (DP) parameter which controls the rate at which UEs access the RACH, if managed at RNC.

The number of RACH accesses attempted by the admitted UE can be predicted using the establishment cause in the RRC CONNECTION REQUEST message. For instance, a UE would use RACH for RAB setup in the case of “Originating Conversational Call” which would typically result in 5 RACH accesses and 5 FACH accesses in a handshake manner. From the estimated number of RACH accesses attempted by the admitted UE, (i.e. the expected RACH traffic), an estimate in number of successful and failed RACH accesses and the corresponding transmission error rate within the cell is obtained from basic mathematics/simulations related to the RACH access mechanism or system monitoring.

Following step 52, (i.e. once the RACH transmission error rate is known), there are two possibilities for evaluating if the RACH quality is sufficient to admit a UE (step 54). The admission may be based on the predicted delay or the admission may be based on the predicted increase in RACH load. In the former case the delay is calculated based on the transmission error rate, whereas in the latter case the transmission error rate itself is evaluated. Whether admission of a UE is based on delay or load, is dependent on the establishment cause. For example, delay sensitive connections, such as an originating conversational call, should be admitted based on delay. Other types of requests can be accepted solely on the expected increase in RACH load.

For signaling requests having establishment causes that require RACH admission to be based on delay, the method proceeds to step 55. In step 55, the resulting delay in accessing the RACH may be calculated using the transmission error rate calculated at step 52. The value of the delay is evaluated in step 56 to determine whether it is below a predetermined maximum value. If, on the other hand, the admission is based on load (i.e. the delay is not calculated), the transmission error rate itself is evaluated in step 58 to determine whether it is below a predetermined maximum value. If either of those values (delay or transmission error rate) is below their respective predetermined maximum value, the conditions at the RACH are considered acceptable for admission to common resources.

A margin is preferably subtracted from a maximum-allowed-value to get the predetermined maximum value. The margin takes into consideration UEs transmitting/receiving over common resources from neighboring cells that might re-select the current cell, a procedure that is assumed to be uncontrollable or at least difficult to control with the UTRAN. In the cases where the idle and connected mode common resources are the same, (i.e. where idle mode and connected mode UEs transmit and receive using the same common resources), the method should also consider the transmission of other RRC connection messages in the margin. Note that the predetermined maximum values may vary according to the establishment cause that is transmitted in the RRC CONNECTION REQUEST message.

Once the effect of admitting a signaling connection request to common resources has been evaluated in terms of the RACH, it must also be evaluated in terms of the FACH. The factor impacting on common resources in terms of the FACH is the amount of congestion at the FACH. In step 60, the congestion at the FACH is identified. The amount of FACH congestion is known at the RAN by the FACH scheduler and the FACH buffer which includes the number of FACH messages waiting to be transmitted. The level of FACH congestion is a function of the number of FACH resources, the FACH scheduler design and implementation and the UTRAN architecture.

Similar to the evaluation of the RACH, following step 60, (i.e. once the FACH congestion is identified), there are two possibilities for evaluating whether to admit a UE based on the identified level of congestion (step 62). The admission may be based on the predicted delay that will be the result of the identified congestion or the admission may be based on the predicted increase in FACH load, i.e. the congestion itself. The selection of which method is again dependent on the establishment cause.

For establishment causes that require the evaluation of FACH congestion to be based on delay, the method proceeds to step 64. In step 64, the resulting delay in accessing the FACH may be calculated using the amount of congestion identified at step 60. The value of the resulting delay is evaluated in step 65 to determine whether it is below a predetermined maximum value. If, on the other hand, the admission is based on load (i.e. the delay is not calculated), the congestion itself is evaluated in step 66 to determine whether it is below a predetermined maximum value. If either of those values (delay or congestion) is below their respective predetermined maximum value, the conditions at the FACH are considered acceptable for admission to common resources and the signaling connection is admitted to common resources (step 70). As with the evaluation of the RACH, a margin is preferably subtracted from a maximum allowed value to get the predetermined maximum value.

As can be seen in FIG. 2, if the transmission error rate (step 52) or the delay caused thereby (step 55) at the RACH are above the predetermined maximum value, the signaling connection request will not be admitted to common resources (step 68). Similarly, if the congestion (step 60) or the delay caused thereby (step 64) at the FACH are above the predetermined maximum value, the signaling connection request will not be admitted to common resources (step 68).

As with the criteria for determining high quality and low quality access in step 16 of FIG. 1, the predetermined maximum value for the parameters at both the RACH and the FACH may vary as a function of the establishment cause. Therefore, the establishment cause may be used to ensure that signaling connection requests having certain establishment causes are admitted to common resources regardless of the conditions at the RACH and the FACH. By way of example, for high priority establishment causes such as emergency calls, the predetermined maximum value can be very high so that all requests are admitted regardless of error rates, congestion or the resulting delays caused thereby.

If admission to common resources is denied in FIG. 2, the method shown in FIG. 1 will move from step 14 to step 15 to determine whether the request may be admitted to dedicated resources and continue as described above. Similarly, if admission to common resources is accepted in FIG. 2, the method shown in FIG. 1 will move from step 14 to step 16 and continue as described above.

Although the present invention has been described in detail, it is to be understood that the invention is not limited thereto, and that various changes can be made therein without departing from the spirit and scope of the invention, which is defined by the attached claims.

Claims

1. A method comprising:

receiving, by a radio access network (RAN) using a random access procedure, a radio resource control (RRC) connection request message from a user equipment (UE), wherein the RRC connection request message includes an establishment cause indicating an admission delay of the UE; and
determining whether to admit the UE in response to the indicated admission delay.

2. The method of claim 1, wherein the determining whether to admit the UE is based on loading and not on delay.

3. The method of claim 1, wherein the UE is in an idle state prior to the RAN receiving the RRC connection request message.

4. A radio access network (RAN) comprising:

a controller configured to receive using a random access procedure an establishment cause in a radio resource control (RRC) connection request message from a user equipment (UE), wherein the establishment cause indicates an admission delay of the UE; and
the controller is further configured to determine whether to admit the UE in response to the indicated admission delay.

5. The RAN of claim 4, wherein the determining whether to admit the UE is based on loading and not on delay.

6. The RAN of claim 4, wherein the UE is in an idle state prior to the receiving of the establishment cause.

7. A user equipment (UE) comprising:

transmitting and receiving components configured to form an idle state to transmit a radio resource control (RRC) connection request message using a random access procedure, wherein the RRC connection request message includes an establishment cause indicating an admission delay of the user equipment; and
the transmitting and receiving components are further configured to establish an RRC connection with a radio access network (RAN) in response to receiving a connection setup message from the RAN, wherein a decision to admit the UE is in response to the indicated admission delay.

8. The UE of claim 7, wherein the decision to admit the UE is based on loading and not on delay.

Referenced Cited
U.S. Patent Documents
5408682 April 18, 1995 Ranner et al.
5430760 July 4, 1995 Dent
5570355 October 29, 1996 Dail et al.
5742588 April 21, 1998 Thornberg et al.
5802465 September 1, 1998 Hamalainen et al.
5884171 March 16, 1999 Tanabe et al.
5886988 March 23, 1999 Yun et al.
6167248 December 26, 2000 Hamalainen et al.
6222824 April 24, 2001 Marin et al.
6266322 July 24, 2001 Berger et al.
6301252 October 9, 2001 Rangachar
6393014 May 21, 2002 Daly et al.
6396837 May 28, 2002 Wang et al.
6483826 November 19, 2002 Akerberg
6490249 December 3, 2002 Aboul-Magd et al.
6507570 January 14, 2003 Holma et al.
6539237 March 25, 2003 Sayers et al.
6631269 October 7, 2003 Cave
6711129 March 23, 2004 Bauer et al.
6775542 August 10, 2004 Vilander et al.
6778812 August 17, 2004 Zhang
6778835 August 17, 2004 You et al.
6801515 October 5, 2004 Ishikawa et al.
6868273 March 15, 2005 Cave
6947750 September 20, 2005 Kakani et al.
7065366 June 20, 2006 Cave
7218619 May 15, 2007 Koo et al.
7283825 October 16, 2007 Cave
7453847 November 18, 2008 Wallentin et al.
7583970 September 1, 2009 Cave
7848236 December 7, 2010 Rinne et al.
8249610 August 21, 2012 Cave
20010043561 November 22, 2001 Burns et al.
20010053140 December 20, 2001 Choi et al.
20010053145 December 20, 2001 Willars et al.
20020041578 April 11, 2002 Kim et al.
20020094816 July 18, 2002 Boudjema et al.
20020094833 July 18, 2002 Lieshout et al.
20020110106 August 15, 2002 Koo et al.
20020119784 August 29, 2002 Agin
20020119796 August 29, 2002 Vanghi
20020176360 November 28, 2002 Racz
20020181394 December 5, 2002 Partain et al.
20020196803 December 26, 2002 Ota
20030012217 January 16, 2003 Andersson et al.
20040053597 March 18, 2004 Agin
20040097191 May 20, 2004 Meyer et al.
20040110521 June 10, 2004 Soldani et al.
20040136342 July 15, 2004 Pedersen et al.
20040162081 August 19, 2004 Lu
20040203807 October 14, 2004 Bi et al.
20040213153 October 28, 2004 Nagato et al.
20040218578 November 4, 2004 Fisher
20110032935 February 10, 2011 Yang
Foreign Patent Documents
2 330 881 July 2001 CA
0 565 507 October 1993 EP
1 079 650 February 2001 EP
S62-213340 September 1987 JP
H03-270432 December 1991 JP
H08-213990 August 1996 JP
H08-336177 December 1996 JP
H11-205352 July 1999 JP
2001-016215 January 2001 JP
2001-044914 February 2001 JP
382167 February 2000 TW
98/30057 July 1998 WO
00/01186 January 2000 WO
00/35235 June 2000 WO
0032001 June 2000 WO
00/57663 September 2000 WO
0054522 September 2000 WO
01/05050 January 2001 WO
02/065796 August 2002 WO
02/093838 November 2002 WO
Other references
  • Third Generation Partnership Project, “Technical Specification Group Radio Access Network; MAC protocol specification (Release 5),” 3GPP TS 25.321 V5.2.0 (Sep. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Radio Access Network; MAC protocol specification (Release 5),” 3GPP TS 25.321 V5.0.0 (Mar. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Radio Access Network; MAC protocol specification (Release 4),” 3GPP TS 25.321 V4.6.0 (Sep. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Radio Access Network; MAC protocol specification (Release 1999),” 3GPP TS 25.321 V3.11.0 (Mar. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Radio Access Network; MAC protocol specification (Release 1999),” 3GPP TS 25.321 V3.13.0 (Sep. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Radio Access Network; MAC protocol specification (Release 4),” 3GPP TS 25.321 V4.4.0 (Mar. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 1999),” 3GPP TS 25.331 V3.10.0 (Mar. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 1999),” 3GPP TS 25.331 V3.12.0 (Sep. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 4),” 3GPP TS 25.331 V4.4.0 (Mar. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 4),” 3GPP TS 25.331 V4.7.0 (Sep. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 5),” 3GPP TS 25.331 V5.0.0 (Mar. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 5),” 3GPP TS 25.331 V5.2.0 (Sep. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Core Network; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (Release 5),” 3GPP TS 24.008 V5.5.0 (Sep. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Core Network; Mobile radio interface layer 3 specification; Core Network Protocols—Stage 3 (Release 1999),” 3GPP TS 24.008 V3.11.0 (Mar. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Core Network; Mobile radio interface layer 3 specification; Core Network Protocols—Stage 3 (Release 1999),” 3GPP TS 24.008 V3.13.0 (Sep. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Core Network; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (Release 4),” 3GPP TS 24.008 V4.6.0 (Mar. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Core Network; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (Release 4),” 3GPP TS 24.008 V4.8. 0 (Sep. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Core Network; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (Release 5),” 3GPP TS 24.008 V5.3. 0 (Mar. 2002).
  • Ericsson, “Mapping of NAS procedures to RRC Establishment Causes,” 3GPP TSG-CN1 Meeting #20, Tdoc N1-011467 (Oct. 15-19, 2001).
  • Siemens, “PRACH Establishment Causes,” 3GPP TSG GERAN #9, Tdoc GP-020840 (Apr. 15-19, 2002).
  • Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Radio Rescue Control (RRC); Protocol Specification (Release 1999),” 3GPP TS 25.321 V3.10.0 (Mar. 2002).
  • Third Generation Partnership Project, “Technical Specification Group Core Network; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (Release 5),” 3GPP TS 24.008 V5.3.0 (Mar. 2002).
Patent History
Patent number: 8606285
Type: Grant
Filed: Jul 24, 2012
Date of Patent: Dec 10, 2013
Patent Publication Number: 20120320850
Assignee: InterDigital Technology Corporation (Wilmington, DE)
Inventor: Christopher R. Cave (Montreal)
Primary Examiner: Sharad Rampuria
Application Number: 13/556,352