CN116743761B

CN116743761B - Cooperative working method and electronic equipment

Info

Publication number: CN116743761B
Application number: CN202211319661.1A
Authority: CN
Inventors: 纪胜伍
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2022-10-26
Filing date: 2022-10-26
Publication date: 2024-04-16
Anticipated expiration: 2042-10-26
Also published as: CN116743761A

Abstract

The application provides a cooperative working method and electronic equipment, and relates to the technical field of terminals. The method can filter the equipment in the process of acquiring the equipment information, so that the equipment information only comprises equipment corresponding to the equipment role concerned by the equipment information, and the efficiency of the processing process based on the equipment information can be improved. The method comprises the following steps: the method comprises the steps that a main device receives first operation of a user on a first application, generates a collaborative task according to the first operation, and decomposes the collaborative task into a plurality of subtasks; the master device screens one or more slave devices according to the client roles of the first application to obtain available devices, wherein the device roles of the available devices are matched with the client roles of the first application; the master device determines a device for executing each subtask from available devices; the main device sends the plurality of subtasks to the corresponding devices for execution.

Description

Cooperative working method and electronic equipment

Technical Field

The present application relates to the field of terminal technologies, and in particular, to a method and an electronic device for collaborative work.

Background

In general, a plurality of devices may form a collaboration system through a hotspot or a router of a certain device, and after the collaboration system is formed, each device in the collaboration system may perform collaborative tasks such as collaborative playing, collaborative recording, collaborative conference, and the like. A cooperative system is generally composed of one master device and a plurality of slave devices, wherein the master device is used for controlling each slave device to perform a cooperative task together, and each slave device performs the cooperative task according to control information of the master device. That is, in the cooperative system, only the master device can respond to the cooperative task initiated by the user, and then the cooperative task is allocated to the slave device in the cooperative system to be executed.

In practical application, when the master device allocates a cooperative task, it is necessary to acquire a device list including all the slave devices, and then select one slave device from the device list to allocate the cooperative task for the master device. However, not every slave device in the device list may perform the cooperative task, that is, the slave devices in the device list having the cooperative task and not being required, resulting in a low efficiency of the subsequent master device to allocate the cooperative task.

Disclosure of Invention

The embodiment of the application provides a cooperative working method and electronic equipment, which can filter equipment before task allocation and reduce the interference of irrelevant equipment to a processing process.

In order to achieve the above purpose, the embodiment of the present application adopts the following technical scheme:

In a first aspect, the present application provides a method for cooperative work, applied to a cooperative system, where the cooperative system includes a master device and one or more slave devices, the master device includes a first application, the master device stores device information of the one or more slave devices, the device information includes a device identifier and a device role, and the method includes: the method comprises the steps that a main device receives first operation of a user on a first application, generates a collaborative task according to the first operation, and decomposes the collaborative task into a plurality of subtasks; the master device screens one or more slave devices according to the client roles of the first application to obtain available devices, wherein the device roles of the available devices are matched with the client roles of the first application, and when the device roles of the available devices are identical or partially identical to the client roles of the first application, the device roles of the available devices are matched with the client roles of the first application; the master device determines a device for executing each subtask from available devices; the main device sends the plurality of subtasks to the corresponding devices for execution.

It can be seen that when the master device initiates the collaborative task, the available devices (i.e. the devices meeting the service requirements of the first application) are screened out from all the devices according to the client role of the first application. Therefore, the finally obtained available equipment information only comprises equipment meeting the first application requirement, so that the interference of other irrelevant equipment to the main equipment when sub-tasks are distributed according to the available equipment information can be reduced, and the efficiency of the processing process is improved; but also can reduce the information quantity transmitted in the transmission process and improve the transmission efficiency.

In one embodiment provided in the first aspect, the method further comprises: the method comprises the steps that a master device receives a second operation of a user on a first application, and a client identifier and a client role are distributed to the first application; the master device records the mapping relation between the client identification and the client role. Therefore, the master device can allocate the client identifier and the client role to the first application, record the mapping relationship between the client identifier and the client role, and facilitate the subsequent device filtering by using the mapping relationship.

In one embodiment provided in the first aspect, the method further comprises: when detecting that the state of the first device changes, the master device generates a state change notification, wherein the state change notification is used for notifying the target application that the state of the first device changes, the first device is any device for executing subtasks, the client role of the target application is matched with the device role of the first device, and when the device role of the first device is identical or partially identical to the client role of the target application, the device role of the first device is matched with the client role of the target application. Thus, for applications that do not focus on the role of the device corresponding to the first device, no notification of a state change is received. That is, the application may not process the state change notification of the device corresponding to the device role that is not of interest, so as to achieve the purpose of filtering the message.

In one embodiment provided in the first aspect, the method further comprises: and the master device screens out the target application from the plurality of applications according to the device role of the first device.

In one implementation manner provided in the first aspect, the master device further includes a device management software development kit SDK and a device management service, where the device management service includes a control center module, and after the master device receives a first operation of the first application by a user, the method further includes: the first application calls a device management SDK to acquire available device information; the device management SDK sends a request to the control center module to obtain the available device information, the request to obtain the available device information including a client identification of the first application.

In an implementation manner provided in the first aspect, the device management service further includes a client role management module and a device management module, where the master device screens available devices from one or more slave devices according to a client role of the first application, and specifically includes: the control center module sends a request for acquiring available equipment information to the equipment management module; in response to receiving a request to obtain available device information, the device management module obtains a device list including one or more slave devices and device information for each slave device; the device management module sends a device list to the control center module; the control center module sends a device list and a client identifier of the first application to the client role management module; the client role management module obtains the client role of the first application based on the client identification query of the first application, and takes the equipment with the equipment role matched with the client role of the first application in the equipment list as available equipment.

In one embodiment provided in the first aspect, the method further comprises: the client role management module sends available equipment information to the control center module, wherein the available equipment information comprises available equipment; the control center module sends available equipment information to the equipment management SDK; the device management SDK sends available device information to the first application.

In an implementation manner provided in the first aspect, the master device further includes a device management SDK, and after the master device receives the second operation of the first application by the user, the method further includes: the first application calls a device management SDK creation client; assigning a client identifier and a client role to a first application, comprising: the device management SDK assigns a client identity and a client role to the first application.

In one implementation manner provided in the first aspect, the master device further includes a device management service, where the device management service includes a control center module and a client role management module, and the method further includes: the first application calls the equipment management SDK to connect with the control center module; the equipment management SDK sends a connection request to the control center module, wherein the connection request comprises a client identifier and a client role of the first application; the control center module sends a connection request to the client role management module; the master device records the mapping relation between the client identifier and the client role, and comprises the following steps: in response to receiving the connection request, the client role management module records a mapping relationship of the client identity and the client role.

In an implementation manner provided in the first aspect, the master device further includes a device management service, where the device management service includes a sensing module, and when detecting that a state of the first device changes, the master device generates a state change notification, and specifically includes: if the state of the first device is detected to change, the sensing module generates a state change notification, wherein the state change notification comprises the device identifier of the first device.

In an implementation manner provided in the first aspect, the device management service further includes a device management module, a client role management module, and a notification module, and the method further includes: the sensing module sends a state change notification to the notification module; in response to receiving the state change notification, the perception module sends a request for acquiring the equipment role to the equipment management module, wherein the request for acquiring the equipment role carries the equipment identifier of the first equipment; the device management module acquires the device role of the first device according to the device identifier of the first device; the device management module sends the device role of the first device to the notification module; the notification module sends a request for acquiring an application set to the client role management module, wherein the request for acquiring the application set carries the equipment role of the first equipment; in response to receiving a request for acquiring an application set, the role management module takes an application, of which the client roles are matched with the device roles of the first device, in the plurality of applications as a target application; the role management module sends an application collection set to the notification module, wherein the application collection set comprises a target application; the notification module sends a state change notification to the target application.

In an implementation manner provided in the first aspect, the device role and the client role both include a super terminal device and an internet of things device.

In a second aspect, the present application provides an electronic device, including: a wireless communication module, a memory, and one or more processors; the wireless communication module and the memory are coupled with the processor; wherein the memory is for storing computer program code, the computer program code comprising computer instructions; the computer instructions, when executed by a processor, cause an electronic device to perform a method as in any of the embodiments of the first aspect.

In a third aspect, the present application provides a computer-readable storage medium comprising computer instructions; when executed on an electronic device, the computer instructions cause the electronic device to perform a method as in any of the embodiments of the first aspect.

In a fourth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any of the first aspects described above.

In a fifth aspect, an apparatus (e.g., the apparatus may be a chip system) is provided, where the apparatus includes a processor configured to support a first device to implement the functions referred to in the first aspect, e.g., obtain information about a first transmission delay corresponding to a transmission of a message related to a terminal between the first device and a second device. In one possible design, the apparatus further includes a memory for holding program instructions and data necessary for the first device. When the device is a chip system, the device can be formed by a chip, and can also comprise the chip and other discrete devices.

The technical effects of any one of the design manners of the fourth aspect to the fifth aspect may be referred to the technical effects of the different design manners of the first aspect, and will not be repeated here.

Drawings

Fig. 1 is a schematic structural diagram of a collaboration system according to an embodiment of the present application;

Fig. 2 is a schematic structural diagram of a mobile phone 200 according to an embodiment of the present application;

fig. 3 is a schematic software structure diagram of a mobile phone 200 according to an embodiment of the present application;

FIG. 4 is a schematic diagram showing interactions between software modules of a method for collaborative effort provided by an embodiment of the present application;

FIG. 5 is a schematic diagram showing interactions between software modules of a method for collaborative effort provided by an embodiment of the present application;

FIG. 6 is a schematic diagram showing interactions between another software module of a method for collaborative work provided by an embodiment of the present application;

FIG. 7 is a flowchart showing a method for collaborative work according to an embodiment of the present application;

FIG. 8 is a second flowchart of a method for collaborative work according to an embodiment of the present application;

FIG. 9 is a flowchart III of a method for collaborative work provided by an embodiment of the present application;

Fig. 10 is a schematic structural diagram of a chip system according to an embodiment of the present application.

Detailed Description

The terms "first" and "second" are used below for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the present embodiment, unless otherwise specified, the meaning of "plurality" is two or more.

In the prior art, a master device may respond to a user initiated collaborative task and then assign the collaborative task to a slave device within the system for execution. In practical application, when the master device allocates a cooperative task, it is required to acquire a device list including all the slave devices and then select one slave device from the device list to allocate the cooperative task to the master device. However, not every slave device in the device list may perform the cooperative task, that is, the slave devices in the device list having the cooperative task and not requiring the cooperative task, resulting in a inefficiency in the master device allocating the cooperative task.

The collaborative tasks may include two types of collaborative tasks, namely, a collaborative task with strong interactivity and a collaborative task with weak interactivity, according to service requirements satisfied by the collaborative tasks. For example, when the collaborative task is a collaborative play task, the business requirement is only to play audio, video or pictures, and the whole process has less interaction with the user. For another example, when the collaborative task is a collaborative call task, the service requirement that the collaborative task meets is a call, and the whole process has more interaction with the user. And the two different types of cooperative tasks, the required devices are not the same. Specifically, a more interactive collaborative task typically requires a more interactive device (e.g., a cell phone, tablet, computer, etc.), and a less interactive collaborative task typically requires a less interactive device (e.g., headphones, air conditioner, audio, etc.).

It can be seen that in the prior art, there is a problem that the device list includes the slave devices that are not required by the cooperative task, so that the efficiency of allocating the cooperative task by the master device is low.

The application provides a collaborative work method, when receiving the operation of a user for initiating a collaborative task by using a first application, the collaborative task can be decomposed into a plurality of subtasks, equipment which can meet the business requirement of the first application is screened out from all equipment according to the client role of the first application, and the equipment is selected to distribute the subtasks. Therefore, the equipment acquired by the first application only comprises the equipment capable of meeting the service requirement, so that the interference of the equipment which is not required by the first application to the task distribution process of the first application is reduced, and the distribution efficiency is improved.

The roles of the client are used for reflecting roles played by the first application when the first application meets the service requirement of the user, and can comprise two types of super terminal equipment and IOT equipment, wherein the super terminal equipment can refer to terminal equipment with relatively high use frequency and rich interaction modes, such as mobile phones, tablet computers, intelligent bracelets, intelligent screens and the like. IOT devices may refer to relatively low frequency, relatively single interactive terminal devices such as wireless headphones, bluetooth speakers, routers, etc.

Fig. 1 is a schematic diagram of a collaboration system according to an embodiment of the present application. The collaboration system may include a master device and one or more slave devices. The master device and the one or more slave devices may communicate through wireless fidelity (WIRELESS FIDELITY, WIFI), bluetooth, near field communication (NEAR FIELD communication, NFC), and other communication modes. The host device may have installed thereon a first application, such as a telephony application, a video application, etc., that may initiate a collaborative task.

In the embodiment of the present application, the devices (including the master device and the slave device) may be a mobile phone, a smart phone, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA), a tablet computer, a wearable device (for example, a watch, a bracelet), a sound box, a camera, a large screen, and devices capable of implementing mutual communication of the devices, and so on.

The embodiment of the present application will be described by taking the device (master device, slave device) shown in fig. 1 as a mobile phone 200 as an example. As shown in fig. 2, the mobile phone 200 may include A processor 210, an external memory interface 220, an internal memory 221, A universal serial bus (universal serial bus, USB) interface 230, A charge management module 240, A power management module 241, A battery 242, an antenna 1, an antenna 2, A mobile communication module 250, A wireless communication module 260, an audio module 270, A speaker 270A, A receiver 270B, A microphone 270C, an earphone interface 270D, A sensor module 280, keys 290, A motor 291, an indicator 292, A camera 293, A display (touch screen) 294, A subscriber identity module (subscriber identification module, SIM) card interface 295, and the like.

The sensor module 280 may include pressure sensors, gyroscope sensors, barometric pressure sensors, magnetic sensors, acceleration sensors, distance sensors, proximity sensors, fingerprint sensors, temperature sensors, touch sensors, ambient light sensors, bone conduction sensors, and the like.

It is to be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic apparatus 200. In other embodiments, the electronic device 200 may include more or fewer components than shown, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 210 may include one or more processing units such as, for example: processor 210 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (IMAGE SIGNAL processor, ISP), a controller, a memory, a video codec, a digital signal processor (DIGITAL SIGNAL processor, DSP), a baseband processor, and/or a neural Network Processor (NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller may be a neural hub and command center of the electronic device 200. The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 210 for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory. The memory may hold instructions or data that the processor 210 has just used or recycled. If the processor 210 needs to reuse the instruction or data, it may be called directly from the memory. Repeated accesses are avoided and the latency of the processor 210 is reduced, thereby improving the efficiency of the system.

In some embodiments, processor 210 may include one or more interfaces. The interfaces may include an integrated circuit (inter-INTEGRATED CIRCUIT, I2C) interface, an integrated circuit built-in audio (inter-INTEGRATED CIRCUIT SOUND, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, among others.

It should be understood that the connection relationship between the modules illustrated in this embodiment is only illustrative, and does not limit the structure of the electronic device 200. In other embodiments, the electronic device 200 may also employ different interfaces in the above embodiments, or a combination of interfaces.

The charge management module 240 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger. The charging management module 240 may also provide power to the electronic device through the power management module 241 while charging the battery 242.

The power management module 241 is used for connecting the battery 242, and the charge management module 240 and the processor 210. The power management module 241 receives input from the battery 242 and/or the charge management module 240 and provides power to the processor 210, the internal memory 221, the external memory, the display 294, the camera 293, the wireless communication module 260, and the like. In some embodiments, the power management module 241 and the charge management module 240 may also be provided in the same device.

The wireless communication function of the electronic device 200 can be implemented by the antenna 1, the antenna 2, the mobile communication module 250, the wireless communication module 260, a modem processor, a baseband processor, and the like. In some embodiments, antenna 1 and mobile communication module 250 of electronic device 200 are coupled, and antenna 2 and wireless communication module 260 are coupled, such that electronic device 200 may communicate with a network and other devices via wireless communication techniques.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 200 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example, the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 250 may provide a solution for wireless communication including 2G/3G/4G/5G, etc., applied on the electronic device 200. The mobile communication module 250 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), or the like. The mobile communication module 250 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation.

The mobile communication module 250 can amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate. In some embodiments, at least some of the functional modules of the mobile communication module 250 may be disposed in the processor 210. In some embodiments, at least some of the functional modules of the mobile communication module 250 may be provided in the same device as at least some of the modules of the processor 210.

The wireless communication module 260 may provide solutions for wireless communication including WLAN (e.g., wireless fidelity (WIRELESS FIDELITY, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation SATELLITE SYSTEM, GNSS), frequency modulation (frequency modulation, FM), near field communication (NEAR FIELD communication, NFC), infrared (IR), etc., applied on the electronic device 200.

The wireless communication module 260 may be one or more devices that integrate at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 210. The wireless communication module 260 may also receive a signal to be transmitted from the processor 210, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 2.

The electronic device 200 implements display functions through a GPU, a display screen 294, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display screen 294 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 210 may include one or more GPUs that execute program instructions to generate or change display information.

The display 294 is used to display images, videos, and the like. The display 294 includes a display panel.

The electronic device 200 may implement a photographing function through an ISP, a camera 293, a video codec, a GPU, a display 294, an application processor, and the like. The ISP is used to process the data fed back by the camera 293. The camera 293 is used to capture still images or video. In some embodiments, the electronic device 200 may include 1 or N cameras 293, N being a positive integer greater than 1.

The external memory interface 220 may be used to connect an external memory card, such as a Micro SD card, to enable expansion of the memory capabilities of the electronic device 200. The external memory card communicates with the processor 210 through an external memory interface 220 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.

Internal memory 221 may be used to store computer executable program code that includes instructions. The processor 210 executes various functional applications of the electronic device 200 and data processing by executing instructions stored in the internal memory 221. For example, in an embodiment of the present application, the processor 210 may include a memory program area and a memory data area by executing instructions stored in the internal memory 221.

The storage program area may store an application program (such as a sound playing function, a service preemption function, etc.) required for at least one function of the operating system, etc. The storage data area may store data created during use of the electronic device 200 (e.g., audio data, phonebook, etc.), and so on. In addition, the internal memory 221 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like.

The electronic device 200 may implement audio functions through an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, an ear-headphone interface 270D, an application processor, and the like. Such as music playing, recording, etc.

Keys 290 include a power on key, a volume key, etc. The keys 290 may be mechanical keys. Or may be a touch key. The motor 291 may generate a vibration alert. The motor 291 may be used for incoming call vibration alerting or for touch vibration feedback. The indicator 292 may be an indicator light, which may be used to indicate a state of charge, a change in power, a message indicating a missed call, a notification, etc. The SIM card interface 295 is for interfacing with a SIM card. The SIM card may be inserted into the SIM card interface 295 or removed from the SIM card interface 295 to enable contact and separation from the electronic device 200. The electronic device 200 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 295 may support Nano SIM cards, micro SIM cards, and the like.

The software system of the mobile phone 200 may employ a layered architecture, an event driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the application, taking an Android system with a layered architecture as an example, a software structure of the mobile phone 200 is illustrated.

The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate via interfaces. In some embodiments, the Android system may include an application layer, an application framework layer, an Zhuoyun rows (Android runtime) and system libraries, and a kernel layer. It should be noted that, in the embodiment of the present application, an Android system is illustrated, and in other operating systems (such as a hong mo system, an IOS system, etc.), the scheme of the present application can be implemented as long as the functions implemented by the respective functional modules are similar to those implemented by the embodiment of the present application.

The application layer may include a series of application packages, among other things.

As shown in fig. 3, the application layer may include applications of cameras, phone calls, bluetooth, music, video, short messages, settings, first applications, etc. Of course, the application layer may also include other application programs, such as a payment application, a shopping application, a banking application, a chat application, or a financial application, etc., which are not limited by the present application. The first application may be any application that may initiate a cooperative task, and is not specifically limited herein.

The application framework layer provides an application programming interface (application programming interface, API) and programming framework for the application of the application layer. The application framework layer includes a number of predefined functions. For example, a process manager, a telephone manager, a notification manager, a device management service, etc., to which embodiments of the application are not limited in any way.

Wherein the process manager is used to create, suspend processes and threads.

The telephony manager is used to provide the communication functions of the handset 200. Such as the management of call status (including on, hung-up, etc.).

The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, a text message is prompted in a status bar, a prompt tone is emitted, the electronic device vibrates, and an indicator light blinks, etc.

The device management service may be used to manage devices connected to the handset 200. The device management service may include a control center module, a client role management module, a device management module, a notification module, a perception module, and the like. Wherein the function of the modules is described below.

The system library may include a plurality of functional modules. For example: surface manager (surface manager), media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., openGL ES), two-dimensional graphics processing Libraries (e.g., SGL), etc.

The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.

Media libraries support a variety of commonly used audio, video format playback and recording, still image files, and the like. The media library may support a variety of audio video encoding formats, such as: MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc.

OpenGL ES is used to implement three-dimensional graphics drawing, image rendering, compositing, and layer processing, among others.

SGL is the drawing engine for 2D drawing.

Android Runtime (Android run) includes a core library and virtual machines. Android runtime is responsible for scheduling and management of the android system. The core library consists of two parts: one part is a function which needs to be called by java language, and the other part is a core library of android. The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver, a sensor driver and a Bluetooth driver.

The hardware layer includes a display, a camera, a speaker (which may also be referred to as a speaker), a bluetooth module, and the like. The Bluetooth module can comprise a hardware unit for realizing Bluetooth connection and data interaction: a Radio frequency unit (Radio), a baseband or link control unit (link controller), a link management unit (LINK MANAGER), and the like. The wireless radio frequency unit is used for realizing the transmission/reception of data and voice; the link management unit is used for carrying out the mutual conversion between the radio frequency signal and the digital or voice signal and realizing the baseband protocol and other bottom layer connection regulations; the link management unit is responsible for managing communication between Bluetooth devices and realizing operations such as link establishment, verification, link configuration and the like.

The method of co-operation provided by the present application will be described in the following three sections with reference to the accompanying drawings.

(1) The first application may connect to the device management service before the first application initiates the collaborative task. The first application is connected to the device management service, which may be understood as allocating a client identifier (client ID) and a client role to the first application, and recording, by the device management service, a mapping relationship between the client identifier and the client role.

(2) When the first application initiates a collaborative task, a request to obtain available device information may be initiated to a device management service. The device management service screens the devices which can meet the service requirement of the first application from all the available devices according to the client roles of the first application, and device filtering is realized.

(3) The device management service may sense a state change of the second device, screen an application focusing on the device role from the client set according to the device role of the second device, and send a state change notification to the screened application. Device filtering can be realized as well, and interference of irrelevant information to application is reduced.

The software modules and interactions between the modules involved in the collaborative method provided by the embodiments of the present application are described below.

FIG. 4 shows a schematic diagram of interactions between software modules during a first application connection device management service. As shown in fig. 4, a first application in the application layer may interact with the device management SDK, which may assign a client identification and a client role to the first application. Wherein the client identification is a unique identifier of the first application. The device management SDK may also interact with the device management services in the framework layer by calling a preset application program interface (application programming interface, API) interface. The device management service may include a control center module and a client role management module. The device management SDK can transfer the client identifier and the client role of the first application to the control center module by calling a preset API. The control center module can transmit the client identification and the client role of the first application to the client role management module, and the client role management module stores and manages the mapping relation between the client identification and the client role of each application (including the first application).

FIG. 5 illustrates interactions between software modules during the process of a first application obtaining available device information. As shown in fig. 5, the first application in the application layer may also call the device management SDK to obtain the available device information. The device management SDK may interact with a control center module of the device management service by invoking a preset APK interface to transfer a request to the control center module to acquire the device. The device management service also comprises a device management module. The control center module may forward a request to acquire a device to the device management module. After receiving the request for acquiring the devices, the device management module may acquire all the devices and feed back a device list including all the devices to the control center module. The control center module can interact with the client role management module, the client role management module screens out the equipment types required by the first application from the equipment list according to the client identification of the first application to obtain available equipment information, and the control center module sends the available equipment information to the first application through the equipment management SDK.

FIG. 6 shows a schematic diagram of interactions between software modules after a change in device state is perceived. As shown in fig. 6, the device management service further includes a sensing module and a notification module. The sensing module may send a state change notification to the notification module when a change in the state of the target device is sensed. The notification module may interact with the device acquisition module to acquire the device role of the target device and then transmit the device role of the target device to the client role management module. The client role management module may obtain an application set from all clients (i.e., applications) focusing on the role of the target device according to the device role of the target device. The notification module may send the state change notification to all applications within the set of clients. If the application set includes the first application, the notification module may send the state change notification to the first application through the device management SDK.

For easy understanding, the method provided by the embodiment of the application is specifically described below by taking the device as an example of a mobile phone with reference to the accompanying drawings.

As shown in fig. 7, a flowchart of a method for cooperative work provided in an embodiment of the present application is shown, and the method for cooperative work may be applied to the master device in fig. 1. Fig. 7 specifically illustrates a process of the first application connecting to the device management service. The method of cooperative work may include S101 to S109.

S101, a first application calls a device management SDK creation client.

Upon detecting an operation (which may be referred to as a second operation) by which the user opens the first application, the first application invokes the device management SDK creation client. The first application is an application capable of initiating a cooperative task. Collaborative tasks refer to tasks that need to be completed in concert by one or more devices.

For example, the first application may be a super incoming call application, and the user may use the super incoming call application to implement collaborative answering and dialing through two devices (e.g., a mobile phone and a tablet), that is, the super incoming call application may initiate a collaborative call task. For example, the mobile phone and the tablet are both provided with super incoming call applications, and when the mobile phone receives an incoming call, the first application can initiate a collaborative call task and distribute the collaborative call task to the tablet, so that a user can answer the incoming call through the tablet.

S102, the device management SDK distributes client identification and client roles to the first application.

Wherein the client identification is a unique identifier of the first application for identifying the first application. The roles of the client are used to reflect the roles that the first application plays when meeting the service requirements of the user, and may include two classes of super terminal devices (e.g., may correspond to the identifier ST) and IOT devices (e.g., may correspond to the identifier IOT). The super terminal device can refer to terminal devices with relatively high use frequency and rich interaction modes, such as mobile phones, tablet computers, smart bracelets, smart screens and the like. IOT devices may refer to relatively low frequency, relatively single interactive terminal devices such as wireless headphones, bluetooth speakers, routers, etc.

It should be noted that, the client role is related to the service requirement satisfied by the first application, for example, the service requirement satisfied by the first application is a collaboration session, and the client role of the first application may be a super terminal; for another example, if the service requirement satisfied by the first application is to cooperatively play music, video, etc., the client role of the first application may be IOT device; for another example, if the service requirement satisfied by the first application is to control the IOT device (e.g., a television) to turn on, turn off, adjust the volume of the IOT device, etc., the client role of the first application is IOT device.

Alternatively, the handset may include a plurality of different first applications thereon, which may have different client roles. That is, one device may have two different client roles depending on the traffic scenario.

In an alternative embodiment, each application and its corresponding client role may be pre-stored in the device management SDK. After receiving the request of creating the client by the first application, a corresponding client role can be allocated to the first application according to the pre-stored corresponding relationship.

S103, the first application calls the equipment management SDK to connect with the control center module.

Meanwhile, the first application can register a callback with the device management SDK, and when the device management SDK obtains a connection result after registering the action of the callback, the connection result can be returned to the first application.

S104, the equipment management SDK sends a connection request to the control center module.

The connection request carries a client identifier and a client role of the first application.

For example, the client identifier carried in the connection request may be a01, and the client role may be ST (i.e., super terminal device).

S105, the control center module sends a connection request to the client role management module.

S106, the client role management module records the mapping relation between the client identification of the first application and the client role of the first application.

After receiving the connection request, the client role management module may record a mapping relationship between the client identifier of the first application and the client role of the first application. The mapping may, for example, exist in the form of a mapping table (e.g., table 1).

As shown in table 1, the client identifier of the application 1 is a01, and the client role thereof is ST (i.e., super terminal device); the client of application 2 is identified as a02, and its client role is IOT (i.e., IOT device); the client of application 3 is identified as B01 and its client role is ST (i.e. superterminal device).

TABLE 1

Application of	Client identifier (client ID)	Client role (client role)
			Application 1	A01	ST
Application 2	A02	IOT
			Application 3	B01	ST
……	……	……

It should be noted that table 1 is only an example, and the mapping relation table may further include more or less contents than those shown in table 1.

S107, the client role management module sends a connection result to the control center module.

It can be understood that after the client role management module records the mapping relationship between the client identifier of the first application and the client role of the first application, it indicates that the first application has successfully connected to the device management service, and then the first application can obtain the available device information through the device management service.

S108, the control center module sends a connection result to the equipment management SDK.

S109, the device management SDK sends a connection result to the first application.

Through S101-S109, the master device can allocate a client identifier and a client role to the first application, record a mapping relationship between the client identifier and the client role, and facilitate subsequent device filtering by using the mapping relationship.

After the first application is connected with the device management service, available device information can be actively obtained from the device management service, wherein the available device information comprises a plurality of available devices meeting the first application requirement and corresponding device information, so that the first application can select target devices from the plurality of available devices meeting the first application requirement to execute tasks.

As shown in fig. 8, a second flowchart of a cooperative method according to an embodiment of the present application is provided, and the cooperative method may be applied to the master device in fig. 1. Fig. 8 specifically illustrates a first application acquiring available device information procedure. The method of cooperative work may include S201 to S210.

S201, the first application calls a device management SDK to acquire available device information.

When a first operation of a user on a first application is detected, the first application calls a device management SDK to acquire available device information. The first operation of the user on the first application may be an operation for enabling the first application to initiate a collaborative task, which may specifically relate to a specific usage scenario of the first application, and is not limited herein. For example, if the first application is a video application, the first operation of the first application by the user may include an operation of the user clicking a screen-drop control in the first application; if the first application is a telephony application, the first operation of the first application by the user may include an operation of the user to enter a telephone number in the first application and click a dial control.

Optionally, when the first application receives the service notification, the device management SDK may be called to obtain the available device information. It will be appreciated that in some scenarios the handset may actively initiate a collaborative task. For example, the first application is a call application, and when the call application receives an incoming call notification, the device management SDK may be actively invoked to obtain available device information, so as to select a target device from the available device information, and flow the information to the target device, so that a user may answer an incoming call through the target device.

Meanwhile, the first application may register a callback with the device management SDK, where the function of registering the callback is that the available device information may be returned to the first application after the device management SDK obtains the available device information.

When detecting a first operation of the user on the first application, the first application may further generate a collaborative task according to the first operation, and decompose the collaborative task into a plurality of subtasks, so as to perform task allocation after obtaining the available device information.

S202, the device management SDK sends a request for acquiring available device information to the control center module.

The request for acquiring the available equipment information carries a client identifier and a client role of the first application.

Regarding the client identifier of the first application and the relevant content of the client role, refer to S104, which is not described herein.

S203, the control center module sends a request for acquiring the available equipment information to the equipment management module.

S204, the device management module acquires a device list.

The device list includes device information of a plurality of devices. The plurality of devices are all terminal devices capable of communicating with the mobile phone. The device information for each device may include a device identification of the device as well as a device role. Wherein the device identification is a unique identifier of the device for identifying the device. The device roles of the device may refer to roles that the device plays in various business scenarios, and may include two classes of superordinate devices (e.g., may correspond to identification ST) and IOT devices (e.g., may correspond to identification IOT). Wherein the roles played by a device under different traffic scenarios may be different, i.e. a device may have multiple device roles. For example, in a screen-throwing scene, the large-screen device only plays audio, video and the like, and the device role is IOT (i.e., IOT device); in the video call scene, the large screen device can interact with the user, so that the user can carry out video call through the large screen device, and the device role of the large screen device in the service scene is ST (i.e. super terminal device). The list of devices may be as shown in table 2, for example.

TABLE 2

Apparatus and method for controlling the operation of a device	Device identification	Device role
			Apparatus 1	A03	ST、IOT
Device 2	A04	IOT
			Device 3	B05	ST
……	……	……

As shown in table 2, where the device identifier of device 1 is a03, its device role includes ST (i.e., superterminal device) and IOT (i.e., IOT device); device 2 has a device identifier of a04, whose device role includes IOT (i.e., IOT device); the device 3 has a device identifier B05, and its device role includes ST (i.e., super terminal device).

S205, the device management module sends the device list to the control center module.

The description of the device list is referred to S204, and is not repeated here.

S206, the control center module sends the device list and the client identification of the first application to the client role management module.

S207, the client role management module screens available devices from the device list based on the client identification of the first application.

It should be noted that, in a service scenario, a first application capable of meeting a strong interaction requirement of a user, where a target device selected by the first application is a device with strong interactivity; only the first application, which can meet the requirement of less interaction of the user, selects the target device which is also the device with weaker interaction. In other words, the roles played by the first application and the target device selected by the first application should be the same, e.g. both super terminal devices or both IOT devices. For example, if the first application needs to meet the requirement of user cooperative communication, the selected target device needs to interact with the user to make the user communicate, and the client role of the first application and the device role of the target device are both super terminal devices. For another example, if the first application needs to meet the requirement of the user for controlling the smart home, the target device selected by the first application does not need to interact with the user, and the client role of the first application and the device role of the target device are IOT devices.

Specifically, the client role management module may first query in a mapping relationship table (e.g. table 1) according to the client identifier of the first application, to determine the client role of the first application. Then, the device which plays the same role as the first application is inquired in the device list, and the device which plays the same role as the first application is used as an available device.

Illustratively, if the client identifier of the first application is a01, it can be queried that the client role of the first application is ST (i.e. the super terminal device) according to table 1. The client role management module may query from table 2 that the device roles of device 1 and device 2 include ST (i.e., super terminal device), and the client role management module regards device 1 and device 2 as available devices.

Optionally, the client role management module may be set according to a requirement of a user, for example, the first application may also pay attention to devices of all device roles, where in this case, the available devices obtained by screening by the client role management module are all devices in the device list.

S208, the client role management module sends available device information to the control center module.

The available device information may carry device identification, current status, etc. information for all available devices.

S209, the control center module sends available device information to the device management SDK.

S210, the device management SDK sends available device information to the first application.

After receiving the available device information, the first application may determine a device for executing each subtask from the available devices, and send a plurality of subtasks to the corresponding devices for executing.

It can be seen that when the first application initiates the cooperative task, the device provided by the application can screen available devices (i.e. devices meeting the service requirement of the first application) from all devices according to the client role of the first application. Therefore, the finally obtained available equipment information only comprises equipment meeting the first application requirement, so that the interference of other irrelevant equipment on the follow-up relevant operation according to the available equipment information can be reduced, and the efficiency of the processing process is improved; but also can reduce the information quantity transmitted in the transmission process and improve the transmission efficiency.

After the first application distributes the cooperative task to the target device, if the running state of the target device changes, a change notification can be sent to each application focusing on the type of the target device on the mobile phone.

As shown in fig. 9, a flowchart of a cooperative method provided in an embodiment of the present application is shown, and the cooperative method may be applied to the master device in fig. 1. The method of co-operation may include S301-308.

S301, the sensing module sends a state change notification to the notification module.

Specifically, when detecting that the state of the target device changes, the sensing module sends a state change notification to the notification module. For example, the target device is executing a screen-throwing task sent by the mobile phone, and when the target device terminates the screen throwing, the current state information can be sent to the sensing module. The sensing module can compare the current state and the historical state of the target device, and determine that the state of the target device changes, so that a state change notification is sent to the notification module. For another example, the target device is executing a collaborative call task sent by the mobile phone, and when the target device ends the call, the current state information may be sent to the awareness module. The sensing module can compare the current state and the historical state of the target device, and determine that the state of the target device changes, so that a state change notification is sent to the notification module.

The state change notification may carry the device identifier of the target device, the current state information, and the like, and is not particularly limited herein.

S302, the notification module sends a request for acquiring the device role to the device management module.

The request for acquiring the device role may carry the device identifier of the target device, and be used for acquiring the device role of the target device.

S303, the device management module acquires the device role of the target device.

Specifically, the device management module may query the device list for the device role of the target device according to the device identifier of the target device. Illustratively, if the device identifier of the target device may be a04, a device role of the target device (i.e., IOT device) may be queried according to table 2.

S304, the device management module sends the device role of the target device to the notification module.

S305, the notification module sends a request for acquiring the application set to the client role management module.

The request for acquiring the application set may carry a device role of the target device.

S306, the client role management module screens to obtain an application set.

Specifically, the client role management module may query the mapping table for an application that plays the same role as the target device, and add it to the application set. Illustratively, if the device role of the target device is IOT (i.e., IOT device), the client role management module queries according to table 1 to add application 2 whose client role is IOT (i.e., IOT device) to the application set. For another example, if the device role of the target device is ST (i.e., the super terminal device), the client role management module may query according to table 1, and add the application 1 and the application 3 whose client roles are ST (i.e., the super terminal device) to the application set.

S307, the client role management module sends the application set to the notification module.

S308, the notification module sends a state change notification to all applications in the application set.

It will be appreciated that for applications that do not focus on the device role to which the target device corresponds, no notification of a state change is received. That is, the application may not process the state change notification of the device corresponding to the device role that is not of interest, so as to achieve the purpose of filtering the message.

Optionally, after the notification module obtains the application set, the notification module may further filter according to a subscription condition of each application to the running state. The subscription condition of the application to the running state may refer to that the application may subscribe to a request for a certain type of state change from the notification module, and when the notification module detects the type of state change, the notification module may send a state change notification to the corresponding application. For example, application a assigns a screen-casting task to a large screen device and subscribes to the notification module for a request for termination of the screen-casting task. In this way, when the notification module receives the running state information indicating termination of the screen-casting task, a state change notification may be sent to the application a. If the notification module receives the running state information indicating that the playing source is switched in the screen throwing process, the notification module does not need to send a state change notification to the application a because the application a is not subscribed to the state change.

In summary, the method for collaborative work provided in the embodiment of the present application is applied to a terminal device, and can allocate a client identifier and a client role to a first application before the first application initiates a collaborative task, and record a mapping relationship between the client identifier and the client role. After the first application initiates the collaborative task, the equipment which can meet the first application requirement is screened from all the available equipment according to the client role of the first application, so that the terminal equipment can conveniently select target equipment from the equipment which meets the first application requirement to execute the collaborative task. Because available equipment is screened, the interference of equipment which is not required by the first application on the task allocation process of the first application can be reduced, and the allocation efficiency is improved. In the process of executing the task by the target equipment, the terminal equipment can sense the state change of the target equipment, screen out the application focusing on the state change of the target equipment from all the applications, and send a change notification to the application focusing on the state change of the target equipment. In the whole process, only the application focusing on the type of the target equipment can sense the state change, so that the purpose of filtering the message is achieved.

Embodiments of the present application also provide a system-on-a-chip (SoC) including at least one processor 1001 and at least one interface circuit 1002, as shown in fig. 10. The processor 1001 and the interface circuit 1002 may be interconnected by wires. For example, interface circuit 1002 may be used to receive signals from other devices (e.g., a memory of an electronic apparatus). For another example, the interface circuit 1002 may be used to send signals to other devices (e.g., the processor 1001 or a touch screen of an electronic apparatus). The interface circuit 1002 may, for example, read instructions stored in a memory and send the instructions to the processor 1001. The instructions, when executed by the processor 1001, may cause the electronic device to perform the various steps of the embodiments described above. Of course, the system-on-chip may also include other discrete devices, which are not particularly limited in accordance with embodiments of the present application.

Embodiments of the present application also provide a computer readable storage medium, where the computer readable storage medium includes computer instructions, which when executed on an electronic device, cause the electronic device to perform the functions or steps performed by the electronic device in the method embodiments described above.

The embodiment of the application also provides a computer program product, which when run on an electronic device, causes the electronic device to execute the functions or steps executed by the electronic device in the above-mentioned method embodiment.

It will be apparent to those skilled in the art from this description that, for convenience and brevity of description, only the above-described division of the functional modules is illustrated, and in practical application, the above-described functional allocation may be performed by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to perform all or part of the functions described above.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical functional division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another apparatus, 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 an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and the parts displayed as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed in a plurality of different places. 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 the embodiments 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 readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or a part contributing to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several instructions for causing a device (may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of specific embodiments of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present application should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of co-operating, for use in a co-operating system comprising a master device and one or more slave devices, the master device comprising a first application, the master device storing device information for the one or more slave devices, the device information comprising a device identity and a device role, the method comprising:

the main equipment receives a first operation of a user on the first application, generates a cooperative task according to the first operation, and decomposes the cooperative task into a plurality of subtasks;

The master device screens available devices from the one or more slave devices according to the client roles of the first application, the device roles of the available devices are matched with the client roles of the first application, and when the device roles of the available devices are identical or partially identical to the client roles of the first application, the device roles of the available devices are matched with the client roles of the first application;

The master device determining a device from the available devices that performs each subtask;

and the main equipment sends the plurality of subtasks to corresponding equipment for execution.

2. The method according to claim 1, wherein the method further comprises:

the master device receives a second operation of a user on the first application, and distributes a client identifier and a client role to the first application;

And the master device records the mapping relation between the client identifier and the client role.

3. The method according to claim 1, wherein the method further comprises:

When detecting that the state of the first device changes, the master device generates a state change notification, wherein the state change notification is used for notifying a target application that the state of the first device changes, the first device is any device executing subtasks, a client role of the target application is matched with a device role of the first device, and when the device role of the first device is identical or partially identical to the client role of the target application, the device role of the first device is matched with the client role of the target application.

4. A method according to claim 3, characterized in that the method further comprises:

and the master device screens the target application from a plurality of applications according to the device role of the first device.

5. The method of any of claims 1-4, wherein the host device further comprises a device management software development kit, SDK, and a device management service, the device management service comprising a control center module, the host device receiving a first operation of the first application by a user, the method further comprising:

the first application calls the equipment management SDK to acquire available equipment information;

The device management SDK sends a request for obtaining available device information to the control center module, where the request for obtaining available device information includes a client identifier of the first application.

6. The method according to claim 5, wherein the device management service further includes a client role management module and a device management module, and the master device screens available devices from the one or more slave devices according to the client role of the first application, specifically including:

the control center module sends the request for acquiring the available equipment information to the equipment management module;

in response to receiving the request to obtain available device information, the device management module obtains a device list including the one or more slave devices and device information for each slave device;

The device management module sends the device list to the control center module;

the control center module sends the equipment list and the client identification of the first application to the client role management module;

And the client role management module obtains the client role of the first application based on the client identification query of the first application, and takes the equipment with the equipment role matched with the client role of the first application in the equipment list as available equipment.

7. The method of claim 6, wherein the method further comprises:

the client role management module sends available equipment information to the control center module, wherein the available equipment information comprises the available equipment;

the control center module sends the available equipment information to the equipment management SDK;

the device management SDK sends the available device information to the first application.

8. The method of claim 2, wherein the master device further comprises a device management SDK, and wherein the master device receives the second operation of the first application from the user, the method further comprising:

the first application calls the equipment management SDK creation client;

The assigning the client identifier and the client role to the first application includes:

the device management SDK assigns a client identifier and the client role to the first application.

9. The method of claim 8, wherein the master device further comprises a device management service comprising a control center module and a client role management module, the method further comprising:

the first application calls the equipment management SDK to connect with the control center module;

The equipment management SDK sends a connection request to the control center module, wherein the connection request comprises a client identifier and a client role of the first application;

The control center module sends the connection request to the client role management module;

the master device records the mapping relation between the client identifier and the client role, and the mapping relation comprises the following steps:

And responding to the received connection request, and recording the mapping relation between the client identification and the client role by the client role management module.

10. The method according to claim 3, wherein the master device further comprises a device management service, the device management service comprises a perception module, and the master device generates a state change notification when detecting that the state of the first device changes, specifically comprising:

and if the state of the first equipment is detected to be changed, the perception module generates a state change notification, wherein the state change notification comprises the equipment identifier of the first equipment.

11. The method of claim 10, wherein the device management service further comprises a device management module, a client role management module, and a notification module, the method further comprising:

The perception module sends the state change notification to the notification module;

in response to receiving the state change notification, the perception module sends a request for acquiring the equipment role to the equipment management module, wherein the request for acquiring the equipment role carries the equipment identifier of the first equipment;

The device management module acquires the device role of the first device according to the device identifier of the first device;

the device management module sends the device role of the first device to the notification module;

The notification module sends a request for acquiring an application set to the client role management module, wherein the request for acquiring the application set carries the equipment role of the first equipment;

in response to receiving the request for acquiring the application set, the role management module takes an application, of which the client roles are matched with the device roles of the first device, in a plurality of applications as a target application;

The role management module sends an application collection to the notification module, wherein the application collection comprises the target application;

The notification module sends the state change notification to the target application.

12. The method of any of claims 1-4, wherein the device role and the client role each comprise a superterminal device and an internet of things device.

13. An electronic device, the electronic device comprising: a wireless communication module, a memory, and one or more processors; the wireless communication module, the memory, and the processor are coupled;

Wherein the memory is for storing computer program code, the computer program code comprising computer instructions; the computer instructions, when executed by the processor, cause the electronic device to perform the method of any of claims 1-12.

14. A computer-readable storage medium comprising computer instructions;

The computer instructions, when run on an electronic device, cause the electronic device to perform the method of any one of claims 1-12.