CN112040317B

CN112040317B - Event response method and display device

Info

Publication number: CN112040317B
Application number: CN202010851701.1A
Authority: CN
Inventors: 段宝山
Original assignee: Hisense Visual Technology Co Ltd
Current assignee: Vidaa Netherlands International Holdings BV
Priority date: 2020-08-21
Filing date: 2020-08-21
Publication date: 2022-08-09
Anticipated expiration: 2040-08-21
Also published as: CN112040317A

Abstract

The application discloses an event response method and display equipment, which are used for enabling all HBBTV modules not to influence each other when responding to an event in the display equipment. The display device includes: a display; a controller coupled to the display, comprising at least: the HBBTV broadcast system comprises a main program module and at least two mixed broadcast broadband television HBBTV modules; the main program module is configured to, when an event is detected, find at least one event queue corresponding to the event from event queues pre-configured for each HBBTV module, and store the event in the corresponding event queue; each HBBTV module is used for detecting a configured event queue, determining a configured calling function of the HBBTV module to be called according to the event type of a newly added event when detecting the newly added event in the configured event queue, and running the calling function according to the event parameter of the newly added event when the corresponding event parameter exists in the newly added event.

Description

Event response method and display device

Technical Field

The present application relates to the field of television technologies, and in particular, to an event response method and a display device.

Background

A Hybrid Broadcast Broadband TV (HBBTV) application in a display device generally needs to respond to an event in the display device, for example, when a channel switching event in the display device is triggered, part of the HBBTV module needs to respond to the event, and perform operations such as updating related information according to a switched channel.

Currently, when a main program module of a display device detects an event, a callback function of each HBBTV module that needs to respond to the event is sequentially called, so that each HBBTV module responds to the event. In this process, for each HBBTV module, the main program module needs to call the callback function of the next HBBTV module after the execution of the callback function of the HBBTV module is completed, and if the callback function of a certain HBBTV module is blocked, the main program module cannot continue to call the callback functions of other HBBTV modules behind the HBBTV module, so that other HBBTV modules cannot respond to the event.

Disclosure of Invention

The embodiment of the application provides an event response method and display equipment, which are used for enabling each HBBTV module not to influence each other when responding to an event in the display equipment.

In a first aspect, there is provided a display device comprising:

a display;

a controller coupled to the display, comprising at least: the HBBTV broadcast system comprises a main program module and at least two mixed broadcast broadband television HBBTV modules; wherein the content of the first and second substances,

the main program module is configured to, when an event is detected, find at least one event queue corresponding to the event from event queues pre-configured for each HBBTV module, and store the event into the corresponding event queue;

each HBBTV module is used for detecting a configured event queue, determining a configured calling function of the HBBTV module to be called according to the event type of a newly added event when detecting the newly added event in the configured event queue, and running the calling function according to the event parameter of the newly added event when the corresponding event parameter exists in the newly added event.

In a second aspect, an event response method is provided, which is applied to a display device, where the display device at least includes a main program module and at least two hybrid broadcast broadband television HBBTV modules, and the method includes:

when the main program module detects an event, at least one event queue corresponding to the event is searched from event queues pre-configured for each HBBTV module, and the event is stored in the corresponding event queue;

each HBBTV module detects an event queue configured by the HBBTV module, determines a calling function configured by the HBBTV module to be called according to the event type of a newly added event when the newly added event in the configured event queue is detected, and operates the calling function according to the event parameter of the newly added event when the corresponding event parameter exists in the newly added event.

In the above embodiment, the main program module only needs to store the event into the corresponding event queue configured for the HBBTV module when detecting the event, and each HBBTV module only needs to respond to the event stored in the event queue configured for the HBBTV module. Therefore, when responding to the event in the display device, the HBBTV modules do not influence each other, and even if the function called when one HBBTV module responds to the event is blocked, other HBBTV modules are not influenced.

Drawings

Fig. 1A is a schematic diagram illustrating an operation scenario between the display device 200 and the control apparatus 100;

fig. 1B is a block diagram schematically illustrating a configuration of the control apparatus 100 in fig. 1A;

fig. 1C is a block diagram schematically illustrating a configuration of the display device 200 in fig. 1A;

FIG. 1D is a block diagram illustrating an architectural configuration of an operating system in memory of display device 200;

2A-2B illustrate an event response flow diagram;

fig. 3 is a flowchart illustrating an event response method provided by an embodiment of the present application;

4A-4B illustrate another event response flow diagram;

a flowchart for implementing step S41 is exemplarily shown in fig. 5.

Detailed Description

To make the objects, technical solutions and advantages of the exemplary embodiments of the present application clearer, the technical solutions in the exemplary embodiments of the present application will be clearly and completely described below with reference to the drawings in the exemplary embodiments of the present application, and it is obvious that the described exemplary embodiments are only a part of the embodiments of the present application, but not all the embodiments.

All other embodiments, which can be derived by a person skilled in the art from the exemplary embodiments shown in the present application without inventive effort, shall fall within the scope of protection of the present application. Moreover, while the disclosure herein has been presented in terms of exemplary one or more examples, it is to be understood that each aspect of the disclosure can be utilized independently and separately from other aspects of the disclosure to provide a complete disclosure.

The terms "comprises" and "comprising," and any variations thereof, as used herein, are intended to cover a non-exclusive inclusion, such that a product or device that comprises a list of elements is not necessarily limited to those elements explicitly listed, but may include other elements not expressly listed or inherent to such product or device.

The term "module," as used herein, refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and/or software code that is capable of performing the functionality associated with that element.

The term "gesture" as used in this application refers to a user's behavior through a change in hand shape or an action such as hand motion to convey a desired idea, action, purpose, or result.

Fig. 1A is a schematic diagram illustrating an operation scenario between the display device 200 and the control apparatus 100. As shown in fig. 1A, the control apparatus 100 and the display device 200 may communicate with each other in a wired or wireless manner.

Among them, the control apparatus 100 is configured to control the display device 200, which may receive an operation instruction input by a user and convert the operation instruction into an instruction recognizable and responsive by the display device 200, serving as an intermediary for interaction between the user and the display device 200. Such as: the user operates the channel up/down key on the control device 100, and the display device 200 responds to the channel up/down operation.

The control device 100 may be a remote controller 100A, which includes infrared protocol communication or bluetooth protocol communication, and other short-distance communication methods, etc. to control the display apparatus 200 in a wireless or other wired manner. The user may input a user instruction through a key on a remote controller, voice input, control panel input, etc., to control the display apparatus 200. Such as: the user can input a corresponding control command through a volume up/down key, a channel control key, up/down/left/right moving keys, a voice input key, a menu key, a power on/off key, etc. on the remote controller, to implement the function of controlling the display device 200.

The control device 100 may also be an intelligent device, such as a mobile terminal 100B, a tablet computer, a notebook computer, and the like. For example, the display device 200 is controlled using an application program running on the smart device. The application program may provide various controls to a user through an intuitive User Interface (UI) on a screen associated with the smart device through configuration.

For example, the mobile terminal 100B may install a software application with the display device 200 to implement connection communication through a network communication protocol for the purpose of one-to-one control operation and data communication. Such as: the mobile terminal 100B may be caused to establish a control instruction protocol with the display device 200 to implement the functions of the physical keys as arranged in the remote control 100A by operating various function keys or virtual buttons of the user interface provided on the mobile terminal 100B. The audio and video content displayed on the mobile terminal 100B may also be transmitted to the display device 200, so as to implement a synchronous display function.

The display apparatus 200 may be implemented as a television, and may provide an intelligent network television function of a broadcast receiving television function as well as a computer support function. Examples of the display device include a digital television, a web television, a smart television, an Internet Protocol Television (IPTV), and the like.

The display device 200 may be a liquid crystal display, an organic light emitting display, a projection display device. The specific display device type, size, resolution, etc. are not limited.

The display apparatus 200 also performs data communication with the server 300 through various communication means. Here, the display apparatus 200 may be allowed to be communicatively connected through a Local Area Network (LAN), a Wireless Local Area Network (WLAN), and other networks. The server 300 may provide various contents and interactions to the display apparatus 200. By way of example, the display device 200 may send and receive information such as: receiving Electronic Program Guide (EPG) data, receiving software program updates, or accessing a remotely stored digital media library. The servers 300 may be a group or groups of servers, and may be one or more types of servers. Other web service contents such as a video on demand and an advertisement service are provided through the server 300.

Fig. 1B is a block diagram illustrating the configuration of the control device 100. As shown in fig. 1B, the control device 100 includes a controller 110, a memory 120, a communicator 130, a user input interface 140, an output interface 150, and a power supply 160.

The controller 110 includes a Random Access Memory (RAM)111, a Read Only Memory (ROM)112, a processor 113, a communication interface, and a communication bus. The controller 110 is used to control the operation of the control device 100, as well as the internal components of the communication cooperation, external and internal data processing functions.

Illustratively, when an interaction of a user pressing a key disposed on the remote controller 100A or an interaction of touching a touch panel disposed on the remote controller 100A is detected, the controller 110 may control to generate a signal corresponding to the detected interaction and transmit the signal to the display device 200.

And a memory 120 for storing various operation programs, data and applications for driving and controlling the control apparatus 100 under the control of the controller 110. The memory 120 may store various control signal commands input by a user.

The communicator 130 enables communication of control signals and data signals with the display apparatus 200 under the control of the controller 110. Such as: the control apparatus 100 transmits a control signal (e.g., a touch signal or a button signal) to the display device 200 via the communicator 130, and the control apparatus 100 may receive the signal transmitted by the display device 200 via the communicator 130. The communicator 130 may include an infrared signal interface 131 and a radio frequency signal interface 132. For example: when the infrared signal interface is used, the user input instruction needs to be converted into an infrared control signal according to an infrared control protocol, and the infrared control signal is sent to the display device 200 through the infrared sending module. The following steps are repeated: when the rf signal interface is used, a user input command needs to be converted into a digital signal, and then modulated according to an rf control signal modulation protocol, and then transmitted to the display device 200 through the rf transmitting terminal.

The user input interface 140 may include at least one of a microphone 141, a touch pad 142, a sensor 143, a key 144, and the like, so that a user can input a user instruction regarding control of the display apparatus 200 to the control device 100 through voice, touch, gesture, pressing, and the like.

The output interface 150 outputs a user instruction received by the user input interface 140 to the display apparatus 200, or outputs an image or voice signal received by the display apparatus 200. Here, the output interface 150 may include an LED interface 151, a vibration interface 152 generating vibration, a sound output interface 153 outputting sound, a display 154 outputting an image, and the like. For example, the remote controller 100A may receive an output signal such as audio, video, or data from the output interface 150, and display the output signal in the form of an image on the display 154, in the form of audio on the sound output interface 153, or in the form of vibration on the vibration interface 152.

And a power supply 160 for providing operation power support for the elements of the control device 100 under the control of the controller 110. In the form of a battery and associated control circuitry.

A hardware configuration block diagram of the display device 200 is exemplarily illustrated in fig. 1C. As shown in fig. 1C, the display apparatus 200 may further include a tuner demodulator 210, a communicator 220, a detector 230, an external device interface 240, a controller 250, a memory 260, a user interface 265, a video processor 270, a display 275, an audio processor 280, an audio input interface 285, and a power supply 290.

The tuner demodulator 210 receives the broadcast television signal in a wired or wireless manner, may perform modulation and demodulation processing such as amplification, mixing, and resonance, and is configured to demodulate, from a plurality of wireless or wired broadcast television signals, an audio/video signal carried in a frequency of a television channel selected by a user, and additional information (e.g., EPG data).

The tuner demodulator 210 is responsive to the user selected frequency of the television channel and the television signal carried by the frequency, as selected by the user and controlled by the controller 250.

The tuner demodulator 210 may receive a television signal in various ways according to the broadcasting system of the television signal, such as: terrestrial broadcasting, cable broadcasting, satellite broadcasting, internet broadcasting, or the like; and according to different modulation types, a digital modulation mode or an analog modulation mode can be adopted; and can demodulate the analog signal and the digital signal according to the different kinds of the received television signals.

In other exemplary embodiments, the tuning demodulator 210 may also be in an external device, such as an external set-top box. In this way, the set-top box outputs a television signal after modulation and demodulation, and inputs the television signal into the display apparatus 200 through the external device interface 240.

The communicator 220 is a component for communicating with an external device or an external server according to various communication protocol types. For example, the display apparatus 200 may transmit content data to an external apparatus connected via the communicator 220, or browse and download content data from an external apparatus connected via the communicator 220. The communicator 220 may include a network communication protocol module or a near field communication protocol module, such as a WIFI module 221, a bluetooth communication protocol module 222, and a wired ethernet communication protocol module 223, so that the communicator 220 may receive a control signal of the control device 100 according to the control of the controller 250, and implement the control signal as a WIFI signal, a bluetooth signal, a radio frequency signal, and the like.

The detector 230 is a component of the display apparatus 200 for collecting signals of an external environment or interaction with the outside. The detector 230 may include an image collector 231, such as a camera, a video camera, etc., which may be used to collect external environment scenes to adaptively change the display parameters of the display device 200; and the function of acquiring the attribute of the user or interacting gestures with the user so as to realize the interaction between the display equipment and the user. A light receiver 232 may also be included to collect ambient light intensity to adapt to changes in display parameters of the display device 200, etc.

In some other exemplary embodiments, the detector 230 may further include a temperature sensor, such as by sensing an ambient temperature, and the display device 200 may adaptively adjust a display color temperature of the image. For example, when the temperature is higher, the display apparatus 200 may be adjusted to display a color temperature of an image that is cooler; when the temperature is lower, the display device 200 may be adjusted to display a warmer color temperature of the image.

In some other exemplary embodiments, the detector 230, which may further include a sound collector, such as a microphone, may be configured to receive a sound of a user, such as a voice signal of a control instruction of the user to control the display device 200; alternatively, ambient sounds may be collected that identify the type of ambient scene, enabling the display device 200 to adapt to ambient noise.

The external device interface 240 is a component for providing the controller 210 to control data transmission between the display apparatus 200 and an external apparatus. The external device interface 240 may be connected to an external apparatus such as a set-top box, a game device, a notebook computer, etc. in a wired/wireless manner, and may receive data such as a video signal (e.g., moving image), an audio signal (e.g., music), additional information (e.g., EPG), etc. of the external apparatus.

The external device interface 240 may include: a High Definition Multimedia Interface (HDMI) terminal 241, a Composite Video Blanking Sync (CVBS) terminal 242, an analog or digital Component terminal 243, a Universal Serial Bus (USB) terminal 244, a Component terminal (not shown), a red, green, blue (RGB) terminal (not shown), and the like.

The controller 250 controls the operation of the display device 200 and responds to the operation of the user by running various software control programs (such as an operating system and various application programs) stored on the memory 260.

As shown in fig. 1C, the controller 250 includes a Random Access Memory (RAM)251, a Read Only Memory (ROM)252, a graphics processor 253, a CPU processor 254, a communication interface 255, and a communication bus 256. The RAM251, the ROM252, the graphic processor 253, and the CPU processor 254 are connected to each other through a communication bus 256 through a communication interface 255.

The ROM252 stores various system boot instructions. When the display apparatus 200 starts power-on upon receiving the power-on signal, the CPU processor 254 executes a system boot instruction in the ROM252, copies the operating system stored in the memory 260 to the RAM251, and starts running the boot operating system. After the start of the operating system is completed, the CPU processor 254 copies the various application programs in the memory 260 to the RAM251 and then starts running the various application programs.

A graphic processor 253 for generating screen images of various graphic objects such as icons, images, and operation menus. The graphic processor 253 may include an operator for performing an operation by receiving various interactive instructions input by a user, and further displaying various objects according to display attributes; and a renderer for generating various objects based on the operator and displaying the rendered result on the display 275.

A CPU processor 254 for executing operating system and application program instructions stored in memory 260. And according to the received user input instruction, processing of various application programs, data and contents is executed so as to finally display and play various audio-video contents.

In some example embodiments, the CPU processor 254 may comprise a plurality of processors. The plurality of processors may include one main processor and a plurality of or one sub-processor. A main processor for performing some initialization operations of the display apparatus 200 in the display apparatus preload mode and/or operations of displaying a screen in the normal mode. A plurality of or one sub-processor for performing an operation in a state of a standby mode or the like of the display apparatus.

The communication interface 255 may include a first interface to an nth interface. These interfaces may be network interfaces that are connected to external devices via a network.

The controller 250 may control the overall operation of the display apparatus 200. For example: in response to receiving a user input command for selecting a GUI object displayed on the display 275, the controller 250 may perform an operation related to the object selected by the user input command.

Where the object may be any one of the selectable objects, such as a hyperlink or an icon. The operation related to the selected object is, for example, an operation of displaying a link to a hyperlink page, document, image, or the like, or an operation of executing a program corresponding to an icon. The user input command for selecting the GUI object may be a command input through various input means (e.g., a mouse, a keyboard, a touch panel, etc.) connected to the display apparatus 200 or a voice command corresponding to a user uttering voice.

A memory 260 for storing various types of data, software programs, or applications for driving and controlling the operation of the display device 200. The memory 260 may include volatile and/or nonvolatile memory. And the term "memory" includes the memory 260, the RAM251 and the ROM252 of the controller 250, or a memory card in the display device 200.

In some embodiments, the memory 260 is specifically used for storing an operating program for driving the controller 250 of the display device 200; storing various application programs built in the display apparatus 200 and downloaded by a user from an external apparatus; data such as visual effect images for configuring various GUIs provided by the display 275, various objects related to the GUIs, and selectors for selecting the GUI objects are stored.

In some embodiments, the memory 260 is specifically configured to store drivers and related data for the tuner demodulator 210, the communicator 220, the detector 230, the external device interface 240, the video processor 270, the display 275, the audio processor 280, and the like, external data (e.g., audio-visual data) received from the external device interface, or user data (e.g., key information, voice information, touch information, and the like) received from the user interface.

In some embodiments, memory 260 specifically stores software and/or programs representing an Operating System (OS), which may include, for example: a kernel, middleware, an Application Programming Interface (API), and/or an application program. Illustratively, the kernel may control or manage system resources, as well as functions implemented by other programs (e.g., the middleware, APIs, or applications); at the same time, the kernel may provide an interface to allow middleware, APIs, or applications to access the controller to enable control or management of system resources.

A block diagram of the architectural configuration of the operating system in the memory of the display device 200 is illustrated in fig. 1D. The operating system architecture comprises an application layer, a middleware layer and a kernel layer from top to bottom.

The application layer, the application programs built in the system and the non-system-level application programs belong to the application layer and are responsible for direct interaction with users. The application layer may include a plurality of applications such as NETFLIX applications, setup applications, media center applications, and the like. These applications may be implemented as Web applications that execute based on a WebKit engine, and in particular may be developed and executed based on HTML, Cascading Style Sheets (CSS), and JavaScript.

Here, HTML, which is called HyperText Markup Language (HyperText Markup Language), is a standard Markup Language for creating web pages, and describes the web pages by Markup tags, where the HTML tags are used to describe characters, graphics, animation, sound, tables, links, etc., and a browser reads an HTML document, interprets the content of the tags in the document, and displays the content in the form of web pages.

CSS, known as Cascading Style Sheets (Cascading Style Sheets), is a computer language used to represent the Style of HTML documents, and may be used to define Style structures, such as fonts, colors, locations, etc. The CSS style can be directly stored in the HTML webpage or a separate style file, so that the style in the webpage can be controlled.

JavaScript, a language applied to Web page programming, can be inserted into an HTML page and interpreted and executed by a browser. The interaction logic of the Web application is realized by JavaScript. The JavaScript can package a JavaScript extension interface through a browser, realize the communication with the kernel layer,

the middleware layer may provide some standardized interfaces to support the operation of various environments and systems. For example, the middleware layer may be implemented as multimedia and hypermedia information coding experts group (MHEG) middleware related to data broadcasting, DLNA middleware which is middleware related to communication with an external device, middleware which provides a browser environment in which each application program in the display device operates, and the like.

The kernel layer provides core system services, such as: file management, memory management, process management, network management, system security authority management and the like. The kernel layer may be implemented as a kernel based on various operating systems, for example, a kernel based on the Linux operating system.

The kernel layer also provides communication between system software and hardware, and provides device driver services for various hardware, such as: provide display driver for the display, provide camera driver for the camera, provide button driver for the remote controller, provide wiFi driver for the WIFI module, provide audio driver for audio output interface, provide power management drive for Power Management (PM) module etc..

A user interface 265 receives various user interactions. Specifically, it is used to transmit an input signal of a user to the controller 250 or transmit an output signal from the controller 250 to the user. For example, the remote controller 100A may transmit an input signal, such as a power switch signal, a channel selection signal, a volume adjustment signal, etc., input by the user to the user interface 265, and then the input signal is transferred to the controller 250 through the user interface 265; alternatively, the remote controller 100A may receive an output signal such as audio, video, or data output from the user interface 265 via the controller 250, and display the received output signal or output the received output signal in audio or vibration form.

In some embodiments, a user may enter user commands on a Graphical User Interface (GUI) displayed on the display 275, and the user interface 265 receives the user input commands through the GUI. Specifically, the user interface 265 may receive user input commands for controlling the position of a selector in the GUI to select different objects or items.

Alternatively, the user may input a user command by inputting a specific sound or gesture, and the user interface 265 receives the user input command by recognizing the sound or gesture through the sensor.

The video processor 270 is configured to receive an external video signal, and perform video data processing such as decompression, decoding, scaling, noise reduction, frame rate conversion, resolution conversion, and image synthesis according to a standard codec protocol of the input signal, so as to obtain a video signal that is directly displayed or played on the display 275.

Illustratively, the video processor 270 includes a demultiplexing module, a video decoding module, an image synthesizing module, a frame rate conversion module, a display formatting module, and the like.

The demultiplexing module is configured to demultiplex an input audio/video data stream, where, for example, an input MPEG-2 stream (based on a compression standard of a digital storage media moving image and voice), the demultiplexing module demultiplexes the input audio/video data stream into a video signal and an audio signal.

And the video decoding module is used for processing the video signal after demultiplexing, including decoding, scaling and the like.

And the image synthesis module is used for carrying out superposition mixing processing on the GUI signal input by the user or generated by the user and the video image after the zooming processing by the graphic generator so as to generate an image signal for display.

The frame rate conversion module is configured to convert a frame rate of an input video, for example, convert a frame rate of an input 60Hz video into a frame rate of 120Hz or 240Hz, where a common format is implemented by using, for example, an interpolation frame method.

And a display formatting module for converting the signal output by the frame rate conversion module into a signal conforming to a display format of a display, such as converting the format of the signal output by the frame rate conversion module to output RGB data signals.

And a display 275 for receiving the image signal from the output of the video processor 270 and displaying video, images and menu manipulation interfaces. For example, the display may display video from a broadcast signal received by the tuner demodulator 210, may display video input from the communicator 220 or the external device interface 240, and may display an image stored in the memory 260. The display 275 and also displays a user manipulation interface UI generated in the display apparatus 200 and used to control the display apparatus 200.

And, the display 275 may include a display screen assembly for presenting a picture and a driving assembly for driving the display of an image. Alternatively, a projection device and projection screen may be included, provided display 275 is a projection display.

The audio processor 280 is configured to receive an external audio signal, decompress and decode the received audio signal according to a standard codec protocol of the input signal, and perform audio data processing such as noise reduction, digital-to-analog conversion, and amplification processing to obtain an audio signal that can be played by the speaker 286.

Illustratively, audio processor 280 may support various audio formats. Such as MPEG-2, MPEG-4, Advanced Audio Coding (AAC), high efficiency AAC (HE-AAC), and the like.

Audio output interface 285 receives audio signals from the output of audio processor 280. For example, the audio output interface may output audio in a broadcast signal received via the tuner demodulator 210, may output audio input via the communicator 220 or the external device interface 240, and may output audio stored in the memory 260. The audio output interface 285 may include a speaker 286, or an external audio output terminal 287, such as an earphone output terminal, that outputs to a generating device of an external device.

In other exemplary embodiments, video processor 270 may comprise one or more chips. Audio processor 280 may also comprise one or more chips.

And, in other exemplary embodiments, the video processor 270 and the audio processor 280 may be separate chips or may be integrated with the controller 250 in one or more chips.

And a power supply 290 for supplying power supply support to the display apparatus 200 from the power input from the external power source under the control of the controller 250. The power supply 290 may be a built-in power supply circuit installed inside the display apparatus 200 or may be a power supply installed outside the display apparatus 200.

In one example, at least a main program module and at least one HBBTV module are included in a display device. The main program module is mainly used for realizing functions of the display device, such as channel switching, system language changing, signal source switching and the like, and the HBBTV module is mainly used for realizing related functions of the HBBTV, such as updating display content of the HBBTV application and the like.

In some embodiments, when an event is triggered, if at least two HBBTV modules need to respond to the event, the main program module sequentially calls the callback functions of the at least two HBBTV modules so that the at least two HBBTV modules can respond to the event. For convenience of description, in the following embodiments, an HBBTV module that needs to respond to an event is denoted as an HBBTV module corresponding to the event.

To facilitate understanding of the above embodiments, an event response flow diagram is illustrated in FIGS. 2A-2B. Described below in connection with FIGS. 2A-2B by way of example:

in fig. 2A, module B, module C, and module D are all HBBTV modules. The module a, the module B, and the module C all need to respond to a channel switching type event (hereinafter, referred to as a channel switching event), and register their callback function a, callback function B, and callback function C in the main program module in advance, respectively. For the above channel switching event, in an embodiment, a channel switching instruction input by a user operating the control device may be used as a trigger for the channel switching event, where the channel switching instruction may be a key input instruction corresponding to a key on the control device (e.g., a "CH +" key/"CH-" key), and the channel switching event is triggered when the key input instruction corresponding to the key on the control device is received.

When a channel switching event in the display device is triggered, the main program module in the display device in fig. 2A needs to sequentially call the callback function a, the callback function B, and the callback function C, so that the module a, the module B, and the module C respond to the channel switching event. As shown in fig. 2A, when the callback function B of the module B is called, the callback function B needs to call the function D of the module D; for the callback function of each module, the main program module needs to call the callback function of the next module after the execution of the callback function is completed and a call result is returned.

If a certain callback function is blocked and cannot return a call result when the callback function B calls the function D in the flow shown in fig. 2A, as shown in fig. 2B, the main program cannot call the callback function C that should be called after the callback function B because the call result returned by the callback function B is not received, so that the module C corresponding to the callback function C cannot respond to the channel switching event.

As can be seen from the flow shown in fig. 2A-2B, when an event is triggered, the main program module sequentially calls the callback functions of the HBBTV modules corresponding to the event, so that the HBBTV modules are coupled when responding to the event in the display device, and if the callback function of a module called by the main program module is blocked and cannot be executed, the main program module cannot continue to call the callback function of the next module, so that the next module cannot respond to the event.

Moreover, since other functions may need to be called when the callback function is called, and other functions may also call other functions, the call chain may be relatively deep, and the blocking of any function in the call chain may cause the blocking of the callback function, which makes it difficult to find and repair the root of the blocking of the callback function in a short time, so that the next HBBTV module of the HBBTV module corresponding to the blocked callback function is continuously affected by the blocking.

Therefore, the application provides an event response method, so that the HBBTV module does not influence each other when responding to the event triggered in the display device. The following is described in connection with fig. 3:

referring to fig. 3, fig. 3 is a flowchart illustrating an event response method provided by an embodiment of the present application. As shown in fig. 3, the process may include the following steps:

step S41, when the main program module detects an event, finds at least one event queue corresponding to the event from the event queues pre-configured for each HBBTV module, and stores the event in the corresponding event queue.

For convenience of description, the event detected in this step S41 will be hereinafter referred to as a target event. In one example, the target event may be any event registered in the display device, such as a channel switching event instructing the display device to switch from a current channel to a target channel, a language switching event instructing the display device to switch a system language from a current language to a target language, and so on. Taking the channel switching event as an example, the main program module may perform a channel switching operation in response to the channel switching event, and perform the step S41, so that the HBBTV module may respond to the channel switching event.

The event queue in step S41 is an event queue configured by the HBBTV module, and in one example, before step S41 is executed, at least one event queue for storing events may be created and configured for each HBBTV module in the display device, so that each HBBTV module is configured with a different event queue. As an embodiment, if there is an HBBTV module that does not need to respond to an event in the display device, the event queue may be configured only for HBBTV modules other than the HBBTV module that need to respond to an event in the display device.

In creating each event queue, as one embodiment, the event queue may be assigned a queue ID that is used to distinguish the event queue from other event queues. As an embodiment, when configuring an event queue for any HBBTV module, the queue ID of the event queue may be recorded in the HBBTV module, so that the HBBTV module records the event queue as an event queue configured by itself.

The main program module finds at least one event queue corresponding to the event from the event queues pre-configured for each HBBTV module, and there are various implementation manners, which are described below with reference to the embodiments.

In one example, the main program module may receive event information sent by each HBBTV module, the event information including a queue ID of an event queue to which the HBBTV module is configured. When searching for the event queue corresponding to the target event, as an embodiment, the main program module may determine the event queue corresponding to each received queue ID as the event queue corresponding to the target event. Thus, the target event is stored in the event queue corresponding to each queue ID.

For any HBBTV module, as an embodiment, the HBBTV module may send event information including a queue ID of an event queue to which the HBBTV module is configured to the main program module after booting (for convenience of description, this step is described as registering the event queue with the main program module in the following embodiments). Specifically, the starting of the HBBTV module herein may be the first starting of the HBBTV module in the display device, or may be each starting of the HBBTV module in the display device. For one embodiment, when the HBBTV module stops operating, a logout message may be sent to the main program module, where the logout message includes the queue ID of the event queue to which the HBBTV module is configured, so that the main program module deletes the recorded queue ID. As another example, any HBBTV module may register the queue ID of the configured event queue to the main program module after being configured with the event queue.

In another example, the number of registered events in the display device is large, and when the HBBTV module is actually applied, only part of the events need to respond. The main program module may receive event information sent by each HBBTV module, where the event information may include a queue ID of an event queue configured by the HBBTV module and an event type of an event that the HBBTV module needs to respond to, that is, may include a correspondence between the queue ID of the event queue configured by the HBBTV module and the event type of the event that the HBBTV module needs to respond to.

When searching for the event queue corresponding to the target event, as an embodiment, the main program module may find a queue ID having a corresponding relationship with the event type according to the event type of the target event, and determine the event queue corresponding to the queue ID as the event queue corresponding to the target event. Thus, the target event is deposited into the event queue configured by the HBBTV module which needs to respond to the target event.

In another example, the above two examples may be used in combination, and specifically, the main program module may receive event information sent by each HBBTV module, where the event information may include only a queue ID of an event queue configured by the HBBTV module, and may also include a correspondence between the queue ID of the event queue configured by the HBBTV module and an event type of an event to which the HBBTV module needs to respond.

When searching for an event queue corresponding to a target event, as an embodiment, for a queue ID having a correspondence with an event type, searching for a queue ID having a correspondence with the event type according to the event type of the target event, and determining an event queue corresponding to the queue ID as an event queue corresponding to the target event; and directly determining the event queue corresponding to the queue ID as the event queue corresponding to the target event for the queue ID which does not have the corresponding relation with the event type.

In the above embodiments, the queue ID of the event queue configured for each HBBTV module, and the correspondence between the queue ID of the event queue configured for each HBBTV module and the event type of the event that the HBBTV module needs to respond to may also be recorded to the main program module by other means (such as manual configuration).

In specific implementation, there are multiple implementation manners of step S41, which are described below with reference to fig. 5 for example, and are not described herein again.

In step S42, each HBBTV module calls the configured calling function of the HBBTV module according to the event type of the newly added event when detecting the newly added event in the event queue configured by the HBBTV module.

In one example, each HBBTV module configured with an event queue may retrieve a deposited event from the configured event queue and respond to the event. As an embodiment, when the event queue configured by the HBBTV module does not store an event, the HBBTV module may detect whether an event is newly added to the configured event queue in real time, so that when an event is newly stored to the event queue, the event can be timely taken out and responded. In one embodiment, the HBBTV module is provided with an event detection thread for detecting in real time whether an event is newly added to the configured event queue.

In one example, when any HBBTV module detects a newly added event in an event queue in which the HBBTV module is configured, the HBBTV module may determine a configured calling function that needs to be called according to an event type of the newly added event. As an embodiment, when there is a corresponding event parameter for the newly added event, the HBBTV module runs the determined call function according to the event parameter. For one embodiment, when there is no corresponding event parameter for the newly added event, the HBBTV module may directly run the determined calling function.

Whether the newly added event corresponds to the event parameter or not and what event parameter corresponds to the newly added event can be configured in the display device in advance according to actual needs. For example, for the event type of channel switching, the event parameter corresponding to the event of the event type may be configured as the relevant information of the switched channel, so that when the HBBTV module responds to the channel switching event, the HBBTV module may run a call function according to the relevant information of the switched channel, so as to achieve the effects of updating the channel information in the user interface of the HBBTV application to the relevant information of the switched channel, and the like.

As an embodiment, if the event information sent by the HBBTV module to the main program module includes a correspondence between a queue ID of an event queue configured by the HBBTV module and an event type of an event that the HBBTV module needs to respond to, the newly added event in the event queue configured by the HBBTV module is an event that the HBBTV module needs to respond to, and the HBBTV module can directly determine a calling function that needs to be called for the newly added event in the event queue configured by the HBBTV module.

As an embodiment, if the event information sent by the HBBTV module to the main program does not include a correspondence between a queue ID of an event queue configured by the HBBTV module and an event type of an event that the HBBTV module needs to respond to, a newly added event in the event queue configured by the HBBTV module is not necessarily an event that the HBBTV module needs to respond to, and when detecting a newly added event in the configured event queue, the HBBTV module may first determine whether the newly added event is an event that the HBBTV module needs to respond to, specifically, may determine whether the event type of the newly added event is an event type of an event that the HBBTV module needs to respond to, and if the determination result is yes, determine an already configured calling function of the HBBTV module that needs to be called according to the event type of the newly added event. For one embodiment, in the case where the determination result is negative, the HBBTV module may discard the newly added event.

The flow shown in fig. 3 is completed.

Through the flow shown in fig. 3, each HBBTV module only needs to call a call function of a response according to an event stored in the event queue configured for each HBBTV module to respond to the event, and each HBBTV module does not affect each other, and even if a certain HBBTV module blocks the call function called by the event, other HBBTV modules are not affected.

To facilitate understanding of the flow and benefits shown in fig. 3, another event response flow diagram is illustrated in fig. 4A-4B, which is described below in connection with fig. 4A-4B by way of example:

in fig. 4A, module B, module C, and module D are all HBBTV modules, and module a, module B, and module C are configured with event queue a, event queue B, and event queue C, respectively. The module a, the module B and the module C all need to respond to a channel switching event, and respectively register the corresponding relationship between the queue ID of the event queue a, the queue ID of the event queue B and the queue ID of the event queue C corresponding to the module a and the module C and the channel switching event type to the main program module in advance.

When the main program module detects a channel switching event, for example, when a channel switching instruction is received, as shown in fig. 4A, the main program module stores the channel switching event in the event queue a, the event queue B, and the event queue C, respectively, so that the module a, the module B, and the module C take out the channel switching event from their corresponding event queues, respectively, and respond to the channel switching event. When the module B responds to the channel switching event, the function D of the module D needs to be called.

If the function D called by the module B is blocked and cannot return the calling result in the flow shown in fig. 4A, as shown in fig. 4B, the module B cannot receive the calling result returned by the module D, and the module C is not affected by the blocking of the function D and can still respond to the channel switching event stored in the event queue C corresponding to the module C.

As can be seen from the processes shown in fig. 4A-4B, by applying the event response method provided in the embodiment of the present application, each HBBTV module may not affect each other when responding to an event triggered in a display device, and even if a function called when a certain HBBTV module responds to an event is blocked, other modules may not be affected to respond to the event.

Step S41 in the above-described flow shown in fig. 3 is described below by way of example with reference to fig. 5.

Referring to fig. 5, an implementation flowchart of step S41 is exemplarily shown in fig. 5. In one example, before the flow shown in fig. 5 is executed, each HBBTV module has sent the correspondence between the queue ID of the configured event queue and the event type of the event that needs to be responded to the main program module. As shown in fig. 5, the process may include the following steps:

in step S51, when detecting an event, the main program module determines at least one queue ID having a correspondence relationship with the event type from the received correspondence relationship between the queue ID and the event type according to the event type of the event.

In step S52, for each determined queue ID, the main program module generates an event according to the event type of the detected event, and stores the generated event in the event queue corresponding to the queue ID.

In one example, the event generated by the main program module may include at least an event type and a parameter corresponding to the event. Taking a channel switching event as an example, the event parameter corresponding to the event may be related information of a channel to be switched to, where the related information may include: original Network Identification (ONID), Transport Stream Identification (TSID), Service Identification (SID), and the like.

To facilitate understanding of the present step S52, a simple example is given below. Taking the event detected by the main program module as a channel switching event and the event parameter corresponding to the event is the related information of the channel a as an example, the main program module may generate an event for each queue ID determined in step S51, where the event includes the event type of channel switching and the event parameter as the related information of the channel a, and store the generated event in the event queue corresponding to the queue ID.

To facilitate understanding of the events generated by the main program module, the data structure of the generated events is exemplarily shown by table 1 below:

string eventName；
	int eventType；
Type1 eventParam1；
	Type2 eventParam2；
……
	TypeN eventParamN；

TABLE 1

As shown in table 1, the data structure of the event mainly includes: eventName (event name), eventType (event type), and eventParam (event parameter). The event name and the event type are used for uniquely identifying the event, each module in the display equipment mainly identifies different events according to the event type, and the different events are mainly identified according to the event name during manual testing; the event parameters 1-N are event parameters that need to be transmitted by the event, and are filled in by the main program module according to the event parameters actually corresponding to the event, and if the event does not correspond to the event parameters, the event parameters in table 1 may be empty.

This completes the description of the flow shown in fig. 5.

It should be noted that the flow shown in fig. 5 is only an example of a specific implementation of the step S41, and other implementation manners may exist in practical application, which are not listed here.

As described in the above embodiments, when an event occurs, the main program module in the display device stores the event in the corresponding event queue, and each HBBTV module only needs to respond to the event stored in the event queue configured for the HBBTV module, so that when responding to the event in the display device, each HBBTV module does not affect each other, and even if a function called when a certain HBBTV module responds to the event is blocked, other HBBTV modules are not affected.

While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A display device, comprising:

a display;

the main program module is configured to create and configure at least one event queue for storing events for each HBBTV module in the display device, so that each HBBTV module is configured with different event queues, when an event is detected, find at least one event queue corresponding to the event from the event queues pre-configured for each HBBTV module, and store the event into the corresponding event queue;

2. The display device according to claim 1, wherein the main program module is further configured to receive event information sent by each HBBTV module, and the event information includes: the corresponding relation between the queue ID of the event queue configured by the HBBTV module and the event type of the event which needs to be responded by the HBBTV module;

the finding, by the main program module, of the at least one event queue corresponding to the event from the event queues pre-configured for the HBBTV modules includes:

and the main program module finds a queue ID which has a corresponding relation with the event type according to the event type of the detected event, and determines an event queue corresponding to the queue ID as the event queue corresponding to the event.

3. The display device according to claim 1, wherein the main program module is further configured to receive event information sent by each HBBTV module, and the event information includes: queue ID of event queue where HBBTV module is configured;

and the main program module determines the event queue corresponding to each received queue ID as the event queue corresponding to the event.

4. The display device according to claim 3,

when detecting that an event is newly added to an event queue configured by the HBBTV module, each HBBTV module judges whether the event type of the event is the event type of the event to which the HBBTV module needs to respond, and if so, determines a configured calling function of the HBBTV module needing to be called according to the event type of the newly added event.

5. The display device according to claim 1, wherein the HBBTV module directly runs the call function when there is no corresponding event parameter for a newly added event.

6. An event response method, applied to a display device at least comprising a main program module and at least two Hybrid Broadcast Broadband Television (HBBTV) modules, comprises the following steps:

the main program module creates and configures at least one event queue for storing events for each HBBTV module in the display device, so that each HBBTV module is configured with different event queues, when an event is detected, at least one event queue corresponding to the event is searched from the event queues pre-configured for each HBBTV module when the event is detected, and the event is stored into the corresponding event queue;

7. The method of claim 6, further comprising:

the main program module receives event information sent by each HBBTV module, and the event information comprises: the corresponding relation between the queue ID of the event queue configured by the HBBTV module and the event type of the event which needs to be responded by the HBBTV module;

the finding of at least one event queue corresponding to the event from the event queues pre-configured for each HBBTV module includes:

and finding a queue ID which has a corresponding relation with the event type according to the event type of the detected event, and determining an event queue corresponding to the queue ID as the event queue corresponding to the event.

8. The method of claim 6, further comprising:

the main program module receives event information sent by each HBBTV module, and the event information comprises: queue ID of event queue where HBBTV module is configured;

and determining the event queue corresponding to each received queue ID as the event queue corresponding to the event.

9. The method according to claim 8, wherein the determining, when a newly added event in the configured event queue is detected, the configured calling function of the HBBTV module that needs to be called according to the event type of the newly added event includes:

when detecting that an event is newly added in an event queue configured by the HBBTV module, judging whether the event type of the event is the event type of the event which needs to be responded by the HBBTV module, if so, determining a configured calling function of the HBBTV module which needs to be called according to the event type of the newly added event.

10. The method according to claim 6, wherein when there is no corresponding event parameter for the newly added event, the method comprises: the HBBTV module directly runs the calling function.