Ims call setup method, terminal, server, electronic device, and storage medium

Abstract

The application discloses an IMS call establishment method, a terminal, a server, an electronic device and a storage medium. The method comprises the following steps: in the case of IMS special bearer exception, a terminal sends a first signaling to a network server on an IMS default bearer, the first signaling is used for notifying that the IMS special bearer is abnormal and instructing the network server to send a second signaling to a media server, the second signaling is used for notifying that the IMS special bearer is abnormal and instructing the media server to switch the IMS call data bearer of the terminal; the terminal receives a first feedback signaling sent by the network server, the first feedback signaling is used for notifying that the media server has switched the IMS call data bearer from the IMS special bearer to the IMS default bearer; and the terminal transmits IMS call data on the IMS default bearer according to the first feedback signaling.

Description

Technical Field

[0001] This application belongs to the field of electronic technology, specifically relating to an IMS call establishment method, terminal, server, electronic device and storage medium. Background Technology

[0002] The Internet Protocol Multimedia Subsystem (IMS) is a fundamental solution for providing voice and video calls over communication networks, such as voice services based on Long Term Evolution (LTE) and voice services based on New Radio (NR).

[0003] In a communication network using IMS, after the two parties establish a call using the Session Initiation Protocol (SIP), they send and receive call data, namely voice and video data packets, using the Real Time Streaming Protocol (RTP).

[0004] However, whether it's LTE-based voice services or VoNR based on NR, IMS SIP messages or call data rely on its bearer network for transmission. During the IMS call establishment process, some regional operators experience delays, failures, or automatic disconnections in establishing the dedicated IMS call bearer, leading to IMS call termination and severely impacting user calls, thus causing IMS call failure. Summary of the Invention

[0005] The purpose of some embodiments of this application is to provide an IMS call establishment method, terminal, server, electronic device, and storage medium that can avoid IMS call failure when an IMS call dedicated bearer anomaly occurs, thereby ensuring the continuity of IMS calls and improving the smoothness of user calls.

[0006] In a first aspect, some embodiments of this application provide an IMS call establishment method, which includes: in the event of an IMS dedicated bearer anomaly, a terminal sends a first signaling message to a network server on an IMS default bearer, the first signaling message being used to notify that the IMS dedicated bearer is abnormal and to instruct the network server to send a second signaling message to a media server, the second signaling message being used to notify the media server that the IMS dedicated bearer is abnormal and to instruct the media server to switch the bearer of the terminal's IMS call data; the terminal receives a first feedback signaling message sent by the network server, the first feedback signaling message being used to notify the media server that the bearer of the IMS call data has been switched from the IMS dedicated bearer to the IMS default bearer; and the terminal transmits IMS call data on the IMS default bearer according to the first feedback signaling message.

[0007] Secondly, some embodiments of this application provide a terminal, which includes: a sending module, configured to send a first signaling message to a network server on an IMS default bearer in the event of an IMS dedicated bearer anomaly, the first signaling message being used to notify the network server of the IMS dedicated bearer anomaly and to instruct the network server to send a second signaling message to a media server, the second signaling message being used to notify the media server of the IMS dedicated bearer anomaly and to instruct the media server to switch the bearer of the terminal's IMS call data; a receiving module, configured to receive a first feedback signaling message sent by the network server, the first feedback signaling message being used to notify the media server that the bearer of the IMS call data has been switched from the IMS dedicated bearer to the IMS default bearer; and a transmission module, configured to transmit IMS call data on the IMS default bearer according to the first feedback signaling message received by the receiving module.

[0008] Thirdly, some embodiments of this application provide an IMS call establishment method, the method comprising: a media server receiving a second signaling sent by a network server, the second signaling being used to notify the media server that there is an anomaly in the IMS dedicated bearer and to instruct the media server to switch the bearer of the terminal's IMS call data; the second signaling being generated based on a first signaling received by the network server from a terminal, the first signaling being used to notify the network server that there is an anomaly in the IMS dedicated bearer and to instruct the network server to send the second signaling to the media server; the media server switching the bearer of the IMS call data from the IMS dedicated bearer to the IMS default bearer according to the second signaling, and sending a third feedback signaling to the network server, the third feedback signaling being used to notify the network server that the bearer of the IMS call data has been switched from the IMS dedicated bearer to the IMS default bearer.

[0009] Fourthly, some embodiments of this application provide a server comprising: a receiving module for receiving a second signaling sent by a network server, the second signaling being used to notify a media server of an anomaly in the IMS dedicated bearer and to instruct the media server to switch the bearer of the terminal's IMS call data; the second signaling being generated based on a first signaling received by the network server from a terminal, the first signaling being used to notify the network server of an anomaly in the IMS dedicated bearer and to instruct the network server to send the second signaling to the media server; a switching module for switching the bearer of the IMS call data from the IMS dedicated bearer to the IMS default bearer according to the second signaling received by the receiving module; and a sending module for sending a third feedback signaling to the network server, the third feedback signaling being used to notify the network server that the bearer of the IMS call data has been switched from the IMS dedicated bearer to the IMS default bearer.

[0010] Fifthly, some embodiments of this application provide an electronic device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method described in the first aspect.

[0011] In a sixth aspect, some embodiments of this application provide a server including a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implementing the steps of the method described in the third aspect.

[0012] In a seventh aspect, some embodiments of this application provide a readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect.

[0013] Eighthly, some embodiments of this application provide a readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the third aspect.

[0014] Ninthly, some embodiments of this application provide a chip including a processor and a communication interface coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect.

[0015] In a tenth aspect, some embodiments of this application provide a chip including a processor and a communication interface coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the third aspect.

[0016] Eleventhly, some embodiments of this application provide a computer program product stored in a storage medium, which is executed by at least one processor to implement the method described in the first aspect.

[0017] In a twelfth aspect, some embodiments of this application provide a computer program product stored in a storage medium, which is executed by at least one processor to implement the method described in the third aspect.

[0018] In a thirteenth aspect, some embodiments of this application provide a communication system, including: a terminal and a server, wherein the terminal can be used to perform the steps of the IMS call establishment method as described in the first aspect, and the server can be used to perform the steps of the IMS call establishment method as described in the third aspect.

[0019] In some embodiments of this application, in the event of an IMS dedicated bearer anomaly, the terminal can send a first signaling message to the network server to notify that the IMS dedicated bearer is abnormal. This causes the network server to send a second signaling message to the media server to notify that the IMS dedicated bearer is abnormal and to switch the bearer for IMS call data. The media server can then switch the bearer for IMS call data from the IMS dedicated bearer to the IMS default bearer, allowing the terminal to transmit IMS call data on the IMS default bearer. In this solution, by adding a notification signaling process for checking IMS dedicated bearer anomalies between the terminal and the network server, when an IMS dedicated bearer anomaly occurs, the terminal will promptly notify the network server of the detected anomaly or the need to update the bearer, and the network server can promptly notify the terminal to perform the corresponding state switch. Furthermore, by adding a handover recovery signaling process between the network server and the media server, the media server can switch the IMS call data to another bearer for transmission. This allows for the switching and recovery of the IMS bearer, enabling IMS call data to be transmitted directly on other bearers in the event of an IMS dedicated bearer anomaly. This avoids voice problems caused by IMS dedicated bearer anomalies, such as IMS call disconnection or delay, ensuring the continuity of IMS calls and improving the smoothness of user calls. Attached Figure Description

[0020] Figure 1 These are architectural diagrams of wireless communication systems provided in some embodiments of this application;

[0021] Figure 2 This is a flowchart illustrating an IMS call establishment method provided in some embodiments of this application;

[0022] Figure 3 This is a flowchart illustrating an IMS call establishment method provided in some embodiments of this application;

[0023] Figure 4 This is a flowchart illustrating an IMS call establishment method provided in some embodiments of this application;

[0024] Figure 5 This is a flowchart illustrating an IMS call establishment method provided in some embodiments of this application;

[0025] Figure 6 This is a flowchart illustrating an IMS call establishment method provided in some embodiments of this application;

[0026] Figure 7 This is a flowchart illustrating an IMS call establishment method provided in some embodiments of this application;

[0027] Figure 8 This is a flowchart illustrating an IMS call establishment method provided in some embodiments of this application;

[0028] Figure 9 This is a flowchart illustrating an IMS call establishment method provided in some embodiments of this application;

[0029] Figure 10 These are schematic diagrams of the terminal structure provided in some embodiments of this application;

[0030] Figure 11 These are schematic diagrams of the server structure provided in some embodiments of this application;

[0031] Figure 12 These are schematic diagrams of the hardware structure of electronic devices provided in some embodiments of this application;

[0032] Figure 13 These are schematic diagrams of the hardware structure of electronic devices provided in some embodiments of this application;

[0033] Figure 14 This is a schematic diagram of the hardware structure of a server provided in some embodiments of this application. Detailed Implementation

[0034] The technical solutions of some embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0035] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class, and the number of objects is not limited; for example, a first object can be one or more. Furthermore, the character " / " generally indicates that the preceding and following objects have an "or" relationship.

[0036] The following description, in conjunction with the accompanying drawings, details the video content display provided by some embodiments of this application through specific examples and application scenarios.

[0037] Before introducing the embodiments of this application, some terms involved in the embodiments of this application will be explained. It should be noted that the following explanations are for the purpose of making the embodiments of this application easier to understand, and should not be regarded as a limitation on the scope of protection claimed by the embodiments of this application.

[0038] IMS is based on the SIP protocol and provides voice services through the packet switch (PS) domain connected by Transmission Control Protocol / Internet Protocol (TCP / IP). It utilizes the bandwidth and latency characteristics of LTE and NR to provide high-quality voice services.

[0039] IMS SIP messages are transmitted based on the TCP / IP protocol, but they can use either TCP or User Datagram Protocol (UDP). IMS protocols require TCP transmission when the SIP message packet length exceeds a certain threshold. However, some terminal and network IMS implementations force the use of only UDP, especially when sending SIP messages over the network. In IMS-enabled communication networks, after the two parties establish a call via SIP, they then send and receive voice and video data packets via RTP. Whether it's VoLTE based on LTE or VoNR based on NR, IMS SIP messages or media data rely on the bearer of its network for transmission.

[0040] The IMS call establishment method in some embodiments of this application can be applied to scenarios where IMS call data transmission is interrupted when the dedicated IMS call bearer is abnormal.

[0041] The technologies described in some embodiments of this application are not limited to LTE / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems.

[0042] The terms "system" and "network" in some embodiments of this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes an NR system for illustrative purposes, and NR terminology is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.

[0043] Figure 1 This diagram illustrates an architecture of a wireless communication system to which some embodiments of this application may be applied. The wireless communication system includes at least one terminal 11, a network server 12, and a media server 13.

[0044] In this configuration, at least one terminal device 11 can establish a connection with the network server 12, and the network server 12 can establish a connection with the media server 13.

[0045] It should be noted that the above Figure 1 This description uses a wired network connection between at least one terminal device 11 and the network server 12, and between the network server 12 and the media server 13, as an example, and does not limit the scope of some embodiments of this application. It is understood that in actual implementation, at least one terminal device 11 and the network server 12 may also be connected wirelessly, and the network server 12 and the media server 13 may also be connected wirelessly, depending on the actual usage requirements.

[0046] At least one terminal 11 includes a Mobile Originated (MO) terminal and a Mobile Terminated (MT) terminal; the at least one terminal 11 can communicate with each other, for example, by transmitting call data. The network server, also known as a core network device, is used to forward signaling and data between the at least one terminal 11 and the media server 13, and to manage the media server 13 in performing operations such as bearer replacement and network updates. The media server is a third-party server or an operator server, used to perform bearer replacement on data between the at least one terminal 11 and to perform network updates.

[0047] Specifically, at least one terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that some embodiments in this application do not limit the specific type of terminal.

[0048] Network server 12 may include, but is not limited to, at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. Function (BSF), Application Function (AF), etc.

[0049] Media server 13 is a computer device that manages resources and provides services to terminals. Media server 13 may include a processor, hard disk, memory, and bus, etc. For example, media server 13 can provide an IMS bearer for terminals to transmit IMS call data.

[0050] Currently, it has been found that during the IMS call setup process, many regional operators are experiencing delays, failures, or automatic disconnections in the establishment of dedicated IMS call bearers, which in turn causes IMS calls to be dropped, severely impacting users' calls.

[0051] Therefore, based on this, this solution proposes an IMS call establishment scheme based on bearer switching. In the event of an IMS dedicated bearer anomaly, the terminal can send a signaling message to the network server to notify that the IMS dedicated bearer is abnormal. This causes the network server to send a signaling message to the media server to notify that the IMS dedicated bearer is abnormal and that an IMS call data bearer switching operation needs to be performed. As a result, the media server can switch the IMS call data bearer from the IMS dedicated bearer to the IMS default bearer, so that the terminal can transmit IMS call data on the IMS default bearer.

[0052] This solution adds a notification signaling process between the terminal and the network server to check for IMS dedicated bearer anomalies. This ensures that when an IMS dedicated bearer anomaly occurs, the terminal promptly notifies the network server of the detected anomaly or the need to update the bearer, and the network server promptly notifies the terminal to perform the corresponding state switch. Furthermore, by adding a handover recovery signaling process between the network server and the media server, the media server switches IMS call data to other bearers for transmission. This completes the handover and recovery of the IMS bearer, allowing IMS call data to be transmitted directly on other bearers when an IMS dedicated bearer anomaly occurs. This avoids voice problems caused by IMS dedicated bearer anomalies, such as IMS call disconnection or delay, ensuring the continuity of IMS calls and improving the smoothness of user calls.

[0053] It is understandable that this solution enables seamless reuse between IMS bearers, fully utilizing the correlation and maximum availability between IMS bearers, and effectively reducing the occurrence of abnormal hang-ups in video or audio call scenarios.

[0054] The execution entity of the IMS call establishment method provided in some embodiments of this application can be a terminal, a functional module or entity in the terminal, or an IMS call establishment device. The following uses a terminal as an example to illustrate the technical solutions provided in some embodiments of this application.

[0055] Based on the communication system described above, some embodiments of this application provide an IMS call establishment method. Figure 2 A flowchart illustrating an IMS call establishment method provided by some embodiments of this application is shown. For example... Figure 2 As shown, some embodiments of this application provide an IMS call establishment method that may include the following steps 201 to 203.

[0056] Step 201: In the event of an IMS dedicated bearer malfunction, the terminal sends the first signaling message to the network server on the IMS default bearer.

[0057] In some embodiments of this application, the first signaling is used to notify the IMS dedicated bearer of an anomaly and to instruct the network server to send a second signaling to the media server. The second signaling is used to notify the media server of the IMS dedicated bearer an anomaly and to instruct the media server to switch the bearer of the terminal's IMS call data.

[0058] It should be noted that the bearer described in this application refers to the logical channel between the terminal and the core network, i.e., the path for signaling and service data transmission. Optionally, it may include the logical channel between the terminal and the base station, and the logical channel between the base station and the core network.

[0059] The aforementioned IMS dedicated bearers are dynamically established, meaning they are dedicated bearers established according to different service types to transmit user service data. In other words, IMS dedicated bearers are established to provide a specific Quality of Service (QoS) transmission requirement. The IMS dedicated bearer remains active during the user's IMS session; once the session ends, the IMS dedicated bearer is deactivated to release related radio resources, such as the Data Radio Bearer (DRB).

[0060] The aforementioned IMS default bearer is statically established and is a user bearer that meets default QoS requirements for data and signaling. It can be simply understood as a bearer providing a best-effort IP connection, offering users a permanently online IP transmission service. That is, the IMS default bearer remains active throughout the entire IMS user registration period, allowing the terminal to initiate IMS calls anytime, anywhere. Of course, if the terminal is powered off, IMS registration expires, or the user cancels registration, the default bearer will be deactivated, and the associated resources will be released.

[0061] It should be noted that the aforementioned dedicated IMS bearer is established based on the default IMS bearer. Furthermore, the dedicated IMS bearer can be initiated by either the network or the terminal, while the default IMS bearer can only be initiated by the network. The dedicated IMS bearer can be either a guaranteed bit rate (GBR) bearer or a non-GBR bearer, while the default bearer can only be a non-GBR bearer.

[0062] In some embodiments of this application, the aforementioned IMS private bearer anomalies include, but are not limited to, at least one of the following: IMS private bearer establishment failure, IMS private bearer establishment delay, and IMS private bearer automatic disconnection. Here, IMS private bearer establishment delay refers to the IMS private bearer establishment being completed after a timer expires; this timer is used to time the IMS private bearer establishment process.

[0063] In some embodiments of this application, the aforementioned IMS dedicated bearer anomaly can be detected by the terminal. One scenario is that the terminal can detect whether there is an anomaly in the IMS dedicated bearer when initiating an IMS call; another scenario is that the terminal can detect whether there is an anomaly in the IMS dedicated bearer during the IMS call.

[0064] In some embodiments of this application, step 201 can be implemented by step 201a or step 201b as described below.

[0065] Step 201a: When initiating an IMS call, if the IMS dedicated bearer is abnormal, the terminal sends the first signaling to the network server on the IMS default bearer.

[0066] It is understandable that when a terminal initiates an IMS call, the IMS call has not yet been established. If an anomaly is detected in the established IMS dedicated bearer at this time, the terminal can send the first signaling message to the network server on the default IMS bearer to notify the network server that there is an anomaly in the IMS dedicated bearer.

[0067] In some embodiments of this application, the MO terminal and the MT terminal register with the IMS network and establish an IMS default bearer. The MO terminal can send a call establishment signaling message, such as an INVITE message, to the network server. At this time, an IMS dedicated bearer establishment anomaly occurs between the MO terminal and the network server, such as IMS dedicated bearer establishment delay or establishment failure. When the MT terminal receives the call establishment signaling message from the MO terminal, it can send a call establishment feedback signaling message to the network server and negotiate the corresponding Session Description Protocol (SDP) parameters with the network. At this time, an anomaly occurs in the establishment of the IMS dedicated bearer between the MT terminal and the network server. That is, when initiating an IMS call, an IMS dedicated bearer anomaly occurs, and the terminal sends a first signaling message to the network server. This terminal includes at least one of the MO terminal and the MT terminal.

[0068] It should be noted that after the MO terminal sends a call establishment signaling message to the network server, if the IMS dedicated bearer between the MO terminal and the network server is established normally, then the MO terminal and the MT terminal can directly conduct IMS calls through the established IMS dedicated bearer, that is, transmit IMS call data.

[0069] In some embodiments of this application, the above-mentioned SDP parameters may include, but are not limited to, at least one of the following: network bandwidth, port number, encoding method, etc.

[0070] Step 201b: During an IMS call, if the IMS dedicated bearer is abnormal, the terminal sends the first signaling message to the network server on the IMS default bearer.

[0071] It is understandable that after the terminal initiates the IMS call process, the IMS call is established and the IMS call is conducted on the established IMS dedicated bearer, that is, the IMS call data is transmitted. During the IMS call, if an anomaly is detected in the IMS dedicated bearer, the terminal can send the first signaling to the network server on the default IMS bearer to notify the network server that there is an anomaly in the IMS dedicated bearer.

[0072] In some embodiments of this application, the MO terminal and the MT terminal register with the IMS network and establish an IMS default bearer. The MO terminal can send a call establishment signaling message, such as an INVITE message, to the network server, which is then forwarded to the MT terminal. At this time, the MO terminal establishes an IMS private bearer with the network server. After receiving the call establishment signaling message from the network server, the MT terminal performs corresponding processing and interface updates, and establishes an IMS private bearer with the network server. The MT terminal sends call establishment feedback information to the network server and negotiates the corresponding SDP parameters with the network. After receiving the call establishment feedback signaling message from the MT terminal, the network server forwards the message to the MO terminal, which then updates its interface and status. At this point, the call between the MO terminal and the MT terminal is successfully established. After a period of time, an anomaly occurs in the IMS private bearer between the MO terminal, the MT terminal, and the network server, i.e., an IMS private bearer anomaly occurs during the IMS call. The terminal sends a first signaling message to the network server, and this terminal includes at least one of the MO terminal and the MT terminal.

[0073] This solution allows the terminal to notify the network server of the IMS dedicated bearer anomaly, whether it is detected when initiating an IMS call or during an IMS call. This enables the network server to understand that the dedicated bearer for the IMS call is abnormal, thereby achieving bearer switching for the IMS call. In other words, this solution can be used to directly switch the IMS call bearer before or during an IMS call, ensuring the continuity of the IMS call.

[0074] In some embodiments of this application, the first signaling can be a SIP message. For example, the "terminal sends the first signaling to the network server on the IMS default bearer" in steps 201, 201a, or 201b can be specifically implemented through step 201c below.

[0075] Step 201c: The terminal sends a SIP message to the network server on the IMS default bearer.

[0076] In some embodiments of this application, the above-mentioned SIP message is an INVITE signaling message, an UPDATE signaling message, or a NOTIFY signaling message.

[0077] In some embodiments of this application, the SIP message includes at least one of the following: the calling and called party numbers, the media types supported by the terminal for transmission, the network capabilities supported by the terminal, the IP information of the terminal, and the reason information for the IMS private bearer anomaly.

[0078] It is understandable that if at least one of the MO terminal and MT terminal fails to establish a dedicated bearer with the network server, it will send a dedicated bearer failure signaling to the network server. This dedicated bearer failure signaling is the first signaling mentioned above, which is a signaling signaling element added in this scheme. This first signaling is the signaling interaction between the terminal and the network server, and its function is to notify the network server that there is an anomaly in the IMS dedicated bearer. This first signaling can take the following three forms:

[0079] (1) SIP message, sent in INVITE form. In addition to carrying the calling and called party numbers, the media type supported by the terminal, and the NR or LTE capability information supported by the terminal, the INVITE form signaling also includes information on the reason for the IMS private bearer anomaly.

[0080] (2) SIP messages are sent in UPDATE form. In addition to carrying the calling and called party numbers, the media types supported by the terminal, the NR or LTE capability information supported by the terminal, and the IP information of the terminal, the UPDATE form signaling also includes information about the reason for the IMS private bearer anomaly.

[0081] (3) SIP messages are sent in NOTIFY form. In the UPDATE form, in addition to carrying the calling and receiving numbers, the media types supported by the terminal, and the NR or LTE capabilities supported by the terminal, an additional IMS private bearer error information is added.

[0082] It should be noted that all three signaling formats mentioned above can be used as the primary signaling in this solution. These signals operate between the network server and the terminal, performing IMS dedicated bearer notifications and status updates, and can be used interchangeably at different times. For example, INVITE or UPDATE signaling can be used before ringing, and NOTIFY signaling can be used after ringing; alternatively, only one format can be used consistently, such as always using INVITE signaling. This solution does not impose any restrictions; the specific requirements of the implementer will determine the appropriate format.

[0083] In some embodiments of this application, the aforementioned calling and called terminal numbers include the numbers of the MO terminal and the MT terminal, which are used by the network to identify the calling and called terminals.

[0084] In some embodiments of this application, the media types supported by the terminal for transmission refer to the media types that the terminal is capable of transmitting, negotiated between the network and the terminal. Optionally, the media types supported by the terminal for transmission may include at least one of the following: voice type, video type, and other data types.

[0085] In some embodiments of this application, the IP information of the terminal mentioned above refers to the IP address assigned to the UE by the network.

[0086] In some embodiments of this application, the network capability information supported by the terminal mentioned above includes at least one of the following: the terminal supports LTE capability, and the terminal supports NR capability.

[0087] In some embodiments of this application, the cause information of the above-mentioned IMS dedicated bearer anomaly may include, but is not limited to, at least one of the following: network-side anomaly cause and terminal-side anomaly cause.

[0088] Among them, the above-mentioned network-side abnormalities include, but are not limited to, at least one of the following: insufficient network resources, network failure, network server abnormalities, such as information transmission delays on the network server.

[0089] The above-mentioned terminal-side abnormalities include, but are not limited to, at least one of the following: slow terminal signaling response process, terminal telephone process freezing, etc.

[0090] This scheme allows the terminal to send SIP messages to the network server, carrying information about the terminal and the reason for the IMS private bearer anomaly. This enables the network server to understand the reason for the IMS private bearer anomaly, thus facilitating the network server's decision on whether to trigger the media server to perform IMS call bearer switching and to determine the bearer that needs to be switched, thereby ensuring the accuracy of IMS call bearer switching.

[0091] Step 202: The terminal receives the first feedback signaling sent by the network server.

[0092] In some embodiments of this application, the aforementioned first feedback signaling is used to notify that the media server has switched the bearer of IMS call data from the IMS dedicated bearer to the IMS default bearer.

[0093] In some embodiments of this application, after receiving feedback signaling from the media server and learning that the media server has switched the bearer of IMS call data from the IMS dedicated bearer to the IMS default bearer, the network server sends a first feedback signaling to at least one of the MO terminal and the MT terminal to notify it that the network is ready to switch the IMS call data to the IMS default bearer for transmission. This is the feedback signaling of the first signaling mentioned above in this scheme, which can also be a SIP message.

[0094] In some embodiments of this application, under normal handover conditions, i.e., when the media server successfully performs bearer handover, the network server sends a first feedback signaling message to the terminal, for example, in the form of a 200 OK signaling message. Under abnormal handover conditions, i.e., when the media server fails to perform bearer handover, the network server sends feedback to the terminal in the form of an error code + ERROR signaling message, indicating that the media server will not perform bearer handover transmission of IMS call data.

[0095] Step 203: The terminal transmits IMS call data on the IMS default bearer according to the first feedback signaling.

[0096] In some embodiments of this application, the aforementioned IMS call data includes at least one of the following: IMS voice call data and IMS video call data. It should be noted that the data described in this application can be understood as data packets, such as audio data packets and video data packets.

[0097] In some embodiments of this application, after receiving the first feedback signaling, the MT terminal can send a call establishment feedback signaling to the network server to notify the network server that the MT terminal is ready to establish a call. After receiving the call establishment feedback signaling from the MT terminal, the network server will forward the call establishment feedback signaling to the MO terminal. After receiving the call establishment feedback signaling, the MO terminal completes the call establishment between the MO terminal and the MT terminal to transmit IMS call data on the IMS default bearer.

[0098] The IMS call establishment method provided in some embodiments of this application allows the terminal to promptly send signaling to the network server in the event of an IMS dedicated bearer anomaly. This notifies the network server of the IMS dedicated bearer anomaly, enabling the network server to promptly notify the media server to perform an IMS call data bearer switching operation. After the media server switches the IMS call data bearer from the IMS dedicated bearer to the IMS default bearer, it feeds back the bearer switching result to the terminal, allowing the terminal to transmit IMS call data on the IMS default bearer. This completes the switching and recovery of the IMS bearer, ensuring that IMS call data can be directly transmitted on other bearers when an IMS dedicated bearer anomaly occurs. This avoids voice problems caused by IMS dedicated bearer anomalies, such as IMS call disconnection or delay, ensuring the continuity of IMS calls and improving the smoothness of user calls.

[0099] In some embodiments of this application, combined with Figure 2 ,like Figure 3 As shown, after step 203 above, some embodiments of this application provide an IMS call establishment method that further includes steps 204 to 206 as described below.

[0100] Step 204: If the IMS dedicated bearer is established normally, the terminal sends a third signaling message to the network server on the IMS default bearer.

[0101] In some embodiments of this application, the aforementioned third signaling is used to notify that the IMS private bearer has been successfully established.

[0102] In some embodiments of this application, after a period of time during which the terminal transmits IMS call data on the IMS default bearer, if the IMS dedicated bearer between the MO terminal and the MT terminal and the network server is successfully established, at least one of the MO terminal and the MT terminal sends an IMS dedicated bearer establishment notification signaling to the network server to notify that the IMS dedicated bearer has been successfully established. It should be noted that the IMS dedicated bearer establishment notification signaling here is the third signaling mentioned above.

[0103] In some embodiments of this application, the aforementioned third signaling can be a SIP message, and the SIP message can take one of the following three forms:

[0104] 1. SIP messages are sent in INVITE format. In addition to carrying the calling and called party numbers, the media types supported by the terminal, and the NR or LTE capabilities supported by the terminal, the INVITE format signaling also includes an indication that the IMS dedicated bearer is normal.

[0105] 2. SIP messages are sent in UPDATE format. In addition to carrying the calling and called party numbers, the media types supported by the terminal, the NR or LTE capabilities supported by the terminal, and the terminal's IP information, the UPDATE format signaling also includes an indication that the IMS dedicated bearer is normal.

[0106] 3. SIP messages are sent in NOTIFY format. In the UPDATE format, in addition to carrying the calling and receiving numbers, the media types supported by the terminal, and the NR or LTE capabilities supported by the terminal, an indication that the IMS dedicated bearer is normal is also added.

[0107] In some embodiments of this application, the normal establishment of the IMS private bearer includes, but is not limited to, at least one of the following: successful establishment of the IMS private bearer, completion of IMS private bearer establishment without timeout, and maintaining the IMS private bearer connection. The timer is used to time the IMS private bearer establishment process.

[0108] Step 205: The terminal receives the second feedback signaling sent by the network server.

[0109] In some embodiments of this application, the aforementioned second feedback signaling is used to notify that the media server has switched the bearer of IMS call data from the IMS default bearer to the IMS dedicated bearer.

[0110] Step 206: The terminal transmits IMS call data on the IMS dedicated bearer according to the second feedback signaling.

[0111] It is understandable that after the network server receives the feedback signaling sent by the media server and learns that the media server has switched the bearer of IMS call data from the default IMS bearer to the dedicated IMS bearer, it will send a second feedback signaling to at least one of the MO terminal and the MT terminal to notify it that the media server has switched the IMS call data to the dedicated IMS bearer for transmission. At this time, the switch from the default IMS bearer to the dedicated IMS bearer has been completed, ensuring the continuity of IMS calls.

[0112] This scheme allows the terminal to promptly send signaling to the network server when the IMS dedicated bearer is functioning normally, notifying the network server that the IMS dedicated bearer has been successfully established. This enables the network server to promptly instruct the media server to perform a bearer switching operation for IMS call data. After the media server switches the IMS call data bearer from the default IMS bearer to the dedicated IMS bearer, it sends feedback on the bearer switching result to the terminal, allowing the terminal to transmit IMS call data on the dedicated IMS bearer. This completes the switching and recovery of the IMS bearer, enabling the terminal to switch to a more suitable IMS dedicated bearer that meets specific QoS transmission requirements when the dedicated IMS bearer returns to normal, thus ensuring the continuity and quality of IMS calls.

[0113] The execution entity of the IMS call establishment method provided in some embodiments of this application can be a media server, a functional module or entity within the media server, or an IMS call establishment device. The following uses a media server as an example to illustrate the technical solutions provided in some embodiments of this application.

[0114] Based on the communication system described above, some embodiments of this application also provide an IMS call establishment method. Figure 4 A flowchart illustrating an IMS call establishment method provided by some embodiments of this application is shown. For example... Figure 4 As shown, some embodiments of this application provide an IMS call establishment method that may include the following steps 301 and 302.

[0115] Step 301: The media server receives the second signaling sent by the network server.

[0116] In some embodiments of this application, the aforementioned second signaling is used to notify the media server of an anomaly in the IMS dedicated bearer and to instruct the media server to switch the bearer of the terminal's IMS call data. The aforementioned second signaling is generated based on the network server receiving a first signaling sent by the terminal, which is used to notify the IMS dedicated bearer of the anomaly and to instruct the network server to send the second signaling to the media server.

[0117] In some embodiments of this application, after the network server receives a first signaling message from at least one of the MO terminal and the MT terminal, that is, a signaling message notifying that the IMS dedicated bearer is abnormal, it will send a bearer switching signaling message to the media server to notify the media server that the current IMS dedicated bearer is abnormal, and after establishing an IMS call, the IMS call data will be switched to the IMS default bearer for transmission. It should be noted that the bearer switching signaling message here is the same as the second signaling message mentioned above.

[0118] In some embodiments of this application, the second signaling can be a SIP message or a request-response signaling. For example, step 301 can be implemented specifically through step 301a as described below.

[0119] Step 301a: The media server receives a SIP message or request / response signaling sent by the network server.

[0120] In some embodiments of this application, the above-mentioned SIP message is an INVITE signaling message.

[0121] In some embodiments of this application, the SIP message includes at least one of the following: the calling and called party numbers, the media type supported by the terminal for transmission, the network capability information supported by the terminal, the IP information of the network server, and the duration information of the bearer timeout timer.

[0122] The duration of the aforementioned bearer timeout timer indicates the timing when the media server sends a Notify message to the network server, which in turn queries the network server whether to continue maintaining the current bearer.

[0123] It is understandable that after receiving the first signaling from at least one of the MO terminal and MT terminal, the network server will send a bearer switching notification signaling to the media server. This bearer switching notification signaling is the aforementioned second signaling, a signaling second added in this scheme. This second signaling is the signaling interaction between the network server and the media server, and its function is to notify the media server to change the bearer for transmitting IMS call data and update the network. This second signaling can take the following two forms:

[0124] 1. SIP messages are sent in the form of INVITE signaling. The INVITE signaling carries the calling and called party numbers, the media types supported by the terminal, the NR or LTE capabilities supported by the terminal, the IP information of the network server, and the duration T of the bearer timeout timer. After the SIP message is sent for a duration T, the media service will send a Notify message to the network server to inquire whether the network server should continue to maintain the current bearer.

[0125] Upon receiving a Notify message, if the network server needs to maintain the bearer, it sends a 200 OK signaling message to the media server. This 200 OK signaling message must carry the calling and called party numbers, the media types supported by the terminal, the NR or LTE capabilities supported by the terminal, the network server's IP address, and the bearer timeout timer duration (T). The current bearer will only be maintained and data packets will continue to be sent if the parameters carried in the 200 OK signaling message received by the media server are the same as those carried in the original INVITE signaling message. Otherwise, the bearer will be disconnected, for example, if no 200 OK signaling message is received from the network server, or if the parameters carried in the received 200 OK signaling message are different from those carried in the original INVITE signaling message.

[0126] In some embodiments of this application, the fact that the parameters carried by the 200OK signaling are the same as those carried by the originally sent INVITE signaling can be understood as follows: the calling and called party numbers, the media types supported by the terminal, the NR or LTE capability information supported by the terminal, the IP information of the network server, and the duration information T of the bearer timeout timer are all the same as those carried by the 200OK signaling and the originally sent INVITE signaling.

[0127] In some embodiments of this application, the difference between the parameters carried by the 200OK signaling and those carried by the original INVITE signaling can be understood as follows: at least one of the following is different between the 200OK signaling and the original INVITE signaling: the calling and called party numbers, the media type supported by the terminal, the NR or LTE capability information supported by the terminal, the IP information of the network server, and the duration information T of the bearer timeout timer.

[0128] 2. Request and Response signaling is sent in the form of Request signaling. The Request signaling carries the calling and called party numbers, the media types supported by the terminal, the NR or LTE capability information supported by the terminal, the IP information of the network server, and the duration T of the bearer timeout timer. After the SIP message is sent for a duration T, the media service will send a Notify message to the network server to inquire whether the network server should continue to maintain the current bearer.

[0129] Upon receiving a Notify message, if the network server needs to maintain the bearer, it sends a 200 OK signaling message to the media server. This 200 OK signaling message must carry the calling and called party numbers, the media types supported by the terminal, the NR or LTE capabilities supported by the terminal, the network server's IP address, and the bearer timeout timer duration T. The current bearer will continue sending data packets only if the parameters carried in the 200 OK signaling message received by the media server are identical to those carried in the original Request signaling message. For example, if the calling and called party numbers, the media types supported by the terminal, the NR or LTE capabilities supported by the terminal, the network server's IP address, and the bearer timeout timer duration T are all the same. Otherwise, the bearer will be disconnected, for example, if no 200 OK signaling message is received from the network server, or if the parameters carried in the received 200 OK signaling message are different from those carried in the original Request signaling message. For example, if the 200OK signaling carries at least one different item from the original Request, including the calling and called party numbers, the media types supported by the terminal, the NR or LTE capabilities supported by the terminal, the IP information of the network server, and the duration T of the bearer timeout timer, then the bearer is disconnected.

[0130] In some embodiments of this application, the IP information of the network server mentioned above refers to the IP address information of the network server.

[0131] This scheme allows the media server to receive SIP messages or request-response signaling sent by the network server. Based on the information carried in the SIP messages or request-response signaling, the media server can determine whether to perform bearer switching for the IMS call and identify the bearer that needs to be switched, thereby ensuring the accuracy of bearer switching for the IMS call.

[0132] Step 302: According to the second signaling, the media server switches the bearer of the IMS call data from the IMS dedicated bearer to the IMS default bearer and sends the third feedback signaling to the network server.

[0133] In some embodiments of this application, the aforementioned third feedback signaling is used to notify that the bearer of IMS call data has been switched from the IMS dedicated bearer to the IMS default bearer.

[0134] It is understandable that after receiving the second signaling from the network server, the media server will record relevant information such as the calling and called party numbers to be switched to the default bearer, the media types supported by the terminal, the NR or LTE capabilities supported by the terminal, the network server's IP information, and the duration of the bearer timeout timer. Then, it sends a feedback signaling to the network server, notifying it that it is ready to switch the IMS call data to the IMS default bearer for transmission. This feedback signaling is the media server's feedback signaling, specifically the feedback signaling of signaling two mentioned above, i.e., the third feedback signaling. This feedback signaling can take one of two forms:

[0135] 1. When the second signaling is a SIP message, the third feedback signaling is fed back in the form of a 200 OK signaling.

[0136] 2. If the second signaling is a request-response signaling, the third feedback signaling shall be provided in the form of a Response.

[0137] It should be noted that the above two methods apply to the normal handover scenario, i.e., when the media server successfully performs the bearer handover, the media server will send a third feedback signaling to the network server. In the abnormal handover scenario, i.e., when the media server fails to perform the bearer handover, the media server will send an error code + ERROR signaling to the network server, indicating that the media server will not perform bearer handover transmission for IMS call data.

[0138] The IMS call establishment method provided in some embodiments of this application allows the media server to detect an anomaly in the IMS dedicated bearer based on a second signaling sent by the network server. This allows the media server to promptly switch the IMS call data bearer from the IMS dedicated bearer to the IMS default bearer and send feedback on the bearer switch result to the network server. This enables the terminal to transmit IMS call data on the IMS default bearer. By adding a handover recovery signaling process between the network server and the media server, the media server can switch the IMS call data to other bearers for transmission. This completes the handover and recovery of the IMS bearer, ensuring that when an IMS dedicated bearer anomaly occurs, IMS call data can be directly transmitted on other bearers. This avoids voice problems caused by IMS dedicated bearer anomalies, such as IMS call disconnection or delay, ensuring the continuity of IMS calls and improving the smoothness of user calls.

[0139] In some embodiments of this application, combined with Figure 4 ,like Figure 5 As shown, after step 302 above, some embodiments of this application provide an IMS call establishment method that further includes steps 303 and 304 as described below.

[0140] Step 303: The media server receives the fourth signaling sent by the network server.

[0141] In some embodiments of this application, the aforementioned fourth signaling is used to notify the media server that the IMS dedicated bearer has been successfully established and to instruct the media server to switch the bearer of the terminal's IMS call data.

[0142] In some embodiments of this application, after the network server receives an IMS private bearer establishment notification signaling from at least one of the MO terminal and the MT terminal, it sends a fourth signaling to the media server to notify the media server that the IMS private bearer has been successfully established and that IMS call data can be switched to the IMS private bearer for transmission. It should be noted that the IMS private bearer establishment notification signaling here is the same as the third signaling mentioned above.

[0143] In some embodiments of this application, the fourth signaling can be a SIP message or a request-response signaling. For example, step 303 can be implemented specifically through step 303a as described below.

[0144] Step 303a: The media server receives a SIP message or request / response signaling sent by the network server.

[0145] In some embodiments of this application, the above-mentioned SIP message is a CANCEL signaling.

[0146] In some embodiments of this application, the aforementioned fourth signaling can be understood as a signaling interaction between the network server and the media server. Its function is to notify the media server to change the bearer for transmitting IMS call data and to update the network. The fourth signaling can take the following two forms:

[0147] 1. SIP messages are sent in CANCEL format, which includes: the calling and called party numbers, the media types supported by the terminal, the NR or LTE capabilities supported by the terminal, the IP information of the network server, and the duration T of the bearer timeout timer. Upon receiving the CANCEL format signaling, the media server will cancel the transmission of IMS call data on the default bearer and switch to the dedicated IMS bearer.

[0148] 2. Request and Response Signaling: This is sent in Request form, which includes the calling and called party numbers, the media types supported by the terminal, the NR or LTE capabilities supported by the terminal, the network server's IP address, and the duration T of the bearer timeout timer. Upon receiving the Request signaling, the media server will cancel the transmission of IMS call data on the default bearer and switch to the dedicated IMS bearer.

[0149] Step 304: According to the fourth signaling, the media server switches the bearer of the terminal's IMS call data from the default IMS bearer to the dedicated IMS bearer, and sends the fourth feedback signaling to the network server.

[0150] In some embodiments of this application, the aforementioned fourth feedback signaling is used to notify the network server that the bearer of IMS call data has been switched from the IMS default bearer to the IMS dedicated bearer.

[0151] It is understandable that after receiving the fourth signaling, the media server will switch the IMS call data to the IMS dedicated bearer for transmission, and then send a feedback signaling to the network server to notify it that the IMS call data has been switched to the IMS dedicated bearer for transmission. This feedback signaling is the media server's feedback signaling, specifically the feedback signaling of the fourth signaling mentioned above in this scheme. This feedback signaling can take one of two forms:

[0152] 1. When the fourth signaling is a SIP message, the fourth feedback signaling is fed back in the form of a 200 OK signaling.

[0153] 2. When the fourth signaling is a request-response signaling, the fourth feedback signaling is given in the form of a Response.

[0154] It should be noted that the above two methods apply to the normal handover scenario, i.e., when the media server successfully performs the bearer handover, the media server will send a fourth feedback signaling to the network server. In the abnormal handover scenario, i.e., when the media server fails to perform the bearer handover, the media server will send an error code + ERROR signaling to the network server, indicating that the media server will not perform bearer handover transmission for IMS call data.

[0155] This scheme allows the media server to detect the successful establishment of the IMS dedicated bearer based on the fourth signaling sent by the network server. It then promptly switches the IMS call data bearer from the default IMS bearer to the dedicated IMS bearer and reports the switch result back to the network server. This enables the terminal to transmit IMS call data on the dedicated IMS bearer, thus completing the switching and recovery of the IMS bearer. When the dedicated IMS bearer returns to normal, it can switch to a more suitable IMS dedicated bearer that meets specific QoS transmission requirements, ensuring the continuity and quality of IMS calls.

[0156] Based on the communication system described above, some embodiments of this application also provide an IMS call establishment method. Figure 6 The diagram illustrates an interactive process flowchart of an IMS call establishment method provided by some embodiments of this application. For example... Figure 6 As shown, some embodiments of this application provide an IMS call establishment method that may include steps 401 to 406 as described below.

[0157] Step 401: In the event of an IMS dedicated bearer malfunction, the terminal sends the first signaling message to the network server on the IMS default bearer.

[0158] Step 402: The network server receives the first signaling sent by the terminal and sends the second signaling to the media server according to the first signaling.

[0159] Step 403: The media server receives the second signaling sent by the network server.

[0160] Step 404: According to the second signaling, the media server switches the bearer of the IMS call data from the IMS dedicated bearer to the IMS default bearer and sends the third feedback signaling to the network server.

[0161] Step 405: The network server receives the third feedback signaling sent by the media server, and sends the first feedback signaling to the terminal according to the third feedback signaling.

[0162] Step 406: The terminal receives the first feedback signaling sent by the network server, and transmits IMS call data on the IMS default bearer according to the first feedback signaling.

[0163] It should be noted that for the relevant explanations of steps 401 to 406, please refer to the descriptions in the above method embodiments, and they will not be repeated here.

[0164] Understandably, in the event of an IMS dedicated bearer anomaly, the terminal sends a first signaling message to notify the network server, informing the network server that the current IMS dedicated bearer is abnormal. The network server then sends a third signaling message to notify the media server to perform an IMS bearer switchover. After the bearer switchover, the media server sends a third feedback signaling message (i.e., feedback signaling of the third signaling message) to the network server, informing the network server that an IMS bearer switchover has been performed. Then, the network server sends a first feedback signaling message (i.e., feedback signaling of the first signaling message) to the terminal, enabling the terminal to establish a call on the switched IMS bearer, i.e., the default IMS bearer, and to transmit IMS call data.

[0165] The IMS call establishment method provided in some embodiments of this application adds a notification signaling process for checking IMS dedicated bearer anomalies between the terminal and the network server. This ensures that when an IMS dedicated bearer anomaly occurs, the terminal promptly notifies the network server of the detected anomaly or the need to update the bearer, and the network server promptly notifies the terminal to perform the corresponding state switch. Furthermore, by adding a handover recovery signaling process between the network server and the media server, the media server switches the IMS call data to another bearer for transmission. This enables the handover and recovery of the IMS bearer, allowing IMS call data to be transmitted directly on another bearer when an IMS dedicated bearer anomaly occurs. This avoids voice problems caused by IMS dedicated bearer anomalies, such as IMS call disconnection or delay, ensuring the continuity of IMS calls and improving the smoothness of user calls.

[0166] In some embodiments of this application, combined with Figure 6 ,like Figure 7 As shown, after step 406 above, some embodiments of this application provide an IMS call establishment method that further includes steps 407 to 412 below.

[0167] Step 407: If the IMS dedicated bearer is established normally, the terminal sends a third signaling message to the network server on the IMS default bearer.

[0168] Step 408: The network server receives the third signaling sent by the terminal and sends the fourth signaling to the media server according to the third signaling.

[0169] Step 409: The media server receives the fourth signaling sent by the network server.

[0170] Step 410: The media server switches the bearer of the terminal's IMS call data from the default IMS bearer to the dedicated IMS bearer according to the fourth signaling, and sends the fourth feedback signaling to the network server.

[0171] Step 411: The network server receives the fourth feedback signaling sent by the media server, and sends the second feedback signaling to the terminal according to the fourth feedback signaling.

[0172] Step 412: The terminal receives the second feedback signaling sent by the network server, and transmits IMS call data on the IMS dedicated bearer according to the second feedback signaling.

[0173] It should be noted that the relevant explanations and beneficial effects of steps 407 to 412 can be found in the descriptions in the above method embodiments, and will not be repeated here.

[0174] Based on the above communication system, the interaction process of the terminal, network server and media server in the IMS call establishment method provided by some embodiments of this application will be described below in combination with specific application scenarios, wherein the terminal includes a sending end (MO) terminal and a receiving end (MT) terminal.

[0175] In some embodiments of this application, there are cases where the IMS dedicated bearer malfunctions during the initiation of an IMS call process, i.e., when establishing an IMS call. For example... Figure 8 As shown, some embodiments of this application provide an IMS call establishment method that may include the following steps 501 to 513.

[0176] Step 501: The MO terminal and the MT terminal register with the IMS network and establish the default IMS bearer.

[0177] Step 502: The MO terminal sends a call establishment signaling message to the network server, which then forwards the call establishment signaling message to the MT terminal.

[0178] At this time, an abnormal situation occurs in the establishment of the IMS private bearer between the MO terminal and the network server, such as delay or failure in the establishment of the IMS private bearer.

[0179] Step 503: When the MT terminal receives the call establishment signaling from the MO terminal, it sends a call establishment feedback signaling to the network server and negotiates the corresponding SDP parameters with the network.

[0180] At this time, there is an anomaly in the establishment of the IMS private bearer between the MT terminal and the network server.

[0181] Step 504: After at least one of the MO terminal and MT terminal establishes a private bearer with the network server, it sends a private bearer exception signaling message to the network server to notify the network server that there is an exception in the IMS private bearer.

[0182] It should be noted that this is the first signaling added to this solution, namely the first signaling mentioned above. This first signaling is a signaling interaction between the terminal and the network server, and its function is to notify the network server that there is an anomaly in the IMS private bearer. For a related explanation of the first signaling, please refer to the description of the above embodiments, which will not be repeated here.

[0183] Step 505: After receiving a dedicated bearer abnormality signaling from at least one of the MO terminal and MT terminal, the network server sends a notification bearer switching signaling to the media server.

[0184] The aforementioned notification bearer switching signaling is used to notify the media server that the current IMS dedicated bearer is abnormal, and after establishing an IMS call, the IMS call data will be switched to the IMS default bearer for transmission. The IMS call data here can be audio data packets.

[0185] It should be noted that this is the second signaling added to this solution, namely the second signaling mentioned above. This second signaling is a signaling interaction between the network server and the media server, and its function is to notify the media server to change the bearer for transmitting IMS call data and update the network. For a detailed explanation of the second signaling, please refer to the description of the above embodiments, which will not be repeated here.

[0186] Step 506: After receiving the notification bearer switching signaling sent by the network server, the media server records the calling and called party numbers of the default bearer to be switched, the media types supported by the terminal, the NR or LTE capabilities supported by the terminal, the IP information of the network server, the duration of the bearer timeout timer, and other relevant information. Then, it sends a feedback signaling to the network server to notify the network server that it is ready to switch the IMS call data to the IMS default bearer for transmission.

[0187] It should be noted that this is the feedback signaling from the media server, specifically the feedback signaling of signaling two mentioned above in this solution, i.e., the third feedback signaling. For a detailed explanation of this feedback signaling, please refer to the description in the above embodiments; it will not be repeated here.

[0188] Step 507: After receiving the feedback signaling sent by the media server, the network server sends feedback signaling to at least one of the MO terminal and the MT terminal to notify it that the network is ready to switch the IMS call data to the IMS default bearer for transmission.

[0189] It should be noted that the feedback signaling here refers to the feedback signaling of signaling one mentioned above in this scheme, i.e., the first feedback signaling. For a detailed explanation of this feedback signaling, please refer to the description of the above embodiments; it will not be repeated here.

[0190] Step 508: The MT terminal sends a call establishment feedback signaling to the network server, notifying the network server that the MT terminal has established a call and is ready.

[0191] Step 509: After receiving the call establishment feedback signaling from the MT terminal, the network server forwards the call establishment feedback signaling to the MO terminal. After receiving the call establishment feedback signaling, the MO terminal completes the call establishment between the MO terminal and the MT terminal to transmit IMS call data on the IMS default bearer.

[0192] Step 510: After a period of time, at least one of the MO terminal and MT terminal establishes an IMS private bearer with the network server. At this time, at least one of the MO terminal and MT terminal sends an IMS private bearer establishment notification signaling to the network server to notify that the IMS private bearer has been established normally.

[0193] It should be noted that the IMS private bearer establishment notification signaling here is the third signaling mentioned above in this scheme. For relevant explanations of the notification signaling here, please refer to the description of the above embodiments, which will not be repeated here.

[0194] Step 511: After receiving the IMS private bearer establishment notification signaling from at least one of the MO terminal and MT terminal, the network server sends a notification signaling to the media server to notify the media server that the IMS private bearer has been established normally and the IMS call data can be switched to the IMS private bearer for transmission.

[0195] It should be noted that the notification signaling here is the fourth signaling mentioned above in this solution. For a description of the notification signaling here, please refer to the description of the above embodiments, which will not be repeated here.

[0196] Step 512: After receiving the notification signaling, the media server switches the IMS call data to the IMS dedicated bearer for transmission, and then sends a feedback signaling to the network server to notify the network server that the call IMS data has been switched to the IMS dedicated bearer for transmission.

[0197] It should be noted that the feedback signaling here refers to the feedback signaling of the media server, specifically the feedback signaling of the fourth signaling mentioned above in this solution, i.e., the aforementioned fourth feedback signaling. For a detailed explanation of this feedback signaling, please refer to the description in the above embodiments; it will not be repeated here.

[0198] Step 513: After receiving the feedback signaling sent by the media server, the network server sends feedback signaling to at least one of the MO terminal and the MT terminal to notify it that the media server has switched the IMS call data to the IMS dedicated bearer for transmission.

[0199] At this point, the switch from the default IMS bearer to the dedicated IMS bearer has been completed, ensuring the continuity of IMS calls.

[0200] It should be noted that the feedback signaling sent to at least one of the MO terminal and the MT terminal here is the second feedback signaling described above in this scheme. For a detailed explanation of this feedback signaling, please refer to the description in the above embodiments; it will not be repeated here.

[0201] This scheme allows the terminal to notify the network server of an anomaly detected in the IMS dedicated bearer when initiating an IMS call. This informs the network server that the dedicated bearer for the IMS call is faulty, enabling it to promptly switch the IMS call data bearer from the dedicated bearer to the default IMS bearer. This ensures that when the IMS call is established, the terminal continues to transmit IMS call data on the default IMS bearer, achieving direct switching of the IMS call bearer and guaranteeing the continuity of the IMS call.

[0202] Furthermore, when the IMS dedicated bearer is established normally, the terminal can promptly send signaling to the network server to notify that the IMS dedicated bearer has been established normally. This allows the network server to promptly notify the media server to switch the IMS call data bearer from the default IMS bearer to the dedicated IMS bearer. As a result, the terminal can continue to transmit IMS call data on the dedicated IMS bearer. This completes the switching and recovery of the IMS bearer, enabling the terminal to switch to a dedicated IMS bearer that better meets specific QoS transmission requirements when the dedicated IMS bearer is restored to normal operation, thus ensuring the continuity and quality of IMS calls.

[0203] In some embodiments of this application, the situation arises when the IMS dedicated bearer malfunctions during an IMS call, i.e., after the IMS call has been successfully established. For example... Figure 9 As shown, some embodiments of this application provide an IMS call establishment method that may include steps 601 to 613 as described below.

[0204] Step 601: The MO terminal and the MT terminal register with the IMS network and establish the default IMS bearer.

[0205] Step 602: The MO terminal sends a call establishment signaling message to the network server, which then forwards the call establishment signaling message to the MT terminal.

[0206] At this point, the MO terminal needs to establish a dedicated IMS bearer with the network server.

[0207] For example, the call setup signaling here could be an INVITE message.

[0208] Step 603: After receiving the call establishment signaling from the network server, the MT terminal performs the corresponding processing and interface update, and establishes an IMS dedicated bearer between the MT terminal and the network server.

[0209] Step 604: The MT terminal sends a call establishment feedback signaling to the network server and negotiates the corresponding SDP parameters with the network.

[0210] Step 605: After receiving the call establishment feedback signaling from the MT terminal, the network server forwards the call establishment feedback signaling to the MO terminal. The MO terminal updates its interface and status accordingly. At this time, the call between the MO terminal and the MT terminal is successfully established.

[0211] Step 606: After a period of time, at least one of the MO terminal and MT terminal experiences an anomaly in the IMS private bearer with the network server. At least one of the MO terminal and MT terminal sends a private bearer anomaly signaling to the network server to notify the network server that the IMS private bearer is abnormal.

[0212] It should be noted that this is the first signaling added to this solution, namely the first signaling mentioned above. This first signaling is a signaling interaction between the terminal and the network server, and its function is to notify the network server that there is an anomaly in the IMS private bearer. For a related explanation of the first signaling, please refer to the description of the above embodiments, which will not be repeated here.

[0213] Steps 607 to 609 are the same as steps 505 to 507 described above, and can be found in the description of the above embodiments, which will not be repeated here.

[0214] It should be noted that this solution is for cases where the IMS dedicated bearer is abnormal during an IMS call. That is, if the IMS call has already been successfully established through steps 601 to 605, then after executing step 609, the terminal can continue to transmit IMS call data on the default IMS bearer without having to execute steps 508 and 509 of the above implementation method to complete the establishment of the IMS call.

[0215] Steps 610 to 613 are the same as steps 510 to 513 above. For details, please refer to the description of the above embodiments, which will not be repeated here.

[0216] This scheme enables the terminal to notify the network server of any anomalies detected during an IMS call if an anomaly is detected in the dedicated IMS bearer. This allows the network server to become aware of the anomaly and promptly notify the media server to switch the IMS call data bearer from the dedicated IMS bearer to the default IMS bearer. This allows the terminal to continue transmitting IMS call data on the default IMS bearer, achieving direct switching of the IMS call bearer and ensuring the continuity of the IMS call.

[0217] Furthermore, when the IMS dedicated bearer is established normally, the terminal can promptly send signaling to the network server to notify that the IMS dedicated bearer has been established normally. This allows the network server to promptly notify the media server to switch the IMS call data bearer from the default IMS bearer to the dedicated IMS bearer. As a result, the terminal can continue to transmit IMS call data on the dedicated IMS bearer. This completes the switching and recovery of the IMS bearer, enabling the terminal to switch to a dedicated IMS bearer that better meets specific QoS transmission requirements when the dedicated IMS bearer is restored to normal operation, thus ensuring the continuity and quality of IMS calls.

[0218] Figure 10 A schematic diagram of a possible structure of a terminal involved in some embodiments of this application is shown. For example... Figure 10 As shown, the terminal 60 may include: a sending module 61, a receiving module 62, and a transmission module 63.

[0219] The sending module 61 is configured to send a first signaling message to the network server on the IMS default bearer in the event of an IMS dedicated bearer anomaly. This first signaling message notifies the network server of the IMS dedicated bearer anomaly and instructs the network server to send a second signaling message to the media server. This second signaling message notifies the media server of the IMS dedicated bearer anomaly and instructs the media server to switch the bearer of the terminal's IMS call data. The receiving module 62 is configured to receive a first feedback signaling message sent by the network server, which notifies the media server that it has switched the bearer of the IMS call data from the IMS dedicated bearer to the IMS default bearer. The transmitting module 63 is configured to transmit IMS call data on the IMS default bearer according to the first feedback signaling message received by the receiving module 62.

[0220] Some embodiments of this application provide a terminal that, in the event of an IMS dedicated bearer anomaly, can promptly send signaling to the network server to notify of the anomaly. This enables the network server to promptly instruct the media server to perform an IMS call data bearer switching operation. After the media server switches the IMS call data bearer from the IMS dedicated bearer to the IMS default bearer, it feeds back the bearer switching result to the terminal, allowing the terminal to transmit IMS call data on the IMS default bearer. This completes the switching and recovery of the IMS bearer, ensuring that IMS call data can be transmitted directly on other bearers when an IMS dedicated bearer anomaly occurs. This avoids voice problems caused by IMS dedicated bearer anomalies, such as IMS call disconnection or delay, ensuring the continuity of IMS calls and improving the smoothness of user calls.

[0221] In one possible implementation, the aforementioned sending module 61 is specifically used to send SIP messages to the network server over the IMS default bearer. The SIP messages are in the form of INVITE, UPDATE, or NOTIFY signaling.

[0222] In one possible implementation, the SIP message includes at least one of the following: the calling and called party numbers, the media types supported by the terminal, the network capabilities supported by the terminal, the IP information of the terminal, and the reason for the IMS private bearer anomaly.

[0223] In one possible implementation, the sending module 61 is further configured to, after the transmission module 63 transmits IMS call data on the IMS default bearer according to the first feedback signaling, and assuming the IMS dedicated bearer is successfully established, send a third signaling message to the network server on the IMS default bearer. This third signaling message is used to notify that the IMS dedicated bearer has been successfully established. The receiving module 62 is further configured to receive a second feedback signaling message sent by the network server. This second feedback signaling message is used to notify that the media server has switched the bearer of the IMS call data from the IMS default bearer to the IMS dedicated bearer. The transmission module 63 is further configured to transmit IMS call data on the IMS dedicated bearer according to the second feedback signaling received by the receiving module 62.

[0224] In one possible implementation, the sending module 61 is specifically used to send a first signaling message to the network server on the IMS default bearer when initiating an IMS call and in the event of an IMS dedicated bearer malfunction. Alternatively, the sending module 61 is specifically used to send a first signaling message to the network server on the IMS default bearer during an IMS call and in the event of an IMS dedicated bearer malfunction.

[0225] In some embodiments of this application, the IMS call establishment device can be a terminal or a component within the terminal, such as an integrated circuit or a chip. Exemplary examples include mobile phones, tablets, laptops, PDAs, in-vehicle electronic devices, mobile internet devices (MIDs), augmented reality (AR) / virtual reality (VR) devices, robots, wearable devices, ultra-mobile personal computers (UMPCs), netbooks, or personal digital assistants (PDAs), etc. It can also be a server, network attached storage (NAS), a personal computer (PC), a television set (TV), an ATM, or a self-service machine, etc. Some embodiments of this application do not specifically limit the scope of the device.

[0226] In some embodiments of this application, the terminal can be a terminal with an operating system. This operating system can be Android, iOS, or other possible operating systems; however, some embodiments of this application do not impose specific limitations.

[0227] Some embodiments of this application provide terminals that can implement the various processes implemented in the above method embodiments. To avoid repetition, they will not be described again here.

[0228] Figure 11 A schematic diagram of a possible structure of the server involved in some embodiments of this application is shown. For example... Figure 11 As shown, the server 70 may include a receiving module 71, a switching module 72, and a sending module 73.

[0229] The receiving module 71 is used to receive a second signaling message sent by the network server. This second signaling message is used to notify the media server of an anomaly in the IMS dedicated bearer and to instruct the media server to switch the bearer of the terminal's IMS call data. This second signaling message is generated based on a first signaling message received by the network server from the terminal. This first signaling message is used to notify the network server of the anomaly in the IMS dedicated bearer and to instruct the network server to send the second signaling message to the media server. The switching module 72 is used to switch the bearer of the IMS call data from the IMS dedicated bearer to the IMS default bearer according to the second signaling message received by the receiving module 71. The sending module 73 is used to send a third feedback signaling message to the network server. This third feedback signaling message is used to notify the network server that the bearer of the IMS call data has been switched from the IMS dedicated bearer to the IMS default bearer.

[0230] Some embodiments of this application provide a server in which a media server can detect an anomaly in the IMS dedicated bearer based on a second signaling sent by a network server. This allows the media server to promptly switch the IMS call data bearer from the IMS dedicated bearer to the IMS default bearer and send feedback on the bearer switch result to the network server. This enables the terminal to transmit IMS call data on the IMS default bearer. By adding a handover recovery signaling process between the network server and the media server, the media server can switch the IMS call data to other bearers for transmission. This completes the handover and recovery of the IMS bearer, ensuring that when an IMS dedicated bearer anomaly occurs, IMS call data can be directly transmitted on other bearers. This avoids voice problems caused by IMS dedicated bearer anomalies, such as IMS call disconnection or delay, ensuring the continuity of IMS calls and improving the smoothness of user calls.

[0231] In one possible implementation, the receiving module 71 is specifically used to receive SIP messages or request-response signaling sent by the network server, wherein the SIP message is in the form of INVITE signaling.

[0232] In one possible implementation, the SIP message includes at least one of the following: the calling and called party numbers, the media types supported by the terminal, the network capabilities supported by the terminal, the IP address of the network server, and the duration of the bearer timeout timer. The duration information indicates when the media server sends a Notify message to the network server, which inquires whether the network server should continue maintaining the current bearer.

[0233] In one possible implementation, the receiving module 71 is further configured to receive a fourth signaling message sent by the network server after the sending module 73 sends a third feedback signaling message to the network server. This fourth signaling message is used to notify the media server that the IMS dedicated bearer has been successfully established and to instruct the media server to switch the bearer of the terminal's IMS call data. The switching module 72 is further configured to switch the bearer of the terminal's IMS call data from the IMS default bearer to the IMS dedicated bearer according to the fourth signaling message received by the receiving module 71. The sending module 73 is further configured to send a fourth feedback signaling message to the network server, which is used to notify the network server that the bearer of the IMS call data has been switched from the IMS default bearer to the IMS dedicated bearer.

[0234] In one possible implementation, the receiving module 71 is specifically used to receive SIP messages or request-response signaling sent by the network server, wherein the SIP message is a CANCEL signaling.

[0235] The servers provided in some embodiments of this application can implement the various processes implemented by the media server in the above method embodiments. To avoid repetition, they will not be described again here.

[0236] Optionally, such as Figure 12 As shown, some embodiments of this application also provide an electronic device 900, including a processor 901 and a memory 902. The memory 902 stores a program or instructions that can run on the processor 901. When the program or instructions are executed by the processor 901, they implement the various steps of the above method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0237] It should be noted that the electronic devices in some embodiments of this application include the mobile electronic devices and non-mobile electronic devices described above.

[0238] Figure 13 A schematic diagram of the hardware structure of an electronic device for implementing some embodiments of this application.

[0239] The electronic device 100 includes, but is not limited to, components such as: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, and processor 110.

[0240] Those skilled in the art will understand that the electronic device 100 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 110 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 13 The electronic device structure shown does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0241] In some embodiments of this application, the electronic device may be a terminal or other devices besides a terminal.

[0242] The radio frequency unit 101 is used for:

[0243] In the event of an IMS dedicated bearer anomaly, a first signaling message is sent to the network server on the IMS default bearer. This first signaling message is used to notify the network server of the IMS dedicated bearer anomaly and to instruct the network server to send a second signaling message to the media server. This second signaling message is used to notify the media server of the IMS dedicated bearer anomaly and to instruct the media server to switch the bearer of the terminal's IMS call data. A first feedback signaling message is received from the network server, which is used to notify that the media server has switched the bearer of the IMS call data from the IMS dedicated bearer to the IMS default bearer. Based on the first feedback signaling message, IMS call data is transmitted on the IMS default bearer.

[0244] Some embodiments of this application provide an electronic device that, in the event of an IMS dedicated bearer anomaly, can promptly send a signaling message to a network server to notify that the IMS dedicated bearer is abnormal. This allows the network server to promptly instruct a media server to perform an IMS call data bearer switching operation. After the media server switches the IMS call data bearer from the IMS dedicated bearer to the IMS default bearer, it feeds back the bearer switching result to the electronic device, enabling the electronic device to transmit IMS call data on the IMS default bearer. This completes the switching and recovery of the IMS bearer, allowing IMS call data to be transmitted directly on other bearers when an IMS dedicated bearer anomaly occurs. This avoids voice problems caused by IMS dedicated bearer anomalies, such as IMS call disconnection or delay, ensuring the continuity of IMS calls and improving the smoothness of user calls.

[0245] Optionally, the radio frequency unit 101 is specifically used to send SIP messages to the network server on the IMS default bearer. The SIP messages are in the form of INVITE, UPDATE, or NOTIFY signaling.

[0246] Optionally, the above SIP message includes at least one of the following: the calling and called party numbers, the media types supported by the terminal, the network capabilities supported by the terminal, the IP information of the terminal, and the reason for the IMS private bearer anomaly.

[0247] Optionally, the radio frequency unit 101 is further configured to: after transmitting IMS call data on the IMS default bearer according to the first feedback signaling, and under the condition that the IMS dedicated bearer has been established normally, send a third signaling to the network server on the IMS default bearer, the third signaling being used to notify that the IMS dedicated bearer has been established normally; and receive a second feedback signaling sent by the network server, the second feedback signaling being used to notify that the media server has switched the bearer of the IMS call data from the IMS default bearer to the IMS dedicated bearer; and transmit IMS call data on the IMS dedicated bearer according to the received second feedback signaling.

[0248] Optionally, the radio frequency unit 101 is specifically used to send a first signaling message to the network server on the IMS default bearer when initiating an IMS call or when the IMS dedicated bearer is abnormal. Alternatively, the radio frequency unit 101 is specifically used to send a first signaling message to the network server on the IMS default bearer during an IMS call or when the IMS dedicated bearer is abnormal.

[0249] The electronic devices provided in some embodiments of this application can implement the various processes implemented in the above method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0250] For details on the beneficial effects of the various implementation methods in this embodiment, please refer to the beneficial effects of the corresponding implementation methods in the above method embodiments. To avoid repetition, these will not be repeated here.

[0251] It should be understood that in some embodiments of this application, the input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 107 includes at least one of a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0252] The memory 109 can be used to store software programs and various data. The memory 109 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 109 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). Memory 109 in some embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0253] Processor 110 may include one or more processing units; optionally, processor 110 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 110.

[0254] Figure 14 This is a schematic diagram of the hardware structure of a server provided for some embodiments of this application. The server can be the aforementioned media server. Figure 14 As shown, the server 1600 may include one or more processors 1601, memory 1602, communication interface 1603, and bus 1604.

[0255] The processor 1601 is configured to receive a second signaling message sent by the network server via a bus 1604 and a communication interface 1603. The second signaling message is used to notify the media server that there is an anomaly in the IMS dedicated bearer and to instruct the media server to switch the bearer of the terminal's IMS call data. The second signaling message is generated based on the network server receiving a first signaling message sent by the terminal. The first signaling message is used to notify the network server that there is an anomaly in the IMS dedicated bearer and to instruct the network server to send the second signaling message to the media server. Furthermore, according to the second signaling message, the processor switches the bearer of the IMS call data from the IMS dedicated bearer to the IMS default bearer and sends a third feedback signaling message to the network server via the bus 1604 and the communication interface 1603. The third feedback signaling message is used to notify the network server that the bearer of the IMS call data has been switched from the IMS dedicated bearer to the IMS default bearer.

[0256] Optionally, the processor 1601 is specifically configured to receive SIP messages or request-response signaling sent by the network server via the bus 1604 and the communication interface 1603, wherein the SIP message is in the form of INVITE signaling.

[0257] Optionally, the SIP message may include at least one of the following: the calling and called party numbers, the media types supported by the terminal, the network capabilities supported by the terminal, the IP address of the network server, and the duration of the bearer timeout timer. The duration information indicates when the media server sends a Notify message to the network server, which inquires whether the network server should continue maintaining the current bearer.

[0258] Optionally, the processor 1601 is further configured to, after sending a third feedback signaling to the network server via the bus 1604 and the communication interface 1603, receive a fourth signaling sent by the network server, the fourth signaling being used to notify the media server that the IMS dedicated bearer has been successfully established and to instruct the media server to switch the bearer of the terminal's IMS call data; and according to the fourth signaling, switch the bearer of the terminal's IMS call data from the IMS default bearer to the IMS dedicated bearer, and send a fourth feedback signaling to the network server via the bus 1604 and the communication interface 1603, the fourth feedback signaling being used to notify the network server that the bearer of the IMS call data has been switched from the IMS default bearer to the IMS dedicated bearer.

[0259] Optionally, the processor 1601 is specifically configured to receive SIP messages or request-response signaling sent by the network server via the bus 1604 and the communication interface 1603, wherein the SIP message is a CANCEL signaling.

[0260] The servers provided in some embodiments of this application can implement the various processes implemented in the above method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0261] For details on the beneficial effects of the various implementation methods in this embodiment, please refer to the beneficial effects of the corresponding implementation methods in the above method embodiments. To avoid repetition, these will not be repeated here.

[0262] In some embodiments of this application, one or more processors 1601, memory 1602, and communication interface 1603 are interconnected via bus 1604. Bus 1604 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Bus 1604 can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 14 The bus is represented by a single thick line, but this does not indicate that there is only one bus or one type of bus. Additionally, the server 1600 may include some functional modules not shown, which will not be described further here.

[0263] Optionally, some embodiments of this application also provide a server, including Figure 14 The processor 1601 and memory 1602 shown are stored in the memory 1602 and can run on the processor 1601. When the computer program is executed by the processor 1601, it implements the various processes of the above method embodiments and can achieve the same technical effect, which will not be described again here.

[0264] Some embodiments of this application also provide a readable storage medium storing a program or instructions that, when executed by a processor, implement the various processes of the above method embodiments and achieve the same technical effect. To avoid repetition, these will not be described again here.

[0265] The processor is the processor in the electronic device or server described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0266] Some embodiments of this application also provide a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0267] It should be understood that the chips mentioned in some embodiments of this application may also be referred to as system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0268] Some embodiments of this application provide a computer program product that is stored in a storage medium and executed by at least one processor to implement the various processes of the above method embodiments and achieve the same technical effects. To avoid repetition, further details are omitted here.

[0269] Some embodiments of this application also provide a communication system, including: a terminal and a server, wherein the terminal can be used to perform the steps of the IMS call establishment method as described above, and the server can be used to perform the steps of the IMS call establishment method as described above.

[0270] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0271] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0272] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for establishing an IMS call, characterized in that, The method includes: In the event of an IMS dedicated bearer anomaly, the terminal sends a first signaling message to the network server on the IMS default bearer. The first signaling message is used to notify the network server that the IMS dedicated bearer is abnormal and to instruct the network server to send a second signaling message to the media server. The second signaling message is used to notify the media server that the IMS dedicated bearer is abnormal and to instruct the media server to switch the bearer of the terminal's IMS call data. The terminal receives a first feedback signaling sent by the network server. The first feedback signaling is used to notify the media server that the bearer of IMS call data has been switched from the IMS dedicated bearer to the IMS default bearer. The terminal transmits IMS call data on the IMS default bearer according to the first feedback signaling.

2. The method according to claim 1, characterized in that, The terminal sends a first signaling message to the network server on the IMS default bearer, including: The terminal sends a Session Initiation Protocol (SIP) message to the network server on the IMS default bearer. The SIP message is in the form of INVITE, UPDATE, or NOTIFY.

3. The method according to claim 2, characterized in that, The SIP message includes at least one of the following: the calling and called party numbers, the media types supported by the terminal, the network capabilities supported by the terminal, the IP information of the terminal, and the reason for the IMS private bearer anomaly.

4. The method according to claim 1, characterized in that, After the terminal transmits IMS call data on the IMS default bearer according to the first feedback signaling, the method further includes: When the IMS dedicated bearer is established normally, the terminal sends a third signaling message to the network server on the IMS default bearer. The third signaling message is used to notify that the IMS dedicated bearer has been established normally. The terminal receives a second feedback signaling sent by the network server. The second feedback signaling is used to notify the media server that the bearer of IMS call data has been switched from the IMS default bearer to the IMS dedicated bearer. The terminal transmits IMS call data on the IMS dedicated bearer according to the second feedback signaling.

5. The method according to claim 1, characterized in that, In the event of an IMS dedicated bearer anomaly, the terminal sends a first signaling message to the network server on the IMS default bearer, including: When initiating an IMS call, if the IMS dedicated bearer is abnormal, the terminal sends the first signaling to the network server on the IMS default bearer; or, During an IMS call, if the IMS dedicated bearer malfunctions, the terminal sends the first signaling message to the network server on the IMS default bearer.

6. A method for establishing an IMS call, characterized in that, The method includes: The media server receives a second signaling message sent by the network server. The second signaling message is used to notify the media server that there is an anomaly in the IMS dedicated bearer and to instruct the media server to switch the bearer of the terminal's IMS call data. The second signaling message is generated based on the first signaling message sent by the terminal received by the network server. The first signaling message is used to notify the IMS dedicated bearer that there is an anomaly and to instruct the network server to send the second signaling message to the media server. According to the second signaling, the media server switches the bearer of IMS call data from the IMS dedicated bearer to the IMS default bearer, and sends a third feedback signaling to the network server. The third feedback signaling is used to notify the network server that the bearer of IMS call data has been switched from the IMS dedicated bearer to the IMS default bearer.

7. The method according to claim 6, characterized in that, The media server receives a second signaling message sent by the network server, including: The media server receives SIP messages or request / response signaling sent by the network server, wherein the SIP messages are in INVITE format.

8. The method according to claim 7, characterized in that, The SIP message includes at least one of the following: the calling and called party numbers, the media types supported by the terminal, the network capabilities supported by the terminal, the IP information of the network server, and the duration information of the bearer timeout timer; The duration information indicates when the media server sends a Notify message to the network server, and the Notify message is used to inquire whether the network server should continue to maintain the current bearer.

9. The method according to claim 6, characterized in that, After sending the third feedback signaling to the network server, the method further includes: The media server receives a fourth signaling message sent by the network server. The fourth signaling message is used to notify the media server that the IMS dedicated bearer has been established normally and to instruct the media server to switch the bearer of the terminal's IMS call data. According to the fourth signaling, the media server switches the bearer of the terminal's IMS call data from the IMS default bearer to the IMS dedicated bearer, and sends a fourth feedback signaling to the network server. The fourth feedback signaling is used to notify the network server that the bearer of the IMS call data has been switched from the IMS default bearer to the IMS dedicated bearer.

10. The method according to claim 9, characterized in that, The media server receives the fourth signaling sent by the network server, including: The media server receives SIP messages or request / response signaling sent by the network server, wherein the SIP message is a CANCEL signaling message.

11. A terminal, characterized in that, The terminal includes: The sending module is used to send a first signaling message to the network server on the IMS default bearer in the event of an IMS dedicated bearer anomaly. The first signaling message is used to notify the network server that the IMS dedicated bearer is abnormal and to instruct the network server to send a second signaling message to the media server. The second signaling message is used to notify the media server that the IMS dedicated bearer is abnormal and to instruct the media server to switch the bearer of the terminal's IMS call data. The receiving module is used to receive a first feedback signaling sent by the network server. The first feedback signaling is used to notify the media server that the bearer of IMS call data has been switched from the IMS dedicated bearer to the IMS default bearer. The transmission module is used to transmit IMS call data on the IMS default bearer according to the first feedback signaling received by the receiving module.

12. The terminal according to claim 11, characterized in that, The sending module is specifically used to send a Session Initiation Protocol (SIP) message to the network server on the IMS default bearer. The SIP message is in the form of INVITE, UPDATE, or NOTIFY.

13. The terminal according to claim 12, characterized in that, The SIP message includes at least one of the following: the calling and called party numbers, the media types supported by the terminal, the network capabilities supported by the terminal, the IP information of the terminal, and the reason for the IMS private bearer anomaly.

14. The terminal according to claim 11, characterized in that, The sending module is further configured to send a third signaling message to the network server on the IMS default bearer after the transmission module transmits IMS call data on the IMS default bearer according to the first feedback signaling message, provided that the IMS dedicated bearer is established normally. The third signaling message is used to notify the IMS dedicated bearer that it has been established normally. The receiving module is further configured to receive a second feedback signaling sent by the network server, the second feedback signaling being used to notify the media server that the bearer of the IMS call data has been switched from the IMS default bearer to the IMS dedicated bearer; The transmission module is further configured to transmit IMS call data on the IMS dedicated bearer according to the second feedback signaling received by the receiving module.

15. The terminal according to claim 11, characterized in that, The sending module is specifically used to send the first signaling to the network server on the IMS default bearer when initiating an IMS call or when the IMS dedicated bearer is abnormal. or, The sending module is specifically used to send the first signaling to the network server on the IMS default bearer during an IMS call or in the event of an IMS dedicated bearer malfunction.

16. A server, characterized in that, The server includes: The receiving module is used to receive a second signaling sent by the network server. The second signaling is used to notify the media server that there is an anomaly in the IMS dedicated bearer and to instruct the media server to switch the bearer of the terminal's IMS call data. The second signaling is generated based on the first signaling sent by the terminal received by the network server. The first signaling is used to notify the IMS dedicated bearer that there is an anomaly and to instruct the network server to send the second signaling to the media server. The switching module is used to switch the bearer of IMS call data from the IMS dedicated bearer to the IMS default bearer according to the second signaling received by the receiving module. The sending module is used to send a third feedback signaling to the network server, the third feedback signaling being used to notify the network server that the bearer of IMS call data has been switched from the IMS dedicated bearer to the IMS default bearer.

17. The server according to claim 16, characterized in that, The receiving module is specifically used to receive SIP messages or request-response signaling sent by the network server, wherein the SIP message is in INVITE format.

18. The server according to claim 17, characterized in that, The SIP message includes at least one of the following: the calling and called party numbers, the media types supported by the terminal, the network capabilities supported by the terminal, the IP information of the network server, and the duration information of the bearer timeout timer; The duration information indicates when the media server sends a Notify message to the network server, and the Notify message is used to inquire whether the network server should continue to maintain the current bearer.

19. The server according to claim 16, characterized in that, The receiving module is further configured to receive a fourth signaling sent by the network server after the sending module sends a third feedback signaling to the network server. The fourth signaling is used to notify the media server that the IMS dedicated bearer has been established normally and to instruct the media server to switch the bearer of the terminal's IMS call data. The switching module is further configured to switch the bearer of the terminal's IMS call data from the IMS default bearer to the IMS dedicated bearer according to the fourth signaling received by the receiving module; The sending module is further configured to send a fourth feedback signaling to the network server, the fourth feedback signaling being used to notify the network server that the bearer of IMS call data has been switched from the IMS default bearer to the IMS dedicated bearer.

20. The server according to claim 19, characterized in that, The receiving module is specifically used to receive SIP messages or request-response signaling sent by the network server, wherein the SIP message is a CANCEL signaling message.

21. An electronic device, characterized in that, It includes a processor and a memory, the memory storing programs or instructions that can run on the processor, the programs or instructions being executed by the processor to implement the steps of the IMS call establishment method as described in any one of claims 1-5.

22. A server, characterized in that, It includes a processor and a memory, the memory storing programs or instructions that can run on the processor, the programs or instructions being executed by the processor to implement the steps of the IMS call establishment method as described in any one of claims 6-10.

23. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the IMS call establishment method as described in any one of claims 1-5.

24. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the IMS call establishment method as described in any one of claims 6-10.

Images