Methods and apparatus for acquiring media data, storage media and electronic devices

Abstract

This application discloses a method, apparatus, storage medium, and electronic device for acquiring media data. The method includes: acquiring target object information of a target media object through a first application of a target device, wherein the target object information is used to acquire the target media data from a shared media memory area where the target media data of the target media object is stored; sending the target object information to a second application of the target device through the first application; and acquiring the target media data from the shared media memory area using the target object information through the second application. This application solves the problem of high resource consumption caused by the large amount of data to be transmitted in related technologies for acquiring media data.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a method and apparatus for acquiring media data, a storage medium, and an electronic device. Background Technology

[0002] In related technologies, when an application needs to use media data from another application, it typically uses a data copying method to copy the media data from the other application to its own application. For example, when application X needs to use media data from application Y, it can copy the data from application Y to application X.

[0003] However, copying media data between different applications requires transferring a large amount of data, consuming significant copying resources. Therefore, current media data acquisition methods suffer from high resource consumption due to the large volume of data to be transferred. Summary of the Invention

[0004] This application provides a method and apparatus for acquiring media data, a storage medium, and an electronic device to at least solve the problem of high resource consumption caused by the large amount of data to be transmitted in related technologies for acquiring media data.

[0005] According to one aspect of the embodiments of this application, a method for acquiring media data is provided, comprising: acquiring target object information of a target media object through a first application of a target device, wherein the target object information is used to acquire the target media data from a shared media memory area where the target media data of the target media object is stored; sending the target object information to a second application of the target device through the first application; and acquiring the target media data from the shared media memory area using the target object information through the second application.

[0006] In one exemplary embodiment, before obtaining the target object information of the target media object through a first application of the target device, the method further includes: sending a target encoding request to a target component of the target device through the first application, wherein the target encoding request is used to request encoding the media data to be shared in the shared media memory area into media data of a target format; and receiving the target object information returned by the target component in response to the target encoding request, wherein the target object information is object information obtained by the target component after encoding the media data to be shared into the target media data according to the target format.

[0007] In an exemplary embodiment, before sending the target object information to a second application of the target device through the first application, the method further includes: adding a first transmission record in a reserved area of ​​the target object information, wherein the first transmission record is used to record the target object information being transmitted from the first application to the second application.

[0008] In one exemplary embodiment, sending the target object information to a second application of the target device through the first application includes: transmitting the target object information to the second application through the first application, wherein after transmitting the target object information, the first application does not allow the use of the target object information, while the second application allows the use of the target object information.

[0009] In an exemplary embodiment, after obtaining the target object information of the target media object through the first application of the target device, the method further includes: generating corresponding reference information for each application in a group of applications based on the target object information, wherein the reference information corresponding to each application is used to allow the corresponding application to read the target media data; and sending the reference information corresponding to each application to the corresponding application respectively, so that each application uses the target media data according to the corresponding usage sequence.

[0010] In an exemplary embodiment, after the first application sends the target object information to the second application of the target device, the method further includes: in response to a memory allocation request from the second application, performing a pre-allocation operation for media data to be added, wherein the media data to be added is media data at a target location to be added to the target media data, and the memory allocation request is used to request pre-allocate memory space for the media data to be added; if the pre-allocation operation is successful, adding the media data to be added to the pre-allocated memory space.

[0011] In an exemplary embodiment, after performing the pre-allocation operation for the media data to be added, the method further includes: if the pre-allocation operation fails, allocating heap space from the heap memory of the target device for the target media data to obtain a target heap space, wherein the size of the target heap space is greater than the sum of the sizes of the target media data and the media data to be added; migrating the target media data to the target heap space, and adding the media data to be added to the target location of the target media data.

[0012] According to another aspect of the embodiments of this application, a media data acquisition apparatus is also provided, comprising: a first acquisition unit, configured to acquire target object information of a target media object through a first application of a target device, wherein the target object information is used to acquire the target media data from a shared media memory area where the target media data of the target media object is stored; a first sending unit, configured to send the target object information to a second application of the target device through the first application; and a second acquisition unit, configured to acquire the target media data from the shared media memory area using the target object information through the second application.

[0013] In one exemplary embodiment, the apparatus further includes: a second sending unit, configured to send a target encoding request to a target component of the target device via the first application before obtaining target object information of the target media object through the first application of the target device, wherein the target encoding request is used to request encoding the media data to be shared in the shared media memory area into media data of a target format; and a receiving unit, configured to receive the target object information returned by the target component in response to the target encoding request, wherein the target object information is object information obtained by the target component after encoding the media data to be shared into the target media data according to the target format.

[0014] In one exemplary embodiment, the apparatus further includes: a first adding unit, configured to add a first transmission record in a reserved area of ​​the target object information before the target object information is sent to a second application of the target device through the first application, wherein the first transmission record is used to record the target object information being transmitted from the first application to the second application.

[0015] In an exemplary embodiment, the first sending unit includes a transmission module, configured to transmit the target object information to a second application via the first application, wherein after transmitting the target object information, the first application does not allow the use of the target object information, while the second application allows the use of the target object information.

[0016] In one exemplary embodiment, the apparatus further includes: a generation unit, configured to, after obtaining target object information of a target media object through a first application of a target device, generate corresponding reference information for each application in a group of applications based on the target object information, wherein the reference information corresponding to each application is used to allow the corresponding application to read the target media data; and a third sending unit, configured to send the reference information corresponding to each application to the corresponding application respectively, so that each application uses the target media data according to the corresponding usage sequence.

[0017] In one exemplary embodiment, the apparatus further includes: an execution unit, configured to, after the target object information is sent to a second application of the target device via the first application, perform a pre-allocation operation for media data to be added in response to a memory allocation request from the second application, wherein the media data to be added is media data at a target location to be added to the target media data, and the memory allocation request is used to request pre-allocation of memory space for the media data to be added; and a second adding unit, configured to add the media data to be added to the pre-allocated memory space if the pre-allocation operation is successfully executed.

[0018] In one exemplary embodiment, the apparatus further includes: an allocation unit, configured to allocate heap space from the heap memory of the target device for the target media data after the pre-allocation operation for the media data to be added has failed, to obtain a target heap space, wherein the size of the target heap space is greater than the sum of the sizes of the target media data and the media data to be added; and a migration unit, configured to migrate the target media data to the target heap space and add the media data to be added to the target location of the target media data.

[0019] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer-readable storage medium, and the computer program is configured to execute the above-described method for acquiring media data when running.

[0020] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the above-described method for acquiring media data through the computer program.

[0021] In this embodiment, media data is shared between different applications based on object information instead of directly copying media data. The first application on the target device obtains target object information of the target media object, which is used to retrieve target media data from a shared media memory area where the target media data of the target media object is stored. The first application sends the target object information to a second application on the target device. The second application then uses the target object information to retrieve the target media data from the shared media memory area. Because media data is not directly copied during inter-application media data transmission, but rather object information corresponding to the media data is transferred between applications, and then media data is retrieved from the shared media memory area based on the transferred object information, the amount of information to be transferred is smaller than that of the media information. Furthermore, reading media data from the shared media memory area is more efficient than copying data. This reduces resource waste during media data transfer between applications, achieving the technical effect of reducing resource consumption and improving data transmission efficiency. This solves the problem of high resource consumption caused by large amounts of data to be transferred in related technologies. Attached Figure Description

[0022] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0023] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This is a schematic diagram of the hardware environment for an optional media data acquisition method according to an embodiment of this application;

[0025] Figure 2 This is a flowchart illustrating an optional method for acquiring media data according to an embodiment of this application;

[0026] Figure 3 This is a flowchart of an optional method for acquiring media data according to an embodiment of this application;

[0027] Figure 4 This is a structural block diagram of an optional media data acquisition device according to an embodiment of this application;

[0028] Figure 5 This is a structural block diagram of an optional electronic device according to an embodiment of this application. Detailed Implementation

[0029] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0030] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0031] According to one aspect of the embodiments of this application, a method for acquiring media data is provided. Optionally, in this embodiment, the above-described method for acquiring media data can be applied to, for example... Figure 1 The hardware environment shown consists of terminal device 102 and server 104. For example... Figure 1 As shown, server 104 is connected to terminal device 102 via a network and can be used to provide services (such as application services) to the terminal or clients installed on the terminal. A database can be set up on the server or independently of the server to provide data storage services for server 104.

[0032] The aforementioned network may include, but is not limited to, at least one of the following: wired network, wireless network. The aforementioned wired network may include, but is not limited to, at least one of the following: wide area network, metropolitan area network, local area network. The aforementioned wireless network may include, but is not limited to, at least one of the following: Wi-Fi (Wireless Fidelity), Bluetooth. The terminal device 102 may not be limited to PC (Personal Computer), mobile phone, tablet computer, etc.

[0033] The media data acquisition method of this application embodiment can be executed by server 104, terminal device 102, or jointly by server 104 and terminal device 102. The media data acquisition method of this application embodiment executed by terminal device 102 can also be executed by a client installed on it.

[0034] Taking the method for acquiring media data in this embodiment executed by terminal device 102 as an example, Figure 2 This is a flowchart illustrating an optional media data acquisition method according to an embodiment of this application, such as... Figure 2 As shown, the process of this method may include the following steps:

[0035] Step S202: Obtain target object information of the target media object through the first application of the target device, wherein the target object information is used to obtain target media data from the shared media memory area where the target media data of the target media object is stored.

[0036] The media data acquisition method in this embodiment can be applied to scenarios where media data is transmitted between different applications on a target device (i.e., terminal device 102). The target device can be a smartphone, a smart tablet, or a smart home device such as a smart TV. The media data can be image data, video data, or other media data that can be transmitted between different applications on the same device. This embodiment does not limit the type of smart device or the type of media data.

[0037] In related technologies, during the process of transferring media data between different applications on the same device, for example, when a process of application X compresses a YUV (a color encoding method, where "Y" represents luminance or Luma, i.e., grayscale value, and "U" and "V" represent chrominance or Chroma) image into a JPEG (Joint Photographic Experts Group) image, and then transfers the compressed media data to other applications (e.g., App[B,C] or Srv[A,B,C]), the easiest data copying method can be used. However, when transferring a large number of JPEGs, the data copying method will consume a lot of copying resources.

[0038] In this embodiment, a first application may run on the target device. This first application can be any type of application, such as an application that allows media data transfer between different applications. When it is necessary to transfer media data from the first application to other applications, or when it is determined, based on preset configuration information, that the media data in the first application needs to be shared, or based on other triggering events, the target device can obtain target object information of the target media object through the first application. The target object information is used to obtain the target media data from the shared media memory area where the target media data of the target media object is stored.

[0039] Optionally, obtaining the target object information of the target media object through the first application can be performed in response to an acquisition request sent by another application. For example, after receiving an acquisition request sent by another application other than the first application on the target device, the target device responds to the received acquisition request and obtains the target object information of the target media object through the first application.

[0040] The target media object may include target media data and target object information. The target media data is obtained by encoding (e.g., compressing) the media data to be shared by the first application, or in other words, media data generated after the media data to be shared is compressed (e.g., JPEG data). The target object information can be used to retrieve the target media data from the shared media memory area where the target media data is stored. It may include descriptive information about the target media data, or structured data that the target media object can be shared by multiple applications, such as a shared lock or a counter. This embodiment does not limit this, and the amount of target media data is greater than the amount of target object information.

[0041] Optionally, if the target object information is stored in the first application, the process of obtaining the target object information of the target media object through the first application of the target device can be: directly obtaining the target object information stored in the first application. If the target object information is not stored in the first application, the process of obtaining the target object information of the target media object through the first application of the target device can be: encoding the shared media data by calling a specific component, thereby obtaining the encoded target object information from the specific component. This embodiment does not limit this process.

[0042] It should be noted that the aforementioned shared media memory area is a region in the target device's memory used to store media data shared between different applications. It can be a virtual region in the target device's memory, rather than a fixed region, and the size of the shared media memory area can be adjusted as needed. Any memory region in the target device's memory that allows data sharing between two applications can be called a shared media memory area; this embodiment does not impose any limitation on this.

[0043] Step S204: The target object information is sent to the second application of the target device through the first application.

[0044] In this embodiment, after obtaining the target object information through the first application, the target device can send the target object information to other applications, such as the second application mentioned above. Optionally, the first application may obtain the target object information based on a media data acquisition request from the second application mentioned above.

[0045] The first application and the second application can be two different applications installed on the target device, or two different sub-applications installed on the same application on the target device, or two different mini-program applications installed on the application on the target device. This embodiment does not limit this.

[0046] During the process of sending target object information to a second application on the target device via a first application, application information of the second application can be added to the target object information. This application information can be used to send the target object information from the first application to the specified second application. Optionally, if the target object information is mistakenly sent to an application other than the second application, the other application will be unable to process the target object information.

[0047] Step S206: Obtain target media data from the shared media memory area using the target object information through the second application.

[0048] In this embodiment, after the target object information is sent to the second application via the first application, the target device can use the target object information to obtain target media data. Optionally, the target media data can be obtained from the shared media memory area using the target object information via the second application.

[0049] Through the above steps, the target object information of the target media object is obtained through the first application of the target device. The target object information is used to obtain the target media data from the shared media memory area where the target media data of the target media object is stored. The target object information is sent to the second application of the target device through the first application. The target media data is obtained from the shared media memory area through the second application using the target object information. This solves the problem of high resource consumption caused by the large amount of data to be transmitted in the media data acquisition method of related technologies, reduces resource consumption, and improves data transmission efficiency.

[0050] In one exemplary embodiment, before obtaining the target object information of the target media object through a first application of the target device, the above method further includes:

[0051] S11, a target encoding request is sent to the target component of the target device through the first application, wherein the target encoding request is used to request the media data to be shared in the shared media memory area to be encoded into media data in the target format;

[0052] S12, receive the target object information returned by the target component in response to the target encoding request, wherein the target object information is the object information obtained by the target component after encoding the media data to be shared into target media data according to the target format.

[0053] In this embodiment, the target data object can be obtained by encoding the media data to be shared by a target component. The target component can be a component in the target device used to process media data, for example, it can be called ServInc. For example, if the format of the media data to be shared is inconsistent with the media data shared between different applications, or if other data encoding conditions are met, a target encoding request can be sent to the target component through the first application. The target encoding request is used to request that the media data to be shared in the shared media memory area be encoded into media data in the target format.

[0054] The target component mentioned above can be a component of the target device independent of any application, or it can be a component installed within an application on the target device. The target component can encode the media data to be shared in the shared media memory area into media data in the target format. For example, it can encode YUV format media data to be shared into JPEG format target media data.

[0055] Upon receiving a target encoding request from the first application, the target component can respond to the received target encoding request by encoding (i.e., compressing) the media data to be shared in the shared media memory area into media data in the target format. Optionally, after encoding the media data to be shared into media data in the target format, the target component can return target object information to the first application. The target object information is the object information obtained by the target component after encoding the media data to be shared into target media data in the target format, and the first application can obtain the target object information.

[0056] For example, such as Figure 3 As shown, application X (the first application mentioned above) sends an image encoding (compression) request to SrvIEnc (the target component mentioned above) (i.e., step S1.0), and the source data for image compression (i.e., YUV object data) is stored in the shared media memory area (i.e., step S1.1). SrvIEnc can respond to the received image encoding request and encode the source data (i.e., YUV object data) stored in the shared media memory area into target media data (i.e., JPEG object data). After completing image compression, SrvIEnc can generate an image object (ImgObj, the target media object mentioned above), which includes "image data (ImgData, the target media data mentioned above)" and "image information (ImgInfo, the target object information mentioned above)" (i.e., step S1.2).

[0057] In this embodiment, the media data to be shared is encoded into media data of a specific format in response to the application's media data encoding request by a predetermined component on the device, and the obtained object information is returned to the application. This can improve the convenience of obtaining object information and improve the efficiency of resource utilization.

[0058] In one exemplary embodiment, before sending the target object information to the second application of the target device via the first application, the method further includes:

[0059] S21, add a first transmission record in the reserved area of ​​the target object information, wherein the first transmission record is used to record the target object information being transmitted from the first application to the second application.

[0060] During the transmission of object information, the transmission record of media data can be used to document the process of transferring object information (or media objects, media data) between different applications. The transmission record can track which applications the object information flows between, thereby enabling the target device or other devices to diagnose anomalies (e.g., transmission errors) and to forcibly reclaim the object due to prolonged non-return.

[0061] Taking a transmission error as an example, when object information is being transferred from application X to application Y, it is mistakenly transferred to application C during the transfer process. Based on the transmission record, it can be determined that the application to which the information was intended is application Y, and the object information can be determined to have been mistakenly transferred through the transmission record.

[0062] In this embodiment, a transmission record can be added to the reserved area of ​​the target object information to indicate the transmission route of the target object information. Optionally, a first transmission record can be added to the reserved area of ​​the target object information. The first transmission record is used to record the transmission of the target object information from the first application to the second application.

[0063] For example, such as Figure 3 As shown, SrvIEnc can record the information of who will transfer ImgObj to whom in the reserved area after ImgInfo (i.e., steps S1.3.0 to S1.3.1) before passing ImgObj to application X. The "who" here can be defined during system design or can be information such as the runtime process ID (identifier) ​​during system operation, as long as it is identifiable within the diagnostic scope.

[0064] Optionally, when multiple processes write information simultaneously, a method can be adopted to first write the identification information, then read the identification information, and then match the identification information. The read identification information can be used to determine the process to be passed to (or the application corresponding to the process), so as to ensure that information processing errors occur when concurrent information writing conflicts occur, while avoiding the problems that exist in using shared locks globally.

[0065] In this embodiment, by adding a transmission record in the reserved area of ​​the object information during the transmission of object information to record the transmission direction of the object information, the accuracy of anomaly diagnosis and the security of data transmission can be improved.

[0066] In one exemplary embodiment, sending target object information to a second application of a target device via a first application includes:

[0067] S31, the target object information is transmitted to the second application through the first application, wherein after the target object information is transmitted, the first application is not allowed to use the target object information, while the second application is allowed to use the target object information.

[0068] In this embodiment, after obtaining the target object information, the first application can use the target object information to obtain target media data, or it can send the target object information to other applications. Optionally, the first application can transmit the target object information to a second application.

[0069] For example, after application X obtains the result of image compression (i.e., ImgInfo), this result can be passed to other applications, and application X can also obtain ImgData through this information, as well as release the shared media memory it occupies after use.

[0070] It should be noted that the transfer of target object information from the first application to the second application can be either a transfer of the right to use the target media data or a transfer of ownership of the target media data. Transferring the right to use the target media data to the second application can be done within the second application's time frame, allowing the second application to use the target media data. Transferring ownership of the target media data to the second application can be a transfer of ownership of the target media data to the second application, meaning the second application becomes the owner of the target media data. Optionally, during the transfer process, there can be only one user of the target object information, either the first application or the second application; similarly, there can also be only one owner of the target object information, either the first application or the second application.

[0071] For example, after application X directly passes ImgInfo to application Y (i.e., steps S2.0 to S2.1), the right to use ImgInfo will also transfer from application X to application Y. After application X passes out ImgInfo, it will not and cannot use ImgInfo again. Throughout the entire process, ImgInfo has only one user, either application X or application Y.

[0072] In this embodiment, after object information is transferred between applications, the applications that were transferred before cannot use the transferred object information, which can avoid timing errors caused by multiple applications using object information to obtain corresponding media data at the same time.

[0073] In one exemplary embodiment, after obtaining the target object information of the target media object through a first application of the target device, the above method further includes:

[0074] S41, Generate corresponding reference information for each application in a group of applications based on the target object information, wherein the reference information corresponding to each application is used to allow the corresponding application to read the target media data;

[0075] S42, the reference information corresponding to each application is sent to the corresponding application so that each application uses the target media data according to the corresponding usage sequence.

[0076] In this embodiment, when it is necessary for each application in a group of applications to obtain the right to use the target media data, corresponding reference information can be generated for each application in the group of applications based on the target object information. The reference information corresponding to each application is used to allow the corresponding application to read the target media data. Here, each application in the group of applications is an independent application and they do not communicate with each other.

[0077] Optionally, generating corresponding reference information for each application in a group of applications based on the target object information can be performed by the application that owns the target object information. For example, when a group of applications includes applications Z1 and Z2, and application Y owns the target object information, application Y can generate corresponding reference information for applications Z1 and Z2 respectively based on the target object information, and distribute the generated reference information to applications Z1 and Z2 respectively.

[0078] The process described above, which generates corresponding reference information for each application in a group of applications based on the target object information, can be achieved by calling a reference information generation method to add the same number of reference information as the number of applications in the group of applications to the target object information, or by adding reference information corresponding to each application separately to the target object information, thereby generating multiple reference information.

[0079] For example, such as Figure 3 As shown, application Y can call the AddNewRef method (i.e., step S3.0) to add a newly used reference count to ImgInfo and pass the new reference count's ImgInfo to application Z2 (i.e., steps S3.1.0 to S3.1.1), and then pass the old ImgInfo to application Z1 (i.e., steps S3.2.0 to S3.2.1). This ImgInfo originates from application X. From application Y's perspective, these two ImgInfos are completely identical at the usage level, differing only in logic as old and new. Here, passing ImgInfo to application Z2 can mean passing the right to use ImgInfo to application Z2, while passing ImgInfo to application Z1 can mean passing the ownership of ImgInfo to application Z1.

[0080] In this embodiment, after generating reference information corresponding to each application, the reference information corresponding to each application can be sent to the corresponding application so that each application uses the target media data according to the corresponding usage sequence. The reference addition operation performed for obtaining and distributing media data is carried out only in the information area of ​​the media object, without the need for additional communication with the media object generator (e.g., SrvIEnc), and communication only occurs during the final release.

[0081] For example, applications Z1 and Z2 can obtain ImgData based on their respective ImgInfo to fulfill the business requirement of reading ImgData. During the reading process, application Z2 can read ImgData with read-only permissions by default (i.e., step S4.0). After use, application Z2 can call the FreeImageObject method to release it to SrvIEnc, which will then reclaim the resources occupied by the Image Object (i.e., steps S4.1.0 to 4.1.1). During the reading process, application Z1 can read ImgData with read-write permissions by default (i.e., step S50). After use, application Z1 can also call the FreeImageObject method to release it to SrvIEnc, which will then reclaim the resources occupied by the Image Object (i.e., step S5.2).

[0082] It should be noted that when multiple applications simultaneously obtain target media data through their corresponding reference information, timing errors may occur. Therefore, when sending the reference information corresponding to each application to the respective application so that each application uses the target media data according to its corresponding usage timing, the timing information corresponding to each application can be sent synchronously to each application, so that each application can use the target media data sequentially according to its corresponding timing.

[0083] To ensure efficient data transfer between applications, the overhead of this diagnostic needs to be sufficiently low. Optionally, when an application uses the target media data for more than a threshold time, the reference messages allocated to that application can be forcibly reclaimed. This enables the ability to capture and diagnose "leakage" and "freezing" during media object transfer, as well as handle abnormal situations such as a sudden restart of a process, providing potential opportunities for exception handling.

[0084] This embodiment demonstrates how media data can be used in a set of applications according to the corresponding usage sequence by referencing the target object information. This can improve the accuracy of media data usage across different applications.

[0085] In one exemplary embodiment, after sending the target object information to a second application of the target device via a first application, the method further includes:

[0086] S51, in response to the memory allocation request of the second application, a pre-allocation operation is performed for the media data to be added, wherein the media data to be added is the media data at the target position to be added to the target media data, and the memory allocation request is used to request pre-allocate memory space for the media data to be added;

[0087] S52, if the pre-allocation operation is successful, adds the media data to be added to the pre-allocated memory space.

[0088] In some cases, it is necessary to meet the needs of users (here, the user is the owner of the object information) to add information to the beginning or end of media data. To avoid incurring additional copying overhead during information addition, a certain amount of memory can be pre-allocated at the target location in the target media data. Optionally, to add the media data to be added to the target media data, the second application can send a memory allocation request to the target device or a target component of the target device to request pre-allocation of memory space for the media data to be added. Here, the media data to be added is the media data at the target location to be added to the target media data. The aforementioned target location can be the beginning or end of the target media data.

[0089] For example, such as Figure 3 As shown, when application Z1 obtains ImgData through ImgInfo, in order to add additional information to the header and tail of ImgData, address space can be pre-allocated to store this additional information (i.e., step S5.1). This additional information can be used for business scenarios such as data header synchronization and data tail verification or signing.

[0090] In response to a memory allocation request from the second application, the target device can perform a pre-allocation operation for the media data to be added; that is, it pre-allocates memory space to store the media data to be added. Since the shared memory region has limited memory space, the pre-allocation operation will succeed if the pre-allocated memory space for the media data to be added is less than or equal to the remaining space of the target media data at the target location. However, the pre-allocation operation will fail if the pre-allocated memory space for the media data to be added is greater than the remaining space of the target media data at the target location.

[0091] For example, such as Figure 3 As shown, there are maximum threshold limits for SizN at the beginning and end of ImgData, set using MaxHSiz and MaxTSiz respectively. Application Z1, based on ImgInfo or ImgData, requests header space for Siz1 and tail space for Siz2. Requesting space for Siz1 greater than MaxHSiz or requesting space for Siz2 greater than MaxTSiz will result in request failure.

[0092] If the pre-allocation operation is successful, the media data to be added can be added to the pre-allocated memory space. Optionally, before adding the media data to be added to the pre-allocated memory space, the pre-allocated memory space can be set to read-write mode so that the media data to be added can be successfully written to the pre-allocated memory space.

[0093] It should be noted that if the media data to be added is added to the pre-allocated memory space and there is a misalignment of the tail data, for example, if the tail end address is 1, but the newly written data needs to be aligned to 8 bytes, a misalignment will occur. In this case, the tail data can be copied to the newly mapped physical memory in advance.

[0094] In this embodiment, based on the application's memory allocation request, a pre-allocation operation is performed on the media data to be added. Memory space is pre-allocated at specific locations of the media data, which can avoid additional copying overhead during the information addition process and improve the rationality of resource utilization.

[0095] In one exemplary embodiment, after performing a pre-allocation operation for the media data to be added, the method further includes:

[0096] S61, if the pre-allocation operation fails, allocate heap space for the target media data from the heap memory of the target device to obtain the target heap space, wherein the size of the target heap space is greater than the sum of the size of the target media data and the media data to be added;

[0097] S62, migrate the target media data to the target heap space, and add the media data to be added to the target location of the target media data.

[0098] In this embodiment, if the pre-allocation operation fails, the target device can perform the pre-allocation operation again or try again after a certain delay. Alternatively, it can allocate heap space for the target media data from the target device's heap memory to obtain a target heap space. The size of the target heap space is greater than the sum of the sizes of the target media data and the media data to be added. For example, memory can be allocated directly from the heap memory, and then ImgData can be migrated to the newly allocated heap space. After obtaining the target heap space, the target media data can be migrated to the target heap space, and the media data to be added can be added to the target location of the target media data.

[0099] The aforementioned heap space and shared media memory area can both be located within the target device, and there is no overlap between them; that is, there is no memory region that simultaneously belongs to both the target heap space and the shared media memory area. The heap space and the shared media memory area can be adjacent memory regions or non-adjacent memory regions. This embodiment does not impose any limitations on the heap memory.

[0100] Optionally, before allocating heap space for target media data from the heap memory of the target device, the target device may first determine the heap memory occupancy. If the free heap memory is less than the sum of the data sizes of the target media data and the media data to be added, heap space allocation may not be performed. If the free heap memory is greater than the sum of the data sizes of the target media data and the media data to be added, then heap space allocation may be performed.

[0101] In this embodiment, when the pre-allocation operation fails, the media data is migrated to the heap space within the target device, which can improve the success rate of adding additional information to the media data.

[0102] The method for acquiring media data in this application embodiment will be explained below with reference to optional examples. In this optional example, the first application is application X, the second application is application Y, and it may also include application Z1. The target media data is image data, the target object information is image information, the target media object is an image object, the target component is SrvIEnc, and a group of applications includes application Z2.

[0103] This optional example provides a method for sharing digital media objects. The media object's creator and user share media memory, eliminating the need to copy the media object from the creator to the user, thus reducing the overhead caused by copying. Here, ownership of the media object belongs to the creator, while the right to use the media object is given to the user. The user can choose to use and transmit only the information description portion of the media object. This information can flow between multiple processes, and the corresponding media data can be obtained at any time based on this information. Based on the above information flow method, the overhead required for information transmission between applications can be significantly reduced.

[0104] like Figure 3 As shown, the process of acquiring media data in this optional example may include the following steps:

[0105] Step S1.0: Application X sends an image encoding (compression) request to SrvIEnc. When the parameter InfoOnly in the image encoding request is YES, it means that application X only cares about the information part in the image result, namely ImgInfo.

[0106] In step S1.1, the source data for image compression (i.e., YUV object data) is stored in the shared media memory area.

[0107] In step S1.2, SrvIEnc completes image compression and generates an image object (ImgObj). The image object includes image data (ImgData) and image information (ImgInfo). ImgData is the data generated after the image is compressed, and ImgInfo is the information of the image object. It may include a description of ImgData, and may also include structured data of ImgObj that can be shared by multiple applications, such as shared locks, counters, etc.

[0108] In step S1.3.0, before passing ImgObj to application X, SrvIEnc records the information of who will be transferred from whom in the reserved area after ImgInfo in the form of a "footprint".

[0109] In step S1.3.1, application X obtains the image compression result (i.e., ImgInfo). For application X, this information can be passed to other apps, and it can also obtain ImgData through this information, as well as release the shared media memory it occupies after use.

[0110] In step S2.0, when transferring ownership of the media object to application Y, as in step S1.3.0, it can be recorded as a "footprint" in the reserved area following ImgInfo.

[0111] In step S2.1, application X directly passes ImgInfo to application Y. At this point, the right to use ImgInfo has been transferred from application X to application Y. After application X passes out ImgInfo, it will not and cannot use ImgInfo again. Throughout the entire process, ImgInfo has only one user, either application X or application Y.

[0112] Application Y will distribute ImgInfo to applications Z1 and Z2. Applications Z1 and Z2 are two independent applications that do not communicate with each other. Each application obtains ImgData based on ImgInfo, reads ImgData, and releases it after use.

[0113] Step S3.0: Application Y calls the AddNewRef method to add the newly used reference count in ImgInfo;

[0114] You can add references to the information of a media object to distribute it to multiple users. Each user can independently obtain the media data and release the right to use the media object according to their own independent time sequence.

[0115] In step S3.1.0, when passing the new reference number's ImgInfo to application Z2, as in step S1.3.0, it can be recorded as a "footprint" in the reserved area following ImgInfo.

[0116] In step S3.1.1, application Y passes the ImgInfo of the new reference number to application Z2.

[0117] In step S3.2.0, when passing the old ImgInfo to application Z1, as in step S1.3.0, it can be recorded as a "footprint" in the reserved area following ImgInfo.

[0118] In step S3.2.1, application Y passes the old ImgInfo to application Z1. This ImgInfo originates from application X. From the perspective of application Y, the two ImgInfos are completely identical at the usage level, with the only difference being old and new at the logical level.

[0119] In step S4.0, application Z2 obtains ImgData through ImgInfo to fulfill the business requirement of reading Image data. At this time, ImgData is accessed with read-only permission by default.

[0120] In step S4.1.0, when reading ImgData, as in step S1.3.0, it can be recorded as a "footprint" in the reserved area after ImgInfo.

[0121] Step S4.1.1: After use, call the FreeImageObject method to release it to SrvIEnc, which will then reclaim the resources occupied by the Image Object.

[0122] Step S5.0 is the same as step S4.0, using Z1 to implement the business requirement of reading Image data.

[0123] In step S5.1, the application Z1 attempts to add additional information to the header and footer of ImgData. The added information can be used for business scenarios such as data header synchronization and data footer verification or signing.

[0124] An application can request reserved header and footer space to add custom information to the beginning and end of media data without incurring additional copying overhead. Reference operations performed for reading media data or for distribution only occur within the media object's information area, requiring no additional communication with the media object's creator; communication only occurs during final release.

[0125] For application Z1, based on ImgInfo or ImgData, it can request the header space of Siz1 and the tail space of Siz2. When obtaining ImgData through ImgInfo, address space pre-allocation is performed. If pre-allocation is successful, the pre-allocated address space is set to read-write mode during this request operation. If the tail data is misaligned, the tail data can be copied to the newly mapped physical memory in advance. If pre-allocation fails, during this request operation, it can either delay for a certain period of time before trying to request again, or allocate memory directly from heap memory and then migrate ImgData to the newly allocated heap space. If allocated from heap memory, step S4.1 is completed simultaneously, releasing the usage rights of the shared object.

[0126] Step S5.2 is the same as step S4.1 (i.e., S4.1.0 and step S4.1.1), completing the use of ImgData and reclaiming the resources occupied by the Image Object.

[0127] This optional example demonstrates how replacing large image data with object information of smaller image objects during image data transfer between applications can reduce the overhead of copying image data and improve the rationality of resource utilization.

[0128] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0129] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM (Read-Only Memory) / RAM (Random Access Memory), magnetic disk, optical disk), and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0130] According to another aspect of the embodiments of this application, a media data acquisition apparatus for implementing the above-described media data acquisition method is also provided. Figure 4 This is a structural block diagram of an optional media data acquisition device according to an embodiment of this application, such as... Figure 4 As shown, the device may include:

[0131] The first acquisition unit 402 is used to acquire target object information of the target media object through the first application of the target device, wherein the target object information is used to acquire target media data from the shared media memory area where the target media data of the target media object is stored;

[0132] The first sending unit 404 is connected to the first acquiring unit 402 and is used to send target object information to the second application of the target device through the first application.

[0133] The second acquisition unit 406 is connected to the first sending unit 404 and is used to acquire target media data from the shared media memory area using target object information through the second application.

[0134] It should be noted that the first acquisition unit 402 in this embodiment can be used to execute the above step S202, the first sending unit 404 in this embodiment can be used to execute the above step S204, and the second acquisition unit 406 in this embodiment can be used to execute the above step S206.

[0135] Through the above modules, the target object information of the target media object is obtained through the first application of the target device. The target object information is used to obtain the target media data from the shared media memory area where the target media data of the target media object is stored. The first application sends the target object information to the second application of the target device. The second application uses the target object information to obtain the target media data from the shared media memory area. This solves the problem of high resource consumption caused by the large amount of data to be transmitted in the media data acquisition methods of related technologies, reduces resource consumption, and improves data transmission efficiency.

[0136] In one exemplary embodiment, the above-described apparatus further includes:

[0137] The second sending unit is used to send a target encoding request to the target component of the target device through the first application before obtaining the target object information of the target media object through the first application of the target device. The target encoding request is used to request that the media data to be shared in the shared media memory area be encoded into media data in the target format.

[0138] The receiving unit is used to receive target object information returned by the target component in response to the target encoding request. The target object information is the object information obtained by the target component after encoding the media data to be shared into target media data according to the target format.

[0139] In one exemplary embodiment, the above-described apparatus further includes:

[0140] The first adding unit is used to add a first transmission record in the reserved area of ​​the target object information before sending the target object information to the second application of the target device through the first application. The first transmission record is used to record the target object information being transmitted from the first application to the second application.

[0141] In one exemplary embodiment, the first transmitting unit includes:

[0142] The transmission module is used to transmit target object information to a second application through a first application. After the target object information is transmitted, the first application is not allowed to use the target object information, while the second application is allowed to use the target object information.

[0143] In one exemplary embodiment, the above-described apparatus further includes:

[0144] The generation unit is used to generate corresponding reference information for each application in a set of applications based on the target object information after obtaining the target object information of the target media object through the first application of the target device. The reference information corresponding to each application is used to allow the corresponding application to read the target media data.

[0145] The third sending unit is used to send the reference information corresponding to each application to the corresponding application, so that each application can use the target media data according to the corresponding usage sequence.

[0146] In one exemplary embodiment, the above-described apparatus further includes:

[0147] The execution unit is configured to, after sending the target object information to the second application of the target device through the first application, perform a pre-allocation operation for the media data to be added in response to the memory allocation request of the second application, wherein the media data to be added is the media data at the target position to be added to the target media data, and the memory allocation request is used to request the pre-allocation of memory space for the media data to be added;

[0148] The second addition unit is used to add the media data to be added to the pre-allocated memory space if the pre-allocation operation is successful.

[0149] In one exemplary embodiment, the above-described apparatus further includes:

[0150] The allocation unit is used to allocate heap space from the heap memory of the target device for the target media data after performing a pre-allocation operation for the media data to be added, in the event that the pre-allocation operation fails, to obtain the target heap space, wherein the size of the target heap space is greater than the sum of the sizes of the target media data and the media data to be added;

[0151] The migration unit is used to migrate the target media data to the target heap space and add the media data to be added to the target location of the target media data.

[0152] It should be noted that the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the content disclosed in the above embodiments. It should also be noted that the above modules, as part of a device, can operate in environments such as... Figure 1 The hardware environment shown can be implemented through software or hardware, and the hardware environment includes the network environment.

[0153] According to another aspect of the embodiments of this application, a storage medium is also provided. Optionally, in this embodiment, the storage medium can be used to execute program code for any of the media data acquisition methods described above in the embodiments of this application.

[0154] Optionally, in this embodiment, the storage medium may be located on at least one of the network devices in the network shown in the above embodiment.

[0155] Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps:

[0156] S1, obtain target object information of the target media object through the first application of the target device, wherein the target object information is used to obtain target media data from the shared media memory area where the target media data of the target media object is stored;

[0157] S2, the target object information is sent to the second application of the target device through the first application;

[0158] S3, using the target object information, retrieves target media data from the shared media memory area through the second application.

[0159] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments, and will not be repeated in this embodiment.

[0160] Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, ROMs, RAMs, portable hard drives, magnetic disks, or optical disks.

[0161] According to another aspect of the embodiments of this application, an electronic device for implementing the above-described method for acquiring media data is also provided. The electronic device may be a server, a terminal, or a combination thereof.

[0162] Figure 5 This is a structural block diagram of an optional electronic device according to an embodiment of this application, such as... Figure 5 As shown, it includes a processor 502, a communication interface 504, a memory 506, and a communication bus 508. The processor 502, communication interface 504, and memory 506 communicate with each other via the communication bus 508.

[0163] Memory 506 is used to store computer programs;

[0164] When processor 502 executes a computer program stored in memory 506, it performs the following steps:

[0165] S1, obtain target object information of the target media object through the first application of the target device, wherein the target object information is used to obtain target media data from the shared media memory area where the target media data of the target media object is stored;

[0166] S2, the target object information is sent to the second application of the target device through the first application;

[0167] S3, using the target object information, retrieves target media data from the shared media memory area through the second application.

[0168] Optionally, in this embodiment, the communication bus can be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. This communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 5 The symbol is represented by a single thick line, but this does not indicate that there is only one bus or one type of bus. The communication interface is used for communication between the aforementioned electronic device and other devices.

[0169] The memory may include RAM, or non-volatile memory, such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0170] As an example, the memory 506 described above may include, but is not limited to, the first acquisition unit 402, the first transmission unit 404, and the second acquisition unit 406 of the media data acquisition device described above. Furthermore, it may include, but is not limited to, other module units of the media data acquisition device described above, which will not be elaborated upon in this example.

[0171] The processors mentioned above can be general-purpose processors, including but not limited to: CPU (Central Processing Unit), NP (Network Processor), etc.; they can also be DSP (Digital Signal Processor), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0172] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments, and will not be repeated here.

[0173] Those skilled in the art will understand that Figure 5 The structure shown is for illustrative purposes only. The device implementing the above method for acquiring media data can be a terminal device, such as a smartphone (e.g., an Android phone, an iOS phone), a tablet computer, a PDA, a mobile internet device (MID), a PAD, or other terminal devices. Figure 5 This does not limit the structure of the aforementioned electronic device. For example, the electronic device may also include components that are more... Figure 5 The more or fewer components shown (such as network interfaces, display devices, etc.), or having the same Figure 5 The different configurations shown.

[0174] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing the hardware related to the terminal device. The program can be stored in a computer-readable storage medium, which may include: flash drive, ROM, RAM, disk or optical disk, etc.

[0175] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0176] If the integrated units in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in the aforementioned computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause one or more computer devices (which may be personal computers, servers, or network devices, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.

[0177] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0178] In the several embodiments provided in this application, it should be understood that the disclosed client can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection between units or modules, and may be electrical or other forms.

[0179] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the solution provided in this embodiment, depending on actual needs.

[0180] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0181] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for acquiring media data, characterized in that, include: A target encoding request is sent to a target component of a target device via a first application, wherein the target encoding request is used to request that the media data to be shared in the shared media memory area be encoded into media data in a target format; The system receives target object information returned by the target component in response to the target encoding request, wherein the target object information is object information obtained by the target component after encoding the media data to be shared into target media data according to the target format; The target object information of the target media object is obtained through the first application of the target device, wherein the target object information is used to obtain the target media data from the shared media memory area where the target media data of the target media object is stored; The first application sends the target object information to the second application of the target device; The second application uses the target object information to obtain the target media data from the shared media memory area.

2. The method according to claim 1, characterized in that, Before sending the target object information to the second application of the target device via the first application, the method further includes: A first transmission record is added to the reserved area of ​​the target object information, wherein the first transmission record is used to record the target object information being transmitted from the first application to the second application.

3. The method according to claim 1, characterized in that, The second application that sends the target object information to the target device through the first application includes: The first application transmits the target object information to the second application, wherein after transmitting the target object information, the first application does not allow the use of the target object information, while the second application allows the use of the target object information.

4. The method according to claim 1, characterized in that, After obtaining the target object information of the target media object through the first application of the target device, the method further includes: Based on the target object information, corresponding reference information is generated for each application in a group of applications, wherein the reference information corresponding to each application is used to allow the corresponding application to read the target media data; Reference information corresponding to each application is sent to the respective application so that each application uses the target media data according to the corresponding usage sequence.

5. The method according to any one of claims 1 to 4, characterized in that, After the first application sends the target object information to the second application of the target device, the method further includes: In response to the memory allocation request of the second application, a pre-allocation operation is performed for the media data to be added, wherein the media data to be added is media data at a target position to be added to the target media data, and the memory allocation request is used to request pre-allocate memory space for the media data to be added; If the pre-allocation operation is successful, the media data to be added is added to the pre-allocated memory space.

6. The method according to claim 5, characterized in that, After performing the pre-allocation operation for the media data to be added, the method further includes: If the pre-allocation operation fails, heap space is allocated from the heap memory of the target device for the target media data to obtain the target heap space, wherein the size of the target heap space is greater than the sum of the size of the target media data and the size of the media data to be added; The target media data is migrated to the target heap space, and the media data to be added is added to the target location of the target media data.

7. A media data acquisition device, characterized in that, include: The second sending unit is used to send a target encoding request to the target component of the target device through the first application before obtaining the target object information of the target media object through the first application of the target device. The target encoding request is used to request that the media data to be shared in the shared media memory area be encoded into media data in the target format. The receiving unit is configured to receive target object information returned by the target component in response to the target encoding request, wherein the target object information is object information obtained by the target component after encoding the media data to be shared into target media data according to the target format; The first acquisition unit is used to acquire target object information of the target media object through the first application of the target device, wherein the target object information is used to acquire target media data from the shared media memory area where the target media data of the target media object is stored; The first sending unit is used to send target object information to a second application of the target device through a first application; The second acquisition unit is used to acquire target media data from the shared media memory area using target object information through the second application.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program, when executed, performs the method of any one of claims 1 to 6.

9. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to execute the method of any one of claims 1 to 6 through the computer program.

Images