WO2018103484A1 - 直播页面的数据处理方法、装置和系统 - Google Patents

直播页面的数据处理方法、装置和系统 Download PDF

Info

Publication number
WO2018103484A1
WO2018103484A1 PCT/CN2017/109611 CN2017109611W WO2018103484A1 WO 2018103484 A1 WO2018103484 A1 WO 2018103484A1 CN 2017109611 W CN2017109611 W CN 2017109611W WO 2018103484 A1 WO2018103484 A1 WO 2018103484A1
Authority
WO
WIPO (PCT)
Prior art keywords
page
scenario
live broadcast
scene
configuration information
Prior art date
Application number
PCT/CN2017/109611
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 WO2018103484A1 publication Critical patent/WO2018103484A1/zh
Priority to US16/282,015 priority Critical patent/US11025963B2/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/21Server components or server architectures
    • H04N21/218Source of audio or video content, e.g. local disk arrays
    • H04N21/2187Live feed
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/957Browsing optimisation, e.g. caching or content distillation
    • G06F16/9577Optimising the visualization of content, e.g. distillation of HTML documents
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/958Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/958Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
    • G06F16/986Document structures and storage, e.g. HTML extensions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/41Structure of client; Structure of client peripherals
    • H04N21/414Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance
    • H04N21/41407Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance embedded in a portable device, e.g. video client on a mobile phone, PDA, laptop
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/443OS processes, e.g. booting an STB, implementing a Java virtual machine in an STB or power management in an STB
    • H04N21/4438Window management, e.g. event handling following interaction with the user interface
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47End-user applications
    • H04N21/472End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content
    • H04N21/47202End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content for requesting content on demand, e.g. video on demand
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47End-user applications
    • H04N21/478Supplemental services, e.g. displaying phone caller identification, shopping application
    • H04N21/4782Web browsing, e.g. WebTV
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47End-user applications
    • H04N21/482End-user interface for program selection
    • H04N21/4825End-user interface for program selection using a list of items to be played back in a given order, e.g. playlists
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47End-user applications
    • H04N21/488Data services, e.g. news ticker
    • H04N21/4884Data services, e.g. news ticker for displaying subtitles

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a data processing method, apparatus, and system for a live broadcast page.
  • live broadcast clients As the live broadcast quickly became popular in the network, various live broadcast clients came into being. In addition to providing live viewing, these live broadcast clients can also provide various live rooms for live broadcast by the anchor; the pages on which the user views the live broadcast and the pages on which the anchor broadcasts can be collectively referred to as the live broadcast page.
  • live broadcast page On the live page, in addition to the live window, there are usually other operational portals, such as barrage, chat windows, and/or gift giving.
  • the embodiment of the present application provides a data processing method, device, and system for a live broadcast page, which can improve flexibility and efficiency.
  • the embodiment of the present application provides a data processing method for a live broadcast page, which is applied to a live broadcast server, and includes:
  • scenario configuration information corresponding to the scenario identifier; where the scenario configuration information is The corresponding relationship between the scene identifier and the corresponding function plug-in is included in the function;
  • the embodiment of the present application further provides a data processing apparatus for a live broadcast page, including:
  • a memory coupled to the processor; storing, in the memory, a machine readable instruction unit; the machine readable instruction unit comprising:
  • a receiving unit configured to receive a display request of a live broadcast page, where the display request carries a scene identifier, where the scene identifier is determined by the live broadcast client according to an operating environment thereof;
  • An acquiring unit configured to acquire scenario configuration information corresponding to the scenario identifier, where the scenario configuration information includes a correspondence between the scenario identifier and a corresponding function plug-in;
  • a loading unit configured to load a function plug-in corresponding to the scene identifier in a preset basic page according to the scenario configuration information, to obtain a target live broadcast page;
  • the display unit is configured to send the target live broadcast page to the live broadcast client for display.
  • the embodiment of the present application further provides a data processing system for a live broadcast page, including the data processing device of any live broadcast page provided by the embodiment of the present application.
  • the embodiment of the present application further provides a non-transitory computer readable storage medium, wherein the storage medium stores machine readable instructions, which are executable by a processor to complete the embodiments of the present application.
  • FIG. 1 is a schematic diagram of a data processing method of a live broadcast page according to an embodiment of the present application
  • FIG. 1b is a flowchart of a data processing method of a live broadcast page provided by an embodiment of the present application
  • 2a is a relationship diagram of components in a server provided by an embodiment of the present application.
  • 2b is another flowchart of a data processing method of a live broadcast page provided by an embodiment of the present application.
  • 2c is a diagram showing an example of a live broadcast page in a data processing method of a live broadcast page according to an embodiment of the present application
  • FIG. 3 is a schematic structural diagram of a data processing apparatus of a live broadcast page according to an embodiment of the present application.
  • FIG. 3b is another schematic structural diagram of a data processing apparatus of a live broadcast page according to an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a server provided by an embodiment of the present application.
  • FIG. 5 is another schematic structural diagram of a server according to an embodiment of the present application.
  • the embodiment of the present application provides a data processing method, apparatus, and system for a live broadcast page.
  • the data processing system of the live broadcast page may include any data processing device of the live broadcast page provided by the embodiment of the present application, and the data processing device of the live broadcast page may be integrated into a server or the like;
  • the data processing system may further include other devices, such as a terminal, and the terminal may be configured with a client corresponding to the data processing device of the live broadcast page, configured to obtain a target live broadcast page from the data processing device of the live broadcast page, and Show it.
  • the data processing apparatus of the live broadcast page is specifically integrated into the server 101 as an example.
  • the function module on the page can be divided into several independent version function plug-ins, and correspondingly set for different scenes.
  • the corresponding scene configuration information can be obtained according to the scene identifier carried in the display request, for example, the plug-in list is obtained, and then the corresponding function plug-in is loaded in the preset basic page according to the scene configuration information, and the target live broadcast is obtained.
  • the page is sent to the client in the corresponding terminal 102 for display, so that the function plug-in can be flexibly increased or decreased according to different scenario requirements to generate different live pages.
  • the data processing device of the live broadcast page may be integrated into a device such as a server.
  • a data processing method for a live broadcast page comprising: receiving a display request of a live broadcast page, where the display request carries a scene identifier, where the scene identifier is determined by the live broadcast client according to the running environment; and the scenario configuration corresponding to the scene identifier is obtained.
  • Information wherein the scene The configuration information includes a mapping between the scenario identifier and the corresponding function plug-in.
  • the function plug-in corresponding to the scenario identifier is loaded in the preset basic page according to the scenario configuration information, and the target live broadcast page is obtained.
  • the live broadcast page is sent to the live broadcast client for display.
  • the specific process of the data processing method of the live broadcast page may be as follows:
  • S101 Receive an impression request of a live broadcast page, where the display request carries a scene identifier.
  • the display request of the live broadcast page sent by the terminal or other device may be received, or the display request of the live broadcast page triggered by the local device (ie, the data processing device of the live broadcast page) may be received, and the like.
  • the local device ie, the data processing device of the live broadcast page
  • the scenario identifier is used to distinguish and identify different running environments of the live page, and may include information such as a name, a code, a number, and/or an icon of the scenario.
  • the runtime environment may refer to a type of application for opening the live page, such as WeChat, Weibo, QQ, browser, and the like.
  • a core component can be set to load and initialize other components and each plug-in, and manage its life cycle; thus, after receiving the display request of the live page, the core component can be passed.
  • the step of obtaining the scenario configuration information corresponding to the scenario identifier may be as follows:
  • the preset core component is loaded according to the display request, and the scenario configuration information corresponding to the scenario identifier is obtained by the core component.
  • the core component can extract the scene identifier from the display request, obtain the scene configuration information corresponding to the scene identifier, and the like.
  • a scene determination component and a scene configuration component may be separately configured.
  • the scene determination component is mainly used to distinguish different scenes
  • the scene configuration component is mainly used to provide scene configuration information corresponding to each scene.
  • the scenario component is loaded by the core component, and the scenario determination component extracts the scenario identifier from the display request, and loads the scenario configuration component, and obtains the scenario configuration information corresponding to the scenario identifier from the scenario configuration component.
  • the corresponding relationship between the scenario configuration information and the scenario identifier may be pre-stored in the data processing device of the live broadcast page, or may be established by the data processing device of the live broadcast page, that is, before the step of “receiving the display request of the live broadcast page”.
  • the data processing method of the live page may further include:
  • Obtaining a scene setting request the scene setting request carrying a scene identifier, acquiring a plurality of function plug-in information according to the scene setting request, receiving function plug-in information selected by the user from the plurality of function plug-in information, and generating a scene configuration according to the selected function plug-in information Information, and establish the corresponding relationship between the scenario configuration information and the scenario identifier.
  • the scenario configuration information includes at least one related information of the function plug-in to be loaded (referred to as function plug-in information in the embodiment of the present application); in specific implementation, the information format of the scenario configuration information may be For example, the text may be a list or a list. For the convenience of description, in the embodiment of the present application, the scenario configuration information is specifically described as an example of a plug-in list.
  • the function structure required by the corresponding function plug-in is rendered in the preset basic page, for example, as follows:
  • the user interface management component is invoked, and according to the scenario configuration information, the user interface management component renders the functional structure required by the corresponding function plug-in in the preset basic page, and the like.
  • the basic page refers to before loading the function plug-in provided by the embodiment of the present application.
  • the live broadcast page can be set according to the actual application requirements, and will not be described here.
  • the corresponding function plug-in is sequentially loaded, and the function plug-in is initialized to obtain a target live broadcast page.
  • the target live broadcast page may be sent to each client for display.
  • the target live broadcast page may be sent to the terminal to which the client belongs, so that the terminal Show the target live page on the screen, and more.
  • each function plug-in in the target live broadcast page can also respond to each event, that is, after the step “show the target live broadcast page”, the data processing method of the live broadcast page is further Can include:
  • the plug-in in the live broadcast page may be modified, for example, to be deleted or added, that is, after the step of displaying the target live broadcast page, the data processing method of the live broadcast page may further include:
  • the modification request indicating a function plug-in that needs to be deleted or added, and deleting or adding the function plug-in in the target live broadcast page according to the modification request.
  • the embodiment may obtain the scene configuration information corresponding to the scene identifier, and then load the corresponding function in the preset basic page according to the scene configuration information.
  • the plug-in obtains the target live page and displays the target live page; since the solution can flexibly load different function plug-ins according to different scene requirements to generate different live pages, therefore, compared with the existing ones, In terms of hard coded way to achieve page differentiation, not only is it simpler and more flexible, but it also saves development time and improves processing efficiency.
  • the data processing device of the live broadcast page is specifically integrated into the server, and the scenario configuration information is specifically a plug-in list as an example for description.
  • the “live function” corresponds to the live function plug-in
  • the “bar-play interaction” corresponds to the barrage interactive plug-in.
  • Gift giving bonus plugin "live count” corresponds to the live count plugin, and so on.
  • the corresponding scene identifiers are set for different scenarios, and the association relationship between each scene identifier and each plug-in information is established, and the plug-in list is established according to the association relationship; thus, when the server receives the display request of the live page, The corresponding plug-in list may be obtained according to the scenario identifier carried in the display request, and then the corresponding function plug-in is loaded in the preset basic page based on the plug-in list to obtain the target live broadcast page and display.
  • the server may include multiple modules, such as the core component 201, the scene determination component 202, the scene configuration component 203, and the event.
  • the core component 201 is used for loading and initializing other components and each plug-in, and managing its life cycle; for example, the core component can be used to load the scene judgment component, the scene configuration component, the event engine, and the user interface management. Components, as well as individual feature plugins, and more.
  • the scene judging component 202 is configured to distinguish different scenes.
  • the scene identifier may be extracted from the display request, and the current scene may be determined according to the scene identifier.
  • the scenario configuration component 203 is configured to provide a plug-in list (ie, scenario configuration information) corresponding to each scenario. For example, after the scenario determination component extracts the scenario identifier, the scenario configuration component provides a plug-in list corresponding to the scenario identifier.
  • a plug-in list ie, scenario configuration information
  • the event engine 204 is configured to acquire an event processing request triggered by the target live page, determine an event to be processed according to the event processing request, and invoke a corresponding function plug-in to process the event.
  • the user interface management component 205 is configured to render a function structure required by the corresponding function plug-in in the preset basic page, sequentially load the corresponding function plug-in according to the function structure, and initialize the function plug-in to obtain a target live broadcast page.
  • the function plug-in 206 respectively corresponds to the function modules on the live broadcast page, such as the barrage interaction, the gift-giving reward, and the live broadcast count, etc., after the function plug-in is called, the corresponding event can be processed.
  • a data processing method for a live page can be as follows:
  • the server receives a display request of a live broadcast page, where the display request carries a scene identifier.
  • the scenario identifier is used to distinguish and identify different running environments of the live page, and may include information such as a name, a code, a number, and/or an icon of the scenario.
  • the runtime environment may refer to a type of application for opening the live page, such as WeChat, Weibo, QQ, browser, and the like.
  • the server loads the preset core component according to the display request, and initializes the core component, and then performs step S203.
  • the core component loads the scenario determining component, and uses the scenario determining component to extract the scenario identifier from the display request, and then performs step S204.
  • the core component loads the scenario configuration component, obtains a plug-in list corresponding to the scenario identifier from the scenario configuration component, and then performs step S205.
  • the scenario configuration component includes two plug-in lists as an example, wherein the plug-in list 1 includes information of a live function plug-in and information of a barrage interactive plug-in, and the plug-in list 2 includes information of a live function plug-in, and a barrage interactive plug-in.
  • Information and gifts to reward the plugin information then:
  • scenario ID of the scenario 1 is 001
  • the function plug-in to be loaded in the scenario includes a live function plug-in and a barrage interactive plug-in
  • the scenario identifier "001" can be obtained according to the scenario, and the plug-in list is obtained from the scenario configuration component. .
  • the component may be identified according to the scenario identifier “002”. Get the list of plugins 2, and so on.
  • the core component invokes a user interface management component, and according to the plug-in list, the user interface management component renders a functional structure required by the corresponding function plug-in in the preset basic page, and then performs step S206.
  • step S204 taking the example in step S204 as an example, if the function plug-ins to be loaded are “live play function plug-in” and “bar-play interactive plug-in”, then at this time, according to the plug-in list 1, the user interface management component can be pre- The function structure required for the "live function plug-in” and the "shadow interaction plug-in” is rendered in the basic page, and then step S206 is performed.
  • the user interface management component is preset in the The function structure required for the "live function plug-in”, the "barrage interactive plug-in” and the “gift-to-play plug-in” is rendered in the basic page, and then step S206 is performed, and so on.
  • the basic page refers to the live broadcast page before the function plug-in provided by the embodiment of the present application is loaded, and may be set according to the requirements of the actual application, and details are not described herein again.
  • the core component sequentially loads the corresponding function plug-in according to the functional structure, and initializes the function plug-in to obtain a target live broadcast page, and then performs step S207.
  • the "live function plug-in” and the “barrage interaction” may be sequentially loaded according to the functional structure.
  • Plugins and initialize these function plugins to get the target live page; for example, see Figure 2c, because in addition to loading the "live plugin", the "bounce interactive plugin” is also loaded, so at this target On the live page, the corresponding barrage interaction function can be provided, that is, the user can perform the barrage interaction by triggering the “bouncer interaction” button.
  • the function structure may be sequentially loaded according to the function structure. "Live Streaming Plugin”, “Barrage Interactive Plugin” and “Gift Gifts Plugin”, and initialize these feature plugins separately, and so on.
  • the server sends the target live broadcast page to the live broadcast client for display.
  • the target live broadcast page may be sent to each client for display.
  • the target live broadcast page may be sent to the terminal to which the client belongs, so that the terminal Show the target live page on the screen, and more.
  • each function plug-in in the target live broadcast page can also be used to respond to each event, that is, step S208 can also be performed, as follows:
  • the core component loads and initializes the event engine, distributes the event through the event engine, and invokes the corresponding function plug-in to process the event.
  • the specific information may be as follows:
  • the event engine obtains an event processing request triggered by the target live page, determines an event to be processed according to the event processing request, and triggers the core component to call a corresponding function plug-in, and processes the event through the called function plug-in.
  • the core component can be triggered to invoke the barrage interactive plug-in, the event is processed through the barrage interactive plug-in, and so on.
  • the plug-in in the target live page may also be modified, such as deleting or adding, that is, step S209 may also be performed, as follows:
  • the core component acquires a modification request triggered by the target live broadcast page, where the modification request indicates a function plug-in that needs to be modified, and the function plug-in in the target live broadcast page is modified according to the modification request, for example, deleting or adding.
  • a modification request for the target live page may be initiated, and then, according to the modification request, the "bounce" in the target live page is The interactive plugin is removed.
  • a “barcing interactive function” needs to be added to the target live broadcast page, at this time, a modification request for the target live broadcast page may be initiated, and then, according to the modification request, a corresponding “boom” is added to the target live broadcast page.
  • Screen interactive plugin and more.
  • steps S208 and S209 may be in no particular order, and details are not described herein again.
  • the present embodiment can obtain the plug-in list corresponding to the scene identifier by loading various components, and then, according to the plug-in list, the preset basic page. Loading the corresponding function plug-in, obtaining the target live page, and displaying the target live page; since the solution can flexibly load different function plug-ins according to different scene requirements to generate different live pages, therefore, relative to the existing In terms of the solution of page differentiation by means of hard code, not only is it simpler and more flexible, but also it can greatly save development time and improve processing efficiency.
  • the live broadcast page of the live client A can provide only the most basic live viewing capability, and the live broadcast page of the live client B can provide various interactive functions in addition to the live viewing function, and the like.
  • the embodiment of the present application further provides a data processing device for a live broadcast page, which is referred to as a data processing device.
  • the data processing device may include a receiving unit 301, an obtaining unit 302, and a loading unit.
  • 303 and display unit 304 are as follows:
  • the receiving unit 301 is configured to receive a display request of a live broadcast page, where the display request carries a scene identifier.
  • the scenario identifier is used to distinguish and identify different running environments of the live page, and may include information such as a name, a code, a number, and/or an icon of the scenario.
  • the runtime environment may refer to a type of application for opening the live page, such as WeChat, Weibo, QQ, browser, and the like.
  • the obtaining unit 302 is configured to acquire scene configuration information corresponding to the scene identifier.
  • the obtaining unit 302 may include a loading subunit and an obtaining subunit, as follows:
  • the loading subunit is configured to load a preset core component according to the display request.
  • the sub-unit is configured to obtain the scenario configuration information corresponding to the scenario identifier by using the core component.
  • the acquiring the sub-unit may be used to extract the scene identifier from the display request, obtain the scene configuration information corresponding to the scene identifier, and the like.
  • a scene determination component and a scene configuration component may also be separately configured to perform operations, namely:
  • the acquiring sub-unit may be configured to load the scene determining component by using the core component, and use the scene determining component to extract the scene identifier from the display request, and load the scene configuration component, and obtain the scene identifier from the scene configuration component. Corresponding scene configuration information.
  • the corresponding relationship between the scenario configuration information and the scenario identifier may be pre-stored in the data processing device of the live broadcast page, or may be established by the data processing device of the live broadcast page, that is, as shown in FIG. 3b, the data processing device further A setting unit 305 can be included as follows:
  • the setting unit 305 may be configured to obtain a scene setting request, where the scene setting request carries a scene identifier, obtains a plurality of function plug-in information according to the scene setting request, and receives function plug-in information selected by the user from the plurality of function plug-in information, according to the selection.
  • the function plug-in information generates scenario configuration information, and establishes a correspondence between the scenario configuration information and the scenario identifier.
  • the obtaining unit 302 is specifically configured to acquire the scenario configuration information corresponding to the scenario identifier based on the corresponding relationship between the scenario configuration information and the scenario identifier established by the setting unit 305.
  • the loading unit 303 is configured to load a corresponding function plug-in in the preset basic page according to the scenario configuration information to obtain a target live broadcast page.
  • the loading unit 303 can include a rendering subunit and a processing subunit, as follows:
  • the rendering subunit can be used to render the functional structure required by the corresponding function plugin in the preset basic page according to the scene configuration information.
  • the rendering sub-unit may be specifically configured to invoke a user interface management component, and according to the scenario configuration information, the user interface management component renders a functional structure required by the corresponding function plug-in in the preset basic page.
  • the basic page can be set according to the requirements of the actual application, and details are not described herein.
  • the processing sub-unit can be used to sequentially load the corresponding function plug-in according to the functional structure, and initialize the function plug-in to obtain the target live broadcast page.
  • the display unit 304 is configured to display the target live broadcast page.
  • the display unit 304 may also send the target live broadcast page to each client for display, for example, the target live broadcast page may be sent to the terminal to which the client belongs. So that the terminal displays the target live page on the screen, and so on.
  • each function plug-in in the target live broadcast page may also be used to respond to each event, that is, as shown in FIG. 3b, the data processing apparatus may further include an event processing unit 306, as follows: :
  • the event processing unit 306 can be configured to obtain an event processing request triggered by the target live broadcast page, determine an event to be processed according to the event processing request, and invoke a corresponding function plug-in to process the event by using a function plug-in.
  • the plug-in in the target live broadcast page may also be modified, such as deleting or adding. That is, as shown in FIG. 3b, the data processing apparatus may further include a modifying unit 307, as follows:
  • the modifying unit 307 may be configured to obtain a modification request triggered by the target live broadcast page, where the modification request indicates a function plug-in that needs to be deleted or added, and the function plug-in in the target live broadcast page is deleted or added according to the modification request.
  • the foregoing unit may be implemented as a separate entity, and may be implemented in any combination, and may be implemented as the same entity or a plurality of entities.
  • the foregoing unit may be implemented as a separate entity, and may be implemented in any combination, and may be implemented as the same entity or a plurality of entities.
  • the data processing device may be specifically integrated in a device such as a server.
  • the data processing apparatus of the embodiment may obtain the scene configuration information corresponding to the scene identifier by the obtaining unit 302, and then the loading unit 303 configures according to the scene.
  • the information is loaded into the corresponding function plug-in in the preset basic page to obtain the target live broadcast page, and the target live broadcast page is displayed by the display unit 304.
  • the embodiment of the present application further provides a data processing system for a live broadcast page, including
  • the data processing apparatus may be specifically integrated into the server, for example, as follows:
  • a server configured to receive a display request of a live broadcast page, where the display request carries a scene identifier, where the scene identifier is determined by the live broadcast client according to the running environment, and the scenario configuration information corresponding to the scene identifier is obtained, where the scenario is
  • the configuration information includes a mapping between the scenario identifier and the corresponding function plug-in.
  • the function plug-in corresponding to the scenario identifier is loaded in the preset basic page according to the scenario configuration information, and the target live broadcast page is obtained.
  • the live broadcast page is sent to the live broadcast client for display.
  • the server may be configured to load a preset core component according to the display request, load a scenario determining component by using the core component, and use the scenario determining component to extract a scenario identifier from the display request, and load a scenario configuration component.
  • the function structure according to the function structure, sequentially loads the corresponding function plug-in, and initializes the function plug-in to obtain the target live broadcast page.
  • the mapping between the scenario configuration information and the scenario identifier may be pre-stored in the data processing device of the live broadcast page, or may be established by the data processing device of the live broadcast page, that is,
  • the server may be further configured to obtain a scenario setting request, where the scenario setting request carries a scenario identifier, and according to the scenario setting request, acquire multiple function plug-in information, and receive function plug-in information selected by the user from the multiple function plug-in information, according to the selected
  • the function plug-in information generates scenario configuration information, and establishes a correspondence between the scenario configuration information and the scenario identifier.
  • each function plug-in in the target live page can also be used to respond to each event, namely:
  • the server may be further configured to obtain an event processing request triggered by the target live page, determine an event to be processed according to the event processing request, and invoke a corresponding function plug-in to process the event by using a function plug-in.
  • the plug-in in the target live page may also be modified, such as deleting or adding, ie:
  • the server may be further configured to obtain a modification request triggered by the target live page, where the modification request indicates a function plug-in that needs to be deleted or added, and the function plug-in in the target live page is deleted or added according to the modification request.
  • the data processing system of the live broadcast page may further include other devices, for example, may include a client, where the client may be specifically integrated in the terminal, as follows:
  • the terminal can be used to receive the target live page sent by the server and display it.
  • the data processing system of the live broadcast page can include any data processing device of the live broadcast page provided by the embodiment of the present application. Therefore, the data processing device of any live broadcast page provided by the embodiment of the present application can be implemented.
  • the beneficial effects are specifically described in the foregoing embodiments, and are not described herein again.
  • the embodiment of the present application further provides a server, as shown in FIG. 4, which shows a schematic structural diagram of a server involved in the embodiment of the present application, specifically:
  • the server may include one or more processors 401 of the processing core, a memory 402 of one or more computer readable storage media, a radio frequency (RF) circuit 403, a power source 404, an input unit 405, and a display unit 406, etc. component.
  • RF radio frequency
  • FIG. 4 does not constitute a limitation to the server, and may include more or less components than those illustrated, or some components may be combined, or different component arrangements. among them:
  • the processor 401 is the control center of the server, and connects the entire interface by using various interfaces and lines.
  • the various portions of the server perform overall monitoring of the server by running or executing software programs and/or modules stored in memory 402, as well as invoking data stored in memory 402, performing various functions of the server and processing the data.
  • the processor 401 can include one or more processing cores; preferably, the processor 401 can integrate an application processor and a modem processor, wherein the application processor primarily processes an operating system, a user interface, and an application. Programs, etc., the modem processor primarily handles wireless communications. It can be understood that the above modem processor may not be integrated into the processor 401.
  • the memory 402 can be used to store software programs and modules, and the processor 401 executes various functional applications and data processing by running software programs and modules stored in the memory 402.
  • the memory 402 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored according to Data created by the use of the server, etc.
  • memory 402 can include high speed random access memory, and can 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, memory 402 can also include a memory controller to provide processor 401 access to memory 402.
  • the RF circuit 403 can be used for receiving and transmitting signals during the process of transmitting and receiving information. Specifically, after receiving the downlink information of the base station, the downlink information is processed by one or more processors 401. In addition, the data related to the uplink is sent to the base station.
  • the RF circuit 403 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, and a Low Noise Amplifier (LNA). , duplexer, etc.
  • RF circuitry 403 can also communicate with the network and other devices via wireless communication.
  • the wireless communication may use any communication standard or protocol, including but not limited to Global System of Mobile communication (GSM), General Packet Radio Service (GPRS), and code division multiple access.
  • GSM Global System of Mobile communication
  • GPRS General Packet Radio Service
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • LTE Long Term Evolution
  • SMS Short Messaging Service
  • the server also includes a power source 404 (such as a battery) that supplies power to the various components.
  • the power source 404 can be logically coupled to the processor 401 via a power management system to manage functions such as charging, discharging, and power management through the power management system.
  • the power supply 404 may also include any one or more of a DC or AC power source, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.
  • the server can also include an input unit 405 that can be used to receive input numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.
  • input unit 405 can include a touch-sensitive surface as well as other input devices. Touch-sensitive surfaces, also known as touch screens or trackpads, collect touch operations on or near the user (such as the user using a finger, stylus, etc., any suitable object or accessory on a touch-sensitive surface or touch-sensitive Operation near the surface), and drive the corresponding connecting device according to a preset program.
  • the touch-sensitive surface can include two portions of a touch detection device and a touch controller.
  • the touch detection device detects the touch orientation of the user, and detects a signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into contact coordinates, and sends the touch information.
  • the processor 401 is provided and can receive commands from the processor 401 and execute them.
  • touch-sensitive surfaces can be implemented in a variety of types, including resistive, capacitive, infrared, and surface acoustic waves.
  • the input unit 405 can also include other input devices. Specifically, other input devices may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackballs, mice, joysticks, and the like.
  • the server can also include a display unit 406 that can be used to display information entered by the user or information provided to the user, as well as various graphical user interfaces of the server, which can be composed of graphics, text, icons, video, and It is composed of any combination.
  • the display unit 406 can include a display panel.
  • the display panel can be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.
  • the touch-sensitive surface may cover the display panel, and when the touch-sensitive surface detects a touch operation thereon or nearby, it is transmitted to the processor 401 to determine the type of the touch event, and then the processor 401 displays the type according to the touch event. A corresponding visual output is provided on the panel.
  • the touch-sensitive surface and display panel are implemented as two separate components to perform input and input functions, in some embodiments, the touch-sensitive surface can be integrated with the display panel to implement input and output functions.
  • the server may further include a camera, a Bluetooth module, and the like, and details are not described herein again.
  • the processor 401 in the server loads the executable file corresponding to the process of one or more applications into the memory 402 according to the following instruction, and is stored in the memory by the processor 401.
  • the application in 402 thus implementing various functions, as follows:
  • the display request carries the scenario identifier, where the scenario identifier is determined by the live broadcast client according to the running environment; and the scenario configuration information corresponding to the scenario identifier is obtained, where the scenario configuration information includes Corresponding relationship between the scenario identifier and the corresponding function plug-in; loading a function plug-in corresponding to the scenario identifier in the preset basic page according to the scenario configuration information, obtaining a target live broadcast page, and sending the target live broadcast page to The live client is for display.
  • the preset core component may be loaded according to the display request, and the scenario determining component is loaded by the core component, and the scenario determining component extracts the scenario identifier from the display request, and loads the scenario configuration component, and configures the component from the scenario.
  • Corresponding scene configuration information invoking a user interface management component, according to the scenario configuration information, the user interface management component renders a functional structure required by the corresponding function plug-in in the preset basic page, and sequentially loads the corresponding function according to the functional structure.
  • Function plugin and initialize the function plugin to get the target live page.
  • the corresponding relationship between the scenario configuration information and the scenario identifier may be pre-stored in the data processing device of the live broadcast page, or may be established by the data processing device of the live broadcast page, that is, the application stored in the memory 402, and may also be Implement the following functions:
  • Obtaining a scene setting request the scene setting request carrying a scene identifier, acquiring a plurality of function plug-in information according to the scene setting request, receiving function plug-in information selected by the user from the plurality of function plug-in information, and generating a scene configuration according to the selected function plug-in information Information, and establish the corresponding relationship between the scenario configuration information and the scenario identifier.
  • each function plug-in in the target live broadcast page can also respond to each event, that is, the application stored in the memory 402, and can also implement the following functions:
  • the plug-in in the target live page may also be modified, such as deleting or adding, that is, an application stored in the memory 402, and also implementing the following functions:
  • the modification request indicating a function plug-in that needs to be deleted or added, and deleting or adding the function plug-in in the target live broadcast page according to the modification request.
  • FIG. 5 is another schematic structural diagram of a server according to an embodiment of the present application. As shown in FIG. 5, the server 500 includes:
  • processors CPUs
  • network interfaces 504
  • memories 506 RAMs
  • communication bus 508 for interconnecting these components.
  • the network interface 504 is configured to implement a network connection between the server 500 and an external device, such as receiving a live page display request of a live client, sending a target live page to the live client, and the like.
  • the server 500 may also further include one or more output devices 512 (eg, a touch screen, display, etc.), and/or include one or more input devices 514 (eg, a touch screen, stylus, or other input controls, etc.).
  • output devices 512 eg, a touch screen, display, etc.
  • input devices 514 eg, a touch screen, stylus, or other input controls, etc.
  • the memory 506 can be a high speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid state storage device; or a non-volatile memory such as one or more disk storage devices, optical disk storage devices, flash memory devices, Or other non-volatile solid-state storage devices.
  • a high speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid state storage device
  • non-volatile memory such as one or more disk storage devices, optical disk storage devices, flash memory devices, Or other non-volatile solid-state storage devices.
  • the memory 506 includes:
  • Operating system 516 including programs for processing various basic system services and for performing hardware related tasks
  • the data processing application 518 of the live broadcast page is configured to receive a display request of the live broadcast page, where the display request carries a scene identifier, where the scene identifier is determined by the live broadcast client according to the running environment; and the scenario configuration information corresponding to the scene identifier is obtained.
  • the scene configuration information includes a corresponding relationship between the scene identifier and the corresponding function plug-in; and the function plug-in corresponding to the scene identifier is loaded in the preset basic page according to the scene configuration information, and the target is obtained.
  • the live broadcast page is sent to the live broadcast client for display.
  • the server of the embodiment can obtain the scene configuration information corresponding to the scene identifier, and then load the corresponding basic page according to the scene configuration information.
  • Feature plugin get the target live
  • the page displays the target live page; since the solution can flexibly load different function plug-ins according to different scene requirements to generate different live pages, it can only be implemented by hard code compared with the existing ones. In terms of page differentiation, not only is it simpler and more flexible, but it also saves development time and improves processing efficiency.
  • the program may be stored in a computer readable storage medium, and the storage medium may include: Read Only Memory (ROM), Random Access Memory (RAM), disk or optical disk.
  • ROM Read Only Memory
  • RAM Random Access Memory

Abstract

本申请实施例公开了一种直播页面的数据处理方法、装置和系统;本申请实施例在接收到携带场景标识的直播页面的展示请求后,可以获取该场景标识对应的场景配置信息,然后,根据该场景配置信息在预设的基础页面中加载相应的功能插件,得到目标直播页面,并将该目标直播页面发送给直播客户端进行展示。

Description

直播页面的数据处理方法、装置和系统
本申请要求于2016年12月6日提交中国专利局、申请号为201611110592.8,发明名称为“一种直播页面的数据处理方法、装置和系统”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域,具体涉及一种直播页面的数据处理方法、装置和系统。
发明背景
随着直播在网络中迅速蹿红,各种直播客户端也应运而生。这些直播客户端,除了可以提供直播观看功能之外,还可以提供各式直播房间,供主播进行直播;其中,用户观看直播时所在的页面,以及主播进行直播的页面,可以统称为直播页面。在直播页面上,除了直播窗口之前,通常还会提供其他一些操作入口,比如弹幕、聊天窗口、和/或礼物赠送等。
发明内容
本申请实施例提供一种直播页面的数据处理方法、装置和系统,可以提高其灵活性和效率。
本申请实施例提供一种直播页面的数据处理方法,应用于直播服务器,包括:
接收直播页面的展示请求,所述展示请求携带场景标识;其中,所述场景标识是直播客户端根据其运行环境确定的;
获取所述场景标识对应的场景配置信息;其中,所述场景配置信息 中包含所述场景标识与相应的功能插件之间的对应关系;
根据所述场景配置信息在预设的基础页面中加载与所述场景标识对应的功能插件,得到目标直播页面;
将所述目标直播页面发送给所述直播客户端,以进行展示。
相应的,本申请实施例还提供一种直播页面的数据处理装置,包括:
处理器;
与所述处理器相连接的存储器;所述存储器中存储有机器可读指令单元;所述机器可读指令单元包括:
接收单元,用于接收直播页面的展示请求,所述展示请求携带场景标识;其中,所述场景标识是直播客户端根据其运行环境确定的;
获取单元,用于获取所述场景标识对应的场景配置信息;其中,所述场景配置信息中包含所述场景标识与相应的功能插件之间的对应关系;
加载单元,用于根据所述场景配置信息在预设的基础页面中加载与所述场景标识对应的功能插件,得到目标直播页面;
展示单元,用于将所述目标直播页面发送给直播客户端,以进行展示。
此外,本申请实施例还提供一种直播页面的数据处理系统,包括本申请实施例所提供的任一种直播页面的数据处理装置。
本申请实施例还提供了一种非易失性计算机可读存储介质,其中所述存储介质中存储有机器可读指令,所述机器可读指令可以由处理器执行以完成本申请实施例所提供的任一种直播页面的数据处理方法。
附图简要说明
为了更清楚地说明本申请实施例中的技术方案,下面将对实施例描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本申请的一些实施例,对于本领域技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1a是本申请实施例提供的直播页面的数据处理方法的场景示意图;
图1b是本申请实施例提供的直播页面的数据处理方法的流程图;
图2a是本申请实施例提供的服务器中各组件的关系图;
图2b是本申请实施例提供的直播页面的数据处理方法的另一流程图;
图2c是本申请实施例提供的直播页面的数据处理方法中直播页面的示例图;
图3a是本申请实施例提供的直播页面的数据处理装置的结构示意图;
图3b是本申请实施例提供的直播页面的数据处理装置的另一结构示意图;
图4是本申请实施例提供的服务器的结构示意图。
图5为本申请实施例提供的服务器的另一种结构示意图。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本申请 保护的范围。
本申请实施例提供一种直播页面的数据处理方法、装置和系统。
其中,该直播页面的数据处理系统(简称数据处理系统)可以包括本申请实施例所提供的任一种直播页面的数据处理装置,该直播页面的数据处理装置可以集成在服务器等设备中;此外,该数据处理系统还可以包括其他的设备,比如终端,该终端可以安装有与该直播页面的数据处理装置对应的客户端,用于从该直播页面的数据处理装置中获取目标直播页面,并进行展示。
例如,参见图1a,以该直播页面的数据处理装置具体集成在服务器101中为例,首先,可以将页面上的功能模块划分为若干个独立版的功能插件,并分别为不同的场景设置对应的场景标识;其次,可以建立各个场景标识与各个插件信息之间的关联关系,并将该关联关系保存为场景配置信息,比如插件列表;这样,当服务器101接收到来自终端102的直播页面的展示请求时,便可以根据该展示请求中携带的场景标识获取对应的场景配置信息,比如获取插件列表,然后,根据该场景配置信息在预设的基础页面中加载相应的功能插件,得到目标直播页面,并将该目标直播页面发送给相应的终端102中的客户端,以进行展示,从而实现根据不同的场景需求,灵活地增减功能插件,以生成不同的直播页面的目的。
以下分别进行详细说明。本实施例将从直播页面的数据处理装置的角度进行描述,该直播页面的数据处理装置具体可以集成在服务器等设备中。
一种直播页面的数据处理方法,包括:接收直播页面的展示请求,该展示请求携带场景标识,其中,所述场景标识是直播客户端根据其运行环境确定的;获取该场景标识对应的场景配置信息,其中,所述场景 配置信息中包含所述场景标识与相应的功能插件之间的对应关系;根据该场景配置信息在预设的基础页面中加载与所述场景标识对应的功能插件,得到目标直播页面,将该目标直播页面发送给所述直播客户端,以进行展示。
如图1b所示,该直播页面的数据处理方法的具体流程可以如下:
S101、接收直播页面的展示请求,该展示请求携带场景标识。
例如,具体可以接收终端或其他设备发送的直播页面的展示请求,或者,接收本地设备(即该直播页面的数据处理装置)触发的直播页面的展示请求,等等。
其中,该场景标识用于对直播页面的不同的运行环境进行区分和识别,具体可以包括场景的名称、代号、编号、和/或图标等信息。在一些实施例中,所述运行环境可以指用于打开所述直播页面的应用的类型,例如,微信、微博、QQ、浏览器等。
S102、获取该场景标识对应的场景配置信息。
例如,具体可以设置一核心组件,用于对其他组件、以及各个插件进行加载和初始化,并对其生命周期进行管理;这样,在接收到直播页面的展示请求之后,便可以通过该核心组件,来获取相应的场景配置信息,即,步骤“获取该场景标识对应的场景配置信息”具体可以如下:
根据该展示请求加载预设的核心组件,通过该核心组件获取该场景标识对应的场景配置信息。
比如,可以通过该核心组件从该展示请求中提取出场景标识,并获取与该场景标识对应的场景配置信息,等等。
在一些实施例中,也可以分别设置一场景判断组件和场景配置组件,场景判断组件主要用于区分出不同的场景,而场景配置组件主要用于提供与各个场景对应的场景配置信息,这样,此时便可以通过加载该场景 判断组件和场景配置组件,来获取场景配置信息,即步骤“通过该核心组件获取该场景标识对应的场景配置信息”具体可以如下:
通过该核心组件加载场景判断组件,利用该场景判断组件从该展示请求中提取出场景标识,并加载场景配置组件,从该场景配置组件中获取与该场景标识对应的场景配置信息。
其中,场景配置信息与场景标识的对应关系可以预先存储在该直播页面的数据处理装置中,也可以由该直播页面的数据处理装置自行进行建立,即在步骤“接收直播页面的展示请求”之前,该直播页面的数据处理方法还可以包括:
获取场景设置请求,该场景设置请求携带场景标识,根据该场景设置请求获取多个功能插件信息,接收用户从该多个功能插件信息中选择的功能插件信息,根据选择的功能插件信息生成场景配置信息,并建立该场景配置信息与场景标识的对应关系。
此外,需说明的是,该场景配置信息包括至少一个需要加载的功能插件的相关信息(在本申请实施例中称为功能插件信息);具体实施时,该场景配置信息的信息格式可以有多种,比如可以是文本,也可以是列表等,为了描述方便,在本申请实施例中,以该场景配置信息具体为插件列表为例进行说明。
S103、根据该场景配置信息在预设的基础页面中加载相应的功能插件,得到目标直播页面;例如,具体可以如下:
首先,根据该场景配置信息在预设的基础页面中渲染出相应功能插件所需的功能结构,比如,可以如下:
调用用户界面管理组件,根据该场景配置信息,通过该用户界面管理组件在预设的基础页面中渲染出相应功能插件所需的功能结构,等等。
其中,基础页面指的是在加载本申请实施例所提供的功能插件之前 的直播页面,具体可以根据实际应用的需求进行设置,在此不再赘述。
然后,根据该功能结构依次加载相应的功能插件,并初始化该功能插件,得到目标直播页面。
S104、将该目标直播页面发送到直播客户端,以进行展示。
例如,除了可以在本地展示该目标直播页面之外,还可以将该目标直播页面发送到各个客户端,以进行展示,比如,可以将该目标直播页面发送给客户端所属的终端,以便该终端在屏幕上展示该目标直播页面,等等。
此外,在展示该目标直播页面之后,还可以通过该目标直播页面中的各个功能插件,来对各个事件进行响应,即在步骤“展示该目标直播页面”之后,该直播页面的数据处理方法还可以包括:
获取基于该目标直播页面触发的事件处理请求,根据该事件处理请求确定需要处理的事件,并调用相应的功能插件,通过调用的功能插件对该事件进行处理。
在一些实施例中,还可以对该目标直播页面中的插件进行修改,比如进行删除或增加,即,在步骤“展示该目标直播页面”之后,该直播页面的数据处理方法还可以包括:
获取基于该目标直播页面触发的修改请求,该修改请求指示需要进行删除或增加的功能插件,根据该修改请求对该目标直播页面中的功能插件进行删除或增加。
由上可知,本实施例在接收到携带场景标识的直播页面的展示请求后,可以获取该场景标识对应的场景配置信息,然后,根据该场景配置信息在预设的基础页面中加载相应的功能插件,得到目标直播页面,并展示该目标直播页面;由于该方案可以根据不同的场景需求,灵活地加载不同的功能插件,以生成不同的直播页面,因此,相对于现有中只能 通过硬代码的方式来实现页面差异化的方案而言,不仅实现更为简单和灵活,而且可以大大节省开发时间,有利于提高其处理效率。
根据上述实施例所描述的方法,以下将举例作进一步详细说明。
在本实施例中,将以该直播页面的数据处理装置具体集成在服务器中,且场景配置信息具体为插件列表为例进行说明。
首先,可以将直播页面上各个功能进行划分,并分别设置对应的功能插件,比如“直播功能”对应着直播功能插件,“弹幕互动”对应着弹幕互动插件,“送礼打赏”对应着送礼打赏插件,“直播计数”对应着直播计数插件,等等。其次,分别为不同的场景设置对应的场景标识,并建立各个场景标识与各个插件信息之间的关联关系,根据该关联关系建立插件列表;这样,当服务器接收到直播页面的展示请求时,便可以根据该展示请求中携带的场景标识获取对应的插件列表,然后,基于该插件列表在预设的基础页面中加载相应的功能插件,以得到目标直播页面并进行展示。
其中,可以通过在服务器设置多个模块,来协助完成上述操作,例如,参见图2a,在该服务器中,可以包括多个模块,比如核心组件201、场景判断组件202、场景配置组件203、事件引擎204、用户界面(UI,User Interface)管理组件205、以及多个功能插件206等,其中,各个模块的功能如下:
核心组件201,用于对其他组件、以及各个插件进行加载和初始化,并对其生命周期进行管理;比如,具体可以通过该核心组件来加载场景判断组件、场景配置组件、事件引擎、用户界面管理组件、以及各个功能插件,等等。
场景判断组件202,用于区分出不同的场景,比如,具体可以从展示请求中提取出场景标识,并根据该场景标识确定当前场景,等等。
场景配置组件203,用于提供与各个场景对应的插件列表(即场景配置信息),比如,具体可以在场景判断组件提取出场景标识后,提供与该场景标识对应的插件列表。
事件引擎204,用于获取基于该目标直播页面触发的事件处理请求,根据该事件处理请求确定需要处理的事件,并调用相应的功能插件,以对该事件进行处理。
用户界面管理组件205,用于在预设的基础页面中渲染出相应功能插件所需的功能结构,根据该功能结构依次加载相应的功能插件,并初始化该功能插件,得到目标直播页面。
功能插件206,分别对应着直播页面上的功能模块,比如弹幕互动、送礼打赏、以及直播计数等,功能插件在被调用后,可以对相应的事件进行处理。
基于上述服务器的架构,以下将举例对其执行流程进行详细说明。
如图2b所示,一种直播页面的数据处理方法,具体流程可以如下:
S201、服务器接收直播页面的展示请求,该展示请求携带场景标识。
其中,该场景标识用于对直播页面的不同的运行环境进行区分和识别,具体可以包括场景的名称、代号、编号、和/或图标等信息。在一些实施例中,所述运行环境可以指用于打开所述直播页面的应用的类型,例如,微信、微博、QQ、浏览器等。
S202、服务器根据该展示请求加载预设的核心组件,并初始化该核心组件,然后执行步骤S203。
S203、核心组件加载场景判断组件,并利用该场景判断组件从该展示请求中提取出场景标识,然后执行步骤S204。
S204、核心组件加载场景配置组件,从该场景配置组件中获取与该场景标识对应的插件列表,然后执行步骤S205。
例如,以该场景配置组件中包括两个插件列表为例,其中,插件列表1包括直播功能插件的信息和弹幕互动插件的信息,插件列表2包括直播功能插件的信息、弹幕互动插件的信息和送礼打赏插件的信息,那么:
若场景1的场景标识为001,且该场景需要加载的功能插件包括直播功能插件和弹幕互动插件,则此时,可以根据该场景标识“001”,从该场景配置组件中获取插件列表1。
若场景2的场景标识为002,且该场景需要加载的功能插件包括直播功能插件、弹幕互动插件和送礼打赏插件,则此时,可以根据该场景标识“002”,从该场景配置组件中获取插件列表2,依次类推,等等。
S205、核心组件调用用户界面管理组件,根据该插件列表,通过该用户界面管理组件在预设的基础页面中渲染出相应功能插件所需的功能结构,然后执行步骤S206。
例如,还是以步骤S204中的例子为例,如果需要加载的功能插件为“直播功能插件”和“弹幕互动插件”,则此时,可以根据插件列表1,通过该用户界面管理组件在预设的基础页面中渲染出“直播功能插件”和“弹幕互动插件”所需的功能结构,然后执行步骤S206。
同理,如果需要加载的功能插件为“直播功能插件”、“弹幕互动插件”和“送礼打赏插件”,则此时,可以根据插件列表2,通过该用户界面管理组件在预设的基础页面中渲染出“直播功能插件”、“弹幕互动插件”和“送礼打赏插件”所需的功能结构,然后执行步骤S206,依次类推,等等。
其中,基础页面指的是在加载本申请实施例所提供的功能插件之前的直播页面,具体可以根据实际应用的需求进行设置,在此不再赘述。
S206、核心组件根据该功能结构依次加载相应的功能插件,并初始化该功能插件,得到目标直播页面,然后执行步骤S207。
例如,若在步骤S205中,已渲染出“直播功能插件”和“弹幕互动插件”所需的功能结构,则此时,可以根据该功能结构依次加载“直播功能插件”和“弹幕互动插件”,并对这些功能插件进行初始化,以得到目标直播页面;比如,参见图2c,由于除了加载了“直播功能插件”之外,还加载了“弹幕互动插件”,因此,在该目标直播页面上,可以提供相应的弹幕互动功能,即用户可以通过触发该“弹幕互动”按键,来进行弹幕互动。
又例如,若在步骤S205中,渲染出的是“直播功能插件”、“弹幕互动插件”和“送礼打赏插件”所需的功能结构,那么此时,便可以根据该功能结构依次加载“直播功能插件”、“弹幕互动插件”和“送礼打赏插件”,并分别对这些功能插件进行初始化,等等。
S207、服务器将该目标直播页面发送给直播客户端,以进行展示。
其中,除了可以在本地展示该目标直播页面之外,还可以将该目标直播页面发送到各个客户端,以进行展示,比如,可以将该目标直播页面发送给客户端所属的终端,以便该终端在屏幕上展示该目标直播页面,等等。
此外,在展示该目标直播页面之后,还可以通过该目标直播页面中的各个功能插件,来对各个事件进行响应,即还可以执行步骤S208,如下:
S208、核心组件加载并初始化事件引擎,通过事件引擎分发事件,并调用相应的功能插件对事件进行处理,例如,具体可以如下:
事件引擎获取基于该目标直播页面触发的事件处理请求,根据该事件处理请求确定需要处理的事件,并触发核心组件调用相应的功能插件,通过调用的功能插件对该事件进行处理。
比如,以该事件为“弹幕互动”为例,则此时,可以触发核心组件调用弹幕互动插件,通过该弹幕互动插件对该事件进行处理,等等。
在一些实施例中,还可以对该目标直播页面中的插件进行修改,比如进行删除或增加,即还可以执行步骤S209,如下:
S209、核心组件获取基于该目标直播页面触发的修改请求,该修改请求指示需要进行修改的功能插件,根据该修改请求对该目标直播页面中的功能插件进行修改,比如进行删除或增加。
例如,如果需要将目标直播页面中的“弹幕互动功能”进行删除,则此时,可以发起对该目标直播页面的修改请求,然后,根据该修改请求将该目标直播页面中的“弹幕互动插件”进行删除。
又例如,如果需要在目标直播页面中增加“弹幕互动功能”,则此时,可以发起对该目标直播页面的修改请求,然后,根据该修改请求在该目标直播页面中增加相应的“弹幕互动插件”,等等。
其中,步骤S208和S209的执行顺序可以不分先后,在此不再赘述
由上可知,本实施例在接收到携带场景标识的直播页面的展示请求后,可以通过加载各种组件,来获取该场景标识对应的插件列表,然后,根据该插件列表在预设的基础页面中加载相应的功能插件,得到目标直播页面,并展示该目标直播页面;由于该方案可以根据不同的场景需求,灵活地加载不同的功能插件,以生成不同的直播页面,因此,相对于现有中只能通过硬代码的方式来实现页面差异化的方案而言,不仅实现更为简单和灵活,而且可以大大节省开发时间,有利于提高其处理效率。
比如,直播客户端A的直播页面可以只提供最基本的直播观看能力,而直播客户端B的直播页面除了可以提供直播观看功能之外,还可以提供各种互动功能,等等。
此外,由于可以灵活地对直播页面中的功能插件进行删减,因此,相对于现有方案而言,当需要添加其他功能或者改变场景的话,不需要重新编写代码以开发新的直播页面,就可以达到场景差异化表现效果, 可以更好更快速地适配不断变化的场景和需求,适用性较强。
为了更好地实施以上方法,本申请实施例还提供一种直播页面的数据处理装置,简称数据处理装置,如图3a所示,该数据处理装置可以包括接收单元301、获取单元302、加载单元303和展示单元304,如下:
接收单元301,用于接收直播页面的展示请求,该展示请求携带场景标识。
其中,该场景标识用于对直播页面的不同的运行环境进行区分和识别,具体可以包括场景的名称、代号、编号、和/或图标等信息。在一些实施例中,所述运行环境可以指用于打开所述直播页面的应用的类型,例如,微信、微博、QQ、浏览器等。
获取单元302,用于获取该场景标识对应的场景配置信息。
例如,获取单元302可以包括加载子单元和获取子单元,如下:
该加载子单元,用于根据该展示请求加载预设的核心组件。
获取子单元,用于通过该核心组件获取该场景标识对应的场景配置信息。
比如,获取子单元,具体可以用于通过该核心组件从该展示请求中提取出场景标识,并获取与该场景标识对应的场景配置信息,等等。
在一些实施例中,也可以分别设置一场景判断组件和场景配置组件来执行操作,即:
该获取子单元,具体可以用于通过该核心组件加载场景判断组件,利用该场景判断组件从该展示请求中提取出场景标识,并加载场景配置组件,从该场景配置组件中获取与该场景标识对应的场景配置信息。
其中,场景配置信息与场景标识的对应关系可以预先存储在该直播页面的数据处理装置中,也可以由该直播页面的数据处理装置自行进行建立,即如图3b所示,该数据处理装置还可以包括设置单元305,如下:
设置单元305,可以用于获取场景设置请求,该场景设置请求携带场景标识,根据该场景设置请求获取多个功能插件信息,接收用户从该多个功能插件信息中选择的功能插件信息,根据选择的功能插件信息生成场景配置信息,并建立该场景配置信息与场景标识的对应关系。
则此时,获取单元302,具体可以用于基于设置单元305建立的场景配置信息与场景标识的对应关系,来获取与该场景标识对应的场景配置信息。
加载单元303,用于根据该场景配置信息在预设的基础页面中加载相应的功能插件,得到目标直播页面。
例如,其中,该加载单元303可以包括渲染子单元和处理子单元,如下:
渲染子单元,可以用于根据该场景配置信息在预设的基础页面中渲染出相应功能插件所需的功能结构。
比如,该渲染子单元,具体可以用于调用用户界面管理组件,根据该场景配置信息,通过该用户界面管理组件在预设的基础页面中渲染出相应功能插件所需的功能结构。
其中,基础页面具体可以根据实际应用的需求进行设置,在此不再赘述。
处理子单元,可以用于根据该功能结构依次加载相应的功能插件,并初始化该功能插件,得到目标直播页面。
展示单元304,用于展示该目标直播页面。
例如,除了可以在本地展示该目标直播页面之外,展示单元304还可以将该目标直播页面发送到各个客户端,以进行展示,比如,可以将该目标直播页面发送给客户端所属的终端,以便该终端在屏幕上展示该目标直播页面,等等。
此外,在展示该目标直播页面之后,还可以通过该目标直播页面中的各个功能插件,来对各个事件进行响应,即如图3b所示,该数据处理装置还可以包括事件处理单元306,如下:
事件处理单元306,可以用于获取基于该目标直播页面触发的事件处理请求,根据该事件处理请求确定需要处理的事件,并调用相应的功能插件,通过调用的功能插件对该事件进行处理。
在一些实施例中,还可以对该目标直播页面中的插件进行修改,比如进行删除或增加,即,如图3b所示,该数据处理装置还可以包括修改单元307,如下:
修改单元307,可以用于获取基于该目标直播页面触发的修改请求,该修改请求指示需要进行删除或增加的功能插件,根据该修改请求对该目标直播页面中的功能插件进行删除或增加。
具体实施时,以上单元可以作为独立的实体来实现,也可以进行任意组合,作为同一或若干个实体来实现,以上各个单元的具体实施可参见前面的实施例,在此不再赘述。
该数据处理装置具体可以集成在服务器等设备中。
由上可知,本实施例的数据处理装置在接收到携带场景标识的直播页面的展示请求后,可以由获取单元302获取该场景标识对应的场景配置信息,然后,由加载单元303根据该场景配置信息在预设的基础页面中加载相应的功能插件,得到目标直播页面,并由展示单元304展示该目标直播页面;由于该方案可以根据不同的场景需求,灵活地加载不同的功能插件,以生成不同的直播页面,因此,相对于现有中只能通过硬代码的方式来实现页面差异化的方案而言,不仅实现更为简单和灵活,而且可以大大节省开发时间,有利于提高其处理效率。
相应的,本申请实施例还提供一种直播页面的数据处理系统,包括 本申请实施例所提供的任一种直播页面的数据处理装置,具体可参见前述实施例;其中,该数据处理装置具体可以集成在服务器中,例如,可以如下:
服务器,用于接收直播页面的展示请求,该展示请求携带场景标识,其中,所述场景标识是直播客户端根据其运行环境确定的;获取该场景标识对应的场景配置信息,其中,所述场景配置信息中包含所述场景标识与相应的功能插件之间的对应关系;根据该场景配置信息在预设的基础页面中加载与所述场景标识对应的功能插件,得到目标直播页面,将该目标直播页面发送给所述直播客户端,以进行展示。
例如,该服务器,具体可以用于根据该展示请求加载预设的核心组件,通过该核心组件加载场景判断组件,利用该场景判断组件从该展示请求中提取出场景标识,并加载场景配置组件,从该场景配置组件中获取与该场景标识对应的场景配置信息,调用用户界面管理组件,根据该场景配置信息,通过该用户界面管理组件在预设的基础页面中渲染出相应功能插件所需的功能结构,根据该功能结构依次加载相应的功能插件,并初始化该功能插件,得到目标直播页面。
其中,场景配置信息与场景标识的对应关系可以预先存储在该直播页面的数据处理装置中,也可以由该直播页面的数据处理装置自行进行建立,即:
服务器,还可以用于获取场景设置请求,该场景设置请求携带场景标识,根据该场景设置请求获取多个功能插件信息,接收用户从该多个功能插件信息中选择的功能插件信息,根据选择的功能插件信息生成场景配置信息,并建立该场景配置信息与场景标识的对应关系。
此外,在展示该目标直播页面之后,还可以通过该目标直播页面中的各个功能插件,来对各个事件进行响应,即:
该服务器,还可以用于获取基于该目标直播页面触发的事件处理请求,根据该事件处理请求确定需要处理的事件,并调用相应的功能插件,通过调用的功能插件对该事件进行处理。
在一些实施例中,还可以对该目标直播页面中的插件进行修改,比如进行删除或增加,即:
该服务器,还可以用于获取基于该目标直播页面触发的修改请求,该修改请求指示需要进行删除或增加的功能插件,根据该修改请求对该目标直播页面中的功能插件进行删除或增加。
此外,该直播页面的数据处理系统还可以包括其他的设备,比如,可以包括客户端,其中,该客户端具体可以集成在终端中,如下:
终端,可以用于接收服务器发送的目标直播页面,并进行展示。
以上各个设备的具体实施可参见前面的实施例,在此不再赘述。
由于该直播页面的数据处理系统可以包括本申请实施例所提供的任一种直播页面的数据处理装置,因此,可以实现本申请实施例所提供的任一种直播页面的数据处理装置所能实现的有益效果,具体详见前面的实施例,在此不再赘述。
本申请实施例还提供一种服务器,如图4所示,其示出了本申请实施例所涉及的服务器的结构示意图,具体来讲:
该服务器可以包括一个或者一个以上处理核心的处理器401、一个或一个以上计算机可读存储介质的存储器402、射频(Radio Frequency,RF)电路403、电源404、输入单元405、以及显示单元406等部件。本领域技术人员可以理解,图4中示出的服务器结构并不构成对服务器的限定,可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。其中:
处理器401是该服务器的控制中心,利用各种接口和线路连接整个 服务器的各个部分,通过运行或执行存储在存储器402内的软件程序和/或模块,以及调用存储在存储器402内的数据,执行服务器的各种功能和处理数据,从而对服务器进行整体监控。在一些实施例中,处理器401可包括一个或多个处理核心;优选的,处理器401可集成应用处理器和调制解调处理器,其中,应用处理器主要处理操作系统、用户界面和应用程序等,调制解调处理器主要处理无线通信。可以理解的是,上述调制解调处理器也可以不集成到处理器401中。
存储器402可用于存储软件程序以及模块,处理器401通过运行存储在存储器402的软件程序以及模块,从而执行各种功能应用以及数据处理。存储器402可主要包括存储程序区和存储数据区,其中,存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等;存储数据区可存储根据服务器的使用所创建的数据等。此外,存储器402可以包括高速随机存取存储器,还可以包括非易失性存储器,例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。相应地,存储器402还可以包括存储器控制器,以提供处理器401对存储器402的访问。
RF电路403可用于收发信息过程中,信号的接收和发送,特别地,将基站的下行信息接收后,交由一个或者一个以上处理器401处理;另外,将涉及上行的数据发送给基站。通常,RF电路403包括但不限于天线、至少一个放大器、调谐器、一个或多个振荡器、用户身份模块(SIM)卡、收发信机、耦合器、低噪声放大器(LNA,Low Noise Amplifier)、双工器等。此外,RF电路403还可以通过无线通信与网络和其他设备通信。所述无线通信可以使用任一通信标准或协议,包括但不限于全球移动通讯系统(GSM,Global System of Mobile communication)、通用分组无线服务(GPRS,General Packet Radio Service)、码分多址 (CDMA,Code Division Multiple Access)、宽带码分多址(WCDMA,Wideband Code Division Multiple Access)、长期演进(LTE,Long Term Evolution)、电子邮件、短消息服务(SMS,Short Messaging Service)等。
服务器还包括给各个部件供电的电源404(比如电池),优选的,电源404可以通过电源管理系统与处理器401逻辑相连,从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。电源404还可以包括一个或一个以上的直流或交流电源、再充电系统、电源故障检测电路、电源转换器或者逆变器、电源状态指示器等任意组件。
该服务器还可包括输入单元405,该输入单元405可用于接收输入的数字或字符信息,以及产生与用户设置以及功能控制有关的键盘、鼠标、操作杆、光学或者轨迹球信号输入。具体地,在一个具体的实施例中,输入单元405可包括触敏表面以及其他输入设备。触敏表面,也称为触摸显示屏或者触控板,可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触敏表面上或在触敏表面附近的操作),并根据预先设定的程式驱动相应的连接装置。在一些实施例中,触敏表面可包括触摸检测装置和触摸控制器两个部分。其中,触摸检测装置检测用户的触摸方位,并检测触摸操作带来的信号,将信号传送给触摸控制器;触摸控制器从触摸检测装置上接收触摸信息,并将它转换成触点坐标,再送给处理器401,并能接收处理器401发来的命令并加以执行。此外,可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触敏表面。除了触敏表面,输入单元405还可以包括其他输入设备。具体地,其他输入设备可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆等中的一种或多种。
该服务器还可包括显示单元406,该显示单元406可用于显示由用户输入的信息或提供给用户的信息以及服务器的各种图形用户接口,这些图形用户接口可以由图形、文本、图标、视频和其任意组合来构成。显示单元406可包括显示面板,在一些实施例中,可以采用液晶显示器(LCD,Liquid Crystal Display)、有机发光二极管(OLED,Organic Light-Emitting Diode)等形式来配置显示面板。进一步的,触敏表面可覆盖显示面板,当触敏表面检测到在其上或附近的触摸操作后,传送给处理器401以确定触摸事件的类型,随后处理器401根据触摸事件的类型在显示面板上提供相应的视觉输出。虽然在图4中,触敏表面与显示面板是作为两个独立的部件来实现输入和输入功能,但是在某些实施例中,可以将触敏表面与显示面板集成而实现输入和输出功能。
尽管未示出,服务器还可以包括摄像头、蓝牙模块等,在此不再赘述。具体在本实施例中,服务器中的处理器401会按照如下的指令,将一个或一个以上的应用程序的进程对应的可执行文件加载到存储器402中,并由处理器401来运行存储在存储器402中的应用程序,从而实现各种功能,如下:
接收直播页面的展示请求,该展示请求携带场景标识,其中,所述场景标识是直播客户端根据其运行环境确定的;获取该场景标识对应的场景配置信息,其中,所述场景配置信息中包含所述场景标识与相应的功能插件之间的对应关系;根据该场景配置信息在预设的基础页面中加载与所述场景标识对应的功能插件,得到目标直播页面,将该目标直播页面发送给所述直播客户端,以进行展示。
例如,具体可以根据该展示请求加载预设的核心组件,通过该核心组件加载场景判断组件,利用该场景判断组件从该展示请求中提取出场景标识,并加载场景配置组件,从该场景配置组件中获取与该场景标识 对应的场景配置信息,调用用户界面管理组件,根据该场景配置信息,通过该用户界面管理组件在预设的基础页面中渲染出相应功能插件所需的功能结构,根据该功能结构依次加载相应的功能插件,并初始化该功能插件,得到目标直播页面。
其中,场景配置信息与场景标识的对应关系可以预先存储在该直播页面的数据处理装置中,也可以由该直播页面的数据处理装置自行进行建立,即存储在存储器402中的应用程序,还可以实现如下功能:
获取场景设置请求,该场景设置请求携带场景标识,根据该场景设置请求获取多个功能插件信息,接收用户从该多个功能插件信息中选择的功能插件信息,根据选择的功能插件信息生成场景配置信息,并建立该场景配置信息与场景标识的对应关系。
此外,在展示该目标直播页面之后,还可以通过该目标直播页面中的各个功能插件,来对各个事件进行响应,即存储在存储器402中的应用程序,还可以实现如下功能:
获取基于该目标直播页面触发的事件处理请求,根据该事件处理请求确定需要处理的事件,并调用相应的功能插件,通过调用的功能插件对该事件进行处理。
在一些实施例中,还可以对该目标直播页面中的插件进行修改,比如进行删除或增加,即存储在存储器402中的应用程序,还可以实现如下功能:
获取基于该目标直播页面触发的修改请求,该修改请求指示需要进行删除或增加的功能插件,根据该修改请求对该目标直播页面中的功能插件进行删除或增加。
图5为本申请实施例提供的服务器的另一种结构示意图。如图5所示,所述服务器500包括:
一个或者多个处理器(CPU)502、网络接口504、存储器506、以及用于互联这些组件的通信总线508。
在一些实施例中,所述网络接口504用于实现所述服务器500与外部设备之间的网络连接,例如接收直播客户端的直播页面展示请求,向直播客户端发送目标直播页面等。
所述服务器500还可以进一步包含一个或多个输出设备512(例如触摸屏、显示器等),和/或包括一个或多个输入设备514(例如触摸屏、手写笔,或其他输入控件等)。
存储器506可以是高速随机存取存储器,诸如DRAM、SRAM、DDR RAM、或其他随机存取固态存储设备;或者非易失性存储器,诸如一个或多个磁盘存储设备、光盘存储设备、闪存设备,或其他非易失性固态存储设备。
存储器506包括:
操作系统516,包括用于处理各种基本系统服务和用于执行硬件相关任务的程序;
直播页面的数据处理应用518,用于接收直播页面的展示请求,该展示请求携带场景标识,其中,所述场景标识是直播客户端根据其运行环境确定的;获取该场景标识对应的场景配置信息,其中,所述场景配置信息中包含所述场景标识与相应的功能插件之间的对应关系;根据该场景配置信息在预设的基础页面中加载与所述场景标识对应的功能插件,得到目标直播页面,将该目标直播页面发送给所述直播客户端,以进行展示。
由上可知,本实施例的服务器在接收到携带场景标识的直播页面的展示请求后,可以获取该场景标识对应的场景配置信息,然后,根据该场景配置信息在预设的基础页面中加载相应的功能插件,得到目标直播 页面,并展示该目标直播页面;由于该方案可以根据不同的场景需求,灵活地加载不同的功能插件,以生成不同的直播页面,因此,相对于现有中只能通过硬代码的方式来实现页面差异化的方案而言,不仅实现更为简单和灵活,而且可以大大节省开发时间,有利于提高其处理效率。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成,该程序可以存储于一计算机可读存储介质中,存储介质可以包括:只读存储器(ROM,Read Only Memory)、随机存取记忆体(RAM,Random Access Memory)、磁盘或光盘等。
以上对本申请实施例所提供的一种直播页面的数据处理方法、装置和系统进行了详细介绍,本文中应用了具体个例对本申请的原理及实施方式进行了阐述,以上实施例的说明只是用于帮助理解本申请的方法及其核心思想;同时,对于本领域的技术人员,依据本申请的思想,在具体实施方式及应用范围上均会有改变之处,综上所述,本说明书内容不应理解为对本申请的限制。

Claims (18)

  1. 一种直播页面的数据处理方法,应用于直播服务器,包括:
    接收直播页面的展示请求,所述展示请求携带场景标识;其中,所述场景标识是直播客户端根据其运行环境确定的;
    获取所述场景标识对应的场景配置信息;其中,所述场景配置信息中包含所述场景标识与相应的功能插件之间的对应关系;
    根据所述场景配置信息在预设的基础页面中加载与所述场景标识对应的功能插件,得到目标直播页面;
    将所述目标直播页面发送给所述直播客户端,以进行展示。
  2. 根据权利要求1所述的方法,所述运行环境包括所述直播客户端中用于运行所述直播页面的应用的类型。
  3. 根据权利要求1所述的方法,所述获取所述场景标识对应的场景配置信息,包括:
    根据所述展示请求加载预设的核心组件;
    通过所述核心组件获取所述场景标识对应的场景配置信息。
  4. 根据权利要求3所述的方法,所述通过所述核心组件获取所述场景标识对应的场景配置信息,包括:
    通过所述核心组件加载场景判断组件;
    利用所述场景判断组件从所述展示请求中提取出场景标识,并加载场景配置组件;
    从所述场景配置组件中获取与所述场景标识对应的场景配置信息。
  5. 根据权利要求1至4任一项所述的方法,所述根据所述场景配置信息在预设的基础页面中加载相应的功能插件,得到目标直播页面,包括:
    根据所述场景配置信息在预设的基础页面中渲染出相应功能插件所 需的功能结构;
    根据所述功能结构依次加载相应的功能插件,并初始化所述功能插件,得到目标直播页面。
  6. 根据权利要求5所述的方法,所述根据所述场景配置信息在预设的基础页面中渲染出相应功能插件所需的功能结构,包括:
    调用用户界面管理组件;
    根据所述场景配置信息,通过所述用户界面管理组件在预设的基础页面中渲染出相应功能插件所需的功能结构。
  7. 根据权利要求1至4任一项所述的方法,所述将所述目标直播页面发送给所述直播客户端之后,还包括:
    获取基于所述目标直播页面触发的事件处理请求;
    根据所述事件处理请求确定需要处理的事件,并调用相应的功能插件;
    通过调用的功能插件对所述事件进行处理。
  8. 根据权利要求1至4任一项所述的方法,接收直播页面的展示请求之前,还包括:
    获取场景设置请求,所述场景设置请求携带场景标识;
    根据所述场景设置请求获取多个功能插件信息;
    接收用户从所述多个功能插件信息中选择的功能插件信息;
    根据选择的功能插件信息生成场景配置信息,并建立所述场景配置信息与场景标识的对应关系。
  9. 一种直播页面的数据处理装置,包括:
    处理器;
    与所述处理器相连接的存储器;所述存储器中存储有机器可读指令单元;所述机器可读指令单元包括:
    接收单元,用于接收直播页面的展示请求,所述展示请求携带场景标识;其中,所述场景标识是直播客户端根据其运行环境确定的;
    获取单元,用于获取所述场景标识对应的场景配置信息;其中,所述场景配置信息中包含所述场景标识与相应的功能插件之间的对应关系;
    加载单元,用于根据所述场景配置信息在预设的基础页面中加载与所述场景标识对应的功能插件,得到目标直播页面;
    展示单元,用于将所述目标直播页面发送给直播客户端,以进行展示。
  10. 根据权利要求9所述的装置,所述运行环境包括所述直播客户端中用于运行所述直播页面的应用的类型。
  11. 根据权利要求9所述的装置,所述获取单元包括加载子单元和获取子单元;
    所述加载子单元,用于根据所述展示请求加载预设的核心组件;
    获取子单元,用于通过所述核心组件获取所述场景标识对应的场景配置信息。
  12. 根据权利要求11所述的装置,
    所述获取子单元,具体用于通过所述核心组件加载场景判断组件,利用所述场景判断组件从所述展示请求中提取出场景标识,并加载场景配置组件,从所述场景配置组件中获取与所述场景标识对应的场景配置信息。
  13. 根据权利要求9至12任一项所述的装置,所述加载单元包括渲染子单元和处理子单元;
    渲染子单元,用于根据所述场景配置信息在预设的基础页面中渲染出相应功能插件所需的功能结构;
    处理子单元,用于根据所述功能结构依次加载相应的功能插件,并初始化所述功能插件,得到目标直播页面。
  14. 根据权利要求13所述的装置,
    所述渲染子单元,具体用于调用用户界面管理组件,根据所述场景配置信息,通过所述用户界面管理组件在预设的基础页面中渲染出相应功能插件所需的功能结构。
  15. 根据权利要求9至12任一项所述的装置,还包括事件处理单元;
    所述事件处理单元,用于获取基于所述目标直播页面触发的事件处理请求,根据所述事件处理请求确定需要处理的事件,并调用相应的功能插件,通过调用的功能插件对所述事件进行处理。
  16. 根据权利要求9至12任一项所述的装置,还包括设置单元;
    所述设置单元,用于获取场景设置请求,所述场景设置请求携带场景标识,根据所述场景设置请求获取多个功能插件信息,接收用户从所述多个功能插件信息中选择的功能插件信息,根据选择的功能插件信息生成场景配置信息,并建立所述场景配置信息与场景标识的对应关系。
  17. 一种直播页面的数据处理系统,包括权利要求9至16任一项所述的直播页面的数据处理装置。
  18. 一种非易失性计算机可读存储介质,其中,所述存储介质中存储有机器可读指令,所述机器可读指令可以由处理器执行以完成上述权利要求1至8任一项所述的直播页面的数据处理方法。
PCT/CN2017/109611 2016-12-06 2017-11-07 直播页面的数据处理方法、装置和系统 WO2018103484A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/282,015 US11025963B2 (en) 2016-12-06 2019-02-21 Data processing method, apparatus, and system for live streaming page

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611110592.8A CN106792188B (zh) 2016-12-06 2016-12-06 一种直播页面的数据处理方法、装置、系统和存储介质
CN201611110592.8 2016-12-06

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/282,015 Continuation US11025963B2 (en) 2016-12-06 2019-02-21 Data processing method, apparatus, and system for live streaming page

Publications (1)

Publication Number Publication Date
WO2018103484A1 true WO2018103484A1 (zh) 2018-06-14

Family

ID=58874448

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/109611 WO2018103484A1 (zh) 2016-12-06 2017-11-07 直播页面的数据处理方法、装置和系统

Country Status (3)

Country Link
US (1) US11025963B2 (zh)
CN (1) CN106792188B (zh)
WO (1) WO2018103484A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112835671A (zh) * 2021-02-23 2021-05-25 北京字节跳动网络技术有限公司 应用页面场景切换方法、装置及设备
CN113360806A (zh) * 2021-06-08 2021-09-07 上海哔哩哔哩科技有限公司 直播页面显示方法及装置

Families Citing this family (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106991108A (zh) * 2016-09-27 2017-07-28 阿里巴巴集团控股有限公司 一种信息的推送方法及装置
CN106792188B (zh) 2016-12-06 2020-06-02 腾讯数码(天津)有限公司 一种直播页面的数据处理方法、装置、系统和存储介质
CN107181978A (zh) * 2017-06-19 2017-09-19 武汉斗鱼网络科技有限公司 一种弹幕处理方法及装置
CN107690078B (zh) 2017-09-28 2020-04-21 腾讯科技(深圳)有限公司 弹幕信息显示方法、提供方法以及设备
CN109933261A (zh) * 2017-12-18 2019-06-25 北京奇虎科技有限公司 直播应用中的交互方法、装置和计算机可读存储介质
CN110475121B (zh) * 2018-05-10 2022-02-11 腾讯科技(深圳)有限公司 一种视频数据处理方法、装置以及相关设备
CN108897597B (zh) * 2018-07-20 2021-07-13 广州方硅信息技术有限公司 指导配置直播模板的方法和装置
CN110830839B (zh) * 2018-08-08 2022-03-08 腾讯科技(深圳)有限公司 多挂件展示方法、装置及存储介质
CN109120981B (zh) * 2018-09-20 2021-12-07 北京达佳互联信息技术有限公司 信息列表展示方法、装置及存储介质
CN109634597B (zh) * 2018-12-11 2022-02-18 武汉瓯越网视有限公司 数据处理方法、装置、电子设备及存储介质
CN109788302B (zh) * 2019-01-11 2021-05-14 上海六界信息技术有限公司 媒介信息投放方法、装置、设备及存储介质
CN110460895B (zh) * 2019-07-30 2022-05-06 视联动力信息技术股份有限公司 一种标志展示方法、装置、电子设备和存储介质
CN111093084A (zh) * 2019-12-27 2020-05-01 贵阳朗玛信息技术股份有限公司 一种直播中应用场景的制作方法及装置
CN111258694A (zh) * 2020-01-15 2020-06-09 广州虎牙科技有限公司 界面加载方法、装置、用户端及存储介质
CN111338722B (zh) * 2020-02-05 2024-02-27 广州虎牙科技有限公司 直播间模板加载方法、装置、电子设备及可读存储介质
CN113253880B (zh) * 2020-02-11 2024-03-08 腾讯科技(深圳)有限公司 互动场景的页面的处理方法、装置及存储介质
US11388067B2 (en) * 2020-03-30 2022-07-12 Tencent America LLC Systems and methods for network-based media processing (NBMP) for describing capabilities
CN111585869B (zh) * 2020-04-29 2022-09-16 上海掌门科技有限公司 一种即时消息的弹幕呈现方法及设备
CN111654717B (zh) * 2020-07-17 2023-11-03 腾讯科技(深圳)有限公司 数据处理方法、装置、设备及存储介质
CN111913708B (zh) * 2020-08-07 2024-02-27 广州虎牙科技有限公司 界面显示方法、装置、存储介质及电子设备
CN112423111A (zh) * 2020-11-05 2021-02-26 上海哔哩哔哩科技有限公司 图形引擎和适用于播放器的图形处理方法
CN112804551B (zh) * 2021-01-25 2023-07-25 北京有竹居网络技术有限公司 一种直播方法、装置、计算机设备及存储介质
CN113315982B (zh) * 2021-05-07 2023-06-27 广州虎牙科技有限公司 一种直播方法、计算机存储介质及设备
CN113542785B (zh) * 2021-07-13 2023-04-07 北京字节跳动网络技术有限公司 应用于直播的音频的输入输出的切换方法、直播设备
CN113722638B (zh) * 2021-07-30 2022-12-27 北京达佳互联信息技术有限公司 页面展示方法、装置、电子设备及存储介质
CN116088739A (zh) * 2021-11-04 2023-05-09 北京字跳网络技术有限公司 直播界面显示方法、装置、设备、存储介质及程序产品
CN114860358A (zh) * 2022-03-31 2022-08-05 北京达佳互联信息技术有限公司 一种对象处理方法、装置、电子设备及存储介质
CN115119037A (zh) * 2022-06-06 2022-09-27 深圳康佳电子科技有限公司 一种视频发布方法、推送方法、系统、设备及存储介质
CN115460428A (zh) * 2022-09-05 2022-12-09 北京达佳互联信息技术有限公司 数据处理方法、数据处理装置、电子设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101141625A (zh) * 2007-10-08 2008-03-12 中兴通讯股份有限公司 一种动态加载机顶盒控制逻辑的方法及系统
US20140359444A1 (en) * 2013-05-31 2014-12-04 Escape Media Group, Inc. Streaming live broadcast media
CN105589932A (zh) * 2015-12-10 2016-05-18 浪潮通信信息系统有限公司 一种页面配置的方法及装置
CN105898438A (zh) * 2016-04-07 2016-08-24 广州华多网络科技有限公司 直播间动态配置方法、装置、系统及服务器
CN106792188A (zh) * 2016-12-06 2017-05-31 腾讯数码(天津)有限公司 一种直播页面的数据处理方法、装置和系统

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030009771A1 (en) * 2001-06-26 2003-01-09 Chang Glen C. Method and system to provide a home style user interface to an interactive television system
US8667523B2 (en) * 2005-04-25 2014-03-04 Hewlett-Packard Development Company, L.P. Systems and methods for soliciting feedback using print-augmented broadcast signal
US8312486B1 (en) * 2008-01-30 2012-11-13 Cinsay, Inc. Interactive product placement system and method therefor
CN101625649A (zh) * 2009-08-17 2010-01-13 中兴通讯股份有限公司 一种软件的加载方法及装置
US8760488B2 (en) * 2010-10-22 2014-06-24 Litl Llc Video integration
CN102546777A (zh) * 2011-12-27 2012-07-04 广东宇天科技有限公司 移动终端桌面信息推送系统及其方法
EP2862350A4 (en) * 2012-06-19 2015-11-18 Sony Corp EXPANSIONS OF A TRIGGER PARAMETER PANEL FOR INTERACTIVE TELEVISION
US20140101548A1 (en) * 2012-10-05 2014-04-10 Apple Inc. Concurrently presenting interactive invitational content and media items within a media station through the use of bumper content
US10182272B2 (en) * 2013-03-15 2019-01-15 Samir B Makhlouf System and method for reinforcing brand awareness with minimal intrusion on the viewer experience
US9491496B2 (en) * 2014-05-01 2016-11-08 Verizon Patent And Licensing Inc. Systems and methods for delivering content to a media content access device
US20150319206A1 (en) * 2014-05-01 2015-11-05 Apple Inc. Sharing a media station
US9380345B2 (en) * 2014-12-01 2016-06-28 Microsoft Technology Licensing, Llc Immersive scaling interactive television

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101141625A (zh) * 2007-10-08 2008-03-12 中兴通讯股份有限公司 一种动态加载机顶盒控制逻辑的方法及系统
US20140359444A1 (en) * 2013-05-31 2014-12-04 Escape Media Group, Inc. Streaming live broadcast media
CN105589932A (zh) * 2015-12-10 2016-05-18 浪潮通信信息系统有限公司 一种页面配置的方法及装置
CN105898438A (zh) * 2016-04-07 2016-08-24 广州华多网络科技有限公司 直播间动态配置方法、装置、系统及服务器
CN106792188A (zh) * 2016-12-06 2017-05-31 腾讯数码(天津)有限公司 一种直播页面的数据处理方法、装置和系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112835671A (zh) * 2021-02-23 2021-05-25 北京字节跳动网络技术有限公司 应用页面场景切换方法、装置及设备
CN113360806A (zh) * 2021-06-08 2021-09-07 上海哔哩哔哩科技有限公司 直播页面显示方法及装置

Also Published As

Publication number Publication date
US11025963B2 (en) 2021-06-01
CN106792188B (zh) 2020-06-02
CN106792188A (zh) 2017-05-31
US20190200047A1 (en) 2019-06-27

Similar Documents

Publication Publication Date Title
WO2018103484A1 (zh) 直播页面的数据处理方法、装置和系统
US10635449B2 (en) Method and apparatus for running game client
CN110032512B (zh) 一种小程序的调试方法、相关设备及终端
US11864248B2 (en) Application function implementation method and electronic device
WO2018077041A1 (zh) 应用运行的方法及装置
WO2016150270A1 (zh) 群组会话消息处理方法和装置
US10474507B2 (en) Terminal application process management method and apparatus
WO2018045873A1 (zh) 即时通信应用的消息处理方法及相关产品
US20170257403A1 (en) Screen Sharing Method, Sharing Device, and Receiving Device
EP3179693B1 (en) Method, apparatus, storage medium and computer program product for establishing a data connection
CN106843868B (zh) 一种多账号登录的方法、装置以及移动终端
CN108605373B (zh) 用于提供网络共享服务的方法和电子装置
WO2018086454A1 (zh) 页面数据处理方法和装置
WO2018161543A1 (zh) 指纹处理资源的控制方法及设备
CN111078316B (zh) 布局文件加载方法、装置、存储介质及电子设备
CN108874554B (zh) 信息通信方法及装置
CN111273955B (zh) 热修复插件优化方法、装置、存储介质及电子设备
CN111104180B (zh) 应用程序优化方法、装置、存储介质及电子设备
CN107463524A (zh) 一种访问数据的方法及相关设备
CN105282628B (zh) 一种视频播放的方法和装置
JP7319431B2 (ja) アプリケーション機能の実施方法及び電子装置
CN116594616A (zh) 一种组件配置方法、装置及计算机可读存储介质
CN106209601B (zh) 状态更新消息的推送方法及装置
CN113268210A (zh) 投屏方法、设备及存储介质
CN109426572B (zh) 任务处理方法、装置及电子设备

Legal Events

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

Ref document number: 17878723

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17878723

Country of ref document: EP

Kind code of ref document: A1