CN106933678A - A kind of many equipment application supporting frames and its implementation - Google Patents

Abstract

The present invention provides a multi-device application support framework, including: a device communication module, used for remote interaction between different device components, and data exchange between different device components, providing external interfaces and underlying support for device discovery and communication; device management The module is used to manage the accessed devices, provide an interface to obtain the right to use the device, monitor the status of each device, and provide notification of device status changes; the application development kit module is used to provide components that can adapt to split-screen requirements, and provide A component manager that governs the behavior of each of the described components. The present invention enables developers to be completely freed from trivial matters such as bottom communication and component distribution, and only need to care about the details of the application itself, so as to develop multi-device applications with high quality at a relatively fast speed. The invention can improve the user's application interaction experience and make full use of the user's personal equipment.

Description

A multi-device application support framework and its implementation method

technical field

The invention relates to the field of communication technology, in particular to a multi-device application support framework and an implementation method thereof.

Background technique

With the emergence of a large number of smart hardware and the continuous development of Internet technology, the interaction between users and applications and the Internet between users is no longer limited to traditional desktop computers. Smartphones, tablet computers, and smart TVs have brought different benefits to users. interactive experience.

The current application uses a certain type of device as the operating platform. There are two problems in this operating mode: a certain type of application is not suitable for running on the same type of platform; the user owns more than one smart device, and the application itself does not These equipment resources cannot be fully utilized. A multi-device application solves the above problems. It can be split and run on multiple devices, but it is still a complete application for the user experience. In order to rapidly develop such multi-device applications, a multi-device application support framework is needed to solve the above problems.

Contents of the invention

In view of the above-mentioned shortcomings of the prior art, the purpose of the present invention is to provide a multi-device application support framework and its implementation method, which is used to solve the problems in the prior art that the applications that use a certain device as the operating platform are not suitable for running on the same device. The operation of similar platforms or the application itself cannot make full use of smart devices and other issues.

In order to achieve the above object and other related objects, the present invention provides a multi-device application support framework, including: a device communication module, used for remote interaction between different device components, and data exchange between different device components, providing external interfaces and device The underlying support for discovery and communication; the device management module is used to manage the accessed devices, provide an interface for obtaining device usage rights, monitor the status of each device, and provide device status change notifications; the application development kit module is used to provide Components that adapt to split-screen requirements, while providing a component manager that manages the behavior of each of the components.

In an embodiment of the present invention, the device communication module includes: a proxy-stub unit, which includes a stub subunit defining the external interface, a proxy subunit corresponding to the stub subunit, and a proxy engine, Invoke the internally defined transmission interface through the proxy stub and the proxy engine and complete the data exchange between the internal and external network processing units by isolating the switching unit, and establish an information exchange path between the internal network client and the external network server; RPC communication guard unit , which is used to realize peer-to-peer communication within the device and communication between different devices; the data exchange guard unit is used to realize point-to-point data exchange between different devices.

In an embodiment of the present invention, the application development kit module hides details of interaction with the device management module and provides an event interface to the user.

In an embodiment of the present invention, the component manager manages the allocated components and devices, and distributes the components to corresponding devices.

In an embodiment of the present invention, the components include basic component combinations, custom component combinations, and custom component and basic component combinations.

A method for implementing a multi-device application support framework, comprising the following steps: S1: providing components that can adapt to split-screen requirements through the application development kit module; S2: after discovering a new device, the component manager obtains device characteristics, And compare the characteristics of components and devices, and then generate a component distribution plan, then notify the user, and finally the user decides whether to distribute the component to a specific device; then through the device management module and device communication module, the components are split and run on multiple on the device.

In an embodiment of the present invention, the step S2 includes the following steps: S21: Realize the remote interaction between different device components and the data exchange between different device components through the device communication module. When the framework is running, the customized The external interface of the device is published in a specific network, and the remote interface provided by other components can be easily accessed through the external interface; S22: Obtain the interface of the device usage right through the device management module, monitor the status of each device, and notify the device status change.

In one embodiment of the present invention, the step S21 includes the following process: S211, proxy-stub process: define the external interface in the stub subunit, and define the corresponding proxy subunit at the same time. After the process starts, the interface of the stub Published to the IPC component of the current running platform, other processes obtain the proxy module of the target process, or obtain the interface of the target process, and implement IPC through interface calls; S212, RPC communication daemon process: implement peer-to-peer communication between devices through the RPC communication daemon process , the process that needs cross-device communication needs to call the corresponding interface through the proxy subunit of the RPC communication daemon process; S213, the data exchange daemon process: the client process establishes and obtains a data stream object through the interface, and implements the inter-device operation interface on the data stream object Data exchange, to achieve point-to-point data exchange between devices.

In an embodiment of the present invention, the step S22 specifically includes the following processes: S221, the device management module collects the device information of the device at startup, and generates description information; S222, when the device joins the device cluster, Multicast its own device information to notify all reachable devices, synchronize the shared information list, and send corresponding event notifications; when a device leaves the cluster, multicast notifies reachable devices, synchronously modifies the shared information list, and sends corresponding events Notification; when the device is online, it will periodically multicast heartbeat packets to inform other devices that it is still online; when a heartbeat timeout occurs, it means that the device is currently unreachable and offline abnormally, and needs to send a corresponding event to notify the application process; S223, When the application process applies for using a certain device, it establishes a data stream channel and returns the corresponding data stream object.

As mentioned above, the multi-device application support framework and its implementation method of the present invention have the following beneficial effects:

The invention hides the implementation details of the underlying communication through the device communication module, exposes a simple communication interface to the outside, and realizes cross-device and cross-platform communication; through the establishment of inter-device communication links, management of interconnected device information, and fast application development kits, developers Just focus on the application logic itself, you can easily and quickly implement multi-device applications, make full use of the user's rich device resources, and obtain the best application experience.

Further, the present invention uses the component manager to enable the developer to only process the necessary event process, and the component manager will automatically call the developer to write the event processing process to determine the behavior of the application.

Further, the application of basic components in the present invention complies with the CMD specification, each component is an independent module, and the components adopt object-oriented design, and all components inherit from basic classes such as input and output, thereby limiting the behavior of components, component management The controller implements scheduling management for the component according to its type.

Further, the present invention enables developers to be completely freed from trivial matters such as low-level communication and component distribution, and only need to care about the details of the application itself, so as to develop multi-device applications with higher quality at a faster speed. The method can improve the user's application interaction experience and make full use of the user's personal device.

Description of drawings

FIG. 1 is a schematic diagram of the composition of the multi-device application support framework in an embodiment of the multi-device application support framework and its implementation method of the present invention.

FIG. 2 is a schematic flow diagram of the implementation method of the multi-device application support framework in an embodiment of the multi-device application support framework and its implementation method of the present invention.

FIG. 3 is a schematic diagram of the implementation process of the device communication module in an embodiment of the multi-device application support framework and its implementation method of the present invention.

FIG. 4 is a schematic diagram of a device management implementation process in an embodiment of the multi-device application support framework and its implementation method of the present invention.

FIG. 5 is a schematic diagram of an implementation process of an application development kit in an embodiment of the multi-device application support framework and its implementation method of the present invention.

Component designation description

1 Multi-device application support framework

11 Device communication module

12 Device Management Module

13 Application Development Kit Modules

S1～S2 steps

detailed description

Embodiments of the present invention are described below through specific examples, and those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various modifications or changes can be made to the details in this specification based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that, in the case of no conflict, the following embodiments and features in the embodiments can be combined with each other.

It should be noted that the diagrams provided in the following embodiments are only schematically illustrating the basic ideas of the present invention, and only the components related to the present invention are shown in the diagrams rather than the number, shape and shape of the components in actual implementation. Dimensional drawing, the type, quantity and proportion of each component can be changed arbitrarily during actual implementation, and the component layout type may also be more complicated.

The present invention provides a multi-device application support framework, which is an application platform for interactive experience between different smart devices such as smart phones, tablet computers, and smart TVs of users, which can improve the user's application interactive experience and make full use of the user's personal experience. equipment.

Please refer to FIG. 1, which is a schematic diagram showing the composition of the multi-device application support framework of the present invention. As shown in the figure, the multi-device application support framework 1 includes: a device communication module 11, a device management module 12 and an application development kit module 13,

The device communication module 11 is used for remote interaction between different device components and data exchange between different device components, providing external interfaces and underlying support for device discovery and communication, only exposing external interfaces to users, and hiding the bottom layer of device discovery and communication Details of support; in an embodiment, the device communication module 11 includes: a proxy-stub unit, an RPC communication guard unit, and a data exchange guard unit, and the proxy-stub unit includes a stub subunit defining the external interface and a stub unit associated with the stub The proxy subunit and proxy engine corresponding to the subunit call the internally defined transmission interface through the proxy stub and the proxy engine, and complete the data exchange between the internal and external network processing units through the isolation switching unit, and establish the intranet client and external network. The information exchange path between servers; the RPC communication guard unit is used to realize peer-to-peer communication within the device and communication between different devices; the data exchange guard unit is used to realize point-to-point data exchange between different devices.

The device management module 12 is used to manage the accessed devices, provide an interface for obtaining device usage rights, monitor the status of each device, and provide device status change notifications;

The application development kit module 13 is used to provide components that can adapt to split-screen requirements, and at the same time provide a component manager that manages and controls the behavior of each of the components; in the embodiment, the application development kit module hides the interaction details with the device management module , providing an event interface to the user, the component manager manages and distributes adapted components and devices, and distributes components to corresponding devices, wherein the components include basic component combinations, custom component combinations, and custom components and basic combination of components.

The present invention provides a method for implementing a multi-device application support framework, which is used as an application platform for interactive experience among different smart devices such as smart phones, tablet computers, and smart TVs of users, which can improve the user's application interactive experience and make full use of User's Personal Device.

Please refer to FIG. 2 , which is a schematic flowchart of the implementation method of the multi-device application support framework of the present invention. As shown in the figure, it includes the following steps:

S1: Provide components that can adapt to split-screen requirements through the application development kit module;

S2: After discovering a new device, the component manager generates a component distribution plan by acquiring device characteristics and comparing the characteristics of the component and the device, and then notifies the user, and finally the user decides whether to distribute the component to a specific device; then Through the device management module and the device communication module, the components are split and run on multiple devices; in the embodiment, step S2 includes the following steps: S21: realize remote interaction between different device components through the device communication module, and different For data exchange between components between devices, when the framework is running, a custom external interface is published in a specific network, and the remote interface provided by other components can be easily accessed through the external interface; S22: Obtaining the right to use the device through the device management module Interface to monitor the status of each device and notify of device status changes.

Further, step S21 specifically includes the following processes:

S211, proxy-stub process: define the external interface in the stub subunit, and define the corresponding proxy subunit at the same time, after the process starts, publish the interface of the stub to the IPC component of the current running platform, and other processes obtain the proxy of the target process module, or obtain the interface of the target process, and implement IPC through interface calling;

S212, RPC communication daemon process: implement peer-to-peer communication between devices through the RPC communication daemon process, and the process that needs cross-device communication needs to call the corresponding interface through the proxy subunit of the RPC communication daemon process;

S213, data exchange daemon process: through this process, point-to-point data exchange between devices can be realized. The client process establishes and obtains a data stream object through the interface, and operates the interface on the data stream object to realize data exchange between devices.

Further, step S22 specifically includes the following processes:

S221, the device management module collects device information of the device where it is located when starting, and generates description information;

S222, when the device joins the device cluster, multicast its own device information to notify all reachable devices, synchronize the shared information list, and send a corresponding event notification; when the device leaves the cluster, multicast the reachable device and modify it synchronously Share the information list and issue corresponding event notifications; when the device is online, it will periodically multicast heartbeat packets to inform other devices that it is still online; when a heartbeat timeout occurs, it means that the device is currently unreachable and abnormally offline, and needs to be sent The corresponding event notifies the application process;

S223. When the application process applies for using a certain device, establish a data stream channel and return a corresponding data stream object.

The implementation process of the device communication module, the implementation process of the device management, and the implementation process of the application development kit will be described in detail below.

A. The implementation process of the device communication module:

Please refer to Fig. 3, Fig. 3 shows the schematic diagram of the implementation process of the device communication module in the embodiment, as shown in the figure, the implementation process of the inter-device communication module is mainly composed of three parts: the process of agent-stub (Proxy-Stub), RPC Communication daemon, data exchange daemon.

Proxy-stub (Proxy-Stub) process: define its external interface in the stub subunit, and define the corresponding proxy subunit at the same time, when the process starts. The framework mechanism will ensure that the interface of the stub is published only in the IPC component of the current running platform. IPC refers to inter-process communication. Other processes can obtain the proxy subunit of the target process through the method provided by the framework, or use the method provided by the current platform itself. The interface of the target process (therefore, the process implemented based on this framework is compatible with other processes, but the framework hides the underlying complex mechanism), and IPC can be realized by calling the interface. Process A-1, process A-2, process B-1, process C-1, etc. in FIG. 3 are all such processes.

The RPC communication daemon, which is Communication-Daemon (abbreviated as CD), as shown in Figure 3, is based on the process implemented by the agent-stub unit, and the RPC communication daemon is uniquely running on each device, and the IPC between devices passes through this process. The daemon process implements peer-to-peer communication, and the process that needs to communicate across devices only needs to call the corresponding interface through the proxy subunit of CD. This implementation has the following effects:

a) The only RPC import and export is restricted to facilitate the implementation of a security verification mechanism.

b) Only one communication link is maintained between every two devices, which greatly reduces the overhead.

c) Each process does not need to implement the function of connecting to other devices independently, which realizes the multiplexing of functions.

The data exchange daemon process is DataTransfer (abbreviated as DT). As shown in Figure 3, based on the process implemented by the agent-stub unit, there is only one data exchange daemon process running on each device. Through this process, the transfer between devices can be realized. For point-to-point data exchange, the client process (such as process A-2) establishes and obtains a data stream object through the DT interface, and then operates the interface on the data stream object to realize data exchange between devices. Separating DT from CD is mainly due to the different nature of these two connections. CD messages are usually relatively short, and CD needs to respond as quickly as possible, while DT usually occupies the connection channel for a long time. If put together Will cause serious RPC delay.

B. Implementation process of equipment management:

The device management module, namely Resource-Manager, runs on each device in the form of a daemon process. In order to realize the main responsibilities of the device management module, the following functions need to be implemented:

When the unit starts, it collects the device information of the device where it is located, and generates accurate description information (including the information of the device itself, such as screen size, resolution, etc., and also includes the applicable type of the device, such as display output, control input, etc.), initialization List of shared information.

Please refer to Figure 4, Figure 4 shows a schematic diagram of the device management implementation process in the embodiment, as shown in the figure, when the device goes online (joins the device cluster), the device information of the multicast itself notifies all reachable devices, and performs a shared information list Synchronize and issue corresponding event notifications; similarly, when going offline (leaving the cluster), the multicast notification reaches the device, synchronously modifies the shared information list, and sends corresponding event notifications; when the device is online, it will periodically multicast heartbeat packets, To inform other devices that they are still online. When a heartbeat timeout occurs, it means that the device is currently unreachable and abnormally offline. It is necessary to send a corresponding event to notify the application process.

When an application process applies to use a certain device (non-native), it completes the establishment of the data stream channel and returns the corresponding data stream object. Taking the video output device as an example, the specific steps are as follows:

a) Apply to use the screen of another device as the output device;

b) Complete the establishment of the data stream (stream1) channel between devices through DT;

c) The peer node Resource-Manager process receives the request, establishes the data stream (stream2) channel from the DT process to the video output process, and connects stream1 and stream2;

d) The local node establishes a data stream (stream3) channel between the application process and the DT, and connects stream1 and stream3.

e) Return the stream3 object to the application process, and the application process will input the generated video data into stream3, which can be processed by the video output process of another device and output to the screen.

C. Application development kit implementation process:

Please refer to Fig. 5. Fig. 5 shows a schematic diagram of the implementation process of the application development kit in the embodiment. As shown in the figure, the application development kit module is submitted to the user in the form of SDK, which includes the basic application framework, basic components and related Documentation to help developers quickly build such applications. The basic components of the application comply with the CMD specification, and each component is an independent module. At the same time, the components adopt an object-oriented design, and all components inherit from basic classes such as input and output, thereby limiting the behavior of the components, and the component manager will implement scheduling management for the components according to their types.

The application framework consists of several components, the most important of which is the component manager:

1) It hides the interaction details with the device management module, and only exposes the event interface to application developers;

2) Organize and manage components, distribute and recycle components, and establish data flow channels between cross-device components.

With the component manager, as a developer, you only need to implement the necessary event processing process, such as finding a device that is more suitable for display, a device that is more suitable for controlling input, etc., the component manager will automatically call the developer to write event processing process to determine the behavior of the application.

In summary, the present invention hides the implementation details of the underlying communication through the device communication module, exposes a simple communication interface to the outside, and realizes cross-device and cross-platform communication; by establishing communication links between devices, managing interconnected device information, and fast application development The suite allows developers to only focus on the application logic itself, and can easily and quickly implement multi-device applications, make full use of the user's rich device resources, and obtain the best application experience. Therefore, the present invention effectively overcomes various shortcomings in the prior art and has high industrial application value.

The above-mentioned embodiments only illustrate the principles and effects of the present invention, but are not intended to limit the present invention. Anyone skilled in the art can modify or change the above-mentioned embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or changes made by those skilled in the art without departing from the spirit and technical ideas disclosed in the present invention shall still be covered by the claims of the present invention.

Claims (9)

1. A multi-device application support framework, comprising: The device communication module is used for remote interaction between different device components and data exchange between different device components, providing external interfaces and underlying support for device discovery and communication; The device management module is used to manage the accessed devices, provide an interface for obtaining device usage rights, monitor the status of each device, and provide device status change notifications; The application development kit module is used to provide components that can adapt to split-screen requirements, and at the same time provide a component manager that manages and controls the behavior of each of the components. 2. The multi-device application support framework according to claim 1, wherein the device communication module includes: Proxy-stub unit, which includes a stub subunit defined with the external interface and a proxy subunit corresponding to the stub subunit, a proxy engine, calling the internally defined transmission interface through the proxy stub and the proxy engine and passing through the isolation exchange unit to complete the data exchange between the internal and external network processing units, and establish an information exchange path between the internal network client and the external network server; The RPC communication guard unit is used to realize peer-to-peer communication within the device and communication between different devices; The data exchange guard unit is used to realize point-to-point data exchange between different devices. 3. The multi-device application support framework according to claim 1, wherein the application development kit module hides details of interaction with the device management module and provides an event interface to the user. 4. The multi-device application support framework according to claim 1, wherein the component manager manages the allocated components and devices, and distributes the components to corresponding devices. 5 . The multi-device application support framework according to claim 1 , wherein the components include a combination of basic components, a combination of custom components, and a combination of custom components and basic components. 6. The method for implementing the multi-device application support framework according to any one of claims 1 to 5, characterized in that: comprising the following steps: S1: Provide components that can adapt to split-screen requirements through the application development kit module; S2: After discovering a new device, the component manager generates a component distribution plan by acquiring device characteristics and comparing the characteristics of the component and the device, and then notifies the user, and finally the user decides whether to distribute the component to a specific device; then Through the device management module and the device communication module, the components are split and run on multiple devices. 7. The method for realizing the multi-device application support framework according to claim 6, characterized in that: said step S2 comprises the following steps: S21: Realize remote interaction between different device components and data exchange between different device components through the device communication module. When the framework is running, the customized external interface is published in a specific network, and other external interfaces can be easily accessed through the external interface. The remote interface provided by the component; S22: Obtain the interface of the device usage right through the device management module, monitor the status of each device, and notify the device status change. 8. The method for realizing the multi-device application support framework according to claim 7, characterized in that: said step S21 includes the following processes: S211, proxy-stub process: define the external interface in the stub subunit, and define the corresponding proxy subunit at the same time, after the process starts, publish the interface of the stub to the IPC component of the current running platform, and other processes obtain the proxy of the target process module, or obtain the interface of the target process, and implement IPC through interface calling; S212, RPC communication daemon process: implement peer-to-peer communication between devices through the RPC communication daemon process, and the process that needs cross-device communication needs to call the corresponding interface through the proxy subunit of the RPC communication daemon process; S213, data exchange daemon process: the client process establishes and obtains a data stream object through the interface, operates the interface on the data stream object to realize data exchange between devices, and realizes point-to-point data exchange between devices. 9. The method for realizing the multi-device application support framework according to claim 7, characterized in that: the step S22 specifically includes the following processes: S221, the device management module collects device information of the device where it is located when starting, and generates description information; S222. When a device joins the device cluster, multicast its own device information to notify all reachable devices, perform shared information list synchronization, and send a corresponding event notification; When the device leaves the cluster, the multicast notification reaches the device, synchronously modifies the shared information list, and sends a corresponding event notification; when the device is online, it will periodically multicast heartbeat packets to inform other devices that it is still online; When a heartbeat timeout occurs, it means that the device is currently unreachable and abnormally offline, and a corresponding event needs to be sent to notify the application process; S223. When the application process applies for using a certain device, establish a data stream channel and return a corresponding data stream object.