WO2025260985A1 - 降低掉话率的方法、设备及芯片系统 - Google Patents

降低掉话率的方法、设备及芯片系统

Info

Publication number
WO2025260985A1
WO2025260985A1 PCT/CN2025/093188 CN2025093188W WO2025260985A1 WO 2025260985 A1 WO2025260985 A1 WO 2025260985A1 CN 2025093188 W CN2025093188 W CN 2025093188W WO 2025260985 A1 WO2025260985 A1 WO 2025260985A1
Authority
WO
WIPO (PCT)
Prior art keywords
release information
drb
logical channel
cell
rrc reconfiguration
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.)
Pending
Application number
PCT/CN2025/093188
Other languages
English (en)
French (fr)
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.)
Honor Device Co Ltd
Original Assignee
Honor Device Co 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 Honor Device Co Ltd filed Critical Honor Device Co Ltd
Publication of WO2025260985A1 publication Critical patent/WO2025260985A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • This application relates to the field of communication technology, and in particular to a method, device and chip system for reducing call drop rate.
  • RRC Radio Resource Control Reconfiguration
  • DRB data radio bearer
  • PDCP Packet Data Convergence Protocol
  • RB Radio Link Control
  • embodiments of this application provide a method, device, and chip system for reducing call drop rates, aiming to reduce call failures and improve user experience.
  • embodiments of this application provide a method for reducing call drop rate.
  • the method is applied to a terminal device and includes: during a first call in a first cell, receiving a first RRC reconfiguration message sent by a base station corresponding to the first cell; wherein the first RRC reconfiguration message includes first release information, the first release information including first data radio bearer (DRB) release information and first logical channel release information, the first DRB release information indicating the information of the first DRB to be released, and the first logical channel release information indicating the information of the first logical channel to be released; if the first DRB release information and the first logical channel release information do not match, releasing the first DRB according to the first DRB release information, releasing the first logical channel according to the first logical channel release information, and replying a first RRC reconfiguration complete message to the base station corresponding to the first cell.
  • DRB data radio bearer
  • the first DRB is the DRB corresponding to the Packet Data Convergence Protocol (PDCP) layer.
  • PDCP Packet Data Convergence Protocol
  • the first logical channel is the logical channel corresponding to the Radio Link Control (RLC) layer.
  • RLC Radio Link Control
  • the first DRB release information and the first logical channel release information do not match.
  • the first DRB release information indicating the first DRB to be released does not match the first logical channel to be released. That is, determining whether the first DRB release information and the first logical channel release information match involves, for example, determining whether the first DRB to be released and the first logical channel match based on the first DRB release information and the first logical channel release information.
  • the first RRC reconfiguration completion message is used to inform the base station corresponding to the first cell that the RRC reconfiguration based on the first RRC reconfiguration message has been completed.
  • the terminal device can be referred to as UE.
  • the UE can ignore the mismatch between the DRB and logical channel that need to be released, thus prompting the UE to complete the RRC reconfiguration.
  • the current first call will not be interrupted, and the UE can continue to camp on its current cell, such as NR CELL A, to conduct the first call, achieving the effects of reducing call failures, ensuring call quality, and improving user experience.
  • a strong verification switch is set in the modem processor of the terminal device; when the first DRB release information and the first logical channel release information do not match, the first DRB is released according to the first DRB release information, the first logical channel is released according to the first logical channel release information, and a first RRC reconfiguration completion message is replied to the base station corresponding to the first cell, including: when the strong verification switch is in the off state and the first DRB release information and the first logical channel release information do not match, the first DRB is released according to the first DRB release information, the first logical channel is released according to the first logical channel release information, and a first RRC reconfiguration completion message is replied to the base station corresponding to the first cell.
  • the strong verification switch can be understood as a software switch or software interface. This strong verification switch controls whether the UE performs strong verification on the information in the RRC reconfiguration message sent by the network side that instructs the UE to release the DRB and logical channel. That is, whether to strictly verify according to the provisions of the existing standard protocol, or to ignore mismatches.
  • the strong verification switch is, for example, a functional module implemented through software code.
  • the UE is configured not to perform strong verification on the release information in the RRC reconfiguration message sent by the network side. This way, if the DRB to be released and the logical channel do not match, the mismatch can be ignored, prompting the UE to complete the RRC reconfiguration and ensuring that the current call is not interrupted.
  • the method further includes: when the strong verification switch is in the on state and the first DRB release information and the first logical channel release information do not match, releasing the first DRB according to the first DRB release information, releasing the first logical channel according to the first logical channel release information, and triggering the RRC re-establishment process.
  • the UE when the strong verification switch is on, the UE follows the provisions of the existing standard protocol to perform strong verification on the release information in the RRC reconfiguration message sent by the network side. If the first DRB release information and the first logical channel release information do not match, the RRC re-establishment procedure is triggered, and the current call is interrupted.
  • the first release information is carried in the first field of the first RRC reconfiguration message, and the first field is the field specified in the standard protocol for carrying the first DRB release information and the first logical channel release information.
  • the first DRB release information and the first logical channel release information are carried in the first field, there is a strong binding relationship between the first DRB to be released indicated by the first DRB release information and the first logical channel to be released indicated by the first logical channel release information. For instance, the number of DRBs must be the same, and there must be a corresponding relationship set in the addition step.
  • the addition step is set so that DRB 4 corresponds to logical channel 3, DRB 5 corresponds to logical channel 4, and DRB 6 corresponds to logical channel 5, then when the first DRB release information indicates that DRB 4, DRB 5, and DRB 6 are to be released, the first logical channel information indicates that the first logical channel to be released must be logical channel 3, logical channel 4, and logical channel 5.
  • the first field is the CellGroupConfig field for cell group configuration.
  • the following steps are performed: if the first DRB release information and the first logical channel release information do not match, release the first DRB according to the first DRB release information, release the first logical channel according to the first logical channel release information, and reply to the base station corresponding to the first cell with the first RRC reconfiguration completion message.
  • the first release information is carried in the second field of the first RRC reconfiguration message.
  • the second field is different from the first field.
  • the first field is the field specified in the standard protocol for carrying the first DRB release information and the first logical channel release information.
  • the second field does not limit the strong binding relationship between the first DRB to be released indicated by the first DRB release information and the first logical channel to be released indicated by the first logical channel release information.
  • the second field is the masterCellGroup field.
  • the following steps are performed: if the first DRB release information and the first logical channel release information do not match, release the first DRB according to the first DRB release information, release the first logical channel according to the first logical channel release information, and reply to the base station corresponding to the first cell with the first RRC reconfiguration completion message.
  • the method further includes: if the first release information is carried in the first field and the first DRB release information and the first logical channel release information do not match, releasing the first DRB according to the first DRB release information, releasing the first logical channel according to the first logical channel release information, and triggering the RRC re-establishment process; wherein, after completing the RRC re-establishment process, if no message configuring the second DRB and the second logical channel is received from the base station corresponding to the cell accessed in the RRC re-establishment process within the first time period, the first call is released.
  • the first call in the first cell adopts an acknowledgment mode for data reception and transmission.
  • the method further includes: if the first DRB release information and the first logical channel release information do not match, it is recorded as an anomaly; if the cumulative number of anomalies is greater than the first anomaly threshold, the identification information of the first cell is added to the list of anomaly cells, the anomaly duration of the first cell is set to the second duration, and access to the first cell is prohibited during the third duration, wherein the second duration is greater than the third duration.
  • the UE by configuring the UE not to perform strong verification on the release information in the RRC reconfiguration message sent by the network side, if the DRB to be released and the logical channel do not match, the mismatch is ignored, prompting the UE to complete the RRC reconfiguration. Furthermore, the number of anomalies caused by the mismatch between the DRB to be released and the logical channel is recorded, and an abnormal cell penalty mechanism is applied to that cell to prevent it from re-entering the cell within a short period afterward. This ensures that the current call is not interrupted and reduces the probability of the subsequent UE camping on that cell, allowing calls to occur in normal cells as much as possible, further reducing call failures, ensuring call quality, and improving user experience.
  • the method further includes: during a second call in the first cell within a second duration, receiving a second RRC reconfiguration message sent by the base station corresponding to the first cell; wherein the second RRC reconfiguration message includes second release information, the second release information includes second DRB release information and second logical channel release information, the second DRB release information indicating the information of the second DRB to be released, and the second logical channel release information indicating the information of the second logical channel to be released; if the second DRB release information and the second logical channel release information do not match, releasing the second DRB according to the second DRB release information, releasing the second logical channel according to the second logical channel release information, replying to the base station corresponding to the first cell with a second RRC reconfiguration completion message, and accumulating one abnormal occurrence; if the accumulated number of abnormal occurrences is greater than a second abnormal threshold, prohibiting access to the first cell within a fourth duration, the second abnormal threshold being greater than a
  • the method further includes: within the fourth time period, conducting a third call through the base station corresponding to the second cell, wherein the second cell is not a cell in the list of abnormal cells.
  • the first DRB release information and the first logical channel release information are mismatched.
  • the first DRB release information indicates that the first DRB to be released is DRB 4, DRB 5 and DRB 6, and the first logical channel release information indicates that the first logical channel to be released is logical channel 3, then it is determined that the first DRB release information and the first logical channel release information do not match.
  • the first DRB release information indicating that the first DRB to be released and the first logical channel release information indicating that the first logical channel to be released do not correspond, the first DRB release information and the first logical channel release information are mismatched.
  • the terminal device includes: a memory and a processor, coupled together; the memory stores program instructions, which, when executed by the processor, cause the terminal device to perform the method of the first aspect or any possible implementation thereof.
  • embodiments of this application provide a computer program including instructions for performing the method in the first aspect or any possible implementation thereof.
  • the processor includes a modem processor.
  • the processor provides instructions for supporting the terminal device in implementing the method of the first aspect or any possible implementation thereof, specifically including:
  • the fifth aspect and any implementation thereof correspond to the first aspect and any implementation thereof, respectively.
  • the technical effects of the fifth aspect and any implementation thereof are similar to those of the first aspect and any implementation thereof, and will not be repeated here.
  • Figure 2 is a schematic diagram of a voice call scenario provided by an exemplary embodiment of this application.
  • Figure 3 is a schematic diagram of the interaction between the UE and the gNB on the network side in a scenario where RRC reconfiguration is successful, as exemplarily provided in an embodiment of this application.
  • Figure 5 is a schematic diagram illustrating an example of an RRC reconfiguration message release bearer anomaly that causes the current call to drop, provided by an embodiment of this application.
  • Figure 7 is a schematic diagram of the release information in an RRC reconfiguration message that instructs the UE to release the DRB and logical channel, provided by an exemplary embodiment of this application.
  • Figure 9 is a schematic diagram of another method for reducing call drop rate provided by an exemplary embodiment of this application.
  • Figure 10 is a schematic diagram of another method for reducing call drop rate provided by an exemplary embodiment of this application.
  • Figure 11 is a schematic diagram of the hardware structure of a terminal device provided by an exemplary embodiment of this application.
  • Figure 12 illustrates the relationship between the software structure and hardware devices of a terminal device provided by an embodiment of this application, as well as its interaction with a gNB.
  • a and/or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.
  • first,” “second,” “third,” “fourth,” etc. used in the specification and claims of this application are used to distinguish different objects, not to describe a specific order of objects.
  • first target object and second target object are used to distinguish different target objects, not to describe a specific order of target objects.
  • the terms "exemplary” or “for example” are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as “exemplary” or “for example” in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms “exemplary” or “for example” is intended to present the relevant concepts in a specific manner.
  • multiple means two or more.
  • multiple processing units means two or more processing units; multiple systems means two or more systems.
  • the technical solution provided in this application addresses the RRC reconfiguration process between the network side and the terminal devices (calling party's terminal device and/or called party's terminal device) during a call between the calling party and the called party.
  • the network architecture targeted by the technical solution provided in this application and the voice call scenario implemented based on this communication architecture, will first be described with reference to the accompanying drawings.
  • the network architecture may include terminal devices, LTE network devices, NR network devices, a core network, and IMS or the Internet.
  • the terminal equipment also known as user equipment (UE), user terminal, mobile station (MS), or mobile terminal (MT), may be referred to as such.
  • the terminal equipment may be a mobile phone, a wearable device (such as a smartwatch), etc.
  • LTE Long Term Evolution
  • 4G 4th generation mobile communication technology
  • E-UTRAN Evolved UMTS Terrestrial Radio Access Network
  • NR New Radio
  • NG-RAN Next Generation Radio Access Network
  • NG RAN Next Generation Radio Access Network
  • NG RAN Next Generation Radio Access Network
  • NR has the same meaning as NG-RAN (or NG RAN), both referring to the access network portion of the 5G network.
  • LTE and NR are access networks.
  • the access network is responsible for using some wired or wireless connection and communication technology to connect a large number of end users, level by level, to the core network (also known as the backbone network), thus achieving network connectivity.
  • the access network is the edge of the entire network, that is, the part closest to the user, often referred to as the "last mile.”
  • network equipment refers to devices on the network side used to communicate with terminal devices.
  • the network equipment may be a base station. That is, in some embodiments of this application, the network equipment for LTE is, for example, a 4G base station; the network equipment for NR is, for example, a 5G base station, such as a gNB (the next generation Node B, gNodeB).
  • gNB the next generation Node B, gNodeB
  • the terminal device can access LTE via a 4G base station.
  • the terminal device can access NR via a gNB.
  • the core network's main functions are to provide user connections, manage users, and carry out service provision, serving as the interface to external networks.
  • User connection establishment includes functions such as Mobility Management (MM), Call Management (CM), switching/routing, and recording notifications (combined with intelligent network services to establish connections to intelligent network peripheral devices).
  • MM Mobility Management
  • CM Call Management
  • switching/routing switching/routing
  • recording notifications combined with intelligent network services to establish connections to intelligent network peripheral devices.
  • the core network of a 4G network is an Evolved Packet Core (EPC) network.
  • EPC Evolved Packet Core
  • the core network of a 5G network is the 5G Core (which can be abbreviated as 5GC).
  • 5GC uses general-purpose network function virtualization equipment to replace the dedicated communication equipment of 4G networks.
  • the core network in the network architecture shown in Figure 1 can be obtained by merging the EPC network and the 5GC. That is, the core network in this network architecture can include network elements from both the EPC network and the 5GC.
  • the core network in this network architecture can include Access and Mobility Management Function (AMF) network elements, Mobility Management Entity (MME) network elements, Serving Gateway (SGW) network elements, Packet Data Network Gateway (PGW) network elements, Session Management Function (SMF) network elements, User Plane Function (UPF) network elements, Unified Data Management (UDM) network elements, and Home Subscriber Server (HSS) network elements, etc.
  • AMF Access and Mobility Management Function
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • PGW Packet Data Network Gateway
  • SGW Packet Data Network Gateway
  • SGW Packet Data Network Gateway
  • SGW Packet Data Network Gateway
  • SGW Packet Data Network Gateway
  • SGW Packet Data Network Gateway
  • SGW Packet Data Network Gateway
  • SGW Packe
  • the core network in this network architecture includes converged network elements, which are converged network elements obtained from network elements in the EPC network and network elements in the 5GC network, such as SMF+PGW-C, UPF+PGW-U, or UDM+HSS, etc.
  • PGW-C is the control plane node of the PGW network element
  • PGW-U is the user plane node of the PGW network element.
  • the core network in the network architecture shown in Figure 1 may include a Proxy Session Border Control (PSBC) network element.
  • PSBC Proxy Session Border Control
  • the PSBC can be understood as a combined network element integrating Session Border Control (SBC), Proxy Call Session Control Function (P-CSCF), Access Transfer Control Function (ATCF), and Access Transfer Gateway (ATGW).
  • SBC Session Border Control
  • P-CSCF Proxy Call Session Control Function
  • ATCF Access Transfer Control Function
  • ATGW Access Transfer Gateway
  • the PSBC network element When the PSBC network element acts as an SBC network element, it connects the IMS core network/softswitch network with the external user access area, enabling IMS/softswitch users to access services, achieve interoperability of user services in different network environments, ensure the security of IMS/softswitch networks, and support functions such as QoS management, CAC traffic control, media management, and CDR media call detail records.
  • the P-CSCF serves as the unified entry point for the IMS visitor domain control plane. It proxies and forwards Session Initialization Protocol (SIP) messages from the visitor domain access network, such as registration, session, and presence messages, to its home domain S-CSCF or I-CSCF.
  • SIP Session Initialization Protocol
  • the PSBC network element When the PSBC network element is used as a built-in ATCF/ATGW network element, by configuring the ATCF/ATGW functional entity between the P-CSCF and I-CSCF/S-CSCF, for devices that may undergo Enhanced Single Radio Call Continuity (eSRVCC) handover, the media stream is anchored to the ATGW. This way, when an sSRVCC handover occurs subsequently, only the media information on the ATGW needs to be updated, without updating the media information on the terminal device, thus shortening the overall eSRVCC handover time.
  • eSRVCC Enhanced Single Radio Call Continuity
  • the various network elements in the core network can also be referred to as functional entities. That is, the core network can be a network element implemented on dedicated hardware, a software instance running on dedicated hardware, or an instance of virtualized functionality on an appropriate platform.
  • the names of all network elements in the embodiments of this application are merely examples. In future communications, such as 6G networks, these network elements may be called by other names. Alternatively, in future communications, such as 6G networks, these network elements may be replaced by other entities or devices with the same function, and this application does not limit them in this regard. This is a unified explanation here and will not be repeated later.
  • the various network elements in the embodiments of this application may be communication devices, or chips or chip systems that can be used in the communication devices, and this application does not limit them in this regard.
  • the core network in the network architecture shown in Figure 1 may also include other devices, network elements, network entities, or network subsystems, such as Policy Control Function (PCF) network elements, and this application does not impose any restrictions on this.
  • PCF Policy Control Function
  • IMS IP Multimedia Subsystem
  • IP Internet Protocol
  • IMS IP Multimedia Subsystem
  • IP Internet Protocol
  • IMS enables secure and reliable multimedia communication between different devices on different networks.
  • the IMS architecture provides a unified infrastructure and common mechanisms for controlling, operating, routing, and managing sessions, as well as implementing authentication, authorization, and accounting controls.
  • the IMS specification includes widely used recommendations from the Internet Engineering Task Force (IETF), such as the Session Initialization Protocol (SIP) for session control signaling.
  • IETF Internet Engineering Task Force
  • SIP Session Initialization Protocol
  • the Internet also known as the international network, refers to a vast network of interconnected networks linked by a set of common protocols, forming a logically single, enormous international network. From a network communication perspective, the Internet is a data communication network that connects computer networks of various countries, regions, and organizations around the world using Transmission Control Protocol (TCP) and Internet Protocol (IP).
  • TCP Transmission Control Protocol
  • IP Internet Protocol
  • network architecture shown in Figure 1 is not limited to the devices and networks shown in the figure, but may also include other devices not shown in the figure. This application will not provide examples of these devices.
  • the first terminal can transmit voice data with the second terminal, i.e., conduct a call, through a first network device, IMS, and a second network device.
  • the first network device is the network device corresponding to the cell where the first terminal is currently registered
  • the second network device is the network device corresponding to the cell where the second terminal is currently registered.
  • the first network device and the second network device may be the same network device.
  • the first terminal may be the party initiating a voice call to request a voice call with the second terminal.
  • the second terminal may be the party initiating a voice call to request a voice call with the first terminal.
  • the first terminal and the second terminal may be 5G mobile phones, that is, smartphones using the fifth generation communication system.
  • the first network device and the second network device can be 4G base stations.
  • the first network device and the second network device can be gNBs.
  • the first terminal and the second terminal can directly connect to the 5G network without relying on the 4G network, thereby obtaining faster network speeds and lower latency, and improving the call experience.
  • RRC reconfiguration has been introduced to modify the RRC connection between the UE and the base station. Examples include establishing (adding)/modifying/releasing DRBs and logical channels/RBs, performing cell handover (base station handover), and setting/modifying/releasing measurement reports.
  • RRC reconfiguration can also be implemented in 4G networks.
  • RRC reconfiguration is referred to as RRC connection reconfiguration.
  • this application embodiment uses RRC reconfiguration performed in a 5G network as an example for illustration.
  • RRC reconfiguration is initiated by the network side (5G base station, such as gNB). That is, the gNB actively sends an RRC reconfiguration message to the corresponding UE, as shown in "RRC Reconfiguration" in Figure 3.
  • 5G base station such as gNB
  • the RRC reconfiguration message may carry information instructing the UE to add/modify/release DRBs and logical channels/RBs.
  • the RRC reconfiguration message may also carry measurement configurations that indicate UE measurement and reporting operations, SRS resource configurations for antenna switching modes, and encryption/decryption algorithm configurations for data packets exchanged with the base station, etc., which will not be listed here.
  • the UE After receiving an RRC reconfiguration message from the gNB, the UE needs to verify the content of the RRC reconfiguration message. If the verification is successful, the UE will complete the RRC reconfiguration according to the RRC reconfiguration message, and after the RRC reconfiguration is completed, it will reply to the gNB with an RRC reconfiguration completion message, as shown in Figure 3, "RRC Reconfiguration Complete,” to inform the gNB that the RRC reconfiguration based on the RRC reconfiguration message has been completed. Conversely, if the verification fails, the UE will not reply to the gNB with "RRC Reconfiguration Complete,” but will instead trigger the RRC re-establishment procedure, as shown in Figure 4, "RRC Connection re-establishment.”
  • the UE will first execute a Radio Link Failure (RLF) procedure, such as releasing the connection with the gNB of the current cell. Then, the UE will reselect a cell and initiate an RRC re-establishment procedure with the gNB corresponding to the newly selected cell, such as sending an RRC re-establishment request (carrying the reason value of the RRC reconfiguration failure, such as Reconfiguration failure) to the newly selected gNB.
  • RLF Radio Link Failure
  • the reselected gNB will reply to the UE with a Radio Resource Control Connection Setup (RRC Connection Setup) message indicating the radio bearer and serving cell group, so that the UE can establish an RRC connection with the reselected gNB.
  • RRC Connection Setup Radio Resource Control Connection Setup
  • the UE can choose to camp on the original cell (the cell it camped on before triggering the RRC re-establishment procedure) or a new cell. That is, the gNB reselected by the UE can be the gNB that was accessed before triggering the RRC re-establishment procedure (hereinafter referred to as: the original base station), another gNB in the original cell, or a gNB from another cell.
  • the original base station the gNB that was accessed before triggering the RRC re-establishment procedure
  • another gNB in the original cell or a gNB from another cell.
  • the embodiments of this application take the RRC re-establishment phase, where the UE selects the original base station to camp on, as an example.
  • the reselected gNB is the original base station that has just disconnected, the original base station will consider the current RRC connection to be abnormal after completing the RRC Connection re-establishment with the UE.
  • the reselected gNB i.e., the original base station, will send a BYE message to the UE to end the current call, thereby terminating the current call.
  • RRC reconfiguration message sent by the gNB which indicates the addition/release of DRB (DRB in all embodiments of this application refers to the DRB corresponding to the PDCP layer) and logical channel/RB (hereinafter uniformly described as: logical channel; in addition, the logical channel in all embodiments of this application refers to the logical channel corresponding to the RLC layer).
  • DRB in all embodiments of this application refers to the DRB corresponding to the PDCP layer
  • logical channel/RB hereinafter uniformly described as: logical channel; in addition, the logical channel in all embodiments of this application refers to the logical channel corresponding to the RLC layer).
  • the RRC reconfiguration process based on the information indicating the addition/release of the DRB in the RRC reconfiguration message sent by the gNB, specifically includes:
  • the RRC reconfiguration message 1 received by the UE is sent by the gNB corresponding to NR CELL A.
  • the gNB that sends RRC reconfiguration message 1 is the gNB in NR CELL A that establishes an RRC connection with the UE and conducts a call.
  • the received RRC reconfiguration message may include (or carry) addition information for instructing the UE to add DRB and logical channel, and/or modification information for instructing the UE to modify DRB and logical channel, and/or release information for instructing the UE to release DRB and logical channel.
  • the RRC reconfiguration message 1 received by the UE from NR CELL A is an example of an RRC reconfiguration message carrying information for instructing the UE to add DRB and logical channels.
  • the UE verifies the addition information carried in RRC reconfiguration message 1, and if the verification is successful, adds DRB and logical channel according to the addition information.
  • the addition information carried by RRC reconfiguration message 1 for instructing the UE to add DRB and logical channels includes DRB addition information and logical channel addition information.
  • the addition information in the RRC reconfiguration message instructing the UE to add a DRB and a logical channel may include the identity information (such as an identifier) of each DRB to be added, the identity information (such as an identifier) of each logical channel to be added, and the correspondence between each DRB to be added and the logical channel.
  • the added information can be configured in a field specified in the RRC reconfiguration message, such as rlc-BearerToAddModList, and corresponding DRBs and logical channels can appear in pairs.
  • the DRBs to be added include three DRBs with identity information 4, 5, and 6, and the logical channels to be added include three logical channels with identity information 3, 4, and 5, and DRB 4 corresponds to logical channel 3, DRB 5 corresponds to logical channel 4, and DRB 6 corresponds to logical channel 5,
  • the added information configured under the rlc-BearerToAddModList field of the RRC reconfiguration message can be as shown in Figure 6.
  • the addition information carried in RRC reconfiguration message 1 indicates that the number of DRBs to be added is the same as the number of logical channels to be added, and each DRB corresponds to a separate logical channel. Therefore, the UE successfully verifies the addition information and can add the corresponding DRBs and logical channels according to the addition information shown in Figure 6.
  • the interaction logic between the UE and gNB indicates that the UE will reply to NR CELL A with RRC reconfiguration completion message 1, that is, execute step S103.
  • the UE's verification of RRC reconfiguration message 1 will fail. Based on the interaction logic between the UE and gNB in the case of RRC reconfiguration failure shown in Figure 4, the UE will trigger the RRC re-establishment procedure.
  • the addition information in the RRC reconfiguration message instructing the UE to add a DRB and a logical channel appears in pairs, as shown in Figure 6. Therefore, the verification of the addition information usually does not fail. That is, in the scenario where the RRC reconfiguration message is used to instruct the UE to add a DRB and a logical channel, after the UE receives the reconfiguration message 1 sent by NR CELL A, it will normally execute steps S102 and S103.
  • the UE replies with RRC reconfiguration complete message 1 to the gNB that sent RRC reconfiguration message 1 in NR CELL A.
  • RRC reconfiguration completion message 1 is used to inform the gNB that issued RRC reconfiguration message 1 has been completed based on RRC reconfiguration message 1 (adding DRB and logical channel).
  • calls made by the UE camped on NR CELL A can continue normally until either the calling UE or the called UE triggers a hang-up operation, such as pressing the hang-up button in the UE user interface.
  • a hang-up operation such as pressing the hang-up button in the UE user interface.
  • the embodiment of this application takes the case where the UE continues to make calls while camped on NR CELL A after the RRC reconfiguration based on RRC reconfiguration message 1 is completed. That is, the UE continues to make calls while camped on NR CELL A.
  • the network side (the base station of the currently camped cell) will resend RRC reconfiguration messages to the UE to re-add new DRBs and logical channels, and/or modify previously added DRBs and logical channels, and/or release previously added DRBs and logical channels, thereby ensuring the quality of the current call.
  • the embodiments of this application take the following example: during the process of a UE camped on NR CELL A and continuing a call, the NR CELL A wireless network resources change, and the RRC reconfiguration message resent by NR CELL A to the UE is an RRC reconfiguration message 2 carrying information indicating that the UE releases the previously added DRB and logical channel.
  • the UE verifies the release information carried in RRC reconfiguration message 2 to determine the DRB to be released and the logical channel release match.
  • the release information carried in RRC reconfiguration message 2 to instruct the UE to release DRBs and logical channels includes DRB release information and logical channel release information.
  • the DRB release information may include the identity information (such as an identifier) of each DRB to be released
  • the logical channel release information may include the identity information (such as an identifier) of each logical channel to be released.
  • the number of DRBs to be released indicated by the DRB release information carried in RRC reconfiguration message 2 and the number of logical channels to be released indicated by the logical channel release information must be the same.
  • the DRBs and logical channels to be released must satisfy the correspondence configured when adding the stage for the RRC reconfiguration to succeed. For example, if the correspondence between DRBs and logical channels configured when adding the stage is shown in Figure 6, and the DRBs to be released in the release stage are DRB 4, DRB 5, and DRB 6, then the logical channel release information must indicate that the logical channels to be released are logical channel 3, logical channel 4, and logical channel 5. In this case, the DRBs and logical channels to be released match. Otherwise, the DRBs and logical channels to be released do not match.
  • release information can be configured in fields specified in the RRC reconfiguration message, such as DRB release information configured in the drb-ToReleaseList field, and logical channel release information configured in the rlc-BearerToReleaseList field.
  • the DRB release information configured in the drb-ToReleaseList field indicates the release of DRB 5, DRB 4 and DRB 6, and the logical channel release information configured in the rlc-BearerToReleaseList field indicates the release of logical channel 3, logical channel 4 and logical channel 5.
  • the UE successfully verifies the RRC reconfiguration message 2.
  • the UE can release the DRB and logical channel according to the release information and reply to the NR CELL A with the RRC reconfiguration completion message 2, that is, execute step S106.
  • the DRB release information configured in the drb-ToReleaseList field indicates the release of DRB 5, DRB 4 and DRB 6, while the logical channel release information configured in the rlc-BearerToReleaseList field only indicates the release of logical channel 3.
  • the UE fails to verify the RRC reconfiguration message 2.
  • the UE can release the DRB and logical channel according to the release information and trigger the RRC re-establishment process, that is, execute step S107.
  • the UE releases the DRB and logical channel according to the release information carried in the RRC reconfiguration message 2, and replies to NR CELL A with the RRC reconfiguration completion message 2.
  • the UE replies with RRC reconfiguration complete message 2 to the gNB that sends RRC reconfiguration message 2 in NR CELL A.
  • RRC reconfiguration completion message 2 is used to inform the gNB that issued RRC reconfiguration message 2 has been completed based on RRC reconfiguration message 2 (release of DRB and logical channel).
  • the UE releases the DRB and logical channel according to the release information carried in RRC reconfiguration message 2, and triggers the RRC re-establishment procedure.
  • RRC reconfiguration fails, it triggers an RRC re-establishment process.
  • the original base station After the RRC connection between the UE and the network is re-established, the original base station will consider the RRC connection with the UE to be abnormal. In this situation, the network side, i.e., the original base station, will not send information to configure DRB and logical channels, such as not resending the RRC reconfiguration message instructing the UE to add/modify/release DRB and logical channels. Consequently, the UE does not receive the RRC reconfiguration message sent by the network side and therefore cannot restore bearer functionality, such as being unable to configure the DRB and logical channels required for the call.
  • the UE Because the bearer between the UE and the network side has not been restored, the UE is unable to send voice data packets generated during the call to the network side, nor can it receive voice data packets generated during the call from the network side; that is, there is no sound in the current call. According to the provisions of the existing standard protocol, if there is no sound within the first duration (T1 duration), a timeout will be triggered and the call will be dropped, thereby interrupting the call in NR CELL A.
  • the first duration is, for example, 20 seconds (s).
  • a timeout-triggered call drop occurs, such as when the gNB of NR CELL A sends a BYE message to the UE to release the current call.
  • a call ending in this situation can be understood as an abnormal termination scenario or an interruption scenario.
  • some embodiments of this application provide a method to reduce call drop rate, which aims to enable the UE to complete RRC reconfiguration when the network side has not fully configured the DRB and logical channel to be released in accordance with the existing standard protocol, so that the current call will not be interrupted, reduce call failures, and improve user experience.
  • the premise is that the DRB and logical channel to be released have been successfully added in accordance with the provisions of the existing standard protocol, with a one-to-one strong binding relationship.
  • DRBs and logical channels have been successfully added in accordance with existing standard protocols, with a one-to-one strong binding relationship, such as the number and relationship of DRBs and logical channels shown in Figure 6. That is, before receiving the RRC reconfiguration message instructing the UE to release DRBs and logical channels, the UE has already added DRB 4, DRB 5, and DRB 6, as well as logical channels 3, 4, and 5, and DRB 4 corresponds one-to-one with logical channel 3, DRB 5 corresponds one-to-one with logical channel 4, and DRB 6 corresponds one-to-one with logical channel 5.
  • the UE can be either the calling party UE or the called party UE.
  • the cell where the UE camps is taken as a 5G cell.
  • the method for reducing call drop rate specifically includes:
  • the first RRC reconfiguration message received by the UE is sent by the gNB corresponding to NR CELL A.
  • the gNB that sends the first RRC reconfiguration message is the gNB in NR CELL A that establishes an RRC connection with the UE and conducts a call.
  • the first RRC reconfiguration message carries first release information.
  • the first release information includes first DRB release information instructing the UE to release the DRB corresponding to the PDCP layer, and first logical channel release information instructing the UE to release the DRB corresponding to the RLC layer.
  • the first DRB release information instructs the UE to release DRB 4, DRB 5, and DRB 6.
  • the first logical channel release information instructs the UE to release logical channel 3.
  • the UE determines that the DRB and logical channel to be released do not match according to the first release information in the first RRC reconfiguration message, it releases the DRB and logical channel according to the first release information and replies to NR CELL A with the first RRC reconfiguration completion message.
  • the first release information such as the first DRB release information and the first logical channel release information
  • the first release information can be carried in the first field of the first RRC reconfiguration message, or it can be carried in the second field of the first RRC reconfiguration message.
  • the first field contains release information that must be configured therein, such as a field where the first DRB release information and the first logical channel information are strongly bound together.
  • DRB 4 is configured to correspond one-to-one with logical channel 3, DRB 5 with logical channel 4, and DRB 6 with logical channel 5, then according to the existing standard protocol's provisions for the first field, if the first DRB release information configured in the first field instructs the UE to release DRB 4, DRB 5, and DRB 6, then the first logical channel release information configured in the first field must instruct the UE to release logical channels 3, 4, and 5 to meet the requirements.
  • the first field is, for instance, the CellGroupConfig field. That is, the first DRB release information configured in the drb-ToReleaseList field and the first logical channel release information configured in the rlc-BearerToReleaseList field are both carried in the CellGroupConfig field.
  • the network side may not fully comply with the existing standard protocol in configuring the first release information carried in the CellGroupConfig field. That is, the number of DRBs to be released by the UE according to the first DRB release information and the number of logical channels to be released according to the first logical channel release information may not be the same.
  • the DRBs to be released are DRB 4, DRB 5, and DRB 6, but the logical channel to be released is only logical channel 3, which corresponds to DRB 4, this results in a mismatch between the DRBs to be released and the logical channels.
  • DRBs 4, 5, and 6 are unusable after being released according to the first DRB release information, logical channels 3, 4, and 5, corresponding to DRBs 4, 5, and 6 respectively, also become inaccessible. Therefore, in some embodiments of this application, if the UE determines that the DRBs to be released and the logical channels do not match based on the first RRC release information in the first RRC reconfiguration message, it can ignore this mismatch, i.e., it does not perform strong verification on the first release information in the first RRC reconfiguration message (not following the existing standard protocol's provisions for the first release information configured in the CellGroupConfig field), thereby prompting the UE to complete the RRC reconfiguration based on the first RRC reconfiguration message. In this way, the UE can reply to NR CELL A with a first RRC reconfiguration completion message, thus informing NR CELL A that the RRC reconfiguration based on the first RRC reconfiguration message has been completed.
  • the UE may not ignore the mismatch. That is, it may perform strong verification on the first release information in the first RRC reconfiguration message (following the existing standard protocol's provisions for the first release information configured in the CellGroupConfig field), thereby triggering the RRC re-establishment process.
  • the UE can perform subsequent processing according to the method for reducing call drop rate provided in the embodiment shown in Figure 10.
  • the description section of the embodiment shown in Figure 10 please refer to the description section of the embodiment shown in Figure 10, which will not be repeated here.
  • the second field is different from the first field.
  • it may contain release information that is not required to be configured therein, such as a field where the first DRB release information and the first logical channel information are strongly bound together. That is, in the scenario where the first release information is carried in the second field, the first DRB release information and the first logical channel release information configured in the second field are not strongly bound together.
  • the second field could be the masterCellGroup field. That is, the first DRB release information configured in the drb-ToReleaseList field and the first logical channel release information configured in the rlc-BearerToReleaseList field are both carried in the masterCellGroup field.
  • the masterCellGroup field can carry information such as cellGroupId, rlc-BearerToAddModList, mac-CellGroupConfig, and physicalCellGroupConfig.
  • the UE when the first release information is carried in the masterCellGroup field, the UE does not need to perform strong verification on the first release information in the first RRC reconfiguration message. Thus, regardless of whether the DRB and logical channel to be released match, the UE can complete the RRC reconfiguration based on the first RRC reconfiguration message and then reply to NR CELL A with a first RRC reconfiguration completion message to inform NR CELL A that the RRC reconfiguration based on the first RRC reconfiguration message has been completed.
  • the UE determines, based on the first release information in the first RRC reconfiguration message, that the DRB to be released and the logical channel do not match, it can release the DRB according to the first DRB release information and release the first logical channel according to the first logical channel release information. That is, the release processing of the DRB and the logical channel is performed according to the first DRB release information and the first logical channel information carried in the received first RRC reconfiguration message.
  • the UE determines that the DRB to be released and the logical channel do not match based on the first release information in the first RRC reconfiguration message, it can release the DRB according to the first DRB release information and release the first logical channel corresponding to the DRB to be released as indicated by the first DRB release information according to the correspondence between the DRB and the logical channel set in the addition process. This reduces the UE's power consumption and the occupation of logical channel resources, making it easier for the network side to reallocate these logical channels.
  • the UE by configuring the UE not to perform strong verification on the release information in the RRC reconfiguration message sent by the network side, such as the first release information in the first RRC reconfiguration message described in the above embodiment, if the DRB and logical channel to be released do not match, the mismatch is ignored, prompting the UE to complete the RRC reconfiguration. In this way, the current first call will not be interrupted, and the UE can continue to camp on its current cell, such as NR CELL A, to conduct the first call, achieving the effects of reducing call failures, ensuring call quality, and improving user experience.
  • its current cell such as NR CELL A
  • the method for reducing call drop rate specifically includes:
  • the UE determines that the DRB and logical channel to be released do not match according to the first release information in the first RRC reconfiguration message, it releases the DRB and logical channel according to the first release information and replies to NR CELL A with the first RRC reconfiguration completion message.
  • Steps S301 and S302 in this embodiment are similar to steps S201 and S202 in the embodiment shown in FIG8.
  • steps S201 and S202 please refer to the description of steps S201 and S202, which will not be repeated here.
  • the UE records the number of abnormalities if it determines that the DRB to be released and the logical channel do not match based on the first release information in the first RRC reconfiguration message.
  • steps S302 and S303 can be executed in any order. That is, when the UE determines that the first DRB release information and the first logical channel release information carried in the first RRC reconfiguration message do not match, it can simultaneously trigger the release of the DRB and the logical channel according to the first release information, reply to the NR CELL A with the first RRC reconfiguration completion message, and record the number of abnormalities.
  • the UE adds the identification information of NR CELL A to the list of abnormal cells, sets the abnormal duration of NR CELL A to the second duration (T2 duration), and sets the access to NR CELL A to be prohibited during the third duration (T3 duration).
  • the abnormal cell list is a list maintained locally by the UE. In subsequent use cases, the UE can determine whether to conduct voice calls in the currently camped cell by checking if the cell is recorded in the abnormal cell list.
  • K1 can be set to 1. This way, when a mismatch between the DRB to be released and the logical channel first occurs, the cell experiencing the problem can be marked in a timely manner.
  • T2 can be greater than T3.
  • T2 is, for instance, 2 days.
  • the identifier of NR CELL A is recorded in the list of abnormal cells, and after 2 days, the identifier of NR CELL A can be removed from the list of abnormal cells.
  • T3 is 5 minutes.
  • the UE is prohibited from accessing NR CELL A for 5 minutes. That is, the prohibition period set for an abnormal cell takes effect after the UE ends its call in that cell.
  • the UE after the UE completes step S302 and normally ends the first call, it can select a normal cell, such as a cell not recorded in the abnormal cell list, to camp on, for example, NR CELL B.
  • a normal cell such as a cell not recorded in the abnormal cell list
  • the UE will not camp on NR CELL A for a new call within the T3 duration, thereby preventing NR CELL A from sending unreasonable RRC reconfiguration messages again in a short period of time, such as sending an RRC reconfiguration message carrying release information indicating that the DRB and logical channel to be released by the UE do not match.
  • the UE can re-camp to NR CELL A or remain in another cell.
  • This application embodiment takes the UE re-camping to NR CELL A after a duration of T3 as an example.
  • the UE receives a second RRC reconfiguration message sent by NR CELL A while camping on NR CELL A and conducting a second call.
  • the UE re-camps on NR CELL A, which is recorded in the list of abnormal cells, to make a new call, such as during the second call, when the UE receives the second RRC reconfiguration message sent by NR CELL A.
  • the second RRC reconfiguration message carries a second release message.
  • the second release information includes second DRB release information instructing the UE to release the DRB corresponding to the PDCP layer, and second logical channel release information instructing the UE to release the DRB corresponding to the RLC layer.
  • the UE has successfully added DRBs and logical channels in accordance with the provisions of existing standard protocols, with a one-to-one strong binding relationship, such as the number and relationship of DRBs and logical channels shown in Figure 6, and the second release information carried in the second RRC reconfiguration message is the same as the first release information carried in the first RRC reconfiguration message.
  • the UE determines that the DRB and logical channel to be released do not match according to the second release information in the second RRC reconfiguration message, it releases the DRB and logical channel according to the second release information and replies to NR CELL A with the second RRC reconfiguration completion message.
  • Step S306 in this embodiment is similar to step S202.
  • step S202 For specific implementation details, please refer to the description of step S202, which will not be repeated here.
  • the UE determines, based on the second release information in the second RRC reconfiguration message, that if the DRB to be released does not match the logical channel, the UE will accumulate the number of abnormalities N.
  • N N + 1.
  • steps S306 and S307 can be executed in any order. That is, if the UE determines that the second DRB release information and the second logical channel release information carried in the second RRC reconfiguration message do not match, it can simultaneously trigger the release of the DRB and the logical channel according to the second release information, reply to the NR CELL A with the second RRC reconfiguration completion message, and record the number of abnormalities.
  • K2 can be set to 5.
  • T4 can be greater than T3 and less than or equal to T2. For instance, if T2 is 2 days and T3 is 5 minutes, T4 can be 1 day, 30 hours (h), 2 days, etc.
  • the UE when the cumulative N is greater than the second abnormal threshold, the UE can modify the abnormal duration set for NR CELL A in the abnormal cell list from T2 to T5 (T5 is greater than T2).
  • T5 might be 7 days.
  • T4 can be greater than T3 and less than or equal to T5.
  • the mismatch between the DRB to be released and the logical channel is ignored, prompting the UE to complete the RRC reconfiguration.
  • the system records the number of anomalies caused by the mismatch between the DRB to be released and the logical channel, and employs an abnormal cell penalty mechanism (e.g., if the anomaly occurs for the first time, the cell is added to the abnormal cell list with a corresponding anomaly duration and a short access ban duration; if the same anomaly occurs again and the number of anomalies exceeds a certain number, the penalty is increased, such as setting a longer access ban duration).
  • an abnormal cell penalty mechanism e.g., if the anomaly occurs for the first time, the cell is added to the abnormal cell list with a corresponding anomaly duration and a short access ban duration; if the same anomaly occurs again and the number of anomalies exceeds a certain number, the penalty is increased, such as setting a longer access ban duration).
  • NR CELL A may be referred to as the first cell and NR CELL B may be referred to as the second cell.
  • some embodiments of this application also provide a method for reducing call drop rate, which aims to reduce the probability that the UE is camped in an abnormal cell (a cell that has not been configured to release DRBs and logical channels in accordance with existing standard protocols), thereby ensuring that calls can occur as much as possible in normal cells (cells that have been configured to release DRBs and logical channels in accordance with existing standard protocols), so that calls can proceed normally, reduce call failures, and improve user experience.
  • an abnormal cell a cell that has not been configured to release DRBs and logical channels in accordance with existing standard protocols
  • the example is still based on the premise that the DRB and logical channel to be released have been successfully added in accordance with the provisions of the existing standard protocol, with a one-to-one strong binding relationship.
  • DRBs and logical channels have been successfully added in accordance with existing standard protocols, with a one-to-one strong binding relationship, such as the number and relationship of DRBs and logical channels shown in Figure 6. That is, before receiving the RRC reconfiguration message instructing the UE to release DRBs and logical channels, the UE has already added DRB 4, DRB 5, and DRB 6, as well as logical channels 3, 4, and 5, and DRB 4 corresponds one-to-one with logical channel 3, DRB 5 corresponds one-to-one with logical channel 4, and DRB 6 corresponds one-to-one with logical channel 5.
  • the UE can be either the calling party UE or the called party UE.
  • the cell where the UE is camped is still a 5G cell as an example.
  • the method for reducing call drop rate specifically includes:
  • Step S401 in this embodiment is similar to step S201 in the embodiment shown in FIG8.
  • step S201 for specific implementation details, please refer to the description of step S201, which will not be repeated here.
  • the UE determines that the DRB and logical channel to be released do not match according to the first release information in the first RRC reconfiguration message, it releases the DRB and logical channel according to the first release information and triggers the RRC re-establishment procedure.
  • Step S402 in this embodiment is similar to step S107 in the embodiment shown in FIG5.
  • step S107 for specific implementation details, please refer to the description of step S107, which will not be repeated here.
  • the UE determines, based on the first release information in the first RRC reconfiguration message, that if the DRB to be released and the logical channel do not match, the UE records the number of abnormalities.
  • steps S402 and S403 can be executed in any order. That is, when the UE determines that the first DRB release information and the first logical channel release information carried in the first RRC reconfiguration message do not match, it can simultaneously trigger the release of the DRB and the logical channel according to the first release information, reply to the NR CELL A with the first RRC reconfiguration completion message, and record the number of abnormalities.
  • the UE adds the identification information of NR CELL A to the list of abnormal cells, sets the abnormal duration of NR CELL A to the second duration (T2 duration), and sets the access to NR CELL A to be prohibited during the third duration (T3 duration).
  • Steps S403 and S404 in this embodiment are similar to steps S303 and S304 in the embodiment shown in FIG9.
  • steps S303 and S304 please refer to the description of steps S303 and S304, which will not be repeated here.
  • the UE received a second RRC reconfiguration message sent by NR CELL A while camped on NR CELL A and conducting a second call.
  • the UE if the first call ends abnormally due to the failure of the first RRC reconfiguration, triggering the RRC re-establishment, and after the first call ends abnormally, the UE camps on NR CELL A, which is recorded in the abnormal cell list, for a new call within the time interval T3 and T2. For example, during the second call, the UE receives the second RRC reconfiguration message sent by NR CELL A.
  • the second RRC reconfiguration message received in step S405 of this embodiment is the same as the second RRC reconfiguration message received in step S305 of the embodiment shown in FIG9.
  • the UE determines that the DRB and logical channel to be released do not match according to the second release information in the second RRC reconfiguration message, it releases the DRB and logical channel according to the second release information and triggers the RRC re-establishment procedure.
  • Step S406 in this embodiment is similar to step S107 in the embodiment shown in FIG5.
  • step S107 for specific implementation details, please refer to the description of step S107, which will not be repeated here.
  • the UE determines, based on the second release information in the second RRC reconfiguration message, that if the DRB to be released does not match the logical channel, the abnormal number N is accumulated.
  • steps S406 and S407 can be executed in any order. That is, if the UE determines that the second DRB release information and the second logical channel release information carried in the second RRC reconfiguration message do not match, it can simultaneously trigger the release of the DRB and the logical channel according to the second release information, reply to the NR CELL A with the second RRC reconfiguration completion message, and record the number of abnormalities.
  • Steps S407 and S408 in this embodiment are similar to steps S307 and S308 in the embodiment shown in FIG9.
  • steps S307 and S308 please refer to the description of steps S307 and S308, which will not be repeated here.
  • the RRC re-establishment procedure is triggered according to the existing standard protocol. After interrupting the current call, the number of abnormalities caused by the mismatch between the DRB and logical channel to be released is recorded.
  • An abnormal cell penalty mechanism is adopted (if the abnormality occurs for the first time, the cell is added to the abnormal cell list and a corresponding abnormal duration and a short access prohibition duration are set. If the same type of abnormality occurs again in the future and the number of abnormalities exceeds a certain number, the penalty is increased, such as setting a longer access prohibition duration).
  • calls conducted by the UE while camped on a 5G cell can be data reception and transmission using Acknowledged Mode (AM).
  • AM Acknowledged Mode
  • AM data transmission and reception share a single entity. Therefore, under AM, one DRB in the PDCP layer corresponds to one entity in the RLC layer, and one logical channel.
  • the terminal device includes a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, antenna 1, antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.
  • SIM subscriber identification module
  • the terminal may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements.
  • the illustrated components may be implemented in hardware, software, or a combination of software and hardware.
  • Antennas 1 and 2 are used to transmit and receive electromagnetic wave signals.
  • Each antenna in the terminal device can be used to cover one or more communication frequency bands. Different antennas can also be reused to improve antenna utilization.
  • antenna 1 can be reused as a diversity antenna for a wireless local area network.
  • the antennas can be used in conjunction with a tuning switch.
  • the base station such as the gNB mentioned in the above embodiments, can receive messages sent to the UE, such as the first RRC reconfiguration message and the second RRC reconfiguration message, through antenna 1 or antenna 2.
  • messages sent by the terminal device to the gNB can be transmitted through antenna 1 or antenna 2.
  • the mobile communication module 150 can provide solutions for wireless communication applications on terminal devices, including 2G/3G/4G/5G.
  • the mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc.
  • the wireless communication module 160 can provide solutions for wireless communication applications on terminal devices, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), and other wireless communication technologies.
  • WLANs wireless local area networks
  • Wi-Fi wireless fidelity
  • BT Bluetooth
  • GNSS global navigation satellite system
  • FM frequency modulation
  • NFC near field communication
  • IR infrared
  • antenna 1 of the terminal device may be coupled to mobile communication module 150, and antenna 2 may be coupled to wireless communication module 160. This allows the terminal device to communicate with networks and other devices via mobile communication technology or wireless communication technology.
  • the audio module 170 of the terminal device may include a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, etc.
  • the terminal device can implement audio functions, such as music playback, recording, and voice call services as described in the embodiments of this application, through the speaker 170A, receiver 170B, microphone 170C, headphone jack 170D in the audio module 170, and application processor.
  • audio functions such as music playback, recording, and voice call services as described in the embodiments of this application, through the speaker 170A, receiver 170B, microphone 170C, headphone jack 170D in the audio module 170, and application processor.
  • the sensor module 180 in the terminal device may include, in some embodiments, a pressure sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an accelerometer, a distance sensor, a proximity sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc., which will not be listed here, and this application does not impose any limitations on it.
  • the processor 110 may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and/or a neural network processing unit (NPU), etc.
  • AP application processor
  • GPU graphics processing unit
  • ISP image signal processor
  • DSP digital signal processor
  • NPU neural network processing unit
  • processing units can be independent devices or integrated into one or more processors.
  • the terminal device can implement the technical solutions provided in the embodiments of this application through the two processing units, AP 110A and Modem 110B.
  • the AP responds to a user-initiated call request, and then calls the call service-related services in the application framework layer shown in Figure 12, as well as the corresponding drivers in the kernel layer, to hand over the call request to the Modem.
  • the Modem can then interact with the network side to establish a call. Accordingly, during the call, the Modem can interact with the network side according to the processing logic involved in the methods for reducing call drop rates provided in the embodiments of this application.
  • the processing logic involved in the methods for reducing call drop rates provided in the embodiments of this application.
  • the controller unit included in the processor 110 can be the nerve center and command center of the terminal device.
  • the controller can generate operation control signals based on the instruction opcode and timing signals to control the fetching and execution of instructions.
  • the memory in processor 110 is primarily used to store instructions and data.
  • the memory in processor 110 is a cache memory.
  • USB interface 130 shown in Figure 11 is an interface that conforms to the USB standard specification, specifically it can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc.
  • the charging management module 140 receives charging input from the charger. Additionally, the power management module 141 shown in Figure 11 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and/or the charging management module 140, supplying power to the processor 110, internal memory 121, external memory, display 194, camera 193, and wireless communication module 160, etc.
  • the wireless communication function of the terminal device can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor, and baseband processor, etc.
  • the terminal device shown in Figure 11 implements display functions through a GPU, a display screen 194, and an application processor.
  • the GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor.
  • the GPU is used to perform mathematical and geometric calculations for graphics rendering.
  • the processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.
  • display screen 194 is used to display images, videos, etc.
  • Display screen 194 includes a display panel.
  • the terminal device may include one or N display screens 194, where N is a positive integer greater than 1.
  • the terminal device can implement shooting functions through an ISP, camera 193, video codec, GPU, display 194, and application processor.
  • the camera 193 is used to capture still images or videos.
  • the terminal device may include one or N cameras 193, where N is a positive integer greater than 1.
  • Figure 11 shows that the external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device.
  • the external memory card communicates with the processor 110 through the external memory interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.
  • FIG. 11 shows that internal memory 121 can be used to store computer executable program code, which includes instructions.
  • Processor 110 executes various functional applications and data processing of the terminal device by running the instructions stored in internal memory 121.
  • the list of abnormal cells recorded in the above embodiment can be stored in the internal memory 121 of the terminal device.
  • the motor 191 shown in Figure 11 may be, for example, a vibration motor; the indicator 192 may be an indicator light.
  • SIM card interface 195 shown in Figure 11 can be used to connect a SIM card or a USIM card.
  • the SIM card can be inserted into or removed from the SIM card interface 195 to achieve contact and separation with the terminal device.
  • the terminal device can support one or N (N is an integer greater than 1) SIM card interfaces 195. That is, multiple SIM cards or USIM cards can be inserted into the terminal.
  • operating systems run on top of these components. Examples include Apple's iOS operating system, Google's Android open-source operating system, and Microsoft's Windows operating system.
  • the operating system of a terminal device can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservices architecture, or a cloud architecture.
  • This application uses the layered architecture of the Android system as an example to exemplify the software structure of the terminal device. It should be noted that although this application uses the Android system as an example, its basic principles are equally applicable to terminal devices based on operating systems such as iOS or Windows.
  • an exemplary diagram illustrates the relationship between the software structure and hardware components of a terminal device, as well as its interaction with a gNB.
  • the software structure adopts a layered architecture, which divides the software into several layers, each with a clear role and division of labor. Layers communicate with each other through software interfaces.
  • the Android system which runs on the application processor (AP)
  • the Android system is divided into five layers, from top to bottom: the application layer, the application framework layer (Framework), the Android runtime and system libraries, the hardware abstraction layer (HAL), and the system kernel layer (Kernel).
  • the application layer can include a series of application packages. These application packages can include systemUI, camera, gallery, calendar, call, map, WLAN, Bluetooth, music, video, SMS, and other applications (APPs).
  • application packages can include systemUI, camera, gallery, calendar, call, map, WLAN, Bluetooth, music, video, SMS, and other applications (APPs).
  • APPs applications
  • systemUI is used to display the interface of the terminal device, such as displaying the signal icon corresponding to the SIM card, displaying the call interface, etc.
  • the application framework layer provides application programming interfaces (APIs) and programming frameworks for applications within the application layer.
  • APIs application programming interfaces
  • these programming interfaces and frameworks can be described as functions.
  • the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, etc.
  • the phone manager is used to provide call functionality for terminal devices, such as call status management (including connection, hang-up, etc.).
  • the application framework layer may also include a Radio Interface Layer (RIL).
  • RIL Radio Interface Layer
  • the modem can interact with the telephony via the RIL.
  • the Android Runtime comprises the core libraries and the virtual machine.
  • the Android Runtime is responsible for the scheduling and management of the Android system.
  • the core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.
  • the application layer and application framework layer run in a virtual machine.
  • the virtual machine executes the Java files of the application layer and application framework layer as binary files.
  • the virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.
  • System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.
  • surface manager e.g., media libraries
  • 3D graphics processing libraries e.g., OpenGL ES
  • 2D graphics engines e.g., SGL
  • the kernel layer is the layer between hardware and software. It can include various drivers, such as display drivers, camera drivers, audio drivers, and sensor drivers.
  • the modem may include the Non-Access Stratum (NAS layer), RRC layer, PDCP layer, RLC layer, Medium Access Control Layer (MAC layer), and Physical (PHY) layer.
  • NAS layer Non-Access Stratum
  • RRC layer Radio Resource Control Layer
  • PDCP layer Radio Link Control Layer
  • RLC layer Radio Link Control Layer
  • MAC layer Medium Access Control Layer
  • PHY Physical
  • a strong check switch can be set in the RRC layer of the Modem.
  • the strong verification switch when the strong verification switch is off, if the UE determines, based on the received RRC reconfiguration message, that the DRB to be released does not match the logical channel, it can execute step S202 in the embodiment shown in Figure 8, or steps S302 and S306 in the embodiment shown in Figure 9. That is, when the strong verification switch is off, the UE is configured not to perform strong verification on the release information in the RRC reconfiguration message sent by the network side. Thus, when the DRB to be released does not match the logical channel, ignoring this mismatch allows the UE to complete the RRC reconfiguration, thereby ensuring that the current call is not interrupted.
  • the strong verification switch when the strong verification switch is on, if the UE determines, based on the received RRC reconfiguration message, that the DRB to be released does not match the logical channel, it can execute step S402 of the embodiment shown in Figure 10, and the subsequent steps. That is, when the strong verification switch is on, the UE follows existing standard protocols to perform strong verification on the release information in the RRC reconfiguration message sent by the network side, triggering the RRC re-establishment process. After interrupting the current call, it records the number of anomalies caused by the mismatch between the DRB to be released and the logical channel, and applies an abnormal cell penalty mechanism to that cell. This avoids re-entering the cell within a short period afterward, effectively reducing the probability of the UE camping in an abnormal cell and ensuring that subsequent calls occur in normal cells as much as possible, allowing call services to proceed normally.
  • the strong verification switch set in the RRC layer is only visible to the UE and not to the user. That is, the terminal manufacturer pre-installs it in the RRC layer and sets its switch state before the UE leaves the factory.
  • the strong verification switch can be understood as a software switch, or a software interface. This strong verification switch controls whether the UE performs strong verification on the information in the RRC reconfiguration message sent by the network side that instructs the UE to release the DRB and logical channel; that is, whether it strictly verifies according to the provisions of existing standard protocols, or whether mismatches can be ignored.
  • the strong verification switch is, for example, a functional module implemented by software code.
  • the strong verification switch may be in the on state by default.
  • the strong verification switch may be in the off state by default.
  • the layers in a modem can be software modules.
  • the modem can interact with the base station through the antenna, such as receiving the first RRC reconfiguration message and the second RRC reconfiguration message sent by the network side in various embodiments of this application, sending the first RRC reconfiguration completion message and the second RRC reconfiguration completion message to the network side, and the interactions involved in the RRC re-establishment process.
  • the layers and components contained in each layer of the software structure shown in Figure 12 do not constitute a specific limitation on the first terminal.
  • the first terminal may include more or fewer layers than illustrated, and each layer may include more or fewer components; this application does not impose any limitations.
  • the terminal device includes hardware and/or software modules corresponding to the execution of each function.
  • this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in conjunction with the embodiments, but such implementation should not be considered beyond the scope of this application.
  • this application embodiment also provides a chip system, which may include a processor.
  • the chip system can be coupled to a memory, enabling the processor in the chip system to call a computer program stored in the memory during runtime, thereby implementing the steps executed by the terminal device.
  • the processor in the chip system can be an application processor (AP) or a non-application processor, such as a modem processor.
  • this application embodiment also provides a computer-readable storage medium storing computer instructions.
  • the terminal device When the computer instructions are executed on a terminal device, the terminal device performs the aforementioned related method steps to achieve the method for reducing call drop rate in the above embodiments.
  • this application also provides a computer program product that, when run on a terminal device, causes the terminal device to perform the aforementioned related steps to achieve the method for reducing call drop rate described in the above embodiments.
  • the terminal device, computer-readable storage medium, computer program product, or chip system provided in the embodiments of this application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

Landscapes

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

Abstract

本申请提供了一种降低掉话率的方法、设备及芯片系统。在终端设备驻留在第一小区进行第一通话的过程中，当第一小区对应的基站下发的第一RRC重配置消息中携带的第一DRB释放信息和第一逻辑信道释放信息不匹配的情况下，设置终端设备按照第一DRB释放信息释放DRB，第一逻辑信道释放信息逻辑信道后，向第一小区对应的基站正常回复第一RRC重配置完成消息。即，忽略该不匹配的情况，从而保证了终端设备能够基于第一RRC重配置消息完成RRC重配置，降低通话故障，提升用户体验。

Description

降低掉话率的方法、设备及芯片系统
本申请要求于2024年06月21日提交中国专利局、申请号为202410814397.1、发明名称为“降低掉话率的方法、设备及芯片系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种降低掉话率的方法、设备及芯片系统。
背景技术
在5G，即NR(New Radio，新空口)网络中，由网络侧向终端设备发起的RRC重配置(Radio Resource Control Reconfiguration，无线资源控制重配置)，可用于修改分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层对应的数据无线承载(Data Radio Bearer，DRB)，以及无线链路层控制协议(Radio Link Control，RLC)层对应的逻辑信道或资源承载(Radio Link Control，RB)，以更好的适应于实际的业务场景。
然而，目前存在终端设备校验RRC重配置消息失败，进而导致通话中断的情况。
发明内容
为了解决上述技术问题，本申请实施例提供一种降低掉话率的方法、设备及芯片系统，旨在降低通话故障，提升用户体验。
第一方面，本申请实施例提供一种降低掉话率的方法。该方法应用于终端设备，包括：在第一小区进行第一通话的过程中，接收到第一小区对应的基站发送的第一RRC重配置消息；其中，第一RRC重配置消息包括第一释放信息，第一释放信息包括第一数据无线承载DRB释放信息和第一逻辑信道释放信息，第一DRB释放信息指示了要被释放的第一DRB的信息，第一逻辑信道释放信息指示了要被释放的第一逻辑信道的信息；在第一DRB释放信息和第一逻辑信道释放信息不匹配的情况下，根据第一DRB释放信息释放第一DRB，根据第一逻辑信道释放信息释放第一逻辑信道，并向第一小区对应的基站回复第一RRC重配置完成消息。
其中，第一DRB为分组数据汇聚协议PDCP层对应的DRB。
其中，第一逻辑信道为无线链路层控制协议RLC层对应的逻辑信道。
其中，第一DRB释放信息和第一逻辑信道释放信息不匹配，例如为第一DRB释放信息指示要被释放的第一DRB和第一逻辑信道释放信息指示要被释放的第一逻辑信道不匹配。即，确定第一DRB释放信息和第一逻辑信道释放信息释放匹配，例如为根据第一DRB释放信息和第一逻辑信道释放信息，确定要释放的第一DRB和第一逻辑信道是否匹配。
其中，第一RRC重配置完成消息用于告知第一小区对应的基站，基于第一RRC重配置消息进行的RRC重配置已完成。
其中，终端设备可以称为UE。
由此，通过设置UE不对网络侧下发的RRC重配置消息中的释放信息，如第一RRC重配置消息中第一释放信息进行强校验，在需要释放的DRB和逻辑信道不匹配的情况下，忽略该不匹配情况，促使UE完成RRC重配置。这样，当前进行的第一通话就不会被中断，UE就可以继续驻留在当前所在小区，如NR CELL A中进行第一通话，达到了降低通话故障，保障通话质量，提升用户体验的效果。
根据第一方面，终端设备的调制解调处理器中设置了强校验开关；在第一DRB释放信息和第一逻辑信道释放信息不匹配的情况下，根据第一DRB释放信息释放第一DRB，根据第一逻辑信道释放信息释放第一逻辑信道，并向第一小区对应的基站回复第一RRC重配置完成消息，包括：在强校验开关处于关闭状态，并且第一DRB释放信息和第一逻辑信道释放信息不匹配的情况下，根据第一DRB释放信息释放第一DRB，根据第一逻辑信道释放信息释放第一逻辑信道，并向第一小区对应的基站回复第一RRC重配置完成消息。
其中，强校验开关可以理解为一个软件开关或软件接口。该强校验开关用于控制UE是否对网络侧下发的RRC重配置消息中用于指示UE释放DRB和逻辑信道的信息进行强校验，即是严格按照现有的标准协议的规定进行校验，还是可以忽略不匹配情况。
在一些实现方式中，强校验开关例如为通过软件代码实现的功能模块。
由此，在强校验开关处于关闭状态的情况下，设置UE不对网络侧下发的RRC重配置消息中的释放信息进行强校验。这样，在需要释放的DRB和逻辑信道不匹配的情况下，忽略该不匹配情况，就可以促使UE完成RRC重配置，进而保证当前进行的通话不会被中断。
根据第一方面，或者以上第一方面的任意一种实现方式，方法还包括：在强校验开关处于开启状态，并且第一DRB释放信息和第一逻辑信道释放信息不匹配的情况下，根据第一DRB释放信息释放第一DRB，根据第一逻辑信道释放信息释放第一逻辑信道，并触发RRC重建立流程。
由此，在强校验开关处于开启状态的情况下，UE遵循现有的标准协议的规定，对网络侧下发的RRC重配置消息中的释放信息进行强校验，在第一DRB释放信息和第一逻辑信道释放信息不匹配的情况下，触发RRC重建立流程，中断当前进行的通话后。
根据第一方面，或者以上第一方面的任意一种实现方式，第一释放信息被携带在第一RRC重配置消息的第一字段中，第一字段为标准协议中规定的用于携带第一DRB释放信息和第一逻辑信道释放信息的字段。
示例性的，根据现有的标准协议的规定，在第一DRB释放信息和第一逻辑信道释放信息被携带在第一字段的情况下，第一DRB释放信息指示的要被释放的第一DRB和第一逻辑信道释放信息指示的要被释放的第一逻辑信道存在强绑定关系，如数量必须相同，并且存在添加环节设置的对应关系。如添加环节设置了DRB 4对应逻辑信道3，DRB 5对应了逻辑信道4，DRB 6对应了逻辑信道5，则在第一DRB释放信息指示要释放DRB 4、DRB 5和DRB 6的情况下，第一逻辑信道信息指示要被释放的第一逻辑信道必须为逻辑信道3、逻辑信道4和逻辑信道5。
根据第一方面，或者以上第一方面的任意一种实现方式，第一字段为小区组配置CellGroupConfig字段。
根据第一方面，或者以上第一方面的任意一种实现方式，在第一释放信息被携带在第一字段的情况下，执行在第一DRB释放信息和第一逻辑信道释放信息不匹配的情况下，根据第一DRB释放信息释放第一DRB，根据第一逻辑信道释放信息释放第一逻辑信道，并向第一小区对应的基站回复第一RRC重配置完成消息的步骤。
根据第一方面，或者以上第一方面的任意一种实现方式，第一释放信息被携带在第一RRC重配置消息的第二字段中，第二字段与第一字段不相同，第一字段为标准协议中规定的用于携带第一DRB释放信息和第一逻辑信道释放信息的字段。
其中，第二字段不限定第一DRB释放信息指示的要被释放的第一DRB和第一逻辑信道释放信息指示的要被释放的第一逻辑信道存在强绑定关系。
根据第一方面，或者以上第一方面的任意一种实现方式，第二字段为主小区组masterCellGroup字段。
根据第一方面，或者以上第一方面的任意一种实现方式，在第一释放信息被携带在第二字段的情况下，执行在第一DRB释放信息和第一逻辑信道释放信息不匹配的情况下，根据第一DRB释放信息释放第一DRB，根据第一逻辑信道释放信息释放第一逻辑信道，并向第一小区对应的基站回复第一RRC重配置完成消息的步骤。
根据第一方面，或者以上第一方面的任意一种实现方式，方法还包括：在第一释放信息被携带在第一字段，并且第一DRB释放信息和第一逻辑信道释放信息不匹配的情况下，根据第一DRB释放信息释放第一DRB，根据第一逻辑信道释放信息释放第一逻辑信道，并触发RRC重建立流程；其中，在完成RRC重建立流程后，在第一时长内未接收到RRC重建立流程中接入的小区对应的基站下发的配置第二DRB和第二逻辑信道的消息的情况下，释放第一通话。
根据第一方面，或者以上第一方面的任意一种实现方式，在第一小区进行的第一通话采用确认模式进行数据的接收和发送。
根据第一方面，或者以上第一方面的任意一种实现方式，方法还包括：在第一DRB释放信息和第一逻辑信道释放信息不匹配的情况下，记为一次异常；在累计的异常的次数，大于第一异常阈值的情况下，将第一小区的标识信息添加到异常小区名单，设置第一小区的异常时长为第二时长，并在第三时长内禁止访问第一小区，第二时长大于第三时长。
由此，通过设置UE不对网络侧下发的RRC重配置消息中的释放信息进行强校验，在需要释放的DRB和逻辑信道不匹配的情况下，忽略该不匹配情况，促使UE完成RRC重配置。并记录因为要释放的DRB和逻辑信道不匹配出现的异常次数，对该小区采用异常小区惩罚机制，避免事后短时间内再进入该小区，从而既可以保证当前进行的通话不会被中断，又可以降低后续UE驻留在该小区的概率，使得通话能够尽可能发生在正常小区，进一步降低了通话故障，保障了通话质量，提升了用户体验。
根据第一方面，或者以上第一方面的任意一种实现方式，方法还包括：在第二时长内，在第一小区进行第二通话的过程中，接收到第一小区对应的基站发送的第二RRC重配置消息；其中，第二RRC重配置消息包括第二释放信息，第二释放信息包括第二DRB释放信息和第二逻辑信道释放信息，第二DRB释放信息指示了要被释放的第二DRB的信息，第二逻辑信道释放信息指示了要被释放的第二逻辑信道的信息；在第二DRB释放信息和第二逻辑信道释放信息不匹配的情况下，根据第二DRB释放信息释放第二DRB，根据第二逻辑信道释放信息释放第二逻辑信道，向第一小区对应的基站回复第二RRC重配置完成消息，并累计一次异常的次数；在累计的异常的次数，大于第二异常阈值的情况下，在第四时长内禁止访问第一小区，第二异常阈值大于第一异常阈值，第四时长大于第三时长。
根据第一方面，或者以上第一方面的任意一种实现方式，方法还包括：在第四时长内，通过第二小区对应的基站进行第三通话，第二小区不是异常小区名单中的小区。
根据第一方面，或者以上第一方面的任意一种实现方式，在第一DRB释放信息指示要被释放的第一DRB的数量和第一逻辑信道释放信息指示要被释放的第一逻辑信道的数量不相同的情况下，第一DRB释放信息和第一逻辑信道释放信息不匹配。
例如，在第一DRB释放信息指示要被释放的第一DRB为DRB 4、DRB 5和DRB 6这3个DRB，第一逻辑信道释放信息指示要被释放的第一逻辑信道为逻辑信道3这一个逻辑信道的情况下，确定第一DRB释放信息和第一逻辑信道释放信息不匹配。
根据第一方面，或者以上第一方面的任意一种实现方式，在第一DRB释放信息指示要被释放的第一DRB和第一逻辑信道释放信息指示要被释放的第一逻辑信道不对应的情况下，第一DRB释放信息和第一逻辑信道释放信息不匹配。
例如，在添加环节设置了DRB 4对应逻辑信道3，DRB 5对应了逻辑信道4，DRB 6对应了逻辑信道5，则在第一DRB释放信息指示要被释放的第一DRB为DRB 4、DRB 5和DRB 6，第一逻辑信道释放信息指示要被释放的第一逻辑信道为逻辑信道3的情况下，确定第一DRB释放信息和第一逻辑信道释放信息不匹配。
第二方面，本申请实施例提供了一种终端设备。该终端设备包括：存储器和处理器，存储器和处理器耦合；存储器存储有程序指令，程序指令由处理器执行时，使得所述终端设备执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
第三方面，本申请实施例提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
第四方面，本申请实施例提供了一种计算机程序，该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
第五方面，本申请实施例提供了一种芯片系统，该芯片系统包括处理器。处理器用于支持终端设备实现上述第一方面或第一方面的任意可能的实现方式中的方法的指令。
根据第五方面，处理器包括调制解调处理器。
相应地，处理器用于支持终端设备实现上述第一方面或第一方面的任意可能的实现方式中的方法的指令，具体包括：
调制解调处理器用于支持终端设备实现上述第一方面或第一方面的任意可能的实现方式中的方法的指令。
第五方面以及第五方面的任意一种实现方式分别与第一方面以及第一方面的任意一种实现方式相对应。第五方面以及第五方面的任意一种实现方式所对应的技术效果可参见上述第一方面以及第一方面的任意一种实现方式所对应的技术效果，此处不再赘述。
附图说明
图1为本申请实施例示例性提供的一种网络架构示意图；
图2为本申请实施例示例性提供的一种语音通话场景示意图；
图3为本申请实施例示例性提供的一种RRC重配置成功的场景下，UE和网络侧的gNB的交互示意图；
图4为本申请实施例示例性提供的一种RRC重配置失败的场景下，UE和网络侧的gNB的交互示意图；
图5为本申请实施例示例性提供的一种基于RRC重配置消息释放承载异常，导致当前通话掉话的示意图；
图6为本申请实施例示例性提供的一种RRC重配置消息中指示UE添加DRB和逻辑信道的添加信息的示意图；
图7为本申请实施例示例性提供的一种RRC重配置消息中指示UE释放DRB和逻辑信道的释放信息的示意图；
图8为本申请实施例示例性提供的一种降低掉话率的方法示意图；
图9为本申请实施例示例性提供的又一种降低掉话率的方法示意图；
图10为本申请实施例示例性提供的又一种降低掉话率的方法示意图；
图11为本申请实施例示例性提供的一种终端设备的硬件结构示意图；
图12为本申请实施例示例性提供的一种终端设备的软件结构与硬件器件的关系，以及与gNB的交互示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。应当理解地是，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
本申请实施例的说明书和权利要求书中的术语“第一”、“第二”、“第三”、“第四”等是用于区别不同的对象，而不是用于描述对象的特定顺序。例如，第一目标对象和第二目标对象等是用于区别不同的目标对象，而不是用于描述目标对象的特定顺序。
在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
在本申请实施例的描述中，除非另有说明，“多个”的含义是指两个或两个以上。例如，多个处理单元是指两个或两个以上的处理单元；多个系统是指两个或两个以上的系统。
基于上述前提，以下对本申请实施例提供的技术方案进行说明。
具体地说，本申请实施例提供的技术方案，是针对主叫方和被叫方进行通话的过程中，网络侧和终端设备(主叫方终端设备和/或被叫方终端设备)之间进行的RRC重配置流程的。为了更好地说明本申请实施例提供的技术方案，首先结合附图对本申请实施例提供的技术方案针对的网络架构，以及基于该通信架构实现的语音通话场景进行说明。
参见图1，示例性示出一种网络架构示意图。如图1所示，该网络架构可以包括终端设备、LTE的网络设备、NR的网络设备、核心网，以及IMS或因特网(Internet)。
其中，终端设备(terminal equipment)，也可以称为用户设备(User Equipment，UE)、用户终端、移动台(Mobile Station，MS)、移动终端(Mobile Terminal，MT)等。在本申请的一些实施例中，终端设备可以是手机、可穿戴设备(例如智能手表)等。
其中，LTE(Long Term Evolution，长期演进)，可以理解为第四代移动通信技术(the4th generation mobile communication technology，4G)网络的无线接入网。在LTE网络(即俗称的：4G网络)中，因为演进关系，将接入网部分称为演进的通用移动通信系统(Universal Mobile Telecommunications System，UMTS)陆地无线接入网(Evolved UMTS Terrestrial Radio Access Network，E-UTRAN)。在本申请实施例中，LTE的含义与E-UTRAN的含义相同，均指的是4G网络的接入网部分。
其中，NR(New Radio，新空口)，可以理解为5G网络的无线接入网。在5G网络中，将接入网部分称为下一代无线接入网(Next Generation Radio Access Network，NG-RAN或NG RAN)。在本申请实施例中，NR的含义与NG-RAN(或称NG RAN)的含义相同，均指的是5G网络的接入网部分。
可理解地，LTE和NR均为接入网。接入网负责使用某种有线或者无线的连接和通信技术，将广大最终用户(End User)一级一级汇接到核心网(也称：骨干网)中，实现与网络的连接。接入网是整个网络的边缘部分，即与用户距离最近的一部分，通常也叫“最后一公里”。
其中，网络设备是网络侧用于与终端设备进行通信的设备。在本申请的一些实施例中，网络设备可以是基站。即，在本申请的一些实施例中，LTE的网络设备，例如为4G基站；NR的网络设备，例如为5G基站，如gNB(the next Generation Node B，gNodeB)。
示例性的，在本申请的一些实施例中，终端设备可以通过4G基站接入到LTE。在本申请的另一些实施例中，终端设备可以通过gNB接入到NR。
其中，核心网主要功能是提供用户连接、对用户的管理，以及对业务完成承载，作为承载网络提供到外部网络的接口。用户连接的建立包括移动性管理(Mobile Management，MM)、呼叫管理(Call Management，CM)、交换/路由、录音通知(结合智能网业务完成到智能网外围设备的连接关系)等功能。
可理解地，4G网络的核心网为演进的分组核心(Evolved Packet Core，EPC)网络。EPC网络属于核心网范畴，具备用户签约数据存储、移动性管理和数据交换等移动网络的传统能力，并能够给用户提供超高速的上网体验。5G网络的核心网为5G Core(可简称为：5GC)。5GC会使用通用的网络功能虚拟化设备来代替4G网络的专用通信设备。
需要说明的是，在本申请的一些实施例中，图1所示的网络架构中的核心网可以由EPC网络和5GC融合得到。也就是说，该网络架构中的核心网既可以包括EPC网络中的网元，又可以包括5GC中的网元。例如，该网络架构中的核心网可以包括接入和移动管理功能(Access and Mobility Management Function，AMF)网元、移动管理节点(Mobility Management Entity，MME)网元、服务网关(Serving GateWay，SGW)网元、分组数据网络网关(Packet Data Network GateWay，PGW)网元、会话管理功能(Session Management Function，SMF)网元、用户面功能(User Plane Function，UPF)网元、统一数据管理功能(Unified Data Management，UDM)网元和归属用户服务器(Home Subscriber Server，HSS)网元等。
示例性的，在本申请的一些实施例中，该网络架构中的核心网包括的融合网元，即由EPC网络中的网元和5GC中的网元所得的融合网元，例如为SMF+PGW-C，或者UPF+PGW-U，或UDM+HSS等。其中，PGW-C为PGW网元的控制面节点，PGW-U为PGW网元的用户面节点。
此外，还需要说明的是，在本申请的另一些实施例中，图1所示的网络架构中的核心网可以包括代理会话边界控制(Proxy Session Border Control，PSBC)网元。PSBC可以理解为一个集会话边界控制(Session Border Control，SBC)、代理呼叫会话控制功能(Proxy-CSCF，P-CSCF)、接入转换控制功能(Access Transfer Control Function，ATCF)、接入转换网关(Access Transfer Gateway，ATGW)于一身的合设网元。
当PSBC网元作为SBC网元时，它连接IMS核心网/软交换网络与外部用户接入区域，完成IMS/软交换用户的业务接入、实现不同网络环境下用户业务的互通、保障IMS/软交换网络安全、支持QoS管理、CAC话务控制、媒体管理、CDR媒体呼叫详单等功能。
当PSBC网元作为内置P-CSCF网元时，P-CSCF作为IMS拜访域控制平面统一的入口点，将来自拜访域接入网络的会话初始协议(Session initialization Protocol，SIP)消息，如注册、会话、呈现(Presence)等消息，代理转发到其归属域S-CSCF或I-CSCF。
当PSBC网元作为内置ATCF/ATGW网元时，通过设置ATCF/ATGW功能实体于P-CSCF与I-CSCF/S-CSCF之间，对于可能发生增强的单一无线语音呼叫连续性(Enhanced Single Radio Voice Call Continuity，eSRVCC)切换的护具，将媒体流锚定到ATGW。这样后续在发生sSRVCC切换时，只需要更新ATGW上的媒体信息，不需要更新终端设备的媒体信息，使整个eSRVCC切换时间更短。
此外，应当理解地，核心网中的各个网元也可以称为功能实体。即，核心网既可以是在专用硬件上实现的网络元件，也可以是在专用硬件上运行的软件实例，或者是在适当平台上虚拟化功能的实例。
此外，还应当理解地，本申请实施例中所有网元的名称仅仅作为示例。在未来通信中，如6G网络中，这些网元还可以称为其它名称。或者，在未来通信中，如6G网络中，这些网元还可以通过其它具有相同功能的实体或者设备等来替代，本申请对此均不作限定。这里做统一说明，后续不再赘述。可选地，本申请实施例中的各种网元，可以是通信设备，也可以是可用于该通信设备中的芯片或芯片系统等，本申请实施例对此不作限定。
此外，还应当理解地，图1所示的网络架构中的核心网还可以包括其他设备、网元、网络实体或网络子系统，如策略控制功能(Policy Control function，PCF)网元，本申请对此不作限制。
此外，本申请实施例对核心网中各个网元的分布方式不作限制，该分布方式具体可以参考相关技术文档，本申请在此不展开说明。
其中，IMS即IP多媒体子系统(IP Multimedia Subsystem)，是一个基于网际互连协议(Internet Protocol，IP)网络提供语音及多媒体通信业务(例如语音、视频和文本消息等)的网络体系架构。IMS可在不同网络的不同设备之间实现安全可靠的多媒体通信。IMS的架构模型提供了统一的基础结构和通用机制，用于控制、操作、路由和管理会话，以及实现身份验证、授权和记帐控制。IMS规范包含广泛使用的互联网工程任务组(The Internet Engineering Task Force，IETF)建议。例如，用于会话控制信令的会话初始协议(Session initialization Protocol，SIP)。
其中，Internet一般指互联网，又称国际网络，指的是网络与网络之间所串连成的庞大网络，这些网络以一组通用的协议相连，形成逻辑上的单一巨大国际网络。从网络通信的角度来看，Internet是一个以传输控制协议(Transmission Control Protocol，TCP)/网间协议(Internet Protocol，IP)连接全球各个国家、各个地区、各个机构计算机网络的数据通信网。
需要说明的是，图1所示的网络架构中不限于仅包括图中所示的设备和网络，还可以包括其它未在图中表示的设备，本申请对此不再一一举例说明。
参见图2，示例性示出一种语音通话场景的示意图。如图2所示，第一终端可以通过第一网络设备、IMS和第二网络设备来与第二终端进行语音数据的传输，即进行通话。其中，第一网络设备为第一终端当前驻留的小区所对应的网络设备，第二网络设备为第二终端当前驻留的小区所对应的网络设备。
示例性的，在本申请的一些实施例中，第一网络设备和第二网络设备可以为同一个网络设备。
示例性的，在本申请的一些实施例中，第一终端可以为发起语音通话的一方，以请求与第二终端进行语音通话。
示例性的，在本申请的另一些实施例中，第二终端可以为发起语音通话的一方，以请求与第一终端进行语音通话。
示例性的，在本申请的一些实施例中，第一终端和第二终端可以是5G手机，即使用第五代通信系统的智能手机。
示例性的，在本申请的一些实施例中，如第一终端和第二终端均为5G手机，但均未开启独立组网(Standalone，SA)开关/功能，或者均为4G手机的场景中，第一网络设备和第二网络设备可以是4G基站。
示例性的，在本申请的另一些实施例中，如第一终端和第二终端均为5G手机，并且均开启了SA开关/功能的场景中，第一网络设备和第二网络设备可以是gNB。这样，第一终端和第二终端就可以直接连接到5G网络，而不必依赖于4G网络，从而获得更快的网络速度和更低的延迟，能够更好的提升通话体验。
此外，应当理解地，通话的正常进行，依赖于UE与网络侧的基站基于RRC确定的无线网络资源。随着通信技术的发展，例如，5G网络，为了保证通话过程中，无线网络资源能够更好地适应于实际的业务场景，引入了RRC重配置，以实现对UE和基站之间的RRC连接的修改。例如，建立(添加)/修改/释放DRB、逻辑信道/RB，执行小区切换(基站的切换)，设置/修改/释放测量报告等。
此外，还应当理解地是，关于RRC重配置，在4G网络中也可以实现。具体到4G网络中，RRC重配置被称为RRC连接重配置。为了便于说明，本申请实施例以5G网络中进行的RRC重配置为例进行说明。
具体地说，在5G网络中，RRC重配置是由网络侧(5G基站，如gNB)发起的。即，gNB主动向对应的UE发送RRC重配置消息，如图3中的“RRC Reconfiguration”。
示例性的，RRC重配置消息中可以携带指示UE添加/修改/释放DRB、逻辑信道/RB的信息。
示例性的，RRC重配置消息中还可以携带指示UE测报操作的测量配置、天线切换模式的SRS资源的配置、与基站之间交互的数据包采用的加解密算法的配置等，此处不再一一列举。
关于携带不同配置下的RRC重配置消息中具体的内容、格式，可以参见现有的标准协议，此处不再赘述。
基于现有的标准协议的规定，UE接收到gNB下发的RRC重配置消息(RRC Reconfiguration)后，需要先对RRC重配置消息中的内容进行校验。如果校验成功，将按照RRC重配置消息，完成RRC重配置，并在完成RRC重配置，即RRC重配置成功后，向gNB回复RRC重配置完成消息如图3中示出的“RRC Reconfiguration Complete”，以告知gNB基于RRC重配置消息进行的RRC重配置已完成。反之，如果校验失败，UE不会向gNB回复“RRC Reconfiguration Complete”，而是会触发RRC重建立流程，如图4中示出的“RRC Connection re-establishment”。
基于现有的标准协议的规定，在RRC重配置失败，UE触发RRC重建立流程的场景中，UE会先执行无线链路故障(Radio link failure，RLF)流程，如释放与当前所在小区的gNB之间的连接。然后，UE会重新进行小区选择，进而与重新选择的小区对应的gNB进行RRC重建立流程，如向重选的gNB发送RRC重建立请求(携带了RRC重配置失败的原因值，如Reconfiguration failure)。
相应地，重选的gNB接收到该RRC重建立请求后，会给UE回复指示了无线承载和服务小区组的无线资源控制连接建立(RRC Connection Setup)消息，以使UE与该重选的gNB建立RRC连接。
可理解地，RRC重建立阶段，UE可以选择原小区(触发RRC重建立流程前驻留的小区)驻留，也可以选择新的小区进行驻留。即UE重选的gNB可以是触发RRC重建立流程前接入gNB(后续称为：原基站)，也可以是原小区中其他的gNB，还可以是其他小区的gNB。
关于UE与gNB进行RRC连接重建立的具体实现流程，以及RLF流程的具体实现细节，可以参见现有的标准协议，此处不再赘述。
本申请的实施例以RRC重建立阶段，UE选择原基站驻留为例。对于这种场景，由于重选的gNB是刚刚断开连接的原基站，因此原基站在与UE完成RRC Connection re-establishment后，会认为当前的RRC连接存在异常。基于现有的标准协议的规定，重选的gNB，即原基站会向UE下发结束当前通话的BYE消息，进而挂断当前通话。
也就是说，RRC重配置失败，会导致当前正在进行的通话被中断。
为了更好地理解，以UE驻留在5G小区gNB进行通话过程中，UE根据gNB下发的RRC重配置消息中指示添加/释放DRB(本申请各实施例所说的DRB均为PDCP层对应的DRB)、逻辑信道/RB(后续统一描述为：逻辑信道，另外本申请各实施例所说的逻辑信道均为RLC层对应的逻辑信道)的信息，进行RRC重配置的具体流程进行说明。
参见图5，示例性的，UE驻留在5G小区gNB进行通话过程中，根据gNB下发的RRC重配置消息中指示添加/释放DRB的信息，进行RRC重配置的流程，具体包括：
S101，UE驻留在5G小区(如NR CELL A)进行通话的过程中，接收到NR CELL A发送的RRC重配置消息1。
示例性的，UE接收到的RRC重配置消息1为NR CELL A对应的gNB下发的。
示例性的，下发RRC重配置消息1的gNB为NR CELL A中，与UE建立RRC连接，进行通话的gNB。
示例性的，UE驻留在NR CELL A进行通话的过程中，接收到的RRC重配置消息中可以包括(或者说携带)用于指示UE添加DRB和逻辑信道的添加信息，和/或用于指示UE修改DRB和逻辑信道的修改信息，和/或用于指示UE释放DRB和逻辑信道的释放信息。
作为一种可能的实现方式，本申请实施例的步骤S101中UE接收到的来自NR CELL A下发的RRC重配置消息1为携带了用于指示UE添加DRB和逻辑信道的添加信息的RRC重配置消息为例。
S102，UE对RRC重配置消息1中携带的添加信息进行校验，并在校验成功的情况下，根据添加信息，添加DRB和逻辑信道。
示例性的，RRC重配置消息1携带的用于指示UE添加DRB和逻辑信道的添加信息包括DRB添加信息和逻辑信道添加信息。
此外，需要说明的是，为了保证通话的正常进行，一个DRB需要对应一个逻辑信道，并且二者之间存在一一对应的关系。在本申请的一些实施例中，RRC重配置消息中携带的指示UE添加DRB和逻辑信道的添加信息可以包括每一个需要添加的DRB的身份(Identity)信息(如标识号)，每一个需要添加的逻辑信道的身份(Identity)信息(如标识号)，以及每一个需要添加的DRB和逻辑信道之间的对应关系。
示例性的，在本申请的一些实施例中，添加信息可以配置在RRC重配置消息中指定的字段，如rlc-BearerToAddModList中，并且存在对应关系的DRB和逻辑信道可以成对出现。例如，在需要添加的DRB包括身份信息为4、5、6这3个DRB，需要添加的逻辑信道包括身份信息为3、4、5这3个逻辑信道，并且DRB 4与逻辑信道3对应，DRB5与逻辑信道4对应，DRB 6与逻辑信道5对应的情况下，RRC重配置消息的rlc-BearerToAddModList字段下配置的添加信息可以如图6所示。
可理解地，图6中省略号“...”部分省略了RRC重配置消息中可以在rlc-BearerToAddModList字段下配置的其他字段的配置信息。关于携带不同配置下的RRC重配置消息中具体的内容、格式，可以参见现有的标准协议，此处不再赘述。
以RRC重配置消息1中携带的添加信息如图6所示，由于需要添加的DRB的数量和需要添加的逻辑信道的数量相同，并且每一个DRB对应了一个单独的逻辑信道。故而，UE对该添加信息校验成功，可以根据图6所示添加信息，添加对应的DRB和逻辑信道。
相应地，在完成步骤S102的操作后，基于图3所示RRC重配置成功的情况下，UE与gNB的交互逻辑可知，UE将向NR CELL A回复RRC重配置完成消息1，即执行步骤S103。
可理解地，如果RRC重配置消息1中携带的添加消息指示UE要添加的DRB数量和逻辑信道数量不匹配，如要添加的DRB数量有3个，要添加的逻辑信道有2个；或者指示UE要添加的DRB与逻辑信道没有一一对应，如1个DRB对应了2个逻辑信道，或者1个逻辑信道对应的2个DRB。这种情况下，根据现有的标准协议的规定，UE对RRC重配置消息1的校验将失败，基于图4所示RRC重配置失败的情况下，UE与gNB的交互逻辑可知，UE将触发RRC重建立流程。
此外，根据现有的标准协议的规定，RRC重配置消息中指示UE添加DRB和逻辑信道的添加信息是成对出现的，如图6所示。因此，添加信息的校验通常不会出现失败的情况下。即，在RRC重配置消息是用于指示UE进行添加DRB和逻辑信道的场景中，UE接收到NR CELL A下发的重配置消息1后，会正常执行步骤S102和步骤S103。
S103，UE向NR CELL A回复RRC重配置完成消息1。
示例性的，UE是向NR CELL A中下发RRC重配置消息1的gNB回复RRC重配置完成消息1。
示例性的，RRC重配置完成消息1用于告知下发RRC重配置消息1的gNB，基于RRC重配置消息1进行的RRC重配置(添加DRB和逻辑信道)已完成。
可理解地，在基于RRC重配置消息1进行的RRC重配置完成的情况下，UE驻留在NR CELL A进行的通话依旧可以正常进行，直到主叫方的UE或者被叫方的UE触发挂机操作，如按下UE用户界面中挂断通话的按钮，当前通话才会结束。为了区分，这种情况下结束的通话可以理解为正常结束场景。
本申请的实施例以基于RRC重配置消息1进行的RRC重配置完成后，UE驻留在NR CELL A进行的通话依旧进行为例，即UE驻留在NR CELL A继续进行通话。
S104，UE驻留在NR CELL A继续进行通话的过程中，接收到NR CELL A发送的RRC重配置消息2。
可理解地，为了更好地适应于实际的业务场景，在UE驻留在NR CELL A继续进行通话的过程中，随着NR CELL A无线网络资源的变化，或者驻留小区的变化，网络侧(当前驻留小区的基站)会重新向UE下发RRC重配置消息，以重新添加新的DRB和逻辑信道，和/或修改之前添加的DRB和逻辑信道，和/或释放之前添加的DRB和逻辑信道，从而保证当前进行的通话质量。
本申请的实施例以UE驻留在NR CELL A继续进行通话的过程中，NR CELL A无线网络资源的变化，NR CELL A重新向UE下发的RRC重配置消息为携带了指示UE释放之前添加的DRB和逻辑信道的释放信息的RRC重配置消息2为例。
S105，UE对RRC重配置消息2中携带的释放信息进行校验，确定要释放的DRB和逻辑信道释放匹配。
示例性的，RRC重配置消息2携带的用于指示UE释放DRB和逻辑信道的释放信息包括DRB释放信息和逻辑信道释放信息。其中，DRB释放信息可以包括每一个需要释放的DRB的身份(Identity)信息(如标识号)，逻辑信道释放信息可以包括每一个需要释放的逻辑信道的身份(Identity)信息(如标识号)。
根据现有的标准协议的规定，DRB和逻辑信道之间存在一一对应的关系。因此，RRC重配置消息2中携带的DRB释放信息指示的要释放的DRB的数量和逻辑信道释放信息指示的要释放的逻辑信道的数量需要相同，并且要释放的DRB和要释放的逻辑信道满足添加环节时配置的对应关系的情况下，基于RRC重配置消息2进行的RRC重配置才能成功。例如，在添加环节时配置的DRB和逻辑信道的对应关系如图6所示的情况下，若释放环节需要释放的DRB分别是DRB 4、DRB 5和DRB 6时，逻辑信道释放信息指示要释放的逻辑信道需要是逻辑信道3、逻辑信道4和逻辑信道5。这种情况下，要释放的DRB和逻辑信道才是匹配的。否则，要释放的DRB和逻辑信道不匹配。
示例性的，在本申请的一些实施例中，释放信息可以配置在RRC重配置消息中指定的字段，如DRB释放信息配置在drb-ToReleaseList字段中，逻辑信道释放信息配置在rlc-BearerToReleaseList字段中。
示例性的，在要释放的DRB和逻辑信道匹配的情况下，如图7中(1)所示，drb-ToReleaseList字段中配置的DRB释放信息指示释放DRB 5、DRB 4和DRB 6，rlc-BearerToReleaseList字段中配置的逻辑信道释放信息指示释放逻辑信道3、逻辑信道4和逻辑信道5，根据上述添加环节配置的对应关系，UE对RRC重配置消息2校验成功，根据现有协议标准的规定，UE可以根据释放信息释放DRB和逻辑信道，并向NR CELL A回复RRC重配置完成消息2，即执行步骤S106。
示例性的，在要释放的DRB和逻辑信道不匹配的情况下，如图7中(2)所示，drb-ToReleaseList字段中配置的DRB释放信息指示释放DRB 5、DRB 4和DRB 6，而rlc-BearerToReleaseList字段中配置的逻辑信道释放信息只指示释放逻辑信道3，根据上述添加环节配置的对应关系，UE对RRC重配置消息2校验失败，根据现有协议标准的规定，UE可以根据释放信息释放DRB和逻辑信道，并触发RRC重建立流程，即执行步骤S107。
S106，UE根据RRC重配置消息2中携带的释放信息，释放DRB和逻辑信道，并向NR CELL A回复RRC重配置完成消息2。
示例性的，UE是向NR CELL A中下发RRC重配置消息2的gNB回复RRC重配置完成消息2。
示例性的，RRC重配置完成消息2用于告知下发RRC重配置消息2的gNB，基于RRC重配置消息2进行的RRC重配置(释放DRB和逻辑信道)已完成。
可理解地，在基于RRC重配置消息2进行的RRC重配置完成的情况下，UE驻留在NR CELL A进行的通话依旧可以正常进行，直到主叫方的UE或者被叫方的UE触发挂机操作，如按下UE用户界面中挂断通话的按钮，当前通话才会结束。
S107，UE根据RRC重配置消息2中携带的释放信息，释放DRB和逻辑信道，并触发RRC重建立流程。
关于RRC重配置失败，触发RRC重建立流程的具体实现细节，可以参见图4所示实施例的描述部分，此处不再赘述。
根据现有的标准协议的规定，RRC重配置失败，触发RRC重建立流程，重新建立UE与网络侧之间的RRC连接后，原基站会认为与UE之间的RRC连接存在异常。对于这种情况，网络侧，即原基站不会下发配置DRB和逻辑信道的信息，如不会重新下发指示UE添加/修改/释放DRB和逻辑信道的RRC重配置消息。相应地，UE没有接收到网络侧下发的RRC重配置消息，便无法恢复承载，如无法配置通话所需的DRB和逻辑信道。
由于UE和网络侧之间的承载没有恢复，因此UE无法向网络侧发送通话过程中产生的语音数据包，也无法从网络侧接收通话过程中产生的语音数据包，即当前通话没有声音。根据现有的标准协议的规定，在第一时长(T1时长)内没有声音，会触发超时掉话，进而中断在NR CELL A中进行的通话。
示例性的，第一时长，例如为20秒(s)。
示例性的，在第一时长内没有声音，触发的超时掉话，例如为NR CELL A的gNB向UE下发了释放当前通话的BYE消息。为了区分，这种情况下结束的通话可以理解为异常结束场景或者中断场景。
通过上述针对图5所示场景的描述可知，在RRC重配置消息中携带的指示UE释放的DRB和逻辑信道未按照标准协议的规定配置，导致要释放的DRB和逻辑信道不匹配的情况下，会因为RRC重配置消息校验失败，导致RRC重配置失败，进而触发RRC重建立流程，中断当前进行的通话。
有鉴于此，本申请一些实施例提供了一种降低掉话率的方法，旨在使UE在网络侧未完全按照现有的标准协议来配置要释放的DRB和逻辑信道的情况下，完成RRC重配置，使得当前进行的通话不会被中断，降低通话故障，提升用户体验。
为了更好地理解这种降低掉话率的方法，在图5所示场景的基础上，引入该降低掉话率的方法。以下结合图8和图9对这种降低掉话率的方法的具体实现进行说明。
在对图8和图9所示实施例提供的降低掉话率的方法进行说明前，先对这两种实施例中涉及的一些描述进行说明。
具体地，在图8和图9所示实施例中，均以要释放的DRB和逻辑信道已经按照现有的标准协议的规定，以一一对应的强绑定关系，添加成功这一前提为例。
示例性的，已经按照现有的标准协议的规定，以一一对应的强绑定关系，添加成功的DRB和逻辑信道，例如为图6所示数量和关系的DRB和逻辑信道。即，在接收到指示UE释放DRB和逻辑信道的RRC重配置消息前，UE已经添加了DRB 4、DRB 5和DRB 6，以及逻辑信道3、逻辑信道4和逻辑信道5，并且DRB 4和逻辑信道3一一对应，DRB 5和逻辑信道4一一对应，DRB 6和逻辑信道5一一对应。
关于添加DRB和逻辑信道的具体实现细节，可以参见图5所示实施例中步骤S101至步骤S103的描述部分，此处不再赘述。
此外，需要说明的是，在图8和图9所示实施例中，UE可以是主叫方UE，也可以是被叫方UE。
此外，还需要说明的是，在图8和图9所示实施例中，UE驻留的小区以5G小区为例。
参见图8，本申请实施例提供的降低掉话率的方法，具体包括：
S201，UE驻留在NR CELL A进行第一通话的过程中，接收到NR CELL A发送的第一RRC重配置消息。
示例性的，UE接收到的第一RRC重配置消息为NR CELL A对应的gNB下发的。
示例性的，下发第一RRC重配置消息的gNB为NR CELL A中，与UE建立RRC连接，进行通话的gNB。
示例性的，第一RRC重配置消息携带了第一释放信息。
示例性的，第一释放信息包括指示UE释放PDCP层对应的DRB的第一DRB释放信息，以及指示UE释放RLC层对应的第一逻辑信道释放信息。
在本申请的实施例中，第一DRB释放信息指示UE释放DRB 4、DRB 5和DRB 6。第一逻辑信道释放信息指示UE释放逻辑信道3。
S202，UE根据第一RRC重配置消息中的第一释放信息，确定要释放的DRB和逻辑信道不匹配的情况下，根据第一释放信息释放DRB和逻辑信道，并向NR CELL A回复第一RRC重配置完成消息。
示例性的，第一释放信息，如第一DRB释放信息和第一逻辑信道释放信息可以被携带在第一RRC重配置消息的第一字段中，也可以被携带在第一RRC重配置消息的第二字段中。
其中，第一字段，例如为要求配置在其内的释放信息，如第一DRB释放信息和第一逻辑信道信息存在强绑定关系的字段。例如，在添加环节配置了DRB 4与逻辑信道3一一对应，DRB 5与逻辑信道4一一对应，DRB 6与逻辑信道5一一对应的情况下，根据现有的标准协议的对第一字段的规定，在第一字段中配置的第一DRB释放信息指示UE释放DRB 4、DRB 5和DRB 6的情况下，第一字段中配置的第一逻辑信道释放信息需要指示UE释放逻辑信道3、逻辑信道4和逻辑信道5才符合要求。
示例性的，第一字段例如为小区组配置(CellGroupConfig)字段。即，配置在drb-ToReleaseList字段中的第一DRB释放信息和配置在rlc-BearerToReleaseList字段中的第一逻辑信道释放信息均被携带在CellGroupConfig字段中。
关于现有的标准协议对CellGroupConfig字段的规定，可以参见3GPP协议38.331中第5.3.5.6.4章节对DRB release的规定。下述为从该标准协议中截取的部分内容“The UE shall：
1>for each drb-Identity value included in the drb-ToReleaseList that is part of the current UE configuration；or
1>for each drb-Identity value that is to be released as the result of full configuration according to 5.3.5.11：
2>release the PDCP entity and the drb-Identity；
2>if SDAP entity associated with this DRB is configured：
3>indicate the release of the DRB to SDAP entity associated with this DRB(TS 37.324[24],clause 5.3.3)；
2>if the DRB is associated with an eps-BearerIdentity：
3>if a new bearer is not added either with NR or E-UTRA with same eps-BearerIdentity：
4>indicate the release of the DRB and the eps-BearerIdentity of the released DRB to upper layers.
NOTE 1：The UE does not consider the message as erroneous if the drb-ToReleaseList includes any drb-Identity value that is not part of the current UE configuration.
NOTE 2：Whether or not the RLC and MAC entities associated with this PDCP entity are reset or released is determined by the CellGroupConfig”。
也就是说，若严格按照现有的标准协议的规定，在第一释放信息被携带在CellGroupConfig字段的情况下，第一DRB释放信息指示UE要释放的DRB和第一逻辑信道释放信息指示UE要释放的逻辑信道数量是相同的，并且要释放的DRB和逻辑信道一一对应。但在一些实现场景中，可能存在网络侧未完全按照现有的标准协议的规定，配置被携带在CellGroupConfig字段中的第一释放信息，即存在第一DRB释放信息指示UE要释放的DRB和第一逻辑信道释放信息指示UE要释放的逻辑信道数量不相同，如果要释放的DRB为DRB 4、DRB 5和DRB 6这3个DRB，而要释放的逻辑信道只有与DRB 4对应的逻辑信道3这1个逻辑信道。这就导致要释放的DRB和逻辑信道不匹配。
由于根据第一DRB释放信息，释放DRB 4、DRB 5和DRB 6后，这3个DRB已经是不可用的状态了，所以释放DRB 4、DRB 5和DRB 6后，与DRB 4、DRB 5和DRB 6分别对应的逻辑信道3、逻辑信道4和逻辑信道5也就无法访问使用了。因此，在本申请的一些实施例中，UE在根据第一RRC重配置消息中的第一RRC释放信息，确定要释放的DRB和逻辑信道不匹配的情况下，可以忽略该不匹配情况，即不对第一RRC重配置消息中的第一释放信息进行强校验(不遵循现有的标准协议对CellGroupConfig字段中配置的第一释放信息的规定)，进而促使UE基于第一RRC重配置消息完成RRC重配置。这样，UE就可以向NR CELL A回复第一RRC重配置完成消息，进而告知NR CELL A，基于第一RRC重配置消息进行的RRC重配置已完成。
示例性的，在本申请的另一些实现方式中，UE在根据第一RRC重配置消息中的第一RRC释放信息，确定要释放的DRB和逻辑信道不匹配的情况下，也可以不忽略该不匹配情况，即对第一RRC重配置消息中的第一释放信息进行强校验(遵循现有的标准协议对CellGroupConfig字段中配置的第一释放信息的规定)，进而触发RRC重建立流程。关于因为要释放的DRB和逻辑信道不匹配，导致RRC重配置失败，触发RRC重建立流程，释放第一通话的场景，UE可以按照图10所示实施例提供的降低掉话率的方法，进行后续处理。关于该实现方式的具体细节，可以参见图10所示实施例的描述部分，此处暂不赘述。
其中，第二字段为与第一字段不相同的字段，例如为不要求配置在其内的释放信息，如第一DRB释放信息和第一逻辑信道信息存在强绑定关系的字段。即，在第一释放信息被携带在第二字段的场景中，第二字段中配置的第一DRB释放信息和第一逻辑信道释放信息不存在强绑定关系。
示例性的，第二字段例如为主小区组(masterCellGroup)字段。即，配置在drb-ToReleaseList字段中的第一DRB释放信息和配置在rlc-BearerToReleaseList字段中的第一逻辑信道释放信息均被携带在masterCellGroup字段中。其中，masterCellGroup字段可以用来携带cellGroupId、rlc-BearerToAddModList、mac-CellGroupConfig、physicalCellGroupConfig等内容。
关于现有的标准协议对masterCellGroup字段的规定，具体可以参见3GPP协议38.311中第6.3.2章节的内容，此处不再赘述。
也就是说，在第一释放信息被携带在masterCellGroup字段的场景中，UE可以不对第一RRC重配置消息中的第一释放信息进行强校验。这样，不论要释放的DRB和逻辑信道是否匹配，UE均可以基于第一RRC重配置消息完成RRC重配置，进而向NR CELL A回复第一RRC重配置完成消息，以告知NR CELL A，基于第一RRC重配置消息进行的RRC重配置已完成。
此外，需要说明的是，在本申请的一些实施例中，UE根据第一RRC重配置消息中的第一释放信息，确定要释放的DRB和逻辑信道不匹配的情况下，可以根据第一DRB释放信息释放DRB，根据第一逻辑信道释放信息释放第一逻辑信道。即，根据接收到的第一RRC重配置消息中携带的第一DRB释放信息和第一逻辑信道信息来进行DRB和逻辑信道的释放处理。
此外，还需要说明的是，在本申请的另一些实施例中，UE根据第一RRC重配置消息中的第一释放信息，确定要释放的DRB和逻辑信道不匹配的情况下，可以根据第一DRB释放信息释放DRB，并根据添加环节中设置的DRB和逻辑信道的对应关系，释放与第一DRB释放信息指示要被释放的DRB对应的第一逻辑信道，从而降低UE的功耗，以及对逻辑信道资源的占有，便于网络侧能够将这些逻辑信道进行重新分配。
由此，通过设置UE不对网络侧下发的RRC重配置消息中的释放信息，如上述实施例所说的第一RRC重配置消息中第一释放信息进行强校验，在需要释放的DRB和逻辑信道不匹配的情况下，忽略该不匹配情况，促使UE完成RRC重配置。这样，当前进行的第一通话就不会被中断，UE就可以继续驻留在当前所在小区，如NR CELL A中进行第一通话，达到了降低通话故障，保障通话质量，提升用户体验的效果。
参见图9，本申请实施例提供的降低掉话率的方法，具体包括：
S301，UE驻留在NR CELL A进行第一通话的过程中，接收到NR CELL A发送的第一RRC重配置消息。
S302，UE根据第一RRC重配置消息中的第一释放信息，确定要释放的DRB和逻辑信道不匹配的情况下，根据第一释放信息释放DRB和逻辑信道，并向NR CELL A回复第一RRC重配置完成消息。
本申请实施例中的步骤S301和步骤S302与图8所示实施例中的步骤S201和步骤S202相类似，具体实现细节可以参见步骤S201和步骤S202的描述部分，此处不再赘述。
S303，UE根据第一RRC重配置消息中的第一释放信息，确定要释放的DRB和逻辑信道不匹配的情况下，记录异常次数。
示例性的，UE驻留在NR CELL A首次进行通话时，可以初始化一个异常次数N。如将N设置为0，即N在初始情况下，对应的初始值为0。这样，在进行通话的过程中，在每一次根据接收到的RRC重配置消息中的释放信息，确定要释放的DRB和逻辑信道不匹配时，对N进行自加处理，即设置N＝N+1。
可理解地，“＝”前的N为本次需要与第一异常阈值，如K1进行比较的异常次数，“＝”后的N为本次进行累计处理前记录的异常次数，如初始值。
此外，还应当理解地是，上述关于N的初始值的设置，仅是为了更好地理解本实施例的技术方案而列举的示例，不作为对本实施例的唯一限制。
此外，需要说明的是，步骤S302和步骤S303可以不区分先后执行顺序。即，UE在确定第一RRC重配置消息中携带的第一DRB释放信息和第一逻辑信道释放信息不匹配的情况，可以同时触发根据第一释放信息释放DRB和逻辑信道，并向NR CELL A回复第一RRC重配置完成消息，以及记录异常次数的操作。
S304，在累计的N大于第一异常阈值(K1)的情况下，UE将NR CELL A的标识信息添加到异常小区名单，设置NR CELL A的异常时长为第二时长(T2时长)，并设置第三时长(T3时长)内禁止访问NR CELL A。
其中，异常小区名单为该UE本地维护的名单。这样，在后续的使用场景中，UE通过确定当前驻留的小区是否为异常小区名单中记录的小区，就可以决定是否在当前驻留的小区进行语音通话业务。
示例性的，K1例如可以设置为1。这样，在首次出现要释放的DRB和逻辑信道不匹配的情况下，就可以及时对出现该问题的小区进行标记。
示例性的，T2可以大于T3。
示例性的，T2例如为2天。例如，在2天内，NR CELL A的标识记录在异常小区名单中，2天后，NR CELL A的标识可以从异常小区名单中剔除。
示例性的，T3例如为5分钟(min)。这样，在正常结束第一通话后，在5min内UE禁止访问NR CELL A。即，为异常小区设置的禁止访问时间从UE结束在该小区的通话后生效。
示例性的，在一些实施例中，UE完成步骤S302，正常结束第一通话后，可以通过选择一个正常的小区，如没有被记录在异常小区名单中的小区进行驻留，例如驻留到NR CELL B。这样，在T3时长内，UE就不会驻留在NR CELL A进行新的通话，从而避免短时间内NR CELL A再次下发不合理的RRC重配置消息，如下发携带指示UE要释放的DRB和逻辑信道不匹配的释放信息的RRC重配置消息。
示例性的，在一些实施例中，T3时长后，UE可以重新驻留到NR CELL A，也可以停留在其他小区。本申请实施例以T3时长后，UE重新驻留到NR CELL A为例。
应当理解地是，上述K1、T2、T3的取值仅是为了更好地理解本实施例的技术方案而列举的示例，不作为对本实施例的唯一限制。
S305，在正常结束第一通话，T3时长后UE重新驻留到NR CELL A，但NR CELL A还处于异常时长内的情况下，UE驻留在NR CELL A中进行第二通话的过程中，接收到NR CELL A发送的第二RRC重配置消息。
即，在正常结束第一通话后，在超过T3时长，但在T2时长内，UE重新驻留在该被记录在异常小区名单中的NR CELL A进行新的通话，如第二通话的过程中，接收到了NR CELL A发送的第二RRC重配置消息。
示例性的，第二RRC重配置消息携带了第二释放信息。
示例性的，第二释放信息包括指示UE释放PDCP层对应的DRB的第二DRB释放信息，以及指示UE释放RLC层对应的第二逻辑信道释放信息。
在本申请的实施例中，以接收到第二RRC重配置消息前，UE已经按照现有的标准协议的规定，以一一对应的强绑定关系，添加成功的DRB和逻辑信道，例如为图6所示数量和关系的DRB和逻辑信道，并且第二RRC重配置消息中携带的第二释放信息与第一RRC重配置消息中携带的第一释放信息相同为例。
S306，UE根据第二RRC重配置消息中的第二释放信息，确定要释放的DRB和逻辑信道不匹配的情况下，根据第二释放信息释放DRB和逻辑信道，并向NR CELL A回复第二RRC重配置完成消息。
本申请实施例中的步骤S306与步骤S202相类似，具体实现细节可以参见步骤S202的描述部分，此处不再赘述。
S307，UE根据第二RRC重配置消息中的第二释放信息，确定要释放的DRB和逻辑信道不匹配的情况下，对异常次数N进行累计处理。
即，执行N＝N+1的操作。其中，“＝”前的N为本次需要与第二异常阈值，如K2进行比较的异常次数，“＝”后的N为本次进行累计处理前记录的异常次数。
此外，需要说明的是，步骤S306和步骤S307可以不区分先后执行顺序。即，UE在确定第二RRC重配置消息中携带的第二DRB释放信息和第二逻辑信道释放信息不匹配的情况，可以同时触发根据第二释放信息释放DRB和逻辑信道，并向NR CELL A回复第二RRC重配置完成消息，以及记录异常次数的操作。
S308，在累计的N大于第二异常阈值的情况下，UE设置第四时长(T4时长)内禁止访问NR CELL A。
示例性的，K2例如可以设置为5。
示例性的，T4可以大于T3，小于或等于T2。例如，在T2为2天，T3为5min的情况下，T4可以为1天、30小时(h)、2天等。
示例性的，在本申请的一些实施例中，在累计的N大于第二异常阈值的情况下，UE可以将异常小区名单中为NR CELL A设置的异常时长，从T2修改为T5(T5大于T2)。
示例性的，T5例如为7天。对于这种情况，T4可以大于T3，小于或等于T5。
应当理解地是，上述K2、T4、T5的取值仅是为了更好地理解本实施例的技术方案而列举的示例，不作为对本实施例的唯一限制。
由此，通过设置UE不对网络侧下发的RRC重配置消息中的释放信息进行强校验，在需要释放的DRB和逻辑信道不匹配的情况下，忽略该不匹配情况，促使UE完成RRC重配置。并记录因为要释放的DRB和逻辑信道不匹配出现的异常次数，采用异常小区惩罚机制(如首次出现该异常，将该小区添加到异常小区名单，并设置对应的异常时长，以及一个较短的禁止访问时长，在后续再次出现该类异常，并且异常次数大于一定次数后，加重惩罚，如设置一个较长的禁止访问时长)，避免事后短时间内再进入该小区，从而既可以保证当前进行的通话不会被中断，又可以降低后续UE驻留在该小区的概率，使得通话能够尽可能发生在正常小区(不是异常小区名单中的小区)，例如在T4时长内，UE可以通过没有被记录在异常小区名单中的NR CELL B对应的gNB进行第三通话，进一步降低了通话故障，保障了通话质量，提升了用户体验。
可理解地，在本申请的一些实施例中，NR CELL A可以称为第一小区，NR CELL B可以称为第二小区。
此外，本申请一些实施例还提供了一种降低掉话率的方法，旨在降低UE驻留在异常小区(未完全按照现有的标准协议来配置要释放的DRB和逻辑信道的小区)的概率，从而保证进行的通话能够尽可能发生在正常小区(完全按照现有的标准协议来配置要释放的DRB和逻辑信道的小区)，使得通话能够正常进行，降低通话故障，提升用户体验。
为了更好地理解这种降低掉话率的方法，在图5所示场景的基础上，引入该降低掉话率的方法。以下结合图10对这种降低掉话率的方法的具体实现进行说明。
在对图10所示实施例提供的降低掉话率的方法进行说明前，先对这种实施例中涉及的一些描述进行说明。
具体地，在图10所示实施例中，仍以要释放的DRB和逻辑信道已经按照现有的标准协议的规定，以一一对应的强绑定关系，添加成功这一前提为例。
示例性的，已经按照现有的标准协议的规定，以一一对应的强绑定关系，添加成功的DRB和逻辑信道，例如为图6所示数量和关系的DRB和逻辑信道。即，在接收到指示UE释放DRB和逻辑信道的RRC重配置消息前，UE已经添加了DRB 4、DRB 5和DRB 6，以及逻辑信道3、逻辑信道4和逻辑信道5，并且DRB 4和逻辑信道3一一对应，DRB 5和逻辑信道4一一对应，DRB 6和逻辑信道5一一对应。
关于添加DRB和逻辑信道的具体实现细节，可以参见图5所示实施例中步骤S101至步骤S103的描述部分，此处不再赘述。
此外，需要说明的是，在图10所示实施例中，UE可以是主叫方UE，也可以是被叫方UE。
此外，还需要说明的是，在图10所示实施例中，仍以UE驻留的小区为5G小区为例。
参见图10，本申请实施例提供的降低掉话率的方法，具体包括：
S401，UE驻留在NR CELL A进行第一通话的过程中，接收到NR CELL A发送的第一RRC重配置消息。
本申请实施例中的步骤S401与图8所示实施例中的步骤S201相类似，具体实现细节可以参见步骤S201的描述部分，此处不再赘述。
S402，UE根据第一RRC重配置消息中的第一释放信息，确定要释放的DRB和逻辑信道不匹配的情况下，根据第一释放信息释放DRB和逻辑信道，并触发RRC重建立流程。
本申请实施例中的步骤S402与图5所示实施例中的步骤S107相类似，具体实现细节可以参见步骤S107的描述部分，此处不再赘述。
S403，UE根据第一RRC重配置消息中的第一释放信息，确定要释放的DRB和逻辑信道不匹配的情况下，记录异常次数。
需要说明的是，步骤S402和步骤S403可以不区分先后执行顺序。即，UE在确定第一RRC重配置消息中携带的第一DRB释放信息和第一逻辑信道释放信息不匹配的情况，可以同时触发根据第一释放信息释放DRB和逻辑信道，并向NR CELL A回复第一RRC重配置完成消息，以及记录异常次数的操作。
S404，累计的N大于第一异常阈值(K1)的情况下，UE将NR CELL A的标识信息添加到异常小区名单，设置NR CELL A的异常时长为第二时长(T2时长)，并设置第三时长(T3时长)内禁止访问NR CELL A。
本申请实施例中的步骤S403和步骤S404，与图9所示实施例中的步骤S303和步骤S304相类似，具体实现细节可以参见步骤S303和步骤S304的描述部分，此处不再赘述。
S405，在第一通话被中断后，NR CELL A还处于异常时长内的情况下，UE驻留在NR CELL A中进行第二通话的过程中，接收到NR CELL A发送的第二RRC重配置消息。
即，在第一通话因为第一RRC重配置失败，触发RRC重建立，导致通话异常结束后，在T3时长后，T2时长内，UE驻留在该被记录在异常小区名单中的NR CELL A进行新的通话，如第二通话的过程中，接收到了NR CELL A发送的第二RRC重配置消息。
本申请实施例中步骤S405接收到的第二RRC重配置消息，与图9所示实施例中步骤S305中接收到的第二RRC重配置消息相同，关于第二RRC重配置消息的描述，可以参见步骤S305的描述部分，此处不再赘述。
S406，UE根据第二RRC重配置消息中的第二释放信息，确定要释放的DRB和逻辑信道不匹配的情况下，根据第二释放信息释放DRB和逻辑信道，并触发RRC重建立流程。
本申请实施例中的步骤S406与图5所示实施例中的步骤S107相类似，具体实现细节可以参见步骤S107的描述部分，此处不再赘述。
S407，UE根据第二RRC重配置消息中的第二释放信息，确定要释放的DRB和逻辑信道不匹配的情况下，对异常次数N进行累计处理。
需要说明的是，步骤S406和步骤S407可以不区分先后执行顺序。即，UE在确定第二RRC重配置消息中携带的第二DRB释放信息和第二逻辑信道释放信息不匹配的情况，可以同时触发根据第二释放信息释放DRB和逻辑信道，并向NR CELL A回复第二RRC重配置完成消息，以及记录异常次数的操作。
S408，在累计的N大于第二异常阈值的情况下，UE设置第四时长(T4时长)内禁止访问NR CELL A。
本申请实施例中的步骤S407和步骤S408，与图9所示实施例中的步骤S307和步骤S308相类似，具体实现细节可以参见步骤S307和步骤S308的描述部分，此处不再赘述。
由此，在需要释放的DRB和逻辑信道不匹配的情况下，按照现有的标准协议的规定触发RRC重建立流程，中断当前进行的通话后，记录因为要释放的DRB和逻辑信道不匹配出现的异常次数，采用异常小区惩罚机制(如首次出现该异常，将该小区添加到异常小区名单，并设置对应的异常时长，以及一个较短的禁止访问时长，在后续再次出现该类异常，并且异常次数大于一定次数后，加重惩罚，如设置一个较长的禁止访问时长)，避免事后短时间内再进入该小区，从而可以有效降低UE驻留在异常小区(未完全按照现有的标准协议来配置要释放的DRB和逻辑信道的小区)的概率，保证后续发生的通话能够尽可能发生在正常小区(完全按照现有的标准协议来配置要释放的DRB和逻辑信道的小区)，使得通话业务能够正常进行，达到了降低通话故障，提升用户体验的效果。
此外，需要说明的是，在本申请的各实施例中，UE驻留在5G小区进行的通话，如第一通话、第二通话、第三通话等，可以是采用确认模式(Acknowledged Mode，AM)进行的数据的接收和发送。其中，AM数据收发共用一个实体。故而，在AM下，一个PDCP层的DRB，对应一个RLC层的实体(entity)，对应一个逻辑信道。
关于AM的具体工作原理，可以参见现有的标准协议，此处不再赘述。
此外，关于实现本申请各实施例提供的降低掉话率的方法的终端设备的硬件结构可以如图11所示。
参见图11，终端设备处理器110，外部存储器接口120，内部存储器121，通用串行总线(universal serial bus，USB)接口130，充电管理模块140，电源管理模块141，电池142，天线1，天线2，移动通信模块150，无线通信模块160，音频模块170，扬声器170A，受话器170B，麦克风170C，耳机接口170D，传感器模块180，按键190，马达191，指示器192，摄像头193，显示屏194，以及用户标识模块(subscriber identification module，SIM)卡接口195等。
可以理解的是，本申请实施例示意的结构并不构成对终端的具体限定。在另一些实施例中，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
其中，天线1和天线2用于发射和接收电磁波信号。终端设备中的每个天线可用于覆盖单个或多个通信频带。不同的天线还可以复用，以提高天线的利用率。例如：可以将天线1复用为无线局域网的分集天线。在另外一些实施例中，天线可以和调谐开关结合使用。
具体到本申请各实施例中，基站，如上述实施例中所说的gNB，向终端设备这一UE发送的消息，如第一RRC重配置消息、第二RRC重配置消息等，可以通过天线1或天线2实现接收。
相应地，终端设备向gNB发送的消息，如第一RRC重配置完成消息、第二RRC重配置完成消息、触发RRC重建立流程中向gNB发送的消息等，可以通过天线1或天线2实现发送。
其中，移动通信模块150可以提供应用在终端设备上的包括2G/3G/4G/5G等无线通信的解决方案。移动通信模块150可以包括至少一个滤波器，开关，功率放大器，低噪声放大器(low noise amplifier，LNA)等。无线通信模块160可以提供应用在终端设备上的包括无线局域网(wireless local area networks，WLAN)(如无线保真(wireless fidelity，Wi-Fi)网络)，蓝牙(bluetooth，BT)，全球导航卫星系统(global navigation satellite system，GNSS)，调频(frequency modulation，FM)，近距离无线通信技术(near field communication，NFC)，红外技术(infrared，IR)等无线通信的解决方案。
示例性的，在一些实施例中，可设置终端设备的天线1和移动通信模块150耦合，天线2和无线通信模块160耦合。从而使得终端设备可以通过移动通信技术或无线通信技术与网络以及其他设备通信。
继续参见图11，示例性的，对于终端设备的音频模块170，可包括扬声器170A、受话器170B、麦克风170C、耳机接口170D等。
示例性的，终端设备可以通过音频模块170中的扬声器170A、受话器170B、麦克风170C、耳机接口170D，以及应用处理器等实现音频功能，例如音乐播放，录音、以及本申请各实施例中所说的语音通话业务等。
此外，关于终端设备中的传感器模块180，在一些实施例中可以包括：压力传感器、陀螺仪传感器、气压传感器、磁传感器、加速度传感器、距离传感器、接近光传感器、指纹传感器、温度传感器、触摸传感器、环境光传感器、骨传导传感器等，此处不再一一列举，本申请对此不做限制。
此外，需要说明的是，在一些实施例中，处理器110可以包括一个或多个处理单元，例如：处理器110可以包括应用处理器(application processor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，控制器，存储器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-network processing unit，NPU)等。
可理解地，在具体实现中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
需要说明的，具体到实际应用中，终端设备可通过AP 110A和Modem 110B这两个处理单元，实现本申请各实施例提供的技术方案。例如，通过AP实现响应于用户发起的呼叫请求，进而调用如图12中示出的应用程序框架层中与呼叫业务相关的服务，以及内核层中对应的驱动，将呼叫请求交由Modem。Modem便可以与网络侧进行交互进而建立通话。相应地，在进行通话的过程中，Modem便可以根据本申请各实施例提供的降低掉话率的方法中涉及的处理逻辑，与网络侧进行交互。具体实现细节，可以参加上述实施例，此处不再赘述。
此外，还可理解地，处理器110中包括的控制器这一处理单元，可以是终端设备的神经中枢和指挥中心。在实际应用中，控制器可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。
此外，处理器110中的存储器主要用于存储指令和数据。在一些实施例中，处理器110中的存储器为高速缓冲存储器。
此外，关于图11中示出的USB接口130是符合USB标准规范的接口，具体可以是Mini USB接口，Micro USB接口，USB Type C接口等。
充电管理模块140用于从充电器接收充电输入。此外，图11中示出的电源管理模块141用于连接电池142，充电管理模块140与处理器110。电源管理模块141接收电池142和/或充电管理模块140的输入，为处理器110，内部存储器121，外部存储器，显示屏194，摄像头193，和无线通信模块160等供电。终端设备的无线通信功能可以通过天线1，天线2，移动通信模块150，无线通信模块160，调制解调处理器以及基带处理器等实现。
此外，图11中示出的终端设备通过GPU，显示屏194，以及应用处理器等实现显示功能。GPU为图像处理的微处理器，连接显示屏194和应用处理器。GPU用于执行数学和几何计算，用于图形渲染。处理器110可包括一个或多个GPU，其执行程序指令以生成或改变显示信息。
关于，显示屏194具体用于显示图像，视频等。显示屏194包括显示面板，在一些实施例中，终端设备可以包括1个或N个显示屏194，N为大于1的正整数。
此外，终端设备可以通过ISP，摄像头193，视频编解码器，GPU，显示屏194以及应用处理器等实现拍摄功能。其中，摄像头193用于捕获静态图像或视频，在一些实施例中，终端设备可以包括1个或N个摄像头193，N为大于1的正整数。
此外，图11中示出外部存储器接口120可以用于连接外部存储卡，例如Micro SD卡，实现扩展终端设备的存储能力。外部存储卡通过外部存储器接口120与处理器110通信，实现数据存储功能。例如将音乐，视频等文件保存在外部存储卡中。
此外，图11中示出内部存储器121可以用于存储计算机可执行程序代码，所述可执行程序代码包括指令。处理器110通过运行存储在内部存储器121的指令，从而执行终端设备的各种功能应用以及数据处理。
具体地，上述实施例中所说的记录了异常小区的异常小区名单，可以保存在终端设备的内部存储器121中。
此外，图11中示出的马达191，例如可以是振动马达；指示器192可以是指示灯。
此外，图11中示出的SIM卡接口195，可用于连接SIM卡，或者USIM卡。其中，SIM卡可以通过插入SIM卡接口195，或从SIM卡接口195拔出，实现与终端设备的接触和分离。终端设备可以支持1个或N(N为大于1的整数)个SIM卡接口195。即，终端中可以插入多个SIM卡或USIM卡。
此外，还需要说明的是，在上述部件之上，运行有操作系统。例如苹果公司所开发的iOS操作系统，谷歌公司所开发的Android开源操作系统，微软公司所开发的Windows操作系统等。
终端设备的操作系统可以采用分层架构，或事件驱动架构，或微核架构，或微服务架构，或云架构。本申请实施例以分层架构的Android系统为例，示例性说明终端设备的软件结构。需要说明的是，本申请实施例虽然以Android系统为例进行说明，但是其基本原理同样适用于基于iOS或Windows等操作系统的终端设备。
参见图12，示例性示出一种终端设备的软件结构与硬件器件的关系，以及与gNB的交互示意图。
如图12所示，软件结构采用分层架构，分层架构将软件分成若干个层，每一层都有清晰的角色和分工。层与层之间通过软件接口通信。以Android系统，Android系统运行在AP(应用处理器)上为例，在一些实施例中，将Android系统分为五层，从上至下分别为应用程序层，应用程序框架层(Framework)，安卓运行时(Android runtime)和系统库，硬件抽象层(HAL)以及系统内核层(Kernel)。
其中，应用程序层可以包括一系列应用程序包。应用程序包可以包括systemUI(系统UI)、相机、图库、日历、通话、地图、WLAN、蓝牙、音乐、视频、短信息等应用程序(application，APP)。
systemUI用于显示终端设备的界面，如显示SIM卡对应的信号图标、显示通话界面等。
其中，应用程序框架层为应用程序层的应用程序提供应用编程接口(application programming interface，API)和编程框架。在本申请的一些实施例中，这些编程接口和编程框架可以描述为函数。如图12所示，应用程序框架层可以包括窗口管理器、内容提供器、视图系统、电话管理器(telephony)、资源管理器、通知管理器等。
电话管理器用于提供终端设备的通话功能，例如通话状态的管理(包括接通、挂断等)。
继续参见图12，应用程序框架层还可以包括无线通信接口层(Radio Interface Layer，RIL)。
具体到本申请各实施例的通话场景中，调制解调处理器(Modem)可以通过RIL与telephony进行信息交互。
其中，Android Runtime包括核心库和虚拟机。Android Runtime负责安卓系统的调度和管理。
核心库包含两部分：一部分是java语言需要调用的功能函数，另一部分是安卓的核心库。
应用程序层和应用程序框架层运行在虚拟机中。虚拟机将应用程序层和应用程序框架层的java文件执行为二进制文件。虚拟机用于执行对象生命周期的管理，堆栈管理，线程管理，安全和异常的管理，以及垃圾回收等功能。
系统库可以包括多个功能模块。例如：表面管理器(surface manager)，媒体库(Media Libraries)，三维(3D)图形处理库(例如：OpenGL ES)，二维(2D)图形引擎(例如：SGL)等。
其中，内核层是硬件和软件之间的层。内核层可以包括各种驱动，如显示驱动，摄像头驱动，音频驱动，传感器驱动等。
其中，Modem可以包括非接入层(Non-Access Stratum，NAS层)、RRC层、PDCP层、RLC层、介质访问控制层(Medium Access Control Layer，MAC层)和物理(Physical，PHY)层。
示例性的，在本申请的一些实现方式中，可以在Modem的RRC层中设置一个强校验开关。
示例性的，在强校验开关处于关闭状态的情况下，若UE根据接收到的RRC重配置消息，确定需要释放的DRB和逻辑信道不匹配，则可以执行图8所示实施例中的步骤S202，或者执行图9所示实施例中的步骤S302、S306等操作。即在强校验开关处于关闭状态的情况下，设置UE不对网络侧下发的RRC重配置消息中的释放信息进行强校验。这样，在需要释放的DRB和逻辑信道不匹配的情况下，忽略该不匹配情况，就可以促使UE完成RRC重配置，进而保证当前进行的通话不会被中断。
示例性的，在强校验开关处于开启状态的情况下，若UE根据接收到的RRC重配置消息，确定需要释放的DRB和逻辑信道不匹配，则可以执行图10所示实施例步骤S402，以及之后的步骤的操作。即在强校验开关处于开启状态的情况下，UE遵循现有的标准协议，对网络侧下发的RRC重配置消息中的释放信息进行强校验，触发RRC重建立流程，中断当前进行的通话后，记录因为要释放的DRB和逻辑信道不匹配出现的异常次数，对该小区采用异常小区惩罚机制。这样，就可以避免事后短时间内再进入该小区，从而可以有效降低UE驻留在异常小区的概率，保证后续发生的通话能够尽可能发生在正常小区，使得通话业务能够正常进行。
示例性的，在本申请的实施例中，设置于RRC层中的强校验开关仅对UE可见，对用户不可见。即，是在UE出厂前，终端厂商预置到RRC层，并且设置好其开关状态的。
示例性的，在本申请的一些实施例中，强校验开关可以理解为是一个软件开关，或者说软件接口。该强校验开关用于控制UE是否对网络侧下发的RRC重配置消息中用于指示UE释放DRB和逻辑信道的信息进行强校验，即是严格按照现有的标准协议的规定进行校验，还是可以忽略不匹配情况。
示例性的，在本申请的一些实施例中，强校验开关例如为通过软件代码实现的功能模块。
示例性的，在本申请的一些实施例中，强校验开关可以默认处于开启状态。
示例性的，在本申请的一些实施例中，强校验开关可以默认处于关闭状态。
此外，可理解地，Modem中的各层可以是软件模块。
继续参见图12，Modem可以通过天线与基站进行交互，如实现本申请各实施例中接收网络侧下发的第一RRC重配置消息、第二RRC重配置消息，向网络侧发送第一RRC重配置完成消息、第二RRC重配置完成消息、RRC重建立流程中涉及的交互等。
关于第一终端的软件结构就介绍到此，可以理解地是，图12示出的软件结构中的层以及各层中包含的部件，并不构成对第一终端的具体限定。在本申请另一些实施例中，第一终端可以包括比图示更多或更少的层，以及每个层中可以包括更多或更少的部件，本申请不做限定。
此外，可以理解地是，终端设备为了实现上述功能，其包含了执行各个功能相应的硬件和/或软件模块。结合本文中所公开的实施例描述的各示例的算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以结合实施例对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
此外，需要说明的是，在实际的应用场景中由终端设备实现的上述各实施例提供的降低掉话率的方法，也可以由终端设备中包括的一种芯片系统来执行。基于此，本申请实施例还提供了一种芯片系统，该芯片系统可以包括处理器。该芯片系统可以与存储器耦合，使得该芯片系统中的处理器运行时调用该存储器中存储的计算机程序，实现上述终端设备执行的步骤。其中，该芯片系统中的处理器可以是应用处理器(AP)，也可以是非应用处理器，如调制解调处理器(Modem)。
此外，本申请实施例还提供一种计算机可读存储介质，该计算机存储介质中存储有计算机指令，当该计算机指令在终端设备上运行时，使得终端设备执行上述相关方法步骤实现上述实施例中的降低掉话率的方法。
此外，本申请实施例还提供了一种计算机程序产品，当该计算机程序产品在终端设备上运行时，使得终端设备执行上述相关步骤，以实现上述实施例中的降低掉话率的方法。
此外，通过上述描述可知，本申请实施例提供的终端设备、计算机可读存储介质、计算机程序产品或芯片系统均用于执行上文所提供的对应的方法，因此，其所能达到的有益效果可参考上文所提供的对应的方法中的有益效果，此处不再赘述。
此外，还应当理解地是，以上实施例仅用于说明本申请的技术方案，而非对其限制。尽管参照前述实施例对本申请进行了详细地说明，本领域的普通技术人员应当理解，其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换。而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (18)

  1. 一种降低掉话率的方法，其特征在于，应用于终端设备，所述方法包括：
    在第一小区进行第一通话的过程中，接收到所述第一小区对应的基站发送的第一RRC重配置消息；其中，所述第一RRC重配置消息包括第一释放信息，所述第一释放信息包括第一数据无线承载DRB释放信息和第一逻辑信道释放信息，所述第一DRB释放信息指示了要被释放的第一DRB的信息，所述第一逻辑信道释放信息指示了要被释放的第一逻辑信道的信息；
    在所述第一DRB释放信息和所述第一逻辑信道释放信息不匹配的情况下，根据所述第一DRB释放信息释放所述第一DRB，根据所述第一逻辑信道释放信息释放所述第一逻辑信道，并向所述第一小区对应的基站回复第一RRC重配置完成消息。
  2. 根据权利要求1所述的方法，其特征在于，所述终端设备的调制解调处理器中设置了强校验开关；
    所述在所述第一DRB释放信息和所述第一逻辑信道释放信息不匹配的情况下，根据所述第一DRB释放信息释放所述第一DRB，根据所述第一逻辑信道释放信息释放所述第一逻辑信道，并向所述第一小区对应的基站回复第一RRC重配置完成消息，包括：
    在所述强校验开关处于关闭状态，并且所述第一DRB释放信息和所述第一逻辑信道释放信息不匹配的情况下，根据所述第一DRB释放信息释放所述第一DRB，根据所述第一逻辑信道释放信息释放所述第一逻辑信道，并向所述第一小区对应的基站回复所述第一RRC重配置完成消息。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    在所述强校验开关处于开启状态，并且所述第一DRB释放信息和所述第一逻辑信道释放信息不匹配的情况下，根据所述第一DRB释放信息释放所述第一DRB，根据所述第一逻辑信道释放信息释放所述第一逻辑信道，并触发RRC重建立流程。
  4. 根据权利要求1所述的方法，其特征在于，所述第一释放信息被携带在所述第一RRC重配置消息的第一字段中，所述第一字段为标准协议中规定的用于携带所述第一DRB释放信息和所述第一逻辑信道释放信息的字段。
  5. 根据权利要求4所述的方法，其特征在于，所述第一字段为小区组配置CellGroupConfig字段。
  6. 根据权利要求4所述的方法，其特征在于，在所述第一释放信息被携带在所述第一字段的情况下，执行所述在所述第一DRB释放信息和所述第一逻辑信道释放信息不匹配的情况下，根据所述第一DRB释放信息释放所述第一DRB，根据所述第一逻辑信道释放信息释放所述第一逻辑信道，并向所述第一小区对应的基站回复所述第一RRC重配置完成消息的步骤。
  7. 根据权利要求1所述的方法，其特征在于，所述第一释放信息被携带在所述第一RRC重配置消息的第二字段中，所述第二字段与第一字段不相同，所述第一字段为标准协议中规定的用于携带所述第一DRB释放信息和所述第一逻辑信道释放信息的字段。
  8. 根据权利要求7所述的方法，其特征在于，所述第二字段为主小区组masterCellGroup字段。
  9. 根据权利要求7所述的方法，其特征在于，在所述第一释放信息被携带在所述第二字段的情况下，执行所述在所述第一DRB释放信息和所述第一逻辑信道释放信息不匹配的情况下，根据所述第一DRB释放信息释放所述第一DRB，根据所述第一逻辑信道释放信息释放所述第一逻辑信道，并向所述第一小区对应的基站回复所述第一RRC重配置完成消息的步骤。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    在所述第一释放信息被携带在所述第一字段，并且所述第一DRB释放信息和所述第一逻辑信道释放信息不匹配的情况下，根据所述第一DRB释放信息释放所述第一DRB，根据所述第一逻辑信道释放信息释放所述第一逻辑信道，并触发RRC重建立流程；
    其中，在完成所述RRC重建立流程后，在第一时长内未接收到所述RRC重建立流程中接入的小区对应的基站下发的配置第二DRB和第二逻辑信道的消息的情况下，释放所述第一通话。
  11. 根据权利要求1所述的方法，其特征在于，在所述第一小区进行的所述第一通话采用确认模式进行数据的接收和发送。
  12. 根据权利要求1至11任一项所述的方法，其特征在于，所述方法还包括：
    在所述第一DRB释放信息和所述第一逻辑信道释放信息不匹配的情况下，记为一次异常；
    在累计的所述异常的次数，大于第一异常阈值的情况下，将所述第一小区的标识信息添加到异常小区名单，设置所述第一小区的异常时长为第二时长，并在第三时长内禁止访问所述第一小区，所述第二时长大于所述第三时长。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    在所述第二时长内，在所述第一小区进行第二通话的过程中，接收到所述第一小区对应的基站发送的第二RRC重配置消息；其中，所述第二RRC重配置消息包括第二释放信息，所述第二释放信息包括第二DRB释放信息和第二逻辑信道释放信息，所述第二DRB释放信息指示了要被释放的第二DRB的信息，所述第二逻辑信道释放信息指示了要被释放的第二逻辑信道的信息；
    在所述第二DRB释放信息和所述第二逻辑信道释放信息不匹配的情况下，根据所述第二DRB释放信息释放所述第二DRB，根据所述第二逻辑信道释放信息释放所述第二逻辑信道，向所述第一小区对应的基站回复第二RRC重配置完成消息，并累计一次所述异常的次数；
    在累计的所述异常的次数，大于第二异常阈值的情况下，在第四时长内禁止访问所述第一小区，所述第二异常阈值大于所述第一异常阈值，所述第四时长大于所述第三时长。
  14. 根据权利要求1至13任一项所述的方法，其特征在于，在所述第一DRB释放信息指示要被释放的所述第一DRB的数量和所述第一逻辑信道释放信息指示要被释放的所述第一逻辑信道的数量不相同的情况下，所述第一DRB释放信息和所述第一逻辑信道释放信息不匹配。
  15. 根据权利要求1至13任一项所述的方法，其特征在于，在所述第一DRB释放信息指示要被释放的所述第一DRB和所述第一逻辑信道释放信息指示要被释放的所述第一逻辑信道不对应的情况下，所述第一DRB释放信息和所述第一逻辑信道释放信息不匹配。
  16. 一种终端设备，其特征在于，所述终端设备包括：存储器和处理器，所述存储器和所述处理器耦合；所述存储器存储有程序指令，所述程序指令由所述处理器执行时，使得所述终端设备执行如权利要求1至15任意一项所述的降低掉话率的方法。
  17. 一种芯片系统，其特征在于，所述芯片系统包括处理器，所述处理器用于支持终端设备实现如权利要求1至15任意一项所述的降低掉话率的方法。
  18. 根据权利要求17所述的芯片系统，其特征在于，所述处理器包括调制解调处理器。
PCT/CN2025/093188 2024-06-21 2025-05-07 降低掉话率的方法、设备及芯片系统 Pending WO2025260985A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202410814397.1A CN121240261A (zh) 2024-06-21 2024-06-21 降低掉话率的方法、设备及芯片系统
CN202410814397.1 2024-06-21

Publications (1)

Publication Number Publication Date
WO2025260985A1 true WO2025260985A1 (zh) 2025-12-26

Family

ID=98146649

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/093188 Pending WO2025260985A1 (zh) 2024-06-21 2025-05-07 降低掉话率的方法、设备及芯片系统

Country Status (2)

Country Link
CN (1) CN121240261A (zh)
WO (1) WO2025260985A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190306918A1 (en) * 2018-04-02 2019-10-03 Lg Electronics Inc. Method for handling sdap entity in wireless communication system and apparatus therefor
CN113574961A (zh) * 2019-01-10 2021-10-29 三星电子株式会社 用于在无线通信系统中执行通信的方法和装置
CN113709682A (zh) * 2021-08-10 2021-11-26 Oppo广东移动通信有限公司 呼叫处理方法、装置、终端设备及存储介质
CN114557039A (zh) * 2019-10-21 2022-05-27 夏普株式会社 终端装置、基站装置以及方法
CN117135684A (zh) * 2023-04-05 2023-11-28 荣耀终端有限公司 用于通话的方法、设备、芯片系统及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190306918A1 (en) * 2018-04-02 2019-10-03 Lg Electronics Inc. Method for handling sdap entity in wireless communication system and apparatus therefor
CN113574961A (zh) * 2019-01-10 2021-10-29 三星电子株式会社 用于在无线通信系统中执行通信的方法和装置
CN114557039A (zh) * 2019-10-21 2022-05-27 夏普株式会社 终端装置、基站装置以及方法
CN113709682A (zh) * 2021-08-10 2021-11-26 Oppo广东移动通信有限公司 呼叫处理方法、装置、终端设备及存储介质
CN117135684A (zh) * 2023-04-05 2023-11-28 荣耀终端有限公司 用于通话的方法、设备、芯片系统及存储介质

Also Published As

Publication number Publication date
CN121240261A (zh) 2025-12-30

Similar Documents

Publication Publication Date Title
EP4228322B1 (en) Communication system for improving phone call success rate under sa network and user equipment
US12075277B2 (en) Method of processing network slice based congestion, device and system thereof
US12376163B2 (en) 5G SA network-based call method, electronic device, and system
WO2021227615A1 (zh) 一种提升通话质量的方法及终端
WO2021057526A1 (zh) 一种网关设备容灾的方法及通信设备
WO2024066150A1 (zh) 网络回落方法、设备及存储介质
US20260032760A1 (en) Method for call, device, chip system, and storage medium
CN113271588B (zh) 安全密钥同步方法及通信装置
CN115397003A (zh) 注册信息同步方法、装置、设备及介质
CN111556506B (zh) 异常链路的处理方法及设备
CN121240261A (zh) 降低掉话率的方法、设备及芯片系统
CN115066917B (zh) 一种通信方法、装置、可读存储介质和芯片系统
CN116709393B (zh) 蜂窝数据业务激活失败时的恢复方法及电子设备
CN113812201A (zh) 数据传输方法、装置及通信设备
CN118450451B (zh) 小区切换方法及相关设备
US20260081929A1 (en) Communication Method, Communication Apparatus, and Electronic Device
WO2024198414A1 (zh) 通话处理方法和装置
US20250240615A1 (en) PUSH NOTIFICATION MANAGEMENT FOR A RESERVE eSIM CONNECTION
WO2025066583A1 (zh) 信息处理方法、终端设备及芯片系统
US12477316B2 (en) Network slice local switching at a distributed unit
WO2024124949A1 (zh) 通信方法及终端设备
WO2025208942A1 (zh) 一种通信方法、电子设备和可读存储介质
WO2025055620A1 (zh) 语音通话方法、装置和芯片
WO2025138902A1 (zh) 一种随机接入方法和装置
WO2025195047A1 (zh) 通话建立方法和电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25829467

Country of ref document: EP

Kind code of ref document: A1