WO2012055176A1 - Procédé de traitement pour un terminal mobile et terminal mobile - Google Patents

Procédé de traitement pour un terminal mobile et terminal mobile 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
English (en)
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/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/75—Structural 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Telephone Function (AREA)

Abstract

L'invention concerne un terminal mobile et un procédé de traitement pour le terminal mobile. Le procédé comprend les étapes suivantes : le moteur de module d'exploitation automatique (AOME) du terminal mobile accepte le script permettant de réaliser une fonction d'opération automatique utilisateur à configurer dans l'AOME (S102); le script contenant des informations d'indication et une logique de commande. Les informations d'indication sont utilisées pour indiquer l'invocation d'une application et/ou d'un équipement global du terminal mobile, et la logique de commande est utilisée pour indiquer la séquence logique de l'invocation d'une application et/ou d'un équipement global; l'AOME analyse le script, et sur la base des informations d'indication et de la logique de commande, l'AOME invoque l'application et/ou l'équipement global ci-dessus pour réaliser la fonction d'opération automatique utilisateur (S104). Grâce à la présente invention, un utilisateur peut réaliser l'opération automatique définie par l'utilisateur sur un terminal mobile selon son souhait. Lorsqu'il utilise le terminal mobile, l'utilisateur a davantage de liberté.
PCT/CN2011/070485 2010-10-27 2011-01-21 Procédé de traitement pour un terminal mobile et terminal mobile WO2012055176A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010523313.7 2010-10-27
CN201010523313.7A CN101977268B (zh) 2010-10-27 2010-10-27 移动终端处理方法及移动终端

Publications (1)

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

Family

ID=43577111

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/070485 WO2012055176A1 (fr) 2010-10-27 2011-01-21 Procédé de traitement pour un terminal mobile et terminal mobile

Country Status (2)

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

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104063658A (zh) * 2013-03-20 2014-09-24 深圳富泰宏精密工业有限公司 操作干预系统及方法
CN105320505A (zh) * 2014-06-25 2016-02-10 中兴通讯股份有限公司 脚本处理方法及装置
CN105847552A (zh) * 2016-03-25 2016-08-10 乐视控股（北京）有限公司 一种移动终端中的应用操作方法及移动终端

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1719925A (zh) * 2004-07-08 2006-01-11 中兴通讯股份有限公司 一种cdma手机软件自动测试的方法及装置
US20070006039A1 (en) * 2005-06-29 2007-01-04 International Business Machines Corporation Automated multilingual software testing method and apparatus
CN101025686A (zh) * 2007-03-22 2007-08-29 中兴通讯股份有限公司 一种自动化测试系统及测试脚本的生成和运行方法
WO2009073872A1 (fr) * 2007-12-06 2009-06-11 Artoftest, Inc. Systèmes, produit de programme et procédés pour permettre l'enregistrement et l'édition visuels de scénarios d'automatisation d'essai pour des applications de majoration
CN101763275A (zh) * 2009-12-31 2010-06-30 华为终端有限公司 自动运行方法和装置及移动设备
CN101866294A (zh) * 2010-05-26 2010-10-20 深圳桑菲消费通信有限公司 一种手机应用软件自动运行的方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101304563B (zh) * 2008-06-18 2012-03-21 腾讯科技（深圳）有限公司 一种消息推送方法和系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1719925A (zh) * 2004-07-08 2006-01-11 中兴通讯股份有限公司 一种cdma手机软件自动测试的方法及装置
US20070006039A1 (en) * 2005-06-29 2007-01-04 International Business Machines Corporation Automated multilingual software testing method and apparatus
CN101025686A (zh) * 2007-03-22 2007-08-29 中兴通讯股份有限公司 一种自动化测试系统及测试脚本的生成和运行方法
WO2009073872A1 (fr) * 2007-12-06 2009-06-11 Artoftest, Inc. Systèmes, produit de programme et procédés pour permettre l'enregistrement et l'édition visuels de scénarios d'automatisation d'essai pour des applications de majoration
CN101763275A (zh) * 2009-12-31 2010-06-30 华为终端有限公司 自动运行方法和装置及移动设备
CN101866294A (zh) * 2010-05-26 2010-10-20 深圳桑菲消费通信有限公司 一种手机应用软件自动运行的方法

Also Published As

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

Similar Documents

Publication Publication Date Title
CN106445448B (zh) 终端的音频设备控制方法、系统及移动终端
EP2982083B1 (fr) Procédé et appareil pour réseaux à auto-organisation
US20080046888A1 (en) Framework for Rule-Based Execution and Scheduling of Tasks in Mobile Devices
US10073553B2 (en) Scripting cross-device wearable interaction
EP2587771B1 (fr) Traitement et configuration améliorés d'un terminal de communication mobile
US20140179377A1 (en) Mobile electronic device having program notification function and program notification method thereof
US20140317639A1 (en) Method and System for Implementing Function Extension of Open Platform
WO2023093429A1 (fr) Procédé et appareil d'exécution de micro-application, et dispositif, support de stockage et produit de programme
US9870239B2 (en) Method and device for running application program
US9727705B2 (en) Remotely defining security data for authorization of local application activity
CN102550003A (zh) 用于管理持续丰富因特网应用的方法和设备
JP2005518015A (ja) 移動体端末用プラットフォーム・システムのミドルウエア・サービス・レイヤ
WO2013009683A1 (fr) Dispositif informatique portatif et son procédé de fonctionnement
WO2014101393A1 (fr) Procédé et dispositif de mise en œuvre d'une application
WO2011060735A1 (fr) Procédé, dispositif et système d'invocation de composant d'interface graphique
US20060140144A1 (en) Method and system for providing an open gateway initiative bundle over the air
KR20070112839A (ko) 무선 디바이스에 대한 주문형 보조를 제공하는 방법 및장치
KR20050056214A (ko) 미들웨어 어플리케이션 메시지/이벤트 모델
CN111427622B (zh) 应用程序中脚本代码的执行方法及装置
US7096012B2 (en) System and method for emulating a telephony driver
WO2012055176A1 (fr) Procédé de traitement pour un terminal mobile et terminal mobile
US20070156841A1 (en) Platform independent user interface for a mobile device
WO2021097683A1 (fr) Procédé et appareil de démarrage de système android, dispositif et support de stockage
KR101482149B1 (ko) 어플리케이션 실행 장치, 그 방법 및 그 방법이 기록된 컴퓨터로 판독 가능한 기록 매체
WO2023124657A1 (fr) Procédé et appareil de fonctionnement de micro-application, dispositif, support de stockage et produit-programme

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