WO2017167125A1 - Procédé de composition graphique, procédé d'interaction d'informations, et système - Google Patents

Procédé de composition graphique, procédé d'interaction d'informations, et système Download PDF

Info

Publication number
WO2017167125A1
WO2017167125A1 PCT/CN2017/078035 CN2017078035W WO2017167125A1 WO 2017167125 A1 WO2017167125 A1 WO 2017167125A1 CN 2017078035 W CN2017078035 W CN 2017078035W WO 2017167125 A1 WO2017167125 A1 WO 2017167125A1
Authority
WO
WIPO (PCT)
Prior art keywords
subsystem
control
information
graphics
graphic
Prior art date
Application number
PCT/CN2017/078035
Other languages
English (en)
Chinese (zh)
Inventor
吴涛
吴昌松
Original Assignee
阿里巴巴集团控股有限公司
吴涛
吴昌松
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司, 吴涛, 吴昌松 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2017167125A1 publication Critical patent/WO2017167125A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/542—Event management; Broadcasting; Multicasting; Notifications

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a graphics synthesis method, an information interaction method, and a system.
  • the cloud operating system also known as cloud OS, is an operating system supported by cloud computing and cloud storage technologies.
  • the cloud operating system will be widely used in the future because it can integrate massive computing power and provide powerful resource allocation capabilities.
  • Cloud operating systems can be used for both traditional desktop systems (such as PCs) and mobile devices.
  • Applications or services based on cloud operating systems, as well as applications or services based on traditional operating systems, will operate within the framework of the cloud operating system, which requires the cloud operating system framework to integrate applications or services based on different operating systems.
  • the embodiment of the present application provides a graphics synthesis method and system for implementing compatibility between different operating systems at a graphics processing level.
  • the first control in the first subsystem receives the graphic data sent by the graphic object corresponding to the first control in the second subsystem graphics synthesizer;
  • the first control transmits the graphics data to a first subsystem graphics synthesizer.
  • the method further includes the first subsystem graphics synthesizer receiving graphics data transmitted by the graphics object in the first subsystem.
  • the method further includes: the first subsystem graphics synthesizer synthesizes the graphics data sent by the first control and the graphics data sent by the graphics object in the first subsystem.
  • the first control is a plurality, and the first control sends the graphic data to the first Subsystem graphics synthesizer, including:
  • the plurality of first controls send the respective received graphic data to the graphic objects in the first subsystem
  • the graphic object in the first subsystem sends the graphic data sent by the plurality of first controls to the first subsystem graphic synthesizer as the graphic data corresponding to the graphic object.
  • the method further includes: the first control receives graphic object setting information sent by the application component in the first subsystem; the first control sends the received graphic object setting information to the first subsystem graphic synthesis Device.
  • the graphic object is an application window, and the graphic object setting information includes window attribute information.
  • the method further includes: creating the first control.
  • the creating the first control includes: the application component in the first subsystem is configured to create a graphic object corresponding to the graphic object in the second subsystem for providing graphic data according to the request for using the graphic data in the second subsystem.
  • the first control is configured to create a graphic object corresponding to the graphic object in the second subsystem for providing graphic data according to the request for using the graphic data in the second subsystem.
  • the method further includes: destroying the first control.
  • Destroying the first control comprising: the application component in the first subsystem receiving the information that the graphic object corresponding to the first control in the second subsystem is destroyed, and destroying the first control; or The application component in the first subsystem receives an indication to end the use of the graphics data in the second subsystem, and then destroys the first control corresponding to the graphics object in the second subsystem for providing the graphics data.
  • the method further includes:
  • the first application component in the first subsystem sends control information to the first system service component in the first subsystem, the control information is used to indicate that the graphic data in the second subsystem is acquired;
  • the first system service component sends the control information to a second system service component of the second subsystem
  • the second system service component sends the control information to a second one of the second subsystems.
  • the first subsystem is a Host subsystem
  • the second subsystem is a Guest subsystem.
  • the graphics synthesis system includes: a first subsystem graphics synthesizer, a second subsystem graphics synthesizer, and a first control in the first subsystem;
  • a first control in the first subsystem configured to receive graphic data sent by the graphic object corresponding to the first control in the second subsystem graphics synthesizer, and send the graphic data to the first subsystem graphic synthesis Device.
  • the first subsystem graphics synthesizer is further configured to: receive graphics data sent by the graphic object in the first subsystem.
  • the first subsystem graphic synthesizer is further configured to: synthesize the graphic data sent by the first control and the graphic data sent by the graphic object in the first subsystem.
  • the first control is a plurality of, the plurality of first controls send the respective received graphic data to the graphic object in the first subsystem;
  • the first subsystem graphics synthesizer is specifically configured to: receive graphic data sent by the graphic object in the first subsystem; wherein the graphic object corresponds to the graphic data sent by the plurality of first controls The graphics data is sent to the first subsystem graphics synthesizer.
  • first control is further configured to:
  • the received graphic object setting information is sent to the first subsystem graphic synthesizer.
  • the graphic object is an application window, and the graphic object setting information includes window attribute information.
  • the first subsystem further includes an application component; and the application component in the first subsystem is configured to create the first control.
  • the application component in the first subsystem is specifically configured to: create a first control corresponding to the graphic object for providing graphic data in the second subsystem according to the request for using the graphic data in the second subsystem .
  • the first subsystem further includes an application component; and the application component in the first subsystem is configured to destroy the first control.
  • the application component in the first subsystem is specifically configured to:
  • the first control corresponding to the graphical object in the second subsystem for providing the graphics data is destroyed.
  • the first subsystem further includes a first application component
  • the second subsystem further includes a second application component
  • a first application component in the first subsystem configured to send control information to the first system service component in the first subsystem, where the control information is used to indicate that the graphic data in the second subsystem is acquired;
  • the first system service component is specifically configured to: send the control information to a second system service component in the second subsystem;
  • the second system service component is specifically configured to send the control information to a second application component in the second subsystem.
  • the first subsystem is a Host subsystem
  • the second subsystem is a Guest subsystem.
  • the first control in the first subsystem receives the graphic data sent by the graphic object corresponding to the first control in the second subsystem graphics synthesizer, and the first control will receive the graphic data.
  • Sending to the first subsystem graphics synthesizer it can be seen that, in the first subsystem, there is a corresponding first control corresponding to the graphic object in the second subsystem graphics synthesizer, and the first control provides between the two subsystems
  • the transfer function of graphic data enables compatibility between different operating systems at the graphics processing level.
  • the embodiment of the present application provides an information interaction method and system for implementing compatibility between different operating systems at a control level.
  • the first system service component in the first subsystem receives the first information sent by the first application component in the first subsystem
  • the first system service component sends the first information to a second system service component of the second subsystem
  • the second system service component transmits the first information to a second one of the second subsystems.
  • the method further comprises:
  • the second system service component receives the second information sent by the second application component, where the second information is obtained by the first application component according to the first information;
  • the second system service component sends the second information to the first system service component
  • the first system service component sends the second information to the first application component.
  • the first application component sends the first information to the first system service component in one or more of the following cases:
  • the application components in the second subsystem need to be notified for processing.
  • the method further comprises: creating the first system service component.
  • the first system service component is created when the first application component is created.
  • the method further comprises: destroying the first system service component.
  • the first system service component is destroyed when the first application component is destroyed.
  • the information comprises: control information and/or data.
  • the first subsystem is a Host subsystem
  • the second subsystem is a Guest subsystem
  • the first subsystem is a Guest subsystem
  • the second subsystem is a Host subsystem
  • a first system service component in the first subsystem configured to receive first information sent by the first application component in the first subsystem
  • the first system service component configured to send the first information to a second system service component in the second subsystem
  • the second system service component is configured to send the first information to a second application component in the second subsystem.
  • the second system service component is further configured to: receive second information sent by the second application component, and send the second information to the first system service component; wherein the second information Obtained for the first application component according to the first information;
  • the first system service component is further configured to: send the second information to the first application component.
  • the first application component is specifically configured to: in one or more of the following cases, The first system service component sends the first information:
  • the application components in the second subsystem need to be notified for processing.
  • the information comprises: control information and/or data.
  • the first subsystem is a Host subsystem
  • the second subsystem is a Guest subsystem
  • the first subsystem is a Guest subsystem
  • the second subsystem is a Host subsystem
  • the first system service component in the first subsystem receives the information sent by the first application component in the first subsystem; the first system service component sends the information to the second subsystem.
  • the second system service component, the second system service component sends the information to the second application component in the second subsystem, thereby implementing information interaction between the application components in the different subsystems.
  • FIG. 1 is a schematic diagram of an operating system framework applicable to an embodiment of the present application
  • FIG. 2 is a schematic diagram of an information interaction architecture of a cross-system according to an embodiment of the present application
  • FIG. 3 is a schematic diagram of a dual-system compatible architecture of a graphics synthesis layer according to an embodiment of the present application
  • FIG. 4 is a schematic diagram of a user interface of a video playback application provided by an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a graphics synthesis system according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of an information interaction system according to an embodiment of the present application.
  • the embodiment of the present application provides integration and unification at the graphics processing level in the framework of the first operating system. To provide users with a seamless dual system user experience.
  • the embodiment of the present application can be applied to an application that needs to run across operating systems, and is also applicable to a scenario in which graphics data or control information needs to be transmitted between applications based on different operating systems.
  • the first operating system and the second operating system are different operating systems.
  • the first operating system may be a cloud operating system
  • the second operating system may be a traditional operating system. More Specifically, the first operating system may be YunOS, and the second operating system may be Android.
  • FIG. 1 is a schematic diagram of an operating system framework applicable to an embodiment of the present application. Taking YunOS as the first operating system and Android as the second operating system as an example, FIG. 1 shows a dual system compatible architecture within the YunOS framework.
  • the system framework includes two subsystems: Host and Guest.
  • YunOS is the Host subsystem
  • Android is the Guest subsystem
  • the two subsystems are isolated by the container technology.
  • the Hardware Abstraction Layer (HAL) within the framework provides interfaces and driver services for graphical display and other aspects.
  • Glibc in the Host subsystem is the lowest API (Application Programming Interface) in Linux.
  • Bioric in the Guest subsystem is the Linux kernel library for Android.
  • Libhybris is a compatibility layer that enables Glibc-based operating systems to reuse existing Android driver services; in graphics processing, libhybris also implements the EGL platform.
  • EGL platform This is a backend-independent graphical platform that follows the EGL interface and multiple backend implementations.
  • the Gralloc module is located in the hardware abstraction layer and encapsulates all access operations to the framebuffer.
  • the InputManageerService (input management module) in the Guest subsystem is mainly used to monitor and manage input events.
  • Wayland Compositor (or Weston) is the graphics synthesizer of the Host subsystem, where Weston is the reference implementation of the Wayland Compositor.
  • the Wayland protocol can be used for communication between the graphics synthesizer of the Guest subsystem and the graphics synthesizer of the Host subsystem.
  • the Wayland protocol defines how to communicate with the kernel and how to communicate with the client; Wayland reuses the graphics, input and output technologies of all Linux kernels.
  • the Wayland protocol can be communicated between the graphic synthesizer of Andriod and the graphic synthesizer of YunOS, so that the graphics system in Android is overhead and bridged to the graphic system of YunOS, and the unified synthesis rendering of the dual system is realized. This provides better dual system compatibility and a seamless user experience for dual systems.
  • the embodiments of the present application provide dual system compatibility on the following two levels:
  • the Host subsystem is YunOS
  • the Guest subsystem is Android.
  • the embodiment of the present application establishes a connection path for data and/or control information of the cross-operating system environment from the first subsystem to the second subsystem, that is, provides an IPC (Inter -process communication, mechanism to implement information exchange between application components (or processes) of different subsystems.
  • IPC Inter -process communication, mechanism to implement information exchange between application components (or processes) of different subsystems.
  • an information interaction architecture provided by an embodiment of the present application is provided.
  • a Bridge Proxy is established in the Host subsystem, and a Bridge Service is established in the Guest subsystem.
  • Bridge Proxy and Bridge Service are system service components.
  • the Android system uses the Binder mechanism as the IPC (Inter-Process Communication) mechanism, and the YunOS uses the socket or dbus as the IPC communication mechanism, in order to make information between application components (that is, application processes) of different operating systems.
  • the Bridage Proxy is used as a system service to convert the IPC mechanism between the two systems.
  • An application component is one of the components of an application. It is called an Activity in the Android system and a Page in the YunOS. It is the main body of the application.
  • a process is an application or application component that is running.
  • the Bridge Service is usually a resident service and the Bridge Proxy can be created or enabled when needed.
  • Bridge Proxy when an application component (process) is created in the Host subsystem, Bridge Proxy is created or enabled to enable information interaction between different subsystems through the Bridge Proxy.
  • an application component (process) is destroyed in the Host subprocess, the Bridge Proxy is destroyed or closed.
  • the application component (process) described in the embodiment of the present application indicates that the application component and the process are in an alternative relationship, and the process herein can be understood as an application component in an operational state.
  • application components (processes) in the Host subsystem can send information, such as data and/or control information, to the Bridge Proxy, which sends the data and/or control information sent by the Bridge Proxy to Bridge.
  • the Service, Bridge Service sends the data and/or control information to the application components (processes) in the Guest subsystem.
  • the Bridge Proxy and the Bridge Service can communicate based on the Binder mechanism.
  • the Bridge Service can interact with application components (processes) in the Guest subsystem through intent or socket methods.
  • the data and/or control information as a result of the processing may be sent to the Bridge Service, and the Bridge Service compares the data and / or control information is sent to the Bridge Proxy, the Bridge Proxy sends the data and / or control information to the application components (processes) in the Host subsystem.
  • application components (processes) in the Guest subsystem may send information, such as data and/or control information, to the Bridge Service, which sends the data and/or control information to the Bridge Proxy, Bridge.
  • the Proxy sends the data and/or control information to the application components (processes) in the Host subsystem.
  • the application component (process) in the Host subsystem processes the received data and/or control information
  • the data and/or control information as a result of the processing may be sent to the Bridge Proxy
  • the Bridge Proxy may / or control information is sent to the Bridge Service
  • the Bridge Service sends the data and / or control information to the application components (processes) in the Guest subsystem.
  • the information exchanged between processes in different subsystems may be data or control information
  • the control information may include an event, or request information, or window attribute information.
  • the above information interaction method can be applied to some functions of an application that need to be implemented based on the Host subsystem, and some functions need to be based on the scenario implemented by the Guest subsystem.
  • a video playback app when a user submits a request to play a movie through the video playback app user interface, the event is acquired by the video playback app in the process of the Host subsystem due to the video content.
  • SDK Software Development Kit
  • the logic related to video content is developed in the Android environment, that is, the object requested by the event is in the Guse subsystem.
  • the process of the video playback app in the Host subsystem sends the event to the Bridge Proxy, which sends the event to the Bridge Service, which is sent by the Bridge Service to the video playback app in the Guest subsystem.
  • the process of the video playback app in the Guest subsystem sends the requested video data to the graphics synthesizer of the Host subsystem for processing.
  • the IPC architecture provided by the embodiment of the present application implements information exchange across operating systems, so that different operating systems are merged at the control level, thereby making the application-level fusion interactive experience seamless.
  • FIG. 3 is a schematic diagram of a dual-system compatible architecture of a graphics synthesis layer according to an embodiment of the present application.
  • a layer is created in the graphics synthesizer SurfaceFlinger of the Guest subsystem, and only two layers are exemplarily shown in the figure, namely layer1 and layer2.
  • p_surface1 and p_surface2 are created, where p_surface1 corresponds to layer1 in the Guest subsystem and corresponds to surface1 in the graphics synthesizer of the Host subsystem (not shown in the figure) for connecting layer1 And the graphics synthesizer Weston of the Host subsystem, more specifically for connecting surface1 in layer1 and Weston; P_surface2 corresponds to layer2 and corresponds to surface2 in the graphics synthesizer of the Host subsystem (not shown in the figure), the graphics synthesizer Weston for connecting layer2 and the Host subsystem, more specifically for connecting layer2 and Surface2 in Weston.
  • P_surface can be a control, which is used to connect the layer synthesizer of the layer and Host subsystem in the guest subsystem graphics synthesizer, as a proxy of the layer in the guest subsystem, and pass the graphics data of the guest subsystem to the host sub
  • the graphics synthesizer of the system Specifically, layer1 can send graphics data to p_surface1, p_surface1 can send graphics data sent by layer1 to the graphics synthesizer Weston of Host subsystem; layer2 can send graphics data to p_surface1, and p_surface2 can send graphics data sent by layer2 The graphics synthesizer Weston sent to the Host subsystem.
  • the application component can also create a local surface in the Host subsystem, and send the graphic data in the Host subsystem to the graphic synthesizer Weston of the Host subsystem through the local surface.
  • local surface is the surface in the Host subsystem.
  • the graphics synthesizer of the Host subsystem can synthesize the graphics data of the Host subsystem, and synthesize the graphics data of the Guest subsystem, and realize the graphics synthesis across operating systems.
  • the application component can also create layer3.
  • Layer3 can send the graphics data in the Guest subsystem to the graphics synthesizer Weston in the Host subsystem, and the graphics data is synthesized by Weston.
  • the embodiment of the present application uses layer content as the basic unit of the integration of the two subsystems, that is, the graphic data sent through the p_surface may be
  • the layer content more specifically, may be the graphics data stored in the GraphicBuffer queue corresponding to the layer.
  • a layer is a graphical object created by an application process. Generally, a layer represents a layer, and multiple layers can be superimposed in a Z-order order to form a user interface.
  • a layer can correspond to a GraphicBuffer queue, and a GraphicBuffer queue contains multiple GraphicBuffers.
  • the GraphicBuffer is created by the application component in the process of the Guest subsystem, where the graphic data is stored, such as the graphic data stored by the process of the application component in the Guest subsystem.
  • Figure 3 the architecture of Figure 3 is described by YunOS and Android, and the graphics data is The layer is submitted to the Surfaceflinger for synthesis.
  • the graphics object in the Guest subsystem and the control of the Host subsystem graphics synthesizer can be connected to other types of graphic objects.
  • the data is sent to the Host Subsystem Graphics Synthesizer for synthesis.
  • the p_surface may further receive graphic object setting information sent by the application component in the Host subsystem, and send the graphic object setting information to the graphic synthesizer Weston of the Host subsystem.
  • Weston can set or update graphic objects based on the graphic object setting information.
  • the graphic object may be an application window
  • the graphic object setting information may be window attribute information
  • Weston may update the corresponding window according to the window attribute information, such as changing a window transparency.
  • the p_surface may provide an interface for calling the application component in the Host subsystem.
  • the application component calls the graphic object to process the related interface
  • the corresponding operation of the interface is performed to implement the graphic object setting, such as window property update.
  • the application component in the Host subsystem receives the video window attribute update event (which can be triggered by the user by adjusting the video window size or transparency, the application component sends the updated window attribute information to the video)
  • the surface of the window corresponds to p_surface1, and the window attribute information is sent to Weston by p_surface1, and Weston redraws the window according to the window attribute information.
  • the lifecycle of p_surface can be managed by application components in the Host subsystem.
  • the application component in the Host subsystem may create p_surface1 according to the request for displaying the graphics data obtained by the Guest subsystem; when the graphic object corresponding to p_surface1 in the Guest subsystem is destroyed, p_surface1 is destroyed.
  • the p_surface1 corresponding to the graphics object in the Guest subsystem for providing the graphics data is destroyed.
  • p_surface can be created based on the classes provided by the system, such that the functional properties of the parent class (ie, the classes provided by the system) can be inherited. Further, considering different application scenarios, there may be different requirements. Therefore, when a p_surface is created based on a system-provided class, some parameters or attributes are reset in combination with the current application scenario.
  • the video playback application can be based on the system when creating p_surface
  • the class is created and set to the sub-surface of the h5surface, controlling the width, position, and so on.
  • graphics data sent by multiple p_surfaces may be sent to a local surface (ie, a surface in the Host subsystem) to obtain synthesized graphics data, which is sent to Weston by the local surface, and finally submitted.
  • a local surface ie, a surface in the Host subsystem
  • the above graphic synthesis method can be applied to some applications, and some functions need to be implemented based on the Host subsystem, and some functions need to be implemented based on the Guest subsystem.
  • the video playback app when the video playback app acquires a video play event in the process in the Host subsystem (this event can be triggered by the user submitting a video play request through the user interface), create p_surface1, P_surface1 corresponds to the surface of the video window in Weston; further, the process of the video playback app in the Host subsystem sends the event to the video playback app in the guest subsystem (see the information interaction between operating system processes)
  • the process of the video playback app in the guest subsystem acquires video data from the network side according to the event, and the video decoded content is transmitted to the VideoView control through the MediaCodec (media decoder), and then submitted to the surfaceflinger, and passed through the p_surface1.
  • the graphic data is sent to the weston for synthesis to
  • the process in the guest subsystem of the video playback app sends the event to the process in the video subsystem, and the process in the video subsystem app destroys p_surface1 according to the event.
  • the p_surface in the Host subsystem receives the graphics data sent by the layer corresponding to the p_surface in the guest subsystem graphics synthesizer by the above-mentioned embodiment of the present application, and the p_surface will receive the received data.
  • the graphics data is sent to the host subsystem graphics synthesizer.
  • the p_surface provides the transmission function of the graphics data between the two subsystems. This achieves compatibility between different operating systems at the graphics processing level.
  • Tom's mobile phone uses the YunOS system, and its system architecture is shown in Figure 1.
  • the video playback app is installed on the mobile phone.
  • the video data downloading and decoding related functions in the application are based on Android, and the playback control related functions are implemented based on YunOS.
  • the main interface of the video playback app is shown in FIG. 4, which mainly includes the video window 100.
  • the play control bar 200 and the window control bar 300 are displayed.
  • the play control bar 200 is provided with a play control button, and specifically includes a pause button 201, a stop button 202, a play button 203, and a process drag bar 204.
  • a window maximizer key 301 and a window restore key 302 are disposed on the window control strip 300.
  • the main interface of the video playback app also includes an exit key 400.
  • Tom selects a movie and submits a request to view the movie, after which the movie is played in the video window 100.
  • the video playback app process in the Host subsystem creates a p_surface; the video playback app process in the Guest subsystem creates a buffer queue, obtains video data of the movie from the network side, and performs the obtained video data. Decoding, the decoded video data is stored in the buffer queue.
  • the layer in the graphics synthesizer SurfaceFlinger sends the video data in the buffer queue to the p_surface; in the Host subsystem, the p_surface sends the video data to the graphics synthesizer weston, which combines the video data, and Displayed in the video window 100 by the display driver.
  • the video playback app process sends the relevant information of the maximized video window 100 (such as the indication information of the maximized window and/or the window attribute information, etc.) to the p_surface, which p_surface will The information is sent to weston, which repaints the video window 100 based on this information to maximize display.
  • relevant information of the maximized video window 100 such as the indication information of the maximized window and/or the window attribute information, etc.
  • the video playback app process in the Host subsystem sends an event generated by clicking the pause button 201 to the Bridge Proxy, and the Bridge Proxy sends the event to the Bridge corresponding to the video playback app process in the Guest subsystem.
  • Service, Bridge Service sends the event to the video playback app process in the Guest subsystem.
  • the video playback app process responds to the event and no longer sends video data to the p_surface through the layer.
  • the video playback app process in the Host subsystem sends an event generated by clicking the play button 203 to the Bridge Proxy, and the Bridge Proxy sends the event to the Bridge corresponding to the video playback app process in the Guest subsystem.
  • Service, Bridge Service sends the event to the video playback app process in the Guest subsystem.
  • the video playback app process responds to the event and continues to send video data to the p_surface through the layer.
  • the video window 100 is closed.
  • the video playback app process in the Guest subsystem sends the event to the Bridge Proxy through the Bridge Service, and the Bridge Proxy sends the event to the video playback app process in the Host subsystem; the video playback app process in the Host subsystem.
  • the video window 100 is closed and the p_surface is destroyed.
  • the video playback app process in the Host subsystem acquires the event of clicking the exit key 400, destroys the Bridge Proxy, and closes the video playback app.
  • the Android application when the embodiment of the present application is applied to a scenario in which the Android and the YunOS are integrated, the Android application can be made transparent, and the Android application can compile the corresponding APK or binary code through the SDK or the NDK without performing an Android application. Too many improvements.
  • the embodiments of the present application can implement diversification of cross-system integration.
  • Host SDKs for example, h5, qt, domoless, native, etc.
  • the input access method can be customized.
  • the embodiment of the present application provides a fusion of application-level content, which can display the content processed by the application process of YunOS and Android in one window, and organically integrate two different operating systems into one, and a unified interactive experience does not need to be performed. Switch windows to manage all content in a unified manner.
  • the embodiment of the present application provides a graphics synthesis system, which can implement the graphics synthesis process described in the foregoing embodiment.
  • FIG. 5 is a schematic structural diagram of a graphics synthesis system according to an embodiment of the present application.
  • the system may include: a first subsystem graphics synthesizer 51, a second subsystem graphics synthesizer 52, and a first one of the first subsystems. Control 53;
  • a first control 53 in the first subsystem configured to receive graphic data sent by the graphic object corresponding to the first control in the second subsystem graphic synthesizer 52, and send the graphic data to the first subsystem Graphic synthesizer 51.
  • first subsystem graphics synthesizer 51 is further configured to: receive graphics data sent by the graphic object in the first subsystem.
  • first subsystem graphics synthesizer 51 is further configured to: synthesize the graphics data sent by the first control 53 and the graphics data sent by the graphics object in the first subsystem.
  • the first control is a plurality of, the plurality of first controls send the respective received graphics data to the graphic objects in the first subsystem; correspondingly, the first subsystem graphics synthesizer 51 is specifically configured to: And receiving the graphic data sent by the graphic object in the first subsystem; wherein the graphic object sends the graphic data sent by the plurality of first controls as the graphic data corresponding to the graphic object to the first subsystem graphic synthesizer.
  • the first control 53 is further configured to: receive graphic object setting information sent by the application component in the first subsystem; and send the received graphic object setting information to the first subsystem graphic synthesizer 51.
  • the graphic object is an application window, and the graphic object setting information includes window attribute information.
  • the first subsystem further includes an application component; and the application component in the first subsystem is configured to create the first control.
  • the application component in the first subsystem is specifically configured to: create a first control corresponding to the graphic object for providing graphic data in the second subsystem according to the request for using the graphic data in the second subsystem 53.
  • the first subsystem further includes an application component; and the application component in the first subsystem is configured to destroy the first control 53.
  • the application component in the first subsystem is specifically configured to: after receiving information that the graphic object corresponding to the first control 53 in the second subsystem is destroyed, destroying the first control 53; or Upon receiving an indication to end the use of the graphical data in the second subsystem, the first control 53 corresponding to the graphical object in the second subsystem for providing the graphical data is destroyed.
  • the first subsystem further includes a first application component
  • the second subsystem further includes a second application component; correspondingly, the first application component of the first subsystem is configured to be in the first subsystem
  • the first system service component 54 sends control information, the control information is used to indicate that the graphic data in the second subsystem is acquired; the first system service component 54 is specifically configured to send the control information to the second subsystem.
  • the second system service component 55 is configured to send the control information to the second application component in the second subsystem.
  • the first subsystem is a Host subsystem
  • the second subsystem is a Guest subsystem.
  • the embodiment of the present application provides an information interaction system, and the system The information interaction method described in the foregoing embodiment can be implemented.
  • FIG. 6 it is a schematic diagram of an information interaction system architecture provided by an embodiment of the present application.
  • the system may include: a first system service component 61 in the first subsystem, and a second system service component 62 in the second subsystem, where:
  • a first system service component 61 in the first subsystem configured to receive first information sent by the first application component in the first subsystem, and send the first information to a second system in the second subsystem Service component 62;
  • the second system service component 62 is configured to send the first information to a second application component in the second subsystem.
  • the second system service component 62 is further configured to: receive the second information sent by the second application component, and send the second information to the first system service component 61; wherein, the The second information is obtained by the first application component according to the first information.
  • the first system service component 61 is further configured to: send the second information to the first application component.
  • the first application component is specifically configured to: send the first information to the first system service component 61 in one or more of the following cases:
  • the application components in the second subsystem need to be notified for processing.
  • the information comprises: control information and/or data.
  • the first subsystem is a Host subsystem
  • the second subsystem is a Guest subsystem
  • the first subsystem is a Guest subsystem
  • the second subsystem is a Host subsystem
  • These computer program instructions can also be stored at a computer or other programmable data location.
  • the device is readable in a computer readable memory that operates in a particular manner such that instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device implemented in a flow or a flow and/or block diagram of the flowchart The function specified in the box or in multiple boxes.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Abstract

L'invention concerne un procédé de composition graphique, un procédé d'interaction d'informations, et un système. Dans l'application, un premier élément de commande dans un premier sous-système reçoit des données graphiques transmises par un objet graphique correspondant au premier élément de commande dans un compositeur graphique d'un second sous-système. Le premier élément de commande transmet les données graphiques reçues à un compositeur graphique du premier sous-système. Le premier élément de commande dans le premier sous-système correspond à l'objet graphique dans le compositeur graphique du second sous-système. Le premier élément de commande fournit une fonction permettant de transmettre des données graphiques entre les deux sous-systèmes, réalisant ainsi une compatibilité entre différents systèmes d'exploitation dans une couche de traitement graphique.
PCT/CN2017/078035 2016-03-31 2017-03-24 Procédé de composition graphique, procédé d'interaction d'informations, et système WO2017167125A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610202571.2 2016-03-31
CN201610202571.2A CN107291561B (zh) 2016-03-31 2016-03-31 一种图形合成方法、信息交互方法及系统

Publications (1)

Publication Number Publication Date
WO2017167125A1 true WO2017167125A1 (fr) 2017-10-05

Family

ID=59962568

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/078035 WO2017167125A1 (fr) 2016-03-31 2017-03-24 Procédé de composition graphique, procédé d'interaction d'informations, et système

Country Status (2)

Country Link
CN (1) CN107291561B (fr)
WO (1) WO2017167125A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110851205A (zh) * 2019-11-12 2020-02-28 成都九鼎瑞信科技股份有限公司 一种基于水务云平台的app管理方法
CN117149341A (zh) * 2023-10-31 2023-12-01 成都阿加犀智能科技有限公司 一种显示Linux GUI程序的方法、装置、设备及介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1797345A (zh) * 2004-12-30 2006-07-05 微软公司 用于虚拟化图形子系统的系统和方法
CN101655798A (zh) * 2008-08-18 2010-02-24 联想(北京)有限公司 一种计算机和虚拟机环境中应用程序部署和运行的方法
US20110154328A1 (en) * 2009-12-21 2011-06-23 Samsung Electronics Co., Ltd. Virtualization Apparatus and Method
CN102945169A (zh) * 2012-12-05 2013-02-27 江苏鸿信系统集成有限公司 一种基于Android的Native APP融合Web APP开发系统
CN103370689A (zh) * 2010-10-01 2013-10-23 Flex Electronics ID Co.,Ltd. 跨环境应用兼容

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296204B (zh) * 2007-04-25 2010-11-03 财团法人工业技术研究院 共享数字家庭电子服务资源的系统及方法
CN102053871B (zh) * 2009-10-28 2013-03-13 中国移动通信集团公司 一种应用程序图像的显示方法和装置
US9354900B2 (en) * 2011-04-28 2016-05-31 Google Technology Holdings LLC Method and apparatus for presenting a window in a system having two operating system environments
CN102981894B (zh) * 2011-09-05 2016-07-06 联想(北京)有限公司 显示方法和电子设备
CN104360900B (zh) * 2014-11-03 2020-05-12 上海迈微软件科技有限公司 用于运行多操作系统的方法以及相应的系统和移动设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1797345A (zh) * 2004-12-30 2006-07-05 微软公司 用于虚拟化图形子系统的系统和方法
CN101655798A (zh) * 2008-08-18 2010-02-24 联想(北京)有限公司 一种计算机和虚拟机环境中应用程序部署和运行的方法
US20110154328A1 (en) * 2009-12-21 2011-06-23 Samsung Electronics Co., Ltd. Virtualization Apparatus and Method
CN103370689A (zh) * 2010-10-01 2013-10-23 Flex Electronics ID Co.,Ltd. 跨环境应用兼容
CN102945169A (zh) * 2012-12-05 2013-02-27 江苏鸿信系统集成有限公司 一种基于Android的Native APP融合Web APP开发系统

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110851205A (zh) * 2019-11-12 2020-02-28 成都九鼎瑞信科技股份有限公司 一种基于水务云平台的app管理方法
CN117149341A (zh) * 2023-10-31 2023-12-01 成都阿加犀智能科技有限公司 一种显示Linux GUI程序的方法、装置、设备及介质
CN117149341B (zh) * 2023-10-31 2024-01-05 成都阿加犀智能科技有限公司 一种显示Linux GUI程序的方法、装置、设备及介质

Also Published As

Publication number Publication date
CN107291561B (zh) 2020-11-24
CN107291561A (zh) 2017-10-24

Similar Documents

Publication Publication Date Title
US11347530B2 (en) Method, apparatus and system for transparent unification of virtual machines
US10976981B2 (en) Remote desktop exporting
Bierbaum et al. VR Juggler: A virtual platform for virtual reality application development
US9606629B2 (en) Systems and methods for gesture interaction with cloud-based applications
US10063430B2 (en) Systems and methods for workspace interaction with cloud-based applications
US10817086B2 (en) Touch support for remoted applications
US9965151B2 (en) Systems and methods for graphical user interface interaction with cloud-based applications
CN104704448A (zh) 本地和远程计算环境之间的反向无缝集成
WO2019007216A1 (fr) Dispositif et procédé de traitement de couche graphique
CN103262057B (zh) 跨环境通信框架
US9197697B2 (en) Cloud computing system and method
US9886189B2 (en) Systems and methods for object-based interaction with cloud-based applications
US20140143305A1 (en) Apparatus and system for providing software service using software virtualization and method thereof
US20140026057A1 (en) Providing access to a remote application via a web client
US7463268B2 (en) Providing 3D graphics across partitions of computing device
WO2017167127A1 (fr) Procédé de composition d'image, procédé de configuration de fenêtre, et système
EP2782038A1 (fr) Gestion de ressources dans un processeur pour des applications fiables et non-fiables
WO2017167126A1 (fr) Procédé d'affichage de fenêtre, procédé d'échange d'informations et système
JP2005209173A (ja) 非同期挙動変更をマネージドアプリケーションプロセスに誘導するためのシステムおよび方法
WO2017167125A1 (fr) Procédé de composition graphique, procédé d'interaction d'informations, et système
CN114860401B (zh) 异构云桌面调度系统、方法、服务系统、装置及介质
US20150193284A1 (en) Host/hosted hybrid apps in multi-operating system mobile and other computing devices
EP2782010A1 (fr) Gestion hierarchique des ressources
US11704159B2 (en) System and method for unified infrastructure architecture
WO2014064535A2 (fr) Systèmes et procédés pour une interaction basée sur des objets avec des applications basées sur le nuage

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17773155

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17773155

Country of ref document: EP

Kind code of ref document: A1