CN116679998B

CN116679998B - Multi-device cooperative conflict processing method and electronic device

Info

Publication number: CN116679998B
Application number: CN202211321160.7A
Authority: CN
Inventors: 许嘉; 李鹏飞; 魏同嘉
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2022-10-26
Filing date: 2022-10-26
Publication date: 2024-06-21
Anticipated expiration: 2042-10-26
Also published as: CN116679998A

Abstract

The application provides a multi-device cooperative conflict processing method and electronic equipment, which are applied to the technical field of terminals. The method comprises the following steps: acquiring service information of the first electronic device and service information of the second electronic device, and determining that a device combination of the first electronic device and the second electronic device has a cooperative conflict according to the service information when a user performs system operation on the first electronic device and the second electronic device. When the cooperative conflict exists, the fact that the equipment combination cannot conduct cooperative service is determined. Wherein the service information includes at least one of a service name supported by the device, a service scheduling type, an ongoing collaborative service, or a device combination type supported by the service. Thus, the collaborative services with collaborative conflict are filtered through the method, so that the collaborative services of the equipment are normally established.

Description

Multi-device cooperative conflict processing method and electronic device

Technical Field

The present application relates to the field of terminal technologies, and in particular, to a method for processing multi-device cooperative conflict and an electronic device.

Background

Multi-device collaboration is a technique applied to multiple electronic devices. By utilizing the multi-device cooperation technology, cross-system and cross-device cooperation can be performed between two or more electronic devices, so that resource sharing and cooperation operation are realized.

Along with the improvement of the technical demands of users on the terminals, the collaborative unified management of multiple devices becomes the key of collaborative technical development. The multi-device collaborative unified management refers to that a user realizes the function of executing collaborative business establishment with different devices through a device control center interface. For example, the interface of the mobile phone equipment control center presents all other electronic equipment which can be connected with the mobile phone equipment, namely equipment A, equipment B and equipment C, and the interface of the mobile phone equipment control center can realize the cooperation of the mobile phone and the equipment A, the cooperation of the mobile phone and the equipment B and the equipment C, and the cooperation business of the equipment A and other equipment can be terminated.

However, in the collaborative service establishment process, there may be a problem of conflict between the collaborative services of multiple devices, for example, the mobile phone of the device and the flat panel of the opposite terminal device perform the collaborative service establishment process, but the mobile phone and the flat panel do not have the services that can be performed together, that is, there is no collaborative service, so that the collaborative services of multiple devices cannot be normally established.

Disclosure of Invention

The application aims at: the method and the electronic equipment are used for solving the problem of multi-equipment cooperative conflict in the business establishment process based on multi-equipment cooperative unified management, so that multi-equipment cooperative business is normally established.

In a first aspect, the present application provides a method for multi-device cooperative conflict processing, applied to a first electronic device, where the method includes:

Acquiring service information of a first electronic device and a second electronic device, wherein the second electronic device is an electronic device capable of cooperating with the first electronic device, and the service information comprises at least one of a service name supported by the device, a service scheduling type, an ongoing cooperation service or a device combination type supported by the service;

When the user performs cooperative operation on the first electronic device and the second electronic device, judging whether the device combination of the first electronic device and the second electronic device has cooperative conflict or not according to the service information of the devices. If the cooperative conflict exists, the fact that the equipment combination cannot conduct cooperative service is determined. Thus, according to the service information, the cooperative conflict exists in the cooperation of the plurality of devices, and the cooperative service of the cooperative conflict is filtered, so that the device combination can normally establish the service.

In one possible implementation, it is determined whether the device combination has at least one electronic device that is performing a collaboration service based on the device that is performing a collaboration service. If at least one electronic device is in cooperative service, judging whether the cooperative service in progress of the electronic device can be scheduled according to the service scheduling type. If not, it indicates that there is a co-conflict with the device combination of the first electronic device and the second electronic device. Thus filtering out traffic that cannot be scheduled.

In one possible implementation manner, according to the service name supported by the device, it is determined that the first electronic device and the second electronic device do not support the same cooperative service, or according to the type of the device combination supported by the service, it is determined that the same cooperative service does not belong to the service supported by the device combination, that is, there is a non-existence service intersection between the first electronic device and the second electronic device, or there is a service intersection, but the service intersection does not satisfy the service supported by the device combination of the first electronic device and the second electronic device, which indicates that there is a cooperative conflict between the device combinations of the first electronic device and the second electronic device. Thus, the service intersection of the device combination which does not exist or is not matched with the service supported by the device combination is filtered.

In one possible implementation manner, when the ongoing collaboration service of the first electronic device and the ongoing collaboration service of the second electronic device can be invoked, it is determined that the first electronic device and the second electronic device do not support the same collaboration service according to service names supported by the devices, or it is determined that the same collaboration service does not belong to a service supported by the device combination according to a device combination type supported by the services, that is, there is no service intersection between the first electronic device and the second electronic device, or there is a service intersection, but the service intersection does not satisfy the service supported by the device combination of the first electronic device and the second electronic device, which indicates that there is a collaboration conflict between the device combinations of the first electronic device and the second electronic device. In this way, services that can be scheduled when the cooperative services in progress by the devices in the device combination are filtered out, but the device combination does not have a service intersection or a service whose service intersection does not match the services supported by the device combination.

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

In one possible implementation manner, when a device combination of a first electronic device and a second electronic device has a service record of cooperative operation, a cooperative service corresponding to a service record of a nearest neighbor is used as the first service, and the device combination is triggered to perform cooperative operation of the first service. And when the service record does not exist, determining the first service according to the preset service priority, and triggering the equipment combination to carry out the cooperative 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 services performed by the first electronic device and the second electronic device include a first collaborative service and a second collaborative service, the first collaborative service is a collaborative service of the mobile phone and the notebook computer, the second collaborative service is a collaborative service of the tablet and the notebook computer, and the preset service priority is that the first collaborative service is higher than the second collaborative service. Thus, according to the service priority, when the equipment combination has a plurality of cooperative services, the service disorder of triggering the cooperative services is avoided, and the cooperative services are orderly carried out.

In one possible implementation manner, when at least one electronic device is performing cooperative service on the device combination, judging whether the first service can be executed together with all devices in the device combination; if the first service can be executed together, executing the cooperative operation of the first service of the equipment combination; if the first service and the second service cannot be executed together, determining all the cooperative services which cannot be executed together with the first service from all the cooperative services which are executed by at least one electronic device in the device combination, and executing the cooperative operation of the first service when the user terminates all the cooperative services which cannot be executed together with the first service. Therefore, when the mutual exclusion service exists, whether the first service operation is executed or not is determined according to the user requirement, so that the operation is more humanized.

In one possible implementation manner, when the user performs cancellation to terminate all collaboration services that cannot be performed together with the first service, triggering an operation that cannot be performed by the device combination collaboration.

In a second aspect, the present application provides a method for multi-device cooperative conflict processing, applied to a second electronic device, where the method includes:

When the user performs cooperative operation on the first electronic device and the 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 first electronic equipment executes the cooperative conflict exists in the equipment combination, determining that the equipment combination cannot perform cooperative service; the service information comprises at least one of service names supported by the device, service scheduling types, ongoing collaborative services or device combination types supported by the service. Thus, according to the service information, the cooperative conflict exists in the cooperation of the plurality of devices, and the cooperative service of the cooperative conflict is filtered, so that the device combination can normally establish the service.

In one possible implementation, the existence of a co-conflict for a combination of devices 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. Thus filtering out traffic that cannot be scheduled.

In one possible implementation, the existence of a co-conflict for a combination of devices is determined by: the first electronic device determines that the first electronic device and the second electronic device do not support the same cooperative service according to the service names supported by the devices in the device combination, or determines that the same cooperative service does not belong to the service supported by the device combination according to the type of the device combination supported by the service, and determines that the device combination of the first electronic device and the second electronic device has cooperative conflict. Thus, the service intersection of the device combination which does not exist or is not matched with the service supported by the device combination is filtered.

In one possible implementation, if the ongoing collaboration service of the first electronic device and the ongoing collaboration service of the second electronic device can be invoked, the existence of a collaboration conflict in the device combination is determined by: the first electronic device determines that the first electronic device and the second electronic device do not support the same cooperative service according to the service names supported by the devices in the device combination, or determines that the same cooperative service does not belong to the service supported by the device combination according to the type of the device combination supported by the service, and determines that the device combination of the first electronic device and the second electronic device has cooperative conflict. In this way, services that can be scheduled when the cooperative services in progress by the devices in the device combination are filtered out, but the device combination does not have a service intersection or a service whose service intersection does not match the services supported by the device combination.

In one possible implementation manner, when the second electronic device is performing the collaboration service, the second electronic device performing the collaboration service determined according to the first electronic device cannot perform with the first service, and the second electronic device stopping the second electronic device performing the collaboration service according to the first electronic device determining, disconnect the second electronic device performing the collaboration service, so that the first electronic device performs the collaboration operation of the first service. Therefore, when the mutual exclusion service exists, whether the first service operation is executed or not is determined according to the user requirement, so that the operation is more humanized.

In a third aspect, the present application provides an electronic device comprising a memory and a processor, the memory coupled to the processor; the memory stores program instructions that, when executed by the processor, cause the electronic device to perform the method of any of the first aspects

In a fourth aspect, the present application provides an electronic device comprising a memory and a processor, the memory coupled to the processor; the memory stores program instructions that, when executed by the processor, cause the electronic device to perform the method of any of the second aspects.

In a fifth aspect, the present application provides a co-operating system comprising the electronic device of the third aspect and the electronic device of the fourth aspect.

It should be appreciated that the description of technical features, aspects, benefits or similar language in the present application does not imply that all of the features and advantages may be realized with any single embodiment. Conversely, it should be understood that the description of features or advantages is intended to include, in at least one embodiment, the particular features, aspects, or advantages. Therefore, the description of technical features, technical solutions or advantageous effects in this specification does not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions and advantageous effects described in the present embodiment may also be combined in any appropriate manner. Those of skill in the art will appreciate that an embodiment may be implemented without one or more particular features, aspects, or benefits of a particular embodiment. In other embodiments, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments.

Drawings

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

fig. 1B is a schematic diagram of a scenario where a master device and a slave device have no cooperative service according to an embodiment of the present application;

Fig. 1C is a schematic diagram of service preemption of a first electronic device in a cross-device collaboration service according to an embodiment of the present application;

fig. 2 is a schematic hardware structure of an electronic device according to an embodiment of the present application;

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

FIG. 4 is a block diagram of a layered architecture for implementing collaborative unified management of multiple devices according to an embodiment of the present application;

Fig. 5 is a timing diagram of implementing service establishment based on multi-device collaborative unified management according to an embodiment of the present application;

FIG. 6 is a flowchart of a method for processing a conflict according to an embodiment of the present application;

fig. 7A is a schematic diagram of interaction timing chart of multi-device cooperative service conflict processing according to an embodiment of the present application;

Fig. 7B is a schematic diagram of interaction timing chart of multi-device cooperative service conflict processing according to an embodiment of the present application;

FIG. 8 is a schematic diagram of a connection failure establishment notification according to an embodiment of the present application;

FIG. 9 is a schematic diagram of a prompt box for requesting user confirmation according to an embodiment of the present application;

fig. 10 is a schematic diagram of a connection establishment of a primary second electronic device without a collaboration service according to an embodiment of the present application;

Fig. 11 is a schematic diagram of establishment of an ongoing cross-device service in a second electronic device according to an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone.

The terms first and second and the like in the description and in the claims of embodiments of the application, are used for distinguishing between different objects and not necessarily for describing a particular sequential order of objects. For example, the first target object and the second target object, etc., are used to distinguish between different target objects, and are not used to describe a particular order of target objects.

In embodiments of the application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g." in an embodiment should not be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

In the description of the embodiments of the present application, unless otherwise indicated, the meaning of "a plurality" means two or more. For example, the plurality of processing units refers to two or more processing units; the plurality of systems means two or more systems.

Multi-device collaboration is a distributed technology applied to multiple electronic devices. By utilizing the multi-device cooperation technology, cross-system and cross-device cooperation can be performed between two or more electronic devices, so that resource sharing and cooperation operation are realized.

Multi-device collaboration may be applied between electronic devices of the same type or different types. Types of electronic devices include, but are not limited to, mobile phones, tablet computers, notebook computers, large screen devices (e.g., smart televisions, smart screens), personal Computers (PCs), handheld computers, netbooks, personal Digital Assistants (PDAs), wearable electronic devices, vehicle devices, virtual reality devices, and the like.

Multi-device collaboration needs to be implemented based on communication connections between devices. The communication connection may be a wired communication connection or a wireless communication connection. Among other things, the solution for The wired communication connection may include, for example, USB On-The-Go (OTG) technology; solutions for wireless communication may include, for example, wireless fidelity (WIRELESS FIDELITY, wi-Fi), wi-Fi Direct (Wi-Fi Direct), bluetooth (BT), near field communication (NEAR FIELD communication, NFC), infrared (IR), etc.

With the continuous development of terminal technology, multi-device collaboration has generated a plurality of different collaboration types (also called collaboration services), such as: multi-screen collaboration (including screen expansion, screen mirroring and screen sharing), mouse collaboration, call collaboration, connection collaboration, and the like. Wherein:

Screen mirror image: and (3) completely mirror-displaying all contents in the screen of the electronic device A in the screen of the electronic device B. The content of the electronic device a displayed in the electronic device B is the same as the content displayed by the electronic device a, and changes as the content displayed by the electronic device a changes.

Screen expansion: the screen of the electronic equipment B is used as the auxiliary screen of the electronic equipment A, the electronic equipment A can transfer part of the content to be displayed to the auxiliary screen for displaying, and the screen of the electronic equipment A and the screen of the electronic equipment B can jointly display the content, so that the display capability of the electronic equipment A is expanded.

Screen sharing: the method comprises the steps of projecting a user interface of the electronic device A into a screen of the electronic device B for display, allowing a user to operate the user interface of the electronic device A in the electronic device B, and transmitting files in the electronic device B into the electronic device A by performing specific operations in the electronic device B (such as dragging files from the user interface of the electronic device B into the user interface of the electronic device A), so as to realize cross-device operation between the electronic device A and the electronic device B, cross-device file transmission and the like. The user interface of the electronic device a may be displayed in any area of the screen of the electronic device B, or may be displayed in full screen.

Mouse and key synergy: electronic device a and electronic device B may share input devices that are native to each other, such as: a mouse, a keyboard, etc. For example, the input device of the electronic device a is shared to the electronic device B, and the shared input device may perform input in the electronic device a or the electronic device B. In addition, in the keyboard-mouse sharing type, file transfer can also be performed between the electronic device a and the electronic device B.

And (3) connection coordination: the user runs the application on the electronic device a, and the interface of the electronic device B can prompt the user to open the application running on the electronic device a on the electronic device B, so as to transfer to the electronic device B for continuous operation, such as watching video, editing documents, and the like. For example: the method comprises the steps that a document application is running on electronic equipment A, the document application can be a memo, word and the like, a user edits a document on the electronic equipment A, when the electronic equipment B is close to the electronic equipment A, prompt information is displayed on the electronic equipment B, the user clicks the prompt information on the electronic equipment B, and in response to clicking operation of the user, the electronic equipment B opens the document application and displays the editing position of the user, so that the electronic equipment B is shifted to continue editing and the like.

Conversation collaboration: when the electronic device A receives an incoming call of a voice call or a video call, an incoming call interface can be synchronously displayed on the electronic device B, so that a user can select to answer or hang up the call on the electronic device B.

Notification collaboration: when the electronic device a receives the notification message, the notification message may be synchronously displayed in the electronic device B, and may also allow the user to perform operations such as replying to, deleting, reading, etc. the notification message in the electronic device B.

The above listed collaboration types, some of which are initiated by a first electronic device (typically an initiator of multi-device collaboration) to a second electronic device (typically a participant of multi-device collaboration) in response to a user operation, may be referred to as manual collaboration services, such as screen expansion, screen sharing, keymouse collaboration, and the like. Some collaboration types are automatically triggered when a trigger rule is satisfied in a user-on function state, and may be referred to as automatic collaboration services, such as call collaboration, notification collaboration, and connection collaboration.

Taking manual collaboration services 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 non-folding screen mobile phone in the mobile phones, the second electronic device is a PC, and the supported collaboration types can comprise keyboard-mouse collaboration and screen sharing. When the non-folding screen mobile phone is connected with the PC in a first triggering mode, the default collaboration type can be screen sharing.

If the first electronic device is a folding screen mobile phone in the mobile phones, the second electronic device is a PC, and supported collaboration types can include keyboard-mouse collaboration, screen sharing, screen mirroring and screen expansion. When the folding screen mobile phone is connected with the PC in a first triggering mode, the default collaboration type can be screen sharing.

If the first electronic device is a mobile phone, the second electronic device is a large-screen device, and the supported collaboration type can comprise screen projection.

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

If the first electronic device is a tablet computer and the second electronic device is a PC, the supported collaboration types can include screen mirroring, screen expansion and mouse collaboration. When the tablet computer is connected with the PC in a first triggering manner, the default collaboration type can be a screen mirror image.

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

If the first electronic device is a PC, the second electronic device is a non-folding screen mobile phone, and the supported collaboration type can comprise keyboard-mouse collaboration and screen sharing. When the PC is connected with the non-folding screen mobile phone in a first triggering mode, the default collaboration type can be screen sharing.

If the first electronic device is a PC, the second electronic device is a folding screen mobile phone, and supported collaboration types can include keyboard and mouse collaboration, screen sharing, screen mirroring and screen expansion. When the PC and the folding screen mobile phone are connected in a first triggering mode, the default collaboration type can be screen sharing.

If the first electronic device is a PC, the second electronic device is a tablet computer, and the supported collaboration types can include screen mirroring, screen expansion and mouse collaboration. When the PC and the tablet PC are connected by first triggering, the default collaboration type may be a screen image.

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

Taking automatic collaboration services as an example:

Electronic devices supporting call collaboration may include cell phones, tablets, PCs, large screen display devices, and the like.

Electronic devices supporting notification collaboration may include cell phones, tablets, PCs, etc.

Electronic devices supporting continued collaboration may include cell phones, tablets, PCs, large screen display devices, and the like.

At present, along with the improvement of the technical requirements of users on terminals, the cooperative and unified management of multiple devices becomes a key for the development of cooperative technology. The multi-device collaborative unified management refers to that a user realizes the function of executing collaborative business establishment with different devices through a device control center interface. For example, the interface of the mobile phone equipment control center presents all other equipment which can be established with the mobile phone equipment, namely equipment A, equipment B and equipment C, and the interface of the mobile phone equipment control center can realize the cooperation of the mobile phone with the equipment A, the cooperation of the mobile phone with the equipment B and the equipment C, and the cooperation business of the equipment A and the other equipment can be terminated. Referring to fig. 1A, a schematic interface diagram of a device control center according to an embodiment of the present application is provided. The intelligent interconnection interface of the full-screen interface of the first electronic device is a control center interface of the multi-device cooperation. The interface can display a mobile phone of the first electronic device, is positioned in the center of the interface, and is wrapped by a blue (or other marks which are different from the bubble primary colors of the second electronic device) bubble. The device identification of the blister wrapped second electronic device icons of all other second electronic devices, pad, magic Book, smart TV and Pad, that can be connected to the first electronic device can also be displayed. The manner in which the collaboration is established-the drag device establishes the collaboration may also be displayed. The collaborative business establishment of the mobile phone and the pad can be realized through a dragging mode, and the collaborative business establishment of the mobile phone and the Magic Book, smart TV can also be realized.

However, in the collaborative service establishment process based on the premise of multi-device collaborative unified management, the problem of conflict of multi-device collaborative services may exist, and the collaborative services are specifically implemented that the first electronic device and the second electronic device do not have collaborative services capable of being performed, or the first electronic device and the second electronic device support collaborative services, but the collaborative services and services supported by a device combination formed by the first electronic device and the second electronic device, etc., so that the multi-device collaborative services cannot be normally established. Based on the above conflict problem, there are two general application scenarios, one is that neither the first electronic device nor the second electronic device has an ongoing collaborative service. One is that there is traffic conflict preemption, i.e. the first electronic device has an ongoing collaborative traffic, or/and the second electronic device has an ongoing collaborative traffic.

Exemplary description 1: referring to fig. 1B (10B), a schematic view of a scenario where a master-slave electronic device does not have a cross-device collaboration service, that is, a first electronic device and a second electronic device do not have an ongoing collaboration service is provided in an embodiment of the present application. The second electronic device pad and the first electronic device mobile phone have no cross-device cooperative service, namely the first electronic device and the second electronic device have no cooperative service. Exemplary description 2: referring to fig. 1C, a schematic diagram of preemption with service collision according to an embodiment of the present application is provided. The first electronic equipment mobile phone and the pad are in cross-equipment cooperative service, namely the pad and the mobile phone are in a bubble connection mode. And when the Smart TV of the second electronic device is dragged to be established with the mobile phone, the first electronic device service preemption exists.

In the method for processing the multi-device cooperative conflict provided by the embodiment of the application, the cooperative conflict exists in the device combination of the first electronic device and the second device through the service information, and the cooperative service with the multi-device cooperative service conflict is filtered, so that the multi-device cooperative service is normally established.

The method for processing the multi-device cooperative conflict can be applied to various types of electronic devices with display functions.

Referring to fig. 2, a schematic hardware structure of an electronic device according to an embodiment of the present application is shown. The device can be used as a first electronic device in multi-device cooperation or a second electronic device in multi-device cooperation. As shown in fig. 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 180, a touch sensor 190, an air pressure sensor 210, keys 220, and the like.

The processor 110 may include one or more processing units, such as: processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (IMAGE SIGNAL processor, ISP), a video codec, a digital signal processor (DIGITAL SIGNAL processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. The different processing units may be separate devices or may be integrated in one or more processors, for example, in 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 the 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, the processor 110 may include one or more interfaces. The interfaces may include an integrated circuit (inter-INTEGRATED CIRCUIT, I2C) interface, an integrated circuit built-in audio (inter-INTEGRATED CIRCUIT SOUND, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, among others.

Memory 120 may be used to store computer-executable program code that includes instructions. The memory 120 may include a stored program area and a stored data area. The storage program area may store an operating system, application programs (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. The storage data area may store data created during use of the electronic device 100 (e.g., audio data, phonebook, etc.), and so on. Further, the memory 120 may include one or more memory units, for example, may include 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.; non-volatile memory (NVM) may also be included, such as: read-only memory (ROM), flash memory (flash memory), and the like. The processor 110 performs various functional applications 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.

It should be noted that the operating system according to the embodiment of the present application includes, but is not limited to, an Android operating system, an IOS operating system, an iPad OS, a hong operating system (HarmonyOS), a Windows operating system, a Linux operating system, a MAC OS operating system, an embedded system, and the like.

The wireless communication functions 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 the electronic device 100 may be used to cover a single or multiple communication bands. In some embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution for wireless communication including 2G/3G/4G/5G applications 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), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 141, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 may amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 141 to radiate the electromagnetic waves. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be provided in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (including but not limited to speakers, headphones, etc.) or displays images or video through the display 180. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional module, independent of the processor 110.

The wireless communication module 160 may include a wireless fidelity (WIRELESS FIDELITY) module, a Bluetooth (BT) module, a GNSS module, a Near Field Communication (NFC) module, an Infrared (IR) module, and the like. The wireless communication module 160 may be one or more devices integrating at least one of the modules described above. The wireless communication module 160 receives electromagnetic waves via the antenna 141, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 141.

In an embodiment of the present application, the wireless communication functions of the electronic device 100 may include, for example, functions of the global system for mobile communications (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 (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), fifth generation mobile communication technology new air interface (5th generation mobile networks new radio,5G NR), BT, GNSS, WLAN, NFC, FM, and/or IR. The GNSS may include a global satellite positioning system (global positioning system, GPS), a global navigation satellite system (global navigation SATELLITE SYSTEM, GLONASS), a beidou satellite navigation system (beidou navigation SATELLITE SYSTEM, BDS), a quasi zenith satellite system (quasi-zenith SATELLITE SYSTEM, QZSS) and/or a satellite based augmentation system (SATELLITE BASED AUGMENTATION SYSTEMS, SBAS).

The camera 170 is used to capture still images or video. The camera 170 includes a lens and a photosensitive element, and an object is projected to the photosensitive element by generating an optical image through the lens. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, RYYB, or the like format. In some embodiments, the electronic device 100 may include 1 or N cameras 170, N being a positive integer greater than 1.

The NPU is a neural-network (NN) computing processor, and can rapidly process input information by referencing a biological neural network structure, for example, referencing a transmission mode between human brain neurons, and can also continuously perform self-learning. Applications such as intelligent awareness of the electronic device 100 may be implemented by the NPU, for example: image recognition, face recognition, speech recognition, text understanding, etc.

The display 180 is used to display images, videos, and the like. The display 180 includes a display panel. The display panel may employ a Liquid Crystal Display (LCD) CRYSTAL DISPLAY, an organic light-emitting diode (OLED), an active-matrix organic LIGHT EMITTING diode (AMOLED), a flexible light-emitting diode (FLED), miniLED, microLED, a Micro-OLED, a quantum dot LIGHT EMITTING diodes (QLED), or the like. In some embodiments, the electronic device 100 may include 1 or N display screens 180, N being a positive integer greater than 1.

The touch sensor 190 is also referred to as a "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, which is also referred to as a "touch screen". The touch sensor 190 is used to detect a touch operation acting thereon or thereabout. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to touch operations may be provided through the display 180. In other embodiments, the touch sensor 190 may also be disposed on a surface of the electronic device 100 at a different location than the display 180.

The air pressure sensor 210 is used to measure air pressure. In some embodiments, the electronic device 100 calculates altitude from barometric pressure values measured by the barometric pressure sensor 210, aiding in positioning and navigation.

The keys 220 include a power-on key, a volume key, etc. The key 220 may be a mechanical key. Or may be a touch key. The electronic device 100 may receive key inputs, generating key signal inputs related to user settings and function controls of the electronic device 100.

It should be understood that the illustrated structure of the embodiment of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the application, the electronic device may include more or less components than illustrated, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The following describes exemplary steps of the multi-device collaboration method according to the embodiment of the present application.

The software system of the electronic device 100 may employ a layered architecture, an event driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. In the embodiment of the invention, taking an Android system with a layered architecture as an example, a software structure of the electronic device 100 is illustrated.

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

The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun rows (Android runtime) and system libraries, and a kernel layer, respectively.

The application layer may include a series of application packages.

As shown in fig. 3, the application package may include applications for cameras, gallery, calendar, phone calls, maps, navigation, WLAN, bluetooth, music, video, short messages, etc.

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

As shown in FIG. 3, the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like.

The window manager is used for managing window programs. The window manager can acquire the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make such data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, etc.

The view system includes visual controls, such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, a display interface including a text message notification icon may include a view displaying text and a view displaying a picture.

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

The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like.

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

Android run time includes a core library and virtual machines. Android runtime is responsible for scheduling and management of the android system.

The core library consists of two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

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

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

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

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

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

A two-dimensional graphics engine is a drawing engine that draws two-dimensional drawings.

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

The multi-device cooperative conflict processing method is mainly applied to an application program layer of electronic equipment. The method is particularly applied to a capability layer, a service layer and a control layer of an application program layer. Referring to fig. 4, a block diagram of an application layer architecture is provided in an embodiment of the present application.

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

Wherein SystemUI provides a loading window of the drop-down status bar card, and the service status of the device on-line service can be loaded through SystemUI.

And the notification bar card is used for presenting the business state content of the state bar card.

The control center full screen interface is used for displaying the full screen UI interface.

The service application set is used for providing service use, receiving service scheduling and performing service processing. The service application set integrates collaborative services such as mouse collaboration, call collaboration, connection collaboration, navigation-following and the like, and service development kits (profile Software Development Kit, profile SDK) corresponding to the collaborative services. The profile SDK is used for writing and reading the device service management module. The device service management module is used for performing device data synchronization. The service application set can integrate other collaborative services and profile SDKs corresponding to the collaborative services. In the embodiment of the application, other cooperative services are services which meet the connection of the first electronic device and other multi-devices. In the embodiment of the application, the service layer also integrates a control center SDK for interacting with the control layer.

The control layer is used as a core module of the multi-device collaborative unified management architecture and comprises a communication module, a device management module, a service state management module, a service scheduling management module, a setting management module, a communication module SDK corresponding to the communication module, a profile SDK corresponding to the device management module and a profile SDK corresponding to the service state management module.

The communication module realizes communication of two control centers, including cross-device instruction distribution and cross-device inquiry, and is connected with the communication module of the capability layer through the communication module SDK. The communication module is also used for realizing that the control center carries out switching when the service needs to be communicated before the connection is established. If the first electronic equipment issues a connection instruction, but the equipment cannot be initiated and needs to be initiated by the second electronic equipment, the instruction is established by the second electronic equipment.

The device management module is used for acquiring the online and offline information, the capability information, the service state and the like of the device which is in the same account as the first electronic device from the device service management module in real time through the profile SDK. The device management module includes an online device, connection status management, and a set of all device capabilities. The online equipment is used for inquiring the current online equipment, the connection state management is used for inquiring whether the current equipment is connected or not, whether the current equipment can be connected or not, and all equipment capability sets are used for intensively acquiring a plurality of equipment states of all equipment. Wherein the device status includes device on-line and off-line information, capability information, service status, etc.

The service state management module is used for reading service information supported by the first electronic device and the peripheral online device from the device service management module in real time through the Profile SDK, such as a service capability list supported by the application, a service switch, whether a service can be scheduled by the control center, a specific service supporting device type, a specific service supporting connection scheme, a current service running state and the like. The service state management module comprises a service set of the equipment and service state management. The service set of the device inquires the service set supported by the device, and the service state management is used for inquiring the service state supported by the online device, receiving the change update state of the external service state and synchronizing the change update state to the control center display interface.

The service scheduling management module is used for judging service conflict, sending a prompt to a user, and issuing a service instruction according to the user intention, namely, carrying out service connection, switching and disconnection according to user selection and service conflict callback service. The service scheduling management module comprises service conflict scheduling and service connection management. Wherein traffic collision scheduling is used for collision handling. For example, the mobile phone supports screen projection, the pad supports screen projection, but the mobile phone and the pad cannot coexist due to notification limitation, and service conflict scheduling is needed to process service conflict. The service connection management is used for managing whether the multi-device has cooperative service or not and whether the multi-device can be connected or not.

The setting management module is used for managing relevant settings of the control center, including mode settings and the like.

The capability layer comprises the same account discovery, old service discovery compatibility and connection transmission of the communication module, and is used for realizing equipment connection establishment, transmission and discovery. The capability layer also comprises a device service management module, which is used for realizing device Data synchronization, such as device Data synchronization of on-line and off-line information, capability information, service state and the like, and storing the device Data synchronization in a Data storage control Data Controller of the Data layer for mode persistence storage.

In addition, the embodiment of the application also provides a cooperative work system, which comprises the first electronic equipment and the second electronic equipment. The specific structure of the first electronic device is shown in fig. 2, and the specific structure of the second electronic device is shown in fig. 2, which is not described herein.

In order to better explain the method for processing the multi-device collaboration conflict, firstly, an implementation timing diagram of service establishment based on multi-device collaboration unified management is introduced.

Referring to fig. 5, a timing diagram for implementing service establishment based on multi-device collaborative unified management is provided in an embodiment of the present application. The method specifically comprises the following steps:

The service scheduling management module responds to the user to execute the connection establishment operation of the first service of the equipment combination, inquires service information from the service state management module, and judges the connection mode of the first service according to a preset conflict rule. And determining a service establishment result according to the connection mode of the first service.

In the embodiment of the application, the equipment combination is a combination of the first electronic equipment and the second electronic equipment. The first service is a service cooperatively performed by the first electronic device and the second electronic device. And when the user operates in a mode of dragging the second electronic equipment of the control center interface and the like, the method is used for executing the business linking operation of the main second electronic equipment. The service scheduling management module acquires a service scheduling instruction which is sent by the Control view and requests the service, and sends a service state query instruction to the service state management module to acquire the service information of the first electronic equipment and the service information of the second electronic equipment. The service information comprises at least one of service names supported by the device, service scheduling types, ongoing collaborative services or device combination types supported by the service. And the service scheduling module determines the connection mode of the first service according to a preset conflict rule. In the embodiment of the application, the connection mode of the first service comprises a connection disallowing mode, a connection allowing mode and a conflict preemption mode. And determining a service establishment result according to the connection mode of the first service.

Specifically, when the connection mode of the first service is the connection mode not allowed (principle 1), the communication module performs control center interface popup processing, so that the control center interface popup cannot establish the connection identifier.

When the connection mode of the first service is the allowed connection mode (principle 2), it is determined whether a cross-device service communication establishment is required, that is, whether connection through communication modules of different devices is required. If the service scheduling management module sends a command for establishing the cross-equipment service communication to the service scheduling management module, the service scheduling management module realizes the communication module communication of the two-end equipment through the scheduling of the control center, such as information interaction, service initiation and the like, so that the main second electronic equipment cooperates with the service to establish the service. If not, the control center SDK directly builds the business. The Data Controller of the Data layer records the current established connection service state. When the next time of establishing the connection, the service state of the current time of establishing the connection is optimized. And meanwhile, the control center SDK updates the service state change to the equipment service management module, or the control center SDK informs the service state management module to update in a broadcasting mode.

When the connection mode of the first service is a conflict preemption mode, wherein the conflict preemption mode is at least one of that the first electronic device has an ongoing service or that the second electronic device has an ongoing service. Firstly, changing the service state to a device service management module, or informing the service state management module to update in a broadcast mode, determining that the first service is allowed to be connected according to a preset conflict rule, and establishing connection of the first service according to the processing mode of principle 2. The specific processing is shown with reference to fig. 6 and 7A-7B below and will not be discussed here. If the service schedule management module determines that schedule establishment can be performed, the specific implementation is described in the previous section of principles 2, which is not discussed here.

Referring to fig. 6, a flowchart of a conflict processing method is provided in an embodiment of the present application. The method comprises the following steps:

S101: and reading service information of the first electronic equipment and the peripheral online equipment.

The service status management module may read the first electronic device service information and the peripheral online device service information from the device service management module.

Table 1 device service information table

Referring to table 1, the device service information provided in the embodiment of the present application is provided. The method comprises the steps of supporting a service list, namely a service name supported by equipment, a service switching state, whether the service can support control center scheduling (namely a service scheduling type), a device form supported by the service (namely a service supported equipment combination type), a physical channel supported by the service, a current running state of the service (namely an ongoing cooperative service), and a currently used physical channel.

S102: and performing interaction between the first electronic device and the second electronic device, and establishing a device combination.

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

S103: and judging whether the equipment combinations are in a no-service state. If yes, S105 is executed, and if no, S104 is executed.

In the embodiment of the application, whether the equipment combination is in a no-service state or not is judged, namely whether the first electronic equipment and the second electronic equipment are in cooperative service with other equipment is judged. And if the first electronic equipment and the second electronic equipment are in a no-service state, namely the current main second electronic equipment and other equipment are not establishing cooperative service. If the first electronic device and the second electronic device are in a service state, it means that the first electronic device and the other devices are establishing a cooperative service, or the second electronic device and the other devices are establishing a cooperative service.

S104: it is determined whether the device combinations can all be scheduled. If the traffic can be scheduled, S105 is performed. Otherwise, S115 is performed.

And when at least one end device in the first electronic device and the second electronic device is carrying out cooperative service with other devices, judging whether the current service can be scheduled by the control center. Exemplary description:

Table 2 service schedule schematic table

Table 2 is a schematic service scheduling table provided in the embodiment of the present application, which is a memory table of a control center, and indicates whether a cooperative service can be scheduled by the control center. Where 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 description: if the PC and the flat panel are in cooperative service A, two flat panel device cooperative services are established, the current service cooperative service A cannot be scheduled by other flat panels through the control center of the flat panel. At this time, one end device is performing cooperative service with other devices, and the current service cannot be scheduled by the control center. If the cooperative service of the PC and the folding screen is established, the current service cooperative service A can be scheduled by the control center. Those skilled in the art will note that the traffic scheduling schematic is only illustrative and is not limited to these few features, supporting all multi-device features.

S105: and judging whether the equipment combination has a service intersection, if so, executing S106. Otherwise, S115 is performed.

Exemplary description: the first electronic device has wireless screen-throwing service, and the second electronic device also has wireless screen-throwing service, which indicates that the device combination has service intersection. For example, a first electronic device has a wireless screen-cast service, and a second electronic device has screen-mirror, screen-expansion, and screen-mirror services, indicating that the device combination does not have a service intersection.

S106: and judging whether the equipment combination is matched. If yes, S107 is performed. Otherwise, S115 is performed.

Exemplary description: and assuming the current service is notification collaboration, and the electronic equipment supporting the notification collaboration is a mobile phone, a tablet and a PC. If the first electronic device is a mobile phone, the second electronic device is a large-screen display device, and the combination of the devices is not matched. If the first electronic device is a mobile phone, the second electronic device is a tablet, and the device combination is matched.

S107: and obtaining an available service list to be triggered.

In the embodiment of the application, the service list to be triggered refers to collaborative services supported by the first electronic device and the second electronic device. As shown in table 2, the folding screen and the PC have a collaboration service a and a collaboration service B, and the two collaboration services are stored in a list form.

S108: the reading device combines the last service record.

S109: and if no record exists, reading the default priority from the preset service priority, and triggering the service according to the default priority. There is a record, and the service is triggered according to the last record.

If the first electronic equipment and the second electronic equipment establish the cooperative service, the data storage center records the connection mode of the last first service. When the service is used, the last service state can be queried, and the last service state is utilized to establish the cooperative service. If the last service is not available, that is, the first electronic device and the second electronic device are the first to establish the collaborative service, 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 multiple collaboration services exist in the device, for example, a folding screen (unfolding) and a PC exist a mobile phone and PC collaboration service B, a tablet and PC collaboration service A is provided, and the preset mobile phone and PC collaboration service B has a higher priority than the tablet and PC collaboration service A, namely, the triggering service is the mobile phone and PC collaboration service B.

S110: and judging whether the first electronic equipment and the second electronic equipment currently have mutual exclusion service or not. If the exclusive service does not exist, S115 is executed. Otherwise, S111 is performed.

In the embodiment of the application, whether the main second electronic equipment currently has the mutual exclusion service or not refers to whether the service in the running process of the cross-equipment and the cooperative service of the first electronic equipment and the second electronic equipment can coexist or not. For example, the mobile phone and the PC are in collaboration with the service B, and if the mobile phone and the tablet collaboration service a, such as the navigation-related service, is established, the mobile phone and the tablet collaboration service a and the mobile phone and the PC collaboration service B have mutual exclusion and cannot coexist.

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

And setting and inquiring whether the user terminates the service prompt box of the current equipment and starts a new service prompt box at the interface of the control center. If the user selects to terminate the cooperative service of the current device to establish a new cooperative service, a stop instruction is issued to the devices with the services at both ends, and after stopping operation is completed, an instruction for establishing the new service is issued.

In addition, in the embodiment of the application, the prompt box also provides the user with a choice of no-prompt any more, and if the user chooses to no-prompt any more, the inquiry of 'interrupt current prompt' is no longer popped up to the user. If the user does not select whether to 'no longer prompt', the subsequent corresponding scene needs to continue to query the user for operation.

S112: and obtaining a user confirmation result.

S113: and when the user confirms to terminate the current equipment service, terminating the current service of the first electronic equipment and the second electronic equipment.

S114: and issuing a scheduling instruction, and establishing a target service between the first electronic equipment and the second electronic equipment.

S115: no service trigger and popup prompt.

In the method for processing multi-device collaboration conflict provided by the embodiment of the application, the service states of the first electronic device and the second electronic device are acquired through the second electronic device service management module, whether the first electronic device and the second electronic device have cross-device collaboration services or not is judged, whether the ongoing cross-device collaboration services can be scheduled by the control center or not is judged, whether the service intersection of the first electronic device and the second electronic device and the supported device types are matched or not, whether mutual exclusion exists or not is judged, and the collaboration services which have no collaboration services or have service preemption are filtered. And enabling the multi-equipment cooperative service to normally establish the connection.

In the following, the Android device is taken as an example, and specific implementation of the multi-device cooperative conflict processing method provided by the embodiment of the application is described in detail. Referring to fig. 7A-7B, an interaction timing diagram for processing a multi-device cooperative service conflict is provided in an embodiment of the present application. The method specifically comprises the following steps:

S31: the equipment state management module and the business state management module the second electronic equipment service management module reads the business state of the first electronic equipment and the business list supported by the first electronic equipment, and reads the business state of the peripheral online equipment and the business list supported by the second electronic equipment.

The device state management module sends a request first electronic device business state instruction to the device service management module. And the device service management module returns the service state of the first electronic device and the support service list to the service state management module. The device management module sends a device state instruction for requesting to read the peripheral online device to the device service management module, and the second electronic device service management module obtains the device state of the peripheral online device. And meanwhile, the equipment management module sends a service state instruction for inquiring and registering the peripheral equipment to the service state management module. After receiving the notification and inquiry of the service state instruction of the peripheral equipment, the service state management module sends an instruction for reading the service state of the peripheral online equipment to the equipment service management module, and the second electronic equipment service management module acquires the service state of the peripheral online equipment and a service list supported by the second electronic equipment.

S32: and the service conflict scheduling responds to the operation of executing the service establishment of the main second electronic equipment by the user, and acquires the service states and the support service lists of the first electronic equipment and the second electronic equipment from the service state management module.

When the user operates the Control view through a drag Control center interface and the like, namely the user executes the business linking operation of the main second electronic equipment, the equipment business conflict query is triggered. The service conflict scheduling acquires a service conflict inquiry instruction of the trigger equipment, sends an inquiry main second electronic equipment service state and a service support list instruction to a service state management module, and acquires a first electronic equipment service state and a service support list and a second electronic equipment service state and a service support list from the service state management module.

S33: and the service conflict scheduling responds to the fact that the current service with at least one end cannot be scheduled in the first electronic equipment and the second electronic equipment, and sends an instruction that the current service with at least one end cannot be scheduled to the Control View, and the Control center interface prompts the user that the connection instruction is not allowed currently, so that the flow is ended. The traffic conflict schedule performs S34 in response to the current traffic of the first electronic device and the second electronic device being scheduled or no traffic.

And judging whether the current business of at least one end of the first electronic equipment and the second electronic equipment cannot be scheduled or not by business conflict scheduling. That is, at least one end of the first electronic device and the second electronic device has an ongoing cooperative service with other devices, and the cooperative service cannot be scheduled. As described in table 2 above, if the PC and the tablet are performing the collaboration service a, and two tablet device collaboration services are established, the current collaboration service a cannot be scheduled by other tablets through the control center of the tablet. At this time, one end device is performing cooperative service with other devices, and the current service cannot be scheduled by the control center.

When the service conflict scheduling obtains the condition that the current service of at least one end of the main second electronic equipment cannot be scheduled, a current service non-scheduled instruction with at least one end is sent to the Control View, and the Control center interface prompts the user that the connection instruction is not allowed currently. In one possible implementation, the control center interface displays a prompt dialog, the prompt being unable to be established. Exemplary description: fig. 8 is a schematic diagram of a connection failure establishment notification according to an embodiment of the present application. The first electronic device handset and the magic book are doing collaborative services, and the user drags smartTV, because the current business cannot be scheduled when the first electronic device handset is currently doing, the "Smart Internet" interface display prompt dialog "smartTV does not allow for establishing a connection with the handset. In another possible implementation, the control center interface pops up the second electronic device directly. The embodiment of the application does not limit the prompt that the connection cannot be established.

S34: the service conflict scheduling checks that the service states of the first electronic device and the second electronic device are open service intersections. And the service conflict scheduling responds to the fact that the first electronic equipment and the second electronic equipment do not have service intersection, a no-service intersection instruction is sent to the Control View so as to Control the Control center interface to prompt the user that connection is not allowed currently, and the flow is ended. When the traffic conflict schedule is responsive to the first electronic device and the second electronic device having a traffic intersection, S35 is performed.

S35: and the service conflict scheduling responds to the fact that the device type supported by the cooperative service is not matched with the current device combination, a command that the two ends do not support to establish new service is sent to the Control View, and the Control View Control center interface prompts the user that the connection is not allowed currently, so that the flow is ended. The service conflict scheduling performs S36 in response to the device type supported by the collaborative service matching the current device combination.

S36: and the service conflict scheduling combines the last service record from the Data Controller reading equipment, and when the last record does not exist, the service establishment with the highest preset priority is selected.

And the service conflict scheduling sends a reading device combination last service record instruction to the Data Controller, and the Data Controller returns the stored last service record. And if the last record does not exist, the service conflict scheduling selects the service with the highest priority from the preset priority table to carry out service establishment.

S37: when the equipment combination currently has the mutual exclusion service and no prompt dialog box is set, the service conflict scheduling sends a request user confirmation instruction to the Control View to confirm whether to terminate the current equipment service, start a new service, reject the user, and return a flow end instruction to the service conflict scheduling to end conflict processing.

Exemplary description: fig. 9 is a schematic diagram of a prompt box for requesting user confirmation according to an embodiment of the present application. When the user clicks the reject mark, the reject mark indicates that the user rejects, and the control center interface displays a prompt box which does not allow connection.

Notably, when the current device combination user confirms to terminate the current device service, or the control center interface is set to be no longer prompted, a new service is started, and S38 is executed.

If the current device combination does not have mutually exclusive services, S39 is performed directly.

S38: and the service conflict scheduling sends a notification to the service connection management to send out a current service stopping instruction, and acquires a current service stopping result.

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

When the mutual exclusion service exists in the equipment, the mutual exclusion service exists in the second electronic equipment, and the service connection management sends a service termination instruction to the second electronic equipment through the first electronic equipment control layer communication module, the capability layer communication module, the second electronic equipment capability layer communication module and the control layer communication module. And stopping the current mutual exclusion service of the second electronic equipment by the SDK of the second electronic equipment, and returning the capability layer communication module to the service connection management through the second electronic equipment capability layer communication module, the control layer communication module and the first electronic equipment control layer communication module. And the service connection management sends a service stopping result to the service conflict scheduling.

S39: and the service conflict scheduling sends a new service establishment instruction to the service connection management, and the service connection management control center SDK sends a scheduling instruction to establish cooperative service with the second electronic equipment.

Exemplary description 1: referring to fig. 10, a schematic diagram of a connection establishment of a primary second electronic device without cooperative service is provided in an embodiment of the present application. The first electronic equipment mobile phone is other Android mobile phones, and the second electronic equipment is a notebook. Neither the first electronic device nor the second electronic device has ongoing cross-device traffic. And the first electronic device and the second electronic device have no coordinated service. And dragging the notebook to a distance within a preset range from the mobile phone, and directly rebounding the notebook. Namely, the mobile phone and the notebook can not establish cooperative service.

Exemplary description 2: referring to fig. 11, a schematic diagram of establishment of an ongoing cross-device service exists in a second electronic device according to 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 carrying out cross-device screen mirroring service. The screen mirroring service may be scheduled by the handset control center. The mobile phone and the notebook have a service intersection, and the cooperative service to be performed supports the equipment combination of the mobile phone and the notebook. But the collaborative service to be established is mutually exclusive with the ongoing screen image service. Dragging the notebook to a position within a preset distance range from the mobile phone, and displaying a prompt box on a control center interface to prompt a user whether to terminate the current equipment service. The user clicks "reject" and directly rebounds the notebook.

The multi-device cooperative conflict processing method provided by the embodiment of the application can be used for processing non-cooperative service existing in the service establishment process based on multi-device cooperative unified management and the service preemption problem of the main second electronic device. And filtering out non-cooperative traffic. Aiming at the problem of service preemption of the main second electronic equipment, under the condition that the main second electronic equipment is determined to have cooperative service, different treatments are carried out aiming at whether the main second electronic equipment has mutual exclusion or not. So that the cooperation of multiple devices can be normally established.

From the foregoing description of the embodiments, it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of functional modules is illustrated, and in practical application, the above-described functional allocation may be implemented by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to implement all or part of the functions described above. The specific working processes of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which are not described herein.

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 embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical functional division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present embodiment may be integrated in one processing unit, each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present embodiment may be essentially or a part contributing to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the method described in the respective embodiments. And the aforementioned storage medium includes: flash memory, removable hard disk, read-only memory, random access memory, magnetic or optical disk, and the like.

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

Claims

1.A 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;

When the equipment combination has cooperative conflict, determining that the equipment combination cannot perform cooperative service;

When the equipment combination does not have cooperative conflict, triggering the equipment combination to perform cooperative operation of a first service based on a preset service priority rule; when at least one electronic device is in cooperative service on the device combination, judging whether the first service can be executed together with all the devices in the device combination in cooperative service;

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.

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:

5. The method of claim 1, 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.

6. The method according to claim 1, 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.

7. The method of claim 5, 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.

8. 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 and ongoing collaborative services or equipment combination types supported by the services;

when the first electronic equipment judges that the equipment combination does not have cooperative conflict, the first electronic equipment triggers the equipment combination to perform cooperative operation of a first service based on a preset service priority rule; when at least one electronic device is in cooperative service on the device combination, the first electronic device judges whether the first service can be executed together with all the devices in the device combination in cooperative service;

If the first service and the second service can be jointly executed, the first electronic equipment executes the cooperative operation of the first service of the equipment combination; and if the first electronic equipment cannot execute the first service jointly, determining all the collaborative services which cannot execute the first service jointly from all the collaborative services which are executed by at least one electronic equipment in the equipment combination, and when a user terminates all the collaborative services which cannot execute the first service jointly, executing the collaborative operation of the first service by the first electronic equipment.

9. The method of claim 8, 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.

10. The method of claim 9, 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.

11. The method of claim 9, 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:

12. The method of claim 9, 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.

13. 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-7.

14. 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 8-12.

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