CN111901471B - Drive test system and method for non-root android mobile phone - Google Patents
Drive test system and method for non-root android mobile phone Download PDFInfo
- Publication number
- CN111901471B CN111901471B CN202010638791.6A CN202010638791A CN111901471B CN 111901471 B CN111901471 B CN 111901471B CN 202010638791 A CN202010638791 A CN 202010638791A CN 111901471 B CN111901471 B CN 111901471B
- Authority
- CN
- China
- Prior art keywords
- mobile phone
- drive test
- signaling data
- data acquisition
- test software
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/24—Arrangements for testing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
- H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/14—Direct-mode setup
Abstract
The application relates to a drive test system and a drive test method for a non-root android mobile phone. Wherein the system comprises: a mobile phone end and a PC end which are mutually communicated and connected; the mobile phone end is a non-root android mobile phone to be subjected to drive test; the mobile phone end is provided with drive test software, and the PC end comprises a Windows system agent library and is provided with a data acquisition client based on a Windows system; the data acquisition client is used for acquiring signaling data of the mobile phone terminal by using the Windows system agent library and sending the acquired signaling data to the drive test software; the drive test software is used for processing the received signaling data, thereby completing the drive test of the mobile phone terminal. According to the setting, for the non-root android mobile phone, a mobile phone manufacturer is not required to provide an android system agent library in time, and the mobile phone can be subjected to drive test only by the Windows system agent library, so that a drive test product can be put into the market in time.
Description
Technical Field
The application relates to the technical field of communication, in particular to a drive test system and a drive test method for a non-root android mobile phone.
Background
When a new type of android (android) mobile phone comes into the market, Drive Test (DT) is generally performed on the mobile phone, that is, signaling data (Drive Test data) is acquired on the mobile phone, and the method mainly aims at evaluating the quality of a mobile phone network, voice and the like.
At present, the android mobile phone is usually subjected to drive test in a form of installing drive test software APP on the android mobile phone to acquire mobile phone signaling data and decode, but this way requires the android mobile phone to obtain root permission (i.e. super administrator permission), otherwise, the drive test software APP cannot operate the mobile phone to acquire the signaling data. In this case, the existing solution for non-root android phones is to collect signaling data through a proxy library under the android system. However, some mobile phone manufacturers only provide the agent library under the Windows system, but not the agent library under the android system, and thus, the signaling data acquisition cannot be realized at this time.
That is to say, for a non-root android mobile phone at present, if a manufacturer does not provide an agent library under an android system, the mobile phone cannot be subjected to drive test through mobile phone drive test software.
Disclosure of Invention
The application provides a drive test system and method for a non-root android mobile phone, which aim to solve the problem that the drive test of the non-root android mobile phone can not be carried out on the mobile phone through mobile phone drive test software when an agent library under the android system is not available.
The above object of the present application is achieved by the following technical solutions:
in a first aspect, an embodiment of the present application provides a drive test system for a non-root android mobile phone, including:
a mobile phone end and a PC end which are mutually communicated and connected; the mobile phone end is a non-root android mobile phone to be subjected to drive test;
the mobile phone end is provided with drive test software, and the PC end comprises a Windows system agent library and is provided with a data acquisition client based on a Windows system;
the data acquisition client is used for acquiring signaling data of the mobile phone terminal by using the Windows system agent library and sending the acquired signaling data to the drive test software;
and the drive test software is used for processing the received signaling data so as to complete the drive test of the mobile phone terminal.
Optionally, the mobile phone end and the PC end are connected by a data line, the PC end is further provided with an ADB tool of an android debug bridge, and the mobile phone end and the PC end establish communication in an ADB forward interactive mode based on the ADB tool.
Optionally, the mobile phone end and the PC end both include bluetooth adapters and are connected in a pairing manner, so that the mobile phone end and the PC end establish communication in a bluetooth manner.
Optionally, the drive test software is a Walktour APP.
Optionally, the data acquisition client is a small box client.
In a second aspect, an embodiment of the present application further provides a drive test method for a non-root android mobile phone, where the non-root android mobile phone to be subjected to drive test is used as a mobile phone end and is in communication connection with a PC end in advance, the mobile phone end is installed with drive test software, the PC end includes a Windows system agent library and is installed with a data acquisition client based on a Windows system, and the method includes:
the data acquisition client acquires the signaling data of the mobile phone terminal by using the Windows system agent library and sends the acquired signaling data to the drive test software;
and the drive test software processes the received signaling data so as to complete the drive test of the mobile phone terminal.
Optionally, the mobile phone end and the PC end are connected by a data line, and the PC end is further provided with an android debug bridge ADB tool; and the mobile phone end and the PC end establish communication in an ADB forward interactive mode of the ADB tool.
Optionally, the specific process of establishing communication between the mobile phone end and the PC end based on the adb forward interactive manner includes:
when the fact that the mobile phone end is connected through a data line is detected, the ADB tool creates a Socket client at the PC end, and creates a Socket server at the mobile phone end, and therefore Socket communication is established between the mobile phone end and the PC end on the basis of the Socket client and the Socket server.
Optionally, the specific process of the data acquisition client acquiring the signaling data of the mobile phone end by using the Windows system agent library and sending the acquired signaling data to the drive test software includes:
and the data acquisition client receives a data acquisition instruction sent by the drive test software, calls the Windows system agent library according to the data acquisition instruction, and establishes connection with a trace interface of the mobile phone terminal so as to acquire signaling data and send the acquired signaling data to the drive test software through Socket communication.
Optionally, the mobile phone end and the PC end both include bluetooth adapters and are connected in a pairing manner, so that the mobile phone end and the PC end establish communication in a bluetooth manner.
The technical scheme provided by the embodiment of the application can have the following beneficial effects:
according to the technical scheme, the non-root android mobile phone to be subjected to the drive test is used as a mobile phone end to be in communication connection with a PC end, drive test software is installed on the mobile phone end, the PC end comprises a Windows system agent library, and a data acquisition client based on a Windows system is installed on the PC end, so that the data acquisition client can acquire signaling data of the mobile phone end by using the Windows system agent library and sends the acquired signaling data to the drive test software, and finally the drive test software processes the signaling data, and then the drive test of the non-root android mobile phone is completed. That is to say, for a non-root android mobile phone, a mobile phone manufacturer is not required to provide an android system agent library in time, and the mobile phone can be subjected to drive test only by the Windows system agent library, so that a drive test product can be put into the market in time.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
Fig. 1 is a schematic structural diagram of a drive test system for a non-root android mobile phone according to an embodiment of the present application;
fig. 2 is a schematic flow chart of a drive test method for a non-root android mobile phone according to an embodiment of the present application;
fig. 3 is a schematic view of an actual application flow of a drive test system for a non-root android mobile phone according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. The following description refers to the accompanying drawings in which the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the application, as detailed in the appended claims.
At present, the android mobile phone is usually subjected to drive test in a form of installing drive test software APP on the android mobile phone to acquire and decode mobile phone signaling data, but in this way, the android mobile phone needs to obtain root permission (namely, super administrator permission), otherwise, the drive test software APP cannot operate the mobile phone to acquire the signaling data.
In this case, the existing solution for the non-root android phone is to collect signaling data through a proxy library in the android system, where the proxy library is an interface library function, and in the computer system, a program can directly call an interface to implement functions corresponding to the interface, such as establishing connection, obtaining data, and the like.
However, some mobile phone manufacturers, for example, hua ye, usually only provide the agent library under the Windows system, but not provide the agent library under the android system, and in this case, the signaling data acquisition cannot be realized.
In order to solve the above problem, an embodiment of the present application provides a drive test system for a non-root android mobile phone and a drive test method of the system, so as to implement a drive test for a non-root android mobile phone without an android system agent library based on mobile phone drive test software. The scheme of the present application will be described in detail by examples below.
Examples
Referring to fig. 1, fig. 1 is a schematic structural diagram of a drive test system for a non-root android mobile phone according to an embodiment of the present application. As shown in fig. 1, the system integrally comprises a mobile phone end and a PC end, wherein the mobile phone end and the PC end are in communication connection with each other, and the mobile phone end is a non-root android mobile phone to be subjected to drive test. And the mobile phone end is provided with drive test software, and the PC end comprises a Windows system agent library and is provided with a data acquisition client based on a Windows system.
The data acquisition client is used for acquiring signaling data of the mobile phone terminal by using the Windows system agent library (the principle is that the mobile phone can be driven and operated by the mobile phone in a Windows system), and transmitting the acquired signaling data to the drive test software; the drive test software is used for processing the received signaling data, thereby completing the drive test of the mobile phone terminal.
As a feasible implementation manner, the mobile phone end and the PC end may be connected to each other through a data line to perform data exchange, and further, the data exchange process may be implemented based on an ADB (Android Debug Bridge) tool installed at the PC end, and communication may be established based on an ADB forward interaction manner in the ADB tool.
More specifically, with reference to fig. 1, a specific process of establishing communication based on an adb forward interactive manner includes: when the PC end detects that the mobile phone end is connected to the USB interface through the data line, the ADB tool creates a Socket client at the PC end (particularly in the data acquisition client) and creates a Socket server at the mobile phone end (particularly in the drive test software), so that Socket communication is established between the mobile phone end and the PC end based on the Socket client and the Socket server. Wherein the principle of adb forward is as follows: firstly, port forwarding is carried out by using adb forward tcp:8888tcp: 9999; then, a mobile phone (Server) end establishes a Server socket monitoring 9999 port; meanwhile, the PC side establishes a Socket and is connected with a Serversocket through an 8888 port. As can be seen, Socket communication is actually a TCP (Transmission Control Protocol) connection.
In some embodiments, the drive test software is preferably a walker APP, and the data collection client is preferably a small box client (i.e., Caddy client).
In addition, in some embodiments, in addition to the ADB forward exchange mode implemented based on the ADB tool, the mobile phone end and the PC end may establish communication based on a bluetooth mode to perform data exchange. At this moment, both the mobile phone end and the PC end need to contain the Bluetooth adapters, and the Bluetooth adapters of the mobile phone end and the PC end need to be connected in a matching mode. The advantages and disadvantages of the interactive mode of the Bluetooth mode and the adb forward are as follows: the method for realizing the interaction between the mobile phone end and the PC end by using ADB forward is more convenient and stable than that by using a Bluetooth mode, has low requirement on the hardware of the PC end, and only needs to install an ADB tool in a PC end program, but physically needs to connect the mobile phone end and the PC end through a data line; the bluetooth mode has the advantage of wireless connection, and therefore can be used in some cases.
According to the technical scheme, the non-root android mobile phone to be subjected to the drive test is used as a mobile phone end to be in communication connection with a PC end, drive test software is installed on the mobile phone end, the PC end comprises a Windows system agent library, and a data acquisition client based on a Windows system is installed on the PC end, so that the data acquisition client can acquire signaling data of the mobile phone end by using the Windows system agent library, the acquired signaling data are sent to the drive test software, and finally the drive test software processes the signaling data, and then the drive test of the non-root android mobile phone is completed. That is to say, for a non-root android mobile phone, a mobile phone manufacturer is not required to provide an android system agent library in time, and the mobile phone can be subjected to drive test only by the Windows system agent library, so that a drive test product can be put into the market in time.
Based on the system and referring to fig. 2, the embodiment of the application further provides a drive test method for the non-root android mobile phone. As shown in fig. 2, the method comprises the steps of:
s201: the data acquisition client acquires the signaling data of the mobile phone terminal by using the Windows system agent library and sends the acquired signaling data to the drive test software;
specifically, if the Socket communication method is adopted, step S201: the specific process that the data acquisition client acquires the signaling data of the mobile phone terminal by using the Windows system agent library and sends the acquired signaling data to the drive test software comprises the following steps: the data acquisition client receives a data acquisition instruction sent by the drive test software, calls a Windows system proxy library according to the data acquisition instruction, and establishes connection with a trace interface of the mobile phone terminal so as to acquire signaling data and send the acquired signaling data to the drive test software through Socket communication. The data acquisition instruction may be triggered by the user operating the mobile phone drive test software, or may be automatically triggered by the drive test software according to a preset setting, which is not limited to this.
That is, because the data acquisition client is based on the Windows system, the data acquisition client can call an interface in a Windows system proxy library and establish connection with the mobile phone end, so that the mobile phone is driven and operated by the mobile phone, and then signaling data of the mobile phone end is acquired.
S202: and the drive test software processes the received signaling data so as to complete the drive test of the mobile phone terminal.
The processing of the signaling data by the drive test software includes conventional decoding and other processing, and reference may be made to related methods in the prior art.
In order to better explain the technical solution of the present application, the practical application process of the above system and method will be described below by a specific example.
Referring to fig. 3, fig. 3 is a schematic view of an actual application flow of a drive test system for a non-root android mobile phone according to an embodiment of the present application. It should be noted that in the system of this embodiment, the mobile phone end and the PC end perform data interaction in a Socket communication mode established in an adb forward interaction mode, the drive test software selects walker, and the data acquisition client selects a small box (Caddy) client.
As shown in fig. 3, the application process includes:
1) the mobile phone end and the PC end are connected through a data line, and the Walktour in the mobile phone end and the Caddy client in the PC end are started;
2) when a Caddy client in a PC (personal computer) end monitors that a mobile phone is connected with a serial port of the mobile phone, an ADB (ADB tool) tool creates a Socket client at the PC end, creates a Socket server at the mobile phone end, and broadcasts information such as an interface and the like so as to establish connection between the Socket client and the Socket server;
specifically, the Caddy client comprises a main process and a plurality of sub-processes, wherein the main process is responsible for monitoring the connection condition of the serial port, when the connection of the mobile phone is monitored, one sub-process is automatically created, and the ADB tool creates the Socket client in the sub-process. In addition, the Caddy client comprises a plurality of serial ports, so that a plurality of mobile phone ends are simultaneously connected, and the simultaneous acquisition of drive test data by a plurality of mobile phones can be realized based on the connection.
3) The method comprises the following steps that a mobile phone end sends information such as own equipment name to a Caddy client of a PC end through a Socket server, and the PC end sends information such as own IMEI to a Walktour of the mobile phone end through the Socket client;
4) a Caddy client in the PC terminal creates an equipment library according to the equipment name sent by the mobile phone terminal, and the equipment library is used for storing signaling data;
5) the mobile phone sends a control command to the Caddy client of the PC end through the Socket server, and the control command comprises the following steps: starting to collect signaling data, stopping to collect signaling data, powering off the mobile phone, powering on the mobile phone, locking the network of the mobile phone, requesting MOS scoring and the like.
6) The PC terminal executes corresponding operation or returns corresponding control commands based on the control commands sent by the mobile phone terminal, such as Walktour, response of an MOS score calculation request command, MOS score reporting and the like, which start to collect signaling data and send the signaling data to the mobile phone terminal;
7) the Walktour at the mobile phone end decodes the received signaling data and performs a drive test service test;
8) and after the test is finished, closing the drive test software Walktour, disconnecting the data line and the like.
Through the operation process, a user can acquire and test the drive test data of the non-root mobile phone, the condition that whether a mobile phone manufacturer can provide an android system agent library or not is not required, and the drive test can be performed on the mobile phone only by the Windows system agent library, so that a drive test product can be put into the market in time.
It is understood that the same or similar parts in the above embodiments may be mutually referred to, and the same or similar parts in other embodiments may be referred to for the content which is not described in detail in some embodiments.
It should be noted that, in the description of the present application, the terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Further, in the description of the present application, the meaning of "a plurality" means at least two unless otherwise specified.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried out in the method of implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and the program, when executed, includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.
Claims (7)
1. A drive test system for non-root android mobile phones is characterized by comprising:
a mobile phone end and a PC end which are mutually connected in a communication way; the mobile phone end is a non-root android mobile phone to be subjected to drive test;
the mobile phone end is provided with drive test software, and the PC end comprises a Windows system agent library and is provided with a data acquisition client based on a Windows system; the drive test software is a Walktour APP, and the data acquisition client is a small box client;
the data acquisition client is used for acquiring the signaling data of the mobile phone terminal by using the Windows system agent library and sending the acquired signaling data to the drive test software;
the drive test software is used for processing the received signaling data so as to complete the drive test of the mobile phone end;
the data acquisition client is used for acquiring the signaling data of the mobile phone terminal by using the Windows system agent library and sending the acquired signaling data to the drive test software, and the specific process comprises the following steps:
and the data acquisition client receives a data acquisition instruction sent by the drive test software, calls the Windows system agent library according to the data acquisition instruction, and establishes connection with a trace interface of the mobile phone terminal, so as to acquire signaling data and send the acquired signaling data to the drive test software through Socket communication.
2. The system of claim 1, wherein the mobile phone end and the PC end are connected through a data line, the PC end is further provided with an ADB (android debug bridge) tool, and the mobile phone end and the PC end establish communication in an ADB forward interactive mode of the ADB tool.
3. The system of claim 1, wherein the mobile phone end and the PC end each comprise a bluetooth adapter and are connected in a pairing manner, such that the mobile phone end and the PC end establish communication in a bluetooth manner.
4. A drive test method for a non-root android mobile phone is characterized in that the non-root android mobile phone to be subjected to drive test is used as a mobile phone end to be in communication connection with a PC end in advance, drive test software is installed at the mobile phone end, the PC end comprises a Windows system agent library and is provided with a data acquisition client based on a Windows system, the drive test software is Walktour APP, and the data acquisition client is a small box client; the method comprises the following steps:
the data acquisition client acquires the signaling data of the mobile phone terminal by using the Windows system agent library and sends the acquired signaling data to the drive test software;
the drive test software processes the received signaling data, so as to complete the drive test of the mobile phone end;
the data acquisition client is used for acquiring signaling data of the mobile phone terminal by using the Windows system agent library and sending the acquired signaling data to the drive test software, and the specific process comprises the following steps:
and the data acquisition client receives a data acquisition instruction sent by the drive test software, calls the Windows system agent library according to the data acquisition instruction, and establishes connection with a trace interface of the mobile phone terminal, so as to acquire signaling data and send the acquired signaling data to the drive test software through Socket communication.
5. The method according to claim 4, wherein the mobile phone end and the PC end are connected through a data line, and an ADB (android debug bridge) tool is further installed at the PC end; and the mobile phone end and the PC end establish communication in an ADB forward interactive mode of the ADB tool.
6. The method according to claim 5, wherein the specific process of establishing communication between the mobile phone end and the PC end based on an adb forward interactive mode comprises the following steps:
when the fact that the mobile phone end is connected through a data line is detected, the ADB tool creates a Socket client at the PC end, and creates a Socket server at the mobile phone end, and therefore Socket communication is established between the mobile phone end and the PC end on the basis of the Socket client and the Socket server.
7. The method according to claim 4, wherein the mobile phone terminal and the PC terminal both comprise Bluetooth adapters and are connected in pairs, so that the mobile phone terminal and the PC terminal establish communication in a Bluetooth manner.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010638791.6A CN111901471B (en) | 2020-07-06 | 2020-07-06 | Drive test system and method for non-root android mobile phone |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010638791.6A CN111901471B (en) | 2020-07-06 | 2020-07-06 | Drive test system and method for non-root android mobile phone |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111901471A CN111901471A (en) | 2020-11-06 |
| CN111901471B true CN111901471B (en) | 2022-06-17 |
Family
ID=73191635
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010638791.6A Active CN111901471B (en) | 2020-07-06 | 2020-07-06 | Drive test system and method for non-root android mobile phone |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111901471B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102546825A (en) * | 2012-02-20 | 2012-07-04 | 大唐移动通信设备有限公司 | Remote monitoring method and device for automatic drive test system |
| CN103581953A (en) * | 2012-07-19 | 2014-02-12 | 珠海世纪鼎利通信科技股份有限公司 | Association method for wireless drive test data and signaling monitoring data |
| WO2015054689A1 (en) * | 2013-10-11 | 2015-04-16 | Mte Corporation | Adjustable integrated combined common mode and differential mode three phase inductors and methods of manufacture and use thereof |
| CN105611507A (en) * | 2016-01-06 | 2016-05-25 | 东华大学 | Mobile network optimization data collection method based on Android terminal |
| CN106657028A (en) * | 2016-12-02 | 2017-05-10 | 杭州字节信息技术有限公司 | Implementation method of Android mobile phone data encryption export technology |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104239202A (en) * | 2013-06-09 | 2014-12-24 | 刘伟 | Non-Root testing method and system of interactive intelligent equipment |
| CN104391695B (en) * | 2014-11-06 | 2017-11-24 | 北京凌阳益辉科技有限公司 | A kind of method and its device that control is synchronized by external equipment |
| CN106547687A (en) * | 2016-10-14 | 2017-03-29 | 深圳前海微众银行股份有限公司 | Application testing method, apparatus and system |
| CN106961357B (en) * | 2017-04-28 | 2021-01-12 | 西安海润通信技术有限公司 | Internet service packet capturing and fault positioning method based on non-root android terminal |
| CN107656866B (en) * | 2017-09-06 | 2020-11-27 | 厦门美图移动科技有限公司 | Method for testing application fluency, mobile terminal and computing device |
-
2020
- 2020-07-06 CN CN202010638791.6A patent/CN111901471B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102546825A (en) * | 2012-02-20 | 2012-07-04 | 大唐移动通信设备有限公司 | Remote monitoring method and device for automatic drive test system |
| CN103581953A (en) * | 2012-07-19 | 2014-02-12 | 珠海世纪鼎利通信科技股份有限公司 | Association method for wireless drive test data and signaling monitoring data |
| WO2015054689A1 (en) * | 2013-10-11 | 2015-04-16 | Mte Corporation | Adjustable integrated combined common mode and differential mode three phase inductors and methods of manufacture and use thereof |
| CN105611507A (en) * | 2016-01-06 | 2016-05-25 | 东华大学 | Mobile network optimization data collection method based on Android terminal |
| CN106657028A (en) * | 2016-12-02 | 2017-05-10 | 杭州字节信息技术有限公司 | Implementation method of Android mobile phone data encryption export technology |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111901471A (en) | 2020-11-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4575418B2 (en) | How to manage mobile stations with radio waves | |
| US7324815B2 (en) | Remote interaction with a wireless device resident diagnostic interface across a wireless network | |
| CN104980215A (en) | System and method for achieving WiFi configuration of intelligent equipment based on optical signal transmission | |
| EP2320328B1 (en) | Operation mode switching of data card and its control method, device and data card | |
| CN110012527B (en) | Awakening method and electronic equipment | |
| CN113746821B (en) | Intelligent device control method and device, storage medium and electronic device | |
| US20170280410A1 (en) | Method, device and system for implementing information self-registration, and computer storage medium | |
| CN106416196B (en) | Mobile terminal, power adapter and upgrading method thereof | |
| CN104684015B (en) | Plant maintenance method and apparatus | |
| CN111901471B (en) | Drive test system and method for non-root android mobile phone | |
| CN110853323A (en) | Upgrading method and device for remote control equipment | |
| CN116546467A (en) | Access control method and system of vehicle-mounted equipment, storage medium and electronic device | |
| KR101104048B1 (en) | Radio device testing system | |
| CN112867044A (en) | Base station simulation test terminal, test method and device | |
| CN112866980A (en) | Pre-authentication 4G communication module and firmware upgrading method thereof | |
| CN109831767A (en) | A kind of Bluetooth connecting method and system of intelligence wearable device | |
| CN106375603B (en) | System for connecting wireless earphone and network phone based on switch adapter and control method thereof | |
| CN110532012B (en) | Distributed system software upgrading method and device | |
| JP2005184294A (en) | Portable terminal tester | |
| TWI681686B (en) | Judgment method of connecting router and machine control system | |
| CN112492555A (en) | Control instruction processing method and device | |
| CN107248935B (en) | System and method for network management to discover and monitor network elements | |
| US20210359916A1 (en) | Communication apparatus, control method for controlling communication apparatus, and storage medium | |
| CN107710681B (en) | Method and apparatus for upgrading multi-dwelling unit | |
| CN111432392B (en) | Method for improving input stability of Bluetooth human-computer interaction equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |