Abnormal call ending method and related device

Abstract

The invention discloses an abnormal call ending method and a related device, and relates to the field of wireless communication, when a session management network element of a core network judges that a current session between a terminal and an opposite terminal is a session based on an IP multimedia subsystem when an abnormal call occurs in the terminal, according to session information of the current session, the session information of the current session is sent to the terminal; and further determining a target data stream based on the IP multimedia subsystem between the terminal and the opposite terminal, then actively starting a termination process for the target data stream, and notifying the IP multimedia subsystem to end the current session. When the session between the terminals based on the IP multimedia subsystem is abnormal, the termination process of the target data stream is actively triggered through the session management network element, and the call between the terminals is terminated in time, so that the terminals stop sending of the data stream in time, and the user experience and the service quality are improved.

Description

Technical Field

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

[0002] IMS (IP Multimedia Subsystem) is an indispensable component of 5G networks, providing rich multimedia service functions and widely used in multimedia communications, such as video calls, voice calls, messaging services, etc. It supports the integration of multiple media forms, including text, voice, pictures, videos, animations, emoticons, locations, etc. Its functions are similar to rich media communication tools, meeting the needs of modern communications.

[0003] Currently, when two terminals are talking 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, the present application provides a method and related device for terminating an abnormal call, so as to achieve the purpose of quickly terminating the call and improving the user experience and service quality. The specific scheme is as follows:

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

[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, the 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 whether the current session is a session based on the IP multimedia subsystem according to the session identifier of the current session.

[0011] In a possible implementation, determining, according to 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 determined according to the data packet detection rule identifier.

[0014] In a possible implementation, the 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, the executing a deletion process of 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] In response to a connection disconnection signal between the first terminal and the core network, triggering a paging process for the first terminal;

[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 of 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 used to start a termination process for the target data flow to end the call between the first terminal and the second terminal.

[0029] A third aspect of the present application provides a computer program product, including 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 first aspect or any implementation method of the first aspect.

[0033] A fifth aspect of 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 in a terminal, the session management network element of the core network further determines the target data stream between the terminal and the opposite end based on the IP multimedia subsystem when it is determined that the current session between the terminal and the opposite end is a session based on the IP multimedia subsystem, and then actively starts the termination process of the target data stream, notifying the IP multimedia subsystem to end the current session. When an abnormal session based on the IP multimedia subsystem occurs between terminals, the termination process of the target data stream is actively triggered by the session management network element, the call between the terminals is terminated in time, and the terminals stop sending data streams in time, thereby improving user experience and service quality. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0037] Figure 2 A flow chart 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 The flowchart of the proprietary data stream deletion triggered by the network side provided by this application;

[0040] Figure 5 A flow chart of a session management network element provided in this application for quickly ending a call after detecting an abnormal call;

[0041] Figure 6 A flow chart of proprietary data flow deletion initiated by a 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] Fig. 9 This is a structural diagram of the electronic device provided for this application. DETAILED DESCRIPTION

[0045] The following describes the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. The terms used in the implementation method section 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 need not be 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, which is only to describe the distinction mode adopted by the objects of the same attributes when describing 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 the 5G (5th Generation Mobile Communication Technology) IMS (IP Multimedia Subsystem) call service, the 5G core network plays a key role and works with the IMS to establish and manage the data channel for IMS calls. The key network elements involved in the core network include PCF (Policy Control Function), SMF (Session Management Function) and UPF (User Plane Function). PCF is responsible for interacting with the IMS system, processing IMS messages, and generating PCC (Policy and Charging Control) policies, which are then sent to SMF. SMF is responsible for session management and implementation of PCC policies, and sends policies to UPF, base stations and terminals according to the 3GPP protocol to ensure the establishment of IMS call data channels. UPF is responsible for user plane management, including identifying and forwarding service data flows. The collaborative work between network elements ensures call management and data transmission in the 5G IMS call service. When the terminal performs 5G IMS call services, SMF plays an important role according to the PCC policy issued by PCF: it creates IMS-specific QoS Flow (Quality of Service Flow) for voice and video data transmission for the calling terminal and the called terminal respectively. These traffic control policies ensure high-quality services during the call. After the call, SMF is also responsible for deleting these IMS-specific QoS Flows to release network resources and ensure effective use of resources. The implementation of this process enables the 5G IMS call service to provide stable voice and video transmission quality during the call, and release network resources in time after the call ends.

[0049] Currently in the 5G core network, when two terminals are talking, for example, when terminal A and terminal B are talking, the service data is transmitted through the core network. If terminal B is out of the coverage of the base station, the base station will detect that it can no longer provide services to it, and trigger the corresponding process to release the user plane connection between the base station and UPF. Since terminal A and the IMS system cannot quickly determine the abnormal cause of terminal B, terminal A may continue to send data streams to terminal B, and since terminal B has lost connection, terminal A cannot receive data. As a result, the user experience of terminal A will be affected, reducing 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 in 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 in 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 of a first terminal, determine whether a current session between the first terminal and a second terminal is a session based on an IP multimedia subsystem.

[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: SMF processes the session establishment request. In the message, the terminal will indicate whether the current session is an IMS session. SMF obtains the terminal subscription data from UDM (Unified Data Management).

[0057] Step 4: SMF subscribes to the contract data change notification so that SMF can be notified in time when the 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 to the terminal via AMF with a session creation acceptance message; 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: SMF receives the PCC policy creation message from PCF and initiates the dedicated QoS FLOW process. SMF constructs a message to notify the terminal and base station to create a dedicated QoS FLOW, and the message is sent to the terminal and base station via 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 replies 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 the establishment of the IMS dedicated QoS flow through the above two processes respectively, and then realize the IMS call between the two parties.

[0074] The abnormal call signal here can be a signal generated when the first terminal is still in an abnormal state after triggering the paging process for the first terminal due to abnormal communication caused by the first terminal losing base station coverage during the call. In actual application scenarios, due to the small coverage of 5G base stations, the above problems may occur from time to time, resulting in the failure of paging to terminal B. Due to the occurrence of 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 a session based on the IP Multimedia Subsystem according to 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 based on the IP multimedia subsystem between the first terminal and the second terminal according to the session information of the current session.

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

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

[0080] Specifically, when SMF confirms that the data flow is IMS call data, it will trigger the IMS-specific QoS Flow deletion process and notify PCF to delete the IMS-specific PCC rules. After receiving the message from SMF, PCF will notify the IMS system to end the call. After receiving the message from PCF, the IMS system can identify the abnormal situation of terminal B, and then trigger the process of deleting the network resources of terminal A's call, thereby ending the call.

[0081] From the above, it can be seen that when two terminals are conducting a 5G IMS call, if one of the two parties loses connection, the SMF network element of the 5G core network can detect it in time and start the corresponding process to quickly end the abnormal call, thereby significantly improving the user experience. And it plays a more important role in some vertical industries that only deploy 5G core networks.

[0082] In a possible implementation, the process of starting 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 the 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 the dedicated quality of service data flow shown 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 dedicated QoS FLOW related detection rules.

[0095] Step 7: The terminal replies 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 is the deletion process of the dedicated QoS FLOW triggered by the network side after the call is normally ended:

[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 dedicated 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 dedicated QoS FLOW related detection rules.

[0105] Step 7: The terminal replies 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 other 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 a possible implementation, in order 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 a connection state of an interface between a wireless access network and a 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 the release process of the N3 interface is detected, 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 that the terminal is abnormal or cannot continue to provide services to it, it triggers the N3 connection release process to release the user plane connection between the base station and 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, indicates 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 process from the establishment of a call between two terminals to the abnormal termination of the call by one terminal is shown as follows:

[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 proprietary QoS FLOW flow, and ensure that both 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 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, the call service can be successfully restored, and the two parties continue to talk. 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 the call abnormality of terminal B and triggers the deletion process of the dedicated QoS Flow.

[0121] Step 7: When SMF confirms that the data flow is IMS call data, it triggers the IMS-specific QoS Flow deletion process and notifies 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 message from the PCF, the IMS system can identify the abnormal situation of terminal B, and then trigger the process of deleting the network resources of the call of terminal A, thereby ending the call.

[0124] A method for terminating an abnormal call provided in an embodiment of the present application is introduced above, and a device for executing the above method for terminating an abnormal call will be introduced below.

[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 used to determine whether the current session between the first terminal and the second terminal is a session based on the IP multimedia subsystem in response to the abnormal call signal of the first terminal;

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

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

[0129] In a possible implementation, the process of the session category 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] It is determined whether the current session is a session based on the IP multimedia subsystem according to the session identifier of the current session.

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

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

[0133] The target data flow is identified based on the packet detection rule.

[0134] In a possible implementation, the session termination module 803 initiates a termination process for the target data flow to terminate 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 process of executing the deletion process of the target data flow by the session ending module 803 includes:

[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 the resources associated with the target data flow;

[0138] 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;

[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 category 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 a 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 wireless access network and the user plane network element.

[0145] The present application also provides an electronic device in an embodiment. Fig. 9As shown, it shows a schematic diagram of the structure of an electronic device suitable for implementing the embodiment of the present application. The electronic device in the embodiment 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. Fig. 9 The electronic device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0146] like Fig. 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 according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage device 908 to a random access memory (RAM) 903. When the electronic device is powered on, various programs and data required for the operation of the electronic device are also stored in the RAM 903. The processing device 901, the ROM 902, and the RAM 903 are connected to each other 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 touch pad, 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 Fig. 9 An electronic device having various devices is shown, but it should be understood that it is not required to implement or possess all 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 schematic, wherein the units described as separate components may or may not be physically separated, 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 over multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, in the drawings of the device embodiments provided by the present application, the connection relationship between the modules indicates that there is a communication connection between them, which may be specifically implemented as one or more communication buses or signal lines.

[0151] Through the description of the above implementation mode, the technicians in the field can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course, it can also be implemented by special hardware including special integrated circuits, special CPUs, special memories, special components, etc. In general, all functions completed by computer programs can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be various, such as analog circuits, digital circuits or special circuits. However, for the present application, software program implementation is a better implementation mode in more cases. Based on such an 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 floppy disk, a U disk, a mobile hard disk, a ROM, a RAM, a disk or an optical disk, etc., including a number of instructions to enable a computer device (which can be a personal computer, a training device, or a network device, 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 may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may 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 may be transmitted from a website site, 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 site, computer, training device, or data center. The computer-readable storage medium may 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 may 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)), etc.

Claims

1. A method for terminating an abnormal call, characterized in that: Session management elements used in the core network include: 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 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; A termination process for the target data flow is initiated to end the call between the first terminal and the second terminal.

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 whether the current session is a session based on the IP multimedia subsystem according to the session identifier of the current session.

3. The abnormal call termination method according to claim 1, characterized in that: The determining, according to 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 determined according to the data packet detection rule identifier.

4. The abnormal call termination method according to claim 1, characterized in that: The initiating a termination process for the target data flow 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 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 generation process of the abnormal call signal includes: In response to a connection disconnection signal between the first terminal and the core network, triggering a paging process for the first terminal; 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.

7. The abnormal call termination method according to claim 6, characterized in that: The generation process of 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.

8. An abnormal call termination device, characterized in that: Session management elements used in the core network include: a session category determination module, configured to determine, in response to an abnormal call signal of 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 The session termination module is used to start a termination process for the target data flow to end the call between the first terminal and the second terminal.

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

10. 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 as described in any one of claims 1 to 7.

Images