WO2017096878A1 - 掉话测试方法及装置 - Google Patents

掉话测试方法及装置 Download PDF

Info

Publication number
WO2017096878A1
WO2017096878A1 PCT/CN2016/089252 CN2016089252W WO2017096878A1 WO 2017096878 A1 WO2017096878 A1 WO 2017096878A1 CN 2016089252 W CN2016089252 W CN 2016089252W WO 2017096878 A1 WO2017096878 A1 WO 2017096878A1
Authority
WO
WIPO (PCT)
Prior art keywords
call
log
error rate
bit error
recording
Prior art date
Application number
PCT/CN2016/089252
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 乐视控股（北京）有限公司
Priority to US15/240,901 priority Critical patent/US20170163800A1/en
Publication of WO2017096878A1 publication Critical patent/WO2017096878A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic

Definitions

  • the invention relates to the field of communication test technology, in particular to a call drop test method and device.
  • dropped calls are a common phenomenon.
  • the test personnel need to manually test and capture the call log (hereinafter referred to as LOG), and then provide it to the R&D personnel for analysis; the whole process is manually completed by the test personnel, and It takes a long time, and the tester needs to be vigilant to capture the moment of the call at any time.
  • LOG call log
  • the existing technical solution is usually that the tester needs to manually open the LOG recorder or the LOG record module through the tool before the call is made; after the call is dropped, the record LOG needs to be manually saved and manually submitted to the R&D. personnel.
  • This technical solution requires the tester to track a large number of calls, and manually judge whether it is a dropped call, and the labor cost is high; and manually crawling the LOG is not conducive to statistical data drop, which is easy to cause data omission, and statistics also require human resources. cost.
  • the existing technical solution is usually that the user can manually open the LOG recording unit in the mobile phone communication module (modem) of the mobile phone to perform LOG recording, and the call drop problem occurring during the recording process is recorded in the LOG. And upload it to the server through the mobile phone, so as to provide analysis to the R&D personnel of the mobile phone manufacturer.
  • the mobile phone communication module (modem) of the current mainstream mobile phone chip manufacturer has a large amount of LOG information. For example, in the process of using the mobile phone, the LOG will always fill the storage space; but if the call is found, the LOG is normally opened. The best time to grab the LOG has been missed.
  • the object of the present invention is to provide a call drop test method and device, which can capture the LOG in time and count the dropped call data without occupying too much space.
  • the call drop test method provided by the present invention based on the above object includes:
  • the step of starting to record the call log further includes:
  • the recording of the call log if the bit error rate is lower than the bit error rate threshold at a certain time, the recording of the call log is stopped.
  • the step of starting to record the call log further includes:
  • the recording of the call log if the bit error rate is lower than the bit error rate threshold at a certain time and the duration exceeds the preset second time threshold, the recording of the call log is stopped.
  • the step of stopping recording the call log further includes:
  • the step of saving the call log further includes:
  • the call log is uploaded to the server.
  • Another aspect of the present invention also provides a call drop test apparatus, including:
  • a call initiation module for starting a call
  • a bit error rate monitoring module for continuously monitoring the bit error rate of the physical layer
  • Call drop danger determination module when the bit error rate is higher than the preset error rate threshold and the duration exceeds the preset The first time threshold is used to determine that a dropped incident is occurring;
  • a logging module configured to start recording a call log based on the dropped call risk event
  • the log saving module is used to save the call log when the call ends abnormally
  • the log uploading module is used to upload the saved call log to the server when the call ends abnormally.
  • the error rate monitoring module is further configured to continue to monitor a bit error rate of the physical layer
  • the log recording module is further configured to stop recording the call log.
  • the error rate monitoring module is further configured to continue to monitor a bit error rate of the physical layer
  • the log recording module is further configured to stop recording the call log.
  • the apparatus further includes a log deletion module
  • the log deletion module is configured to delete the already recorded call log.
  • the device further includes a WIFI connection determination module, configured to determine whether to connect to the WIFI;
  • the log uploading module is configured to upload the call log to the server
  • the log uploading module is configured to upload the call log to the server after the WIFI is connected.
  • the present invention further provides a computer storage medium, wherein the computer storage medium can store a program, and when executed, the program can implement some or all of the steps of the implementation of the call drop test method provided by the present invention.
  • the call drop test method and device provided by the present invention automatically captures the call log (LOG) and uploads the server by monitoring the bit error rate of the physical layer during the call, thereby user or test
  • the person can automatically complete the entire crawling and uploading process in the terminal only by using the mobile phone normally; and, by testing according to the error rate monitoring result, the terminal will only capture the call log in the dropped call, and will not A large number of invalid call logs are generated to occupy the storage space of the terminal; because there is a bit error rate as a basis, once the call is dropped, since the recording has been started before the call is dropped, the number of missed scenes is reduced. Rate; in addition, automatically sending call logs to the server facilitates statistics and further analysis.
  • FIG. 1 is a schematic flow chart of an embodiment of a call drop test method provided by the present invention.
  • FIG. 2 is a schematic flow chart of another embodiment of a call drop test method provided by the present invention.
  • FIG. 3 is a schematic structural diagram of a module of an embodiment of a call drop test apparatus according to the present invention.
  • FIG. 1 is a schematic flowchart diagram of an embodiment of a call drop test method provided by the present invention.
  • the call drop test method includes the following steps:
  • Step 101 Start a call; that is, the mobile terminal is turned on and enters a call mode;
  • Step 102 continuously monitor the error rate of the physical layer at the bottom of the protocol stack
  • the BER symbol error rate
  • Bit error rate error in transmission / total number of codes transmitted *100%. If there is a bit error, there is a bit error rate. The error is generated because the decay changes the voltage of the signal during signal transmission, causing the signal to be corrupted during transmission, resulting in bit errors. Pulses caused by noise, AC or lightning, transmission equipment failures, and other factors can cause bit error rates (such as a transmitted signal of 1 and a received 0; and vice versa). For various reasons, digital signals inevitably generate errors during transmission. For example, the external signal is disturbed during transmission, or the transmitted signal is distorted due to the insufficient quality of each component in the communication system.
  • Step 103 Determine whether the bit error rate is higher than a preset error rate threshold (Vcrc) and the duration exceeds a preset first time threshold;
  • Step 104 If the error rate is higher than the preset error rate threshold (Vcrc) and the duration exceeds the preset first time threshold (Tcrc), it is determined that a dropped incident is occurred (the protocol stack reports the upper call module) That is, in this case, there is a high risk that a dropped call will occur; the bit error rate threshold is set according to different communication signals, such as GSM, 3G, 4G signals, and the corresponding bit error rate.
  • the thresholds are not the same, and need to be specifically set according to the specific situation; similarly, the first time threshold needs to be differently set according to different specific situations;
  • Step 105 If the error rate is not higher than the preset error rate threshold or higher than the preset error rate threshold but the duration does not exceed the preset first time threshold and falls back below the bit error rate threshold, then Determining that no dropped incident has occurred, and returning to step 102 to continue monitoring the bit error rate of the physical layer;
  • Step 106 Start recording a call log based on the call drop dangerous event (the call module notifies the log module to open the LOG on the modem side); that is, the function of logging the log is started at this time, and the call log is started to be recorded in real time, so as to be about to happen.
  • the event is recorded in the LOG;
  • Step 107 Determine whether the call ends abnormally
  • Step 108 If the call ends abnormally (a call drop event occurs), the already recorded call log is saved and uploaded to the server for research and development personnel to investigate the cause of the dropped call event;
  • Step 109 If the call ends normally, stop recording the call log and delete the recorded call log.
  • the call drop test method provided by the present invention automatically captures the call log (LOG) and uploads the server by monitoring the error rate of the physical layer during the call, so that the user or the tester only
  • the normal use of the mobile phone can automatically complete the entire crawling and uploading process in the terminal; and, by testing according to the error rate monitoring result, the terminal will only capture the call log in the dropped call, without generating a large amount of
  • the invalid call log occupies the storage space of the terminal; because there is a bit error rate as the basis, if there is a call drop, since the recording has already started before the call drop, the probability of missing the scene is reduced; in addition, the call log is automatically sent to the server, there is Conducive to statistics and further analysis.
  • step 105 of starting to record the call log may further include the following steps:
  • the recording of the call log if the bit error rate is lower than the bit error rate threshold at a certain time, the recording of the call log is stopped.
  • step 105 of starting to record the call log may further include the following steps:
  • the second time threshold may be set according to actual needs, and is not limited herein.
  • the step of stopping recording the call log may further include the following steps:
  • the unnecessary call log can be cleaned, and the storage space of the terminal is saved.
  • the call log is uploaded to the server.
  • the WIFI when the WIFI is connected after uploading the call log, the user can save traffic and reduce the consumption of money.
  • FIG. 2 is a schematic flowchart diagram of another embodiment of a call drop test method provided by the present invention.
  • the call drop test method includes the following steps:
  • Step 202 continuously monitor the error rate of the physical layer at the bottom of the protocol stack
  • Step 203 Determine whether the error rate is higher than a preset error rate threshold (Vcrc) and the duration exceeds a preset first time threshold;
  • Step 204 If yes, determine that a dropped incident is occurred (the protocol stack reports the upper call module);
  • Step 206 Start recording a call log based on the dropped call risk event
  • Step 207 Continue to monitor the error rate of the physical layer
  • Step 210 Delete the recorded call log, and return to step 202 to continue monitoring the error rate of the physical layer;
  • Step 211 If no, continue to record the call log
  • Step 213 If no, stop recording the call log and delete the recorded call log;
  • Step 214 If yes, save the recorded call log
  • Step 215 Determine whether to connect to WIFI
  • Step 216 If yes, upload the call log to the server;
  • Step 217 If no, manually connect to the WIFI. After the WIFI is connected, the call log is uploaded to the server.
  • the call drop test method provided by the present invention automatically captures the call log (LOG) and uploads the server by monitoring the error rate of the physical layer during the call, so that the user or the tester only
  • the normal use of the mobile phone can automatically complete the entire crawling and uploading process in the terminal; and, by testing according to the error rate monitoring result, the terminal will only capture the call log in the dropped call, without generating a large amount of Invalid call logs occupy the storage space of the terminal; because of the bit error rate, Therefore, once the call is dropped, since the recording has been started before the call is dropped, the probability of missing the scene is reduced; at the same time, the call log is automatically sent to the server, which is beneficial for statistics and further analysis.
  • FIG. 3 is a schematic structural diagram of a module of an embodiment of a call drop test apparatus provided by the present invention.
  • the call drop test device includes:
  • the call initiation module 301 is configured to start a call; that is, the mobile terminal is turned on and enters a call mode;
  • the error rate monitoring module 302 is configured to continuously monitor the error rate of the physical layer
  • the BER symbol error rate
  • Bit error rate error in transmission / total number of codes transmitted *100%. If there is a bit error, there is a bit error rate. The error is generated because the decay changes the voltage of the signal during signal transmission, causing the signal to be corrupted during transmission, resulting in bit errors. Pulses caused by noise, AC or lightning, transmission equipment failures, and other factors can cause bit error rates (such as a transmitted signal of 1 and a received 0; and vice versa). For various reasons, digital signals inevitably generate errors during transmission. For example, the external signal is disturbed during transmission, or the transmitted signal is distorted due to the insufficient quality of each component in the communication system.
  • bit error rate is an indicator for measuring the accuracy of data transmission within a specified time.
  • Bit error rate number of error symbols / total number of transmitted symbols.
  • Bit error rate number of error bits / total number of bits transmitted.
  • the bit error rate/bit error rate is the most commonly used data communication transmission quality indicator. It means that the quality of the digital system transmission is "one bit error in how many bits of data";
  • the dropped call risk determination module 303 is configured to determine that a dropped call dangerous event occurs when the error rate is higher than a preset error rate threshold (Vcrc) and the duration exceeds a preset first time threshold (Tcrc); In this case, it is very likely that the risk of dropped calls will occur; the bit error rate threshold is set according to different communication signals, such as GSM, 3G, 4G signals, and the corresponding bit error rate threshold is incomplete. The same, and need to be set according to specific circumstances; similarly, the first time threshold needs to be based on different specific situations. Make different specific settings;
  • the logging module 304 is configured to start recording a call log based on the dropped call event; that is, the function of logging the log is started, and the call log is started to be recorded in real time, so that the upcoming call drop event is recorded in the LOG;
  • the log uploading module 306 is configured to upload the saved call log to the server when the call ends abnormally, for the research and development personnel to investigate the cause of the dropped call event.
  • the call drop test apparatus provided by the present invention automatically captures the call log (LOG) and uploads the server by monitoring the error rate of the physical layer during the call, so that the user or the tester only
  • the normal use of the mobile phone can automatically complete the entire crawling and uploading process in the terminal; and, by testing according to the error rate monitoring result, the terminal will only capture the call log in the dropped call, without generating a large amount of
  • the invalid call log occupies the storage space of the terminal; because there is a bit error rate as the basis, if there is a call drop, since the recording has already started before the call drop, the probability of missing the scene is reduced; in addition, the call log is automatically sent to the server, there is Conducive to statistics and further analysis.
  • the error rate monitoring module 302 is further configured to continue to monitor a bit error rate of the physical layer
  • the log recording module 304 is further configured to stop recording the call log.
  • the error rate monitoring module 302 is further configured to continue to monitor a bit error rate of the physical layer
  • the log recording module 304 is further configured to stop recording the call log. .
  • the apparatus further includes a log deletion module 307, and after the log recording module 304 stops recording the call log, the log deletion module 307 is configured to delete the already recorded call log.
  • the unnecessary call log can be cleaned, and the storage space of the terminal is saved.
  • the storage device occupies a large amount of storage space. Therefore, in some preferred embodiments, the device further includes a WIFI connection determining module 308, configured to determine whether to connect to the WIFI;
  • the log uploading module 306 is configured to upload the call log to the server
  • the log uploading module 306 is configured to upload the call log to the server after the WIFI is connected.
  • Step 201 The call initiation module 301 starts a call
  • Step 202 The error rate monitoring module 302 continuously monitors the error rate of the physical layer at the bottom of the protocol stack.
  • Step 203 The error rate monitoring module 302 determines whether the error rate is higher than a preset error rate threshold (Vcrc) and the duration exceeds a preset first time threshold.
  • Vcrc preset error rate threshold
  • Step 204 If yes, the dropped call risk determining module 303 determines that a dropped call dangerous event occurs (the protocol stack reports the upper call module);
  • Step 207 The error rate monitoring module 302 continues to monitor the error rate of the physical layer.
  • Step 208 In the process of recording the call log, the error rate monitoring module 302 determines whether the error rate is lower than the error rate threshold at a certain time and the duration exceeds a preset second time threshold;
  • Step 209 If yes, the logging module 304 stops recording the call log.
  • Step 210 The log deletion module 307 deletes the recorded call log, and returns to step 202.
  • the error rate monitoring module 302 continues to monitor the error rate of the physical layer.
  • Step 211 If no, the logging module 304 continues to record the call log;
  • Step 212 The call module 309 determines whether the call ends abnormally
  • Step 213 If no, the logging module 304 stops recording the call log, and the log deleting module 307 deletes the recorded call log.
  • Step 216 If yes, the log uploading module 306 uploads the call log to the server;
  • Step 217 If no, the WIFI is manually connected. After the WIFI is connected, the log uploading module 306 uploads the call log to the server.
  • the call drop test apparatus provided by the present invention automatically captures the call log (LOG) and uploads the server by monitoring the error rate of the physical layer during the call, so that the user or the tester only
  • the normal use of the mobile phone can automatically complete the entire crawling and uploading process in the terminal; and, by testing according to the error rate monitoring result, the terminal will only capture the call log in the dropped call, without generating a large amount of
  • the invalid call log occupies the storage space of the terminal; because there is a bit error rate as the basis, if there is a dropped call, since the recording has already started before the call is dropped, the probability of missing the scene is reduced; at the same time, the call log is automatically sent to the server, there is Conducive to statistics and further analysis.
  • the embodiment of the present invention further provides a computer storage medium, wherein the computer storage medium can store a program, and the program can be implemented in each implementation manner of the call drop test method provided by the embodiment shown in FIG. Some or all of the steps.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Monitoring And Testing Of Exchanges (AREA)
  • Telephone Function (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本发明公开了一种掉话测试方法及装置，包括：启动通话；持续监测物理层的误码率；若误码率高于预设的误码率阈值且持续时间超过预设的第一时间阈值，则判定发生掉话危险事件；基于所述掉话危险事件，开始记录通话日志；若通话异常结束，则保存通话日志并将其上传至服务器。本发明提出的掉话测试方法及装置，能够及时抓取LOG并统计掉话数据，且不会占用过多的空间。

Description

掉话测试方法及装置
本申请要求于2015年12月8日提交中国专利局、申请号为2015108980981、发明名称为“掉话测试方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信测试技术领域，特别是指一种掉话测试方法及装置。
背景技术
在无线通信中，掉话是一种比较常见的现象。为了保证手机不出现掉话问题，目前在手机研发过程中，都需要经测试人员手工测试和抓取通话日志(以下简称LOG)，然后提供给研发人员分析；整个过程由测试人员手动完成，并且需要花费很长的时间，同时需要测试人员一直保持警觉状态，才能随时捕捉掉话时刻；但在很多时候，如果测试人员没有提前准备，则无法获取有效LOG，错失掉话现场。
对于测试方来说，现有的技术方案通常是，在进行通话前，测试人员需要通过工具手动开启LOG记录器或LOG记录模块；出现掉话之后，需手动保存记录的LOG并手动提交给研发人员。而这种技术方案需要测试人员对大量的通话进行跟踪，并通过人工判断是否属于掉话，人力成本高；并且手动抓取LOG不利于统计掉话数据，容易造成数据遗漏，并且统计也需要人力成本。
对于手机端来说，现有的技术方案通常是，用户可手动开启手机的手机通信模块(modem)中的LOG记录单元来进行LOG记录，记录过程中发生的掉话问题被记录到LOG中，并通过手机上传到服务器，从而提供给手机厂商的研发人员进行分析。但是，目前主流的手机芯片厂商的手机通信模块(modem)的LOG信息量较大，如在使用手机的过程中一直开启LOG会很快占满存储空间；但如果发现掉话再开启LOG，一般已错失抓取LOG的最佳时机。
发明内容
有鉴于此，本发明的目的在于提出一种掉话测试方法及装置，能够及时抓取LOG并统计掉话数据，且不会占用过多的空间。
基于上述目的本发明提供的掉话测试方法，包括：
启动通话；
持续监测物理层的误码率；
若误码率高于预设的误码率阈值且持续时间超过预设的第一时间阈值，则判定发生掉话危险事件；
基于所述掉话危险事件，开始记录通话日志；
若通话异常结束，则保存通话日志并将其上传至服务器。
在一些实施方式中，所述开始记录通话日志的步骤之后还包括：
继续监测物理层的误码率；
在记录通话日志的过程中，若误码率在某一时刻低于所述误码率阈值，则停止记录通话日志。
在一些实施方式中，所述开始记录通话日志的步骤之后还包括：
继续监测物理层的误码率；
在记录通话日志的过程中，若误码率在某一时刻低于所述误码率阈值且持续时间超过预设的第二时间阈值，则停止记录通话日志。
在一些实施方式中，所述停止记录通话日志的步骤之后还包括：
删除已经记录的通话日志。
在一些实施方式中，所述保存通话日志的步骤之后还包括：
判断是否连接上WIFI；
若是，则将通话日志上传至服务器；
若否，则待连接上WIFI后，将通话日志上传至服务器。
本发明的另一方面还提供了一种掉话测试装置，包括：
通话启动模块，用于启动通话；
误码率监测模块，用于持续监测物理层的误码率；
掉话危险判定模块，当误码率高于预设的误码率阈值且持续时间超过预设的 第一时间阈值时，用于判定发生掉话危险事件；
日志记录模块，用于基于所述掉话危险事件，开始记录通话日志；
日志保存模块，当通话异常结束时，用于保存通话日志；
日志上传模块，当通话异常结束时，用于将保存的通话日志上传至服务器。
在一些实施方式中，所述误码率监测模块，还用于继续监测物理层的误码率；
在记录通话日志的过程中，若误码率在某一时刻低于所述误码率阈值，所述日志记录模块，还用于停止记录通话日志。
在一些实施方式中，所述误码率监测模块，还用于继续监测物理层的误码率；
在记录通话日志的过程中，若误码率在某一时刻低于所述误码率阈值且持续时间超过预设的第二时间阈值，所述日志记录模块，还用于停止记录通话日志。
在一些实施方式中，所述的装置还包括日志删除模块，
所述日志记录模块停止记录通话日志后，所述日志删除模块用于删除已经记录的通话日志。
在一些实施方式中，所述的装置还包括WIFI连接判定模块，用于判断是否连接上WIFI；
若是，则所述日志上传模块用于将通话日志上传至服务器；
若否，则待连接上WIFI后，所述日志上传模块用于将通话日志上传至服务器。
另外，本发明还提供一种计算机存储介质，其中，该计算机存储介质可存储有程序，该程序执行时可实现本发明上述提供的掉话测试方法的各实现方式中的部分或全部步骤。
从上面所述可以看出，本发明提供的掉话测试方法及装置，通过监测通话过程中物理层的误码率来实现自动抓取掉话通话日志(LOG)并上传服务器，从而用户或测试人员只需正常使用手机，就能自动在终端中完成整个抓取和上传过程；并且，通过根据误码率监控结果进行测试，终端只会在掉话的通话中抓取通话日志，而不会产生大量无效的通话日志占用终端的存储空间；因为有误码率作为依据，因此一旦出现掉话，因在掉话之前已经开始记录，降低了错失现场的几 率；此外，自动发送通话日志到服务器，有利于统计和进一步分析。
附图说明
图1为本发明提供的掉话测试方法的一个实施例的流程示意图；
图2为本发明提供的掉话测试方法的另一个实施例的流程示意图；
图3为本发明提供的掉话测试装置实施例的模块结构示意图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚明白，以下结合具体实施例，并参照附图，对本发明进一步详细说明。
需要说明的是，本发明实施例中所有使用“第一”和“第二”的表述均是为了区分两个相同名称非相同的实体或者非相同的参量，可见“第一”“第二”仅为了表述的方便，不应理解为对本发明实施例的限定，后续实施例对此不再一一说明。
本发明的第一个方面，提供了一种能够及时抓取LOG并统计掉话数据，且不会占用过多的空间的掉话测试方法。如图1所示，为本发明提供的掉话测试方法的一个实施例的流程示意图。
所述掉话测试方法，包括以下步骤：
步骤101：启动通话；即移动终端开启并进入了通话模式；
步骤102：持续监测协议栈底层的物理层的误码率；
误码率(SER：symbol error rate)是衡量数据在规定时间内数据传输精确性的指标。误码率＝传输中的误码/所传输的总码数*100％。如果有误码就有误码率。误码的产生是由于在信号传输中，衰变改变了信号的电压，致使信号在传输中遭到破坏，产生误码。噪音、交流电或闪电造成的脉冲、传输设备故障及其他因素都会导致误码率(比如传送的信号是1，而接收到的是0；反之亦然)。由于种种原因，数字信号在传输过程中不可避免地会产生差错。例如在传输过程中受到外界的干扰，或在通信***内部由于各个组成部分的质量不够理想而使传送的信号发生畸变等。当受到的干扰或信号畸变达到一定程度时，就会产生差错。误比特率(BER：bit error rate)是衡量数据在规定时间内数据传输精确性的指 标。误码率＝错误码元数/传输总码元数。误比特率＝错误比特数/传输总比特数。误码率/误比特率是最常用的数据通信传输质量指标。它表示数字***传输质量的式是“在多少位数据中出现一位差错”。
步骤103：判断误码率是否高于预设的误码率阈值(Vcrc)且持续时间超过预设的第一时间阈值；
步骤104：若误码率高于预设的误码率阈值(Vcrc)且持续时间超过预设的第一时间阈值(Tcrc)，则判定发生掉话危险事件(协议栈上报上层的通话模块)；即，此种情况下，很有可能将会发生掉话的危险；所述误码率阈值，是根据不同的通信信号来分别设置的，如GSM、3G、4G信号，对应的误码率阈值不尽相同，且需要根据具体情况具体设置；同样的，所述第一时间阈值，也需要根据不同的具体情况进行不同的具体设置；
步骤105：若误码率没有高于预设的误码率阈值或者高于预设的误码率阈值但持续时间没有超过预设的第一时间阈值而又回落到误码率阈值以下，则判定没有发生掉话危险事件，并返回步骤102，继续监测物理层的误码率；
步骤106：基于所述掉话危险事件，开始记录通话日志(通话模块通知日志模块开启modem侧的LOG)；即，此时开启记录日志的功能，开始实时记录通话日志，以期把即将发生的掉话事件记录在LOG中；
步骤107：判断通话是否异常结束；
步骤108：若通话异常结束(发生掉话事件)，则保存已经记录的通话日志并将其上传至服务器，供研发人员对掉话事件的原因进行研究；
步骤109：若通话正常结束，则停止记录通话日志，并删除已记录的通话日志。
从上述实施例可以看出，本发明提供的掉话测试方法，通过监测通话过程中物理层的误码率来实现自动抓取掉话通话日志(LOG)并上传服务器，从而用户或测试人员只需正常使用手机，就能自动在终端中完成整个抓取和上传过程；并且，通过根据误码率监控结果进行测试，终端只会在掉话的通话中抓取通话日志，而不会产生大量无效的通话日志占用终端的存储空间；因为有误码率作为依据，因此一旦出现掉话，因在掉话之前已经开始记录，降低了错失现场的几率；此外，自动发送通话日志到服务器，有利于统计和进一步分析。
进一步的，在一些可选实施方式中，所述开始记录通话日志的步骤105之后还可包括以下步骤：
继续监测物理层的误码率；
在记录通话日志的过程中，若误码率在某一时刻低于所述误码率阈值，则停止记录通话日志。
或者，进一步的，在另一些可选实施方式中，所述开始记录通话日志的步骤105之后还可包括以下步骤：
继续监测物理层的误码率；
在记录通话日志的过程中，若误码率在某一时刻低于所述误码率阈值且持续时间超过预设的第二时间阈值，则停止记录通话日志。其中，第二时间阈值可根据实际需要进行设置，在此不对其进行限定。
通过上述两种方式，使得在通话进入正常状态时，停止记录通话日志，从而节省了终端的存储空间，以避免过多地记录不需要的通话日志。
更进一步的，在一些可选实施方式中，所述停止记录通话日志的步骤之后还可包括以下步骤：
删除已经记录的通话日志。
通过在停止记录通话日志后删除已经记录的通话日志，从而可以将不需要的通话日志进行清理，节省终端的存储空间。
由于通话日志所占的存储空间较大，因此，在一些较佳实施例中，所述保存通话日志的步骤之后还包括：
判断是否连接上WIFI；
若是，则将通话日志上传至服务器；
若否，则待连接上WIFI后，将通话日志上传至服务器。
从而，当连接上WIFI后再上传通话日志，能够为用户节省流量，减少金钱消耗。
如图2所示，为本发明提供的掉话测试方法的另一个实施例的流程示意图。
所述掉话测试方法，包括以下步骤：
步骤201：启动通话；
步骤202：持续监测协议栈底层的物理层的误码率；
步骤203：判断误码率是否高于预设的误码率阈值(Vcrc)且持续时间超过预设的第一时间阈值；
步骤204：若是，则判定发生掉话危险事件(协议栈上报上层的通话模块)；
步骤205：若否，则判定没有发生掉话危险事件，并返回步骤202，继续监测物理层的误码率；
步骤206：基于所述掉话危险事件，开始记录通话日志；
步骤207：继续监测物理层的误码率；
步骤208：在记录通话日志的过程中，判断误码率是否在某一时刻低于所述误码率阈值且持续时间超过预设的第二时间阈值；
步骤209：若是，则停止记录通话日志；
步骤210：删除已经记录的通话日志，并返回步骤202，继续监测物理层的误码率；
步骤211：若否，继续记录通话日志；
步骤212：判断通话是否异常结束；
步骤213：若否，则停止记录通话日志，并删除已记录的通话日志；
步骤214：若是，则保存已经记录的通话日志；
步骤215：判断是否连接上WIFI；
步骤216：若是，则将通话日志上传至服务器；
步骤217：若否，则手动连接WIFI，待连接上WIFI后，将通话日志上传至服务器。
从上述实施例可以看出，本发明提供的掉话测试方法，通过监测通话过程中物理层的误码率来实现自动抓取掉话通话日志(LOG)并上传服务器，从而用户或测试人员只需正常使用手机，就能自动在终端中完成整个抓取和上传过程；并且，通过根据误码率监控结果进行测试，终端只会在掉话的通话中抓取通话日志，而不会产生大量无效的通话日志占用终端的存储空间；因为有误码率作为依据， 因此一旦出现掉话，因在掉话之前已经开始记录，降低了错失现场的几率；同时，自动发送通话日志到服务器，有利于统计和进一步分析。此外，还通过持续监测误码率来判断通话是否回归正常水平，若是则停止记录LOG并删除已记录的LOG，从而节省了存储空间，同时，还通过判断是否连接上WIFI来确定是否上传LOG，从而为用户节约了流量。
本发明的第二个方面，提供了一种能够及时抓取LOG并统计掉话数据，且不会占用过多的空间的掉话测试装置。如图3所示，为本发明提供的掉话测试装置实施例的模块结构示意图。
所述掉话测试装置，包括：
通话启动模块301，用于启动通话；即移动终端开启并进入了通话模式；
误码率监测模块302，用于持续监测物理层的误码率；
误码率(SER：symbol error rate)是衡量数据在规定时间内数据传输精确性的指标。误码率＝传输中的误码/所传输的总码数*100％。如果有误码就有误码率。误码的产生是由于在信号传输中，衰变改变了信号的电压，致使信号在传输中遭到破坏，产生误码。噪音、交流电或闪电造成的脉冲、传输设备故障及其他因素都会导致误码率(比如传送的信号是1，而接收到的是0；反之亦然)。由于种种原因，数字信号在传输过程中不可避免地会产生差错。例如在传输过程中受到外界的干扰，或在通信***内部由于各个组成部分的质量不够理想而使传送的信号发生畸变等。当受到的干扰或信号畸变达到一定程度时，就会产生差错。误比特率(BER：bit error rate)是衡量数据在规定时间内数据传输精确性的指标。误码率＝错误码元数/传输总码元数。误比特率＝错误比特数/传输总比特数。误码率/误比特率是最常用的数据通信传输质量指标。它表示数字***传输质量的式是“在多少位数据中出现一位差错”；
掉话危险判定模块303，当误码率高于预设的误码率阈值(Vcrc)且持续时间超过预设的第一时间阈值(Tcrc)时，用于判定发生掉话危险事件；即，此种情况下，很有可能将会发生掉话的危险；所述误码率阈值，是根据不同的通信信号来分别设置的，如GSM、3G、4G信号，对应的误码率阈值不尽相同，且需要根据具体情况具体设置；同样的，所述第一时间阈值，也需要根据不同的具体情况 进行不同的具体设置；
日志记录模块304，用于基于所述掉话危险事件，开始记录通话日志；即，此时开启记录日志的功能，开始实时记录通话日志，以期把即将发生的掉话事件记录在LOG中；
日志保存模块305，当通话异常结束时，用于保存通话日志；
日志上传模块306，当通话异常结束时，用于将保存的通话日志上传至服务器，供研发人员对掉话事件的原因进行研究。
从上述实施例可以看出，本发明提供的掉话测试装置，通过监测通话过程中物理层的误码率来实现自动抓取掉话通话日志(LOG)并上传服务器，从而用户或测试人员只需正常使用手机，就能自动在终端中完成整个抓取和上传过程；并且，通过根据误码率监控结果进行测试，终端只会在掉话的通话中抓取通话日志，而不会产生大量无效的通话日志占用终端的存储空间；因为有误码率作为依据，因此一旦出现掉话，因在掉话之前已经开始记录，降低了错失现场的几率；此外，自动发送通话日志到服务器，有利于统计和进一步分析。
进一步的，在一些可选实施方式中，所述误码率监测模块302，还用于继续监测物理层的误码率；
在记录通话日志的过程中，若误码率在某一时刻低于所述误码率阈值，所述日志记录模块304，还用于停止记录通话日志。
或者，进一步的，在另一些可选实施方式中，所述误码率监测模块302，还用于继续监测物理层的误码率；
在记录通话日志的过程中，若误码率在某一时刻低于所述误码率阈值且持续时间超过预设的第二时间阈值，所述日志记录模块304，还用于停止记录通话日志。
通过上述两种方式，使得在通话进入正常状态时，停止记录通话日志，从而节省了终端的存储空间，以避免过多地记录不需要的通话日志。
更进一步的，在一些可选实施方式中，所述的装置还包括日志删除模块307，所述日志记录模块304停止记录通话日志后，所述日志删除模块307用于删除已经记录的通话日志。
通过在停止记录通话日志后删除已经记录的通话日志，从而可以将不需要的通话日志进行清理，节省终端的存储空间。
由于通话日志所占的存储空间较大，因此，在一些较佳实施例中，所述的装置还包括WIFI连接判定模块308，用于判断是否连接上WIFI；
若是，则所述日志上传模块306用于将通话日志上传至服务器；
若否，则待连接上WIFI后，所述日志上传模块306用于将通话日志上传至服务器。
从而，当连接上WIFI后再上传通话日志，能够为用户节省流量，减少金钱消耗。
下面结合图2所示，介绍本发明提供的掉话测试装置如何应用与本发明提供的掉话测试方法的另一个实施例。
所述掉话测试方法，包括以下步骤：
步骤201：通话启动模块301启动通话；
步骤202：误码率监测模块302持续监测协议栈底层的物理层的误码率；
步骤203：误码率监测模块302判断误码率是否高于预设的误码率阈值(Vcrc)且持续时间超过预设的第一时间阈值；
步骤204：若是，则掉话危险判定模块303判定发生掉话危险事件(协议栈上报上层的通话模块)；
步骤205：若否，则掉话危险判定模块303判定没有发生掉话危险事件，并返回步骤202，误码率监测模块302继续监测物理层的误码率；
步骤206：日志记录模块304基于所述掉话危险事件，开始记录通话日志；
步骤207：误码率监测模块302继续监测物理层的误码率；
步骤208：在记录通话日志的过程中，误码率监测模块302判断误码率是否在某一时刻低于所述误码率阈值且持续时间超过预设的第二时间阈值；
步骤209：若是，则日志记录模块304停止记录通话日志；
步骤210：日志删除模块307删除已经记录的通话日志，并返回步骤202，误码率监测模块302继续监测物理层的误码率；
步骤211：若否，日志记录模块304继续记录通话日志；
步骤212：通话模块309判断通话是否异常结束；
步骤213：若否，则日志记录模块304停止记录通话日志，日志删除模块307删除已记录的通话日志；
步骤214：若是，则日志保存模块305保存已经记录的通话日志；
步骤215：WIFI连接判定模块308判断是否连接上WIFI；
步骤216：若是，则日志上传模块306将通话日志上传至服务器；
步骤217：若否，则手动连接WIFI，待连接上WIFI后，日志上传模块306将通话日志上传至服务器。
从上述实施例可以看出，本发明提供的掉话测试装置，通过监测通话过程中物理层的误码率来实现自动抓取掉话通话日志(LOG)并上传服务器，从而用户或测试人员只需正常使用手机，就能自动在终端中完成整个抓取和上传过程；并且，通过根据误码率监控结果进行测试，终端只会在掉话的通话中抓取通话日志，而不会产生大量无效的通话日志占用终端的存储空间；因为有误码率作为依据，因此一旦出现掉话，因在掉话之前已经开始记录，降低了错失现场的几率；同时，自动发送通话日志到服务器，有利于统计和进一步分析。此外，还通过持续监测误码率来判断通话是否回归正常水平，若是则停止记录LOG并删除已记录的LOG，从而节省了存储空间，同时，还通过判断是否连接上WIFI来确定是否上传LOG，从而为用户节约了流量。
本发明实施例还提供一种计算机存储介质，其中，该计算机存储介质可存储有程序，该程序执行时可实现图1-图2所示实施例提供的掉话测试方法的各实现方式中的部分或全部步骤。
所属领域的普通技术人员应当理解：以上任何实施例的讨论仅为示例性的，并非旨在暗示本公开的范围(包括权利要求)被限于这些例子；在本发明的思路下，以上实施例或者不同实施例中的技术特征之间也可以进行组合，并存在如上所述的本发明的不同方面的许多其它变化，为了简明它们没有在细节中提供。因此，凡在本发明的精神和原则之内，所做的任何省略、修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (10)

  1. 一种掉话测试方法，其特征在于，包括：
    启动通话；
    持续监测物理层的误码率；
    若误码率高于预设的误码率阈值且持续时间超过预设的第一时间阈值，则判定发生掉话危险事件；
    基于所述掉话危险事件，开始记录通话日志；
    若通话异常结束，则保存通话日志并将其上传至服务器。
  2. 根据权利要求1所述的方法，其特征在于，所述开始记录通话日志的步骤之后还包括：
    继续监测物理层的误码率；
    在记录通话日志的过程中，若误码率在某一时刻低于所述误码率阈值，则停止记录通话日志。
  3. 根据权利要求1所述的方法，其特征在于，所述开始记录通话日志的步骤之后还包括：
    继续监测物理层的误码率；
    在记录通话日志的过程中，若误码率在某一时刻低于所述误码率阈值且持续时间超过预设的第二时间阈值，则停止记录通话日志。
  4. 根据权利要求2或3所述的方法，其特征在于，所述停止记录通话日志的步骤之后还包括：
    删除已经记录的通话日志。
  5. 根据权利要求1所述的方法，其特征在于，所述保存通话日志的步骤之后还包括：
    判断是否连接上WIFI；
    若是，则将通话日志上传至服务器；
    若否，则待连接上WIFI后，将通话日志上传至服务器。
  6. 一种掉话测试装置，其特征在于，包括：
    通话启动模块，用于启动通话；
    误码率监测模块，用于持续监测物理层的误码率；
    掉话危险判定模块，当误码率高于预设的误码率阈值且持续时间超过预设的第一时间阈值时，用于判定发生掉话危险事件；
    日志记录模块，用于基于所述掉话危险事件，开始记录通话日志；
    日志保存模块，当通话异常结束时，用于保存通话日志；
    日志上传模块，当通话异常结束时，用于将保存的通话日志上传至服务器。
  7. 根据权利要求6所述的装置，其特征在于，所述误码率监测模块，还用于继续监测物理层的误码率；
    在记录通话日志的过程中，若误码率在某一时刻低于所述误码率阈值，所述日志记录模块，还用于停止记录通话日志。
  8. 根据权利要求6所述的装置，其特征在于，所述误码率监测模块，还用于继续监测物理层的误码率；
    在记录通话日志的过程中，若误码率在某一时刻低于所述误码率阈值且持续时间超过预设的第二时间阈值，所述日志记录模块，还用于停止记录通话日志。
  9. 根据权利要求7或8所述的装置，其特征在于，还包括日志删除模块，
    所述日志记录模块停止记录通话日志后，所述日志删除模块用于删除已经记录的通话日志。
  10. 根据权利要求6所述的装置，其特征在于，还包括WIFI连接判定模块，用于判断是否连接上WIFI；
    若是，则所述日志上传模块用于将通话日志上传至服务器；
    若否，则待连接上WIFI后，所述日志上传模块用于将通话日志上传至 服务器。
PCT/CN2016/089252 2015-12-08 2016-07-07 掉话测试方法及装置 WO2017096878A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/240,901 US20170163800A1 (en) 2015-12-08 2016-08-18 Methods and electronic device for testing call drop

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510898098.1A CN105873094A (zh) 2015-12-08 2015-12-08 掉话测试方法及装置
CN201510898098.1 2015-12-08

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/240,901 Continuation US20170163800A1 (en) 2015-12-08 2016-08-18 Methods and electronic device for testing call drop

Publications (1)

Publication Number Publication Date
WO2017096878A1 true WO2017096878A1 (zh) 2017-06-15

Family

ID=56624460

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/089252 WO2017096878A1 (zh) 2015-12-08 2016-07-07 掉话测试方法及装置

Country Status (2)

Country Link
CN (1) CN105873094A (zh)
WO (1) WO2017096878A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107948447B (zh) * 2017-12-21 2021-02-19 中国联合网络通信集团有限公司 掉话率检测方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1864157A (zh) * 2003-05-08 2006-11-15 国际商业机器公司 自主记日志支持
CN102065458A (zh) * 2010-02-09 2011-05-18 熊文俊 基于用户通话行为的移动网络质量测试方法及***
CN102724565A (zh) * 2012-05-30 2012-10-10 宇龙计算机通信科技(深圳)有限公司 一种移动终端异常信号处理方法及装置
CN103458454A (zh) * 2012-05-31 2013-12-18 北京鼹鼠科技发展有限公司 一种基于安卓***的通信终端掉话测试方法和测试装置
CN104268055A (zh) * 2014-09-01 2015-01-07 腾讯科技（深圳）有限公司 一种程序异常的监控方法和装置
CN104735697A (zh) * 2015-03-09 2015-06-24 惠州Tcl移动通信有限公司 一种基于at指令的移动终端自动化呼叫场测方法及***

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100531254C (zh) * 2005-08-12 2009-08-19 华为技术有限公司 掉话故障信息的上报方法、装置及掉话故障原因定位***
CN101378577B (zh) * 2008-09-27 2012-07-04 华为技术有限公司 一种链路故障检测的方法和***
CN101715213B (zh) * 2009-11-24 2013-08-07 中兴通讯股份有限公司 一种通话优化处理方法和***
CN104469654A (zh) * 2013-09-18 2015-03-25 中兴通讯股份有限公司 一种内部通信的切换方法和装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1864157A (zh) * 2003-05-08 2006-11-15 国际商业机器公司 自主记日志支持
CN102065458A (zh) * 2010-02-09 2011-05-18 熊文俊 基于用户通话行为的移动网络质量测试方法及***
CN102724565A (zh) * 2012-05-30 2012-10-10 宇龙计算机通信科技(深圳)有限公司 一种移动终端异常信号处理方法及装置
CN103458454A (zh) * 2012-05-31 2013-12-18 北京鼹鼠科技发展有限公司 一种基于安卓***的通信终端掉话测试方法和测试装置
CN104268055A (zh) * 2014-09-01 2015-01-07 腾讯科技（深圳）有限公司 一种程序异常的监控方法和装置
CN104735697A (zh) * 2015-03-09 2015-06-24 惠州Tcl移动通信有限公司 一种基于at指令的移动终端自动化呼叫场测方法及***

Also Published As

Publication number Publication date
CN105873094A (zh) 2016-08-17

Similar Documents

Publication Publication Date Title
EP3197097B1 (en) Multi kpi correlation in wireless protocols
US9420090B2 (en) Diagnostic methods for twisted pair telephone lines based on line data distribution analysis
CN103632680B (zh) 一种语音质量评估方法、网元及***
US20170207988A1 (en) Apparatus, System, and Method for Obtaining Quality of Service Parameter of Voice Over Internet Protocol Service
US20160241429A1 (en) Knowledge base radio and core network prescriptive root cause analysis
KR102126362B1 (ko) 비디오 품질을 결정하기 위한 방법과 장치, 및 네트워크 결함의 위치를 찾아내기 위한 방법과 장치
WO2022028120A1 (zh) 指标检测模型获取及故障定位方法、装置、设备及存储介质
US20150085115A1 (en) Systems and methods of measuring quality of video surveillance infrastructure
US10355810B1 (en) Method, device, and system for calibrating and adapting transmission rate in wireless communication
CN107667504A (zh) 使用回声定位进行用户体验质量的分析
WO2017096878A1 (zh) 掉话测试方法及装置
CN110493077B (zh) 802.11ax协议的延时丢包性能测试方法
JP2008306435A5 (zh)
JP5707309B2 (ja) 品質劣化判定装置及び方法
Mickulicz et al. Zephyr: First-person wireless analytics from high-density in-stadium deployments
KR101119848B1 (ko) 영상 입력 기기의 접속 장애 판별 장치 및 접속 장애 판별 방법
CN103634158B (zh) 一种snmp管理进程的压力测试方法和装置
US20170163800A1 (en) Methods and electronic device for testing call drop
JP6666872B2 (ja) 情報処理装置、情報処理方法およびプログラム
CN112929228B (zh) 带宽测试方法及用户设备、存储装置
CN112486009B (zh) 一种授时信号异常波形记录分析仪及方法
CN111372071B (zh) 一种搜集视频图像异常信息的方法及装置
EP3528408B1 (en) Method, device, and system for calibrating and adapting transmission rate in wireless communication
KR20130099671A (ko) 네트워크 품질을 진단하는 단말기 및 단말에서의 네트워크 품질 진단 방법
CN112822029A (zh) 一种可阻挡外界信号的录音采集方法、模块和装置

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: 16872078

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: 16872078

Country of ref document: EP

Kind code of ref document: A1