Abnormal call termination method and related device

Abstract

The present application discloses a method for terminating an abnormal call and a related device, which relates to the field of wireless communications. When an abnormal call occurs at a terminal, the session management network element of the core network determines that the current session between the terminal and the other end is a session based on the IP multimedia subsystem. Based on the session information of the current session, the method further determines the target data flow between the terminal and the other end based on the IP multimedia subsystem, and then actively initiates the termination process of the target data flow, notifying the IP multimedia subsystem to end the current session. When an abnormality occurs in the session based on the IP multimedia subsystem between the terminals, the session management network element actively triggers the termination process of the target data flow, promptly terminates the call between the terminals, and enables the terminals to promptly stop sending data flows, thereby improving user experience and service quality.

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a method for terminating an abnormal call and a related device. Background Art

[0002] IMS (IP Multimedia Subsystem) is an integral component of 5G networks, providing a rich set of multimedia services and widely used in multimedia communications, such as video calls, voice calls, and messaging. It supports the convergence of multiple media formats, including text, voice, images, video, animation, emoticons, and location information. Its functionality is similar to that of a rich media communication tool, meeting the needs of modern communications.

[0003] Currently, when two terminals are communicating through IMS, if an abnormal call occurs on one of the terminals, the call link between the two terminals will not be terminated because the cause of the abnormal call cannot be quickly determined. The other terminal will not receive a response from the other end when continuing to send data streams, thereby reducing the user's network experience. Summary of the Invention

[0004] In view of the above problems, this application provides a method and related device for terminating an abnormal call to achieve the purpose of quickly terminating the call and improving user experience and service quality. The specific solution is as follows:

[0005] The first aspect of the present application provides a method for terminating an abnormal call, which is applied to a session management network element of a core network, comprising:

[0006] In response to an abnormal call signal of the first terminal, determining whether a current session between the first terminal and the second terminal is a session based on the IP multimedia subsystem;

[0007] If yes, determining a target data flow between the first terminal and the second terminal based on the IP multimedia subsystem according to the session information of the current session;

[0008] A termination process for the target data flow is initiated to end the call between the first terminal and the second terminal.

[0009] In a possible implementation, determining whether the current session between the first terminal and the second terminal is a session based on the IP Multimedia Subsystem includes:

[0010] It is determined according to the session identifier of the current session whether the current session is a session based on the IP multimedia subsystem.

[0011] In a possible implementation, determining, based on the session information of the current session, a target data flow between the first terminal and the second terminal based on the IP multimedia subsystem includes:

[0012] Determining a data packet detection rule identifier from a user plane network element according to the session identifier of the current session;

[0013] The target data flow is identified and determined according to the data packet detection rule.

[0014] In a possible implementation, initiating a termination process for the target data flow to end the call between the first terminal and the second terminal includes:

[0015] Execute the deletion process of the target data flow, and send a first deletion notification to the policy control network element to trigger the policy control network element to execute the deletion of policy and billing control rules, and trigger the policy control network element to send a second deletion notification to the IP multimedia subsystem to trigger the IP multimedia subsystem to execute the deletion process of the network resources of the second terminal.

[0016] In a possible implementation, executing a process of deleting the target data stream includes:

[0017] Sending a third deletion notification of the target data flow to the access and mobility management network element, so that the access and mobility management network element sends a deletion message to the second terminal and the base station, triggering the second terminal and the base station to delete the resources associated with the target data flow;

[0018] In response to the first deletion response notification sent by the base station, sending an update notification to the user plane network element to trigger the user plane network element to delete the data packet detection rule;

[0019] The first deletion notification is generated in response to the second deletion response notification sent by the second terminal.

[0020] In a possible implementation, the process of generating the abnormal call signal includes:

[0021] triggering a paging procedure for the first terminal in response to a connection disconnection signal between the first terminal and the core network;

[0022] If, after the paging process is completed, the first terminal and the core network are in a disconnected state, the abnormal call signal is generated.

[0023] In a possible implementation, the process of generating the disconnection signal includes:

[0024] Whether to generate the connection disconnection signal is determined according to the connection status of the interface between the radio access network and the user plane network element.

[0025] A second aspect of the present application provides an abnormal call termination device, which is applied to a session management network element of a core network, including:

[0026] a session category determination module, configured to determine, in response to an abnormal call signal from the first terminal, whether a current session between the first terminal and the second terminal is a session based on the IP multimedia subsystem;

[0027] a data flow determination module configured to determine, when the session category determination module determines that the current session is a session based on the IP multimedia subsystem, a target data flow between the first terminal and the second terminal based on the IP multimedia subsystem according to the session information of the current session; and

[0028] The session termination module is configured to initiate a termination process for the target data stream to terminate the call between the first terminal and the second terminal.

[0029] A third aspect of the present application provides a computer program product comprising computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements the abnormal call termination method of the first aspect or any implementation of the first aspect.

[0030] A fourth aspect of the present application provides an electronic device, comprising at least one processor and a memory connected to the processor, wherein:

[0031] The memory is used to store computer programs;

[0032] The processor is used to execute the computer program so that the electronic device can implement the abnormal call termination method of the above-mentioned first aspect or any implementation method of the first aspect.

[0033] In a fifth aspect, the present application provides a computer storage medium, which carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement the abnormal call termination method of the above-mentioned first aspect or any implementation of the first aspect.

[0034] By means of the above technical solution, the abnormal call termination method provided by the present application, when an abnormal call occurs at a terminal, the core network's session management network element, upon determining that the current session between the terminal and the peer end is an IP multimedia subsystem-based session, further determines the target data stream between the terminal and the peer end based on the IP multimedia subsystem based session information of the current session, then proactively initiates a termination process for the target data stream, notifying the IP multimedia subsystem to terminate the current session. This method enables the session management network element to proactively trigger the termination process for the target data stream when an abnormality occurs in an IP multimedia subsystem-based session between the terminals, promptly terminating the call between the terminals and causing the terminals to promptly stop sending data streams, thereby improving user experience and service quality. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The above and other features, advantages, and aspects of the various embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that the originals and elements are not necessarily drawn to scale.

[0036] Figure 1 A flowchart of a method for terminating an abnormal call provided by this application;

[0037] Figure 2 A flowchart of a session establishment provided for this application;

[0038] Figure 3 Create a flow chart for the proprietary data flow triggered by the network side provided by this application;

[0039] Figure 4 Flowchart of proprietary data stream deletion triggered by the network side provided by this application;

[0040] Figure 5 A flowchart of how the session management network element provided in this application quickly ends a call after detecting a call anomaly;

[0041] Figure 6 Flowchart of proprietary data flow deletion initiated by the session management network element provided in this application;

[0042] Figure 7 N3 connection release flow chart provided for this application;

[0043] Figure 8 A structural diagram of the abnormal call termination device provided by this application;

[0044] Figure 9 This is a structural diagram of the electronic device provided in this application. DETAILED DESCRIPTION

[0045] The following describes the embodiments of the present application in conjunction with the accompanying drawings. The terms used in the implementation methods of the present application are only used to explain the specific embodiments of the present application and are not intended to limit the present application.

[0046] The embodiments of the present application are described below in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0047] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, and this is merely a way of distinguishing the objects of the same attributes when describing them in the embodiments of the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0048] In 5G (5th Generation Mobile Communication Technology) IMS (IP Multimedia Subsystem) call services, the 5G core network plays a key role, collaborating with the IMS to establish and manage IMS call data channels. Key network elements involved in the core network include the PCF (Policy Control Function), the SMF (Session Management Function), and the UPF (User Plane Function). The PCF interacts with the IMS system, processes IMS messages, and generates PCC (Policy and Charging Control) policies, which are then delivered to the SMF. The SMF is responsible for session management and PCC policy implementation, distributing these policies to the UPF, base stations, and terminals in accordance with 3GPP protocols to ensure the establishment of IMS call data channels. The UPF is responsible for user plane management, including identifying and forwarding service data flows. This collaborative work among network elements ensures call management and data transmission in 5G IMS call services. When a terminal conducts a 5G IMS call, the SMF, based on the PCC policies delivered by the PCF, plays a key role: creating IMS-specific QoS flows (Quality of Service flows) for voice and video data transmission for both the calling and called terminals. These traffic control policies ensure high-quality service during the call. After the call, the SMF is also responsible for deleting these IMS-specific QoS flows to free up network resources and ensure efficient resource utilization. This process ensures that the 5G IMS call service provides stable voice and video transmission quality during the call and promptly releases network resources after the call ends.

[0049] Currently, in the 5G core network, when two terminals are talking, for example, between Terminal A and Terminal B, service data is transmitted through the core network. If Terminal B leaves the base station's coverage area, the base station detects that it can no longer provide service and triggers the appropriate process to release the user plane connection between the base station and the UPF. Because Terminal A and the IMS system cannot quickly determine the cause of Terminal B's anomaly, Terminal A may continue to send data streams to Terminal B. However, because Terminal B has lost its connection, Terminal A cannot receive the data. This impacts Terminal A's user experience and reduces the user's network experience.

[0050] In order to solve the above problems, the embodiment of the present application provides a method for terminating an abnormal call. The method for terminating an abnormal call according to the embodiment of the present application is described in detail below with reference to the accompanying drawings.

[0051] Reference Figure 1 , Figure 1 The following is a flow chart of a method for terminating an abnormal call provided in an embodiment of the present application: Figure 1 As shown, an abnormal call termination method provided by an embodiment of the present application may include steps 101 to 103, and these steps are described in detail below.

[0052] 101. In response to an abnormal call signal from a first terminal, determine whether a current session between the first terminal and a second terminal is an IP multimedia subsystem-based session.

[0053] Specifically, refer to Figure 2 The process of establishing a session between terminals in the 5G core network includes:

[0054] Step 1: The terminal initiates a session establishment request, and the message is sent to the AMF (Access and Mobility Management Function) via the base station in the RAN (Radio Access Network).

[0055] Step 2: AMF processes and sends a session establishment request to SMF.

[0056] Step 3: The SMF processes the session establishment request. The terminal indicates in the message whether the current session is an IMS session. The SMF obtains the terminal subscription data from the Unified Data Management (UDM).

[0057] Step 4: SMF subscribes to contract data change notifications so that SMF can be notified in a timely manner when UDM contract data changes.

[0058] Step 5: SMF first replies to AMF with a create response.

[0059] Step 6: SMF interacts with PCF to create PCC policy rules for the session.

[0060] Step 7: SMF interacts with UPF to create a PFCP (Packet Forwarding Control Protocol) session for packet forwarding on the data plane.

[0061] Step 8: SMF replies with a session creation acceptance message to the terminal via AMF; sends a session creation request to the base station, notifying the base station to create session resources.

[0062] Step 9: After the base station session resources are successfully created, a response is sent to SMF via AMF.

[0063] Step 10: SMF notifies UPF to update base station information and open the downlink data channel.

[0064] Step 11: After the terminal session is successfully created, SMF registers with UDM with the terminal information.

[0065] The subsequent creation process of the dedicated service quality data flow triggered by the IMS network side refers to Figure 3 As shown:

[0066] Step 1: IMS notifies the 5G core network to establish a data channel, that is, to create a dedicated QoS FLOW (quality of service data flow).

[0067] Step 2: The SMF receives the PCC policy creation message from the PCF and initiates the dedicated QoS FLOW process. The SMF constructs a message to notify the terminal and base station to create a dedicated QoS FLOW. The message is sent to the terminal and base station via the AMF.

[0068] Step 3: Notify the base station to create dedicated QoS FLOW related resources.

[0069] Step 4: Notify the terminal to create dedicated QoS FLOW related resources.

[0070] Step 5: The base station replies with a dedicated QoS FLOW creation response.

[0071] Step 6: SMF notifies UPF to update the PFCP session and create dedicated QoS FLOW related detection rules.

[0072] Step 7: The terminal responds with a dedicated QoS FLOW creation response.

[0073] In daily usage scenarios, after two terminals access the 5G core network, they complete the IMS session creation and IMS dedicated QoS flow establishment through the above two processes respectively, and then realize IMS calls between the two parties.

[0074] The abnormal call signal here can be a signal generated when the first terminal remains in an abnormal state after triggering the paging process for the first terminal due to a communication anomaly during a call, such as due to a loss of base station coverage. In actual application scenarios, due to the limited coverage of 5G base stations, this problem may occur from time to time, resulting in the failure of paging to terminal B. Due to this situation, terminal A and the IMS system may find it difficult to quickly determine the specific cause of the failure.

[0075] After the above situation occurs at the first terminal, the SMF can determine whether the current session is an IP Multimedia Subsystem-based session based on the terminal identifier, session identifier, etc. in the above IMS session creation process.

[0076] It is understandable that those skilled in the art may also use other well-known means to identify the session category, which will not be described in detail here.

[0077] 102. If yes, determine the target data flow between the first terminal and the second terminal based on the IP multimedia subsystem according to the session information of the current session.

[0078] Specifically, the SMF can determine the dedicated QoS data flow used between the two terminals based on the PDR ID (Packet Detection Rule Identifier) ​​reported by the UPF. In actual scenarios, the SMF can also determine whether the target data flow is a voice-dedicated QoS flow or a video-dedicated QoS flow based on the relationship between the identifier in the message reported by the UPF and the type of dedicated QoS data flow.

[0079] 103. Start a termination process for the target data stream to end the call between the first terminal and the second terminal.

[0080] Specifically, once the SMF confirms that the data flow is an IMS call, it triggers the IMS-specific QoS Flow deletion process and notifies the PCF to delete the IMS-specific PCC rules. Upon receiving the SMF message, the PCF notifies the IMS system to terminate the call. Upon receiving the PCF message, the IMS system identifies the abnormality on Terminal B and triggers the process of deleting the network resources for Terminal A's call, thus terminating the call.

[0081] As can be seen from the above, when two terminals are engaged in a 5G IMS call and one of them loses connection, the 5G core network's SMF network element can promptly detect and initiate the corresponding process to quickly end the abnormal call, significantly improving the user experience. This makes it even more important in some vertical industries that only deploy 5G core networks.

[0082] In a possible implementation, the process of initiating the termination process of the target data flow to end the call between the first terminal and the second terminal specifically includes:

[0083] Execute the deletion process of the target data flow and send a first deletion notification to the policy control network element to trigger the policy control network element to execute the deletion of the policy and billing control rules, and trigger the policy control network element to send a second deletion notification to the IP multimedia subsystem to trigger the IP multimedia subsystem to execute the deletion process of the network resources of the second terminal.

[0084] The target data stream deletion process includes:

[0085] Step 11: Send a third deletion notification of the target data flow to the access and mobility management network element, so that the access and mobility management network element sends a deletion message to the second terminal and the base station, triggering the second terminal and the base station to delete resources associated with the target data flow;

[0086] Step 12: In response to the first deletion response notification sent by the base station, an update notification is sent to the user plane network element to trigger the user plane network element to delete the data packet detection rule;

[0087] Step 13: Generate a first deletion notification in response to the second deletion response notification sent by the second terminal.

[0088] Specifically, refer to Figure 6 The SMF-triggered deletion process of a dedicated quality of service data flow includes:

[0089] Step 1: SMF triggers the QoS FLOW deletion process.

[0090] Step 2: SMF constructs a message to notify the terminal and base station to delete the dedicated QoS FLOW, and the message is sent to the terminal and base station via AMF.

[0091] Step 3: Notify the base station to delete the dedicated QoS FLOW related resources.

[0092] Step 4: Notify the terminal to delete the dedicated QoS FLOW related resources.

[0093] Step 5: The base station replies with a dedicated QoS FLOW deletion response.

[0094] Step 6: SMF notifies UPF to update the PFCP session and delete the proprietary QoS FLOW related detection rules.

[0095] Step 7: The terminal responds with a dedicated QoS FLOW deletion response.

[0096] Step 8: SMF notifies PCF to delete the PCC rules related to the dedicated QoS FLOW.

[0097] Step 9: PCF receives the SMF message and notifies IMS to delete related resources.

[0098] The corresponding reference Figure 4 The following figure shows the deletion process of the proprietary QoS FLOW triggered by the network side after the call ends normally:

[0099] Step 1: When the IMS call ends, the IMS triggers a process to notify the deletion of the resources created during the call, that is, the proprietary QoS FLOW deletion process triggered by the network side.

[0100] Step 2: SMF constructs a message to notify the terminal and base station to delete the dedicated QoS FLOW, and the message is sent to the terminal and base station via AMF.

[0101] Step 3: Notify the base station to delete the dedicated QoS FLOW related resources.

[0102] Step 4: Notify the terminal to delete the dedicated QoS FLOW related resources.

[0103] Step 5: The base station replies with a dedicated QoS FLOW deletion response.

[0104] Step 6: SMF notifies UPF to update the PFCP session and delete the proprietary QoS FLOW related detection rules.

[0105] Step 7: The terminal responds with a dedicated QoS FLOW deletion response.

[0106] By comparison, it can be seen that when two terminals are conducting a 5G IMS call, if one terminal fails to page the terminal, the SMF provided in this application actively initiates the IMS proprietary QoS Flow deletion process, which enables the IMS system to promptly perceive the call abnormality and quickly end the abnormal call, thereby improving the user experience.

[0107] In one possible implementation, to improve the accuracy of abnormal call signal determination, the abnormal call signal generation process may specifically include:

[0108] Step 21: In response to a disconnection signal between the first terminal and the core network, trigger a paging process for the first terminal, wherein whether to generate a disconnection signal can be determined based on the connection status of the interface between the wireless access network and the user plane network element.

[0109] Step 22: If the first terminal and the core network are disconnected after the paging process is completed, an abnormal call signal is generated.

[0110] Specifically, the N3 interface in 5G (full name: NG-U interface‌, which is the interface between RAN and UPF in the 5G core network) can be used to monitor the connection release process of the N3 interface. After monitoring the release process of the N3 interface, a connection disconnection signal can be generated. The N3 connection release process triggered by the base station side is as follows: Figure 7 As shown:

[0111] Step 1: When the base station detects a terminal abnormality or is unable to continue to provide services to it, it triggers the N3 connection release process to release the user plane connection between the base station and the UPF.

[0112] Step 2: The base station initiates N3 resource release.

[0113] Step 3: SMF processes the N3 resource release process, notifies UPF to modify the downlink data forwarding rules, and when receiving downlink data, instructs to cache the data and notifies SMF at the same time to trigger the paging process.

[0114] As a specific application of the above abnormal call termination method, refer to Figure 5 The diagram shows the process from the establishment of a call between two terminals to the abnormal termination of the call by one terminal, including:

[0115] Step 1: First, terminal A and terminal B access the 5G core network, complete the IMS session creation and the establishment of the IMS-specific QoS FLOW flow, ensuring that the two parties are conducting an IMS call.

[0116] Step 2: During the call, due to reasons such as terminal B losing base station coverage, the base station triggers the N3 connection release process, and terminal B disconnects the data plane connection from the core network.

[0117] Step 3: Since terminal A and the IMS system cannot detect the abnormal behavior of terminal B, terminal A continues to send call data streams to terminal B.

[0118] Step 4: When the UPF, which is responsible for data flow identification and forwarding, receives the service data flow sent to terminal B, it finds that its downlink data is blocked. The UPF then notifies the SMF, triggering the corresponding process to page terminal B.

[0119] Step 5: If the paging is successful, it means that terminal B is only temporarily abnormal and the call service can be restored smoothly, and the two parties can continue the call. If the paging fails, it means that terminal B is still in an abnormal state and cannot be restored in a short time.

[0120] Step 6: SMF detects that the call on terminal B is abnormal and triggers the deletion process of the proprietary QoS Flow.

[0121] Step 7: When the SMF confirms that the data flow is IMS call data, it will trigger the IMS-specific QoS Flow deletion process and notify the PCF to delete the IMS-specific PCC rules.

[0122] Step 8: After receiving the message from SMF, PCF will notify the IMS system to end the call.

[0123] Step 9: After receiving the PCF message, the IMS system can identify the abnormal situation of terminal B and trigger the process of deleting the network resources of terminal A's call, thereby ending the call.

[0124] The above describes a method for terminating an abnormal call provided by an embodiment of the present application. The following describes a device for executing the above method for terminating an abnormal call.

[0125] See also Figure 8 , Figure 8 This is a schematic diagram of the structure of an abnormal call termination device provided in an embodiment of the present application. Figure 8 As shown, the abnormal call ending device includes:

[0126] The session category determination module 801 is configured to determine, in response to an abnormal call signal from the first terminal, whether the current session between the first terminal and the second terminal is an IP multimedia subsystem-based session;

[0127] a data flow determination module 802 configured to determine, when the session type determination module determines that the current session is an IP multimedia subsystem-based session, a target data flow between the first terminal and the second terminal based on the IP multimedia subsystem based on the session information of the current session; and

[0128] The session ending module 803 is configured to start a termination process for the target data flow to end the call between the first terminal and the second terminal.

[0129] In one possible implementation, the process of the session type determination module 801 determining whether the current session between the first terminal and the second terminal is a session based on the IP multimedia subsystem includes:

[0130] Determine whether the current session is an IP multimedia subsystem-based session according to the session identifier of the current session.

[0131] In one possible implementation, the process of the data flow determining module 802 determining the target data flow between the first terminal and the second terminal based on the IP multimedia subsystem according to the session information of the current session includes:

[0132] Determine a packet detection rule identifier from a user plane network element based on the session identifier of the current session;

[0133] Identify the target data flow based on the packet detection rule identification.

[0134] In a possible implementation, the session ending module 803 initiates a termination process for the target data stream to end the call between the first terminal and the second terminal, including:

[0135] Execute the deletion process of the target data flow and send a first deletion notification to the policy control network element to trigger the policy control network element to execute the deletion of the policy and billing control rules, and trigger the policy control network element to send a second deletion notification to the IP multimedia subsystem to trigger the IP multimedia subsystem to execute the deletion process of the network resources of the second terminal.

[0136] In a possible implementation, the session ending module 803 executes a process of deleting the target data stream, including:

[0137] Sending a third deletion notification of the target data flow to the access and mobility management network element, so that the access and mobility management network element sends a deletion message to the second terminal and the base station, triggering the second terminal and the base station to delete resources associated with the target data flow;

[0138] In response to the first deletion response notification sent by the base station, an update notification is sent to the user plane network element to trigger the user plane network element to delete the data packet detection rule;

[0139] In response to the second deletion response notification sent by the second terminal, a first deletion notification is generated.

[0140] In a possible implementation, the process of generating the abnormal call signal by the session type determination module 801 includes:

[0141] In response to a connection disconnection signal between the first terminal and the core network, triggering a paging process for the first terminal;

[0142] If the first terminal and the core network are disconnected after the paging process is completed, an abnormal call signal is generated.

[0143] In one possible implementation, the process of generating the disconnection signal in the session type determination module 801 includes:

[0144] Determine whether to generate a connection disconnection signal according to the connection status of the interface between the radio access network and the user plane network element.

[0145] An electronic device is also provided in an embodiment of the present application. Figure 9, which shows a schematic diagram of the structure of an electronic device suitable for implementing the embodiments of the present application. The electronic device in the embodiments of the present application may include, but is not limited to, fixed terminals such as mobile phones, laptops, PDAs (personal digital assistants), PADs (tablet computers), desktop computers, etc. Figure 9 The electronic device shown is merely an example and should not limit the functions and scope of use of the embodiments of the present application.

[0146] like Figure 9 As shown, the electronic device may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 901, which can perform various appropriate actions and processes based on programs stored in a read-only memory (ROM) 902 or programs loaded from a storage device 908 into a random access memory (RAM) 903. When the electronic device is powered on, the RAM 903 also stores various programs and data required for the operation of the electronic device. The processing device 901, ROM 902, and RAM 903 are interconnected via a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0147] Typically, the following devices may be connected to the I / O interface 905: an input device 906 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 907 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 908 including, for example, a memory card, a hard disk, etc.; and a communication device 909. The communication device 909 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. Although Figure 9 The electronic device is shown with various devices, but it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed instead.

[0148] An embodiment of the present application also provides a computer program product including computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements any abnormal call termination method provided in the embodiment of the present application.

[0149] A computer-readable storage medium is also provided in an embodiment of the present application. The storage medium carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement any abnormal call termination method provided in the embodiment of the present application.

[0150] It should also be noted that the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed across multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment. In addition, in the drawings of the device embodiments provided in this application, the connection relationship between the modules indicates that there is a communication connection between them, which can be specifically implemented as one or more communication buses or signal lines.

[0151] Through the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course can also be implemented by special hardware including application-specific integrated circuits, special CPUs, special memories, special components, etc. In general, all functions performed by computer programs can be easily implemented with corresponding hardware, and the specific hardware structures used to implement the same function can also be diverse, such as analog circuits, digital circuits or special circuits, etc. However, for the present application, software program implementation is a better implementation method in most cases. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer's floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk or optical disk, etc., and includes a number of instructions to enable a computer device (which can be a personal computer, training equipment, or network equipment, etc.) to execute the methods described in each embodiment of the present application.

[0152] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0153] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, a computer, a training device or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website, a computer, a training device or a data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a training device, a data center, etc. that includes one or more available media integrations. The available medium can be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

Claims

1. A method for terminating an abnormal call, characterized in that: The session management network element (SMF) used in the 5G core network includes: In response to an abnormal call signal of the first terminal, determining whether a current session between the first terminal and the second terminal is a session based on the IP multimedia subsystem; If yes, determining a target data flow between the first terminal and the second terminal based on the IP multimedia subsystem according to the session information of the current session; Initiate a termination process for the target data flow and send a deletion notification to a policy control network element to end the call between the first terminal and the second terminal; The abnormal call signal generation process includes: In response to a connection disconnection signal between the first terminal and the 5G core network, triggering a paging process for the first terminal; If, after the paging process is completed, the first terminal and the 5G core network are in a disconnected state, the abnormal call signal is generated.

2. The abnormal call termination method according to claim 1, characterized in that: The determining whether the current session between the first terminal and the second terminal is a session based on the IP multimedia subsystem includes: It is determined according to the session identifier of the current session whether the current session is a session based on the IP multimedia subsystem.

3. The abnormal call termination method according to claim 1, characterized in that: The determining, based on the session information of the current session, a target data flow between the first terminal and the second terminal based on the IP multimedia subsystem includes: Determining a data packet detection rule identifier from a user plane network element according to the session identifier of the current session; The target data flow is identified and determined according to the data packet detection rule.

4. The abnormal call termination method according to claim 1, wherein: The initiating a termination process for the target data flow and sending a deletion notification to a policy control network element to end the call between the first terminal and the second terminal includes: Execute the deletion process of the target data flow, and send a first deletion notification to the policy control network element to trigger the policy control network element to execute the deletion of policy and billing control rules, and trigger the policy control network element to send a second deletion notification to the IP multimedia subsystem to trigger the IP multimedia subsystem to execute the deletion process of the network resources of the second terminal.

5. The abnormal call termination method according to claim 4, characterized in that: The process of executing the deletion process of the target data stream includes: Sending a third deletion notification of the target data flow to the access and mobility management network element, so that the access and mobility management network element sends a deletion message to the second terminal and the base station, triggering the second terminal and the base station to delete the resources associated with the target data flow; In response to the first deletion response notification sent by the base station, sending an update notification to the user plane network element to trigger the user plane network element to delete the data packet detection rule; The first deletion notification is generated in response to the second deletion response notification sent by the second terminal.

6. The abnormal call termination method according to claim 1, characterized in that: The process of generating the disconnection signal includes: Whether to generate the connection disconnection signal is determined according to the connection status of the interface between the radio access network and the user plane network element.

7. An abnormal call termination device, characterized in that: The session management network element (SMF) used in the 5G core network includes: a session category determination module, configured to determine, in response to an abnormal call signal from the first terminal, whether a current session between the first terminal and the second terminal is a session based on the IP multimedia subsystem; a data flow determination module configured to determine, when the session category determination module determines that the current session is a session based on the IP multimedia subsystem, a target data flow between the first terminal and the second terminal based on the IP multimedia subsystem according to the session information of the current session; and a session termination module, configured to initiate a termination process for the target data flow and send a deletion notification to a policy control network element to terminate the call between the first terminal and the second terminal; The process of generating an abnormal call signal in the conversation category determination module includes: In response to a connection disconnection signal between the first terminal and the 5G core network, triggering a paging process for the first terminal; If, after the paging process is completed, the first terminal and the 5G core network are in a disconnected state, the abnormal call signal is generated.

8. An electronic device, characterized in that: comprising at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs; The processor is configured to execute the computer program so that the electronic device can implement the abnormal call termination method according to any one of claims 1 to 6.

9. A computer storage medium, characterized in that The storage medium carries one or more computer programs, and when the one or more computer programs are executed by an electronic device, the electronic device can implement the abnormal call termination method according to any one of claims 1 to 6.

Images