CN113992634B

CN113992634B - Call establishment method and related device

Info

Publication number: CN113992634B
Application number: CN202111614409.9A
Authority: CN
Inventors: 李海波
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2021-12-28
Filing date: 2021-12-28
Publication date: 2022-06-03
Anticipated expiration: 2041-12-28
Also published as: CN113992634A

Abstract

The embodiment of the application provides a call establishment method and a related device, and is applied to the technical field of terminals. The method comprises the following steps: the second device receiving a video call request originating from the first device; the second equipment sends a temporary response message to the core network equipment based on the video call request; when the second equipment receives a first message from the core network equipment, the second equipment establishes a voice bearer, and the first message is used for indicating to activate the voice bearer; when the second device receives a second message from the core network device, the second device sends a third message to the first device; the second message is used for indicating that the video bearer cannot be established; the third message is used to indicate voice bearer establishment. Therefore, the second device can identify that the core network does not support the establishment of the video bearer according to the message of the core network, reduce the situation that the call is cancelled due to waiting for the establishment of the video bearer, and improve the call rate. In addition, the degradation waiting time can be reduced, and the user experience is improved.

Description

Call establishment method and related device

Technical Field

The present application relates to the field of terminal technologies, and in particular, to a call setup method and a related device.

Background

With the development of communication technology, more and more multimedia services, such as Video Sharing (VS), voice over long term evolution (VoLTE) voice over IP (VoIP), video and voice over IP (V2 IP), push to talk (PoC), and the like, can be deployed under an IP Multimedia Subsystem (IMS) network.

For example, when both the first device and the second device are deployed in an IMS network, the first device may initiate a video call to the second device over the IMS network.

However, when a first device initiates a video call to a second device through an IMS network, a call failure may occur, resulting in a low call completion rate.

Disclosure of Invention

The embodiment of the application provides a call establishment method and a related device, and when a second device identifies that a network cannot support video bearing, video is degraded into voice. Therefore, the method is converted into voice communication, and the call completing rate is improved.

In a first aspect, an embodiment of the present application provides a call setup method, which is applied to a second device.

The method comprises the following steps: the second device receiving a video call request originating from the first device; the second equipment sends a temporary response message to the core network equipment based on the video call request; when the second equipment receives a first message from the core network equipment, the second equipment establishes a voice bearer, and the first message is used for indicating to activate the voice bearer; when the second device receives a second message from the core network device, the second device sends a third message to the first device; the second message is used for indicating that the video bearer cannot be established; the third message is used to indicate voice bearer establishment.

The first device may also be referred to as a calling end; the second device may also be referred to as a called end. The core network device may be a second core network device below. Therefore, the second device can confirm that the core network does not support the establishment of the video bearer according to the message of the core network, and establishes the voice call with the first device, thereby reducing the situation of call failure and improving the call completing rate.

Optionally, the second message is bearer deactivation information, and a bearer identifier in the bearer deactivation information is not established.

Optionally, when the second device receives the second message from the core network device, the sending, by the second device, the third message to the first device includes: the second equipment sets a timer when receiving the second message; and when the second equipment does not receive the fourth message before the timer is overtime, the second equipment sends a third message to the first equipment, wherein the fourth message is used for indicating the activation of the video bearer.

Therefore, the judgment error that the second equipment cannot establish the video bearer for the core network equipment can be reduced.

Optionally, the second device stores historical failure conditions, where the historical failure conditions include: cell information corresponding to the video bearing can not be established; when the second device receives the second message from the core network device, the second device sends a third message to the first device, including: and when the second equipment receives the second message and the corresponding cell information is consistent with the cell information where the second equipment is located when the video bearer cannot be established, the second equipment sends a third message to the first equipment.

Therefore, the accuracy of the second device in judging that the core network device cannot establish the video bearer can be increased, and the judgment error is reduced.

Optionally, the method further comprises: the second device receives a network fault table originated from the cloud server, and the network fault table comprises: cell information which does not support video bearing; when the second device receives the second message from the core network device, the second device sends a third message to the first device, including: and when the second equipment receives the second message and the cell information where the second equipment is located is consistent with the cell information which does not support the video bearer, the second equipment sends a third message to the first equipment.

Optionally, the method further comprises: the second equipment sends a fifth message to the first equipment, wherein the fifth message is used for indicating the maximum bandwidth AS value corresponding to the second equipment; the method comprises the steps that a second device receives a call request sent by a first device by adopting an AS value when the first device meets a first preset condition, the first preset condition is that the first device receives a first operation within a preset time length, and the first operation is used for indicating to start calling the second device.

Therefore, the first device can initiate a call according to the previously negotiated AS value, thereby reducing the situation of call failure and increasing the call completing rate of the call.

In a second aspect, an embodiment of the present application provides a call setup method, which is applied to a first device, and the method includes: the first equipment sends a video call request to the second equipment; the first equipment receives a third message from the second equipment, wherein the third message is used for indicating voice bearing establishment; the third message is sent by the second device after meeting a second preset condition, where the second preset condition includes: the second device receives a first message from the core network device and a second message from the core network device, wherein the first message is used for indicating to activate the voice bearer, and the second message is used for indicating that the video bearer cannot be established.

Optionally, the second preset condition further includes: the second device does not receive the fourth message before the timer times out, and the timer is set when the second device receives the second message.

Optionally, the second preset condition further includes: the cell information where the second equipment is located is consistent with the first cell information; the first cell information is corresponding cell information when the video bearer cannot be established in historical failure conditions stored by the second device.

Optionally, the second preset condition further includes: the cell information where the second device is located is consistent with the second cell information; the second cell information is cell information which does not support video bearing and corresponds to a network fault table, and the network fault table is originated from a cloud server.

Optionally, the method further comprises: after receiving the third message, the first device displays a first interface, where the first interface includes: an indication that the second device does not support video telephony.

Optionally, the method further comprises: the first equipment receives a fifth message from the second equipment, wherein the fifth message is used for indicating the maximum bandwidth AS value corresponding to the second equipment; the first equipment stores call parameters when the call fails, wherein the call parameters comprise: an identity and an AS value of the second device; when the first equipment receives a first operation within a preset time length, the first equipment sends a call request by adopting the call parameters, and the first operation is used for indicating to start calling the second equipment.

Optionally, the call parameters further include: the moment of origination of the call; and when the difference between the time when the first equipment receives the first operation and the calling starting time is less than the preset time length, the first equipment sends a calling request by adopting the communication parameters.

In a third aspect, an embodiment of the present application provides an electronic device, including: a processor and a memory; the memory stores computer-executable instructions; the processor executes computer-executable instructions stored by the memory to cause the processor to perform the method of the first aspect or to perform the method of the second aspect.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium, in which a computer program or instructions are stored, and when the computer program or instructions are executed, the method of the first aspect or the method of the second aspect is implemented.

In a fifth aspect, embodiments of the present application provide a computer program product comprising a computer program or instructions which, when executed by a processor, implement the method of the first aspect or the method of the second aspect.

For the beneficial effects of the possible implementations of the second aspect to the fifth aspect, reference may be made to the beneficial effects of the possible implementations of the first aspect and the first aspect, and details are not described here again.

Drawings

Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application;

fig. 2 is a schematic diagram of a video call setup procedure in a possible implementation;

FIG. 3A is a schematic diagram of a contact 1 interface of a first device in a possible implementation;

FIG. 3B is a schematic diagram of a video call waiting interface of a first device in a possible implementation;

FIG. 3C is a schematic diagram of a contact interface of a first device in a possible implementation;

FIG. 4A is a schematic diagram of a contact 1 interface of a first device in a possible implementation;

FIG. 4B is a schematic diagram of a video call waiting interface of a first device in a possible implementation;

FIG. 4C is a schematic diagram of a voice call interface of a first device in a possible implementation;

FIG. 4D is a schematic diagram of a contact 1 interface of a first device in a possible implementation;

fig. 5 is a schematic diagram of a call setup procedure according to an embodiment of the present application;

fig. 6A is a schematic view of a contact 1 interface of a first device according to an embodiment of the present application;

fig. 6B is a schematic view of a video call waiting interface of a first device according to an embodiment of the present disclosure;

fig. 6C is a schematic diagram of a voice call waiting interface of a first device according to an embodiment of the present application;

fig. 6D is a schematic diagram of a voice call interface of a first device according to an embodiment of the present application;

fig. 6E is a schematic view of a contact 1 interface of a first device according to an embodiment of the present application;

fig. 7 is a flowchart illustrating a call setup method according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same or similar items having substantially the same function and action. For example, the first device and the second device are only used for distinguishing different devices, and the sequence order thereof is not limited. Those skilled in the art will appreciate that the terms "first," "second," etc. do not denote any order or quantity, nor do the terms "first," "second," etc. denote any order or importance.

It is noted that, in the present application, words such as "exemplary" or "for example" are used to mean exemplary, illustrative, or descriptive. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

It should be noted that the network architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not constitute a limitation to the technical solution provided in the embodiment of the present application, and it is known by a person skilled in the art that the technical solution provided in the embodiment of the present application is also applicable to similar technical problems along with the evolution of the network architecture and the appearance of a new service scenario.

The call establishment method of the embodiment of the present application can be applied to various communication systems, for example: code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, LTE-advanced long term evolution (LTE-A) system, New Radio (NR) system, evolution system of NR system, LTE-based (LTE-based) system on unlicensed band, NR (NR-based access to unlicensed band, UMTS-U) system on unlicensed band, UMTS-based (UMTS-based) system on mobile communication, WiMAX), a Wireless Local Area Network (WLAN), a wireless fidelity (WiFi), a fifth generation (5 th generation, 5G) mobile communication system, a next generation communication system, or other communication systems. The 5G mobile communication system may include a non-independent Network (NSA) and/or an independent network (SA), among others.

The technical scheme provided by the embodiment of the application can also be applied to Machine Type Communication (MTC), Long Term Evolution-machine (Long Term Evolution-machine) communication, device-to-device (D2D) network, machine-to-machine (M2M) network, internet of things (IoT) network, or other networks. The IoT network may comprise, for example, a car networking network. The communication modes in the car networking system are collectively referred to as a vehicle-to-other device (V2X, X may represent anything) system, for example, the V2X may include: vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian (V2P) or vehicle to network (V2N) communication, etc. The technical scheme provided by the application can also be applied to future communication systems, such as a sixth generation mobile communication system and the like. This is not a limitation of the present application.

Exemplarily, fig. 1 is a schematic structural diagram of a communication system provided in an embodiment of the present application, and as shown in fig. 1, the communication system includes: a first device 101, a first core network 102, an IMS network 103, a second core network 104, and a second device 105.

The first device 101 is used for video calling the second device 105, and the first device 101 may also be referred to as a calling end. The second device 105 is used to respond to the call of the first device 101, and the second device 105 may also be referred to as a called end.

The first device 101 and the second device 105 are both electronic devices with communication functions, and the electronic devices include terminal devices, which may also be referred to as terminals (terminal), User Equipment (UE), Mobile Stations (MS), Mobile Terminals (MT), and the like. The terminal device may be a mobile phone (mobile phone), a smart television (or called a large screen or a smart screen), a wearable device, a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self-driving (self-driving), a wireless terminal in remote surgery (remote management), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), and so on. The embodiment of the present application does not limit the specific technology and the specific device form adopted by the terminal device.

The first device 101 and the second device 105 may be the same or different. The embodiment of the present application does not limit this.

The first core network 102 is configured to connect the call request or the data request transmitted by the first device 101 to the IMS network 103. The IMS network 103 is configured to determine the second core network 104 and the second device 105 according to the call request or the data request. The second core network 104 is configured to transmit the call request or the data request transmitted by the IMS network 103 to the second device 105.

The first core network 102 and the second core network 104 may each include one or more core network devices. The core network device may include: user plane network elements (UPF). The UPF, i.e. a data plane gateway, may be used for packet routing and forwarding, or quality of service (QoS) processing of user plane data, and the like, and the user data may be accessed into the network through the network element.

In the embodiment of the present application, the core network device for performing the following call setup method may be, for example, a UPF or other network elements having the same or similar functions as the UPF. The core network device may also include functional network elements of other core networks, for example, network open function (NEF), Session Management Function (SMF), Policy Control Function (PCF), and other network elements. Among them, the NEF can be used to securely open services and capabilities, etc. provided by the 3GPP network functions to the outside; the SMF is mainly used for session management, IP address allocation and management of a terminal, selection of a termination point of an interface capable of managing a user plane function, policy control, or a charging function, downlink data notification, and the like; the PCF may be used to guide a unified policy framework of network behavior, provide policy rule information for control plane functional network elements (e.g., SMFs, etc.), and the like.

It will be appreciated that data exchanged between the device and the core network is typically forwarded by the access network device. The access network device may be any device with wireless transceiving function. Access network devices include, but are not limited to: evolved Node B (eNB), Node B (NB), Radio Network Controller (RNC), Base Station Controller (BSC), Base Transceiver Station (BTS), home base station (e.g., home evolved Node B, or home Node B, HNB), baseband unit (BBU), Access Point (AP) in a wireless network system, Radio Relay Node (RRN), radio backhaul Node, Transmission Point (TP), or transmission and reception point (BBU), etc., and may also be 5G, such as NR, a gbb in a system, or a TRP, transmission point (TRP or TP), a group (including multiple antennas) of a base station in a 5G system, or a panel of a network, and may also be a panel of a network or a panel of a network, such as a baseband unit (BBU), or a Distributed Unit (DU), etc. It is understood that all or part of the functions of the access network device in the present application may also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform (e.g., a cloud platform).

Specifically, data exchanged between the device and the core network is usually forwarded by the base station. The base station may be: a macro base station, a micro base station, a pico base station, a small station, a relay station, a balloon station, or the like. If a plurality of network devices exist in the communication system, the plurality of network devices may be base stations of the same type or different types; the multiple base stations may support the same technology network as mentioned above, or may support different technologies networks as mentioned above. The base station may communicate with the terminal, or may communicate with the terminal through the relay station.

With the development of communication technology, more and more multimedia services, such as Video Sharing (VS), voice over IP (VoIP), video and voice over IP (V2 IP) and push to talk (PoC), etc., can be deployed under an IP Multimedia Subsystem (IMS) network.

For example, when both the first device and the second device are deployed in an IMS network, the first device may initiate a video call to the second device through the IMS network.

However, the first device may fail or be degraded from video to voice while calling the second device. Specifically, when the first device is in a video call, and the requested application-specific maximum bandwidth (AS) is large, the call may fail or be degraded from video to voice. Further, it may result in low call completion rate and long call waiting time.

Illustratively, a video call of a first type device with an A chip has a failure or a call to voice of a second type device with a B chip, and the video call between the second type devices has no problem. Specifically, for example, the first type of device is a chip a mobile phone, and the second type of device is a chip B mobile phone, the chip a mobile phone calls the chip B mobile phone in a video mode, and the call fails or the call is switched to voice; the video of the B chip mobile phone calls the B chip mobile phone, and the video call is successfully established; the B chip mobile phone or the A chip mobile phone starts to call the A chip mobile phone by video, and the call is converted into voice. It can be understood that handsets with different chips request different AS values during a video call. The AS requested by the chip A mobile phone is larger, and the AS requested by the chip B mobile phone is smaller.

The following describes a video call setup procedure in a possible implementation. Fig. 2 is a schematic diagram illustrating an exemplary video call setup procedure in a possible implementation. As shown in fig. 2, includes:

s201, when the first device receives a trigger operation for indicating the video to call the second device, the first device sends a first instruction for indicating the video to start calling to a first core network.

The first instruction carries an AS value corresponding to the first device and identification information of the second device. The identification information of the second device includes, but is not limited to: telephone number and IP address, etc.

S202, when receiving the instruction for instructing video origination, the first core network sends an invite (invite) message to the second device via the IMS network and the second core network to request establishment of a video call.

The invite message carries information indicating the video call and identification information of the second device.

S203, after receiving the invite message, the second device feeds back a temporary response (100 trying) message to the first device through the second core network, the IMS network, and the first core network, so as to indicate that the second device receives the invite message.

In a possible implementation manner, after receiving the invite message, the IMS network feeds back a temporary response (100 trying) message to the first device through the first core network to indicate that the IMS network receives the invite message. After receiving the invite message, the second device feeds back a temporary response (100 trying) message to the IMS network through the second core network to indicate that the second device receives the invite message.

S204, after receiving the 100 trying message transmitted by the second core network, the IMS network sends a bearer establishment request to the first core network, and adaptively, a bearer is established between the IMS network and the first core network.

After establishing a bearer with the IMS network, the first core network establishes a voice bearer and a video bearer with the first device.

S205, the first core network sends an instruction for instructing establishment of a voice bearer to the first device.

S206, the first core network sends an instruction for indicating the establishment of the video bearer to the first equipment.

And S207, after receiving the invite message, the second device sends a session progress (183 session progress) message to the first device through the second core network, the IMS network and the first core network so as to indicate the progress of the video call.

And S208, after receiving the 183 session progress message transmitted by the second device, the IMS network sends a bearer establishment request to the second core network, and adaptively establishes a bearer between the IMS network and the second core network.

S209, the second core network sends an instruction for instructing establishment of a voice bearer to the second device.

S210, when the second core network does not support the establishment of the video bearer, the second core network sends an instruction for indicating the deactivation of the unknown bearer to the second device.

And S211, after receiving the instruction for indicating the deactivation of the unknown bearer, the second device waits for the establishment of the video bearer and sets an 8-second (S) timer.

And after the 8S timer finishes timing, abandoning to wait for the video bearer to be established.

S212, after receiving the instruction for indicating the establishment of the video bearer, the first device sends a parameter update (update) message to the second device through the first core network, the IMS network, and the second core network, so as to indicate that the establishment of the video bearer of the first device is completed.

S213, when the IMS network does not receive the response information of the first device within the first preset time, the IMS network retransmits the update message to the second device through the second core network.

And S214, when the IMS network does not receive the response information of the first device within the first preset time after S213, the IMS network retransmits the update message to the second device through the second core network.

And the IMS network retransmits the update message at intervals of a first preset time until a second preset time arrives or receives the response message of the first equipment.

And S215, when the IMS network does not receive the response information of the first device within a second preset time (for example, 6S), the IMS network sends an instruction for indicating to cancel the video call to the second device through the second core network.

And S216, when the IMS network does not receive the response information of the first device within a second preset time (for example, 6S), the IMS network sends a server internal error (500) message to the first device through the first core network.

Adaptively, the first device drops the video call after receiving the server internal error (500) message.

In the above call flow, the first device initiates a video call, and the second device is limited in bandwidth due to a network, so that when the maximum bandwidth AS value negotiated by the first device is larger, the second core network refuses to establish a bearer (video bearer) of quality of service class identifier (QCI) = 2. In the existing implementation, the second device starts a timer (generally 8 s) and waits for the establishment of a video bearer (QCI = 2), and when the timer expires, the second device abandons the waiting, and when waiting, the IMS network sends an update message, and the devices of different chips behave differently.

In a first possible implementation manner, the second device does not respond to the update message while waiting for the video bearer to be established. When the IMS network does not receive the response message, it retransmits the update (the interval is generally 2 s), and when the IMS network retransmits the update message for many times and does not receive the response, the IMS network cancels the call, and the call is suspended. When the first device video-calls the second device again, the call is cancelled, causing the user of the first device to think that the first device is in problem. And the second device does not respond and sense because the call is cancelled.

For example, fig. 3A-3C are schematic diagrams of interfaces corresponding to a first device when a video call is implemented. Taking VoLTE video calls in telephony applications as an example, as shown in figures 3A-3C,

the interface shown in fig. 3A is a contact 1 interface in a telephony application. The contact 1 interface can include: number 1, call log, and function control. The functionality controls may include one or more of: a voice call control, a video call control 301, a text message control, an edit contact control, or other type of functionality control. The number, arrangement mode and effect of the controls are not limited in the embodiment of the application.

When the first device receives the triggering operation of the video call control 301 at the interface shown in fig. 3A, the first device may enter the video call waiting interface shown in fig. 3B. As shown in fig. 3B, the video call waiting interface may include an identifier 302 for indicating waiting for answering, an identifier 304 for indicating call cancellation, and an identifier 303 for indicating switching to a voice call.

When the first device does not receive the message indicating that the second device supports voice and video, the first device may enter the contact 1 interface shown in fig. 3C from the video call waiting interface shown in fig. 3B without receiving the trigger operation of the identifier 304. The contact 1 interface may include: number 1, call log, and function control. The functionality controls may include one or more of: a voice call control, a video call control 305, a text message control, an edit contact control, or other type of functionality control. Wherein, the call record includes: an identification of not being turned on.

When the first device receives the triggering operation of the video call control 305 in the contact 1 interface shown in fig. 3C, the call is cancelled after the first device enters the video call waiting interface shown in fig. 3B.

In a second possible implementation manner, the second device responds to the update message while waiting for the video bearer to be established, and replies with a message indicating that the second device supports voice and video. When the timer is overtime and the update message is received, the second equipment replies a message for indicating the support of voice, and the voice call is successfully established. When the user of the first device hangs up the call and restarts the call in a video mode, a voice call is established between the first device and the second device, so that the user of the first device thinks that the first device has a problem. And the second device cannot select video listening due to call degradation.

For example, fig. 4A to 4D are schematic diagrams of interfaces corresponding to the first device when a video call in the second mode is possibly implemented. Taking VoLTE video calls in telephony applications as an example, as shown in figures 4A-4D,

the interface shown in fig. 4A is a contact 1 interface in a telephony application. The contact 1 interface can include: number 1, call log, and function control. The functionality controls may include one or more of: a voice call control, a video call control 401, a text message control, an edit contact control, or other type of functionality control. The number, arrangement mode and effect of the controls are not limited in the embodiment of the application.

When the first device receives the triggering operation of the video call control 401 at the interface shown in fig. 4A, the first device may enter the video call waiting interface shown in fig. 4B. As shown in fig. 4B, the video call waiting interface may include an identifier 402 of waiting for answering, an identifier 404 of call cancellation, and an identifier 403 of switching to a voice call.

When the first device receives the message indicating that the second device supports voice, the first device may enter the voice call interface shown in fig. 4C from the video call waiting interface shown in fig. 4B when the first device does not receive the trigger operation of the identifier 403 for switching to the voice call. The voice call interface may include: the duration of the call and an identification 405 of the call hanging up.

When the first device receives a trigger operation of the identifier 405 of hanging up from the voice call interface shown in fig. 4C, the first device enters a contact 1 interface shown in fig. 4D, where the contact 1 interface may include: number 1, call log, and function control. The functionality controls may include one or more of: a voice call control, a video call control 406, a text message control, an edit contact control, or other type of functionality control. Wherein, the call record includes: the call time of the call corresponding to the interface shown in fig. 4C and the call duration of the call corresponding to the interface shown in fig. 4C.

When the first device receives the trigger operation of the video call control 406 on the contact 1 interface shown in fig. 4D, the first device enters the voice call interface shown in fig. 4C after entering the video call waiting interface shown in fig. 4B.

In the two manners, when the second core network cannot establish the video bearer, the first device cannot determine the reason for the failure or degradation of the video call, so that the user thinks that the first device has a problem when the video call cannot be established, and the user experience is poor.

Based on this, an embodiment of the present application provides a call setup method, where after the second device recognizes that the second core network cannot support the video bearer, the video is degraded to voice. Therefore, the situation that the call is cancelled due to the fact that the response message of the second device is not received can be reduced, the situation of call failure is reduced, and the call rate is improved. In addition, the first device can learn and record the parameters of the second device and abnormal call conditions during call establishment. When the second device is called again within a certain time, the calling and parameter negotiation can be carried out by using the previously negotiated parameters, and the call rate is further improved.

For convenience of understanding, the following description explains terms related to embodiments of the present application.

1. IMS: a core network subsystem. The IMS serves as a control system for multimedia calls/sessions, and a key protocol at the core of the IMS includes a Session Initiation Protocol (SIP) protocol. IMS may consist of the following entities: a Call Session Control Function (CSCF), a Home Subscriber Server (HSS), a Subscription Location Function (SLF), an Application Server (AS), a Media Gateway Control Function (MGCF), an IP multimedia subsystem-media gateway function (IMS _ gateway function), a Multimedia Resource Function Controller (MRFC), a Media Resource Function Processor (MRFP), a domain gateway control function (BGCF), a gateway control function (gateway cf), a gateway control function (gw), a gateway switching function (PDF), and the like.

2. A core network: a network subsystem. The core network may provide user connectivity, management of users, and bearer completion for services as a bearer network provides an interface to external networks. The establishment of the user connection includes functions such as Mobility Management (MM), Call Management (CM), switching/routing, voice announcement (connection to the intelligent network peripheral devices is completed in conjunction with intelligent network services). The user management comprises user description, Qos (description of user service Qos is added), user communication record (Accounting), Virtual Home Environment (VHE) provided by dialog with intelligent network platform, and security (providing corresponding security measures by the authentication center includes security management for mobile services and security processing for external network access). The bearer connection (access to) includes a Public Switched Telephone Network (PSTN) to the outside, an external circuit data network and a packet data network, the internet (internet) and an intranet (internets), and a SMS server of the mobile itself, and so on. Basic services that can be provided by a core network include mobile office, e-commerce, communications, entertainment services, travel and location based services, telesensing services (telemetering) -simple messaging services (supervisory control), and so on.

3. Bandwidth (bandwidth): refers to the bandwidth occupied by the signal. The bandwidth can be divided into conference bandwidth (CT) and application-specific maximum bandwidth AS, where CT is the bandwidth for setting the whole conference, AS is the bandwidth for setting a single session, and the units of CT and AS are kilobits per second (kbit/s). Generally expressed as: b = < type > < bandwidth > (b = < modifier > < bandwidth-value >).

Fig. 5 is a schematic flowchart of call setup according to an embodiment of the present application. As shown in fig. 5, the call setup procedure includes:

s501, when the first device receives an operation for indicating the video to call the second device, the first device sends a first instruction for indicating the video to start calling to a first core network.

In the embodiment of the present application, the relevant descriptions may be given for possible structures and functions of the first device, the second device, the first core network, the IMS network, and the second core network, which are not described herein again.

In a possible implementation manner, the first instruction carries an AS value corresponding to the first device and identification information corresponding to the second device. The identification information corresponding to the second device may be a number corresponding to the second device, or may be an IP address corresponding to the second device.

Illustratively, the AS value corresponding to the first device may be 2000 kbit/s.

S502, when receiving the instruction for indicating the video call, the first core network sends an invite message to the second device through the IMS network and the second core network to request to establish a video call.

The invite message carries information for indicating a video call and an AS value corresponding to the first device.

Illustratively, the invite message includes: m = voice (audio) and m = video (video), and the port number is not 0. Specifically, the invite message includes: m = audio 46010 RTP/AVP 98968105100111106018; m = video 33608 RTP/AVP 114115.

S503, after receiving the invite message, the second device feeds back a temporary response (100 Trying) message to the first device through the second core network, the IMS network, and the first core network, so as to notify the first device that the IMS network receives the call request.

S504, after receiving the invite message, the IMS sends a bearer establishment request to the first core network, and adaptively establishes a bearer between the IMS network and the first core network.

S505, the first core network sends an instruction for instructing establishment of a voice bearer to the first device.

For example, the instruction for indicating the establishment of the voice bearer may be dedicated bearer activation information (activated dedicated EPS bearer context request Msg).

S506, the first core network sends an instruction for indicating the establishment of the video bearer to the first device.

And S507, the second equipment sends a session progress (183 session progress) message to the first equipment through the second core network, the IMS network and the first core network so as to indicate the progress of the video call.

In this embodiment of the present application, the 183 session progress message carries an AS value corresponding to the second device.

Illustratively, the AS value corresponding to the second device may be 1060 kbit/s.

In a possible implementation manner, the 183 session progress message further transmits a preset prompting ring tone or a preset prompting word, so that the user of the first device waits, and user experience is enhanced.

And S508, after the first device receives the 183 session progress, saving the AS value corresponding to the second device.

S509, after receiving the 183 session progress message transmitted by the second device, the IMS network sends a bearer establishment request to the second core network, and adaptively establishes a bearer between the IMS network and the second core network.

And S510, the second core network sends an instruction for indicating voice bearer establishment to the second equipment.

Adaptively, the second device receives an instruction indicating a voice bearer establishment.

For example, the instruction for indicating the voice bearer establishment may be an activate dedicated bearer message, where the corresponding bearer identity (eps _ bearer _ id, EBI) in the activate dedicated bearer message corresponds to the voice bearer identity.

For example, the instruction for indicating voice bearer establishment may be:

LTE NAS ESM Plain OTA Incoming Message -- Activate dedicated EPS bearer context request Msg

eps_bearer_id_or_skip_id = 7 (0x7)

msg_type = 197 (0xc5) (Activate dedicated EPS bearer context request)

lte_esm_msg

act_dedicated_eps_bearer_context_req

eps_qos

qci = 1 (0x1) (QC1)

wherein, the activated differentiated EPS bearer context request Msg is used for representing the activation of the special bearer; qci =1 (0x1) (QC1) is used to represent voice traffic.

And S511, when the second core network does not support the establishment of the video bearer, the second core network sends an instruction for indicating the deactivation of the unknown bearer to the second device.

For example, the instruction for indicating the unknown bearer deactivation may be bearer deactivation information (deactivation EPS bearer context request Msg). Wherein, the corresponding bearer identifier (eps _ bearer _ id, EBI) in the bearer deactivation information is not established.

For example, the instruction for indicating the unknown bearer deactivation may be:

LTE NAS ESM Plain OTA Incoming Message -- Deactivate EPS bearer context request Msg

eps_bearer_id_or_skip_id = 8 (0x8)

msg_type = 205 (0xcd) (Deactivate EPS bearer context request)

lte_esm_msg

deact_eps_bearer_req

esm_cause

esm_cause = 36 (0x24) (Regular deactivation)

here, msg _ type = 205 (0xcd) (deactivating EPS bearer context request) is used to indicate a network error. esm _ cause = 36 (0x24) (Regular deactivation) is used to indicate the cause of the error.

And S512, after receiving the instruction for indicating the deactivation of the unknown bearer, the second device determines that the second core network cannot establish the video bearer.

In a possible implementation manner, after receiving the instruction for instructing the unknown bearer to deactivate, the second device sets a first timer, and when the first timer is ended and the instruction for instructing the video bearer establishment is not received, determines that the second core network cannot establish the video bearer.

In this embodiment, the duration of the first timer may be 1S or 2S. Therefore, the judgment error that the second core network cannot establish the video bearer can be reduced.

In a possible implementation manner, the second device determines that the second core network cannot establish the video bearer according to the network fault table and the location of the second device. The network fault table includes but is not limited to: information about cells that do not support video bearers.

For example, the second device may determine the cell corresponding to the second device through the configuration information transmitted by the second core network. And when the second device receives an instruction for indicating the deactivation of the unknown bearer and confirms that the cell corresponding to the second device is consistent with the cell corresponding to the network fault table, determining that the second core network cannot establish the video bearer.

For example, it may be determined whether the cell corresponding to the second device is consistent with the cell corresponding to the network fault table by whether the cell information corresponding to the second device is consistent with the cell information corresponding to the network fault table. It is to be understood that the network failure table is stored on a cloud server, and the second device may be obtained through the second core network. The second device can actively acquire the network fault table from the cloud server; or the cloud server actively pushes the network fault table to the second device. The cloud server may be a cloud server of a second device manufacturer, or may also be a cloud server of a third party, which is not limited in this embodiment of the present application.

In the embodiment of the present application, the network fault table may be obtained in advance, or may be obtained in the call process.

In a possible implementation manner, the second device determines that the second core network cannot establish the video bearer according to the location where the second device is located and the historical failure condition. Illustratively, when the cell information where the second device is located is consistent with the cell information recorded in the historical failure condition, it is determined that the second core network cannot establish the video bearer.

In this embodiment, the cell information may be an identification code corresponding to the cell. The identification code corresponding to the cell may be composed of an operator identity (PLMN), a location area (TAC), and a cell id (cell id) below the TAC.

In a possible implementation manner, when the second device determines that the second core network cannot establish the video bearer, the second device reports the position of the second device and other related information to the cloud server, so that the cloud server can form or update the network fault table conveniently.

S513, after receiving the instruction for indicating the establishment of the video bearer, the first device sends an update message to the second device through the first core network, the IMS network, and the second core network, so as to indicate that the establishment of the video bearer of the first device is completed.

S514, when the second device receives the update message and confirms that the second core network cannot establish the video bearer, the second device replies a parameter update response (update ok) message to the first device through the second core network, the IMS network and the first core network to indicate that the second device supports the voice call.

And S515, after the first device replies the update ok message, the first device and the second device perform voice communication.

In a possible implementation manner, the second device stores the location information of the second device after the second device is degraded to voice or the call fails. Illustratively, the second device records that the corresponding cell information is stored in a historical failure condition.

In a possible implementation manner, the first device may notify the user of the first device through display on an interface or in a voice manner, and the second device does not support a video call.

S516, when the first device receives the update ok message transmitted by the IMS network, the first device stores the call parameters when the call with the second device fails. Call parameters include, but are not limited to: a call fault type, a number corresponding to the second device, a maximum bandwidth AS, a call start time, a preset duration or a failure time (failure time), and the like. The type of the call failure may be degraded to a voice call or a call failure.

TABLE 1 Call Fault watch

Number of

Type of originating call

Type of failure

Destination number

AS value

Protocol level ID

Time to failure

1

Video

Failed to originate call

11111

900

1F

T1

1

Video

Failed to originate call

22222

315

1F

T2

2

Video

Degradation to speech

33333

1060

1E

T3

Exemplary, as shown in table 1: the call parameters include: fault number, originating type, fault type, destination number, AS value, protocol level ID, and expiration time.

In the embodiment of the present application, the preset time period may be 24 hours or 30 minutes. The embodiment of the present application does not limit this.

In table 1, if the number corresponding to the second device is 33333, when the first device starts to call the second device in the video, the video call is degraded to voice, and the negotiated AS value is 1060. When the first device originates a call to the second device earlier than time T3, the first device originates a call using 1060 AS the AS value.

And S517, when the first equipment calls the second equipment within the preset time length, the first equipment uses the stored call parameters corresponding to the second equipment to call.

In the embodiment of the application, the failure time is the sum of the call starting time and the preset time. It can also be understood that, when the first device initiates the call to the second device before the expiration time, the first device initiates the call by using the stored call parameters corresponding to the second device. Or when the difference value between the time for the first device to call the second device again and the stored call starting time is less than the preset time, the first device uses the stored call parameters corresponding to the second device to start calling.

In the call setup procedure shown in fig. 5, the second device may monitor bearer activation and deactivation requests of the second core network, and when the second device confirms that the second core network does not support video bearer setup, the first device and the second device establish a voice call. Therefore, the waiting time is shortened, the situation of call failure is reduced, and the call rate is improved. In addition, the first device can also learn and store the call parameters of the second device, and when the call is started within the preset time, the call is started according to the call parameters, so that the situation of call failure is further reduced, and the call rate is improved.

The interface display of the first device in the embodiment of the present application is described below with reference to fig. 6A to 6E.

Illustratively, as shown in FIGS. 6A-6E, the interface shown in FIG. 6A is a contact 1 interface in a telephony application. The contact 1 interface can include: number 1, call log, and function control. The functionality controls may include one or more of: a voice call control, a video call control 601, a text message control, an edit contact control, or other type of functionality control. The number, arrangement mode and effect of the controls are not limited in the embodiment of the application.

When the first device receives a triggering operation of the video call control 601 at the interface shown in fig. 6A, the first device may enter the video call waiting interface shown in fig. 6B. As shown in fig. 6B, the video call waiting interface may include an identifier 602 of waiting for answering, an identifier 604 of call cancellation, and an identifier 603 of switching to a voice call.

When the first device receives a message for indicating that the second device cannot establish the video bearer, the first device prompts a user of the first device in a voice mode. Or the first device enters the voice call waiting interface shown in fig. 6C from the video call waiting interface shown in fig. 6B. The voice call waiting interface can comprise: a reason identification 605 and an identification 606 of the cancellation of the call. The reason identifier 605 is used to indicate that the second device does not currently support video calls. In a possible implementation manner, the voice call waiting interface further includes an identifier of switching to video in a gray state to indicate that switching to video cannot be performed.

It is understood that the first device may also perform video origination in other manners, and enter the video call waiting interface shown in fig. 6B. For example, the control switched to the video is switched from the voice call waiting interface to the video call waiting interface. The embodiment of the present application does not limit the specific manner of the video call.

When the voice call is connected, the first device enters the voice call interface shown in fig. 6D from the voice call waiting interface shown in fig. 6C. The voice call interface includes: the duration of the call and an indication of the call hanging up 607. When the first device receives the trigger operation of the identifier 607 of the call drop, the first device enters a contact 1 interface shown in fig. 6E, where the contact 1 interface may include: number 1, call log, and function control. The functionality controls may include one or more of: a voice call control, a video call control 608, a text message control, an edit contact control, or other type of functionality control. Wherein, the call record includes: the call time of the call corresponding to the interface shown in fig. 6D and the call duration of the call corresponding to the interface shown in fig. 6D.

When the first device receives the trigger operation of the video call control 608 in the contact 1 interface shown in fig. 6E within the preset duration, the first device may enter the voice call waiting interface shown in fig. 6C, and then enter the voice call interface shown in fig. 6D when receiving an instruction for instructing to put through a call.

In a possible implementation manner, when the first device receives the triggering operation of the video call control 608 in the contact 1 interface shown in fig. 6E within the preset duration, the first device may prompt the user whether to insist on the video call. When receiving an operation of selecting a video call by a user, the first device enters a video call waiting interface shown in fig. 6B; when receiving an operation of selecting a voice call by the user or receiving no selection operation, the first device enters a voice call waiting interface shown in fig. 6C.

It may be understood that the foregoing display interface is only an example, and the display interface of the first device may further include more or less contents, which is not limited in this embodiment of the application.

Exemplarily, fig. 7 is a flowchart illustrating a call setup method according to an embodiment of the present application. As shown in fig. 7, the call setup procedure includes: when the first device video calls the second device, the first device sends a video call request to the second device. The second device sends a provisional response message to the core network device based on the video call request.

S701, when the second equipment receives a first message from the core network equipment, the second equipment establishes a voice bearer, and the first message is used for indicating to activate the voice bearer.

For example, the first message may be an activate dedicated bearer message, and the activate dedicated bearer message includes: identification of the voice bearer. The identity of the voice bearer may be QCI = 1.

S702, when the second device receives a second message from the core network device, the second device sends a third message to the first device; the second message is used for indicating that the video bearer cannot be established; the third message is used to indicate voice bearer establishment.

It can be appreciated that when the second device receives the second message from the core network device, the second device confirms that the video bearer cannot be established. Therefore, when the core network corresponding to the second device cannot establish the video bearer, the second device can confirm that the video bearer cannot be established, and send a message supporting voice to the first device, so that the second device and the first device are degraded into voice call.

On the basis of the above embodiments, the second device may further identify that the video bearer cannot be established in various ways.

In a possible implementation manner, after receiving the second message, a timer is set, and if the timer is overtime, it is determined that the video bearer cannot be established when the fourth message is received. In the embodiment of the present application, the duration of the timer may be 1S or 2S. And are not limited herein.

In a possible implementation manner, the second device determines that the video bearer cannot be established according to the location where the second device is located and the historical failure condition. And when the cell information of the second device is consistent with the cell information recorded in the historical fault condition, determining that the core network device cannot establish the video bearer. Therefore, the accuracy of the second device in judging that the core network device cannot establish the video bearer can be increased, and the judgment error is reduced.

In a possible implementation manner, the second device further determines that the video bearer cannot be established according to the network fault table and the location of the second device.

In the embodiment of the present application, the network fault table includes, but is not limited to: information about cells that do not support video bearers. It can be understood that, when the location where the second device is located is within the range of the cell that does not support the video bearer and is stored in the network fault table, and the second device receives the first message and the second message, the second device confirms that the video bearer cannot be established. Or, when the cell where the second device is located is consistent with the cell which does not support the video bearer and is stored in the network fault table, and the second device receives the first message and the second message, the second device confirms that the video bearer cannot be established. Therefore, the accuracy of the second device in judging that the core network device cannot establish the video bearer can be increased, and the judgment error is reduced.

For example, the second device may determine the cell corresponding to the second device through the configuration information transmitted by the core network device. When the second device receives an instruction for indicating the deactivation of the unknown bearer and confirms the corresponding cell in the network fault table, it is determined that the core network device cannot establish the video bearer.

Optionally, the second device receives a network fault table from the cloud server, where the network fault table includes: cell information which does not support video bearing; when the second device receives the second message from the core network device, the second device sends a third message to the first device, including: and when the second equipment receives the second message and the cell information where the second equipment is located is consistent with the cell information which does not support the video bearer, the second equipment sends a third message to the first equipment. Therefore, the accuracy of the second device in judging that the core network device cannot establish the video bearer can be increased, and the judgment error is reduced.

S703, the first device receives a third message from the second device, where the third message is used to indicate establishment of a voice bearer.

S704, after receiving the third message, the first device downgrades to a voice call.

Therefore, the conversation is degraded into voice, the situation that the conversation is cancelled due to waiting for the establishment of the video bearer can be reduced, and the conversation rate is improved.

Optionally, after receiving the third message, the first device displays a first interface, where the first interface includes: an indication that the second device does not support video telephony. Therefore, the user of the first device is prompted to switch to the voice call, and user experience is improved.

S705, the first device stores the call parameters during the call failure, where the call parameters include: an identification of the second device and an AS value.

In the embodiment of the present application, the call parameters include, but are not limited to: the calling type, the number corresponding to the second device, the type of the call failure, the calling time of the first device, the maximum bandwidth AS, the failure time or the preset time length, etc. The call parameters may refer to the above description, and are not described herein again.

Optionally, the first device receives a fifth message from the second device, where the fifth message is used to indicate a maximum bandwidth AS value corresponding to the second device.

And S706, when the first equipment calls the second equipment within the preset time length, calling according to the call parameters.

In a possible implementation manner, when the first device receives a first operation within a preset time period, the first device sends a call request by using the call parameter, and the first operation is used for instructing to initiate a call to the second device.

And the second equipment confirms that the video bearer can not be established or the voice bearer can not be established according to the first message.

It will be appreciated that the process of voice origination is similar to that of video origination. The following explains a voice call process.

When the first device starts to call the second device by voice, the first device sends a voice call request to the second device. The second device sends a temporary response message to the core network device based on the voice call request. When the second device receives a message from the core network device for indicating that the voice bearer cannot be established, the second device sends a message for indicating that the voice bearer is not supported to the first device. The first device cancels the call. In addition, the interface of the first device also displays the reason of the call cancellation to inform the user that the other party does not support the voice call. Therefore, when the core network corresponding to the second device cannot establish the voice bearer, the second device can confirm that the voice bearer cannot be established, and then cancel the call between the second device and the first device. Therefore, the waiting time for establishing the voice bearing can be reduced, and the user experience is improved.

It can be understood that, in the voice call initiating process, the second device may further determine, through a timer, a history fault condition (including cell information corresponding to the condition that the voice bearer cannot be established), and a network fault table (cell information that does not support the voice bearer), that the voice bearer cannot be established.

Having described the call establishment method according to the embodiment of the present application, a related apparatus for performing the call establishment method according to the embodiment of the present application is described below. Those skilled in the art will appreciate that the methods and apparatuses may be combined and referred to one another, and that the electronic device provided in the embodiments of the present application may perform the steps of the call setup method described above.

Fig. 8 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present application. Referring to fig. 8, the apparatus includes: memory 1001, processor 1002, and interface circuit 1003. The device may also include a display 1004, wherein the memory 1001, processor 1002, interface circuit 1003, and display 1004 may be in communication; illustratively, the memory 1001, the processor 1002, the interface circuit 1003 and the display screen 1004 may communicate via a communication bus, and the memory 1001 is used for storing computer-executable instructions, which are controlled by the processor 1002 to execute and executed by the interface circuit 1003 to execute communication, thereby implementing the call establishment method provided by the following embodiments of the present application.

In a possible implementation manner, the computer execution instruction in the embodiment of the present application may also be referred to as an application program code, which is not specifically limited in the embodiment of the present application.

Optionally, the interface circuit 1003 may further include a transmitter and/or a receiver. Optionally, the processor 1002 may include one or more CPUs, and may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor, or in a combination of the hardware and software modules in the processor.

The embodiment of the application also provides a computer readable storage medium. The methods described in the above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media may include computer storage media and communication media, and may include any medium that can communicate a computer program from one place to another. A storage medium may be any target medium that can be accessed by a computer.

In one possible implementation, the computer-readable medium may include RAM, ROM, a compact disk read-only memory (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and Disc, as used herein, includes Disc, laser Disc, optical Disc, Digital Versatile Disc (DVD), floppy disk and blu-ray Disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processing unit of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above embodiments are only for illustrating the embodiments of the present invention and are not to be construed as limiting the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made on the basis of the embodiments of the present invention shall be included in the scope of the present invention.

Claims

1. A method for call setup, the method comprising:

a second device receiving a video call request originating from a first device, the video call request being transmitted by the first device to the second device via a first core network device, an IP multimedia subsystem network device, and a second core network device;

the second device sends a temporary response message to the second core network device based on the video call request;

when the second device receives a first message from the second core network device, the second device establishes a voice bearer, and the first message is used for indicating to activate the voice bearer;

when the second device receives a second message from the second core network device and meets a first preset condition, the second device sends a third message to the first device; the second message is used for indicating that a video bearer cannot be established; the third message is used for indicating voice bearing establishment;

the first preset condition includes that the second device does not receive a fourth message before a timer is overtime, the timer is set by the second device when the second device receives the second message, and the fourth message is used for indicating that a video bearer is activated;

or the first preset condition includes that the cell information where the second device is located is consistent with the corresponding cell information when the second device cannot establish the video bearer in the case that the historical failure condition is stored;

or the first preset condition includes that the cell information where the second device is located is consistent with the cell information, which does not support video bearer, in the network fault table received by the second device and originated from the cloud server.

2. The method of claim 1, wherein the second message is bearer deactivation information, and wherein a bearer identifier in the bearer deactivation information is not established.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

the second device sends a fifth message to the first device, wherein the fifth message is used for indicating a maximum bandwidth AS value corresponding to the second device;

and the second equipment receives a call request sent by the first equipment by adopting the AS value when the first equipment meets a second preset condition, wherein the second preset condition is that the first equipment receives a first operation within a preset time length, and the first operation is used for indicating to start to call the second equipment.

4. A method for call setup, the method comprising:

the method comprises the steps that a first device sends a video call request to a second device, wherein the video call request is transmitted to the second device by the first device through a first core network device, an IP multimedia subsystem network device and a second core network device;

the first device receives a third message from the second device, wherein the third message is used for indicating voice bearer establishment;

the third message is sent by the second device after meeting a first preset condition and a second preset condition, where the first preset condition includes: the second device receives a first message from the second core network device and a second message from the second core network device, wherein the first message is used for indicating to activate a voice bearer, and the second message is used for indicating that a video bearer cannot be established;

the second preset condition includes that the second device does not receive a fourth message before a timer is overtime, and the timer is set when the second device receives the second message;

or the second preset condition includes that the cell information where the second device is located is consistent with the first cell information; the first cell information is corresponding cell information when the video bearer cannot be established in the historical fault conditions stored in the second device;

or the second preset condition includes that the cell information where the second device is located is consistent with the second cell information; the second cell information is cell information which does not support video bearing and corresponds to a network fault table, and the network fault table is originated from a cloud server.

5. The method of claim 4, wherein the second message is bearer deactivation information, and wherein a bearer identifier in the bearer deactivation information is not established.

6. The method according to claim 4 or 5, characterized in that the method further comprises:

after receiving the third message, the first device displays a first interface, where the first interface includes: an indication that the second device does not support video telephony.

7. The method according to claim 4 or 5, characterized in that the method further comprises:

the first device receives a fifth message from the second device, wherein the fifth message is used for indicating a maximum bandwidth AS value corresponding to the second device;

the first device stores call parameters when a call fault occurs, wherein the call parameters include: an identity of the second device and the AS value;

and when the first equipment receives a first operation within a preset time length, the first equipment sends a calling request by adopting the conversation parameters, and the first operation is used for indicating to start calling the second equipment.

8. The method of claim 7, wherein the call parameters further comprise: the moment of origination of the call;

and when the difference value between the moment when the first equipment receives the first operation and the calling moment is less than the preset duration, the first equipment adopts the conversation parameters to send a calling request.

9. An electronic device, comprising: a processor and a memory;

the memory stores computer-executable instructions;

the processor executes the computer-executable instructions stored by the memory, causing the processor to perform the method of any of claims 1-3 or the method of any of claims 4-8.

10. A computer-readable storage medium, in which a computer program or instructions are stored which, when executed, implement the method of any one of claims 1-3 or the method of any one of claims 4-8.