WO2012055176A1 - Processing method for mobile terminal and mobile terminal - Google Patents

Processing method for mobile terminal and mobile terminal Download PDF

Info

Publication number
WO2012055176A1
WO2012055176A1 PCT/CN2011/070485 CN2011070485W WO2012055176A1 WO 2012055176 A1 WO2012055176 A1 WO 2012055176A1 CN 2011070485 W CN2011070485 W CN 2011070485W WO 2012055176 A1 WO2012055176 A1 WO 2012055176A1
Authority
WO
WIPO (PCT)
Prior art keywords
aome
tnm
trigger
mobile terminal
application
Prior art date
Application number
PCT/CN2011/070485
Other languages
French (fr)
Chinese (zh)
Inventor
孟兆
蒋敏
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012055176A1 publication Critical patent/WO2012055176A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/75Structural analysis for program understanding

Definitions

  • the present invention relates to the field of communications, and in particular to a mobile terminal processing method and a mobile terminal.
  • mobile terminals mobile communication terminals
  • BACKGROUND OF THE INVENTION With the development of mobile communication technologies and microelectronic technologies, the trend of convergence of mobile communication terminals (hereinafter referred to as mobile terminals) with handheld computers has become apparent. Users not only want mobile terminals to implement inherent communication functions (for example, making calls, texting, etc.), but also hope that mobile phones can provide functions such as document processing, Internet access, games, and multimedia. In recent years, automatic processing of transactions through mobile terminals has also become one of the directions of user demand. For example, some business users want mobile terminals to receive emails from the Internet at regular intervals, uploading and downloading documents; younger users may want to pay attention to trend information in real time.
  • a primary object of the present invention is to provide a mobile terminal processing method and a mobile terminal to solve at least the above problems.
  • An aspect of the present invention provides a mobile terminal processing method, including:
  • the AOME accepts a script configuration for implementing a user automatic operation function into the AOME, wherein the script includes indication information and control logic, the indication information is used to indicate an application and/or global call on the mobile terminal
  • the control logic is configured to indicate a logical sequence of invoking the application and/or the global device; the AOME parses the script, and invokes the application and/or according to the indication information and the control logic
  • the global device implements the automatic operation of the user.
  • the control logic is further used to indicate an event trigger condition to be met when the application and/or the global device is invoked, the AOME invokes the application and/or the location according to the indication information and control logic.
  • the global device implementing the user automatic operation function includes: the TNM in the mobile terminal notifying the AOME if the event triggering condition configured in the TNM is satisfied; the AOME receiving the notification, determining the location
  • the event triggering condition that is satisfied is the same as the event triggering condition that is to be satisfied by the control logic, and the application and/or the global indication indicated by the indication information is invoked according to the logical sequence indicated by the control logic.
  • the device implements the automatic operation function of the user.
  • the TNM in the mobile terminal when the event triggering condition configured in the TNM is satisfied, notifying the AOME includes: the TNM traversing a Trigger list corresponding to an application or a global device monitored by the TNM, Each Trigger in the Trigger list corresponds to an event triggering condition, and is triggered if the corresponding event triggering condition is met; the TNM detects that the Trigger list exists in the Tringer by the traversal The triggered Trigger returns a notification message Notification corresponding to the triggered Trigger to the AOME.
  • the TNM includes a local TNM and a global TNM, where the local TNM is used to monitor an application, and the global TNM is used to monitor a global device.
  • the local TNM is located in an application monitored by the local TNM, and the global TNM is an independent application or located in the AOME.
  • the Trigger is preset in the TNM, or is configured by the user through the AOME into the TNM.
  • the script is configured to the AOME by macro recording on the AOME, or the script is configured to the AOME by importing the script into the AOME.
  • a mobile terminal including an AOME
  • the AOME includes: a configuration module configured to accept a script configured to implement a user automatic operation function into the AOME, where the script includes Instructing information and control logic, the indication information being used to indicate an application and/or a global device on the mobile terminal, the control logic is configured to indicate a logical sequence of invoking the application and/or the global device; a module, configured to parse the script; a calling module configured to invoke the application and/or the global device to implement the user automatic operation function according to the indication information and the control logic.
  • the mobile terminal further includes: TNM, configured to be configured in the TNM.
  • TNM configured to be configured in the TNM.
  • the calling module is configured to determine, when the notification is received, the event triggering condition that is satisfied and the event triggering condition that is required to be satisfied by the control logic
  • the application and/or the global device indicated by the indication information are invoked according to the logical sequence indicated by the control logic to implement the user automatic operation function.
  • the TNM includes: a traversal module, configured to traverse a Trigger list corresponding to an application or a global device monitored by the TNM, where each Trigger in the Trigger list corresponds to an event trigger condition, and corresponds to The event triggering condition is triggered; the notification module is configured to notify the notification message corresponding to the triggered Trigger if the traversal module detects that there is a triggered Trigger in the Trigger list Return to the AOME.
  • the mobile terminal further includes: a console module CPM, configured to be an interface between the AOME and the user, configured to configure the script imported by the user to the AOME, or set to provide an interface to accept the user to record through the macro The script is configured to the AOME.
  • the AOME is used to implement the automatic operation function of the user by calling the corresponding application and/or the global device according to the instruction information and the control logic in the script provided by the user, and solving the related art, the mobile terminal cannot implement the automatic operation according to the user's intention.
  • the problem of the operation function the user can implement the customized automatic operation on the mobile terminal according to his own wishes, which undoubtedly provides the user with greater freedom to use the mobile terminal.
  • FIG. 2 is a structural block diagram of a mobile terminal according to an embodiment of the present invention
  • FIG. 3 is a mobile terminal according to an embodiment of the present invention
  • Preferred structural block diagram 1 is a block diagram of a preferred structure of a mobile terminal according to an embodiment of the present invention
  • FIG. 5 is a block diagram 3 of a preferred structure of a mobile terminal according to an embodiment of the present invention
  • FIG. 6 is a diagram for implementing automatic user in a mobile terminal according to Embodiment 1. Schematic diagram of an automatic operation model of operation
  • FIG. 7 is a flow chart of a test for repeatedly downloading a file link using a mobile phone browser according to the embodiment 3.
  • BEST MODE FOR CARRYING OUT THE INVENTION will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.
  • FIG. 1 is a flowchart of a method for processing a mobile terminal according to an embodiment of the present invention. As shown in FIG.
  • Step S102 An Automatic Operating Module Engine (AOME in the mobile terminal) Accepting a script configuration for implementing a user automatic operation function into the AOME, wherein the script includes indication information and control logic, the indication information is used to indicate that an application and/or a global device on the mobile terminal is invoked, Control logic is used to indicate the logical sequence of invoking the application and/or the global device; Step S104, the AOME parses the script, and invokes the above application and/or global device in accordance with the indication information and control logic to implement the user automatic operation function.
  • AOME Automatic Operating Module Engine
  • AOME is set in the mobile terminal, and the AOME is used to parse and run the script for implementing the automatic operation function of the user (involving logic control and application and/or global device call), so as to implement the automatic operation of the user.
  • the method can be widely applied to a situation where a mobile terminal needs to automatically live in some real-time situations instead of the user's automatic action, and can also be used for automatic testing of the mobile platform. Users can freely choose to arrange what the mobile terminal does according to their own preferences, such as automatically transferring pictures after receiving MMS, and automatically making calls at regular intervals.
  • the functions that need to be embedded in the developer can now be completed by the users themselves.
  • the automatic control function undoubtedly provides users with more freedom to use the mobile terminal.
  • AOME can monitor the execution result, for example, recording the execution log, making an error prompt when an error occurs, and the like.
  • the Trigger and Notification Monitor (TNM) in the mobile terminal is configured in the TNM.
  • TNM Trigger and Notification Monitor
  • Trigger is a trigger object used to synchronize with AOME. It can be built by the manufacturer to local TNM (TNM - Local, referred to as TNM-L), or can be defined by the user for global TNM (TNM - Global, referred to as TNM-G). ). When a specified event (Event) occurs, Trigger will send the corresponding notification to AOME, which is the port associated with the Trigger.
  • TNM-L local TNM
  • TNM-G global TNM
  • the process of notifying the AOME may include the following processing:
  • the TNM traverses the Trigger list corresponding to the application or the global device monitored by the TNM, where the Trigger list Each Trigger corresponds to an event trigger condition and is triggered if the corresponding event trigger condition is satisfied; the TNM detects that there is a triggered Trigger in the Trigger list by traversing, which will correspond to the triggered Trigger
  • the notification message Notification is returned to AOME.
  • This method is easy to implement.
  • the above TNM may include a local TNM for monitoring applications and a global TNM for monitoring global devices.
  • the local TNM can be located in an application monitored by the local TNM, and the global TNM can be a standalone application or located in the AOME.
  • the Trigger can be pre-configured in the TNM, or it can be configured by the user into the TNM via AOME.
  • the Trigger in the local TNM is mostly preset, and the Trigger in the global TNM can be preset or configured by the user through the AOME.
  • the ⁇ can be configured to AOME by recording macro (Macro, user-recorded control logic, usually stored in ⁇ ) on AOME, or by importing ⁇ into AOME. This configuration is awkward.
  • 2 is a structural block diagram of a mobile terminal according to an embodiment of the present invention.
  • the mobile terminal includes an AOME 22.
  • the AOME 22 includes: a configuration module 24 configured to accept a script configured to implement a user automatic operation function into the AOME 22, wherein , the script includes instructions and control logic,
  • the indication information is used to indicate an application and/or a global device on the calling mobile terminal, the control logic is used to indicate a logical sequence of invoking the application and/or the global device;
  • the parsing module 26 is configured to parse the copy;
  • the calling module 28 is set to follow the indication Information and control logic invokes applications and/or global devices to implement user automation functions.
  • FIG. 3 is a block diagram of a preferred structure of a mobile terminal according to an embodiment of the present invention. As shown in FIG. 3, when the above control logic is further used to indicate an event trigger condition to be met when an application and/or a global device is invoked, the mobile terminal moves.
  • the terminal may further include: ⁇ 32, configured to notify ⁇ 22 when the event trigger condition configured in ⁇ 32 is satisfied; the calling module 28 is configured to determine that the event trigger condition is satisfied if the notification is received The same as the event triggering condition indicated by the control logic, the application and/or global device indicated by the indication information is invoked in a logical order indicated by the control logic to implement the user automatic operation function.
  • ⁇ 32 configured to notify ⁇ 22 when the event trigger condition configured in ⁇ 32 is satisfied
  • the calling module 28 is configured to determine that the event trigger condition is satisfied if the notification is received
  • the application and/or global device indicated by the indication information is invoked in a logical order indicated by the control logic to implement the user automatic operation function.
  • 4 is a block diagram 2 of a preferred structure of a mobile terminal according to an embodiment of the present invention, as shown in FIG.
  • the ⁇ 32 may include: a traversal module 42 configured to traverse a trigger object Trigger list corresponding to the application or global device monitored by the UI 32, wherein each Trigger in the Trigger list corresponds to an event trigger condition, and corresponds to The event triggering condition is triggered; the notification module 44 is configured to, in the case that the traversing module 42 detects that there is a triggered Trigger in the Trigger list, ⁇ " the notification message corresponding to the triggered Trigger is returned to the Notification message AOME 22.
  • Figure 5 is a block diagram of a preferred structure of a mobile terminal according to an embodiment of the present invention.
  • the mobile terminal may further include: a Control Panel Module (CPM) 52, which is set as The interface between AOME 22 and the user configures the user-imported script to AOME 22, or is set to provide an interface to accept the user's configuration to AOME 11 through macro recording.
  • CCM Control Panel Module
  • Embodiment 1-3 which combines the above Technical Solution of a Preferred Embodiment.
  • FIG. 6 is a diagram for implementing automatic user in a mobile terminal according to Embodiment 1.
  • FIG 6 Architecture diagram for automatic operation model (Automatic Operating Module, abbreviated as ⁇ ) as shown in FIG 6,
  • the system runs an application responsible for the basic functions of the AOM (including the generic name of the functional entities for implementing the automatic operation functions of AOME, TNM, etc.), and the foreground provides a foreground application for interacting with the user.
  • the middle layer TNM provides communication mechanisms for AOM and other applications.
  • the function modules are described in detail below. This embodiment is implemented on the BREW platform. The implementation on other platforms can refer to the BREW platform and will not be mentioned.
  • AOME this module is a privileged application running in the background, responsible for the interpretation and execution of user-defined instructions, and the implementation of control logic.
  • the AOME receives the synchronization event from the TNM and sends the corresponding operation instruction to the user-specified application (or global device).
  • This module includes but is not limited to the following sub-function modules: interpretation execution of user scripts, macro recording, management and maintenance of notification, monitoring of running effects (including logging, error prompts, etc.).
  • CPM which is a stand-alone application that acts as an interface between the AOM and the user.
  • the user can issue commands to start or stop, import scripts, etc. to the AOM through the CPM.
  • Specific sub-functions include, but are not limited to: turning on/off AOM functions, starting/stopping specified scripts or macros, importing scripts or macro files, starting/stopping recording macros, defining or registering or unregistering Trigger and Notification through the CPM, simple edit.
  • TNM-L TNM-L exists as part of the application, not a stand-alone application. It collects a series of Triggers that are pre-defined by AOM, inside the application, and sends their corresponding notifications to AOME in real time.
  • the definition of the predefined Notification is stored in the AOM configuration file in the form of code.
  • the manufacturer determines which notifications should be monitored by the AOM.
  • the mobile function modules such as clock, SMS, and incoming calls can define their own built-in Triggers.
  • the specific conditions that need to be monitored are completely determined by the developer according to the actual situation and user requirements, and these predefined Triggers can be tailored by version upgrade or expansion.
  • TNM-G unlike TNM-L, the global monitoring module is also a stand-alone application; however, since TNM-G should also run in the background, TNM-G can also be placed as part of the AOME function.
  • AOME exists as a submodule.
  • TNM-G is mainly responsible for monitoring global resources, such as LEDs, file systems, network devices, etc., which can be monitored by TNM-G. The developer can selectively open the monitoring function of the specific device to the user, and the user defines the corresponding Trigger to synchronize with AOME.
  • TNM-L and TNM-G maintains a timer belonging to itself.
  • the timer's callback function will traverse the Trigger list registered by the application to which it belongs. If the Trigger in the list is triggered, it will send a message to AOME.
  • Notification, (5) Scripts, scripts can be directly recorded to ⁇ in macro mode, or they can be pre-written and then dumped from the PC device to the mobile device (that is, the script is imported into the mobile device).
  • the set of instructions that a script needs to provide generally includes but is not limited to the following:
  • A. Trigger and Notification registration and logout The user needs to indicate to the AOM (specifically to AOME) the condition of the event (equivalent to the event trigger condition in the control logic;). For example, LED devices, users may need to send a notification to AOME when certain pixels on the screen are in a specific RGB color.
  • Embodiment 2 This embodiment describes, by way of example, a process of applying the above AOM for user-defined automatic operation, which is based on the following scenario: The user wants to receive a short message sent by a mobile phone of a specified number with a fixed content.
  • Step 1 write a script, specify the content of the mobile phone and reply that need to be automatically replied;
  • Step 2 specify the AOM to run the script through CPM;
  • Step 3 the script starts to monitor the TNM from the short message module -
  • the SMS notification sent by the -L layer (assuming the OEM defines the notification as AOM SM INCOMING);
  • Step 4 after the new SMS is received, the AOM_SM_INCOMING notification is sent to the AOM, #p this parses out the sender of the other party; if the sender matches
  • the short message interface is started by sending a keyboard message, and the predetermined content is written into the short message and sent back to the other party.
  • Example 3 7 is a flow chart of a test for repeatedly downloading a file link using a mobile phone browser according to Embodiment 3,
  • Triggerl and Trigger2 are two registered triggers (also called trigger objects), if the above trigger is predefined, this is Two triggers will automatically send Notification to AOME by the browser; if there is no predefined for the above triggers, the user will need to register them to send the corresponding Notification: Define Triggerl as the screenshot of the browser's main interface is displayed on the LED, define Trigger2 is displayed for the feature point pixels of the specified link string.
  • Process 4 is a sub-process with several steps, in which several triggers and notifications need to be defined, and will not be described here.
  • the automatic operation process includes the following steps: Step 1: The script starts running; Step 2, Start the browser; Step 3, Triggerl detects whether the browser has been started, and if yes, proceeds to step 4, if the timeout is not Start, then go to step 4 to gather 10; Step 4, go to the specified link; Step 5, Trigger2 detects whether the specified link is opened, and if so, proceeds to step 6, if the timeout is not open, then returns to step 4 to continue processing until timeout The number of times exceeds the preset number of retry attempts, and the process proceeds to step 4: 10; step 6, download the link; step 7, the results of the download are classified into statistics, including download speed, number of failures, and response speed.
  • Step 8 Determine whether the preset number of tests is reached. If yes, go to step 9. Otherwise, return to step 4 to continue processing; step 9, output the test result; step 10, enter the error processing flow, for example, the error will be Information is displayed to the user, an error log is recorded, and the like.
  • the solution provided by the embodiment of the present invention introduces the concept of a trigger and a notification to implement monitoring and response to real-time events. Developers can selectively open specific monitoring functions to users to achieve a balance between user experience and security; and automatically control from lab applications (from Dynamic testing) derived from user applications is also one of the effects of this solution.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Abstract

A mobile terminal and a processing method for the mobile terminal are provided. The method includes that: the Automatic Operating Module Engine (AOME) in the mobile terminal accepts the script for realizing user automatic operation function to configure into the AOME (S102); wherein, the script includes indication information and control logic. The indication information is used for indicating the invocation of an application and/or a global equipment of the mobile terminal, and the control logic is used for indicating the logic sequence of the invocation of an application and/or a global equipment; the AOME parses the script, and based on the indication information and control logic, the AOME invokes the above application and/or global equipment to realize the user automatic operation function (S104). By using the present invention, a user can realize the user-defined automatic operation on a mobile terminal according to his desire. When using the mobile terminal, the user obtains more freedom.

Description

移动终端处理方法及移动终端 技术领域 本发明涉及通信领域, 具体而言, 涉及一种移动终端处理方法及移动终 端。 背景技术 随着移动通信技术和微电子技术的发展, 移动通信终端 (以下简称为移 动终端) 与掌上电脑融合的趋势日异明显。 用户不仅仅希望移动终端能实现 固有的通信功能(例如,打电话、发短信等),还希望手机可以提供文档处理、 上网、 游戏、 多媒体等功能。 近年来,通过移动终端自动处理事务也成为用户需求的方向之一。例如, 某些商务用户希望移动终端能够定时从网上接收邮件, 上传下载文档; 较年 轻的用户可能希望实时关注潮流信息等。 目前, 用户仅能够使用配置在移动终端上的终端厂商所提供的应用 (例 如, 闹钟、 纪念日提醒等) 来实现一些比较简单的自动操作功能, 然而, 终 端厂商提供的自动操作种类较少, 且灵活性低, 不能够按照用户的意愿随意 进行自动操作, 这势必给用户的使用带来不便。 发明内容 本发明的主要目的在于提供一种移动终端处理方法及移动终端, 以至少 解决上述问题。 本发明的一个方面提供了一种移动终端处理方法, 包括: 移动终端中的 The present invention relates to the field of communications, and in particular to a mobile terminal processing method and a mobile terminal. BACKGROUND OF THE INVENTION With the development of mobile communication technologies and microelectronic technologies, the trend of convergence of mobile communication terminals (hereinafter referred to as mobile terminals) with handheld computers has become apparent. Users not only want mobile terminals to implement inherent communication functions (for example, making calls, texting, etc.), but also hope that mobile phones can provide functions such as document processing, Internet access, games, and multimedia. In recent years, automatic processing of transactions through mobile terminals has also become one of the directions of user demand. For example, some business users want mobile terminals to receive emails from the Internet at regular intervals, uploading and downloading documents; younger users may want to pay attention to trend information in real time. Currently, users can only use some applications (such as alarm clocks, anniversaries, etc.) provided by terminal manufacturers configured on mobile terminals to implement some simple automatic operation functions. However, terminal manufacturers provide fewer types of automatic operations. The flexibility is low, and it is not possible to perform automatic operations as desired by the user, which is inconvenient for the user's use. SUMMARY OF THE INVENTION A primary object of the present invention is to provide a mobile terminal processing method and a mobile terminal to solve at least the above problems. An aspect of the present invention provides a mobile terminal processing method, including:
AOME接受将用于实现用户自动操作功能的脚本配置到所述 AOME中, 其 中, 所述脚本包括指示信息和控制逻辑, 所述指示信息用于指示调用所述移 动终端上的应用和 /或全局设备, 所述控制逻辑用于指示调用所述应用和 /或 所述全局设备的逻辑顺序; 所述 AOME解析所述脚本, 并按照所述指示信息 和所述控制逻辑调用所述应用和 /或所述全局设备实现所述用户自动操作功 匕。 在所述控制逻辑还用于指示调用所述应用和 /或所述全局设备时需满足 的事件触发条件的情况下,所述 AOME按照所述指示信息和控制逻辑调用所 述应用和 /或所述全局设备实现所述用户自动操作功能包括: 所述移动终端中 的 TNM在配置于所述 TNM中的事件触发条件被满足的情况下, 通知所述 AOME; 所述 AOME接收到通知, 判断所述被满足的事件触发条件与所述控 制逻辑指示的需满足的事件触发条件相同, 则按照所述控制逻辑指示的所述 逻辑顺序调用所述指示信息指示的所述应用和 /或所述全局设备来实现所述 用户自动操作功能。 所述移动终端中的 TNM在配置于所述 TNM中的事件触发条件被满足的 情况下, 通知所述 AOME包括: 所述 TNM遍历对应于所述 TNM所监控的 应用或全局设备的 Trigger列表, 其中, 所述 Trigger列表中的每个 Trigger 对应于一个事件触发条件, 且在所对应的事件触发条件被满足的情况下被触 发;所述 TNM通过所述遍历检测到所述 Trigger列表中存在被触发的 Trigger, 则将对应于所述被触发的 Trigger的通知消息 Notification返回给所述 AOME。 所述 TNM包括局部 TNM和全局 TNM, 其中, 所述局部 TNM用于监 控应用, 所述全局 TNM用于监控全局设备。 所述局部 TNM位于所述局部 TNM所监控的应用中, 所述全局 TNM为 独立的应用或位于所述 AOME中。 所述 Trigger被预先设置在所述 TNM中, 或者, 由用户通过所述 AOME 配置到所述 TNM中。 通过在所述 AOME上进行宏录制的方式来将所述脚本配置到所述 AOME, 或者, 通过将所述脚本导入所述 AOME来将所述脚本配置到所述 AOME。 本发明的另一个方面提供了一种移动终端, 包括 AOME, 所述 AOME 包括: 配置模块, 设置为接受将用于实现用户自动操作功能的脚本配置到所 述 AOME中, 其中, 所述脚本包括指示信息和控制逻辑, 所述指示信息用于 指示调用所述移动终端上的应用和 /或全局设备,所述控制逻辑用于指示调用 所述应用和 /或所述全局设备的逻辑顺序; 解析模块, 设置为解析所述脚本; 调用模块,设置为按照所述指示信息和所述控制逻辑调用所述应用和 /或所述 全局设备实现所述用户自动操作功能。 在所述控制逻辑还用于指示调用所述应用和 /或所述全局设备时需满足 的事件触发条件的情况下, 所述移动终端还包括: TNM, 设置为在配置于所 述 TNM中的事件触发条件被满足的情况下, 通知所述 AOME; 所述调用模 块设置为在接收到通知的情况下, 判断所述被满足的事件触发条件与所述控 制逻辑指示的需满足的事件触发条件相同, 则按照所述控制逻辑指示的所述 逻辑顺序调用所述指示信息指示的所述应用和 /或所述全局设备来实现所述 用户自动操作功能。 所述 TNM包括: 遍历模块,设置为遍历对应于所述 TNM所监控的应用 或全局设备的 Trigger列表, 其中, 所述 Trigger列表中的每个 Trigger对应于 一个事件触发条件, 且在所对应的事件触发条件被满足的情况下被触发; 通 知模块, 设置为在所述遍历模块检测到所述 Trigger列表中存在被触发的 Trigger的情况下, 将对应于所述被触发的 Trigger的通知消息 Notification返 回给所述 AOME。 所述移动终端还包括: 控制台模块 CPM, 设置为作为所述 AOME和用 户之间的接口, 将用户导入的所述脚本配置到所述 AOME, 或者, 设置为提 供界面接受用户通过宏录制将所述脚本配置到所述 AOME。 通过本发明,釆用 AOME按照用户提供的脚本中的指示信息和控制逻辑 调用相应的应用和 /或全局设备来实现用户自动操作功能,解决了相关技术中 移动终端不能够按照用户的意愿实现用户自动操作功能的问题, 用户可以根 据自己的意愿在移动终端上实现自定义的自动操作, 这无疑为用户使用移动 终端提供了更大的自由度。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部 分, 本发明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的 不当限定。 在附图中: 图 1是才艮据本发明实施例的移动终端处理方法的流程图; 图 2是 居本发明实施例的移动终端的结构框图; 图 3是 居本发明实施例的移动终端的优选结构框图一; 图 4是 居本发明实施例的移动终端的优选结构框图二; 图 5是 居本发明实施例的移动终端的优选结构框图三; 图 6是根据实施例 1的移动终端中用于实现用户自动操作的自动操作模 型的架构示意图; 图 7是根据实施例 3的测试使用手机浏览器反复下载一个文件链接的流 程图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是, 在 不冲突的情况下, 本申请中的实施例及实施例中的特征可以相互组合。 图 1是才艮据本发明实施例的移动终端处理方法的流程图, 如图 1所示, 该方法包括: 步骤 S 102, 移动终端中的自动操作模型引擎 ( Automatic Operating Module Engine, 简称为 AOME )接受将用于实现用户自动操作功能的 本 ( Script ) 配置到该 AOME中, 其中, 该脚本包括指示信息和控制逻辑, 指 示信息用于指示调用该移动终端上的应用和 /或全局设备,控制逻辑用于指示 调用应用和 /或全局设备的逻辑顺序; 步骤 S 104 , AOME解析脚本, 并按照指示信息和控制逻辑调用以上的 应用和 /或全局设备实现用户自动操作功能。 通过该方法, 在移动终端中设置 AOME, 由该 AOME对用于实现用户 自动操作功能的脚本进行解析、 运行(涉及到逻辑控制及应用和 /或全局设备 的调用), 以便实现该用户自动操作功能。该方法可广泛应用于需要移动终端 自动 居某些实时发生的状况代替用户自动动作的场合, 也可用于移动平台 的自动测试。 用户可以根据自身喜好自由选择安排移动终端所做的事情, 诸 如接收彩信后自动转存图片、 定时自动拨打电话这类以前需要开发商内嵌的 功能现在也可以由用户自己来完成了。 自动操控功能无疑为用户使用移动终 端提供了更大的自由度。 优选地, 在 AOME实现用户自动操作功能时, AOME可以对执行的结 果进行监控, 例如, 对执行日志进行记录、 出错时进行错误提示等。 在控制逻辑还用于指示调用应用和 /或全局设备时需满足的事件触发条 件的情况下, 移动终端中的触发器与通知监视器 ( Trigger and Notification Monitor, 简称为 TNM ) 在配置于 TNM中的事件触发条件被满足的情况下, 通知 AOME; AOME接收到通知, 判断被满足的事件触发条件与控制逻辑指 示的需满足的事件触发条件相同, 则按照控制逻辑指示的逻辑顺序调用指示 信息指示的应用和 /或全局设备来实现用户自动操作功能。 通过以上的方法, 能够实现条件控制, 在一定事件被触发的时候, 进行后续的操作, 能够实现 更加复杂, 更加多元化的用户自动操作功能。 在实际应用中,可以通过触发器对象( Trigger )来实现条件的控制。 Trigger 是用于与 AOME同步的触发器对象, 可以由厂商内置于局部 TNM ( TNM - Local , 简称为 TNM-L ) , 也可以由用户定义用于全局 TNM ( TNM - Global , 简称为 TNM-G )。 当一个指定的事件 (Event ) 发生时, Trigger将发送相应 的通 口 ( Notification ) 到 AOME, Notification是与 Trigger 目关联的通 口。 移动终端中的 TNM在配置于 TNM中的事件触发条件被满足的情况下, 通知 AOME的过程可以包括以下处理: TNM遍历对应于该 TNM所监控的 应用或全局设备的 Trigger列表, 其中, Trigger列表中的每个 Trigger对应于 一个事件触发条件, 且在所对应的事件触发条件被满足的情况下被触发; TNM通过遍历检测到 Trigger列表中存在被触发的 Trigger, 则将对应于被触 发的 Trigger的通知消息 Notification返回给 AOME。 该方法易于实现。 以上的 TNM可以包括局部 TNM和全局 TNM , 其中, 局部 TNM用于 监控应用, 全局 TNM用于监控全局设备。 局部 TNM可以位于局部 TNM所 监控的应用中,全局 TNM可以为独立的应用或位于 AOME中。 Trigger可以 被预先设置在 TNM中, 或者, 也可以由用户通过 AOME配置到 TNM中。 一般情况下, 局部 TNM中的 Trigger多为预先设置的, 而全局 TNM中的 Trigger可以为预先设置的, 也可以由用户通过 AOME配置。 优选地, 可以通过在 AOME上进行宏( Macro, 由用户录制的控制逻辑, 通常以 έρ本的方式存放)录制的方式来将έρ本配置到 AOME, 也可以通过将 έρ本导入 AOME来将έρ本配置到 ΑΟΜΕ。 图 2是 居本发明实施例的移动终端的结构框图, 该移动终端包括 AOME 22 , AOME 22包括: 配置模块 24 , 设置为接受将用于实现用户自动 操作功能的脚本配置到 AOME 22中, 其中, 脚本包括指示信息和控制逻辑, 指示信息用于指示调用移动终端上的应用和 /或全局设备,控制逻辑用于指示 调用应用和 /或全局设备的逻辑顺序; 解析模块 26 , 设置为解析 本; 调用 模块 28 , 设置为按照指示信息和控制逻辑调用应用和 /或全局设备实现用户 自动操作功能。 通过该移动终端中设置的 ΑΟΜΕ 22 ,对用于实现用户自动操作功能的脚 本进行解析、 运行 (涉及到逻辑控制及应用和 /或全局设备的调用), 以便实 现该用户自动操作功能, 这无疑为用户使用移动终端提供了更大的自由度。 图 3是 居本发明实施例的移动终端的优选结构框图一, 如图 3所示, 在上述控制逻辑还用于指示调用应用和 /或全局设备时需满足的事件触发条 件的情况下, 移动终端还可以包括: ΤΝΜ 32 , 设置为在配置于 ΤΝΜ 32中的 事件触发条件被满足的情况下, 通知 ΑΟΜΕ 22; 调用模块 28设置为在接收 到通知的情况下, 判断被满足的事件触发条件与控制逻辑指示的需满足的事 件触发条件相同, 则按照控制逻辑指示的逻辑顺序调用指示信息指示的应用 和 /或全局设备来实现用户自动操作功能。 图 4是才艮据本发明实施例的移动终端的优选结构框图二, 如图 4所示,The AOME accepts a script configuration for implementing a user automatic operation function into the AOME, wherein the script includes indication information and control logic, the indication information is used to indicate an application and/or global call on the mobile terminal The control logic is configured to indicate a logical sequence of invoking the application and/or the global device; the AOME parses the script, and invokes the application and/or according to the indication information and the control logic The global device implements the automatic operation of the user. In the case that the control logic is further used to indicate an event trigger condition to be met when the application and/or the global device is invoked, the AOME invokes the application and/or the location according to the indication information and control logic. The global device implementing the user automatic operation function includes: the TNM in the mobile terminal notifying the AOME if the event triggering condition configured in the TNM is satisfied; the AOME receiving the notification, determining the location The event triggering condition that is satisfied is the same as the event triggering condition that is to be satisfied by the control logic, and the application and/or the global indication indicated by the indication information is invoked according to the logical sequence indicated by the control logic. The device implements the automatic operation function of the user. The TNM in the mobile terminal, when the event triggering condition configured in the TNM is satisfied, notifying the AOME includes: the TNM traversing a Trigger list corresponding to an application or a global device monitored by the TNM, Each Trigger in the Trigger list corresponds to an event triggering condition, and is triggered if the corresponding event triggering condition is met; the TNM detects that the Trigger list exists in the Tringer by the traversal The triggered Trigger returns a notification message Notification corresponding to the triggered Trigger to the AOME. The TNM includes a local TNM and a global TNM, where the local TNM is used to monitor an application, and the global TNM is used to monitor a global device. The local TNM is located in an application monitored by the local TNM, and the global TNM is an independent application or located in the AOME. The Trigger is preset in the TNM, or is configured by the user through the AOME into the TNM. The script is configured to the AOME by macro recording on the AOME, or the script is configured to the AOME by importing the script into the AOME. Another aspect of the present invention provides a mobile terminal, including an AOME, the AOME includes: a configuration module configured to accept a script configured to implement a user automatic operation function into the AOME, where the script includes Instructing information and control logic, the indication information being used to indicate an application and/or a global device on the mobile terminal, the control logic is configured to indicate a logical sequence of invoking the application and/or the global device; a module, configured to parse the script; a calling module configured to invoke the application and/or the global device to implement the user automatic operation function according to the indication information and the control logic. In the case that the control logic is further used to indicate an event triggering condition to be met when the application and/or the global device is invoked, the mobile terminal further includes: TNM, configured to be configured in the TNM. In the case that the event trigger condition is satisfied, the AOME is notified; the calling module is configured to determine, when the notification is received, the event triggering condition that is satisfied and the event triggering condition that is required to be satisfied by the control logic Similarly, the application and/or the global device indicated by the indication information are invoked according to the logical sequence indicated by the control logic to implement the user automatic operation function. The TNM includes: a traversal module, configured to traverse a Trigger list corresponding to an application or a global device monitored by the TNM, where each Trigger in the Trigger list corresponds to an event trigger condition, and corresponds to The event triggering condition is triggered; the notification module is configured to notify the notification message corresponding to the triggered Trigger if the traversal module detects that there is a triggered Trigger in the Trigger list Return to the AOME. The mobile terminal further includes: a console module CPM, configured to be an interface between the AOME and the user, configured to configure the script imported by the user to the AOME, or set to provide an interface to accept the user to record through the macro The script is configured to the AOME. Through the invention, the AOME is used to implement the automatic operation function of the user by calling the corresponding application and/or the global device according to the instruction information and the control logic in the script provided by the user, and solving the related art, the mobile terminal cannot implement the automatic operation according to the user's intention. The problem of the operation function, the user can implement the customized automatic operation on the mobile terminal according to his own wishes, which undoubtedly provides the user with greater freedom to use the mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, 1 is a flowchart of a mobile terminal processing method according to an embodiment of the present invention; FIG. 2 is a structural block diagram of a mobile terminal according to an embodiment of the present invention; FIG. 3 is a mobile terminal according to an embodiment of the present invention; Preferred structural block diagram 1; 4 is a block diagram of a preferred structure of a mobile terminal according to an embodiment of the present invention; FIG. 5 is a block diagram 3 of a preferred structure of a mobile terminal according to an embodiment of the present invention; FIG. 6 is a diagram for implementing automatic user in a mobile terminal according to Embodiment 1. Schematic diagram of an automatic operation model of operation; FIG. 7 is a flow chart of a test for repeatedly downloading a file link using a mobile phone browser according to the embodiment 3. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. FIG. 1 is a flowchart of a method for processing a mobile terminal according to an embodiment of the present invention. As shown in FIG. 1, the method includes: Step S102: An Automatic Operating Module Engine (AOME in the mobile terminal) Accepting a script configuration for implementing a user automatic operation function into the AOME, wherein the script includes indication information and control logic, the indication information is used to indicate that an application and/or a global device on the mobile terminal is invoked, Control logic is used to indicate the logical sequence of invoking the application and/or the global device; Step S104, the AOME parses the script, and invokes the above application and/or global device in accordance with the indication information and control logic to implement the user automatic operation function. Through the method, AOME is set in the mobile terminal, and the AOME is used to parse and run the script for implementing the automatic operation function of the user (involving logic control and application and/or global device call), so as to implement the automatic operation of the user. Features. The method can be widely applied to a situation where a mobile terminal needs to automatically live in some real-time situations instead of the user's automatic action, and can also be used for automatic testing of the mobile platform. Users can freely choose to arrange what the mobile terminal does according to their own preferences, such as automatically transferring pictures after receiving MMS, and automatically making calls at regular intervals. The functions that need to be embedded in the developer can now be completed by the users themselves. The automatic control function undoubtedly provides users with more freedom to use the mobile terminal. Preferably, when AOME implements the user automatic operation function, AOME can monitor the execution result, for example, recording the execution log, making an error prompt when an error occurs, and the like. In the case where the control logic is also used to indicate an event trigger condition to be met when the application and/or the global device is invoked, the Trigger and Notification Monitor (TNM) in the mobile terminal is configured in the TNM. When the event trigger condition is satisfied, the AOME is notified; the AOME receives the notification, and determines that the satisfied event trigger condition is the same as the event trigger condition indicated by the control logic, and then invokes the indication information indication according to the logical sequence indicated by the control logic. Application and / or global device to achieve user automatic operation functions. Through the above method, conditional control can be realized, and when a certain event is triggered, subsequent operations can be performed, and a more complicated and diversified user automatic operation function can be realized. In practical applications, conditional control can be achieved through a trigger object ( Trigger ). Trigger is a trigger object used to synchronize with AOME. It can be built by the manufacturer to local TNM (TNM - Local, referred to as TNM-L), or can be defined by the user for global TNM (TNM - Global, referred to as TNM-G). ). When a specified event (Event) occurs, Trigger will send the corresponding notification to AOME, which is the port associated with the Trigger. In the case that the TNM in the mobile terminal is satisfied that the event triggering condition configured in the TNM is satisfied, the process of notifying the AOME may include the following processing: The TNM traverses the Trigger list corresponding to the application or the global device monitored by the TNM, where the Trigger list Each Trigger corresponds to an event trigger condition and is triggered if the corresponding event trigger condition is satisfied; the TNM detects that there is a triggered Trigger in the Trigger list by traversing, which will correspond to the triggered Trigger The notification message Notification is returned to AOME. This method is easy to implement. The above TNM may include a local TNM for monitoring applications and a global TNM for monitoring global devices. The local TNM can be located in an application monitored by the local TNM, and the global TNM can be a standalone application or located in the AOME. The Trigger can be pre-configured in the TNM, or it can be configured by the user into the TNM via AOME. In general, the Trigger in the local TNM is mostly preset, and the Trigger in the global TNM can be preset or configured by the user through the AOME. Preferably, the έρ can be configured to AOME by recording macro (Macro, user-recorded control logic, usually stored in έρ本) on AOME, or by importing έρ本 into AOME. This configuration is awkward. 2 is a structural block diagram of a mobile terminal according to an embodiment of the present invention. The mobile terminal includes an AOME 22. The AOME 22 includes: a configuration module 24 configured to accept a script configured to implement a user automatic operation function into the AOME 22, wherein , the script includes instructions and control logic, The indication information is used to indicate an application and/or a global device on the calling mobile terminal, the control logic is used to indicate a logical sequence of invoking the application and/or the global device; the parsing module 26 is configured to parse the copy; the calling module 28 is set to follow the indication Information and control logic invokes applications and/or global devices to implement user automation functions. Through the ΑΟΜΕ 22 set in the mobile terminal, the script for implementing the automatic operation function of the user is parsed and operated (involving logic control and application and/or global device call), so as to realize the automatic operation function of the user, which is undoubtedly Provides greater freedom for users to use mobile terminals. 3 is a block diagram of a preferred structure of a mobile terminal according to an embodiment of the present invention. As shown in FIG. 3, when the above control logic is further used to indicate an event trigger condition to be met when an application and/or a global device is invoked, the mobile terminal moves. The terminal may further include: ΤΝΜ 32, configured to notify ΑΟΜΕ 22 when the event trigger condition configured in ΤΝΜ 32 is satisfied; the calling module 28 is configured to determine that the event trigger condition is satisfied if the notification is received The same as the event triggering condition indicated by the control logic, the application and/or global device indicated by the indication information is invoked in a logical order indicated by the control logic to implement the user automatic operation function. 4 is a block diagram 2 of a preferred structure of a mobile terminal according to an embodiment of the present invention, as shown in FIG.
ΤΝΜ 32可以包括: 遍历模块 42 , 设置为遍历对应于 ΤΝΜ 32所监控的应用 或全局设备的触发器对象 Trigger列表, 其中, Trigger列表中的每个 Trigger 对应于一个事件触发条件, 且在所对应的事件触发条件被满足的情况下被触 发; 通知模块 44 , 设置为在遍历模块 42检测到 Trigger列表中存在被触发的 Trigger的情况下, ^"对应于被触发的 Trigger的通知消息 Notification返回给 AOME 22。 图 5是 居本发明实施例的移动终端的优选结构框图三, 如图 5所示, 该移动终端还可以包括: 控制台模块 ( Control Panel Module, 简称为 CPM ) 52 , 设置为作为 AOME 22和用户之间的接口, 将用户导入的脚本配置到 AOME 22 , 或者,设置为提供界面接受用户通过宏录制将 本配置到 AOME 11。 下面描述的实施例 1-3 , 综合了上述多个优选实施例的技术方案。 实施例 1 图 6是根据实施例 1的移动终端中用于实现用户自动操作的自动操作模 型( Automatic Operating Module , 简称为 ΑΟΜ )的架构示意图,如图 6所示, 在系统启动时后台运行一个应用负责 AOM (包括 AOME、 TNM等模块的用 于实现自动操作功能的功能实体的总称) 的基本功能, 同时前台提供一个前 台应用程序用于与用户进行交互。 中间层 TNM则提供 AOM和其它应用的 通信机制。 下面就各功能模块分别进行详细说明。 该实施例在 BREW平台上 实现, 其它平台上的实现可参考 BREW平台, 将不再赞述。 The ΤΝΜ 32 may include: a traversal module 42 configured to traverse a trigger object Trigger list corresponding to the application or global device monitored by the UI 32, wherein each Trigger in the Trigger list corresponds to an event trigger condition, and corresponds to The event triggering condition is triggered; the notification module 44 is configured to, in the case that the traversing module 42 detects that there is a triggered Trigger in the Trigger list, ^" the notification message corresponding to the triggered Trigger is returned to the Notification message AOME 22. Figure 5 is a block diagram of a preferred structure of a mobile terminal according to an embodiment of the present invention. As shown in Figure 5, the mobile terminal may further include: a Control Panel Module (CPM) 52, which is set as The interface between AOME 22 and the user configures the user-imported script to AOME 22, or is set to provide an interface to accept the user's configuration to AOME 11 through macro recording. The following describes Embodiment 1-3, which combines the above Technical Solution of a Preferred Embodiment. Embodiment 1 FIG. 6 is a diagram for implementing automatic user in a mobile terminal according to Embodiment 1. Architecture diagram for automatic operation model (Automatic Operating Module, abbreviated as ΑΟΜ) as shown in FIG 6, In the background, the system runs an application responsible for the basic functions of the AOM (including the generic name of the functional entities for implementing the automatic operation functions of AOME, TNM, etc.), and the foreground provides a foreground application for interacting with the user. The middle layer TNM provides communication mechanisms for AOM and other applications. The function modules are described in detail below. This embodiment is implemented on the BREW platform. The implementation on other platforms can refer to the BREW platform and will not be mentioned.
( 1 ) AOME, 该模块为运行于后台的特权应用, 负责对用户定义的指令 进行解释和执行, 操控逻辑的实施。 AOME接收 TNM传来的同步事件, 并 将相应的操作指令发给用户指定的应用(或全局设备)。该模块包含但不限于 下述子功能模块: 用户脚本的解释执行、宏录制、 Notification的管理和维护、 运行效果监控 (包括日志记录、 错误提示等)。 (1) AOME, this module is a privileged application running in the background, responsible for the interpretation and execution of user-defined instructions, and the implementation of control logic. The AOME receives the synchronization event from the TNM and sends the corresponding operation instruction to the user-specified application (or global device). This module includes but is not limited to the following sub-function modules: interpretation execution of user scripts, macro recording, management and maintenance of notification, monitoring of running effects (including logging, error prompts, etc.).
( 2 ) CPM,其为一独立运行的应用程序,充当 AOM和用户之间的接口。 用户可通过 CPM向 AOM下达启动或停止的指令、导入脚本等。 其具体子功 能包括但不限于: 开启 /关闭 AOM功能、 启动 /停止指定脚本或宏、 导入脚本 或宏文件、 开始 /停止录制宏、 用户通过该 CPM定义或注册或注销 Trigger 和 Notification, 简单 本编辑。 (2) CPM, which is a stand-alone application that acts as an interface between the AOM and the user. The user can issue commands to start or stop, import scripts, etc. to the AOM through the CPM. Specific sub-functions include, but are not limited to: turning on/off AOM functions, starting/stopping specified scripts or macros, importing scripts or macro files, starting/stopping recording macros, defining or registering or unregistering Trigger and Notification through the CPM, simple edit.
( 3 ) TNM-L, TNM-L作为应用程序的一部分存在, 不是独立的应用。 它负责收集由 AOM预定义、 应用程序内部发生的一系列 Trigger, 并将其对 应的 Notification实时发送给 AOME。 预定义 Notification的定义以代码的形 式存放在 AOM的配置文件中, 由厂家确定有哪些通知应该被 AOM监控。 一般时钟、 短信、 来电等移动功能模块都可以定义出各自的内置 Triggers, 具体需要监控哪些状态完全由开发厂商根据实际情况和用户需求决定, 且可 以通过版本升级对这些预定义的 Trigger进行裁剪或扩充。 (3) TNM-L, TNM-L exists as part of the application, not a stand-alone application. It collects a series of Triggers that are pre-defined by AOM, inside the application, and sends their corresponding notifications to AOME in real time. The definition of the predefined Notification is stored in the AOM configuration file in the form of code. The manufacturer determines which notifications should be monitored by the AOM. Generally, the mobile function modules such as clock, SMS, and incoming calls can define their own built-in Triggers. The specific conditions that need to be monitored are completely determined by the developer according to the actual situation and user requirements, and these predefined Triggers can be tailored by version upgrade or expansion.
( 4 ) TNM-G, 不同于 TNM-L,全局监控模块也是一个独立的应用程序; 但是, 由于 TNM-G也应在后台运行, 因此也可以将 TNM-G作为 AOME功 能的一部分, 放到 AOME中作为一个子模块存在。 TNM-G主要负责对全局 资源进行监控, 诸如 LED、 文件系统、 网络设备等都可以作为 TNM-G的监 控对象。 开发厂商可以有选择地向用户开放特定设备的监控功能, 并由用户 定义对应的 Trigger与 AOME进行同步。 (4) TNM-G, unlike TNM-L, the global monitoring module is also a stand-alone application; however, since TNM-G should also run in the background, TNM-G can also be placed as part of the AOME function. AOME exists as a submodule. TNM-G is mainly responsible for monitoring global resources, such as LEDs, file systems, network devices, etc., which can be monitored by TNM-G. The developer can selectively open the monitoring function of the specific device to the user, and the user defines the corresponding Trigger to synchronize with AOME.
TNM-L和 TNM-G各自维护隶属于自身的一个定时器, 该定时器的回调 函数将遍历自身所属应用所注册的 Trigger列表,若列表中的 Trigger被触发, 则向 AOME发送 ^目应的 Notification, ( 5 )脚本, 脚本可以用宏的方式直接录制到 ΑΟΜΕ , 也可以预先编写 好再从 PC设备转储到移动设备(即该脚本被导入到移动设备中) 上。 脚本 需要提供的指令集一般包括但不限于以下几方面: Each of TNM-L and TNM-G maintains a timer belonging to itself. The timer's callback function will traverse the Trigger list registered by the application to which it belongs. If the Trigger in the list is triggered, it will send a message to AOME. Notification, (5) Scripts, scripts can be directly recorded to ΑΟΜΕ in macro mode, or they can be pre-written and then dumped from the PC device to the mobile device (that is, the script is imported into the mobile device). The set of instructions that a script needs to provide generally includes but is not limited to the following:
A. Trigger和 Notification的注册和注销: 用户需要向 AOM指明 (具体 指示给 AOME ) 该事件的发生条件 (相当于控制逻辑中的事件触发条件;)。 比如 LED设备, 用户可能需要在屏幕上某几个像素为特定的 RGB颜色时, 向 AOME发送一个 Notification A. Trigger and Notification registration and logout: The user needs to indicate to the AOM (specifically to AOME) the condition of the event (equivalent to the event trigger condition in the control logic;). For example, LED devices, users may need to send a notification to AOME when certain pixels on the screen are in a specific RGB color.
B. 控制逻辑中的调用应用和 /或全局设备的逻辑顺序, 一般通过普通算 术和逻辑指令来实现。 C. 用于指示调用应用和 /或全局设备的指示信息, 可以包括: 特定功能 的库函数、 指定操作的指令(比如按键、 触摸屏滑动等)、 用户 IO指令(如 用户 log输出、 屏幕提示信息等) 等。 实施例 2 该实施例通过举例的方式描述了应用以上的 AOM进行用户自定义的自 动操作的过程, 该实施例基于如下场景: 用户希望收到指定号码的手机发来 的短信后以固定的内容自动回复, 那么用户可以作下面的设置: 步骤 1 , 编写脚本, 指定需要自动回复的手机和回复的内容; 步骤 2, 通过 CPM指定 AOM运行该脚本; 步骤 3 , 脚本开始监控从短信模块的 TNM-L层发出的短信通知 (假设 OEM定义该通知为 AOM SM INCOMING ); 步骤 4, 新短信收到后, AOM_SM_INCOMING通知被发到 AOM, #p 本解析出对方发件人; 若发件人匹配, 则通过发送键盘消息的方式启动写短 信界面,将预定的内容写入短信并发回给对方。作为另一种可选的实施方式, 也可以不开启写短信界面, 在后台进行构造短信的处理, 并将构造后的短信 发到指定号码。 实施例 3 图 7是根据实施例 3的测试使用手机浏览器反复下载一个文件链接的流 程图, Triggerl和 Trigger2是两个注册的触发器(也称触发器对象), 如果以 上触发器为预定义的, 这两个触发器将由浏览器自动发送 Notification到 AOME; 如果对以上触发器没有预定义, 用户就需要自己注册它们来发送相 应的 Notification: 定义 Triggerl为浏览器主界面的截图被显示在 LED上, 定义 Trigger2为指定链接的字符串的特征点像素被显示。 过程 4是一个包含 数个步骤的子过程, 其中同样需要定义数个触发器和通知, 这里不再赘述。 如图 7所示, 该自动操作过程包括以下步骤: 步骤 1 , 脚本开始运行; 步骤 2, 启动浏览器; 步骤 3 , Triggerl检测浏览器是否已启动, 若是, 则转入步骤 4, 若超时 未启动, 则转入步 4聚 10; 步骤 4, 转到指定链接; 步骤 5 , Trigger2检测指定链接是否被打开, 若是, 则进入步骤 6, 若超 时未打开, 则返回步骤 4继续处理, 直到超时次数超过了预设的重试( Retry ) 次数, 转入步 4聚 10; 步骤 6, 下载该链接; 步骤 7, 将本次下载的结果归入统计数据, 包括下载速度、 失败次数、 响应速度等; 步骤 8, 判断是否达到预设的测试次数, 若是, 则进入步骤 9, 否则, 返回步 4聚 6继续处理; 步骤 9, 输出测试结果; 步骤 10, 进入错误处理流程, 例如, 将错误信息显示给用户、 记录错误 日志等。 综上所述, 本发明实施例提供的方案引入了触发器和通知的概念, 实现 对实时事件的监控和响应。 开发厂商可以有选择地对用户开放特定的监控功 能, 以获得用户体验和安全性上的平衡; 同时将自动操控从实验室应用 ( 自 动测试)衍生到用户应用也是该方案的效果之一。 用户可以根据自身喜好自 由选择安排手机所做的事情, 诸如接收彩信后自动转存图片、 定时自动拨打 电话这类以前需要开发商内嵌的功能现在也可以由用户自己来完成了, 自动 操控功能无疑为用户使用手机等移动平台提供了更大的自由度。 需要说明的是, 在附图的流程图示出的步骤可以在诸如一组计算机可执 行指令的计算机系统中执行, 并且, 虽然在流程图中示出了逻辑顺序, 但是 在某些情况下, 可以以不同于此处的顺序执行所示出或描述的步骤。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布 在多个计算装置所组成的网络上, 可选地, 它们可以用计算装置可执行的程 序代码来实现, 从而, 可以将它们存储在存储装置中由计算装置来执行, 或 者将它们分别制作成各个集成电路模块, 或者将它们中的多个模块或步骤制 作成单个集成电路模块来实现。 这样, 本发明不限制于任何特定的硬件和软 件结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本 领域的技术人员来说, 本发明可以有各种更改和变化。 凡在本发明的^"神和 原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护 范围之内。 B. The logical sequence of calling applications and/or global devices in the control logic, typically implemented by ordinary arithmetic and logic instructions. C. Instructions for instructing the application and/or global device to be invoked, which may include: library functions for specific functions, instructions for specifying operations (such as buttons, touch screen sliding, etc.), user IO commands (such as user log output, screen prompt information) and many more. Embodiment 2 This embodiment describes, by way of example, a process of applying the above AOM for user-defined automatic operation, which is based on the following scenario: The user wants to receive a short message sent by a mobile phone of a specified number with a fixed content. Automatic reply, then the user can make the following settings: Step 1, write a script, specify the content of the mobile phone and reply that need to be automatically replied; Step 2, specify the AOM to run the script through CPM; Step 3, the script starts to monitor the TNM from the short message module - The SMS notification sent by the -L layer (assuming the OEM defines the notification as AOM SM INCOMING); Step 4, after the new SMS is received, the AOM_SM_INCOMING notification is sent to the AOM, #p this parses out the sender of the other party; if the sender matches Then, the short message interface is started by sending a keyboard message, and the predetermined content is written into the short message and sent back to the other party. As another optional implementation manner, the short message writing interface may not be opened, the short message processing is performed in the background, and the constructed short message is sent to the designated number. Example 3 7 is a flow chart of a test for repeatedly downloading a file link using a mobile phone browser according to Embodiment 3, Triggerl and Trigger2 are two registered triggers (also called trigger objects), if the above trigger is predefined, this is Two triggers will automatically send Notification to AOME by the browser; if there is no predefined for the above triggers, the user will need to register them to send the corresponding Notification: Define Triggerl as the screenshot of the browser's main interface is displayed on the LED, define Trigger2 is displayed for the feature point pixels of the specified link string. Process 4 is a sub-process with several steps, in which several triggers and notifications need to be defined, and will not be described here. As shown in FIG. 7, the automatic operation process includes the following steps: Step 1: The script starts running; Step 2, Start the browser; Step 3, Triggerl detects whether the browser has been started, and if yes, proceeds to step 4, if the timeout is not Start, then go to step 4 to gather 10; Step 4, go to the specified link; Step 5, Trigger2 detects whether the specified link is opened, and if so, proceeds to step 6, if the timeout is not open, then returns to step 4 to continue processing until timeout The number of times exceeds the preset number of retry attempts, and the process proceeds to step 4: 10; step 6, download the link; step 7, the results of the download are classified into statistics, including download speed, number of failures, and response speed. Step 8: Determine whether the preset number of tests is reached. If yes, go to step 9. Otherwise, return to step 4 to continue processing; step 9, output the test result; step 10, enter the error processing flow, for example, the error will be Information is displayed to the user, an error log is recorded, and the like. In summary, the solution provided by the embodiment of the present invention introduces the concept of a trigger and a notification to implement monitoring and response to real-time events. Developers can selectively open specific monitoring functions to users to achieve a balance between user experience and security; and automatically control from lab applications (from Dynamic testing) derived from user applications is also one of the effects of this solution. Users can freely choose to arrange the things that the mobile phone does according to their own preferences, such as automatically transferring pictures after receiving MMS, and automatically making calls at regular intervals. The functions that need to be embedded in the developer can now be completed by the user himself. Undoubtedly, users are given more freedom to use mobile platforms such as mobile phones. It should be noted that the steps shown in the flowchart of the accompanying drawings may be performed in a computer system such as a set of computer executable instructions, and, although the logical order is shown in the flowchart, in some cases, The steps shown or described may be performed in an order different than that herein. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Claims

权 利 要 求 书 Claim
1. 一种移动终端处理方法, 包括: A mobile terminal processing method, comprising:
移动终端中的自动操作模型引擎 AOME接受将用于实现用户自 动操作功能的脚本配置到所述 AOME中, 其中, 所述脚本包括指示信 息和控制逻辑, 所述指示信息用于指示调用所述移动终端上的应用和 / 或全局设备, 所述控制逻辑用于指示调用所述应用和 /或所述全局设备 的逻辑顺序;  The automatic operation model engine AOME in the mobile terminal accepts a script configuration for implementing a user automatic operation function into the AOME, wherein the script includes indication information and control logic, the indication information is used to indicate that the movement is invoked An application and/or a global device on the terminal, the control logic being configured to indicate a logical sequence of invoking the application and/or the global device;
所述 AOME解析所述έρ本,并按照所述指示信息和所述控制逻辑 调用所述应用和 /或所述全局设备实现所述用户自动操作功能。  The AOME parses the έρ本, and invokes the application and/or the global device according to the indication information and the control logic to implement the user automatic operation function.
2. 根据权利要求 1所述的方法, 其中, 在所述控制逻辑还用于指示调用 所述应用和 /或所述全局设备时需满足的事件触发条件的情况下, 所述 AOME按照所述指示信息和控制逻辑调用所述应用和 /或所述全局设 备实现所述用户自动操作功能包括: 2. The method according to claim 1, wherein, in the case that the control logic is further used to indicate an event trigger condition to be met when the application and/or the global device is invoked, the AOME is as described Instructing the information and control logic to invoke the application and/or the global device to implement the user automatic operation function includes:
所述移动终端中的触发器与通知监视器 TNM在配置于所述 TNM 中的事件触发条件被满足的情况下, 通知所述 AOME;  The trigger in the mobile terminal and the notification monitor TNM notify the AOME if the event triggering condition configured in the TNM is satisfied;
所述 AOME接收到通知,判断所述被满足的事件触发条件与所述 控制逻辑指示的需满足的事件触发条件相同, 则按照所述控制逻辑指 示的所述逻辑顺序调用所述指示信息指示的所述应用和 /或所述全局 设备来实现所述用户自动操作功能。  Receiving, by the AOME, that the met event triggering condition is the same as the event triggering condition that is to be satisfied by the control logic, and instructing the indication information according to the logical sequence indicated by the control logic The application and/or the global device implements the user automatic operation function.
3. 才艮据权利要求 2所述的方法, 其中, 所述移动终端中的 TNM在配置 于所述 TNM中的事件触发条件被满足的情况下, 通知所述 AOME包 括: 3. The method according to claim 2, wherein the TNM in the mobile terminal notifies the AOME that the event triggering condition configured in the TNM is satisfied:
所述 TNM遍历对应于所述 TNM所监控的应用或全局设备的触发 器对象 Trigger列表, 其中, 所述 Trigger列表中的每个 Trigger对应于 一个事件触发条件, 且在所对应的事件触发条件被满足的情况下被触 发;  The TNM traverses a trigger object Trigger list corresponding to the application or global device monitored by the TNM, where each Trigger in the Trigger list corresponds to an event trigger condition, and the corresponding event trigger condition is Triggered in case of satisfaction;
所述 TNM通过所述遍历检测到所述 Trigger列表中存在被触发的 Trigger , 则 夺对应于所述被触发的 Trigger的通^ ^消息 Notification返 回给所述 AOME。 The TNM detects that there is a triggered Trigger in the Trigger list by using the traversal, and then returns a message corresponding to the triggered Trigger to the AOME.
4. 才艮据权利要求 2或 3所述的方法, 其中, 所述 TNM包括局部 TNM和 全局 TNM, 其中, 所述局部 TNM用于监控应用, 所述全局 TNM用 于监控全局设备。 4. The method according to claim 2 or 3, wherein the TNM comprises a local TNM and a global TNM, wherein the local TNM is used for monitoring applications, and the global TNM is used for monitoring global devices.
5. 根据权利要求 4所述的方法,其中,所述局部 TNM位于所述局部 TNM 所监控的应用中,所述全局 TNM为独立的应用或位于所述 AOME中。 5. The method of claim 4, wherein the local TNM is located in an application monitored by the local TNM, the global TNM being a standalone application or located in the AOME.
6. 才艮据权利要求 3所述的方法, 其中, 所述 Trigger被预先设置在所述 TNM中, 或者, 由用户通过所述 AOME配置到所述 TNM中。 6. The method according to claim 3, wherein the Trigger is preset in the TNM, or is configured by the user into the TNM through the AOME.
7. 根据权利要求 1所述的方法, 其中, 通过在所述 AOME上进行宏录制 的方式来将所述脚本配置到所述 AOME, 或者, 通过将所述脚本导入 所述 AOME来将所述脚本配置到所述 AOME。 7. The method according to claim 1, wherein the script is configured to the AOME by macro recording on the AOME, or by importing the script into the AOME The script is configured to the AOME.
8. —种移动终端, 包括自动操作模型引擎 AOME, 所述 AOME包括: 配置模块, 设置为接受将用于实现用户自动操作功能的脚本配置 到所述 AOME中, 其中, 所述脚本包括指示信息和控制逻辑, 所述指 示信息用于指示调用所述移动终端上的应用和 /或全局设备, 所述控制 逻辑用于指示调用所述应用和 /或所述全局设备的逻辑顺序; 解析模块, 设置为解析所述脚本; 8. A mobile terminal, comprising an automatic operation model engine AOME, the AOME comprising: a configuration module configured to accept a script configured to implement a user automatic operation function into the AOME, wherein the script includes indication information And control logic, the indication information is used to indicate that an application and/or a global device on the mobile terminal is invoked, the control logic is used to indicate a logical sequence of invoking the application and/or the global device; a parsing module, Set to parse the script;
调用模块, 设置为按照所述指示信息和所述控制逻辑调用所述应 用和 /或所述全局设备实现所述用户自动操作功能。  The calling module is configured to invoke the application and/or the global device according to the indication information and the control logic to implement the user automatic operation function.
9. 根据权利要求 8所述的移动终端, 其中, 在所述控制逻辑还用于指示 调用所述应用和 /或所述全局设备时需满足的事件触发条件的情况下, 所述移动终端还包括: 触发器与通知监视器 TNM, 设置为在配置 于所述 TNM中的事件触发条件被满足的情况下, 通知所述 AOME; 所述调用模块设置为在接收到通知的情况下, 判断所述被满足的 事件触发条件与所述控制逻辑指示的需满足的事件触发条件相同, 则 按照所述控制逻辑指示的所述逻辑顺序调用所述指示信息指示的所述 应用和 /或所述全局设备来实现所述用户自动操作功能。 The mobile terminal according to claim 8, wherein, when the control logic is further used to indicate an event trigger condition to be met when the application and/or the global device is invoked, the mobile terminal further The method includes: a trigger and a notification monitor TNM, configured to notify the AOME if an event trigger condition configured in the TNM is satisfied; the calling module is configured to determine, when the notification is received, The event triggering condition that is satisfied is the same as the event triggering condition that is to be satisfied by the control logic, and the application and/or the global indication indicated by the indication information is invoked according to the logical sequence indicated by the control logic. The device implements the automatic operation function of the user.
10. 根据权利要求 9所述的移动终端, 其中, 所述 TNM包括: The mobile terminal according to claim 9, wherein the TNM comprises:
遍历模块, 设置为遍历对应于所述 TNM所监控的应用或全局设 备的触发器对象 Trigger列表,其中,所述 Trigger列表中的每个 Trigger 对应于一个事件触发条件, 且在所对应的事件触发条件被满足的情况 下被触发; a traversal module, configured to traverse a trigger object Trigger list corresponding to an application or global device monitored by the TNM, wherein each Trigger in the Trigger list Corresponding to an event trigger condition, and triggered if the corresponding event trigger condition is satisfied;
通知模块,设置为在所述遍历模块检测到所述 Trigger列表中存在 被触发的 Trigger的情况下, 将对应于所述被触发的 Trigger的通知消 息 Notification返回给所述 AOME。  The notification module is configured to, when the traversal module detects that the triggered Trigger exists in the Trigger list, return a notification message notification corresponding to the triggered Trigger to the AOME.
11. 根据权利要求 8至 10中任一项所述的移动终端, 其中, 还包括: 控制台模块 CPM , 设置为作为所述 AOME和用户之间的接口, 将用户导入的所述脚本配置到所述 AOME, 或者, 用于提供界面接受 用户通过宏录制将所述脚本配置到所述 AOME。 The mobile terminal according to any one of claims 8 to 10, further comprising: a console module CPM configured to configure the script imported by the user as an interface between the AOME and the user The AOME, or, for providing an interface accepting a user to configure the script to the AOME by macro recording.
PCT/CN2011/070485 2010-10-27 2011-01-21 Processing method for mobile terminal and mobile terminal WO2012055176A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010523313.7 2010-10-27
CN201010523313.7A CN101977268B (en) 2010-10-27 2010-10-27 Mobile terminal processing method and mobile terminal

Publications (1)

Publication Number Publication Date
WO2012055176A1 true WO2012055176A1 (en) 2012-05-03

Family

ID=43577111

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/070485 WO2012055176A1 (en) 2010-10-27 2011-01-21 Processing method for mobile terminal and mobile terminal

Country Status (2)

Country Link
CN (1) CN101977268B (en)
WO (1) WO2012055176A1 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104063658A (en) * 2013-03-20 2014-09-24 深圳富泰宏精密工业有限公司 Operation intervention system and method
CN105320505A (en) * 2014-06-25 2016-02-10 中兴通讯股份有限公司 Script processing method and device
CN105847552A (en) * 2016-03-25 2016-08-10 乐视控股(北京)有限公司 Application operation method of mobile terminal and mobile terminal

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1719925A (en) * 2004-07-08 2006-01-11 中兴通讯股份有限公司 Method and apparatus for automatically testing CDMA cell phone software
US20070006039A1 (en) * 2005-06-29 2007-01-04 International Business Machines Corporation Automated multilingual software testing method and apparatus
CN101025686A (en) * 2007-03-22 2007-08-29 中兴通讯股份有限公司 Automation test system and test script generating and operating method
WO2009073872A1 (en) * 2007-12-06 2009-06-11 Artoftest, Inc. Systems, program product, and methods to enable visual recording and editing of test automation scenarios for markup applications
CN101763275A (en) * 2009-12-31 2010-06-30 华为终端有限公司 Automatic operation method and device, and mobile device
CN101866294A (en) * 2010-05-26 2010-10-20 深圳桑菲消费通信有限公司 Method for automatic operation of mobile phone application software

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101304563B (en) * 2008-06-18 2012-03-21 腾讯科技(深圳)有限公司 Method and system for pushing-transmitting message

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1719925A (en) * 2004-07-08 2006-01-11 中兴通讯股份有限公司 Method and apparatus for automatically testing CDMA cell phone software
US20070006039A1 (en) * 2005-06-29 2007-01-04 International Business Machines Corporation Automated multilingual software testing method and apparatus
CN101025686A (en) * 2007-03-22 2007-08-29 中兴通讯股份有限公司 Automation test system and test script generating and operating method
WO2009073872A1 (en) * 2007-12-06 2009-06-11 Artoftest, Inc. Systems, program product, and methods to enable visual recording and editing of test automation scenarios for markup applications
CN101763275A (en) * 2009-12-31 2010-06-30 华为终端有限公司 Automatic operation method and device, and mobile device
CN101866294A (en) * 2010-05-26 2010-10-20 深圳桑菲消费通信有限公司 Method for automatic operation of mobile phone application software

Also Published As

Publication number Publication date
CN101977268A (en) 2011-02-16
CN101977268B (en) 2013-11-06

Similar Documents

Publication Publication Date Title
US9003431B2 (en) Method and system for implementing function extension of open platform
CN106445448B (en) Audio device control method and system of terminal and mobile terminal
EP2982083B1 (en) Method and apparatus for self organizing networks
US20080046888A1 (en) Framework for Rule-Based Execution and Scheduling of Tasks in Mobile Devices
EP2587771B1 (en) Improved handling and configuration of a mobile communications terminal
US20140179377A1 (en) Mobile electronic device having program notification function and program notification method thereof
US9870239B2 (en) Method and device for running application program
US20160085366A1 (en) Scripting Cross-Device Wearable Interaction
US9727705B2 (en) Remotely defining security data for authorization of local application activity
CN102550003A (en) A method and arrangement for managing persistent rich internet applications
JP2005518015A (en) Middleware service layer for platform systems for mobile terminals
EP2730054A1 (en) Portable computing device and method of operation of same
WO2006071339A1 (en) Method and system for providing an open gateway initiative bundle over the air
WO2014101393A1 (en) Application implementation method and device
WO2011060735A1 (en) Method,device and system for invoking widget
KR20050056214A (en) Middleware application message/event model
CN111427622B (en) Execution method and device of script codes in application program
US7096012B2 (en) System and method for emulating a telephony driver
US20070157194A1 (en) Post-deployment user interface update in a mobile device
WO2012055176A1 (en) Processing method for mobile terminal and mobile terminal
US20070156841A1 (en) Platform independent user interface for a mobile device
WO2021097683A1 (en) Android system starting method and apparatus, device, and storage medium
KR101482149B1 (en) Apparatus for executing application, method thereof and computer recordable medium storing the method
JPWO2004102932A1 (en) Mobile communication terminal and application program suspension method
WO2023124657A1 (en) Micro-application running method and apparatus, device, storage medium, and program product

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

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

Country of ref document: EP

Kind code of ref document: A1