CN114924860A - Method and device for calling data by multiple applications and intelligent wearable equipment - Google Patents

Method and device for calling data by multiple applications and intelligent wearable equipment Download PDF

Info

Publication number
CN114924860A
CN114924860A CN202210599483.6A CN202210599483A CN114924860A CN 114924860 A CN114924860 A CN 114924860A CN 202210599483 A CN202210599483 A CN 202210599483A CN 114924860 A CN114924860 A CN 114924860A
Authority
CN
China
Prior art keywords
application
data
functional component
unit
instruction
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
CN202210599483.6A
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.)
Goertek Inc
Original Assignee
Goertek Inc
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 Goertek Inc filed Critical Goertek Inc
Priority to CN202210599483.6A priority Critical patent/CN114924860A/en
Publication of CN114924860A publication Critical patent/CN114924860A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements 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/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4411—Configuring for operating with peripheral devices; Loading of device drivers
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Abstract

The embodiment of the invention discloses a method and a device for calling data by multiple applications and intelligent wearable equipment. The application processor starts the first object and sets a data calling function corresponding to the first object. And when a data calling instruction of the second application to the first functional component is acquired, adding the application identifier of the second application in the corresponding relation. And acquiring data acquired by the first functional component according to the data calling function, and feeding back the data to the first application and the second application respectively based on the corresponding relation. The first object is deployed on the application processor, so that the first functional component is managed and controlled, even if a plurality of applications call data of the first functional component, the corresponding relation between the plurality of applications and the first object is recorded, the obtained data can be fed back to the corresponding plurality of applications according to the corresponding relation, and the problem that the plurality of applications cannot coexist is solved.

Description

Method and device for multi-application data calling and intelligent wearable equipment
Technical Field
The invention relates to the technical field of intelligent equipment, in particular to a method and a device for multi-application data calling and intelligent wearable equipment.
Background
With the development of electronic devices, smart wearable devices are beginning to lead new electronic wave instead of smart phones and PCs (Personal computers). Because of the fashionable appearance of the intelligent wearable device, the wearable performance of the intelligent wearable device is superior to that of a mobile phone, and the intelligent wearable device is more and more popular with consumers. But the wearable device is limited by the characteristics of small and exquisite appearance, long-time wearing and the like, so the system architecture level of the intelligent wearable device is also different from the current mainstream smart phone architecture. The smart phone mainly adopts a single processor architecture, and the current intelligent wearable device adopts a dual processor architecture. The dual process may use a mainstream AP (Application Processor) and MCU (Micro Control Unit).
The AP side mainly runs an operating system with high power consumption, and the MCU side is mainly used for mounting various sensors (sensors) and needs to run an embedded operating system with low power consumption all the time. The dual-processor architecture of the intelligent wearable device can greatly prolong the standby time of the product on the premise of meeting the functional requirements. Therefore, the mainstream intelligent wearable equipment at present mostly adopts a dual-processor architecture.
However, for a dual system, how to make synchronization between the two systems is a new challenge. In the existing dual-system intelligent wearable device, an AP side and an MCU side control the operation of a Sensor at the MCU side and receive Sensor data reported by the MCU through defining instructions. If only a single application or service on the AP side needs to control the Sensor on the MCU side, the AP side can operate normally. However, at the same time, the AP side only supports connection of a single application with the Sensor of the MCU side, and if there are multiple applications or services on the AP side that need to control the Sensor of the MCU side at the same time, a conflict will be caused, and coexistence of multiple applications cannot be supported.
Therefore, how to solve the problem that multiple applications cannot coexist is a problem to be solved by those skilled in the art.
Disclosure of Invention
The embodiment of the invention aims to provide a method and a device for calling data by multiple applications and intelligent wearable equipment, which can solve the problem that the multiple applications cannot coexist.
To solve the foregoing technical problem, an embodiment of the present invention provides a method for multi-application data retrieval, including:
under the condition that a data calling instruction of a first application to a first functional component is obtained, recording the corresponding relation between the first application and a first object; the first object is a module which is deployed on an application processor and used for managing and controlling a first functional component;
starting the first object, and setting a data calling function corresponding to the first object;
under the condition that a data calling instruction of a second application to the first functional component is obtained, adding an application identifier of the second application in the corresponding relation;
acquiring data acquired by the first functional component according to the data calling function;
feeding back the data to the first application and the second application based on the corresponding relationship.
Optionally, in the case of acquiring a data call instruction of a first application to a first functional component, before recording a correspondence between the first application and a first object, the method further includes:
after the equipment is started, acquiring a functional component list fed back by a microcontroller;
and constructing an object corresponding to each functional component according to the functional components contained in the functional component list.
Optionally, the constructing an object corresponding to each of the functional components according to the functional components included in the functional component list further includes:
and establishing a monitoring module for detecting the use condition of the object at the application layer for each object.
Optionally, after the starting the first object, further comprising:
recording the state of the first object as an active state;
adding one to an application count value corresponding to the first object;
correspondingly, after the second application is added to the corresponding relationship, the method further includes:
and adding one to the application count value corresponding to the first object.
Optionally, after the feeding back the data to the first application and the second application based on the correspondence relationship, the method further includes:
under the condition that an occupation canceling instruction of the first application for the first object is obtained, deleting the first application from the corresponding relation, and subtracting one from an application count value corresponding to the first object;
judging whether an application count value corresponding to the first object is zero or not;
under the condition that the application count value corresponding to the first object is zero, the state of the first object is adjusted to be in an inactive state, and an instruction for closing the first functional component is sent to a microcontroller;
and when the application count value corresponding to the first object is not zero, keeping the state of the first object as an active state.
Optionally, after the feeding back the data to the first application and the second application based on the corresponding relationship, the method further includes:
deleting the second application from the corresponding relation under the condition that an occupation canceling instruction of the second application on the first object is obtained, and subtracting one from an application count value corresponding to the first object;
judging whether an application count value corresponding to the first object is zero or not;
under the condition that the application count value corresponding to the first object is zero, adjusting the state of the first object to be in an inactive state, and sending an instruction for closing the first functional component to a microcontroller;
and when the application count value corresponding to the first object is not zero, keeping the state of the first object as an active state.
Optionally, the recording the correspondence between the first application and the first object includes:
establishing a corresponding relation list for the first object;
and adding the application identifier of the first application to the corresponding relation list.
The embodiment of the application also provides a device for calling data by multiple applications, which comprises a recording unit, a starting unit, a setting unit, an adding unit, an acquiring unit and a feedback unit;
the recording unit is used for recording the corresponding relation between a first application and a first object under the condition of acquiring a data calling instruction of the first application to a first functional component; the first object is a module which is deployed on an application processor and used for managing and controlling a first functional component;
the starting unit is used for starting the first object;
the setting unit is used for setting a data calling function corresponding to the first object;
the adding unit is used for adding the application identifier of the second application in the corresponding relation under the condition of acquiring a data calling instruction of the second application to the first functional component;
the acquisition unit is used for acquiring the data acquired by the first functional component according to the data calling function;
the feedback unit is configured to feed back the data to the first application and the second application based on the correspondence.
Optionally, the system further comprises a construction unit;
the acquisition unit is used for acquiring a functional component list fed back by the microcontroller after the equipment is started;
and the constructing unit is used for constructing the object corresponding to each functional component according to the functional components contained in the functional component list.
Optionally, the system further comprises a establishing unit;
the establishing unit is used for establishing a monitoring module for detecting the use condition of the object in the application layer for each object.
Optionally, the system further comprises a state recording unit and a counting unit;
the state recording unit is used for recording the state of the first object as an active state after the first object is started;
the counting unit is used for adding one to an application counting value corresponding to the first object after the first object is started; and after the second application is added in the corresponding relation, adding one to the application count value corresponding to the first object.
Optionally, the system further comprises a first deleting unit, a first judging unit, a first adjusting unit, a first sending unit and a first keeping unit;
the first deleting unit is configured to delete the first application from the corresponding relationship and subtract one from an application count value corresponding to the first object when an occupation cancellation instruction of the first application for the first object is obtained;
the first judging unit is configured to judge whether an application count value corresponding to the first object is zero;
the first adjustment unit is configured to adjust the state of the first object to an inactive state when the application count value corresponding to the first object is zero;
the first sending unit is used for sending an instruction for closing the first functional part to the microcontroller;
the first holding unit is configured to hold the state of the first object as an active state when the application count value corresponding to the first object is not zero.
Optionally, the system further comprises a second deleting unit, a second judging unit, a second adjusting unit, a second sending unit and a second holding unit;
the second deleting unit is configured to delete the second application from the corresponding relationship and subtract one from the application count value corresponding to the first object when the occupation cancellation instruction of the second application for the first object is obtained;
the second judging unit is configured to judge whether an application count value corresponding to the first object is zero;
the second adjusting unit is configured to adjust the state of the first object to be in an inactive state when the application count value corresponding to the first object is zero;
the second sending unit is used for sending an instruction for closing the first functional component to the microcontroller;
the second holding unit is configured to hold the state of the first object as an active state when the application count value corresponding to the first object is not zero.
Optionally, the recording unit includes an establishing subunit and an adding subunit;
the establishing subunit is used for establishing a corresponding relation list for the first object;
the adding subunit is configured to add the application identifier of the first application to the correspondence list.
The embodiment of the present application further provides a device for invoking data by multiple applications, including:
a memory for storing a computer program;
a processor for executing the computer program to implement the steps of the method for multi-application retrieval of data as described above.
The embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the computer program implements the steps of the method for invoking data by multiple applications as described above.
The embodiment of the application also provides intelligent wearable equipment, which comprises an application processor and a microcontroller;
the application processor is used for recording the corresponding relation between the first application and the first object under the condition of acquiring a data calling instruction of the first application to the first functional component; the first object is a module which is deployed on an application processor and used for managing and controlling a first functional component; starting the first object, and setting a data calling function corresponding to the first object; under the condition that a data calling instruction of a second application to the first functional component is acquired, adding an application identifier of the second application in the corresponding relation; acquiring data acquired by the first functional component according to the data calling function; feeding back the data to the first application and the second application based on the corresponding relation;
and the microcontroller is used for starting the first functional component to collect data under the condition of acquiring the starting instruction transmitted by the first object.
According to the technical scheme, the application processor records the corresponding relation between the first application and the first object under the condition of acquiring the data calling instruction of the first application to the first functional component; the first object is a module deployed on the application processor and used for managing and controlling the first functional component. The application processor starts the first object, and the first object can transmit a starting instruction to the microcontroller, so that the microcontroller starts the first functional component to collect data. In order to ensure smooth transmission of data, the application processor sets a data calling function corresponding to the first object, and a transmission path between the first functional component and the first object can be established based on the data calling function. When the application processor acquires a data calling instruction of the second application to the first functional component, in order to meet the data acquisition requirement of the second application, a transmission path between the first functional component and the first object also needs to be established, but before this, the application processor has already set a data calling function corresponding to the first object. In order to meet the requirement of coexistence of multiple applications, on the basis that the data retrieval function corresponding to the first object is set, the application identifier of the second application can be added in the corresponding relation, so that the problem of establishing multiple transmission paths between the first functional component and the application processor is avoided, and the application processor can clearly know which applications the first functional component needs to provide data for. Therefore, after the data acquired by the first functional component is acquired according to the data calling function, the data can be fed back to the first application and the second application respectively based on the corresponding relation. In the technical scheme, the first object is deployed on the application processor, so that the first functional component can be managed and controlled, even if a plurality of applications need to call data of the first functional component, the application processor can feed back the acquired data to the corresponding plurality of applications according to the corresponding relation on the basis of only establishing one transmission path between the first functional component and the first object by recording the corresponding relation between the plurality of applications and the first object, and the problem that the plurality of applications cannot coexist is solved.
Drawings
In order to more clearly illustrate the embodiments of the present invention, the drawings required for the embodiments will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained by those skilled in the art without inventive effort.
Fig. 1 is a schematic diagram of a software architecture of an improved Framework layer according to an embodiment of the present application;
fig. 2 is a flowchart of a method for retrieving data by multiple applications according to an embodiment of the present invention;
fig. 3 is a schematic flow chart illustrating a process of providing data of the same functional unit for two applications at the same time according to an embodiment of the present application;
fig. 4 is a schematic flowchart of a process that two applications close data acquisition requirements for a same functional unit according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an apparatus for retrieving data by multiple applications according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of another apparatus for retrieving data by multiple applications according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of an intelligent wearable device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without any creative work belong to the protection scope of the present invention.
In order that those skilled in the art will better understand the disclosure, the invention will be described in further detail with reference to the accompanying drawings and specific embodiments.
A commonly used dual system may consist of an application processor and a microcontroller. Based on the functional demand, dual system's intelligent wearing equipment often includes a plurality of functional unit, and the functional unit mount is on microcontroller. Multiple Applications (APPs) may be deployed on an application processor, or the application processor may enable interaction with multiple applications.
At present, the AP side only supports the connection of a single application and functional components of the MCU side at the same time of the intelligent wearable equipment based on the dual systems, and if the AP side has a plurality of applications or services which need to control the functional components of the MCU side at the same time, conflicts can be caused, and the coexistence of the applications can not be supported.
The conventional application processor comprises an application layer, a Framework layer, a HAL layer and a Kernel layer. The application layer runs mainly APP. The Framework layer provides an interface for the APP layer, and is used for controlling the functional components and acquiring data of the functional components, and a SubSystemSensorControl module is developed and defined in the Framework layer and is mainly used for controlling and managing the functional components mounted on the MCU side. The functional components are often presented in the form of sensors, and for ease of description, sensors may be used to represent the functional components. The HAL layer mainly analyzes the Sensor data at the MCU side according to the Protocol or assembles a control instruction sent to the MCU according to the Protocol. And the Kernel layer monitors data transmitted by the MCU side and transmits HAL layer data to the MCU side.
In order to satisfy the simultaneous calling of the same functional unit by multiple applications, in the embodiment of the application, the software architecture of the application processor is improved. In the embodiment of the application, the software architecture of the Framework layer is mainly improved. The application layer, the HAL layer and the Kernel layer may still perform related operations according to the original software architecture.
Fig. 1 is a schematic diagram of a software architecture of an improved Framework layer provided in an embodiment of the present application, where the improved Framework layer may include five parts, which are a subsystem Sensor service module, a subsystem Sensor manager module, a SensorBase module, a Sensor module, and a SensorAliveMonitor module. The Sensor module may include a plurality of Sensor objects, and in fig. 1, two Sensor objects, i.e., Sensor1 and Sensor2, are taken as an example, and each Sensor object has a corresponding Sensor alive monitor. For the convenience of distinction, a Sensor1AliveMonitor may be used to represent a Sensor AliveMonitor corresponding to Sensor1, and a Sensor2AliveMonitor may be used to represent a Sensor AliveMonitor corresponding to Sensor 2.
The SubSystemSensorService is a main service for managing the mount of the application processor Sensor, and can realize the interaction with the SubSystemSensormanager. The SubSystemSensorManager is mainly used to create and manage various sensors and corresponding Sensor data on the MCU side. SensorBase is used to define various general methods for sensors. The Sensor objects of various types are mainly used for controlling the sniser of the corresponding type and reporting related data. Each type of SensorAliveMonitor is used for detecting and controlling the use condition of the current Sensor in the application layer, and the control of the application layer is ensured not to cause conflict.
In the embodiment of the application, the Sensor objects corresponding to the functional components in a one-to-one mode are deployed on the application processor. Each Sensor object can realize the control of one corresponding functional component. Taking the first functional component, which is any one of all the functional components, as an example, the Sensor object corresponding to the first functional component may be referred to as a first object. Even if a plurality of applications need to call data of the first functional component, the corresponding relation between the plurality of applications and the first object is recorded, and the application processor can feed back the obtained data to the corresponding plurality of applications according to the corresponding relation on the basis of only establishing a transmission path between the first functional component and the first object, so that the problem that the plurality of applications cannot coexist is solved.
Next, a method for retrieving data by multiple applications according to an embodiment of the present invention is described in detail. Fig. 2 is a flowchart of a method for multiple applications to retrieve data according to an embodiment of the present invention, where the method includes:
s201: and recording the corresponding relation between the first application and the first object under the condition of acquiring a data calling instruction of the first application to the first functional component.
The method for calling data by multiple applications can be suitable for intelligent wearable equipment with double systems. More functional units are often arranged on the intelligent wearable device. Use intelligent bracelet as an example, be provided with the rhythm of the heart sensor that is used for rhythm of the heart to detect on the intelligent bracelet, be used for the acceleration sensor of meter step, these sensors are functional unit.
In the embodiment of the present application, the processing manner of invoking the functional component for each application is similar, and for convenience of description, the invocation of the first functional component is taken as an example for explanation.
The first object is a module deployed on the application processor for governing the first functional component. The first object corresponds to a first feature, and the first object may record an application having a call requirement for the first feature.
When a first application needs to acquire data acquired by a first functional component, because the first functional component is deployed on a microcontroller and is not directly controlled by an application processor, in the embodiment of the present application, a first object may be pre-deployed on the application processor, the application processor may implement direct control on the first object, and the first object may implement control on the first functional component, so that when a plurality of applications need to call the first functional component, all the applications may be converted into operations on the first object. Therefore, in the case of acquiring the data call instruction of the first application to the first functional component, the corresponding relationship between the first application and the first object can be recorded.
In consideration of the practical application, the number of objects deployed on the application processor can be multiple, and each object corresponds to a different type of functional component. And different applications may call for different features.
In order to ensure the ordered execution of the calling of the functional components by the applications, a correspondence list may be established for each object, and the application identifier of the application having the calling requirement for the functional component corresponding to the object may be recorded in the correspondence list.
Taking the first object as an example, in a specific implementation, a corresponding relationship list may be established for the first object; and adding the application identification of the first application to the corresponding relation list.
In the embodiment of the present application, the form of the application identifier is not limited, and may be used to distinguish different applications.
S202: and starting the first object, and setting a data calling function corresponding to the first object.
In the initial state, all objects deployed on the application processor are in an inactive state, and no specific work task is executed. Therefore, when a data calling instruction of the first application to the first functional component is acquired, the first object needs to be started, so that the first object is in an active state, at the moment, the first object can transmit a starting instruction to the microcontroller, and the microcontroller starts the first functional component to collect data.
In the initial state, there is no path between the first object and the first functional component, and therefore, in order to achieve communication between the first object and the first functional component, a corresponding data retrieval function needs to be provided for the first object. The data calling function may be a callback function.
S203: and under the condition that the data calling instruction of the second application to the first functional component is acquired, adding the application identifier of the second application in the corresponding relation.
When the application processor acquires a data calling instruction of the second application to the first functional component, in order to meet the data acquisition requirement of the second application, a transmission path between the first functional component and the first object also needs to be established, but before this, the application processor has already set a data calling function corresponding to the first object. In order to meet the requirement of coexistence of multiple applications, on the basis that the data calling function corresponding to the first object is set, the data calling function does not need to be set repeatedly for the first object, and the application identifier of the second application can be added in the corresponding relation, so that the problem of establishing multiple transmission paths between the first functional component and the application processor is avoided, and the application processor can clearly know which applications need to be provided with data by the first functional component.
S204: and acquiring data acquired by the first functional component according to the data calling function.
As can be seen from the schematic diagram of the software architecture in fig. 1, the present application mainly improves the software architecture of the Framework layer, and the application layer, the HAL layer, and the Kernel layer still operate in the original manner. For the convenience of the following description, the first object is Sensor1, the first application is App1, and the second application is App 2.
In practical applications, App1 may call a corresponding Sensor1 in the subsystem Sensor manager module, so that Sensor1 starts to work. The AP may call a HAL layer API for Sensor 1. The HAL layer encapsulates the command for starting the operation of the Sensor1 into fixed command format data through protocol specification. The HAL layer writes fixed command format data to the Kernel layer. And the Kernel layer transmits the data to the MCU side. And the MCU side opens corresponding functional parts according to the data format and starts to collect and report data. After the first functional component on the MCU side collects data, the data can be packaged into a fixed data format according to protocol regulations and then sent to the Kernel layer equipment node on the AP side; HAL layer service reads Kernel layer node data; the HAL layer analyzes the data according to the protocol; the HAL layer reports the data to the Sensor1 object through a callback registered by the Sensor1 object of the SubSystemSensorManager module.
S205: and feeding back data to the first application and the second application based on the corresponding relation.
The AP side records the corresponding relation between the first application, the second application and the first object, so that the first object can report the acquired data to the first application and the second application simultaneously based on the corresponding relation.
According to the technical scheme, the application processor records the corresponding relation between the first application and the first object under the condition of acquiring the data calling instruction of the first application to the first functional component; the first object is a module deployed on the application processor and used for managing and controlling the first functional component. The application processor starts the first object, and the first object can transmit a starting instruction to the microcontroller, so that the microcontroller starts the first functional component to collect data. In order to ensure smooth transmission of data, the application processor sets a data calling function corresponding to the first object, and a transmission path between the first functional component and the first object can be established based on the data calling function. When the application processor acquires a data calling instruction of the second application to the first functional component, in order to meet the data acquisition requirement of the second application, a transmission path between the first functional component and the first object also needs to be established, but before this, the application processor has already set a data calling function corresponding to the first object. In order to meet the requirement of coexistence of multiple applications, on the basis that the data retrieval function corresponding to the first object is set, the application identifier of the second application can be added in the corresponding relation, so that the problem of establishing multiple transmission paths between the first functional component and the application processor is avoided, and the application processor can clearly know which applications the first functional component needs to provide data for. Therefore, after the data collected by the first functional component is acquired according to the data calling function, the data can be fed back to the first application and the second application respectively based on the corresponding relation. In the technical scheme, the first object is deployed on the application processor, so that the first functional component can be managed and controlled, even if a plurality of applications need to call the data of the first functional component, the application processor can feed back the acquired data to the corresponding plurality of applications according to the corresponding relation on the basis of only establishing one transmission path between the first functional component and the first object by recording the corresponding relation between the plurality of applications and the first object, and the problem that the plurality of applications cannot coexist is solved.
In the embodiment of the present application, a software architecture of a Framework layer needs to be improved. Considering that types of functional components mounted on the MCU side are different for different types of devices, in order to be suitable for different types of devices, the SensorBase module, the Sensor module, and the SensorAliveMonitor module included in the Framework layer need to be dynamically set based on the functional components mounted on the MCU side, and therefore in the embodiment of the present application, the SubSystemSensorService module and the subsystemsensermanager module included in the Framework layer may be preset based on functions that need to be implemented, and may be automatically started when the device is started. The SensorBase module, the Sensor module and the SensorAliveMonitor module included in the Framework layer may be set after the AP side acquires the list of the functional components fed back by the MCU side.
In a specific implementation, after the device is started, the application processor can obtain a functional component list fed back by the microcontroller; the feature list contains all the types of features connected to the microcontroller and the functions that can be implemented by each feature. The application processor may construct an object corresponding to each functional unit according to the functional unit included in the functional unit list. In order to realize monitoring management of each object, a SensorAliveMonitor module, which is a monitoring module for detecting the use condition of the object in an application layer, can be established for each object.
With reference to the schematic diagram of the software architecture shown in fig. 1, when the device is powered on, the AP side system is loaded, the ServiceManager of the AP side system pulls up the subsystem sensor service module and the subsystem sensor manager module, and at this time, the AP side notifies the MCU side of powering on and powering on. The MCU side sequentially executes the initialization of the mounting equipment, acquires the creation of the relevant Task and the initialization of the Sensor, informs the AP side of finishing the startup and informs the AP side of a functional component list (Sensor list) mounted on the MCU side. After receiving the MCU side startup message, the AP side transmits the Sensor list to the SubSystemSensorManager module through the SubSystemSensorService module, the SubSystemSensorManager module creates sensors of various types through the Sensor list, and simultaneously creates corresponding Sensor Alivemonitor for the sensors of various types, and then the equipment is started successfully. As can be seen from fig. 1, the upper layer application controls each functional component on the MCU side and receives functional component data through the subsystem sensor service module. The data on the MCU side will eventually be passed to the application layer through each Sensor.
Each object has its corresponding monitoring module, which can be used to record the state of the object and the applications currently served by the object. Taking the first object as an example, in an actual application, when a data calling instruction of the first application to the first functional component is obtained, it is described that the first application needs to obtain data of the first functional component, in this application embodiment, the data collected by the first functional component may be fed back to each application by the first object, so that the first object may be started, and at this time, the monitoring module may record that the state of the first object is an active state; and adding one to the application count value corresponding to the first object.
The count value may be used to characterize the number of applications currently served by the first object. Correspondingly, after the second application is added to the corresponding relationship, it is described that the first object also needs to provide a service for the second application, and at this time, the application count value corresponding to the first object may be incremented by one. In an initial state, the count value corresponding to the first object is 0, and when the first object needs to provide services for the first application and the second application at the same time, the count value becomes 2.
Fig. 3 is a schematic flowchart of data of the same functional unit provided for two applications simultaneously according to an embodiment of the present application, and fig. 3 illustrates two applications, namely app1 and app 2. In fig. 3, ServiceManager belongs to the subsystem sensor service module, and Driver belongs to the function module included in the Kernel layer. In fig. 3, step 1 to step 6 are processes for starting up the AP-side system and starting and creating each Sensor by the subsystem Sensor manager, and the steps are as follows:
step 1: and when the AP side is started, the AP side system is loaded.
Step 2: and the AP side system starts a ServiceManager module.
And step 3: the ServiceManager module will start the subsystem Sensor service module to wait for the MCU to feed back the Sensor list.
And 4, step 4: the AP side informs the MCU side of powering on and starting up.
In practical applications, there is no restriction on the order of step 2 and step 4.
And 5: if the MCU side successfully starts the machine, the initialization of the mounted equipment is sequentially executed, the related Task creation and Sensor initialization are obtained, the AP side is informed to finish the startup, and the Sensor list mounted on the MCU side is reported to the SubSystemSensorManager module of the AP side.
Step 6: the SubSystemSensorManager module creates the various types of sensors through Sensor list.
The following describes the flow of controlling the Sensor by multiple applications and obtaining the Sensor data reported by the MCU.
And 7: after the system is started, App1 is started, and App1 starts a Sensor corresponding to the MCU side and processes corresponding data.
And 8: app1 calls the ServiceManager module of the system to acquire the SubSystemSensorService of the Framework layer, thereby acquiring the SubSystemSensorManager.
And step 9: app1 obtains a Sensor object corresponding to a Sensor of a specific type through a SubSystemSensorManager module, and registers a Sensor for receiving Sensor data. At this time, the Sensor1AliveMonitor module may record that the state of the Sensor object is an activity state, and count the value + 1.
The registration Sensor is mainly used for recording the corresponding relation between App1 and a Sensor object.
Step 10, the Sensor object acquires HAL layer service and registers callback for acquiring original Sensor data.
Step 11: app1 calls a corresponding Sensor object in the SubSystemSensorManager module to start the operation of the Sensor object.
Step 12: the HAL layer API is called for the Sensor object.
Step 13: and the HAL layer encapsulates the instruction for starting the MCU side Sensor to work into fixed command format data through protocol specification.
Step 14: the HAL layer writes fixed command format data to the Kernel layer.
Step 15: the Kernel layer sends the data to the MCU.
Step 16: and the MCU side opens a corresponding Sensor according to the data format and starts to collect and report data.
Step 17 to step 20: the same as the process of controlling the Sensor1 by the APP1, the process of step 7 can be referred to in step 17, the process of step 8 can be referred to in step 18, the process of step 9 can be referred to in step 19, and the process of step 10 can be referred to in step 20, and only the APP1 needs to be adjusted to APP 2.
In step 20, since App1 already registers a callback with the HAL layer service, App2 flow will not register a callback with the HAL layer again. The step is controlled by a Sensor1AliveMonitor module, when the Sensor1AliveMonitor module detects that the state of the Sensor at the AP side is activity, the registration of the callback to the HAL layer service is not repeated, and at the moment, the Sensor1AliveMonitor module records the count value + 1.
Step 21: and the data collected by the MCU side Sensor is packaged into a fixed data format through protocol specification and then is sent to the AP side Kernel layer equipment node.
Step 22: the HAL layer service reads Kernel layer node data.
Step 23: the HAL layer parses the data according to the protocol.
Step 24: the HAL layer reports the data to the Sensor object in the SubSystemSensorManager module through a callback registered by the Sensor object of the SubSystemSensorManager module.
Step 25-26: the Sensor in the SubSystemSensorManager module simultaneously reports the data to App1 and App2 through the sensors registered by App1 and App 2.
Through the process shown in fig. 3, a conflict that multiple applications open a Sensor at the same time is avoided, and multiple applications can receive Sensor data at the same time.
In this embodiment, the Sensor1AliveMonitor module may record the state of the first object and the number of applications of the service currently required by the first object, and may delete the correspondence between the applications and the first object when the applications do not require the service provided by the first object, and at this time, the Sensor1AliveMonitor module may adjust the state and the count value of the first object based on the number of applications of the service currently required by the first object.
In a specific implementation, the application processor may transmit an instruction to the Sensor1AliveMonitor module when acquiring an occupation canceling instruction of the first application for the first object, where the Sensor1AliveMonitor module may delete the first application from the corresponding relationship and subtract an application count value corresponding to the first object by one; and judging whether the application count value corresponding to the first object is zero or not.
When the application counter value corresponding to the first object is zero, it indicates that there is no application to invoke the first object, and at this time, the state of the first object may be adjusted to an inactive state, and an instruction to turn off the first functional unit is sent to the microcontroller. Under the condition that the application count value corresponding to the first object is not zero, it is shown that the first application does not have a demand for calling the first object at present, but other applications have a demand for calling the first object, and in order to ensure that the first object can feed back the acquired data to the served application, the state of the first object can be maintained in an active state at this time.
Similarly, for the second application, the application processor may transmit the instruction to the Sensor1AliveMonitor module when acquiring the occupation cancellation instruction of the second application on the first object, and at this time, the Sensor1AliveMonitor module may delete the second application from the corresponding relationship, and subtract the application count value corresponding to the first object by one; judging whether the application count value corresponding to the first object is zero or not; under the condition that the application count value corresponding to the first object is zero, adjusting the state of the first object to be in an inactive state, and sending an instruction for closing the first functional part to the microcontroller; and under the condition that the application count value corresponding to the first object is not zero, keeping the state of the first object as an active state.
Fig. 4 is a schematic flowchart of an embodiment of the present application, where two applications close data acquisition requirements for a same functional component, and fig. 4 takes two applications, namely app1 and app2 as an example. In fig. 4, ServiceManager belongs to the subsystem sensor service module, and Driver belongs to the function module included in the Kernel layer. The process flow of FIG. 4 is as follows:
step 1: app1 calls the corresponding Sensor interface to turn off the Sensor. Turning off a Sensor here refers to turning off App 1's invocation requirements for the Sensor object.
Step 2: the Sensor1AliveMonitor module corresponding to the Sensor will count value-1 and determine whether the count value is 0, the count value is not zero, and the Sensor state is kept as activity state.
And step 3: the Sensor object cancels the liener registered by App1, and the Sensor object does not send the data of the Sensor to App 1.
Step 4 to step 7: the Sensor of the MCU side is not closed, so the MCU side still sends the data collected by the Sensor to the AP side.
And 8: the Sensor object under the SubSystemSensorManager module will send data to App 2.
And step 9: app2 calls the Sensor interface to turn off the Sensor. Turning off a Sensor here refers to turning off the invocation demand of the App2 on the Sensor object.
Step 10: the Sensor1AliveMonitor module corresponding to the Sensor will count the value-1 and determine whether the count value is 0. The count value is zero, and the Sensor state is updated to be an inactivity state.
Step 11, 13-15: after the Sensor1AliveMonitor module updates the state of the Sensor to the inactivity state, the Sensor object sends a command for closing the Sensor, and the HAL layer encapsulates the command for closing the Sensor according to a protocol, then writes the command into a Kernel layer node, and sends the command to the MCU side.
Step 12: the Sensor object cancels the liener registered by App2, and the Sensor object does not send the data of the Sensor to App 2.
Steps 11 and 12 belong to two parallel process flows, while steps 13-15 belong to steps performed after step 11, and thus steps 11, 13-15 are incorporated together for the description.
Step 16: and the MCU side analyzes the data according to the protocol specification, closes the Sensor and stops data acquisition and reporting.
The above-mentioned Sensor refers to an object included in the AP side when the Sensor is on the AP side, and refers to a functional component included in the MCU side when the Sensor is on the MCU side. Since the object is created based on the functional component, and the functional component and the object are in a one-to-one correspondence relationship, they are all represented by Sensor in the above description.
The flow shown in fig. 4 avoids the conflict of closing the functional unit by a plurality of applications at the same time. When the first functional component provides services for a plurality of applications at the same time, if some application or some applications do not need to acquire data of the functional component any more, the data feedback to the applications is cancelled at the AP side, but the operation of the first functional component for feeding back data to the first object is not cancelled, and the first object still feeds back data to other applications with requirements, so that when some application or some applications do not need to acquire data of the functional component any more, the data transmission work between other applications and the functional component is not influenced.
Fig. 5 is a schematic structural diagram of an apparatus for invoking data by multiple applications according to an embodiment of the present invention, including a recording unit 51, a starting unit 52, a setting unit 53, an adding unit 54, an obtaining unit 55, and a feedback unit 56;
the recording unit 51 is configured to record a corresponding relationship between the first application and the first object when a data call instruction of the first application to the first functional component is acquired; the first object is a module which is deployed on the application processor and used for managing and controlling the first functional component;
an activation unit 52 for activating the first object;
a setting unit 53, configured to set a data call function corresponding to the first object;
an adding unit 54, configured to add an application identifier of the second application in the correspondence when the data call instruction of the second application to the first functional unit is acquired;
an obtaining unit 55, configured to obtain data collected by the first functional component according to a data call function;
and a feedback unit 56, configured to feed back data to the first application and the second application based on the correspondence.
Optionally, the system further comprises a construction unit;
the acquisition unit is used for acquiring a functional component list fed back by the microcontroller after the equipment is started;
and the construction unit is used for constructing the objects corresponding to the functional components according to the functional components contained in the functional component list.
Optionally, the system further comprises an establishing unit;
and the establishing unit is used for establishing a monitoring module for detecting the use condition of the object in the application layer for each object.
Optionally, the system further comprises a state recording unit and a counting unit;
the state recording unit is used for recording the state of the first object as an active state after the first object is started;
the counting unit is used for adding one to an application counting value corresponding to the first object after the first object is started; after adding the second application in the correspondence, the application count value corresponding to the first object is incremented by one.
Optionally, the system further comprises a first deleting unit, a first judging unit, a first adjusting unit, a first sending unit and a first keeping unit;
the first deleting unit is used for deleting the first application from the corresponding relation and subtracting one from the application count value corresponding to the first object under the condition of acquiring the occupation canceling instruction of the first application to the first object;
the first judging unit is used for judging whether the application count value corresponding to the first object is zero or not;
a first adjusting unit, configured to adjust a state of the first object to an inactive state when an application count value corresponding to the first object is zero;
the first sending unit is used for sending an instruction for closing the first functional part to the microcontroller;
and a first holding unit configured to hold the state of the first object in an active state when the application count value corresponding to the first object is not zero.
Optionally, the system further comprises a second deleting unit, a second judging unit, a second adjusting unit, a second sending unit and a second holding unit;
the second deleting unit is used for deleting the second application from the corresponding relation and subtracting one from the application count value corresponding to the first object under the condition of acquiring the occupation canceling instruction of the second application to the first object;
a second judging unit, configured to judge whether an application count value corresponding to the first object is zero;
a second adjusting unit, configured to adjust the state of the first object to be an inactive state when the application count value corresponding to the first object is zero;
the second sending unit is used for sending an instruction for closing the first functional part to the microcontroller;
and a second holding unit configured to hold the state of the first object as an active state when the application count value corresponding to the first object is not zero.
Optionally, the recording unit includes an establishing subunit and an adding subunit;
the establishing subunit is used for establishing a corresponding relation list for the first object;
and the adding subunit is used for adding the application identifier of the first application to the corresponding relationship list.
The description of the features in the embodiment corresponding to fig. 5 may refer to the related descriptions in the embodiments corresponding to fig. 1, fig. 3, and fig. 4, and is not repeated here.
According to the technical scheme, the application processor records the corresponding relation between the first application and the first object under the condition of acquiring the data calling instruction of the first application to the first functional component; the first object is a module deployed on the application processor and used for managing and controlling the first functional component. The application processor starts the first object, and the first object can transmit a starting instruction to the microcontroller, so that the microcontroller starts the first functional component to collect data. In order to ensure smooth transmission of data, the application processor sets a data calling function corresponding to the first object, and a transmission path between the first functional component and the first object can be established based on the data calling function. When the application processor acquires a data calling instruction of the second application to the first functional component, in order to meet the data acquisition requirement of the second application, a transmission path between the first functional component and the first object also needs to be established, but before this, the application processor has already set a data calling function corresponding to the first object. In order to meet the requirement of coexistence of multiple applications, on the basis that the data retrieval function corresponding to the first object is set, the application identifier of the second application can be added in the corresponding relation, so that the problem of establishing multiple transmission paths between the first functional component and the application processor is avoided, and the application processor can clearly know which applications the first functional component needs to provide data for. Therefore, after the data collected by the first functional component is acquired according to the data calling function, the data can be fed back to the first application and the second application respectively based on the corresponding relation. In the technical scheme, the first object is deployed on the application processor, so that the first functional component can be managed and controlled, even if a plurality of applications need to call data of the first functional component, the application processor can feed back the acquired data to the corresponding plurality of applications according to the corresponding relation on the basis of only establishing one transmission path between the first functional component and the first object by recording the corresponding relation between the plurality of applications and the first object, and the problem that the plurality of applications cannot coexist is solved.
Fig. 6 is a schematic structural diagram of another apparatus 60 for multiple applications to retrieve data according to an embodiment of the present invention, including:
a memory 61 for storing a computer program;
a processor 62 for executing the computer program to implement the steps of the method for multi-application retrieval of data as described above.
The embodiment of the application also provides a computer readable storage medium, on which a computer program is stored, and when being executed by a processor, the computer program realizes the steps of the method for invoking data by multiple applications as described above.
Fig. 7 is a schematic structural diagram of an intelligent wearable device provided in an embodiment of the present invention, including an application processor 71 and a microcontroller 72;
the application processor 71 is configured to record a corresponding relationship between the first application and the first object when a data call instruction of the first application to the first functional component is acquired; the first object is a module which is deployed on the application processor and used for managing and controlling the first functional component; starting a first object, and setting a data calling function corresponding to the first object; under the condition that a data calling instruction of a second application to the first functional component is obtained, adding an application identifier of the second application in the corresponding relation; acquiring data acquired by a first functional component according to a data calling function; feeding back data to the first application and the second application based on the corresponding relation;
and the microcontroller 72 is used for starting the first functional component to collect data under the condition of acquiring the starting instruction transmitted by the first object.
Fig. 7 illustrates three functional units mounted on the microcontroller 72, and in practical applications, the number of the functional units may be more or less, which is not limited herein, and fig. 7 is only an example.
In combination with an actual application scenario, the first functional component may be a heart rate sensor, the first application may be a user APP, and the user may realize the control of the intelligent wearable device through the user APP, for example, acquire data acquired by the heart rate sensor on the intelligent wearable device. The second application can be a self-starting application program set by the intelligent wearable device, and the self-starting application program can acquire data collected by the heart rate sensor at regular time according to a set time interval. The object corresponding to the heart rate sensor can be deployed by the application processor on the intelligent wearable device, the corresponding relation between the first application and the object and the corresponding relation between the second application and the object are recorded, the object can acquire data acquired by the heart rate sensor, and the data acquired by the object can be fed back to the first application and the second application by the application processor according to the requirements of the first application and the second application.
The description of the features in the embodiment corresponding to fig. 7 may refer to the related descriptions in the embodiments corresponding to fig. 1, fig. 3, and fig. 4, and is not repeated here.
According to the technical scheme, the application processor records the corresponding relation between the first application and the first object under the condition of acquiring the data calling instruction of the first application to the first functional component; the first object is a module deployed on the application processor and used for managing and controlling the first functional component. The application processor starts the first object, and the first object can transmit a starting instruction to the microcontroller, so that the microcontroller starts the first functional component to collect data. In order to ensure smooth transmission of data, the application processor sets a data calling function corresponding to the first object, and a transmission path between the first functional component and the first object can be established based on the data calling function. When the application processor acquires a data calling instruction of the second application to the first functional component, in order to meet the data acquisition requirement of the second application, a transmission path between the first functional component and the first object also needs to be established, but before this, the application processor has already set a data calling function corresponding to the first object. In order to meet the requirement of coexistence of multiple applications, on the basis that the data retrieval function corresponding to the first object is set, the application identifier of the second application can be added in the corresponding relationship, so that the problem of establishing multiple transmission paths between the first functional component and the application processor is avoided, and the application processor can clearly know which applications the first functional component needs to provide data for. Therefore, after the data acquired by the first functional component is acquired according to the data calling function, the data can be fed back to the first application and the second application respectively based on the corresponding relation. In the technical scheme, the first object is deployed on the application processor, so that the first functional component can be managed and controlled, even if a plurality of applications need to call data of the first functional component, the application processor can feed back the acquired data to the corresponding plurality of applications according to the corresponding relation on the basis of only establishing one transmission path between the first functional component and the first object by recording the corresponding relation between the plurality of applications and the first object, and the problem that the plurality of applications cannot coexist is solved.
The method and the device for multi-application data retrieval and the intelligent wearable device provided by the embodiment of the invention are described in detail above. The embodiments are described in a progressive mode in the specification, the emphasis of each embodiment is on the difference from the other embodiments, and the same and similar parts among the embodiments can be referred to each other. The device disclosed in the embodiment corresponds to the method disclosed in the embodiment, so that the description is simple, and the relevant points can be referred to the description of the method part. It should be noted that, for those skilled in the art, it is possible to make various improvements and modifications to the present invention without departing from the principle of the present invention, and those improvements and modifications also fall within the scope of the claims of the present invention.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

Claims (10)

1. A method for retrieving data by multiple applications, comprising:
under the condition that a data calling instruction of a first application to a first functional component is obtained, recording the corresponding relation between the first application and a first object; the first object is a module which is deployed on an application processor and used for managing and controlling a first functional component;
starting the first object, and setting a data calling function corresponding to the first object;
under the condition that a data calling instruction of a second application to the first functional component is acquired, adding an application identifier of the second application in the corresponding relation;
acquiring data acquired by the first functional component according to the data calling function;
feeding back the data to the first application and the second application based on the corresponding relationship.
2. The method according to claim 1, wherein before the recording the correspondence between the first application and the first object in the case of acquiring the data call instruction of the first application to the first functional component, further comprises:
after the equipment is started, acquiring a functional component list fed back by a microcontroller;
and constructing an object corresponding to each functional component according to the functional components contained in the functional component list.
3. The method for retrieving data by multiple applications according to claim 2, wherein after the building of the object corresponding to each of the functional components according to the functional components included in the functional component list, the method further comprises:
a monitoring module for detecting the use condition of the object in the application layer is established for each object.
4. The method of claim 1, further comprising, after said launching said first object:
recording the state of the first object as an active state;
adding one to an application count value corresponding to the first object;
correspondingly, after the second application is added to the corresponding relationship, the method further includes:
and adding one to the application count value corresponding to the first object.
5. The method for retrieving data by multiple applications according to claim 4, further comprising, after the feeding back the data to the first application and the second application based on the correspondence relationship:
under the condition that an occupation canceling instruction of the first application on the first object is obtained, deleting the first application from the corresponding relation, and subtracting one from an application count value corresponding to the first object;
judging whether an application count value corresponding to the first object is zero or not;
under the condition that the application count value corresponding to the first object is zero, adjusting the state of the first object to be in an inactive state, and sending an instruction for closing the first functional component to a microcontroller;
and when the application count value corresponding to the first object is not zero, keeping the state of the first object as an active state.
6. The method for retrieving data by multiple applications according to claim 4, further comprising, after the feeding back the data to the first application and the second application based on the correspondence relationship:
deleting the second application from the corresponding relation under the condition that an occupation canceling instruction of the second application on the first object is obtained, and subtracting one from an application count value corresponding to the first object;
judging whether an application count value corresponding to the first object is zero or not;
under the condition that the application count value corresponding to the first object is zero, the state of the first object is adjusted to be in an inactive state, and an instruction for closing the first functional component is sent to a microcontroller;
and when the application count value corresponding to the first object is not zero, keeping the state of the first object as an active state.
7. The method for calling data from multiple applications according to claim 1, wherein the recording the correspondence between the first application and the first object comprises:
establishing a corresponding relation list for the first object;
adding the application identifier of the first application to the correspondence list.
8. The device for calling data by multiple applications is characterized by comprising a recording unit, a starting unit, a setting unit, an adding unit, an acquiring unit and a feedback unit;
the recording unit is used for recording the corresponding relation between the first application and the first object under the condition of acquiring a data calling instruction of the first application to the first functional component; the first object is a module which is deployed on an application processor and used for managing and controlling a first functional component;
the starting unit is used for starting the first object;
the setting unit is used for setting a data calling function corresponding to the first object;
the adding unit is used for adding the application identifier of the second application in the corresponding relation under the condition of acquiring a data calling instruction of the second application to the first functional component;
the acquisition unit is used for acquiring the data acquired by the first functional component according to the data calling function;
the feedback unit is configured to feed back the data to the first application and the second application based on the correspondence.
9. An apparatus for retrieving data by multiple applications, comprising:
a memory for storing a computer program;
a processor for executing the computer program to carry out the steps of the method of multi-application calling data according to any one of claims 1 to 7.
10. The intelligent wearable device is characterized by comprising an application processor and a microcontroller;
the application processor is used for recording the corresponding relation between the first application and the first object under the condition of acquiring a data calling instruction of the first application to the first functional component; the first object is a module which is deployed on an application processor and used for managing and controlling a first functional component; starting the first object, and setting a data calling function corresponding to the first object; under the condition that a data calling instruction of a second application to the first functional component is obtained, adding an application identifier of the second application in the corresponding relation; acquiring data acquired by the first functional component according to the data calling function; feeding back the data to the first application and the second application based on the corresponding relation;
and the microcontroller is used for starting the first functional component to collect data under the condition of acquiring the starting instruction transmitted by the first object.
CN202210599483.6A 2022-05-30 2022-05-30 Method and device for calling data by multiple applications and intelligent wearable equipment Pending CN114924860A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210599483.6A CN114924860A (en) 2022-05-30 2022-05-30 Method and device for calling data by multiple applications and intelligent wearable equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210599483.6A CN114924860A (en) 2022-05-30 2022-05-30 Method and device for calling data by multiple applications and intelligent wearable equipment

Publications (1)

Publication Number Publication Date
CN114924860A true CN114924860A (en) 2022-08-19

Family

ID=82813301

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210599483.6A Pending CN114924860A (en) 2022-05-30 2022-05-30 Method and device for calling data by multiple applications and intelligent wearable equipment

Country Status (1)

Country Link
CN (1) CN114924860A (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101833520A (en) * 2009-03-11 2010-09-15 凹凸电子（武汉）有限公司 Method for simultaneously utilizing one camera by computer system and a plurality of application programs
CN105554059A (en) * 2015-11-25 2016-05-04 北京华油信通科技有限公司 Logistics transportation intelligent perception and position service system based on Beidou navigation technology
CN111149141A (en) * 2017-09-04 2020-05-12 Nng软件开发和商业有限责任公司 Method and apparatus for collecting and using sensor data from a vehicle

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101833520A (en) * 2009-03-11 2010-09-15 凹凸电子（武汉）有限公司 Method for simultaneously utilizing one camera by computer system and a plurality of application programs
CN105554059A (en) * 2015-11-25 2016-05-04 北京华油信通科技有限公司 Logistics transportation intelligent perception and position service system based on Beidou navigation technology
CN111149141A (en) * 2017-09-04 2020-05-12 Nng软件开发和商业有限责任公司 Method and apparatus for collecting and using sensor data from a vehicle

Similar Documents

Publication Publication Date Title
CN109582472B (en) Micro-service processing method and device
WO2021036809A1 (en) Subscriber identity module (sim) management method and electronic device
US7536688B2 (en) Segmented virtual machine
CN103970601B (en) Execute operational order method and apparatus
EP3989613A1 (en) Sim card resource management scheduling apparatus, communication terminal, and system
CN106331065A (en) Proxy application for host system with service container and system
CN110875833A (en) Cluster hybrid cloud, job processing method and device and electronic equipment
CN110391873A (en) For determining the method, apparatus and computer program product of data mode
CN114924860A (en) Method and device for calling data by multiple applications and intelligent wearable equipment
CN112312494B (en) Communication method and terminal device
JP6140939B2 (en) Network device, communication method, communication program
CN110336712B (en) Method and device for capturing empty packet by mobile terminal, storage medium and mobile terminal
US20100113084A1 (en) Power saving in wireless networks
CN113806030A (en) Application scheduling method and electronic equipment
CN112787828B (en) Application flow statistical method and device and mobile electronic device
CN113039517A (en) Audio resource calling method and device and electronic equipment
CN107205027A (en) A kind of method and device of alarm clock management
CN110650259B (en) Call request response method, device, server, terminal and storage medium
CN115226048A (en) Data transmission method, device, equipment and storage medium
KR100593843B1 (en) An application program management system for a mobile telecommunication terminal
US11874722B2 (en) Applying modern standby configurations on a per-application basis
WO2024078251A1 (en) Display method and electronic device
CN103546625A (en) Terminal operation control method and device
CN107332928B (en) Using account synchronization management method, device, storage medium and electronic equipment
CN110662280B (en) Method and device for switching operation modes, readable storage medium and electronic equipment

Legal Events

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