CN116679895B

CN116679895B - Collaborative business scheduling method, electronic equipment and collaborative system

Info

Publication number: CN116679895B
Application number: CN202211321621.0A
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-07
Anticipated expiration: 2042-10-26
Also published as: CN116679895A

Abstract

A scheduling method of cooperative service, electronic equipment and a cooperative system are applied to the technical field of terminals. The method comprises the following steps: when a user executes on the first electronic equipment, the scheduling operation of the first cooperative service of the first electronic equipment and the second electronic equipment is obtained, and whether the first electronic equipment is responsible for executing the scheduling operation instruction is judged. When the first electronic equipment is responsible for executing the scheduling operation instruction, the scheduling operation instruction is directly executed, and when the first electronic equipment is not responsible for executing the scheduling operation instruction, the scheduling operation instruction is sent to the second electronic equipment, so that the second electronic equipment executes the scheduling operation of the first collaborative service. In this way, the scheduling operation instruction of the cooperative service is initiated for different devices, one end of the double-end device of the cooperative service executes the operation of the first electronic device, and the other end executes the operation of the second electronic device, so that the scheduling operation instruction initiated by different electronic devices is realized, a set of processing logic is shared, and the complexity and maintenance difficulty of the scheme are reduced.

Description

Collaborative business scheduling method, electronic equipment and collaborative system

Technical Field

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

Background

The multi-device collaboration technology is a distributed technology applied to a plurality of 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. In order to enable the double-end equipment of the cooperative service to conveniently perform the scheduling operation of the cooperative service, such as connection and disconnection of the cooperative service, a control center is deployed at the equipment terminal of each equipment so as to perform scheduling processing on the cooperative service through the control center.

However, the dual-end device of the collaborative service has a different role in the overall service process of the collaborative service. One electronic device performs the scheduling operation and the other electronic device does not perform the scheduling operation. Therefore, when the double-end equipment is expected to execute the scheduling operation in the control center deployed by the equipment, different implementation schemes are needed, so that the design complexity of the scheme is high, and the maintenance difficulty is high.

Disclosure of Invention

The application aims at: the application provides a cooperative service scheduling method, electronic equipment and a cooperative system, and aims to design a shared cooperative service scheduling method in a control center of double-end equipment of cooperative service, realize that any one end of the double-end equipment initiates a cooperative service scheduling instruction and share a set of scheme, so that the design complexity and maintenance difficulty of the scheme are reduced.

In a first aspect, the method for scheduling collaborative services provided by the application is applied to a first electronic device. The method comprises the following steps:

When a user executes on the first electronic equipment, scheduling operation of a first collaborative service of the first electronic equipment and the second electronic equipment is performed, and a scheduling operation instruction is obtained; judging whether the first electronic equipment is responsible for executing the scheduling operation instruction or not; when the first electronic equipment is responsible for executing the scheduling operation instruction, executing the scheduling operation instruction to perform the scheduling operation of the first collaborative service; and when the first electronic equipment is not responsible for executing the scheduling operation instruction, the scheduling operation instruction is sent to the second electronic equipment, so that the second electronic equipment executes the scheduling operation instruction to perform scheduling operation of the first collaborative service.

For example, when a mobile phone is used for projecting a screen to a flat pad, a user acquires a scheduling operation instruction of projecting the screen in a mode of dragging and the like at a mobile phone terminal control center. And presetting a screen throwing instruction in the control center, if the screen throwing instruction is not the pad, the first electronic equipment is not responsible for executing the screen throwing instruction. And sending the scheduling operation instruction to the pad, and carrying out the cooperative operation of the first cooperative service through the pad. And when a user acquires a scheduling operation instruction of screen throwing in a mode of dragging and the like at the pad end control center. The first electronic device is a pad and is responsible for executing the scheduling operation instruction, and directly executing the scheduling operation instruction. Thus, by initiating the scheduling operation instruction of the cooperative service to the different devices, one end of the double-end device of the cooperative service executes the operation of the first electronic device, and the other end executes the operation of the second electronic device, thereby realizing that the different electronic devices initiate the scheduling operation instruction, sharing one set of processing logic, and further reducing the complexity and maintenance difficulty of the scheme.

In one possible implementation manner, according to a pre-configured reference electronic device for executing the scheduling of the first collaborative service, whether the first electronic device is one of the reference electronic devices is determined, so as to determine whether the first electronic device is responsible for executing the scheduling operation instruction.

In one possible implementation manner, when the first electronic device is not responsible for executing the scheduling operation instruction, the scheduling operation instruction is sent to the second electronic device through a communication channel between the first electronic device and the second electronic device; the communication channel is used for realizing instruction transmission of the first electronic device and the second electronic device.

In one possible implementation manner, when the second electronic device receives the scheduling operation instruction and determines that the second electronic device executes the scheduling operation instruction, a request instruction sent by the second electronic device is received; the request instruction is used for sending an operation corresponding to the scheduling operation instruction to be executed to the first electronic equipment; and determining an instruction for executing the scheduling operation by the second electronic equipment according to the request instruction, so that the second electronic equipment executes the scheduling operation instruction to perform the scheduling operation of the first collaborative service. Therefore, the scheduling result can meet the user requirements by informing the user whether the execution mode is executed by the opposite terminal equipment.

In one possible implementation, according to the request instruction, it is determined that the instruction of the scheduling operation cannot be executed by the second electronic device, and the scheduling operation of the first collaborative service is not performed.

In one possible implementation manner, when a user performs a scheduling operation of a first collaborative service on a second electronic device, the second electronic device obtains a scheduling operation instruction, and determines whether the second electronic device is responsible for executing the scheduling operation instruction; when the second electronic equipment is determined not to be responsible for executing the scheduling operation instruction, receiving the scheduling operation instruction sent by the second electronic equipment, and executing the scheduling operation instruction so as to perform scheduling operation of the first collaborative service; and when the second electronic equipment is determined to be responsible for executing the scheduling operation instruction, executing the scheduling operation of the first collaborative service from the second electronic equipment. When a user executes scheduling operation on the control center interface of the second electronic equipment, the scheduling operation still meets the requirement of sharing one set of processing logic with the first electronic equipment, so that the complexity of the scheme and the maintenance difficulty can be reduced.

In a second aspect, the present application provides a method for scheduling a collaboration service, which is applied to a second electronic device. The method comprises the following steps:

When a user executes scheduling operation of a first cooperative service of the first electronic device and the second electronic device on the first electronic device, the first electronic device acquires a scheduling operation instruction, and the first electronic device judges whether the first electronic device is responsible for executing the scheduling operation instruction according to the scheduling operation instruction; when the first electronic equipment is determined not to be responsible for executing the scheduling operation instruction, receiving the scheduling operation instruction sent by the first electronic equipment, and executing the scheduling operation instruction to perform scheduling operation of the first collaborative service; and when the first electronic equipment is determined to be responsible for executing the scheduling operation instruction, executing the scheduling operation of the first collaborative service from the second electronic equipment.

For example, when a mobile phone is used for projecting a screen to a flat pad, a user acquires a scheduling operation instruction of projecting the screen in a mode of dragging and the like at a mobile phone terminal control center. And presetting a screen throwing instruction in the control center, if the screen throwing instruction is not the pad, the first electronic equipment is not responsible for executing the screen throwing instruction. And sending the scheduling operation instruction to the pad, and carrying out the cooperative operation of the first cooperative service through the pad. And when a user acquires a scheduling operation instruction of screen throwing in a mode of dragging and the like at the pad end control center. The first electronic device is a pad and is responsible for executing the scheduling operation instruction, and directly executing the scheduling operation instruction. In this way, the scheduling operation instruction of the cooperative service is initiated for different devices, one end of the double-end device of the cooperative service executes the operation of the first electronic device, and the other end executes the operation of the second electronic device, so that the scheduling operation instruction initiated by different electronic devices is realized, a set of processing logic is shared, and the complexity and maintenance difficulty of the scheme are reduced.

In one possible implementation manner, the first electronic device performs an operation of determining whether the first electronic device is one of the reference electronic devices according to a pre-configured reference electronic device performing scheduling of the first collaborative service, so as to determine whether the first electronic device is responsible for performing the scheduling operation instruction.

In one possible implementation manner, when the first electronic device is not responsible for executing the scheduling operation instruction, receiving the scheduling operation instruction sent by the first electronic device through a communication channel between the first electronic device and the second electronic device;

the communication channel is used for realizing instruction transmission of the first electronic device and the second electronic device.

In one possible implementation manner, when the second electronic device receives the scheduling operation instruction and determines that the second electronic device executes the scheduling operation instruction, acquiring a request instruction; the request instruction is used for sending an operation corresponding to the scheduling operation instruction to be executed to the first electronic equipment; and sending the request instruction to the first electronic equipment, receiving the instruction of executing the scheduling operation by the second electronic equipment, and executing the scheduling operation instruction to perform the scheduling operation of the first collaborative service. Therefore, the scheduling result can meet the user requirements by informing the user whether the execution mode is executed by the opposite terminal equipment.

In one possible implementation, an instruction is received that a scheduling operation cannot be performed by the second electronic device, and the scheduling operation of the first collaborative service is not performed.

In one possible implementation manner, when a user executes on the second electronic device, a scheduling operation instruction is obtained for a scheduling operation of a first cooperative service of the first electronic device and the second electronic device; judging whether the second electronic equipment is responsible for executing the dispatching operation instruction or not;

when the second electronic equipment is responsible for executing the scheduling operation instruction, executing the scheduling operation instruction to perform scheduling operation of the first collaborative service; and when the second electronic equipment is not responsible for executing the scheduling operation instruction, the scheduling operation instruction is sent to the second electronic equipment, so that the second electronic equipment executes the scheduling operation instruction to perform the scheduling operation of the first collaborative service. When a user executes scheduling operation on the control center interface of the first electronic equipment, the scheduling operation still meets the requirement of sharing one set of processing logic with the second electronic equipment, so that the complexity of the scheme and the maintenance difficulty can be reduced.

In a third aspect, the present application provides an 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 the first aspects.

In a fourth aspect, the present application provides an 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 the second aspects.

In a fifth aspect, the present application provides a collaboration system comprising the electronic device of the third aspect and the electronic device of the third 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. 1 is a schematic diagram of a scheduling method for mobile phone screen-throwing to a tablet 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 illustrating an architecture of an application layer according to an embodiment of the present application;

fig. 5A is a logic architecture diagram implemented by a cooperative service scheduling method according to an embodiment of the present application;

fig. 5B is a scheduling timing diagram of a cooperative service according to an embodiment of the present application;

FIG. 6A is a timing diagram of a mobile phone screen-on-pad scheduling according to an embodiment of the present application;

FIG. 6B is a schematic diagram of a service association display result of a mobile phone screen-cast to pad according to an embodiment of the present application;

Fig. 7 is a scheduling timing diagram of another mobile phone screen-throwing to pad 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: screen expansion, screen throwing, mouse cooperation and the like. Wherein:

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 throwing: 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.

In order to enable the double-end equipment of the cooperative service to conveniently perform the scheduling operation of the cooperative service, a control center is deployed at the equipment terminal of each equipment so as to perform scheduling processing on the cooperative service through the control center. Referring to fig. 1, a schematic diagram of a method for scheduling a mobile phone to be screen-projected to a tablet is provided in an embodiment of the present application. The collaborative service is screen throwing, the double-end equipment of the collaborative service is a mobile phone and a tablet, and the mobile phone and the tablet are provided with a control center. The left side of the figure 1 is a control center deployed at a tablet end, and the right side of the figure 1 is a control center deployed at a mobile phone end. The control center arranged at the mobile phone end is provided with a mobile phone 11 identifier wrapped by a blue small ball, the connectable equipment comprises a large screen display device 12, a flat plate 13, a notebook computer 14 and a mobile phone 15 different from the mobile phone 11 of the main equipment, and the equipment identifier of the connectable equipment is wrapped by a white small ball. The main equipment of the control center deployed at the tablet end is a tablet 13 mark wrapped by a blue small ball, the connectable equipment is a large-screen display equipment 16, a mobile phone 11, a notebook computer 17 and a tablet 18, and the equipment mark of the connectable equipment is wrapped by a white small ball. Wherein the tablet 18 is a different device than the tablet 13, and 16 and 12 may be the same large screen display device or different large screen display devices. 17 and 14 may be the same notebook computer or may be different notebook computers.

When the mobile phone 11 is connected to the tablet 13, the mobile phone 11 hopes to trigger the connection operation of the mobile phone 11 to the tablet 13 at the control center deployed at the terminal of the device, for example, the connection operation of the mobile phone 11 to the tablet 13 is triggered by dragging (indicated by the arrow in the drawing) the mobile phone 11 to a position within a preset distance range from the tablet 13. The tablet 13 is desirably disposed in the control center of the terminal of the present application, and triggers a connection operation of the mobile phone 11 for projecting the screen onto the tablet 13, for example, on the right side of fig. 1, and the tablet 13 is dragged (shown by an arrow in the drawing) to a position within a preset distance range from the mobile phone 11 by a dragging manner, so as to trigger a connection operation of the mobile phone 11 for projecting the screen onto the tablet 13. In the whole service realization process of screen throwing, roles of the mobile phone 11 and the tablet 13 are different, and the roles are also different. The cell phone 11 does not perform the scheduling operation and the tablet 13 performs the scheduling operation. Therefore, if the mobile phone 11 is to be connected to the tablet 13, the logic of the left side of fig. 1 is different from that of the right side of fig. 1, and different implementation schemes are required, resulting in high design complexity and high maintenance difficulty.

Aiming at the problems, the application provides a scheduling method of cooperative service, which aims to design a shared scheduling method of cooperative service for a control center of double-end equipment of the cooperative service, and realize that any end of the double-end equipment initiates scheduling instructions of the cooperative service, and all the two ends share a set of scheme, so that the design complexity and maintenance difficulty of the scheme are reduced.

The collaborative business scheduling method provided by the embodiment of the application can be applied to various types of electronic equipment with a display function.

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 master device in multi-device cooperation or a slave 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 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, map, navigation, WLAN, bluetooth, voice-over-device collaboration applications, and the like.

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 scheduling method of the collaborative business of the embodiment of the application 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 business layer comprises a control center display interface and a business application set. The control center interface is a human-computer interaction interface and is used for displaying a multi-device collaborative interaction interface, and the multi-device collaborative interaction interface comprises a system interface (System User Interface, systemUI), a notification bar card and a control center full-screen interface.

SystemUI provide a loading window for drop-down status bar cards through SystemUI to load the service status of the device's online service.

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, multi-screen collaboration 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 main equipment and other multi-equipment. 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 master device issues a connection instruction, but the device cannot initiate, and needs to initiate from the slave device, the connection instruction is established by the slave device. The communication management module has communication transmission capability, such as a Bluetooth channel, a network channel, a p2p direct connection channel and the like.

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 main 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 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 main equipment and the peripheral online equipment in real time from the equipment service management module through the Profile SDK, such as a service capability list supported by the application, a service switch, whether the service can be scheduled by the control center, a specific service supporting equipment 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 peripheral 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 of communication transmission, the compatibility of old service discovery and connection transmission, 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.

The following describes the scheduling method of the cooperative service in detail with reference to the specific drawings. First, an architecture diagram of a collaboration system for collaboration services provided by an embodiment of the present application is described.

Referring to fig. 5A, a logic architecture diagram implemented by a cooperative service scheduling method is provided in an embodiment of the present application. The implementation logic architecture diagram includes a device 1 and a device 2.

The equipment terminals of the equipment 1 and the equipment 2 are deployed with the same control center, and each control center comprises a service layer, a control layer and a capability layer. The service layers of the device 1 and the device 2 each comprise two services, distributed as service 1 and service 2. In the embodiment of the present application, the service 1 and the service 2 are services that can be cooperated by the device 1 and the device 2. Although not illustrated in the drawings, other collaborative services may be included as well, as in fig. 4. The control centers of the control layers of the device 1 and the device 2 each include a service status management module, a service scheduling management module, a communication module SDK, and the like, which are respective modules of the control layer shown in fig. 4. The capability layers of the device 1 and the device 2 are used for realizing capability reporting and communication transmission functions, and comprise a device service management module and a communication module shown in fig. 4.

When triggering the scheduling operation of triggering the service 2 of the equipment 1 and the equipment 2, the service scheduling management module of the equipment 1 or the equipment 2 issues a scheduling instruction to the service 2 of the service layer, and the service 2 judges whether the equipment end of the application can process the scheduling operation of the service 2. If the processing can be performed, the scheduling operation of the scheduling service 2 is triggered similarly to the control center of the slave device 2, and the scheduling operation of the service 2 is directly performed based on the scheduling of the service 2 by the service scheduling management module of the device 2.

If the service 2 judges that the equipment end of the application can not process the scheduling operation of the service 2, the method is equivalent to triggering the scheduling operation of the service 2 from the control center of the equipment 1. At this time, the service 2 of the device 1 transmits the scheduling information included in the scheduling instruction to the device 2 through the communication module SDK of the device 1 and the communication module of the capability layer. Specifically, the scheduling information is sent to the service scheduling management module of the device 2 through the communication module and the communication module SDK of the device 2. The control center of the device 2 performs a scheduling operation of the service 2.

In this way, for different devices to initiate the scheduling operation instruction of the cooperative service, one end is determined as the device 1 (not responsible for executing the scheduling operation instruction, that is, the passive responder) and one end is determined as the device 2 (responsible for executing the scheduling operation instruction, that is, the active responder) according to whether the two-end device of the cooperative service can execute the scheduling operation. According to the implementation logic shown in fig. 5 described above, the cooperative operation is performed. The method realizes that different devices initiate scheduling operation instructions to share one set of processing logic, and reduces complexity and dimension difficulty of a scheme.

To better illustrate embodiments of the present application, a specific implementation diagram of implementation logic shown in fig. 5A is provided. Referring to fig. 5B, a scheduling timing diagram of a cooperative service according to an embodiment of the present application is provided. The method comprises the following steps:

S51: when a user initiates a scheduling operation instruction of a first collaborative service on a first electronic device, a service scheduling management module of the first electronic device triggers the scheduling operation instruction.

In the embodiment of the application, the scheduling operation of the first cooperative service of the first electronic device and the second electronic device is executed at the cooperative interface of the first electronic device, and the service scheduling management module of the first electronic device triggers the scheduling operation instruction based on the first cooperative service. The scheduling operation comprises operations such as service establishment, service disconnection and the like.

The scheduling operation instruction carries service information such as a first cooperative service required device ID, a device type, a remote device ID, a remote device type, a service connection mode and the like. According to the scheduling operation instruction, specific services of the service layer can be scheduled.

In the embodiment of the application, the scheduling operation instruction can adopt a TCP/IP-like encapsulation format. Exemplary description: the scheduling instruction is class callBusinessCmd. The specific package format is as follows:

Public class CallBusinessCmd

{

PRIVATE STRING localDeviceId; /(local device ID)

PRIVATE STRING localDeviceType; type of/(native device)

PRIVATE STRING localBusinessId; /(present service ID)

PRIVATE STRING remoteDeviceId; remote device ID

PRIVATE STRING remoteDeviceType; type of remote device

PRIVATE STRING remoteBusinessId; the remote service ID is generally the same as the home service ID

PRIVATE STRING extraString; information of// extra

}

By means of the packaging mode of the standardized instruction, related parameters of the instruction do not need to be filled in manually and sequentially, the complexity of codes is reduced, and the coding efficiency of a service side is improved.

S52: and the service scheduling management module of the first electronic device sends the scheduling operation instruction to the first collaborative service of the second electronic device.

After the service scheduling management module triggers the scheduling operation instruction of the first cooperative service, the scheduling operation instruction carrying the service information such as the equipment ID, the equipment type, the far-end equipment ID, the far-end equipment type, the service connection mode and the like of the first cooperative service is sent to the first cooperative service of the service layer. The service scheduling management module can send scheduling operation instructions to the first collaborative service by adopting a uniform resource locator and other modes.

S53: the first cooperative service of the first electronic device judges whether the device executes the scheduling operation instruction. When it is determined to execute the scheduling operation instruction, S58 is executed. Otherwise, S54 is performed.

And judging whether the first electronic equipment is one of the reference electronic equipment according to the pre-configured reference electronic equipment for executing the scheduling of the first cooperative service so as to judge whether the first electronic equipment is responsible for executing the scheduling operation instruction. For example, when the reference electronic device is a mobile phone, the first electronic device executes the scheduling operation instruction when the first electronic device is a mobile phone. And if the first electronic device is a tablet pad, the first electronic device does not execute the scheduling operation instruction.

S64: the first cooperative service of the first electronic device sends a scheduling operation instruction to the service scheduling management module of the second electronic device through a communication channel.

When the first cooperative service of the first electronic device determines that the first electronic device does not execute the scheduling operation instruction, the scheduling operation instruction is sent to the service scheduling management module of the second electronic device through the communication module SDK of the first electronic device, the communication module of the second electronic device and the communication module SDK, so that the pad end executes the scheduling operation instruction. The communication management module (i.e., communication channel) has communication transmission capabilities such as bluetooth channel, network channel, p2p direct channel, etc.

S55: the service scheduling management module of the second electronic device distributes the instruction to the first system service of the service layer of the second electronic device.

The service scheduling management module of the second electronic device receives a scheduling operation instruction issued by a first cooperative service of the first electronic device, and accurately transmits the scheduling operation instruction to the first cooperative service according to service information such as a device ID, a device type, a remote device ID, a remote device type, a service connection mode and the like carried by the scheduling operation instruction.

S56: the first cooperative service of the second electronic device determines that the device is responsible for executing the scheduling operation instruction, and accurately executes the scheduling operation.

And judging whether the second electronic equipment is one of the reference electronic equipment according to the pre-configured reference electronic equipment for executing the scheduling of the first cooperative service by the first cooperative service so as to determine that the second electronic equipment is responsible for executing the scheduling operation instruction. Ready to perform scheduling operations is necessary for completing the service connection, such as initialization, etc.

In one possible implementation manner, when the first cooperative service of the second electronic device determines that the second electronic device is responsible for executing the operation instruction, the first electronic device may send notification information to notify that the scheduling operation of the first cooperative service is about to be executed when the scheduling operation is ready to be executed. For example, a monitor for monitoring bluetooth connection is installed at the mobile phone end, when the pad end is monitored to have bluetooth connection, notification information is initiated to the mobile phone end, and the mobile phone end receives the notification information. In one possible implementation manner, a prompt dialog box can be popped up on the mobile phone end in cooperation with the display interface to prompt whether the pad end executes the prompt box of the scheduling operation corresponding to the scheduling operation instruction. When the user determines that the dispatching operation instruction is executed by the pad, executing the operation instruction corresponding to the dispatching operation, and carrying out the dispatching service of the mobile phone screen-throwing to the pad. If the user selects to refuse to execute the scheduling operation corresponding to the scheduling operation instruction by the pad end, the execution result fails, and the scheduling flow is ended.

S57: and the second electronic equipment executes the scheduling instruction to perform scheduling service of the first cooperative service.

The timing diagram shown in fig. 5B is described in detail below with reference to an example of a scheduling operation of the mobile phone screen to pad shown in fig. 1.

Referring to fig. 6A, a scheduling timing diagram of a mobile phone screen-throwing to pad according to an embodiment of the present application is provided. The mobile phone is used for throwing the screen to the scheduling service of the pad, the control center which is responsible for executing the operation instruction is used for determining whether the mobile phone or the pad is preset in the control center when the scheduling operation instruction of the screen throwing service is executed. The control center of the mobile phone terminal is not in charge of executing the operation instruction. The specific implementation mode is as follows:

s61: and the service scheduling management module of the control center of the mobile phone terminal initiates a scheduling operation instruction for triggering screen throwing.

In the embodiment of the application, a user executes screen-throwing service scheduling operation of the mobile phone end and the pad end on the collaborative display interface of the mobile phone end control center. The scheduling operation comprises operations such as service establishment, service disconnection and the like. Exemplary:

when a user initiates a screen-throwing operation instruction on the collaborative display interface of the mobile phone control center, for example, the user drags the flat plate 103 identifier wrapped by the white small ball within a preset distance range from the mobile phone 101 through operation modes such as dragging on the collaborative display interface on the right side of fig. 1, the service scheduling management module of the mobile phone control center triggers the screen-throwing service establishment operation instruction executed by the user on the collaborative display interface, namely, the scheduling operation instruction is a service establishment operation instruction.

In the embodiment of the application, the scheduling operation instruction of the screen throwing carries service information such as equipment ID, equipment type, remote equipment ID, remote equipment type, service connection mode and the like of the screen throwing service. According to the scheduling operation instruction of the screen, the screen-throwing service of the specific service layer can be scheduled.

Public class CallBusinessCmd

{

PRIVATE STRING localDeviceId; /(local device ID)

PRIVATE STRING localDeviceType; type of/(native device)

PRIVATE STRING localBusinessId; /(present service ID)

PRIVATE STRING remoteDeviceId; remote device ID

PRIVATE STRING remoteDeviceType; type of remote device

PRIVATE STRING extraString; information of// extra

}

S62: and the service scheduling management module of the mobile phone terminal sends a scheduling operation instruction to the screen throwing service of the service layer of the mobile phone terminal.

After the service scheduling management module triggers the scheduling operation instruction of the mobile phone to screen the pad, the scheduling operation instruction carrying the service information such as the equipment ID, the equipment type, the far-end equipment ID, the far-end equipment type, the service connection mode and the like of the screen-throwing service is sent to the screen-throwing service of the service layer. The method can particularly adopt a uniform resource locator and other modes to realize that the service scheduling management module issues a scheduling operation instruction to the screen throwing service.

S63: the screen-throwing service of the mobile phone terminal service layer determines that the equipment does not execute the scheduling operation instruction.

And the screen throwing service of the mobile phone terminal service layer determines that the mobile phone terminal does not execute the scheduling operation instruction according to the fact that the responsible operation instruction execution terminal preset in the control center is a pad terminal control center. It should be noted that, in the embodiment of the present application, the dual-end device for implementing the cooperative service is a device service management module preset in the control center, which device is responsible for executing the scheduling operation instruction, and which device is not responsible for executing the scheduling operation. In the using process, the device management module acquires a preset result from the device service management module in real time and sends the preset result to the service layer. The business layer judges whether the equipment executes the dispatching operation instruction.

S64: the screen-throwing service of the mobile phone terminal service layer sends a scheduling operation instruction to the service scheduling management module of the pad terminal through the communication channel of the mobile phone terminal and the communication channel of the pad terminal.

When the screen throwing service of the service layer of the mobile phone end determines that the mobile phone end does not execute the scheduling operation instruction, the scheduling operation instruction is sent to the service scheduling management module of the pad end through the communication module SDK of the mobile phone end, the communication module of the pad end and the communication module SDK, so that the pad end executes the scheduling operation instruction. The communication management module has communication transmission capability, such as a Bluetooth channel, a network channel, a p2p direct connection channel and the like.

S65: and the service scheduling management module of the pad end distributes the instruction to the screen throwing service of the service layer of the pad end.

The service scheduling management module of the Pad end receives a scheduling operation instruction issued by the screen-throwing service of the mobile phone end service layer, and accurately transmits the scheduling operation instruction to the screen-throwing corresponding screen-throwing service according to the service information such as the equipment ID, the equipment type, the far-end equipment ID, the far-end equipment type, the service connection mode and the like carried by the scheduling operation instruction.

S66: the pad end screen-throwing service determines that the device is responsible for executing the dispatching operation instruction and accurately executes the dispatching operation.

The Pad end screen service determines the screen service execution scheduling operation instruction of the service layer of the Pad end according to the preset responsible operation instruction execution end at the control center as the Pad end control center. Ready to perform scheduling operations is necessary for completing the service connection, such as initialization, etc.

In one possible implementation manner, when the pad end screen-throwing service determines that the pad end is responsible for executing the operation instruction and accurately executes the scheduling operation, notification information may be sent to the mobile phone end to notify that the scheduling operation of the screen-throwing service is about to be executed, for example, a monitor for monitoring bluetooth connection is installed at the mobile phone end, when the pad end is monitored to have bluetooth connection, notification information is initiated to the mobile phone end, and the mobile phone end receives the notification information. In one possible implementation manner, a prompt dialog box can be popped up on the mobile phone end in cooperation with the display interface to prompt whether the pad end executes the prompt box of the scheduling operation corresponding to the scheduling operation instruction. When the user determines that the dispatching operation instruction is executed by the pad, executing the operation instruction corresponding to the dispatching operation, and carrying out the dispatching service of the mobile phone screen-throwing to the pad. If the user selects to refuse to execute the scheduling operation corresponding to the scheduling operation instruction by the pad end, the execution result fails, and the scheduling flow is ended.

S67: and the pad end screen-throwing service executes a scheduling instruction to perform the scheduling service from the mobile phone screen throwing to the pad.

The Pad end screen-throwing service executes the dispatching operation instruction and executes the dispatching service from the mobile phone screen throwing to the Pad. Referring to fig. 6B, a schematic diagram of a service association display result of a mobile phone screen-cast to pad is provided for an embodiment of the present application. And projecting the display content of the whole display screen of the mobile phone terminal onto the pad display screen. In the embodiment of the application, the mobile phone terminal display screen comprises a local space, a cloud space, pictures, videos, audios, compressed packets, internal storage, network neighbor information marks and information contents which are all projected to the pad terminal.

Referring to fig. 7, another scheduling timing diagram of a mobile phone screen-throwing to pad according to an embodiment of the present application is provided. The method specifically comprises the following steps:

S71: and a service scheduling management module of the pad end control center of the user initiates a scheduling operation instruction for triggering screen throwing.

When a user initiates a screen-throwing operation instruction on a full-screen display interface of the pad end control center, for example, the user drags the mobile phone 101 wrapped by the white small ball to a position within a preset distance range from the tablet 103 through operation modes such as dragging on a collaborative display interface on the left side of fig. 1, a service scheduling management module of the pad end control center triggers a screen-throwing scheduling operation instruction executed by the user on the collaborative display interface.

The scheduling instruction is class callBusinessCmd. The specific package format is as follows:

Public class CallBusinessCmd

{

PRIVATE STRING localDeviceId; /(local device ID)

PRIVATE STRING localDeviceType; type of/(native device)

PRIVATE STRING localBusinessId; /(present service ID)

PRIVATE STRING remoteDeviceId; remote device ID

PRIVATE STRING remoteDeviceType; type of remote device

PRIVATE STRING extraString; information of// extra

}

S72: and the service scheduling management module of the pad end distributes the scheduling operation instruction of the screen to the screen-throwing service of the service layer of the pad end.

S73: the pad end screen-throwing service determines that the device is responsible for executing the dispatching operation instruction and accurately executes the dispatching operation.

S74: and the pad end screen-throwing service executes a scheduling instruction to perform the scheduling service from the mobile phone screen throwing to the pad.

The Pad end screen-throwing service executes the dispatching operation instruction and executes the dispatching service from the mobile phone screen throwing to the Pad. The result of the mobile phone screen-throwing to pad shown in fig. 6B is specifically achieved.

Thus, for each operation of the cross-device collaborative service, after a device for which the collaborative service is responsible for scheduling operation instruction execution (the device service is an active responder device) is specified, the other party is not responsible for executing the scheduling operation instruction (the device is a passive responder device). But is executed directly on the device after the active responder triggers the dispatch operation instruction. If the scheduling operation instruction is triggered at the passive responder device, the scheduling operation instruction needs to be forwarded to the opposite terminal device to execute the scheduling operation corresponding to the scheduling operation instruction. Thus, different equipment launching operation instructions share one set of processing logic, and scheme complexity and maintenance degree are reduced.

The screen-throwing to pad of the mobile phone in the embodiment of the application is only an exemplary representation, and the collaborative service can be a plurality of services, such as screen expansion, a key mouse system and the like. The double-end device of the collaborative service can also be a device combination composed of pad, mobile phone, notebook computer, large screen display device and the like, which will not be discussed here.

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 method for scheduling a collaboration service, the method being applied to a first electronic device, the method comprising:

Responding to the dispatching operation of a first cooperative service of the first electronic device and the second electronic device, which is executed by a user on the first electronic device, and acquiring a dispatching operation instruction, wherein the dispatching operation instruction comprises service information of the first cooperative service and is used for dispatching the first cooperative service; judging whether the first electronic equipment is responsible for executing the scheduling operation instruction or not;

when the first electronic equipment is responsible for executing the scheduling operation instruction, executing the scheduling operation instruction to perform scheduling operation of the first collaborative service;

When the first electronic equipment is not responsible for executing the scheduling operation instruction, the scheduling operation instruction is sent to the second electronic equipment, so that the second electronic equipment executes the scheduling operation instruction to perform scheduling operation of the first collaborative service;

Responding to the scheduling operation of the first cooperative service executed by the user on the second electronic equipment, acquiring a scheduling operation instruction by the second electronic equipment, and judging whether the second electronic equipment is responsible for executing the scheduling operation instruction;

When the second electronic equipment is determined to be not responsible for executing the scheduling operation instruction, receiving the scheduling operation instruction sent by the second electronic equipment, and executing the scheduling operation instruction so as to perform scheduling operation of the first collaborative service;

And when the second electronic equipment is determined to be responsible for executing the scheduling operation instruction, executing the scheduling operation of the first collaborative service from the second electronic equipment.

2. The method of claim 1, wherein said determining whether the first electronic device is responsible for executing the scheduling operation instruction comprises:

And judging whether the first electronic equipment is one of the reference electronic equipment according to the pre-configured reference electronic equipment for executing the scheduling operation of the first collaborative service so as to judge whether the first electronic equipment is responsible for executing the scheduling operation instruction.

3. The method of claim 1, wherein the sending the scheduling operation instruction to the second electronic device when the first electronic device is not responsible for executing the scheduling operation instruction comprises:

when the first electronic equipment is not responsible for executing the scheduling operation instruction, the scheduling operation instruction is sent to the second electronic equipment through a communication channel between the first electronic equipment and the second electronic equipment;

4. A method according to any of claims 1-3, wherein when the first electronic device is not responsible for executing the scheduling operation instruction, the method further comprises:

When the second electronic equipment receives the scheduling operation instruction and determines that the second electronic equipment executes the scheduling operation instruction, receiving a request instruction sent by the second electronic equipment; the request instruction is used for sending an operation corresponding to the scheduling operation instruction to be executed to the first electronic equipment;

And determining an instruction for executing the scheduling operation by the second electronic equipment according to the request instruction, so that the second electronic equipment executes the scheduling operation instruction to perform the scheduling operation of the first collaborative service.

5. The method of claim 4, wherein the method further comprises:

And determining an instruction which can not be executed by the second electronic equipment for scheduling operation according to the request instruction, and not performing scheduling operation of the first cooperative service.

6. A method for scheduling collaborative services, which is applied to a second electronic device, the method comprising:

Responding to a user to execute a scheduling operation of a first cooperative service of a first electronic device and a second electronic device on the first electronic device, acquiring a scheduling operation instruction by the first electronic device, and judging whether the first electronic device is responsible for executing the scheduling operation instruction according to the scheduling operation instruction by the first electronic device, wherein the scheduling operation instruction comprises service information of the first cooperative service and is used for scheduling the first cooperative service;

When the first electronic equipment is determined not to be responsible for executing the scheduling operation instruction, receiving the scheduling operation instruction sent by the first electronic equipment, and executing the scheduling operation instruction so as to perform scheduling operation of the first collaborative service;

When the first electronic equipment is determined to be responsible for executing the scheduling operation instruction, executing the scheduling operation of the first collaborative service from the second electronic equipment;

Responding to the dispatch operation of the first collaborative service of the first electronic device and the second electronic device, which is executed by the user on the second electronic device, and acquiring a dispatch operation instruction; judging whether the second electronic equipment is responsible for executing the scheduling operation instruction or not;

When the second electronic equipment is responsible for executing the scheduling operation instruction, executing the scheduling operation instruction to perform scheduling operation of the first collaborative service;

And when the second electronic equipment is not responsible for executing the scheduling operation instruction, the scheduling operation instruction is sent to the second electronic equipment, so that the second electronic equipment executes the scheduling operation instruction to perform the scheduling operation of the first cooperative service.

7. The method of claim 6, wherein the determining, by the first electronic device, whether the first electronic device is responsible for executing the scheduling operation instruction according to the scheduling operation instruction comprises:

And executing the reference electronic equipment for executing the scheduling of the first cooperative service according to the pre-configuration by the first electronic equipment, and judging whether the first electronic equipment is one operation of the reference electronic equipment or not so as to judge whether the first electronic equipment is responsible for executing the scheduling operation instruction or not.

8. The method of claim 6, wherein receiving the scheduling operation instruction sent by the first electronic device when it is determined that the first electronic device is not responsible for executing the scheduling operation instruction comprises:

When the first electronic equipment is not responsible for executing the scheduling operation instruction, receiving the scheduling operation instruction sent by the first electronic equipment through a communication channel between the first electronic equipment and the second electronic equipment;

9. The method of any of claims 6-8, wherein when the first electronic device is not responsible for executing the scheduling operation instructions, the method further comprises:

When the second electronic equipment receives the scheduling operation instruction and determines that the second electronic equipment executes the scheduling operation instruction, acquiring a request instruction; the request instruction is used for sending an operation corresponding to the scheduling operation instruction to be executed to the first electronic equipment;

And sending the request instruction to the first electronic equipment, receiving an instruction for executing the scheduling operation by the second electronic equipment, and executing the scheduling operation instruction to perform the scheduling operation of the first collaborative service.

10. The method of claim 9, wherein the method further comprises:

And receiving an instruction that the scheduling operation cannot be executed by the second electronic equipment, and not executing the scheduling operation of the first cooperative service.

11. 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-5.

12. 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 6-10.

13. A collaboration system, the system comprising the electronic device of claim 11 and the electronic device of claim 12.