CN103744761B - Method and system for controlling multiple mobile terminals to automatically execute tasks - Google Patents
Method and system for controlling multiple mobile terminals to automatically execute tasks Download PDFInfo
- Publication number
- CN103744761B CN103744761B CN201410027603.0A CN201410027603A CN103744761B CN 103744761 B CN103744761 B CN 103744761B CN 201410027603 A CN201410027603 A CN 201410027603A CN 103744761 B CN103744761 B CN 103744761B
- Authority
- CN
- China
- Prior art keywords
- task
- mobile terminal
- terminal
- entity
- test
- 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.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 31
- 238000012360 testing method Methods 0.000 claims abstract description 108
- 238000012790 confirmation Methods 0.000 claims abstract description 3
- 230000005540 biological transmission Effects 0.000 claims description 14
- 238000013507 mapping Methods 0.000 claims description 8
- 230000001419 dependent effect Effects 0.000 claims description 7
- 206010048669 Terminal state Diseases 0.000 claims description 3
- 238000004891 communication Methods 0.000 claims description 3
- 235000013399 edible fruits Nutrition 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 238000010276 construction Methods 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 210000004247 hand Anatomy 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Abstract
The invention discloses a method and a system for controlling multiple mobile terminals to automatically execute tasks. When the method and the system are applied to automatic testing of cellphones, multiple cellphones can be controlled to simultaneously execute different tasks by setting a single thread for each cellphone in connection with a computer at a computer side and establishing corresponding task entities for tasks needed to be executed, so that execution time of automatic testing is greatly reduced, and testing efficiency is effectively improved; through a comprehensive mechanism for task execution result confirmation and re-execution, accuracy of testing results can be improved greatly, smoothness of automatic testing is greatly guaranteed, and the problem of testing interrupt caused by various abnormities in the process of testing is effectively solved.
Description
Technical field
The present invention relates to a kind of method and system controlling multiple stage mobile terminal automatically to execute task.
Background technology
With the popularization of mobile terminal, people also get more and more to the demand of mobile terminal, more and more higher.For mobile whole
For the manufacturer of end, mobile terminal（As smart mobile phone）Test also become increasingly complex, occur that increasing therewith
Automated test tool.But make a general survey of the automated test tool on market, single thread can only execute test assignment, can only make every time
One smart mobile phone executes a task, so that the time of test is longer, efficiency comparison is low.
Content of the invention
In order to overcome deficiency of the prior art, the present invention provides a kind of control multiple stage mobile terminal automatically to execute task
Method and test terminal, to improve efficiency and the test accuracy rate of test.
The present invention is achieved by the following technical solutions：
A kind of method controlling multiple stage mobile terminal automatically to execute task, methods described includes：
S1, multiple stage mobile terminal is connected with test terminal, test terminal obtains the device name of each mobile terminal, sets up
Port mapping, and build mobile terminal entity, described mobile terminal entity is used for recording the relevant information of each mobile terminal；
S2, each mobile terminal for being connected with test terminal foundation arrange a single thread, and described thread is used for
Detect corresponding mobile terminal and execution task；
S3, acquisition need the task of execution, and respectively each single task builds a Task entity, and each task is real
Body adds to task queue, and described Task entity is used for recording the relevant information of each task；
S4, take out corresponding task from task queue, and distributed transmission to each mobile terminal；
S5, each mobile terminal execute corresponding task, and the standby communication terminal end such as test terminal returns implementing result；
S6, finish when all tasks in task queue are all performed, it is simultaneously that it is defeated that implementing result is collected in test terminal
Go out.
Further, described step S5 also includes：
If a certain task of S51 mobile terminal successful execution, implementing result is back to test terminal, test terminal connects
Receive implementing result and take out the distribution transmission of next task from task queue to this mobile terminal, if the unsuccessful execution of mobile terminal
A certain task, then be back to test terminal by implementing result, and test terminal receives implementing result and sends dependent instruction, makes this shifting
Dynamic terminal re-executes this task；
If S52 re-executes this Mission Success, test terminal updates implementing result, and under taking-up from task queue
One task distribution sends to this mobile terminal；If re-executing this mission failure, mark re-executes this mission failure, test
Terminal changes execution status of task, takes out the distribution of next task and sends to this mobile terminal, will indicate simultaneously from task queue
At the position of pending task that the task of re-executing failure is added to task queue.
Preferably, in described step S52, in re-executing task process, if the number of times repeating a certain task surpasses
Cross preset value, ability mark re-executes this mission failure, execution status of task is changed in test terminal；Treating in described task queue
It is preferably the most end end position of task queue at the position of execution task；Described test terminal is computer, described mobile end
Hold as mobile phone.
It is preferred that the relevant information of each mobile terminal of described mobile terminal entity record includes the mobile end of each mobile terminal
End title, connection end slogan, whether set up with test terminal be connected and mobile terminal working condition in one or more
Information；The relevant information of each task of described Task entity record include each task mission number, be performed number of times and by
Executory one or more information of any platform mobile terminal.
Based on foregoing invention design, present invention also offers a kind of control multiple stage mobile terminal automatically execute task be
System, it is applied in test terminal, and described system includes：
Mobile terminal entity builds module, and for being connected with test terminal when multiple stage mobile terminal, test terminal obtains each
After the device name of mobile terminal, set up port mapping and build mobile terminal entity, described mobile terminal entity is used for recording
The relevant information of each mobile terminal；
Thread setup module, for arranging a single line for setting up each mobile terminal being connected with test terminal
Journey, described thread is used for detecting corresponding mobile terminal and execution task；
Task entity builds module, for, after obtaining the task of needing execution, respectively each single task builds
One Task entity, and each Task entity is added to task queue, described Task entity is used for recording the related letter of each task
Breath；
Task distributes sending module, for taking out corresponding task from task queue, and is distributed transmission to each shifting
Dynamic terminal；
Implementing result receives and output module, for, after each mobile terminal executes corresponding task, receiving and being derived from each shifting
The implementing result that dynamic terminal returns, finishes when all tasks in task queue are all performed, collect implementing result and by its
Output.
Further, described system also includes task action result confirmation and task re-executes module, described task
Implementing result confirms and task re-executes module and is used for：
When a certain task of mobile terminal successful execution, implementing result is back to behind test terminal, test terminal receives and holds
Row result simultaneously takes out the distribution transmission of next task to this mobile terminal from task queue；
When mobile terminal unsuccessful execution task, implementing result is back to behind test terminal, test terminal receives execution
Result simultaneously sends dependent instruction, makes this mobile terminal re-execute this task；
If re-executing this Mission Success, test terminal updates implementing result, and takes out next from task queue
Business distribution sends to this mobile terminal；If re-executing this mission failure, mark re-executes this mission failure, test terminal
Change execution status of task, takes out the distribution of next task from task queue and sends to this mobile terminal, again by mark simultaneously
The task of execution failure is added at the position of pending task to task queue；In re-executing task process, if weight
The number of times executing a certain task again exceedes preset value, and ability mark re-executes this mission failure, and tasks carrying is changed in test terminal
State.
The relevant information of each mobile terminal of described mobile terminal entity record include each mobile terminal mobile terminal title,
Connection end slogan, whether set up with test terminal be connected and mobile terminal working condition in one or more information；Institute
The relevant information stating each task of Task entity record includes the mission number of each task, is performed number of times and has been moved by which platform
Executory one or more information of terminal；It is preferably task queue at the position of pending task in described task queue
Most end end position；Described test terminal is computer, and described mobile terminal is mobile phone.
Apply the present invention to mobile phone automatic test when, by being each to set up the handss being connected with computer in computer end
Machine arranges a single thread and the corresponding Task entity of task creation for needing execution, and controllable multiple stage mobile phone is held simultaneously
The different task of row, greatly shortens the execution time of automatic test, effectively improves testing efficiency；Meanwhile, by complete
The mechanism that kind task action result confirms and re-executes, is capable of the accuracy rate of significant increase test result, also greatly protects
Hinder the fluency of automatic test, effectively reduced in test process and lead to test the problem interrupted because occurring various abnormal.
Brief description
Accompanying drawing 1 is the method flow schematic diagram of the embodiment of the present invention；
Accompanying drawing 2 is a kind of construction module of the system controlling multiple stage mobile terminal automatically to execute task in the embodiment of the present invention
Schematic diagram；
Accompanying drawing 3 is the flow process simplified schematic diagram of the specific embodiment of the invention.
Specific embodiment
For the ease of the understanding of those skilled in the art, the invention will be further described below in conjunction with the accompanying drawings.
As shown in Figure 1, a kind of method controlling multiple stage mobile terminal automatically to execute task, methods described includes：
S1, multiple stage mobile terminal is connected with test terminal, test terminal obtains the device name of each mobile terminal, sets up
Port mapping, and build mobile terminal entity, described mobile terminal entity is used for recording the relevant information of each mobile terminal；
S2, each mobile terminal for being connected with test terminal foundation arrange a single thread, and described thread is used for
Detect corresponding mobile terminal and execution task；
S3, acquisition need the task of execution, and respectively each single task builds a Task entity, and each task is real
Body adds to task queue, and described Task entity is used for recording the relevant information of each task；
S4, take out corresponding task from task queue, and distributed transmission to each mobile terminal；
S5, each mobile terminal execute corresponding task, and the standby communication terminal end such as test terminal returns implementing result；
If a certain task of S51 mobile terminal successful execution, implementing result is back to test terminal, test terminal connects
Receive implementing result and take out the distribution transmission of next task from task queue to this mobile terminal, if the unsuccessful execution of mobile terminal
A certain task, then be back to test terminal by implementing result, and test terminal receives implementing result and sends dependent instruction, makes this shifting
Dynamic terminal re-executes this task；
If S52 re-executes this Mission Success, test terminal updates implementing result, and under taking-up from task queue
One task distribution sends to this mobile terminal；If re-executing this mission failure, mark re-executes this mission failure, test
Terminal changes execution status of task, takes out the distribution of next task and sends to this mobile terminal, will indicate simultaneously from task queue
At the position of pending task that the task of re-executing failure is added to task queue；In this step S52, re-executing
In task process, if the number of times repeating a certain task exceedes preset value, ability mark re-executes this mission failure, and test is eventually
End change execution status of task；It is preferably the least significant end position of task queue at the position of pending task in described task queue
Put；
S6, finish when all tasks in task queue are all performed, it is simultaneously that it is defeated that implementing result is collected in test terminal
Go out.
Wherein, the relevant information of each mobile terminal of described mobile terminal entity record includes the mobile terminal of each mobile terminal
Title, connection end slogan, whether set up with test terminal has been connected and mobile terminal working condition in believe for one or more
Breath；The relevant information of each task of described Task entity record includes the mission number of each task, is performed number of times and by which
Executory one or more information of platform mobile terminal.
A kind of control multiple stage mobile terminal providing for the present invention as shown in Figure 2 executes the system of task, application automatically
In test terminal, described system includes：
Mobile terminal entity builds module, and for being connected with test terminal when multiple stage mobile terminal, test terminal obtains each
After the device name of mobile terminal, set up port mapping and build mobile terminal entity, described mobile terminal entity is used for recording
The relevant information of each mobile terminal；
Thread setup module, for arranging a single line for setting up each mobile terminal being connected with test terminal
Journey, described thread is used for detecting corresponding mobile terminal and execution task；
Task entity builds module, for, after obtaining the task of needing execution, respectively each single task builds
One Task entity, and each Task entity is added to task queue, described Task entity is used for recording the related letter of each task
Breath；
Task distributes sending module, for taking out corresponding task from task queue, and is distributed transmission to each shifting
Dynamic terminal；
Task action result confirms and task re-executes module, and it is used for：
When a certain task of mobile terminal successful execution, implementing result is back to behind test terminal, test terminal receives and holds
Row result simultaneously takes out the distribution transmission of next task to this mobile terminal from task queue；
When mobile terminal unsuccessful execution task, implementing result is back to behind test terminal, test terminal receives execution
Result simultaneously sends dependent instruction, makes this mobile terminal re-execute this task；
If re-executing this Mission Success, test terminal updates implementing result, and takes out next from task queue
Business distribution sends to this mobile terminal；If re-executing this mission failure, mark re-executes this mission failure, test terminal
Change execution status of task, takes out the distribution of next task from task queue and sends to this mobile terminal, again by mark simultaneously
The task of execution failure is added at the position of pending task to task queue；In re-executing task process, if weight
The number of times executing a certain task again exceedes preset value, and ability mark re-executes this mission failure, and tasks carrying is changed in test terminal
State；
Implementing result receives and output module, for, after each mobile terminal executes corresponding task, receiving and being derived from each shifting
The implementing result that dynamic terminal returns, finishes when all tasks in task queue are all performed, collect implementing result and by its
Output.
Wherein, the relevant information of each mobile terminal of described mobile terminal entity record includes the mobile terminal of each mobile terminal
Title, connection end slogan, whether set up with test terminal has been connected and mobile terminal working condition in believe for one or more
Breath；The relevant information of each task of described Task entity record includes the mission number of each task, is performed number of times and by which
Executory one or more information of platform mobile terminal；It is preferably task at the position of pending task in described task queue
The most end end position of queue.
The automatic test applying the present invention to mobile phone below is made further to the present invention as specific embodiment
Elaboration explanation, wherein, test terminal is with computer (PC), mobile terminal with the mobile phone using android system for being embodied as
Example is being described in detail.
Step 001, multiple stage mobile phone is connected with PC, PC obtains the device name of each mobile phone, sets up port mapping, and builds
Mobile phone entity.
In the present embodiment, pass through data wire between each mobile phone and PC（As USB data line）Connect, finish it in connection
Afterwards, port mapping is set up by " ADB Forward " in PC end, thus can communicate with carrying out PC end and mobile phone using Socket
The data transfer at end.PC end is used as the identity of every mobile phone again by the title that " ADB Devices " gets each mobile phone
Mark, thus build mobile phone entity.The full name of ADB is Android Debug Bridge it is simply that playing the effect of debugging bridge.
ADB is an instrument of Android SDK, can direct operation management Android simulator or real with this instrument
Android device.Mobile phone entity is used for recording the relevant information of mobile phone, in the present embodiment, each mobile phone of mobile phone entity record
Relevant information include the mobile phone title of each mobile phone, connection end slogan, whether set up with PC be connected, working state of mobile phone etc..
Step 002, it is that each mobile phone that established a connection arranges a single thread at PC end, each thread is used for
Detect corresponding mobile phone and execute corresponding task.
Step 003, acquisition need the task of execution, and respectively each single task builds a Task entity, and will be respectively
Task entity adds to task queue.
PC end, after obtaining the task of needing execution, is that each task builds Task entity respectively, Task entity is used for recording
The mission number of each task, it is performed number of times and by relevant informations such as any mobile phone execution.
Step 004, take out corresponding task from task queue, and distributed transmission to each mobile phone；In the task of structure
Entity, each Task entity is added to after task queue, you can takes out task distribution transmission from task queue and holds to mobile phone terminal
OK.It is assumed that the mobile phone being connected with PC is three in the present embodiment, respectively mobile phone A, B, C, task of taking out from task queue is compiled
Task number for 1,2,3 is respectively allocated and is sent to mobile phone A, B, C.
Step 005, each mobile phone execute corresponding task, and PC end waits each mobile phone to return implementing result.If mobile phone A is successfully held
Row task 1, then be back to PC end by implementing result, and PC collects at end this implementing result, and takes out next task from task queue
(as task 4) distribution sends to mobile phone A；If mobile phone B unsuccessful execution task 2, implementing result is back to PC end, PC terminates
Receive implementing result and send dependent instruction, make mobile phone B re-execute this task 2；If re-executing this task 2 success, PC end
Update implementing result, and take out next task (as task 5) distribution from task queue and send to mobile phone B；If re-execute appointing
Business 2 failure, repeats and executes this task more than 2 time（The number of times repeating, can be repeated in the present embodiment by user preset
Number of times be twice, that is, in re-executing task process, repeat a certain task number of times preset value be 2）, then indicate
Re-execute this mission failure, execution status of task is changed at PC end, take out next task (as task 5) distribution from task queue
Send to this mobile terminal, the task (i.e. task 2) simultaneously mark being re-executed failure is added treating to task queue and held
At the position of row task, here, can be at the position of task not also being performed at the position of pending task（As appointed
Business 6,7,8 ... wait between position at, the present embodiment be preferably task queue most end end position）.Mobile phone C executes task
Process is similar with the task of above-mentioned mobile phone A, B execution, repeats no more here.During each mobile phone execution task, if task
Quantity be more than mobile phone quantity when, PC end can be taken out the distribution of corresponding task and be sent to each mobile phone, to guarantee every mobile phone all
Have tasks carrying, and performed task be also different, you can make multiple stage mobile phone execute different tasks simultaneously so that its
The time of execution task greatly shortens,
During task is performed, mobile phone entity can correspondingly record mobile phone the relevant information such as working condition,
Upon execution, the working condition of mobile phone is busy to task as existing in mobile phone, then the working condition of mobile phone is set to 1, mobile phone executed
Complete a certain task, when PC does not also have corresponding task distribution, the working condition of mobile phone is the free time, then its working condition is set to 0,
If the distribution of a certain task is sent to after this mobile phone by PC end, the working condition of mobile phone is set to 1 again；Meanwhile, Task entity
Also the number of times that is performed of each task can be recorded during task, by information such as which platform mobile phone execution, as stated above appoints
Business 2, if it is executed failure first by mobile phone B, and during being repeated by mobile phone, corresponding Task entity can logger task
2 are executed by mobile phone B, its number of times being executed by mobile phone B；If the number of times that it is executed by mobile phone B has reached 3 times（Repeated by mobile phone B
The number of times of execution is twice）, and if also failing after third time is performed, it will flagged re-execute this mission failure.
During task is performed, the mechanism that the present embodiment is confirmed by perfect task action result and re-executes, can
The accuracy rate of significant increase test result, has also greatly ensured the fluency of automatic test, effectively reduces in test process
Lead to test the problem interrupted because occurring various abnormal.
Step 006, finish when all tasks in task queue are all performed, it is simultaneously that it is defeated that implementing result is collected at PC end
Go out.
The brief flow process of this specific embodiment see accompanying drawing 3, repeats no more here.In addition, it is necessary to explanation, this
Bright it is not only applicable to mobile phone（Or other mobile terminals）Automatic test, could be applicable to for heap file to be sent to multiple stage
Mobile phone（Or other mobile terminals）, in multiple stage mobile phone（Or other mobile terminals）A large amount of softwares of upper installation etc..
The content mentioned in above-described embodiment is the present invention preferably embodiment, is not limited to the present invention,
On the premise of present inventive concept, any obvious replacement is all within protection scope of the present invention.
Claims (10)
1. a kind of method controlling multiple stage mobile terminal automatically to execute task, methods described includes：
S1, multiple stage mobile terminal is connected with test terminal, test terminal obtains the device name of each mobile terminal, sets up port
Mapping, and build mobile terminal entity, described mobile terminal entity is used for recording the relevant information of each mobile terminal；
S2, each mobile terminal for being connected with test terminal foundation arrange a single thread, and described thread is used for detecting
Corresponding mobile terminal and execution task；
S3, acquisition need the task of execution, and respectively each single task builds a Task entity, and each Task entity is added
Add in task queue, described Task entity is used for recording the relevant information of each task；
S4, take out corresponding task from task queue, and distributed transmission to each mobile terminal；
S5, each mobile terminal execute corresponding task, and the standby communication terminal such as test terminal returns implementing result；
S6, finish when all tasks in task queue are all performed, test terminal is collected implementing result and simultaneously output it.
2. method according to claim 1 is it is characterised in that described step S5 also includes：
If a certain task of S51 mobile terminal successful execution, implementing result is back to test terminal, test terminal receives and holds
Row result simultaneously takes out the distribution transmission of next task to this mobile terminal, if the unsuccessful execution of mobile terminal is a certain from task queue
Task, then be back to test terminal by implementing result, and test terminal receives implementing result and sends dependent instruction, makes this movement eventually
End re-executes this task；
If S52 re-executes this Mission Success, test terminal updates implementing result, and takes out next from task queue
Business distribution sends to this mobile terminal；If re-executing this mission failure, mark re-executes this mission failure, test terminal
Change execution status of task, takes out the distribution of next task from task queue and sends to this mobile terminal, again by mark simultaneously
The task of execution failure is added at the position of pending task to task queue.
3. method according to claim 2 it is characterised in that：In described step S52, in re-executing task process,
If the number of times repeating a certain task exceedes preset value, ability mark re-executes this mission failure, and task is changed in test terminal
Execution state.
4. method according to claim 3 it is characterised in that：At the position of pending task in described task queue it is
The most end end position of task queue.
5. the method according to any one of Claims 1 to 4 it is characterised in that：Described mobile terminal entity record respectively moves
Whether the relevant information of dynamic terminal is included the mobile terminal title of each mobile terminal, connection end slogan, is set up with test terminal
One or more information in connection and mobile terminal working condition；The relevant information bag of each task of described Task entity record
Include the mission number of each task, be performed number of times and by executory one or more information of any platform mobile terminal.
6. the method according to any one of Claims 1 to 4 it is characterised in that：Described test terminal is computer, described
Mobile terminal be mobile phone.
7. a kind of control multiple stage mobile terminal automatically to execute the system of task, be applied in test terminal it is characterised in that described
System includes：
Mobile terminal entity builds module, and for being connected with test terminal when multiple stage mobile terminal, test terminal obtains each movement
After the device name of terminal, set up port mapping and build mobile terminal entity, described mobile terminal entity is used for recording each shifting
The relevant information of dynamic terminal；
Thread setup module, for arranging a single thread, institute for setting up each mobile terminal being connected with test terminal
State thread to be used for detecting corresponding mobile terminal and execution task；
Task entity builds module, for, after obtaining the task of needing execution, respectively each single task builds one
Entity, and each Task entity is added to task queue, described Task entity is used for recording the relevant information of each task；
Task distributes sending module, for taking out corresponding task from task queue, and is distributed transmission to each movement eventually
End；
Implementing result receives and output module, for, after each mobile terminal executes corresponding task, receiving from each movement eventually
The implementing result that end returns, finishes when all tasks in task queue are all performed, collects implementing result and outputs it.
8. system according to claim 7 is it is characterised in that described system also includes task action result confirmation and appoints
Business re-executes module, and described task action result confirms and task re-executes module and is used for：
When a certain task of mobile terminal successful execution, implementing result is back to behind test terminal, test terminal receives and executes knot
Fruit simultaneously takes out the distribution transmission of next task to this mobile terminal from task queue；
When mobile terminal unsuccessful execution task, implementing result is back to behind test terminal, test terminal receives implementing result
And send dependent instruction, make this mobile terminal re-execute this task；
If re-executing this Mission Success, test terminal updates implementing result, and takes out next task from task queue and divide
This mobile terminal is delivered in allocation；If re-executing this mission failure, mark re-executes this mission failure, and test terminal is changed
Execution status of task, takes out the distribution of next task from task queue and sends to this mobile terminal, re-execute mark simultaneously
The task of failure is added at the position of pending task to task queue；In re-executing task process, if repeating to hold
The number of times of a certain task of row exceedes preset value, and ability mark re-executes this mission failure, and execution status of task is changed in test terminal.
9. system according to claim 8 it is characterised in that：The correlation of each mobile terminal of described mobile terminal entity record
Whether information is included the mobile terminal title of each mobile terminal, connection end slogan, is set up with test terminal and has been connected and movement
One or more information in terminal operating status；The relevant information of each task of described Task entity record includes appointing of each task
Business is numbered, is performed number of times and by executory one or more information of which platform mobile terminal；In described task queue
It is the most end end position of task queue at the position of pending task.
10. the system according to any one of claim 7～9 it is characterised in that：Described test terminal is computer, institute
The mobile terminal stated is mobile phone.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410027603.0A CN103744761B (en) | 2014-01-22 | 2014-01-22 | Method and system for controlling multiple mobile terminals to automatically execute tasks |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410027603.0A CN103744761B (en) | 2014-01-22 | 2014-01-22 | Method and system for controlling multiple mobile terminals to automatically execute tasks |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103744761A CN103744761A (en) | 2014-04-23 |
| CN103744761B true CN103744761B (en) | 2017-02-08 |
Family
ID=50501781
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410027603.0A Expired - Fee Related CN103744761B (en) | 2014-01-22 | 2014-01-22 | Method and system for controlling multiple mobile terminals to automatically execute tasks |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103744761B (en) |
Families Citing this family (95)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8677377B2 (en) | 2005-09-08 | 2014-03-18 | Apple Inc. | Method and apparatus for building an intelligent automated assistant |
| US9318108B2 (en) | 2010-01-18 | 2016-04-19 | Apple Inc. | Intelligent automated assistant |
| US8977255B2 (en) | 2007-04-03 | 2015-03-10 | Apple Inc. | Method and system for operating a multi-function portable electronic device using voice-activation |
| US8676904B2 (en) | 2008-10-02 | 2014-03-18 | Apple Inc. | Electronic devices with voice command and contextual data processing capabilities |
| US10255566B2 (en) | 2011-06-03 | 2019-04-09 | Apple Inc. | Generating and processing task items that represent tasks to perform |
| US10276170B2 (en) | 2010-01-18 | 2019-04-30 | Apple Inc. | Intelligent automated assistant |
| US8682667B2 (en) | 2010-02-25 | 2014-03-25 | Apple Inc. | User profiling for selecting user specific voice input processing information |
| US10417037B2 (en) | 2012-05-15 | 2019-09-17 | Apple Inc. | Systems and methods for integrating third party services with a digital assistant |
| EP3809407A1 (en) | 2013-02-07 | 2021-04-21 | Apple Inc. | Voice trigger for a digital assistant |
| US10652394B2 (en) | 2013-03-14 | 2020-05-12 | Apple Inc. | System and method for processing voicemail |
| US10748529B1 (en) | 2013-03-15 | 2020-08-18 | Apple Inc. | Voice activated device for use with a voice-based digital assistant |
| US10176167B2 (en) | 2013-06-09 | 2019-01-08 | Apple Inc. | System and method for inferring user intent from speech inputs |
| DE112014002747T5 (en) | 2013-06-09 | 2016-03-03 | Apple Inc. | Apparatus, method and graphical user interface for enabling conversation persistence over two or more instances of a digital assistant |
| US10296160B2 (en) | 2013-12-06 | 2019-05-21 | Apple Inc. | Method for extracting salient dialog usage from live data |
| US9633004B2 (en) | 2014-05-30 | 2017-04-25 | Apple Inc. | Better resolution when referencing to concepts |
| EP3149728B1 (en) | 2014-05-30 | 2019-01-16 | Apple Inc. | Multi-command single utterance input method |
| US9430463B2 (en) | 2014-05-30 | 2016-08-30 | Apple Inc. | Exemplar-based natural language processing |
| US10170123B2 (en) | 2014-05-30 | 2019-01-01 | Apple Inc. | Intelligent assistant for home automation |
| US9715875B2 (en) | 2014-05-30 | 2017-07-25 | Apple Inc. | Reducing the need for manual start/end-pointing and trigger phrases |
| US9338493B2 (en) | 2014-06-30 | 2016-05-10 | Apple Inc. | Intelligent automated assistant for TV user interactions |
| US10127911B2 (en) | 2014-09-30 | 2018-11-13 | Apple Inc. | Speaker identification and unsupervised speaker adaptation techniques |
| US9668121B2 (en) | 2014-09-30 | 2017-05-30 | Apple Inc. | Social reminders |
| US10152299B2 (en) | 2015-03-06 | 2018-12-11 | Apple Inc. | Reducing response latency of intelligent automated assistants |
| US9721566B2 (en) | 2015-03-08 | 2017-08-01 | Apple Inc. | Competing devices responding to voice triggers |
| US9886953B2 (en) | 2015-03-08 | 2018-02-06 | Apple Inc. | Virtual assistant activation |
| US10460227B2 (en) | 2015-05-15 | 2019-10-29 | Apple Inc. | Virtual assistant in a communication session |
| US10083688B2 (en) | 2015-05-27 | 2018-09-25 | Apple Inc. | Device voice control for selecting a displayed affordance |
| US10200824B2 (en) | 2015-05-27 | 2019-02-05 | Apple Inc. | Systems and methods for proactively identifying and surfacing relevant content on a touch-sensitive device |
| CN104965780A (en) * | 2015-06-04 | 2015-10-07 | 北京奇虎科技有限公司 | Data processing method and system |
| US9578173B2 (en) | 2015-06-05 | 2017-02-21 | Apple Inc. | Virtual assistant aided communication with 3rd party service in a communication session |
| US20160378747A1 (en) | 2015-06-29 | 2016-12-29 | Apple Inc. | Virtual assistant for media playback |
| US10671428B2 (en) | 2015-09-08 | 2020-06-02 | Apple Inc. | Distributed personal assistant |
| US10747498B2 (en) | 2015-09-08 | 2020-08-18 | Apple Inc. | Zero latency digital assistant |
| US10331312B2 (en) | 2015-09-08 | 2019-06-25 | Apple Inc. | Intelligent automated assistant in a media environment |
| US10740384B2 (en) | 2015-09-08 | 2020-08-11 | Apple Inc. | Intelligent automated assistant for media search and playback |
| US10691473B2 (en) | 2015-11-06 | 2020-06-23 | Apple Inc. | Intelligent automated assistant in a messaging environment |
| US10956666B2 (en) | 2015-11-09 | 2021-03-23 | Apple Inc. | Unconventional virtual assistant interactions |
| US10223066B2 (en) | 2015-12-23 | 2019-03-05 | Apple Inc. | Proactive assistance based on dialog communication between devices |
| US11227589B2 (en) | 2016-06-06 | 2022-01-18 | Apple Inc. | Intelligent list reading |
| US10586535B2 (en) | 2016-06-10 | 2020-03-10 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
| CN107493374B (en) * | 2016-06-11 | 2020-06-19 | 苹果公司 | Application integration device with digital assistant and method |
| DK179343B1 (en) | 2016-06-11 | 2018-05-14 | Apple Inc | Intelligent task discovery |
| DK201670540A1 (en) | 2016-06-11 | 2018-01-08 | Apple Inc | Application integration with a digital assistant |
| CN107491469B (en) * | 2016-06-11 | 2020-11-24 | 苹果公司 | Intelligent task discovery |
| DK179415B1 (en) | 2016-06-11 | 2018-06-14 | Apple Inc | Intelligent device arbitration and control |
| US10474753B2 (en) | 2016-09-07 | 2019-11-12 | Apple Inc. | Language identification using recurrent neural networks |
| US11204787B2 (en) | 2017-01-09 | 2021-12-21 | Apple Inc. | Application integration with a digital assistant |
| CN106997307A (en) * | 2017-02-13 | 2017-08-01 | 上海大学 | A kind of Socket thread pool design methods towards multiple terminals radio communication |
| DK201770383A1 (en) | 2017-05-09 | 2018-12-14 | Apple Inc. | User interface for correcting recognition errors |
| DK180048B1 (en) | 2017-05-11 | 2020-02-04 | Apple Inc. | MAINTAINING THE DATA PROTECTION OF PERSONAL INFORMATION |
| US10395654B2 (en) | 2017-05-11 | 2019-08-27 | Apple Inc. | Text normalization based on a data-driven learning network |
| US10726832B2 (en) | 2017-05-11 | 2020-07-28 | Apple Inc. | Maintaining privacy of personal information |
| US11301477B2 (en) | 2017-05-12 | 2022-04-12 | Apple Inc. | Feedback analysis of a digital assistant |
| DK179745B1 (en) | 2017-05-12 | 2019-05-01 | Apple Inc. | SYNCHRONIZATION AND TASK DELEGATION OF A DIGITAL ASSISTANT |
| DK201770427A1 (en) | 2017-05-12 | 2018-12-20 | Apple Inc. | Low-latency intelligent automated assistant |
| DK179496B1 (en) | 2017-05-12 | 2019-01-15 | Apple Inc. | USER-SPECIFIC Acoustic Models |
| US10311144B2 (en) | 2017-05-16 | 2019-06-04 | Apple Inc. | Emoji word sense disambiguation |
| US10303715B2 (en) | 2017-05-16 | 2019-05-28 | Apple Inc. | Intelligent automated assistant for media exploration |
| DK179560B1 (en) | 2017-05-16 | 2019-02-18 | Apple Inc. | Far-field extension for digital assistant services |
| US20180336892A1 (en) | 2017-05-16 | 2018-11-22 | Apple Inc. | Detecting a trigger of a digital assistant |
| CN108073514B (en) * | 2017-07-18 | 2023-09-05 | 北京微应软件科技有限公司 | Method and device for simultaneously connecting multiple mobile phone terminals by personal computer |
| US10592604B2 (en) | 2018-03-12 | 2020-03-17 | Apple Inc. | Inverse text normalization for automatic speech recognition |
| US10818288B2 (en) | 2018-03-26 | 2020-10-27 | Apple Inc. | Natural assistant interaction |
| US10928918B2 (en) | 2018-05-07 | 2021-02-23 | Apple Inc. | Raise to speak |
| US11145294B2 (en) | 2018-05-07 | 2021-10-12 | Apple Inc. | Intelligent automated assistant for delivering content from user experiences |
| DK180639B1 (en) | 2018-06-01 | 2021-11-04 | Apple Inc | DISABILITY OF ATTENTION-ATTENTIVE VIRTUAL ASSISTANT |
| US10892996B2 (en) | 2018-06-01 | 2021-01-12 | Apple Inc. | Variable latency device coordination |
| DK179822B1 (en) | 2018-06-01 | 2019-07-12 | Apple Inc. | Voice interaction at a primary device to access call functionality of a companion device |
| US10944859B2 (en) | 2018-06-03 | 2021-03-09 | Apple Inc. | Accelerated task performance |
| CN110895488B (en) * | 2018-09-12 | 2023-10-20 | 三六零科技集团有限公司 | Task scheduling method and device |
| US11010561B2 (en) | 2018-09-27 | 2021-05-18 | Apple Inc. | Sentiment prediction from textual data |
| US11170166B2 (en) | 2018-09-28 | 2021-11-09 | Apple Inc. | Neural typographical error modeling via generative adversarial networks |
| US11462215B2 (en) | 2018-09-28 | 2022-10-04 | Apple Inc. | Multi-modal inputs for voice commands |
| US10839159B2 (en) | 2018-09-28 | 2020-11-17 | Apple Inc. | Named entity normalization in a spoken dialog system |
| US11475898B2 (en) | 2018-10-26 | 2022-10-18 | Apple Inc. | Low-latency multi-speaker speech recognition |
| CN109636404A (en) * | 2018-12-29 | 2019-04-16 | 福建易联众医联信息技术有限公司 | A kind of fast and safely method of payment, system, equipment and the readable medium of hospital |
| US11638059B2 (en) | 2019-01-04 | 2023-04-25 | Apple Inc. | Content playback on multiple devices |
| US11348573B2 (en) | 2019-03-18 | 2022-05-31 | Apple Inc. | Multimodality in digital assistant systems |
| US11307752B2 (en) | 2019-05-06 | 2022-04-19 | Apple Inc. | User configurable task triggers |
| DK201970509A1 (en) | 2019-05-06 | 2021-01-15 | Apple Inc | Spoken notifications |
| US11475884B2 (en) | 2019-05-06 | 2022-10-18 | Apple Inc. | Reducing digital assistant latency when a language is incorrectly determined |
| US11423908B2 (en) | 2019-05-06 | 2022-08-23 | Apple Inc. | Interpreting spoken requests |
| US11140099B2 (en) | 2019-05-21 | 2021-10-05 | Apple Inc. | Providing message response suggestions |
| US11496600B2 (en) | 2019-05-31 | 2022-11-08 | Apple Inc. | Remote execution of machine-learned models |
| DK201970510A1 (en) | 2019-05-31 | 2021-02-11 | Apple Inc | Voice identification in digital assistant systems |
| US11289073B2 (en) | 2019-05-31 | 2022-03-29 | Apple Inc. | Device text to speech |
| DK180129B1 (en) | 2019-05-31 | 2020-06-02 | Apple Inc. | User activity shortcut suggestions |
| US11468890B2 (en) | 2019-06-01 | 2022-10-11 | Apple Inc. | Methods and user interfaces for voice-based control of electronic devices |
| US11360641B2 (en) | 2019-06-01 | 2022-06-14 | Apple Inc. | Increasing the relevance of new available information |
| WO2021056255A1 (en) | 2019-09-25 | 2021-04-01 | Apple Inc. | Text detection using global geometry estimators |
| US11061543B1 (en) | 2020-05-11 | 2021-07-13 | Apple Inc. | Providing relevant data items based on context |
| US11183193B1 (en) | 2020-05-11 | 2021-11-23 | Apple Inc. | Digital assistant hardware abstraction |
| US11755276B2 (en) | 2020-05-12 | 2023-09-12 | Apple Inc. | Reducing description length based on confidence |
| US11490204B2 (en) | 2020-07-20 | 2022-11-01 | Apple Inc. | Multi-device audio adjustment coordination |
| US11438683B2 (en) | 2020-07-21 | 2022-09-06 | Apple Inc. | User identification using headphones |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5383192A (en) * | 1992-12-23 | 1995-01-17 | Intel Corporation | Minimizing the likelihood of slip between the instant a candidate for a break event is generated and the instant a microprocessor is instructed to perform a break, without missing breakpoints |
| CN1149735A (en) * | 1994-05-25 | 1997-05-14 | 西门子公司 | Service personal computer of modular structure |
-
2014
- 2014-01-22 CN CN201410027603.0A patent/CN103744761B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5383192A (en) * | 1992-12-23 | 1995-01-17 | Intel Corporation | Minimizing the likelihood of slip between the instant a candidate for a break event is generated and the instant a microprocessor is instructed to perform a break, without missing breakpoints |
| CN1149735A (en) * | 1994-05-25 | 1997-05-14 | 西门子公司 | Service personal computer of modular structure |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103744761A (en) | 2014-04-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103744761B (en) | Method and system for controlling multiple mobile terminals to automatically execute tasks | |
| CN102567203B (en) | A kind of method and system of test distributed file system performance | |
| CN102967815B (en) | Chip testing method, automated testing equipment and system | |
| CN103890595A (en) | Method and system for utilizing stand-alone controller in multiplexed handler test cell for indexless tandem semiconductor test | |
| CN104781682B (en) | The pseudo- tester function of often standing in the local automatic test equipment per pin tester for semiconductor test | |
| CN104020763A (en) | Automatic test method and system for input and output interfaces | |
| CN102301344A (en) | Method for debugging kernel of operating system and virtual debugging service module | |
| Canfora et al. | A case study of automating user experience-oriented performance testing on smartphones | |
| CN109118097B (en) | Reliability maintainability guarantee assessment method and device | |
| CN102968371A (en) | Method and device for testing JAVA API unit component | |
| CN105260297B (en) | A kind of test data management system and method | |
| US20160094158A1 (en) | Method for power station simulation | |
| CN107170218B (en) | Remote assistance method and system for debugging fire alarm system | |
| CN101557437A (en) | Automatic testing method of mobile phone software and device thereof | |
| CN106294121A (en) | Aircraft embedded real-time diagnosis reasoning algorithm test method | |
| CN102135939B (en) | Test case operation dispatching device and method | |
| CN106295809A (en) | Aircraft embedded real-time diagnosis reasoning algorithm pilot system | |
| CN106020898A (en) | Software upgrading method and system of multi-processor device | |
| US20080162900A1 (en) | System, Method and Apparatus for Observing a Control Device | |
| CN102331961B (en) | Method, system and dispatcher for simulating multiple processors in parallel | |
| CN106325219A (en) | CNC processing program call device and method | |
| CN105320510B (en) | A kind of method and device of automatic tracing data relationship | |
| US20020099953A1 (en) | Debugging of chipcards | |
| CN105205545A (en) | Method for optimizing logistics system by applying simulation experiment | |
| CN109144840A (en) | A kind of test method, device and its equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder |
Address after: Changan town in Guangdong province Dongguan 523860 usha Beach Road No. 18 Patentee after: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS Corp.,Ltd. Address before: Changan town in Guangdong province Dongguan 523860 usha Beach Road No. 18 Patentee before: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS Corp.,Ltd. |
|
| CP01 | Change in the name or title of a patent holder | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20170208 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |