WO2017190709A1 - 媒体文件的展示方法、客户端及插件 - Google Patents

媒体文件的展示方法、客户端及插件 Download PDF

Info

Publication number
WO2017190709A1
WO2017190709A1 PCT/CN2017/083413 CN2017083413W WO2017190709A1 WO 2017190709 A1 WO2017190709 A1 WO 2017190709A1 CN 2017083413 W CN2017083413 W CN 2017083413W WO 2017190709 A1 WO2017190709 A1 WO 2017190709A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
brief information
client
display
media file
Prior art date
Application number
PCT/CN2017/083413
Other languages
English (en)
French (fr)
Inventor
徐刚
王平
裴林
阳丹
王贤骏
谢奕
Original Assignee
腾讯科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Publication of WO2017190709A1 publication Critical patent/WO2017190709A1/zh
Priority to US15/982,249 priority Critical patent/US10754668B2/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • G06F9/44526—Plug-ins; Add-ons
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
    • G06F16/43—Querying
    • G06F16/438—Presentation of query results
    • 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/954—Navigation, e.g. using categorised browsing
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/75—Indicating network or usage conditions on the user display

Definitions

  • the present application relates to the field of Internet technologies, and in particular, to a method, a client, and a plug-in for displaying a media file.
  • APPs applications
  • the user When the user opens an APP for the first time on the smart terminal, the user will push some type of information of the media file, such as displaying a static advertisement picture, playing an advertisement video, or playing a public service video. After displaying this media information, enter the main interface of the app.
  • the application provides a method for displaying a media file, which is applied to a client, and the method includes:
  • the media file is obtained and displayed.
  • the application also provides a method for displaying a media file, which is applied to a plug-in installed in a client, and the method includes:
  • the application further provides a client, comprising: a sending module, configured to send a media information acquisition request to a plug-in installed in the client, so that the plug-in is based on the media information acquisition request, from the server Obtaining first brief information and second brief information of a media file;
  • a receiving module configured to receive a notification message for the media file from the plugin
  • a display module configured to display the first brief information on the first display position according to the notification message received by the receiving module, and then display the second brief information on the second display position;
  • the media file is obtained and displayed.
  • the application provides a plugin installed in a client, including:
  • a receiving module configured to receive a media information acquisition request sent by the client
  • An obtaining module configured to acquire, according to the media information acquisition request received by the receiving module, a first brief information and a second brief information of a media file from a server;
  • a sending module configured to send, to the client, a notification message for the media file, so that the client displays the first brief information on the first display position according to the notification message, and then, in the second display The second brief information is displayed on the bit, wherein when the operation of the second brief information by the user is received, the media file is acquired and displayed.
  • the application also provides a non-transitory computer readable storage medium storing computer readable instructions that cause at least one processor to perform the method as described above.
  • FIG. 1 is a schematic structural diagram of an implementation environment involved in an example of the present application.
  • FIG. 2a is an exemplary flowchart of a method for displaying a media file according to an example of the present application
  • 2b is an exemplary flowchart of a method of displaying a media file according to another example of the present application
  • FIG. 3a is a schematic diagram showing an interface showing first brief information according to an example of the present application.
  • FIG. 3b is a schematic diagram showing an interface showing second brief information according to an example of the present application.
  • 3c is a schematic diagram showing an interface of a media file according to an example of the present application.
  • FIG. 4 is an exemplary flowchart of a method of displaying a media file according to another example of the present application.
  • FIG. 5 is an exemplary flowchart of a method for displaying a media file according to an example of the present application
  • FIG. 6 is an exemplary flowchart of a method of displaying a media file according to another example of the present application.
  • FIG. 7 is an interaction flowchart of a method for displaying a media file according to an example of the present application.
  • FIG. 8 is a schematic structural diagram of a client according to an example of the present application.
  • FIG. 9 is a schematic structural diagram of a client according to another example of the present application.
  • FIG. 10 is a schematic structural diagram of a plug-in according to an example of the present application.
  • FIG. 11 is a schematic structural diagram of an insert according to another example of the present application.
  • FIG. 12 is a schematic diagram showing the composition of a media file display system according to an example of the present application.
  • the media file to be displayed does not have the function of promotion.
  • the media information is no longer visible to the user, that is, the user cannot click the media information to understand the corresponding media file. More content, or any interaction with this media information. Therefore, the user's experience is not high, and the resource utilization of the terminal device is lowered. Therefore, there is a need to improve the promotion and display of such media files.
  • the media files to be displayed have promotional functions that are different from ordinary video files such as movies, TV shows, and the like.
  • the media file to be displayed may be a native advertisement provided by an advertiser, that is, an advertisement video that is not associated with other media files and is intended to promote a certain product.
  • the media file to be displayed is other video files for promotion or broadcasting purposes, such as news, public service videos, and the like.
  • the process of presenting a media file includes multiple steps. First, when the client is launched, the first brief information of the media file is displayed before entering the main interface of the client. Then, displaying the second brief information of the media file on the main interface, the user can Clicking on the two kinds of abbreviated information to enter the landing page of the media file, and displaying the complete information of the media file, such as a video, a QR code, a picture, and the like on the landing page.
  • the first brief information may be referred to as a splash screen advertisement
  • the second brief information may be referred to as a splash screen advertisement recovery bit (or an advertisement brief information displayed on a splash screen advertisement collection position) in the medium.
  • the full ad content is displayed on the landing page of the file.
  • FIG. 1 is a schematic structural diagram of an implementation environment according to an example of the present application.
  • the implementation environment includes a terminal device 110 and a server 120.
  • a client 111 is installed in the terminal device 110, and a plug-in 112 is installed in the client 111.
  • a promotion subserver 121 and a media subserver 122 are included in the server 120.
  • the screen of the terminal device 110 provides a display interface that displays the media file.
  • the terminal device 110 is a smart TV, a smart phone, a tablet computer, a laptop portable computer, or the like.
  • the client 111 is a media client for controlling the display of media files on the display interface.
  • the client 111 is a video app such as Tencent Video, Mango TV, and Aiqi.
  • the plug-in 112 is used to interact with the server to obtain various materials of the media file, including two kinds of abbreviated information and display control information (such as display duration), and forwarded to the client 111.
  • the plugin 112 can be used as an adware development kit (SDK).
  • SDK adware development kit
  • the server 120 can be a server, or a server cluster composed of several servers, or a cloud computing service center.
  • the promotion sub-server 121 may be referred to as an order server for interacting with the plug-in 112 for information on the advertising order;
  • the media sub-server 122 also referred to as the material server, is used to send various materials for the advertisement to the plug-in 112.
  • the client 111 when the user clicks on either of the two kinds of abbreviated information, the client 111 requests the media sub-server 122 for the complete media file, for example, entering the ad landing page to play the complete advertisement.
  • the terminal device 110 and the server 120 can be connected through a wireless network or a wired network.
  • FIG. 2a is an exemplary flowchart of a method of displaying a media file in accordance with an example of the present application. This method is applied to the client. As shown in Figure 2a, the method can include the following steps:
  • Step 201a Send a media information acquisition request to the plug-in installed in the client, so that the plug-in obtains the first brief information and the second brief information of the media file from the server based on the media information acquisition request.
  • the media information acquisition request is sent to the plug-in, for example, requesting to play a splash advertisement.
  • the plug-in requests the server to obtain two kinds of abbreviated information of the media file, that is, the first brief information and the second brief information.
  • the first simplified information and the second simplified information are all simplified versions of the media file, and may be in the form of a picture (such as a thumbnail of a promotional video), a graphic (such as a thumbnail and a summary of a promotional video), or a video file (such as a A short video of the promotion video).
  • the second abbreviated information may be part of the first abbreviated information, for example, a part of the text in the digest, or a part of the content in the thumbnail, or a screenshot of the video or the like.
  • Step 202a Receive a notification message for the media file from the plug-in, display the first brief information on the first display position according to the notification message, and then display the second brief information on the second display position.
  • the first brief information is first displayed, and after the display is completed, the second brief information is displayed.
  • the notification message includes a first display duration of the first brief information and a second display duration of the second brief information, such that the first brief information is displayed during the period of the first display duration, in the second
  • the second brief information is displayed during the period of the display duration.
  • the first display duration expires
  • the display of the first brief information is ended, and the main interface of the client is entered.
  • the second display duration expires, the second brief information disappears on the main interface.
  • the first display duration is 5 seconds
  • the second display duration may be permanent display or a specific value.
  • the timer is configured to display the remaining display duration while displaying the first brief information.
  • the second display duration is a specific value, the remaining display duration is displayed while displaying the second brief information.
  • the first display position can be a full-screen interface of the client
  • the second display position can be an advertisement space on the client's main interface.
  • the client receives the setting information of the second display bit from the plug-in, the setting information includes the shape, size and position of the second display bit, and then determines the second display position on the main interface of the client according to the setting information.
  • the shape is strip-shaped
  • the size includes the length and width of the strip
  • the position is located in the status bar of the main interface.
  • FIG. 3a is a schematic diagram showing an interface for displaying first brief information according to an example of the present application.
  • the interface 310 is a full-screen interface, and the first brief information of the media file to be displayed is displayed on the interface 310.
  • the media file to be displayed is an advertisement named "Meizu New Year Festival", and the first brief information is a short video of the advertisement.
  • the user installs Tencent video software on the smart TV.
  • the splash screen advertisement is played on the full screen interface of the smart TV, that is, a short video of the advertisement "Meizu New Year Festival".
  • the remaining display duration is displayed in block 311, for example, 3 seconds.
  • the interface turns to the main interface of Tencent video.
  • FIG. 3b is a schematic diagram of an interface showing second brief information according to an example of the present application.
  • the interface 320 is the main interface of the Tencent video
  • the dotted line 322 is the status bar area.
  • the second brief information of the media file to be displayed is displayed, such as the screenshot of the above-mentioned splash screen advertisement, or the above. Screen shot of the splash screen advertisement and the text "Meizu New Year Festival".
  • the second display duration is a permanent display.
  • various information of a normal media file can be displayed. For example, thumbnails of media files 1-4 are displayed in blocks 323-326, respectively, and animation of media files 5 is displayed in block 327.
  • FIG. 2b is an exemplary flowchart of a method for displaying a media file according to another example of the present application. As shown in FIG. 2b, the method may include the following steps:
  • Step 201b Send a media information acquisition request to the plug-in installed in the client, so that the plug-in obtains the first brief information and the second brief information of the media file from the server based on the media information acquisition request.
  • Step 202b Receive a notification message for the media file from the plug-in, display the first brief information on the first display position according to the notification message, and then display the second brief information on the second display position.
  • Step 203b in response to the user performing an operation on the second brief information, sending a media file display request to the server.
  • the client may directly send a media file display request to the server, or the client may forward the media file display request to the server through the plug-in.
  • Step 204b Receive a link address of the media file returned by the server, and obtain the media file according to the link address and display it.
  • the content of the media file includes one or more full-screen large images, video files, one or more thumbnails, two-dimensional codes, and the like.
  • Figure 3b when the user clicks on box 321, the interface enters the landing page displaying the media file, as shown in Figure 3c.
  • 3c is a schematic diagram of an interface for displaying a media file according to an example of the present application.
  • a full-screen large image or video of the media file is displayed in the interface 330, and the two-dimensional code of the media file is displayed in a frame 331 in the form of a floating layer.
  • Thumbnails 1-3 of the media file are displayed in blocks 332-334, respectively.
  • the small code icon is also embedded in the center 3311 of the two-dimensional code displayed on the 331.
  • the app on the mobile smart device (such as a mobile phone) can obtain the URL of the landing page by scanning the two-dimensional code, and can then move the smart device according to the URL.
  • the landing page is shown on the display.
  • the placement of all content on the entire interface shown in Figure 3c is called a template and is generated by the client.
  • the content of the media file is uploaded to the server by the media file provider (such as an advertiser).
  • the media file provider such as an advertiser
  • upload to a media subserver including full-screen large images, videos, and multiple thumbnails.
  • the two-dimensional code in the block 331 is that the advertiser provides the two-dimensional code address (ie, the landing page click address) and the small icon, and then the server generates the two-dimensional code according to the two-dimensional code address and the small icon.
  • the server can return a global resource locator (URL) address to the client as the link address.
  • URL global resource locator
  • the plug-in receives the URL address returned by the server, obtains the media file through the URL address, and stores the media file in the cache, and then the plug-in sends the cached address of the media file to the client. , so that the client obtains the media file according to the cache address, and then displays.
  • the application client sends a media information acquisition request to the plug-in installed in the client, and the plug-in acquires the media file from the server according to the media information acquisition request.
  • First brief information (such as a full screen large image), second short information (such as a part of a thumbnail), and the media file (such as a landing page), the media file including a video, a plurality of thumbnails, and the media file a second-dimensional code or the like
  • the plug-in receiving the first simplified information, the second simplified information, and the URL address of the media file returned by the server, and acquiring the first simplified information and the second information of the media file by using the URL address
  • the short message and the media file are stored in the cache, and then the plug-in sends the first brief information, the second brief information, and the cache address of the media file to the client, and the client according to the media file
  • the cached address of the first brief information acquires the first brief information of the media file and displays it on the first display position, and then, according
  • the client when receiving When the user specifies a first brief information, such as the user clicking an option in the full screen image (for example, clicking block 312 in FIG. 3a), the client may obtain the media file according to the cache address of the media file. And then displaying the media file (such as a landing page) on the smart TV.
  • the first brief information is displayed, it is not necessary to display the second brief information on the second display position. That is to say, when the landing page is opened on the smart TV by operating the full-screen large image, it is not necessary to display the second brief information on the flash screen recycling bit that can be linked to the landing page.
  • the first brief information is displayed on the first display position, and then the second brief information is displayed on the second display position, and the media file is sent to the server in response to the user's operation on the second brief information.
  • Displaying the request receiving the link address of the media file returned by the server, obtaining the media file according to the link address and displaying, visible, establishing association with the first brief information through the second brief information, and displaying the second on the main interface of the client.
  • the brief information introduces user interaction behavior, so that after opening an APP and viewing the first brief information (such as a splash screen advertisement), the user can further obtain a complete media file (such as viewing a complete advertisement), thereby improving the prior art.
  • the user can only passively watch the shortcomings of the first brief information, further dig out the user's interest points, satisfy the user's experience of actively watching the advertisement video, and improve the client display media through the interaction between the plug-in and the server and the client. Resource utilization at the time of the file.
  • FIG. 4 is an exemplary flow chart of a method of displaying a media file in accordance with another example of the present application. This method is applied to the client. As shown in FIG. 4, the method may include the following steps:
  • Step 401 Send a media information acquisition request to the plug-in installed in the client, so that the plug-in obtains the first brief information and the second brief information of the media file from the server according to the media information acquisition request.
  • Step 402 Receive a notification message for the media file from the plug-in, display the first brief information on the first display position according to the notification message, and input the floating layer in the first display position. An option to display the media file.
  • a floating layer may be outputted at block 312, and a picture of the remote controller is displayed thereon, and the text “press the OK button to learn the details” is displayed.
  • the user sees the first brief information, the user can further view the corresponding media file.
  • the client can obtain the first brief information and the second brief information according to the notification message, and the specific obtaining manners are as follows:
  • the notification message carries the first simplified information and the second simplified information.
  • the client After receiving the notification message, the client directly reads the first simplified information and the second simplified information from the notification message, and then displays the information separately.
  • the notification message sent by the plugin to the client may carry the first brief information and the first The cache address of the second brief information.
  • the client reads the first brief information from the notification message and displays it. After displaying the first brief information, the second brief information is obtained according to the cache address and displayed.
  • step 403 it is determined whether the user's operation on the option is received. If yes, go to step 405; otherwise, go to step 404.
  • Step 404 after displaying the first brief information, displaying the second brief information on the second display position.
  • step 405 is further performed.
  • Step 405 sending a media file display request to the server.
  • Step 406 Receive a link address of the media file returned by the server, obtain the media file according to the link address, and display the file.
  • the first brief information output prompt is displayed to display the selection of the media file.
  • Item and then display the second brief information, in each of the two display steps are configured a click path for the user to click on the option or the second brief information, thereby entering the landing page to view the complete media file, which can satisfy the user to the media at different times.
  • the viewing requirements of the file and improve the resource utilization of the client.
  • FIG. 5 is an exemplary flowchart of a method for displaying a media file according to an example of the present application, the method being applied to a plug-in installed in a client. As shown in Figure 5, the following steps are included:
  • Step 501 Receive a media information acquisition request sent by a client.
  • Step 502 Acquire, according to the media information acquisition request, the first brief information and the second brief information of a media file from the server.
  • the method in which the plug-in requests the server to obtain the abbreviated information is different according to the following two situations. in particular,
  • the first brief information displayed by the client is different each time it is started.
  • the plug-in requests the server to obtain the first brief information and the second brief information of a media file.
  • the plugin requests the server for abbreviated information, which only happens when the client is first started. Specifically, when the client is installed on the terminal device, when the user starts the client for the first time, the client sends the media information acquisition request to the plug-in for the first time, and the plug-in obtains the first brief information and the first file of the media file from the server. Second, the information can be returned to the client by the plug-in, for example, to notify the client to continue the startup process without the splash screen advertisement. Moreover, the plugin stores the obtained first brief information and the second brief information in a cache. In this way, when the client is subsequently started and sends a media information acquisition request to the plugin, the plugin can read the previously stored short information from the cache.
  • the plugin can request the server to obtain the abbreviated information in the following two ways:
  • the plug-in can directly obtain the first brief information and the second brief information from the server.
  • the plug-in receives the link address of the first abbreviated information and the link address of the second abbreviated information from the server, and the link address of the two kinds of abbreviated information may be a URL address. Then, the first brief information is pulled from the server according to the link address of the first brief information, and the second brief information is pulled from the server according to the link address of the second brief information.
  • Step 503 Send a notification message for the media file to the client.
  • the client displays the first brief information on the first display position according to the notification message, and then displays the second brief information on the second display position, and sends the media to the server in response to the operation performed by the user on the second brief information.
  • the file display request receives the link address of the media file returned by the server, and obtains the media file according to the link address and displays it.
  • the plug-in transfers information between the client and the server, requests the first brief information and the second brief information from the server, and then transmits the information to the client for display, so that the plug-in can be jointly processed with various clients. It reduces the client's acquisition process of the abbreviated information and improves the resource utilization of the client.
  • FIG. 6 is an exemplary flowchart of a method for displaying a media file according to another example of the present application, the method being applied to a plug-in installed in a client. As shown in FIG. 6, the following steps are included:
  • Step 601 Receive a media information acquisition request sent by the client.
  • Step 602 Acquire, according to the media information acquisition request, the first brief information, the first display duration, the second brief information, and the second display duration of the media file from the server, and store the first brief information and the second brief information in the cache. in.
  • Step 603 Read the first brief information and the second brief information from the cache, generate a notification message, and send the notification message to the client.
  • the notification message carries the cache information of the first brief information and the second brief information, so that the client reads the first brief information from the notification message and displays, and then, The second brief information is obtained according to the cache address and displayed.
  • the notification message carries a first display duration and a second display duration, so that the client displays the first brief information according to the first display duration, and displays the second brief information according to the second display duration.
  • FIG. 7 is an interaction flowchart of a method for displaying a media file according to an example of the present application, including interaction between a client, a plug-in, and a server. Specifically, the following steps are included:
  • step 701 when the client is started for the first time, the media information acquisition request is sent to the plugin.
  • step 702 the plug-in returns an instruction to the client that no media information can be displayed.
  • Step 703 The plug-in sends a media information acquisition request to the server.
  • the plug-in may perform step 703 first and then perform step 702.
  • Step 704 The server returns, to the plug-in, the first brief information, the first display duration, the second brief information, and the second display duration.
  • the client requests a splash screen advertisement from the plug-in.
  • the plug-in does not have a cached advertisement order locally.
  • the plug-in returns an instruction that the media-free information can be displayed to the client, that is, the client is notified that there is no splash screen.
  • the advertisement directly enters the main interface; on the other hand, the plug-in pulls the order of the splash screen advertisement from the server, and takes out the order information, that is, the link address of the first brief information (ie, the splash screen advertisement), the display duration, and the second brief information ( That is, the link address and display duration of the splash screen advertisement recycling bit).
  • Step 705 The plugin stores the first brief information and the second brief information in a cache.
  • Step 706 When the client is subsequently started, the media information acquisition request is sent to the plug-in.
  • Step 707 The plug-in reads the first abbreviated information and the second abbreviated information from the cache, and generates a notification message for obtaining the media information.
  • the notification message carries the first brief information, the first display duration, the cache address of the second brief information, and the second display duration.
  • the first brief information and the first display duration may be used for direct display by the client; and the cache address of the second brief information is used by the client to obtain the second brief information.
  • Step 708 The plug-in sends a notification message for obtaining media information to the client.
  • Step 709 The client displays the first brief information in the first display position according to the first display duration, and outputs an option prompting to display the media file.
  • Step 710 during the presentation of the first brief information, the client determines whether the user's operation on the option is received. If yes, go to step 711; otherwise, go to step 714.
  • step 711 the client sends a media file acquisition request to the server.
  • step 712 the server returns the link address of the media file to the client.
  • step 713 the client obtains the media file according to the link address and displays it.
  • the displayed media files include full-screen large images, videos, multiple thumbnails, two-dimensional codes, and the like.
  • Step 714 after displaying the first brief information, the client displays the second brief information in the second display position according to the second display duration.
  • the second brief information is displayed through the banner advertisement position in the status bar.
  • step 715 is performed.
  • step 715 the client sends a scan operation indication to the server.
  • step 716 the server counts the number of scans according to the received scan operation indication.
  • These times data can be used to charge advertisers, for example, in a prepaid manner, at a cost per thousand (CPM).
  • CPM cost per thousand
  • FIG. 8 is a schematic structural diagram of a client 800 according to an example of the present application. As shown in FIG. 8, the client 800 includes:
  • the sending module 810 is configured to send a media information acquisition request to the plug-in installed in the client, so that the plug-in obtains the first brief information and the second brief information of the media file from the server according to the media information obtaining request;
  • the receiving module 820 is configured to receive, by the plug-in, a notification message for the media file.
  • the display module 830 is configured to display the first brief information on the first display position according to the notification message received by the receiving module 820, and then display the second brief information on the second display position; wherein, when the user receives the When the operation of the second brief information is performed, the media file is obtained and displayed.
  • the notification message carries the cache information of the first brief information and the second brief information;
  • the display module 830 is configured to: read the first brief information from the notification message and display, and after displaying the first brief information, The second brief information is obtained according to the cache address and displayed.
  • the notification message includes a first display duration of the first brief information and a second display duration of the second brief information; the display module 830 is configured to display the first brief information according to the first display duration, according to the second display duration Show the second brief information.
  • the display module 830 is further configured to: when the first brief information is displayed, output an option to display the media file in a floating layer manner on the first display bit; wherein, if the user receives the option The operation module 830 obtains the media file and displays, and no longer displays the second brief information; if the user does not receive the operation of the option, after displaying the first brief information, the second display position is displayed. The second brief information.
  • the first display bit is a full-screen interface of the client
  • the display module 830 is configured to: when the client is started, display the first brief information on the full-screen interface; receive the setting information of the second display bit from the plug-in, according to The setup information determines the second presentation bit on the client's main interface.
  • FIG. 9 is a schematic structural diagram of a client 900 according to another example of the present application.
  • the client 900 can include a processor 910, a memory 920, a port 930, and a bus 940.
  • Processor 910 and memory 920 are interconnected by a bus 940.
  • Processor 910 can receive and transmit data through port 930. among them,
  • the processor 910 is configured to execute a machine readable instruction module stored by the memory 920.
  • Memory 920 stores machine readable instruction modules executable by processor 910.
  • the instruction module executable by the 910 includes a sending module 921, a receiving module 922, and a display module 923. among them,
  • the method may be: sending a media information obtaining request to the plug-in installed in the client, so that the plug-in obtains the first brief information and the second brief information of the media file from the server based on the media information obtaining request. information;
  • the receiving module 922 may be executed by the processor 910 to: receive a notification message for the media file from the plug-in;
  • the first brief information is displayed on the first display position according to the notification message received by the receiving module 922, and then the second brief information is displayed on the second display position;
  • the media file is obtained and displayed.
  • FIG. 10 is a schematic structural diagram of an insert 1000 according to an example of the present application.
  • the plugin 1000 includes:
  • the receiving module 1010 is configured to receive a media information acquisition request sent by the client.
  • the obtaining module 1020 is configured to obtain, according to the media information acquisition request received by the receiving module 1010, the first brief information and the second brief information of the media file from the server;
  • the sending module 1030 is configured to send a notification message for the media file to the client, so that the client displays the first brief information on the first display position according to the notification message, and then displays the second brief information on the second display position. And, when the operation of the second brief information by the user is received, the media file is obtained and displayed.
  • the obtaining module 1020 is configured to receive, by the server, a link address of the first brief information and a link address of the second brief information; and a link address according to the first brief information. Pulling the first brief information from the server; pulling the second brief information from the server according to the link address of the second brief information.
  • the obtaining module 1020 is further configured to: obtain, by the server, a first display duration of the first brief information and a second display duration of the second brief information, where the notification message sent by the sending module 1030 carries the first The display duration and the second display duration are such that the client displays the first brief information according to the first display duration and the second brief information according to the second display duration.
  • the plugin 1000 further includes a storage module 1040. among them,
  • the storage module 1040 is configured to store the first brief information and the second brief information in a cache
  • the sending module 1030 is configured to read the first brief information and the second brief information from the cache, and generate a notification message.
  • FIG. 11 is a schematic structural diagram of an insert 1100 according to another example of the present application.
  • the server 1100 can include a processor 1110, a memory 1120, a port 1130, and a bus 1140.
  • the processor 1110 and the memory 1120 are interconnected by a bus 1140.
  • the processor 1110 can receive and transmit data through the port 1130. among them,
  • the processor 1110 is configured to execute a machine readable instruction module stored by the memory 1120.
  • the memory 1120 stores a machine readable instruction module executable by the processor 1110.
  • the instruction module executable by the processor 1110 includes a receiving module 1121, an obtaining module 1122, and a sending module 1123. among them,
  • the receiving module 1121 may be: receiving a media information acquisition request sent by the client;
  • the method may be: acquiring, according to the media information obtaining request received by the receiving module 1121, the first simplified information and the second simplified information of the media file from the server;
  • the sending module 1123 When the sending module 1123 is executed by the processor 1110, it may be: sending the a notification message of the media file, so that the client displays the first brief information on the first display position according to the notification message, and then displays the second brief information on the second display position, wherein when the user receives the second brief information, When the operation of the brief information is obtained, the media file is obtained and displayed.
  • the instruction module further includes a storage module 1124. In some instances,
  • the first simplified information and the second simplified information may be stored in the cache
  • the sending module 1123 When the sending module 1123 is executed by the processor 1110, the first short information and the second simplified information may be read from the cache, and a notification message is generated.
  • FIG. 12 is a schematic diagram showing the composition of a media file display system 1200 according to an example of the present application.
  • the display system 1200 of the media file includes: a client 1210, a plug-in 1220, and a server 1230, where
  • the client 1210 is configured to send a media information acquisition request to the plug-in 1220, receive a notification message for a media file from the plug-in 1220, display the first brief information on the first display position according to the notification message, and then, on the second display position, Displaying second brief information; wherein, when receiving the operation of the second brief information by the user, acquiring the media file and displaying
  • the plug-in 1220 is configured to receive a media information acquisition request sent by the client 1210.
  • the first brief information and the second brief information of the media file are obtained from the server 1230 according to the media information acquisition request; and the notification message is sent to the client 1210.
  • the client 1210 may include the various modules shown in FIG. 8, and the plug-in 1220 may include the various modules shown in FIG.
  • the sending module 810 of the client 1210 sends a media information acquisition request to the receiving module 1010 of the plug-in 1220.
  • the sending module 1030 of the plug-in 1220 sends a media information obtaining request to the server 1230, and the receiving module 1010 of the plug-in 1220 obtains the first brief information and the second brief information of the media file from the server 1230;
  • the sending module 1030 of the plug-in 1220 sends a notification message to the receiving module 820 of the client 1210.
  • the sending module 810 of the client 1210 sends a media file display request to the server 1230;
  • the receiving module 820 of the client 1210 receives the link address of the media file returned by the server 1230.
  • each functional module in each example of the present application may be integrated into one processing unit, or each module may exist physically separately, or two or more modules may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • each of the examples of the present application can be implemented by a data processing program executed by a data processing device such as a computer.
  • the data processing program constitutes the present application.
  • a data processing program usually stored in a storage medium is executed by directly reading a program out of a storage medium or by installing or copying the program to a storage device (such as a hard disk and or a memory) of the data processing device. Therefore, such a storage medium also constitutes the present application.
  • the storage medium can use any type of recording method, such as paper storage medium (such as paper tape, etc.), magnetic storage medium (such as floppy disk, hard disk, flash memory, etc.), optical storage medium (such as CD-ROM, etc.), magneto-optical storage medium ( Such as MO, etc.).
  • the present application also discloses a storage medium in which is stored a data processing program for performing any of the above examples of the methods of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Remote Sensing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请公开了一种媒体文件的展示方法、客户端及插件。该方法包括：客户端向安装于客户端内的插件发送媒体信息获取请求，以使插件基于媒体信息获取请求，从服务器获取一媒体文件的第一简略信息和第二简略信息；从插件接收针对该媒体文件的通知消息，根据通知消息在第一展示位上展示第一简略信息，之后，在第二展示位上展示第二简略信息，其中，当收到用户对所述第二简略信息的操作时，获取该媒体文件并展示。

Description

媒体文件的展示方法、客户端及插件
本申请要求于2016年05月06日提交中国专利局、申请号为201610298190.9、发明名称为“一种媒体文件的展示方法、客户端、插件及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及互联网技术领域，尤其涉及一种媒体文件的展示方法、客户端及插件。
背景
基于智能终端的飞速发展，用户可以在智能终端上安装各种应用程序(APP)用于浏览、观看各种媒体文件。当用户在智能终端上首次打开一APP时，会向用户推送媒体文件的某类信息，比如展示一张静态的广告图片，或者播放一段广告视频，或者播放一公益宣传片等。在展示完这一媒体信息后，再进入该APP的主界面。
技术内容
本申请提供了一种媒体文件的展示方法，应用于客户端，所述方法包括：
向安装于所述客户端内的插件发送媒体信息获取请求，以使所述插件基于所述媒体信息获取请求，从所述服务器获取一媒体文件的第一简略信息和第二简略信息；
从所述插件接收针对该媒体文件的通知消息，根据所述通知消息在第一展示位上展示所述第一简略信息，之后，在第二展示位上展示所述 第二简略信息；
其中，当收到用户对所述第二简略信息的操作时，获取该媒体文件并展示。
本申请还提供了一种媒体文件的展示方法，应用于安装于客户端内的插件，所述方法包括：
接收所述客户端发送的媒体信息获取请求；
基于所述媒体信息获取请求，从服务器获取一媒体文件的第一简略信息和第二简略信息；及，
向所述客户端发送针对该媒体文件的通知消息，以使所述客户端根据所述通知消息在第一展示位上展示所述第一简略信息，之后，在第二展示位上展示所述第二简略信息，其中，当收到用户对所述第二简略信息的操作时，获取该媒体文件并展示。
本申请又提供了一种客户端，包括：发送模块，用于向安装于所述客户端内的插件发送媒体信息获取请求，以使所述插件基于所述媒体信息获取请求，从所述服务器获取一媒体文件的第一简略信息和第二简略信息；
接收模块，用于从所述插件接收针对该媒体文件的通知消息；
展示模块，用于根据所述接收模块接收的通知消息，在第一展示位上展示所述第一简略信息，之后，在第二展示位上展示所述第二简略信息；其中，当收到用户对所述第二简略信息的操作时，获取该媒体文件并展示。
本申请提供了一种插件，所述插件安装于客户端内，包括：
接收模块，用于接收所述客户端发送的媒体信息获取请求；
获取模块，用于基于所述接收模块接收的媒体信息获取请求，从服务器获取一媒体文件的第一简略信息和第二简略信息；及，
发送模块，用于向所述客户端发送针对该媒体文件的通知消息，以使所述客户端根据所述通知消息在第一展示位上展示所述第一简略信息，之后，在第二展示位上展示所述第二简略信息，其中，当收到用户对所述第二简略信息的操作时，获取该媒体文件并展示。
本申请还提供了一种非易失性计算机可读存储介质，存储有计算机可读指令，可以使至少一个处理器执行如上所述的方法。
附图简要说明
为了更清楚的说明本申请实例中的技术方案，下面将对实例描述中所需要使用的附图作简单的介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实例，对于本领域普通技术人员来说，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。其中，
图1为本申请一实例所涉及的实施环境的结构示意图；
图2a为依据本申请一实例的媒体文件的展示方法的示例性流程图；
图2b为依据本申请另一实例的媒体文件的展示方法的示例性流程图；
图3a为依据本申请一实例的展示第一简略信息的界面示意图；
图3b为依据本申请一实例的展示第二简略信息的界面示意图；
图3c为依据本申请一实例的展示媒体文件的界面示意图；
图4为依据本申请另一实例的媒体文件的展示方法的示例性流程图；
图5为依据本申请一实例的媒体文件的展示方法的示例性流程图；
图6为依据本申请另一实例的媒体文件的展示方法的示例性流程图；
图7为依据本申请一实例的媒体文件的展示方法的交互流程图；
图8依据本申请一实例的客户端的结构示意图；
图9为依据本申请另一实例的客户端的结构示意图；
图10依据本申请一实例的插件的结构示意图；
图11为依据本申请另一实例的插件的结构示意图；
图12为依据本申请一实例的媒体文件的展示系统的组成示意图。
实施方式
为下面将结合本申请实例中的附图，对本申请实例中的技术方案进行清楚、完整地描述，显然，所描述的实例是本申请一部分实例，而不是全部的实例。基于本申请中的实例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实例，都属于本申请保护的范围。
在一些实例中，待展示的媒体文件不具备推广的功能，当用户首次打开APP、展示完一媒体信息后，该媒体信息对用户不再可见，即用户无法点击该媒体信息以了解相应媒体文件的更多内容，或者针对该媒体信息进行任何互动。因此，用户的体验不高，并且降低了终端设备的资源利用率。因此，需要改善这种媒体文件的推广和展示效果。
在一些实例中，待展示的媒体文件具备推广的功能，不同于普通的视频文件，如电影、电视剧等。该待展示的媒体文件可以是由广告主提供的原生广告，即不与其他媒体文件相关联、旨在推广某产品的广告视频。或者，该待展示的媒体文件是以推广或者广播为目的其他视频文件，如新闻、公益宣传片等。
在一些实例中，展示一媒体文件的过程包括多个步骤。首先，在客户端被启动时，在进入客户端的主界面之前，展示该媒体文件的第一简略信息。然后，在主界面上展示该媒体文件的第二简略信息，用户可以 针对这两种简略信息进行点击操作，从而进入媒体文件落地页，在落地页上显示该媒体文件的完整信息，如视频、二维码、图片等。在具体实现时，第一简略信息可以被称为闪屏广告，第二简略信息可以被称为闪屏广告回收位(或者说是在闪屏广告回收位上展示的广告简略信息)，在媒体文件落地页上显示完整的广告内容。
图1为本申请一实例所涉及的实施环境的结构示意图。如图1所示，该实施环境包括终端设备110和服务器120。在终端设备110中安装有客户端111，在客户端111内安装有插件112。在服务器120中包括推广子服务器121和媒体子服务器122。
在展示一媒体文件时，终端设备110的屏幕提供展示该媒体文件的显示界面。例如，终端设备110为智能电视、智能手机、平板电脑、膝上型便携计算机等。客户端111为媒体客户端，用于控制媒体文件在显示界面上的展示。例如，客户端111为腾讯视频、芒果TV、爱奇异等视频APP。插件112用于和服务器交互、获取媒体文件的各种素材，包括两种简略信息和展示控制信息(如展示时长)，并且向客户端111转发。在具体实现时，插件112可以作为一种广告软件开发工具包(SDK)。
其中，服务器120可以是一台服务器，或者由若干台服务器组成的服务器集群，或者是一个云计算服务中心。根据处理功能的不同，推广子服务器121可称为订单服务器，用于和插件112交互广告订单的信息；媒体子服务器122又称为素材服务器，用于向插件112发送广告的各种素材。在本申请的实例中，当用户点击两种简略信息的任一种时，客户端111向媒体子服务器122请求完整的媒体文件，例如，进入广告落地页播放完整的广告。
其中，终端设备110和服务器120可以通过无线网络或有线网络相连。
图2a为依据本申请一实例的媒体文件的展示方法的示例性流程图。该方法应用于客户端。如图2a所示，该方法可包括如下步骤：
步骤201a，向安装于客户端内的插件发送媒体信息获取请求，以使插件基于媒体信息获取请求，从服务器获取一媒体文件的第一简略信息和第二简略信息。
本步骤中，客户端被启动时，向插件发送媒体信息获取请求，例如，请求播放一闪屏广告。此时，插件接收到该媒体信息获取请求后，向服务器请求获取一媒体文件的两种简略信息，即第一简略信息和第二简略信息。
其中，第一简略信息和第二简略信息都是媒体文件的简略版，其形式可以是图片(如一推广视频的缩略图)、图文(如一推广视频的缩略图和摘要)或者视频文件(如一推广视频的简短视频)。第二简略信息可以是第一简略信息的一部分，例如，摘要中的部分文字，或者缩略图中的一部分内容，或者视频的截图等。
步骤202a，从插件接收针对该媒体文件的通知消息，根据通知消息在第一展示位上展示第一简略信息，之后，在第二展示位上展示第二简略信息。
本步骤中，在展示的先后顺序上，首先展示第一简略信息，展示完毕后，再展示第二简略信息。
在展示的时长上，通知消息中包括第一简略信息的第一展示时长和第二简略信息的第二展示时长，这样，在第一展示时长内的期间内展示第一简略信息，在第二展示时长内的期间内展示第二简略信息。当第一展示时长到期时，结束第一简略信息的展示，进入客户端的主界面。当第二展示时长到期时，第二简略信息在主界面上消失。例如，第一展示时长为5秒，第二展示时长可以为永久展示或者为一具体的数值。在一 些实例中，配置计时器，在展示第一简略信息的同时展示剩余的展示时长，当第二展示时长为一具体的数值时，在展示第二简略信息的同时展示剩余的展示时长。
在展示位置上，第一展示位可以为客户端的全屏界面，第二展示位可以为客户端的主界面上的某个广告位。这样，当客户端被启动时，在全屏界面上展示第一简略信息。客户端从插件接收第二展示位的设置信息，设置信息包括第二展示位的形状、尺寸和位置，然后根据设置信息在客户端的主界面上确定第二展示位。例如，形状为条状，尺寸包括条状的长和宽，位置位于主界面的状态栏中。
图3a为依据本申请一实例的展示第一简略信息的界面示意图，如图3a所示，界面310为全屏界面，在界面310上展示待展示媒体文件的第一简略信息。例如，待展示媒体文件为一广告，名称为“魅族年货节”，第一简略信息为该广告的简短视频。具体而言，用户在智能电视上安装有腾讯视频的软件，当用户启动腾讯视频后，在智能电视的全屏界面上播放闪屏广告，即广告“魅族年货节”的简短视频。此外，在方框311中显示剩余的展示时长，例如为3秒。在播放完该简短视频后，界面转向腾讯视频的主界面。
图3b为依据本申请一实例的展示第二简略信息的界面示意图。如图3b所示，界面320为腾讯视频的主界面，虚线322以上为状态栏区域，在方框321中展示待展示媒体文件的第二简略信息，如上述闪屏广告的截屏图，或者上述闪屏广告的截屏图以及文字“魅族年货节”。第二展示时长为永久展示。在虚线322以下，可以显示普通媒体文件的各种信息。例如，在方框323-326中分别显示媒体文件1-4的缩略图，在方框327中显示媒体文件5的动画。
图2b为依据本申请另一实例的媒体文件的展示方法的示例性流程图，如图2b所示，该方法可包括如下步骤：
步骤201b，向安装于客户端内的插件发送媒体信息获取请求，以使插件基于媒体信息获取请求，从服务器获取一媒体文件的第一简略信息和第二简略信息。
步骤202b，从插件接收针对该媒体文件的通知消息，根据通知消息在第一展示位上展示第一简略信息，之后，在第二展示位上展示第二简略信息。
步骤203b，响应于用户对第二简略信息所做的操作，向服务器发送媒体文件展示请求。
在具体实现时，客户端可直接向服务器发送媒体文件展示请求，或者客户端可以通过插件向服务器转发上述媒体文件展示请求。
步骤204b，接收服务器返回的该媒体文件的链接地址，根据链接地址获取该媒体文件并展示。
本步骤中，该媒体文件的内容包括一个或多个全屏大图、视频文件、一个或多个缩略图、二维码等。例如，在图3b中，当用户点击方框321后，界面进入展示媒体文件的落地页，如图3c所示。图3c为依据本申请一实例的展示媒体文件的界面示意图，在界面330中显示该媒体文件的全屏大图或者视频，以浮层的形式在方框331中显示该媒体文件的二维码，在方框332-334中分别显示该媒体文件的缩略图1-3。其中，在331显示的二维码中央3311还嵌有小图标，移动智能设备(如手机)上的app通过扫描该二维码，可以获取落地页的URL，进而能根据此URL在移动智能设备上展示所述落地页。图3c所示的整个界面上所有内容的摆放方式称为模板，是由客户端来生成。
媒体文件的这些内容由媒体文件提供商(如广告主)上传到服务器， 例如，上传到媒体子服务器，包括全屏大图、视频、多个缩略图。其中，方框331中的二维码，是由广告主提供二维码地址(即落地页点击地址)以及小图标，然后由服务器根据二维码地址和小图标生成该二维码。
当客户端直接向服务器发送媒体文件展示请求时，服务器可以向客户端返回一全球资源定位器(URL)地址作为链接地址。当客户端通过插件向服务器转发上述媒体文件展示请求时，插件接收服务器返回的URL地址，通过该URL地址获取该媒体文件并存入缓存中，然后插件将该媒体文件的缓存地址发送给客户端，使得客户端根据该缓存地址获取该媒体文件，进而展示。
具体的，当所述客户端位于智能电视上时，所述应用客户端向安装于客户端内的插件发送媒体信息获取请求，所述插件基于媒体信息获取请求，从服务器获取所述媒体文件的第一简略信息(如全屏大图)、第二简略信息(如缩略图中的一部分)及所述媒体文件(如落地页)，所述媒体文件包括视频、多个缩略图及该媒体文件的二维码等，插件接收服务器返回的所述媒体文件的第一简略信息、第二简略信息及所述媒体文件的URL地址，通过上述URL地址获取所述媒体文件的第一简略信息、第二简略信息及所述媒体文件并存入缓存中，然后插件将所述媒体文件的第一简略信息、第二简略信息及所述媒体文件的缓存地址发送给客户端，客户端根据所述媒体文件的第一简略信息的缓存地址获取所述媒体文件的第一简略信息并在第一展示位上进行展示，之后，根据所述媒体文件的第二简略信息的缓存地址获取所述媒体文件的第二简略信息并在第二展示位(如闪屏广告回收位)上进行展示，当接收到用户对第二简略信息所做的操作(如用户点击闪屏广告回收位的区域)时，客户端根据所述媒体文件的缓存地址获取所述媒体文件，进而在智能电视上展示所述媒体文件。可选的，在客户端展示第一简略信息时，当接收 到用户对第一简略信息的指定操作时，如用户点击全屏大图中某个选项(例如点击图3a中的方框312)，客户端可根据所述媒体文件的缓存地址获取所述媒体文件，进而在智能电视上展示所述媒体文件(如落地页)，此种情况下，当第一简略信息展示完毕之后，就不必在第二展示位上展示第二简略信息。也就是说，当通过操作全屏大图而在智能电视上打开了落地页之后，就不必在能够链接到落地页的闪屏回收位上展示第二简略信息了。
在本实例中，通过在第一展示位上展示第一简略信息，之后，在第二展示位上展示第二简略信息，响应于用户对第二简略信息所做的操作，向服务器发送媒体文件展示请求，接收服务器返回的该媒体文件的链接地址，根据链接地址获取该媒体文件并展示，可见，通过第二简略信息建立与第一简略信息的关联，在客户端的主界面上通过展示第二简略信息引入用户互动行为，使得用户在打开一APP、观看完第一简略信息(如一闪屏广告)后，能够进一步获取完整的媒体文件(如观看完整的广告)，因此，改善了现有技术中用户只能被动观看第一简略信息的缺点，进一步挖掘出用户的兴趣点，满足了用户主动观看广告视频的体验，并且通过插件和服务器、客户端之间的交互，提高了客户端展示媒体文件时的资源利用率。
图4为依据本申请另一实例的媒体文件的展示方法的示例性流程图。该方法应用于客户端。如图4所示，该方法可包括如下步骤：
步骤401，向安装于客户端内的插件发送媒体信息获取请求，以使插件基于媒体信息获取请求，从服务器获取一媒体文件的第一简略信息和第二简略信息。
步骤402，从插件接收针对该媒体文件的通知消息，根据通知消息在第一展示位上展示第一简略信息，并在第一展示位上以浮层的方式输 出提示展示该媒体文件的选项。
如图3a所示，在方框312中显示“若了解详情，请点击此处”，即提示用户若要观看完整的媒体文件，可点击312所示的选项。具体实现时，当显示终端为智能电视时，可以在方框312处输出一浮层，在其上显示一张遥控器的图片，并配以文字“按确定键，了解详情”，以此提示用户在看到第一简略信息时，也可以进一步观看相应的媒体文件。
本步骤中，客户端根据通知消息可以获取到第一简略信息和第二简略信息，具体的获取方式又有以下两种：
方式一，通知消息携带有第一简略信息以及第二简略信息，这样，客户端在接收到通知消息后，直接从通知消息中读取出第一简略信息以及第二简略信息，进而分别展示。
方式二，如步骤204b中所述，若插件将从服务器获取到的第一简略信息和第二简略信息存入缓存中，那么插件发送给客户端的通知消息中可以携带有第一简略信息以及第二简略信息的缓存地址，此时客户端从通知消息中读取第一简略信息并展示，在展示第一简略信息之后，根据缓存地址获取第二简略信息并展示。
步骤403，判断是否接收到用户对选项所做的操作。若是，执行步骤405；否则，执行步骤404。
步骤404，在展示第一简略信息之后，在第二展示位上展示第二简略信息。当接收到用户对第二简略信息所做的操作时，进一步执行步骤405。
步骤405，向服务器发送媒体文件展示请求。
步骤406，接收服务器返回的该媒体文件的链接地址，根据链接地址获取该媒体文件并展示。
通过上述实例，在展示第一简略信息输出提示展示该媒体文件的选 项，然后展示第二简略信息，在这两个展示步骤中都配置了点击路径，供用户点击选项或者第二简略信息，从而进入落地页观看完整的媒体文件，能够满足用户在不同时刻对媒体文件的观看需求，并提高客户端的资源利用率。
图5为依据本申请一实例的媒体文件的展示方法的示例性流程图，该方法应用于安装于客户端内的插件。如图5所示，包括如下步骤：
步骤501，接收客户端发送的媒体信息获取请求。
步骤502，基于媒体信息获取请求，从服务器获取一媒体文件的第一简略信息和第二简略信息。
其中，插件向服务器请求获取简略信息的方式，根据以下两种情况，获取的次数有所不同。具体而言，
情况一，客户端每次被启动时，所展示的第一简略信息不同
此时，插件每接收到媒体信息获取请求，都向服务器请求获得一媒体文件的第一简略信息和第二简略信息。
情况二，客户端每次被启动时，所展示的第一简略信息相同
此时，插件向服务器请求获取简略信息，仅发生在客户端被首次启动的情况。具体而言，当客户端被安装于终端设备后，用户首次启动客户端时，客户端第一次向插件发送该媒体信息获取请求，插件向服务器请获取一媒体文件的第一简略信息和第二简略信息，同时插件可以向客户端返回无媒体信息可展示的指令，例如，通知客户端继续无闪屏广告的启动流程。并且，插件将获取到的第一简略信息和第二简略信息存入缓存中。这样，当客户端后续被启动、向插件发送媒体信息获取请求时，插件从缓存中读取之前存入的简略信息即可。
此外，插件向服务器请求获取简略信息的途径也可以有如下两种方式：
方式一，插件可以从服务器直接获取第一简略信息和第二简略信息。
方式二，插件从服务器接收第一简略信息的链接地址和第二简略信息的链接地址，这两种简略信息的链接地址可以为URL地址。然后，根据第一简略信息的链接地址从服务器拉取第一简略信息，根据第二简略信息的链接地址从服务器拉取第二简略信息。
步骤503，向客户端发送针对该媒体文件的通知消息。
这样，客户端根据通知消息在第一展示位上展示第一简略信息，之后，在第二展示位上展示第二简略信息，响应于用户对第二简略信息所做的操作，向服务器发送媒体文件展示请求，接收服务器返回的该媒体文件的链接地址，根据链接地址获取该媒体文件并展示。
根据本实例，插件在客户端和服务器之间传递信息，将第一简略信息和第二简略信息从服务器请求到，再传递给客户端进行显示，使得该插件可以和多种客户端进行联合处理，减轻了客户端对简略信息的获取过程，提高了客户端的资源利用率。
图6为依据本申请另一实例的媒体文件的展示方法的示例性流程图，该方法应用于安装于客户端内的插件。如图6所示，包括如下步骤：
步骤601，接收客户端发送的媒体信息获取请求。
步骤602，基于媒体信息获取请求，从服务器获取一媒体文件的第一简略信息、第一展示时长、第二简略信息和第二展示时长，并将第一简略信息和第二简略信息存入缓存中。
步骤603，从缓存中读取第一简略信息和第二简略信息，生成通知消息，并向客户端发送针对该通知消息。
在一些实例中，通知消息携带有第一简略信息以及第二简略信息的缓存地址，以使客户端从通知消息中读取第一简略信息并展示，之后， 根据缓存地址获取第二简略信息并展示。此外，在通知消息中携带有第一展示时长和第二展示时长，以使客户端根据第一展示时长展示第一简略信息，以及根据第二展示时长展示第二简略信息。
图7为依据本申请一实例的媒体文件的展示方法的交互流程图，包括客户端、插件和服务器之间的交互。具体包括如下步骤：
步骤701，客户端首次被启动时，向插件发送媒体信息获取请求。
步骤702，插件向客户端返回无媒体信息可展示的指令。
步骤703，插件向服务器发送媒体信息获取请求。
其中，插件可以先执行步骤703，再执行步骤702。
步骤704，服务器向插件返回第一简略信息、第一展示时长、第二简略信息和第二展示时长。
具体实现时，客户端向插件请求一闪屏广告，此时插件在本地并没有缓存的广告订单，那么一方面，插件向客户端返回无媒体信息可展示的指令，即告知客户端无闪屏广告，直接进入主界面；另一方面，插件向服务器拉取闪屏广告的订单，从中取出订单信息，即第一简略信息(即闪屏广告)的链接地址及展示时长、第二简略信息(即闪屏广告回收位)的链接地址及展示时长。
步骤705，插件将第一简略信息和第二简略信息存入缓存中。
步骤706，客户端后续被启动时，再向插件发送媒体信息获取请求。
步骤707，插件从缓存中读取第一简略信息和第二简略信息，生成获取媒体信息的通知消息。
通知消息携带有第一简略信息、第一展示时长、第二简略信息的缓存地址和第二展示时长。其中，第一简略信息和第一展示时长可以用于客户端直接展示；二简略信息的缓存地址则用于客户端获取该第二简略信息。
步骤708，插件向客户端发送获取媒体信息的通知消息。
步骤709，客户端根据第一展示时长在第一展示位展示第一简略信息，并输出提示展示该媒体文件的选项。
步骤710，在展示第一简略信息期间，客户端判断是否接收到用户对选项所做的操作。若是，执行步骤711；否则，执行步骤714。
步骤711，客户端向服务器发送媒体文件获取请求。
步骤712，服务器向客户端返回该媒体文件的链接地址。
步骤713，客户端根据链接地址获取该媒体文件并展示。
所展示的媒体文件包括全屏大图、视频、多个缩略图、二维码等。
步骤714，在展示第一简略信息之后，客户端根据第二展示时长在第二展示位展示第二简略信息。
具体实现时，闪屏广告结束后，在客户端的主界面上，通过状态栏中的条幅广告位展示第二简略信息。
然后，响应于用户针对第二简略信息所做的操作，客户端进而执行步骤711-713。当接收到用户扫描二维码的操作时，执行步骤715。
步骤715，客户端向服务器发送扫描操作指示。
步骤716，服务器根据接收到的扫描操作指示，统计扫描次数。
这些次数数据可以用于向广告主收费，例如可以采用预先付费的方式，按照每千人成本(CPM)方式售卖。
图8为依据本申请一实例的客户端800的结构示意图。如图8所示，客户端800包括：
发送模块810，用于向安装于客户端内的插件发送媒体信息获取请求，以使插件基于媒体信息获取请求，从服务器获取一媒体文件的第一简略信息和第二简略信息；
接收模块820，用于从插件接收针对该媒体文件的通知消息；
展示模块830，用于根据接收模块820接收的通知消息，在第一展示位上展示第一简略信息，之后，在第二展示位上展示第二简略信息；其中，当收到用户对所述第二简略信息的操作时，获取该媒体文件并展示。
在一些实例中，通知消息携带有第一简略信息以及第二简略信息的缓存地址；展示模块830用于，从通知消息中读取第一简略信息并展示，并在展示第一简略信息之后，根据缓存地址获取第二简略信息并展示。
在一些实例中，通知消息包括第一简略信息的第一展示时长和第二简略信息的第二展示时长；展示模块830用于，根据第一展示时长展示第一简略信息，根据第二展示时长展示第二简略信息。
在一些实例中，展示模块830进一步用于，在展示第一简略信息时，在第一展示位上以浮层的方式输出提示展示该媒体文件的选项；其中，若接收到用户对选项所做的操作，则令展示模块830获取媒体文件并展示，不再展示第二简略信息；若未接收到用户对选项所做的操作，则在展示第一简略信息之后，在第二展示位上展示第二简略信息。
在一些实例中，第一展示位为客户端的全屏界面，展示模块830用于，当客户端被启动时，在全屏界面上展示第一简略信息；从插件接收第二展示位的设置信息，根据设置信息在客户端的主界面上确定第二展示位。
图9为依据本申请另一实例的客户端900的结构示意图。该客户端900可包括：处理器910、存储器920、端口930以及总线940。处理器910和存储器920通过总线940互联。处理器910可通过端口930接收和发送数据。其中，
处理器910用于执行存储器920存储的机器可读指令模块。
存储器920存储有处理器910可执行的机器可读指令模块。处理器 910可执行的指令模块包括：发送模块921、接收模块922和展示模块923。其中，
发送模块921被处理器910执行时可以为：向安装于客户端内的插件发送媒体信息获取请求，以使插件基于媒体信息获取请求，从服务器获取一媒体文件的第一简略信息和第二简略信息；
接收模块922被处理器910执行时可以为：从插件接收针对该媒体文件的通知消息；
展示模块923被处理器910执行时可以为：根据接收模块922接收的通知消息，在第一展示位上展示第一简略信息，之后，在第二展示位上展示第二简略信息；其中，当收到用户对所述第二简略信息的操作时，获取该媒体文件并展示。
由此可以看出，当存储在存储器920中的指令模块被处理器910执行时，可实现前述各个实例中发送模块、接收模块和展示模块的各种功能。
图10为依据本申请一实例的插件1000的结构示意图。如图10所示，插件1000包括：
接收模块1010，用于接收客户端发送的媒体信息获取请求；
获取模块1020，用于基于接收模块1010接收的媒体信息获取请求，从服务器获取一媒体文件的第一简略信息和第二简略信息；及，
发送模块1030，用于向客户端发送针对该媒体文件的通知消息，以使客户端根据通知消息在第一展示位上展示第一简略信息，之后，在第二展示位上展示第二简略信息，其中，当收到用户对所述第二简略信息的操作时，获取该媒体文件并展示。
在一些实例中，获取模块1020用于，从服务器接收第一简略信息的链接地址和第二简略信息的链接地址；根据第一简略信息的链接地址 从服务器拉取第一简略信息；根据第二简略信息的链接地址从服务器拉取第二简略信息。
在一些实例中，获取模块1020进一步用于，从服务器获取第一简略信息的第一展示时长和第二简略信息的第二展示时长，其中，在发送模块1030发送的通知消息中携带有第一展示时长和第二展示时长，以使客户端根据第一展示时长展示第一简略信息，以及根据第二展示时长展示第二简略信息。
在一些实例中，插件1000进一步包括存储模块1040。其中，
存储模块1040，用于将第一简略信息和第二简略信息存入缓存中；
发送模块1030用于，从缓存中读取第一简略信息和第二简略信息，并生成通知消息。
图11为依据本申请另一实例的插件1100的结构示意图。该服务器1100可包括：处理器1110、存储器1120、端口1130以及总线1140。处理器1110和存储器1120通过总线1140互联。处理器1110可通过端口1130接收和发送数据。其中，
处理器1110用于执行存储器1120存储的机器可读指令模块。
存储器1120存储有处理器1110可执行的机器可读指令模块。处理器1110可执行的指令模块包括：接收模块1121、获取模块1122和发送模块1123。其中，
接收模块1121被处理器1110执行时可以为：接收客户端发送的媒体信息获取请求；
获取模块1122被处理器1110执行时可以为：基于接收模块1121接收的媒体信息获取请求，从服务器获取一媒体文件的第一简略信息和第二简略信息；
发送模块1123被处理器1110执行时可以为：向客户端发送针对该 媒体文件的通知消息，以使客户端根据通知消息在第一展示位上展示第一简略信息，之后，在第二展示位上展示第二简略信息，其中，当收到用户对所述第二简略信息的操作时，获取该媒体文件并展示。
在一些实例中，指令模块还包括：存储模块1124。在一些实例中，
存储模块1124被处理器1110执行时可以为：将第一简略信息和第二简略信息存入缓存中；
发送模块1123被处理器1110执行时可以为：从缓存中读取第一简略信息和第二简略信息，并生成通知消息。
由此可以看出，当存储在存储器1120中的指令模块被处理器1110执行时，可实现前述各个实例中接收模块、获取模块、发送模块和存储模块的各种功能。
图12为依据本申请一实例的媒体文件的展示系统1200的组成示意图。其中，媒体文件的展示系统1200包括：客户端1210、插件1220及服务器1230，其中，
客户端1210，用于向插件1220发送媒体信息获取请求；从插件1220接收针对一媒体文件的通知消息，根据通知消息在第一展示位上展示第一简略信息，之后，在第二展示位上展示第二简略信息；其中，当收到用户对所述第二简略信息的操作时，获取该媒体文件并展示
插件1220，用于接收客户端1210发送的媒体信息获取请求；基于媒体信息获取请求，从服务器1230获取该媒体文件的第一简略信息和第二简略信息；及，向客户端1210发送通知消息。
其中，客户端1210可以包括图8所示的各个模块，插件1220可以包括图10所示的各个模块。
以下仅对涉及客户端1210、插件1220及服务器1230之间交互的操作进行说明，具体如下：
客户端1210的发送模块810向插件1220的接收模块1010发送媒体信息获取请求；
插件1220的发送模块1030向服务器1230发送媒体信息获取请求，插件1220的接收模块1010从服务器1230获取该媒体文件的第一简略信息和第二简略信息；
插件1220的发送模块1030向客户端1210的接收模块820发送通知消息；
响应于用户对第二简略信息所做的操作，客户端1210的发送模块810向服务器1230发送媒体文件展示请求；
客户端1210的接收模块820接收服务器1230返回的该媒体文件的链接地址。
上述装置和系统实例中，各个模块及单元实现自身功能的具体方法在方法实例中均有描述，这里不再赘述。
另外，在本申请各个实例中的各功能模块可以集成在一个处理单元中，也可以是各个模块单独物理存在，也可以两个或两个以上模块集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
另外，本申请的每一个实例可以通过由数据处理设备如计算机执行的数据处理程序来实现。显然，数据处理程序构成了本申请。此外，通常存储在一个存储介质中的数据处理程序通过直接将程序读取出存储介质或者通过将程序安装或复制到数据处理设备的存储设备(如硬盘和或内存)中执行。因此，这样的存储介质也构成了本申请。存储介质可以使用任何类型的记录方式，例如纸张存储介质(如纸带等)、磁存储介质(如软盘、硬盘、闪存等)、光存储介质(如CD-ROM等)、磁光存储介质(如MO等)等。
因此，本申请还公开了一种存储介质，其中存储有数据处理程序，该数据处理程序用于执行本申请上述方法的任何一种实例。
以上所述仅为本申请的较佳实例而已，并不用以限制本申请，凡在本申请的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本申请保护的范围之内。

Claims (18)

  1. 一种媒体文件的展示方法，应用于客户端，所述方法包括：
    向安装于所述客户端内的插件发送媒体信息获取请求，以使所述插件基于所述媒体信息获取请求，从所述服务器获取一媒体文件的第一简略信息和第二简略信息；
    从所述插件接收针对该媒体文件的通知消息，根据所述通知消息在第一展示位上展示所述第一简略信息，之后，在第二展示位上展示所述第二简略信息；
    其中，当收到用户对所述第二简略信息的操作时，获取该媒体文件并展示。
  2. 根据权利要求1所述的方法，其中，所述通知消息携带有所述第一简略信息以及所述第二简略信息的缓存地址；
    所述展示所述第一简略信息包括：
    从所述通知消息中读取所述第一简略信息并展示；
    所述展示所述第二简略信息包括：
    在展示所述第一简略信息之后，根据所述缓存地址获取所述第二简略信息并展示。
  3. 根据权利要求1所述的方法，其中，所述通知消息包括所述第一简略信息的第一展示时长和所述第二简略信息的第二展示时长；
    所述展示所述第一简略信息包括：
    根据所述第一展示时长展示所述第一简略信息；
    所述展示所述第二简略信息包括：
    根据所述第二展示时长展示所述第二简略信息。
  4. 根据权利要求1所述的方法，进一步包括：
    在展示所述第一简略信息时，在所述第一展示位上以浮层的方式输出提示展示该媒体文件的选项；
    其中，若接收到用户对所述选项所做的操作，则获取所述媒体文件并展示，不再展示所述第二简略信息；若未接收到用户对所述选项所做的操作，则在展示所述第一简略信息之后，在所述第二展示位上展示所述第二简略信息。
  5. 根据权利要求1至4中任一项所述的方法，其中，所述第一展示位为所述客户端的全屏界面，所述在第一展示位上展示所述第一简略信息包括：
    当所述客户端被启动时，在所述全屏界面上展示所述第一简略信息；
    所述在第二展示位上展示所述第二简略信息包括：
    从所述插件接收所述第二展示位的设置信息，根据所述设置信息在所述客户端的主界面上确定所述第二展示位。
  6. 一种媒体文件的展示方法，应用于安装于客户端内的插件，所述方法包括：
    接收所述客户端发送的媒体信息获取请求；
    基于所述媒体信息获取请求，从服务器获取一媒体文件的第一简略信息和第二简略信息；及，
    向所述客户端发送针对该媒体文件的通知消息，以使所述客户端根据所述通知消息在第一展示位上展示所述第一简略信息，之后，在第二展示位上展示所述第二简略信息，其中，当收到用户对所述第二简略信息的操作时，获取该媒体文件并展示。
  7. 根据权利要求6所述的方法，进一步包括：
    将所述第一简略信息和所述第二简略信息存入缓存中；
    所述向所述客户端发送针对该媒体文件的通知消息包括：
    从缓存中读取所述第一简略信息和所述第二简略信息，并生成所述通知消息。
  8. 根据权利要求7所述的方法，其中，所述通知消息携带有所述第一简略信息以及所述第二简略信息的缓存地址，以使所述客户端从所述通知消息中读取所述第一简略信息并展示，之后，根据所述缓存地址获取所述第二简略信息并展示。
  9. 根据权利要求6所述的方法，其中，所述从服务器获取一媒体文件的第一简略信息和第二简略信息包括：
    从所述服务器接收所述第一简略信息的链接地址和所述第二简略信息的链接地址；
    根据所述第一简略信息的链接地址从所述服务器拉取所述第一简略信息；
    根据所述第二简略信息的链接地址从所述服务器拉取所述第二简略信息。
  10. 一种客户端，包括：
    发送模块，用于向安装于所述客户端内的插件发送媒体信息获取请求，以使所述插件基于所述媒体信息获取请求，从所述服务器获取一媒体文件的第一简略信息和第二简略信息；
    接收模块，用于从所述插件接收针对该媒体文件的通知消息；
    展示模块，用于根据所述接收模块接收的通知消息，在第一展示位上展示所述第一简略信息，之后，在第二展示位上展示所述第二简略信息；其中，当收到用户对所述第二简略信息的操作时，获取该媒体文件 并展示。
  11. 根据权利要求10所述的客户端，其中，所述通知消息携带有所述第一简略信息以及所述第二简略信息的缓存地址；
    所述展示模块用于，从所述通知消息中读取所述第一简略信息并展示，并在展示所述第一简略信息之后，根据所述缓存地址获取所述第二简略信息并展示。
  12. 根据权利要求10所述的客户端，其中，所述通知消息包括所述第一简略信息的第一展示时长和所述第二简略信息的第二展示时长；
    所述展示模块用于，根据所述第一展示时长展示所述第一简略信息，根据所述第二展示时长展示所述第二简略信息。
  13. 根据权利要求10所述的客户端，其中，所述展示模块进一步用于，在展示所述第一简略信息时，在所述第一展示位上以浮层的方式输出提示展示该媒体文件的选项；其中，若接收到用户对所述选项所做的操作，则令所述展示模块获取所述媒体文件并展示，不再展示所述第二简略信息；若未接收到用户对所述选项所做的操作，则在展示所述第一简略信息之后，在所述第二展示位上展示所述第二简略信息。
  14. 根据权利要求10至13中任一项所述的客户端，其中，所述第一展示位为所述客户端的全屏界面，所述展示模块用于，当所述客户端被启动时，在所述全屏界面上展示所述第一简略信息；从所述插件接收所述第二展示位的设置信息，根据所述设置信息在所述客户端的主界面上确定所述第二展示位。
  15. 一种插件，所述插件安装于客户端内，包括：
    接收模块，用于接收所述客户端发送的媒体信息获取请求；
    获取模块，用于基于所述接收模块接收的媒体信息获取请求，从服务器获取一媒体文件的第一简略信息和第二简略信息；及，
    发送模块，用于向所述客户端发送针对该媒体文件的通知消息，以使所述客户端根据所述通知消息在第一展示位上展示所述第一简略信息，之后，在第二展示位上展示所述第二简略信息，其中，当收到用户对所述第二简略信息的操作时，获取该媒体文件并展示。
  16. 根据权利要求15所述的插件，进一步包括：
    存储模块，用于将所述第一简略信息和所述第二简略信息存入缓存中；
    所述发送模块用于，从缓存中读取所述第一简略信息和所述第二简略信息，并生成所述通知消息。
  17. 根据权利要求15所述的插件，其中，所述获取模块用于，从所述服务器接收所述第一简略信息的链接地址和所述第二简略信息的链接地址；根据所述第一简略信息的链接地址从所述服务器拉取所述第一简略信息；根据所述第二简略信息的链接地址从所述服务器拉取所述第二简略信息。
  18. 一种非易失性计算机可读存储介质，存储有计算机可读指令，可以使至少一个处理器执行如权利要求1至9任一项所述的方法。
PCT/CN2017/083413 2016-05-06 2017-05-08 媒体文件的展示方法、客户端及插件 WO2017190709A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/982,249 US10754668B2 (en) 2016-05-06 2018-05-17 Media file presentation method, client application, and plug-in

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610298190.9A CN106059999B (zh) 2016-05-06 2016-05-06 一种媒体文件的展示方法、客户端、插件及系统
CN201610298190.9 2016-05-06

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/982,249 Continuation US10754668B2 (en) 2016-05-06 2018-05-17 Media file presentation method, client application, and plug-in

Publications (1)

Publication Number Publication Date
WO2017190709A1 true WO2017190709A1 (zh) 2017-11-09

Family

ID=57176865

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/083413 WO2017190709A1 (zh) 2016-05-06 2017-05-08 媒体文件的展示方法、客户端及插件

Country Status (3)

Country Link
US (1) US10754668B2 (zh)
CN (1) CN106059999B (zh)
WO (1) WO2017190709A1 (zh)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106059999B (zh) * 2016-05-06 2021-03-23 腾讯科技（北京）有限公司 一种媒体文件的展示方法、客户端、插件及系统
CN106303654B (zh) * 2016-08-16 2020-02-18 腾讯科技（北京）有限公司 一种媒体信息的展示方法、客户端、插件及系统
CN108121748B (zh) * 2016-11-30 2020-08-28 腾讯科技（北京）有限公司 提供媒体推送的方法和装置
CN107071504B (zh) * 2017-03-02 2020-08-11 北京潘达互娱科技有限公司 闪屏内容处理方法及装置
CN106959798A (zh) * 2017-03-28 2017-07-18 联想(北京)有限公司 一种动态消息的显示控制方法和电子设备
CN109144444B (zh) * 2018-07-24 2021-11-05 深圳微盐传媒科技有限公司 一种人物信息展示方法和装置
CN110798711B (zh) * 2018-08-01 2022-07-08 腾讯科技（深圳）有限公司 广告信息处理方法、装置、计算机设备和存储介质
CN109672901A (zh) * 2018-12-25 2019-04-23 北京潘达互娱科技有限公司 一种视频展现方法和移动终端
CN110442350B (zh) * 2019-06-15 2022-12-30 深圳市江波龙电子股份有限公司 一种SPI flash烧录器
CN111427650A (zh) * 2020-03-24 2020-07-17 上海连尚网络科技有限公司 一种用于提供呈现信息的方法与设备
CN114500731A (zh) * 2020-10-27 2022-05-13 华为技术有限公司 一种广告显示方法及电子设备
CN112689162B (zh) * 2020-11-30 2023-04-11 当趣网络科技(杭州)有限公司 推送处理方法、系统、电子设备及介质
CN112511909B (zh) * 2020-11-30 2023-04-11 当趣网络科技(杭州)有限公司 开机推送处理方法、系统、电子设备及介质
CN112616075B (zh) * 2020-11-30 2023-04-11 当趣网络科技(杭州)有限公司 基于智能电视的推送处理方法、系统、电子设备及介质
CN112817850A (zh) * 2021-01-28 2021-05-18 北京达佳互联信息技术有限公司 信息处理方法、装置、系统、电子设备及存储介质
CN113656093A (zh) * 2021-08-02 2021-11-16 珠海格力电器股份有限公司 插件配置方法、装置、设备及存储介质
CN114422637B (zh) * 2021-12-20 2023-12-29 阿里巴巴（中国）有限公司 媒体请求处理方法和跨平台引擎系统

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080092071A1 (en) * 2006-10-14 2008-04-17 Fu-Sheng Chiu Automatically collapsing advertising module
CN103297841A (zh) * 2012-03-02 2013-09-11 北京四达时代软件技术股份有限公司 数字机顶盒展示广告的方法及装置
CN104023271A (zh) * 2014-02-26 2014-09-03 华为技术有限公司 广告信息推送方法和用户设备
CN104166931A (zh) * 2014-08-21 2014-11-26 广州华多网络科技有限公司 一种广告信息展示方法及客户端
CN104462535A (zh) * 2014-12-24 2015-03-25 北京奇艺世纪科技有限公司 一种推送信息展示方法及装置
CN104703014A (zh) * 2013-12-10 2015-06-10 腾讯科技（北京）有限公司 一种视频播放方法、装置和系统
CN105472033A (zh) * 2015-12-31 2016-04-06 腾讯科技（深圳）有限公司 媒体信息处理方法及移动终端
CN106059999A (zh) * 2016-05-06 2016-10-26 腾讯科技（北京）有限公司 一种媒体文件的展示方法、客户端、插件及系统

Family Cites Families (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999004561A1 (en) * 1997-07-21 1999-01-28 E-Guide, Inc. Systems and methods for displaying and recording control interfaces
US6279036B1 (en) * 1998-05-15 2001-08-21 International Business Machines Corporation Method and apparatus for detecting actual viewing or electronic advertisements
US6563515B1 (en) * 1998-05-19 2003-05-13 United Video Properties, Inc. Program guide system with video window browsing
US6188398B1 (en) * 1999-06-02 2001-02-13 Mark Collins-Rector Targeting advertising using web pages with video
US20030028622A1 (en) * 2001-08-06 2003-02-06 Mitsuhiro Inoue License management server, terminal device, license management system and usage restriction control method
GB0206090D0 (en) * 2002-03-15 2002-04-24 Koninkl Philips Electronics Nv Previewing documents on a computer system
US20060212347A1 (en) * 2005-03-15 2006-09-21 1000 Oaks Hu Lian Technology Development Co., Ltd. System and method for advertisement delivery in a network system
US8060824B2 (en) * 2007-01-05 2011-11-15 Starz Entertainment Llc User interface for a multimedia service
KR101386882B1 (ko) * 2007-06-08 2014-04-18 삼성전자주식회사 디지털 방송 채널 정보 표시 방법 및 장치
US9843774B2 (en) * 2007-10-17 2017-12-12 Excalibur Ip, Llc System and method for implementing an ad management system for an extensible media player
US9594900B2 (en) * 2008-12-09 2017-03-14 Microsoft Technology Licensing, Llc Isolating applications hosted by plug-in code
US9264759B2 (en) * 2009-11-17 2016-02-16 Lg Electronics Inc. Method for transmitting and receiving broadcast signals, and broadcast reception device using said method
US20110191151A1 (en) * 2010-02-01 2011-08-04 Rodney Boyd Rosa System for serving advertisements that allows compensation for user viewing
US20150161277A1 (en) * 2011-03-14 2015-06-11 Browsium, Inc. Methods and systems for one browser version to use a rendering engine of another browser version for displaying information
US9135371B2 (en) * 2011-05-09 2015-09-15 Google Inc. Contextual video browsing
US8732579B2 (en) * 2011-09-23 2014-05-20 Klip, Inc. Rapid preview of remote video content
CN102833186B (zh) * 2012-08-27 2014-06-04 腾讯科技（深圳）有限公司 信息传输方法、装置、系统及终端
CN104049986B (zh) * 2013-03-14 2018-12-18 腾讯科技（深圳）有限公司 插件加载方法及装置
US20140282014A1 (en) * 2013-03-14 2014-09-18 Apple Inc. Presenting snapshots of plug-in content in user interfaces
EP3001692A4 (en) * 2013-07-02 2016-06-08 Huawei Tech Co Ltd METHOD, APPARATUS AND SYSTEM FOR PROCESSING MULTIMEDIA STREAMS
CN104301779B (zh) * 2013-07-16 2018-10-26 腾讯科技（深圳）有限公司 一种视频文件的播放方法、系统和装置
CN103458397B (zh) * 2013-08-26 2017-12-15 华为技术有限公司 广告处理方法及装置
CN103793244A (zh) * 2013-12-26 2014-05-14 百度在线网络技术（北京）有限公司 在启动页面显示信息的方法及装置
CN103870121B (zh) * 2014-02-24 2017-06-27 联想(北京)有限公司 一种信息处理方法及电子设备
US10579248B2 (en) * 2014-10-27 2020-03-03 Samsung Electronics Co., Ltd. Method and device for displaying image by using scroll bar
CN104615432B (zh) * 2015-02-10 2020-06-16 腾讯科技（北京）有限公司 闪屏信息处理方法及客户端
CN105094520B (zh) * 2015-05-18 2018-11-16 努比亚技术有限公司 一种显示方法及终端
CN104932888B (zh) * 2015-06-12 2019-01-15 联想(北京)有限公司 一种信息处理方法及装置
CN105046525A (zh) * 2015-06-30 2015-11-11 腾讯科技（北京）有限公司 广告投放系统、装置及方法
CN105117187B (zh) * 2015-08-13 2018-04-24 小米科技有限责任公司 多媒体信息展示方法和装置

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080092071A1 (en) * 2006-10-14 2008-04-17 Fu-Sheng Chiu Automatically collapsing advertising module
CN103297841A (zh) * 2012-03-02 2013-09-11 北京四达时代软件技术股份有限公司 数字机顶盒展示广告的方法及装置
CN104703014A (zh) * 2013-12-10 2015-06-10 腾讯科技（北京）有限公司 一种视频播放方法、装置和系统
CN104023271A (zh) * 2014-02-26 2014-09-03 华为技术有限公司 广告信息推送方法和用户设备
CN104166931A (zh) * 2014-08-21 2014-11-26 广州华多网络科技有限公司 一种广告信息展示方法及客户端
CN104462535A (zh) * 2014-12-24 2015-03-25 北京奇艺世纪科技有限公司 一种推送信息展示方法及装置
CN105472033A (zh) * 2015-12-31 2016-04-06 腾讯科技（深圳）有限公司 媒体信息处理方法及移动终端
CN106059999A (zh) * 2016-05-06 2016-10-26 腾讯科技（北京）有限公司 一种媒体文件的展示方法、客户端、插件及系统

Also Published As

Publication number Publication date
US20180267815A1 (en) 2018-09-20
CN106059999B (zh) 2021-03-23
US10754668B2 (en) 2020-08-25
CN106059999A (zh) 2016-10-26

Similar Documents

Publication Publication Date Title
WO2017190709A1 (zh) 媒体文件的展示方法、客户端及插件
US11677806B2 (en) Platform-independent content generation for thin client applications
US10326715B2 (en) System and method for updating information in an instant messaging application
US11463540B2 (en) Relevant secondary-device content generation based on associated internet protocol addressing
US11503356B2 (en) Intelligent multi-device content distribution based on internet protocol addressing
US20140279075A1 (en) Interactive advertising
WO2018032923A1 (zh) 一种媒体信息的展示方法、客户端、插件及系统
CN107529082B (zh) 使用共用和个人装置来提供个性化用户功能的方法和设备
US9015179B2 (en) Media content tags
WO2018107719A1 (zh) 数据分享方法、装置、终端设备和服务器
CN103546813A (zh) 基于Android平台的视频预览方法及智能电视
CN113157157A (zh) 基于直播的互动图像管理方法、装置、设备和存储介质
US20190014063A1 (en) System and Methods for Dynamically Generating Animated GIF Files for Delivery Via the Network
WO2014176896A1 (en) System and method for updating information in an instant messaging application
US20170070784A1 (en) Interactive content generation for thin client applications
CN114679621A (zh) 一种视频展示方法、装置及终端设备
US9940645B1 (en) Application installation using in-video programming
US10075485B2 (en) Animated snapshots
CN113784194A (zh) 一种视频播放器的嵌入方法和装置
JP2018022298A (ja) 配信装置、配信方法、配信プログラム及び情報表示プログラム
CN110198455B (zh) 内容推送监测方法、装置及存储介质
US11645680B2 (en) Method and system for distributing electronic publishing content

Legal Events

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

Ref country code: DE

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

Ref document number: 17792535

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17792535

Country of ref document: EP

Kind code of ref document: A1