Patent Application
20050036462
The present invention relates to mobile telecommunication systems. In particular, the present invention relates to a novel and improved method and system for avoiding unnecessary handovers, relocation and/or anchoring especially for packet services.
The Radio Resource Management (RRM) in the GERAN (GSM/EDGE Radio Access Network; GSM, Global System for Mobile Communications; EDGE, Enhanced Data rates for GSM Evolution) and the UTRAN (Universal Terrestrial Radio Access Network) are responsible for the utilisation of air interface resources. The RRM is needed for e.g. maintaining the QoS (Quality of Service), the planned coverage, and for offering high capacity. The RRM enables optimising service capacity and capability.
The full scope of the RRM is large, and several algorithms are needed to perform various tasks. These algorithms include, for example:
1. Power Control
2. Handover Control
3. Admission Control
4. Load Control
5. Packet Scheduler
6. Data rate control.
A handover in a wireless telecommunication network, such as the GSM or the Universal Mobile Telecommunications System (UMTS), is the mechanism that transfers an ongoing call from one cell to another. In case of a handover in the IP-RAN (Internet Protocol Radio Access Network), anchoring or relocation may take place (this may happen at the Base Station Gateway (BSGW) or in other places). Anchoring may also be used in the UTRAN. Anchoring is the process where the source after a handover still sends the user data packets to the old address and the old address sends them to the new address for transmission. This is done by tunnelling the packets from the old address to the new address. Relocation may be used in any or most of the networks. It is the traditional way of moving data buffers and protocol peers to a new point, such as Radio Network Controller (RNC) in the UTRAN, Internet Protocol Base Tranceiver Station (IP BTS) in the IPRAN or Base Station Controller (BSC) in the General Packet Radio Service (GPRS), in the EGPRS or in the GERAN. Relocation is the mechanism of changing the place of the address, i.e. packets are sent directly to the new address.
Different wireless telecommunication networks may possess different kinds of properties so that soft handover, relocation, anchoring and hard handover may not all be available for use. Hard handover refers to a handover from one frequency to another, whereby all the old radio links in the user equipment are abandoned before the new radio links are established. Soft handover refers to an intra-frequency handover which occurs between sectors or cells within one base station (BS) and where the radio links are added and abandoned in such a manner that the user's device always keeps at least two radio links to the base station. In the UTRAN, radio handover (hard or soft) does not need to affect the handling of the user plane in the network. Therefore, it is possible to keep or not to keep the same Radio Network Controller (RNC), and further, it is possible to anchor the RNC or to relocate the RNC. When the Wideband Code-Division Multiple Access (WCDMA) is used, soft handover is possible, e.g. in the UTRAN or WCDMA based IP-RAN. When Time Division Multiple Access (TDMA) is used (e.g. in the GSM, GPRS, EGPRS) like in GSM or GERAN based IP-RAN, only hard handover and relocation may be possible.
Each relocation may increase the network load, while anchoring may increase the transmission delay of data packets. Therefore unnecessary relocations and anchoring should be avoided. Relocation is a “fast” procedure that moves all information (user and control plane information) of the connection to another instant. There is a possibility of some loss of information, and that may affect the user plane transmission. And even if the relocation is “fast”, it may not be fast enough, and it may thus affect transport protocols, like TCP, causing retransmission. On the other hand, anchoring is probably the longer lasting state so the transmission network is loaded more.
Anchoring and relocation have quite an impact on the capacity of the last part of the transmission to the user (the last mile). This means that the gain from decreasing the number of relocations and anchoring is high, since the last mile of the transmission is the most expensive one. For longer calls, like speech calls, relocations and anchoring cannot necessarily be avoided, but for short packet calls, it can be done in most of the cases. A packet service session contains one or several packet calls depending on the application. During a packet call several packets may be generated, so that the packet call constitutes a bursty sequence of packets. Therefore, a packet call can be defined as an arriving data sequence where the packets are not separated by a long silent period of time.
From handover algorithms and area update algorithm, several algorithms are known to minimise the number of handovers and area updates. They are either using hysteresis or a timer. Hysteresis may be the difference between thresholds Th1 and Th2, where the Th1 is triggered when a certain parameter increases, while Th2 is triggered when the same parameter decreases. When Th1=Th2, the hysteresis is equal to zero.
When trying to avoid anchoring and relocations for short packet calls, one problem is that it is not known in advance how long a packet call will last. The network just sees data arriving in a buffer. Another problem is that ping-pong handovers can happen. A ping-pong situation basically means that a system switches frequently between two different states. In case of a handover it means that a handover between cell A and cell B and back is made frequently.
In prior art, relocation and anchoring are performed when triggered due to e.g. signal level, quality or power budget. Therefore, unnecessary relocations and anchoring cases occur. Relocation increases the network's signalling and also transmission load, whereas anchoring may delay the service and increases the transmission and signalling load of the network.
The present invention describes a method and system for avoiding unnecessary handovers, relocation and/or anchoring during packet calls in a wireless telecommunication system. The wireless telecommunication network comprises a data buffer where data to be sent to a mobile terminal is stored. The method presented in the invention is used when the amount of data in the buffer exceeds a predetermined threshold value. The data from the buffer is sent to the mobile terminal. Relocation or anchoring is performed only if one or more conditions are fulfilled, when relocation or anchoring is requested.
In a preferred embodiment, when the predetermined threshold value is exceeded and the data is sent to the mobile terminal, a first timer for carrying out a relocation or an anchoring procedure is started, and when relocation or anchoring is requested, relocation or anchoring is performed only if the first timer has expired. In another embodiment, data is sent to the mobile terminal when the amount of data in the buffer exceeds a predetermined threshold value. A first timer and a second timer for carrying out a relocation or an anchoring procedure are started, and when relocation or anchoring is requested, performing anchoring only if the first timer has expired, or performing relocation only if the first and the second timers have expired. The timers must be started again when the data in the buffer exceeds the threshold value next time. It must be noted that data can be sent to the mobile terminal even if the buffer contains less data than the threshold value. In this case, however, the method presented here should not be used.
In the aforementioned embodiments where the connection to which the anchoring or relocation is requested is not in a soft handover, the rejection of the anchoring or relocation may also be a rejection of a hard handover.
The same effect can be achieved also with adaptive thresholds, e.g. by using adaptive hysteresis.
By setting a first timer at the start of a connection, during which hard handovers, relocation and anchoring are forbidden, the amount of relocations and anchoring during the start can be decreased. The timer should be reset when relocation is made (relocation is a start of a connection from the algorithm point of view). The same effect can be achieved by using adaptive hysteresis, which is extra high at the start of the transmissions, and is then lowered after a certain time to the normal hysteresis level. However, if soft handover is possible, soft handover legs can be limited by high hysteresis limits.
To avoid unnecessary relocations, a second timer is started at the start of a connection. The second timer should be longer than the first one. Only when the second timer has expired, relocations can be made. When the first timer expires, anchoring can be used. The same effect can be achieved by setting a higher hysteresis for relocations than for anchoring.
In one embodiment it is relocation that is specially avoided for packet calls. However, if either relocation or anchoring was to be used, anchoring should be allowed. For example, if the first timer is not used, the second timer chooses either relocation or anchoring to be performed. Then, anchoring should be preferred for some time.
The transmission of a packet call takes typically less than a few seconds. During this period it is very likely that the signal level will stay quite constant, i.e. during the packet call transmission no relocation or anchoring should be done. During the silent periods relocation can be made, since no delay will be noticed (no data is transmitted). When the quality decreases very fast, the timer may prevent a relocation and anchoring case. This may lead to a very bad quality or even call drops. This can be prevented by allowing only certain kinds of handovers even if the timer has not expired.
The present invention has several advantages over the prior-art solutions. The present invention lowers the delay of the packet calls, and less transmission and signalling capacity is used for the cases when anchoring is used. Less network transmission capacity and less signalling capacity are used when relocations are made. A further advantage is that the Quality of Service (QoS) may be better because relocations are not performed so often.
With the solution of the present invention it is possible to balance the usage of relocation and anchoring in an optimum way. For example, to anchor the shortest packet calls and to perform relocation only when needed. This minimises the risk of errors in relocation but does not use the transmission network too much in anchoring.
When a handover is done, it usually triggers either anchoring or relocation. The present invention lowers the number of handovers and thus the number of anchoring and relocation cases.
The accompanying drawings, which are included to provide a further understanding of the invention and constitute a part of this specification, illustrate embodiments of the invention and together with the description help to explain the principles of the invention. In the drawings:
Reference will now be made in detail to the embodiments of the present invention, examples of which are illustrated in the accompanying drawings.
In
The data is sent to the mobile terminal, as represented in box 34. If a relocation or anchoring request is not requested within e.g. Transmission Time Interval (TTI), the timer values (T1 and T2) are decremented by the TTI, as represented in boxes 36 and 38. The transmission time interval indicates how often data arrives from higher layers.
It must be noted that data can be sent to the mobile terminal even if the buffer contains less data than the threshold value. In this case, however, the method presented here should not be used. The method presented here is not triggered before the threshold value is exceeded and the timers are set. The threshold value can also be set to zero. If the threshold value is set, for example, to 100 bytes, the method presented here is not utilised during the start phase of
If a relocation or anchoring request is received, the first timer T1 value is checked, as represented in box 40. As long as the first timer T1 has not expired, it is not allowed to perform relocation or anchoring. If the first timer T1 has not expired, relocation or anchoring may be performed only for compelling reasons. One reason can be a rapid field strength drop, as represented in box 42. The signal level may drop for some reason very fast. Only a fast relocation can save the call. Only if the rapid signal level drop cannot be handled by the power control of the original cell, and this affects the frame error rate (QoS), a radio handover and possibly relocation is needed. This is appropriate especially for the cases where there is no soft handover, e.g. in the GSM, General Packet Radio Service (GPRS), EGPRS or in the Downlink Shared Channel (DSCH) or the UTRAN of the IP-RAN. In such a case, the main objective is to keep the signal in one cell if the signal level is quite reasonable even if a handover request arrives. The handover decisions are usually made by relative measures to the neighbouring cells signals. If the absolute value of the original signal is sufficient, it is probably better to hold on the original cell if, at the same time, it is predicted that the packet call will be short.
Another reason for relocation or anchoring is when a gap in the transmission appears, as represented in box 44. This gap will often be one of the silent periods in the transmission, like the reading times between packets. Then it is possible to perform relocation and anchoring, as represented in box 46.
The second timer T2 can be used, of course, also in a non soft handover case. This, however, requires anchoring possibility for a non soft handover case which might not be supported, e.g. for some channels in the UTRAN of the IP-RAN and for none of the channels in the GERAN. Another way of avoiding unnecessary relocation and anchoring is to set two adaptive thresholds, H1 which is used for anchoring, and H2 which is used for relocation. H2 should be equal or higher than H1. H1 and H2 preferably refer to hysteresis levels.
After the first timer T1 has expired anchoring is allowed as described above, as represented in boxes 48 and 50. However, after the second timer T2 has expired it is also allowed to perform relocations, as represented in boxes 48 and 46. This way unnecessary relocations are avoided. For example, when a mobile terminal is using multiple radio connections (soft handover), the set of active radio connections may be updated frequently. If the radio connection to the master cell is lost, in a traditional system the relocation is performed. On the other hand it is very probable that the radio connection is lost for some temporary cause and it will recover in few seconds. Therefore, the relocation should not be performed right away but a timer should be used. It is also probable that the active packet call will end in a few seconds, and therefore, relocation is not necessary. It may take more time to relocate and send the data using a good radio connection than send the data with the old connection or, if anchoring is possible, by an anchored leg. In case the connection to which the anchoring or relocation is requested is not in soft handover, the rejection of the anchoring or relocation may also be a rejection of a hard handover. However, if soft handover is possible, soft handover legs can be limited by high hysteresis limits.
In one embodiment of
In one embodiment of
In one embodiment of
In
Add a second timer, which is used for relocations at the start of the transmission in order to avoid ping-pong relocations.
The transmission of a packet call takes typically less than a few seconds. Within this period it is very likely that the signal level will stay quite constant, i.e. during the packet call transmission no relocation or anchoring should be done. During the silent periods relocation can be made, since no delay will be noticed (no data is transmitted). When the quality decreases very fast, the timer may prevent a relocation and anchoring case. This may cause very bad quality or even call drops. This can be prevented by only allowing certain kinds of handovers even if the timer has not expired.
When handover is done, it triggers either anchoring or relocation. Therefore, the present invention lowers the number of handovers needed, and thus the number of anchoring and relocation cases.
The timer values may be determined using the idea of the patent application PCT/FI01/01055 of the applicant. The statistical models based on the TCP/UDP (User Datagram Protocol) port numbers may provide useful information. For example, if some services are known to be lasting less than three seconds with a 64 Kbps bearer with 80% probability, the timer values can be set for it very accurately, and the timer values are different than for a service that has 80% limit at 20 seconds. The shorter the expected packet call, the more strict limits for the relocation should be set.
In one embodiment of
Traditionally, at point 2 either relocation or anchoring would be performed. In one embodiment of the present invention at point 2, if the first timer T1 has not expired, relocation and anchoring are both rejected. Also the leg deletion must be prevented and the mobile terminal kept in soft handover by increasing level TH2. In another embodiment at point 2, if the first timer T1 has not expired, depending on the second timer T2, either relocation or anchoring is performed. Anchoring is chosen, if the second timer T2 has not expired. If the T2 has expired, relocation is performed. The request, however, can be stored for later use. When the timer or timers have expired, it can be re-evaluated whether to perform relocation or anchoring or neither.
In case of a hard handover, there would be only two limits, L1 and L2 (instead of four (−TH1, −TH2, TH1 TH2) as in a soft handover case). Limit L1 for going from the base station BS1 to the base station BS2, and limit L2 for going back to the base station BS1.
It is obvious to a person skilled in the art that with the advancement of technology, the basic idea of the invention may be implemented in various ways. The invention and its embodiments are thus not limited to the examples described above, instead they may vary within the scope of the claims.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/FI02/00096 | Feb 2002 | US |
| Child | 10901356 | Jul 2004 | US |
