A user equipment release method and apparatus, a network device, and a storage medium

Abstract

Embodiments of the present application provide a user equipment release method and device, network equipment and storage medium. The method comprises: in the case that it is detected that a user equipment fails to release resources occupied in a source cell, a master base station interacts with a core network and a secondary base station to release a context of the user equipment; and the master base station interacts with the user equipment to release a connection between the user equipment and the master base station. Therefore, in the embodiments of the present application, in the case that a user is hung, a release process of the user equipment is automatically triggered, thereby releasing the resources occupied by the user equipment in the source cell, and further improving NSA cell throughput and capacity, avoiding affecting the access of new users, and improving real user rate.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of mobile communication, and in particular to a user equipment release method and device, a network device and a storage medium. BACKGROUND

[0002] 5G non-standalone (NSA) architecture has been built by a large number of construction companies. The 5G carrier only carries user data, and its control signaling is still transmitted through the 4G network. In the NSA network, the primary base station is the 4G base station, which is already a relatively mature wide-coverage mobile network, and the secondary base station is the 5G base station. That is, the 5G base station relies on the 4G base station and the 4G core network to operate without an independent signaling surface. Among them, there are many NSA networking modes, and the option3x (i.e., option3x architecture) networking scheme is preferred during network construction, that is, as shown in Figure 1 , the 4G core network is an evolved packet switching core network (EPC), and the 5G new radio (NR) accesses the EPC with the long term evolution (LTE) eNB as the control plane anchor point. The gNB and eNB are connected through the ENDC X2 to transmit data streams and signaling streams. Among them, the eNB is the 4G base station, and the gNB is the 5G base station.

[0003] Currently, in the NSA network, during user switching or transmission splicing, the problem of hanging users in both the LTE cell and the NR cell occasionally occurs. Among them, the cell hanging users occupy cell radio resources but are not real users, thereby causing the NSA cell throughput and capacity to decrease, causing the access problem of new users, and also causing the real user rate to decrease. SUMMARY

[0004] Embodiments of the present application provide a user equipment release method, device, network device and storage medium to solve the problem of cell hanging users occupying cell radio resources, thereby reducing the NSA cell throughput and capacity, affecting the access of new users, and causing the real user rate to decrease.

[0005] In a first aspect, embodiments of the present application provide a user equipment release method applied to a primary base station, the method comprising:

[0006] In the case where it is detected that the resources occupied by the user equipment in the source cell are not successfully released, interacting with the core network and the secondary base station to release the context of the user equipment;

[0007] Interacting with the user equipment to release the connection between the user equipment and the primary base station.

[0008] Optionally, the interacting with the core network and the secondary base station to release the context of the user equipment comprises:

[0009] sending a user equipment context release request to the core network, wherein the user equipment context release request is used to instruct the core network to release the context of the user equipment;

[0010] receiving a user equipment context release instruction sent by the core network;

[0011] sending a user equipment context release message to the secondary base station, wherein the user equipment context release message is used to instruct the secondary base station to release the context of the user equipment.

[0012] Optionally, after the sending the user equipment context release message to the secondary base station, the method further comprises:

[0013] sending a user equipment context release complete message to the core network.

[0014] Optionally, the user equipment context release request carries target indication information, and the target indication information is used to instruct the release of the user equipment triggered by an OM.

[0015] Optionally, the interacting with the user equipment to release the connection between the user equipment and the primary base station comprises:

[0016] sending a radio resource control connection release message to the user equipment, wherein the radio resource control connection release message is used to instruct the user equipment to release the radio resource control connection between the user equipment and the primary base station.

[0017] Optionally, before the interacting with the core network and the secondary base station to release the context of the user equipment, the method further comprises:

[0018] detecting whether the resource occupied by the user equipment in the source cell is successfully released;

[0019] Optionally, the detecting whether the resource occupied by the user equipment in the source cell is successfully released comprises:

[0020] in a case where a secondary base station modification request rejection message sent by the secondary base station is received, or in a case where a secondary base station modification rejection message sent by the primary base station to the secondary base station is received, determining that the resource occupied by the user equipment in the source cell is not successfully released;

[0021] in a case where the secondary base station modification request rejection message sent by the secondary base station is not received, and the secondary base station modification rejection message sent by the primary base station to the secondary base station is not received, determining that the resource occupied by the user equipment in the source cell is successfully released.

[0022] In a second aspect, the embodiments of the present application further provide a user equipment release method applied to a core network, the method comprising:

[0023] In the case that the resources occupied by the user equipment in the source cell are not successfully released, interacting with a master base station to release the context of the user equipment.

[0024] Optionally, the interacting with the master base station to release the context of the user equipment comprises:

[0025] receiving a user equipment context release request sent by the master base station;

[0026] releasing the context of the user equipment according to the user equipment context release request;

[0027] sending a user equipment context release instruction to the master base station, wherein the user equipment context release instruction is used to instruct the master base station to send a user equipment context release message to the secondary base station, and the user equipment context release message is used to instruct the secondary base station to release the context of the user equipment.

[0028] Optionally, after the sending of the user equipment context release instruction to the master base station, the method further comprises:

[0029] receiving a user equipment context release completion message sent by the master base station.

[0030] Optionally, the user equipment context release request carries target indication information, and the target indication information is used to instruct to release the user equipment triggered by an OM.

[0031] In a third aspect, the embodiments of the present application provide a network device applied to a master base station, comprising a memory, a transceiver and a processor:

[0032] the memory is used to store a computer program; the transceiver is used to transceive data under the control of the processor; and the processor is used to execute the user equipment release method of the first aspect.

[0033] In a fourth aspect, the embodiments of the present application provide a network device applied to a core network, comprising a memory, a transceiver and a processor:

[0034] the memory is used to store a computer program; the transceiver is used to transceive data under the control of the processor; and the processor is used to execute the user equipment release method of the second aspect.

[0035] In a fifth aspect, the embodiments of the present application provide a user equipment release device applied to a master base station, the device comprising:

[0036] a first interaction module, configured to interact with the core network and the secondary base station to release a context of the user equipment in a case where it is detected that the resources occupied by the user equipment in the source cell are not successfully released;

[0037] a second interaction module, configured to interact with the user equipment to release a connection between the user equipment and the primary base station.

[0038] In the sixth aspect, an embodiment of the present application provides a user equipment release device applied to a core network, and the device comprises:

[0039] a third interaction module, configured to interact with the primary base station to release a context of the user equipment in a case where the resources occupied by the user equipment in the source cell are not successfully released.

[0040] In the seventh aspect, an embodiment of the present application further provides a processor readable storage medium, which stores a computer program, and the computer program is used to make the processor execute the user equipment release method in the first aspect or the second aspect.

[0041] In the embodiment of the present application, in a case where the resources occupied by the user equipment in the source cell are not successfully released, that is, in a case where the user hanging phenomenon occurs, the primary base station interacts with the core network and the secondary base station to release the context of the user equipment, and interacts with the user equipment to release the connection between the user equipment and the primary base station. Therefore, in the embodiment of the present application, in a case where the user hanging phenomenon occurs, the release process of the user equipment is automatically triggered, so as to release the resources occupied by the user equipment in the source cell, thereby improving the NSA cell throughput and capacity, avoiding affecting the access of new users, and improving the real user rate. BRIEF DESCRIPTION OF DRAWINGS

[0042] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the description of the embodiments of the present application. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can also be obtained by those skilled in the art without any creative labor on the basis of these drawings.

[0043] Figure 1 It is a NSA network architecture diagram in the prior art;

[0044] Figure 2 It is a process diagram of establishing an EN-DC X2 link in the prior art;

[0045] Figure 3 It is a process diagram of UE accessing an NSA cell in the prior art;

[0046] Figure 4 A mobile diagram of a UE in the prior art;

[0047] Figure 5 A flow diagram of a UE in the prior art;

[0048] Figure 6 A diagram of the interaction time of a UE, MN, EPC and SN in the prior art;

[0049] Figure 7 A diagram of the interaction time of a UE, MN, EPC and SN in the prior art;

[0050] Figure 8 A diagram of the interaction time of a UE, MN, EPC and SN in the prior art;

[0051] Figure 9 A diagram of the interaction time of a UE, MN, EPC and SN in the prior art;

[0052] Figure 10 A flow diagram of a UE in the prior art;

[0053] Figure 11 A flow diagram of a UE in the prior art;

[0054] Figure 12 A flow diagram of a UE in the prior art;

[0055] Figure 13 A flow diagram of a UE in the prior art;

[0056] Figure 14 A flow diagram of a UE in the prior art;

[0057] Figure 15 A flow diagram of a UE in the prior art;

[0058] Figure 16 A flow diagram of a UE in the prior art;

[0059] Figure 17 A flow diagram of a UE in the prior art; DETAILED DESCRIPTION

[0060] The term "and / or" in the embodiments of the present application describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent the following three cases: A exists alone, A and B exist together, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after it.

[0061] The term "multiple" in the embodiments of the present application refers to two or more, and other quantifiers are similar.

[0062] The technical solutions in the embodiments of the present application will be described clearly and completely below in combination with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0063] The embodiments of the present application provide a user equipment release method and device, network equipment and storage medium, to solve the problem that the cell hanging user occupies the wireless resources of the cell, thereby reducing the NSA cell throughput and capacity, affecting the access of new users, and causing the real user rate to decrease.

[0064] The method and the device are based on the same application concept. Since the principles of the method and the device for solving the problem are similar, the implementation of the device and the method can be referred to each other, and the repeated parts will not be described again.

[0065] In addition, the technical solutions provided by the embodiments of the present application can be applied to various systems, especially 5G systems. For example, the applicable systems can be global system of mobile communication (GSM) systems, code division multiple access (CDMA) systems, Wideband Code Division Multiple Access (WCDMA) general packet radio service (GPRS) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, long term evolution advanced (LTE-A) systems, universal mobile systems (UMTS), worldwide interoperability for microwave access (WiMAX) systems, 5G new radio (NR) systems, etc. Among these various systems, there are terminal devices and network devices. The system can also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0066] The terminal device to which the embodiments of the present application relate can refer to a device that provides voice and / or data connectivity to a user, a handheld device having a wireless connection function, or other processing devices connected to a wireless modem, etc. In different systems, the name of the terminal device can also be different, for example, in the 5G system, the terminal device can be called user equipment (User Equipment, UE). The wireless terminal device can communicate with one or more core networks (Core Network, CN) through a radio access network (Radio Access Network, RAN). The wireless terminal device can be a mobile terminal device, such as a mobile phone (also known as a "cellular" phone) and a computer with a mobile terminal device, for example, it can be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a radio access network. For example, personal communication service (Personal Communication Service, PCS) phones, cordless phones, session initiation protocol (Session Initiated Protocol, SIP) phones, wireless local loop (Wireless Local Loop, WLL) stations, personal digital assistants (Personal Digital Assistant, PDA) and the like. The wireless terminal device can also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, an access point, a remote terminal, an access terminal, a user terminal, a user agent, a user device, which is not limited in the embodiments of the present application.

[0067] The network device related to the embodiments of the present application can be a base station, which can include multiple cells serving terminals. According to different application scenarios, the base station can also be referred to as an access point, or can be a device in an access network that communicates with wireless terminal devices through one or more sectors over an air interface, or other names. The network device can be used to exchange received air frames and Internet Protocol (IP) packets as a router between wireless terminal devices and the rest of the access network, which can include an Internet Protocol (IP) communication network. The network device can also coordinate the management of the properties of the air interface. For example, the network device related to the embodiments of the present application can be a network device (Base Transceiver Station, BTS) in the Global System for Mobile Communications (GSM) or Code Division Multiple Access (CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolved network device (evolutional Node B, eNB or e-NodeB) in a long term evolution (LTE) system, or a 5G base station (gNB) in a next generation system, or a Home evolved Node B (HeNB), a relay node, a femto, a pico, etc., which are not limited in the embodiments of the present application. In some network structures, the network device can include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit can also be geographically separated.

[0068] The network device and the terminal device can each use one or more antennas for multi-input multi-output (MIMO) transmission, which can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). According to the shape and number of root antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, and can also be diversity transmission or precoding transmission or beamforming transmission, etc.

[0069] In order to facilitate the understanding of the user equipment release method of the embodiments of the present application, first, the phenomenon of hanging users and the method for solving the phenomenon of hanging users in the prior art are described as follows.

[0070] In the option3x networking, the gNB and the eNB transmit data streams and signaling streams through the dual connectivity (ENDC X2) between the LTE base station and the NR base station. Among them, the ENDC link establishment related process defined in 3GPP TS36.423 is as shown in the following table: Figure 2 As shown in the table, the initiator of the EN-DC X2 setup request (EN-DC X2 Setup Request) can be the primary base station or the secondary base station, and the opposite party returns the EN-DC X2 setup response (EN-DC X2 Setup Response) when the EN-DC is successfully established. The establishment of the EN-DC X2 link is used for the primary base station and the secondary base station to interact with the application data on the X2 interface, this process will delete any existing application data in the two nodes and replace it with the received data, this process uses non-UE related signaling, the radio resource control protocol data unit (RRC PDU) of the secondary base station can be transmitted to the UE through the primary base station, that is, at the initial access, the RRC PDU of the secondary base station must be transmitted through the primary base station, but it can be completed through the primary base station or the secondary base station thereafter.

[0071] Among them, the flow of 5G user accessing NSA cell is shown in the signaling flow Figure 3 , which is described in detail as follows:

[0072] Step 301: The master base station (i.e. MN or MeNB) sends a secondary base station addition request (SgNBAdditionRequest) to the secondary base station (i.e. SN or SgNB), which carries parameters for allocating resources for user plane (E-RAB) to establish a control plane protocol (X2AP) of the X2 interface and parameters for establishing a GPRS tunneling protocol (GTP). The SN addition process is triggered by the MN, and a UE context is established on the SN, which is used to provide NR-side wireless resources for the UE. When a secondary cell group (SCG) wireless resource bearer is required, at least one SCG cell is added in this process, and the MN adds the SN while carrying UE capability information to transfer UE measurement-related information.

[0073] Step 302: The SN returns a secondary base station addition response (SgNBAdditionRequestAcknowledge) to the MN, which carries information related to the establishment of the E-RAB X2AP interface and GTP. The container information transmitted by the SN to the MN carries the wireless configuration of the SCG, and the SN allocates wireless resource configuration through the NR radio resource control reconfiguration (rrcReconfiguration), which is finally transmitted to the UE by the MN.

[0074] Step 303: The MN sends a radio resource control connection reconfiguration signaling (rrcConnectionReconfiguration) to the UE, which contains rrcReconfiguration information of the NR cell.

[0075] Step 304: The UE returns a RRC connection reconfiguration complete (rrcConnectionReconfigurationComplete) to the MN after receiving the cell information on the NR side, which contains the rrcConnectionReconfigurationComplete. If the UE cannot perform the reconfiguration, it will trigger an RRC reestablishment process.

[0076] Step 305: The MN sends a secondary base station reconfiguration complete (SgNBReconfigurationComplete) to the SN, which carries information related to the establishment of the E-RAB, X2AP interface, and GTP tunnel. After receiving the rrcConnectionReconfigurationComplete, the MN notifies the SN that the UE has successfully completed the RRC reconfiguration process.

[0077] Step 306: The UE starts random access to the SN and completes the random access signaling process of the NR-side cell.

[0078] Step 307: If the SN triggered bearer configuration is a Radio Link Control Acknowledge Mode (RLC AM) mode, the MN sends a SN Status Transfer to the SN;

[0079] Step 308: If the SN triggered bearer configuration is a RLC AM mode, the MN forwards data flow to the SN due to EN-DC activation, thereby reducing service latency.

[0080] Up to now, the user can perform various services.

[0081] In addition, the mobility of the user equipment is as shown in Figure 4 That is, when the UE moves from one NR cell to another NR cell, in order to ensure the continuity of services, the UE is triggered to perform a primary secondary cell (PSCell) change. Details are as follows:

[0082] The UE first performs RRC connection to enter an RRC connected state at the primary base station MeNB1 coverage area shown in ①;

[0083] When the UE moves to the position shown in ②, that is, the UE moves to the NR1 cell in the coverage area of the secondary base station SgNB1, if the secondary base station SgNB1 is within the coverage area of the primary base station MeNB1, the UE enters a secondary base station addition process (i.e., performs the flow shown in Figure 3 When the UE moves to the position shown in ③, that is, the UE moves to the NR2 cell in the coverage area of the secondary base station SgNB1, if the signal of the NR2 cell is stronger than that of the NR1 cell, the UE enters a secondary base station modification process;

[0084] When the UE moves to the position shown in ④, that is, the UE moves to the coverage area of the secondary base station SgNB2, if the secondary base station SgNB2 is also within the coverage area of the primary base station MeNB1, and the cell signal of the secondary base station SgNB2 is stronger than that of the secondary base station SgNB1, the UE enters a secondary base station change process;

[0085] When the UE moves to the position shown in ⑤, that is, the UE moves to the coverage area of the primary base station MeNB2, if the cell signal of the primary base station MeNB2 is stronger than that of the primary base station MeNB1, the UE enters an inter-primary base station handover process;

[0086] When the UE moves to the position shown in ⑥, that is, the UE moves out of the coverage area of the secondary base station SgNB2 and there is no other secondary base station coverage, the UE enters a secondary base station release flow.

[0087]

[0088] ​In the current NSA user switching test, there are occasional user hanging phenomena when thousands of switches are performed. As shown in Figure 4 , the positions of ③, ④, and ⑤ all have this low probability problem. The following will take the secondary base station modification process at the position of ③ in Figure 4 as an example for illustration.

[0089] As shown in Figure 5 , the signaling of steps 501 to 508 is a normal secondary base station modification process, and steps 509 to 512 are an abnormal flow. The probability of this abnormal flow problem occurring in the network is less than 0.1%. Among them, when the UE is about to enter the secondary base station modification process, the MN does not receive the measurement report reported by the user UE from the signaling (i.e. the MN does not receive the uplink information forwarding NR measurement report (ULInformationTransferMRDC) reported by the UE, and the SN does not receive the RRC transmission information (RRCTransfer) transferred by the MN), resulting in incorrect cause value in the modification request of the SN or incorrect cause value in the modification request of the MN (i.e. radioNetwork:sCG-Mobility does not appear, but radioNetwork:count-reaches-max-value appears, that is, no radioNetwork NR mobility information appears in the cause value field, but radioNetwork count reaches the maximum value appears), so that the SN sends a secondary base station modification request rejection (SgNBModificationRequestReject) to the MN, or the MN sends a secondary base station modification refusal (SgNBModificationRefuse) to the SN, that is, the modification request of the SN is rejected, and the SN and the MN will not issue a change confirmation message, and then the RRC connection and UE context release process cannot occur, and finally the user hanging phenomenon occurs.

[0090] As shown in Figure 6 and Figure 7 , it is the signaling interaction diagram between the same UE and the MN (i.e. the eNB shown in Figure 6 and Figure 7 ), the SN (i.e. the Adj_eNB shown in Figure 6 and Figure 7 ), and the EPC. Among them, at 2021-04-03 05:15:10:676 (i.e. the time circled in the block in Figure 6 ) and 2021-04-0316:15:40:343 (i.e. the time circled in the block in Figure 7After the two time points (the time points circled in the middle box), no UE release process, it will become the user hanging. In addition, at the two time points of 2021-04-03 05:15:11:019 and 2021-04-03 16:15:40:655, the UE immediately initiates a new access process, causing the user resources at the two time points to be released, so that the UE occupying the resources becomes a virtual user after the two time points of 2021-04-03 05:15:11:019 and 2021-04-03 16:15:40:655. That is, the UE still occupying the wireless resources of the base station becomes the hanging NSA user. This problem will always occupy the wireless resources of the base station when it occurs in the live network, and is a stubborn problem of the current network.

[0091] Currently, there are two ways to deal with the above-mentioned hanging user phenomenon:

[0092] Method one: when the NSA UE survival detection switch on the MN or SN side is closed, only manual operation command on the network side can be used to release, that is, the hanging user can be cleared when the cell is deleted or the network is upgraded and the base station is reset.

[0093] Method two: when the NSA UE survival detection switch on the MN and SN sides is opened at the same time, the release of the hanging user will be triggered as long as the duration of no data transmission between the UE and the base station exceeds the NSA UE survival detection period. However, in fact, there is still a small amount of data interaction between the hanging user and the base station, which is the reason why the hanging user cannot be released for a long time. Through test observation, the duration of the hanging user is less than 20 seconds, more than 5 minutes, for example Figure 8 The duration of the hanging user is about 20 seconds (i.e. Figure 8 The duration of the hanging user is about 20 seconds (i.e. Figure 9 The duration of the hanging user is about 20 seconds (i.e. Figure 9 The duration of the hanging user is about 20 seconds (i.e.

[0094] It should be noted that in Figures 6 to 9In the present embodiment, SgNB Modification Required indicates a secondary base station modification request; SgNB Modification Request indicates a secondary base station modification request; SgNB Modification Request Acknowledge indicates a secondary base station modification request acknowledgement; rrcConnectionReconfigruation indicates an RRC connection reconfiguration command; rrcConnectionReconfigruationComplete indicates an RRC connection reconfiguration completion; SgNB Modification Confirm indicates a secondary base station modification confirmation; rrcConnectionSetup indicates an RRC connection setup command; rrcConnectionSetupComplete indicates an RRC connection setup completion; Initial UE Message indicates initial user information; E-RAB Modification Request indicates a user plane bearer modification request; E-RAB Modification Confirm indicates a user plane bearer modification confirmation; SgNB Modification Confirm indicates a secondary base station modification confirmation; SgNB Activity Notification indicates a secondary base station activity notification; UE Context Release Request indicates a UE context release request; UE Context Release Command indicates a UE context release command; UE Context Release indicates a UE context release; rrcConnectionRelease indicates an RRC connection release; UE Context Release Complete indicates a UE context release completion; Initial Context Setup Request indicates an initial context setup request; and ueCapabilityEnquiry indicates a UE capability enquiry.

[0095] In summary, the current processing flow for the hanging user phenomenon is as shown in Figure 10 , that is, as follows:

[0096] In the NSA UE moving process, when the SN sends SgNBModificationRequired to the MN, the MN parses the cause value in the signaling as "radioNetwork: count-reaches-max-value", and then the MN sends "SgNBModificationRefuse" to the SN; when the MN sends SgNBModificationRequest to the SN, the SN parses the cause value in the signaling as "radioNetwork: count-reaches-max-value", and then the SN sends "SgNBModificationRequestRefuse" to the MN. When the MN sends "SgNBModificationRefuse" to the SN, or the SN sends "SgNBModificationRequestRefuse" to the MN, if the NSA user alive detection switch in the cell is on, it is judged that there is data interaction between the UE and the base station, and if there is not, the UE is released after waiting for an NSA user alive detection period; if there is, the UE remains in the suspended user state until it is manually released; if the NSA user alive detection switch in the cell is not on, the UE remains in the suspended user state until it is manually released.

[0097] As can be seen from the above, the current manual network side processing method for eliminating suspended users has the following shortcomings:

[0098] (1) The NSA UE alive detection switch is turned on, and the suspended UE needs to wait for the NSA UE alive detection period before being released. The default period is 10 seconds, and if there is no data interaction between the NSA user and the base station, the actual waiting time for the base station to trigger the release of the suspended UE is not less than 20 seconds.

[0099] (2) If the NSA UE alive detection switch is turned on, and there is data interaction between the NSA user and the base station, the actual waiting time for the base station to trigger the release of the suspended UE is more than 5 minutes, and if there is always data interaction, the UE will not be released.

[0100] (3) The time point of manually releasing the suspended user is not easy to control. Since there are many users in the cell and the mobility is random, the time point of the suspended user is indefinite, so the manual judgment is inevitably delayed, resulting in a longer time for the suspended users in the NR cell to occupy resources.

[0101] (4) In the case that the NSA UE survival detection is not opened, if multiple NR cells all have the phenomenon of hanging users, the UE can be released manually after a command is input on the network side. However, the operability is poor. Although the deletion and construction of the NR cell can release all users, the user perception is affected.

[0102] (5) The user hung by the NR cell is a virtual user, cannot be used, occupies the NR cell resource and cannot be normally released, which obviously affects the capacity of the NR cell and can cause the failure of new user access.

[0103] (6) The user hung by the NR cell waits for a large time span of network upgrade base station reset, and the present network upgrade is generally once per several months, so it is not realistic to solve the problem of hanging users by this way.

[0104] Figure 11 A flowchart of a user equipment release method provided by an embodiment of the application is shown. The method is applied to a master base station, as shown in the figure, and can include the following steps: Figure 11

[0105] Step 1101: In the case that the resource occupied by the user equipment in the source cell is not successfully released, interact with the core network and the secondary base station to release the context of the user equipment.

[0106] The source cell is the cell accessed by the user equipment before cell switching. The source cell can be an NR cell, an SgNB or an MeNB.

[0107] In addition, the resource occupied by the UE in the source cell is not successfully released, which means that the UE has the phenomenon of hanging users, that is, the UE is a virtual user, cannot be used but still occupies the source cell resource and cannot be normally released.

[0108] Optionally, before the interaction with the core network and the secondary base station to release the context of the user equipment, the method further includes:

[0109] detecting whether the resource occupied by the user equipment in the source cell is successfully released;

[0110] The detection of whether the resource occupied by the user equipment in the source cell is successfully released includes:

[0111] In the case that the secondary base station modification request rejection message sent by the secondary base station is received, or in the case that the secondary base station modification rejection message is sent by the master base station to the secondary base station, it is determined that the resource occupied by the user equipment in the source cell is not successfully released;

[0112] ​In a case that the secondary base station modification request rejection message sent by the secondary base station is not received and the secondary base station modification rejection message is not sent by the master base station to the secondary base station, it is determined that the resource occupied by the user equipment in the source cell is successfully released.

[0113] Therefore, in the embodiment of the application, the fact that the secondary base station modification request rejection message sent by the SN is received by the MN or the secondary base station modification rejection message sent by the MN is received by the SN indicates that the resource occupied by the UE in the source cell is not successfully released, i.e., the phenomenon of hanging user occurs.

[0114] Optionally, the interaction with the core network and the secondary base station to release the context of the user equipment comprises:

[0115] sending a user equipment context release request to the core network, wherein the user equipment context release request is used to instruct the core network to release the context of the user equipment;

[0116] receiving a user equipment context release instruction sent by the core network;

[0117] sending a user equipment context release message to the secondary base station, wherein the user equipment context release message is used to instruct the secondary base station to release the context of the user equipment.

[0118] Therefore, in the embodiment of the application, when the phenomenon of hanging user occurs, the MN sends a user equipment context release request to the core network to make the core network release the context of the user equipment (i.e., release the resource occupied by the UE in the core network). After receiving the user equipment context release request sent by the MN, the core network also replies to the MN with a user equipment context release instruction to instruct the MN to send a user equipment context release message to the SN, so that the SN releases the context of the user equipment (i.e., releases the resource occupied by the user equipment on the SN side) according to the user equipment context release message.

[0119] Optionally, after the user equipment context release message is sent to the secondary base station, the method further comprises:

[0120] sending a user equipment context release completion message to the core network.

[0121] Therefore, in the embodiment of the application, after the user equipment context release message is sent to the SN by the MN, a user equipment context release completion message can also be sent to the core network by the MN, so that the core network can be made to know that the context of the user equipment has been released.

[0122] Optionally, the user equipment context release request carries target indication information, and the target indication information is used to instruct the release of the user equipment triggered by the OM.

[0123] The target indication information carried in the user equipment context release request sent by the MN to the core network can make the core network know that the release of the user equipment is triggered by the OM.

[0124] Step 1102: interacting with the user equipment to release the connection between the user equipment and the master base station.

[0125] In step 1102, the released connection between the user equipment and the master base station can be an RRC connection between the user equipment and the master base station.

[0126] Optionally, the interaction with the user equipment to release the connection between the user equipment and the master base station includes:

[0127] sending a radio resource control connection release message to the user equipment, where the radio resource control connection release message is used to instruct the user equipment to release the radio resource control connection with the master base station.

[0128] Therefore, in the embodiment of the application, the MN can send an RRC release message to the user equipment to make the user equipment release the RRC connection between the user equipment and the master base station.

[0129] As can be seen from steps 1101 to 1102, in the embodiment of the application, when it is detected that the resources occupied by the user equipment in the source cell are not successfully released, that is, when the user hanging phenomenon occurs, the master base station interacts with the core network and the secondary base station to release the context of the user equipment, and interacts with the user equipment to release the connection between the user equipment and the master base station. Therefore, in the embodiment of the application, when the user hanging phenomenon occurs, the release process of the user equipment is automatically triggered, so that the resources occupied by the user equipment in the source cell are released, thereby improving the NSA cell throughput and capacity, avoiding affecting the access of new users, and improving the real user rate.

[0130] Figure 12 Fig. 2 shows a flowchart of another user equipment release method provided by the embodiment of the application. The method is applied to a core network, such as a mobility management entity (MME). Figure 12 As shown in the figure, the method can include the following steps:

[0131] Step 1201: in the case where the resources occupied by the user equipment in the source cell are not successfully released, interacting with the master base station to release the context of the user equipment.

[0132] In the embodiment of the present application, in the case that the resources occupied by the user equipment in the source cell are not successfully released, the MN interacts with the core network to release the context of the user equipment, and the MN also interacts with the user equipment to release the connection between the user equipment and the MN, so as to realize the release of the user equipment, i.e. the release of the resources occupied by the user equipment.

[0133] The source cell is a cell accessed by the user equipment before the cell switching. The source cell can be an NR cell, an SgNB or an MeNB.

[0134] In addition, the fact that the resources occupied by the UE in the source cell are not successfully released means that the UE is a virtual user, i.e. the UE cannot be used but still occupies the resources of the source cell and cannot be normally released.

[0135] In addition, in the embodiment of the present application, the fact that the MN receives the secondary base station modification request rejection message sent by the SN or the SN receives the secondary base station modification rejection message sent by the MN means that the resources occupied by the UE in the source cell are not successfully released, i.e. the UE is a virtual user.

[0136] Optionally, the interaction with the master base station to release the context of the user equipment comprises:

[0137] receiving a user equipment context release request sent by the master base station;

[0138] releasing the context of the user equipment according to the user equipment context release request;

[0139] sending a user equipment context release instruction to the master base station, wherein the user equipment context release instruction is used to instruct the master base station to send a user equipment context release message to the secondary base station, and the user equipment context release message is used to instruct the secondary base station to release the context of the user equipment.

[0140] Therefore, in the embodiment of the present application, when the virtual user phenomenon occurs, the MN sends a user equipment context release request to the core network to make the core network release the context of the user equipment (i.e. release the resources occupied by the UE in the core network). After receiving the user equipment context release request sent by the MN, the core network also returns a user equipment context release instruction to the MN to instruct the MN to send a user equipment context release message to the SN, so that the SN releases the context of the user equipment (i.e. releases the resources occupied by the user equipment on the SN side) according to the user equipment context release message.

[0141] Optionally, after the user equipment context release instruction is sent to the master base station, the method further comprises:

[0142] receiving a user equipment context release completion message sent by the master base station.

[0143] In the embodiment of the application, after the core network sends the user equipment context release instruction to the MN, the core network receives the user equipment context release completion message sent by the MN, so that the core network can determine that the context of the user equipment has been released.

[0144] Optionally, the user equipment context release request carries target indication information, and the target indication information is used to indicate that the release of the user equipment is triggered by the OM.

[0145] The target indication information carried in the user equipment context release request sent by the MN to the core network can make the core network determine that the release of the user equipment is triggered by the OM.

[0146] As can be seen from the above, in the embodiment of the application, in the case where it is detected that the resources occupied by the user equipment in the source cell are not successfully released, that is, in the case where the user hanging phenomenon occurs, the master base station interacts with the core network and the secondary base station to release the context of the user equipment, and interacts with the user equipment to release the connection between the user equipment and the master base station. Therefore, in the embodiment of the application, in the case where the user hanging phenomenon occurs, the release process of the user equipment is automatically triggered, so as to release the resources occupied by the user equipment in the source cell, thereby improving the NSA cell throughput and capacity, avoiding affecting the access of new users, and improving the real user rate.

[0147] As can be seen from the above, in the embodiment of the application, in the case where it is detected that the resources occupied by the user equipment in the source cell are not successfully released, that is, in the case where the user hanging phenomenon occurs, the master base station interacts with the core network and the secondary base station to release the context of the user equipment, and interacts with the user equipment to release the connection between the user equipment and the master base station. Therefore, in the embodiment of the application, in the case where the user hanging phenomenon occurs, the release process of the user equipment is automatically triggered, so as to release the resources occupied by the user equipment in the source cell, thereby improving the NSA cell throughput and capacity, avoiding affecting the access of new users, and improving the real user rate. Figure 13 As can be seen from the above, in the embodiment of the application, in the case where it is detected that the resources occupied by the user equipment in the source cell are not successfully released, that is, in the case where the user hanging phenomenon occurs, the master base station interacts with the core network and the secondary base station to release the context of the user equipment, and interacts with the user equipment to release the connection between the user equipment and the master base station. Therefore, in the embodiment of the application, in the case where the user hanging phenomenon occurs, the release process of the user equipment is automatically triggered, so as to release the resources occupied by the user equipment in the source cell, thereby improving the NSA cell throughput and capacity, avoiding affecting the access of new users, and improving the real user rate.

[0148] In the NSA UE movement process, when the SN sends SgNBModificationRequired to the MN, the MN analyzes the cause value in the signaling as "radioNetwork: count-reaches-max-value", and then the MN sends SgNBModificationRefuse to the SN; when the MN sends SgNBModificationRequest to the SN, the SN analyzes the cause value in the signaling as "radioNetwork: count-reaches-max-value", and then the SN sends SgNBModificationRequestRefuse to the MN.

[0149] When the MN sends the SgNBModificationRefuse to the SN, or the SN sends the SgNBModificationRequestRefuse to the MN, the MN triggers the release procedure of the UE. That is, the MN sends the UEContextReleaseRequest to the core network, wherein the UEContextReleaseRequest carries the key field value valueCause:misc:om-intervention. The valueCause:misc:om-intervention is used to indicate that the release of the UE is triggered by the OM. After receiving the UEContextReleaseRequest, the core network triggers the release procedure of the UE.

[0150] Specifically, as shown in FIG. 14, the signaling of steps 1401 to 1408 is a normal secondary base station modification procedure, and steps 1409 to 1412 are an abnormal signaling procedure in which the modification request of the secondary base station is refused. When the MN receives the SgNBModificationRequestReject message sent by the SN, that is, the modification request of the SN is refused, the MN considers that the preparation of the change of the SN fails, and thus does not send the change execution message, but sends the SgNBModificationRefuse message to the SN. Figure 14

[0151] In the embodiment of the application, after the SN sends the SgNBModificationRequestReject message to the MN, or the SN receives the SgNBModificationRefuse message sent by the MN, the OM of the LTE side immediately triggers the release signaling of the user hung to the upper layer: UEContextReleaseRequest, wherein the key field value valueCause:misc:om-intervention is contained.

[0152] After receiving the UEContextReleaseRequest, the core network releases the context of the UE, and returns the UEContextReleaseCommand to the MN, so as to trigger the MN to send the UEContextRelease to the SN, so that the SN releases the context of the UE.

[0153] In addition, the MN also sends the UEContextReleaseComplete to the core network.

[0154] In addition, the MN also sends the rrcConnectionRelease to the UE, so as to release the RRC connection between the UE and the MN. ​

[0155] From the above, Figure 14 Steps 1413-1417 in the above, the normal UE context release process and the release of the RRC connection appear, the abnormal phenomenon of hanging users of the NSA cell can be avoided, so as to not affect the normal throughput of the cell, and further improve the cell capacity and improve the user perception.

[0156] In summary, the user equipment method provided by the embodiment of the application can solve the problem that the LTE cell and the Nr cell occasionally hang users simultaneously during the UE switching process or transmission switching. The following advantages exist:

[0157] (1) The abnormal process (i.e., the hanging user phenomenon) automatically triggers the release of the hung user. As long as the NSA cell has the hanging user problem, the process will automatically trigger the release process, so that the release is performed as soon as the problem occurs, and the problem of human judgment lag is avoided.

[0158] (2) It has obvious advantages for large networks and multiple users, can timely solve unnecessary resource occupation, improve the throughput of the NSA cell, so that the new user access does not exist the interference of the hanging user problem, and improves the user perception.

[0159] (3) The hanging user problem does not have to wait until the network is upgraded and the base station is reset to be solved, so that the network quality can be improved.

[0160] The user equipment release method provided by the embodiment of the application is introduced above, and the user equipment release device provided by the embodiment of the application will be introduced below with reference to the drawings.

[0161] Referring to Figure 15 The embodiment of the application also provides a user equipment release device, which comprises:

[0162] A first interaction module 1501 is configured to interact with a core network and a secondary base station to release the context of the user equipment in the case that the resource occupied by the user equipment in a source cell is not successfully released.

[0163] A second interaction module 1502 is configured to interact with the user equipment to release the connection between the user equipment and the primary base station.

[0164] Optionally, the first interaction module 1501 comprises:

[0165] A first sending sub-module is configured to send a user equipment context release request to the core network, wherein the user equipment context release request is used to instruct the core network to release the context of the user equipment.

[0166] A first receiving sub-module is configured to receive a user equipment context release instruction sent by the core network.

[0167] a second sending sub-module, configured to send a user equipment context release message to the secondary base station, wherein the user equipment context release message is used to instruct the secondary base station to release the context of the user equipment.

[0168] Optionally, the apparatus further comprises:

[0169] a release completion indication module, configured to send a user equipment context release completion message to the core network.

[0170] Optionally, the user equipment context release request carries target indication information, and the target indication information is used to instruct the OM to trigger the release of the user equipment.

[0171] Optionally, the second interaction module 1502 is specifically configured to:

[0172] send a radio resource control connection release message to the user equipment, wherein the radio resource control connection release message is used to instruct the user equipment to release the radio resource control connection between the user equipment and the primary base station.

[0173] Optionally, the apparatus further comprises:

[0174] a detection module, configured to detect whether the resource occupied by the user equipment in the source cell is successfully released;

[0175] Optionally, the detection module is specifically configured to:

[0176] in a case where the secondary base station modification request rejection message sent by the secondary base station is received, or in a case where the secondary base station modification rejection message sent by the primary base station to the secondary base station is received, it is determined that the resource occupied by the user equipment in the source cell is not successfully released;

[0177] in a case where the secondary base station modification request rejection message sent by the secondary base station is not received, and the secondary base station modification rejection message sent by the primary base station to the secondary base station is not received, it is determined that the resource occupied by the user equipment in the source cell is successfully released.

[0178] From the above, in the embodiment of the application, in the case that the user equipment occupies the resources of the source cell are not successfully released, that is, in the case that the user hanging phenomenon occurs, the master base station interacts with the core network and the secondary base station to release the context of the user equipment, and interacts with the user equipment to release the connection between the user equipment and the master base station. Therefore, in the embodiment of the application, in the case that the user hanging phenomenon occurs, the release process of the user equipment is automatically triggered, so as to release the resources of the user equipment in the source cell, thereby improving the NSA cell throughput and capacity, avoiding affecting the access of new users, and improving the real user rate.

[0179] Referring to Figure 16 The embodiment of the application further provides a user equipment release device applied to a core network, and the device comprises:

[0180] A third interaction module 1601 is configured to interact with the master base station to release the context of the user equipment in the case that the user equipment occupies the resources of the source cell are not successfully released.

[0181] In the embodiment of the application, in the case that the user equipment occupies the resources of the source cell are not successfully released, the master base station interacts with the core network and the secondary base station to make the core network and the secondary base station release the context of the user equipment. In addition, the core network also interacts with the user equipment to make the user equipment release the connection between the user equipment and the master base station.

[0182] Optionally, the third interaction module 1601 comprises:

[0183] A second receiving sub-module is configured to receive the user equipment context release request sent by the master base station.

[0184] A release sub-module is configured to release the context of the user equipment according to the user equipment context release request.

[0185] A third sending sub-module is configured to send a user equipment context release instruction to the master base station, wherein the user equipment context release instruction is used to instruct the master base station to send a user equipment context release message to the secondary base station, and the user equipment context release message is used to instruct the secondary base station to release the context of the user equipment.

[0186] Optionally, the device further comprises:

[0187] A release completion indication receiving module is configured to receive a user equipment context release completion message sent by the master base station.

[0188] Optionally, the user equipment context release request carries target indication information, and the target indication information is used to instruct to release the user equipment triggered by the OM.

[0189] As described above, in the embodiments of the present invention, when it is detected that the resources occupied by the user equipment in the source cell have not been successfully released, i.e., when a user is suspended, the primary base station interacts with the core network and the secondary base station to release the context of the user equipment and interacts with the user equipment to release the connection between the user equipment and the primary base station. Therefore, in the embodiments of the present invention, when a user is suspended, the user equipment release process is automatically triggered, thereby releasing the resources occupied by the user equipment in the source cell, thereby improving the throughput and capacity of the NSA cell, avoiding affecting the access of new users, and improving the actual user rate.

[0190] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0191] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0192] It should be noted that the apparatus provided in this embodiment of the invention can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0193] Embodiments of the present invention also provide a network device, such as... Figure 17 As shown, the network device includes a memory 1720, a transceiver 1710, and a processor 1700;

[0194] a memory 1720, configured to store a computer program;

[0195] a transceiver 1710, configured to receive and send data under control of the processor 1700.

[0196] In a first aspect, when the network device is applied to a master base station, the processor 1700 is configured to read the computer program in the memory 1720 and perform the following operations:

[0197] In the case where it is detected that the resources occupied by the user equipment in the source cell are not successfully released, interacting with the core network and the secondary base station to release the context of the user equipment;

[0198] Interacting with the user equipment to release the connection between the user equipment and the master base station.

[0199] Optionally, when the processor 1700 interacts with the core network and the secondary base station to release the context of the user equipment, it is specifically used for:

[0200] Controlling the transceiver 1710 to send a user equipment context release request to the core network, wherein the user equipment context release request is used to instruct the core network to release the context of the user equipment;

[0201] Controlling the transceiver 1710 to receive a user equipment context release instruction sent by the core network;

[0202] Controlling the transceiver 1710 to send a user equipment context release message to the secondary base station, wherein the user equipment context release message is used to instruct the secondary base station to release the context of the user equipment.

[0203] Optionally, the transceiver 1710 is further configured to:

[0204] Sending a user equipment context release completion message to the core network.

[0205] Optionally, the user equipment context release request carries target indication information, and the target indication information is used to instruct to release the user equipment triggered by the OM.

[0206] Optionally, when the processor 1700 interacts with the user equipment to release the connection between the user equipment and the master base station, it is specifically used for:

[0207] Controlling the transceiver 1710 to send a radio resource control connection release message to the user equipment, wherein the radio resource control connection release message is used to instruct the user equipment to release the radio resource control connection between the user equipment and the master base station.

[0208] Optionally, the processor 1700 is further configured to:

[0209] detecting whether the resource occupied by the user equipment in the source cell is successfully released;

[0210] The method further includes:

[0211] In a case where the secondary base station sends a secondary base station modification request rejection message or in a case where the primary base station sends a secondary base station modification rejection message to the secondary base station, it is determined that the resource occupied by the user equipment in the source cell is not successfully released.

[0212] In a case where the secondary base station does not send the secondary base station modification request rejection message and the primary base station does not send the secondary base station modification rejection message to the secondary base station, it is determined that the resource occupied by the user equipment in the source cell is successfully released.

[0213] In a first aspect, when the network device is applied to a core network, the processor 1700 is configured to read a computer program in the memory 1720 and perform the following operations:

[0214] In a case where the resource occupied by the user equipment in the source cell is not successfully released, interacting with the primary base station to release the context of the user equipment.

[0215] Optionally, when the processor 1700 interacts with the primary base station to release the context of the user equipment, the processor 1700 is specifically configured to:

[0216] control the transceiver 1710 to receive a user equipment context release request sent by the primary base station;

[0217] control the transceiver 1710 to release the context of the user equipment according to the user equipment context release request;

[0218] control the transceiver 1710 to send a user equipment context release instruction to the primary base station, where the user equipment context release instruction is used to instruct the primary base station to send a user equipment context release message to the secondary base station, and the user equipment context release message is used to instruct the secondary base station to release the context of the user equipment.

[0219] Optionally, the transceiver 1710 is further configured to:

[0220] receive a user equipment context release completion message sent by the primary base station.

[0221] Optionally, the user equipment context release request carries target indication information, and the target indication information is used to instruct to release the user equipment triggered by an OM.

[0222] In a case where the secondary base station sends a secondary base station modification request rejection message or in a case where the primary base station sends a secondary base station modification rejection message to the secondary base station, it is determined that the resource occupied by the user equipment in the source cell is not successfully released.Figure 17 In one embodiment, the bus architecture can include any number of interconnected buses and bridges, specifically, various circuitry of the one or more processors represented by the processor 1700 and the memory represented by the memory 1720 linked together by a bus architecture. The bus architecture can also link various other circuitry such as peripheral devices, voltage stabilizers, and power management circuitry, and the like, which are well known in the art, and thus, are not further described herein. The bus interface provides an interface. The transceiver 1710 can be a plurality of elements, i.e., including a transmitter and a receiver, providing a unit for communicating with various other apparatuses on transmission media, including wireless channels, wired channels, optical cables, and the like. The processor 1700 is responsible for managing the bus architecture and general processing, and the memory 1720 can store data used by the processor 1700 in performing operations.

[0223] The processor 1700 can be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD), and the processor 1700 can also adopt a multi-core architecture.

[0224] It should be noted that the above-mentioned device provided by the embodiments of the present application can realize all the method steps realized by the above-mentioned method embodiments, and achieve the same technical effects. Therefore, the same parts and beneficial effects of the method embodiments are not described in detail herein.

[0225] The embodiments of the present application also provide a processor readable storage medium, which stores a computer program, and the computer program is used for enabling the processor to execute the above-mentioned user equipment release method.

[0226] The processor readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to a magnetic storage (such as a floppy disk, a hard disk, a magnetic tape, a magneto-optical disk (MO), and the like), an optical storage (such as a CD, a DVD, a BD, a HVD, and the like), and a semiconductor storage (such as a ROM, an EPROM, an EEPROM, a non-volatile memory (NAND FLASH), a solid state disk (SSD)), and the like.

[0227] Those skilled in the art will appreciate that embodiments of the present application can be readily used as software, hardware, or a combination of software and hardware. In one

[0228] The present application is described in reference to the flow diagrams and / or block diagrams of the methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each block of the flow diagrams and / or block diagrams, and combinations of blocks in the flow diagrams and / or block diagrams, can be implemented by computer executable instructions. Figure 1 one or more functions specified in the flow diagram and / or block diagram block or blocks. Figure 1 means for performing one or more functions specified in the flow diagram and / or block diagram block or blocks.

[0229] These processor-executable instructions can also be loaded onto a computer or other programmable data processing devices, so that a series of operations are performed on the computer or other programmable data devices, to generate a computer-implemented process such that the instructions executed on the computer or other programmable devices provide steps for implementing the flow diagram and / or block diagram block or blocks. Figure 1 one or more functions specified in the flow diagram and / or block diagram block or blocks. Figure 1 means for performing one or more functions specified in the flow diagram and / or block diagram block or blocks.

[0230] These processor-executable instructions can also be loaded onto a computer or other programmable data processing devices, so that a series of operations are performed on the computer or other programmable data devices, to generate a computer-implemented process such that the instructions executed on the computer or other programmable devices provide steps for implementing the flow diagram and / or block diagram block or blocks. Figure 1 one or more functions specified in the flow diagram and / or block diagram block or blocks. Figure 1 means for performing one or more functions specified in the flow diagram and / or block diagram block or blocks.

[0231] Obviously, various modifications and changes are possible in the present application without departing from the scope and spirit of the application. Accordingly, it is intended that all possible modifications and changes that can be made be included within the scope of the application as defined by the following claims and their equivalents.

Claims

1. A user equipment release method, applied to a main base station, characterized in that, The method includes: Detect whether the resources occupied by the user equipment in the source cell have been successfully released; If the user equipment fails to release the resources it occupies in the source cell, it interacts with the core network and secondary base stations to release the context of the user equipment. Interact with the user equipment to release the connection between the user equipment and the main base station; The detection of whether the resources occupied by the user equipment in the source cell have been successfully released includes: If a secondary base station modification request rejection message is received from a secondary base station, or if a primary base station sends a secondary base station modification rejection message to the secondary base station, it is determined that the resources occupied by the user equipment in the source cell have not been successfully released.

2. The method according to claim 1, characterized in that, The interaction with the core network and secondary base stations to release the context of the user equipment includes: Send a user equipment context release request to the core network, wherein the user equipment context release request is used to instruct the core network to release the context of the user equipment; Receive the user equipment context release command sent by the core network; Send a user equipment context release message to the secondary base station, wherein the user equipment context release message is used to instruct the secondary base station to release the context of the user equipment.

3. The method according to claim 2, characterized in that, After sending the user equipment context release message to the secondary base station, the method further includes: Send a user equipment context release complete message to the core network.

4. The method according to claim 2, characterized in that, The user equipment context release request carries target indication information, which is used to indicate that the user equipment is released by the operation and maintenance module (OM).

5. The method according to claim 1, characterized in that, The step of interacting with the user equipment to release the connection between the user equipment and the main base station includes: A radio resource control connection release message is sent to the user equipment, wherein the radio resource control connection release message is used to instruct the user equipment to release the radio resource control connection with the main base station.

6. The method according to claim 1, characterized in that, Before interacting with the core network and secondary base stations and releasing the context of the user equipment, the method further includes: The step of detecting whether the resources occupied by the user equipment in the source cell have been successfully released also includes: If the primary base station does not receive a secondary base station modification request rejection message from the secondary base station and does not send a secondary base station modification rejection message to the secondary base station, it is determined that the resources occupied by the user equipment in the source cell have been successfully released.

7. A user equipment release method, applied to a core network, characterized in that, The method includes: If the resources occupied by the user equipment in the source cell are not successfully released, the user equipment interacts with the main base station to release the context of the user equipment. The main base station is used to detect whether the resources occupied by the user equipment in the source cell have been successfully released; The method of detecting whether the resources occupied by the user equipment in the source cell have been successfully released includes: determining that the resources occupied by the user equipment in the source cell have not been successfully released when a secondary base station modification request rejection message is received from a secondary base station, or when a primary base station sends a secondary base station modification rejection message to the secondary base station.

8. The method according to claim 7, characterized in that, The interaction with the main base station to release the context of the user equipment includes: Receive the user equipment context release request sent by the main base station; Release the context of the user equipment according to the user equipment context release request; Send a user equipment context release instruction to the primary base station, wherein the user equipment context release instruction is used to instruct the primary base station to send a user equipment context release message to the secondary base station, and the user equipment context release message is used to instruct the secondary base station to release the context of the user equipment.

9. The method according to claim 8, characterized in that, After sending the user equipment context release command to the main base station, the method further includes: Receive the user equipment context release complete message sent by the main base station.

10. The method according to claim 8, characterized in that, The user equipment context release request carries target indication information, which is used to indicate that the user equipment is released by the operation and maintenance module (OM).

11. A network device applied to a main base station, characterized in that, Includes memory, transceiver, and processor: The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor. A processor for performing the method according to any one of claims 1 to 6.

12. A network device, applied in a core network, characterized in that, Includes memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for executing the method according to any one of claims 7 to 10.

13. A user equipment release device, applied to a main base station, characterized in that, The device includes: The first interaction module is used to interact with the core network and the secondary base station to release the context of the user equipment when it is detected that the resources occupied by the user equipment in the source cell have not been successfully released. The second interaction module is used to interact with the user equipment and release the connection between the user equipment and the main base station.

14. A user equipment release device, applied in a core network, characterized in that, The device includes: The third interaction module is used to interact with the main base station to release the context of the user equipment if the resources occupied by the user equipment in the source cell are not successfully released.

15. A processor-readable storage medium, characterized in that, The processor-readable storage medium stores a computer program that causes the processor to perform the method according to any one of claims 1 to 6, or to perform the method according to any one of claims 7 to 10.

Images