WO2010072030A1 - Mobile terminal multimedia broadcast driving interface and realizing method - Google Patents

Abstract

The present invention discloses a mobile terminal multimedia broadcast driving interface and a realizing method, wherein the driving interface is a logic interface set between a lower read interface and a upper application interface of a terminal, and the logic interface is triggered via the application interface to work at least when the application needs to read the multimedia broadcast data stored in the terminal, and the logic interface is used for separating the payload data and the control information from the multimedia broadcast data read from the read interface, and buffering them to different channels respectively for read by the application via the application interface. The present invention provides an uniform interface for different types of the terminal chips, meanwhile the developing flow is simplified, and the developing period is shorten, thereby the producing cost of a product is reduced.

Description

 Mobile terminal multimedia broadcast driver interface and implementation method

Technical field

 The present invention relates to an embedded system applied to a mobile terminal, and more particularly to a multimedia broadcast driver interface and a method for implementing the mobile terminal.

Background technique

 China Mobile Multimedia Broadcasting (CMMB) is a mobile multimedia broadcast TV technology with independent intellectual property rights promulgated by the State Administration of Radio, Film and Television. It is mainly used to provide digital audio, video and information to various portable terminal devices through wireless broadcast television coverage networks. Service; CMMB has the advantage of being able to solve the problem of unsmooth signal of mobile terminal (mobile TV) by means of satellite communication. At present, CMMB is managed by the State Administration of Radio, Film and Television, and it is responsible for the film, television and radio program carriers. TV show resources.

 To implement the CMMB application on the handheld terminal, it is necessary to call the driver interface of the terminal chip to read the multiplexed frame and part of the control information, and uplink to the application, and also need to write some control information of the downlink to control the behavior of the chip. .

 At present, there are many types of CMMB terminal chips on the market, and the solutions are not the same. For example, in some chips, multiplexed frames and control information are transmitted on the same data bus; in others, the two are transmitted separately.

 Therefore, if the driver of the chip is only the driver chip, and the received data is forwarded to the upper application without any treatment, two problems are caused:

 First, for those chips that combine the multiplexed frame and control information on the same bus, the data needs to be packaged accordingly when writing data (that is, the chip just needs to write the data); When data is fetched (that is, when data is needed), the data needs to be separated, which directly increases the complexity of the program and leads to an extended development cycle.

Second, because there are separate chips for multiplexing frames and control information, which breaks the uniformity and versatility of the driver interface, the application must have two sets of logic, and sometimes it is necessary to develop two different versions for the two chips. It also leads to an extended development cycle. It can be seen that the existing mobile terminal multimedia broadcast driver interface needs to be improved, so that it can be uniformly applied to the driving of multiple types of terminal chips.

Summary of the invention

 The technical problem to be solved by the present invention is to provide a multimedia broadcast driver interface and implementation method for a mobile terminal, which can provide a unified interface suitable for any type of chip for a terminal multimedia broadcast upper layer application.

 In order to solve the above technical problem, the present invention provides a method for implementing a multimedia broadcast driver interface of a mobile terminal, comprising: configuring a logical interface between a read interface of a bottom layer of the terminal and an application program interface of an upper layer; When the multimedia broadcast data is stored, the multimedia broadcast data read from the read interface is separated from the payload data and the control information through a logical interface, and buffered to different channels respectively, and the application program reads through the application program interface.

 Further, the logical interface buffers the separated payload data into the payload data channel, and buffers the separated control information into the uplink control information channel.

 Further, the logical interface is further connected to the bottom write interface of the terminal. When the application needs to write the control information to the terminal, the control information that needs to be written is buffered to the downlink control information channel through the application program interface, and then the logic is passed. The interface sends control information read from the downlink control information channel from the write interface to the data bus of the terminal.

 Further, the logical interface separates the payload data and the control information according to a protocol agreed by the terminal and the corresponding multimedia broadcast system.

 Further, the payload data channel and the uplink control information channel in the logical interface are respectively implemented by creating and maintaining a first instance and a second instance of a first-in first-out FIFO pair column; or, downlink control information in the logical interface The channel is implemented by creating and maintaining a third instance of the FIFO pair column; wherein the payload data channel is used for read-only, and the uplink control information channel or the downlink control information channel is used for reading and writing.

Further, the FIFO pair column is implemented by the first cache list and the second cache list; the first cache list is used to arrange the cache block in the use of the cached data, and the second cache list is used to arrange the empty block of the uncached data or has been Take a reusable block of data; Initializing the first cache list and the second cache list before the corresponding channel caches the data, that is, setting the first cache list to be empty, and adding a certain number of cache blocks to the second cache list one by one;

 When there is data to be cached to the corresponding channel, if the second cache list is not empty, the first cache block is requested in the second cache list for data caching, and the first cache block is moved into the first cache list. The last item, then the cache operation ends normally; if the second cache list is empty, wait until the second cache list is not empty and waits for no timeout, continue the data cache and its subsequent operations, if the waiting timeout then the cache operation ends abnormally ;

 When the data is to be read from the corresponding channel, if the first cache list is not empty, the first cache block is taken from the first cache list, and the first cache block is moved to the first after the data is read. The second item of the second cache list, and then the read operation ends normally; if the first cache list is empty, then wait until the first cache list is not empty and wait for no timeout, continue data reading and subsequent operations, if waiting for timeout Then the read operation ends abnormally.

In order to solve the above technical problem, the present invention provides a mobile terminal multimedia broadcast driver interface, which is a logical interface configured between a bottom read interface of the terminal and an upper application interface, and the logical interface is at least applied. When the program needs to read the multimedia broadcast data stored by the terminal, the work is triggered by the application program interface, and the multimedia broadcast data read from the read interface is separated from the payload data and the control information, and buffered to different channels respectively, to be applied. The program is read through the application interface.

 Further, the logical interface includes an interconnected read/write distribution module and a data channel module, where: a data channel module, configured to at least create and maintain a payload data channel and an uplink control information channel;

 The read/write distribution module is connected to the read interface, and is configured to buffer the separated payload data into the payload data channel through the data channel module, and buffer the separated control information into the uplink control information channel through the data channel module, and then to the application interface. Returns a data readable indication.

Further, the logic interface triggers the work through the application program interface when the application is to write the control information to the terminal; The data channel module is also used to create and maintain a downlink control information channel;

 The read/write distribution module is further connected to the underlying write interface of the terminal, and is configured to buffer the control information to be written to the terminal to the downlink control information channel through the application program interface, and then use the data channel module to control the information channel from the downlink. The read control information is sent from the write interface to the data bus of the terminal, and then the data written indication is returned to the application interface.

 Further, the payload data channel is used for read-only, and the uplink control information channel or the downlink control information channel is used for reading or writing; the payload data channel, the uplink control information channel, and the downlink control information channel each have a respective first buffer area. And a respective second buffer area, wherein: the first buffer area is used by the data channel module when receiving the data read request from the application interface when one or more cache blocks in use of the cached data are arranged Reading the data of the first cache block and carrying the data in a normal response to the data returned to the application interface; meanwhile, the first cache block of the read data is placed by the data channel module The last item of the second buffer of the corresponding channel;

 a second buffer area, configured to be requested by the data channel module when receiving a data cache request from the read-write distribution module when an empty cache block having uncached data or a reusable cache block having data taken out is arranged The data carried in the cache is cached in the first cache block, and the first cache block of the write data is placed by the data channel module in the last entry of the first buffer of the corresponding channel.

By using the driving interface and method provided by the present invention, by separating the multiplexing frame from the control information, and by using the read-write dual channel technology, the terminal developer can only develop a set of applications for the motherboards of different types of CMMB chips. The program, while simplifying the logic of the upper application as much as possible, simplifies the development process and shortens the development cycle. At the same time, the production line no longer needs to determine the version of the application to download by judging the type of motherboard, thereby reducing production costs.

BRIEF abstract

 1 is a structural block diagram of an embodiment of a CMMB terminal driving interface of the present invention;

2 is a flow chart of the data read/write distribution operation of the CMMB terminal drive interface of the present invention; FIG. 3 is a flow chart of the data channel initialization and write operation of the CMMB terminal drive interface of the present invention; Figure

 Figure 4 is a flow diagram of a data channel read operation for the CMMB terminal application interface of the present invention. Preferred embodiment of the invention

 The core point of the multimedia broadcast driver interface and implementation method of the mobile terminal provided by the present invention is: adding a device-independent logical interface between the read/write operation interface of the bottom layer of the chip and the application interface of the upper layer, the logical interface includes at least reading Writing a distribution module, a payload data channel, and an uplink control information channel; when the application needs to read data, the read/write distribution module separates the multimedia broadcast data stream read from the read interface of the read/write operation interface into the payload data. And the control information is respectively placed in the payload data channel and the uplink control information channel to be read by the application program. The above technical solution of the present invention will be explained and explained in detail below with reference to the accompanying drawings and with a CMMB terminal as a preferred embodiment. Here, the CMMB terminal is taken as an embodiment for the purpose of illustrating and explaining the invention, and is not intended to limit the invention. The present invention can be applied to terminals of various multimedia broadcasting systems.

1 is a block diagram showing the structure of a CMMB terminal multimedia broadcast driver interface provided by the present invention. As shown in FIG. 1, the drive interface is actually a device-independent logical interface 100 added between the bottom-level read/write operation interface of the chip and the upper application interface, and includes an interconnected read-write distribution module. 110 and data channel module 120; wherein:

 The read/write operation interface includes a read interface and a write interface, and the read interface is used at least to read the multimedia broadcast data stream received by the chip from the terminal memory; the write interface is at least used to send the downlink control information of the application to be written to the chip to the data bus. Upper

The read/write distribution module 110 is also respectively connected to the application program interface, and is connected to the read interface and the write interface, and is used to invoke the program interface when the application needs to read and write data; when the application wants to read the data, it is called. The multiplexed frame payload data and the uplink control information separated in the data stream read by the read interface are respectively placed into the multiplexed frame channel and the uplink channel by the data channel module 120, and returned to the application interface. Data can be read instructions; when the application wants to write data is When called, the downlink control information acquired from the downlink channel by the data channel module 120 is sent from the write interface to the data bus, and the data written indication is returned to the application program interface;

 The data channel module 120 is configured to separately create and maintain a multiplexed frame channel, an uplink channel, and a downlink channel of the buffer multiplexed frame data, the uplink control information, and the downlink control information;

 An application interface, configured to invoke the read-write distribution module 110 when the application is to read data, and read and reuse the multiplexing frame channel and the uplink channel by the data channel module 120 after receiving the data readable indication. The frame payload data and the uplink control information; when the application needs to write data, the downlink control information to be written into the chip is first written into the downlink channel, and the read/write distribution module 110 is called to write the downlink control information.

 The data channel module 120 creates and maintains a multiplexed frame channel, an upstream channel, and a downstream channel by creating and maintaining three instances of a first-in first-out queue FIFO pair column. Among them, the multiplexed frame channel is used for read-only, and the upstream channel and the downstream channel can be used for reading and writing.

 Creating and maintaining a first-in first-out queue FIFO pair column is accomplished by creating and maintaining two lists of FIFO pairs, the first list is used to arrange the list of cached blocks in use, and second A list is an empty block used to arrange uncached data or a reusable block list ( unused list) from which data has been fetched.

 Before the read/write distribution module caches data to the corresponding channel, the data channel module first initializes two lists, that is, sets the used list to null, and allocates a certain number of cache blocks to the unused list one by one.

When the read/write distribution module is to buffer data to the corresponding channel, issue a data cache request to the data channel module, and return a data readable indication after receiving the normal cache response returned by the data channel module; After receiving the data readable instruction, the interface sends a data read request to the data channel module, and obtains corresponding data by reading the normal response of the data returned by the data channel module; after receiving the data cache request, the data channel module receives the data cache request If it is determined that the unused list is not empty, the data carried in the request is cached in the first cache block of the unused list, and the first cache block is moved into the last item of the used list, and then the read-write distribution module is Return to the normal cache response; if it is judged that the unused list is empty, wait until the unused list is not empty and wait for no timeout, continue Data cache and its subsequent operations, and return a normal cache response; if waiting for timeout, return an exception cache response to the read-write distribution module; the read-write distribution module passes the exception cache response to the application interface; the data channel module receives the data read When the request is fetched, if it is judged that the used list is not empty, the data read from the first cache block in the used list is carried in the normal response of the data returned to the application interface, and the first item is The cache block is moved to the last item of the unused list; if it is judged that the used list is empty, it waits until the used list is not empty and waits for no timeout, continues data reading and subsequent operations, and returns a normal response of the data reading; If waiting for a timeout, return a data read exception response to the application interface.

As shown in FIG. 2, a flow chart of data read/write distribution operation of the mobile terminal multimedia broadcast driver interface of the present invention is performed by the application program interface when the upper layer application needs to read and write data, and includes the following steps:

 210: Instantiate a multiplexing frame channel, a control information uplink channel, and a control information downlink channel respectively;

220: Determine whether it is a read operation, if yes, go to step 230, otherwise go to step 250;

 230: Calling the read interface to read the multimedia broadcast data;

 240: Separating the read data according to the protocol, and distributing the separated multiplex frame payload and the uplink control information to the multiplexing frame channel and the control information uplink channel, respectively, and then ending the process;

 The protocol here, for example for the CMMB system, is expressed by multiplexing the information in the frame header. Other multimedia broadcasting systems will also have corresponding protocol statements, which are no longer described.

 250: Obtain downlink control information data to be written by the application from the downlink channel;

 260: Call the write interface, send control information to the data bus, and then end the process.

The multiplexed frame payload and the uplink control information are separately distributed to the multiplexed frame channel and the control information uplink channel, which are implemented by the initialization and write operation flow shown in FIG. 3, where the process includes The following steps:

 301: determining whether the write operation needs to be initialized, if yes, executing step 302, otherwise executing the step

305; 302: Create a used list and an unused list of the FIFO pair column, and set the used list to be empty; 303: add the allocated cache block one by one to the unused list;

 304: Applying a cache block from the unused list;

 305: Determine whether the unused list is empty, if yes, go to step 308, otherwise go to step 306; 306: write data to the first cache block in the unused list, and move the first cache block to the last one of the used list. Item

 307: Set the normal return code, and return;

 308: The write data process is blocked, waiting;

 309: Determine whether the waiting timeout occurs, if yes, go to step 310, otherwise go back to step 305; 310: Set the abnormal return code, and return.

When the above process returns through the normal return code, the application program interface performs the reading of the multiplexed frame payload data or the uplink control information through the flow of the data channel read operation shown in FIG. 4, including the following steps:

 401: Determine whether the used list of the corresponding data channel is empty, if yes, go to step 404, otherwise go to step 402;

 402: Take the first cache block in the used list, and read the data and move the first cache block to the last item of the unused list;

 403: Set the normal return code, and return;

 404: The read data process is blocked, waiting;

 405: Determine whether the waiting timeout is performed, if yes, go to step 406, otherwise return to step 401 to execute;

406: Set the exception return code and return.

In summary, the multimedia broadcast driver interface of the mobile terminal provides a unified interface for different types of terminal chips by separating the multiplexing frame from the control information, and simplifies by simplifying the logic of the upper application. The development process and shortened the development cycle. And because The production version of the application to be downloaded for the motherboard type is unified and the production cost is reduced.

It is a matter of course that the invention may be embodied in various other forms and modifications without departing from the spirit and scope of the invention.

Industrial Applicability The present invention can provide a uniform interface for different types of terminal chips, and at the same time, can simplify the development process and shorten the development cycle, thereby reducing the production cost of the product.

Claims

Claim A method for implementing a multimedia broadcast driver interface of a mobile terminal, comprising: configuring a logical interface between a bottom read interface of the terminal and an upper application interface; and the application needs to read the multimedia broadcast stored by the terminal Data, the multimedia broadcast data read from the read interface is separated from the payload data and the control information by the logical interface, and respectively cached to different channels, and the application is passed through the application program interface. Read. The method according to claim 1, wherein the logical interface buffers the separated payload data into a payload data channel, and buffers the separated control information into an uplink control information channel. The method according to claim 1 or 2, wherein the logical interface is further connected to a write interface of the bottom layer of the terminal, and when the application needs to write control information to the terminal, The application program interface buffers the control information to be written to the downlink control information channel, and then sends the control information read from the downlink control information channel from the write interface to the On the data bus of the terminal. The method according to claim 1, wherein the logical interface separates the payload data from the control information according to a protocol agreed by the terminal and a corresponding multimedia broadcast system. The method according to claim 3, wherein the payload data channel and the uplink control information channel in the logical interface are respectively created and maintained by a first-in first-out FIFO pair column The example and the second instance are implemented; or the downlink control information channel in the logical interface is implemented by creating and maintaining a third instance of the FIFO pair column; wherein the payload data channel is used for read-only The uplink control information channel or the downlink control information channel is used for reading and writing. 6. The method according to claim 5, wherein the FIFO pair column is implemented by using a first cache list and a second cache list; and the first cache list is used to arrange a cache block in use of the cached data. The second cache list is used to arrange empty blocks of uncached data or reusable blocks of data that have been taken away; Initializing the first cache list and the second cache list before buffering data of the corresponding channel, that is, setting the first cache list to be empty, and adding a certain number of cache blocks one by one to the first Two cache list;  When there is data to be cached to the corresponding channel, if the second cache list is not empty, the first cache block is requested in the second cache list for data caching, and the first cache block is Moving into the last item of the first cache list, and then the cache operation ends normally; if the second cache list is empty, waiting until the second cache list is not empty and waiting for no timeout, continuing the data The cache and its subsequent operations, the cache operation ends abnormally if waiting for a timeout;  When the data is to be read from the corresponding channel, if the first cache list is not empty, the first cache block is taken from the first cache list, and the first item is cached after the data is read. The block moves to the last item of the second cache list, and then the read operation ends normally; if the first cache list is empty, waiting until the first cache list is not empty and waiting for no timeout, proceeding The data read and its subsequent operations, the read operation ends abnormally if waiting for a timeout.  A mobile terminal multimedia broadcast driver interface, wherein the drive interface is a logical interface configured between a read interface of an underlying layer of the terminal and an application interface of an upper layer, where the logical interface is at least in an application. When the program needs to read the multimedia broadcast data stored by the terminal, triggering work by the application program interface, for separating the multimedia broadcast data read from the read interface, and downloading payload data and control information, respectively Cache to a different channel to be read by the application through the application interface.  8. The drive interface of claim 7, wherein the logical interface comprises an interconnected read-write distribution module and a data channel module, wherein:  The data channel module is configured to create and maintain at least a payload data channel and an uplink control information channel;  The read-write distribution module is connected to the read interface, configured to buffer the separated payload data into the payload data channel by using the data channel module, and pass the separated control information through the data. The channel module buffers to the upstream control information channel and then returns a data readable indication to the application interface. 9. The drive interface of claim 8 wherein said logical interface is still When the application writes control information to the terminal, triggering the work through the application program interface;  The data channel module is further configured to create and maintain a downlink control information channel;  The read/write distribution module is further connected to the bottom write interface of the terminal, and configured to cache, by the application program, the control information to be written into the terminal to the downlink control information channel by using the application program interface. Afterwards, the control information read from the downlink control information channel by the data channel module is sent from the write interface to the data bus of the terminal, and then the data is returned to the application interface. Write instructions.  The drive interface according to claim 9, wherein the payload data channel is used for read-only, and the uplink control information channel or the downlink control information channel is used for reading or writing; The load data channel, the uplink control information channel, and the downlink control information channel each include a respective first buffer area and a respective second buffer area, where:  The first buffer area is configured to read, by the data channel module, a data read request from the application interface when the one or more cache blocks in use of the cached data are arranged Cache the data of the block and carry the data in a normal response to the data returned to the application interface; meanwhile, the first cache block of the read data is used by the data channel module a last item placed in the second buffer area of the corresponding channel;  The second buffer area is configured to receive data from the read/write distribution module by the data channel module when an empty cache block with uncached data or a reusable cache block for which data has been taken is arranged When the request is cached, the data carried in the request is cached in the first cache block, and the first cache block of the write data is placed in the first cache area of the corresponding channel by the data channel module. The last one.