CN110020293B - Multimedia data display method, device and storage medium - Google Patents
Multimedia data display method, device and storage medium Download PDFInfo
- Publication number
- CN110020293B CN110020293B CN201710966292.8A CN201710966292A CN110020293B CN 110020293 B CN110020293 B CN 110020293B CN 201710966292 A CN201710966292 A CN 201710966292A CN 110020293 B CN110020293 B CN 110020293B
- Authority
- CN
- China
- Prior art keywords
- format
- link address
- application client
- page
- native
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
- G06F16/9577—Optimising the visualization of content, e.g. distillation of HTML documents
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention discloses a multimedia data display method, a multimedia data display device and a storage medium, and belongs to the technical field of networks. The method comprises the following steps: acquiring a first link address to be accessed; creating a display component matched with the format according to the format supported by the application client; sending an access request to a server, and returning a page which corresponds to the first link address and supports the format by the server; when the page is received, the page is analyzed according to the format to obtain the multimedia data in the page, and the multimedia data is displayed through the display component. The embodiment of the invention not only improves the display speed of the application client terminal supporting the native format, but also avoids the problem that the application client terminal not supporting the native format can not be displayed, enlarges the application range and improves the flexibility and the universality.
Description
Technical Field
The embodiment of the invention relates to the technical field of networks, in particular to a multimedia data display method, a multimedia data display device and a storage medium.
Background
With the rapid development of multimedia technology and the wide popularization of the internet, people pay more and more attention to the display efficiency of multimedia data. In order to improve the display efficiency, an Instant advertisements (Instant text) framework is proposed, which can rapidly display multimedia data through native components.
The operation flow of the Instant arms framework comprises the following steps: and developing an application client supporting the native format by using an Instant arms framework by a developer, and setting a page supporting the native format on a server. In the application process, an application client sends an access request to a server, the access request carries a link address of a page, when the server receives the access request, the server returns the page which corresponds to the link address and supports a native format to the application client, when the application client receives the page, the page is analyzed according to the native format to obtain multimedia data in the page, and the multimedia data in the page is displayed through a native component.
In the process of implementing the embodiment of the present invention, the inventor finds that the related art has at least the following defects:
the native format is a proprietary format of the application client and the server, and other application clients except the application client cannot support the native format and cannot analyze the native format, so that the multimedia data in the page cannot be displayed. Therefore, the above-described technology has a narrow application range and is limited.
Disclosure of Invention
The embodiment of the invention provides a multimedia data display method, a multimedia data display device and a storage medium, which can overcome the defects in the related art. The technical scheme is as follows:
in a first aspect, a multimedia data presentation method is provided, which is applied in an application client, and the method includes:
acquiring a first link address to be accessed;
according to a format supported by the application client, creating a display component matched with the format, wherein the format is a native format or a webpage format, and the display component is a native component matched with the native format or a webpage view component matched with the webpage format;
sending an access request to a server, wherein the access request carries the first link address, the server returns a page which corresponds to the first link address and supports the format, and the server is used for storing a native page supporting the native format and a webpage supporting the webpage format;
when the page is received, analyzing the page according to the format to obtain the multimedia data in the page, and displaying the multimedia data through the display component.
In a second aspect, a multimedia data presentation method is provided, which is applied in a server, and the method includes:
receiving an access request sent by an application client, wherein the access request carries a first link address to be accessed;
according to a format supported by the application client, acquiring a page which corresponds to the first link address and supports the format, wherein the format is a native format or a webpage format, and the server is used for storing a native page supporting the native format and a webpage supporting the webpage format;
and sending the page to the application client, wherein the application client is used for analyzing the page according to the format to obtain the multimedia data in the page and displaying the multimedia data through a created display component, and the display component is a native component matched with the native format or a webpage view component matched with the webpage format.
In a third aspect, a multimedia data presentation apparatus is provided, which is applied in an application client, and the apparatus includes:
the acquisition module is used for acquiring a first link address to be accessed;
the creating module is used for creating a display component matched with the format according to the format supported by the application client, wherein the format is a native format or a webpage format, and the display component is a native component matched with the native format or a webpage view component matched with the webpage format;
a sending module, configured to send an access request to a server, where the access request carries the first link address, and the server returns a page that corresponds to the first link address and supports the format, where the server is configured to store a native page that supports the native format and a web page that supports the web format;
and the display module is used for analyzing the page according to the format to obtain the multimedia data in the page when the page is received, and displaying the multimedia data through the display component.
In a fourth aspect, a multimedia data presentation apparatus is provided, which is applied in a server, and the apparatus includes:
the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving an access request sent by an application client, and the access request carries a first link address to be accessed;
the acquisition module is used for acquiring a page which corresponds to the first link address and supports the format according to the format supported by the application client, wherein the format is a native format or a webpage format, and the server is used for storing the native page supporting the native format and the webpage supporting the webpage format;
and the sending module is used for sending the page to the application client, the application client is used for analyzing the page according to the format to obtain the multimedia data in the page and displaying the multimedia data through a created display component, and the display component is a native component matched with the native format or a webpage view component matched with the webpage format.
In a fifth aspect, there is provided a multimedia data presentation apparatus comprising a processor and a memory, the memory having stored therein at least one instruction, at least one program, set of codes, or set of instructions, which is loaded and executed by the processor to implement the operations performed in the multimedia data presentation method according to the first or second aspect.
In a sixth aspect, a computer-readable storage medium is provided, in which at least one instruction, at least one program, a set of codes, or a set of instructions is stored, which is loaded and executed by a processor to implement the operations performed in the multimedia data presentation method according to the first or second aspect.
The technical scheme provided by the embodiment of the invention has the following beneficial effects:
according to the method, the device and the storage medium provided by the embodiment of the invention, the native page supporting the native format and the webpage supporting the webpage format are stored on the server, according to the format supported by the application client, the native page can be displayed on the application client supporting the native format, and the webpage can be displayed on the application client not supporting the native format, so that the display speed of the application client supporting the native format is improved, the problem that the application client not supporting the native format cannot display is avoided, the multimedia data can be normally displayed on the application client not supporting the native format, the application range is expanded, and the flexibility and the universality are improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a schematic illustration of an implementation environment provided by an embodiment of the invention;
FIG. 2A is a flowchart of a method for displaying multimedia data according to an embodiment of the present invention;
FIG. 2B is a diagram illustrating a list of linked addresses according to an embodiment of the present invention;
FIG. 2C is a diagram of a native page according to an embodiment of the present invention;
FIG. 2D is an exemplary operational flow diagram provided by embodiments of the present invention;
FIG. 3A is a flowchart of a multimedia data presentation method according to an embodiment of the present invention;
FIG. 3B is a diagram illustrating a sharing option provided by an embodiment of the invention;
fig. 3C is a schematic diagram of an application client list according to an embodiment of the present invention;
FIG. 4 is a flowchart of a method for displaying multimedia data according to an embodiment of the present invention;
FIG. 5 is a schematic structural diagram of an application client supporting a native format according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of an application client that does not support native formats according to an embodiment of the present invention;
FIG. 7 is a schematic structural diagram of a multimedia data presentation apparatus according to an embodiment of the present invention;
FIG. 8 is a schematic structural diagram of another multimedia data presentation apparatus according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a terminal according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a server according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is a schematic diagram of an implementation environment provided by an embodiment of the present invention, and referring to fig. 1, the implementation environment includes a server 101 and a terminal 102, and the server 101 and the terminal 102 are connected through a network.
The server 101 is a multimedia data server, and can distribute multimedia data, such as text data, picture data, video data, audio data, and the like. In the application process, for multimedia data with the same content, the server 101 may set a page supporting the native format and a page supporting the web format, so that the native page can be displayed at the application client supporting the native format to increase the display speed, and the web page can be displayed at the application client not supporting the native format to avoid the problem that the native page cannot be displayed.
The terminal 102 may be a mobile phone, a computer, a tablet computer, or the like, the first application client 1021 is installed on the terminal 102, and the first application client 1021 supports the native format, so that the first application client 1021 may obtain a page supporting the native format from the server 101, and display multimedia data in the page through the created native component, thereby playing an effect of displaying the native page.
The terminal 102 may further have a second application client 1022 installed thereon, where the second application client 1022 supports a web page format but does not support a native format, and the second application client 1022 may obtain a page supporting the web page format from a server and display multimedia data in the page through the created web page view component, thereby playing an effect of displaying the web page.
The first application client 1021 and the second application client 1022 may interact with each other through an interface, for example, a page may be shared through the interface.
The embodiment of the invention can be applied to a plurality of scenes such as a scene that a user accesses a webpage by using a browser client or accesses a webpage shared by friends by using a chat application client. Two types of pages are set on the server: the page supporting the native format and the page supporting the webpage format ensure that the native page can be displayed when a user accesses by adopting the application client supporting the native format, and the webpage can be displayed when the user accesses by adopting the application client supporting the webpage format.
When the webpage is displayed through the webpage view component, the steps of initializing the browsing function kernel, loading library files related to the browsing function kernel, analyzing, typesetting, rendering and the like are required. When the native page is displayed through the native component, the steps of initializing a browsing function kernel and loading a library file are not needed, and the steps of analyzing, typesetting and rendering are simplified, so that compared with the method of displaying the web page through the web view component, the method has the advantages that the display speed is higher when the native page is displayed through the native component, and the display efficiency is higher.
However, in practical applications, not all application clients support the native format, and for the application clients that do not support the native format, the web page still needs to be exposed through the web view component. Therefore, two types of pages are arranged on the server, so that the display speed of the application client side supporting the native format is improved, the problem that the application client side not supporting the native format cannot display is solved, the multimedia data can be normally displayed on the application client side not supporting the native format, the application range is expanded, and the flexibility and the universality are improved. The specific process is described in detail in the following examples.
Fig. 2A is a flowchart of a multimedia data presentation method according to an embodiment of the present invention, where interaction subjects of the multimedia data presentation method are a server and an application client, and referring to fig. 2A, the method includes:
201. the application client acquires a first link address to be accessed.
And the first link address is used for jumping to a corresponding page so as to display the multimedia data in the page.
In one possible implementation, the user may input the first link address in an application client, and the application client obtains the first link address input by the user. Or, the application client may present one or more link addresses, the user may select a link address to be accessed from the presented link addresses, and the application client obtains a first link address selected by the user.
Referring to fig. 2B, the application client displays a plurality of link addresses, and when the user clicks a link address in the box, the application client obtains the link address clicked by the user.
202. And the application client creates a presentation component matched with the format according to the supported format.
Different application clients support different formats, and for application clients supporting different formats, multimedia data needs to be presented through different types of presentation components. The format supported by the application client is a native format or a webpage format, the display component is a native component matched with the native format or a webpage view component matched with the webpage format, a native page can be displayed when the multimedia data is displayed through the native component, and a webpage can be displayed when the multimedia data is displayed through the webpage view component.
The native components can include a RecycleView component, a TextView component, an ImageView component and the like, and the TextView component and the ImageView component can be mounted on the RecycleView component, so that the layout of text data and picture data in a control page of the RecycleView component is convenient. Of course, the native component may also be other types of components such as a ListView component. Additionally, the web view component may be a WebView component or other component.
In a possible implementation manner, considering that the application clients include an application client supporting a native format and an application client not supporting the native format but supporting a web page format, and the native page is faster than the presentation speed of the web page, for the application client supporting the native format, the native page may be preferentially presented, and for the application client not supporting the native format, the web page may be presented.
To this end, this step 202 may include any of:
2021. when the application client supports native formats, native components are created.
2022. When the application client supports a web page format, a web page view component is created.
In another possible implementation manner, considering that an application client supporting the native format may also support the web page format, some pages supporting the web page format may be exposed. Therefore, whether the page corresponding to the link address supports the native format or the web page format can be distinguished by whether the link address includes a designated identifier for indicating that the multimedia data is presented by the native component. The link address including the specified identification can be exposed through the native component, and the link address not including the specified identification can be exposed through the webpage view component.
The specified identifier may be a specified character, and the link address including the specified character may determine that the link address includes the specified identifier, or a specified field may be set in the link address, where data in the specified field indicates that the link address includes the specified identifier for the first data, and data in the specified field indicates that the link address does not include the specified identifier for the second data. For example, the first data is 1 and the second data is 0, or the first data is true and the second data is false. For example, the first linking address is http:// xxxx. Common = true, "? "indicates that the following is a designated field," initial = true "indicates that the data in the designated field is true, i.e., that the link address contains the designated identification.
To this end, this step 202 may include any of:
2023. when the application client supports a native format and the first link address contains the specified identity, a native component is created.
2024. When the application client supports the native format and the specified identifier is not included in the first link address, the web page view component is created.
2025. When the application client supports a web page format but not a native format, a web page view component is created.
It should be noted that the application client includes a browsing function kernel, the browsing function kernel may be responsible for parsing syntax of a page, rendering the page, and the like, and a general browsing function kernel may support a web page format and may parse the web page, but the general browsing function kernel does not support a native format and cannot parse the native page.
Thus, a parser may be created in an application client that supports native formats for parsing native pages, and an application client that includes a browsing function kernel and a parser may support native formats and web page formats, while an application client that includes a browsing function kernel but no parser may not support native formats but only web page formats.
203. The application client sends an access request to the server.
The access request carries a first link address and is used for requesting the server to return a page corresponding to the first link address.
It should be noted that there is no necessary timing relationship between the step 202 and the step 203, and after the first link address is acquired, the two steps may be executed at the same time or in tandem.
204. And when receiving the access request, the server acquires a page supporting the format corresponding to the first link address and sends the page to the application client.
For any link address, the server may store a page corresponding to the link address, and may provide the corresponding page for the application client according to the link address carried in the access request sent by the application client. In the embodiment of the present invention, the server may store the page supporting the native format and the corresponding page supporting the web page format, that is, store the native page and the web page. The two pages contain the same multimedia data, but the supported formats are different, and the corresponding link addresses of the two pages are different, so that the two pages can be distinguished according to the link addresses.
In one possible implementation, based on steps 2021 and 2022 described above, this step 204 may include any of the following:
2041. when the application client supports the native format, the page corresponding to the first link address is a page supporting the native format, so that the server acquires the page supporting the native format corresponding to the first link address and sends the page supporting the native format to the application client.
2042. When the application client side supports the webpage format but not the native format, the page corresponding to the first link address is the page supporting the webpage format, so that the server acquires the page supporting the webpage format corresponding to the first link address and sends the page supporting the webpage format to the application client side.
In another possible implementation manner, for convenience of management, the link addresses set by the page supporting the native format and the corresponding page supporting the web page format correspond to each other, except that the link address corresponding to the page supporting the native format includes the specified identifier, and the link address corresponding to the page supporting the web page format does not include the specified identifier.
In this case, based on the above steps 2023-2025, the step 204 may further include any one of the following:
2043. when the application client supports the native format and the first link address contains the designated identifier, the page corresponding to the first link address is the page supporting the native format, and the server acquires the page supporting the native format corresponding to the first link address.
2044. When the application client supports the native format and the first link address does not contain the designated identifier, the page corresponding to the first link address is the page supporting the native format, and the server acquires the page supporting the web page format corresponding to the first link address.
2045. And when the application client supports the webpage format but not the native format, acquiring the page which corresponds to the first link address and supports the webpage format.
When the application client supports the web page format but not the native format, if the first link address contains the specified identifier, the page corresponding to the first link address is a page supporting the native format, at this time, the specified identifier in the first link address needs to be deleted, the second link address is obtained, and the page corresponding to the second link address is obtained, so that the page supporting the web page format can be obtained.
For example, the first link address is "http:// xxxx. Common = true", will specify the identity "? And deleting the initial = true ', so that a second link address ' http:// xxxx.com ' can be obtained.
When the application client supports the webpage format but not the native format, if the first link address does not contain the designated identifier, the page corresponding to the first link address is a page supporting the webpage format, and the page supporting the webpage format corresponding to the first link address is directly obtained.
205. When the application client receives the page, the page is analyzed according to the supported format to obtain the multimedia data in the page, and the multimedia data is displayed through the display component.
For different formats supported, this step 205 may include any of:
2051. when the native format is supported by the application client, the page is analyzed according to the native format to obtain the multimedia data, and the multimedia data is displayed through the native component, so that the effect of displaying the native page can be achieved.
Based on the example of fig. 2B, when the application client is exposed through the native component, the exposed native page may be as shown in fig. 2C.
2052. When the application client supports the webpage format but not the native format, the webpage is analyzed according to the webpage format to obtain the multimedia data, and the multimedia data is displayed through the webpage view component, so that the webpage displaying effect can be achieved.
In the embodiment of the invention, the page comprises the structural data and the multimedia data, the structural data is used for describing the structure among the multimedia data, the application client analyzes the page according to the supported format, the structural data and the multimedia data can be identified, at the moment, the typesetting information of the multimedia data can be determined according to the structural data, and the multimedia data is displayed according to the typesetting information through the display component.
The native page and the web page have different structural data formats but the same content, for example, the server sets a tag in a web page format, such as a header "header," an article title "p," a picture "img," a footer "a font," and a font "fold" as the structural data in the web page, and the tag in the native format set in the native page may correspond to the tag in the web page format, and specifically may include tags in the header "x5-header," the article title "x5-p," the picture "x5-img," the footer "x 5-font," and the font "x 5-fold.
Accordingly, an application client supporting the web page format can recognize the tags in the web page format, and an analyzer can be created in the application client not supporting the web page format, so that the tags in the native format are recognized by the analyzer.
When the application client supports the native format, an exemplary operation flowchart of the embodiment of the present invention may be as shown in fig. 2D, referring to fig. 2D, determine a presentation manner by determining whether the link address includes the designated identifier, and present according to the determined presentation manner.
According to the method provided by the embodiment of the invention, the native page supporting the native format and the webpage supporting the webpage format are stored on the server, according to the format supported by the application client, the native page can be displayed on the application client supporting the native format, and the webpage can be displayed on the application client not supporting the native format, so that the display speed of the application client supporting the native format is improved, the problem that the application client not supporting the native format cannot display is avoided, the normal display of multimedia data on the application client not supporting the native format is ensured, the application range is expanded, and the flexibility and the universality are improved.
In the process of displaying multimedia data by an application client, a user may want to share a currently displayed page to a target application client, and when formats supported by the target application client are different, a sharing process executed by the application client and an access process executed by a subsequent target application client are also different, which refers to the following embodiments.
Fig. 3A is a flowchart of a multimedia data presentation method according to an embodiment of the present invention, in which an interaction subject of the multimedia data presentation method is a server, a first application client, and a second application client, where the first application client is an application client initiating sharing, and the second application client is a target application client sharing. In the embodiment of the present invention, taking the browsing function kernel of the first application client and the native format supported by the application client of the second application client as an example, referring to fig. 3A, the method includes:
301. and when the first application client detects the sharing operation of the second application client, sending a sharing request to the server.
The sharing operation may be a click operation on a sharing option on the display page, or the sharing operation may be an operation of sliding the page backwards, or the like. The second application client may be selected or otherwise determined by the user from a plurality of application clients. For example, the sharing option may be as shown in fig. 3B, and after the user clicks the sharing option, the application client list shown in fig. 3C is displayed, and the user selects a target application client to be shared from the application client list.
The sharing request carries the first link address and the application identifier of the second application client, and indicates that the page corresponding to the first link address is to be shared with the second application client, and the application identifier is used for determining the only corresponding application client and can be an application name or an application number.
302. And when receiving the sharing request, the server takes the first link address as a second link address and sends the second link address to the first application client.
When the native format is supported by the application client of the first application client, the page corresponding to the first link address is a page supporting the native format, and at this time, considering that the second application client may not necessarily support the native format, if the first link address is directly shared with the second application client, the second application client may not recognize the first link address. Therefore, the first application client sends a sharing request to the server.
When the server receives the sharing request, it determines whether the second application client supports the native format. And if the second application client also supports the native format, the server sends the first link address serving as a second link address to be shared to the first application client, and the first link address is shared to the second application client by the first application client.
303. And when the first application client receives the second link address, sharing the second link address to the second application client.
The first application client and the second application client are provided with interfaces, and the first application client can call the interfaces and share the second link address with the second application client. Or the first application client side and the second application client side interact through the operating system, the first application client side calls an interface between the first application client side and the operating system, the second link address is transmitted to the operating system, and the operating system transmits the second link address to the second application client side through the interface between the operating system and the second application client side.
304. And the second application client displays the second link address, creates a native component when detecting the access operation of the second link address, and sends an access request to the server, wherein the access request carries the second link address. Wherein the access operation may be an operation of clicking the second link address or other operations.
305. And when receiving the access request, the server acquires a page corresponding to the second link address and sends the page to the second application client.
306. And when the second application client receives the page, analyzing the page according to the native format to obtain the multimedia data in the page, and displaying the multimedia data through the native component.
Fig. 4 is a flowchart of a multimedia data presentation method according to an embodiment of the present invention, where interaction subjects of the multimedia data presentation method are a server, a first application client, and a second application client, where the first application client is used as an application client initiating sharing, and the second application client is used as a second application client sharing. In the embodiment of the present invention, for example, an application client of a first application client supports native format, and a browsing function kernel of a second application client does not support native format, referring to fig. 4, the method includes:
401. and when the first application client detects the sharing operation of the second application client, sending a sharing request to the server.
402. And when receiving the sharing request, the server acquires a link address corresponding to a page supporting the webpage format and corresponding to the first link address, and sends the link address serving as a second link address to the first application client.
If the second application client side does not support the native format, only the web page format is supported, and the first link address cannot be identified, so that the server acquires the link address corresponding to the page supporting the web page format and corresponding to the first link address as the second link address.
When the server distinguishes two link addresses corresponding to two pages according to whether the link addresses contain the specified identification, the server can delete the specified identification in the first link address to obtain a second link address.
403. And when the first application client receives the second link address, sharing the second link address to the second application client.
404. And the second application client displays the second link address, creates a webpage view component when detecting the access operation to the second link address, and sends an access request to the server, wherein the access request carries the second link address.
405. And when receiving the access request, the server acquires a page corresponding to the second link address and sends the page to the second application client.
406. And when the second application client receives the page, analyzing the page according to the webpage format to obtain the multimedia data in the page, and displaying the multimedia data through the webpage view component.
In addition to the embodiments shown in fig. 3A and fig. 4, in a case where the application client of the first application client supports the web page format but does not support the native format, in this case, no matter whether the second application client supports the native format, the first application client may directly share the first link address as the second link address to be shared to the target application client.
It should be noted that, the structure of the application client supporting the native format may be as shown in fig. 5, see fig. 5, and the application client may include a browsing function kernel, a parser, and an application layer, where the browsing function kernel is provided with the parser, and the parser may parse according to the native format to identify the multimedia data in the native page.
In the application process, the browsing function kernel acquires a first link address, creates a native component, sends an access request to the server, and returns a page corresponding to the first link address through the server.
In the display process, the application layer can detect the sharing operation triggered by the user on the first link address, and at the moment, an interface between the application layer and the target application client can be called to share the link address with the target application client. Or the sharing request can be sent to the server, so that the second link address returned by the server is received, an interface between the server and the target application client is called, and the link address is shared to the target application client.
The structure of the application client that does not support the native format may be as shown in fig. 6, and referring to fig. 6, the application client may include a browsing function kernel and an application layer, where the browsing function kernel may parse according to the web page format to identify the multimedia data in the web page.
In the application process, the browsing function kernel acquires a first link address, creates a webpage view component, sends an access request to the server, and returns a page corresponding to the first link address through the server.
In the display process, the application layer can detect the sharing operation triggered by the user on the first link address, and at the moment, an interface between the application layer and the target application client can be called to share the link address to the target application client.
In summary, the Instant advertisements frame in the related art does not support the display of web pages, cannot be applied to most pages, and cannot be shared to other application clients. In the embodiment of the invention, by specifying the identifier and performing format matching on the multimedia data, an Instant advertisements frame is realized on the application client supporting the native format, the page is displayed in the native format, the performance and the display smoothness are greatly improved, the display speed is increased, the user experience is improved, and the user browsing time is saved. In addition, the webpage can be normally displayed on the application client which does not support the native format, so that the user can normally browse the related content, and the smooth execution of the sharing process is ensured.
Fig. 7 is a schematic structural diagram of a multimedia data presentation apparatus according to an embodiment of the present invention. Referring to fig. 7, the apparatus includes:
an obtaining module 701, configured to perform the step of obtaining the link address in the foregoing embodiment;
a creating module 702, configured to perform the steps of creating the display component in the foregoing embodiments;
a sending module 703, configured to execute the step of sending the access request to the server in the foregoing embodiment;
a presentation module 704, configured to perform the parsing and presentation steps in the foregoing embodiments.
Optionally, the creating module 702 is configured to perform the step of creating the presentation component according to the format supported by the application client and whether the first link address includes the specified identifier in the foregoing embodiment.
Optionally, the presentation module 704 is configured to perform the steps of performing typesetting and presentation after the structural data and the multimedia data are identified in the above embodiments.
Optionally, the apparatus further comprises:
the sending module 703 is further configured to execute the step of sending the sharing request to the server in the foregoing embodiment;
and the sharing module is used for executing the step of sharing the second link address to the target application client in the embodiment.
Fig. 8 is a schematic structural diagram of a multimedia data presentation apparatus according to an embodiment of the present invention. Referring to fig. 8, the apparatus includes:
a receiving module 801, configured to perform the steps of receiving an access request in the foregoing embodiments;
an obtaining module 802, configured to perform the step of obtaining a page in the foregoing embodiment;
a sending module 803, configured to execute the step of sending the page to the application client in the foregoing embodiment.
Optionally, the obtaining module 802 is configured to perform the step of obtaining the page according to the format supported by the application client and whether the first link address includes the designated identifier in the foregoing embodiment.
Optionally, the apparatus further comprises:
the receiving module 801 is further configured to execute the step of receiving the sharing request in the foregoing embodiment;
the deleting module is used for executing the step of deleting the specified identification in the first link address;
the sending module 803 is further configured to execute the step of sending the second link address to the application client in the foregoing embodiment.
Optionally, the apparatus further comprises:
a receiving module 801, further configured to perform the step of receiving an access request in the foregoing embodiment;
the obtaining module 802 is further configured to perform the step of obtaining the page corresponding to the second link address and supporting the web page format in the foregoing embodiment;
the sending module 803 is further configured to execute the step of sending the page to the target application client in the foregoing embodiment.
It should be noted that: in the multimedia data presentation apparatus provided in the foregoing embodiment, when presenting multimedia data, only the division of the functional modules is exemplified, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the terminal or the server is divided into different functional modules to complete all or part of the functions described above. In addition, the multimedia data presentation apparatus and the multimedia data presentation method provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments and are not described herein again.
Fig. 9 is a schematic structural diagram of a terminal according to an embodiment of the present invention. The terminal is equipped with an application client, which can be used to implement the functions executed in the multimedia data presentation method shown in the above embodiments. Specifically, the method comprises the following steps:
terminal 900 can include components such as RF (Radio Frequency) circuitry 110, memory 120 including one or more computer-readable storage media, input unit 130, display unit 140, sensor 150, audio circuitry 160, transmission module 170, processor 180 including one or more processing cores, and power supply 190. Those skilled in the art will appreciate that the terminal structure shown in fig. 9 does not constitute a limitation of the terminal, and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components. Wherein:
the RF circuit 110 may be used for receiving and transmitting signals during information transmission and reception or during a call, and in particular, receives downlink information from a base station and then sends the received downlink information to the one or more processors 180 for processing; in addition, data relating to uplink is transmitted to the base station. In general, the RF circuitry 110 includes, but is not limited to, an antenna, at least one Amplifier, a tuner, one or more oscillators, a Subscriber Identity Module (SIM) card, a transceiver, a coupler, an LNA (Low Noise Amplifier), a duplexer, and the like. In addition, the RF circuitry 110 may also communicate with networks and other terminals via wireless communications. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System for Mobile communications), GPRS (General Packet Radio Service), CDMA (Code Division Multiple Access), WCDMA (Wideband Code Division Multiple Access), LTE (Long Term Evolution), email, SMS (Short Messaging Service), and the like.
The memory 120 may be used to store software programs and modules, such as the software programs and modules corresponding to the terminal shown in the above exemplary embodiments, and the processor 180 may execute various functional applications and data processing, such as implementing video-based interaction, by operating the software programs and modules stored in the memory 120. The memory 120 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the terminal 900, and the like. Further, the memory 120 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory 120 may also include a memory controller to provide the processor 180 and the input unit 130 access to the memory 120.
The input unit 130 may be used to receive input numeric or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control. In particular, input unit 130 may include a touch-sensitive surface 131 as well as other input terminals 132. The touch-sensitive surface 131, also referred to as a touch display screen or a touch pad, may collect touch operations by a user on or near the touch-sensitive surface 131 (e.g., operations by a user on or near the touch-sensitive surface 131 using a finger, a stylus, or any other suitable object or attachment), and drive the corresponding link device according to a predetermined program. Alternatively, the touch sensitive surface 131 may comprise two parts, a touch detection means and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 180, and receives and executes commands sent from the processor 180. Additionally, the touch-sensitive surface 131 may be implemented using various types of resistive, capacitive, infrared, and surface acoustic waves. In addition to touch-sensitive surface 131, input unit 130 may include other input terminals 132. In particular, other input terminals 132 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.
The display unit 140 may be used to display information input by or provided to a user and various graphical user interfaces of the terminal 900, which may be made up of graphics, text, icons, video, and any combination thereof. The Display unit 140 may include a Display panel 141, and optionally, the Display panel 141 may be configured in the form of an LCD (Liquid Crystal Display), an OLED (Organic Light-Emitting Diode), or the like. Further, the touch-sensitive surface 131 may cover the display panel 141, and when a touch operation is detected on or near the touch-sensitive surface 131, the touch operation is transmitted to the processor 180 to determine the type of the touch event, and then the processor 180 provides a corresponding visual output on the display panel 141 according to the type of the touch event. Although in FIG. 9, touch-sensitive surface 131 and display panel 141 are shown as two separate components to implement input and output functions, in some embodiments, touch-sensitive surface 131 may be integrated with display panel 141 to implement input and output functions.
The terminal 900 can also include at least one sensor 150, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor that may adjust the brightness of the display panel 141 according to the brightness of ambient light, and a proximity sensor that may turn off the display panel 141 and/or the backlight when the terminal 900 is moved to the ear. As one of the motion sensors, the gravity acceleration sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when the mobile phone is stationary, and can be used for applications of recognizing the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured in the terminal 900, detailed descriptions thereof are omitted.
The terminal 900, through the transmission module 170, can assist a user in sending and receiving e-mail, browsing web pages, accessing streaming media, etc., and it provides the user with wireless or wired broadband internet access. Although fig. 9 shows the transmission module 170, it is understood that it does not belong to the essential constitution of the terminal 900 and can be omitted entirely as needed within a scope not changing the essence of the invention.
The processor 180 is a control center of the terminal 900, links various parts of the entire handset using various interfaces and lines, and performs various functions of the terminal 900 and processes data by operating or executing software programs and/or modules stored in the memory 120 and calling data stored in the memory 120, thereby integrally monitoring the handset. Optionally, processor 180 may include one or more processing cores; preferably, the processor 180 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 180.
Although not shown, the terminal 900 may further include a camera, a bluetooth module, etc., which will not be described herein. Specifically, in the present embodiment, the display unit of the terminal 900 is a touch screen display, and the terminal 900 further includes a memory and at least one instruction, at least one program, a code set, or an instruction set, where the at least one instruction, the at least one program, the code set, or the instruction set is stored in the memory and configured to be loaded and executed by one or more processors, so as to implement the operations executed in the multimedia data presentation method in the foregoing embodiments.
Fig. 10 is a schematic structural diagram of a server according to an embodiment of the present invention, where the server 1000 may have a relatively large difference due to different configurations or performances, and may include one or more Central Processing Units (CPUs) 1022 (e.g., one or more processors) and a memory 1032, and one or more storage media 1030 (e.g., one or more mass storage devices) for storing applications 1042 or data 1044. Memory 1032 and storage medium 1030 may be transitory or persistent storage, among other things. The program stored on the storage medium 1030 may include one or more modules (not shown), each of which may include a sequence of instructions operating on a server. Still further, the central processor 1022 may be configured to communicate with the storage medium 1030, load a series of instruction operations in the storage medium 1030, and execute the multimedia data presentation method on the server 1000.
The server 1000 may also include one or more power supplies 1026, one or more wired or wireless network interfaces 1050, and one or more input-output interfacesA port 1058, one or more keyboards 1056, and/or one or more operating systems 1041, such as a Windows Server TM ，Mac OS X TM ，Unix TM ，Linux TM ，FreeBSD TM And so on.
The embodiment of the present invention further provides a multimedia data presentation apparatus, where the multimedia data presentation apparatus includes a processor and a memory, where the memory stores at least one instruction, at least one program, a code set, or an instruction set, and the instruction, the program, the code set, or the instruction set is loaded and executed by the processor to implement the operations executed in the multimedia data presentation method according to the foregoing embodiment.
The embodiment of the present invention further provides a computer-readable storage medium, where at least one instruction, at least one program, a code set, or a set of instructions is stored in the computer-readable storage medium, and the instruction, the program, the code set, or the set of instructions is loaded and executed by a processor to implement the operations performed in the multimedia data presentation method according to the above embodiment.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and should not be taken as limiting the scope of the present invention, which is intended to cover any modifications, equivalents, improvements, etc. within the spirit and scope of the present invention.
Claims (15)
1. A multimedia data presentation method is applied to an application client, and comprises the following steps:
acquiring a first link address to be accessed;
when the application client supports a native format and the first link address comprises a specified identifier, creating a native component matched with the native format, wherein the specified identifier is used for indicating that multimedia data is shown through the native component; sending an access request to a server, wherein the access request carries the first link address, the server returns a page supporting the native format corresponding to the first link address, and the server is used for storing a native page supporting the native format and a webpage page supporting the webpage format; when a page supporting the native format is received, analyzing the page supporting the native format according to the native format to obtain multimedia data in the page supporting the native format, and displaying the multimedia data through the native component;
when the application client supports the web page format but not the native format, creating a web page view component matching the web page format; sending the access request to the server, deleting the specified identifier in the first link address by the server under the condition that the first link address contains the specified identifier to obtain a second link address, and returning a page which corresponds to the second link address and supports the webpage format; when a page supporting the webpage format is received, analyzing the page supporting the webpage format according to the webpage format to obtain multimedia data in the page supporting the webpage format, and displaying the multimedia data through the webpage view component.
2. The method of claim 1, further comprising:
creating the web page view component when the application client supports the native format without the specified identification being included in the first link address.
3. The method of claim 1, wherein the page comprises multimedia data and structure data, and the parsing the page supporting the native format according to the native format to obtain the multimedia data in the page supporting the native format and presenting the multimedia data through the native component comprises:
identifying the structural data and the multimedia data according to the native format, and determining the typesetting information of the multimedia data according to the structural data; displaying the multimedia data according to the typesetting information through the native component;
the analyzing the page supporting the web page format according to the web page format to obtain the multimedia data in the page supporting the web page format, and displaying the multimedia data through the web page view component includes:
identifying the structural data and the multimedia data according to the webpage format, and determining the typesetting information of the multimedia data according to the structural data; and displaying the multimedia data according to the typesetting information through the webpage view component.
4. The method of claim 1, wherein the native format is supported by the application client, and wherein the first link address contains the specified identity;
the method further comprises the following steps:
when the sharing operation of a target application client is detected, sending a sharing request to the server, wherein the sharing request carries the first link address and an application identifier of the target application client, and when the server determines that the target application client supports the webpage format but not the native format, deleting the specified identifier in the first link address to obtain a second link address, and returning the second link address to the application client;
and when the second link address returned by the server is received, sharing the second link address to the target application client.
5. A multimedia data presentation method is applied to a server, and comprises the following steps:
receiving an access request sent by an application client, wherein the access request carries a first link address to be accessed;
when the application client supports a native format and the first link address comprises a designated identifier, acquiring a page supporting the native format corresponding to the first link address, wherein the designated identifier is used for indicating that multimedia data are displayed through a native component matched with the native format, and the server is used for storing the native page supporting the native format and a webpage page supporting the webpage format; sending a page supporting the native format to the application client, wherein the application client is used for analyzing the page supporting the native format according to the native format to obtain multimedia data in the page supporting the native format, and displaying the multimedia data through the created native component;
when the application client supports the webpage format but not the native format and the first link address contains a designated identifier, deleting the designated identifier in the first link address to obtain a second link address and acquiring a page supporting the webpage format corresponding to the second link address; and sending a page supporting the webpage format to the application client, wherein the application client is used for analyzing the page supporting the webpage format according to the webpage format to obtain multimedia data in the page supporting the webpage format, and displaying the multimedia data through the created webpage view component matched with the webpage format.
6. The method of claim 5, further comprising:
when the application client supports the native format and the first link address does not contain the specified identification, acquiring a page supporting the webpage format corresponding to the first link address.
7. The method of claim 5, further comprising:
receiving a sharing request sent by the application client, wherein the sharing request carries the first link address and an application identifier of a target application client, and the first link address comprises the specified identifier;
when the target application client side is determined to support the webpage format but not the native format according to the application identifier, deleting the specified identifier in the first link address to obtain a second link address;
and sending the second link address to the application client, and sharing the second link address to the target application client by the application client.
8. The method of claim 7, wherein after sending the second link address to the application client, the method further comprises:
receiving an access request sent by the target application client, wherein the access request carries the second link address;
and if the second link address does not contain the designated identifier, acquiring a page which corresponds to the second link address and supports the webpage format, sending the page to the target application client, analyzing the page by the target application client according to the webpage format to obtain multimedia data in the page, and displaying the multimedia data through the created webpage view component.
9. A multimedia data presentation device, applied to an application client, the device comprising:
the acquisition module is used for acquiring a first link address to be accessed;
a creating module, configured to create a native component matching a native format when the native format is supported by the application client and the first link address includes a specific identifier, where the specific identifier is used to indicate that multimedia data is presented by the native component;
a sending module, configured to send an access request to a server, where the access request carries the first link address, the server returns a page supporting the native format corresponding to the first link address, and the server is configured to store a native page supporting the native format and a web page supporting a web format;
the display module is used for analyzing the page supporting the native format according to the native format when receiving the page supporting the native format to obtain multimedia data in the page supporting the native format, and displaying the multimedia data through the native component;
the creating module is further used for creating a webpage view component matched with the webpage format when the application client side supports the webpage format but not supports the native format;
the sending module is further configured to send the access request to the server, delete the specified identifier in the first link address by the server when the first link address includes the specified identifier, obtain a second link address, and return a page corresponding to the second link address and supporting the web page format;
the display module is further configured to, when a page supporting the web page format is received, parse the page supporting the web page format according to the web page format to obtain multimedia data in the page supporting the web page format, and display the multimedia data through the web page view component.
10. The apparatus of claim 9, wherein the creation module is further configured to:
creating the web page view component when the application client supports the native format without the specified identification being included in the first link address.
11. The apparatus according to claim 9, wherein the native format is supported by the application client, and wherein the first link address contains the specified identity; the device further comprises:
the sending module is further configured to send a sharing request to the server when a sharing operation on a target application client is detected, where the sharing request carries the first link address and an application identifier of the target application client, and when it is determined that the target application client supports the web page format but not the native format, the server deletes the specified identifier in the first link address to obtain a second link address, and returns the second link address to the application client;
and the sharing module is used for sharing the second link address to the target application client when the second link address returned by the server is received.
12. A multimedia data presentation apparatus, for use in a server, the apparatus comprising:
the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving an access request sent by an application client, and the access request carries a first link address to be accessed;
the acquisition module is used for acquiring a page supporting a native format corresponding to the first link address when the application client supports the native format and the first link address contains a specified identifier, wherein the specified identifier is used for indicating that multimedia data are displayed through a native component matched with the native format, and the server is used for storing a native page supporting the native format and a webpage page supporting the webpage format;
the sending module is used for sending the page supporting the native format to the application client, and the application client is used for analyzing the page supporting the native format according to the native format to obtain the multimedia data in the page supporting the native format and displaying the multimedia data through the created native component;
the obtaining module is further configured to delete the specified identifier in the first link address to obtain a second link address when the application client supports the web page format but does not support the native format and the first link address includes the specified identifier, and obtain a page supporting the web page format corresponding to the second link address;
the sending module is further configured to send a page supporting the web page format to the application client, and the application client is configured to analyze the page supporting the web page format according to the web page format to obtain multimedia data in the page supporting the web page format, and display the multimedia data through a created web page view component matched with the web page format.
13. The apparatus of claim 12, wherein the obtaining module is further configured to:
when the application client supports the native format and the first link address does not contain the specified identifier, acquiring a page supporting the webpage format corresponding to the first link address.
14. Multimedia data presentation apparatus, comprising a processor and a memory, wherein the memory stores at least one instruction, at least one program, set of codes, or set of instructions, which is loaded and executed by the processor to implement the operations performed in the multimedia data presentation method according to any one of claims 1 to 4 or the operations performed in the multimedia data presentation method according to any one of claims 5 to 8.
15. A computer-readable storage medium, having at least one instruction, at least one program, a set of codes, or a set of instructions stored therein, which are loaded and executed by a processor to perform the operations as claimed in any one of claims 1 to 4 or 5 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710966292.8A CN110020293B (en) | 2017-10-17 | 2017-10-17 | Multimedia data display method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710966292.8A CN110020293B (en) | 2017-10-17 | 2017-10-17 | Multimedia data display method, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110020293A CN110020293A (en) | 2019-07-16 |
| CN110020293B true CN110020293B (en) | 2023-01-06 |
Family
ID=67186590
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710966292.8A Active CN110020293B (en) | 2017-10-17 | 2017-10-17 | Multimedia data display method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110020293B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110347979A (en) * | 2019-07-18 | 2019-10-18 | 网易（杭州）网络有限公司 | Information sharing method, device and touch control terminal, storage medium of the split screen across application |
| CN111259287B (en) * | 2020-01-14 | 2021-05-25 | 北京字节跳动网络技术有限公司 | Page content display method and device, electronic equipment and storage medium |
| CN111324834B (en) * | 2020-01-20 | 2024-01-16 | 北京有竹居网络技术有限公司 | Method, device, electronic equipment and computer readable medium for image-text mixed arrangement |
| CN111459529A (en) * | 2020-05-26 | 2020-07-28 | 北京拓世寰宇网络技术有限公司 | Application software updating method and device, readable medium and equipment |
| CN114115652A (en) * | 2020-08-10 | 2022-03-01 | 腾讯科技（武汉）有限公司 | Information display method, device, equipment and storage medium |
| CN112559069B (en) * | 2020-12-08 | 2022-04-12 | 腾讯科技（深圳）有限公司 | Running control method and device of sub-application, storage medium and electronic equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101778168A (en) * | 2010-02-05 | 2010-07-14 | 中国电信股份有限公司 | Method and system for optimization display of wed pages on browser of mobile terminal |
| CN101794298A (en) * | 2010-01-22 | 2010-08-04 | 中兴通讯股份有限公司 | Method for realizing page adaptation, page adaptation system and communication system |
| CN104572690A (en) * | 2013-10-17 | 2015-04-29 | 腾讯科技（深圳）有限公司 | Webpage data acquisition method, webpage data acquisition device and webpage data acquisition system |
| CN105653658A (en) * | 2015-12-29 | 2016-06-08 | 小米科技有限责任公司 | Information display method and device |
| CN107145490A (en) * | 2016-03-01 | 2017-09-08 | 腾讯科技（深圳）有限公司 | Webpage loads methods of exhibiting and webpage loading exhibiting device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104281621A (en) * | 2013-07-11 | 2015-01-14 | 腾讯科技（深圳）有限公司 | Method and device for browsing web page |
-
2017
- 2017-10-17 CN CN201710966292.8A patent/CN110020293B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101794298A (en) * | 2010-01-22 | 2010-08-04 | 中兴通讯股份有限公司 | Method for realizing page adaptation, page adaptation system and communication system |
| CN101778168A (en) * | 2010-02-05 | 2010-07-14 | 中国电信股份有限公司 | Method and system for optimization display of wed pages on browser of mobile terminal |
| CN104572690A (en) * | 2013-10-17 | 2015-04-29 | 腾讯科技（深圳）有限公司 | Webpage data acquisition method, webpage data acquisition device and webpage data acquisition system |
| CN105653658A (en) * | 2015-12-29 | 2016-06-08 | 小米科技有限责任公司 | Information display method and device |
| CN107145490A (en) * | 2016-03-01 | 2017-09-08 | 腾讯科技（深圳）有限公司 | Webpage loads methods of exhibiting and webpage loading exhibiting device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110020293A (en) | 2019-07-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110020293B (en) | Multimedia data display method, device and storage medium | |
| US10853437B2 (en) | Method and apparatus for invoking application programming interface | |
| CN107040609B (en) | Network request processing method and device | |
| CN107368518B (en) | Notification message management method, terminal and computer readable storage medium | |
| US10643021B2 (en) | Method and device for processing web page content | |
| CN108039963B (en) | Container configuration method and device and storage medium | |
| CN108156508B (en) | Barrage information processing method and device, mobile terminal, server and system | |
| US10956653B2 (en) | Method and apparatus for displaying page and a computer storage medium | |
| US9977661B2 (en) | Method and system for generating a user interface | |
| CN111316618B (en) | Network page storage method and terminal | |
| US9582584B2 (en) | Method, apparatus and system for filtering data of web page | |
| US10298590B2 (en) | Application-based service providing method, apparatus, and system | |
| JP2018521547A (en) | Method, apparatus and system for presenting information | |
| CN105227598B (en) | Resource sharing method, device and system based on cloud storage | |
| CN112749074B (en) | Test case recommending method and device | |
| CN113313804A (en) | Image rendering method and device, electronic equipment and storage medium | |
| JP6915074B2 (en) | Message notification method and terminal | |
| CN108182090B (en) | Flash plug-in loading method and device based on blink kernel | |
| CN106095423B (en) | Method, terminal and server for providing browsing service | |
| CN105631059B (en) | Data processing method, data processing device and data processing system | |
| CN110196662B (en) | Method, device, terminal and storage medium for displaying synchronization state | |
| CN109145182B (en) | Data acquisition method and device, computer equipment and system | |
| CN107798008B (en) | Content pushing system, method and device | |
| CN115828845A (en) | Multimedia data viewing method, device, medium and equipment | |
| CN114510417A (en) | Image rendering effect testing method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |