CN100538622C - A kind of method that improves incident transmission and processing in the apparatus of digital television receiving - Google Patents

Abstract

Fundamental purpose of the present invention is to provide a kind of method that improves event information transmission and treatment effeciency in apparatus of digital television receiving.Label by the type to incident, regulation is carried the method for data, process that standard event registration and rope rise and agreement, pending times such as minimizing incident, thereby the communication speed between the raising disparate modules, the efficient of raising deal with data.The technological means that method of the present invention adopted is in incident of apparatus of digital television receiving design and message communicating mechanism, the mode of the type of regulation incident, the data layout that carries, Register Cancel and the strategy of processing, thus the incident that makes can effectively be carried out the transmission and the processing of information in different application and thread.The enforcement of the inventive method comprises the following steps: the registration and the cancellation of 1. event call-back functions; 2. the transmission of incident, reception and processing; 3. catching with cancellation of incident caught.

Description

A method for improving event transmission and processing in digital television receiving equipment

technical field

The invention relates to a method for transmitting event information and belongs to the technical field of digital television receiving equipment.

Background technique

Digital TV receiving equipment generally refers to hardware equipment that can receive, decode and display digital TV signals. It is used in the field of digital TV and is the terminal for realizing the digitization of analog TV (see Figure 1). Digital TV receiving equipment receives digital image and data information. Therefore, unlike the reception and processing of traditional analog TV signals, digital TV receiving equipment receives and processes digital image information and data through its internal CPU and peripheral devices connected to it. The receiving system is to develop the application program applicable to digital TV receiving equipment on the basis of corresponding hardware and operating system; similarly, some professional digital broadcast content service providers also need to develop corresponding service software.

In the broadcasting equipment of a TV station or a TV operator, audio and video signals and data content are mixed through a front-end multiplexer to form a transport stream (TS stream). The transmission stream is modulated to form an electromagnetic signal and sent to the digital TV receiving device. The working principle of digital TV receiving equipment (set-top box) is as follows:

◆The tuning/selection module receives the electromagnetic signal and selects a certain range of bandwidth.

◆The demodulation module converts signals into data streams (Bitstreams).

◆The demultiplexing module extracts the desired information from the data stream (Bitstreams) and provides it to different decoders in an appropriate way, which includes a descrambler that cooperates with the conditional access module.

◆The video decoding module converts the video bit stream in the displayed image sequence.

◆The audio decoding module converts the audio bit stream in the analog audio signal.

◆The graphics engine builds the graphics layer and mixes it with the video in the analog signal request to PAL/NTSC before sending.

◆The front control panel part is responsible for interpreting user commands sent by receiving remote control, wireless keyboard or front panel.

The video bit stream and the audio bit stream are mixed with the image through the image processor to become an analog audio and video signal, which is output to the display screen (television). The data stream flows into the CPU through the demultiplexer and is processed by the system program running on the central processing unit (CPU). The processed results can be mixed with the audio and video streams and output to the display device.

In a digital TV receiving device, resource modules with various functions need to exchange information, and this information exchange can take different forms. Each call to a resource module by an application or thread can be synchronous or asynchronous. Synchronous calls are blocked (Blocking). When the called function returns, the request issued by the function has been executed. Asynchronous calls are non-blocking (No Blocking). When the called function returns, the request sent by the function may not be executed, and the caller cannot get the execution result immediately. When the resource module executes the corresponding request, it will send an event (Event) to the caller to return the execution result of the request and related data.

In the existing technology, the way of event (event) or message (message) is generally used for information exchange. Each event or message has a type identifier (type), which in turn distinguishes the nature of the event to achieve the purpose of identifying the event. effect. In the field of digital TV, since the receiving and decoding equipment of digital TV is generally weak in function and the CPU processing speed is slow, if the traditional method is used, it will affect the visual effect of digital TV and affect the performance of the receiving equipment.

The problem with this traditional approach is that:

1. Events can only be broadcast and received one by one;

2. The incidental information is not clearly defined;

3. There is no specific method specified for the event receiving and processing process.

Method of the present invention is exactly the solution that proposes for the deficiency of traditional technology.

The definitions of several terms required by this method are given below:

Thread: refers to a program with a certain operating environment. Threads can exchange information by sending events.

Application: Refers to a program that meets certain functional requirements and purposes. Multiple threads can be used in an application.

Resources: Refers to the software or hardware used to realize certain functions in digital TV receiving equipment, such as providing audio and video decoding, data loaders, etc.

Resource module: refers to the software and hardware modules that provide resources.

Contents of the invention

The technical problem to be solved by the present invention is to provide a method for improving event information transmission and processing efficiency in a digital TV receiving device. By identifying the type of event, specifying the method of carrying data, standardizing the process and protocol of event registration and retrieval, reducing the time for event waiting to be processed, thereby improving the communication speed between different modules and improving the efficiency of data processing.

The present invention solves the above problems through the following technical solutions. Design an event manager in the digital TV receiving device to specify the type of event (type, code), the data format (data) carried, the way of registration and cancellation, the processing strategy, and the way of queuing the event (event), so that the event It can effectively transmit and process information in different applications and threads. The events described by this method have the following characteristics:

Each event (event) is uniquely determined by a type and code (type, code), and the result of the call is returned to the event handler through the data pointer (data) in the event:

The content of the event consists of the following parts:

●Type: type

●Code: code

●Data pointer: data

The data data pointer can point to different data structures according to different event types. If not specified, when sending an event, the data pointer passed along with the event should point to a dynamically allocated data space (instead of passing the address of the static space), so that when the application receives the event, it can pass the data The pointer obtains correct data information, and at the same time, after using the data, the data data pointer can be released by the sender of the event , and can also be released by the handler of the event. The communication mechanism of the basic event principle can also be used in other situations, such as a thread sending information to other threads.

The technical solution of the present invention will be described in detail below.

Steps in this method:

The method of the present invention is to implement an event manager in the digital TV receiving device, which is used to transmit and process events, and it includes the following steps.

1. Event delivery and processing:

Registration and deregistration of events:

When using the event communication mechanism, the target thread must first register with the event manager (Eventmanager), and give the type of event to be monitored and the address of its callback function (callback). When an event arrives, the event manager calls the callback function and passes it a data pointer, and returns the stored client data (client data) to the callback function. An application or thread can register to listen to multiple events at the same time. The operation flow of the event mechanism is shown in Figure 2.

If a thread or application no longer needs to process an event, it can send a logout request to the event manager (Event manager), and the event manager will release the unprocessed event and its corresponding data.

In order to effectively manage events and their callback functions, the event manager can have the following data lists:

● thread list

The data recorded by EventManager is connected in series through the thread list, and an event listening thread will occupy a record in the thread list. In addition to information such as thread id, each thread record also contains a callbakc list and an event list.

■Callback function list

The callback function list is used to record the callback function registered by the listening thread. Whenever the thread registers a callback function, the EventManager will add a callback function record to the callback list. When sending an event, the EventManager will check whether the callback record of the thread is There is a callback for the event, and if so, the event is added to the thread's event list. ; When the registration of the callback function is canceled, the item record in the list will be deleted, and then this type of event will no longer be sent to the thread.

■Event list

The event list is used to record the events sent to the thread. When a thread tries to send an event, the EventManager will check whether the event is registered in the callback function list of the sent thread, and if so, add this event to the After that, if the listening thread wants to get an event, it can find the corresponding event record from the event list.

The relationship between the above lists is shown in Figure 3.

Event handling:

When a thread or application registers a processing request for an event, it can be in a state of waiting for the event. It handles events as they are generated or arrive. Calling the event handler (callback function) First, the event is sent to the event manager, and the event manager calls the event handler (callback function), and the sender of the event directly calls the event handler for processing. Both approaches are essentially the same.

In cases where multiple threads can execute, the RTOS scheduler is responsible for deciding which thread to execute.

All threads (including driver layer threads and application program threads) can use the event manager. So each event management function should be thread-safe.

2. The detailed method of the implementation and use of the event manager:

事件回调函数的注册与注销

Registration and cancellation of event callback function

The main workflow of registering a callback function is shown in Figure 4.

The deregistration process works similarly. First get the thread record, then find the callback record in the callback list according to the callbackId, and delete the record. If all the callback functions of the thread are deleted, clear the thread record, including the events in it. records etc.

事件的发送、接收和处理

Sending, receiving and processing of events

The main workflow for sending events is as follows

1. Check if the event is caught

a) If the event is captured and the capturing thread is not the current thread, an error code is returned

b) otherwise continue

2. Repeat the following operations for all thread records:

a) If the thread id is the same as the thread id sent to, or the thread id sent to is 0, then

i. Do the following operations on all callback records of the thread:

1. If the event type recorded by the callback matches the sent event type, then

a) Add an event record to the thread's event list

b) Associate the callback record of the event

c) Release the conditional delivery of the thread so that the thread waiting for the event is woken up

3. If no thread is found to listen to the event, an error code is returned

Otherwise return success flag

The main workflow for getting events is as follows

1. Get the record of the listening thread in the thread list

2. Repeat the following operations for the event list recorded by the thread:

a) If the event type and code are the same as the type and code of the event to be processed, then

i. Perform the following operations on all callback records of the thread:

a) If the event type recorded by the callback matches the send event type, then

i. Copy event content,

ii. Jump to 3

3. If an event is received or a non-blocking method is used, jump to 5

4. If no event is received, wait for the thread condition variable (will be released when the event is sent)

5. If an event is received, then

a) Modify the current event flag of the thread

b) Output event information

c) return success flag

Otherwise, an error code is returned

The main workflow for handling events is as follows

1. Get the record of the listening thread in the thread list

2. If the current event recorded by the thread is not the same as the processed event, return an error code otherwise

a) Obtain the callback function and data release function associated with the event

b) Delete event records

c) Call the event callback function

d) Check whether all threads listening to the event have processed the event, if so, call the event data release function

e) Return the return value of the callback function

other instructions:

Since the processing speed of the event monitoring processing thread may not be able to keep up with the sending of events, in order to ensure that processing events can comply with the principle of first-in-line output, an event head pointer is added to the thread structure. At the same time, a next pointer is added to the event structure to point to the next Events, and then form a single-linked list of events. Every time you go to an event, you take the first event in the linked list, and add it to the end of the linked list when you send an event, so that you can avoid confusion in the order in which the listening thread processes events.

事件的捕获与取消捕获

Event capture and uncapture

The capture/uncapture event function is managed through a capture list. When a thread tries to capture an event, the Event Manager (EventManager) first checks whether the event has been exclusively occupied by the thread, and if so, does nothing. Otherwise, add a record to the capture list, which is always added to the head of the capture list, and record the type, code and capture thread id of the capture event, so that when an event is sent, it will be first in the capture list in order from beginning to end Look for a record of the event, and if there is a record and the thread id is different from the thread id it will be sent to, then do not send the event to the thread. When canceling the capture event, find the corresponding record in the capture list and delete the record.

Below in conjunction with accompanying drawing, the method of the present invention is described further.

Description of drawings

Figure 1 describes the main role of digital TV receiving equipment.

Figure 2 describes the operation flow of the event mechanism. The thread registers with the event manager (Event manager), and gives the type of event to be monitored and the address of its callback function (callback). When an event arrives, the event manager calls the callback function and passes it a data pointer, and returns the stored client data (client data) to the callback function. An application or thread can register to listen to multiple events at the same time.

Figure 3 describes the list of event data and processing functions.

Figure 4 describes the main workflow of registering a callback function.

The present invention will be further described in detail below in conjunction with specific implementation examples.

Detailed ways

The specific implementation is as follows:

1. The event manager needs to be initialized before use. The initialization function is MBT_EvtInit(), for example.

2. The basic usage of the event mechanism is

a) The use of receiving events (see the description of the event mechanism above for details):

i. Register event callback function

ii. Enter the event processing loop

1. Waiting for an event

2. Handle the event after receiving the event

3. Exit the loop on some condition (or never exit)

iii. Cancel the registration of the callback function when it is no longer necessary to listen to the event

b) Use of sending events

i. Events can be sent to a thread or broadcast to all threads listening to the event

ii. When sending an event, if the data data of the sending event is allocated dynamically, a data release function should be given

c) Use of exclusive events

i. When an event needs to be captured, call the capture event function to make an event exclusive to it. At this time, other threads will not be able to receive the event unless other threads capture the event again later.

ii. If you no longer want to monopolize an event, call the function of uncapturing the event to release the monopoly on the event.

Finally, it should be noted that: the present invention provides a method for improving event transmission and processing in digital television receiving equipment and its design ideas. The above embodiments are only used to illustrate and not limit the technical solutions of the present invention. The embodiment has described the present invention in detail, and those of ordinary skill in the art should understand that: the present invention can still be modified or equivalently replaced, and any modification or partial replacement without departing from the spirit and scope of the present invention should be covered by this within the scope of the claims of the invention.

Claims (9)

1. A method for improving the efficiency of event delivery and processing in digital television receiving equipment, characterized in that, in digital television receiving equipment, the type of event to be transmitted is identified, the method for carrying data is specified, and event registration and retrieval are regulated The process and protocol started, and the method organizes event storage and processing queues in the order of threads, links the callback function queues of event processing with their corresponding threads, and designs an event manager in the digital TV receiving device, The content of the event includes type, code and data pointer. Each event is uniquely determined by the type and code. The data carried by the event is passed to the event handler through the data pointer. The data recorded by the event manager is connected in series through the thread list. Each event listening thread occupies a record in the thread list, and each thread record also includes a callback function list and an event list, the callback function list is used to record the callback function registered by the listening thread, and the event list is used to record sending to the event of the listening thread. 2. A method for improving the efficiency of event transmission and processing according to claim 1, characterized in that the method transmits event information by sending, deleting, capturing and uncapturing events. 3. A method for improving the efficiency of event delivery and processing according to claim 1, characterized in that the method allows events to be processed by registering, canceling, and modifying callback functions for event processing. 4. A method for improving event transmission and processing efficiency according to claim 2 or 3, characterized in that the method allows the sender of the event to directly call the callback function of event processing, so that the event can be processed directly. 5. The method for improving event delivery and processing efficiency in a digital TV receiving device according to claim 1, characterized in that, when the event is delivered and processed by the event manager, the listening thread first registers with the event manager, and gives the required The type of event to monitor and the address of its callback function. When the event arrives, the event manager calls the callback function and passes the data carried by the event to the callback function through the data pointer. 6. The method for improving event delivery and processing efficiency in a digital TV receiving device according to claim 5, characterized in that, when the monitoring thread registers a callback function, the callback function of the event manager to the monitoring thread A callback function record is added in the function list; when the listening thread cancels the registration of the callback function, the event manager deletes the corresponding callback function record in the callback function list of the listening thread. 7. The method for improving event delivery and processing efficiency in a digital TV receiving device according to claim 6, characterized in that, when sending an event to a listening thread, the event manager checks the callback function list of the listening thread Whether there is a callback function corresponding to the event, if so, add the event to the event list of the listening thread; and when the listening thread obtains an event, find the corresponding event from the event list of the listening thread record. 8. The method for improving event delivery and processing efficiency in a digital TV receiving device according to claim 7, characterized in that, when processing an event, the event manager deletes the corresponding event record in the event list, and checks whether all The listening threads have all processed the event, and if so, call the data release function of the event. 9. The method for improving event delivery and processing efficiency in a digital TV receiving device according to claim 8, wherein the event manager further includes a capture list, and the capture list is used to record the exclusive use of events by the listening thread , when sending an event, first look for the record of the event in the capture list, if there is a record and the thread id is different from the thread id to be sent to, then the event will not be sent to the thread to be sent to; when canceling the capture event , then find the corresponding record in the capture list and delete the record.

Images