CN109219094B

CN109219094B - Base station switching and instance distribution method, RLC protocol implementation equipment, base station and terminal

Info

Publication number: CN109219094B
Application number: CN201710537510.6A
Authority: CN
Inventors: 肖黎英; 庄荣海
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2017-07-04
Filing date: 2017-07-04
Publication date: 2021-08-06
Anticipated expiration: 2037-07-04
Also published as: CN109219094A

Abstract

According to the base station switching and instance allocation method, the RLC protocol implementation device, the base station and the terminal provided by the embodiment of the invention, after receiving an RLC instance application request sent by a target base station for a DRB in an acknowledged mode in the process of switching base stations by a terminal, when the source base station is confirmed to have a reusable RLC instance according to the RLC instance application request, setting the RLC instance as the instance of the DRB at the target base station side, namely, multiplexing the RLC instance of the DRB at the source base station side into the RLC instance at the target base station side, at this time, the terminal does not need to perform RLC reconstruction on the DRB in the base station switching process, and the source base station side does not need to delete the original RLC instance, the method can avoid the PDCP retransmission of the RLC SDU messages lost in the RLC reestablishment process, improve the utilization efficiency of air interface bandwidth, improve the switching efficiency of the base station and reduce the interruption time of data transmission.

Description

Base station switching and instance distribution method, RLC protocol implementation equipment, base station and terminal

Technical Field

The present invention relates to the field of communications, and in particular, to a method for switching and allocating a base station, an RLC (Radio Link Control, Radio Link layer Control protocol) protocol implementation device, a base station, and a terminal.

Background

In a current 4G E-UTRA (Evolved-UMTS Terrestrial Radio Access, Evolved UMTS (universal Mobile Telecommunications system)) Mobile communication base station system, in most cases, base stations are deployed in a distributed manner, and therefore user plane protocol stacks of the base stations are usually distributed in different station rooms. The base station of the E-UTRA is called LTE (Long Term Evolution) eNB (evolved Node B).

Compared with an E-UTRA (evolved Universal terrestrial Radio) network, a 5G NR (New Radio) access network has great changes in the aspects of a wireless transmission technology, an air interface protocol and a system architecture, and provides a mobile communication network with higher speed, lower time delay, more connections and more flexibility. The base station of the NR is called the gbb. Meanwhile, the 4G E-UTRA access network will continue to evolve to Evolved E-UTRA, the base station of Evolved E-UTRA is called eLTE (Evolved Long Term Evolution), eNB, and can connect with NR core network. The 3GPP organization proposed in the 38.801 protocol a split deployment of NR base stations CU (Central Unit) -DU (Distributed Unit), see fig. 1 and 2.

And 8 slicing options for the CU-DU interface function slicing, see fig. 3 and 4. It should be noted that, although the CU-DU separation deployment is proposed for NR, it is not excluded to apply to (e) LTE eNB deployment. Among the real networking, C-RAN (centralized radio access network) is increasingly becoming the operator's preference because of its reduced need for site-machine room resources and its low CAPEX (Capital Expenditure) and OPEX (Operating cost) features. Under the condition that the CU-DU interface function segmentation selects the segmentation point 2, the situation of co-deployment of RLC layers of a multi-base station protocol stack exists. As in fig. 5, the NR gbb is co-deployed with the (e) LTE eNB RLC layer in the site room. Under the condition that the CU-DU interface function segmentation selects the segmentation point 7, the situation of co-deployment of RLC layers of a multi-base station protocol stack may exist. As in fig. 6, the NR gbb is co-deployed with the (e) LTE eNB RLC layer in the central office. In this scenario, a site room is usually not needed, and a Low-PHY (Physical Layer bottom Layer) and an RF are directly integrated on a device, and the device is connected to a central room through a switching network.

According to the existing 4G E-UTRA technology, when a terminal UE needs to be switched from a source base station to a destination base station for some reason, such as load balancing, since the handover is between base stations, the destination base station needs to create a new RLC instance for each DRB of the UE, regardless of whether NR gbb and (e) LTE eNB RLC layers are co-deployed or not, and regardless of the Data Radio Bearer (DRB) mode of the UE, the UE performs PDCP (Packet Data Convergence Protocol) re-establishment and RLC instance re-establishment, and the source base station deletes the original RLC instance of each DRB of the UE after the handover is successful. In the process, a new RLC instance is required to be established at the target base station side, and the PDCP retransmits the RLC SDU message lost in the RLC re-establishment process, so that air interface bandwidth is wasted, the base station switching efficiency is low, and the data transmission interruption time is long.

Disclosure of Invention

The base station switching and instance allocation method, the RLC protocol implementation device, the base station and the terminal provided by the embodiment of the invention mainly solve the technical problems that: the problems that the air interface bandwidth is wasted, the base station switching efficiency is low and the time of a data transmission terminal is long due to the fact that the RLC instance needs to be rebuilt in the base station switching process are solved.

To solve the foregoing technical problem, an embodiment of the present invention provides a base station handover control method, including:

receiving an RLC (Radio Link Control, Radio Link layer Control protocol) instance application request sent by a target base station aiming at a Data Radio Bearer (DRB) in a confirmation mode in the process of switching base stations by a terminal;

when the source base station is confirmed to have a reusable RLC instance according to the RLC instance application request, setting the RLC instance as the instance of the DRB at the target base station side;

and feeding back RLC application response information containing the information of the RLC instance to the target base station.

In order to solve the above problem, the present invention further provides a base station switching method, including:

in the process of switching base stations by a terminal, sending an RLC instance application request to RLC protocol implementation equipment aiming at a DRB in a confirmation mode;

receiving RLC application response information fed back by the RLC protocol implementation equipment;

when the RLC application response information comprises RLC instance information, sending a switching confirmation message containing that the DRB does not carry out RLC instance reestablishment identification to a source base station initiating switching;

and the RLC instance information is the RLC instance information which is extracted after the DRB instances on the target base station side are set as the RLC instance information when the RLC protocol implementation equipment confirms that the reusable RLC instance exists in the source base station according to the RLC instance application request.

receiving a switching command sent by a source base station, wherein the switching command comprises target base station information;

initiating an access request to a target base station according to the target base station information, and after the target base station is switched from the source base station, when the switching command contains an RLC instance reestablishment identifier which is not performed on the DRB in the confirmed mode, not reestablishing the RLC instance of the DRB in the confirmed mode;

the identifier for not performing RLC instance re-establishment is obtained by the source base station through the base station handover method as described above.

In order to solve the above problem, the present invention further provides an RLC protocol implementing device, including:

the system comprises an RLC management module, a target base station and a source base station, wherein the RLC management module is used for receiving an RLC instance application request sent by the target base station aiming at a DRB in a confirmation mode in the process of switching base stations by a terminal, setting the RLC instance as an instance of the DRB at the target base station side when the source base station is confirmed to have a reusable RLC instance according to the RLC instance application request, and feeding back RLC application response information containing information of the RLC instance to the target base station.

The system also comprises an RLC instance module, a protocol layer module and a service layer module, wherein the RLC instance module is used for realizing an RLC protocol function specified by a 3GPP protocol and providing a data transmission service for the PDCP layer; the RLC instance is created by an RLC management module and is distributed to the base station DRB instance for use by the RLC management module; the RLC instance can perceive that the terminal is successfully handed over to the target base station.

In order to solve the above problem, the present invention further provides a base station, including:

the terminal comprises an RLC configuration module, a source base station and a terminal, wherein the RLC configuration module is used for sending an RLC instance application request to RLC protocol implementation equipment aiming at a DRB in a confirmation mode in the process of switching base stations, receiving RLC application response information fed back by the RLC protocol implementation equipment, and sending a switching confirmation message containing an RLC instance reestablishment identifier of the DRB to the source base station initiating switching when the RLC application response information comprises the RLC instance information;

In order to solve the above problem, the present invention also provides a terminal, including:

the switching management module is used for receiving a switching command sent by a source base station, wherein the switching command comprises target base station information, and after an access request is initiated to a target base station according to the target base station information to switch from the source base station to the target base station, whether to initiate a reestablishment action to an RLC instance of a DRB in a confirmation mode is determined according to the judgment of the reestablishment strategy module;

the reestablishment strategy module is used for judging whether the DRB in the confirmed mode in the switching command contains an RLC instance reestablishment non-carrying out identification, if so, the DRB does not need to send an RLC reestablishment instruction to the RLC module; otherwise, an RLC re-establishment instruction for the DRB needs to be sent to the RLC module.

In order to solve the above problem, the present invention further provides an RLC protocol implementing device, including a first processor, a first memory and a first data bus;

the first data bus is used for connecting the first processor and the first memory in a communication mode;

the first memory is used for storing a base station switching control program;

the first processor is configured to run a base station handover control program in the first memory to implement the steps in the base station handover control method described above.

In order to solve the above problem, the present invention further provides a base station, including a second processor, a second memory, and a second data bus;

the second data bus is used for connecting the second processor and the second memory in a communication mode;

the second memory is used for storing a base station switching control program;

the second processor is configured to execute the base station handover program in the second memory to implement the steps in the base station handover method as described above.

In order to solve the above problem, the present invention further provides a terminal, including a third processor, a third memory, and a third data bus;

the third data bus is used for connecting the third processor and the third memory in a communication mode;

the third memory is used for storing a base station switching control program;

the third processor is configured to execute the base station handover program in the third memory to implement the steps in the base station handover method as described above.

The embodiment of the invention also provides a computer storage medium, wherein a computer executable instruction is stored in the computer storage medium, and the computer executable instruction is used for executing the base station switching control method or the base station switching method.

The invention has the beneficial effects that:

Drawings

FIG. 1 is a schematic diagram of NR gNB central unit/distribution unit;

fig. 2 is (e) a schematic diagram of an LTE eNB central unit/distribution unit;

FIG. 3 is a schematic diagram of a center unit-distribution unit interface segmentation selection;

FIG. 4 is a schematic diagram of each transmission layer corresponding to each segmentation point in FIG. 3;

fig. 5 is a schematic diagram of NR gbb and (e) LTE eNB protocol stack deployment corresponding to division point 2;

fig. 6 is a schematic diagram of NR gbb and (e) LTE eNB protocol stack deployment corresponding to a division point 7;

fig. 7 is a flowchart illustrating an example allocation method in a base station handover process according to an embodiment of the present invention;

fig. 8 is a flowchart illustrating an RLC instance release process according to an embodiment of the present invention;

fig. 9 is a schematic diagram of a base station handover method according to an embodiment of the present invention;

fig. 10 is a schematic diagram of a base station handover method at a terminal side according to an embodiment of the present invention;

fig. 11 is a schematic structural diagram of an RLC protocol implementation apparatus according to a second embodiment of the present invention;

fig. 12 is a schematic structural diagram of a base station according to a second embodiment of the present invention;

fig. 13 is a schematic structural diagram of a terminal according to a second embodiment of the present invention;

fig. 14 is a schematic structural diagram of an RLC protocol implementation apparatus according to a third embodiment of the present invention;

fig. 15 is a schematic structural diagram of a base station according to a third embodiment of the present invention;

fig. 16 is a schematic structural diagram of a terminal according to a third embodiment of the present invention;

fig. 17 is a first schematic structural diagram of a virtual base station and an RLC protocol implementing device module according to a fourth embodiment of the present invention;

fig. 18 is a schematic structural diagram of a terminal according to a fourth embodiment of the present invention;

fig. 19 is a first schematic diagram illustrating an RLC downlink data transfer procedure in a base station handover procedure according to a fourth embodiment of the present invention;

fig. 20 is a first schematic diagram illustrating an RLC uplink data transfer procedure in a base station handover procedure according to a fourth embodiment of the present invention;

fig. 21 is a second schematic structural diagram of a virtual base station and an RLC protocol implementation apparatus module according to a fourth embodiment of the present invention;

fig. 22 is a second schematic diagram illustrating an RLC downlink data transfer procedure in a base station handover procedure according to a fourth embodiment of the present invention;

fig. 23 is a diagram illustrating a second RLC uplink data transfer procedure in a base station handover procedure according to a fourth embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention are described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The first embodiment is as follows:

in the base station handover control method provided by this embodiment, for the situation that the base station RLC layers of NR gbb, (e) LTE eNB, and LTE eNB are co-deployed, the RLC instance of the DRB may be reused, so that when the terminal UE performs handover between base stations, for the DRB adopting an RLC Acknowledged Mode (AM), the RLC instances of the base station side and the UE side are not re-established, and the original RLC instance does not need to be deleted by the source base station side, which not only can improve the base station handover efficiency, reduce the data transmission interruption time, and improve the resource utilization rate. In addition, a Packet Data Convergence Protocol (PDCP) layer does not need to retransmit a PDCP Packet Data Unit (PDU), and a base station side does not need to forward an RLC context, so that the lossless handover process of the UE between the base stations is smoother, and the user experience is improved.

It should be understood that, in this embodiment, the triggering condition for the source base station to initiate the base station handover to the target base station may be various conditions that need to perform the base station handover, and details are not described herein again. The base station switching process in the embodiment relates to a source base station side, a target base station side, a terminal side and a base station switching control side; it should be understood that the RLC protocol implementing apparatus side in this embodiment may be separately provided from the source base station side and the target base station side, or may be collectively provided.

In this embodiment, the procedure for performing instance allocation for the base station handover control is as follows:

receiving an RLC instance application request sent by a target base station aiming at a DRB in a confirmation mode in the process of switching base stations by a terminal; when the source base station is confirmed to have the reusable RLC instance according to the RLC instance application request, setting the RLC instance as the instance of the DRB at the target base station side; and then feeding back RLC application response information containing the information of the RLC instance to the target base station.

In this embodiment, the RLC instance application request includes a target base station identifier, RLC configuration parameters, and RLC instance matching information corresponding to the DRB on the source base station side, where the RLC instance matching information includes a source base station identifier of the source base station; the method for confirming that the source base station has the reusable RLC instance according to the RLC instance application request comprises the following steps:

and determining that the source base station and the target base station are base stations hung under the source base station according to the source base station identification and the target base station identification, and setting the RLC instance as a reusable RLC instance as an instance of the DRB on the target base station side when the configuration parameters of the RLC instance corresponding to the DRB on the source base station side matched according to the RLC instance matching information are the same as the RLC configuration parameters. The above process is shown in fig. 7, and includes:

s701: and receiving an RLC instance application request sent by a target base station aiming at a DRB in a confirmation mode in the process of switching the base station by the terminal.

The RLC instance request in the step is initiated to the RLC protocol implementation equipment when the target base station receives the base station switching request sent by the source base station and the target base station allows switching according to the base station switching strategy; it should be understood that, of course, the target base station may not only send the RLC instance application request for the confirmation DRB, but also initiate the RLC instance application request for DRBs in other modes, and details thereof are not repeated herein.

In this step, the RLC instance application request sent by the target base station includes the target base station identifier, the RLC configuration parameters, and the RLC instance matching information corresponding to the DRB on the source base station side, and the RLC instance matching information only needs to uniquely determine the RLC instance corresponding to the DRB on the source base station side, and the content included in the RLC instance application request can be flexibly set according to a specific application scenario. The RLC instance matching information in this embodiment includes the source base station identifier of the source base station.

S702: judging that the source base station and the target base station are the base stations hung under the source base station and the target base station according to the source base station identification and the target base station identification, namely judging whether the source base station and the target base station belong to the common deployment condition of an RLC layer, if so, turning to S703; otherwise, go to S707.

S703: and matching the corresponding RLC instance of the DRB at the source base station side according to the RLC instance matching information.

S704: judging whether the configuration parameters of the RLC instance are the same as the RLC configuration parameters in the RLC instance application request, if so, turning to S705; otherwise, go to S707.

S705: and setting the RLC instance as the instance of the DRB on the target base station side.

S706: and feeding back RLC application response information containing the information of the RLC instance to the target base station. Therefore, after receiving the response message, the target base station can determine that the base station switching does not need to be performed with RLC reconstruction, and then performs subsequent switching operation with the source base station according to the base station switching process which does not need to be performed with RLC reconstruction.

S707: a new RLC instance is allocated.

In an example, the RLC instance matching information in the RLC instance application request may further include a source base station terminal identifier and an Evolved Radio Access Bearer (E-RAB) ID to which the DRB belongs, and the RLC instance application request further includes a target base station terminal identifier;

the example in which S706 sets the RLC instance to be DRB on the target base station side in this example includes:

and adding the target base station identification, the target base station terminal identification and the E-RAB ID in the reference information of the RLC instance. In this example, the E-RAB ID to which the base station ID + base station side terminal ID + DRB belongs uniquely corresponds to one RLC instance.

In this embodiment, the source base station may also send an RLC instance release request to the RLC protocol implementing apparatus after the base station of the terminal is handed over, but the release here is only to separate the RLC instance from the source base station, and the RLC instance does not need to be deleted because it is currently used by the target base station. The RLC instance release process is shown in fig. 8 and includes:

s801: and receiving an RLC instance release request sent by the source base station, wherein the RLC instance release request comprises a source base station identifier, a source base station terminal identifier and an E-RAB ID to which the DRB belongs, namely the RLC instance release request comprises RLC instance matching information.

S802: and finding the RLC instance corresponding to the source base station according to the source base station identifier, the source base station terminal identifier and the E-RAB ID to which the DRB belongs.

S803: and deleting the source base station identification, the source base station terminal identification and the E-RAB ID of the DRB in the reference information of the RLC instance, namely the RLC instance is not referred by the source base station.

In this embodiment, after detecting that the terminal is successfully handed over to the target base station through the RLC instance, the RLC protocol implementing device retransmits the downlink packet that has been sent but has not received the acknowledgement information through the previously set RLC instance, and/or sends the latest uplink RLC status report to the terminal.

In this embodiment, detecting (sensing) whether the terminal is successfully handed over to the target base station by using the RLC instance may adopt any one of the following manners:

the detection method comprises the following steps: and judging whether the RLC instance receives a first RLC status report sent by the terminal through the target base station, if so, judging that the terminal is successfully switched to the target base station.

And a second detection mode: and judging whether the RLC instance receives the first packet downlink forwarding data from the target base station, if so, judging that the terminal is successfully switched to the target base station.

Correspondingly, on the target base station side, as shown in fig. 9, the base station handover method includes:

s901: and in the process of switching the base station by the terminal, sending an RLC instance application request to the RLC protocol implementation equipment aiming at the acknowledged mode DRB.

As shown above, the RLC instance application request includes the target base station identifier, the RLC configuration parameters, and the RLC instance matching information corresponding to the DRB on the source base station side, where the RLC instance matching information includes the source base station identifier of the source base station.

S902: and receiving RLC application response information fed back by the RLC protocol implementation equipment.

S903: and when the RLC application response information comprises RLC instance information, sending a switching confirmation message containing an RLC instance reestablishment identifier to the source base station initiating the switching. As shown above, the RLC instance information here is RLC instance information extracted by the RLC protocol implementation device after the source base station identifier and the target base station identifier determine, according to the source base station identifier and the target base station identifier, that the source base station initiating handover and the target base station are base stations hung by themselves, and the configuration parameter of the RLC instance corresponding to the DRB on the source base station side, which is matched according to the RLC instance matching information, is the same as the RLC configuration parameter.

For example, when a handover confirm message is sent to the source base station, an Information Element (IE) may be added to the DRB object in the returned MobilityControlInfo container information, which is called DRB-RLCnotReset, and the asn.1 definition form is: [ [ drb-RLCnotReset ENUMERATED { true } OPTIONAL- -Cond HO ] ],

and taking the value of DRB-RLCnotReset as true, and indicating that the DRB RLC does not reestablish after the UE is switched.

And the source base station sends a switching command to the terminal after receiving the switching confirmation message, wherein the switching command comprises an RLC instance reestablishment non-carrying out identifier so as to indicate that the terminal does not need to reestablish the RLC instance of the DRB in the switching process of the base station. Referring to fig. 10, the method for switching base stations at the terminal side includes:

s101: and receiving a switching command sent by the source base station, wherein the switching command comprises the information of the target base station.

S102: judging whether the DRB in the acknowledged mode in the switching command contains an RLC instance reestablishment non-identification, if so, turning to S103; otherwise, go to S104.

S103: no re-establishment is performed for the RLC instance of the DRB. The RLC instance reestablishment non-performing flag is obtained by the source base station through the base station handover method as described above.

S104: entering a process of performing re-establishment on the RLC instance of the acknowledged mode DRB.

That is, after receiving a handover command including a target base station sent by a source base station, a terminal in this embodiment initiates an access request to the target base station according to the target base station information, and after switching from the source base station to the target base station, and when the handover command includes an RLC instance reestablishment flag that is not performed for a DRB in an acknowledged mode, the terminal does not reestablish the RLC instance of the DRB in the acknowledged mode.

In this embodiment, after accessing the target base station according to the target base station information, the terminal side sends a handover confirmation message to the target base station; and after sending the switching confirmation message to the target base station, immediately sending a downlink RLC status report to the target base station, so that the base station side RLC instance can immediately resend the message which is sent but does not receive the confirmation message, thereby reducing the data transmission interruption time as much as possible.

The base station switching and controlling method provided by the embodiment can directly reuse the RLC instance at the source base station side when the reuse condition of the RLC instance is met, so that the terminal does not need to perform RLC reconstruction in the switching process of the base station, and the PDCP layer is prevented from retransmitting RLC SDU lost due to RLC reconstruction; meanwhile, the original RLC instance is not required to be deleted on the source base station side, so that the utilization rate of air interface resources can be improved, the base station switching efficiency is improved, and the data transmission interruption time is shortened.

Example two:

referring to fig. 11, the present embodiment provides an RLC protocol implementing apparatus, which includes:

the RLC management module 111 initializes the RLC instance 112, and the initialization process is not described herein again; the method is also used for receiving an RLC instance application request sent by a target base station aiming at a DRB in a confirmation mode in the process of switching the base station by a terminal, setting the RLC instance as an instance of the DRB at the target base station side when the source base station is confirmed to have a reusable RLC instance according to the RLC instance application request, and feeding back RLC application response information containing information of the RLC instance to the target base station.

In this embodiment, the function of the RLC management module 111 may be specifically implemented by a processor of an RLC protocol implementation device, where the RLC instance application request includes a target base station identifier, an RLC configuration parameter, and RLC instance matching information corresponding to the DRB on a source base station side, where the RLC instance matching information includes a source base station identifier of a source base station; and the base station is used for determining that the source base station and the target base station are base stations hung under the base station according to the source base station identification and the target base station identification, setting the RLC instance as the instance of the DRB on the target base station side when the configuration parameters of the RLC instance corresponding to the DRB on the source base station side matched according to the RLC instance matching information are the same as the RLC configuration parameters, and feeding back RLC application response information containing the information of the RLC instance to the target base station.

the setting of the RLC instance to be the DRB instance on the target base station side by the RLC management module 111 includes: and adding the target base station identification, the target base station terminal identification and the E-RAB ID in the reference information of the RLC instance. In this example, the E-RAB ID to which the base station ID + base station side terminal ID + DRB belongs uniquely corresponds to one RLC instance.

The RLC management module 111 is further configured to receive an RLC instance release request sent by the source base station, where the RLC instance release request includes a source base station identifier, a source base station terminal identifier, and an E-RAB ID to which the DRB belongs, that is, includes RLC instance matching information, then find the RLC instance corresponding to the source base station according to the source base station identifier, the source base station terminal identifier, and the E-RAB ID to which the DRB belongs, delete the source base station identifier, the source base station terminal identifier, and the E-RAB ID to which the DRB belongs in the reference information of the RLC instance, that is, the RLC instance is not referred by the source base station.

In this embodiment, the RLC instance 112 retransmits the message that has been sent but has not received the acknowledgement information after detecting that the terminal is successfully handed over to the target base station; the messages include an uplink message sent to the target base station side and a downlink message sent to the terminal side.

The RLC instance 112 detects (senses) whether the terminal is successfully handed over to the target base station in any of the following ways:

the detection method comprises the following steps: and judging whether the RLC instance receives a first RLC status report sent by the terminal, if so, judging that the terminal is successfully switched to the target base station.

Referring to fig. 12, the present embodiment further provides a base station, which may be a source base station or a target base station, and includes:

an RLC configuration module 121, configured to send an RLC instance application request to an RLC protocol implementing device for a DRB in a acknowledged mode in a base station switching process of a terminal, where the RLC instance application request includes a target base station identifier, an RLC configuration parameter, and RLC instance matching information corresponding to the DRB on a source base station side, and the RLC instance matching information includes a source base station identifier of a source base station; and the RLC application response information which is used for receiving the RLC application response information containing the RLC instance information and fed back by the RLC protocol implementation equipment, and sending a switching confirmation message containing the RLC instance reestablishment identification to the source base station which initiates the switching when the RLC application response information comprises the RLC instance information. In one example, the functionality of the RLC configuration module 121 may be implemented by a central unit and/or a control module of the base station.

When the source base station receives the switching confirmation message and the switching confirmation message contains the RLC instance reestablishment non-carrying out identification, the source base station sends a switching command to the terminal, and the switching command contains the RLC instance reestablishment non-carrying out identification so as to indicate that the terminal does not need to carry out base station switching in the base station switching process.

Referring to fig. 13, the present embodiment further provides a terminal, including:

the handover management module 131 is configured to receive a handover command sent by a source base station, where the handover command includes target base station information, and the terminal initiates an access request to the target base station according to the target base station information, and after the source base station is handed over to the target base station, determines whether to initiate a reestablishment action on an RLC instance of a DRB in a confirmation mode according to a decision of the reestablishment policy module, where specifically, a function of the handover management module 131 may be implemented by a processor of the terminal.

A reestablishment policy module 132, configured to determine whether the DRB in the acknowledged mode in the handover command includes an RLC instance reestablishment non-performing identifier, and if so, no RLC reestablishment instruction for the DRB needs to be sent to the RLC module; otherwise, an RLC re-establishment instruction for the DRB needs to be sent to the RLC module, and specifically, the function of the re-establishment policy module 132 may be implemented by a processor of the terminal.

In this embodiment, after accessing the target base station according to the target base station information, the terminal side sends a handover confirmation message to the target base station; and after sending the switching confirmation message to the target base station, immediately sending a downlink RLC status report to the RLC instance, so that the base station side RLC instance can immediately resend the message which is sent but does not receive the confirmation message, and the interruption time of data transmission is reduced as much as possible.

The RLC protocol implementation equipment provided by the embodiment can directly reuse the RLC instance of the source base station side when the RLC instance reuse condition is met, so that the terminal does not need to perform RLC reconstruction in the base station switching process, and meanwhile, the source base station side does not need to delete the original RLC instance, so that the base station switching efficiency can be improved, the data transmission interruption time is shortened, and the resource utilization rate is improved.

Example three:

the present embodiment provides an RLC protocol implementing device, as shown in fig. 14, including a first processor 141, a first memory 142, and a first data bus 143;

a first data bus 143 is used to communicatively couple the first processor 141 and the first memory 142;

the first memory 142 is used for storing a base station handover control program, and the first processor 141 is used for operating the base station handover control program in the first memory 142 to implement the steps in the base station handover control method as illustrated in the first embodiment.

The present embodiment provides a base station, as shown in fig. 15, including a second processor 151, a second memory 152, and a second data bus 153;

the second data bus 153 is used for communicatively connecting the second processor 151 and the second memory 152;

the second memory 152 is used for storing a base station handover program, and the second processor 151 is used for running the base station handover control program in the second memory 152 to implement the steps in the base station side base station handover method as illustrated in the first embodiment.

The present embodiment provides a terminal, as shown in fig. 16, including a third processor 161, a third memory 162, and a third data bus 163;

a third data bus 163 is used to communicatively couple the third processor 161 and the third memory 162;

the third memory 162 is used for storing a base station handover program, and the third processor 161 is used for running the base station handover control program in the third memory 162 to implement the steps in the base station side base station handover method as illustrated in the first embodiment.

Example four:

for the convenience of understanding, the present embodiment is illustrated by taking some specific application scenarios as examples.

Example one: the NR gbb is co-deployed with (e) LTE eNB RLC layer in site room. At this time, a block diagram of module deployment of the base station and the RLC protocol implementing device is shown in fig. 17, and a block diagram of the terminal is shown in fig. 18. In fig. 17, the RLC management module and the RLC instance belong to an RLC protocol implementing apparatus. The destination base node distribution unit control module constitutes an RLC configuration module of the base station, and it should be noted that the destination base node distribution unit control module does not only include an RLC configuration function. In fig. 18, an RRC (Radio Resource Control) module constitutes a handover management module, and an RLC re-establishment decision module constitutes a re-establishment policy module.

The first process is as follows: RLC initialization

The RLC management module is powered on and initialized, and the management range is all base nodes (namely base station nodes) in the site computer room.

The RLC management module pre-creates a certain number of RLC instances, and concatenates each RLC instance not referenced by the base node distribution unit DRB.

And a second process: referring to fig. 19, a flow of RLC downlink data transfer in a lossless handover procedure between base stations is shown, which includes:

s1) the SNodeB CU sends measurement control 610 to the UE, and the measurement object comprises a cell under DNodeB.

S2) the UE RRC module reports the measurement report 612.

S3) the downstream packet data communication proceeds, 614-620.

S4) the SNodeB CU makes a handover decision 622 to decide to handover the UE to a cell under DNodeB based on the neighboring cell radio signal quality level in the UE measurement report and the UE' S current serving cell status, thereby starting a handover preparation phase.

S5) the SNodeB CU sends a handover request 624 to the DNodeB CU, carrying the source base node UE identity (assigned by the SNodeB CU).

S6) the DNodeB CU performs admission control 626 to decide to allow UE hand-in and assign the destination base node UE identity.

S7) the DNodeB CU sends a radio resource configuration request 628, including the UE DRB configuration information, to the DNodeB DU CTRL.

S8) DNodeB DU CTRL sends DRB RLC instance application request 630 to RLC MGR for each UE DRB in the confirmation mode, wherein the DRB application request carries source base node identification, source base node UE identification, destination base node UE identification, E-RAB ID to which the DRB belongs and RLC configuration parameters. Wherein, the source base node UE identification plus E-RAB ID corresponds to a DRB RLC instance A.

S9) the RLC MGR makes a reuse RLC instance decision 632, and determines to reuse the DRB RLC instance A according to that the source base node and the target base node both belong to the management and the requested RLC configuration parameters are the same as the DRB RLC instance A configuration corresponding to the source base node UE identification and the E-RAB ID, and updates DRB RLC instance A reference information (newly added and referenced by the target base node cell); and then returns to application DRB RLC instance response 634, carrying DRB RLC instance a information.

S10) the DNodeB DU CTRL sends a GTPU channel configuration request 636 to the GTPU module, carrying the DRB RLC instance a information. Those skilled in the art will recognize that the use of a GTPU to encapsulate PDCP-RLC interlayer messages is one possible implementation and the present invention does not exclude the possibility of encapsulating PDCP-RLC interlayer messages using other communication protocols.

S11) the GTPU module assigns a Tunnel Endpoint Identifier (TEID) and associates the TEID to the DRB RLC instance a described above, returning a configure GTPU tunnel response 638.

S12) the DNodeB DU CTRL returns a radio resource configuration response 640 to the DNodeB CU, and for each DRB in acknowledged mode, carries the corresponding DNodeB DU side transport layer address (IP address, TEID);

s13) the DNodeB CU returns a switch confirmation 642 to the snoodeb CU, and adds an Information Element (IE) for the DRB object in the returned MobilityControlInfo container information, such as DRB-RLCnotReset, in the form of asn.1 definition such as:

[[drb-RLCnotReset ENUMERATED{true}OPTIONAL--Cond HO]],

S14) the SNodeB CU sends a handover command 650 to the UE, thereby starting the handover execution phase.

S15) the SNodeB CU sends an SN Status Transfer 656 to the DNodeB CU to prepare for the next data forwarding; meanwhile, the core network continues to send downlink messages 658 to the SNodeB CUs, and the SNodeB CUs perform data forwarding 660 and forward the downlink messages to the DNodeB CUs, and the DNodeB CUs cache the messages.

S16) simultaneously with S5 to S14, the RLC INST continues transmitting downlink RLC PDUs to the UE through the source cell MAC layer. For convenience of description, for example, RLC INST transmits RLC PDU 1644, RLC PDU 2646, and RLC PDU 3648, where RLC PDU1 is successfully transmitted and RLC PDU2 and RLC PDU3 are unsuccessfully transmitted.

S17) the UE RRC module receives the handover command from the source base node cell, and then performs the separation from the source cell and synchronization to the destination cell 652. According to different source and destination cell systems, the switching may be any one of E-UTRA, Evolved E-UTRA and 5G NR in pairs. Meanwhile, the UE RLC reestablishment decision module reads whether the DRB-RLCnotReset exists or not, and if yes, the UE RLC reestablishment decision module informs the RRC module not to initiate reestablishment operation on the original DRB RLC instance in the switching process.

S18) the UE initiates a random access procedure 654 on the destination base node cell. Note: the MAC layer of the destination cell also participates in this process, which is not shown in the figure.

S19) the UE sends a handover confirm message 662 to the destination base node cell.

S20) the DNodeB CU receives the handover confirm message, and in turn sends a path switch request 666 to the Core Network (CN), entering the handover complete phase.

S21) the UE sends an RLC status report 664 immediately after sending the handover confirm message, e.g. in case of S16, the content is RLC PDU1 ACK.

S22) and S20-S21, the DNodeB CU executes data forwarding 668, and sends the message forwarded by the CNodeB CU in S15 to a GTPU module tunnel of a site room, wherein the TEID is the TEID distributed in S12; the GTPU module executes data distribution 670 and sends the data to a DRB RLC instance associated with the TEID;

s23) the RLC INST instance executes the switching perception 672, the UE is perceived to be successfully switched to the target base node cell, and then the downlink messages of the RLC INST are all sent to the MAC module of the target base node cell. The judgment method of the switching perception comprises the following steps: in the first method, a DRB RLC instance receives a first RLC status report from a target base node cell MAC module; in a second method, the RLC INST instance receives the first packet downlink forwarding data from the DNodeB CU from the GTPU module, and determines that the data is from the DNodeB CU, where the TEID of the GTPU tunnel is the TEID allocated by the GTPU module for the DNodeB CU CTRL in S11.

S24) the RLC INST instance retransmits the RLC PDU 2674, RLC PDU 3676 that was sent but has not received an acknowledgement according to the contents of the RLC status report 664.

S25) the DRB RLC instance encapsulates the forwarded data received in S22 into RLC PDU 678 to be sent to the UE.

S26) the core network performs the path switching 680 and returns a path switching acknowledgement 682.

S27) the core network sends an End Marker message 684 to the SNodeB CU, which indicates that the End Marker message is the last message on the path; and the SNodeB CU performs End Marker message forwarding 686 and forwards the End Marker message to the DNodeB CU. Note: the three steps S15, 20, 22 are described in terms of E-UTRA X2 handover, which may be referred to as E-UTRA S1 handover if the inter-base station handover is a handover across the core network. This part of the embodiment is readily known from the common general knowledge.

S28) after the path switching is completed, core network data 690 is issued to the DNodeB CU, the DNodeB CU issues data 692 to a site room GTPU module tunnel, and the TEID is the TEID distributed in S12; the GTPU module issues the data 694 to a DRB RLC instance associated with the TEID; the DRB RLC instance encapsulates the data into RLC PDUs 696, which are sent from the destination cell MAC layer to the UE.

S29) after receiving the path switch confirmation, the DNodeB CU sends a UE context release request 698 to the SNodeB CU.

S30) the SNodeB CU transmits a radio resource release request 700 to the SNodeB DU CTRL.

S31) the SNodeB DU CTRL sends a release DRB RLC instance request 702 to the RLC MGR.

S32) the RLC MGR updates the DRB RLC instance reference 704, deletes the reference by the source base node cell, and returns a release DRB RLC instance response 706.

S33) the SNodeB DU CTRL sends a GTPU channel release request 708 to the GTPU module, carrying the tunnel TEID information corresponding to the source base node cell DRB RLC.

S34) the GTPU module deletes the tunnel corresponding to the TEID, releases the resource and returns a GTPU channel release response 710.

S35) the SNodeB DU CTRL returns a radio resource release response 712 to the SNodeB CU. The flow ends.

The third process: referring to fig. 20, a flow chart of RLC uplink data transfer in a lossless handover procedure between base stations includes:

S2) the UE RRC module reports the measurement report 612.

S3) the upstream packet data communication proceeds, 720-726.

[[drb-RLCnotReset ENUMERATED{true}OPTIONAL--Cond HO]],

S15) the SNodeB CU sends an SN Status Transfer 656 to the DNodeB CU to prepare for the next data forwarding; next, the SNodeB CU forwards the upstream messages 736 to the DNodeB CU, which buffers the messages.

S16) simultaneously with S5 to S14, the RLC INST continues to receive uplink RLC PDUs from the UE through the source base node cell MAC module. For convenience of description, for example, the UE RLC INST transmits RLC PDU 1730, RLC PDU 2732, and RLC PDU 3734, wherein RLC PDU1 and RLC PDU3 are successfully transmitted, and RLC PDU2 is failed to be transmitted.

S21) the RLC INST instance executes the switching perception 672, the UE is perceived to be successfully switched to the target base node cell, and then the uplink messages of the RLC INST are all sent to the DNodeB CU. And the perception method is described in the second process.

S22) RLC INST immediately sends an RLC status report 738 after sensing that the UE successfully handed over to the destination base node cell, for example, in case of S16, the contents are RLC PDU 1ACK and RLC PDU3 ACK.

S23) the UE RLC module receives the status report and retransmits the RLC PDU 2740 which has been transmitted but has not received the acknowledgement according to the report content.

S24) the RLC INST sends the RLC PDU2 to the GTPU module, and the GTPU tunnel TEID is the TEID distributed in S11.

S25) the UE continues to send the uplink message 742, the RLC INST sends uplink data 744 to the GTPU module, and the TEID of the GTPU tunnel is the TEID distributed in S11; the GTPU module sends the upstream data 746 to the DNodeB CU, which caches the messages.

S26) the core network performs the path switching 680 and returns a path switching acknowledgement 682. Note: both steps S15, 26 are described in terms of E-UTRA X2 handover, which may be referred to as E-UTRA S1 handover if the inter-base station handover is a handover across the core network. This part of the embodiment is readily known from the common general knowledge.

S27) after receiving the path switching confirmation 682, the DNodeB CU executes data uploading 748 and sends the cached uplink message to the core network.

S28) after receiving the path switch acknowledgement 682, the DNodeB CU sends a UE context release request 698 to the SNodeB CU.

S29) the SNodeB CU transmits a radio resource release request 700 to the SNodeB DU CTRL.

S30) the SNodeB DU CTRL sends a release DRB RLC instance request 702 to the RLC MGR.

S31) the RLC MGR updates the DRB RLC instance reference 704, deletes the reference by the source base node cell, and returns a release DRB RLC instance response 706.

S32) the SNodeB DU CTRL sends a GTPU channel release request 708 to the GTPU module, carrying the tunnel TEID information corresponding to the source base node cell DRB RLC.

S33) the GTPU module deletes the tunnel corresponding to the TEID, releases the resource and returns a GTPU channel release response 710.

S34) the SNodeB DU CTRL returns a radio resource release response 712 to the SNodeB CU. The flow ends.

Example two: the NR gbb is co-deployed with (e) LTE eNB RLC layer in a central office.

A block diagram of the base station and RLC protocol implementation device module deployment at this time is shown in fig. 21. In fig. 21, the RLC management module and the RLC instance belong to an RLC protocol implementing apparatus. The destination base node center unit constitutes an RLC configuration module of the base station, and it should be noted that the destination base node center unit does not only include an RLC configuration function.

The first process is as follows: RLC initialization

And the RLC management module is electrified and initialized, and the management range is the base node in the central machine room.

The RLC management module pre-creates a certain number of RLC instances, and concatenates each RLC instance without reference by the base node center unit DRB.

And a second process: the RLC downlink data transfer flow of the lossless handover procedure between base stations is shown in fig. 22.

S1) the SNodeB CU sends measurement control 810 to the UE, and the measurement object comprises a cell under DNodeB.

S2) the UE RRC module reports the measurement report 812.

S3) the downstream packet data communication proceeds, 814-818.

S4) the SNodeB CU performs a handover decision 820 to make a decision to handover the UE to a cell under DNodeB based on the neighboring cell radio signal quality level in the UE measurement report and the UE' S current serving cell status, thereby starting a handover preparation phase.

S5) the SNodeB CU sends a handover request 822 to the DNodeB CU, carrying the source base node UE identity (assigned by the SNodeB CU).

S6) the DNodeB CU performs admission control 824 to decide to allow UE to hand in and assign the UE identity of the destination base node.

S7) the DNodeB CU sends DRB application RLC instance request 826 to the RLC MGR for each UE DRB in the confirmed mode, wherein the DRB application DRB instance request carries source base node identification, source base node UE identification, destination base node UE identification, E-RAB ID to which the DRB belongs, and RLC configuration parameters. Wherein, the source base node UE identification plus E-RAB ID corresponds to a DRB RLC instance A.

S8) the RLC MGR executes an RLC instance reusing decision 828, determines to reuse the DRB RLC instance A according to that the source base node and the target base node both belong to the management and the requested RLC configuration parameters are the same as the configuration of the DRB RLC instance A corresponding to the source base node UE identification and the E-RAB ID, and updates the DRB RLC instance A reference information (newly added and referred by the target base node cell); and then returns a DRB RLC instance application response 830, which carries DRB RLC instance A information.

S9) the DNodeB CU returns a switching confirmation 832 to the SNodeB CU, and adds an Information Element (IE) for the DRB object in the returned MobilityControlInfo container information, such as DRB-RLCnotReset, and the asn.1 definition form is: [ [ drb-RLCnotReset ENUMERATED { true } OPTIONAL- -Cond HO ] ],

S10) the SNodeB CU sends a handover command 840 to the UE, thereby starting the handover execution phase.

S11) the SNodeB CU sends an SN Status Transfer 846 to the DNodeB CU to prepare for the next data forwarding; meanwhile, the core network continues to send downlink messages 848 to the SNodeB CU, and the SNodeB CU forwards the downlink messages 850 to the DNodeB CU, and the DNodeB CU caches these messages.

S12) simultaneously with S5 to S10, the RLC INST continues to transmit downlink RLC PDUs to the UE through the source base node cell MAC module. For convenience of description, for example, RLC INST transmits downlink RLC PDU 1834, RLC PDU 2836, and RLC PDU 3838, where RLC PDU1 is successfully transmitted and RLC PDU2 and RLC PDU3 are unsuccessfully transmitted.

S13) the UE RRC module receives a handover command 840 from the source base node cell, and then performs separation from the source cell and synchronization to the destination cell 842. According to different source and destination cell systems, the switching may be any one of E-UTRA, Evolved E-UTRA and 5G NR in pairs. Meanwhile, the UE RLC reestablishment decision module reads whether the DRB-RLCnotReset exists or not, and if yes, the UE RLC reestablishment decision module informs the RRC module not to initiate reestablishment operation on the original DRB RLC instance in the switching process.

S14) the UE initiates a random access procedure 844 on the destination base node cell. Note: the destination base node cell MAC module also participates in this process, which is not shown in the figure.

S15) the UE sends a handover confirm message 852 to the destination base node cell.

S16) the DNodeB CU receives the handover confirm message, and in turn sends a path switch request 860 to the Core Network (CN), entering the handover complete phase.

S17) the UE sends an RLC status report 854 immediately after sending the handover confirm message, e.g. RLC PDU 1ACK in case of S12.

S18) simultaneously with S16 to S17, the DNodeB CU sends the message 856 forwarded by the CNodeB CU in S11 to the associated DRB RLC instance.

S19) the RLC INST instance performs handover sensing 858, senses that the UE is successfully handed over to the target base node cell, and then sends the downlink packets of the RLC INST to the MAC module of the target base node cell. The judgment method of the switching perception comprises the following steps: in the first method, a DRB RLC instance receives a first RLC status report from a target base node cell MAC module; in the second method, the RLC INST instance receives first packet downlink forwarding data from the DNodeB CU.

S20) the RLC INST instance retransmits the RLC PDU2 and RLC PDU3 that have been transmitted but have not received an acknowledgement according to the contents of the RLC status report 854.

S21) the DRB RLC instance encapsulates the forwarded data received in S18 into RLC PDU 866 to be sent to the UE.

S22) the core network performs a path switch 868, returning a path switch acknowledgement 870.

S23) the core network sends an End Marker message 872 to the SNodeB CU, which indicates that the End Marker message is the last message on the path; the SNodeB CU forwards the End Marker message 874 to the DNodeB CU. Note: the three steps S11, 16, 22 are described in terms of E-UTRA X2 handover, and if the inter-base station handover is a handover across the core network, the E-UTRA S1 handover may be referred to. This part of the embodiment is readily known from the common general knowledge.

S24), after the path switching is completed, the core network directly issues the data 876 to the DNodeB CU, and the DNodeB CU then issues the data 878 to the associated DRB RLC instance; the DRB RLC instance encapsulates the data into RLC PDUs 880, which are sent from the destination base node cell MAC layer to the UE.

S25) after receiving the path switch confirmation 870, the DNodeB CU sends a UE context release request 882 to the SNodeB CU.

S26) the SNodeB CU sends a release DRB RLC instance request 884 to the RLC MGR.

S27) the RLC MGR updates the DRB RLC instance reference 886, deletes the reference by the source base node cell, and returns a release DRB RLC instance response 888. The flow ends.

The third process: a schematic diagram of the RLC uplink data transfer flow of the lossless handover procedure between base stations is shown in fig. 23.

S2) the UE RRC module reports the measurement report 812.

S3) the upstream packet data communication proceeds, 910-914.

S9) the DNodeB CU returns a switching confirmation 832 to the SNodeB CU, and adds an Information Element (IE) for the DRB object in the returned MobilityControlInfo container information, such as DRB-RLCnotReset, and the asn.1 definition form is:

[[drb-RLCnotReset ENUMERATED{true}OPTIONAL--Cond HO]],

S11) the SNodeB CU sends an SN Status Transfer 846 to the DNodeB CU to prepare for the next data forwarding; the SNodeB CU then forwards the upstream messages 930 to the DNodeB CU, which buffers the messages.

S12) simultaneously with S5 to S10, the RLC INST continues to receive uplink RLC PDUs from the UE through the source base node cell MAC module. For convenience of description, for example, the UE RLC INST transmits an uplink RLC PDU 1920, an RLC PDU 2922 and an RLC PDU 3924, where RLC PDU1 and RLC PDU3 are successfully transmitted and RLC PDU2 is failed to be transmitted.

S17) the RLC INST instance executes the switching perception 858 to perceive that the UE is successfully switched to the target base node cell, and then the uplink messages of the RLC INST are all sent to the DNodeB CU. And the perception method is described in the second process.

S18) the RLC INST immediately sends an RLC status report 932 after sensing that the UE successfully switches to the destination base node cell, for example, in the case of S12, the contents are RLC PDU 1ACK and RLC PDU3 ACK.

S19) the UE RLC module receives the status report and retransmits the RLC PDU 2934 which has been sent but has not received the acknowledgement according to the report content.

S20) the UE continues to send uplink messages 936, the RLC INST sends uplink data 938 to the DNodeB CU, which buffers these messages.

S21) the core network performs a path switch 868, returning a path switch acknowledgement 870.

S22) after receiving the path switch acknowledgement 870, the DNodeB CU sends the buffered uplink packet 940 to the core network. Note: the steps S11, 16, 21, 22 are described in terms of E-UTRA X2 handover, and if the handover between base stations is a handover across the core network, the E-UTRA S1 handover may be referred to. This part of the embodiment is readily known from the common general knowledge.

S23) after receiving the path switch confirmation 870, the DNodeB CU sends a UE context release request 882 to the SNodeB CU.

S24) the SNodeB CU sends a release DRB RLC instance request 884 to the RLC MGR.

S25) the RLC MGR updates the DRB RLC instance reference 886, deletes the reference by the source base node cell, and returns a release DRB RLC instance response 888. The flow ends.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling an application device (such as a mobile phone, a computer, a server, an air conditioner, or a network application device) to execute the method according to the embodiments of the present invention.

While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. An example distribution method in a base station switching process comprises the following steps:

feeding back RLC application response information containing the information of the RLC instance to the target base station;

the RLC instance application request comprises a target base station identifier, RLC configuration parameters and RLC instance matching information corresponding to the DRB on a source base station side, wherein the RLC instance matching information comprises a source base station identifier of a source base station;

the method for confirming that the source base station has the reusable RLC instance according to the RLC instance application request comprises the following steps:

and determining that the source base station and the target base station are base stations hung under the source base station according to the source base station identification and the target base station identification, and setting the RLC instance as a reusable RLC instance as an instance of the DRB on the target base station side when the configuration parameters of the RLC instance corresponding to the DRB on the source base station side matched according to the RLC instance matching information are the same as the RLC configuration parameters.

2. The method for allocating instances in the process of switching base stations according to claim 1, wherein the RLC instance matching information further includes a source base station terminal identifier and an Evolved Radio Access Bearer (E-RAB) ID to which the DRB belongs, and the RLC instance application request further includes a target base station terminal identifier;

setting the RLC instance as an instance of the DRB on the target base station side includes:

and adding the target base station identification, the target base station terminal identification and the E-RAB ID in the reference information of the RLC instance.

3. The method for instance allocation during base station handover as claimed in claim 2, wherein said method further comprises:

receiving an RLC instance release request sent by the source base station, wherein the RLC instance release request comprises the source base station identifier, a source base station terminal identifier and an E-RAB ID to which the DRB belongs;

finding the RLC instance corresponding to the source base station according to the source base station identifier, the source base station terminal identifier and the E-RAB ID to which the DRB belongs;

and deleting the source base station identification, the source base station terminal identification and the E-RAB ID to which the DRB belongs in the reference information of the RLC instance.

4. The method for instance allocation in base station handover procedure according to any of claims 1-3, further comprising:

after the RLC instance detects that the terminal is successfully switched to the target base station, the downlink message which is sent but does not receive the confirmation information is retransmitted through the RLC instance;

and/or the presence of a gas in the gas,

and after the RLC instance detects that the terminal is successfully switched to the target base station, sending a latest uplink RLC status report to the terminal.

5. The method for instance allocation in the process of base station handover as claimed in claim 4, wherein the detecting whether the terminal is successfully handed over to the target base station through the RLC instance comprises:

judging whether the RLC instance receives a first RLC state message sent by the terminal through a target base station, if so, judging that the terminal is successfully switched to the target base station;

or the like, or, alternatively,

and judging whether the RLC instance receives first packet downlink forwarding data from the target base station, if so, judging that the terminal is successfully switched to the target base station.

6. A base station switching method comprises the following steps:

the RLC instance information is the RLC instance information which is extracted after the DRB sets the RLC instance as the instance of the target base station side when the RLC protocol implementation equipment confirms that the source base station has the reusable RLC instance according to the RLC instance application request;

7. A base station switching method comprises the following steps:

the no RLC instance re-establishment flag is obtained by the base station handover method according to claim 6.

8. The base station switching method of claim 7, further comprising:

after accessing the target base station according to the target base station information, sending a switching confirmation message to the target base station;

and after sending a handover confirmation message to the target base station, sending a downlink RLC status report to the target base station.

9. An RLC protocol implementing device, comprising:

the system comprises an RLC management module, a target base station and a source base station, wherein the RLC management module is used for receiving an RLC instance application request sent by the target base station aiming at a DRB in a confirmation mode in the process of switching base stations by a terminal, setting the RLC instance as an instance of the DRB at the target base station side when the source base station is confirmed to have a reusable RLC instance according to the RLC instance application request, and feeding back RLC application response information containing information of the RLC instance to the target base station;

10. A base station, comprising:

11. A terminal, comprising:

the switching management module is used for receiving a switching command sent by a source base station, wherein the switching command comprises target base station information, initiating an access request to a target base station according to the target base station information to switch from the source base station to the target base station, and when receiving an RLC reestablishment-free instruction, not reestablishing an RLC instance of a DRB in a confirmation mode;

a reestablishment policy module, configured to send a DRB non-RLC reestablishment instruction to the RLC module when determining that the handover command includes a DRB identified that the acknowledged mode DRB does not perform RLC instance reestablishment;

12. An RLC protocol implementation device is characterized by comprising a first processor, a first memory and a first data bus;

the first memory is used for storing a base station switching control program;

the first processor is configured to execute a base station handover control program in the first memory to implement the steps in the base station handover control method according to any one of claims 1 to 5.

13. A base station comprising a second processor, a second memory, and a second data bus;

the second memory is used for storing a base station switching control program;

the second processor is configured to execute the base station handover procedure in the second memory to implement the steps in the base station handover method according to claim 6.

14. A terminal comprising a third processor, a third memory, and a third data bus;

the third memory is used for storing a base station switching control program;

the third processor is configured to execute a base station handover procedure in the third memory to implement the steps in the base station handover method according to claim 7 or 8.