WO2020233122A1 - 通话控制方法、装置、设备及存储介质 - Google Patents

通话控制方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2020233122A1
WO2020233122A1 PCT/CN2019/128929 CN2019128929W WO2020233122A1 WO 2020233122 A1 WO2020233122 A1 WO 2020233122A1 CN 2019128929 W CN2019128929 W CN 2019128929W WO 2020233122 A1 WO2020233122 A1 WO 2020233122A1
Authority
WO
WIPO (PCT)
Prior art keywords
call
terminal
waiting
network side
information
Prior art date
Application number
PCT/CN2019/128929
Other languages
English (en)
French (fr)
Inventor
洪洋
田浩雨
Original Assignee
珠海格力电器股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 珠海格力电器股份有限公司 filed Critical 珠海格力电器股份有限公司
Publication of WO2020233122A1 publication Critical patent/WO2020233122A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/305—Handover due to radio link failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/50—Connection management for emergency connections

Definitions

  • This application relates to the field of communication technology, and in particular to a call control method, device, equipment, and storage medium.
  • Calling is a basic function of terminals such as mobile phones and smart watches. It is widely used in daily life and is also a common communication method used by people.
  • the call may fail due to poor network signal or network congestion. Once the call fails, the network side will hang up the call, but for the user, he does not know the call.
  • the specific reasons for the failure such as alarms or other emergencies, this will aggravate the user’s panic and anxiety, and cause greater inconvenience to the user, which may cause irreparable economic losses to the user, or even endanger The safety of users' lives.
  • the embodiments of the present application provide a call control method, device, equipment, and storage medium, which can prompt the user the reason for the call failure when the call fails, and avoid the user's panic and anxiety due to the call failure, and cause unnecessary personal and property losses. Improve user experience.
  • a call control method includes:
  • the call failure feedback information is also used to indicate whether to continue to wait to establish a call connection, and the method further includes:
  • the network side when the network side can process the call request, establish a call connection between the first terminal and the second terminal corresponding to the target number.
  • the indicating waiting information is further used to indicate a first waiting time set by the user, and the first waiting time is the longest time that the first terminal can wait to establish a call connection with the second terminal. duration;
  • the first terminal and the first terminal are established according to the call request. The call connection between the two terminals.
  • the indicating waiting information is further used to indicate a first waiting time set by the user, and the first waiting time is the longest time that the first terminal can wait to establish a call connection with the second terminal. Duration; then after holding the call request, the method further includes:
  • the method before determining whether the network side is still in a congested state, the method further includes:
  • the method further includes:
  • a waiting insufficient prompt information is sent to the first terminal, where the waiting insufficient prompt information is used to indicate that the network side is in the first waiting period.
  • the call request cannot be processed within the time period.
  • the method further includes:
  • the call failure feedback information is also used to indicate a third waiting period, and the third waiting period is the shortest period of time for the network side to end the network congestion state.
  • the method also includes:
  • the fourth waiting period When the fourth waiting period is reached from the time when the call failure feedback information is sent, the call connection between the first terminal and the second terminal is established; wherein, the fourth waiting period is from the sending of the call The length of time between the start of the failure feedback information and the actual processing of the call request.
  • the method further includes:
  • a call control method includes:
  • the call failure feedback information is further used to indicate whether to continue to wait to establish a call connection. After receiving the call failure feedback information, the method further includes:
  • determining indicating waiting information wherein the indicating waiting information is used to indicate that the first terminal can wait to establish a call connection
  • the indicating waiting information is further used to indicate a first waiting time set by the user, where the first waiting time is a second terminal corresponding to the target number that the first terminal can wait for The longest time to establish a call connection.
  • the method after receiving the call failure feedback information sent by the network side, the method further includes:
  • the termination request information is used to request termination of the call request
  • a call control device in a third aspect, includes:
  • the first receiving unit is configured to receive a call request to the target number initiated by the first terminal
  • the first determining unit is configured to determine the reason why the call request cannot be processed currently if the call request cannot be processed currently;
  • the feedback unit is configured to send call failure feedback information to the first terminal when the reason why the call request cannot currently be processed is network side congestion, where the call failure feedback information is used to indicate that the network side is currently Network congestion status.
  • the call failure feedback information is further used to indicate whether to continue to wait to establish a call connection
  • the apparatus further includes:
  • a second receiving unit configured to receive waiting information indicating that the first terminal sends based on the call failure feedback information, where the waiting indicating information is used to indicate that the first terminal can wait for the establishment of a call connection;
  • the call establishment unit is configured to establish a call connection between the first terminal and the second terminal corresponding to the target number when the network side can process the call request according to the waiting indication information.
  • the indicating waiting information is further used to indicate a first waiting time set by the user, and the first waiting time is the longest time that the first terminal can wait to establish a call connection with the second terminal. Duration; the call establishment unit is used to:
  • the first terminal and the second terminal are established according to the call request Call connection between.
  • the indicating waiting information is further used to indicate a first waiting time set by the user, and the first waiting time is the longest time that the first terminal can wait to establish a call connection with the second terminal. Duration; the device also includes a termination request unit for:
  • the device further includes a second determining unit, which is further configured to:
  • the termination request unit determines whether the network side is still in a congested state, when receiving the indicating waiting information, determine the second waiting time required for the network side to end the network congested state;
  • the second determining unit is further configured to:
  • a waiting insufficient prompt information is sent to the first terminal, where the waiting insufficient prompt information is used to indicate that the network side is in the first waiting period.
  • the call request cannot be processed within the time period.
  • the device further includes a third determining unit, configured to:
  • the second determining unit After the second determining unit sends the waiting insufficient prompt information to the first terminal, determining whether the target number is a preset emergency number;
  • the call failure feedback information is further used to indicate a third waiting period, the third waiting period being the shortest period of time for the network side to end the congestion state, and the call establishing unit is further used to:
  • the fourth waiting duration is the duration from the sending of the call failure feedback information to the actual processing of the call request.
  • the termination request unit is further used to:
  • the second determining unit After the second determining unit sends the call failure feedback information to the first terminal, receiving the termination request information sent by the first terminal for requesting termination of the call request;
  • Terminating the call request according to the terminating call request information.
  • a call control device in a fourth aspect, includes:
  • the sending unit is used to send a call request for establishing a call with the target number to the network side;
  • the receiving unit is configured to receive call failure feedback information sent by the network side, where the call failure feedback information is used to indicate that the network side is currently in a network congestion state.
  • the call failure feedback information is further used to indicate whether to continue to wait to establish a call connection
  • the sending unit is further used to:
  • determining indicating waiting information wherein the indicating waiting information is used to indicate that the first terminal can wait to establish a call connection
  • the indicating waiting information is further used to indicate a first waiting time set by the user, where the first waiting time is a second terminal corresponding to the target number that the first terminal can wait for The longest time to establish a call connection.
  • the sending unit is further used to:
  • the termination request information is used to request termination of the call request
  • a call control device in a fifth aspect, includes:
  • Memory used to store program instructions
  • the processor is configured to call the program instructions stored in the memory, and execute the steps included in any one of the methods in the first aspect according to the obtained program instructions.
  • a call control device in a sixth aspect, includes:
  • Memory used to store program instructions
  • the processor is configured to call the program instructions stored in the memory, and execute the steps included in any one of the methods in the second aspect according to the obtained program instructions.
  • a storage medium stores computer-executable instructions, and the computer-executable instructions are used to make a computer execute the steps included in any method in the first aspect.
  • a storage medium stores computer-executable instructions, and the computer-executable instructions are used to make a computer execute the steps included in any method in the second aspect.
  • the network side after the network side receives the call request initiated by the first terminal to the target number, it can first determine whether the call request can be processed currently, and when the call request cannot be processed, it can determine that the call request cannot be processed.
  • Reason If it is determined that the current call request cannot be processed due to network congestion, the call failure feedback information can be sent to the first terminal, so as to inform the user using the first terminal that it is currently unable to due to network congestion through the call failure feedback information.
  • the call is established immediately, that is, after the call request initiated by the first terminal fails, the network side can promptly inform the user that the call failed due to network congestion, thereby effectively prompting the user. Therefore, for example, when dialing 110, etc.
  • the user can know that the specific reason for the call failure is due to network congestion, rather than other unknown reasons. This can reassure users in a panic or anxious state, and prevent users from blindly not knowing the specific reason for the call failure To make excessive behaviors in order to avoid some property loss or even life danger, and improve the user experience.
  • FIG. 1 is a schematic diagram of an application scenario provided by an embodiment of the application
  • Figure 2 is a schematic diagram of another application scenario provided by an embodiment of the application.
  • FIG. 3 is a flowchart of a call control method provided by an embodiment of the application.
  • Figure 4a is a structural block diagram of a call control device provided by an embodiment of the application.
  • FIG. 4b is another structural block diagram of the call control device provided by an embodiment of the application.
  • FIG. 5 is another structural block diagram of a call control device provided by an embodiment of the application.
  • FIG. 6 is a schematic structural diagram of a call control device provided by an embodiment of the application.
  • FIG. 7 is a schematic diagram of another structure of a call control device provided by an embodiment of the application.
  • multiple means at least two, for example, two, three or more, and the embodiments of the present application do not limit it.
  • the call may fail. For example, after receiving the call request for the target number initiated by terminal A, the call control center detects that the current network is congested, The amount of pending call requests is overloaded, which causes the current call request initiated by terminal A to be unable to process, so that it is impossible to establish a call connection between terminal A and the terminal corresponding to the target number (for example, terminal B), and directly hang up terminal A. Call, but the user of terminal A does not know why the call cannot be successfully established, so when the user encounters an emergency, it is easy to panic and anxious due to the failure of the call, which will cause inconvenience to the user and may even affect the user’s property Even life is safe.
  • the inventor of the applicant provides a technical solution for call control.
  • the network side determines whether it can currently handle the call according to its own network conditions.
  • Call request when the call request cannot be processed, the network side does not immediately terminate the call request, but determines the reason why the call request cannot be processed, and when it determines that the reason for the call request cannot be processed is network congestion, the network side A terminal sends call failure feedback information to prompt the user of the first terminal of the reason for the failure of the call request, so that users who are in a panic or anxious state can be appeased, and the user can avoid blindly excessive behavior because the user does not know the call failure, and improve user experience.
  • the network side can continue to hold the call request instead of directly hanging up the call as in the related art, so that the network is no longer congested and can handle the call.
  • the call between the first terminal and the terminal corresponding to the target number for example, the second terminal
  • the target number for example, the second terminal
  • the call between the first terminal and the terminal corresponding to the target number can be established in time Connect, to respond evenly to the call request of the first terminal, and to establish a call between the first terminal and the second terminal as soon as possible, so as to maximize the efficiency of the call and increase the probability of successful call.
  • the application scenario includes a terminal 10, a terminal 11, and a network side device 12.
  • the terminal 10 and the terminal 11 are mobile phones, smart watches, and fixed phones.
  • the network side device 12 is composed of one or more network devices required to establish a call connection between the terminal 10 and the terminal 11
  • the network side device 12 is also called, for example, the network side or the call control center.
  • the network side device 12 After the network side device 12 receives the call request for the target number initiated by the terminal 10, the network side device 12 determines whether the call request can be processed currently, and if it cannot process the call request, it determines the reason why the call request cannot be processed. When it is determined that the reason why the call request cannot be processed is network congestion, the network side device 12 sends to the terminal 10 call failure feedback information for notifying the user of the network side congestion. In some embodiments, the call request is maintained at the same time, and then the call connection between the terminal 10 and the terminal 11 is established in time when the network is not congested, so as to increase the probability of the terminal 10 successfully making a call.
  • the application scenario includes a calling terminal 20, at least one called terminal 22, and a network-side device 21.
  • the calling terminal 20 and the called terminal The called terminal 22 is a mobile phone, or a terminal with a call function such as a smart watch or a fixed phone.
  • At least one called terminal 22 is managed by one or more servers (also called a control center), and at least one called terminal 22 corresponds to one Target number.
  • some customer service hotlines have only one number but correspond to multiple fixed telephones, or some alarm calls (such as 110 or 119) also correspond to multiple telephone terminals.
  • the control center Allocate the call request to a fixed phone that is currently idle, thereby establishing a call connection.
  • the network side device 21 is a system composed of one or more devices required to establish a call connection between the calling terminal 20 and the called terminal 22.
  • the network side device 21 includes Base stations and servers, or other network equipment. After the base station receives the call request initiated by the calling terminal 20, it will send the call request to the server for processing, and then the server controls the called terminal 22 (or other specific The called terminal 22) establishes a call connection with the calling terminal 20.
  • the network side device 21 is also called the network side or the call control center.
  • the implementation of the network side device 21 in Figure 2 is similar to the implementation of the network side device 12 in Figure 1.
  • the network-side congestion is caused by the large number of call requests to be processed at the base station, or due to the large number of call requests to be processed at the server that manages the called terminal It may be caused by the temporary power failure of the server or other reasons.
  • FIG. 3 is a flowchart of a call control method provided by an embodiment of this application.
  • the first terminal is the calling terminal and the second terminal is the called terminal as an example.
  • the flow of the call control method in FIG. 3 is described as follows.
  • Step 301 The first terminal sends a call request for requesting to establish a call with the target number to the network side, and the network side can receive the call request.
  • the first terminal is the terminal 10 shown in FIG. 1 or the terminal 20 shown in FIG. 2.
  • At least one user identification card is installed in the first terminal, and the user identification card corresponds to one
  • the target number is the number of the terminal 11 as shown in Figure 1, or the number corresponding to multiple called terminals as shown in Figure 2; therefore, the call request carries the number The number of a terminal and the target number to be called.
  • the network side refers to the network side device 12 as shown in FIG. 1 or the network side device 21 as shown in FIG. 2. In this document, the network side is also referred to as the network side device, that is, this The network side and network side devices in the application embodiment have the same understanding.
  • Step 302 The network side device judges whether the call request to the target number initiated by the first terminal can be processed currently, if yes, execute step 303, if not, execute step 304.
  • Step 303 Establish a call connection between the first terminal and the target number.
  • the call request when the network-side device is currently able to process the call request to the target number initiated by the first terminal, the call request is processed to establish the first terminal and the terminal corresponding to the target number, such as the first terminal in FIG. 2 After the call connection between the two terminals is established, it enters the call phase.
  • Step 304 The network side device determines the reason why the call request cannot be processed currently.
  • the number of call requests currently to be processed by the network-side device as described above exceeds the call requests that the network-side device can handle.
  • the total number for example, the number of call requests to be processed at the base station in the network-side equipment exceeds the load; or the number of call requests currently pending at the server in the network-side equipment as shown in Figure 2 exceeds the load; or as shown in Figure 2
  • the number of call requests currently to be processed by the base station and the server in the network-side equipment shown in Figure 2 exceeds the load; or a certain device in the network-side equipment has a power failure, for example, the server shown in Figure 2
  • a power failure condition occurs, causing the server to fail to receive or process the call request to the target number initiated by the first terminal sent by the base station in time.
  • the signal transmission line in the network side equipment is aging and broken.
  • the aforementioned situation that the number of call requests currently to be processed by the network-side device exceeds the total number of call requests that the network-side device can handle is regarded as a network congestion state.
  • the network-side device The number of call requests that the base station can handle is 300, and the call request to the target number initiated by the first terminal is the 301st call request received by the base station. It is determined that the current network side device is in a network congestion state and needs to wait.
  • the reason that the call request cannot be processed other than the overload of the number of call requests processed by the network side device is collectively referred to as the network abnormal state.
  • the network congestion state means that the network side device can receive the call request initiated by the first terminal to the target number, but there are many call requests waiting to be processed, and it takes a while to process the call request initiated by the first terminal. That is to say, in the state of network congestion, network abnormalities such as abnormal communication link between the first terminal, the network side device and the second terminal corresponding to the target number, power failure, and line damage are only due to the pending call.
  • the request volume is large, and the call request can be processed after waiting for a certain period of time. Therefore, in order to remind the user of the first terminal that the call request initiated by it can be processed, it is necessary to make the call request unable to be processed because of network congestion. Inform users to soothe the panic and anxiety in an emergency.
  • the aforementioned abnormal state of the network refers to problems with the communication link between the first terminal, the network side device, and the second terminal, or power failure, line damage, etc., causing the network side device to fail to receive the first terminal’s initiation Or the first terminal did not send a call request due to poor network signal.
  • Step 305 If the network side device determines that the current reason that the call request cannot be processed is network congestion, it obtains call failure feedback information.
  • the call failure feedback information is used to indicate that the network side device is currently in a network congestion state and needs to wait to process the call request.
  • the call failure feedback information is predetermined information preset by the network side device, which can be directly obtained when network congestion occurs; or it is information temporarily generated according to a determined network congestion state.
  • the call failure feedback information is a text message or a piece of voice. If the call failure feedback information is a piece of voice, for example, the call failure feedback information is a voice like "There are many call requests pending, please wait patiently". . Of course, in order to avoid that the time is too long to affect the processing of the call request by the network side device, the duration of the voice in the call failure feedback information should be controlled within a reasonable time range.
  • Step 306 The network side device sends the call failure feedback information to the first terminal. Accordingly, the first terminal can receive the call failure feedback information sent by the network side device.
  • the call failure feedback information is sent to the first terminal, and the call failure feedback information is used to remind the user of the current network
  • the side device handles the network congestion state, and cannot process the call request sent by the first terminal in time, avoiding the user's panic or anxiety due to not knowing the reason for the call failure, so it can calm the user's mood, improve the user experience, and also Avoid personal or property damage caused by inappropriate behaviors of users in an anxious or panic state.
  • the call failure feedback information is also used to indicate whether to continue to wait to establish a call connection, that is, while the call failure feedback information is used to effectively prompt the user of network congestion, it can also be used to indicate the call failure feedback information. Inform the user to continue waiting without directly hanging up the phone, that is, to keep the user's call request, so that the call connection with the target number can be established in time when the network side can process the call request normally, thereby improving the success rate of the call and Call efficiency, which is convenient for continuous calls after a call fails.
  • the call failure feedback information includes the shortest time period required for the network side device to end the network congestion state, or does not include the shortest time period.
  • the network side device determines the shortest duration required to resolve the current network congestion state and be able to process the call request sent by the first terminal before sending the call failure feedback information to the first terminal, that is, The shortest time required for the network side device to end the network congestion state, and this shortest time is referred to as the third waiting time in the embodiment of the present application.
  • the user can know at least how long the call request needs to wait before being processed according to the call failure feedback message including the third waiting time, so as to avoid anxiety or panic caused by the user not knowing how long it needs to wait, and It is convenient for users to make corresponding decisions according to the length of waiting time.
  • Step 307 Hold the call request.
  • step 307 is performed simultaneously with step 306, that is, the network holds the call request when sending a call failure feedback message to the first terminal; or it is performed before step 306, that is, the call request is held first and then sent to the first terminal.
  • the terminal sends a call failure feedback message; or it is executed after step 306, that is, the call failure feedback message is first sent to the first terminal and then the call request is held.
  • the execution order of step 307 and step 306 is not limited In the following, step 307 is executed after step 306 as an example for illustration.
  • the network side device when the network side device determines that it cannot process the call request to the target number initiated by the first terminal, it will not immediately terminate the call request, that is, it will not hang up the user's call through the first terminal. Instead, the call request is kept on the phone, which can avoid the need for the first terminal to resend the call request to the target number after terminating the call request, so the call time can be saved and the call efficiency can be improved.
  • Step 308 After receiving the call failure feedback information, the first terminal detects the first operation for the first terminal, and determines the waiting information according to the first operation.
  • the indication waiting information is used to indicate that the first terminal can wait to establish a call connection.
  • the user of the first terminal can perform the first operation according to the content of the call failure feedback information, so that the indication waiting information can be determined according to the first operation.
  • the first operation is acquired through a click operation or a key operation, or through a voice method, or through other operation methods.
  • the first operation is the operation of pressing the number keys, which means that the first terminal needs to continue to wait for the establishment of a call connection; and suppose the first operation is the operation of pressing the "*" key, it means that the first terminal actively requests to hang up the call .
  • the indicating waiting information only indicates that the first terminal needs to wait for the establishment of a call connection, and does not limit the length of waiting for the establishment of a call connection, or at the same time instructs the first terminal to be able to wait for the establishment of a call connection and the corresponding waiting time, for example, As the first waiting time, the first waiting time is the longest time that the first terminal can wait to establish a call connection with the second terminal.
  • the first waiting time is when the third waiting time is not indicated in the call failure feedback message, and the user sets the time he is willing to wait through the first operation, for example, the first operation is set to press the number key "1". ", it means that the first terminal needs to wait for 8s. Then, when the first terminal detects the first operation of pressing the number key "1", it determines that the waiting time indicated by the waiting information is 8s. For another example, the first operation is also the operation of sequentially pressing the number keys "1" and "2" to indicate that the first terminal needs to wait for 12s. Then the first terminal detects that the number keys "1" and "2" are pressed quickly. During operation, it is determined that the waiting time indicated in the indicating waiting information is 12s.
  • the call failure feedback information indicates that there is a third waiting time, that is, when the network side device ends the shortest time of network congestion, the first waiting time is directly determined as the same as the third waiting time through the first operation duration. For example, assuming that the third waiting time indicated in the call failure feedback message is 10s, the first waiting time corresponding to the first operation is directly determined as 10s.
  • the call failure feedback message indicates that there is a third waiting period, and the user sets the first waiting period by himself through the first operation, and is not limited by the third waiting period.
  • the third waiting time indicated in the call failure feedback message is 10s, and the user sets any time less than, equal to, or greater than 10s through the first operation.
  • the call failure feedback message clearly indicates the third waiting time that the network side can end the congestion state as soon as possible, in order to ensure that the call request can be processed within the first waiting time set by the user, the user corresponds to the first waiting time set by the user.
  • the first waiting time is generally greater than or equal to the third waiting time.
  • Step 309 The first terminal sends an indication waiting information to the network side device, and accordingly, the network side device can receive the indication waiting information sent by the first terminal based on the call failure feedback information.
  • the first terminal sends the determined indication waiting information to the network side device after determining the indication waiting information according to the first operation of the user, and then the network side device can receive the indication waiting information sent by the first terminal , To make it clear that the user can continue to wait according to the instruction waiting information, so the call request continues to be held without hanging up the phone.
  • Step 310 The network side device determines the time at which the call request can be processed according to the received instruction waiting information, and processes the call request to the target number initiated by the first terminal at the time to establish a relationship between the first terminal and the second terminal. Call connection between.
  • the indicating waiting information is used to indicate that the first terminal can wait to establish a call connection. Then, after the network side device receives the indicating waiting information, the network side device will wait to be able to process the call Once it is determined that the requested time can be processed, the call request is processed in time to establish a call connection between the first terminal and the second terminal as soon as possible.
  • the waiting information does not indicate the length of time the first terminal waits to establish a call connection, that is, no waiting time is set. As long as the network side device ends congestion, the first terminal and the first terminal can be established in time. Call connection between the second terminal. In other words, there is no need to consider the time to wait for the call to be established, and only need to establish a call connection between the first terminal and the second terminal corresponding to the target number when the network side device ends congestion.
  • the network side device if the waiting time for the first terminal set by the user to be set by the user is the first waiting time, the network side device reaches the first waiting time after receiving the waiting information. Inside, if it is determined that the network side can process the call request, the call connection between the first terminal and the second terminal is established according to the call request.
  • the network-side device can also determine whether it is in a congested state. If it is still determined that the network-side device is in a congested state, That is, it indicates that the call request initiated by the first terminal cannot be processed within the time specified by the user, and the call request is terminated at this time to save the user time.
  • the network-side device after the network-side device reaches the first waiting period from the time it receives the indication waiting information, and before judging whether it is in a congested state, the network-side device can also determine to end the network The second waiting time required for the congestion state, where, in order to ensure that the network side device can process the call request initiated by the first terminal within the first waiting time, establish a connection between the first terminal and the second terminal corresponding to the target number Call connection to improve call efficiency.
  • the first waiting period is greater than or equal to the second waiting period. For example, if the second waiting time is 10s, the first waiting time is 12s.
  • the network side device when it is determined that the first waiting period is less than the second waiting period, the network side device sends a waiting insufficient prompt message, where the waiting insufficient prompt information is used to indicate the network side The device cannot process the call request within the first waiting time period. In this way, the insufficient waiting prompt information can clearly inform the user that the call request initiated by the device cannot be processed within the waiting time period set by the device, so as to further effectively prompt the user.
  • the network side device can also determine whether the target number is a preset emergency number after sending the insufficient waiting prompt message to the first terminal, for example, the preset emergency number is 110, 119 or other alarm calls or For emergency calls such as 120, if the target number is a preset emergency number, it means that the user's current situation is more critical, then the call request initiated by the first terminal will continue to be maintained, and the call failure feedback message will be sent to the first terminal again. , To inform the user of the first terminal of the reason for the failure of the call again, so as to reassure the user in a critical situation as many times as possible, so as to minimize the user’s anxiety and panic, so as to avoid the user being unable to make a call in an emergency situation. Inappropriate behavior, or suffer unnecessary personal or property damage; if it is not the preset emergency number, the call request is terminated, which can prevent the user from wasting waiting time, so that the user can choose other handling methods to deal with the current emergency in time.
  • the target number is a preset emergency number
  • the third waiting period is based on the end of the network congestion state on the network side, that is, based on other call requests waiting to be processed before the call request initiated by the first terminal has been processed. If the required time is determined, depending on the network situation, the determined processing time may be different from the actual processing time required. Therefore, in some implementations, the network side device starts from sending the call failure feedback information The actual length of time between actually starting to process the call request is called the fourth waiting time.
  • the third waiting period may be the same as or different from the fourth waiting period, that is, the fourth waiting period may be greater than the third waiting period, or may be less than or equal to the third waiting period.
  • the network side device may establish a call between the first terminal and the second terminal corresponding to the target number when the fourth waiting period is reached after sending the call failure feedback information. connection.
  • the third waiting time is 15s. If the network side device has actually processed call requests other than the call request initiated by the first terminal at the 12th second, that is, the fourth waiting time is 12s, so the network side device actually The above is to start processing the call request initiated by the first terminal after waiting 12s, and establish the call connection between the first terminal and the second terminal.
  • Step 311 The first terminal detects the second operation according to the received call failure feedback information, and determines the termination request information of the termination call request according to the second operation.
  • the user of the first terminal selects to terminate the call request through the second operation, and the first terminal can then use the detected second operation Generate termination request information that determines the termination call request.
  • the second operation is a key operation of the user pressing a corresponding function key in the first terminal based on the call failure feedback information, or a voice made by the user.
  • Step 312 The first terminal sends termination request information to the network side device, and the network side device can receive the termination request information sent by the first terminal.
  • Step 313 The network side device terminates the call request according to the termination request information.
  • the network-side device after the network-side device receives the termination request information, it can terminate the call request initiated by the first terminal to the second terminal corresponding to the target number according to the termination request information, so that the first terminal can initiate a connection Call requests from other numbers to avoid waste of time and power caused by waiting for the terminal corresponding to the target number to establish a call connection.
  • the network side after receiving the call request initiated by the first terminal to the target number, the network side determines whether the call request can be processed currently according to its own network conditions, and when the call request cannot be processed , The network side does not immediately terminate the call request, but determines the reason why the call request cannot be processed, and when it determines that the reason why the call request cannot be processed is network congestion, it sends a call failure feedback message to the first terminal, prompting the first terminal.
  • the reason for the failure of a user's call request on a terminal can therefore reassure users in a panic or anxious state, prevent the user from making excessive behaviors due to unawareness of the call failure, and improve user experience.
  • the network side while sending the call failure feedback message to the first terminal, the network side continues to hold the call request instead of directly hanging up the call as in the related art, so that the call can be processed when the network is no longer congested
  • the predetermined trigger condition for example, receiving specific information sent by the first terminal
  • the call connection between the first terminal and the terminal corresponding to the target number can be established in time .
  • the target number for example, the second terminal
  • an embodiment of the present application provides a call control device, which is a hardware structure, a software module, or a hardware structure plus a software module.
  • the call control device is implemented by a chip system, which is composed of a chip, or includes a chip and other discrete devices.
  • the call control device includes a first receiving unit 401, a first determining unit 402, and a feedback unit 403. among them:
  • the first receiving unit 401 is configured to receive a call request to the target number initiated by the first terminal;
  • the first determining unit 402 is configured to determine the reason why the call request cannot be processed currently if the call request cannot be processed currently;
  • the feedback unit 403 is configured to send call failure feedback information to the first terminal when the current call request cannot be processed because the network side is congested, where the call failure feedback information is used to indicate that the network side is currently in a network congestion state.
  • the call failure feedback information is also used to indicate whether to continue to wait to establish a call connection.
  • the call control device further includes:
  • the holding unit 404 is used to hold the call request
  • the second receiving unit 405 is configured to receive waiting information that is sent by the first terminal based on the call failure feedback information, where the waiting information is used to indicate that the first terminal can wait to establish a call connection;
  • the call establishment unit 406 is configured to establish a call connection between the first terminal and the second terminal corresponding to the target number when the network side can process the call request according to the waiting indication information.
  • the indicating waiting information is also used to indicate the first waiting time set by the user.
  • the first waiting time is the longest time that the first terminal can wait to establish a call connection with the second terminal; the call establishing unit 406 uses in:
  • the call connection between the first terminal and the second terminal is established according to the call request.
  • the indicating waiting information is also used to indicate the first waiting time set by the user, and the first waiting time is the longest time that the first terminal can wait to establish a call connection with the second terminal; as shown in FIG. 4b,
  • the call control device also includes a termination request unit 407, configured to:
  • the call control device further includes a second determining unit 408, configured to:
  • the termination request unit 407 determines whether the network side is still in a congested state, when receiving the waiting information indicating that the network side is in a congested state, determine the second waiting time required for the network side to end the network congested state;
  • the second determining unit 408 is further configured to:
  • the waiting insufficient prompt information is sent to the first terminal, where the waiting insufficient prompt information is used to indicate that the network side cannot process the call request within the first waiting time period.
  • the call control device further includes a third determining unit 409, configured to:
  • the second determining unit 408 After the second determining unit 408 sends the waiting insufficient prompt message to the first terminal, it is determined whether the target number is a preset emergency number;
  • the call failure feedback information is also used to indicate the third waiting time, which is the shortest time for the network side to end the network congestion state, and the call establishing unit 406 is also used to:
  • the call connection between the first terminal and the second terminal is established when the fourth waiting period is reached from when the call failure feedback information is sent;
  • the waiting time is the time from sending the call failure feedback message to the actual processing of the call request.
  • the termination request unit 407 is also used to:
  • the second determining unit 408 After the second determining unit 408 sends the call failure feedback information to the first terminal, receiving the termination request information for requesting the termination of the call request sent by the first terminal;
  • the call request is terminated according to the termination call request information.
  • an embodiment of the present application provides a call control device, which is a hardware structure, a software module, or a hardware structure plus a software module.
  • the call control device is implemented by a chip system, which is composed of a chip, or includes a chip and other discrete devices. As shown in FIG. 5, the call control device includes a sending unit 501 and a receiving unit 502. among them:
  • the sending unit 501 is configured to send a call request for establishing a call with the target number to the network side;
  • the receiving unit 502 is configured to receive call failure feedback information sent by the network side, where the call failure feedback information is used to indicate that the network side is currently in a network congestion state.
  • the call failure feedback information is also used to indicate whether to continue to wait to establish a call connection
  • the sending unit 501 is also used to:
  • the indication waiting information is used to indicate that the first terminal can wait for the establishment of a call connection
  • the indicating waiting information is also used to indicate the first waiting time set by the user, where the first waiting time is the longest time that the first terminal can wait for the second terminal corresponding to the target number to establish a call connection.
  • the sending unit 501 is further configured to:
  • the termination request information is generated, wherein the termination call request information is used to request the termination call request;
  • each functional module in each embodiment of this application Integrate in a processor, or exist alone physically, or two or more modules are integrated in one module.
  • the aforementioned integrated modules are implemented in the form of hardware, or implemented in the form of software functional modules.
  • an embodiment of the present application also provides a call control device.
  • the call control device is, for example, a terminal device such as a mobile phone and a smart watch, such as the terminal 10 or the terminal 11 shown in FIG. 1, or as shown in FIG.
  • the calling terminal 20 includes at least one processor 601 and a memory 602 connected to the at least one processor.
  • the specific connection medium between the processor 601 and the memory 602 is not limited in the embodiment of the present application.
  • the processor 601 and the memory 602 are connected through a bus 600 as an example.
  • the bus 600 is represented by a thick line in FIG. 6, and the connection mode between other components is only for schematic illustration and is not intended to be limiting. .
  • the bus 600 is divided into an address bus, a data bus, a control bus, etc. For ease of presentation, only a thick line is shown in FIG. 6, but it does not mean that there is only one bus or one type of bus.
  • an embodiment of the present application also provides a call control device.
  • the call control device is, for example, a network device such as a base station and a server, such as the network side device 12 shown in FIG. 1, or the network side device shown in FIG. Equipment 21.
  • the call control device includes at least one processor 701 and a memory 702 connected to the at least one processor.
  • the specific connection medium between the processor 701 and the memory 702 is not limited in the embodiment of the present application.
  • the processor 701 and the memory 702 are connected through the bus 700 as an example.
  • the bus 700 is represented by a thick line in FIG. 7.
  • the connection mode between other components is only for schematic illustration and is not to be taken as a limitation. .
  • the bus 700 is divided into an address bus, a data bus, a control bus, etc.
  • a thick line is used in FIG. 7 to represent it, but it does not mean that there is only one bus or one type of bus.
  • the memory 602 in FIG. 6 and the memory 702 shown in FIG. 7 both store instructions that can be executed by at least one processor. At least one processor can execute the aforementioned call by executing the instructions stored in the memory 602 or the memory 702. Steps included in the control method.
  • the processor 601 and the processor 701 are both the control center of the call control device, which can connect various parts of the entire call control device by using various interfaces and lines, and by running or executing the instructions stored in the memory 602 and the memory 702 and calling The data in the memory 602 and the memory 702, various functions and processing data of the call control device, thereby overall monitoring of the call control device.
  • both the processor 601 and the processor 701 include one or more processing units.
  • Both the processor 601 and the processor 701 integrate an application processor and a modem processor.
  • the application processor mainly processes the operating system. , User interface and application programs, etc.
  • the modem processor mainly deals with wireless communication.
  • the foregoing modem processor can also choose not to be integrated into the processor 601 and the processor 701.
  • the processor 601 and the memory 602, and the processor 701 and the memory 702 are implemented on the same chip, and in some embodiments, they are implemented on separate chips.
  • the processor 601 and the processor 701 are general-purpose processors, such as a central processing unit (CPU), a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic devices, discrete gates, or Transistor logic devices and discrete hardware components can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application.
  • a general-purpose processor is a microprocessor or any conventional processor. The steps of the call control method disclosed in the embodiments of the present application are directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • the memory 602 and the memory 702 can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules.
  • both the memory 602 and the memory 702 include at least one type of storage medium, such as flash memory, hard disk, multimedia card, card-type memory, random access memory (RAM), static random access memory ( Static Random Access Memory (SRAM), Programmable Read Only Memory (PROM), Read Only Memory (Read Only Memory, ROM), Electrically Erasable Programmable Read-Only Memory , EEPROM), magnetic memory, magnetic disks, optical disks, etc.
  • the memory 602 and the memory 702 are any other media that can be used to carry or store desired program codes in the form of instructions or data structures and can be accessed by a computer, but are not limited thereto.
  • the memory 602 and the memory 702 are circuits or any other devices capable of implementing storage functions, and are used to store program instructions, or data, or program instructions and data.
  • the code corresponding to the call control method introduced in the foregoing embodiment can be solidified into the chip, so that the chip can execute the steps of the foregoing call control method during operation.
  • the design and programming of the processor 601 and the processor 701 is a technology well known to those skilled in the art, and will not be repeated here.
  • an embodiment of the present application provides a storage medium that stores computer-executable instructions.
  • the computer-executable instructions When the computer-executable instructions are used to run the computer instructions on the computer, the computer executes the aforementioned call Control method steps.
  • this application adopts the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware.
  • this application adopts the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) containing computer-usable program codes.
  • these computer program instructions are stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Landscapes

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

Abstract

本申请公开了一种通话控制方法、装置、设备及存储介质，涉及通信技术领域，用于在呼叫失败时提示用户呼叫失败的原因，避免用户因呼叫失败产生恐慌焦虑的心理，造成不必要的人身财产损失，提升用户体验。所述方法包括：接收第一终端发起的对目标号码的呼叫请求；若当前无法处理所述呼叫请求，确定当前无法处理所述呼叫请求的原因；在当前无法处理所述呼叫请求的原因为网络侧拥堵时，向所述第一终端发送呼叫失败反馈信息，其中，所述呼叫失败反馈信息用于指示所述网络侧当前处于网络拥堵状态。

Description

通话控制方法、装置、设备及存储介质
相关申请
本申请要求2019年05月20日申请的，申请号为201910417175.5，名称为“一种通话控制方法、装置、设备及存储介质”的中国专利申请的优先权，在此将其全文引入作为参考。
技术领域
本申请涉及通信技术领域，尤其涉及一种通话控制方法、装置、设备及存储介质。
背景技术
通话是手机、智能手表等终端的一种基本的功能，其在日常生活中使用十分广泛，也是人们较常使用的一种沟通方式。现实生活中，用户在拨打电话时可能存在着如因网络信号差或者网络拥堵等问题导致呼叫失败，而一旦呼叫失败的话网络侧则会挂断电话，而对于用户来说，却并不知道呼叫失败的具体原因，例如在报警或其它紧急情况下，这将会使得用户恐慌、焦虑的心理加重，进而给用户造成较大的不便，这可能会给用户造成无法挽回的经济损失，甚至危及到用户的生命安全。
由此可见，相关技术中存在着因呼叫失败给用户带来不便或造成的生命财产损失的技术问题。
发明内容
本申请实施例提供了一种通话控制方法、装置、设备及存储介质，能够在呼叫失败时提示用户呼叫失败的原因，避免用户因呼叫失败产生恐慌焦虑的心理，造成不必要的人身财产损失，提升用户体验。
第一方面，提供了一种通话控制方法，所述方法包括：
接收第一终端发起的对目标号码的呼叫请求；
若当前无法处理所述呼叫请求，确定当前无法处理所述呼叫请求的原因；
在当前无法处理所述呼叫请求的原因为网络侧拥堵时，向所述第一终端发送呼叫失败反馈信息，其中，所述呼叫失败反馈信息用于指示所述网络侧当前处于网络拥堵状态。
在一些实施例中，所述呼叫失败反馈信息还用于指示是否继续等待建立通话连接，所述方法还包括：
保持所述呼叫请求；
接收所述第一终端基于所述呼叫失败反馈信息发送的指示等待信息，其中，所述指示等待信息用于指示所述第一终端能够等待建立通话连接；
根据所述等待指示信息，在所述网络侧能够处理所述呼叫请求时，建立所述第一终端与所述目标号码对应的第二终端之间的通话连接。
在一些实施例中，所述指示等待信息还用于指示用户设置的第一等待时长，所述第一等待时长为所述第一终端能够等待的与所述第二终端建立通话连接的最长时长；
则，在从接收所述指示等待信息时开始的所述第一等待时长内，若确定所述网络侧能够处理所述呼叫请求，则根据所述呼叫请求建立所述第一终端与所述第二终端之间的通话连接。
在一些实施例中，所述指示等待信息还用于指示用户设置的第一等待时长，所述第一等待时长为所述第一终端能够等待的与所述第二终端建立通话连接的最长时长；则在保持所述呼叫请求之后，所述方法还包括：
在从接收所述指示等待信息时开始达到所述第一等待时长后，确定所述网络侧是否仍处于网络拥堵状态；
若仍处于网络拥堵状态，则终止所述呼叫请求。
在一些实施例中，在确定所述网络侧是否仍然处于拥堵状态之前，所述方法还包括：
在接收所述指示等待信息时，确定所述网络侧结束网络拥堵状态所需要的第二等待时长；
确定所述第一等待时长大于或等于所述第二等待时长。
在一些实施例中，所述方法还包括：
若确定所述第一等待时长小于所述第二等待时长，则向所述第一终端发送等待不足提示信息，其中，所述等待不足提示信息用于指示所述网络侧在所述第一等待时长内无法处理所述呼叫请求。
在一些实施例中，在向所述第一终端发送等待不足提示信息之后，所述方法还包括：
确定所述目标号码是否是预设的紧急号码；
若是所述预设的紧急号码，则继续保持所述呼叫请求；
若不是所述预设的紧急号码，则终止所述呼叫请求。
在一些实施例中，所述呼叫失败反馈信息还用于指示第三等待时长，所述第三等待时长为所述网络侧结束网络拥堵状态的最短时长，则在保持所述呼叫请求之后，所述方法还包括：
在从发送所述呼叫失败反馈信息时开始达到第四等待时长时，建立所述第一终端与所述第二终端之间的通话连接；其中，所述第四等待时长为从发送所述呼叫失败反馈信息开始到实际处理所述呼叫请求之间的时长。
在一些实施例中，在向所述第一终端发送呼叫失败反馈信息之后，所述方法还包括：
接收所述第一终端发送的用于请求终止所述呼叫请求的终止请求信息；
根据所述终止呼叫请求信息，终止所述呼叫请求。
第二方面，提供一种通话控制方法，所述方法包括：
向网络侧发送请求与目标号码建立通话的呼叫请求；
接收所述网络侧发送的呼叫失败反馈信息，其中，所述呼叫失败反馈信息用于指示所述网络侧当前处于网络拥堵状态。
在一些实施例中，所述呼叫失败反馈信息还用于指示是否继续等待建立通话连接，在接收所述呼叫失败反馈信息之后，所述方法还包括：
获得用户针对所述第一终端进行的第一操作；
根据所述第一操作，确定指示等待信息；其中，所述指示等待信息用于指示所述第一终端能够等待建立通话连接；
向所述网络侧发送所述指示等待信息。
在一些实施例中，所述指示等待信息还用于指示用户设置的第一等待时长，其中，所述第一等待时长为所述第一终端能够等待的与所述目标号码对应的第二终端建立通话连接的最长时长。
在一些实施例中，在接收所述网络侧发送的呼叫失败反馈信息之后，所述方法还包括：
获得用户针对所述第一终端进行的第二操作；
根据所述第二操作，生成终止请求信息，其中，所述终止呼叫请求信息用于请求终止所述呼叫请求；
向所述网络侧发送所述终止请求信息。
第三方面，提供了一种通话控制装置，所述装置包括：
第一接收单元，用于接收第一终端发起的对目标号码的呼叫请求；
第一确定单元，用于若当前无法处理所述呼叫请求，确定当前无法处理所述呼叫请求的原因；
反馈单元，用于在当前无法处理所述呼叫请求的原因为网络侧拥堵时，向所述第一终端发送呼叫失败反馈信息，其中，所述呼叫失败反馈信息用于指示所述网络侧当前处于网络拥堵状态。
在一些实施例中，所述呼叫失败反馈信息还用于指示是否继续等待建立通话连接，所述装置还包括：
保持单元，用于保持所述呼叫请求；
第二接收单元，用于接收所述第一终端基于所述呼叫失败反馈信息发送的指示等待信息，其中，所述指示等待信息用于指示所述第一终端能够等待建立通话连接；
通话建立单元，用于根据所述等待指示信息，在所述网络侧能够处理所述呼叫请求时，建立所述第一终端与所述目标号码对应的第二终端之间的通话连接。
在一些实施例中，所述指示等待信息还用于指示用户设置的第一等待时长，所述第一等待时长为所述第一终端能够等待的与所述第二终端建立通话连接的最长时长；所述通话建立单元，用于：
在从接收所述指示等待信息时开始的所述第一等待时长内，若确定所述网络侧能够处理所述呼叫请求，则根据所述呼叫请求建立所述第一终端与所述第二终端之间的通话连接。
在一些实施例中，所述指示等待信息还用于指示用户设置的第一等待时长，所述第一等待时长为所述第一终端能够等待的与所述第二终端建立通话连接的最长时长；所述装置还包括终止请求单元，用于：
在从接收所述指示等待信息时开始达到所述第一等待时长后，确定所述网络侧是否仍处于网络拥堵状态；
若仍处于网络拥堵状态，则终止所述呼叫请求。
在一些实施例中，所述装置还包括第二确定单元，还用于：
在所述终止请求单元确定所述网络侧是否仍然处于拥堵状态之前，在接收所述指示等待信息时，确定所述网络侧结束网络拥堵状态所需要的第二等待时长；
确定所述第一等待时长大于或等于所述第二等待时长。
在一些实施例中，所述第二确定单元还用于：
若确定所述第一等待时长小于所述第二等待时长，则向所述第一终端发送等待不足提示信息，其中，所述等待不足提示信息用于指示所述网络侧在所述第一等待时长内无法处理所述呼叫请求。
在一些实施例中，所述装置还包括第三确定单元，用于：
在所述第二确定单元向所述第一终端发送等待不足提示信息之后，确定所述目标号码是否是预设的紧急号码；
若是所述预设的紧急号码，则继续保持所述呼叫请求；
若不是所述预设的紧急号码，则终止所述呼叫请求。
在一些实施例中，所述呼叫失败反馈信息还用于指示第三等待时长，所述第三等待时长为所述网络侧结束所述拥堵状态的最短时长，所述建立通话单元还用于：
在所述第二确定单元向所述第一终端发送等待不足提示信息之后，在从发送所述呼叫失败反馈信息时开始达到第四等待时长时，建立所述第一终端与所述第二终端之间的通话连接；其中，所述第四等待时长为从发送所述呼叫失败反馈信息开始到实际处理所述呼叫请求之间的时长。
在一些实施例中，所述终止请求单元还用于：
在所述第二确定单元向所述第一终端发送呼叫失败反馈信息之后，接收所述第一终端发送的用于请求终止所述呼叫请求的终止请求信息；
根据所述终止呼叫请求信息终止所述呼叫请求。
第四方面，提供一种通话控制装置，所述装置包括：
发送单元，用于向网络侧发送请求与目标号码建立通话的呼叫请求；
接收单元，用于接收所述网络侧发送的呼叫失败反馈信息，其中，所述呼叫失败反馈信息用于指示所述网络侧当前处于网络拥堵状态。
在一些实施例中，所述呼叫失败反馈信息还用于指示是否继续等待建立通话连接，所述发送单元还用于：
在接收所述呼叫失败反馈信息之后，获得用户针对所述第一终端进行的第一操作；
根据所述第一操作，确定指示等待信息；其中，所述指示等待信息用于指示所述第一终端能够等待建立通话连接；
向所述网络侧发送所述指示等待信息。
在一些实施例中，所述指示等待信息还用于指示用户设置的第一等待时长，其中，所述第一等待时长为所述第一终端能够等待的与所述目标号码对应的第二终端建立通话连接的最长时长。
在一些实施例中，所述发送单元还用于：
在接收所述网络侧发送的呼叫失败反馈信息之后，获得用户针对所述第一终端进行的第二操作；
根据所述第二操作，生成终止请求信息，其中，所述终止呼叫请求信息用于请求终止所述呼叫请求；
向所述网络侧设备发送所述终止请求信息。
第五方面，提供一种通话控制设备，所述设备包括：
存储器，用于存储程序指令；
处理器，用于调用所述存储器中存储的程序指令，按照获得的程序指令执行第一方面中任一所述的方法包括的步骤。
第六方面，提供一种通话控制设备，所述设备包括：
存储器，用于存储程序指令；
处理器，用于调用所述存储器中存储的程序指令，按照获得的程序指令执行第二方面中任一所述的方法包括的步骤。
第七方面，提供一种存储介质，所述存储介质存储有计算机可执行指令，所述计算机可执行指令用于使计算机执行第一方面中任一方法包括的步骤。
第八方面，提供一种存储介质，所述存储介质存储有计算机可执行指令，所述计算机可执行指令用于使计算机执行第二方面中任一方法包括的步骤。
在本申请实施例中，当网络侧接收到第一终端向目标号码发起的呼叫请求后，能够先判断当前是否能够处理该呼叫请求，并在无法处理该呼叫请求时确定无法处理呼叫请求的具体原因，若确定当前无法处理该呼叫请求的原因是由于网络拥堵，则能够向第一终端发送呼叫失败反馈信息，以通过该呼叫失败反馈信息告知使用第一终端的用户当前由于是网络拥堵而无法立即建立通话，也就是说，在第一终端发起的呼叫请求失败后，网络侧能够及时地告知用户本次呼叫失败是由于网络拥堵，从而对用户进行了有效提示，因此，例如在拨打110等紧急打电话时，用户能够知晓呼叫失败的具体原因是由于网络拥堵，而并非是其它不可知的原因，这样能够安抚处于恐慌或焦急状态的用户，避免用户因不知道呼叫失败的具体原因而盲目地做出过激行为，进而避免一些财产损失甚至生命危险，提升用户体验感。
附图说明
为了更清楚地说明本申请实施例或相关技术中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例。
图1为本申请实施例提供的一种应用场景示意图；
图2为本申请实施例提供的另一种应用场景示意图；
图3为本申请实施例提供的通话控制方法的流程图；
图4a为本申请实施例提供的通话控制装置的结构框图；
图4b为本申请实施例提供的通话控制装置的另一结构框图；
图5为本申请实施例提供的通话控制装置的另一结构框图；
图6为本申请实施例提供的通话控制设备的结构示意图；
图7为本申请实施例提供的通话控制设备的另一结构示意图。
具体实施方式
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合本申请实施例中的附图，对本申请的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请技术方案的一部分实施例，而不是全部的实施例。基于本申请文件中记载的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请技术方案保护的范围。在不冲突的情况下，本申请中的实施例及实施例中的特征能够相互任意组合。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，也能以不同于此处的顺序执行所示出或描述的步骤。
本申请的说明书和权利要求书及上述附图中的术语“第一”和“第二”是用于区别不同对象，而非用于描述特定顺序。此外，术语“包括”以及它们任何变形，意图在于覆盖不排他的保护。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是示例性的还包括没有列出的步骤或单元，或示例性的还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。
本申请实施例中，“多个”表示至少两个，例如表示两个、三个或者更多个，本申请实施例不做限制。
为了便于理解，下面先对本申请实施例的技术背景进行介绍。
如前文叙述，相关技术中，当出现如网络堵塞等原因时，可能出现呼叫失败的情况，例如，呼叫控制中心在接收到终端A发起的对目标号码的呼叫请求后，检测到当前网络拥堵、待处理呼叫请求量超负荷等情况，导致当前无法处理终端A发起的呼叫请求，从而无法建立终端A与目标号码对应的终端(例如终端B)之间的通话连接，进而直接挂断终端A的呼叫，但终端A的用户并不知晓为什么不能成功建立通话，所以当用户遇到紧急情况时，容易因呼叫失败产生恐慌、焦虑的心情，进而给用户带来不便，甚至还可能影响用户的财产甚至人生安全。
鉴于此，本申请人的发明人提供了一种通话控制的技术方案，该方案中，在接收到第一终端向目标号码发起的呼叫请求后，网络侧根据自身网络情况确定当前是否能够处理该呼叫请求，在不能处理该呼叫请求时，网络侧并不立即终止该呼叫请求，而是确定无法处理该呼叫请求的原因，并在确定出无法处理该呼叫请求的原因是网络拥堵时，向第一终端 发送呼叫失败反馈信息，提示第一终端的用户呼叫请求失败的原因，因此能够安抚处于恐慌或焦急状态的用户，避免用户因不知道呼叫失败而盲目做出过激行为，提升用户体验感。
在一些实施例中，在向第一终端发送呼叫失败反馈消息的同时，网络侧能够继续保持呼叫请求，而并不是如相关技术中一样直接挂断电话，进而在网络不再拥堵而能够处理该呼叫请求的时候，且满足预定触发条件(例如接收到第一终端发送的特定信息)时，就能够及时地建立第一终端与目标号码对应的终端(例如称作第二终端)之间的通话连接，以即使地响应第一终端的呼叫请求，尽快地建立第一终端与第二终端之间的通话，以尽量提高呼叫的效率，以及提高呼叫成功的概率。
在介绍完本申请实施例的设计思想后，下面对本申请实施例的技术方案能够适用的应用场景做一些简单介绍，需要说明的是，以下介绍的应用场景仅用于说明本申请实施例而非限定。在具体实施时，根据实际需要灵活地应用本申请实施例提供的技术方案。
请参见图1所示的一种应用场景示意图，该应用场景中包括终端10、终端11和网络侧设备12，其中，在一些实施例中，终端10和终端11是手机、智能手表、固定电话等具有通话功能的终端，例如终端10为主叫终端，终端11为被叫终端；网络侧设备12是由建立终端10和终端11之间的通话连接所需要的一个或多个网络设备组成的系统，网络侧设备12例如也称为网络侧或呼叫控制中心。
当网络侧设备12接收到终端10发起的对目标号码的呼叫请求后，网络侧设备12判断当前是否能够处理该呼叫请求，若不能处理该呼叫请求，则确定出不能处理该呼叫请求的原因，当确定出不能处理呼叫请求的原因为网络拥堵时，网络侧设备12向终端10发送用于告知用户网络侧拥堵的呼叫失败反馈信息。在一些实施例中，同时保持该呼叫请求，进而在网络不拥堵时再及时地建立终端10和终端11之间的通话连接，以提高终端10成功拨打电话的概率。
请参见图2所示的另一种应用场景示意图，该应用场景中包括主叫终端20、至少一个被叫终端22和网络侧设备21，其中，在一些实施例中，主叫终端20和被叫终端22是手机，或是智能手表、固定电话等具有通话功能的终端，至少一个被叫终端22由一个或者多个服务器(也称作控制中心)进行管理，至少一个被叫终端22对应一个目标号码，例如，一些客服热线只有一个号码，但对应有多个固定电话，或者例如一些报警电话(例如110或119)也对应多个电话终端，用户在拨打客服热线或者报警电话后，控制中心将该呼叫请求分配到当前处于空闲状态的固定电话，从而建立通话连接。
在一些实施例中，网络侧设备21是由建立主叫终端20和被叫终端22之间的通话连接所需要的一个或多个设备组成的系统，例如图2所示，网络侧设备21包括基站和服务器， 或者还包括其它网络设备。基站在接收到主叫终端20发起的呼叫请求后，会将该呼叫请求发送给服务器处理，进而由服务器控制其对应的至少一个被叫终端22中处于空闲状态的被叫终端22(或者其它特定的被叫终端22)建立与主叫终端20之间的通话连接。其中，网络侧设备21也称为网络侧或呼叫控制中心。
图2中的网络侧设备21的实施与图1中的网络侧设备12的实施是类似的，对于网络侧设备21的理解请参照前述的网络侧设备12的实施部分的描述，此处就不再重复说明了。
在图1或图2所示的应用场景中，网络侧拥堵是由于基站处待处理的呼叫请求数量较多而导致的，或者是由于管理被叫终端的服务器处待处理的呼叫请求数量较多而导致的，或者是由于服务器临时掉电或其它原因导致的。
为进一步说明本申请实施例提供的通话控制的方案，下面结合附图以及具体实施方式对此进行详细的说明。虽然本申请实施例提供了如下述实施例或附图所示的方法操作步骤，但基于常规或者无需创造性的劳动在所述方法中也能包括更多或者更少的操作步骤。在逻辑上不存在必要因果关系的步骤中，这些步骤的执行顺序不限于本申请实施例提供的执行顺序。所述方法在实际的处理过程中或者装置执行时，按照实施例或者附图所示的方法顺序执行或者并行执行(例如并行处理器或者多线程处理的应用环境)。
请参考图3，图3为本申请实施例提供的通话控制方法的流程图，在图3中是以第一终端为主叫终端、第二终端为被叫终端为例进行说明的。图3中的通话控制方法的流程描述如下。
步骤301：第一终端向网络侧发送用于请求与目标号码建立通话的呼叫请求，则网络侧能够接收到该呼叫请求。
本申请实施例中，请结合前面的图1和图2的应用场景进行理解。在一些实施例中，第一终端是如图1所示的终端10，或者是如图2所示的终端20，第一终端中安装有至少一张用户身份识别卡，用户身份识别卡对应一个号码；在一些实施例中，目标号码是与如图1中所示的终端11的号码，或者是如图2所示的对应有多个被叫终端的号码；所以，呼叫请求中携带有第一终端的号码和被呼叫的目标号码。在一些实施例中，网络侧是指如图1所示的网络侧设备12，或者如图2中所示的网络侧设备21，在本文中，网络侧也称为网络侧设备，即，本申请实施例中的网络侧和网络侧设备作相同理解。
步骤302：网络侧设备判断当前是否能够处理第一终端发起的对目标号码的呼叫请求，若是，则执行步骤303，若否，则执行步骤304。
步骤303：建立第一终端与目标号码之间的通话连接。
在本申请实施例中，当网络侧设备当前能够处理第一终端发起的对目标号码的呼叫请 求时，处理该呼叫请求，以建立第一终端和目标号码对应的终端，例如图2中的第二终端，之间的通话连接，在通话连接建立之后，则进入通话阶段。
步骤304：网络侧设备确定当前无法处理呼叫请求的原因。
在本申请实施例中，导致网络侧设备无法处理呼叫请求的原因可能存在多种，如，是如前文所述的网络侧设备当前待处理的呼叫请求数量超过了网络侧设备能够处理的呼叫请求总数量，例如网络侧设备中的基站处待处理的呼叫请求超过负荷量；或者是如图2中所示的网络侧设备中的服务器当前待处理呼叫请求数量超过负荷量；或者是如图2中所示的网络侧设备中的基站和服务器当前待处理的呼叫请求数量都超过了负荷量；又或者是网络侧设备中的某一设备发生掉电情况，例如，如图2所示的服务器发生掉电状况，致使服务器未接收到或未及时处理基站发送的第一终端发起的对目标号码的呼叫请求。还或者是网络侧设备中某一处信号传输线老化断裂等等。
在一些实施例中，将前文所述的网络侧设备当前待处理的呼叫请求数量超过了网络侧设备能够处理的呼叫请求总数量的情况都看作是网络拥堵状态，例如，假设网络侧设备中的基站能够处理的呼叫请求数量为300，第一终端发起的对目标号码的呼叫请求为基站接收到的第301条呼叫请求，则确定当前网络侧设备处于网络拥堵状态，需要等待。在一些实施例中，将网络侧设备处理的呼叫请求数量超负荷之外的造成无法处理呼叫请求的原因统称为网络异常状态。
其中，网络拥堵状态是指网络侧设备能够接收到第一终端发起对目标号码的呼叫请求，只是当前等待处理的呼叫请求较多，需要等待一段时间后才能处理第一终端发起的呼叫请求，也就是说，在网络拥堵状态下，第一终端、网络侧设备以及目标号码对应的第二终端之间的通信链路异常、掉电和线路损坏等网络异常的问题，仅是因为待处理的呼叫请求量较多，等待一定时间后该呼叫请求就能够被处理，所以，为了提示第一终端的用户其发起的呼叫请求是能够被处理的，有必要将无法处理呼叫请求的原因为网络拥堵状态告知用户，以安抚处于紧急状态下产生的恐慌、焦虑的心理。而前述的网络异常状态则是指第一终端、网络侧设备以及第二终端之间的通信链路出现问题、或者是掉电、线路损坏等问题，造成网络侧设备不能接收到第一终端发起的呼叫请求，或是第一终端因网络信号差未发送出呼叫请求。
步骤305：若网络侧设备确定出当前无法处理所述呼叫请求的原因为网络拥堵，则获得呼叫失败反馈信息。
在本申请实施例中，呼叫失败反馈信息用于指示网络侧设备当前处于网络拥堵状态，需要等待处理呼叫请求。其中，在一些实施方式中，呼叫失败反馈信息是网络侧设备预先 设置的预定信息，当发生网络拥堵时则能够直接获得；或者是根据确定的网络拥堵状态临时生成的信息。
在一些实施例中，呼叫失败反馈信息是短信文本，或者是一段语音，若呼叫失败反馈信息是一段语音，例如，呼叫失败反馈信息是“当前待处理呼叫请求多，请耐心等待”这样的语音。当然，为了避免时间太长影响网络侧设备对呼叫请求的处理，应当呼叫失败反馈信息中语音的时长控制在合理的时间范围内。
步骤306：网络侧设备向第一终端发送呼叫失败反馈信息，相应的，第一终端能够接收到网络侧设备发送的该呼叫失败反馈信息。
在本申请实施例中，当确定出当前无法处理第一终端发送的呼叫请求的原因是因为网络堵塞时，则向第一终端发送呼叫失败反馈信息，该呼叫失败反馈信息用于提示用户当前网络侧设备处理网络拥堵状态，无法及时处理第一终端发送的呼叫请求，避免用户因不知晓呼叫失败的原而产生恐慌或焦虑的心情，所以能够安抚用户的心情，提升了用户体验感，同时还避免用户在焦急或恐慌状态下做出不适当的行为造成的人身或财产损失。
在一些实施例中，呼叫失败反馈信息中还用于指示是否继续等待建立通话连接，也就是说，在通过呼叫失败反馈信息对用户进行网络拥堵的有效提示的同时，还能够通过呼叫失败反馈信息告知使用用户继续等待，而不直接挂断电话，即保持用户的呼叫请求，以在网络侧能正常处理呼叫请求时就及时地建立与目标号码之间的通话连接，进而提高呼叫的成功率和呼叫效率，便于在一次呼叫失败后能够持续的呼叫。
在一些实施例中，呼叫失败反馈信息中包括网络侧设备结束网络拥堵状态所需的最短时长，或者不包括该最短时长。当呼叫失败反馈信息中包括该最短时长时，网络侧设备在向第一终端发送呼叫失败反馈信息之前，确定解决当前网络拥堵状态并能够处理第一终端发送的呼叫请求所需的最短时长，即网络侧设备结束网络拥堵状态所需的最短时长，本申请实施例中将该最短时长称为第三等待时长。进而用户能够根据包括第三等待时长的呼叫失败反馈消息，知晓呼叫请求至少还需要等待多长时间才能被处理，以避免用户因不知晓还需等待多长时间而产生焦虑或恐慌的心理，并方便用户根据需要等待的时长做出相应的决定。
步骤307：保持呼叫请求。
在一些实施方式中，步骤307与步骤306同时执行，即网络在向第一终端发送呼叫失败反馈消息时就保持该呼叫请求；或者在步骤306之前执行，即先保持该呼叫请求再向第一终端发送呼叫失败反馈消息；又或者在步骤306之后执行，即，先向第一终端发送呼叫失败反馈消息再保持呼叫请求，本申请实施例中，对步骤307和步骤306的执行顺序不做 限制，后续以步骤307在步骤306之后执行为例进行举例说明。
在本申请实施例中，当网络侧设备确定出当前无法处理第一终端发起的对目标号码的呼叫请求时，并不会立即终止该呼叫请求，即不会挂断用户通过第一终端拨打的电话，而是保持该呼叫请求，从而能够避免在终止呼叫请求后，需要第一终端重新发送起对目标号码的呼叫请求，所以能够节约呼叫时间，提高呼叫效率。
步骤308：第一终端在接收的呼叫失败反馈信息后，检测针对该第一终端的第一操作，并根据该第一操作确定指示等待信息。
其中，指示等待信息用于指示所述第一终端能够等待建立通话连接。
在本申请实施例中，第一终端在接收到呼叫失败反馈信息后，第一终端的用户能够根据该呼叫失败反馈信息的内容进行第一操作，从而能够根据第一操作确定指示等待信息。在一些实施方式中，第一操作通过点击操作或按键操作获取，或者通过语音方式获取，又或者通过其它操作方式获取。
例如，假设第一操作为按数字键的操作时，表示第一终端需要继续等待建立通话连接；又假设第一操作为按“*”号键的操作时，表示第一终端主动请求挂断电话。
在本申请实施例中，指示等待信息仅指示第一终端需要等待建立通话连接，不限制等待建立通话连接的时长，或者同时指示第一终端能够等待建立通话连接以及对应能够等待的时长，例如称作第一等待时长，第一等待时长为第一终端能够等待的与第二终端建立通话连接的最长时长。
在一些实施方式中，第一等待时长是在呼叫失败反馈信息中未指示有第三等待时长时，用户通过第一操作自行设置自己愿意等待的时长，例如设置第一操作为按数字键“1”时，表示第一终端需要等待8s，那么第一终端在检测到按数字键“1”的第一操作时，则确定指示等待信息指示的等待时长为8s。再如，第一操作也为依次按压数字键“1”和“2”的操作，来表示第一终端需要等待12s，那么第一终端在检测到迅速按压数字键“1”和“2”的操作时，则确定指示等待信息中指示等待时长为12s。
在一些实施例中，在呼叫失败反馈信息中指示有第三等待时长，即网络侧设备结束网络拥堵最短时长时，则通过第一操作直接将第一等待时长确定为与第三等待时长相同的时长。例如，假设呼叫失败反馈信息中指示的第三等待时长为10s，则直接将第一操作对应的第一等待时长确定为10s。
当然，在一些实施方式中，在呼叫失败反馈信息中指示有第三等待时长，用户通过第一操作自行设置第一等待时长，不受第三等待时长的限制。例如，假设呼叫失败反馈信息中指示的第三等待时长为10s，用户通过第一操作设置小于、等于或者大于10s的任何时 长。一般来说，在呼叫失败反馈信息中明确指示了网络侧最快能够结束拥堵状态的第三等待时长时，为了确保呼叫请求在用户设置的第一等待时长内能够被处理，用户对应设置的第一等待时长一般大于或者等于第三等待时长。
步骤309：第一终端向网络侧设备发送指示等待信息，相应的，网络侧设备能够接收第一终端基于呼叫失败反馈信息发送的指示等待信息。
本申请实施例中，第一终端在根据用户的第一操作确定出指示等待信息后，向网络侧设备发送确定出的指示等待信息，进而网络侧设备能够接收到第一终端发送的指示等待信息，以根据该指示等待信息明确用户当前能够继续等待，所以继续保持呼叫请求而不挂断电话。
步骤310：网络侧设备根据接收到的指示等待信息，确定能够处理该呼叫请求的时机，并该时机时处理第一终端发起的对目标号码的呼叫请求，以建立第一终端与第二终端之间的通话连接。
在一些实施例中，如前文所述，指示等待信息用于指示第一终端能够等待建立通话连接，那么，网络侧设备在接收到该指示等待信息后，网络侧设备则会等待能够处理该呼叫请求的时间，一旦确定能够处理，则及时地处理该呼叫请求时，以尽快地建立第一终端与第二终端之间的通话连接。
在另一些实施例中，如前文所述，指示等待信息中并不指示第一终端等待建立通话连接的时长，即不设置等待的时间，只要网络侧设备结束拥堵就能够及时建立第一终端与第二终端之间的通话连接。也就是说，不需要考虑等待建立通话的时间，只需在网络侧设备结束拥堵时建立第一终端与目标号码对应的第二终端之间的通话连接即可。
在本申请实施例中，若指示等待信息中指示了用户设置的第一终端等待建立通话的时长为第一等待时长，那么网络侧设备在从接收到该指示等待信息时开始到达第一等待时长内，若确定出网络侧能够处理所述呼叫请求，则根据该呼叫请求建立第一终端与第二终端之间的通话连接。
在一些实施例中，在网络侧设备在从接收到该指示等待信息时开始到达第一等待时长后，网络侧设备还能够确定其是否处于拥堵状态，若仍确定该网络侧设备处于拥堵状态，即表明在用户指定的时间内还是无法处理第一终端发起的呼叫请求，此时则终止该呼叫请求，以节约用户时间。
在一些实施例中，在本申请实施例中，网络侧设备在从接收到该指示等待信息时开始到达第一等待时长后，且判断其是否处于拥堵状态之前，网络侧设备还能够确定结束网络拥堵状态所需的第二等待时长，其中，为了确保网络侧设备在等待第一等待时长内，能够 处理第一终端发起的呼叫请求，建立第一终端与目标号码对应的第二终端之间的通话连接，以提高呼叫效率，在一些实施方式中，第一等待时长大于或等于第二等待时长。例如，第二等待时长为10s，则第一等待时长则为12s。
当然，由于第一等待时长能够由第一终端的用户自行设置，所以可能存在第一等待时长小于第二等待时长的情况，也就是说，在到达设置的等待建立通话的时间后，若网络侧设备仍处于拥堵状态，无法处理第一终端发起的呼叫请求，从而也可能存在用户因不知道呼叫失败的原因而产生恐慌和焦虑的情况。所以，为了避免这种情况的出现，在一些实施方式中，在确定出第一等待时长小于第二等待时长时，网络侧设备发送等待不足提示信息，其中，等待不足提示信息用于指示网络侧设备在第一等待时长内无法处理所述呼叫请求，这样，通过等待不足提示信息能够明确告知用户在其设置的等待时长内仍旧无法处理其发起的呼叫请求，以进一步地对用户进行有效提示。
在一些实施例中，网络侧设备在向所述第一终端发送等待不足提示信息之后，还能够确定目标号码是否是预设的紧急号码，例如预设的紧急号码是110、119等报警电话或者120等急救电话，若目标号码是预设的紧急号码，即表明用户当前所处情形是比较危急的，则继续保持第一终端发起的呼叫请求，并且选择再次向第一终端发送呼叫失败反馈信息，以再次告知第一终端的用户呼叫失败的原因，这样能够尽量多次安抚处于危急情形的用户，以尽量降低用户的交焦虑恐慌情绪，以避免因用户在紧急状况下因无法打通电话而做出不适当的行为，或者遭受不必要的人身、财产损失；若不是预设的紧急号码，则终止该呼叫请求，这样能够避免用户浪费等待时间，以便用户及时选择其他处理方式处理当前紧急情况。
在一些实施例中，在一种可能的实施方式中，由于第三等待时长是根据网络侧结束网络拥堵状态，即根据处理完在第一终端发起的呼叫请求之前的其它等待处理的呼叫请求所需的时间确定的，根据网络的情况，可能会出现确定出的处理时间与实际所需的处理时间不相同的情况，所以，在一些实施方式中，将网络侧设备从发送呼叫失败反馈信息开始到实际开始处理呼叫请求之间的实际时长称为第四等待时长。其中，第三等待时长可能与第四等待时长相同，也可能不同，即第四等待时长可能大于第三等待时长，也可能小于或等于第三等待时长。一般第三等待时长和第四等待时长的差值都不会太大，保持在一个预定差值范围内。那么，当呼叫失败反馈信息中指示有第三等待时长，网络侧设备可能在从发送呼叫失败反馈信息开始到达第四等待时长时，建立第一终端与目标号码对应的第二终端之间的通话连接。
例如，第三等待时长为15s，若实际上网络侧设备在第12s时已经处理完除第一终端发 起的呼叫请求之外的呼叫请求，即第四等待时长为12s，所以，网络侧设备实际上是在等待12s后就开始处理第一终端发起的呼叫请求，建立第一终端与第二终端之间的通话连接。
步骤311：第一终端根据接收的呼叫失败反馈信息，检测第二操作，并根据第二操作确定终止呼叫请求的终止请求信息。
在本申请实施例中，当第一终端接收到网络侧设备发送呼叫失败反馈信息之后，第一终端的用户通过第二操作选择终止该呼叫请求，进而第一终端能够根据检测到的第二操作生成确定终止呼叫请求的终止请求信息。其中，在一些实施方式中，第二操作是用户基于呼叫失败反馈信息，按下第一终端中对应的功能键的按键操作，或者是用户发出的语音。
也就是说，用户在根据呼叫失败反馈信息的提示，知晓当前无法打通电话的具体原因之后，根据自己当前的实际情况选择主动的挂断电话，以便于进行其它操作或者采用其他的处理方式，以满足不同用户的差异化需求。
步骤312：第一终端向网络侧设备发送终止请求信息，则，网络侧设备能够接收到第一终端发送的终止请求信息。
步骤313：网络侧设备根据终止请求信息，终止呼叫请求。
在本申请实施例中，当网络侧设备接收到终止请求信息后，能够根据该终止请求信息，终止第一终端发起的对目标号码对应的第二终端的呼叫请求，从而第一终端能够发起对其他号码的呼叫请求，避免因等待与目标号码对应的终端建立通话连接造成的时间和电能的浪费。
所以通过上述方法，在本申请一些实施例中，在接收到第一终端向目标号码发起的呼叫请求后，网络侧根据自身网络情况确定当前是否能够处理该呼叫请求，在不能处理该呼叫请求时，网络侧并不立即终止该呼叫请求，而是确定无法处理该呼叫请求的原因，并在确定出无法处理该呼叫请求的原因是网络拥堵时，向第一终端发送呼叫失败反馈信息，提示第一终端的用户呼叫请求失败的原因，因此能够安抚处于恐慌或焦急状态的用户，避免用户因不知道呼叫失败做出过激行为，提升用户体验感。
在一些实施例中，在向第一终端发送呼叫失败反馈消息的同时，网络侧继续保持呼叫请求，而并不是如相关技术中一样直接挂断电话，进而在网络不再拥堵而能够处理该呼叫请求的时候，且满足预定触发条件(例如接收到第一终端发送的特定信息)时，就能够及时地建立第一终端与目标号码对应的终端(例如称作第二终端)之间的通话连接，以即使地响应第一终端的呼叫请求，尽快地建立第一终端与第二终端之间的通话，以尽量提高呼叫的效率，以及提高呼叫成功的概率。
基于同一发明构思，本申请实施例中提供了一种通话控制装置，该通话控制装置是硬 件结构、软件模块、或硬件结构加软件模块。在一些实施方式中，该通话控制装置由芯片系统实现，芯片系统由芯片构成，或者包含芯片和其他分立器件。如图4a所示，该通话控制装置包括第一接收单元401、第一确定单元402和反馈单元403。其中：
第一接收单元401，用于接收第一终端发起的对目标号码的呼叫请求；
第一确定单元402，用于若当前无法处理呼叫请求，确定当前无法处呼叫请求的原因；
反馈单元403，用于在当前无法处理呼叫请求的原因为网络侧拥堵时，向第一终端发送呼叫失败反馈信息，其中，呼叫失败反馈信息用于指示网络侧当前处于网络拥堵状态。
在一些实施例中，呼叫失败反馈信息还用于指示是否继续等待建立通话连接，请参见图4b所示，该通话控制装置还包括：
保持单元404，用于保持呼叫请求；
第二接收单元405，用于接收第一终端基于呼叫失败反馈信息发送的指示等待信息，其中，指示等待信息用于指示第一终端能够等待建立通话连接；
通话建立单元406，用于根据等待指示信息，在网络侧能够处理呼叫请求时，建立第一终端与目标号码对应的第二终端之间的通话连接。
在一些实施例中，指示等待信息还用于指示用户设置的第一等待时长，第一等待时长为第一终端能够等待的与第二终端建立通话连接的最长时长；通话建立单元406，用于：
在从接收指示等待信息时开始的第一等待时长内，若确定网络侧能够处理呼叫请求，则根据呼叫请求建立第一终端与第二终端之间的通话连接。
在一些实施例中，指示等待信息还用于指示用户设置的第一等待时长，第一等待时长为第一终端能够等待的与第二终端建立通话连接的最长时长；如图4b所示，该通话控制装置还包括终止请求单元407，用于：
在从接收指示等待信息时开始达到第一等待时长后，确定网络侧是否仍处于网络拥堵状态；
若仍处于网络拥堵状态，则终止呼叫请求。
在一些实施例中，如图4b所示，该通话控制装置还包括第二确定单元408，用于：
在终止请求单元407确定网络侧是否仍然处于拥堵状态之前，在接收指示等待信息时，确定网络侧结束网络拥堵状态所需要的第二等待时长；
确定第一等待时长大于或等于第二等待时长。
在一些实施例中，第二确定单元408还用于：
若确定第一等待时长小于第二等待时长，则向第一终端发送等待不足提示信息，其中，等待不足提示信息用于指示网络侧在第一等待时长内无法处理呼叫请求。
在一些实施例中，如图4b所示，该通话控制装置还包括第三确定单元409，用于：
在第二确定单元408向第一终端发送等待不足提示信息之后，确定目标号码是否是预设的紧急号码；
若是预设的紧急号码，则继续保持呼叫请求；
若不是预设的紧急号码，则终止呼叫请求。
在一些实施例中，呼叫失败反馈信息还用于指示第三等待时长，第三等待时长为网络侧结束网络拥堵状态的最短时长，建立通话单元406还用于：
在第二确定单元向第一终端发送等待不足提示信息之后，在从发送呼叫失败反馈信息时开始达到第四等待时长时，建立第一终端与第二终端之间的通话连接；其中，第四等待时长为从发送呼叫失败反馈信息开始到实际处理呼叫请求之间的时长。
在一些实施例中，终止请求单元407还用于：
在第二确定单元408向第一终端发送呼叫失败反馈信息之后，接收第一终端发送的用于请求终止呼叫请求的终止请求信息；
根据终止呼叫请求信息终止呼叫请求。
基于同一发明构思，本申请实施例中提供了一种通话控制装置，该通话控制装置是硬件结构、软件模块、或硬件结构加软件模块。在一些实施方式中，该通话控制装置由芯片系统实现，芯片系统由芯片构成，或者包含芯片和其他分立器件。如图5所示，该通话控制装置包括发送单元501和接收单元502。其中：
发送单元501，用于向网络侧发送请求与目标号码建立通话的呼叫请求；
接收单元502，用于接收网络侧发送的呼叫失败反馈信息，其中，呼叫失败反馈信息用于指示网络侧当前处于网络拥堵状态。
在一些实施例中，呼叫失败反馈信息还用于指示是否继续等待建立通话连接，发送单元501还用于：
在接收呼叫失败反馈信息之后，获得用户针对第一终端进行的第一操作；
根据第一操作，确定指示等待信息；其中，指示等待信息用于指示第一终端能够等待建立通话连接；
向网络侧发送指示等待信息。
在一些实施例中，指示等待信息还用于指示用户设置的第一等待时长，其中，第一等待时长为第一终端能够等待的与目标号码对应的第二终端建立通话连接的最长时长。
在一些实施例中，发送单元501还用于：
在接收网络侧发送的呼叫失败反馈信息之后，获得用户针对第一终端进行的第二操作；
根据第二操作，生成终止请求信息，其中，终止呼叫请求信息用于请求终止呼叫请求；
向网络侧设备发送终止请求信息。
前述通话控制方法的实施例涉及的各步骤的所有相关内容均能够援引到本申请实施例中的通话控制装置所对应的功能模块的功能描述，在此不再赘述。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时也有另外的划分方式，另外，在一些实施方式中，在本申请各个实施例中的各功能模块集成在一个处理器中，或者单独物理存在，又或者两个或两个以上模块集成在一个模块中。在一些实施方式中，上述集成的模块采用硬件的形式实现，或者采用软件功能模块的形式实现。
基于同一发明构思，本申请实施例还提供一种通话控制设备，该通话控制设备例如是手机、智能手表等终端设备，例如是图1所示的终端10或终端11，或如图2所示的主叫终端20。如图6所示，该通话控制设备包括至少一个处理器601，以及与至少一个处理器连接的存储器602，本申请实施例中不限定处理器601和存储器602之间的具体连接介质，图6中是以处理器601和存储器602之间通过总线600连接为例，总线600在图6中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。在一些实施方式中，总线600分为地址总线、数据总线、控制总线等，为便于表示，图6中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
基于同一发明构思，本申请实施例还提供一种通话控制设备，该通话控制设备例如是基站、服务器等网络设备，例如是图1所示的网络侧设备12，或图2所示的网络侧设备21。如图7所示，该通话控制设备包括至少一个处理器701，以及与至少一个处理器连接的存储器702，本申请实施例中不限定处理器701和存储器702之间的具体连接介质，图7中是以处理器701和存储器702之间通过总线700连接为例，总线700在图7中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。在一些实施方式中，总线700分为地址总线、数据总线、控制总线等，为便于表示，图7中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
其中，图6中的存储器602和图7中所示的存储器702均存储有能够被至少一个处理器执行的指令，至少一个处理器通过执行存储器602或存储器702存储的指令，能够执行前述的通话控制方法中所包括的步骤。
处理器601和处理器701均是通话控制设备的控制中心，能够利用各种接口和线路连接整个通话控制设备的各个部分，通过运行或执行存储在存储器602和存储器702内的指令以及调用存储在存储器602和存储器702内的数据，通话控制设备的各种功能和处理数 据，从而对通话控制设备进行整体监控。在一些实施例中，处理器601和处理器701均包括一个或多个处理单元，处理器601和处理器701均集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序等，调制解调处理器主要处理无线通信。能够理解的是，上述调制解调处理器也能够选择不集成到处理器601和处理器701中。在一些实施例中，处理器601和存储器602、处理器701存储器702在同一芯片上实现，在一些实施例中，它们在独立的芯片上分别实现。
在一些实施方式中，处理器601和处理器701是通用处理器，例如中央处理器(CPU)、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，能够实现或者执行本申请实施例中公开的各方法、步骤及逻辑框图。通用处理器是微处理器或者任何常规的处理器等。结合本申请实施例所公开的通话控制方法的步骤直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
存储器602和存储器702作为一种非易失性计算机可读存储介质，能够用于存储非易失性软件程序、非易失性计算机可执行程序以及模块。在一些实施方式中，存储器602和存储器702均包括至少一种类型的存储介质，例如包括闪存、硬盘、多媒体卡、卡型存储器、随机访问存储器(Random Access Memory，RAM)、静态随机访问存储器(Static Random Access Memory，SRAM)、可编程只读存储器(Programmable Read Only Memory，PROM)、只读存储器(Read Only Memory，ROM)、带电可擦除可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、磁性存储器、磁盘、光盘等等。存储器602和存储器702是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。在一些实施方式中，存储器602和存储器702是电路或者其它任意能够实现存储功能的装置，用于存储程序指令，或数据，或程序指令和数据。
通过对处理器601和处理器701进行设计编程，能够将前述实施例中介绍的通话控制方法所对应的代码固化到芯片内，从而使芯片在运行时能够执行前述的通话控制方法的步骤，如何对处理器601和处理器701进行设计编程为本领域技术人员所公知的技术，这里不再赘述。
基于同一发明构思，本申请实施例中提供了一种存储介质，该存储介质存储有计算机可执行指令，当计算机可执行指令用于当计算机指令在计算机上运行时，使得计算机执行如前述的通话控制方法的步骤。
本领域内的技术人员应明白，本申请的实施例能够被提供为方法、系统、或计算机程 序产品。因此，本申请采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解能够由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
或者将这些计算机程序指令存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也能够装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员能够对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (17)

  1. 一种通话控制方法，其特征在于，包括：
    接收第一终端发起的对目标号码的呼叫请求；
    若当前无法处理所述呼叫请求，确定当前无法处理所述呼叫请求的原因；
    在当前无法处理所述呼叫请求的原因为网络侧拥堵时，向所述第一终端发送呼叫失败反馈信息，其中，所述呼叫失败反馈信息用于指示所述网络侧当前处于网络拥堵状态。
  2. 如权利要求1所述的通话控制方法，其特征在于，所述呼叫失败反馈信息还用于指示是否继续等待建立通话连接，所述方法还包括：
    保持所述呼叫请求；
    接收所述第一终端基于所述呼叫失败反馈信息发送的指示等待信息，其中，所述指示等待信息用于指示所述第一终端能够等待建立通话连接；
    根据所述等待指示信息，在所述网络侧能够处理所述呼叫请求时，建立所述第一终端与所述目标号码对应的第二终端之间的通话连接。
  3. 如权利要求2所述的通话控制方法，其特征在于，所述指示等待信息还用于指示用户设置的第一等待时长，所述第一等待时长为所述第一终端能够等待的与所述第二终端建立通话连接的最长时长；
    则，在从接收所述指示等待信息时开始的所述第一等待时长内，若确定所述网络侧能够处理所述呼叫请求，则根据所述呼叫请求建立所述第一终端与所述第二终端之间的通话连接。
  4. 如权利要求2所述的通话控制方法，其特征在于，所述指示等待信息还用于指示用户设置的第一等待时长，所述第一等待时长为所述第一终端能够等待的与所述第二终端建立通话连接的最长时长；则在保持所述呼叫请求之后，所述方法还包括：
    在从接收所述指示等待信息时开始达到所述第一等待时长后，确定所述网络侧是否仍处于网络拥堵状态；
    若仍处于网络拥堵状态，则终止所述呼叫请求。
  5. 如权利要求4所述的通话控制方法，其特征在于，在确定所述网络侧是否仍然处于拥堵状态之前，所述方法还包括：
    在接收所述指示等待信息时，确定所述网络侧结束网络拥堵状态所需要的第二等待时长；
    确定所述第一等待时长大于或等于所述第二等待时长。
  6. 如权利要求5所述的通话控制方法，其特征在于，所述方法还包括：
    若确定所述第一等待时长小于所述第二等待时长，则向所述第一终端发送等待不足提示信息，其中，所述等待不足提示信息用于指示所述网络侧在所述第一等待时长内无法处理所述呼叫请求。
  7. 如权利要求6所述的通话控制方法，其特征在于，在向所述第一终端发送等待不足提示信息之后，所述方法还包括：
    确定所述目标号码是否是预设的紧急号码；
    若是所述预设的紧急号码，则继续保持所述呼叫请求；
    若不是所述预设的紧急号码，则终止所述呼叫请求。
  8. 如权利要求2所述的通话控制方法，其特征在于，所述呼叫失败反馈信息还用于指示第三等待时长，所述第三等待时长为所述网络侧结束网络拥堵状态的最短时长，则在保持所述呼叫请求之后，所述方法还包括：
    在从发送所述呼叫失败反馈信息时开始达到第四等待时长时，建立所述第一终端与所述第二终端之间的通话连接；其中，所述第四等待时长为从发送所述呼叫失败反馈信息开始到实际处理所述呼叫请求之间的时长。
  9. 如权利要求1所述的通话控制方法，其特征在于，在向所述第一终端发送呼叫失败反馈信息之后，所述方法还包括：
    接收所述第一终端发送的用于请求终止所述呼叫请求的终止请求信息；
    根据所述终止呼叫请求信息，终止所述呼叫请求。
  10. 一种通话控制方法，其特征在于，包括：
    向网络侧发送请求与目标号码建立通话的呼叫请求；
    接收所述网络侧发送的呼叫失败反馈信息，其中，所述呼叫失败反馈信息用于指示所述网络侧当前处于网络拥堵状态。
  11. 如权利要求10所述的通话控制方法，其特征在于，所述呼叫失败反馈信息还用于指示是否继续等待建立通话连接，在接收所述呼叫失败反馈信息之后，所述方法还包括：
    获得用户针对所述第一终端进行的第一操作；
    根据所述第一操作，确定指示等待信息；其中，所述指示等待信息用于指示所述第一终端能够等待建立通话连接；
    向所述网络侧发送所述指示等待信息。
  12. 如权利要求11所述的通话控制方法，其特征在于，所述指示等待信息还用于指示用户设置的第一等待时长，其中，所述第一等待时长为所述第一终端能够等待的与所述目标号码对应的第二终端建立通话连接的最长时长。
  13. 如权利要求10所述的通话控制方法，其特征在于，在接收所述网络侧发送的呼叫失败反馈信息之后，所述方法还包括：
    获得用户针对所述第一终端进行的第二操作；
    根据所述第二操作，生成终止请求信息，其中，所述终止呼叫请求信息用于请求终止所述呼叫请求；
    向所述网络侧发送所述终止请求信息。
  14. 一种通话控制装置，其特征在于，包括：
    第一接收单元，用于接收第一终端发起的对目标号码的呼叫请求；
    第一确定单元，用于若当前无法处理所述呼叫请求，确定当前无法处理所述呼叫请求的原因；
    反馈单元，用于在当前无法处理所述呼叫请求的原因为网络侧拥堵时，向所述第一终端发送呼叫失败反馈信息，其中，所述呼叫失败反馈信息用于指示所述网络侧当前处于网络拥堵状态。
  15. 一种通话控制装置，其特征在于，包括：
    发送单元，用于向网络侧发送请求与目标号码建立通话的呼叫请求；
    接收单元，用于接收所述网络侧发送的呼叫失败反馈信息，其中，所述呼叫失败反馈信息用于指示所述网络侧当前处于拥堵状态。
  16. 一种通话控制设备，其特征在于，所述设备包括：
    存储器，用于存储程序指令；
    处理器，用于调用所述存储器中存储的程序指令，按照获得的程序指令执行权利要求1-9或权利要求10-13中任一方法包括的步骤。
  17. 一种存储介质，其特征在于，所述存储介质存储有计算机指令，当所述计算机指令在计算机上运行时，使得计算机执行如权利要求1-9或权利要求10-13中任一方法的步骤。
PCT/CN2019/128929 2019-05-20 2019-12-27 通话控制方法、装置、设备及存储介质 WO2020233122A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910417175.5A CN110225559B (zh) 2019-05-20 2019-05-20 一种通话控制方法、装置、设备及存储介质
CN201910417175.5 2019-05-20

Publications (1)

Publication Number Publication Date
WO2020233122A1 true WO2020233122A1 (zh) 2020-11-26

Family

ID=67821361

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/128929 WO2020233122A1 (zh) 2019-05-20 2019-12-27 通话控制方法、装置、设备及存储介质

Country Status (2)

Country Link
CN (1) CN110225559B (zh)
WO (1) WO2020233122A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112777436A (zh) * 2021-01-28 2021-05-11 上海有个机器人有限公司 机器人呼梯方法、装置、终端及存储介质
CN113422873A (zh) * 2021-06-25 2021-09-21 北京小米移动软件有限公司 通话模式切换的提示方法、装置、存储介质及电子设备
WO2024098329A1 (zh) * 2022-11-10 2024-05-16 Oppo广东移动通信有限公司 通信方法和设备

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110225559B (zh) * 2019-05-20 2022-05-03 珠海格力电器股份有限公司 一种通话控制方法、装置、设备及存储介质
CN112040077B (zh) * 2020-08-17 2021-10-19 Oppo（重庆）智能科技有限公司 通信控制方法、装置、移动终端及计算机存储介质
CN112601185A (zh) * 2020-12-10 2021-04-02 海能达通信股份有限公司 呼叫业务处理方法、装置、多模对讲机及存储介质
CN114006974B (zh) * 2021-10-25 2023-04-07 杭州逗酷软件科技有限公司 信息处理方法、装置、终端设备及计算机存储介质

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6826397B1 (en) * 1999-08-20 2004-11-30 Ericsson Inc System and method to notify subscribers of call terminating treatment
CN1798447A (zh) * 2004-12-28 2006-07-05 乐金电子(中国)研究开发中心有限公司 移动通信系统的呼叫连接失败提示方法
CN1878288A (zh) * 2005-06-10 2006-12-13 中国移动通信集团公司 基于移动通信网络的可视电话呼叫失败的处理方法
CN101771977A (zh) * 2008-12-30 2010-07-07 中兴通讯股份有限公司 呼叫失败原因的反馈方法及装置
CN101902712A (zh) * 2010-06-23 2010-12-01 中兴通讯股份有限公司 呼叫失败的处理方法及装置
CN102771107A (zh) * 2010-02-22 2012-11-07 阿尔卡特朗讯 呼叫尝试通知
CN104080065A (zh) * 2013-03-25 2014-10-01 中兴通讯股份有限公司 一种呼叫自动重拨的方法及装置
CN110225559A (zh) * 2019-05-20 2019-09-10 珠海格力电器股份有限公司 一种通话控制方法、装置、设备及存储介质

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5421969B2 (ja) * 2011-10-03 2014-02-19 株式会社Ｎｔｔドコモ 移動通信方法、移動管理ノード、パケット交換機及び移動局
CN103856596B (zh) * 2012-11-28 2016-05-25 腾讯科技（深圳）有限公司 一种通话方法、装置及终端
EP3432616B1 (en) * 2016-05-27 2021-02-03 Huawei Technologies Co., Ltd. Call processing method, call server, base station, and call system

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6826397B1 (en) * 1999-08-20 2004-11-30 Ericsson Inc System and method to notify subscribers of call terminating treatment
CN1798447A (zh) * 2004-12-28 2006-07-05 乐金电子(中国)研究开发中心有限公司 移动通信系统的呼叫连接失败提示方法
CN1878288A (zh) * 2005-06-10 2006-12-13 中国移动通信集团公司 基于移动通信网络的可视电话呼叫失败的处理方法
CN101771977A (zh) * 2008-12-30 2010-07-07 中兴通讯股份有限公司 呼叫失败原因的反馈方法及装置
CN102771107A (zh) * 2010-02-22 2012-11-07 阿尔卡特朗讯 呼叫尝试通知
CN101902712A (zh) * 2010-06-23 2010-12-01 中兴通讯股份有限公司 呼叫失败的处理方法及装置
CN104080065A (zh) * 2013-03-25 2014-10-01 中兴通讯股份有限公司 一种呼叫自动重拨的方法及装置
CN110225559A (zh) * 2019-05-20 2019-09-10 珠海格力电器股份有限公司 一种通话控制方法、装置、设备及存储介质

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112777436A (zh) * 2021-01-28 2021-05-11 上海有个机器人有限公司 机器人呼梯方法、装置、终端及存储介质
CN113422873A (zh) * 2021-06-25 2021-09-21 北京小米移动软件有限公司 通话模式切换的提示方法、装置、存储介质及电子设备
WO2024098329A1 (zh) * 2022-11-10 2024-05-16 Oppo广东移动通信有限公司 通信方法和设备

Also Published As

Publication number Publication date
CN110225559B (zh) 2022-05-03
CN110225559A (zh) 2019-09-10

Similar Documents

Publication Publication Date Title
WO2020233122A1 (zh) 通话控制方法、装置、设备及存储介质
US11799786B2 (en) Device and method for disabling a WLAN hotspot based on data traffic value
CN111131058B (zh) 访问量控制方法和装置
US20160072943A1 (en) Call method of mobile terminal, mobile terminal control method, and related device
CN107995286B (zh) 基于dubbo平台的服务自动启停方法、服务器及存储介质
EP3209005B1 (en) Task processing device, intelligent apparatus, task processing method and baseband processor
CN112965823B (zh) 调用请求的控制方法、装置、电子设备和存储介质
WO2024007995A1 (zh) 网络故障恢复方法、装置、设备及存储介质
WO2022095961A1 (zh) 充电方法、充电装置和充电器
KR100926051B1 (ko) 통신 제한 중에 페이지에 대해 응답하는 시스템 및 방법
US20160255614A1 (en) Network Device, Terminal Device, and Voice Service Control Method
WO2021012506A1 (zh) 语音识别系统中的负载均衡实现方法、装置以及计算机设备
CN105933271A (zh) 一种基于加密机的数据处理方法及装置
CN110266895B (zh) 一种通话回拨方法、装置及设备
CN104506726A (zh) 用于终端的通信事件的处理方法、处理装置和终端
CN112543479A (zh) 上行数据传输的实现方法、装置及用户设备
CN113923801B (zh) 一种基站对ue资源释放方法、装置、设备及产品
CN114268929B (zh) 一种业务激活方法及相关设备
WO2021155859A1 (zh) 接入控制方法及设备
CN112995114B (zh) 一种VoLTE呼叫业务的处理方法及装置
CN114862500A (zh) 订单处理方法、装置、电子设备及存储介质
JP4504189B2 (ja) 無線デバイスのオープンデータチャネルを介してデータをピギーバックするためのシステム及び方法
US9866625B2 (en) Message transmission apparatus, message transmission method, and message transmission program
CN114641016A (zh) 繁忙指示的传输方法及装置
CN110121215B (zh) 5g终端的数据连接建立方法、装置及5g终端

Legal Events

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

Ref document number: 19929532

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19929532

Country of ref document: EP

Kind code of ref document: A1