CN116679998A - Multi-device cooperative conflict processing method and electronic device - Google Patents

Abstract

The present application provides a multi-device cooperative conflict processing method and an electronic device, which are applied in the technical field of terminals. The method includes: acquiring business information of the first electronic device and business information of the second electronic device, and determining the first electronic device and the second electronic device according to the business information when the user performs system operations on the first electronic device and the second electronic device. The device combination for the device has a collaboration conflict. When there is a coordination conflict, it is determined that the equipment combination cannot perform coordinated services. The service information includes at least one of the name of the service supported by the device, the type of service scheduling, the ongoing collaborative service, or the type of device combination supported by the service. In this way, through the above-mentioned method, the collaboration services with collaboration conflicts are filtered out, so that the device collaboration services can normally establish a connection.

Description

Method and electronic device for multi-device cooperative conflict processing

technical field

The present application relates to the technical field of terminals, and in particular to a method for multi-device cooperative conflict handling and an electronic device.

Background technique

Multi-device coordination is a technology applied to multiple electronic devices. Using multi-device collaboration technology, two or more electronic devices can perform cross-system and cross-device collaboration to achieve resource sharing and collaborative operations.

With the improvement of users' demand for terminal technology, multi-device collaborative unified management has become the key to the development of collaborative technology. Multi-device collaborative unified management refers to the function that users can implement collaborative business establishment with different devices through a device control center interface. For example, the interface of the mobile device control center presents all other electronic devices that can establish a connection with the mobile device, namely device A, device B, and device C. Cooperating with device B and device C, it can also terminate the ongoing coordination service between device A and other devices.

However, in the process of establishing a collaborative service, there may be conflicts between multiple devices. business, resulting in multi-device collaboration services cannot be established normally.

Contents of the invention

The purpose of this application is to provide a method and electronic equipment for multi-device collaboration conflict handling, which are used to solve the problem of multi-device collaboration conflicts in the process of establishing a service based on multi-device collaboration and unified management, so that multi-device collaboration services can be established normally .

In a first aspect, the present application provides a method for multi-device cooperative conflict handling, which is applied to a first electronic device, and the method includes:

Obtain the service information of the first electronic device and the second electronic device, wherein the second electronic device is an electronic device capable of coordinating with the first electronic device, and the service information includes the service name supported by the device, service scheduling type, ongoing collaboration At least one of the types of business or equipment combinations supported by the business;

When the user performs cooperative operations on the first electronic device and the second electronic device, it is determined whether there is a coordination conflict in the device combination of the first electronic device and the second electronic device according to the business information of the devices. If there is a collaboration conflict, it is determined that the equipment combination cannot perform collaborative services. In this way, according to the service information, it is determined that there is a collaboration conflict in multi-device collaboration, and the collaboration service with the collaboration conflict is filtered out, so that the device combination can normally establish a service.

In a possible implementation manner, it is determined whether at least one electronic device in the device combination is performing the coordinated service according to the coordinated service being performed by the device. If there is at least one electronic device that is performing a coordinated service, it is determined whether the coordinated service that the electronic device is conducting can be scheduled according to the service scheduling type. If it cannot be scheduled, it means that there is coordination conflict in the device combination of the first electronic device and the second electronic device. In this way, services that cannot be scheduled are filtered out.

In a possible implementation, according to the name of the service supported by the device, it is determined that the first electronic device and the second electronic device do not support the same coordinated service, or according to the type of device combination supported by the service, it is determined that the same coordinated service does not belong to the device combination support business, that is, there is no business intersection between the first electronic device and the second electronic device, or there is a business intersection, but the business intersection does not satisfy the business supported by the combination of the first electronic device and the second electronic device, indicating that the first electronic device There is a synergy conflict with the device combination of the second electronic device. In this way, services with no service intersection in the equipment combination or services whose service intersection does not match the services supported by the equipment combination are filtered out.

In a possible implementation, when the coordinated service being performed by the first electronic device and the coordinated service being performed by the second electronic device can be invoked, the first electronic device and the second electronic device are determined according to the name of the service supported by the device Do not support the same collaborative service, or determine that the same collaborative service does not belong to the service supported by the device combination according to the type of equipment combination supported by the service, that is, there is no business intersection between the first electronic device and the second electronic device, or there is a business intersection, but the business The intersection does not satisfy the services supported by the device combination of the first electronic device and the second electronic device, which means that there is a coordination conflict in the device combination of the first electronic device and the second electronic device. In this way, the services that can be scheduled when the coordinated services of the equipment in the equipment combination are being scheduled, but the equipment combination does not have a service intersection or the service intersection does not match the services supported by the equipment combination.

In a possible implementation manner, when it is determined that there is no coordination conflict in the device combination of the first electronic device and the second electronic device, based on a preset service priority rule, the device combination is triggered to perform a coordinated operation of the first service.

In a possible implementation manner, when there is a cooperative operation service record in the device combination of the first electronic device and the second electronic device, the collaborative service corresponding to the nearest adjacent service record is used as the first service to trigger the The device combination performs the coordinated operation of the first service. When there is no service record, the first service is determined with a preset service priority, and the device combination is triggered to perform coordinated operation of the first service.

In a possible implementation manner, the first electronic device is a folding screen in an unfolded state, and when the collaborative service performed by the first electronic device and the second electronic device includes the first collaborative service and the second collaborative service, wherein the first The collaboration service is a collaboration service between a mobile phone and a notebook computer, and the second collaboration service is a collaboration service between a tablet and a notebook computer, and the default service priority is that the first collaboration service is higher than the second collaboration service. In this way, the service is triggered according to the service priority, and when there are multiple collaborative services in the device combination, the service disorder that triggers the collaborative service is avoided, so that the collaborative service can be carried out in an orderly manner.

In a possible implementation, when there is at least one electronic device in the device combination that is performing a collaborative service, it is judged whether the first service can be executed jointly with all devices in the device combination that are performing the coordinated service; if they can be jointly executed, the execution device Coordinated operation of the combined first service; if it cannot be jointly executed, determine all coordinated services that cannot be jointly performed with the first service from among all coordinated services being performed by at least one electronic device in the device combination. When the first service jointly executes a coordinated service, perform the coordinated operation of the first service. In this way, when there are mutually exclusive services, it is determined whether to execute the first service operation according to user requirements, making the operation more humanized.

In a possible implementation manner, when the user cancels and terminates all coordinated services that cannot be executed together with the first service, an operation that the device combination cannot be coordinated is triggered.

In a second aspect, the present application provides a method for multi-device cooperative conflict handling, which is applied to a second electronic device, and the method includes:

When the user performs cooperative operations on the first electronic device and the second electronic device, the service information of the second electronic device is provided, so that the first electronic device can use the service information of the first electronic device and the service information of the second electronic device , judging whether there is a coordination conflict in the equipment combination of the first electronic device and the second electronic device; and causing the first electronic device to execute when there is a coordination conflict in the equipment combination, determine that the equipment combination cannot perform a collaborative service; wherein, the business information includes the device support At least one of service name, service scheduling type, ongoing collaborative service, or equipment combination type supported by the service. In this way, according to the service information, it is determined that there is a collaboration conflict in multi-device collaboration, and the collaboration service with the collaboration conflict is filtered out, so that the device combination can normally establish a service.

In a possible implementation manner, the existence of a coordination conflict in a device combination is determined in the following manner: the first electronic device determines that at least one electronic device in the device combination is performing a coordinated service according to the ongoing coordinated service of the device; and according to the service scheduling type , it is determined that the ongoing coordination service of at least one electronic device cannot be scheduled, and it is determined that there is a coordination conflict in the device combination. In this way, services that cannot be scheduled are filtered out.

In a possible implementation manner, the collaboration conflict in the device combination is determined in the following manner: the first electronic device determines that the first electronic device and the second electronic device do not support the same coordinated service according to the service names supported by the devices in the device combination, or According to the device combination type supported by the service, it is determined that the same collaborative service does not belong to the service supported by the device combination, and it is determined that there is a collaboration conflict between the device combination of the first electronic device and the second electronic device. In this way, services with no service intersection in the equipment combination or services whose service intersection does not match the services supported by the equipment combination are filtered out.

In a possible implementation, if the ongoing coordination service of the first electronic device and the ongoing coordination service of the second electronic device can be invoked, the existence of a coordination conflict in the device combination is determined in the following manner: the first electronic device The name of the service supported by the equipment in the middle, it is determined that the first electronic device and the second electronic device do not support the same collaborative service, or according to the type of device combination supported by the service, it is determined that the same collaborative service does not belong to the service supported by the device combination, and the first electronic device and the second electronic device are determined. A collaboration conflict exists in the device combination of the second electronic device. In this way, the services that can be scheduled when the coordinated services of the equipment in the equipment combination are being scheduled, but the equipment combination does not have a service intersection or the service intersection does not match the services supported by the equipment combination.

In a possible implementation, when the second electronic device is performing a collaborative service, the coordinated service determined by the first electronic device cannot be performed jointly with the first service, and according to the first electronic device It is determined that the coordinated service being performed by the second electronic device is terminated, and the coordinated service being performed by the second electronic device is disconnected, so that the first electronic device performs the coordinated operation of the first service. In this way, when there are mutually exclusive services, it is determined whether to execute the first service operation according to user requirements, making the operation more humanized.

In a third aspect, the present application provides an electronic device, including a memory and a processor, the memory is coupled to the processor; the memory stores program instructions, and when the program instructions are executed by the processor, making the electronic device execute the method described in any one of the first aspect

In a fourth aspect, the present application provides an electronic device, including a memory and a processor, the memory is coupled to the processor; the memory stores program instructions, and when the program instructions are executed by the processor, Making the electronic device execute the method described in any one of the second aspect.

In a fifth aspect, the present application provides a collaborative work system, including the electronic device of the third aspect and the electronic device of the fourth aspect.

It should be understood that descriptions of technical features, technical solutions, beneficial effects or similar language in this application do not imply that all features and advantages can be realized in any single embodiment. On the contrary, it can be understood that the description of features or beneficial effects means that specific technical features, technical solutions or beneficial effects are included in at least one embodiment. Therefore, descriptions of technical features, technical solutions or beneficial effects in this specification do not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions and beneficial effects described in this embodiment may also be combined in any appropriate manner. Those skilled in the art will understand that the embodiments can be implemented without one or more specific technical features, technical solutions or advantageous effects of the specific embodiments. In other embodiments, additional technical features and beneficial effects may also be identified in certain embodiments that do not embody all embodiments.

Description of drawings

FIG. 1A is a schematic diagram of a multi-device collaboration interface provided by an embodiment of the present application;

FIG. 1B is a schematic diagram of a scenario where a master-slave device has no coordinated service provided by an embodiment of the present application;

FIG. 1C is a schematic diagram of a service preemption of a cross-device collaborative service being performed by a first electronic device provided in an embodiment of the present application;

FIG. 2 is a schematic diagram of a hardware structure of an electronic device provided in an embodiment of the present application;

FIG. 3 is a software structural block diagram of an electronic device 100 according to an embodiment of the present application;

FIG. 4 is a block diagram of a layered architecture for realizing coordinated and unified management of multiple devices provided by an embodiment of the present application;

FIG. 5 is an implementation sequence diagram of service association based on multi-device coordinated unified management provided by an embodiment of the present application;

FIG. 6 is a flowchart of a conflict handling method provided in an embodiment of the present application;

FIG. 7A is an interactive sequence diagram of multi-device collaborative service conflict handling provided by the embodiment of the present application;

FIG. 7B is an interactive sequence diagram of multi-device collaborative service conflict handling provided by the embodiment of the present application;

FIG. 8 is a schematic diagram of a reminder that a connection cannot be established provided by an embodiment of the present application;

FIG. 9 is a schematic diagram of a prompt box requesting user confirmation provided by an embodiment of the present application;

FIG. 10 is a schematic diagram of establishing a connection between a primary and a secondary electronic device without coordinated services provided by an embodiment of the present application;

FIG. 11 is a schematic diagram of establishing a cross-device service in the presence of a second electronic device provided by an embodiment of the present application.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of this application.

The term "and/or" in this article is just an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B can mean: A exists alone, A and B exist simultaneously, and there exists alone B these three situations.

The terms "first" and "second" in the description and claims of the embodiments of the present application are used to distinguish different objects, rather than to describe a specific order of objects. For example, the first target object, the second target object, etc. are used to distinguish different target objects, rather than describing a specific order of the target objects.

In the embodiments of the present application, words such as "exemplary" or "for example" are used as examples, illustrations or illustrations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of the present application shall not be interpreted as being more preferred or more advantageous than other embodiments or design schemes. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete manner.

In the description of the embodiments of the present application, unless otherwise specified, "plurality" means two or more. For example, multiple processing units refer to two or more processing units; multiple systems refer to two or more systems.

Multi-device coordination is a distributed technology applied to multiple electronic devices. Using multi-device collaboration technology, two or more electronic devices can perform cross-system and cross-device collaboration to achieve resource sharing and collaborative operations.

Multi-device collaboration can be applied between electronic devices of the same type or different types. Among them, the types of electronic devices include but are not limited to mobile phones, tablet computers, notebook computers, large-screen devices (such as smart TVs, smart screens), personal computers (persona1computer, PC), handheld computers, netbooks, personal digital assistants (personal digital assistants) , PDA), wearable electronic equipment, vehicle equipment, virtual reality equipment and other equipment.

Multi-device collaboration needs to be realized based on the communication connection between devices. The communication connection may be a wired communication connection or a wireless communication connection. Wherein, the solution of wired communication connection may include, for example, USB On-The-Go (OTG) technology; the solution of wireless communication may include, for example, wireless fidelity (wireless fidelity, Wi-Fi), Wi-Fi direct -Fi Direct), Bluetooth (bluetooth, BT), near field communication technology (near fieldcommunication, NFC), infrared technology (infrared, IR), etc.

With the continuous development of terminal technology, multi-device collaboration has produced a variety of different types of collaboration (also called: collaboration services), such as: multi-screen collaboration (including screen extension, screen mirroring and screen sharing), keyboard and mouse collaboration, call Collaboration, continuation of collaboration, etc. in:

Screen mirroring: mirroring and displaying all content on the screen of electronic device A on the screen of electronic device B. The content of electronic device A displayed on electronic device B is the same as the content displayed by electronic device A, and changes as the content displayed by electronic device A changes.

Screen extension: use the screen of electronic device B as the secondary screen of electronic device A, electronic device A can transfer part of the content it needs to display to the secondary screen for display, and the screen of electronic device A and electronic device B can be displayed together The content expands the display capability of the electronic device A.

Screen sharing: project the user interface of electronic device A to the screen of electronic device B for display, and allow the user to operate the user interface of electronic device A in electronic device B, and perform specific operations in electronic device B (For example: dragging and dropping files from the user interface of electronic device B to the user interface of electronic device A), transfer the files in electronic device B to electronic device A, and realize cross-connection between electronic device A and electronic device B Device operation and cross-device file transfer, etc. Wherein, the user interface of the electronic device A can be displayed in any area of the screen of the electronic device B, and can also be displayed in full screen.

Keyboard and mouse collaboration: Electronic device A and electronic device B can share each other's original input devices, such as mouse and keyboard. For example, the input device of electronic device A is shared with electronic device B, and the shared input device can be input in electronic device A or in electronic device B. In addition, in the keyboard and mouse sharing type, file transfer can also be performed between the electronic device A and the electronic device B.

Continuation collaboration: When the user runs an application on electronic device A, the interface of electronic device B can prompt the user to open the application running on electronic device A on electronic device B, so as to transfer to electronic device B for continuous operation, such as watching Videos, editing documents, etc. For example: a document application is running on electronic device A. The document application can be memo, word, etc., and the user is editing a document on electronic device A. When electronic device B and electronic device A are close, a prompt message is displayed on electronic device B. , the user clicks the prompt information on electronic device B, and in response to the user's click operation, electronic device B opens the document application and displays the location where the user is editing, so as to transfer to electronic device B to continue editing.

Call coordination: When electronic device A receives an incoming voice call or video call, electronic device B can simultaneously display the call-in interface, so that the user can choose to answer or hang up the call on electronic device B.

Notification collaboration: When electronic device A receives a notification message, the notification message can be displayed synchronously on electronic device B, and the user can also perform operations such as replying, deleting, and reading the notification message on electronic device B.

Among the multiple coordination types listed above, some coordination types are initiated by the first electronic device (generally the initiator of multi-device coordination) to the second electronic device (generally the participant of multi-device coordination) in response to user operations, It can be called manual collaboration services, such as screen extension, screen sharing, keyboard and mouse collaboration, etc. Some coordination types are automatically triggered when the triggering rules are met when the user enables the function, which can be called automatic coordination services, such as call coordination, notification coordination, and connection coordination.

Take the manual collaboration business as an example:

If the first electronic device is a mobile phone and the second electronic device is a tablet computer, the supported collaboration type may include screen sharing.

If the first electronic device is a mobile phone with a non-folding screen in the mobile phone, and the second electronic device is a PC, the supported collaboration types may include keyboard and mouse collaboration and screen sharing. Among them, when the non-folding screen mobile phone and the PC trigger the connection for the first time, the default collaboration type can be screen sharing.

If the first electronic device is a folding screen mobile phone in a mobile phone, and the second electronic device is a PC, the types of cooperation supported by it may include keyboard and mouse cooperation, screen sharing, screen mirroring and screen expansion. Among them, when the folding screen mobile phone and the PC trigger the connection for the first time, the default collaboration type can be screen sharing.

If the first electronic device is a mobile phone and the second electronic device is a large-screen device, the supported collaboration types may include screen projection.

If the first electronic device is a tablet computer and the second electronic device is a mobile phone, the supported collaboration types may include.

If the first electronic device is a tablet computer and the second electronic device is a PC, the supported cooperation types may include screen mirroring, screen expansion, and keyboard-mouse cooperation. Wherein, when the connection between the tablet computer and the PC is triggered for the first time, the default collaboration type may be screen mirroring.

If the first electronic device is a tablet computer and the second electronic device is a large-screen device, the supported collaboration types may include screen projection.

If the first electronic device is a PC and the second electronic device is a mobile phone with a non-folding screen, the types of collaboration it supports may include keyboard-mouse collaboration and screen sharing. Among them, when the PC and the non-folding screen mobile phone trigger the connection for the first time, the default collaboration type can be screen sharing.

If the first electronic device is a PC and the second electronic device is a folding screen mobile phone, the supported cooperation types may include keyboard and mouse cooperation, screen sharing, screen mirroring and screen expansion. Among them, when the PC and the folding screen mobile phone trigger the connection for the first time, the default collaboration type can be screen sharing.

If the first electronic device is a PC and the second electronic device is a tablet computer, the supported cooperation types may include screen mirroring, screen expansion, and keyboard-mouse cooperation. Wherein, when the connection between the PC and the tablet is triggered for the first time, the default collaboration type may be screen mirroring.

If the first electronic device is a PC and the second electronic device is a large-screen device, the supported collaboration type may include screen projection.

Take automatic collaboration business as an example:

Electronic devices that support call coordination may include mobile phones, tablets, PCs, large-screen display devices, and the like.

Electronic devices that support notification coordination may include mobile phones, tablets, PCs, and the like.

Electronic devices that support connection coordination may include mobile phones, tablets, PCs, large-screen display devices, and the like.

At present, with the improvement of users' demand for terminal technology, multi-device collaborative unified management has become the key to the development of collaborative technology. Multi-device collaborative unified management refers to the function that users can implement collaborative business establishment with different devices through a device control center interface. For example, the mobile device control center interface presents all other devices that can be established with the mobile device, namely device A, device B, and device C. The collaboration between device B and device C can also terminate the ongoing collaboration service between device A and other devices. Referring to FIG. 1A , it is a schematic diagram of an interface of a device control center provided by an embodiment of the present application. Among them, the "smart interconnection" interface of the full-screen interface of the first electronic device is a multi-device collaborative control center interface. The interface can display the mobile phone of the first electronic device, which is located in the center of the interface and wrapped in blue (or other marks that distinguish it from the primary color of blisters of the second electronic device) blistered mobile phone icon. It is also possible to display all other second electronic devices that can be connected with the first electronic device, and the device identifications of the second electronic device icons wrapped in blisters on pads, MagicBooks, Smart TVs, and Pads. It can also display the way to establish collaboration—drag and drop devices to establish collaboration. That is, by dragging and dropping, it is possible to establish a cooperative business connection between a mobile phone and a pad, and it is also possible to establish a cooperative business connection between a mobile phone and a Magic Book or Smart TV.

However, in the process of establishing a collaboration service based on the premise of multi-device collaboration and unified management, there may be conflicts between multi-device collaboration services. Both the first electronic device and the second electronic device support the collaborative service, but the collaborative service is combined with the services supported by the device composed of the first electronic device and the second electronic device, etc., resulting in the failure of the multi-device collaborative service to establish a connection normally. Based on the above-mentioned conflict problem, there are generally two application scenarios. One is that neither the first electronic device nor the second electronic device is in an ongoing collaborative service. One is that there is a service conflict preemption, that is, the first electronic device has an ongoing coordinated service, or/and the second electronic device has an ongoing coordinated service.

Exemplary Explanation 1: Refer to Figure 1B (10B), which is a schematic diagram of a scenario where the master-slave electronic device does not have cross-device collaborative services provided by the embodiment of the present application, that is, the first electronic device and the second electronic device are not in progress collaborative business. Wherein, the second electronic device pad and the first electronic device mobile phone have no cross-device coordination service, that is, the first electronic device and the second electronic device have no coordination service. Exemplary Explanation 2: Referring to FIG. 1C , it is a schematic diagram of preempting a service conflict provided by an embodiment of the present application. Among them, the first electronic device mobile phone and pad are conducting cross-device collaboration business, that is, the pad and mobile phone become a form of blister connection. When dragging and dropping the second electronic device Smart TV to establish with the mobile phone, there is business preemption of the first electronic device.

In the embodiment of the present application, a method for handling multi-device coordination conflicts is provided, through service information, it is determined that there is a coordination conflict in the device combination of the first electronic device and the second device, and the coordination services with multi-device coordination service conflicts are filtered out, Enable multi-device collaboration services to establish a connection normally.

The method for multi-device cooperative conflict handling in the embodiment of the present application can be applied to various types of electronic devices with a display function.

Referring to FIG. 2 , it is a schematic diagram of a hardware structure of an electronic device provided by an embodiment of the present application. The device can be used not only as the first electronic device in the multi-device coordination, but also as the second electronic device in the multi-device coordination. As shown in Figure 2, the electronic device 100 may include a processor 110, a memory 120, a universal serial bus (universal serial bus, USB) interface 130, a radio frequency circuit 140, a mobile communication module 150, a wireless communication module 160, a camera 170, a display screen 180, touch sensor 190, air pressure sensor 210 and buttons 220, etc.

The processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU), etc. Wherein, different processing units may be independent devices, or may be integrated into one or more processors, for example, integrated into a system on a chip (SoC). A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled.

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

The memory 120 may be used to store computer-executable program code, which includes instructions. The memory 120 may include an area for storing programs and an area for storing data. Wherein, the storage program area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, etc.) and the like. The storage data area can store data created during the use of the electronic device 100 (such as audio data, phonebook, etc.) and the like. In addition, the memory 120 may include one or more storage units, for example, may include a volatile memory (volatile memory), such as: dynamic random access memory (dynamic random access memory, DRAM), static random access memory (static random access memory) , SRAM), etc.; may also include non-volatile memory (non-volatile memory, NVM), such as: read-only memory (read-only memory, ROM), flash memory (flash memory), etc. The processor 110 executes various functional application programs and data processing of the electronic device 100 by executing instructions stored in the memory 120 and/or instructions stored in a memory provided in the processor.

What needs to be supplemented here is that the operating system referred to in the embodiment of this application includes but is not limited to Android operating system, IOS operating system, iPad OS, Hongmeng operating system (HarmonyOS), Windows operating system, Linux operating system, MAC OS operating system systems, embedded systems, etc.

The wireless communication function of the electronic device 100 may be implemented by the radio frequency circuit 140, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The radio frequency circuit 140 may include at least one antenna 141 for transmitting and receiving electromagnetic wave signals. Each antenna in electronic device 100 may be used to cover single or multiple communication frequency bands. In some embodiments, an antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 can provide solutions including wireless communication such as 2G/3G/4G/5G for application programs on the electronic device 100 . The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA) and the like. The mobile communication module 150 can receive electromagnetic waves through the antenna 141, filter and amplify the received electromagnetic waves, and send them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor, convert it into electromagnetic wave and radiate it through the antenna 141 . In some embodiments, at least part of the functional modules of the mobile communication module 150 may be set in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be set in the same device.

A modem processor may include a modulator and a demodulator. Wherein, the modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low frequency baseband signal. Then the demodulator sends the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application program processor. The application processor outputs sound signals through audio equipment (including but not limited to speakers, receivers, etc.), or displays images or videos through the display screen 180 . In some embodiments, the modem processor may be a stand-alone device. In some other embodiments, the modem processor may be independent from the processor 110, and be set in the same device as the mobile communication module 150 or other functional modules.

The wireless communication module 160 may include a wireless fidelity (wireless fidelity, Wi-Fi) module, a bluetooth (bluetooth, BT) module, a GNSS module, a near field communication technology (near field communication, NFC) module, an infrared (infrared, IR) modules etc. The wireless communication module 160 may be one or more devices integrating at least one of the above modules. The wireless communication module 160 receives electromagnetic waves via the antenna 141 , frequency-modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110 , frequency-modulate it, amplify it, and convert it into electromagnetic waves through the antenna 141 for radiation.

In the embodiment of the present application, the wireless communication function of the electronic device 100 may include, for example, global system for mobile communications (GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), 5th generation mobile networks new radio (5G NR), BT, GNSS, WLAN, NFC, FM, and/or IR functions. GNSS can include global positioning system (globalpositioning system, GPS), global navigation satellite system (global navigation satellite system, GLONASS), Beidou satellite navigation system (beidou navigation satellite system, BDS), quasi-zenith satellite system (quasi-zenith satellite system) system, QZSS) and/or satellite based augmentation systems (SBAS).

Camera 170 is used to capture still images or video. The camera 170 includes a lens and a photosensitive element, and an object generates an optical image through the lens and is projected onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a complementary metal-oxide-semiconductor (complementary metal-oxide-semiconductor, CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. DSP converts digital image signals into standard RGB, YUV, RYYB and other image signals. In some embodiments, the electronic device 100 may include 1 or N cameras 170 , where N is a positive integer greater than 1.

The NPU is a neural-network (NN) computing processor. By referring to the structure of biological neural networks, such as the transfer mode between neurons in the human brain, it can quickly process input information and continuously learn by itself. Applications such as intelligent cognition of the electronic device 100 can be implemented through the NPU, such as image recognition, face recognition, speech recognition, text understanding, and the like.

The display screen 180 is used to display images, videos and the like. The display screen 180 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (active-matrix organic light emitting diode). AMOLED), flexible light-emitting diode (flex light-emitting diode, FLED), Mini LED, Micro LED, Micro-OLED, quantum dot light-emitting diodes (quantum dot light emitting diodes, QLED), etc. In some embodiments, the electronic device 100 may include 1 or N display screens 180 , where N is a positive integer greater than 1.

The touch sensor 190 is also called "touch device". The touch sensor 190 may be disposed on the display screen 180, and the touch sensor 190 and the display screen 180 form a touch screen, also called “touch screen”. The touch sensor 190 is used to detect a touch operation on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 180 . In some other embodiments, the touch sensor 190 may also be disposed on the surface of the electronic device 100 , which is different from the position of the display screen 180 .

The air pressure sensor 210 is used to measure air pressure. In some embodiments, the electronic device 100 calculates the altitude based on the air pressure value measured by the air pressure sensor 210 to assist positioning and navigation.

The keys 220 include a power key, a volume key and the like. The key 220 may be a mechanical key. It can also be a touch button. The electronic device 100 may receive key input and generate key signal input related to user settings and function control of the electronic device 100 .

It can be understood that, the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 100 . In other embodiments of the present application, the electronic device may include more or fewer components than shown in the illustrations, or combine certain components, or separate certain components, or arrange different components. The illustrated components can be realized in hardware, software or a combination of software and hardware.

Each method step of the multi-device coordination method provided in the embodiment of the present application is exemplarily described below.

The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the present invention, the software structure of the electronic device 100 is exemplarily described by taking an Android system with a layered architecture as an example.

FIG. 3 is a block diagram of the software structure of the electronic device 100 according to the embodiment of the present application.

The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate through software interfaces. In some embodiments, the Android system is divided into four layers, which are, from top to bottom, the application program layer, the application program framework layer, the Android runtime (Android runtime) and the system library, and the kernel layer.

The application layer can consist of a series of application packages.

As shown in FIG. 3, the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and short message.

The application framework layer provides an application programming interface (application programming interface, API) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 3, the application framework layer can include window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

A window manager is used to manage window programs. The window manager can get the size of the display screen, determine whether there is a status bar, lock the screen, capture the screen, etc.

Content providers are used to store and retrieve data and make it accessible to applications. Said data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebook, etc.

The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, and so on. The view system can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide communication functions of the electronic device 100 . For example, the management of call status (including connected, hung up, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and so on.

The notification manager enables the application to display notification information in the status bar, which can be used to convey notification-type messages, and can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify the download completion, message reminder, etc. The notification manager can also be a notification that appears on the top status bar of the system in the form of a chart or scroll bar text, such as a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in the status bar, issuing a prompt sound, vibrating the electronic device, and flashing the indicator light, etc.

Android Runtime includes core library and virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

The core library consists of two parts: one part is the function function that the java language needs to call, and the other part is the core library of Android.

The application layer and the application framework layer run in virtual machines. The virtual machine executes the java files of the application program layer and the application program framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

A system library can include multiple function modules. For example: surface manager (surface manager), media library (Media Libraries), 3D graphics processing library (eg: OpenGL ES), 2D graphics engine (eg: SGL), etc.

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

The media library supports playback and recording of various commonly used audio and video formats, as well as still image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing, etc.

2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is the layer between hardware and software. The kernel layer includes at least a display driver, a camera driver, an audio driver, and a sensor driver.

The method for multi-device collaboration conflict handling in the embodiment of the present application is mainly applied in the application program layer of the electronic device. Specifically applied to the capability layer, business layer and control layer of the application layer. Referring to FIG. 4 , it is an architectural block diagram of an application program layer provided by an embodiment of the present application.

The layered architecture of the embodiment of the present application includes three layers, namely, a service layer, a control layer, and a capability layer. The business layer includes the control center display interface Control View and business application set. Control View is a human-computer interaction interface for displaying a multi-device collaborative interaction interface. Control View integrates the system interface (System User Interface, SystemUI), the notification bar card and the full-screen interface of the control center.

Among them, the SystemUI provides a loading window for the pull-down status bar card, and the service status of the online service of the device can be loaded through the SystemUI.

The notification bar card is used to present the business status content of the status bar card.

The full-screen interface of the control center is used to display the full-screen UI interface.

The business application set is used to provide business usage, receive business scheduling and perform business processing. The business application set integrates collaboration services such as keyboard and mouse collaboration, call collaboration, connection collaboration, and accompanying flight, as well as the service development kit (profile Software Development Kit, profile SDK) corresponding to the collaboration service. Among them, the profile SDK is used to write and read the device service management module. The device service management module is used for device data synchronization. The service application set can also integrate other collaborative services and their corresponding profile SDKs. In the embodiment of the present application, the other collaborative service is a service that satisfies the connection between the first electronic device and other multiple devices. In this embodiment of the application, the business layer also integrates the control center SDK for interacting with the control layer.

As the core module of multi-device collaborative unified management architecture, the control layer includes communication module, device management module, business status management module, business scheduling management module and setting management module, and also includes communication module SDK corresponding to the communication module, and device management module corresponding The profile SDK corresponding to the profile SDK and the business status management module.

Among them, the communication module realizes the communication between the two control centers, including cross-device instruction distribution and cross-device query, and is connected with the communication module of the capability layer through the communication module SDK. The communication module is also used to realize the transfer by the control center when the business needs to communicate before establishing a connection. If the first electronic device issues a connection instruction, but the device cannot initiate the connection and needs to be initiated by the second electronic device, the instruction is to be established by the second electronic device.

The device management module is used to obtain and manage online and offline information, capability information, service status, etc. of devices with the same account as the first electronic device from the device service management module through the profile SDK in real time. The device management module includes online devices, connection status management and all device capability sets. Among them, the online device is used to query the current online device, the connection status management is used to query whether the current device is connected and whether it can be connected, and the all device capability set is used to centrally obtain multiple device states of all devices. The device status includes device online and offline information, capability information, service status, etc.

The business status management module is used to read the business information supported by the first electronic device and surrounding online devices from the device service management module in real time through the Profile SDK, such as the list of business capabilities supported by this application, business switches, whether the business can be dispatched by the control center, The type of equipment supported by a specific business, the connection scheme supported by a specific business, the current running status of the business, etc. The business status management module includes the equipment business set and business status management. Among them, the service set of the device queries the service set supported by the device, and the service status management is used to query the service status supported by the online device, and receives external service status changes to update the status and synchronize it to the display interface of the control center.

The business scheduling management module is used to judge business conflicts, issue prompts to users, and issue business instructions according to user intentions, that is, to perform business connection, switching and disconnection according to user selection and business conflict callback services. The business scheduling management module includes business conflict scheduling and business connection management. Among them, business conflict scheduling is used for conflict handling. For example, mobile phones support screen projection, and pads support screen projection, but the two cannot coexist due to notification restrictions, and business conflict scheduling is required to handle business conflicts. Business connection management is used to manage whether multiple devices have collaborative services and whether they can be connected.

The setting management module is used to manage related settings of the control center, including mode setting and so on.

The capability layer includes the discovery of the same account of the communication module, compatibility of old business discovery, and connection transmission, which are used to realize device connection establishment, transmission, and discovery. The capability layer also includes a device service management module, which is used to realize device data synchronization, such as device data synchronization such as online and offline information, capability information, and service status, and save it in the data storage control DataController of the data layer for persistent storage of patterns.

In addition, an embodiment of the present application also provides a collaborative work system, which includes a first electronic device and a second electronic device. Refer to FIG. 2 for the specific structure of the first electronic device, and refer to FIG. 2 for the specific structure of the second electronic device, which will not be repeated here.

In order to better illustrate the method for handling multi-device cooperative conflicts provided by the embodiment of the present application, firstly, an implementation sequence diagram of service establishment based on multi-device cooperative unified management is introduced.

Referring to FIG. 5 , it is a sequence diagram of implementing service association based on multi-device coordinated unified management provided by the embodiment of the present application. Specifically include:

The service scheduling management module queries the service information from the service status management module in response to the user performing the establishment operation on the first service of the device combination, and judges the connection mode of the first service according to preset conflict rules. According to the connection mode of the first service, a service association establishment result is determined.

In this embodiment of the application, the device combination is a combination of the first electronic device and the second electronic device. The first service is a service jointly performed by the first electronic device and the second electronic device. When the user operates by dragging and dropping the second electronic device on the control center interface, it is used to perform the main second electronic device business association operation. The service scheduling management module obtains the requested service scheduling instruction sent by the Control view, sends a service status query instruction to the service status management module, and acquires the service information of the first electronic device and the service information of the second electronic device. Wherein, the service information includes at least one of the name of the service supported by the device, the type of service scheduling, the ongoing collaborative service, or the type of device combination supported by the service. The service scheduling module determines the connection mode of the first service according to preset conflict rules. In the embodiment of the present application, the connection mode of the first service includes connection not allowed, connection allowed and conflict preemption mode. According to the connection mode of the first service, a service association establishment result is determined.

Specifically, when the connection mode of the first service is not allowed (principle 1), the communication module performs pop-up processing of the control center interface, so that the control center interface pops up an indication that the connection cannot be established.

When the connection mode of the first service is the allowed connection mode (principle 2), it is necessary to determine whether cross-device service communication establishment is required, that is, it is necessary to determine whether connection through communication modules of different devices is required. For example, the control center SDK sends instructions to the business scheduling management module that require cross-device business communication to establish a connection. The electronic equipment cooperates with the business to establish a business association. If not, the SDK of the control center directly establishes a business association. The Data Controller in the data layer records the business status of this establishment. When establishing a new alliance next time, the business status of this establishment will be optimized. At the same time, the control center SDK updates the service state change to the device service management module, or the control center SDK notifies the service state management module to update by broadcasting.

When the connection mode of the first service is the conflict preemption mode, the conflict preemption mode is at least one of the ongoing service of the first electronic device or the ongoing service of the second electronic device. First, change the business status to the device service management module, or notify the business status management module to update it by broadcasting, determine the first business to allow connection according to the preset conflict rules, and establish a connection with the first business according to the processing method of principle 2 . Refer to FIG. 6 and FIGS. 7A-7B below for specific processing methods, and will not be discussed here. If the business scheduling management module determines that scheduling can be established, see the content of principle 2 in the previous paragraph for specific implementation, and will not be discussed here.

Referring to FIG. 6 , it is a flowchart of a conflict handling method provided by an embodiment of the present application. The method includes the following steps:

S101: Read service information of the first electronic device and surrounding online devices.

The service state management module can read the service information of the first electronic device and the service information of peripheral online devices from the device service management module.

Table 1 Equipment business information table

See Table 1 for device service information provided in this embodiment of the application. Including the list of services supported by this application, that is, the name of the service supported by the device, the status of the service switch, whether the service can support control center scheduling (that is, the type of service scheduling), the device form that the service can support (that is, the type of device combination supported by the service), and the service The physical channels that can be supported, the current running status of the service (that is, the ongoing collaborative service), and the currently used physical channel.

S102: Perform interaction between the first electronic device and the second electronic device, and establish a device combination.

The user realizes the interaction between the first electronic device and the second electronic device by dragging and dropping the second electronic device on the interface of the control center, and establishes a device combination to refer to the first electronic device and the second electronic device.

S103: Determine whether all device combinations are in a no-service state. If yes, execute S105; if not, execute S104.

In the embodiment of the present application, it is judged whether the combination of devices is in a no-service state, that is, it is judged whether the first electronic device and the second electronic device are conducting coordinated services with other devices. If the first electronic device and the second electronic device are in a no-service state, that is, the current master second electronic device is not establishing coordinated services with other devices. If the first electronic device and the second electronic device are in a service state, it means that the first electronic device is establishing a coordinated service with other devices, or the second electronic device is establishing a coordinated service with other devices.

S104: Determine whether all device combinations can be scheduled. If all services can be scheduled, go to S105. Otherwise, execute S115.

When at least one of the first electronic device and the second electronic device is performing collaborative services with other devices, it is determined whether the current service can be dispatched by the control center. Exemplary instructions:

Table 2 Schematic diagram of business scheduling

Table 2 is a schematic table of service scheduling provided by the embodiment of the present application, which is a memory table of the control center, indicating whether the collaborative service can be scheduled by the control center. Among them, N/A indicates that the current service cannot be scheduled by the control center, and others indicate that the current service can be scheduled by the control center. Exemplary explanation: If a PC and a tablet are performing collaborative service A, and a collaborative service is established between two tablet devices, the current service collaborative service A cannot be scheduled by other tablets through the control center of the tablet. At this time, one end device is cooperating with other devices, and the current service cannot be scheduled by the control center. If the collaborative service between the PC and the folding screen is established, it means that the current service collaborative service A can be dispatched by the control center. It should be noted by those skilled in the art that the above service scheduling table is only a schematic illustration, and is not limited to these features, and supports all multi-device features.

S105: Determine whether there is a service intersection in the device combination, and if so, execute S106. Otherwise, execute S115.

Exemplary explanation: the first electronic device has a wireless screen projection service, and the second electronic device also has a wireless screen projection service, indicating that there is a service intersection between the device combinations. For example, the first electronic device has a wireless screen projection service, and the second electronic device has screen mirroring, screen extension, and screen mirroring services, which means that there is no business intersection between the device combinations.

S106: Determine whether the device combination matches. If yes, execute S107. Otherwise, execute S115.

Exemplary description: Assume that the current service is notification coordination, and the electronic devices that support notification coordination are mobile phones, tablets, and PCs. If the first electronic device is a mobile phone and the second electronic device is a large-screen display device, it means that the device combination does not match. If the first electronic device is a mobile phone and the second electronic device is a tablet, it means that the device combination matches.

S107: Obtain a list of available services to be triggered.

In this embodiment of the present application, the list of services to be triggered refers to coordinated services supported by the first electronic device and the second electronic device. If there are multiple collaborative services, as shown in Table 2, there are collaborative service A and collaborative service B between the folding screen and the PC, and the two collaborative services are stored in the form of a list.

S108: Read the last business record of the device combination.

S109: If there is no record, read the default priority from the preset service priority, and trigger the service according to the default priority. If there is a record, the service will be triggered according to the last record.

If the first electronic device and the second electronic device have established a cooperative service, the data storage center records the last connection mode of the first service. When using this time, you can query the last business status, and use the last business status to establish this collaborative business. If there is no previous service, that is, the first electronic device and the second electronic device are establishing a cooperative service for the first time, the default priority is read through the preset service priority. The preset service priority is a schedulable service table embedded in the control center, and the specific preset service priority table is shown in Table 2. When there are multiple collaborative services on the device, for example, there are mobile phone and PC collaborative service B and tablet and PC collaborative service A with the folding screen (expanded) and PC, and the priority of mobile phone and PC collaborative service B is higher than that of tablet and PC collaborative service A. , that is, the trigger service this time is the mobile phone and PC collaboration service B.

S110: Determine whether the first electronic device and the second electronic device currently have mutually exclusive services. If there is no mutually exclusive service, execute S115. Otherwise, execute S111.

In this embodiment of the present application, whether the main second electronic device currently has a mutually exclusive service refers to whether the "service running across devices" and the "cooperative service between the first electronic device and the second electronic device" can coexist. For example, mobile phone and PC are coordinating service B. If mobile phone and tablet coordinating service A is established, such as accompanying service, mobile phone and tablet coordinating service A and mobile phone and PC coordinating service B are mutually exclusive and cannot coexist.

S111: Ask the user whether to terminate the current device service and start a new service.

On the interface of the control center, set a prompt box asking the user whether to terminate the current device service and start a new service prompt box. If the user chooses to terminate the collaborative service of the current device and establish a new collaborative service, a stop instruction will be issued to the devices with services at both ends, and after the stop operation is completed, an instruction to establish a new service will be issued.

In addition, in the embodiment of the present application, the prompt box also provides the user with the option of not prompting again, and if the user chooses not to prompt, the subsequent query of "interrupting the current prompt" will not pop up to the user. If the user does not choose whether to "don't prompt again", the subsequent corresponding scene needs to continue to ask the user for operation.

S112: Obtain a user confirmation result.

S113: Terminate the current services of the first electronic device and the second electronic device when the user confirms to terminate the service of the current device.

S114: Issue a scheduling instruction, and the first electronic device establishes a target service with the second electronic device.

S115: No service is triggered, and a prompt pops up.

In the multi-device collaborative conflict handling method provided in the embodiment of the present application, the service status of the first electronic device and the second electronic device is acquired through the second electronic device service management module, and it is judged whether the first electronic device and the second electronic device exist Cross-device collaboration services, whether the ongoing cross-device collaboration services can be scheduled by the control center, whether the business intersection of the first electronic device and the second electronic device and the types of devices that can be supported match, whether there is mutual exclusion, and filtering without collaboration services , or a collaborative service with service preemption. Enable multi-device collaboration services to establish a connection normally.

Next, this application takes an Android device as an example to introduce in detail the specific implementation of the multi-device collaboration conflict handling method provided by the embodiment of this application. Referring to FIGS. 7A-7B , it is an interaction sequence diagram of multi-device collaborative service conflict handling provided by the embodiment of the present application. Specifically include:

S31: Device status management module and business status management module The second electronic device service management module reads the business status of the first electronic device and the list of services supported by the first electronic device, reads the business status of peripheral online devices and the business supported by the second electronic device list.

The device status management module sends an instruction requesting the service status of the first electronic device to the device service management module. The device service management module returns the service status and supported service list of the first electronic device to the service status management module. The device management module sends an instruction requesting to read the device status of the peripheral online devices to the device service management module, and the second electronic device service management module obtains the device status of the peripheral online devices. At the same time, the device management module sends a notification to the business status management module to inquire about the business status of the registered peripheral devices. After the business status management module receives the instruction of inquiring and registering the business status of the peripheral equipment, it sends an instruction to read the business status of the peripheral online equipment to the equipment service management module, and the second electronic device service management module obtains the business status of the peripheral online equipment and the second electronic device Support business list.

S32: Service Conflict Scheduling Responding to the user's operation of creating a service connection between the main second electronic device, the service status and supported service list of the first electronic device and the second electronic device are obtained from the service status management module.

When the user operates in the Control view by dragging and dropping the control center interface, that is, the user performs the operation of establishing a service connection between the primary and secondary electronic devices, which triggers a device service conflict query. The business conflict scheduling obtains the trigger device business conflict query instruction, sends an instruction to query the business status and supported service list of the main second electronic device to the business status management module, and obtains the business status and supported business list of the first electronic device from the business status management module, And the service status and supported service list of the second electronic device.

S33: Service Conflict Scheduling In response to the first electronic device and the second electronic device having at least one terminal whose current service cannot be scheduled, send an instruction to Control View that the current service of at least one terminal cannot be scheduled, and the control center interface prompts the user that the connection is currently not allowed instruction, the process ends. Service Conflict Scheduling In response to the fact that the current services of the first electronic device and the second electronic device are scheduled or there is no service, S34 is executed.

The service conflict scheduling determines whether the current service of at least one end of the first electronic device and the second electronic device cannot be scheduled. That is, at least one end of the first electronic device and the second electronic device has an ongoing coordinated service with other devices, and the coordinated service cannot be scheduled. As mentioned in Table 2 above, if the PC and the tablet are performing collaborative service A, and the collaborative service is established between two tablet devices, the current service collaborative service A cannot be scheduled by other tablets through the control center of the tablet. At this time, one end device is cooperating with other devices, and the current service cannot be scheduled by the control center.

When the business conflict scheduling acquires that the current business of at least one end of the primary and second electronic devices cannot be scheduled, an instruction is sent to the Control View that the current business of at least one end cannot be scheduled, and the control center interface prompts the user that the connection command is currently not allowed. In a possible implementation manner, a prompt dialog box is displayed on the interface of the control center, prompting that the establishment cannot be established. Exemplary description: FIG. 8 is a schematic diagram of a prompt that a connection cannot be established provided in the embodiment of the present application. The mobile phone of the first electronic device and the magic book are in the collaborative business. The user drags and drops the smartTV. Since the mobile phone of the first electronic device is in the current business and cannot be scheduled, the "smart interconnection" interface displays a prompt dialog box "smartTV is not allowed to establish a connection with the mobile phone. ". In another possible implementation manner, the control center interface directly ejects the second electronic device. The embodiment of the present application does not limit the prompt that the connection cannot be established.

S34: The service conflict scheduling checks the service intersection in which the service states of the first electronic device and the second electronic device are ON. In response to the fact that there is no service intersection between the first electronic device and the second electronic device, the service conflict scheduling sends a no service intersection command to Control View, and the control center interface prompts the user that connection is currently not allowed, and the process ends. When the service conflict scheduling responds to the intersection of services between the first electronic device and the second electronic device, S35 is executed.

S35: Service Conflict Scheduling In response to the fact that the device type supported by the collaborative service does not match the current device combination, an instruction is sent to Control View that both ends do not support the establishment of a new service, and the Control View control center interface prompts the user that connection is currently not allowed, and the process ends. Service conflict scheduling In response to matching the device type supported by the collaborative service with the current device combination, execute S36.

S36: Business conflict scheduling reads the last business record of the equipment combination from the Data Controller, and if there is no last record, selects the highest priority service to establish a connection.

The business conflict scheduling sends an instruction to read the last business record of the equipment combination to the Data Controller, and the Data Controller returns the stored last business record. If the last record does not exist, the service conflict scheduling selects the service with the highest priority from the preset priority table for service establishment.

S37: When the device combination currently has mutually exclusive services and no dialog box is not set, the service conflict dispatcher sends a command to Control View to request user confirmation to confirm whether to terminate the current device service and start a new service. If the user refuses, the process end command returns to the service Conflict scheduling ends conflict processing.

Exemplary description: Fig. 9 is a schematic diagram of a prompt box for requesting user confirmation provided by the embodiment of this application. When the user clicks the "Reject" logo, it means that the user refuses, and the control center interface displays a prompt box that does not allow the connection.

When it is worth noting, the current device combination user confirms to terminate the current device service, or the control center interface is set to stop prompting, start a new service, and execute S38.

If there is no mutually exclusive service in the current device combination, directly execute S39.

S38: The service conflict scheduling sends a notification to the service connection management to issue an instruction to stop the current service, and obtains a result of terminating the current service.

When the mutually exclusive service exists on the first electronic device, the service connection management sends a notification service termination instruction to the control center SDK. The control center SDK terminates the mutual exclusion service of the current first electronic device, and returns the processing result to the service connection management.

When the mutually exclusive service exists on the device and the mutually exclusive service exists on the second electronic device, the service connection management is sent through the first electronic device control layer communication module, the capability layer communication module, and the second electronic device capability layer communication module and control layer communication module. To the second electronic device service connection management, the service connection management sends a notification service termination instruction to the second electronic device control center SDK. The second electronic device control center SDK stops the current mutually exclusive service of the second electronic device, and returns to the service through the second electronic device capability layer communication module and control layer communication module, as well as the first electronic device control layer communication module and the capability layer communication module Connection management. The service connection management sends the service stop result to the service conflict scheduler.

S39: The service conflict scheduling sends an instruction to establish a new service to the service connection management, and the service connection management control center SDK sends a scheduling instruction to establish a coordinated service with the second electronic device.

Exemplary Explanation 1: Refer to FIG. 10 , which is a schematic diagram of establishing a connection between a master and a second electronic device without cooperative services provided by an embodiment of the present application. The first electronic device mobile phone is another Android mobile phone, and the second electronic device is a notebook. Neither the first electronic device nor the second electronic device has an ongoing cross-device service. And the first electronic device and the second electronic device do not have coordinated services. Drag the notebook until it is within the preset distance from the phone, and it will bounce back to the notebook directly. That is, the mobile phone and the notebook cannot establish collaborative services.

Exemplary Explanation 2: Referring to FIG. 11 , it is a schematic diagram of establishing a cross-device service in the presence of a second electronic device provided by an embodiment of the present application. The first electronic device is a mobile phone, the second electronic device is a notebook, and the notebook is performing a cross-device screen mirroring service. The screen mirroring service can be dispatched by the mobile phone control center. Mobile phones and notebooks have business intersections, and the collaborative business to be carried out supports the combination of mobile phones and notebooks. However, the collaboration service to be established and the ongoing screen mirroring service are mutually exclusive. Drag and drop the notebook until it is within the preset distance from the mobile phone, and a prompt box will appear on the interface of the control center, prompting "the user confirms whether to terminate the current device service". The user clicks "Decline" and it bounces back directly to the notebook.

The multi-device collaboration conflict handling method provided by the embodiment of the present application can deal with the non-cooperative service existing in the service establishment process based on multi-device cooperative unified management, and the problem of service preemption by the primary and secondary electronic devices. Filter out non-cooperative services. For the service preemption problem of the main second electronic device, different processing is performed on whether the main second electronic device has mutual exclusion under the condition that the main second electronic device has cooperative services. Enable multi-device collaboration to establish a connection normally.

Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and brevity of the description, only the division of the above-mentioned functional modules is used as an example for illustration. In practical applications, the above-mentioned functions can be allocated according to needs It is completed by different functional modules, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. For the specific working process of the above-described system, device, and unit, reference may be made to the corresponding process in the foregoing method embodiments, and details are not repeated here.

In the several embodiments provided in this embodiment, it should be understood that the disclosed system and method may be implemented in other ways. For example, the above-described embodiments are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined Or it can be integrated into another system, or some features can be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of this embodiment may be integrated into one processing unit, or each unit may physically exist separately, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this embodiment is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium In, several instructions are included to make a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor execute all or part of the steps of the method described in each embodiment. The aforementioned storage medium includes: flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk, and other various media capable of storing program codes.

The above is only a specific implementation of the application, but the protection scope of the application is not limited thereto, and any changes or replacements within the technical scope disclosed in the application should be covered within the protection scope of the application . Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims (17)

1. A multi-device co-conflict processing method, applied to a first electronic device, the method comprising:

acquiring service information of equipment; the device comprises the first electronic device and a second electronic device, wherein the second electronic device is an electronic device which can cooperate with the first electronic device; the service information comprises at least one of a service name supported by the equipment, a service scheduling type, an ongoing cooperative service or an equipment combination type supported by the service;

responding to the cooperative operation of a user on the first electronic equipment and the second electronic equipment, and judging whether the equipment combination of the first electronic equipment and the second electronic equipment has cooperative conflict or not according to the service information of the equipment;

and when the equipment combination has the cooperative conflict, determining that the equipment combination cannot perform cooperative service.

2. The method of claim 1, wherein the determining, according to the service information of the device, whether a cooperative conflict exists between the first electronic device and the second electronic device, specifically includes:

judging whether at least one electronic device in the device combination is in cooperative service according to the cooperative service in progress of the device;

if yes, judging whether the cooperative service in progress of the at least one electronic device can not be scheduled according to the service scheduling type, and if yes, determining that the cooperative conflict exists in the device combination of the first electronic device and the second electronic device.

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

and determining that the first electronic equipment and the second electronic equipment do not support the same cooperative service according to the service names supported by the equipment in the equipment combination, or determining that the same cooperative service does not belong to the service supported by the equipment combination according to the equipment combination type supported by the service, and determining that the equipment combination of the first electronic equipment and the second electronic equipment has cooperative conflict.

4. The method of claim 2, wherein if the ongoing collaborative service of the first electronic device and the ongoing collaborative service of the second electronic device can be invoked, the method further comprises:

and determining that the first electronic equipment and the second electronic equipment do not support the same cooperative service according to the service names supported by the equipment in the equipment combination, or determining that the same cooperative service does not belong to the service supported by the equipment combination according to the equipment combination type supported by the service, and determining that the equipment combination of the first electronic equipment and the second electronic equipment has cooperative conflict.

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

and triggering the equipment combination to carry out the cooperative operation of the first service based on a preset service priority rule when the equipment combination does not have the cooperative conflict.

6. The method of claim 5, wherein triggering the device combination for the co-operation of the first service based on the preset service priority rule comprises:

judging whether the equipment combination has a business record of cooperative operation or not;

When the service records exist, triggering the equipment combination to carry out the cooperative operation of the first service by taking the cooperative service corresponding to the service record of the nearest neighbor as the first service;

and when the service record does not exist, determining the first service based on the preset service priority, and triggering the equipment combination to carry out the cooperative operation of the first service.

7. The method of any of claims 5-6, wherein when there is at least one electronic device on the device combination that is engaged in a collaborative service, the method further comprises:

judging whether the first service can be executed together with the cooperative service carried out by all the devices in the device combination;

executing the cooperative operation of the first service of the equipment combination if the first service can be executed together;

and if the first service and the second service cannot be jointly executed, determining all the collaborative services which cannot be jointly executed with the first service from all the collaborative services which are currently executed by at least one electronic device in the device combination, and executing the collaborative operation of the first service when the user terminates all the collaborative services which cannot be jointly executed with the first service.

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

And triggering the operation that the equipment combination coordination cannot be performed when the user performs cancellation to terminate all coordination services which cannot be performed together with the first service.

9. The method of claim 6, wherein the first electronic device is a folding screen in an unfolded state, and when the collaboration service performed by the first electronic device and the second electronic device includes a first collaboration service and a second collaboration service, the first collaboration service is a collaboration service of a mobile phone and a notebook computer, and the second collaboration service is a collaboration service of a tablet and a notebook computer; the preset service priority includes: the first collaborative service is higher than the second collaborative service.

10. A method of multi-device co-conflict handling, for use with a second electronic device, the method comprising:

when a user performs cooperative operation on a first electronic device and a second electronic device, providing service information of the second electronic device, so that the first electronic device judges whether a cooperative conflict exists between the first electronic device and the second electronic device according to the service information of the first electronic device and the service information of the second electronic device; when the device combination has a cooperative conflict, the first electronic device determines that the device combination cannot perform cooperative service;

The service information comprises at least one of service names supported by the equipment, service scheduling types, ongoing cooperative service or equipment combination types supported by the service.

11. The method of claim 10, wherein the device combination existence of a co-conflict is determined by:

the first electronic equipment determines that at least one electronic equipment in the equipment combination is in cooperative service according to the cooperative service in progress of the equipment; and determining that the cooperative service in progress of at least one electronic device cannot be scheduled according to the service scheduling type, and determining that the device combination has cooperative conflict.

12. The method of claim 10, wherein the device combination existence of a co-conflict is determined by:

and the first electronic equipment determines that the first electronic equipment and the second electronic equipment do not support the same cooperative service according to the service names supported by the equipment in the equipment combination, or determines that the same cooperative service does not belong to the service supported by the equipment combination according to the equipment combination type supported by the service, and determines that the equipment combination of the first electronic equipment and the second electronic equipment has cooperative conflict.

13. The method of claim 11, wherein if the ongoing collaboration service of the first electronic device and the ongoing collaboration service of the second electronic device can be invoked, the device combination presence collaboration conflict is determined by:

and the first electronic equipment determines that the first electronic equipment and the second electronic equipment do not support the same cooperative service according to the service names supported by the equipment in the equipment combination, or determines that the same cooperative service does not belong to the service supported by the equipment combination according to the equipment combination type supported by the service, and determines that the equipment combination of the first electronic equipment and the second electronic equipment has cooperative conflict.

14. The method of claim 10, wherein when the second electronic device has an ongoing collaborative service, the method further comprises:

and when the second electronic equipment is in cooperative service according to the termination determined by the first electronic equipment, disconnecting the cooperative service in progress by the second electronic equipment, so that the first electronic equipment executes the cooperative operation of the first service.

15. An electronic device, the electronic device comprising:

a memory and a processor, the memory coupled with the processor;

the memory stores program instructions that, when executed by the processor, cause the electronic device to perform the method of any of claims 1-9.

16. An electronic device, the electronic device comprising:

a memory and a processor, the memory coupled with the processor;

the memory stores program instructions that, when executed by the processor, cause the electronic device to perform the method of any of claims 10-14.

17. A co-operating system, characterized in that the system comprises an electronic device according to claim 15 and comprises an electronic device according to claim 16.