Patent Application
20120113797
The present invention has its application within the telecommunications sector and, especially, in the industrial area engaged in providing Radio Network Controllers (RNCs) with Mobility Management means for handling different configurations of legacy User Equipments (UEs) in Radio Access Networks (RANs) with or without Space Time Transmit Diversity (STTD). More specifically, it relates to RANs of wireless communications systems supporting HSPA (High Speed Packet Access) and MIMO (Multiple Input Multiple Output).
Transmission diversity based on Space Time Transmit Diversity (STTD), is a standard feature of cellular telecommunications and already appears on radio network vendor roadmaps. STTD which uses space-time block code (STBC) in order to exploit redundancy in multiple transmitted versions of a signal that is, the two antennas transmit the same information but each one uses a different coding scheme. A transmit diversity mode was introduced by the 3rd Generation Partnership Project (3GPP) and specifying STTD for Wideband Code Division Multiple Access (WCDMA) in 3GPP Release 99 (R99). Release 7 of the 3GPP specification expanded the STTD approach to Evolved High-Speed Packet Access (HSPA+). Indeed, the utilization of STTD has been chosen by 3GPP as the main Diversity Technique to be used together with MIMO (Multiple Input Multiple Output).
Legacy devices (non-MIMO HSPA terminals) support STTD feature since it has been mandatory in the baseline 3GPP specification since the initial Release 99 (non-MIMO). However, the lack of interest from mobile telecommunications network operators in the use of the STTD feature for its intended purpose has leaded to face several mobility and interoperability issues. Indeed STTD feature testing has not been considered as part of the testing baseline for Interoperability Testing purposes, especially on the mobility side. This has led to a delayed introduction of STTD in the current commercial networks.
With the renewed interest in STTD, the telecommunications network operators have started to perform Interoperability Testing in their deployed networks, they have found incompatibilities when trying to configure STTD in some radio cells.
The cells with which a User Equipment (UE) communicates form the active set of that UE. In the R99 case at least, a Radio Network Controller (RNC), for example, directs the downlink data heading to a certain user to every cell in the active set (HSDPA user plane data is transferred to the reference best cell only). Correspondingly, the UE listens to the downlink transmissions of all the cells in the active set. When the user changes its location or the qualities of the downlink radio transmissions of the neighbouring cells change for some other reason, it may be necessary to modify the active set. The set of cells whose signals are used during a soft handover is also referred to as the active set.
The following table shows the specific information fields of the ACTIVE SET UPDATE message specified by 3GPP (see 3GPP TS 25.331 V6.2.0, Release 6), which are relevant for the context of the invention. The field Radio Link Addition Information contains the cell identifier to be added to the active set, i.e., to the cells which will have a connection with the UE after the ACTIVE SET UPDATE message is received and accepted by said UE.
In scenarios with a non continuous STTD 3G layer, the active set of cells may include two types of configurations: cells supporting STTD (STTD ON configuration) or cells not using transmit diversity (STTD OFF).
In a normal mobility procedure, when the user starts a call and the UE reports the necessity of adding a cell to the network, the network starts an Active Set Update Procedure of the Radio Resource Control (RRC): an ACTIVE SET UPDATE message from the RRC layer of the RNC is sent and a (positive or negative) reply is sent from the UE. During this procedure, the network indicates the UE whether the cell has STTD configured or not. This is done by means of the “TX Diversity Mode” Information Element valid for the whole active set and the “Closed loop timing adjustment mode” information element specifically defined per Radio Link (this information element is in charge of defining whether the STTD is ON or OFF for each specific cell).
Unfortunately, not all legacy devices can support the adding of a cell with STTD ON when the active set consists only of STTD OFF cells. If this happens, the UE sends an ACTIVE SET UPDATE FAILURE message to the RNC reporting the cause “Invalid Configuration” and the soft or softer (soft refers to the handover with simultaneous connection in different Nodes B or Base Stations, softer is the handover with simultaneous connections to different cells of the same Node B or Base Station) handover procedure fails leading to loss 3G mobility, higher call block and drop rates, and losing 3G coverage.
On the other hand, in the case that the call is established in a cell with STTD ON and a cell with STTD OFF is tried to be added to the active set, the network may also need to fallback its decision because an ACTIVE SET UPDATE FAILURE due to “Invalid Configuration” is received from the UE. Similar situation happens when the cell to be added to the active set supports STTD (both initial and target cells, are configured with STTD ON).
A robust fallback solution is a thus essential to manage the interoperability among (2G, 3G and beyond) wireless communication networks and cope with any unknown mobility issue that may arise among the already existing (legacy) commercial devices and the diverse possible configurations.
The present invention serves to solve the aforesaid problem by providing management mobility procedures for updating the active set corresponding to a UE changing between cells with different configurations of STTD transmission diversity mode. A fallback procedure triggered by the RAN network entity which is in communication with the UE and controlling the UE's mobility, is proposed in order to preserve the call in spite of lack of a full STTD feature support on the UE's side of the existing legacy devices.
UEs having differing capabilities (HSDPA UEs, MIMO UEs, and non-MIMO or Rel′99 UEs) can coexist in the wireless communication system and establish (voice, data, multimedia) calls. A UE engaged in a call establishment communicates with cells which can be configured in either of two possible transmission diversity modes: STTD activated (STTD ON) or STTD deactivated (STTD OFF).
In accordance with one aspect of the invention, there is provided a method for updating the active set of cells used by a User Equipment (UE) for wireless communications in a wide area mobile network as claimed in claim 1.
The source cell is the one in which the UE is engaged in a call establishment. The target cell is the one detected by the UE and to be added to the active set when updating. Each cell of the active set is configured in one of two possible modes of transmission diversity: either STTD activated (STTD ON) or STTD deactivated (STTD OFF).
The method comprises the following steps:
Attempting to add the target cell to the active set involves an event-based Radio Resource Control (RRC) message sent by the UE to the network controller. The event which triggers its sending is a typical measurement report on the active and detected cells, obtained by the UE.
Depending on the transmission diversity mode configuration of the source and target cells which has been determined by the network controller, the reconfiguration of the transmission diversity modes of the two cells in order to set both into STTD deactivated configuration is performed as explained in the following cases:
If the transmission diversity mode configuration of the source cell is STTD OFF and the target cell has STTD ON, an ACTIVE SET UPDATE message is sent from the network controller to instruct the UE to add the target cell to the active set with STTD deactivated configuration.
If the transmission diversity mode configuration of the source cell is STTD ON, a PHYSICAL CHANNEL RECONFIGURATION message is sent from the network controller to instruct the UE to change the transmission diversity mode and reconfigure it with STTD OFF.
When both the source cell and the target cell have STTD activated, an ACTIVE SET UPDATE message is sent (from the network controller) before sending the PHYSICAL CHANNEL RECONFIGURATION message and after a certain time period. This period can be configurable by the mobile network operator and is defined from the time when the first ACTIVE SET UPDATE FAILURE message is received. The ACTIVE SET UPDATE message indicates to the UE the instruction to add the target cell to its active set with the transmission diversity mode configured as STTD deactivated (instead of the initial configuration of the target cell STTD ON reported from the UE). Then, a second ACTIVE SET UPDATE FAILURE message is sent from the UE to the network controller, which prompts the network controller to send the PHYSICAL CHANNEL RECONFIGURATION message for also reconfiguring the source cell to STTD deactivated as explained before.
Optionally, after receiving the first ACTIVE SET UPDATE FAILURE message in the network controller, at least one identifier of the UE can be introduced in a black list during a blocking time period (configurable by the mobile network operator). Thus, the whole method described before can be enhanced by the management of a device “black list” of UEs, in a preferred embodiment of the invention. This black list inform the mobile communication network that updating the active set of the UEs in the list, when implying that said active set involves at least one cell (the source cell and/or the target cell) with STTD ON, is blocked during the configurable blocking time period. Therefore, the black list prevents to receive a second ACTIVE SET UPDATE FAILURE from any of the listed UE, which are already set into the right configuration to send an ACTIVE SET UPDATE ACCEPT. Whenever a device is identified as having interoperability issues with STTD, any of the UE's identifiers in the mobile radio (e.g., IMSI, TMSI, P-TMSI or IMEI) can be inserted into the black list (managed by the corresponding network entity of the core network, for example: HSS, EIR) for further investigation. In addition, the network avoids any attempt of mobility configurations which are likely to end up on known failures during a timer (here called blocking time period and predefined on the network side). After the expiration of this timer, the device is treated as “clean” (out of the “black list”) and treated as a normal full working STTD device. By this mean, the next soft or softer handover failures can be avoided during the length of the timer, if the active set size is again one afterwards.
In accordance with a further aspect of the invention, there is provided a telecommunications network entity as claimed in claim 8.
The network entity may preferably be implemented in a radio network controller (RNC), comprising processing means for performing the method described before, also it can be implemented in the HSPA Node B and if the RAN is based on a flat architecture (Collapsed Architecture) for the packet switching (PS) domain and no RNC nodes are required in the network, the proposed network entity can be a flat HSPA Node B (named evolved HSPA Node B or eHSPA Node B).
In accordance with another aspect of the invention, there is provided a computer program comprising program code means which executes the method described before, when loaded into processing means of the network controller defined above.
Without implementing in the possible network scenarios defined above a fallback mechanism as proposed, customer perception is lower voice quality, lower data throughput and less 3G coverage.
If the network is not provided with these proposed fallback mechanisms, then the customer satisfaction will be reduced, due to a highly limited mobility on the 3G side and due to a higher call block and drop rate which decrease performance.
A major advantage of the described solution is improvement in customer satisfaction and network performance thanks to avoidance of impact from mobility issues with STTD transmission diversity mode activation on legacy devices.
To complete the description that is being made and with the object of assisting in a better understanding of the characteristics of the invention, in accordance with a preferred example of practical embodiment thereof, accompanying said description as an integral part thereof, is a set of drawings wherein, by way of illustration and not restrictively, the following has been represented:
FIG. 1.—Shows a message diagram of an active set update procedure in the case that, having a call established in a source cell which has STTD transmission diversity deactivated, a target cell with STTD transmission diversity activated is to be added to the active set, according to a possible embodiment of the invention.
FIG. 2.—Shows a message diagram of an active set update procedure in the case that, having a call established in a source cell which has STTD transmission diversity activated, a target cell with STTD transmission diversity deactivated is to be added to the active set, according to another possible embodiment of the invention.
FIG. 3.—Shows a message diagram of an active set update procedure in the case that, having a call established in a source cell which has STTD transmission diversity activated, a target cell where STTD transmission diversity is also activated is to be added to the active set, according to a further possible embodiment of the invention.
Many UEs (typically legacy devices) lack full STTD feature support. Consider a network scenario where such a user equipment UE communicates with a radio network controller RNC engaged in a call establishment 100 with transmit diversity mode deactivated, i.e. the UE is in a source cell with STTD OFF. If this UE tries to add a target cell with STTD activated, i.e. STTD ON, the updating of the active set of cells is executed according to the message flow shown in
Having been notified about the new cell, the RNC sends an ACTIVE SET UPDATE message 102 to the UE in order to add the new (target) cell into the active set of the UE. Since the target cell has STTD activated and the existing UE cannot support it (the network is capable of tracking a list of unsupportive UEs, so that certain UE types can be associated with an operating mode in which STTD activation is unsupported), then the UE sends an ACTIVE SET UPDATE FAILURE message 103 notifying “Invalid Configuration” failure cause to the RNC. Note that there are other possible causes for triggering an ACTIVE SET UPDATE FAILURE, e.g. “physical channel failure” which means that there is a synchronisation failure, and in such cases there is no need to change) STTD configuration
After a time period (e.g. in a pre-defined time interval, say 500 ms to 1 second, provided to UE by the RNC), the UE further sends a second event-based message 104 in order to report one more time to the RNC that the detected target cell is to be added into the active set of the UE. Upon receipt of the second message 104, the RNC replies to the UE with another ACTIVE SET UPDATE message 105 indicating that the new cell is configured as STTD OFF and is to be added by the UE into its active set. Thus, even though the new (target) cell has STTD activated, the RNC indicates that the target cell configuration is STTD OFF to keep the call going on. As the existing UE supports this active set update (replacing the source cell, which already had STTD OFF configuration, by the target cell labelled by the RNC as STTD OFF), the UE normally sends an ACTIVE SET UPDATE ACCEPT message 106 and the procedure is completed. Thus, the UE adds the new target cell to the active set treating that cell as having an STTD OFF configuration; therefore, one of the transmission diversity branches is lost but the call is not dropped or moved to 2G and is maintained as a 3G call.
Contrast
Due to the difference in transmit diversity mode configuration between the source and the target cell, the physical layer of the communication link with the UE must be reconfigured to deactivate STTD in (or switch off the initial status of) the source cell. Therefore, the RNC sends a PHYSICAL CHANNEL RECONFIGURATION 204 to the UE in order to configure the source cell as STTD OFF and, once completed, the UE replies with a PHYSICAL CHANNEL RECONFIGURATION ACCEPT 205. Then, second message 206 reporting one more time to the RNC the target cell addition request (in strict terms, said message 206 is a measurement report and its sending is an event trigger configured for adding the new detected cell) in the active set is sent by the UE and, in turn, the UE again receives and ACTIVE SET UPDATE message 207 from the RNC in order to add the target STTD OFF cell into the active set. The UE typically replies by sending an ACTIVE SET UPDATE ACCEPT message 208 and completing the procedure.
After a time period (pre-configured in the UE), the UE retries the new target cell addition request by sending a second message 304 to the RNC and, this time, the RNC replies to the UE with another ACTIVE SET UPDATE message 305 but indicating that the target cell is to be configured as STTD OFF. Since the source cell keeps on STTD ON configuration, another ACTIVE SET UPDATE FAILURE message 306 due to “Invalid Configuration” is sent by the UE. The RNC responds by sending a PHYSICAL CHANNEL RECONFIGURATION 307 to the UE in order to switch off the initial status of the source cell and switch the configuration to a full STTD OFF status. Once the PHYSICAL CHANNEL RECONFIGURATION ACCEPT 308 in sent by the UE, a third message 309 is generated by the UE and sent to the RNC reporting the new target cell addition request into the active set. As both the source and target cells are STTD OFF at this point, the RNC sends an ACTIVE SET UPDATE message 310 to the UE, which replies normally sending an ACTIVE SET UPDATE ACCEPT message 311 that finishes the procedure.
Note that in this text, the term “comprises” and its derivations (such as “comprising”, etc.) should not be understood in an excluding sense, that is, these terms should not be interpreted as excluding the possibility that what is described and defined may include further elements, steps, etc.
| Number | Date | Country | Kind |
|---|---|---|---|
| P201031616 | Nov 2010 | ES | national |
