IMS call problem determination method, apparatus and device, and readable storage medium

Abstract

The invention relates to the technical field of communication, in particular to an IMS call problem determination method and device, equipment and a computer readable storage medium. Under the condition that a calling terminal calls a called terminal, the method is executed by the called terminal, and the method comprises the following steps: determining whether the called terminal is in an idle state or not; under the condition that the called terminal is in the idle state, executing a problem checking operation; wherein the problem checking operation comprises the step of judging whether the called terminal successfully demodulates a paging wireless network identifier in a calling process; under the condition of successful demodulation, judging whether paging sent by a network side is matched with the called terminal or not; and if the call establishment fails and a preset condition is satisfied, a network side fault is prompted, and the preset condition comprises that all paging wireless network identifiers of the called terminal in a preset time period are successfully demodulated and the paging pagging at each time is not matched with the called terminal.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a method, device, equipment and computer-readable storage medium for determining an IMS call problem. Background Art

[0002] During the development of the terminal, testers need to go to different locations to test the terminal's IMS (IP Multimedia Subsystem) call function. When the called terminal fails to establish a call until the calling terminal automatically terminates the call, it can be considered that the IMS call establishment has failed.

[0003] When an IMS call fails to be established, the logs on the terminal AP (Application Processor) side and the BP (Baseband Processor) side can be captured and sent to the developer to analyze the cause of the problem.

[0004] However, in some cases, even if there is no problem with the called terminal itself, the failure of the network to send paging messages may also cause the IMS call to fail. Since testers cannot directly determine whether the IMS call failure is caused by the network, they may still capture the logs of the AP and BP sides and analyze them, which can neither solve the problem on the network side nor lead to a waste of resources. Summary of the invention

[0005] In order to overcome the problems existing in the related art, the present disclosure provides a method, apparatus, device and computer-readable storage medium for determining an IMS call problem, which can solve the above problems.

[0006] According to a first aspect of an embodiment of the present disclosure, a method for determining an IMS call problem is provided, which is executed by the called terminal when a calling terminal calls a called terminal, and the method includes:

[0007] Determining whether the called terminal is in an idle state;

[0008] When the called terminal is in the idle state, performing a problem checking operation; wherein the problem checking operation includes determining whether the called terminal successfully demodulates the paging wireless network identifier during the call process; and if the demodulation is successful, determining whether the paging sent by the network side matches the called terminal;

[0009] If the call establishment fails and the preset conditions are met, a network failure is prompted, wherein the preset conditions include that all paging wireless network identifiers of the called terminal within a preset time period are demodulated successfully and each paging does not match the called terminal.

[0010] According to a second aspect of an embodiment of the present disclosure, a device for determining an IMS call problem is provided. When a calling terminal calls a called terminal, the device is configured at the called terminal. The device includes:

[0011] a determining unit, configured to determine whether the called terminal is in an idle state;

[0012] The checking unit is configured to perform a problem checking operation when the called terminal is in the idle state; wherein the problem checking operation includes determining whether the called terminal successfully demodulates the paging wireless network identifier during the call process; and if the demodulation is successful, determining whether the paging sent by the network side matches the called terminal;

[0013] The prompt unit is configured to prompt a network side failure if the call establishment fails and the preset conditions are met, wherein the preset conditions include that all paging wireless network identifiers of the called terminal within a preset time period are demodulated successfully and each paging does not match the called terminal.

[0014] According to a third aspect of an embodiment of the present disclosure, there is provided an electronic device, including: a processor and a memory;

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

[0016] The processor is configured to execute the method for determining the IMS call problem as described in the first aspect by calling the computer program.

[0017] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the program is executed by a processor, the method for determining an IMS call problem as described in the first aspect is implemented.

[0018] The technical solution provided by the embodiments of the present disclosure may have the following beneficial effects:

[0019] The present disclosure can perform a problem check operation during the process of establishing a call when the called terminal is called, and based on the problem check operation, when the call establishment fails, if the preset conditions are met, it is prompted that the call establishment failure is caused by a network side failure. By checking the process of establishing a call, when there is no problem with the called terminal and the call establishment fails only due to network side reasons, the present disclosure can issue a prompt to avoid the tester from trying to capture the logs on the AP side and the BP side for further analysis, which can help the tester get a preliminary judgment on the call establishment failure, guide the tester's next operation, improve the efficiency of locating problems, and avoid unnecessary waste of resources.

[0020] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0022] Figure 1 The figure is a schematic flow chart of a method for determining an IMS call problem according to an exemplary embodiment of the present disclosure.

[0023] Figure 2 The figure is a schematic flow chart of a method for determining an IMS call problem according to an exemplary embodiment of the present disclosure.

[0024] Figure 3 The present invention is a block diagram of a device for determining an IMS call problem according to an exemplary embodiment of the present invention.

[0025] Figure 4 The present invention is a schematic block diagram of a device for determining an IMS call problem according to an exemplary embodiment of the present invention. DETAILED DESCRIPTION

[0026] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0027] The terms used in this disclosure are for the purpose of describing specific embodiments only and are not intended to limit the disclosure. The singular forms of "a", "said" and "the" used in this disclosure and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0028] It should be understood that although the terms first, second, third, etc. may be used in the present disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the present disclosure, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0029] Figure 1 The present invention is a schematic flow chart of a method for determining an IMS call problem according to an embodiment of the present invention. When a calling terminal calls a called terminal, the method for determining an IMS call problem can be executed by the called terminal. The method for determining an IMS call problem can be used to determine a problem that occurs during an IMS call establishment process of a terminal, and the terminal includes but is not limited to a mobile phone, a tablet computer, a wearable device, a sensor, an Internet of Things device, and other communication devices.

[0030] like Figure 1 As shown, the method for determining the IMS call problem includes:

[0031] In step S101, it is determined whether the called terminal is in an idle state;

[0032] In step S102, when the called terminal is in the idle state, a problem checking operation is performed; wherein the problem checking operation includes determining whether the called terminal successfully demodulates the paging wireless network identifier during the call process; and if the demodulation is successful, determining whether the paging sent by the network side matches the called terminal;

[0033] In step S103, if the call establishment fails and the preset conditions are met, a network failure is prompted, wherein the preset conditions include that all paging wireless network identifiers of the called terminal within a preset time are demodulated successfully and each paging does not match the called terminal.

[0034] In some embodiments, the idle state refers to a state in which the terminal is not actively communicating or calling with the network.

[0035] In the idle state, the terminal is in a low power consumption state and network resources are relatively idle. When the terminal needs to communicate or make a call, the terminal will enter the connected state and establish a connection with the network for communication and data transmission.

[0036] In some embodiments, only when the called terminal is in an idle state, the network side needs to send paging to the terminal during the process of establishing a call.

[0037] Therefore, only in the idle state, the call establishment failure of the called terminal may occur due to network problems such as the paging sent by the network side not matching the terminal.

[0038] In some embodiments, when the called terminal is in an idle state, a problem checking operation is performed.

[0039] Through the problem check operation, it is possible to determine whether the called terminal has successfully established the call during the call process, and then determine whether the call establishment failure is caused by a problem with the called terminal or a problem on the network side based on whether the call establishment failure is successful.

[0040] In some embodiments, the calling process includes the calling terminal calling the called terminal until the call is successfully established or until the calling terminal terminates the call.

[0041] If the call cannot be established successfully before the calling terminal terminates the call, it indicates that the call establishment has failed.

[0042] In some embodiments, the determining whether the called terminal successfully demodulates the paging radio network temporary identity (P-RNTI) during the call process includes: obtaining a log of the called terminal on the BP side, and determining whether the P-RNTI is successfully demodulated based on the log.

[0043] This includes whether the P-RNTI in the physical downlink shared channel (PDSCH) is demodulated successfully.

[0044] The called terminal can obtain the log on the BP side and determine whether the demodulation is successful according to the identifier of the P-RNTI information type in the log.

[0045] In some embodiments, if the P-RNTI demodulation is successful, it indicates that there is no problem with the P-RNTI demodulation of the called terminal. If the P-RNTI demodulation fails, it indicates that there is a problem with the P-RNTI demodulation of the called terminal. Subsequently, it is necessary to obtain the log of the called terminal on the BP side to determine the specific cause of the problem.

[0046] In some embodiments, when P-RNTI demodulation is successful, determining whether the paging sent by the network side matches the called terminal includes: obtaining a log of the called terminal on the BP side, and determining whether the received paging matches the called terminal according to the log.

[0047] The called terminal can determine whether the received paging matches the called terminal through the paging-related identification information recorded in the BP side log.

[0048] If the paging matches the called terminal, it indicates that there is no problem on the network side that causes the failure of the call establishment of the called terminal. If the paging does not match the called terminal, the problem that causes the failure of the call establishment may occur on the network side.

[0049] In some embodiments, if the called terminal fails to establish a call, the problem check operation performed is used to determine whether the preset conditions are met to determine whether the call establishment failure is caused by a network side failure, and then, if the preset conditions are met, the tester is prompted with a network side failure.

[0050] Based on the prompt of the network side fault, the tester can determine that the reason for the failure to establish the call is caused by the network side rather than the called terminal. This can help the tester preliminarily determine the cause of the problem and reduce the tester's unnecessary analysis of the logs on the AP side and BP side, thereby avoiding waste of resources.

[0051] In some embodiments, the preset condition includes: all paging wireless network identifiers of the called terminal within a preset time period are demodulated successfully and each paging does not match the called terminal.

[0052] After the calling terminal calls the called terminal, the calling terminal may wait for the called terminal to establish a call within a preset time. If the call cannot be established within the preset time, it is determined that the called terminal has failed to establish the call.

[0053] It should be noted that within the preset duration of the call initiated by the calling terminal, the called terminal can attempt to establish a call more than once, and each attempt to establish a call requires re-demodulation of the P-RNTI and determination of whether the received paging matches the called terminal.

[0054] Within the preset time, if the called terminal successfully demodulates all P-RNTIs, but the paging sent by the network does not match the called terminal in each successful demodulation, it means that the failure to establish the call is caused by the network side that sent the paging. The called terminal does not need to be responsible for the failure to establish the call, nor does it need to analyze whether there is a problem with the called terminal due to the failure to establish the call.

[0055] In some embodiments, the preset duration may be 20 seconds.

[0056] Whether the preset duration has been reached can be determined through a timer built into the called terminal.

[0057] It should be noted that the preset duration of 20 seconds is only a specific example given in the present disclosure, and can actually be flexibly set according to the needs of technical personnel. 20 seconds is only a reference value based on experience, and the present disclosure does not impose any limitation on this.

[0058] By executing the IMS call problem determination method proposed in the present invention, the called terminal can, when the call establishment fails, perform a problem checking operation to perform a preliminary analysis of the cause of the call establishment failure, and when the preset conditions are met, determine that the call establishment failure is caused by a network side failure, thereby avoiding unnecessary waste of resources and making it unnecessary for the tester to capture the log of the called terminal and analyze whether the called terminal has a fault.

[0059] Figure 2 This is a schematic flow chart of a method for determining an IMS call problem according to an embodiment of the present disclosure. It should be noted that the present disclosure does not modify the process of the called terminal attempting to establish a call after being called, but only monitors part of the process of attempting to establish a call based on the called terminal attempting to establish a call through the method for determining an IMS call problem proposed in the present disclosure, so as to preliminarily determine the cause of the IMS call problem.

[0060] like Figure 2 As shown, in step S200, a problem checking operation is performed; during a called process, the called terminal may attempt to establish a call multiple times, and a problem checking operation needs to be performed during each attempt to establish a call;

[0061] Only when all attempts of the called terminal to establish a call during the called process fail, can the call establishment be considered to have failed. If any attempt to establish a call during the called process succeeds, it means that the call is successfully established.

[0062] In some embodiments, the specific contents of performing a problem checking operation may include:

[0063] In step S201, it is determined whether the P-RNTI is demodulated successfully. If the demodulation is successful, step S202 is executed. If the demodulation fails, step S2011 is executed.

[0064] In step S2011, the first variable is incremented, and the process goes to step S204 to determine that the attempt to establish the call has failed; if the called terminal fails to demodulate the P-RNTI, the call cannot be successfully established;

[0065] In step S202, it is determined whether the paging matches the called terminal. If so, step S2021 is executed. If not, the call cannot be successfully established, and the process goes to step S204. The attempt to establish the call fails.

[0066] In step S2021, the second variable is incremented, and the process goes to step S203;

[0067] In step S203, it is determined whether the call establishment is successful. Based on the determination result, the process proceeds to step S2031 to determine if the call establishment is successful, or proceeds to step S204 to determine if the attempt to establish the call fails. In some embodiments, the called terminal may determine whether the current IMS call is successfully established based on an identifier obtained from the AP side log.

[0068] In some embodiments, the initial values ​​of the first variable and the second variable may be preset to 0, and the increment values ​​may be 1 each time.

[0069] Therefore, in the event of a call establishment failure, the number of times P-RNTI demodulation failed within the preset time length can be determined based on the final value of the first variable, and the number of times P-RNTI demodulation was successful and paging matched within the preset time length but the call establishment still failed in the end can be determined based on the final value of the second variable.

[0070] In some embodiments, after the call process ends, if the call establishment fails, the final values ​​of the first variable and the second variable can be used to determine whether the called terminal has a fault. Furthermore, if it is determined that the called terminal has a fault, a log that can be used to analyze the cause of the problem can be captured.

[0071] See also Figure 2 , it can be seen that in the case of each failed attempt to establish a call, there are a first path, a second path and a third path, wherein the first path and the third path are caused by abnormalities of the called terminal, while the second path is caused by an abnormality on the network side.

[0072] In some embodiments, whether the preset condition is met is determined by the following method: whenever it is determined that the called terminal fails to demodulate the paging wireless network identifier P-RNTI, the value of a predefined first variable is incremented; whenever it is determined that the paging sent by the network side matches the called terminal, the value of a predefined second variable is incremented; if after the preset time period, the values ​​of the first variable and the second variable are both initial values, it is determined that the preset condition is met.

[0073] That is, when all attempts by the called terminal to establish a call fail within a preset time period, if the values ​​of the first variable and the second variable are both initial values, it is determined that the preset condition is met, and a network-side failure is prompted.

[0074] Combination Figure 2 In the illustrated embodiment, it can be seen that in the case of call establishment failure, the preset condition is met only when all attempts to establish calls within the preset time period fail through the second path, and a network side failure can be prompted.

[0075] Therefore, during this call, the called terminal did not show any abnormality, so it is not necessary to obtain and analyze the log of the called terminal. After waiting for the abnormality on the network side to disappear, the called terminal can be called again to test whether the called terminal can successfully establish a call.

[0076] In some embodiments, the method also includes: if the value of the first variable is not the initial value after the preset time period, then capturing the log of the baseband processor BP side; if the value of the first variable is the initial value but the value of the second variable is not the initial value after the preset time period, then capturing the logs of the baseband processor BP side and the application processor AP side.

[0077] In some embodiments, if after the preset time period, the value of the first variable and the value of the second variable are not the initial value, the logs of the baseband processor BP side and the application processor AP side are captured.

[0078] See also Figure 2 In the embodiment, the value of the second variable not being the initial value actually corresponds to a failure in the attempt to establish a call through the first path, and the value of the first variable not being the initial value corresponds to a failure in the attempt to establish a call through the third path.

[0079] Therefore, in addition to the case where the values ​​of the first and second variables are both initial values, there are three other cases:

[0080] In the first case, the value of the first variable is not the initial value, and the value of the second variable is the initial value; this indicates that all attempts to establish a call within the preset time period did not fail through the first path, and at least one attempt through the third path resulted in failure. Therefore, it can be determined that there is a demodulation failure in the P-RNTI. At this time, it is necessary to obtain the log on the BP side for analysis to clarify the abnormality of the called terminal; precisely because all attempts to establish a call within the preset time period did not fail through the first path, it is impossible to determine whether the terminal has an abnormality on the BP side, and subsequent testing is required;

[0081] In the second case, the value of the first variable is the initial value, and the value of the second variable is not the initial value; this indicates that there is no problem with the P-RNTI demodulation of the called terminal. During all attempts to establish calls within the preset time, the P-RNTI demodulation is successful. However, there is at least one failure caused by the first path. Therefore, it is necessary to obtain the logs on the BP side and the AP side to clarify the abnormality of the called terminal.

[0082] In the third case, the values ​​of the first variable and the second variable are not the initial values; this indicates that in the process of multiple attempts to establish a call within the preset time, there are attempts that fail through the first path and attempts that fail through the third path. Therefore, it is also necessary to obtain the logs on the BP side and the AP side to clarify the abnormality of the called terminal.

[0083] In some embodiments, the method further includes: when a network side failure is prompted, not capturing logs on the application processor AP side and the baseband processor BP side.

[0084] When the first variable and the second variable are both initial values, a network side failure is prompted. At this time, the call establishment failure is not caused by an abnormality in the called terminal, but by an abnormality on the network side. Therefore, it is not necessary to capture the logs on the application processor AP side and the baseband processor BP side. After the abnormality on the network side is eliminated, the call test can be performed.

[0085] In some embodiments, the method further comprises: performing the problem checking operation once every time the discontinuous reception (DRX) cycle of the called terminal switches from a sleep state to an active state within the preset time period.

[0086] The DRX (Discontinuous Reception) cycle of the called terminal in the idle mode is divided into an active state and a sleep state.

[0087] The network side can configure a DRX cycle for the called terminal, for example, 320 milliseconds, 640 milliseconds, 1280 milliseconds, etc. The called terminal can enter an active state in a DRX cycle to communicate with the network side. Therefore, in the active state of each DRX cycle within the preset duration, the called terminal will communicate with the network side once and try to establish a call, so for each attempt, a problem check operation needs to be performed.

[0088] In some embodiments, whether the DRX cycle of the called terminal is in an activated state may be determined by analyzing the log on the BP side of the called terminal.

[0089] In some embodiments, the method further includes: when the called terminal is not in the idle state, if the call establishment fails, capturing logs on the baseband processor BP side and the application processor AP side.

[0090] If the called terminal is not in idle state, the network side will not send paging to the terminal. Therefore, if the call establishment fails in this case, it must be due to an abnormality in the called terminal, and it cannot be caused by an abnormality on the network side. Therefore, it is necessary to capture the logs on the BP side and the AP side and determine the abnormality of the called terminal through further analysis.

[0091] In some embodiments, the method further includes: if the call is successfully established, prompting that the called terminal is normal.

[0092] In some embodiments, the prompt of network side failure includes: a prompt on the display interface of the called terminal, that the called terminal successfully demodulates all P-RNTI types, but all received pagings do not match the called terminal, and the failure to establish the call is caused by the network side not sending the correct paging, which is a network side problem and there is no need to capture the logs of the AP side and BP.

[0093] In some embodiments, based on the values ​​of the first variable and the second variable, a prompt can also be displayed on the display interface of the called terminal: the called terminal has not successfully demodulated all P-RNTI types, and it is recommended to capture the BP side log to further analyze the cause; or, the called terminal has successfully demodulated all P-RNTI types, there is a paging match with the called terminal, but the IMS call is not established, and there is an unknown problem with the called terminal that causes the IMS call to fail, and it is recommended to capture the logs on the BP side and the AP side to further analyze the cause.

[0094] The present disclosure can avoid unnecessary waste of resources and improve test efficiency by executing problem checking operations and giving corresponding prompts to testers during testing of the called terminal.

[0095] Corresponding to the embodiment of the method for determining an IMS call problem of the present disclosure, the present disclosure also provides an embodiment of a corresponding device for determining an IMS call problem.

[0096] See also Figure 3 , Figure 3 FIG. 1 is a block diagram of an apparatus for determining an IMS call problem in one embodiment of the present disclosure. Figure 3 As shown, in the case where the calling terminal calls the called terminal, the IMS call problem determination device is configured in the called terminal, including:

[0097] The determining unit 310 is configured to determine whether the called terminal is in an idle state;

[0098] The checking unit 320 is configured to perform a problem checking operation when the called terminal is in the idle state; wherein the problem checking operation includes determining whether the called terminal successfully demodulates the paging wireless network identifier during the call process; and if the demodulation is successful, determining whether the paging sent by the network side matches the called terminal;

[0099] The prompt unit 330 is configured to prompt a network side failure if the call establishment fails and the preset conditions are met, wherein the preset conditions include that all paging wireless network identifiers of the called terminal within a preset time period are demodulated successfully and each paging does not match the called terminal.

[0100] In some embodiments, whether the preset condition is met is determined by the following method: whenever it is determined that the called terminal fails to demodulate the paging wireless network identifier, the value of a predefined first variable is incremented; whenever it is determined that the paging sent by the network side matches the called terminal, the value of a predefined second variable is incremented; if after the preset time period, the values ​​of the first variable and the second variable are both initial values, it is determined that the preset condition is met.

[0101] In some embodiments, the device is further configured to: if the value of the first variable is not the initial value after the preset time period, then capture the log of the baseband processor BP side; if the value of the first variable is the initial value but the value of the second variable is not the initial value after the preset time period, then capture the logs of the baseband processor BP side and the application processor AP side.

[0102] In some embodiments, the device is further configured to: when a network side failure is prompted, not capture logs on the application processor AP side and the baseband processor BP side.

[0103] In some embodiments, the apparatus is further configured to: perform the problem checking operation once every time the discontinuous reception (DRX) cycle of the called terminal switches from a sleep state to an active state within the preset time period.

[0104] In some embodiments, the apparatus is further configured to: when the called terminal is not in the idle state, if the call establishment fails, capture the logs of the baseband processor BP side and the application processor AP side.

[0105] In some embodiments, the apparatus is further configured to: if the call is successfully established, prompt that the called terminal is normal.

[0106] The implementation process of the functions and effects of each unit in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, and will not be repeated here.

[0107] An embodiment of the present disclosure further proposes an electronic device, comprising: a processor and a memory; the memory is used to store a computer program; the processor is used to execute the delay mitigation method as described in any of the above embodiments by calling the computer program.

[0108] An embodiment of the present disclosure further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method for alleviating delay as described in any of the above embodiments.

[0109] Figure 4 4 is a schematic block diagram of an apparatus 400 for determining an IMS call problem according to an embodiment of the present disclosure. For example, the apparatus 400 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0110] Reference Figure 4 , the device 400 may include one or more of the following components: a processing component 402 , a memory 404 , a power component 406 , a multimedia component 408 , an audio component 410 , an input / output (I / O) interface 412 , a sensor component 414 , and a communication component 416 .

[0111] The processing component 402 generally controls the overall operation of the device 400, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 402 may include one or more processors 420 to execute instructions to complete all or part of the steps of the above-mentioned information receiving method. In addition, the processing component 402 may include one or more modules to facilitate the interaction between the processing component 402 and other components. For example, the processing component 402 may include a multimedia module to facilitate the interaction between the multimedia component 408 and the processing component 402.

[0112] The memory 404 is configured to store various types of data to support operations on the device 400. Examples of such data include instructions for any application or method operating on the device 400, contact data, phone book data, messages, pictures, videos, etc. The memory 404 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk.

[0113] The power supply component 406 provides power to the various components of the device 400. The power supply component 406 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device 400.

[0114] The multimedia component 408 includes a screen that provides an output interface between the device 400 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 408 includes a front camera and / or a rear camera. When the device 400 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0115] The audio component 410 is configured to output and / or input audio signals. For example, the audio component 410 includes a microphone (MIC), and when the device 400 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 404 or sent via the communication component 416. In some embodiments, the audio component 410 also includes a speaker for outputting audio signals.

[0116] I / O interface 412 provides an interface between processing component 402 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.

[0117] The sensor assembly 414 includes one or more sensors for providing various aspects of status assessment for the device 400. For example, the sensor assembly 414 can detect the open / closed state of the device 400, the relative positioning of components, such as the display and keypad of the device 400, and the sensor assembly 414 can also detect the position change of the device 400 or a component of the device 400, the presence or absence of user contact with the device 400, the orientation or acceleration / deceleration of the device 400, and the temperature change of the device 400. The sensor assembly 414 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 414 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 414 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0118] The communication component 416 is configured to facilitate wired or wireless communication between the device 400 and other devices. The device 400 can access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G LTE, 5G NR, or a combination thereof. In an exemplary embodiment, the communication component 416 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 416 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0119] In an exemplary embodiment, the device 400 can be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to execute the above-mentioned information receiving method.

[0120] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 404 including instructions, and the instructions can be executed by a processor 420 of the device 400 to complete the above-mentioned information receiving method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0121] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the disclosure disclosed herein. The present disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0122] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

[0123] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "include", "comprises" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "comprises a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0124] The method and device provided in the embodiments of the present disclosure are introduced in detail above. Specific examples are used in this article to illustrate the principles and implementation methods of the present disclosure. The description of the above embodiments is only used to help understand the method of the present disclosure and its core idea. At the same time, for those skilled in the art, according to the idea of ​​the present disclosure, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on the present disclosure.

Claims

1. A method for determining an IMS call problem, It is characterized in that In the case where a calling terminal calls a called terminal, the method is performed by the called terminal and includes: Determining whether the called terminal is in an idle state; When the called terminal is in the idle state, performing a problem checking operation; wherein the problem checking operation includes determining whether the called terminal successfully demodulates the paging wireless network identifier during the call process; and if the demodulation is successful, determining whether the paging sent by the network side matches the called terminal; If the call establishment fails and the preset conditions are met, a network failure is prompted, wherein the preset conditions include that all paging wireless network identifiers of the called terminal within a preset time period are demodulated successfully and each paging does not match the called terminal.

2. The method according to claim 1, It is characterized in that Determine whether the preset conditions are met by the following method: Whenever it is determined that the called terminal fails to demodulate the paging wireless network identifier, incrementing the value of the predefined first variable; Whenever it is determined that the paging sent by the network side matches the called terminal, the value of the predefined second variable is incremented; If after the preset time period, the values ​​of the first variable and the second variable are both initial values, it is determined that the preset condition is met.

3. The method according to claim 2, It is characterized in that The method further comprises: If the value of the first variable is not the initial value after the preset time, capturing the log of the baseband processor BP side; If after the preset time period, the value of the first variable is the initial value but the value of the second variable is not the initial value, the logs of the baseband processor BP side and the application processor AP side are captured.

4. The method according to claim 1, It is characterized in that The method further comprises: When a network fault is indicated, logs on the application processor AP side and the baseband processor BP side are not captured.

5. The method according to claim 1, It is characterized in that The method further comprises: During the preset time period, each time the discontinuous reception (DRX) cycle of the called terminal switches from a sleep state to an active state, the problem checking operation is performed once.

6. The method according to claim 1, It is characterized in that The method further comprises: In the case that the called terminal is not in the idle state, if the call establishment fails, the logs of the baseband processor BP side and the application processor AP side are captured.

7. The method according to claim 1, It is characterized in that The method further comprises: If the call is established successfully, it will prompt that the called terminal is normal.

8. A device for determining an IMS call problem, It is characterized in that When a calling terminal calls a called terminal, the device is configured at the called terminal and includes: a determining unit, configured to determine whether the called terminal is in an idle state; The checking unit is configured to perform a problem checking operation when the called terminal is in the idle state; wherein the problem checking operation includes determining whether the called terminal successfully demodulates the paging wireless network identifier during the call process; and if the demodulation is successful, determining whether the paging sent by the network side matches the called terminal; The prompt unit is configured to prompt a network side failure if the call establishment fails and the preset conditions are met, wherein the preset conditions include that all paging wireless network identifiers of the called terminal within a preset time period are demodulated successfully and each paging does not match the called terminal.

9. An electronic device, It is characterized in that include: Processor, memory; The memory is used to store computer programs; The processor is configured to execute the method for determining an IMS call problem according to any one of claims 1 to 7 by calling the computer program.

10. A computer-readable storage medium having a computer program stored thereon, It is characterized in that When the program is executed by a processor, the method for determining an IMS call problem according to any one of claims 1 to 7 is implemented.

Images