Sign In to Follow Application
View All Documents & Correspondence

Method And Apparatus For Radio Link Failure Recovery In A Wireless Communications Network

Abstract: In a method for radio link failure (RLF) recovery in a wireless communications network, a timer T sets a predetermined time period from a command to a mobile terminal UE to hand over to a new eNB. Resources are reserved at a target eNB 2. If the time period expires without the UE attaching to the target eNB 2, the source eNB requests other candidate eNBs 3 and 4 to reserve resources. Once the UE associates with the target eNB 2, the resources reserved at candidate eNBs 3 and 4 are released. If the UE associates with the target eNB 2 prior to expiry of the time period T, resources are not unnecessarily reserved at the candidate eNBs 3 and 4. If the UE associates with one of the candidate eNB 3 instead of the target eNB 2, resources have already been reserved, enabling RLF recovery to be implemented without the UE going via LTE_IDLE, in an LTE arrangement.

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
03 August 2010
Publication Number
07/2011
Publication Type
INA
Invention Field
COMMUNICATION
Status
Email
patent@depenning.com
Parent Application
Patent Number
Legal Status
Grant Date
2018-04-10
Renewal Date

Applicants

ALCATEL LUCENT
3 AVENUE OCTAVE GREARD 75007 PARIS

Inventors

1. AYDIN, OSMAN
KNAPPENWEG 51H, STUTTGART-70569
2. KAMINSKI, STEPHEN
RUECKERSTRASSE 72, EISLINGEN, 73054.

Specification

METHOD AND APPARATUS FOR RADIO LINK FAILURE RECOVERY IN A WIRELESS COMMUNICATIONS NETWORK

FIELD OF THE INVENTION

The present invention relates to a method and apparatus for radio link failure recovery in a wireless communications network, and more particularly, but not exclusively, to a method and apparatus implemented in accordance with the 3rd Generation Partnership Project (3GPP) evolved Universal Terrestrial Radio Access Network (E-UTRAN) and evolved Universal Terrestrial Radio Access (E-UTRA) specifications.

BACKGROUND

Currently, 3GPP is considering development of E-UTRA and E-UTRAN as set out in the technical specification 3GPP TS 36.300 v 8.3.0 (2007- 12), incorporated herein by way of reference, and related documents. 3GPP Long Term Evolution (LTE) aims to enhance the Universal Mobile Telecommunications System (UMTS) standard, for example, by improving efficiency and services.

In E-UTRAN, user equipment (UE) communicates with a network node, NodeB (eNB), with data being sent on radio bearers (RBs) over a radio link between them. The eNB interfaces with a Mobile Management Entity (MME) via an interface designated as S1. The E-UTRAN network includes a plurality of eNBs and MMEs. The connection between the UE and the source eNB to which it is attached may be lost, this being known as radio link failure (RLF). It had previously been proposed that a UE experiencing an RLF and reappearing in a cell of another eNB would be handled as a transition via an idle state, RRC_IDLE. In this mechanism, when there is RLF in the source eNB, the UE enters IDLE state and selects a new target eNB. When the UE has attached to the new target eNB, and received the system information for the target eNB, the UE may perform the access procedure to establish resources in the target eNB. However, this procedure is time-consuming.

RLF may be particularly likely during fading channel conditions, when handover from the source eNB to a target eNB may be imminent. To avoid going via the IDLE state, it has been suggested that a new eNB could be prepared beforehand to accept the UE by using the handover preparation procedure. The Handover_Request message can be sent to multiple eNBs which are thus able to recognize the UE, each of the eNBs being prepared a$ handover candidates. Then, the UE is able to carry on with its old context after having chosen the new target eNB during the mobility phase of the RLF.

The paper by Nokia Siemens Networks et al "Radio Link Failure Recovery", R2-072382, 3GPP TSG-RAN WG2 Meeting #58, incorporated herein by way of reference, discusses RLF recovery by preparing multiple eNBs using the handover procedure. A prepared eNB , has the UE context and resources reserved, so by preparing multiple eNBs, the probability is increased that the UE can recover from RLF without needing to go via RRC_DDLE, thus reducing recovery time.
The paper by Nokia and Nokia Siemens Networks "Handover Failure Recovery" R2-071717, 3GPP TSG-RAN WG2 Meeting #58, incorporated herein by way of reference, and the paper by Vodafone "Mobility in LTE_ACTIVE state, R2- 0723823, GPP TSG-RAN WG2 Meeting #58, incorporated herein by way of reference, also consider the preparation of multiple eNBs during handover to avoid the UE going via the IDLE state.

With reference to Figure 1, in one LTE network having handover with multiple eNB preparation, a source eNB 1 transmits a Handover_Request to a designated target eNB 2 and to other candidate eNBs 3 and 4, two of which are shown. The Handover_Request causes the designated target and candidate eNBs 2, 3 and 4 to reserve resources, shown at 5, 6 and 7, so that, if the UE attaches to one of the candidate eNBs 3 and 4 during RLF, recovery time is reduced. The eNBs 2, 3 and 4 each send a message Handover_Request_Ack to the source eNB 1 acknowledging the handover request. During RLF the UE appears within a cell associated with the designated target eNB 2, shown at 8. The target eNB 2 sends a Release_Resources message to the source eNB 1 once it has completed the handover procedure. The source eNB 1 then releases resources it has reserved for the UE and sends
Free_Resource messages to the other candidate eNBs 3 and 4 to free the resources that they have reserved, shown at 9 and 10.

In another previous proposal, as set out in R2-074179, UE context information is sent to multiple eNBs that are candidates to be the target eNB to which handover eventually occurs, but no reservation of resources is made at these candidate eNBs. This permits a UE to attach to a new eNB within the RLF procedure without going via RRC IDLE. In a variant, multiple candidate eNBs are sent UE context information and only one candidate eNB, that is the candidate eNB most likely to be the one to which the UE hands over, reserves resources.

BRIEF SUMMARY

According to a first aspect of the invention, a method for radio link failure recovery in a wireless communications network includes the steps of:
designating a network node as a target node to accept a mobile terminal in the event of failure of a radio link between the mobile terminal and a source network node;
designating one or more other network nodes as candidate nodes; reserving resources at the target node;
sending a handover command to the mobile terminal when the target node is ready to accept handover of the mobile terminal from the source node;
starting a timer to define a predetermined time period from when the handover command is sent; and
reserving resources at the one or more candidate nodes when the predetermined time period has elapsed without the mobile terminal attaching to the target node.

The invention is particularly applicable to arrangements in accordance with LTE but it may advantageously be used in networks complying with other specifications or standards. In LTE, the mobile terminal is a UE and the network nodes are eNBs.
When there is radio link failure, if the mobile terminal appears in the cell of a network node at which resources have been reserved on request from the source node, that node will recognize the mobile terminal and is able to initiate procedures to complete the connection without this needing to be set up from the beginning. In an LTE network, this avoids the UE entering the IDLE state, and thus reduces the time required to. recover a radio link connection with the UE. In an arrangement, in accordance with the invention, resources are initially reserved at the target node during RLF, but resources are only reserved at other candidate nodes after a predetermined time period. This deferral of the reservation of resources reduces overheads. For example, in LTE, the Handover_Request message, which instructs the node receiving the message to reserve resources, is delayed for the predetermined specified time period. Then, in the case where the UE re-appears at the source eNB within the first phase of the RLF, and before the time period has expired, no candidate eNBs will have been needlessly prepared and the associated messaging is avoided. In other cases, during RLF, the UE may connect to the designated target eNB at which resources have been reserved and the target node sends a message to the source node to release resources. Candidate eNBs are thus only prepared if the UE fails to either re-attach to the source node or undergo handover to the target node within the predetermined time period. Thus, the signalling load on the X2 interface between eNBs is reduced and resources are reserved at candidate nodes only when they are more likely to be required.

In one arrangement in accordance with the invention, the predetermined time period is calculated from the normal time duration for the source node to receive a message from the designated node to release resources after receiving a handover request acknowledgement from the designated node. For example, this may be set at the maximum duration of the 95 per cent quantile. In another arrangement in accordance with the invention, the predetermined time period is calculated using a timer specified for the radio link failure procedure, and this time may be specific to individual mobile terminals. In LTE, this may be the T1 timer used in RLF, as set out in 3GPP TS 36.300 v 8.3.0 (2007- 12) for example. Other timer, counter or event based parameters may be used to calculate the predetermined time period, such as the timer T2 of the RLF procedure in LTE implementations, or a counter which counts certain events, like positive slopes of a system-internal signal. A combination of these time period parameters may be used, for example, by selecting the minimum time period from a plurality of time periods calculated using respective different parameters.
Reserved resources may include allocating the time and frequency domain at the handover target node, related to its capacity for data transmission. Other resources may include a preamble, which is a special code, with which a UE can access to an eNB if there is no previous communication between the UE and the eNB. This access is carried out via the Random Access Channel (RACH). The UE randomly selects a preamble which is sent via the RACH. The preamble is used to recognize the response from the eNB. Such a RACH1 procedure is contention based. To avoid contention in case of a handover from a source eNB to a target eNB, the set of preambles is split into two basic parts: random preambles, which are randomly selected by the UE; and dedicated preambles, which the eNB sends to a specific UE. The target eNB may send a dedicated preamble to the UE via the source eNB within a transparent container, which is a data portion sent from a potential target eNB towards the UE. This data portion is actually sent from the potential target eNB via the current source eNB to the UE. The source eNB does not change this data portion, hence it being termed a "transparent container". A dedicated preamble is exclusively reserved for the specific UE only and thus avoiding another UE using the same preamble. The RACH access in case of handover is thus kept contention free. Dedicated preambles may thus be considered as reserved resources.

LTE currently only proposes that there be one handover target eNB, but in future versions, or in networks implemented in accordance with other standards or protocols, more than one handover target may be selected. For example, these may be organized in an order of precedence. In such a network, in addition to using at least one candidate node without reserving resources until the predetermined time period expires, there may be more than one target network node selected which is initially requested to reserve resources.
In one method in accordance with the invention, following radio link failure, when the mobile terminal attaches to a node, the node to which the mobile terminal is attached requests the source node to release resources. By attached it is meant that at least the initial steps of the connection process are carried out. The mobile terminal may attach to a node that is a] handover target node or a candidate node. The source node may request those nodes, except that node to which the mobile terminal is attached, that have reserved resources to release them. It may be arranged that a node that has reserved resources releases them after a set time following the request to it to reserve resources. Thus resources are released even if a network node does not receive a release message.
According to a second aspect of the invention, a wireless communications network operates in accordance with the inventive method.

BRIEF DESCRIPTION OF THE DRAWINGS

A method and embodiment of the present invention is now described by way of example only, and with reference to the accompanying drawing in which:
Figure 1 schematically illustrates a prior arrangement using multiple node preparation;
Figure 2 schematically illustrates an arrangement in accordance with the invention in which there is deferred delivery of a Handover_Request to candidate eNBs after expiiy of a predetermined time period;
Figure 3 schematically illustrates an arrangement in accordance with the invention in which a UE arrives at the target eNB before expiry of a predetermined time period; and
Figure 4 schematically illustrates an arrangement in accordance with the invention in which a UE arrives at a candidate eNB after expiry of a predetermined time period.

DETAILED DESCRIPTION
With reference to Figure 2, in an LTE network, a UE (not shown) is connected to a source eNB 1. A Handover_Request message sent to a target eNB 2 and it reserves resources in response, shown at 5: "Activate Resources". If the target eNB 2 is able to accept the UE, it sends a handover request acknowledgement message to the source eNB 1. The source eNB 1 then sends a Handover_Command to the UE and also triggers a timer T, as shown at 11, which in this arrangement is the timer T1 for RLF in LTE.
At the expiry of the timer Tl, when the predetermined time period has expired, there has been no message sent from the target eNB 2 to the source eNB 1 to indicate that the UE has attached to it. Thus, the source eNB 1 then sends Handover_Request messages to other candidate eNBs 3 and 4. The candidate eNBs 3 and 4 reserve resources, shown at 6 and 7, and send a Handover_Request_Ack message back to the source eNB 1 if they are able to accept the UE. Thus, the Handover_Request message is sent to the target eNB 2 initially and then later to the candidate eNBs 3 and 4.
The UE then appears at the target eNB 2, shown at 12, and is recognized by the target eNB 2. The UE associates with the target eNB 2 which sends a Release_Resources message to the source eNB 1 and the source eNB 1 instructs the candidate eNBs 3 and 4 to release the resources they have reserved.
With reference to Figure 3, an alternative sequence to that shown in Figure 2 is similar in that the target node eNB 2 reserves resources at 5. However, this time, the UE appears at the target node eNB 2, and the target node eNB 2 sends a message to the source eNB 1 requesting it to release resources, before expiry of the predetermined time period set by the timer T11. Thus, the source eNB 1 does not need to request other candidate eNBs 3 and 4 to reserve resources, and the stages shown in the greyed out portion 13 are not carried out, thus avoiding the unnecessary use of resources and reducing signalling between the eNBs.

With reference to Figure 4, this illustrates the procedure when the UE does not appear at the target eNB 2, which has reserved resources shown at 5, during the predetermined time period T or after expiry of the time period T. Following expiry of the time period T, the source eNB 1 sends Handover_Request messages to the two candidate eNBs 3 and 4 and receives acknowledgements from both of them. The candidate eNBs 3 and 4 reserve resources at 6 and 7. The UE appears at one of the candidate eNBs 3, shown at 14, which accordingly requests the source eNB 1 to release the resources reserved for the UE once the UE has attached to its new eNB 3. The source eNB 1 then messages the target eNB 2 and the other candidate eNB 4 to instruct them to free the resources they have reserved for the UE, shown at 15 and 10.
In other arrangements the duration of the predetermined time period T is set to a value calculated by a combination, such as the minimum value, of one or more of the following components: (a) a time the source eNB 1 normally has to wait until the

Release_Resources message arrives from the target eNB 2, for example, the maximum duration of the 95 percent quartile; (b) the timer T1 used for the Radio Link Failure procedure in LTE, and this value may be set individually per UE; and (c) another timer, counter or event based on handover or RLF parameters, such as the timer T2 of the RLF procedure in LTE, or combination of these.
The present invention may be embodied in other specific forms and implemented by other methods without departing from its spirit or essential characteristics. The described embodiments and methods are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.

CLAIMS

1. A method for radio link failure recovery in a wireless communications network, including the steps of:

designating a network node as a target node to accept a mobile
terminal in the event of failure of a radio link between the mobile terminal and a source network node;

designating one or more other network nodes as candidate nodes; reserving resources at the target node;

sending a handover command to the mobile terminal when the target node is ready to accept handover of the mobile terminal from the source node;

starting a timer to define a predetermined time period from when the handover command is sent; and

reserving resources at the one or more candidate nodes when the predetermined time period has elapsed without the mobile terminal attaching to the target node.

2. The method as claimed in claim 1 and including the step of sending a handover request to a node to request it to reserve resources.

3. The method as claimed in claim 1 or 2 and, when the mobile terminal has attached to a node, including the step of the source node sending a request to free resources to other nodes that have reserved them.

4. The method as claimed in claim 1, 2 or 3 and wherein the predetermined time period is calculated from the normal time duration for the source node to receive a message from the designated node to release resources after receiving a handover request acknowledgement from the designated node.

5. The method as claimed in any preceding claim and wherein the predetermined time period is calculated using a timer specified for the radio link failure procedure.

6. The method as claimed in claim 5 and wherein the predetermined time period is calculated using the timer for radio link failure procedure and is set individually for each mobile terminal.

7. The method as claimed in claim 4 and 5 and wherein the predetermined time period is calculated using a combination of said normal time duration for the source node to receive a message from the designated node to release resources and the timer for the radio link failure procedure

8. The method as claimed in any preceding claim wherein the network is in accordance with Long Term Evolution (LTE) specifications.

9. The method as claimed in claim 8 and wherein the predetermined time period is calculated using at least one of the timers T1 and T2 defined in LTE specifications.

10. A wireless communications network comprising: a plurality of network nodes where a mobile terminal accesses the network via a source network node, another network node is designated as a target node to accept a mobile terminal in the event of failure of a radio link between the mobile terminal and the source network node, and one or more other network nodes are designated as candidate nodes; and a timer to define a predetermined time period from when a handover command is sent to the mobile terminal when the target node is ready to accept handover of the mobile terminal from the source node, and the network being operative to reserve resources at the target node, start the timer and reserve resources at the one or more candidate nodes when the predetermined time period has elapsed without the mobile terminal attaching to the target node.

Documents

Application Documents

# Name Date
1 4835-chenp-2010 power of attorney 03-08-2010.pdf 2010-08-03
1 4835-CHENP-2010-RELEVANT DOCUMENTS [03-08-2023(online)].pdf 2023-08-03
2 4835-CHENP-2010-RELEVANT DOCUMENTS [26-08-2022(online)].pdf 2022-08-26
2 4835-chenp-2010 pct 03-08-2010.pdf 2010-08-03
3 4835-CHENP-2010-RELEVANT DOCUMENTS [18-09-2021(online)].pdf 2021-09-18
3 4835-chenp-2010 form-5 03-08-2010.pdf 2010-08-03
4 4835-CHENP-2010-RELEVANT DOCUMENTS [23-03-2020(online)].pdf 2020-03-23
4 4835-chenp-2010 form-3 03-08-2010.pdf 2010-08-03
5 4835-CHENP-2010-RELEVANT DOCUMENTS [30-03-2019(online)].pdf 2019-03-30
5 4835-chenp-2010 form-2 03-08-2010.pdf 2010-08-03
6 4835-CHENP-2010-IntimationOfGrant10-04-2018.pdf 2018-04-10
6 4835-chenp-2010 form-18 03-08-2010.pdf 2010-08-03
7 4835-CHENP-2010-PatentCertificate10-04-2018.pdf 2018-04-10
7 4835-chenp-2010 form-1 03-08-2010.pdf 2010-08-03
8 Abstract_Granted 295623_10-04-2018.pdf 2018-04-10
8 4835-chenp-2010 drawings 03-08-2010.pdf 2010-08-03
9 Claims_Granted 295623_10-04-2018.pdf 2018-04-10
9 4835-chenp-2010 description(complete) 03-08-2010.pdf 2010-08-03
10 4835-chenp-2010 correspondence others 03-08-2010.pdf 2010-08-03
10 Description_Granted 295623_10-04-2018.pdf 2018-04-10
11 4835-chenp-2010 claims 03-08-2010.pdf 2010-08-03
11 Drawings_Granted 295623_10-04-2018.pdf 2018-04-10
12 4835-chenp-2010 abstract 03-08-2010.pdf 2010-08-03
12 Marked Up Claims_Granted 295623_10-04-2018.pdf 2018-04-10
13 4835-chenp-2010 form-13 05-01-2011.pdf 2011-01-05
13 Correpondence by Agent_Notarized Assignment_06-11-2017.pdf 2017-11-06
14 4835-chenp-2010 correspondence others 05-01-2011.pdf 2011-01-05
14 4835-CHENP-2010-ABSTRACT [31-10-2017(online)].pdf 2017-10-31
15 4835-chenp-2010 form-3 31-01-2011.pdf 2011-01-31
15 4835-CHENP-2010-CLAIMS [31-10-2017(online)].pdf 2017-10-31
16 4835-chenp-2010 correspondence others 31-01-2011.pdf 2011-01-31
16 4835-CHENP-2010-COMPLETE SPECIFICATION [31-10-2017(online)].pdf 2017-10-31
17 4006-CHENP-2010 FORM-3 19-06-2013.pdf 2013-06-19
17 4835-CHENP-2010-DRAWING [31-10-2017(online)].pdf 2017-10-31
18 4006-CHENP-2010 CORRESPONDENCE OTHERS 19-06-2013.pdf 2013-06-19
18 4835-CHENP-2010-FER_SER_REPLY [31-10-2017(online)].pdf 2017-10-31
19 4835-CHENP-2010-FORM 3 [31-10-2017(online)].pdf 2017-10-31
19 4835-CHENP-2010 FORM-3 13-02-2014.pdf 2014-02-13
20 4835-CHENP-2010 CORRESPONDENCE OTHERS 13-02-2014.pdf 2014-02-13
20 4835-CHENP-2010-FORM-26 [31-10-2017(online)].pdf 2017-10-31
21 4835-CHENP-2010-FER.pdf 2017-05-01
21 4835-CHENP-2010-OTHERS [31-10-2017(online)].pdf 2017-10-31
22 4835-CHENP-2010-PETITION UNDER RULE 137 [31-10-2017(online)].pdf 2017-10-31
22 4835-CHENP-2010-Proof of Right (MANDATORY) [31-10-2017(online)].pdf 2017-10-31
23 4835-CHENP-2010-PETITION UNDER RULE 137 [31-10-2017(online)].pdf 2017-10-31
23 4835-CHENP-2010-Proof of Right (MANDATORY) [31-10-2017(online)].pdf 2017-10-31
24 4835-CHENP-2010-FER.pdf 2017-05-01
24 4835-CHENP-2010-OTHERS [31-10-2017(online)].pdf 2017-10-31
25 4835-CHENP-2010-FORM-26 [31-10-2017(online)].pdf 2017-10-31
25 4835-CHENP-2010 CORRESPONDENCE OTHERS 13-02-2014.pdf 2014-02-13
26 4835-CHENP-2010 FORM-3 13-02-2014.pdf 2014-02-13
26 4835-CHENP-2010-FORM 3 [31-10-2017(online)].pdf 2017-10-31
27 4006-CHENP-2010 CORRESPONDENCE OTHERS 19-06-2013.pdf 2013-06-19
27 4835-CHENP-2010-FER_SER_REPLY [31-10-2017(online)].pdf 2017-10-31
28 4006-CHENP-2010 FORM-3 19-06-2013.pdf 2013-06-19
28 4835-CHENP-2010-DRAWING [31-10-2017(online)].pdf 2017-10-31
29 4835-chenp-2010 correspondence others 31-01-2011.pdf 2011-01-31
29 4835-CHENP-2010-COMPLETE SPECIFICATION [31-10-2017(online)].pdf 2017-10-31
30 4835-chenp-2010 form-3 31-01-2011.pdf 2011-01-31
30 4835-CHENP-2010-CLAIMS [31-10-2017(online)].pdf 2017-10-31
31 4835-chenp-2010 correspondence others 05-01-2011.pdf 2011-01-05
31 4835-CHENP-2010-ABSTRACT [31-10-2017(online)].pdf 2017-10-31
32 4835-chenp-2010 form-13 05-01-2011.pdf 2011-01-05
32 Correpondence by Agent_Notarized Assignment_06-11-2017.pdf 2017-11-06
33 4835-chenp-2010 abstract 03-08-2010.pdf 2010-08-03
33 Marked Up Claims_Granted 295623_10-04-2018.pdf 2018-04-10
34 4835-chenp-2010 claims 03-08-2010.pdf 2010-08-03
34 Drawings_Granted 295623_10-04-2018.pdf 2018-04-10
35 4835-chenp-2010 correspondence others 03-08-2010.pdf 2010-08-03
35 Description_Granted 295623_10-04-2018.pdf 2018-04-10
36 4835-chenp-2010 description(complete) 03-08-2010.pdf 2010-08-03
36 Claims_Granted 295623_10-04-2018.pdf 2018-04-10
37 Abstract_Granted 295623_10-04-2018.pdf 2018-04-10
37 4835-chenp-2010 drawings 03-08-2010.pdf 2010-08-03
38 4835-CHENP-2010-PatentCertificate10-04-2018.pdf 2018-04-10
38 4835-chenp-2010 form-1 03-08-2010.pdf 2010-08-03
39 4835-CHENP-2010-IntimationOfGrant10-04-2018.pdf 2018-04-10
39 4835-chenp-2010 form-18 03-08-2010.pdf 2010-08-03
40 4835-CHENP-2010-RELEVANT DOCUMENTS [30-03-2019(online)].pdf 2019-03-30
40 4835-chenp-2010 form-2 03-08-2010.pdf 2010-08-03
41 4835-CHENP-2010-RELEVANT DOCUMENTS [23-03-2020(online)].pdf 2020-03-23
41 4835-chenp-2010 form-3 03-08-2010.pdf 2010-08-03
42 4835-CHENP-2010-RELEVANT DOCUMENTS [18-09-2021(online)].pdf 2021-09-18
42 4835-chenp-2010 form-5 03-08-2010.pdf 2010-08-03
43 4835-chenp-2010 pct 03-08-2010.pdf 2010-08-03
43 4835-CHENP-2010-RELEVANT DOCUMENTS [26-08-2022(online)].pdf 2022-08-26
44 4835-chenp-2010 power of attorney 03-08-2010.pdf 2010-08-03
44 4835-CHENP-2010-RELEVANT DOCUMENTS [03-08-2023(online)].pdf 2023-08-03

Search Strategy

1 4835search_26-04-2017.pdf

ERegister / Renewals

3rd: 13 Apr 2018

From 02/02/2011 - To 02/02/2012

4th: 13 Apr 2018

From 02/02/2012 - To 02/02/2013

5th: 13 Apr 2018

From 02/02/2013 - To 02/02/2014

6th: 13 Apr 2018

From 02/02/2014 - To 02/02/2015

7th: 13 Apr 2018

From 02/02/2015 - To 02/02/2016

8th: 13 Apr 2018

From 02/02/2016 - To 02/02/2017

9th: 13 Apr 2018

From 02/02/2017 - To 02/02/2018

10th: 13 Apr 2018

From 02/02/2018 - To 02/02/2019

11th: 13 Apr 2018

From 02/02/2019 - To 02/02/2020

12th: 03 Jan 2020

From 02/02/2020 - To 02/02/2021

13th: 04 Jan 2021

From 02/02/2021 - To 02/02/2022

14th: 30 Dec 2021

From 02/02/2022 - To 02/02/2023