WO2018119711A1

WO2018119711A1 - Multimedia encoding/decoding method and device for multi-operating system, and electronic device

Info

Publication number: WO2018119711A1
Application number: PCT/CN2016/112494
Authority: WO
Inventors: 李向远
Original assignee: 深圳前海达闼云端智能科技有限公司
Priority date: 2016-12-27
Filing date: 2016-12-27
Publication date: 2018-07-05
Also published as: CN107996026A

Abstract

A multimedia encoding/decoding method and device for a multi-operating system, and an electronic device. The method comprises: in a client operating system, receiving a multimedia processing request sent by an adaption layer and sending the multimedia processing request to a host operating system, the multimedia processing request comprising a multimedia file (201); and in an OpenMAX integration layer (IL) of the host operating system, loading and controlling a hardware codec in the host operating system to encode/decode the multimedia file (202). The described method can enable a client operating system to use a hardware codec in the host operating system in a cross-system manner so as to achieve the purpose of hardware acceleration.

Description

Multi-operating system multimedia codec method, device and electronic device

Technical field

The present application relates to the field of virtualization technologies, and in particular, to a multi-operating system multimedia codec method, apparatus, and electronic device.

Background technique

Mobile terminals have become an important tool for users' daily work and life. While mobile terminals are driving the rapid development of mobile Internet, mobile terminals contain rich and diverse information (such as enterprise data access, business communication, social networks, financial management, Games, etc.), mobile terminals have become the new focus of cybercrime. For information security and privacy protection, mobile virtualization has become the future development direction of mobile terminals.

Mobile virtualization allows multiple operating systems or virtual machines to run simultaneously on mobile phones or wireless handheld devices, using the Hypervisor to create a secure, stand-alone software runtime environment on the underlying hardware. With mobile virtualization, users do not need to carry two or more mobile devices to access multiple operating systems on a single physical handheld device. Mobile virtualization has significant security features.

The isolation provided by the virtualization technology can isolate multiple operating systems on a single terminal, and prevent processes on each operating system from adversely affecting other operating systems. A typical application scenario is a mobile device such as a mobile phone through virtualization technology. The separation of the enterprise system and the personal system is realized, and the potential harm caused by the process on the personal system is prevented, and the demand for the BYOD (Bring Your Own Device) is met by some enterprises with security requirements.

With the in-depth development of multimedia applications in life, each virtual machine of the terminal must have a multimedia codec. At present, the guest operating system (Guest OS) can only implement software codec through the CPU, resulting in video files of many formats. Unable to support, high power consumption, and smooth playback.

The disadvantages of the prior art are:

The guest's Guest OS can only implement software codec through the CPU, resulting in many formats of video. Files cannot be supported, playback is not smooth, and power consumption is high (heating, shortening battery life).

Summary of the invention

An object of the present application is to solve the technical problem that the guest OS of the terminal can only implement software codec through the CPU, which causes video files of many formats to be unable to be supported and played smoothly.

In a first aspect, the embodiment of the present application provides a multi-operating system multimedia codec method, including:

Receiving, in the guest operating system, a multimedia processing request sent by the adaptation layer and transmitting the multimedia processing request to a host operating system, where the multimedia processing request includes a multimedia file;

In the host operating system OpenMAX integration layer IL, the hardware codec in the host operating system is loaded and controlled to encode and decode the multimedia file.

In a second aspect, the embodiment of the present application provides a multi-operating system multimedia codec device, including: a host operating system, a client operating system, and a vOpenMAX front-end Front end located in a guest operating system and located in a host operating system. vOpenMAX backend;

The vOpenMAX front end Front end is configured to receive, in the guest operating system, a multimedia processing request sent by the adaptation layer and send the multimedia processing request to the host operating system, where the multimedia processing request includes a multimedia file;

The vOpenMAX backend end end is configured to load and control a hardware codec in the host operating system to encode and decode the multimedia file in a host operating system OpenMAX integration layer IL.

In a third aspect, an embodiment of the present application further provides an electronic device, where the electronic device includes: a memory, one or more processors, and one or more modules, where the one or more modules are stored in the In the memory, and configured to be executed by the one or more processors, The one or more modules include instructions for performing the various steps in the method as described above.

In a fourth aspect, an embodiment of the present application provides a computer program product for use in conjunction with an electronic device, the computer program product comprising a computer program embedded in a computer readable storage medium, the computer program comprising The electronic device is caused to execute instructions of the various steps in the method as described above.

The benefits are as follows:

The embodiment of the present application can code and decode the multimedia file by using a hardware codec in the host operating system in the integration layer IL of the OpenMAX of the guest operating system, thereby implementing the client operating system across the system. The hardware codec of the host operating system is used to provide hardware acceleration capability for the guest operating system, and further, since the hardware codec can support multi-format files, and the codec speed is fast, and no CPU is required, the implementation of the present application is adopted. The solution provided by the example can support multi-format files, play smoothly, and has low power consumption, which can prolong the battery life, and solve the problems that the video files of many existing formats cannot be supported, the playback is not smooth, and the power consumption is large.

DRAWINGS

Specific embodiments of the present application will be described below with reference to the accompanying drawings, in which:

FIG. 1 is a schematic structural diagram of a virtualization model in the prior art;

FIG. 2 is a schematic flowchart showing the implementation of a multi-operating system multimedia codec method in Embodiment 1 of the present application;

3 is a schematic structural diagram 1 of a multi-operating system multimedia codec device in Embodiment 2 of the present application;

FIG. 4 is a second schematic structural diagram of a multi-operating system multimedia codec device according to Embodiment 2 of the present application;

FIG. 5 is a schematic structural diagram of an electronic device according to Embodiment 3 of the present application;

6 is a schematic structural diagram of a mobile phone in Embodiment 5 of the present application;

FIG. 7 is a schematic diagram showing a structure of a multi-operating system of an existing Android multimedia framework;

8 is a schematic structural diagram of multiple operating systems of an Android multimedia framework in Embodiment 6 of the present application;

FIG. 9 is a schematic structural diagram of a tablet computer in Embodiment 7 of the present application.

detailed description

The exemplary embodiments of the present application are further described in detail below with reference to the accompanying drawings, in which the embodiments described are only a part of the embodiments of the present application, but not all embodiments. An exhaustive example. And in the case of no conflict, the features in the embodiments and the embodiments in the description can be combined with each other.

FIG. 1 is a schematic structural diagram of a virtualization model in the prior art. As shown in the figure, at the bottom is the entire physical system, that is, system hardware, which mainly includes a processor, a memory, and an input/output device; It is a virtualization layer that runs a virtual machine monitor (referred to as VMM or Hypervisor for short). The main function of the virtual machine monitor is to manage the real physical hardware platform and provide a corresponding virtual hardware platform for each virtual client. The Hypervisor implements the above functions through a host. The host runs a virtual machine (Host VM) on which the host operating system (Host OS) runs.

Figure 1 shows an example of three virtual machines (VMs), each of which can be thought of as a small but complete computer system with its own "system hardware", including its own processor, memory, and input and output. device. On this computer system, the virtual machine's own operating system (Guest OS) is running, such as Android, Windows or Linux.

The inventor noticed during the invention:

Currently, only Host OS has hardware acceleration capability, and Guest OS can only implement software codec through CPU. For Guest OS, it has the following drawbacks:

1) Limited format support

For common resolution AVI, RMVB and other files, most CPUs can do the job. With the popularity of high-definition video (1080i/p), the CPU becomes more and more difficult. Therefore, video files of many formats cannot be supported on terminals with only soft decoding.

2) High CPU usage, unsmooth playback, and high power consumption

Since the resolution of high-definition video is much higher than that of the general format video, the code rate of the high-definition video is very high, and the compression ratio of the VC-1 and H.264 encoding is very high, and the calculation operation of the decoding operation is large. Therefore, conventionally using CPU decoding directly (that is, often referred to as "soft solution") will greatly consume the computing power of the CPU. Some older CPUs have a CPU usage of up to 90% when the H.264 solution is soft, and the older CPU It may not be played at all.

In view of the above deficiencies, the embodiment of the present application proposes a multi-system multimedia hardware virtualization solution based on OpenMAX IL Core, so that the guest OS can be accelerated by using the hardware of the Host OS through the virtualization technology, and the upper layer of the Guest OS can still support the software codec. The choice of hardware codec, that is, the Guest OS and the Host OS, can support two codecs at the same time, as explained below.

Open Multimedia Acceleration, a multimedia application standard that includes application layer AI, integration layer IL and development layer DL, embedded processor or hardware codec module hardware manufacturer, can provide standard OpenMAX IL Layer software interface, software developers can develop multimedia programs based on this level of standardized interfaces.

The technical solution provided by the embodiment of the present application can be applied to all multimedia systems adopting the OpenMAX framework standard to implement hardware virtualization, including the Android multimedia framework (StageFright+OpenMAX) but not limited to Android.

Embodiment 1

FIG. 2 is a schematic flowchart of the implementation of the multi-operating system multimedia codec method in the embodiment of the present application. As shown in the figure, the multi-operating system multimedia codec method may include the following steps:

Step 201: Receive, in a guest operating system, a multimedia processing request sent by an adaptation layer, and send the multimedia processing request to a host operating system, where the multimedia processing request includes a multimedia file.

Step 202: Load and control a hardware codec in the host operating system to encode and decode the multimedia file in a host operating system OpenMAX integration layer IL.

In a specific implementation, the multiple operating systems may include a host operating system and a guest operating system, and the guest operating system may be one, two or more.

The embodiment of the present application may receive, in an OpenMAX integration layer IL of a guest operating system, a multimedia processing request sent by an adaptation layer and send the multimedia processing request to a host operating system, where the multimedia processing request may include a multimedia file; In the OpenMAX integration layer IL of the host operating system, the hardware codec in the host operating system is loaded and controlled to encode and decode the multimedia file.

In an implementation, before the receiving the multimedia processing request sent by the adaptation layer, the method may further include:

And acquiring, at the adaptation layer of the guest operating system, a multimedia file sent by the multimedia application, and adapting the codec to the multimedia file.

In a specific implementation, when the multimedia application in the guest operating system receives the user After the multimedia processing request, an adaptation layer of the guest operating system may select a suitable codec for the multimedia file and determine the class of the codec. The class of codecs may include a software codec and a hardware codec.

The multimedia code is adapted to the codec, and the decoder of the multimedia file may be determined according to the encoding manner of the multimedia file, or the encoder of the multimedia file may be determined according to the decoding manner of the multimedia file.

In a specific implementation, there may be multiple codecs supporting the same format, which may include a hardware codec and a software codec, and the most suitable codec may be selected according to a preset rule when adapting the codec, for example, for example, : Select software codec for multimedia files with low resolution requirements, hardware codecs for multimedia files with high resolution requirements, etc.

When determining that the codec of the multimedia file is a hardware codec, sending a command to a hard codec component in the host operating system by cross-system communication, calling a hardware codec in the host operating system to the multimedia The file is coded and decoded.

The method provided by the embodiment of the present application may add a step of determining the codec category by modifying an adaptation layer in a guest operating system, and determine that the codec of the multimedia file is a hardware codec. When the multimedia file is coded and decoded by using a hardware codec in the host operating system for cross-system communication, the hardware operating code of the host operating system is implemented by the guest operating system across the system to achieve hardware acceleration.

In an implementation, the method may further include:

If the codec of the multimedia file is a software codec, software OpenMAX IL in the guest operating system loads and controls a software codec in the guest operating system to encode and decode the multimedia file .

In the embodiment of the present application, for a software codec (SW Codec), the multimedia file may still be encoded and decoded using a software codec in the guest operating system.

In an implementation, the receiving the multimedia processing request sent by the adaptation layer and the multimedia processing The request is sent to the host operating system, specifically: in the OpenMAX integration layer IL of the guest operating system, as an interface for cross-system communication, receiving a multimedia processing request sent by the adaptation layer and sending the multimedia processing request to the host operating system OpenMAX integration layer IL;

The hardware codec in the host operating system loads and controls the codec of the multimedia file in the OpenMAX integration layer IL of the host operating system, which may be: in the OpenMAX integration layer IL of the host operating system. And as a server of the client operating system hardware codec, loading and controlling a hardware codec in the host operating system to encode and decode the multimedia file delivered by the guest operating system according to the multimedia processing request.

In a specific implementation, the OpenMAX integration layer IL may specifically load and control a multimedia codec in the host operating system by virtual vOpenMAX cross-system communication, and the vOpenMAX may include: located at the client The vOpenMAX front-end Front end in the operating system and the vOpenMAX back-end Back end in the host operating system;

When determining that the codec of the multimedia file is a hardware codec, the vOpenMAX Front end communicates with the vOpenMAX Back end across the system;

The vOpenMAX Back end calls a hardware codec in the host operating system to encode and decode the multimedia file delivered by the guest operating system.

In a specific implementation, the OpenMAX Core required for the hardware codec operation can be divided into two parts: vOpenMAX Front end and vOpenMAX Back end. The vOpenMAX Front end is located on the Guest OS as the interface of the HW OpenMAX Core of the guest operating system; the vOpenMAX Back end is located in the Host OS. It acts as the vOpenMAX Core server and performs all the functions of OpenMAX Core and all the functions of OpenMAX IL, including vOpenMAX Core and The vOpenMAX Component provides hardware acceleration for the front end (ie, the guest operating system) by loading the HW Codec of the Host OS.

vOpenMAX Front end and vOpenMAX Back end can communicate through existing QEMU PIPE, Socket and other cross-system communication methods.

In an implementation, the multimedia processing request is sent to the host operating system in the guest operating system, and in the OpenMAX integration layer IL of the host operating system, the hardware codec in the host operating system is loaded and controlled to the multimedia The file is encoded and decoded, which can be:

Sending a notification message to the host operating system in the guest operating system, in the OpenMAX integration layer IL of the host operating system, loading a corresponding hardware codec according to the notification message;

Sending a multimedia file to the host operating system in the guest operating system, and controlling the hardware codec to encode and decode the multimedia file in an OpenMAX integration layer IL of the host operating system.

In a specific implementation, the guest operating system sends a notification message to the host operating system through cross-system communication between the vOpenMAX Front end and the vOpenMAX Back end, and the host operating system loads the corresponding message according to the notification message. Hardware codec; the guest operating system sends a multimedia file to a hardware codec of the host operating system by cross-system communication between the vOpenMAX Front end and the vOpenMAX Back end, by the host The multimedia codec of the operating system encodes and decodes the multimedia file.

In a specific implementation, the guest operating system may send a control command and data to be transmitted (for example, parameters, etc.) to the host operating system through cross-system communication between the vOpenMAX Front end and the vOpenMAX Back end. The control command and the data to be delivered can be passed to the vOpenMAX Back end of the host operating system under the management of the hypervisor hypervisor.

In an implementation, after the hardware codec of the host operating system completes encoding and decoding the multimedia file, the method may further include:

Passing the coded data back to the guest operating system; or,

The codec processing status is displayed on the host operating system side.

In a specific implementation, after the hardware codec of the host operating system completes the encoding and decoding operation on the multimedia file, the coded data may be transmitted back to the guest operating system, or directly on the host operating system side. The display codec is complete.

The embodiment of the present application provides a multi-system multimedia hardware virtualization solution based on OpenMAX IL Core. The guest OS can be accelerated by using the hardware of the Host OS through the virtualization technology, and the upper layer of the Guest OS can still support the software codec and the hardware codec. Select, that is, the Guest OS, like the Host OS, can support both codecs.

Embodiment 2

Based on the same inventive concept, a multi-operating system multimedia codec device is also provided in the embodiment of the present application. Since the principle of solving the problem of these devices is similar to a multi-operating system multimedia codec method, the implementation of these devices can be referred to the method. The implementation, repetitions will not be repeated.

FIG. 3 is a schematic structural diagram 1 of a multi-operating system multimedia codec device according to Embodiment 2 of the present application. As shown in the figure, the multi-operating system multimedia codec device may include: a host operating system 301, and a guest operating system 302. And a vOpenMAX front end Front end 3021 located in the guest operating system 302 and a vOpenMAX back end Back end 3011 located in the host operating system 301;

The vOpenMAX backend end end is configured to load and control a hardware codec in the host operating system to encode and decode the multimedia file in an OpenMAX integration layer IL of the host operating system.

In a specific implementation, the multimedia application can communicate with the OpenMAX IL core core and components, and the component can operate audio, video, picture or other data.

The multi-operating system multimedia codec device provided by the embodiment of the present application can compile the multimedia file by using a hardware codec in the host operating system through vOpenMAX cross-system communication in the OpenMAX integration layer IL of the guest operating system. Decoding, the hardware operating code of the host operating system is implemented by the guest operating system across the system to achieve hardware acceleration.

FIG. 4 is a schematic structural diagram of a multi-operating system multimedia codec device according to Embodiment 2 of the present application. As shown in the figure, the guest operating system 302 may further include:

The adapting module 3022 is configured to: before the multimedia processing request sent by the receiving adaptation layer, obtain, at an adaptation layer of the guest operating system, a multimedia file sent by the multimedia application, to edit the multimedia file decoder.

In a specific implementation, the guest operating system 302 may further include:

a client software codec 3023, for if the codec of the multimedia file is a software codec, software OpenMAX IL in the guest operating system loads and controls software coding in the guest operating system The decoder encodes and decodes the multimedia file.

In an implementation, the vOpenMAX Front end may be specifically used in the OpenMAX integration layer IL of the guest operating system as an interface for cross-system communication, receiving a multimedia processing request sent by the adaptation layer and sending the multimedia processing request to the host operation. System OpenMAX integration layer IL;

The vOpenMAX Back end may be specifically used in a OpenMAX integration layer IL of the host operating system, as a server of the guest operating system hardware codec, loading and controlling hardware codec in the host operating system according to the multimedia processing request. The program encodes and decodes the multimedia file delivered by the guest operating system.

In an implementation, the vOpenMAX Front end may be specifically used in the client operating system The system sends a notification message to the host operating system, where the vOpenMAX Back end is specifically configured to load, in the OpenMAX integration layer IL of the host operating system, a corresponding hardware codec according to the notification message;

The vOpenMAX Front end can also be used to send a multimedia file to the host operating system in the guest operating system, and the vOpenMAX Back end can also be used in an OpenMAX integration layer IL of the host operating system. The hardware codec controlling the host operating system encodes and decodes the multimedia file.

In an implementation, the apparatus may further include:

a data backhaul module, configured to send the coded data back to the guest operating system in an OpenMAX integration layer IL of the host operating system;

or,

And a display module, configured to display a codec processing state on the host operating system side.

Embodiment 3

Based on the same inventive concept, an embodiment of the present application further provides an electronic device, which will be described below.

5 is a schematic structural diagram of an electronic device in Embodiment 3 of the present application. As shown, the electronic device includes: a memory 401, one or more processors 402, and one or more modules, the one or A plurality of modules are stored in the memory and configured to be executed by the one or more processors, the one or more modules including steps for performing the multi-operating system multimedia codec method as described above Instructions.

The electronic device provided by the embodiment of the present application increases the step of determining the codec category by modifying an adaptation layer in the guest operating system, and determines that the codec of the multimedia file is a hardware codec. When the vOpenMAX cross-system communication uses the hardware codec in the host operating system to encode and decode the multimedia file, the hardware operating code of the host operating system is used to implement hardware acceleration by the guest operating system. .

Embodiment 4

Based on the same inventive concept, the embodiment of the present application further provides a computer program product, which will be described below.

The computer program product provided by the embodiment of the present application encodes an instruction for executing a process, and the process includes a method for multi-operating system multimedia codec as described above.

In a specific implementation, the computer program product can be used in conjunction with an electronic device.

In order to facilitate the implementation of the present application, the following description will be made by way of example.

Embodiment 5

The embodiment of the present application takes a mobile phone as a high-definition video as an example.

FIG. 6 is a schematic structural diagram of a mobile phone in Embodiment 5 of the present application. As shown in the figure, the mobile phone is a dual-operating mobile communication terminal, and the dual operating system may be: a personal operating system and an enterprise operating system. Assume that the enterprise operating system is the host operating system (Host OS) and the personal operating system is the guest operating system (Guest OS).

(1) The user opens a multimedia application in a personal operating system to play a video file;

(2) The embodiment of the present application may select a suitable decoder for the video file in an adaptation layer of the personal operating system, and then determine whether the decoder is a hardware codec (HW Codec) or Software Codec (SW Codec):

If it is SW Codec, the software decoder in the personal operating system can be called to perform decoding operation on the video file;

If it is HW Codec, the vOpenMAX Front end can communicate with the vOpenMAX Back end in the enterprise operating system to call the hardware codec in the enterprise operating system to decode the video file.

In a specific implementation, the personal operating system may notify the enterprise operating system to load a corresponding codec Codec by using a cross-system communication technology (eg, QemuPipe, Socket, etc.); the enterprise operating system loads the corresponding Codec;

Thereafter, the personal operating system can transmit the compressed data to the codec of the enterprise operating system side through the cross-system communication of the vOpenMAX Back end in the enterprise operating system through the vOpenMAX Front end; the hardware codec HW of the enterprise operating system side Codec decodes the video file.

After the Codec decoding of the enterprise operating system is completed, the embodiment of the present application can directly display on the enterprise operating system side according to the display system implementation manner, and can also transmit the decoded data back to the personal operating system.

Embodiment 6

In the embodiment of the present application, a multimedia system using the Android multimedia framework (StageFright+OpenMAX) is taken as an example. The codec function of StageFright is implemented by using the OpenMAX framework. The adaptation layer of OpenMAX is an encapsulation layer on the OpenMAX IL layer, which can be used by StageFright. transfer.

FIG. 7 is a schematic diagram showing the structure of a multi-operating system of the existing Android multimedia framework. As shown in the figure, after the OpenMAX IL APP in the host operating system (Host OS) initiates a multimedia processing event event, the OpenMAX Component is called by the host's OpenMAX Core. Then operate the H/W Codec of the Android Kernel;

After the OpenMAX IL APP in the guest operating system (Guest OS) initiates a multimedia processing event, the OpenMAX Component is called by the client's OpenMAX Core, and the S/W Codec of the Android Kernel is operated.

The embodiment of the present application can modify the interface of the OpenMAX Core so that the guest operating system can support hardware codec.

FIG. 8 is a schematic diagram showing the structure of a multi-operating system of the Android multimedia framework in the sixth embodiment of the present application. The following is an example of video decoding of a video file encoded by AVC (Advanced Video Coding) in the Android system.

StageFright's player class AwesomePlayer creates an event dispatcher based on the view Selecting a suitable splitter from the head of the frequency file to separate the audio and video tracks of the video file;

A separate mVideoTrack (video) data stream is generated by setVideoSource() to provide the desired data stream for the video decoder; a separate mAudioTrack (audio) data stream is generated by setAudioSource() to provide the audio decoder with the required data stream.

AwesomePlayer calls the OMX Client::connect function to obtain the OMX service by sharing the IMOX variable.

The embodiment of the present application may select a suitable decoder for the separated video track and audio track, taking the video track as an example:

All decoders supported by the system can be stored in the preset configuration file XML, and the AVC encoding type corresponds to the AVC Decoder. It is assumed that the decoder supporting the AVC format includes a software decoder and a hardware decoder, and at this time, according to the resolution and the level. A preset rule such as an application scenario further determines a suitable decoder.

For example, if the resolution of the AVC video file is lower (below the preset threshold), then the software decoder supporting the AVC format can be determined, and if the resolution of the AVC video file is higher (above the preset threshold), then it can be determined A hardware decoder supporting AVC format;

In the specific implementation, the software decoder can be selected for the case where the CPU operation is required to be large, and the hardware decoder can be selected for the case where the CPU operation is required to be small. For example, if the current application scenario is to generate a small thumbnail video file for the video file (the amount of computation required is small), then the software decoder supporting the AVC format can be determined if the current application scenario is to play the original video file (the required amount of operation) Larger, then you can determine the hardware decoder that supports the AVC format.

OpenMAX performs preparatory work initialization, creates an OMXNodeInstance instance based on the incoming video file, and associates the decoder's components with the instance.

For software decoders, OpenMAX calls SW Codec in OpenMAX IL through OpenMAX Core in the guest operating system. SW Codec can call the SW Codec driver driver of Android kernel to implement specific software codec during codec implementation. Fuck Work

For the hardware codec, OpenMAX communicates with the vOpenMAX Back end in the host operating system through the virtual OpenMAX Front end of the guest operating system (ie vOpenMAX Front end), calling OpenMAX Core in the host operating system to call Android. HW Codec of the kernel, HW Codec can call the driver of the HW Codec of the Android kernel to implement specific hardware codec operations during the codec implementation.

Specifically, cross-system communication between the virtual OpenMAX hard codec interface (vOpenMAX Front end) in the guest operating system and the virtual OpenMAX server (vOpenMAX Back end) in the host operating system can be managed in the virtual machine monitor Hypervisor The control flow and the data flow are transmitted through the virtual machine KVM and the simulator Qemu.

Example VII.

The embodiment of the present application is described by taking a tablet computer as an example.

FIG. 9 is a schematic structural diagram of a tablet computer in Embodiment 7 of the present application. As shown in the figure, the tablet computer may include a host operating system (Host OS) and a guest operating system (Guest OS), where the client The guest OS can include a personal operating system (POS) and an enterprise operating system (EOS).

The host operating system (Host OS) can call the OpenMAX component in the host operating system after the multimedia application in the host operating system receives the multimedia processing request, and the codec component calls the hardware codec interface during the implementation process, and uses the H/ W Codec encodes and decodes multimedia files.

Both the personal operating system (POS) and the enterprise operating system (EOS) can encode and decode the multimedia file for the software codec by calling the software codec in the respective system after the multimedia application of the respective system receives the processing request. , that is, using the CPU for encoding and decoding; The hardware codec can communicate with the vOpenMAX Back end of the host operating system through the vOpenMAX Back end of the respective system, thereby calling the OpenMAX component in the host operating system, and the OpenMAX component in the host operating system calls the hardware during the implementation process. The codec interface realizes the purpose of encoding and decoding multimedia files by using H/W Codec.

With the technical solution provided by the embodiment of the present application, the hardware codec of the host operating system can be used to provide hardware acceleration capability for the operating system regardless of which operating system (personal operating system or enterprise operating system) the user is in.

Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, system, or computer program product. Thus, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware. Moreover, the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

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.

While the preferred embodiment of the present application has been described, it will be apparent that those skilled in the art can make further changes and modifications to the embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and the modifications and

Claims

A multi-operating system multimedia codec method, comprising:

Receiving, in the guest operating system, a multimedia processing request sent by the adaptation layer and transmitting the multimedia processing request to a host operating system, where the multimedia processing request includes a multimedia file;

In the OpenMAX integration layer IL of the host operating system, the hardware codec in the host operating system is loaded and controlled to encode and decode the multimedia file.
The method according to claim 1, wherein before the receiving the multimedia processing request sent by the adaptation layer, the method further comprises:

And acquiring, at the adaptation layer of the guest operating system, a multimedia file sent by the multimedia application, and adapting the codec to the multimedia file.
The method of claim 1 wherein

Receiving the multimedia processing request sent by the adaptation layer and sending the multimedia processing request to the host operating system, specifically: in the OpenMAX integration layer IL of the guest operating system, as an interface for cross-system communication, receiving the adaptation layer to send Multimedia processing request and send the multimedia processing request to the OpenMAX integration layer IL of the host operating system;

Loading and controlling the hardware codec in the host operating system to encode and decode the multimedia file in the OpenMAX integration layer IL of the host operating system, specifically: in the OpenMAX integration layer IL of the host operating system, As a server of the guest operating system hardware codec, the hardware codec in the host operating system is loaded and controlled according to the multimedia processing request to encode and decode the multimedia file delivered by the guest operating system.
The method of claim 1, wherein the multimedia processing request is sent to a host operating system in a guest operating system, and the host operating system is loaded and controlled in an OpenMAX integration layer IL of the host operating system. The hardware codec in the codec encodes and decodes the multimedia file, specifically:

Sending a notification message to the host operating system in the guest operating system, in the OpenMAX integration layer IL of the host operating system, loading a corresponding hardware codec according to the notification message;

Sending a multimedia file to the host operating system in the guest operating system, and controlling the hardware codec to encode and decode the multimedia file in an OpenMAX integration layer IL of the host operating system.
The method according to claim 1, wherein after the hardware codec of the host operating system completes encoding and decoding of the multimedia file, the method further comprises:

Passing the coded data back to the guest operating system; or,

The codec processing status is displayed on the host operating system side.
A multi-operating system multimedia codec device, comprising: a host operating system, a guest operating system, and a vOpenMAX front end Front end located in the guest operating system and a vOpenMAX back end Back end located in the host operating system;

The vOpenMAX front end Front end is configured to receive, in the guest operating system, a multimedia processing request sent by the adaptation layer and send the multimedia processing request to the host operating system, where the multimedia processing request includes a multimedia file;

The vOpenMAX backend end end is configured to load and control a hardware codec in the host operating system to encode and decode the multimedia file in an OpenMAX integration layer IL of the host operating system.
The apparatus of claim 6 wherein said guest operating system further comprises:

And an adaptation module, configured to acquire, at an adaptation layer of the guest operating system, a multimedia file sent by the multimedia application, and encode and decode the multimedia file for the multimedia file before the receiving the multimedia processing request sent by the adaptation layer Device.
The device of claim 6 wherein:

The vOpenMAX Front end is specifically used in the OpenMAX integration layer IL of the guest operating system, as an interface for cross-system communication, receiving a multimedia processing request sent by the adaptation layer and transmitting the multimedia processing request to the OpenMAX integration of the host operating system. Layer IL;

The vOpenMAX Back end is specifically used in a OpenMAX integration layer IL of a host operating system, as a server of a guest operating system hardware codec, loading and controlling a hardware codec in the host operating system according to the multimedia processing request. Encoding and decoding the multimedia file delivered by the guest operating system.
The device according to claim 6, wherein the vOpenMAX Front end is specifically configured to send a notification message to the host operating system in the guest operating system, where the vOpenMAX Back end is specifically used in the The OpenMAX integration layer IL of the host operating system loads a corresponding hardware codec according to the notification message; the vOpenMAX Frontend is further configured to send the multimedia file to the host operating system in the guest operating system, The vOpenMAX Back end is further configured to control, in an OpenMAX integration layer IL of the host operating system, a hardware codec of the host operating system to encode and decode the multimedia file.
The device of claim 6 further comprising:

a data backhaul module, configured to send the coded data back to the guest operating system in an OpenMAX integration layer IL of the host operating system; or

And a display module, configured to display a codec processing state on the host operating system side.
An electronic device, comprising: a memory, one or more processors, and one or more modules, the one or more modules being stored in the memory and configured to Executed by the one or more processors, the one or more modules comprising instructions for performing the various steps in the method of any of claims 1 to 5.
A computer program product, wherein the computer program product encodes instructions for performing a process, the process comprising the method of any one of claims 1 to 5. Methods.