CN116449936A - Information transmission method, device, storage medium and terminal equipment - Google Patents

Information transmission method, device, storage medium and terminal equipment Download PDF

Info

Publication number
CN116449936A
CN116449936A CN202210024525.3A CN202210024525A CN116449936A CN 116449936 A CN116449936 A CN 116449936A CN 202210024525 A CN202210024525 A CN 202210024525A CN 116449936 A CN116449936 A CN 116449936A
Authority
CN
China
Prior art keywords
target
operating system
target application
application
binder
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210024525.3A
Other languages
Chinese (zh)
Inventor
吴靓
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
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 Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to CN202210024525.3A priority Critical patent/CN116449936A/en
Publication of CN116449936A publication Critical patent/CN116449936A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26Power supply means, e.g. regulation thereof
    • G06F1/32Means for saving power
    • G06F1/3203Power management, i.e. event-based initiation of a power-saving mode
    • G06F1/3234Power saving characterised by the action undertaken
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26Power supply means, e.g. regulation thereof
    • G06F1/32Means for saving power
    • G06F1/3203Power management, i.e. event-based initiation of a power-saving mode
    • G06F1/3234Power saving characterised by the action undertaken
    • G06F1/3293Power saving characterised by the action undertaken by switching to a less power-consuming processor, e.g. sub-CPU
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/4401Bootstrapping
    • G06F9/4406Loading of operating system
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/48Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806Task transfer initiation or dispatching
    • G06F9/4843Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Hardware Redundancy (AREA)

Abstract

The embodiment of the application discloses an information transmission method, an information transmission device, a storage medium and a terminal device, wherein the information transmission method, the information transmission device, the storage medium and the terminal device are applied to the terminal device, the terminal device comprises a first operating system and a second operating system, the power consumption of the terminal device for normally operating the first operating system is smaller than the power consumption of the terminal device for operating the second operating system, and the method comprises the following steps: the first operating system acquires information of abnormal ending operation of a target application, wherein the information of abnormal ending operation is used for indicating the abnormal ending operation of the target application; the second operating system acquires a stop instruction, wherein the stop instruction is generated based on the abnormal ending operation information of the target application, and the stop instruction is used for indicating the second operating system to control the functional device which is being called by the target application to stop working. By adopting the method and the device, the effects of saving the power consumption of the terminal equipment and prolonging the service time of the terminal equipment can be achieved.

Description

Information transmission method, device, storage medium and terminal equipment
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to an information transmission method, an information transmission device, a storage medium, and a terminal device.
Background
With the development of electronic devices, some electronic devices have utilized multi-system technology. Taking a dual system as an example, the system is a hardware architecture based on two processors, each processor runs an independent operating system, and the two systems interact with each other to complete the functions of the electronic equipment.
Disclosure of Invention
The embodiment of the application provides an information transmission method, an information transmission device, a storage medium and terminal equipment, which can avoid the problem of waste of electric quantity of the terminal equipment caused by continuous operation of a functional device which is being called by a target application when the target application abnormally finishes running, and achieve the effects of saving the power consumption of the terminal equipment and prolonging the service time of the terminal equipment. The technical scheme is as follows:
in a first aspect, an embodiment of the present application provides an information transmission method, which is applied to a terminal device, where the terminal device includes a first operating system and a second operating system, and power consumption of the terminal device for normally running the first operating system is smaller than power consumption of the terminal device for running the second operating system, and the method includes:
the first operating system acquires information of abnormal ending operation of a target application, wherein the information of abnormal ending operation is used for indicating the abnormal ending operation of the target application;
The second operating system acquires a stop instruction, wherein the stop instruction is generated based on the abnormal ending operation information of the target application, and the stop instruction is used for indicating the second operating system to control the functional device which is being called by the target application to stop working.
In a second aspect, an embodiment of the present application provides an information transmission device, which is applied to a terminal device, where the terminal device includes a first operating system and a second operating system, and power consumption of the terminal device for normally operating the first operating system is smaller than power consumption of the terminal device for operating the second operating system, and the information transmission device includes:
the first operating system is used for acquiring information of abnormal ending operation of the target application, and the information of abnormal ending operation is used for indicating the abnormal ending operation of the target application;
the second operating system is used for acquiring a stop instruction, the stop instruction is generated based on information of abnormal ending operation of the target application, and the stop instruction is used for indicating the second operating system to control the functional device which is being called by the target application to stop working.
In a third aspect, embodiments of the present application provide a storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the above-described method steps.
In a fourth aspect, an embodiment of the present application provides a terminal device, which may include: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the above-mentioned method steps.
The technical scheme provided by some embodiments of the present application has the beneficial effects that at least includes:
in this embodiment of the present application, the first operating system obtains information of an abnormal ending operation of a target application, where the information of the abnormal ending operation is used to indicate the abnormal ending operation of the target application; the second operating system acquires a stop instruction, wherein the stop instruction is generated based on the abnormal ending operation information of the target application, and the stop instruction is used for indicating the second operating system to control the functional device which is being called by the target application to stop working. The problem of waste of electric quantity of the terminal equipment caused by continuous operation of the functional device which is being called by the target application when the target application abnormally finishes running can be avoided, and the effects of saving the power consumption of the terminal equipment and prolonging the service time of the terminal equipment are achieved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a product architecture diagram of an information transmission method according to an embodiment of the present application;
fig. 2 is a schematic flow chart of an information transmission method according to an embodiment of the present application;
fig. 3 is a product architecture diagram of an information transmission method according to an embodiment of the present application;
fig. 4 is a schematic flow chart of an information transmission method according to an embodiment of the present application;
fig. 5 is a schematic flow chart of an information transmission method according to an embodiment of the present application;
FIG. 6 is an exemplary diagram of a Binder list according to an embodiment of the present application;
FIG. 7 is an exemplary diagram of a Binder list according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of an information transmission device according to an embodiment of the present application;
FIG. 9 is a schematic diagram of a first operating system according to an embodiment of the present disclosure;
fig. 10 is a schematic structural diagram of a terminal device according to an embodiment of the present application;
fig. 11 is a schematic diagram of an Android system operating system according to an embodiment of the present application;
FIG. 12 is a block diagram of an IOS operating system according to one embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
In the description of the present application, it should be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. In the description of the present application, it is to be understood that the terms "comprise" and "have," and any variations thereof, are intended to cover non-exclusive inclusions, unless otherwise specifically defined and defined. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus. The specific meaning of the terms in this application will be understood by those of ordinary skill in the art in a specific context. Furthermore, in the description of the present application, unless otherwise indicated, "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.
One terminal device may have multiple operating systems, for example, one terminal device may include a first operating system and a second operating system, the operating systems operating by means of a processor. The first operating system may include an Android system, the second operating system may include an MCU system, or the first operating system may include an MCU system, and the second operating system may include an Android system, which is not limited herein.
In some embodiments, since the operating system of the terminal device includes a first operating system and a second operating system, the operating system currently used by the terminal device may be the first operating system or the second operating system, which is not limited herein. When the operating system currently used by the terminal device is the first operating system, the second operating system may be in a dormant state or may be in a closed state, and when the operating system currently used by the terminal device is the second operating system, the first operating system may be in a dormant state or may be in a closed state, which is not limited herein.
In some embodiments, the power consumption of the normal operation of the first operating system is higher than the power consumption of the normal operation of the second operating system, that is, the power consumption of the terminal device caused by the operation of the first operating system is higher than the power consumption of the terminal device caused by the operation of the second operating system under the same operation environment. Based on this, in this embodiment, the functional hardware may be mainly mounted on the second processor running the second operating system, that is, the functional hardware may be mainly controlled by the second system with smaller normal running power consumption, so as to reduce the power consumption of the terminal device. Wherein the functional hardware may include a screen, a vibration motor, a horn, a camera, etc., and the screen, the vibration motor, the horn, the camera, etc., may be primarily mounted on a second processor running a second operating system. In the terminal equipment, for an application needing to call a functional device to collect information, if the sensor is required to be started to collect information, a first operating system is required to send a starting instruction to a second operating system, and the second operating system controls the functional device which is being called by the application to start information collection based on the received starting instruction; if the function device finishes information acquisition, the first operating system is required to send a finishing instruction to the second operating system, and the second operating system controls the function device which is being called by the application to finish information acquisition based on the received finishing instruction.
However, if the application is abnormally finished in the running process, the first operating system does not send a finishing instruction to the second operating system, and the second operating system controls the function device which is being called by the application to finish information acquisition, so that the function device which is being called by the application can continue to perform information acquisition, the electric quantity of the terminal equipment is wasted, and the using time of the terminal equipment is influenced.
Referring to fig. 1, a system structure diagram of an information transmission method is provided in an embodiment of the present application. As shown in fig. 1, the information transmission method provided in the embodiment of the present application may be applied to a terminal device having a system structure shown in fig. 1, where the terminal device includes, but is not limited to, a mobile phone, a handheld device, a vehicle-mounted device, a personal computer, a notebook computer, an intelligent wearable device, and other terminal devices having multiple operating systems.
The terminal equipment comprises a first operating system and a second operating system, and the system structure shown in fig. 1 comprises the first operating system and the second operating system. In the first operating system, a keep-alive process and at least one target application may be included. The second operating system may include a task item corresponding to the second operating system, for example, an opening instruction corresponding to the functional device. Optionally, the power consumption of the terminal device for normally operating the first operating system is smaller than the power consumption of the terminal device for operating the second operating system.
The first operating system may be an android system, an IOS system, etc. running on the terminal device, and the second operating system may be a real-time operating system (Rea lTime Operating System, RTOS) running on the terminal device. The real-time operating system may also be WIN CE (Windows Embedded CE, WIN CE), winko system VxWorks, RT-Thread system, uCOS system (Micro-Controller Operating System Two), etc. The first operating system and the second operating system are communicated through a Dual-core communication module (Dual-Core Communication, DCC).
Referring to fig. 2, a flow chart of an information transmission method is provided in an embodiment of the present application. The terminal device is provided with a target application, and the method may include the following steps S101 to S102:
s101, the first operating system acquires information of abnormal ending operation of a target application, wherein the information of abnormal ending operation is used for indicating the abnormal ending operation of the target application;
it can be understood that the target application may be any application pre-installed in the terminal device, or may be a third party application installed by the user. The target application can call the functional device, wherein the functional device can be a sensor, a camera, a lens module and the like, and the functional device called by the target application can acquire information according to the requirement of the target application. For example, the target application may be a relaxation application, where the relaxation application is an application that allows a user to perform rhythmic breathing or meditation under video and audio guidance, and in the running process of the relaxation application, the heart rate detection sensor corresponding to the relaxation application collects information such as a heart rate and pressure of a human body, so that when the relaxation application ends, the collected information such as the heart rate and pressure of the human body is displayed on a display interface of the terminal device for the user to review.
If the target application is required to acquire the information acquired by the functional device, the first operating system does not directly call the functional device on the terminal equipment, the first operating system in the terminal equipment is required to send a starting instruction to the second operating system, and the second operating system controls the functional device required by/corresponding to the target application to start information acquisition based on the received starting instruction; if the functional device called by the target application is required to end information acquisition, the first operating system is required to send an end instruction to the second operating system, and the second operating system controls the functional device called by the target application to end information acquisition based on the received end instruction. The first operating system sends an instruction to the second operating system, and the second operating system controls the starting or ending of the called functional device required by the target application based on the received instruction.
For example, the target application may be a relaxation application and the functional device that the relaxation application is invoking may be a heart rate detection sensor. The relaxation application is an application running on a first operating system, when a user clicks an icon for starting to collect the heart rate of a human body in the relaxation application, the first operating system sends a starting instruction of a heart rate detection sensor corresponding to the relaxation application to a second operating system, and the second operating system controls the heart rate detection sensor corresponding to the relaxation application to start working when receiving the starting instruction. When a user clicks an icon for ending the acquisition of the heart rate of the human body in the relaxation application, the first operating system sends an ending instruction of the heart rate detection sensor corresponding to the relaxation application to the second operating system, and the second operating system controls the heart rate detection sensor corresponding to the relaxation application to stop working when receiving the ending instruction.
However, in the process of running the target application, abnormal ending operation may occur, at this time, the first operating system may not send an ending instruction corresponding to the loosening application to the second operating system, and the functional device being invoked by the loosening application may continuously collect information such as heart rate of a human body. The abnormal ending operation of the target application may be that the target application ends under the condition of non-user wish, for example, due to the phenomena of slow data loading, network interruption and the like caused by the too high temperature of the central processing unit of the terminal equipment, the target application is abnormally ended in the operation process.
In one embodiment, the first operating system continuously monitors the state of the target application, and when the target application abnormally ends running, the first operating system acquires a message that the target application abnormally ends running.
S102, the second operating system acquires a stop instruction, wherein the stop instruction is generated based on the abnormal ending operation information of the target application, and the stop instruction is used for indicating the second operating system to control the functional device which is being called by the target application to stop working.
After acquiring the abnormal ending operation information of the target application, the first operating system generates a stopping instruction corresponding to the target application based on the abnormal ending operation information of the target application, sends the stopping instruction to the second operating system, and controls the target application to stop working.
The function device called by the target application may be a sensor that needs to be called for starting (working) to realize the function of the target application, for example, the target application may be a relaxation application, in order to realize that the relaxation application displays information such as a human heart rate, a heart rate detection sensor is set on the terminal device, when the relaxation application needs to call the heart rate detection sensor, a first operating system sends a start instruction to a second operating system, and the second operating system can control the heart rate detection sensor corresponding to the relaxation application to start collecting the information such as the human heart rate based on the received start instruction.
It can be understood that, under the condition that the target application abnormally ends to run, the first operating system can acquire a message that the target application abnormally ends to run, generate a stop instruction corresponding to the target application based on the message that the target application abnormally ends to run, and send the stop instruction corresponding to the target application to the second operating system, and the second operating system controls the functional device being invoked by the target application to stop working based on the acquired stop instruction.
By adopting the embodiment, the first operating system obtains information of abnormal ending operation of the target application, where the information of abnormal ending operation is used to indicate the abnormal ending operation of the target application; the second operating system acquires a stop instruction, wherein the stop instruction is generated based on the abnormal ending operation information of the target application, and the stop instruction is used for indicating the second operating system to control the functional device which is being called by the target application to stop working. The problem of waste of electric quantity of the terminal equipment caused by continuous operation of the functional device which is being called by the target application when the target application abnormally finishes running can be avoided, and the effects of saving the power consumption of the terminal equipment and prolonging the service time of the terminal equipment are achieved.
Referring to fig. 4, a flowchart of an information transmission method is provided in an embodiment of the present application. The information transmission method is applied to a terminal device, the terminal device comprises a first operating system and a second operating system, a keep-alive process can be operated in the first operating system, in a state that a target application is opened, the target application can register a target Binder in the keep-alive process, and the information transmission method can comprise the following steps S201 to S203:
S201, in a state that the target application is started, the target application calls a Binder registration method of the keep-alive process to register a target Binder, and the target Binder corresponds to at least one target stop instruction;
optionally, in the state that the target application is opened, the target application invokes a Binder registration method of the keep-alive process to register a target Binder, the keep-alive process creates a target deshrifecient for the target Binder, binds the target Binder with the target deshrifecient, and the target deshrifecient corresponds to at least one target stop instruction.
It can be understood that the state that the target application is in the open state may be that the target application is controlled to be in the open state by clicking an open key corresponding to the target application on a display screen of the terminal device by a user.
The first operating system may run a keep-alive process, where the keep-alive process is a service for helping forwarding information, and the generation of the keep-alive process may be divided into two layers, where one layer is to improve the priority of the keep-alive process, so as to reduce the probability that the keep-alive process is accidentally killed, for example, monitor a screen locking event and an unlocking event of the terminal device, start an Activity of 1 pixel when the screen is locked, and destroy the Activity when the screen is unlocked. On the other hand, when abnormal ending operation occurs, the first operating system restarts the keep-alive process, for example, when abnormal ending operation occurs in the keep-alive process, the first operating system sends out response broadcast, and the corresponding broadcast monitor is registered in the Android management in a static mode, so that the keep-alive process can be pulled when a response event occurs, and the keep-alive process is in a survival state continuously. The keep-alive process can help to send messages when other applications abnormally end up running, and the functional devices which can be called by the applications abnormally end up running are controlled.
The method comprises the steps that a Binder registration method is included in a keep-alive process, the target application directly calls the Binder registration method in the keep-alive process to register a target Binder when the target application is in an opened state, the target application calls the Binder registration method once to register a target Binder, if the target application calls the Binder registration method for a plurality of times, a plurality of target binders can be registered, the keep-alive process creates a target deshrifecient for the target Binder while registering the target Binder, and the target Binder and the keep-alive process create the target deshrifecient for the Binder to bind.
The keep-alive process creates a target deathrecept for the target Binder and binds the target Binder with the target deathrecept, e.g., target application a may register a target Binder a in the keep-alive application while the keep-alive process creates a target deathrecept a for this target Binder a and binds target Binder a with target deathrecept a. If the target application calls the Binder registration method multiple times, multiple target Binders may be registered, for example, target application B calls the Binder registration method in the keep-alive process to register the first target Binder, create a corresponding deathreecientB-1 for Binder B-1, bind Binder B-1 with deathreecentB-1, target application may also continue to call the Binder registration method in the keep-alive process to register the second target Binder, create a corresponding deathreecentB-2 for Binder B-2, and bind Binder B-2 with deathreecentB-2.
For example, the target application may be a relax application, and in a state where the relax application is opened, the relax application calls a Binder registration method of the keep-alive process to register the target Binder, and at the same time, the keep-alive process creates a target desthrecient for the target Binder, and binds the target Binder with the target desthrecient.
The Binder is an inter-process communication mechanism, and mainly relates to 4 roles Client, server, service Manager and Binder drivers in a Binder framework, wherein Client, server and Service Manager operate in a user space, binder drivers operate in a kernel space, clients represent Client processes, and servers provide various services such as audio and video and the like for the Client processes. Service Manager is used to manage various system services. The Binder communication process can be divided into three steps, firstly, a process registers itself as a Service Manager through a Binder driver by using a BINDERSETCONTEXT_MGR command, and then, a Server registers a Binder (Binder entity in the Server) in the Service Manager through the Binder driver, which indicates that services can be provided externally. The Binder driver creates a reference to an entity by an entity node and a Service Manager in the kernel for the Binder, packages and transmits the name and the newly created reference to the Service Manager, the Service Manager fills the name and the newly created reference into a lookup table, and finally the Client obtains the reference to the Binder entity from the Service Manager with the help of the Binder driver by the name, and the communication with the Server process can be realized through the reference.
The Binder registration method includes information to be provided by the target application when registering, such as a registration name, parameters used for registering, a calling mechanism being a life monitoring mechanism, and information of a functional device called by the target application.
Optionally, the target desthreeceient created by the keep-alive process corresponds to a sended method, and the sended method includes at least one target stopping instruction, where one target desthreeceient corresponds to one sended method, and one sended method may include at least one target stopping instruction, where the at least one target stopping instruction is set corresponding to each functional device called by the target application. If there are two functional devices called by the target application, the target stop instructions may be two, and the two target stop instructions respectively correspond to the two functional devices called by the target application. For example, the target application may be a relaxation application, the functional device that the relaxation application is calling is an electrocardiographic detection sensor and a human body pressure detection sensor, if the relaxation application registers a target Binder, the target desthrecient corresponding to the target Binder may correspond to two target stop instructions, one may be for controlling the electrocardiographic detection sensor to stop working, and the other may be for controlling the human body pressure detection sensor to stop working.
After the target application registers the target Binder in the keep-alive process, the keep-alive process binds the death monitoring service for the target Binder corresponding to the target application, after the death monitoring service is bound, the first operating system can monitor the target application corresponding to the target Binder, if the abnormal end operation information of the target application is obtained, based on the death monitoring service, the first operating system indicates to which one or which one of the deathfeeceppients the abnormal end operation information of the target application is sent.
S202, the first operating system acquires information of abnormal ending operation of a target application, wherein the information of abnormal ending operation is used for indicating the abnormal ending operation of the target application;
when the abnormal ending operation of the target application occurs, the first operating system acquires information of the abnormal ending operation of the target application and sends the information of the abnormal ending operation to the kept alive process, and specifically, the first operating system sends the information of the abnormal ending operation of the target application to a target desthrecient bound with a target Binder, and triggers and executes a binding speed method corresponding to the target desthrecient.
S203, the second operating system acquires at least one target stopping instruction corresponding to the target Binder, the target stopping instruction is generated based on information of abnormal ending operation of the target application, and the target stopping instruction is used for indicating the second operating system to control the functional device which is being called by the target application to stop working.
And because the BinderDied method corresponding to the target desthrecasting is triggered, the keep-alive process sends at least one target stopping instruction corresponding to the target Binder to the second operating system, and the second operating system controls the functional device which is being called by the target application to stop working based on the target stopping instruction.
And the kept-alive process sends at least one target stopping instruction corresponding to a target desthrecasting bound with a target Binder to the second operating system, and the second operating system controls the functional devices corresponding to the target stopping instructions to stop working.
Because the information of the abnormal ending operation of the target application may include a name of the target application, an abnormal ending time, a functional device that the target application is calling, and the like, and the target application may register one or more target binders, when registering the plurality of target binders, the plurality of target binders bind with respective corresponding target desthrepepents, the first operating system may determine to which desthrepepent the information of the abnormal ending operation of the target application needs to be sent based on the information of the abnormal ending operation of the target application.
For example, the target application may be a relaxation application, the function device that the relaxation application is calling may be a heart rate detection sensor, taking the example that the relaxation application registers a target Binder in a keep-alive process, if the relaxation application abnormally ends running, the first operating system sends a message that the relaxation application abnormally ends running to a target deshrifecient that the relaxation application binds to the registered target Binder, triggers execution of a binderdiod method corresponding to the target deshrifecient bound to the target Binder, the binderdiod method includes an item label stop instruction, the content of the target stop instruction is that the electrocardiograph detection sensor that the relaxation application calls stops working, and sends an item label stop instruction in the binderdiod method to the second operating system in the keep-alive process, and the second operating system controls the electrocardiograph detection sensor corresponding to the target stop instruction to stop working.
If the number of the functional devices called by the target application is multiple, the binderDied method corresponding to the target desthrecient can contain multiple target stop instructions, and can trigger a part of target stop instructions or trigger all target stop instructions. For example, the target application may be a relaxation application, if the functional devices that can be invoked by the relaxation application are a heart rate detection sensor and a pressure detection sensor, but only the heart rate detection sensor is currently being invoked, only the target stop instruction corresponding to the heart rate detection sensor may be sent, the target stop instruction corresponding to the pressure detection sensor is not sent, and all the target stop instructions may be triggered, and because all the stop instructions include the target stop instruction corresponding to the heart rate detection sensor, the heart rate detection sensor that is being invoked by the relaxation application may be stopped.
It can be appreciated that, because the relax application may call the registration method in the keep-alive process one or more times, one target Binder may be registered by calling the registration method once, if the relax application calls the registration method in the keep-alive process multiple times, multiple target binders may be registered, when the relax application registers multiple target binders, the keep-alive process binds one target desthreshould for each target Binder, at this time, if the first operating system obtains a message that the relax application has abnormally ended, the first operating system may send the message that the relax application has abnormally ended to all target desthreshould corresponding to the relax application, and trigger execution of the BinderDied method corresponding to all target desthreshould corresponding to the relax application. For each target desthrecasting, the target stopping instruction corresponding to the functional device being invoked may be selectively sent to the second operating system, or the target stopping instructions corresponding to all functional devices that the loosening application may invoke may be sent to the second operating system. And after the second operating system receives the target stopping instruction, controlling the functional device which is being called by the loosening application to stop working.
Referring to fig. 8, a flowchart of an information transmission method is provided in an embodiment of the present application. The information transmission method is applied to a terminal device, the terminal device includes a first operating system and a second operating system, the first operating system includes a keep-alive process and a target application, in this embodiment, a registered target Binder and a corresponding target deshrifecient may be unbinding or deregistering in the process, and the information transmission method may include the following steps S301 to S304:
s301, in a state that the target application is started, the target application calls a Binder registration method of the keep-alive process to register a target Binder, and the target Binder corresponds to at least one target stop instruction;
please refer to S201, which is not described herein.
S302, the first operating system acquires information of abnormal ending operation of a target application, wherein the information of abnormal ending operation is used for indicating the abnormal ending operation of the target application;
it can be understood that, in a state where the target application normally ends running, the first operating system ends monitoring of the running state of the target application.
In one embodiment, in a state that the target application normally ends running, the target application calls a Binder cancellation method of the keep-alive process to cancel the target Binder, and/or the keep-alive process unbinds the target Binder from the target desthrecient.
The target application calls the Binder logout method of the keep-alive process to logout the target Binder based on the instruction of the user to end the target application, and the target application can avoid excessive number of Binders in the keep-alive process and occupy the memory of the keep-alive process under the state that the target application normally ends operation.
The Binder logout method includes information to be provided by the target application when registering, such as a registration name of the target application, parameters for logout, a calling mechanism being a life monitoring mechanism, and information of a functional device called by the target application.
Please refer to S202, which is not described herein.
S303, the second operating system acquires at least one target stopping instruction corresponding to the target Binder, the target stopping instruction is generated based on information of abnormal ending operation of the target application, and the target stopping instruction is used for indicating the second operating system to control the functional device which is being called by the target application to stop working.
Please refer to S203, which is not described herein.
In one embodiment, only the abnormal ending running message of the target application may be sent to a preset number of target destemeceients in the target destemeceients corresponding to the target application, so as to trigger and execute the binderDied method corresponding to the preset number of target destemeceients.
S304, the keep-alive process logs off the target Binder, and/or unbinds the target Binder and the target desthrecient.
After the second operating system controls the functional devices corresponding to the target stop instructions to stop working, the keep-alive process logs off the target Binder, so that the situation that the number of Binders in the keep-alive process is excessive and the memory of the keep-alive process is occupied can be avoided.
In one embodiment, in the keep-alive process, a Binder list is maintained, where the Binder list includes keys corresponding to applications in which binders are registered and values corresponding to keys corresponding to applications, where each Value is composed of a Binder registered by each application and each deshrifecient corresponding to each Binder. The Key corresponding to each application may be a parameter used for registration when registering the Binder for each application.
As shown in fig. 6, the Key corresponding to the application E in the Binder list is E, the Value corresponding to the Key is a Binder E registered by the application E, and the desthreepiente corresponding to the Binder E, the Key corresponding to the application F is F, and the Value corresponding to the Key is a Binder F registered by the application F, and the desthreepient F corresponding to the Binder F.
The unbinding the target Binder and the target deshrieceient by the keep-alive process may be that the target application is triggered to execute an unbinding action on the target Binder and the target deshrieceient simultaneously based on an instruction of ending the target application by a user or after the second operating system controls the functional device corresponding to each target stop instruction to stop working, and at least one Value corresponding to at least one Key corresponding to the target application is searched in a Binder list based on at least one Key corresponding to the target application, so as to obtain at least one target Binder corresponding to the target application and at least one deshrieceient corresponding to the target Binder, and unbinding the at least one target Binder and the at least one deshrieceient corresponding to the target Binder.
As shown in fig. 7, the target application is target E, and the corresponding Value is searched in the Binder list based on the Key corresponding to the target application E, and the Binder E and the deathreceptent E corresponding to the Binder E are unbinding after the corresponding Value is searched as the Binder E registered by the application E and the deathreceptent E corresponding to the Binder E.
It can be appreciated that the keep-alive process can log off the target Binder, so that excessive numbers of binders and desthreeceptins in the Binder list can be avoided, and the memory of the keep-alive process is occupied. Unbinding the target Binder and the target desthrecasting can avoid re-registering the target Binder when the target application is restarted next time, and save the time of target Binder registration.
An information transmission device according to an embodiment of the present application will be described in detail with reference to fig. 8. It should be noted that, the information transmission device in fig. 8 is used to perform the method of the embodiment shown in fig. 1 to 7, and for convenience of explanation, only the portion relevant to the embodiment of the present application is shown, and specific technical details are not disclosed, please refer to the embodiment shown in fig. 1 to 7 of the present application.
Referring to fig. 8, a schematic structural diagram of an information transmission device is provided in an embodiment of the present application. The information transmission apparatus 1 may be implemented as all or a part of the terminal device by software, hardware or a combination of both. According to some embodiments, the information transmission device is characterized in that,
The information transmission device 1 includes a first operating system 11 and a second operating system 12, and the power consumption of the information transmission device 1 for operating the first operating system is smaller than the power consumption of operating the second operating system, specifically:
the first operating system 11 is configured to obtain information of an abnormal ending operation of a target application, where the information of the abnormal ending operation is used to indicate the abnormal ending operation of the target application;
the second operating system 12 is configured to obtain a stop instruction, where the stop instruction is generated based on information that the target application abnormally ends running, and the stop instruction is used to instruct the second operating system to control the functional device that is being invoked by the target application to stop working.
Optionally, referring to fig. 9, the first operating system 11 includes a target application 111, specifically:
the target application 111 is configured to call a Binder registration method of the keep-alive process to register a target Binder in a state where the target application is started, where the target Binder corresponds to at least one target stop instruction;
the second operating system 12 is configured to obtain at least one target stopping instruction corresponding to the target Binder, where the target stopping instruction is generated based on information of abnormal ending operation of the target application, and the target stopping instruction is used to instruct the second operating system to control the functional device that is being invoked by the target application to stop working.
Optionally, the first operating system 11 is further configured to obtain information of abnormal ending operation of the target application, and send the information of abnormal ending operation to the keep-alive process;
the keep-alive process 111 is further configured to send at least one target stopping instruction corresponding to a target Binder to the second operating system, where the second operating system controls the functional device that is being invoked by the target application to stop working based on the target stopping instruction.
Optionally, the first operating system 11 is further configured to send information of the abnormal ending operation of the target application to a target desthrecasting, and trigger execution of a senderspeed method corresponding to the target desthrecasting, where the senderspeed method includes at least one target stop instruction.
Optionally, the first operating system 11 is further configured to end monitoring the running state of the target application in a state where the target application normally ends running.
Optionally, the target application 111 is further configured to, in a state where the target application normally ends running, invoke a Binder cancellation method of the keep-alive process to cancel the target Binder, and/or unbind the target Binder and the target desthre-client by the keep-alive process.
Optionally, referring to fig. 9, the first operating system 11 includes a keep-alive process 112, specifically:
the keep-alive process 112 is further configured to log off the target Binder and/or unbind the target Binder from the target desthrecient.
It should be noted that, in the information transmission apparatus provided in the foregoing embodiment, when the information transmission method is executed, only the division of the foregoing functional modules is used as an example, in practical application, the foregoing functional allocation may be performed by different functional modules, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the information transmission device and the information transmission method provided in the foregoing embodiments belong to the same concept, which represents a detailed implementation process in the method embodiment, and are not described herein again.
The foregoing embodiment numbers of the present application are merely for describing, and do not represent advantages or disadvantages of the embodiments.
The embodiment of the present application further provides a computer storage medium, where the computer storage medium may store a plurality of instructions, where the instructions are suitable for being loaded by a processor and executed by the processor, where the specific execution process may refer to the specific description of the embodiment shown in fig. 1 to 8, and details are not repeated herein.
Referring to fig. 10, a schematic structural diagram of a terminal device is provided in an embodiment of the present application. As shown in fig. 10, the terminal device may include one or more of the following components: a first processor 110, a second processor 120, a memory 130, an input device 140, an output device 150, and a bus 160. The first processor 110, the second processor 120, the memory 130, the input device 140, and the output device 150 are connected by a centerline 160.
The first processor 110 may include one or more processing cores that utilize various interfaces and lines to connect various portions of the overall terminal device, perform various functions of the terminal device 100 and process data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 130, and invoking data stored in the memory 130. Alternatively, the first processor 110 may be implemented in at least one hardware form of digital signal processing (digita lsigna l processing, DSP), field-programmable gate array (field-programmable gate array, FPGA), programmable logic array (programmable logic Array, PLA). The first processor 110 may integrate one or a combination of several of a central processing unit (centra lprocessing unit, CPU), an image processor (graphics processing unit, GPU), and a modem, etc. Wherein, the CPU mainly processes a first operating system, application programs and the like; the GPU is used for being responsible for rendering and drawing of display content; the modem is used to handle wireless communications. It will be appreciated that the modem may not be integrated into the first processor 110 and may be implemented by a single communication chip.
Similarly, the second processor 120 may include one or more processing cores that utilize various interfaces and lines to connect various portions of the overall terminal device, perform various functions of the terminal device 100 and process data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 130, and invoking data stored in the memory 130. Alternatively, the second processor 120 may be implemented in at least one hardware form of DSP, FPGA, PLA. The second processor 120 may integrate one or a combination of several of a CPU, GPU, modem, etc. It will be appreciated that the modem may not be integrated into the first processor 110 and may be implemented by a single communication chip.
The memory 130 may include a random access memory (random Access Memory, RAM) or a read-only memory (ROM). Optionally, the memory 130 includes a non-transitory computer readable medium (non-transitory computer-readable storage medium). Memory 130 may be used to store instructions, programs, code, sets of codes, or sets of instructions. The memory 130 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described below, etc. The storage data area may also store data created by the terminal device in use, such as phonebooks, audio-video data, chat-record data, etc.
Taking the first operating system as an Android system for example, as shown in fig. 11, a program and data stored in the memory 130 may store a Linux kernel layer 320, a system runtime library layer 340, an application framework layer 360 and an application layer 380 in the memory, where the Linux kernel layer 320, the system runtime library layer 340 and the application framework layer 360 belong to a first operating system space, and the application layer 380 belongs to a user space. The Linux kernel layer 320 provides the various hardware of the terminal device with the underlying drivers, such as display drivers, audio drivers, camera drivers, bluetooth drivers, wi-Fi drivers, power management, etc. The system runtime layer 340 provides the main feature support for the Android system through some C/c++ libraries. For example, the SQLite library provides support for databases, the OpenGL/ES library provides support for 3D graphics, the Webkit library provides support for browser kernels, and the like. Also provided in the system runtime library layer 340 is a An Zhuoyun runtime library (Android run) which provides mainly some core libraries that can allow developers to write Android applications using the Java language. The application framework layer 360 provides various APIs that may be used in building applications, which developers can also build their own applications by using, for example, campaign management, window management, view management, notification management, content provider, package management, call management, resource management, location management. At least one application program is running in the application layer 380, and these application programs may be native application programs of the first operating system, such as a contact program, a sms program, a clock program, a camera application, etc.; and may also be a third party application developed by a third party developer, such as a game-like application, instant messaging program, photo beautification program, operating system control program, etc. The multimedia software may be a native application program of the first operating system, or an application program developed by a third party developer.
Taking the first operating system as an IOS system as an example, the program and data stored in the memory 130 are as shown in fig. 12, the IOS system includes: core operating system layer 420 (Core OS layer), core service layer 440 (Core Services layer), media layer 460 (Media layer), and touchable layer 480 (Cocoa Touch Layer). The core operating system layer 420 includes an operating system kernel, drivers, and underlying program frameworks that provide more hardware-like functionality for use by the program frameworks at the core services layer 440. The core services layer 440 provides system services and/or program frameworks required by the application, such as a Foundation (Foundation) framework, an account framework, an advertisement framework, a data storage framework, a network connection framework, a geographic location framework, a sports framework, and the like. The media layer 460 provides an interface for applications related to audiovisual aspects, such as a graphics-image related interface, an audio technology related interface, a video technology related interface, an audio video transmission technology wireless play (AirPlay) interface, and so forth. The touchable layer 480 provides various commonly used interface-related frameworks for application development, with the touchable layer 480 being responsible for user touch interactions on the terminal device. Such as a local notification service, a remote push service, an advertisement framework, a game tool framework, a message User Interface (UI) framework, a User Interface UIKit framework, a map framework, and so forth.
Among the frameworks illustrated in fig. 12, frameworks related to most applications include, but are not limited to: the infrastructure in core services layer 440 and the UIKit framework in touchable layer 480. The infrastructure provides many basic object classes and data types, providing the most basic system services for all applications, independent of the UI. While the class provided by the UIKit framework is a basic UI class library for creating touch-based user interfaces, iOS applications can provide UIs based on the UIKit framework, so it provides the infrastructure for applications to build user interfaces, draw, process and user interaction events, respond to gestures, and so on.
The manner and principle of implementing data communication between the third party application program and the operating system in the IOS system may refer to the Android system, which is not described herein.
The input device 140 is configured to receive input instructions or data, and the input device 140 includes, but is not limited to, a keyboard, a mouse, a camera, a microphone, or a touch device. The output device 150 is used to output instructions or data, and the output device 150 includes, but is not limited to, a display apparatus, a speaker, and the like. In one example, the input device 140 and the output device 150 may be combined, and the input device 140 and the output device 150 are a touch display screen for receiving a touch operation thereon or thereabout by a user using a finger, a touch pen, or any other suitable object, and displaying a user interface of each application program. The touch display screen is typically provided at the front panel of the terminal device. The touch display screen may be designed as a full screen, a curved screen, or a contoured screen. The touch display screen can also be designed to be a combination of a full screen and a curved screen, and a combination of a special-shaped screen and a curved screen, which is not limited in the embodiment of the application.
In addition, it will be appreciated by those skilled in the art that the structure of the terminal device illustrated in the above-described drawings does not constitute a limitation of the terminal device, and the terminal device may include more or less components than illustrated, or may combine certain components, or may be arranged in different components. For example, the terminal device further includes components such as a radio frequency circuit, an input unit, a sensor, an audio circuit, a wireless fidelity (wireless fidelity, wiFi) module, a power supply, and a bluetooth module, which are not described herein.
The terminal device of the embodiment of the application may further be provided with a display device, where the display device may be various devices capable of implementing a display function, for example: cathode ray tube displays (cathode ray tubedisplay, CR), light-emitting diode displays (light-emitting diode display, LED), electronic ink screens, liquid crystal displays (liquid crysta ldisplay, LCD), plasma display panels (plasma display panel, PDP), and the like. The user can view the displayed text, image, video, etc. information using the display device on the terminal device 101. The terminal device may be a smart phone, a tablet computer, a gaming device, an AR (Augmented Reality ) device, an automobile, a data storage device, an audio playing device, a video playing device, a notebook, a desktop computing device, a wearable device such as an electronic watch, electronic glasses, an electronic helmet, an electronic bracelet, an electronic necklace, an electronic article of clothing, etc.
In the terminal device shown in fig. 10, the first processor 110 and the second processor 120 may be used in combination, to call the information transmission application program stored in the memory 130, and specifically perform the following operations:
the terminal equipment comprises a first operating system and a second operating system, and the power consumption of the terminal equipment for normally operating the first operating system is smaller than that of the terminal equipment for operating the second operating system;
the first operating system acquires information of abnormal ending operation of a target application, wherein the information of abnormal ending operation is used for indicating the abnormal ending operation of the target application;
the second operating system acquires a stop instruction, wherein the stop instruction is generated based on the abnormal ending operation information of the target application, and the stop instruction is used for indicating the second operating system to control the functional device which is being called by the target application to stop working.
Optionally, before executing the first operating system including the keep-alive process, the first operating system acquires information of abnormal ending running of the target application, the second processor 120 further performs the following operations:
in the state that the target application is started, the target application calls a Binder registration method of the keep-alive process to register a target Binder, and the target Binder corresponds to at least one item of target stop instruction;
When a second operating system is executed to acquire a stop instruction, the stop instruction is generated based on the abnormal ending operation information of the target application, and the stop instruction is used for indicating the second operating system to control the function device which is being called by the target application to stop working, the following operations are specifically executed:
the second operating system acquires at least one target stopping instruction corresponding to the target Binder, the target stopping instruction is generated based on information of abnormal ending operation of the target application, and the target stopping instruction is used for indicating the second operating system to control the functional device which is being called by the target application to stop working.
Optionally, when the second processor 120 executes the second operating system to obtain at least one target stopping instruction corresponding to the target Binder, where the target stopping instruction is generated based on information that the target application abnormally ends running, the target stopping instruction is used to instruct the second operating system to control the functional device that is being invoked by the target application to stop working, specifically execute the following operations:
the first operating system acquires information of abnormal ending operation of a target application and sends the information of abnormal ending operation to the kept alive process;
And the keep-alive process sends at least one target stopping instruction corresponding to a target Binder to the second operating system, and the second operating system controls the functional device which is being called by the target application to stop working based on the target stopping instruction.
Optionally, the keep-alive process creates a target desthrecient for the target Binder, binds the target Binder with the target desthrecient, and when executing the first operating system to obtain information of abnormal ending operation of the target application, the second processor 120 specifically executes the following operations:
and the first operating system sends the abnormal ending operation information of the target application to a target desthrecasting, and triggers and executes a BinderDied method corresponding to the target desthrecasting, wherein the BinderDied method comprises at least one item of target stop instruction.
Optionally, the second processor 120 further performs the following operations:
and under the state that the target application normally finishes running, the first operating system finishes monitoring the running state of the target application.
Optionally, the second processor 120 further performs the following operations:
And under the state that the target application normally finishes running, the target application calls a Binder cancellation method of the keep-alive process to cancel the target Binder, and/or the keep-alive process unbinds the target Binder and the target desthrecient.
Optionally, after sending the at least one target stop instruction to the second operating system, the second operating system controls the functional device being invoked by the target application to stop working based on the target stop instruction, the second processor 120 further performs the following operations:
the keep-alive process deregisters the target Binder and/or unbinds the target Binder from the target desthreeceient.
It will be clear to a person skilled in the art that the solution of the present application may be implemented by means of software and/or hardware. "Unit" and "module" in this specification refer to software and/or hardware capable of performing a specific function, either alone or in combination with other components, such as Field programmable gate arrays (Field-Programma BLE Gate Array, FPGAs), integrated circuits (Integrated Circuit, ICs), etc.
It should be noted that, for simplicity of description, the foregoing method embodiments are all expressed as a series of action combinations, but it should be understood by those skilled in the art that the present application is not limited by the order of actions described, as some steps may be performed in other order or simultaneously in accordance with the present application. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily required in the present application.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments.
In the several embodiments provided in this application, it should be understood that the disclosed apparatus may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, such as the division of the units, merely a logical function division, and there may be additional manners of dividing the actual implementation, such as multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some service interface, device or unit indirect coupling or communication connection, electrical or otherwise.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable memory. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a memory, including several instructions for causing a computer device (which may be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. And the aforementioned memory includes: a U-disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Those of ordinary skill in the art will appreciate that all or a portion of the steps in the various methods of the above embodiments may be performed by hardware associated with a program that is stored in a computer readable memory, which may include: flash disk, read-Only Memory (ROM), random-access Memory (Random Access Memory, RAM), magnetic or optical disk, and the like.
The foregoing is merely exemplary embodiments of the present disclosure and is not intended to limit the scope of the present disclosure. That is, equivalent changes and modifications are contemplated by the teachings of this disclosure, which fall within the scope of the present disclosure. Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a scope and spirit of the disclosure being indicated by the claims.

Claims (10)

1. The information transmission method is characterized by being applied to terminal equipment, wherein the terminal equipment comprises a first operating system and a second operating system, the power consumption of the terminal equipment for normally operating the first operating system is smaller than the power consumption of the terminal equipment for operating the second operating system, and the method comprises the following steps:
The first operating system acquires information of abnormal ending operation of a target application, wherein the information of abnormal ending operation is used for indicating the abnormal ending operation of the target application;
the second operating system acquires a stop instruction, wherein the stop instruction is generated based on the abnormal ending operation information of the target application, and the stop instruction is used for indicating the second operating system to control the functional device which is being called by the target application to stop working.
2. The method of claim 1, wherein the first operating system comprises a keep-alive process, and wherein before the first operating system obtains information of an abnormal end of running of the target application, further comprising:
in the state that the target application is started, the target application calls a Binder registration method of the keep-alive process to register a target Binder, and the target Binder corresponds to at least one item of target stop instruction;
the second operating system obtains a stop instruction, wherein the stop instruction is generated based on information of abnormal ending operation of the target application, and the stop instruction is used for indicating the second operating system to control the function device which is being called by the target application to stop working, and the method comprises the following steps:
The second operating system acquires at least one target stopping instruction corresponding to the target Binder, the target stopping instruction is generated based on information of abnormal ending operation of the target application, and the target stopping instruction is used for indicating the second operating system to control the functional device which is being called by the target application to stop working.
3. The method according to claim 2, wherein the second operating system obtains at least one target stop instruction corresponding to the target Binder, the target stop instruction being generated based on information of abnormal ending of the target application, the target stop instruction being used for instructing the second operating system to control the functional device being invoked by the target application to stop working, and the method comprises:
the first operating system acquires information of abnormal ending operation of a target application and sends the information of abnormal ending operation to the kept alive process;
and the keep-alive process sends at least one target stopping instruction corresponding to a target Binder to the second operating system, and the second operating system controls the functional device which is being called by the target application to stop working based on the target stopping instruction.
4. The method of claim 3, wherein the process being kept alive creates a target desthrekeeper for the target Binder and binds the target Binder with the target desthrekeeper, wherein the first operating system obtains information of an abnormally ending operation of a target application and sends the information of the abnormally ending operation to the process being kept alive, comprising:
and the first operating system sends the abnormal ending operation information of the target application to a target desthrecasting, and triggers and executes a BinderDied method corresponding to the target desthrecasting, wherein the BinderDied method comprises at least one item of target stop instruction.
5. A method according to claim 2 or 3, characterized in that the method further comprises:
and under the state that the target application normally finishes running, the first operating system finishes monitoring the running state of the target application.
6. The method according to claim 4, wherein the method further comprises:
and under the state that the target application normally finishes running, the target application calls a Binder cancellation method of the keep-alive process to cancel the target Binder, and/or the keep-alive process unbinds the target Binder and the target desthrecient.
7. The method of claim 4, wherein the sending the at least one target stop instruction to the second operating system, the second operating system controlling the functional device being invoked by the target application to stop working based on the target stop instruction, further comprises:
the keep-alive process deregisters the target Binder and/or unbinds the target Binder from the target desthreeceient.
8. An information transmission device, characterized in that it is applied to a terminal device, the terminal device includes a first operating system and a second operating system, the power consumption of the terminal device for operating the first operating system is smaller than the power consumption of the terminal device for operating the second operating system, the information transmission device includes:
the first operating system is used for acquiring information of abnormal ending operation of the target application, and the information of abnormal ending operation is used for indicating the abnormal ending operation of the target application;
the second operating system is used for acquiring a stop instruction, the stop instruction is generated based on information of abnormal ending operation of the target application, and the stop instruction is used for indicating the second operating system to control the functional device which is being called by the target application to stop working.
9. A storage medium having stored thereon a computer program, which when executed by a processor performs the steps of the method according to any of claims 1 to 7.
10. A terminal device, comprising: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the steps of the method according to any one of claims 1-7.
CN202210024525.3A 2022-01-10 2022-01-10 Information transmission method, device, storage medium and terminal equipment Pending CN116449936A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210024525.3A CN116449936A (en) 2022-01-10 2022-01-10 Information transmission method, device, storage medium and terminal equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210024525.3A CN116449936A (en) 2022-01-10 2022-01-10 Information transmission method, device, storage medium and terminal equipment

Publications (1)

Publication Number Publication Date
CN116449936A true CN116449936A (en) 2023-07-18

Family

ID=87124381

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210024525.3A Pending CN116449936A (en) 2022-01-10 2022-01-10 Information transmission method, device, storage medium and terminal equipment

Country Status (1)

Country Link
CN (1) CN116449936A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117201748A (en) * 2023-11-06 2023-12-08 博泰车联网(南京)有限公司 Video stream display method, device, equipment and storage medium

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117201748A (en) * 2023-11-06 2023-12-08 博泰车联网(南京)有限公司 Video stream display method, device, equipment and storage medium
CN117201748B (en) * 2023-11-06 2024-01-26 博泰车联网(南京)有限公司 Video stream display method, device, equipment and storage medium

Similar Documents

Publication Publication Date Title
US7558884B2 (en) Processing information received at an auxiliary computing device
US20180357085A1 (en) Method and apparatus for running android application on windows system
CN111459586B (en) Remote assistance method, device, storage medium and terminal
CN111124668B (en) Memory release method, memory release device, storage medium and terminal
CN103493010A (en) Cross-environment event notification
CN111597042A (en) Service thread running method and device, storage medium and electronic equipment
EP2972830A1 (en) Switching to and from native web applications
CN110702346B (en) Vibration testing method and device, storage medium and terminal
CN116449936A (en) Information transmission method, device, storage medium and terminal equipment
CN111913614B (en) Multi-picture display control method and device, storage medium and display
CN111078325A (en) Application program running method and device, electronic equipment and storage medium
CN114327087A (en) Input event processing method and device, electronic equipment and storage medium
CN113268286A (en) Application starting method and device, projection equipment and storage medium
CN110489318B (en) Systrace information grabbing method and device, storage medium and terminal
CN112114965A (en) Application program running method and device, terminal and storage medium
CN113825022B (en) Method and device for detecting play control state, storage medium and electronic equipment
CN113950043B (en) Communication method, device, storage medium and terminal
CN113972989B (en) Data verification method, storage medium and electronic equipment
CN111766992B (en) Information display method and device, electronic equipment and storage medium
CN113315687B (en) Proxy network management method, device, storage medium and terminal
CN113312572A (en) Resource processing method and device, storage medium and electronic equipment
CN113419650A (en) Data moving method and device, storage medium and electronic equipment
CN110865760A (en) Electronic equipment operation method and device, electronic equipment and storage medium
CN112698884A (en) Program starting method, device, system, equipment and storage medium
CN112612633B (en) Inter-process communication method, inter-process communication device, storage medium and terminal

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination