CN113038545A - Method and communication system for reducing handover failure - Google Patents

Method and communication system for reducing handover failure Download PDF

Info

Publication number
CN113038545A
CN113038545A CN201911341551.3A CN201911341551A CN113038545A CN 113038545 A CN113038545 A CN 113038545A CN 201911341551 A CN201911341551 A CN 201911341551A CN 113038545 A CN113038545 A CN 113038545A
Authority
CN
China
Prior art keywords
base station
protocol version
function
condition
protocol
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.)
Granted
Application number
CN201911341551.3A
Other languages
Chinese (zh)
Other versions
CN113038545B (en
Inventor
许森
曹磊
赵晔
孙震强
张乐
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Telecom Corp Ltd
Original Assignee
China Telecom Corp Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by China Telecom Corp Ltd filed Critical China Telecom Corp Ltd
Priority to CN201911341551.3A priority Critical patent/CN113038545B/en
Publication of CN113038545A publication Critical patent/CN113038545A/en
Application granted granted Critical
Publication of CN113038545B publication Critical patent/CN113038545B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • H04W36/0072Transmission or use of information for re-establishing the radio link of resource information of target access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • H04W36/0077Transmission or use of information for re-establishing the radio link of access information of target access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/08Reselecting an access point

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The present disclosure provides a method and communication system for reducing handover failures. In a communication system, a first base station acquires a protocol version and functions of an adjacent second base station; under the condition that a user terminal in a cell where a first base station is located needs to be switched to a cell where a second base station is located, if the first base station judges that at least one of a protocol parameter and a function currently configured by the user terminal cannot be supported by the second base station according to a protocol version and a function support condition of the second base station, the first base station adjusts the protocol parameter and the function currently configured by the user terminal by using an RRC reconfiguration message so that the protocol parameter and the function configured by the user terminal can be supported by the second base station, and then the switching from the user terminal to the second base station is executed. According to the method and the device, the bearing and function configuration parameters of the user switched to the adjacent base station are determined by sensing the capacity of the adjacent base station, so that the problem of interoperation failure among base stations with different capacities is reduced, and the user experience is improved.

Description

Method and communication system for reducing handover failure
Technical Field
The present disclosure relates to the field of wireless communications, and in particular, to a method and a communication system for reducing handover failure.
Background
The 5G is used as a main technology of a next-generation wireless network and has the technical characteristics of supporting ultra wide band, large connection and the like. In the current specification, several mainstream networking architectures and interface scenarios are as follows:
in an EN-DC (E-UTRA-NR Dual Connectivity, Evolved universal terrestrial Radio access and Dual Connectivity of a New air interface) networking scenario, an X2 interface is used for connection between an EN-gNB (NR (New Radio, New air interface) base station) and an eNB (Evolved NodeB) to perform connection. In this scenario, the eNB only maintains the S1-C interface to the EPC (Evolved Packet Core, Core network), and the en-gbb needs to support the S1-U interface to the EPC when supporting the SCG (Secondary Cell Group) Split bearer or SCG bearer.
Compared with the past wireless technologies, the 5G supports two types of wireless access base stations, namely, a new air interface-based NR gbb and an LTE (Long Term Evolution) -based ng-eNB, and both the two types of base stations are connected to the core network 5GC of the 5G. The base stations are connected through an Xn interface, and the base stations are connected with the 5G core network through an NG interface.
When the gNB and the LTE eNB are respectively connected to the respective core networks, namely the gNB is connected with 5GC, and the eNB is connected into the EPC, the establishment of an interface between base stations is not supported between the gNB and the eNB.
In the networking process of the 5G network, there is a case where an NSA (Non standard alone) network and an existing LTE network are deployed adjacently. The inventor finds that a large number of handover failure situations occur through research. The reasons for its failure are as follows:
1) the interaction of the lack of capability information between base stations: the 3GPP (The 3rd Generation Partnership Project) protocol considers that The difference between different base station capabilities can be solved by configuration and implementation when designing, but in The process of networking of different vendors, because there is usually no X2 interface or there is a difference in implementation manner of The vendor, information of neighboring base stations of different vendors cannot be configured through network management, so that in some border areas, a handover failure occurs due to IoT problem. For some key capabilities, such as Packet Data Convergence Protocol (PDCP) SN (Sequence Number) Size supporting NR version 18 bits, the current network LTE base station does not support the NSA function and only supports 12 bits of PDCP Sequence Number Size, whereas the NSA base station supports 18 bits of PDCP Sequence Number Size because the user plane may use NR technology for carrying. When switching from NSA to LTE, the existing network LTE base station may not perform 18-bit to 12-bit conversion due to its own design and feed back a handover rejection resulting in a handover failure.
2) The protocol does not enforce protocol version different processing modes: the behavior of the LTE base station when the handover request of the source base station is not understood is specified in TS36.300, where whether the target base station understands an implementation process when receiving RRC (Radio Resource Control) signaling of different versions is specified, and a protocol is not mandatory, so that part of base stations of a current network manufacturer do not perform subsequent handover in a Full Configuration (Full Configuration) manner.
3) The existing network version and the NSA base station have a difference in the analysis of the RRC protocol asn.1(Abstract Syntax Notation): the existing network base station may only support Rel-13 asn.1, and the SCG sent by NSA usually uses Rel-15 asn.1 for coding, resulting in decoding failure of the existing network base station and triggering handover failure.
From the operator's point of view, there is a need for the above problem as follows:
1) how to solve the interconnection problem when base stations with different versions and capabilities are adjacently networked under the condition that the deployed base stations of the current network are not upgraded.
2) In the current LTE network, after NR SA (stand alone networking) is introduced in the future, how to avoid similar problems in the NR SA network caused by introducing new functions and characteristics to subsequent NR base stations is to be solved.
Based on the above requirements and reason analysis, the current protocols of 3GPP LTE and NR cannot meet the requirements, and need to be enhanced in a new manner to meet the requirements of network deployment and optimization.
Disclosure of Invention
The utility model provides a scheme for reducing switching failure, through perception adjacent base station's ability in order to confirm that the user switches to the bearing and the function configuration parameter of adjacent base station to reduce the problem of interoperation failure between the different ability base stations, promoted user experience.
According to a first aspect of the embodiments of the present disclosure, there is provided a method for reducing handover failure, including: the first base station acquires the protocol version and the function of the adjacent second base station; under the condition that a user terminal in a cell where a first base station is located needs to be switched to a cell where a second base station is located, the first base station judges whether protocol parameters and functions currently configured by the user terminal are supported by the second base station or not according to a protocol version and a function support condition of the second base station; if the protocol parameters and functions currently configured by the user terminal can be supported by the second base station, the first base station executes the switching from the user terminal to the second base station; if at least one of the currently configured protocol parameters and functions of the user terminal cannot be supported by the second base station, the first base station adjusts the currently configured protocol parameters and functions of the user terminal by using an RRC reconfiguration message so that the currently configured protocol parameters and functions of the user terminal can be supported by the second base station, and then performs switching from the user terminal to the second base station.
In some embodiments, the acquiring, by the first base station, the protocol version and the function of the neighboring second base station includes: the first base station classifies the protocol version and the function parameter supported by the first base station to generate the protocol version and the function supporting condition of the first base station; the first base station sends the protocol version and the function supporting condition of the first base station to the second base station through a preset interface, so that the second base station stores the protocol version and the function supporting condition of the first base station locally; and after receiving the protocol version and the function supporting condition of the second base station fed back by the second base station, the first base station stores the protocol version and the function supporting condition of the second base station locally.
In some embodiments, the protocol version comprises a parsed version of RRC asn.1, the functional support case comprises at least one of PDCP protocol version capability, RLC protocol version capability, MAC protocol version capability, multi-connection configuration capability, and voice support capability, wherein PDCP protocol version capability comprises at least one of LTE and NR PDCP size support list, PDCP support LTE or NR, multi-connection configuration capability comprises EN-DC support case and/or NE-DC support case, and voice support capability comprises VoNR support case.
In some embodiments, the sending, by the first base station, the protocol version and the function support condition of the first base station to the second base station through the predetermined interface includes: the first base station judges whether a direct interface is established with the second base station; if the first base station and the second base station do not establish a direct interface and the network management configuration information allows the establishment of the direct interface between the first base station and the second base station, the first base station and the second base station establish the direct interface; the first base station sends the protocol version and the function supporting condition of the first base station to the second base station through the establishment message of the direct interface.
In some embodiments, the second base station stores the protocol version and the function support condition of the first base station locally after receiving the protocol version and the function support condition of the first base station through the established direct interface; and the second base station feeds back the protocol version and the function supporting condition of the second base station to the first base station through the established direct interface.
In some embodiments, if the first base station and the second base station have established a direct interface, the first base station sends the protocol version and the function support condition of the first base station to the second base station through the established direct interface by using the configuration update message.
In some embodiments, the second base station stores the protocol version and the function support condition of the first base station locally after receiving the protocol version and the function support condition of the first base station through the configuration update message; and the second base station judges whether the own protocol version and the function supporting condition change or not, and if the own protocol version and the function supporting condition change, the current protocol version and the function supporting condition of the second base station are fed back to the first base station through the established direct interface.
In some embodiments, if the first base station and the second base station do not establish a direct interface, and the network management configuration information does not allow the direct interface to be established between the first base station and the second base station, the first base station sends the protocol version and the function support condition of the first base station to the core network control plane entity through the configuration update message by using an interface with the core network control plane entity under the condition that the protocol version and the function support condition of the first base station are never sent or are updated, so that the core network control plane entity sends the configuration update message to the second base station.
In some embodiments, the configuration update message comprises: an identity of the first base station, an identity of the second base station, and a protocol version and functional support of the first base station.
In some embodiments, after receiving the protocol version and the function support condition of the first base station through the core network control plane entity, the second base station stores the protocol version and the function support condition of the first base station locally; and the second base station feeds back the protocol version and the function support condition of the second base station to the first base station through the core network control plane entity.
In some embodiments, the first base station storing locally the protocol version and the functional support of the second base station comprises: the first base station detects whether the protocol version and the function support condition of the second base station are stored locally; if the first base station does not locally store the protocol version and the function supporting condition of the second base station, the first base station directly stores the protocol version and the function supporting condition of the second base station locally; if the first base station has locally stored the protocol version and the function support condition of the second base station, the first base station updates the locally stored protocol version and the function support condition of the second base station by using the received protocol version and the function support condition of the second base station.
In some embodiments, the adjusting, by the first base station, the currently configured protocol parameters and functions of the user terminal by using the RRC reconfiguration message includes: and the first base station reconfigures the protocol parameters and functions which cannot be supported by the second base station in the current configuration of the user terminal into the protocol parameters and functions which can be supported by the second base station by using the RRC reconfiguration message, and deletes or closes the functions which cannot be supported by the second base station in the current configuration of the user terminal.
In some embodiments, when the ue needs to be handed over to a cell in which a second base station is located, if the first base station does not have a protocol version and a function support of the second base station, the first base station sends a handover request to the second base station, where the handover request includes a protocol parameter and a function currently configured by the ue; if the first base station receives a switching failure message sent by the second base station, the first base station determines protocol parameters and functions which can be supported by the second base station in the user terminal according to the received failure message and a bearing switching failure history record of switching other user terminals in a cell where the first base station is located to the cell where the second base station is located, and records corresponding information locally; the first base station reconfigures the protocol parameters and functions which cannot be supported by the second base station in the current configuration of the user terminal into the protocol parameters and functions which are supported by the second base station by using RRC reconfiguration information, and deletes or closes the functions which cannot be supported by the second base station in the current configuration of the user terminal; the first base station performs a handover of the user terminal to the second base station.
In some embodiments, if the first base station receives a handover success message sent by the second base station, the first base station records the protocol parameters and functions currently configured by the user terminal locally as protocol parameters and functions that can be supported by the second base station; the first base station performs a handover of the user terminal to the second base station.
In some embodiments, the protocol parameters of the user terminal comprise a parsed version of RRC asn.1, the functionality of the user terminal comprises at least one of PDCP protocol version capability, RLC protocol version capability, MAC protocol version capability, multi-connection configuration capability, and voice support capability, wherein PDCP protocol version capability comprises at least one of LTE and NR PDCP size support list, PDCP support LTE or NR, multi-connection configuration capability comprises EN-DC support case and/or NE-DC support case, and voice support capability comprises VoNR support case.
According to a first aspect of the embodiments of the present disclosure, there is provided a communication system for reducing handover failure, comprising a first base station and a second base station which are adjacent, wherein: a first base station configured to acquire a protocol version and a function of an adjacent second base station; under the condition that a user terminal in a cell where a first base station is located needs to be switched to a cell where a second base station is located, judging whether a protocol parameter and a function currently configured by the user terminal are supported by the second base station or not according to a protocol version and a function support condition of the second base station; if the protocol parameters and functions currently configured by the user terminal can be supported by the second base station, executing the switching from the user terminal to the second base station; if at least one of the currently configured protocol parameters and functions of the user terminal cannot be supported by the second base station, the currently configured protocol parameters and functions of the user terminal are adjusted by using an RRC reconfiguration message so that the protocol parameters and functions configured by the user terminal can be supported by the second base station, and then the user terminal is switched to the second base station.
In some embodiments, the first base station is configured to classify the protocol version and the function parameters supported by the first base station to generate a protocol version and a function supporting situation of the first base station; sending the protocol version and the function supporting condition of the second base station to the second base station through a preset interface so that the second base station can store the protocol version and the function supporting condition of the first base station locally; and after receiving the protocol version and the function supporting condition of the second base station fed back by the second base station, storing the protocol version and the function supporting condition of the second base station locally.
In some embodiments, the protocol version comprises a parsed version of RRC asn.1, the functional support case comprises at least one of PDCP protocol version capability, RLC protocol version capability, MAC protocol version capability, multi-connection configuration capability, and voice support capability, wherein PDCP protocol version capability comprises at least one of LTE and NR PDCP size support list, PDCP support LTE or NR, multi-connection configuration capability comprises EN-DC support case and/or NE-DC support case, and voice support capability comprises VoNR support case.
In some embodiments, the first base station is configured to determine whether a direct interface has been established with the second base station; if the direct interface is not established with the second base station and the network management configuration information allows the direct interface to be established between the first base station and the second base station, the direct interface is established with the second base station, and the protocol version and the function support condition of the second base station are sent to the second base station through the establishment message of the direct interface.
In some embodiments, the second base station is configured to store the protocol version and the functional support of the first base station locally after receiving the protocol version and the functional support of the first base station over the established direct interface; and feeding back the protocol version and the function supporting condition of the first base station through the established direct interface.
In some embodiments, the first base station is further configured to send the protocol version and the functional support of the first base station to the second base station by using a configuration update message through the established direct interface if the direct interface is established with the second base station.
In some embodiments, the second base station is further configured to store the protocol version and the function support condition of the first base station locally after receiving the protocol version and the function support condition of the first base station through the configuration update message; and judging whether the own protocol version and the function supporting condition change or not, and if the own protocol version and the function supporting condition change, feeding back the own current protocol version and the function supporting condition to the first base station through the established direct interface.
In some embodiments, the first base station is further configured to, if no direct interface is established with the second base station, and the network management configuration information does not allow a direct interface to be established between the first base station and the second base station, send the protocol version and the functional support condition of the first base station to the core network control plane entity through the configuration update message by using an interface with the core network control plane entity if the protocol version and the functional support condition of the first base station are not sent or are updated, so that the core network control plane entity sends the configuration update message to the second base station.
In some embodiments, the configuration update message comprises: an identity of the first base station, an identity of the second base station, and a protocol version and functional support of the first base station.
In some embodiments, the second base station is further configured to store the protocol version and the functional support of the first base station locally after receiving the protocol version and the functional support of the first base station through the core network control plane entity; and feeding back the protocol version and the function support condition of the core network control plane entity to the first base station.
In some embodiments, the first base station is configured to detect whether the protocol version and functional support of the second base station has been stored locally; if the protocol version and the function supporting condition of the second base station are not stored locally, directly storing the protocol version and the function supporting condition of the second base station locally; and if the protocol version and the function supporting condition of the second base station are locally stored, updating the locally stored protocol version and the locally stored function supporting condition of the second base station by using the received protocol version and the function supporting condition of the second base station.
In some embodiments, the first base station is configured to reconfigure the protocol parameters and functions of the current configuration of the user terminal that cannot be supported by the second base station to the protocol parameters and functions supported by the second base station using an RRC reconfiguration message, and delete or turn off the functions of the current configuration of the user terminal that cannot be supported by the second base station.
In some embodiments, the first base station is configured to send a handover request to the second base station if the first base station does not have a protocol version and a function support condition of the second base station when the user terminal needs to be handed over to a cell where the second base station is located, where the handover request includes a protocol parameter and a function currently configured by the user terminal; if receiving a switching failure message sent by a second base station, determining protocol parameters and functions which can be supported by the second base station in the user terminal according to the received failure message and a bearing switching failure history record of switching other user terminals in a cell where the first base station is located to the cell where the second base station is located, and recording corresponding information locally; reconfiguring the protocol parameters and functions which cannot be supported by the second base station in the current configuration of the user terminal into the protocol parameters and functions which can be supported by the second base station by using an RRC reconfiguration message, and deleting or closing the functions which cannot be supported by the second base station in the current configuration of the user terminal; performing a handover of the user terminal to a second base station.
In some embodiments, the first base station is further configured to, if receiving the handover success message sent by the second base station, record the protocol parameters and functions currently configured by the user terminal locally as protocol parameters and functions that can be supported by the second base station; and performing a handover of the user terminal to a second base station.
In some embodiments, the protocol parameters of the user terminal comprise a parsed version of RRC asn.1, the functionality of the user terminal comprises at least one of PDCP protocol version capability, RLC protocol version capability, MAC protocol version capability, multi-connection configuration capability, and voice support capability, wherein PDCP protocol version capability comprises at least one of LTE and NR PDCP size support list, PDCP support LTE or NR, multi-connection configuration capability comprises EN-DC support case and/or NE-DC support case, and voice support capability comprises VoNR support case.
According to a third aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, in which computer instructions are stored, and when executed by a processor, the computer-readable storage medium implements the method according to any of the embodiments described above.
Other features of the present disclosure and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description, serve to explain the principles of the disclosure.
The present disclosure may be more clearly understood from the following detailed description, taken with reference to the accompanying drawings, in which:
fig. 1 is a flow diagram of a method for reducing handover failures according to one embodiment of the present disclosure;
fig. 2 is a flow diagram of a method for reducing handover failures according to another embodiment of the present disclosure;
fig. 3 is a flow diagram of a method for reducing handover failures according to yet another embodiment of the present disclosure;
fig. 4 is a flow diagram of a method for reducing handover failures according to yet another embodiment of the present disclosure;
fig. 5 is a block diagram of a communication system for reducing handover failures according to one embodiment of the present disclosure.
It should be understood that the dimensions of the various parts shown in the figures are not drawn to scale. Further, the same or similar reference numerals denote the same or similar components.
Detailed Description
Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. The description of the exemplary embodiments is merely illustrative and is in no way intended to limit the disclosure, its application, or uses. The present disclosure may be embodied in many different forms and is not limited to the embodiments described herein. These embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. It should be noted that: the relative arrangement of parts and steps, the composition of materials and values set forth in these embodiments are to be construed as illustrative only and not as limiting unless otherwise specifically stated.
The use of the word "comprising" or "comprises" and the like in this disclosure means that the elements listed before the word encompass the elements listed after the word and do not exclude the possibility that other elements may also be encompassed.
All terms (including technical or scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs unless specifically defined otherwise. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.
Fig. 1 is a flow diagram of a method for reducing handover failures according to one embodiment of the present disclosure. In some embodiments, the following method steps for reducing handover failures are performed by a communication system for reducing handover failures.
In step 101, a first base station acquires a protocol version and a function of a neighboring second base station.
In some embodiments, the first base station classifies the protocol version and the function parameter supported by the first base station to generate the protocol version and the function supporting condition of the first base station.
For example, the protocol version includes a resolved version of RRC asn.1. The resolution version of ASN.1 adopts the format of enum, and respectively represents the previous version of Rel-15, Rel-16 and the like.
The function support case includes at least one of PDCP protocol version capability, RLC (Radio Link Control) protocol version capability, MAC (Media Access Control) protocol version capability, multi-connection configuration capability, and voice support capability. The PDCP protocol version capability comprises at least one of LTE and NR PDCP size support lists, PDCP supports LTE or NR, the multi-connection configuration capability comprises EN-DC support case and/or NE-DC (NR-E-UTRA Dual Connectivity, NR and Dual-connection of E-UTRA) support case, and the Voice support capability comprises VoNR (Voice over NR, NR network Voice service) support case.
Wherein, for the NR PDCP Size support list, it is empty if the NR PDCP is not supported. The EN-DC supporting situation is represented by 1 bit, wherein 1 represents supporting, and no carrying or 0 represents not supporting; the NE-DC supporting situation adopts 1 bit to represent, wherein 1 represents the supporting, and does not carry or 0 represents the non-supporting; the VoNR support case is represented by 1 bit, wherein 1 represents support, and no carrying or 0 represents non-support.
Next, the first base station sends the protocol version and the function supporting situation of the first base station to the second base station through a predetermined interface, so that the second base station stores the protocol version and the function supporting situation of the first base station locally.
In some embodiments, the first base station determines whether a direct interface has been established with the second base station. If the first base station and the second base station do not establish a direct interface and the network management configuration information allows the direct interface to be established between the first base station and the second base station, the first base station establishes the direct interface with the second base station through X2/Xn. The first base station sends the protocol version and the function supporting condition of the first base station to the second base station through the establishment message of the direct interface.
And after receiving the protocol version and the function supporting condition of the first base station through the established direct interface, the second base station stores the protocol version and the function supporting condition of the first base station locally. And the second base station feeds back the protocol version and the function supporting condition of the second base station to the first base station through the established direct interface.
In addition, if the first base station and the second base station have established a direct interface, the first base station sends the protocol version and the function support condition of the first base station to the second base station by using the configuration update message through the established direct interface.
And after receiving the protocol version and the function support condition of the first base station through the configuration updating message, the second base station stores the protocol version and the function support condition of the first base station locally. And the second base station judges whether the own protocol version and the function supporting condition change or not, and if the own protocol version and the function supporting condition change, the current protocol version and the function supporting condition of the second base station are fed back to the first base station through the established direct interface.
In addition, if the first base station and the second base station do not establish a direct interface and the network management configuration information does not allow the direct interface to be established between the first base station and the second base station, the first base station sends the protocol version and the function support condition of the first base station to the core network control plane entity through the configuration update message by using the interface with the core network control plane entity under the condition that the protocol version and the function support condition of the first base station are not sent or are updated, so that the core network control plane entity sends the configuration update message to the second base station.
In some embodiments, the configuration update message includes, but is not limited to, at least one of:
an identity of the first base station;
an identity of the second base station;
protocol version and functional support of the first base station.
And after receiving the protocol version and the function support condition of the first base station through the core network control plane entity, the second base station stores the protocol version and the function support condition of the first base station locally. And the second base station feeds back the protocol version and the function support condition of the second base station to the first base station through the core network control plane entity.
And then, after receiving the protocol version and the function supporting condition of the second base station fed back by the second base station, the first base station stores the protocol version and the function supporting condition of the second base station locally.
In some embodiments, the first base station detects whether the protocol version and the function support condition of the second base station are stored locally or not in the process that the first base station stores the protocol version and the function support condition of the second base station locally. And if the first base station does not locally store the protocol version and the function support condition of the second base station, the first base station directly stores the protocol version and the function support condition of the second base station locally. If the first base station has locally stored the protocol version and the function support condition of the second base station, the first base station updates the locally stored protocol version and the function support condition of the second base station by using the received protocol version and the function support condition of the second base station.
In step 102, when the user terminal in the cell where the first base station is located needs to be switched to the cell where the second base station is located, the first base station determines whether the protocol parameters and functions currently configured by the user terminal are supported by the second base station according to the protocol version and the function support condition of the second base station.
If the protocol parameters and functions currently configured by the user terminal can be supported by the second base station, executing step 103; if at least one of the currently configured protocol parameters and functions of the ue cannot be supported by the second base station, step 104 is executed.
In step 103, the first base station performs a handover of the user terminal to the second base station.
In step 104, the first base station adjusts the currently configured protocol parameters and functions of the user terminal by using the RRC reconfiguration message, so that the protocol parameters and functions configured by the user terminal can be supported by the second base station.
In some embodiments, the first base station reconfigures, by using the RRC reconfiguration message, the protocol parameters and functions that cannot be supported by the second base station in the current configuration of the user terminal to the protocol parameters and functions that are supported by the second base station, and deletes or turns off the functions that cannot be supported by the second base station in the current configuration of the user terminal.
In step 105, the first base station performs a handover of the user terminal to the second base station.
In the method for reducing handover failure provided by the above embodiment of the present disclosure, the bearer and the function configuration parameter for the user to handover to the neighboring base station are determined by sensing the capability of the neighboring base station, so that the problem of interoperation failure between base stations with different capabilities is reduced, and user experience is improved. In addition, the upgrading requirement of the current network base station of the operator is avoided, and the CAPEX (Capital Expenditure) and OPEX (Operating cost) of the operator are reduced.
Fig. 2 is a flow diagram of a method for reducing handover failures according to one embodiment of the present disclosure.
In step 201, the first base station sends its own protocol version and function support to the second base station through a predetermined interface.
In some embodiments, the first base station determines whether a direct interface has been established with the second base station. If the first base station and the second base station do not establish a direct interface and the network management configuration information allows the direct interface to be established between the first base station and the second base station, the first base station establishes the direct interface with the second base station through X2/Xn. The first base station sends the protocol version and the function supporting condition of the first base station to the second base station through the establishment message of the direct interface.
In addition, if the first base station and the second base station have established a direct interface, the first base station sends the protocol version and the function support condition of the first base station to the second base station by using the configuration update message through the established direct interface.
In addition, if the first base station and the second base station do not establish a direct interface and the network management configuration information does not allow the direct interface to be established between the first base station and the second base station, the first base station sends the protocol version and the function support condition of the first base station to the core network control plane entity through the configuration update message by using the interface with the core network control plane entity under the condition that the protocol version and the function support condition of the first base station are not sent or are updated, so that the core network control plane entity sends the configuration update message to the second base station.
In step 202, the second base station stores the protocol version and functional support of the first base station locally.
In step 203, the second base station feeds back its own protocol version and function support to the first base station.
In some embodiments, in the case that the second base station receives the protocol version and the function support condition of the first base station through the newly established direct interface, the second base station feeds back the protocol version and the function support condition of itself to the first base station through the established direct interface.
In addition, under the condition that the second base station receives the protocol version and the function supporting condition of the first base station through the configuration updating message, the second base station judges whether the protocol version and the function supporting condition of the second base station change or not, and if the protocol version and the function supporting condition of the second base station change, the current protocol version and the function supporting condition of the second base station are fed back to the first base station through the established direct interface.
In addition, after the second base station receives the protocol version and the function support condition of the first base station through the core network control plane entity, the second base station feeds back the protocol version and the function support condition of the second base station to the first base station through the core network control plane entity.
In step 204, the first base station stores the protocol version and functional support of the second base station.
In step 205, when the ue in the cell where the first base station is located needs to be switched to the cell where the second base station is located, the first base station determines whether the protocol parameter and the function currently configured by the ue are supported by the second base station according to the protocol version and the function support of the second base station.
In step 206, if at least one of the currently configured protocol parameters and functions of the ue is not supported by the second base station, the first base station sends an RRC reconfiguration message to the ue.
In step 207, the user terminal adjusts the currently configured protocol parameters and functions of the user terminal according to the RRC reconfiguration message, so that the protocol parameters and functions configured by the user terminal can be supported by the second base station.
In some embodiments, the ue reconfigures, according to the RRC reconfiguration message sent by the first base station, the protocol parameters and functions that cannot be supported by the second base station in the current configuration of the ue to the protocol parameters and functions that are supported by the second base station, and deletes or closes the functions that cannot be supported by the second base station in the current configuration of the ue.
In step 208, the user terminal sends an RRC reconfiguration response message to the first base station.
In step 209, the first base station performs a handover of the user terminal to the second base station based on the new configuration of the user terminal.
Fig. 3 is a flow diagram of a method for reducing handover failures according to yet another embodiment of the present disclosure.
In step 301, the first base station sends its own protocol version and function support to the second base station through a predetermined interface.
In some embodiments, the first base station determines whether a direct interface has been established with the second base station. If the first base station and the second base station do not establish a direct interface and the network management configuration information allows the direct interface to be established between the first base station and the second base station, the first base station establishes the direct interface with the second base station through X2/Xn. The first base station sends the protocol version and the function supporting condition of the first base station to the second base station through the establishment message of the direct interface.
In addition, if the first base station and the second base station have established a direct interface, the first base station sends the protocol version and the function support condition of the first base station to the second base station by using the configuration update message through the established direct interface.
In addition, if the first base station and the second base station do not establish a direct interface and the network management configuration information does not allow the direct interface to be established between the first base station and the second base station, the first base station sends the protocol version and the function support condition of the first base station to the core network control plane entity through the configuration update message by using the interface with the core network control plane entity under the condition that the protocol version and the function support condition of the first base station are not sent or are updated, so that the core network control plane entity sends the configuration update message to the second base station.
In step 302, the second base station stores the protocol version and functional support of the first base station locally.
It should be noted that, when the second base station receives the protocol version and the function support condition of the first base station through the configuration update message, the second base station determines whether the protocol version and the function support condition of the second base station change, and if the protocol version and the function support condition of the second base station do not change, the current protocol version and function support condition of the second base station are not fed back to the first base station.
In step 303, when the ue needs to switch to the cell where the second base station is located, if the first base station does not have the protocol version and function support of the second base station, the first base station sends a handover request to the second base station. Wherein the handover request includes protocol parameters and functions currently configured by the user terminal.
In some embodiments, the protocol parameters of the user terminal comprise a parsed version of RRC asn.1, the functionality of the user terminal comprises at least one of PDCP protocol version capability, RLC protocol version capability, MAC protocol version capability, multi-connection configuration capability, and voice support capability, wherein the PDCP protocol version capability comprises at least one of LTE and NR PDCP size support list, PDCP support LTE or NR, multi-connection configuration capability comprises EN-DC support case and/or NE-DC support case, and voice support capability comprises VoNR support case.
In step 304, if the protocol parameters and functions currently configured by the ue are supported by the second base station, the second base station sends a handover success confirmation message to the first base station.
In step 305, after receiving the handover success confirmation message, the first base station records the protocol parameters and functions currently configured by the user terminal locally as the protocol parameters and functions that can be supported by the second base station.
In step 306, the first base station performs a handover of the user terminal to the second base station.
Fig. 4 is a flow diagram of a method for reducing handover failures according to yet another embodiment of the present disclosure.
In step 401, the first base station sends its own protocol version and function support to the second base station through a predetermined interface.
In some embodiments, the first base station determines whether a direct interface has been established with the second base station. If the first base station and the second base station do not establish a direct interface and the network management configuration information allows the direct interface to be established between the first base station and the second base station, the first base station establishes the direct interface with the second base station through X2/Xn. The first base station sends the protocol version and the function supporting condition of the first base station to the second base station through the establishment message of the direct interface.
In addition, if the first base station and the second base station have established a direct interface, the first base station sends the protocol version and the function support condition of the first base station to the second base station by using the configuration update message through the established direct interface.
In addition, if the first base station and the second base station do not establish a direct interface and the network management configuration information does not allow the direct interface to be established between the first base station and the second base station, the first base station sends the protocol version and the function support condition of the first base station to the core network control plane entity through the configuration update message by using the interface with the core network control plane entity under the condition that the protocol version and the function support condition of the first base station are not sent or are updated, so that the core network control plane entity sends the configuration update message to the second base station.
In step 402, the second base station stores the protocol version and functional support of the first base station locally.
It should be noted that, when the second base station receives the protocol version and the function support condition of the first base station through the configuration update message, the second base station determines whether the protocol version and the function support condition of the second base station change, and if the protocol version and the function support condition of the second base station do not change, the current protocol version and function support condition of the second base station are not fed back to the first base station.
In step 403, if the first base station does not have the protocol version and function support of the second base station under the condition that the user equipment needs to be handed over to the cell where the second base station is located, the first base station sends a handover request to the second base station. Wherein the handover request includes protocol parameters and functions currently configured by the user terminal.
In some embodiments, the protocol parameters of the user terminal comprise a parsed version of RRC asn.1, the functionality of the user terminal comprises at least one of PDCP protocol version capability, RLC protocol version capability, MAC protocol version capability, multi-connection configuration capability, and voice support capability, wherein the PDCP protocol version capability comprises at least one of LTE and NR PDCP size support list, PDCP support LTE or NR, multi-connection configuration capability comprises EN-DC support case and/or NE-DC support case, and voice support capability comprises VoNR support case.
In step 404, if at least one of the currently configured protocol parameters and functions of the ue cannot be supported by the second base station, the second base station sends a handover failure message to the first base station.
In step 405, after receiving the handover failure message sent by the second base station, the first base station determines the protocol parameters and functions that can be supported by the second base station in the user terminal according to the received failure message and the history of the bearer handover failure of the handover from the other user terminal in the cell where the first base station is located to the cell where the second base station is located, and records the corresponding information locally.
In step 406, the first base station sends an RRC reconfiguration message to the user terminal.
In step 407, the ue reconfigures the protocol parameters and functions that cannot be supported by the second base station in the current configuration of the ue to the protocol parameters and functions that are supported by the second base station according to the RRC reconfiguration message, and deletes or closes the functions that cannot be supported by the second base station in the current configuration of the ue.
In step 408, the user terminal sends an RRC reconfiguration response message to the first base station.
In step 409, the first base station performs a handover of the user terminal to the second base station based on the new configuration of the user terminal.
Fig. 5 is a block diagram of a communication system for reducing handover failures according to one embodiment of the present disclosure. As shown in fig. 5, the communication system includes a first base station 51 and a second base station 52 adjacent thereto. It should be noted here that there may be a plurality of base stations adjacent to the first base station 51. For simplicity, only one neighboring second base station 52 is shown in fig. 5.
The first base station 51 is configured to acquire the protocol version and functions of the neighboring second base station 52; under the condition that a user terminal in a cell where a first base station 51 is located needs to be switched to a cell where a second base station 52 is located, whether protocol parameters and functions currently configured by the user terminal are supported by the second base station 52 is judged according to a protocol version and a function support condition of the second base station 52; if the protocol parameters and functions currently configured by the user terminal can be supported by the second base station 52, performing handover from the user terminal to the second base station 52; if at least one of the currently configured protocol parameters and functions of the ue cannot be supported by the second base station 52, the currently configured protocol parameters and functions of the ue are adjusted by using the RRC reconfiguration message, so that the currently configured protocol parameters and functions of the ue can be supported by the second base station 52, and then the ue is handed over to the second base station 52.
In the system for reducing handover failure provided by the above embodiment of the present disclosure, the bearer and the function configuration parameter for the user to handover to the neighboring base station are determined by sensing the capability of the neighboring base station, so that the problem of interoperation failure between base stations with different capabilities is reduced, and user experience is improved. In addition, the upgrading requirement of the existing network base station of the operator is avoided, and the CAPEX and OPEX of the operator are reduced.
In some embodiments, the first base station 51 is configured to classify the protocol version and function parameters supported by itself to generate a protocol version and function support condition of the first base station 51; sending the protocol version and the function support condition of the second base station to the second base station 52 through a predetermined interface, so that the second base station 52 stores the protocol version and the function support condition of the first base station 51 locally; after receiving the protocol version and the function support of the second base station 52 fed back by the second base station 52, the protocol version and the function support of the second base station 52 are stored locally.
In some embodiments, the protocol version comprises a parsed version of RRC asn.1, the functional support case comprises at least one of PDCP protocol version capability, RLC protocol version capability, MAC protocol version capability, multi-connection configuration capability, and voice support capability, wherein the PDCP protocol version capability comprises at least one of LTE and NR PDCP size support list, PDCP support LTE or NR, multi-connection configuration capability comprises EN-DC support case and/or NE-DC support case, and voice support capability comprises VoNR support case.
In some embodiments, the first base station 51 is configured to determine whether a direct interface has been established with the second base station 52; if a direct interface is not established with the second base station 52 and the network management configuration information allows a direct interface to be established between the first base station 51 and the second base station 52, the direct interface is established with the second base station 52, and the protocol version and the function support condition of the second base station 52 are sent to the second base station through the establishment message of the direct interface.
Accordingly, the second base station 52 is configured to store the protocol version and the function support of the first base station 51 locally after receiving the protocol version and the function support of the first base station 51 through the established direct interface; and feeds back the protocol version and the function support situation of itself to the first base station 51 through the established direct interface.
In some embodiments, the first base station 51 is further configured to send the protocol version and the function support of the first base station 51 to the second base station 52 by using the configuration update message through the established direct interface if the direct interface with the second base station 52 is established.
Accordingly, the second base station 52 is further configured to store the protocol version and the function support condition of the first base station 51 locally after receiving the protocol version and the function support condition of the first base station 51 through the configuration update message; and judging whether the protocol version and the function support condition of the first base station change, and if the protocol version and the function support condition of the first base station change, feeding back the current protocol version and the current function support condition of the first base station to the first base station 51 through the established direct interface.
In some embodiments, the first base station 51 is further configured to, if no direct interface is established with the second base station 52 and the network management configuration information does not allow a direct interface to be established between the first base station 51 and the second base station 52, send the own protocol version and the function support condition to the core network control plane entity through the configuration update message by using an interface with the core network control plane entity if the own protocol version and the function support condition are never sent or are updated, so that the core network control plane entity sends the configuration update message to the second base station 52.
In some embodiments, the configuration update message comprises: the identity of the first base station 51, the identity of the second base station 52 and the protocol version and functional support of the first base station 51.
Correspondingly, the second base station 52 is further configured to store the protocol version and the function support of the first base station 51 locally after receiving the protocol version and the function support of the first base station 51 through the core network control plane entity; the protocol version and the function support of the first base station 51 are fed back through the core network control plane entity.
In some embodiments, the first base station 51 is configured to detect whether the protocol version and functional support of the second base station 52 has been stored locally; if the protocol version and the function support condition of the second base station 52 are not locally stored, directly storing the protocol version and the function support condition of the second base station 52 locally; if the protocol version and the function support condition of the second base station 52 are locally stored, the locally stored protocol version and the locally stored function support condition of the second base station 52 are updated by using the received protocol version and the function support condition of the second base station 52.
In some embodiments, the first base station 51 is configured to reconfigure the protocol parameters and functions of the current configuration of the user terminal that cannot be supported by the second base station 52 to the protocol parameters and functions supported by the second base station 52 using the RRC reconfiguration message, and delete or turn off the functions of the current configuration of the user terminal that cannot be supported by the second base station 52.
In some embodiments, the first base station 51 is configured to, in a case that the user terminal needs to be handed over to a cell where the second base station 52 is located, send a handover request to the second base station 52 if the user terminal does not have a protocol version and function support condition of the second base station 52, where the handover request includes a protocol parameter and a function currently configured by the user terminal; if receiving a handover failure message sent by the second base station 52, determining protocol parameters and functions that can be supported by the second base station 52 in the user terminal according to the received failure message and a history of bearer handover failure of other user terminals in the cell where the first base station 51 is located to the cell where the second base station 52 is located, and recording corresponding information locally; reconfiguring the protocol parameters and functions that cannot be supported by the second base station 52 in the current configuration of the user terminal to the protocol parameters and functions that are supported by the second base station 52 by using the RRC reconfiguration message, and deleting or closing the functions that cannot be supported by the second base station 52 in the current configuration of the user terminal; a handover of the user terminal to the second base station 52 is performed.
In some embodiments, the protocol parameters of the user terminal comprise a parsed version of RRC asn.1, the functionality of the user terminal comprises at least one of PDCP protocol version capability, RLC protocol version capability, MAC protocol version capability, multi-connection configuration capability, and voice support capability, wherein the PDCP protocol version capability comprises at least one of LTE and NR PDCP size support list, PDCP support LTE or NR, multi-connection configuration capability comprises EN-DC support case and/or NE-DC support case, and voice support capability comprises VoNR support case.
In some embodiments, the first base station 51 is further configured to, if receiving the handover success message sent by the second base station 52, record the protocol parameters and functions currently configured by the user terminal locally as the protocol parameters and functions that can be supported by the second base station 52; and performs handover of the user terminal to the second base station 52.
The present disclosure also provides a computer-readable storage medium. The computer-readable storage medium stores computer instructions, which when executed by the processor implement the method according to any one of the embodiments of fig. 1-4.
The present disclosure is illustrated below by way of a specific example. This example mainly describes a handover procedure between two LTE base stations.
Wherein base station 1 is adjacent to base station 2. Base station 2 adopts rel-13 asn.1 and supports only 12-bit PDCP SN Size, base station 1 has upgraded to support NSA, and has configured NR neighbor cells as NSA cells. Base station 1 supports asn.1 of Rel-15 and supports 12bit and 18bit PDCP SN Size. Currently, there is an NSA user in the cell of the base station 1 that needs to initiate handover to the base station 2, and there is an X2 interface between the base stations 1 and 2, and there is no interaction of protocol and function information between the base stations 1 and 2.
1. The base station 1 classifies the protocol version supported by itself and the functional parameters affecting the interoperation according to the configuration of the OMC (Operation and Maintenance Center), and generates a protocol version and a function support condition, where the generated protocol version and function support condition are as follows:
support for Rel-15
Support for NSA: is set as 1
List of supported PDCP SN Size: 12 bits and 18 bits
Support for VoNR: is set to 0
Support for NE-DC: is set to 0
2. An X2 interface is provided between the base station 1 and the base station 2, and no interaction of protocol and function information exists between the base station 1 and the base station 2. The base station 1 sends the supported protocol version and the function supporting situation to the base station 2 through the eNB Config Update message.
3. The base station 2 does not perform any processing on the interaction information of the protocol and the function information because it does not support the interaction of the protocol and the function information, and does not add the information in the eNB Config Update response message.
4. The base station 1 does not find the protocol version and function support of the base station 2 in the received response message.
5. Base station 1 finds that UE1 needs to switch to base station 2 since UE1 has configured NSA and employs 18-bit PDCP SN Size. The configuration information used by the user is recorded and the UE1 is handed over directly to the base station 2.
6. The base station 1 receives the switching refusing message of the base station 2, judges that the base station 2 does not support Rel-15 and 18bit PDCP SN Size, and records the relevant information to the protocol version and the function information of the base station 2.
7. The base station 1 adopts RRC reconfiguration mode for UE1 to release SCG of UE1, all the bearers are transferred to LTE side, and only 12bit PDCP SN Size is used in configuration.
8. Base station 1 initiates a handover request procedure for UE1 to base station 2.
Through implementing this disclosed above-mentioned scheme, can obtain following beneficial effect:
1. the method and the device support the capability of automatically identifying the adjacent base station when two base stations with different capabilities are adjacently networked, reduce the manual configuration of network management, and support the problem of interconnection and intercommunication when networking of different manufacturers.
2. According to the method and the device, through interaction among the base stations and configuration information acquisition, the possibility of failure of the terminal during switching among different versions of the base stations is reduced, and user perception is improved.
3. The mechanism disclosed by the disclosure can be applied to not only an LTE network and an NSA network, but also an SA network, and can also avoid the problem of interoperation when a new function is introduced into the subsequent 5G.
4. The method and the device have the advantages of small change to the terminal, good backward compatibility and good deployment feasibility. The method and the device enhance the existing protocol, do not introduce a new protocol process, and have low implementation difficulty.
In some embodiments, the functional modules may be implemented as a general purpose Processor, a Programmable Logic Controller (PLC), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other Programmable Logic device, discrete Gate or transistor Logic, discrete hardware components, or any suitable combination thereof, for performing the functions described in this disclosure.
So far, embodiments of the present disclosure have been described in detail. Some details that are well known in the art have not been described in order to avoid obscuring the concepts of the present disclosure. It will be fully apparent to those skilled in the art from the foregoing description how to practice the presently disclosed embodiments.
Although some specific embodiments of the present disclosure have been described in detail by way of example, it should be understood by those skilled in the art that the foregoing examples are for purposes of illustration only and are not intended to limit the scope of the present disclosure. It will be understood by those skilled in the art that various changes may be made in the above embodiments or equivalents may be substituted for elements thereof without departing from the scope and spirit of the present disclosure. The scope of the present disclosure is defined by the appended claims.

Claims (31)

1. A method for reducing handover failures, comprising:
the first base station acquires the protocol version and the function of the adjacent second base station;
under the condition that a user terminal in a cell where a first base station is located needs to be switched to a cell where a second base station is located, the first base station judges whether protocol parameters and functions currently configured by the user terminal are supported by the second base station or not according to a protocol version and a function support condition of the second base station;
if the protocol parameters and functions currently configured by the user terminal can be supported by the second base station, the first base station executes the switching from the user terminal to the second base station;
if at least one of the currently configured protocol parameters and functions of the user terminal cannot be supported by the second base station, the first base station adjusts the currently configured protocol parameters and functions of the user terminal by using an RRC reconfiguration message so that the currently configured protocol parameters and functions of the user terminal can be supported by the second base station, and then performs switching from the user terminal to the second base station.
2. The method of claim 1, wherein the first base station acquiring the protocol version and the function of the neighboring second base station comprises:
the first base station classifies the protocol version and the function parameter supported by the first base station to generate the protocol version and the function supporting condition of the first base station;
the first base station sends the protocol version and the function supporting condition of the first base station to the second base station through a preset interface, so that the second base station stores the protocol version and the function supporting condition of the first base station locally;
and after receiving the protocol version and the function supporting condition of the second base station fed back by the second base station, the first base station stores the protocol version and the function supporting condition of the second base station locally.
3. The method of claim 2, wherein,
the protocol version comprises a parsed version of RRC asn.1, the functional support case comprises at least one of PDCP protocol version capability, RLC protocol version capability, MAC protocol version capability, multi-connection configuration capability, and voice support capability, wherein the PDCP protocol version capability comprises at least one of LTE and NR PDCP size support list, PDCP support LTE or NR, multi-connection configuration capability comprises EN-DC support case and/or NE-DC support case, and voice support capability comprises VoNR support case.
4. The method of claim 2, wherein the first base station transmitting the protocol version and the function support condition of the first base station to the second base station through a predetermined interface comprises:
the first base station judges whether a direct interface is established with the second base station;
if the first base station and the second base station do not establish a direct interface and the network management configuration information allows the establishment of the direct interface between the first base station and the second base station, the first base station and the second base station establish the direct interface;
the first base station sends the protocol version and the function supporting condition of the first base station to the second base station through the establishment message of the direct interface.
5. The method of claim 4, further comprising:
after receiving the protocol version and the function supporting condition of the first base station through the established direct interface, the second base station stores the protocol version and the function supporting condition of the first base station locally;
and the second base station feeds back the protocol version and the function supporting condition of the second base station to the first base station through the established direct interface.
6. The method of claim 4, further comprising:
if the first base station and the second base station establish a direct interface, the first base station sends the protocol version and the function supporting condition of the first base station to the second base station by using the configuration updating message through the established direct interface.
7. The method of claim 6, further comprising:
after receiving the protocol version and the function supporting condition of the first base station through the configuration updating message, the second base station stores the protocol version and the function supporting condition of the first base station locally;
and the second base station judges whether the own protocol version and the function supporting condition change or not, and if the own protocol version and the function supporting condition change, the current protocol version and the function supporting condition of the second base station are fed back to the first base station through the established direct interface.
8. The method of claim 4, further comprising:
if the first base station and the second base station do not establish a direct interface and the network management configuration information does not allow the direct interface to be established between the first base station and the second base station, the first base station sends the protocol version and the function support condition of the first base station to the core network control plane entity through the configuration update message by using the interface with the core network control plane entity under the condition that the protocol version and the function support condition of the first base station are not sent or are updated, so that the core network control plane entity sends the configuration update message to the second base station.
9. The method of claim 8, wherein,
the configuration update message includes: an identity of the first base station, an identity of the second base station, and a protocol version and functional support of the first base station.
10. The method of claim 8, further comprising:
after receiving the protocol version and the function support condition of the first base station through the core network control plane entity, the second base station stores the protocol version and the function support condition of the first base station locally;
and the second base station feeds back the protocol version and the function support condition of the second base station to the first base station through the core network control plane entity.
11. The method of claim 2, wherein the first base station storing the protocol version and the functional support of the second base station locally comprises:
the first base station detects whether the protocol version and the function support condition of the second base station are stored locally;
if the first base station does not locally store the protocol version and the function supporting condition of the second base station, the first base station directly stores the protocol version and the function supporting condition of the second base station locally;
if the first base station has locally stored the protocol version and the function support condition of the second base station, the first base station updates the locally stored protocol version and the function support condition of the second base station by using the received protocol version and the function support condition of the second base station.
12. The method of claim 1, wherein the first base station adjusting currently configured protocol parameters and functions of the user terminal using the RRC reconfiguration message comprises:
and the first base station reconfigures the protocol parameters and functions which cannot be supported by the second base station in the current configuration of the user terminal into the protocol parameters and functions which can be supported by the second base station by using the RRC reconfiguration message, and deletes or closes the functions which cannot be supported by the second base station in the current configuration of the user terminal.
13. The method of claim 1, further comprising:
under the condition that the user terminal needs to be switched to a cell where a second base station is located, if the first base station does not have the protocol version and function supporting condition of the second base station, the first base station sends a switching request to the second base station, wherein the switching request comprises the protocol parameters and the functions currently configured by the user terminal;
if the first base station receives a switching failure message sent by the second base station, the first base station determines protocol parameters and functions which can be supported by the second base station in the user terminal according to the received failure message and a bearing switching failure history record of switching other user terminals in a cell where the first base station is located to the cell where the second base station is located, and records corresponding information locally;
the first base station reconfigures the protocol parameters and functions which cannot be supported by the second base station in the current configuration of the user terminal into the protocol parameters and functions which are supported by the second base station by using RRC reconfiguration information, and deletes or closes the functions which cannot be supported by the second base station in the current configuration of the user terminal;
the first base station performs a handover of the user terminal to the second base station.
14. The method of claim 13, further comprising:
if the first base station receives a switching success message sent by the second base station, the first base station takes the protocol parameters and functions currently configured by the user terminal as the protocol parameters and functions which can be supported by the second base station and records the protocol parameters and functions locally;
the first base station performs a handover of the user terminal to the second base station.
15. The method of claim 13, wherein,
the protocol parameter of the user terminal comprises a resolved version of RRC ASN.1, the function of the user terminal comprises at least one of PDCP protocol version capability, RLC protocol version capability, MAC protocol version capability, multi-connection configuration capability and voice support capability, wherein the PDCP protocol version capability comprises at least one of LTE and NR PDCP size support list, PDCP supports LTE or NR, the multi-connection configuration capability comprises EN-DC support condition and/or NE-DC support condition, and the voice support capability comprises VoNR support condition.
16. A communication system for reducing handover failures, comprising a first base station and a second base station which are adjacent, wherein:
a first base station configured to acquire a protocol version and a function of an adjacent second base station; under the condition that a user terminal in a cell where a first base station is located needs to be switched to a cell where a second base station is located, judging whether a protocol parameter and a function currently configured by the user terminal are supported by the second base station or not according to a protocol version and a function support condition of the second base station; if the protocol parameters and functions currently configured by the user terminal can be supported by the second base station, executing the switching from the user terminal to the second base station; if at least one of the currently configured protocol parameters and functions of the user terminal cannot be supported by the second base station, the currently configured protocol parameters and functions of the user terminal are adjusted by using an RRC reconfiguration message so that the protocol parameters and functions configured by the user terminal can be supported by the second base station, and then the user terminal is switched to the second base station.
17. The system of claim 16, wherein,
the first base station is configured to classify the protocol version and the function parameters supported by the first base station to generate a protocol version and a function supporting situation of the first base station; sending the protocol version and the function supporting condition of the second base station to the second base station through a preset interface so that the second base station can store the protocol version and the function supporting condition of the first base station locally; and after receiving the protocol version and the function supporting condition of the second base station fed back by the second base station, storing the protocol version and the function supporting condition of the second base station locally.
18. The system of claim 17, wherein,
the protocol version comprises a parsed version of RRC asn.1, the functional support case comprises at least one of PDCP protocol version capability, RLC protocol version capability, MAC protocol version capability, multi-connection configuration capability, and voice support capability, wherein the PDCP protocol version capability comprises at least one of LTE and NR PDCP size support list, PDCP support LTE or NR, multi-connection configuration capability comprises EN-DC support case and/or NE-DC support case, and voice support capability comprises VoNR support case.
19. The system of claim 17, wherein,
the first base station is configured to determine whether a direct interface has been established with the second base station; if the direct interface is not established with the second base station and the network management configuration information allows the direct interface to be established between the first base station and the second base station, the direct interface is established with the second base station, and the protocol version and the function support condition of the second base station are sent to the second base station through the establishment message of the direct interface.
20. The system of claim 19, wherein,
the second base station is configured to store the protocol version and the function supporting condition of the first base station locally after receiving the protocol version and the function supporting condition of the first base station through the established direct interface; and feeding back the protocol version and the function supporting condition of the first base station through the established direct interface.
21. The system of claim 19, wherein,
the first base station is further configured to send the protocol version and the function support condition of the first base station to the second base station by using the configuration update message through the established direct interface if the direct interface is established with the second base station.
22. The system of claim 21, wherein,
the second base station is also configured to store the protocol version and the function support condition of the first base station locally after receiving the protocol version and the function support condition of the first base station through the configuration updating message; and judging whether the own protocol version and the function supporting condition change or not, and if the own protocol version and the function supporting condition change, feeding back the own current protocol version and the function supporting condition to the first base station through the established direct interface.
23. The system of claim 19, wherein,
the first base station is further configured to send the protocol version and the function support condition of itself to the core network control plane entity through a configuration update message by using an interface with the core network control plane entity under the condition that the protocol version and the function support condition of itself are not sent or updated if a direct interface is not established with the second base station and the network management configuration information does not allow a direct interface to be established between the first base station and the second base station, so that the core network control plane entity sends the configuration update message to the second base station.
24. The system of claim 23, wherein,
the configuration update message includes: an identity of the first base station, an identity of the second base station, and a protocol version and functional support of the first base station.
25. The system of claim 23, wherein,
the second base station is also configured to store the protocol version and the function support condition of the first base station locally after receiving the protocol version and the function support condition of the first base station through the core network control plane entity; and feeding back the protocol version and the function support condition of the core network control plane entity to the first base station.
26. The system of claim 17, wherein,
the first base station is configured to detect whether the protocol version and the function support condition of the second base station are stored locally; if the protocol version and the function supporting condition of the second base station are not stored locally, directly storing the protocol version and the function supporting condition of the second base station locally; and if the protocol version and the function supporting condition of the second base station are locally stored, updating the locally stored protocol version and the locally stored function supporting condition of the second base station by using the received protocol version and the function supporting condition of the second base station.
27. The system of claim 16, wherein,
the first base station is configured to reconfigure the protocol parameters and functions of the current configuration of the user terminal, which cannot be supported by the second base station, to the protocol parameters and functions supported by the second base station by using the RRC reconfiguration message, and delete or close the functions of the current configuration of the user terminal, which cannot be supported by the second base station.
28. The system of claim 16, wherein,
the first base station is configured to send a switching request to a second base station under the condition that the user terminal needs to be switched to a cell where the second base station is located, if the first base station does not have the protocol version and function supporting condition of the second base station, wherein the switching request comprises the protocol parameters and functions currently configured by the user terminal; if receiving a switching failure message sent by a second base station, determining protocol parameters and functions which can be supported by the second base station in the user terminal according to the received failure message and a bearing switching failure history record of switching other user terminals in a cell where the first base station is located to the cell where the second base station is located, and recording corresponding information locally; reconfiguring the protocol parameters and functions which cannot be supported by the second base station in the current configuration of the user terminal into the protocol parameters and functions which can be supported by the second base station by using an RRC reconfiguration message, and deleting or closing the functions which cannot be supported by the second base station in the current configuration of the user terminal; performing a handover of the user terminal to a second base station.
29. The system of claim 28, wherein,
the first base station is also configured to record the protocol parameters and functions currently configured by the user terminal as protocol parameters and functions which can be supported by the second base station locally if receiving a handover success message sent by the second base station; and performing a handover of the user terminal to a second base station.
30. The system of claim 28, wherein,
the protocol parameter of the user terminal comprises a resolved version of RRC ASN.1, the function of the user terminal comprises at least one of PDCP protocol version capability, RLC protocol version capability, MAC protocol version capability, multi-connection configuration capability and voice support capability, wherein the PDCP protocol version capability comprises at least one of LTE and NR PDCP size support list, PDCP supports LTE or NR, the multi-connection configuration capability comprises EN-DC support condition and/or NE-DC support condition, and the voice support capability comprises VoNR support condition.
31. A computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions which, when executed by a processor, implement the method of any one of claims 1-15.
CN201911341551.3A 2019-12-24 2019-12-24 Method and communication system for reducing handover failure Active CN113038545B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911341551.3A CN113038545B (en) 2019-12-24 2019-12-24 Method and communication system for reducing handover failure

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911341551.3A CN113038545B (en) 2019-12-24 2019-12-24 Method and communication system for reducing handover failure

Publications (2)

Publication Number Publication Date
CN113038545A true CN113038545A (en) 2021-06-25
CN113038545B CN113038545B (en) 2022-07-05

Family

ID=76451280

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911341551.3A Active CN113038545B (en) 2019-12-24 2019-12-24 Method and communication system for reducing handover failure

Country Status (1)

Country Link
CN (1) CN113038545B (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101068442A (en) * 2002-04-11 2007-11-07 高通股份有限公司 Handoff between base stations of different protocol revisions in a CDMA system
CN101137215A (en) * 2007-01-16 2008-03-05 中兴通讯股份有限公司 Method for supporting mobile terminal to move between base stations with diversity of protocol versions
CN101686232A (en) * 2008-09-25 2010-03-31 华为技术有限公司 Method for negotiating communication protocol version, system and equipment thereof
JP2011139328A (en) * 2009-12-28 2011-07-14 Ntt Docomo Inc Mobile communication method, radio base station, and mobile station
CN103581960A (en) * 2012-07-27 2014-02-12 中兴通讯股份有限公司 Capacity indication information processing method and device
CN109831810A (en) * 2017-11-23 2019-05-31 大唐移动通信设备有限公司 A kind of method and apparatus for establishing radio access bearer
CN109874155A (en) * 2017-12-01 2019-06-11 大唐移动通信设备有限公司 A kind of cell switching method and base station

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101068442A (en) * 2002-04-11 2007-11-07 高通股份有限公司 Handoff between base stations of different protocol revisions in a CDMA system
CN101137215A (en) * 2007-01-16 2008-03-05 中兴通讯股份有限公司 Method for supporting mobile terminal to move between base stations with diversity of protocol versions
CN101686232A (en) * 2008-09-25 2010-03-31 华为技术有限公司 Method for negotiating communication protocol version, system and equipment thereof
JP2011139328A (en) * 2009-12-28 2011-07-14 Ntt Docomo Inc Mobile communication method, radio base station, and mobile station
CN103581960A (en) * 2012-07-27 2014-02-12 中兴通讯股份有限公司 Capacity indication information processing method and device
CN109831810A (en) * 2017-11-23 2019-05-31 大唐移动通信设备有限公司 A kind of method and apparatus for establishing radio access bearer
CN109874155A (en) * 2017-12-01 2019-06-11 大唐移动通信设备有限公司 A kind of cell switching method and base station

Also Published As

Publication number Publication date
CN113038545B (en) 2022-07-05

Similar Documents

Publication Publication Date Title
EP2356845B1 (en) Interface setup for communications network with femtocells
CN111182600B (en) Method and apparatus for supporting UE mobility in wireless communication system
EP3573356A1 (en) Method for controlling states of terminal device, terminal device, and network device
CN107925932B (en) Method for dividing control and user plan during LTE-WLAN aggregated handover, communication equipment and communication device
US20200275356A1 (en) Radio network node, network node, database, configuration control node, and methods performed thereby
US20130014210A1 (en) System and method for selection of security algorithms
KR101830740B1 (en) Method for managing information about on/off small cells in radio access system and apparatus for supporting same
US20130070679A1 (en) Method and Device for Data Processing in a Wireless Network
CN110972331B (en) Communication method between base stations, base station and communication system
CN110062467B (en) Radio station, control plane function node, and method thereof
US10104595B2 (en) Method of automatically adjusting mobility parameter
CN112637963B (en) Method for releasing multiple access protocol data unit session and user equipment thereof
TW202106082A (en) Method for voice calls and mobile termination
JP2021531678A (en) Handling of integrity protection in gNB-CU-UP
EP4132101A1 (en) Connection mode configuration method, base station, and communication system
US20230044291A1 (en) RRC SEGMENTATION AND QoE
US20230262557A1 (en) Methods and devices for enhancing integrated access backhaul networks for new radio
CN112788693A (en) Method and device for supporting self-optimization
CN116671085A (en) Apparatus and method for deleting new radio cell not supporting new radio voice from measurement report
CN110740023A (en) Method and device for sending control signaling, serving base station and storage medium
EP3920579A1 (en) Wireless network communication method, network device, and terminal device
CN113038545B (en) Method and communication system for reducing handover failure
CN109792659B (en) Method and apparatus for modifying a user data path in a wireless communication network
US20230199879A1 (en) Methods and devices for enhancing integrated access backhaul networks for new radio
CN114630355B (en) Fault recovery method, device, equipment and storage medium based on core network

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