CN107567041B - Method and equipment for processing wireless link fault - Google Patents
Method and equipment for processing wireless link fault Download PDFInfo
- Publication number
- CN107567041B CN107567041B CN201710672611.4A CN201710672611A CN107567041B CN 107567041 B CN107567041 B CN 107567041B CN 201710672611 A CN201710672611 A CN 201710672611A CN 107567041 B CN107567041 B CN 107567041B
- Authority
- CN
- China
- Prior art keywords
- rlc
- terminal
- network side
- carrier
- logical channel
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method and equipment for processing a wireless link fault, which are used for solving the problems that redundant cell selection processes and service interruption are easy to occur in a wireless link fault processing mechanism in the prior art. The terminal suspends the transmission of the logical channel and/or reestablishes the failed RLC after determining that the member carrier corresponding to the logical channel of the failed RLC is the non-primary carrier. As the failed RLC corresponding to the non-main carrier wave adopts the transmission suspending the logic channel and/or the re-establishment of the failed RLC, the times of redundant cell selection process and service interruption are reduced, and the system performance is improved.
Description
Technical Field
The present invention relates to the field of wireless communications technologies, and in particular, to a method and a device for handling a wireless link failure.
background
In the 5G NR (new air interface), because different services are supported and different types of physical resources are supported by different services, each service (i.e., RB (Radio Bearer)) is allowed to be transmitted only on some specific physical resources, and related information is configured by the network side through an RRC message.
in the configuration of single connection of LTE system (including CA (Carrier Aggregation) and non (non) CA), 1 service is carried on one RLC (Radio Link Control) entity.
when the working mode of the terminal is an RLC AM (acknowledged mode), if the transmission of one data packet reaches the maximum retransmission number, an ARQ (Automatic Repeat reQuest) failure is triggered, thereby causing an RLC failure.
in order to solve the problem that bearer transmission cannot continue, an RLC Failure triggers an RLF (Radio Link Failure) process.
Currently, in a mechanism for handling Long Term Evolution (LTE) radio link failure, when an RLC failure occurs in any one AM RLC entity, RLF is triggered. However, for a UE (terminal) operating in the CA mode, a radio link failure does not mean that the PCell (Primary Cell) cannot operate normally. If the PCell is still operational, triggering the RLF and UE re-establishment procedures, unnecessary cell selection procedures and service interruptions are introduced.
In summary, the existing mechanism for handling radio link failure under 5G is prone to redundant cell selection procedures and service interruption.
Disclosure of Invention
The invention provides a method and equipment for processing a wireless link fault, which are used for solving the problem that redundant cell selection processes and service interruption are easy to occur in a wireless link fault processing mechanism in the prior art.
The embodiment of the invention provides a method for processing wireless link faults, which comprises the following steps:
After the RLC fails, the terminal determines a member carrier corresponding to the logical channel of the failed RLC according to the binding relationship between the logical channel and the member carrier;
and after determining that the member carrier corresponding to the logical channel of the RLC is a non-main carrier, the terminal suspends the transmission of the logical channel and/or reestablishes the RLC with the fault.
another method for processing a radio link failure according to an embodiment of the present invention includes:
The method comprises the steps that network side equipment receives information of a faulted RLC reported by a terminal, wherein the information of the faulted RLC is sent by the terminal after determining that a member carrier corresponding to a logical channel of the faulted RLC is a non-main carrier;
And the network side equipment instructs the terminal to reconfigure or delete the failed RLC through the instruction.
The embodiment of the invention provides a terminal for processing wireless link faults, which comprises:
The carrier determining module is used for determining the member carrier corresponding to the logic channel of the failed RLC according to the binding relationship between the logic channel and the member carrier after the RLC fails;
and the processing module is used for suspending the transmission of the logical channel and/or reestablishing the failed RLC after determining that the member carrier corresponding to the logical channel of the RLC is the non-main carrier.
the embodiment of the invention provides a network side device for processing wireless link failure, which comprises:
The receiving module is used for receiving information of the failed RLC reported by the terminal, wherein the information of the failed RLC is sent by the terminal after determining that a member carrier corresponding to a logical channel of the failed RLC is a non-main carrier;
and the notification module is used for indicating the terminal to reconfigure or delete the failed RLC through the instruction.
Another terminal for processing a radio link failure according to an embodiment of the present invention includes:
At least one processing unit, and at least one memory unit, wherein the memory unit stores program code that, when executed by the processing unit, causes the processing unit to implement any method by which a terminal handles radio link failures.
Another network side device for processing a radio link failure according to an embodiment of the present invention includes:
At least one processing unit, and at least one memory unit, wherein the memory unit stores program code that, when executed by the processing unit, causes the processing unit to implement any method for a network side device to handle a radio link failure.
An embodiment of the present invention provides a storage medium readable by a computing device, in which a software program is stored, and includes a program code, and when the program code runs on the computing device, the software program, when being read and executed by one or more processors, implements any method for handling a radio link failure by a terminal.
another storage medium readable by a computing device is provided by an embodiment of the present invention, and the storage medium stores therein a software program, which includes program code, and when the program code runs on the computing device, the software program, when read and executed by one or more processors, implements any method for a network-side device to handle a wireless link failure.
the terminal suspends the transmission of the logical channel and/or reestablishes the failed RLC after determining that the member carrier corresponding to the logical channel of the failed RLC is the non-primary carrier. As the failed RLC corresponding to the non-main carrier wave adopts the transmission suspending the logic channel and/or the re-establishment of the failed RLC, the times of redundant cell selection process and service interruption are reduced, and the system performance is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
FIG. 1 is a schematic diagram of a system for handling radio link failure according to an embodiment of the present invention;
Fig. 2 is a schematic structural diagram of a first terminal according to an embodiment of the present invention;
Fig. 3 is a schematic structural diagram of a first network-side device according to an embodiment of the present invention;
Fig. 4 is a schematic structural diagram of a second terminal according to an embodiment of the present invention;
Fig. 5 is a schematic structural diagram of a second network-side device according to an embodiment of the present invention;
Fig. 6 is a flowchart illustrating a method for a terminal to handle a radio link failure according to an embodiment of the present invention;
Fig. 7 is a flowchart illustrating a method for a network side device to process a radio link failure in cooperation with a terminal according to an embodiment of the present invention;
FIG. 8 is a diagram illustrating a first CA scenario according to an embodiment of the present invention;
FIG. 9 is a diagram illustrating a second CA scenario according to the embodiment of the present invention;
Fig. 10 is a diagram illustrating a third CA scenario according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
As shown in fig. 1, the system for processing radio link failure according to the embodiment of the present invention includes:
The terminal 10 is configured to determine, after an RLC failure occurs, a component carrier corresponding to a logical channel of the failed RLC according to a binding relationship between the logical channel and the component carrier; and after determining that the member carrier corresponding to the logical channel of the RLC is the non-main carrier, suspending the transmission of the logical channel and/or reestablishing the RLC with the fault.
the network side device 20 is configured to receive information of a failed RLC reported by a terminal, where the information of the failed RLC is sent by the terminal after determining that a member carrier corresponding to a logical channel of the failed RLC is a non-primary carrier; and instructing the terminal to reconfigure or delete the failed RLC through the instruction.
The terminal suspends the transmission of the logical channel and/or reestablishes the failed RLC after determining that the member carrier corresponding to the logical channel of the failed RLC is the non-primary carrier. As the failed RLC corresponding to the non-main carrier wave adopts the transmission suspending the logic channel and/or the re-establishment of the failed RLC, the times of redundant cell selection process and service interruption are reduced, and the system performance is improved.
The binding relationship between the logic channel and the member carrier wave is configured to the terminal by the network side.
In implementation, after an RLC fails, the terminal determines whether a member carrier corresponding to a logical channel of the failed RLC is a non-primary carrier according to a binding relationship between the logical channel and the member carrier, and if so, suspends transmission of the logical channel and/or reestablishes the failed RLC.
And if the member carrier corresponding to the logical channel of the RLC with the fault is the main carrier, the terminal triggers a radio link fault process.
optionally, if the member carrier corresponding to the logical channel of the failed RLC is a non-primary carrier, the terminal reports information of the failed RLC to the network side device;
Correspondingly, after receiving the information of the failed RLC reported by the terminal, the network side equipment instructs the terminal to reconfigure or delete the failed RLC through an instruction;
And the terminal reconfigures or deletes the failed RLC according to the received instruction from the network side equipment.
the scheme of the embodiment of the invention can be applied to CA or CA duplicate.
If the method is applied to the CA, the network side equipment can indicate the terminal to reconfigure the faulted RLC through an instruction after receiving the information of the faulted RLC reported by the terminal;
Correspondingly, the terminal reconfigures the failed RLC according to the received instruction from the network side equipment.
If the method is applied to CA duplicate, after receiving the information of the failed RLC reported by the terminal, the network side equipment can instruct the terminal to reconfigure the failed RLC through an instruction;
correspondingly, the terminal reconfigures the failed RLC according to the received instruction from the network side equipment.
if the method is applied to the CA duplicate, the network side equipment can also instruct the terminal to delete the failed RLC through an instruction after receiving the information of the failed RLC reported by the terminal;
Correspondingly, the terminal deletes the failed RLC according to the received instruction from the network side equipment.
Optionally, if the terminal is applied to CA duplexing, after the CA duplexing is deactivated, if there is an RLC in which a corresponding member carrier is a main carrier in the RLC of the terminal, the network side device instructs the terminal to reserve the RLC of the corresponding main carrier according to the configuration of the network side device, and deactivates other RLC;
Correspondingly, the terminal reserves the RLC corresponding to the main carrier according to the configuration of the network side equipment and deactivates other RLC.
For example, the terminal has RLC1, RLC2 and RLC3, wherein the component carrier corresponding to RLC1 is the main carrier, and the component carriers corresponding to RLC2 and RLC3 are not the main carrier. After the CA duplexing is deactivated, the terminal reserves RLC1, and deactivates RLC2 and RLC 3.
or
If the terminal is applied to the CA duplicate, after the CA duplicate is deactivated, if no corresponding member carrier is the RLC of the main carrier in the RLC of the terminal, the network side equipment indicates the terminal to reserve the RLC specified by the network side equipment, and other RLC is deactivated.
correspondingly, the terminal reserves the RLC appointed by the network side equipment according to the configuration of the network side equipment and deactivates other RLC.
For example, the terminal has RLC1, RLC2 and RLC3, wherein the component carriers corresponding to RLC1, RLC2 and RLC3 are not host carriers. After the CA duplexing is deactivated, the network side device may select which RLC (or which) is (are) reserved from RLC1, RLC2 and RLC3, and assuming that RLC2 is reserved, the terminal reserves RLC2 and deactivates RLC1 and RLC 3.
As shown in fig. 2, a first terminal according to an embodiment of the present invention includes:
A carrier determining module 200, configured to determine, after an RLC failure occurs, a component carrier corresponding to a logical channel of the failed RLC according to a binding relationship between the logical channel and the component carrier;
the processing module 201 is configured to suspend transmission of a logical channel and/or reestablish a failed RLC after determining that a component carrier corresponding to the logical channel of the RLC is an inactive carrier.
optionally, the processing module 201 is further configured to:
And triggering a radio link failure process after determining that the member carrier corresponding to the logical channel of the RLC is the main carrier.
Optionally, the processing module 201 is further configured to:
reporting information of the faulted RLC to network side equipment after determining that a member carrier corresponding to a logical channel of the RLC is a non-main carrier; and reconfiguring or deleting the failed RLC according to the received instruction from the network side equipment.
Optionally, the terminal is applied to CA or CA duplexing.
Optionally, the terminal is applied to CA duplexing; the processing module 201 is further configured to:
After the CA duplicate is deactivated, if the corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, reserving the RLC of the corresponding main carrier according to the configuration of the network side equipment, and deactivating other RLC; or
and after the CA duplicate is deactivated, if no corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, reserving the RLC specified by the network side equipment according to the configuration of the network side equipment, and deactivating other RLC.
as shown in fig. 3, a first network-side device according to an embodiment of the present invention includes:
a receiving module 300, configured to receive information of a failed RLC reported by a terminal, where the information of the failed RLC is sent by the terminal after determining that a member carrier corresponding to a logical channel of the failed RLC is a non-primary carrier;
A notifying module 301, configured to instruct the terminal to reconfigure or delete the failed RLC through the instruction.
Optionally, the terminal is applied to CA duplexing;
the notification module 301 is further configured to:
after the CA duplicate is deactivated, if the corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, the terminal is instructed to reserve the RLC of the corresponding main carrier according to the configuration of the network side equipment and deactivate other RLC; or
And after the CA duplicate is deactivated, if no corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, indicating the terminal to reserve the RLC specified by the network side equipment and deactivating other RLC.
As shown in fig. 4, a second terminal according to the embodiment of the present invention includes:
At least one processing unit 400, and at least one memory unit 401, wherein said memory unit stores program code which, when executed by said processing unit, causes said processing unit to perform the following:
After the RLC fails, determining a member carrier corresponding to the logical channel of the failed RLC according to the binding relationship between the logical channel and the member carrier; and after determining that the member carrier corresponding to the logical channel of the RLC is the non-main carrier, suspending the transmission of the logical channel and/or reestablishing the RLC with the fault.
Optionally, the processing unit 400 is further configured to:
And triggering a radio link failure process after determining that the member carrier corresponding to the logical channel of the RLC is the main carrier.
optionally, the processing unit 400 is further configured to:
Reporting information of the faulted RLC to network side equipment after determining that a member carrier corresponding to a logical channel of the RLC is a non-main carrier; and reconfiguring or deleting the failed RLC according to the received instruction from the network side equipment.
Optionally, the terminal is applied to CA or CA duplexing.
Optionally, the terminal is applied to CA duplexing; the processing unit 400 is further configured to:
after the CA duplicate is deactivated, if the corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, reserving the RLC of the corresponding main carrier according to the configuration of the network side equipment, and deactivating other RLC; or
And after the CA duplicate is deactivated, if no corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, reserving the RLC specified by the network side equipment according to the configuration of the network side equipment, and deactivating other RLC.
As shown in fig. 5, a second network-side device according to the embodiment of the present invention includes:
At least one processing unit 500 and at least one memory unit 501, wherein the memory unit stores program code that, when executed by the processing unit, causes the processing unit to perform the following:
receiving information of a failed RLC reported by a terminal, wherein the information of the failed RLC is sent by the terminal after determining that a member carrier corresponding to a logical channel of the failed RLC is a non-main carrier; and instructing the terminal to reconfigure or delete the failed RLC through the instruction.
optionally, the terminal is applied to CA duplexing;
The processing unit 500 is further configured to:
After the CA duplicate is deactivated, if the corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, the terminal is instructed to reserve the RLC of the corresponding main carrier according to the configuration of the network side equipment and deactivate other RLC; or
And after the CA duplicate is deactivated, if no corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, indicating the terminal to reserve the RLC specified by the network side equipment and deactivating other RLC.
The embodiment of the invention also provides a storage medium readable by the computing equipment, namely, the content is not lost after power failure. The storage medium has stored therein a software program comprising program code which, when said program code is run on a computing device, when read and executed by one or more processors, implements any of the above described schemes for a terminal to handle radio link failure.
the embodiment of the invention also provides a storage medium readable by the computing equipment, namely, the content is not lost after power failure. The storage medium stores therein a software program comprising program code which, when read and executed by one or more processors, implements any of the above-described schemes for a network-side device to handle radio link failure when the program code is run on a computing device.
Based on the same inventive concept, the embodiment of the present invention further provides a method for a terminal to process a wireless link failure, and since the device corresponding to the method is the terminal in the system for processing a wireless link failure in the embodiment of the present invention, and the principle of the method for solving the problem is similar to that of the system, the implementation of the method can refer to the implementation of the system, and repeated details are not repeated.
As shown in fig. 6, the method for processing a radio link failure by a terminal according to the embodiment of the present invention includes:
Step 600, after the RLC fails, the terminal determines a member carrier corresponding to the logical channel of the failed RLC according to the binding relationship between the logical channel and the member carrier;
step 601, after determining that the member carrier corresponding to the logical channel of the RLC is the non-primary carrier, the terminal suspends transmission of the logical channel and/or reestablishes the failed RLC.
optionally, after the terminal determines the member carrier corresponding to the logical channel of the failed RLC, the method further includes:
and the terminal triggers a radio link failure process after determining that the member carrier corresponding to the logical channel of the RLC is the main carrier.
optionally, after determining that the member carrier corresponding to the logical channel of the RLC is the non-primary carrier, the terminal further includes:
The terminal reports the information of the faulted RLC to the network side equipment;
and the terminal reconfigures or deletes the failed RLC according to the received instruction from the network side equipment.
Optionally, the terminal is applied to CA or CA duplexing.
Optionally, the terminal is applied to CA duplexing; the method further comprises the following steps:
After the CA duplicate is deactivated, if the corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, the terminal reserves the RLC of the corresponding main carrier according to the configuration of the network side equipment and deactivates other RLC; or
After the CA duplicate is deactivated, if no corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, the terminal reserves the RLC specified by the network side equipment according to the configuration of the network side equipment, and deactivates other RLC.
Based on the same inventive concept, the embodiment of the present invention further provides a method for a network side device to process a radio link failure, because the device corresponding to the method is the network side device in the system for processing a radio link failure in the embodiment of the present invention, and the principle of the method for solving the problem is similar to that of the system, the implementation of the method can refer to the implementation of the system, and repeated details are not repeated.
As shown in fig. 7, the method for processing a radio link failure by a network side device cooperating with a terminal according to the embodiment of the present invention includes:
step 700, a network side device receives information of a failed RLC reported by a terminal, wherein the information of the failed RLC is sent by the terminal after determining that a member carrier corresponding to a logical channel of the failed RLC is a non-main carrier;
And 701, the network side equipment instructs the terminal to reconfigure or delete the failed RLC through the instruction.
Optionally, the terminal is applied to CA duplexing; the method further comprises the following steps:
After the CA duplicate is deactivated, if the corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, the network side equipment indicates the terminal to reserve the RLC of the corresponding main carrier according to the configuration of the network side equipment and deactivate other RLC; or
After the CA duplicate is deactivated, if no corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, the network side equipment indicates the terminal to reserve the RLC specified by the network side equipment, and deactivates other RLC.
the following describes the embodiments of the present invention by way of a few examples.
Assuming that the terminal is in a CA scenario, there are RLC1 and RLC2, RLC1 is configured on the PCell, and RLC2 is configured on the SCell, which may be specifically referred to fig. 8.
Instance one, RLC1 failed.
step 1, after determining that the RLC1 has a fault, the terminal determines that the member carrier corresponding to the logical channel of the RLC1 is the PCell according to the binding relationship between the logical channel and the member carrier.
and step 2, the terminal triggers a wireless link failure process and a connection reestablishment process.
example two, RLC2 failed.
Step 1, after determining that the RLC2 fails, the terminal determines that the member carrier corresponding to the logical channel of the RLC2 is the SCell according to the binding relationship between the logical channel and the member carrier.
And step 2, the terminal suspends the transmission of the RLC2 and/or reestablishes the failed RLC 2.
And step 3, the terminal reports the information of the RLC2 with the fault to the network side equipment.
And 4, after receiving the information of the failed RLC2, the network side equipment sets the RLC2 to perform data transmission through the PCell and notifies the terminal through a reconfiguration message.
and step 5, after the terminal receives the reconfiguration message, setting the transmission of the RLC2 to the PCell according to the configuration information in the reconfiguration message, and recovering the transmission of the RLC 2.
And 6, the terminal returns a reconfiguration completion message to the network side equipment.
assume that the terminal is in a CA scenario, with RLC1 and RLC2, and RLC1 and RLC2 both belonging to SCG. RLC1 is configured on PCell and RLC2 is configured on SCell, as can be seen in fig. 8.
instance one, RLC1 failed.
step 1, after determining that the RLC1 has a fault, the terminal determines that the member carrier corresponding to the logical channel of the RLC1 is the PCell according to the binding relationship between the logical channel and the member carrier.
and step 2, the terminal triggers a wireless link failure process.
specifically, the terminal triggers a SCG (Secondary Cell Group) failure process, stops all data transmission and reception on the SCG, and reports information of the failed SCG through an MCG (Master Cell Group).
example two, RLC2 failed.
Step 1, after determining that the RLC2 fails, the terminal determines that the member carrier corresponding to the logical channel of the RLC2 is the SCell according to the binding relationship between the logical channel and the member carrier.
And step 2, the terminal suspends the transmission of the RLC2 and/or reestablishes the failed RLC 2.
And step 3, the terminal reports the information (which can be reported by MCG or SCG) of the RLC2 with the fault to the network side equipment.
And 4, after receiving the information of the failed RLC2, the network side equipment sets the RLC2 to perform data transmission through the PCell and notifies the terminal through a reconfiguration message.
And step 5, after the terminal receives the reconfiguration message, setting the transmission of the RLC2 to the PCell according to the configuration information in the reconfiguration message, and recovering the transmission of the RLC 2.
And 6, the terminal returns a reconfiguration completion message to the network side equipment.
Assuming that the terminal is in a CA duplicate scenario, there are RLC1 and RLC2, RLC1 is configured on the PCell, and RLC2 is configured on the SCell, which can be specifically seen in fig. 9.
Instance one, RLC1 failed.
Step 1, after determining that the RLC1 has a fault, the terminal determines that the member carrier corresponding to the logical channel of the RLC1 is the PCell according to the binding relationship between the logical channel and the member carrier.
And step 2, the terminal triggers a wireless link failure process and a connection reestablishment process.
example two, RLC2 failed.
Step 1, after determining that the RLC2 fails, the terminal determines that the member carrier corresponding to the logical channel of the RLC2 is the SCell according to the binding relationship between the logical channel and the member carrier.
And step 2, the terminal suspends the transmission of the RLC2 and/or reestablishes the failed RLC 2.
And step 3, the terminal reports the information of the RLC2 with the fault to the network side equipment.
And 4, after receiving the information of the failed RLC2, the network side equipment deletes the RLC2 or sets the RLC2 to perform data transmission through the PCell and notifies the terminal through a reconfiguration message.
And step 5, after the terminal receives the reconfiguration message, if the terminal instructs to delete the RLC2, deleting the RLC2, and if the terminal instructs to set the RLC2 to transmit data through the PCell, setting the transmission of the RLC2 to the PCell according to the configuration information in the reconfiguration message, and recovering the transmission of the RLC 2.
and 6, the terminal returns a reconfiguration completion message to the network side equipment.
If the duplicate is deactivated, the network side equipment instructs the terminal to reserve the RLC1 to continue data transmission;
Accordingly, the terminal reserves RLC1 for data transmission.
It is assumed that the terminal is in a CA duplicate scenario, and there are RLC1 and RLC2, and RLC1 and RLC2 both belong to SCG. RLC1 is configured on SCell1, and RLC2 is configured on SCell2, see fig. 10 in particular.
Instance one, RLC1 failed.
step 1, after determining that the RLC1 has failed, the terminal determines that the member carrier corresponding to the logical channel of the RLC1 is the SCell1 according to the binding relationship between the logical channel and the member carrier.
And step 2, the terminal suspends the transmission of the RLC1 and/or reestablishes the failed RLC 1.
and step 3, the terminal reports the information of the RLC1 with the fault to the network side equipment.
and 4, after receiving the information of the failed RLC1, the network side equipment deletes the RLC2 or sets the RLC1 to perform data transmission through the PCell and notifies the terminal through a reconfiguration message.
And step 5, after the terminal receives the reconfiguration message, if the terminal instructs to delete the RLC2, deleting the RLC2, and if the terminal instructs to set the RLC1 to transmit data through the PCell, setting the transmission of the RLC1 to the PCell according to the configuration information in the reconfiguration message, and recovering the transmission of the RLC 1.
And 6, the terminal returns a reconfiguration completion message to the network side equipment.
if the duplicate is deactivated, the network side equipment indicates the terminal to reserve the RLC1 for continuing data transmission through an RRC message;
Accordingly, the terminal reserves RLC1 for data transmission.
Example two, RLC2 failed.
The RLC2 failure is handled in a similar manner to the RLC1 failure, and is not described herein again.
the present application is described above with reference to block diagrams and/or flowchart illustrations of methods, apparatus (systems) and/or computer program products according to embodiments of the application. It will be understood that one block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, and/or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, create means for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks.
accordingly, the subject application may also be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.). Furthermore, the present application may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system. In the context of this application, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (12)
1. a method of handling radio link failure, the method comprising:
After a Radio Link Control (RLC) fails, the terminal determines a member carrier corresponding to a logical channel of the failed RLC according to the binding relationship between the logical channel and the member carrier;
after determining that the member carrier corresponding to the logical channel of the RLC is a non-main carrier, the terminal suspends the transmission of the logical channel and/or reestablishes the failed RLC;
The terminal is applied to carrier aggregation CA or CA repeated duplication;
after the terminal determines the member carrier corresponding to the logical channel of the failed RLC, the method further includes:
If the terminal determines that the member carrier corresponding to the logical channel of the RLC is the main carrier, triggering a wireless link failure process;
if the terminal determines that the member carrier corresponding to the logical channel of the RLC is a non-main carrier, the method further comprises the following steps: the terminal reports the information of the faulted RLC to the network side equipment;
and the terminal reconfigures or deletes the failed RLC according to the received instruction from the network side equipment.
2. The method of claim 1, wherein the terminal is used in CA duplexing; the method further comprises the following steps:
After the CA duplicate is deactivated, if the corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, the terminal reserves the RLC of the corresponding main carrier according to the configuration of the network side equipment and deactivates other RLC; or
after the CA duplicate is deactivated, if no corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, the terminal reserves the RLC specified by the network side equipment according to the configuration of the network side equipment, and deactivates other RLC.
3. A method of handling radio link failure, the method comprising:
the method comprises the steps that network side equipment receives information of a faulted RLC reported by a terminal, wherein the information of the faulted RLC is sent after the terminal determines that a member carrier corresponding to a logical channel of the faulted RLC is a non-main carrier and suspends the transmission of the logical channel and/or reestablishes the faulted RLC;
the network side equipment indicates the terminal to reconfigure or delete the failed RLC through an instruction;
The terminal is applied to carrier aggregation CA or CA repeated duplication.
4. The method of claim 3, wherein the terminal is used in a CA replication; the method further comprises the following steps:
after the CA duplicate is deactivated, if the corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, the network side equipment indicates the terminal to reserve the RLC of the corresponding main carrier according to the configuration of the network side equipment and deactivate other RLC; or
after the CA duplicate is deactivated, if no corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, the network side equipment indicates the terminal to reserve the RLC specified by the network side equipment, and deactivates other RLC.
5. A terminal for handling radio link failure, the terminal comprising:
the carrier determining module is used for determining the member carrier corresponding to the logic channel of the failed RLC according to the binding relationship between the logic channel and the member carrier after the RLC fails;
the processing module is used for suspending the transmission of the logical channel and/or reestablishing the failed RLC after determining that the member carrier corresponding to the logical channel of the RLC is the non-main carrier;
The terminal is applied to CA or CA duplicate;
wherein the processing module is further configured to:
Triggering a radio link failure process after determining that a member carrier corresponding to a logical channel of the RLC is a main carrier;
The processing module is further configured to:
Reporting information of the faulted RLC to network side equipment after determining that a member carrier corresponding to a logical channel of the RLC is a non-main carrier; and reconfiguring or deleting the failed RLC according to the received instruction from the network side equipment.
6. the terminal of claim 5, wherein the terminal is employed in a CA duplexing; the processing module is further configured to:
after the CA duplicate is deactivated, if the corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, reserving the RLC of the corresponding main carrier according to the configuration of the network side equipment, and deactivating other RLC; or
And after the CA duplicate is deactivated, if no corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, reserving the RLC specified by the network side equipment according to the configuration of the network side equipment, and deactivating other RLC.
7. a network side device for handling radio link failure, the network side device comprising:
The system comprises a receiving module and a sending module, wherein the receiving module is used for receiving information of a faulted RLC reported by a terminal, and the information of the faulted RLC is sent by the terminal after determining that a member carrier corresponding to a logical channel of the faulted RLC is a non-main carrier and suspending transmission of the logical channel and/or reestablishing the faulted RLC;
The notification module is used for indicating the terminal to reconfigure or delete the failed RLC through the instruction;
Wherein the terminal is applied in CA or CA duplexing.
8. The network-side device of claim 7, wherein the terminal is used in CA replication;
the notification module is further configured to:
after the CA duplicate is deactivated, if the corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, the terminal is instructed to reserve the RLC of the corresponding main carrier according to the configuration of the network side equipment and deactivate other RLC; or
And after the CA duplicate is deactivated, if no corresponding member carrier in the RLC of the terminal is the RLC of the main carrier, indicating the terminal to reserve the RLC specified by the network side equipment and deactivating other RLC.
9. A terminal for handling radio link failure, the terminal comprising:
At least one processing unit, and at least one memory unit, wherein the memory unit stores program code which, when executed by the processing unit, causes the processing unit to carry out the method of claim 1 or 2.
10. a network side device for handling radio link failure, the network side device comprising:
at least one processing unit, and at least one memory unit, wherein the memory unit stores program code which, when executed by the processing unit, causes the processing unit to carry out the method of claim 3 or 4.
11. a storage medium readable by a computing device, in which a software program is stored, comprising program code which, when said program code is run on a computing device, when read and executed by one or more processors, implements the method of claim 1 or 2.
12. a storage medium readable by a computing device, in which a software program is stored, comprising program code which, when said program code is run on a computing device, realizes the method of claim 3 or 4 when read and executed by one or more processors.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710672611.4A CN107567041B (en) | 2017-08-08 | 2017-08-08 | Method and equipment for processing wireless link fault |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710672611.4A CN107567041B (en) | 2017-08-08 | 2017-08-08 | Method and equipment for processing wireless link fault |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107567041A CN107567041A (en) | 2018-01-09 |
| CN107567041B true CN107567041B (en) | 2019-12-10 |
Family
ID=60974370
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710672611.4A Active CN107567041B (en) | 2017-08-08 | 2017-08-08 | Method and equipment for processing wireless link fault |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107567041B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019153139A1 (en) * | 2018-02-07 | 2019-08-15 | Oppo广东移动通信有限公司 | Radio link failure handling method and related product |
| CN110710143B (en) * | 2018-02-08 | 2021-01-12 | Oppo广东移动通信有限公司 | Method and terminal equipment for processing Radio Link Failure (RLF) |
| EP3751764B1 (en) | 2018-02-08 | 2021-12-22 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Method for handling radio link failure (rlf) and terminal device |
| US10616945B2 (en) * | 2018-02-15 | 2020-04-07 | Qualcomm Incorporated | Secondary cell group failure handling |
| RU2754777C1 (en) * | 2018-04-05 | 2021-09-07 | Телефонактиеболагет Лм Эрикссон (Пабл) | Control of radio communication link failures in wireless communication networks |
| CN112514449A (en) * | 2018-08-10 | 2021-03-16 | Oppo广东移动通信有限公司 | Information indication method and device, and terminal |
| CN112789879B (en) * | 2019-04-30 | 2023-02-28 | Oppo广东移动通信有限公司 | Radio link failure processing method, network equipment and terminal equipment |
| US20230138554A1 (en) * | 2020-04-23 | 2023-05-04 | Nokia Technologies Oy | Apparatus for wireless communications system and user equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014163419A1 (en) * | 2013-04-04 | 2014-10-09 | 주식회사 케이티 | Method for processing radio link failure and device therefor |
| CN105101253A (en) * | 2014-05-09 | 2015-11-25 | 上海贝尔股份有限公司 | Used method, main base station and user equipment in dual-connectivity system |
| CN105594141A (en) * | 2013-08-27 | 2016-05-18 | 三星电子株式会社 | Method and system for random access procedure and radio link failure in inter-eNB carrier aggregation |
| CN105960772A (en) * | 2014-01-31 | 2016-09-21 | 高通股份有限公司 | Procedures for managing secondary eNB (senb) radio link failure (s-rlf) in dual connectivity scenarios |
-
2017
- 2017-08-08 CN CN201710672611.4A patent/CN107567041B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014163419A1 (en) * | 2013-04-04 | 2014-10-09 | 주식회사 케이티 | Method for processing radio link failure and device therefor |
| CN105594141A (en) * | 2013-08-27 | 2016-05-18 | 三星电子株式会社 | Method and system for random access procedure and radio link failure in inter-eNB carrier aggregation |
| CN105960772A (en) * | 2014-01-31 | 2016-09-21 | 高通股份有限公司 | Procedures for managing secondary eNB (senb) radio link failure (s-rlf) in dual connectivity scenarios |
| CN105101253A (en) * | 2014-05-09 | 2015-11-25 | 上海贝尔股份有限公司 | Used method, main base station and user equipment in dual-connectivity system |
Non-Patent Citations (2)
| Title |
|---|
| Activation/deactivation for NR;NTT DOCOMO, INC.;《3GPP TSG-RAN WG2 Meeting 98，R2-1704338》;20170519;全文 * |
| Consideration on the activation/deactivation of data duplication for CA;ZTE;《3GPP TSG-RAN WG2 Meeting #98，R2-1704660》;20170519;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107567041A (en) | 2018-01-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107567041B (en) | Method and equipment for processing wireless link fault | |
| KR102455839B1 (en) | Connection failure recovery method and device | |
| CN105101253B (en) | Method, main base station and user equipment used in dual-connection system | |
| US11930554B2 (en) | Radio link failure handling method and related product | |
| WO2019137304A1 (en) | Data processing method, user side device, and network side device | |
| EP3499949B1 (en) | Method, device and system for processing control signalling | |
| CN110831248B (en) | Notification method, device and base station | |
| JP2020503804A (en) | Data transmission method and data transmission equipment | |
| CN111328118A (en) | Transmission method and device | |
| EP3734870B1 (en) | Notification methods and base stations for execution of pdcp data recovery | |
| CN108632869B (en) | Transmission control method and device | |
| CN109565728A (en) | A kind of data processing method and relevant device | |
| CN113424569A (en) | Method and apparatus for processing redundant protocol data unit sessions in a communication system | |
| KR20230028397A (en) | Cell group processing method, device and communication device | |
| EP4354944A1 (en) | Information processing method and apparatus | |
| JP2019527503A (en) | Data retransmission method and apparatus | |
| CN113038550A (en) | Method and apparatus for reestablishing network connection, storage medium, and electronic apparatus | |
| WO2022120744A1 (en) | Data transmission processing method and related apparatus | |
| KR20240047394A (en) | Live-Time State Triggering and Fallback Techniques for Replication Using Dual Connectivity | |
| CN111356248B (en) | Method and device for establishing connection between access network devices | |
| CN110401514B (en) | Counting method and communication device | |
| CN106686673A (en) | Processing method of SN changeover failure in UE switching process and device | |
| WO2018099302A1 (en) | Link processing method and link processing device | |
| CN111464269B (en) | Method and equipment for repeated transmission confirmation | |
| JP2016063377A (en) | Retransmission control method, mobile communication system, and base station |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee after: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY |
|
| CP01 | Change in the name or title of a patent holder | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20210601 Address after: 100085 1st floor, building 1, yard 5, Shangdi East Road, Haidian District, Beijing Patentee after: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd. Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY |
|
| TR01 | Transfer of patent right |