Method of processing traffic information and digital broadcast system
A digital broadcast transmitting/receiving system and a method for processing data are disclosed. The method for processing data may enhance the receiving performance of the receiving system by performing additional coding and multiplexing processes on the traffic information data and transmitting the processed data. Thus, robustness is provided to the traffic information data, thereby enabling the data to respond strongly against the channel environment which is always under constant and vast change.
Latest LG Electronics Patents:
- Method and apparatus for transmitting SCI in NR V2X groupcast communication
- Image/video coding method and apparatus
- Heat radiation module and electronic device comprising same
- Image display apparatus and operating method thereof
- Jig for via-hole processing, via-hole processing device, and via-hole processing method using same
More than one reissue application has been filed for the reissue of U.S. Pat. No. 8,473,807, including the present reissue application, continuation reissue application Ser. No. 14/552,652, filed Nov. 25, 2014, and continuation reissue application Ser. No. 14/534,912, filed Nov. 6, 2014, (now U.S. Pat. No. RE46,891, issued Jun. 12, 2018).
This application is a Continuation of application Ser. No. 12/542,161 filed Oct. 4, 2006 now U.S. Pat. No. 7,840,868 continuation Reissue of U.S. patent application Ser. No. 14/552,652, filed Nov. 25, 2014, which is a continuation reissue of U.S. patent application Ser. No. 14/534,912, filed Nov. 6, 2014, (now U.S. Pat. No. RE46,891, issued Jun. 12, 2018), which is a continuation reissue of U.S. patent application Ser. No. 12/840,878, filed on Jul. 21, 2010 (now U.S. Pat. No. 8,473,807, issued Jun. 25, 2013), which is a continuation of U.S. patent application Ser. No. 11/542,161 (now U.S. Pat. No. 7,840,868), issued on Nov. 23, 2011, which claims the benefit of Korean Patent Application Nos. 10-2005-0093639, filed Oct. 5, 2005; 10-2006-0027063, filed Mar. 24, 2006; 10-2006-0039117, filed Apr. 29, 2006; and 10-2006-0089736, filed on Sep. 15, 2006 and 10-2006-0027063 filed Mar. 24, 2006, all of which are hereby incorporated by reference for all purposes as if fully set forth herein.
BACKGROUND OF THE INVENTION1. Field of the Invention
The present invention relates to a digital broadcasting system, and more particularly, to a digital broadcast transmitting/receiving system and a method for processing traffic data.
2. Discussion of the Related Art
Presently, the technology for processing digital signals is being developed at a vast rate, and, as a larger number of the population uses the Internet, digital electric appliances, computers, and the Internet are being integrated. Therefore, in order to meet with the various requirements of the users, a system that can add video/audio data through a digital broadcasting (or television) channel so as to transmit diverse supplemental information needs to be developed.
Some users may assume that supplemental data broadcasting would be applied by using a PC card or a portable device having a simple in-door antenna attached thereto. However, when used indoors, the intensity of the signals may decrease due to a blockage caused by the walls or disturbance caused by approaching or proximate mobile objects. Accordingly, the performance of the received digital signals may be deteriorated due to a ghost effect and noise caused by reflected waves. Therefore, a system highly resistant to (or robust against) ghost effects and noise is required to be developed. Particularly, in order for the supplemental data to be used in portable and mobile broadcast receivers, a higher degree of resistance (or robustness) against channel interruption and noise is required.
The supplemental data are generally transmitted by a time-division method through the same channel as the MPEG video/audio data. However, with the advent of digital broadcasting, ATSC VSB digital television receivers that receive only MPEG video/audio data are already supplied to the market. Therefore, the supplemental data that are transmitted through the same channel as the MPEG video/audio data should not influence the conventional ATSC VSB receivers that are provided in the market. In other words, this may be defined as ATSC VSB compatibility, and the supplemental data broadcast system should be compatible with the ATSC VSB system. Herein, the supplemental data may also be referred to as enhanced data or EVSB data. Furthermore, as the number of possessed automobiles (or cars) is in constant increase, and with the influence of the working-5-days-a-week policy (which eventually leads to an increase in the usage of cars), the need for traffic information is also increasing accordingly.
SUMMARY OF THE INVENTIONAccordingly, the present invention is directed to a digital broadcast transmitting/receiving system and a method for processing data that substantially obviate one or more problems due to limitations and disadvantages of the related art.
An object of the present invention is to provide a digital broadcast system and a method for processing data that can be compatible to the ATSC VSB system, that is suitable for transmitting enhanced data, and that is resistant to and robust against noise.
Another object of the present invention is to provide a digital broadcast transmitting/receiving system and a method for processing data that can effectively receive and transmit traffic information by applying the traffic information data as the enhanced data.
Another object of the present invention is to provide a digital broadcast transmitting/receiving system and a method for processing data that can enhance the receiving performance of the receiving system by performing additional coding on the traffic information data and transmitting the processed data.
A further object of the present invention is to provide a digital broadcast transmitting/receiving system and a method for processing data that can enhance the receiving performance of the receiving system by multiplexing the known data, which correspond to data known in advance according to an agreement between the transmitting system and the receiving system, and the traffic information data.
Additional advantages, objects, and features of the invention will be set forth in part in the description which follows and in part will become apparent to those having ordinary skill in the art upon examination of the following or may be learned from practice of the invention. The objectives and other advantages of the invention may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
To achieve these objects and other advantages and in accordance with the purpose of the invention, as embodied and broadly described herein, a digital broadcast transmitter according to an embodiment of the present invention includes a traffic information message generator, a pre-processor, a multiplexer, a trellis encoder, and a transmitter.
The traffic information message generator may generate a traffic information message including status information, which includes at least one of information on traffic circulation, prediction information on the traffic circulation, and additional information, and location information associated with the status information. The pre-processor may pre-process traffic information data including the traffic information message by encoding the traffic information data and by generating a traffic information data packet including the encoded traffic information data and known data.
The multiplexer may multiplex the traffic information data packet with one or more main audio and video (AV) data packets. The trellis encoder may have at least one memory and trellis-encoding the multiplexed data packets, the at least one memory being initialized by initialization data when data outputted from the multiplexer correspond to a beginning of a known data sequence. The data transmission unit may insert synchronization data into the trellis-encoded data, modulating the trellis-encoded data having the synchronization data, and transmitting the modulated data.
In other aspect of the present invention, a digital broadcast transmitter may include a traffic information message generator, a pre-processor, a multiplexer, a post-processor, a data encoding and interleaving unit, a trellis encoder, and a transmitter.
The traffic information message generator may generate a traffic information message including status information, which includes at least one of information on traffic circulation, prediction information on the traffic circulation, and additional information, and location information associated with the status information. The pre-processor may pro-process traffic information data including the traffic information message by encoding the traffic information data for at least one of error correction and error detection and by generating a traffic information data packet including the encoded traffic information data and known data. The multiplexer may multiplex the traffic information data packet with one or more main audio and video (AV) data packets. The post-processor post-processing the multiplexed data by encoding only traffic information data included in the multiplexed data with a coding rate of G/H, wherein G and H are positive integers and G is less than H. The data encoding and interleaving unit may add first parity data into the post-processed data and interleave the post-processed data having the first parity data. The trellis encoder may have at least one memory and trellis-encoding the interleaved data, the at least one memory being initialized by initialization data when data outputted from the data encoding and interleaving unit correspond to a beginning of a known data sequence. The data transmission unit may insert synchronization data into the trellis-encoded data, modulating the trellis-encoded data having the synchronization data, and transmitting the modulated data.
In another aspect of the present invention, a digital broadcast transmitter may include a traffic information message generator, a pre-processor, a multiplexer, a data encoding and interleaving unit, a post-processor, a trellis encoder, and a transmitter.
The traffic information message generator may generate a traffic information message including status information, which includes at least one of information on traffic circulation, prediction information on the traffic circulation, and additional information, and location information associated with the status information. The pre-processor may pre-process traffic information data including the traffic information message by encoding the traffic information data for at least one of error correction and error detection and by generating a traffic information data packet including the encoded traffic information data and known data. The multiplexer may multiplex the traffic information data packet with one or more main audio and video (AV) data packets. The data encoding and interleaving unit may add first parity data into the multiplexed data and interleave the multiplexed data having the parity data. The post-processor may post-process the interleaved data by coding only traffic information data included in the interleaved data with a coding rate of G/H, wherein G and H are positive integers and G is less than H. The trellis encoder having at least one memory and trellis-encoding the post-processed data, the at least one memory being initialized by initialization data when data outputted from the post-processor correspond to a beginning of a known data sequence. The data transmission unit may insert synchronization data into the trellis-encoded data, modulating the trellis-encoded data having the synchronization data, and the transmitting the modulated data.
In another aspect of the present invention, a method of processing traffic data in a digital transmitter may include generating a traffic information message including status information, which includes at least one of information on traffic circulation, prediction information on the traffic circulation, and additional information, and location information associated with the status information, generating at least one system information table required for decoding the traffic information message, and multiplexing the traffic information message and the system information table.
In another aspect of the present invention, a digital broadcast transmitter may include a traffic information message generator, a system information generator, and a multiplexer.
The traffic information message generator may generate a traffic information message including status information, which includes at least one of information on traffic circulation, prediction information on the traffic circulation, and additional information, and location information associated with the status information. The system information generator may generate system information required for decoding a traffic information message. The multiplexer may multiplex the traffic information message and the system information.
In another aspect of the present invention, a data structure may include system information required for decoding a traffic information message including status information, which includes at least one of information on traffic circulation, prediction information on the traffic circulation, and additional information, and location information associated with the status information, the system information comprising a traffic information table which includes at least one of a traffic information application identifier, a service component identifier, and service information.
In another aspect of the present invention, a method of processing traffic information data in a digital broadcast receiver may include receiving traffic information data including a traffic information message and system information, demultiplexing the traffic information message and the system information from the traffic information data, and decoding the traffic information message using the system information, thereby extracting status information, which includes at least one of information on traffic circulation, prediction information on the traffic circulation, and additional information, and location information associated with the status information.
In a further aspect of the present invention, a digital broadcast receiver may include, a demodulator, a data demultiplexing and decoding unit, a data storage, and an application manager.
The demodulator may demodulate traffic information data including a traffic information message and system information and performing error correction to the demodulated data. The data demultiplexing and decoding unit may demultiplex the traffic information message and system information from the error-corrected data and decode the demultiplexed traffic information message using the system information. The data storage may store the system information and the decoded traffic information message. The application manager may provide a traffic information service to a user using the stored traffic information message by extracting status information, which includes at least one of information on traffic circulation, prediction information on the traffic circulation, and additional information, and location information associated with the status information.
It is to be understood that both the foregoing general description and the following detailed description of the present invention are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiments of the invention and together with the description serve to explain the principle of the invention. In the drawings:
Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. In addition, although the terms used in the present invention are selected from generally known and used terms, some of the terms mentioned in the description of the present invention have been selected by the applicant at his or her discretion, the detailed meanings of which are described in relevant parts of the description herein. Furthermore, it is required that the present invention is understood, not simply by the actual terms used but by the meaning of each term lying within.
In the present invention, the known data refer to a set of data known in advance according to an agreement between a transmitting system and a receiving system. The main data refer to a set of data that can be received by a conventional receiving system. Both known data and main data may include video data and/or audio data. Also, in the present invention, the enhanced data may refer to data including information, such as a program execution file, stock information, traffic information, and so on. The enhanced data may also include video data and/or audio data. Such enhanced data may include, traffic information, data for providing data service, system information for ground (or terrestrial) wave broadcasting such as PSI and/or PSIP, system information for cable broadcasting such as out of band system information (OOB-SI), supplemental data configured of diverse Java language or HTML language for data services providing a wide range of applications, audio data, and video data. The enhanced data may also include various control software for controlling the receiver, and meta data that are configured of an XML language, for example, in order to provide diverse information to the user.
In the description of the present invention, traffic information data will be applied for the enhanced data, so as to be transmitted and received. A road searching service and a traffic information providing service according to the present invention may be applied to a variety of digital broadcast standards. Representative examples of the digital broadcast standards are a European Digital Audio Broadcasting (DAB) service based on the Eureka-147 [ETSI EN 300 401], a Digital. Video Broadcasting-Terrestrial (DVB-T) service provided in Europe, a Digital Video Broadcasting-Handheld (DVB-H) service also provided in Europe, a Media Forward Link Only (FLO) service provided in the United States, and a Digital Multimedia Broadcasting (DMB) service that is provided in the Republic of Korea. The DMB service of the Republic of Korea is classified into a Terrestrial Digital Multimedia Broadcasting (T-DMB) service based on the Eureka-147 and a Satellite Digital Multimedia Broadcasting (S-DMB) service using satellite communication.
Herein, the traffic information includes information on public transportation, congestion and/or travel time, road traffic, emergency events and situation, and so on. The traffic information also includes information associated with all types of transportation means including train, ship (or cruiser), airplane, and so on. Furthermore, the traffic information may also include information on factors that may influence traffic, such as travel information, information parking facilities, weather information, environmental pollution information, and so on. Most particularly, although the congestion and/or travel time (hereinafter referred to as “CTT”) information is given as an example of the present invention, any other information type may be applied herein. Furthermore, as long as the term indicates a particular function, the terms used in the present invention are not limited only to the ones used in the description set forth herein.
The term “traffic status” is indicative of a road congestion status (i.e., a flow status), however, it is not limited to the above-mentioned road congestion status and can be applied to similar examples as necessary. For the convenience of description and better understanding of the present invention, the term “traffic status” is referred to as a Congestion and/or Travel. Time Information (CTT) status. The above-mentioned CTT status includes CTT status information, and CTT status prediction information, additional information, and so on. The term “section” or “link” is indicative of a specific area of roads. However, it is not limited to the above-mentioned meanings and may be applied to other similar meanings as necessary.
The traffic information service according to the present invention is provided to the users by a receiver having only one or none of an electronic map and a GPS mounted therein in the form of at least one of a text, a voice, a graphic, a still image, and a motion picture. The traffic information data are configured and transmitted by traffic information message units. More specifically, the traffic information message is the smallest unit for transmitting the traffic information. Herein, information on a single traffic information application is included in a traffic information message. In the present invention, the term “Transport Protocol Expert Group (TPEG)” will be used on the traffic information for simplicity. Furthermore, as described above, as long as the term indicates a particular function, the terms used in the present invention are not limited only to the ones used in the description set forth herein.
The traffic information application corresponds to the highest hierarchy within an ISO/OSI protocol stack. Each traffic information application is assigned with a unique identification number, which is referred to as an application identification (AID). Each time a new application is developed and created, a new application identification is assigned. For example, each of the congestion and/or travel time (CTT) information, the road traffic message (RTM), the public transport information (PTI), and so on, is a traffic information application that is given unique application identification. The traffic information data correspond to a stream form including various traffic information messages. Herein, the traffic information messages correspond to at least one application.
Traffic information message generator (not shown in figure) generating a traffic information message can be a broadcast station. For simplicity of the description of the present invention, the traffic information message generator is referred to as a traffic information providing server. The traffic information message generator construct in a traffic information message unit traffic congestion information collected from various sources (e.g., operator input, or information received from another server or probe cars through a network).
At this point, each traffic information message has the same container configuration, which may be referred to as a traffic information (or TPEG) message container. The CTT message container described herein corresponds to one of the traffic information message containers. More specifically, the CTT message container according to the present invention, which transmits the CTT message, includes a CTT message management container 102, a CTT-status container 104, and a TPEG-location container 106.
The above-mentioned CTT message management container 102 includes a message identification information and date and time information, and uses the message identification information and the date and time information as management information of the information received by the receiving system. The message ID information requisite for the message includes a message identifier (MID) and a version number (VER). In this case, the message ID (MID) is indicative of an identifier of a single message associated with individual status of a service component. The MID according to the present invention gradually increases the MID number from 0 by a predetermined number “1” at a time. If the MID value reaches the maximum value “65535”, the maximum value “65535” is initialized to zero. The version number (VER) is indicative of a sequential number for identifying successive messages having a single message ID. The version number according to the present invention may be determined to be any one of 0 to 255, and it should be noted that the version number is sequentially increased in the range from 0 to 255.
The date/time information contained in the CTT message management container 102 according to the present invention does not include start and end times, a message deletion time, and schedule information in the traffic congestion information, differently from other information (i.e., an incident and unexpected accident (road traffic message), and a public transportation status) of the TPEG message.
The congestion and travel time information is not like the unexpected accident varying with time, and includes current congestion and travel time information of each road, therefore it is sequentially transmitted.
Specifically, a message generation time is based on a real message generation time. A message transmission time among the message generation time is based on a transmission time of a corresponding message, and is contained in all messages. The message generation time and the message transmission time are required for a receiving side to manage received messages.
The above-mentioned CTT status container 104 includes a plurality of CTT components (ctt_component), each of which includes CTT status information. The CTT status component (ctt_component) includes CTT status information (ID “80 hex”), CTT status prediction information (ID “81 hex”), and additional information (ID “8A hex”), etc. The CTT status component (ctt_component) to which the identifier “80 hex” is assigned includes a status component (status_component). The status component (status_component) includes an average link speed, a travel time, a link delay time, and a congestion type.
A CTT component (ctt_component) to which the identifier “81 hex” is assigned includes a prediction status component (prediction_status_component) for transmitting. CTT prediction information. The prediction status component (prediction_status_component) includes an average link speed prediction, a link travel time prediction, and prediction status information associated with a congestion change. A CTT component (ctt_component) to which the identifier “8A hex” is assigned includes additional information of basic status information of the CTT information or of prediction status information. The status component including the above-mentioned additional information is formed on the condition that the presence of the additional information is determined.
The TPEG location container 106 includes a plurality of TPEG location components (tpeg_loc_component) equipped with link location information. In this case, the location information may be information based on a coordinates system and information of a predetermined link ID. Each TPEG location container (tpeg_loc_container) includes at least one location coordinates component (location_co-ordinates_component) to which an ID “00 hex” is assigned. The above-mentioned CTT component includes information of a link as a target object both the CTT status information and the CTT status prediction information. The above-mentioned link information includes a road-type list, a WGS 84 indicative of location coordinates, a link shape point, a link ID, link description, and so on.
Referring to
The traffic congestion information message component includes an ID field 222, a byte-unit's component data length field 224, and a corresponding data field 226.
Referring to
In this case, the traffic-flow status class 232 describes information of the degree of traffic-flow of vehicles for each link, the traffic-flow status prediction class 234 describes information of the degree of traffic-flow of vehicles for each link. The additional information class 236 describes traffic congestion information for each TPEG message, and additional- or auxiliary-information associated with the traffic congestion information, and is configured in the form of text data differently from other classes.
Components contained in each class will hereinafter be described with reference to
Referring to
Each status component (status_component) includes the link average speed, the link-travel time, the link delay time, and/or the link congestion type, which are configured in the forms of
Referring to
As shown in
As shown in
As shown in
Referring to
Each prediction status component (prediction_status_component) includes the above-mentioned prediction link average speed of
As shown in
As shown in
As shown in
Referring to
For example, if the status component(“status_component(03)”) equipped with the congestion type information shown in
If the congestion type for each link shown in
If the degree of traffic status is not defined in the form of code tables, a CTT component 8A including additional information may be used for the above-mentioned situation.
For another example, if a speed change information field contained in the prediction status component(“prediction_status_component(02)”) equipped with the link speed change information of
However, if the link speed change information is not defined by the above-mentioned code tables, the additional information component may be used for the above-mentioned situation. In more detail, video data captured by a camera capable of capturing a traffic status for each link is contained in an additional information component, such that the additional information component equipped with the video data may be transmitted to a user or users. In this case, the video data may include moving images and still images.
For still another example, if a famous restaurant or a historical place or theater is contained in a specific link indicating the status information, information associated with the above-mentioned places may also be contained in the CTT component (8A).
For still another example, the CTT component (8A) equipped with the additional information may include multimedia information, which includes text data, variety of video data, and variety of audio data. The multimedia information using the additional information component can be provided via a unidirectional service (e.g., a broadcast service), however, it can be more efficiently used for a communicational service associated with either a unique. IP address of a wired/wireless LAN or a unique code (e.g., a CDMA).
For example, if a user defines his or her interest area or place (e.g., a POI (Point Of Interest)), the additional information component may also be provided to the user using multimedia information associated with the above-mentioned interest area or place.
In more detail, if the user selects a movie theater, he or she may recognize title information of currently-played movies by referring to the above-mentioned multimedia information, may buy a ticket of a desired movie in advance by referring to the same, and may recognize the number of unsold tickets, a current parking status of a parking lot of the movie theater, and the number of vehicles capable of entering the parking lot using audio (video) data, video data, or text data.
Also, if the user selects a desired restaurant, he or she may recognize a menu of the selected restaurant, its price, the number of remaining tables using moving images, still images, audio data or text data by referring to the multimedia information.
For still another example, the CTT component(“ctt_component(8A)”) may include additional information associated with detailed location data. For example, the CTT component (8A) may include not only longitude- and latitude coordinates but also angle or height information incapable of being expressed by coordinates. By means of the above-mentioned information, subway route map information, underground passage information, and overpass information may also be provided to the user. Otherwise, a cubic map (e.g., a 3D or 4D map) may also be provided to the user as necessary.
As shown in
As can be seen from
Referring to
Referring to
Referring to
Referring to
Referring to
In this case, the above-mentioned vertex allows a terminal for receiving traffic information to recognize either coordinates or a link shape designated by a link ID, such that the above-mentioned terminal can express the recognize coordinates or link shape in the form of graphic data using the vertex. The vertex is latitude/longitude information defined by the WGS 84 format. However, it should be noted that the scope of the above-mentioned term “vertex” can also be applied to similar terms or other examples as necessary.
Referring to
The traffic-information receiving terminal unequipped with an electronic map can more realistically display the road shape on the basis of a current location on the screen.
Therefore, the number of vertexes has a scale (e.g., a scale of 10000:1) lower than that of an electronic map stored in a disc. The vertex component (00) may include the number of vertexes to visually display a desired road on a VGA or QVGA. For example, the number of vertexes may be determined to be equal to or less than 23.
Referring to
Referring to
Referring to
A specific ID “00 hex” is allocated to the descriptor component(“descriptor_component(00)”) equipped with direction type information, such that the descriptor component (“descriptor_component(00)”) indicates a direction type using codes defined in the table (loc02). For example, the descriptor component (“descriptor_component(00)”) may indicate whether a current direction is the east, the west, or the opposite direction.
The above described traffic information data require a more stable receiving performance than the general audio and/or video data, i.e., the main data. In case of the main data, small errors that cannot be noticed by the eyes and ears of a user are not problematic. Conversely, in case of the traffic information data, even a 1-bit size error can cause a serious problem. Therefore, the traffic information data are processed with an additional coding process, which is then multiplexed with the main data and transmitted. Thus, robustness is provided to the traffic information data, such as the CTT data, thereby enabling the data to respond strongly against the channel environment which is always under constant and vast change. At this point, system information is required in order to extract the traffic information data from the channel through which the traffic information data are transmitted and, then, to decode the extracted traffic information data. In some cases, the system information is referred to as service information. The system information may include channel information, event information, and so on.
In the preferred embodiment of the present invention, program specific information/program and system information protocol (PSI/PSIP) is applied as the system information. However, the present invention is not limited only to the example given in the description set forth herein. More specifically, if the system information corresponds to a protocol being transmitted in a table format may be applied to the present invention regardless of name of the system information. The PSI is an MPEG-2 system standard defined for classifying the channels and the programs. And, PSIP is an advanced television systems committee (ATSC) standard having channels and programs that can be classified.
Herein, the PSI may include a program association table (PAT), a conditional access table (CAT), a program map table (PMT), and a network information table (NIT). More specifically, the PAT corresponds to a special information that can be transmitted by a packet having a packet identification (PID) of ‘0’. The PAT transmits the corresponding PID information of the PMT and the corresponding PID information of the NIT for each program. The CAT transmits information on a paid broadcast system that is used by the transmitting end. The PMT transmits. PID information of a transport stream packet to which the program identification number and separate bit sequences, such as video data and audio data configuring the corresponding program, are transmitted. The PMT also transmits. PID information to which the PCR is transmitted. The NIT transmits information of the actual transmission network.
On the other hand, the PISP may include a virtual channel table (VCT), a system time table (STT), a rating region table (RRT), an extended text table (ETT), a direct channel change table (DCCT), a direct channel change selection code table (DCCSCT), an event information table (EIT), and a master guide table (MGT). The VCT transmits information on the virtual channel such as channel information for selecting the channel and a packet identification (PID) for receiving audio data and/or video data. More specifically, by parsing the VCT, PIDs of the audio data and video data corresponding to the broadcast program that is being transmitted through the channel along with the channel name, channel number, and so on. The STT transmits information on the current weather and time, and the RRT transmits information on the region and deliberation committee for program rating. The EIT transmits information on the events of a virtual channel (e.g., program title, program start time, etc.). The DCCT/DCCSCT transmits information associated with automatic channel change, and the MGT transmits version and PID information of each table within the PSIP.
Each table within the above-described PSI/PSIP includes a basic unit referred to as a “section”, and at least one or more sections are combined to configure a table. For example, the VCT may be divided into 256 sections. Herein, a single section may carry a plurality of channel information. However, the information on the virtual channel is not divided into two or more sections. An example of multiplexing and transmitting a traffic information message and a table associated with a system information is given in the description of the present invention.
The TS packet is configured of a header part and a payload part. Herein, the header part includes information indicating the beginning of the data and packet identification (PID) identifying the data part corresponding to the payload part. And, the payload part includes a traffic information message that is intended to be transmitted. At this point, the PID within the header part may either correspond to an identifier that can identify the data carried by the payload part as the traffic information message among the enhanced data, or correspond to an identifier that can identify the enhanced data. In case the PID of the header can identify the traffic information message, the traffic information message may be extracted from the TS packet. On the other hand, in case the PID of the header can identify the enhanced data, all TS packets identified as the enhanced data are received. Thereafter, the traffic information message is extracted from the received enhanced data. Furthermore, the Ts packet which carries the traffic information message may correspond either to a packetized elementary stream (PES) type or to a section type. In other words, either a PES type traffic information message may be configured as the TS packet, or a section type traffic information message may be configured as the TS packet.
An example of the traffic information message being transmitted as the section type will be described in the present invention. In this embodiment of the present invention, the traffic information message is included in a digital storage media-command and control (DSM-CC) section, and the DSM-CC section is then configured as a 188-byte size TS packet. Herein, the identifier of the TS packet configuring the DSM-CC section is included in a data service table (DST). When transmitting the DST table, ‘0x95’ is assigned as a stream_type field value within a service location descriptor of either the PMT or the VCT. More specifically, in the receiving system, when the stream_type field value of the PMT or VCT is equal to ‘0x95’, this indicates that data broadcasting (i.e., enhanced data) including the traffic information data is being received. At this point, the traffic information data may be transmitted by a data carousel method. Herein, the data carousel method refers to repeatedly transmitting the same data periodically.
Meanwhile, the PSI/PSIP generator 312 is an example of a system information generator. The table that may be created by the PSI is at least one of PMT, PAT, CAT, and NIT. And, the table that may be created by the PSIP is at least one of VCT, STT, RRT, ETT, DCCT, DCCST, EIT, and MGT. The table created by the PSI/PSIP generator 312 includes a system information so that the receiving system may parse and decode the traffic information message. At this point, the receiving system may use only the tables within the PSI, or only the tables within the PSIP, a combination of tables within both the PSI and the PSIP, so as to parse and decode the traffic information message. At least the PAT and PMT of the PSI and at least the VCT of the PSIP is required for parsing and decoding the traffic information message. For example, the PAT may include the system information transmitting the traffic information message and the PID of the PMT corresponding to the traffic information message (or program number). The PMT may include the PID of the TS packet transmitting the traffic information message. The VCT may include the PID of the TS packet transmitting the information of the virtual channel, which transmits the traffic information message, and the traffic information message.
Also, the present invention includes supplemental information associated with traffic information specifically indicating to which application the traffic information message belonged and information specifically indicating which information is included. The supplemental information associated with the traffic information may include service component identification information, application identification information, service information, and so on. The service information may include service name, service description, service logo, subscriber information, free text information, help information, and so on. Furthermore, such supplemental information may be included in a particular table within the PSI/PSIP either in a descriptor format or in a field format.
For simplicity of the description of the present invention, a descriptor including the supplemental information associated with the traffic information that is included in a particular table within the PSI/PSIP is referred to as a traffic information descriptor. Herein, the traffic information descriptor may also be referred to as a TPEG service descriptor. As described above, the term “traffic information descriptor” is only an example given to facilitate the understanding of the present invention. Therefore, any other term having the same function as the traffic information descriptor may also be applied herein. Moreover, in the description of the present invention, the particular table including the traffic information descriptor is defined as a traffic information providing table. Furthermore, the particular table including the traffic information descriptor is defined as a system information (SI) table wherein the traffic information descriptor is included.
More specifically, the Descriptor_tag field is an 8-bit field, which is given a value that can uniquely identify the TPEG service descriptor. In the example of the present invention, a value of 0xAC is given as the tag value of the TPEG service descriptor. However, this is only an example provided for an easier understanding of the present invention. Depending upon the design of the system designer, other kind of unused tag values may be allocated to the Descriptor_tag field. The Descriptor_length field is an 8-bit field, which indicates in byte units the length starting from the Descriptor_length field to the end of this field.
The Service_component_ID (SCID) field is also an 8-bit field, which indicates a value that can uniquely identify the service component within a service. The SCID field may be decided by the service provider. Herein, a single service component substantially corresponds to a single channel within the TPEG stream. The Application_ID field is a 16-bit field, which indicates a value that can uniquely identify each application. More specifically, a unique application identifier (AID) is assigned to each traffic information application, and a new AID is allocated whenever a new application is developed (or created).
The service information field within the repetition statement may include a Service_name field, a Service_description field, a Service_logo field, a Subscriber_information field, a Free_text_information field, and a Help_information field. The length of each field within the service information field is variable and is indicates in the form of at least one of a text sequence, numbers, and graphics. The Service_name field indicates the name of a service, which allows the user to identify a particular service. For example, a service name such as ‘TPEG service of broadcast company A’ may be included when the broadcast program is being transmitted. The Service_description field indicates a detailed description of the corresponding service. This field is for describing the service contents in more detail. For example, a service named “suburban public transportation information in the southern urban area” may be included and transmitted. The Service_logo field indicates a service logo, so as to allow a service or a service provider to be identified visually. The service logo is generally transmitted in a bitmap format or any other image format.
The Subscriber_information field indicates the subscriber information. For example, information such as a user fee for limited (or restricted) service components and payment information may be included and transmitted. The Free_text_information field indicates additional information that is to be transmitted to the user. For example, information on an interruption (or suspension) of a service, cancellation of a particular information, and so on, may be included and transmitted. And, the Help_information field indicates help information which the user can refer to. For example, information such as Internet addresses, telephone numbers, and so on may be included herein and transmitted.
The order, location, and meaning of each field shown in
More specifically, in the description of the present invention, an example of applying the PMT of the PSI and the VCT of the PSIP as the traffic information providing table. This indicates that the supplemental information associated with the traffic information may be transmitted through the PMT and/or VCT of the descriptor or the field. Similarly, when supplemental information associated with the traffic information is described in a field format, it is apparent that the fields can be applied to at least one of the tables of the PMT of the PSI and the VCT of the PSIP. Herein, the process of including the PMT and/or the VCT in the traffic information descriptor may be either mandatory or optional. Furthermore, whether the PMT and/or the VCT are/is mandatorily or optionally included is also merely an example of the present invention. Accordingly, the example does not limit the scope and spirit at the present invention.
For example, AC-3 audio descriptor is given a value of 0x81 as the descriptor tag value and must indicate that it is used in the PMT and EIT. Furthermore, the TPEG service descriptor according to the example of the present invention is given a value of 0xAC the descriptor tag value and is marked as ‘mandatory (M)’ on the PMT and VCT. The above-described example is only proposed to simplify the description of the present invention. The TPEG service descriptor may also be marked as ‘mandatory (M)’ or ‘optional (O)’ on at least one of the PMT and VCT. The 0xAC value given as the TPEG service descriptor tag value is also only proposed as an example for facilitating the understanding of the present invention. Accordingly, depending upon the design of the system designer, other unused tag values may also be assigned herein.
The VCT syntax further includes a first ‘for’ loop repetition statement that is repeated as much as the num_channels_in_section field value. The first repetition statement may include at least one of a short_name field, a major_channel_number field, a minor_channel_number field, a modulation_mode field, a carrier_frequency field, a channel_TSID field, a program_number field, an ETM_location field, an access controlled field, a hidden field, a service_type field, a source_id field, a descriptor_length field, and a second ‘for’ loop statement that is repeated as much as the number of descriptors included in the first repetition statement. Herein, the second repetition statement will be referred to as a first descriptor loop for simplicity. The descriptor descriptors( ) included in the first descriptor loop is separately applied to each virtual channel.
Furthermore, the VCT syntax may further include an additional_descriptor_length field, and a third ‘for’ loop statement that is repeated as much as the number of descriptors additionally added to the VCT. For simplicity of the description of the present invention, the third repetition statement will be referred to as a second descriptor loop. The descriptor additional_descriptors( ) included in the second descriptor loop is commonly applied to all virtual channels described in the VCT.
As described above, referring to
The version_number field indicates the version number of the VCT. The section_number field indicates the number of this section. The last_section_number field indicates the number of the last section of a complete. VCT. And, the num_channel_in_section field designates the number of the overall virtual channel existing within the VCT section. Furthermore, in the first ‘for’ loop repetition statement, the short_name field indicates the name of a virtual channel. The major_channel_number field indicates a ‘major’ channel number associated with the virtual channel defined within the first repetition statement, and the minor_channel_number field indicates a ‘minor’ channel number. More specifically, each of the channel numbers should be connected to the major and minor channel numbers, and the major and minor channel numbers are used as user reference numbers for the corresponding virtual channel.
A virtual channel number is assigned to the traffic information message according to the present invention, and the traffic information message may be transmitted through the assigned virtual channel. In this case, the short name field indicates the name of the virtual channel through which the traffic information message is transmitted. The major_channel_number/minor_channel_number field the number of the virtual channel through which the traffic information message is transmitted. The program_number field is shown for connecting the virtual channel having an MPEG-2 program association table (PAT) and program map table (PMT) defined therein, and the program_number field matches the program number within the PAT/PMT. Herein, the PAT describes the elements of a program corresponding to each program number, and the PAT indicates the PID of a transport packet transmitting the PMT. The PMT described subordinate information, and a PID list of the transport packet through which a program identification number and a separate bit sequence, such as video and/or audio data configuring the program, are being transmitted.
The source_id field indicates a program source connected to the corresponding virtual channel. Herein, a “source” refers a particular source such as a video image, data or sound. The value of the source_id field corresponds to a unique value within the transport stream, which transmits the VCT. In an example according to the present invention, the traffic information descriptor describing the supplemental information associated with traffic information (i.e., supplemental information associated with the CTT) is included in the first descriptor loop. As described above in the description of the VCT, it is apparent that anyone skilled in the art can apply the example given in the present invention to other tables.
According to the present invention, there are two different methods of defining the PID of the VCT, which includes the traffic information descriptor. Herein, the PID of the VCT is a packet identifier (PID) required for identifying (or distinguishing) the VCT from the other tables. In the first method, the PID of the VCT according to the present invention may be set to depend upon the MGT. In this case, the receiving system cannot directly identify (or verify) the plurality of tables of the PSIP or PSI. Therefore, the VCT can be read only after the PID defined by the MGT is checked. Herein, the MGT is a table defining the PID, size, version number, and so on, of the plurality of tables. In the second method, the PID of the VCT according to the present invention may be set to have a base PID value (i.e., a fixed PID value) that is independent from the MGT. Unlike the first method, the second method is more advantageous in that the VCT can be identified without having to verify every single PID of the MGT. Evidently, the agreement on the base PID should precede the transmitting system and the receiving system.
As described above, the PAT, PMT, VCT, MGT, DCCT, and so on, describing the system information and supplemental information associated with traffic information are generated by the PSI/PSIP generator 312. Herein, the PMT is provided to the first multiplexer 311, and the remaining tables excluding the PMT (i.e., PAT, VCT, MGT, DCCT, and so on) are provided to the second multiplexer 313. The first multiplexer 311 multiplexes the traffic information message, which includes information on the traffic information application that is to be transmitted (e.g., CTT application), with the PMT, which is generated from the PSI/PSIP generator 312, to a 188-byte transport stream (TS) packet. Thereafter, the multiplexed message and table are outputted to the second multiplexer 313. The second multiplexer 313 multiplexes the output of the first multiplexer 311 with the tables outputted from the PSI/PSIP generator 312 to a 188-byte transport stream (TS) packet. Subsequently, the multiplexed message and table are outputted for additional coding.
An example of providing the PMT to the first multiplexer 311 and providing the remaining tables to the second multiplexer 313 is proposed in the description of the present invention. However, the present invention may also be designed to have a single multiplexer by integrating the first multiplexer 311 and the second multiplexer 313. The traffic information data that are outputted from the multiplexer of
Hereinafter, the coding and transmitting processes of the traffic information data will be described in detail according to first, second, and third embodiments of the present invention. By performing the additional coding process on the traffic information data, robustness can be provided to the traffic information data, such as the CTT data. Thus, the data can respond swiftly and appropriately to the channel environment that undergoes fast and frequent change.
First EmbodimentIn the digital broadcast transmitting system having the above described structure, the main data are inputted to the packet multiplexer 402. On the other hand, the traffic information data are inputted to the E-VSB pre-processor 401, which performs additional coding processes so as to enable the traffic information data to respond quickly with robustness against noise and channel change. The E-VSB randomizer 421 of the E-VSB pre-processor 401 receives the traffic information data, thereby randomizing the received data and outputting the randomized data to the RS frame encoder 422. Herein, since the E-VSB randomizer 421 randomizes the traffic information data, the randomizing process of data randomizer 403 on the traffic information in a later process may be omitted.
The RS frame encoder 422 receives the randomized traffic information data and performs at least one of an error correction coding process and an error detection coding process on the received data. Accordingly, by providing robustness to the traffic information data, the data can scatter group error that may occur due to a change in the frequency environment. Thus, the data can respond appropriately to the frequency environment which is very poor and liable to change. The RS frame multiplexer 422 also includes a process of mixing in row units many sets of traffic information data each having pre-determined size. By performing an error correction coding process on the inputted traffic information data, the RS frame encoder 422 adds data required for the error correction and, then, performs an error detection coding process, thereby adding data required for the error detection process.
The error correction coding uses the RS coding method, and the error detection coding uses the cyclic redundancy check (CRC) coding method. When performing the RS coding process, parity data required for error correction are generated. And, when performing the CRC coding process, CRC data required for error detection are generated. More specifically, the RS frame encoder 422 identifies the traffic information data by units of a predetermined length (A). Then, a plurality of (A)-length units of traffic information data is grouped so as to form (or configure) a RS frame. Thereafter, an RS coding process is performed in at least one of a row direction and a column direction on the newly configured RS frame. In the present invention, the predetermined length unit (A) corresponds to 187 bytes.
If the inputted traffic information data correspond to a 188-byte unit. MPEG transport stream (TS) packet, the first MPEG synchronization byte is removed, so as to form a 187-byte unit packet. Herein, the MPEG synchronization byte is removed because all traffic information data packets are given the same value. The MPEG synchronization byte may also be removed during the randomizing process on the E-VSB randomizer 421. In this case, the process of removing the MPEG synchronization byte performed by the RS frame encoder 422 is omitted. More specifically, if the inputted traffic information data does not include a fixed byte that can be removed, or if the length of the inputted packet is not 187 bytes, the inputted traffic information data is distinguished by 187-byte units. Thereafter, a plurality of 187-byte units of traffic information data is grouped so as to form (or configure) a RS frame. Thereafter, an RS coding process is performed in at least one of a row direction and a column direction on the newly configured RS frame.
Depending upon the channel situation between the transmission and the reception, an error may be included in the RS frame. When such error occurs, the CRC data (or CRC code or CRC checksum) may be used for checking whether an error exists by each row unit. In order to generate (or create) the CRC checksum, the RS frame encoder 422 performs CRC coding on the RS-coded traffic information data. The CRC checksum created by the CRC coding process may be used for notifying whether a damage has occurred by an error while the traffic information data are being transmitted through a channel. In the present invention, error detection coding method other than the CRC coding method may be used. Alternatively, an error correction coding method may be used in order to enhance the overall error correction ability of the receiving end.
The traffic information data sets RS-coded and CRC-coded, as described above, are outputted to the E-VSB block processor 423. The E-VSB block processor 423 codes the RS-coded and CRC-coded traffic information data at a coding rate of G/H (wherein G and H are integers, and G<H) and then outputs the G/H-rate coded data to the group formatter 424. For example, if 1 bit of the input data is coded to 2 bits and outputted, then G is equal to 1 and H is equal to 2 (i.e., G=1 and H=2). Alternatively, if 1 bit of the input data is coded to 4 bits and outputted, then G is equal to 1 and H is equal to 4 (i.e., G=1 and H=4).
An example performing a coding process at a coding rate of 1/2 (also referred to as a 1/2-rate coding process) or a coding process at a coding rate of 1/4 (also referred to as a 1/4-rate coding process) on the traffic information data is given in the description of the present invention. More specifically, in case of performing the 1/2-rate coding process, the E-VSB block processor 423 receives 1 bit and codes the received 1 bit to 2 bits (i.e., 1 symbol). Then, the E-VSB block processor 423 outputs the processed 2 bits (or 1 symbol). On the other hand, in case of performing the 1/4-rate coding process, the E-VSB block processor 423 receives 1 bit and codes the received 1 bit to 4 bits (i.e., 2 symbols). Then, the E-VSB block processor 423 outputs the processed 4 bits (or 2 symbols). At this point, in case of performing the 1/4-rate coding process, the symbol coded at a 1/2 coding rate may be repeated twice so as to output 2 symbols, or the input data may be coded twice at a 1/2 coding rate so as to output 2 symbols.
The 1/4-rate coding process may provide more enhanced error correction ability, due to the higher coding rate as compared to the 1/2-rate coding process. For this reason, the data coded at a 1/4 coding rate by the group formatter 424 in a later process are allocated to locations (or positions) in which the channel may affect the performance. On the other hand, the data coded at a 1/2 coding rate are allocated to locations having better performance. Thus, a difference in performance may be decreased. The above-mentioned 1/2-coding rate and 1/4-coding rate are only exemplary embodiments proposed in the description of the present invention, and the coding rate may vary depending upon either the selection of the coded symbols or the number of repetition.
The group formatter 424 inserts the traffic information data outputted from the E-VSB block processor 423 in a corresponding area within a data group formed according to a pre-defined rule. Also, the group formatter 424 inserts various place holders related to data interleaving or known data sets to a corresponding area within the data group. At this point, the data group may be described by at least one hierarchical area. And, depending upon the characteristic of each hierarchical area, the data type being allocated to each area may also vary.
As described above, the head, body, and tail areas have been given as an example to simplify the description of the present invention. Additionally, in the example shown in
Assuming that the data group is allocated to a plurality of hierarchical areas, as shown in
For example, the traffic information data that are to be inserted in the body area are 1/2-rate coded by the E-VSB block processor 423, and such 1/2-rate coded traffic information data are inserted to the body area by the group formatter 424. Additionally, the traffic information data that are to be inserted in the head and tail areas are 1/4-rate coded by the E-VSB block processor 423. Herein, the 1/4-rate coding provides greater error correction performance as compared to 1/2-rate coding. Thereafter, 1/4-rate coded traffic information data are inserted to the head and tail areas by the group formatter 424. Alternatively, the traffic information data that are to be inserted in the head and tail areas may be coded by the E-VSB block processor 423 at a coding rate providing more efficient error correction performance. Subsequently, such coded traffic information data are inserted in the head and tail areas by the E-VSB block processor 423, or such coded data may be stored in a reserve area for future usage.
As shown in
The group formatter 424 either inserts the known data generated by a pre-decided method in a corresponding area, or inserts a known data place holder in a corresponding area so as to insert the known data in a later process. Moreover, a place holder for initializing the trellis encoder 407 is inserted in the corresponding area. For example, the initialization data place holder may be inserted in front of the known data sequence. The output of the group formatter 424 is inputted to the data interleaver 425. The data deinterleaver 425 performs an inverse process of the data interleaver on the data within the data group and the place holder outputted from the group formatter 424. And, then, the data deinterleaver 425 outputs the deinterleaved data to the packet formatter 426. More specifically, when the data within the data group and the place holder the configuration shown in
Among the deinterleaved and inputted data, the packet formatter 426 removes the main data place holder and the RS parity place holder that have been allocated for the deinterleaving process. Then, the packet formatter 426 groups the remaining portion of the input data and inserts the remaining data to the 4-byte MPEG header place holder in the MPEG header. Furthermore, when the known data place holder is inserted by the group formatter 424, the packet formatter 426 may insert the known data in the known data place holder. Alternatively, the known data place holder may be directly outputted without any modification for the replacement insertion in a later process.
Thereafter, the packet formatter 426 configures the data within the data group packet that is formatted as described above, as a 188-byte unit traffic information data packet. Then, the packet formatter 426 provides the configured 188-byte unit traffic information data packet to the packet multiplexer 402. The packet multiplexer 402 multiplexes the 188-byte traffic information data packet and the main data packet outputted from the packet formatter 426 according to a predefined multiplexing method. Then, the multiplexed packets are outputted to the data randomizer 403. The multiplexing method may be altered or modified by various factors in the design of the system.
In a multiplexing method of the packet multiplexer 402, a traffic information data burst section and a main data section are distinguished (or identified) along a time axis, then the two sections are set to be repeated alternately. At this point, in the traffic information data burst section, at least one of the data groups may be transmitted, and only the main data may be transmitted in the main data section. In the traffic information data burst section, the main data may also be transmitted. When the traffic information data are transmitted in the above-described burst structure, the digital broadcast receiving system receiving only the traffic information data may turn on the power only during the data burst section. Alternatively, in the main data section whereby only the main data are transmitted, the power is turned off during the main data section, thereby preventing the main data from being received. Thus, excessive power consumption of the digital broadcast receiving system may be reduced or prevented. As described above, the packet multiplexer 402 receives the main data packet and the data group, which is outputted from the packet formatter 426, and transmits the received packets in a burst structure.
When the inputted data correspond to the main data packet, the data randomizer 403 performs a randomizing process identical to that of the conventional randomizer. More specifically, the MPEG synchronization byte within the main data packet is discarded (or deleted). Then, the remaining 187 bytes are randomized by using a pseudo random byte generated from within the data randomizer 403. Subsequently, the randomized data bytes are outputted to the RS encoder 404.
However, when the inputted data correspond to the traffic information data packet, the MPEG synchronization byte among the 4 bytes inserted in the traffic information data packet by the packet formatter 426 is discarded (or deleted) and only the remaining 3 bytes are randomized. The remaining portion of the traffic information data excluding the MPEG header is not randomized and outputted directly to the RS encoder 404. This is because a randomizing process has already been performed on the traffic information data by the E-VSB randomizer 421. The RS encoder 404 RS-codes the data randomized by the data randomizer 403 or the data bypassing the data randomizer 403. Then, the RS encoder 404 adds a 20-byte RS parity to the coded data, thereby outputting the RS-parity-added data to the data interleaver 405.
At this point, if the inputted data correspond to the main data packet, the RS encoder 404 performs a systematic RS-coding process identical to that of the conventional ATSC VSB system on the inputted data, thereby adding the 20-byte RS parity at the end of the 187-byte data. Alternatively, if the inputted data correspond to the traffic information data packet, each place of the 20 parity bytes is decided within the packet. Thereafter, the 20 bytes of RS parity gained by performing the non-systematic RS-coding are respectively inserted in the decided parity byte places. The data interleaver 405 receives the data having the parity added by the RS encoder 404 and interleaves the received data. Thereafter, the data interleaver 405 outputs the interleaved data to the backward compatibility processor 406 and the trellis encoder 407. Herein, the data interleaver 405 corresponds to a byte unit convolutional interleaver.
Meanwhile, a memory within the trellis encoder 407 should first be initialized in order to allow the output data of the trellis encoder 407 so as to become the known data defined based upon an agreement between the receiver and the transmitter. More specifically, the memory of the trellis encoder 407 should first be initialized before the known data sequence being inputted is trellis-encoded. At this point, the beginning of the known data sequence that is inputted corresponds to the initialization data place holder inserted by the group formatter 424 and not the actual known data. Therefore, a process of generating initialization data right before the trellis-encoding of the known data sequence being inputted and a process of replacing the initialization data place holder of the corresponding trellis encoder memory with the newly generated initialization data are required. This is to ensure the backward-compatibility with the conventional receiving system.
The trellis memory initialization data generated to replace the initialization data place holder are decided based upon the current status of the memory within the trellis encoder 407 and the desired initialization status. Further, due to the replaced initialization data, a process of recalculating the RS parity of the corresponding data packet and a process of replacing the newly calculated RS parity with the RS parity outputted from the data interleaver 405 are required. Therefore, the backward compatibility processor 406 receives the traffic information data packet including the initialization data place holder that is to be replaced with the initialization data from the data interleaver.
Subsequently, the backward compatibility processor 406 receives the initialization data from the trellis encoder 407. Then, the backward compatibility processor 406 calculates a new non-systematic RS parity and outputs the newly calculated non-systematic RS parity to the trellis encoder 407. Thereafter, the trellis encoder 405 selects the output of the data interleaver 405 as the data within the traffic information data packet including the initialization data place holder that is to be replaced. The trellis encoder 405 also selects the output of the backward compatibility processor 406. Accordingly, the trellis encoder 405 trellis-encodes the selected outputs by symbol units. More specifically, the trellis encoder 407 trellis-encodes the initialization data instead of the initialization data place holder included in the traffic information data packet which has been inputted.
Meanwhile, when the main data packet is inputted or when the traffic information data packet is inputted, wherein the traffic information data packet does not include the initialization data place holder that is to be replaced, the trellis encoder 407 selects the data outputted from the data interleaves 405 and the RS parity, thereby performing a trellis-encoding process by symbol units. Then, the data trellis-encoded by the trellis encoder 407 are inputted to the frame multiplexer 408. The frame multiplexer 408 inserts field and segment synchronization signals in the output of the trellis encoder 407 and outputs the processed data to the pilot inserter 409. The pilot inserter 409 adds a pilot signal to the output symbol sequence of the frame multiplexer 408. The pilot-added symbol sequence is modulated to a 8VSB signal of an intermediate frequency band and, then, converted to a RF band signal, thereby being transmitted through the antenna.
Meanwhile, the embodiment shown in
In a third embodiment of the present invention, the E-VSB pre-processor 401 includes a RS frame encoder, an E-VSB randomizer, a group formatter, an E-VSB block processor, a data interleaver, and a packet formatter. The difference between the third embodiment and the E-VSB pre-processor shown in
In this case, since the group formatter is positioned before the E-VSB block processor, a byte expansion process needs to be performed before the group formatter in order to correspond to the coding process of the E-VSB block processor, thereby enabling the group formatter to operate without trouble. Therefore, the E-VSB randomizer not only randomizes the traffic information data but also performs byte expansion by inserting null data bits. Furthermore, the E-VSB block processor performs one of a 1/2-rate coding process and a 1/4-rate coding process on only the valid data of the byte-expanded traffic information data, which correspond to the data bits having the actual information. As described above, the E-VSB pre-processor 401 performing additional coding processes on the traffic information data may be applied in various methods. Thus, the present invention is not limited only to the examples given in the description set forth herein.
Second EmbodimentIn the digital broadcast transmitting system according to the second embodiment of the present invention having the above described structure, the main data are inputted to the packet multiplexer 502. On the other hand, the traffic information data are inputted to the E-VSB pre-processor 501, which performs additional coding processes so as to enable the traffic information data to respond quickly with robustness against noise and channel change.
The RS frame encoder 521 of the E-VSB pre-processor 501 receives the randomized traffic information data and performs at least one of an error correction coding process and an error detection coding process on the received data. Accordingly, by providing robustness to the traffic information data, the data can scatter group error that may occur due to a change in the frequency environment. Thus, the data can respond appropriately to the frequency environment which is very poor and liable to change. The RS frame multiplexer 521 also includes a process of mixing in row units many sets of traffic information data each having pre-determined size. The error correction coding uses the RS coding method, and the error detection coding uses the cyclic redundancy check (CRC) coding method. When performing the RS coding process, parity data required for error correction are generated. And, when performing the CRC coding process, CRC data required for error detection are generated.
In the RS frame encoder 521, the process of creating the RS frame creating process and the process of performing error correction coding and error detection coding on the created RS frame are identical to those of the RS frame encoder 422 shown in
At this point, since the E-VSB randomizer/byte expander 522 already performs a randomizing process on the traffic information data, the process of randomizing the traffic information by the data randomizer 503 at a later end may be omitted for simplicity. Further, the order of performing the data randomizing process and the byte expansion process may be altered. More specifically, the byte expansion process may be performed after the data randomizing process. Alternatively, the data randomizing process may be performed after the byte expansion process. The order may be selected while taking into consideration the overall system and its structure.
The byte expansion may differ depending upon the coding rate of the E-VSB block processor 533 within the E-VSB post-processor 504. More specifically, when the coding rate of E-VSB block processor 533 is G/H, the byte expander expands G bytes to H bytes (wherein G and H are integers, and G<H). For example, if the coding rate if 1/2, 1 data byte is expanded to 2 data bytes. Alternatively, if the coding rate if 1/4, 1 data byte is expanded to 4 data bytes. Then, the traffic information data outputted from the E-VSB randomizer/byte expander 522 is inputted to the group formatter 523. The operations of the group formatter 523, data deinterleaver 524, and the packet formatter 525 within the E-VSB pre-processor 501 are similar to those the group formatter 424, data deinterleaver 425, and the packet formatter 426 within the E-VSB pre-processor 401 shown in
The traffic information data packet pre-processed by the E-VSB pre-processor 501 is inputted to the packet multiplexer 502 so as to be multiplexed with the main data packet. The data multiplexed and outputted from the packet multiplexer 502 are data randomized by the data randomizer 503 and, then, inputted to the E-VSB post-processor 504. Herein, the operations of the packet multiplexer 502 and data randomizer 503 are identical to those shown in
More specifically, the data randomized by the data randomizer 503 or bypassing the data randomizer 503 are inputted the RS parity place holder inserter 531 of the E-VSB post-processor 504. When the inputted data correspond to a 187-byte main data packet, the RS parity place holder inserter 531 inserts a 20-byte RS parity place holder at the back of the 187-byte data, thereby outputting the processed data to the data interleaver 532. Alternatively, when the inputted data correspond to a 187-byte traffic information data packet, the RS parity place holder inserter 531 inserts a 20-byte RS parity place holder within the data packet in order to perform a non-systematic RS-coding process in a later end. Thereafter, in the remaining portion of the 187 byte places bytes are inserted in the traffic information data packet, which are then outputted to the data interleaver 532.
The data interleaver 532 performs a data interleaving process on the output of the RS parity place holder inserter 531 and, then, outputs the processed data to the E-VSB block processor 533. The E-VSB block processor 533 performs additional coding processes on the valid data among the traffic information data being outputted from data interleaver 532. For example, if 1 byte has been expanded to 2 bytes by inserting null bits between data bits from the E-VSB randomizer/byte expander 522, the E-VSB block processor 533 1/2-rate codes only the valid data bit among the symbol configured of a null bit and a valid data bit and, then, outputs the processed data. On the other hand, if 1 byte has been expanded to 4 bytes by inserting null bits between data bits from the E-VSB randomizer/byte expander 522, the E-VSB block processor 533 1/4-rate codes only the valid data bit among the symbol configured of 3 null bits and 1 valid data bit and, then, outputs the processed data.
Either the main data or the RS parity place holder directly bypasses the E-VSB randomizer/byte expander 522. Also, the known data and the initialization data place holder may directly bypass the E-VSB randomizer/byte expander 522. In case of the known data place holder, the known data generated from the E-VSB block processor 533 may be outputted instead of the known data place holder. The data being coded, replaced, and bypassed from the E-VSB block processor 533 are inputted to the data deinterleaver 534. The data deinterleaver 534 performs an inverse process of the data interleaver 532, whereby a data deinterleaving process is performed on the input data, which are then outputted to the RS parity place holder remover 535.
The RS parity place holder remover 535 removes the 20-byte RS parity place holder inserted by the RS parity place holder inserter 531 for the operations of the data interleaver 532 and the data deinterleaver 534 and, then, outputs the processed data to the RS encoder 505. At this point, if the inputted data correspond to main data packet, the last 20 bytes of RS parity place holders are removed from the 207 bytes of the main data packet. Alternatively, if the inputted data correspond to the traffic information data packet, the 20 bytes of RS parity place holders are removed from the 207 bytes of the traffic information data packet in order to perform the non-systematic RS-coding process.
As another embodiment of the E-VSB post-processor 504, if the inputted data correspond to the 187-byte main data packet, the RS parity place holder inserter 531 may perform a systematic RS-coding process so as to insert a 20-byte RS parity at the end of the 187-byte main data. Accordingly, the RS parity place holder inserter 531 removes the last 20 bytes of RS parity from the 207 bytes of the main data packet. Meanwhile, the RS encoder 505, the data interleaver 506, the backward compatibility processor 507, the trellis encoder 508, the frame multiplexer 509, the pilot inserter 510, the VSB modulator 511, and the RF up-converter 512 which are provided behind the E-VSB post-processor 504 are identical to those shown in
In the digital broadcast transmitting system according to the third embodiment of the present invention having the above described structure, the main data are inputted to the packet multiplexer 602. On the other hand, the traffic information data are inputted to the E-VSB pre-processor 601, which performs additional coding processes so as to enable the traffic information data to respond quickly with robustness against noise and channel change. The structure and operation of each component of the E-VSB pre-processor 601 are identical to those of the E-VSB pre-processor 501 shown in
The traffic information data packet pre-processed by the E-VSB pre-processor 601 is inputted to the packet multiplexer 602 so as to be multiplexed with the main data packet. The multiplexed data outputted from the packet multiplexer 602 are data randomized by the data randomizer 603 and, then, inputted to the RS encoder 604. The packet multiplexer 602 multiplexes the main data packet and the traffic information data packet according to a pre-defined multiplexing rule. At this point, the main data packet and the traffic information data packet may be multiplexed to have burst structures as shown in
The RS encoder 604 RS-codes the data being randomized from or bypassing the data randomizer 603, thereby adding a 20-byte RS parity and outputting the processed data to the data interleaver 605. At this point, if the inputted data correspond to the main data packet, the RS encoder 604 performs a systematic RS-coding process identical to that of the conventional. ATSC VSB system on the input data, thereby adding a 20-byte RS parity at the end of the 187-byte data. Conversely, if the inputted data correspond to the traffic information data packet, the RS encoder 604 first decides 20 parity byte places and, then, performs a non-systematic RS-coding process on the decided parity byte places, thereby inserting the 20 bytes of non-systematic RS parity in the traffic information data packet.
The non-systematic coding process is performed on the traffic information data packet because, when the value of the traffic information data is changed by the E-VSB post-processor 606, the process of which will be described in detail in a later process, the RS parity is required to be recalculated. And, at this point, the parity bytes should be outputted later than the traffic information data bytes at the output end of the data interleaver 605. The data interleaver 605 receives the data having parity added thereto by the RS encoder 604. Then, after performing an interleaving process, the data interleaver 605 outputs the processed data to the E-VSB post-processor 606 and the backward compatibility processor 607. Herein, the data interleaver 605 receives the RS parity newly recalculated and outputted from the backward compatibility processor 607, thereby outputting the received RS parity instead of non-systematic. RS parity which is not yet outputted.
The E-VSB post-processor 606 performs additional coding processes in symbol units only on the traffic information data being outputted from the data interleaver 605. For example, if 1 byte has been expanded to 2 bytes by inserting null bits between data bits from the E-VSB pre-processor 606, the E-VSB post-processor 606 1/2-rate codes only the valid data bit among the symbol configured of a null bit and a valid data bit and, then, outputs the processed data. On the other hand, if 1 byte has been expanded to 4 bytes by inserting null bits between data bits from the E-VSB pre-processor 601, the E-VSB post-processor 606 1/4-rate codes only the valid data bit among the symbol configured of 3 null bits and 1 valid data bit and, then, outputs the processed data.
The main data or the RS parity being outputted from the data interleaver 605 directly bypass (or bypasses) the E-VSB post-processor 606. Moreover, the known data and initialization data place holder also directly bypass (or bypasses) the E-VSB post-processor 606. At this point, the known data place holder may be replaced with the known data generated from the E-VSB post-processor 606 and then outputted. Furthermore, the E-VSB post-processor 606 generates initialization data so as to initialize the memory within the trellis encoder 608 to a decided status at the beginning of a known data sequence. Thereafter, the initialization data generated from the E-VSB post-processor 606 is outputted instead of the initialization data place holder. Accordingly, the value of the memory within the trellis encoder 608 should be received from the E-VSB post-processor 606.
The backward compatibility processor 607 calculates the 20-byte non-systematic RS parity corresponding to the traffic information data packet configured on 187 data bytes and outputted from the E-VSB post-processor 606. Subsequently, the calculated non-systematic RS parity is outputted to the data interleaver 605. The data interleaver 605 receives the RS parity bytes calculated and outputted from the backward compatibility processor 607 and, then, outputs the received RS parity bytes instead of the non-systematic RS parity. Herein, the backward compatibility processor 607 performs a non-systematic RS-coding process because the E-VSB post-processor 606 changes the values of the traffic information data and the initialization data place holder. Accordingly, when a decoding process is performed by the conventional ATSC VSB receiver, a decoding error may be prevented. In other words, this process is performed to provide backward compatibility to the conventional ATSC VSB receiver.
The data that are additionally coded and replaced by the E-VSB post-processor 606 and that bypass the E-VSB post-processor 606 are inputted to the trellis encoder 608 so as to be trellis-encoded. Thereafter, the trellis-encoded data sequentially pass through the frame multiplexer 609, the pilot inserter 610, the VSB modulator 611, and the RF up-converter 612. Meanwhile, according to another embodiment of the present invention, initialization data, which are generated for initializing a memory within the trellis encoder 608, are generated from the trellis encoder 608 instead of the E-VSB post-processor 606. In this case, the backward compatibility processor 607 receives a traffic information data packet from the E-VSB post-processor 606 in order to calculate the parity value. Herein, the traffic information data packet includes an initialization data place holder that is to be replaced by the initialization data. Further, the backward compatibility processor 607 receives the initialization data from the trellis encoder 608. Thereafter, the calculated non-systematic RS parity is outputted to the trellis encoder 608. The remaining processes that may follow are identical to those shown in
The tuner 701 tunes a frequency of a particular channel through any one of an antenna, a cable, and a satellite, thereby down-converting the tuned frequency to an intermediate frequency (IF) signal. Thereafter, the down-converted signal is outputted to the demodulator 702. At this point, the tuner 701 is controlled by the channel manager 707. The result and strength of the broadcast signal corresponding to the tuned channel are reported to the channel manager 707. Herein, the data being received through the frequency of a particular channel include the main data, the enhanced data, and the table data which are used for decoding the main data and enhanced data. In the example given in the present invention, traffic information data and a traffic information providing table may be applied to the enhanced data.
The demodulator 702 performs VSB demodulation and channel equalization processes on the signal outputted from the tuner 701. Then, after identifying the main data and the traffic information data from the signal, the demodulator 702 outputs the data (or signal) by TS packet units. The structure and operation of the demodulator 702 will be described in detail in a later process. In the example of the present invention, only the traffic information data packet outputted from the demodulator 702 is inputted to the demultiplexer 703. In other words, the main data packet may be inputted to another demultiplexer (not shown) that processes main data packets. Furthermore, the present invention may also be designed in a way that the demultiplexer 703 also demultiplexes the enhanced data packet as well as the main data packet. In the description of the present invention, the receiving and processing of traffic information data are described in detail. And, it should be noted that a detailed description of the processing of main data starting from the demultiplexer 703 may be omitted.
The demultiplexer 703 demultiplexes the traffic information messages and the PSI/PSIP tables from the traffic information data packets being inputted based upon the control of the data decoder 710. Thereafter, the demultiplexed traffic information messages and PSI/PSIP tables are outputted to the data decoder 710 in a section format. In an example given in the present invention, a traffic information message carried by a payload within the TS packet is outputted in a DSM-CC section format. At this point, the demultiplexer 703 performs a section filtering process based upon the control of the data decoder 710 so as to delete duplicate sections and to output only the non-duplicate sections to the data decoder 710. Moreover, the demultiplexer 703 may output the section configuring a desired table (e.g., VCT) through a section filtering process to the data decoder 710. Herein, the VCT includes traffic information descriptors shown in
The section filtering method includes a method of initiating section filtering after verifying the PID of a table defined by the MGT (e.g., VCT), and, when the VCT has a fixed PID (i.e., a base PID), a method of initiating section filtering without verifying the MGT. At this point, the demultiplexer 703 performs section filtering by referring to the table_id field, the version_number field, the section_number field, and so on. The data decoder 710 parses the DSM-CC section configuring the demultiplexed traffic information message. Then, the data decoder 710 decodes the traffic information message being a result of the parsing process and, then stores the traffic information message in a database of the second memory 711. The data decoder 710 groups a plurality of sections having the same table identifiers (table_id) to configure and parse a table. Then, the data decoder 710 stores the system information being the parsed result in the database of the second memory 711.
The second memory 711 is a table and data carousel database storing system information parsed from the tables and traffic information messages parsed from the DSM-CC section. Whether or not a table is configured of a single section or a plurality of sections can be known by the table_id field, the section_number field, and the last_section_number field within the table. For example, grouping only the TS packets having the PID of the VCT becomes a section. On the other hand, grouping sections having table identifiers allocated to the VCT becomes the VCT.
When parsing the VCT, information on the virtual channel to which traffic information is transmitted may be obtained. In addition, supplemental information associated with the traffic information message described, as shown in
The application identification information, service component identification information, and service information of the traffic information message obtained as described above may either be stored in the second memory 711 or outputted to the data broadcasting application manager 713. Additionally, reference may be made to the application identification information, service component identification information, and service information for decoding the traffic information message. Alternatively, the application identification information, service component identification information, and service information may also be used for preparing the operation of the application program for the traffic information message.
The data decoder 710 controls the demultiplexing of the system information table corresponding to the table associated with channel and event information. Thereafter, the data decoder 710 can transmit an A/V PID list to the channel manager 707. The channel manager 707 may refer to the channel map 708 to send a request (or command) for receiving an information table associated with the system, and then the channel manager 707 can receive the corresponding result. The channel manager 707 may also control the channel tuning of the tuner 701. Furthermore, the channel manager 707 directly controls the demultiplexer 703 so as to directly set up the A/V PID, thereby controlling the audio and video decoders 704 and 705.
The audio and video decoders 704 and 705 may respectively decode and output the audio and video data demultiplexed from the main data packet, or respectively decode and output the audio and video data demultiplexed from the traffic information data packet. Meanwhile, according to the embodiment of the present invention, it is apparent that when traffic information data and also audio data and video data are included in the enhanced data, the audio data and video data demultiplexed by the demultiplexer 703 may be respectively decoded by the audio decoder 704 and the video decoder 705. For example, the audio decoder 704 may decode the audio data by using an audio coding (AC)-3 decoding algorithm, and the video decoder 705 may decode the video data by using an MPEG-2 decoding algorithm.
Meanwhile, the native TV application manager 706 operates a native application program stored in the first memory 709, thereby performing general functions such as channel switching. The native application program refers to a software that is being mounted upon shipping of the receiving system. More specifically, when a user request is transmitted to the receiving system through a user interface (UI), the native TV application manager 706 the request onto the screen through a graphic user interface (GUI), thereby responding to the user request. The user interface receives the user request through an inputting device, such as a remote controller, a key pad, a jog dial, and a touch screen provided on the display screen. Thereafter, the user interface outputs the received user request to the native TV application manager 706, the data broadcasting application manager 713, and so on.
The native TV application manager 706 controls the channel manager 707, thereby controlling channel associated operations, such as managing the channel 708 and controlling the data decoder 710. In addition, the native TV application manager 706 stores the GUI control of the general receiving system, the user request, and the status of the receiving system to the first memory 709, and also recovers the information stored in the first memory 709. The channel manager 707 controls the tuner 701 and the data decoder 710, thereby managing the channel map 708 so as to be able to respond to the channel request made by the user.
More specifically, the channel manager 707 sends a request to the data decoder 710 so that the table associated with the channel, which is to be tuned, can be parsed. Thereafter, the channel manager 707 receives a report on the parsing result of the corresponding table from the data decoder 710. Then, depending upon the reported parsing result, the channel manager 707 updates the channel map 708. The channel manager 707 also sets up a PID to the demultiplexer 703 so as to demultiplex the table associated with the traffic information message from the traffic information data. The system manager 712 controls booting of the receiving system by turning on and off the power and, then, stores a ROM image (including downloaded software images) to the first memory 709. In other words, the first memory 709 stores operation programs, such as operation system (OS) programs required for operating the receiving system, and application programs performing data service functions.
The application program is a program that processes the traffic information message stored in the second memory 711, thereby providing the traffic information service to the user. If a data broadcasting data type other than the traffic information data is stored in the second memory 711, the corresponding data are processed by the application program or another type of application program and, then, provided to the user. The operation program and application program stored in the first memory 709 may be updated or corrected with a newly downloaded program. Furthermore, since the stored operation program and application program are not deleted even when the driving power supply is shut down, when the driving power is supplied, the program can be performed without having to download a new program.
The application program for providing the traffic information service according to the present invention may be mounted in the first memory 709 upon shipping of the receiving system, or stored later on in the first memory 709 after being downloaded. Also, the application program for the traffic information service (i.e., traffic information providing application program) that is stored in the first memory 709 can be deleted, updated, and corrected. Furthermore, the traffic information providing application program may also be downloaded along with the traffic information data and executed each time the traffic information data are being received.
When a data service request is made through the user interface, the data broadcasting application manager 713 operates the corresponding application program stored in the first memory 709 so as to process the requested data, thereby providing the requested data service to the user. And, in order to provide such data service, the data broadcasting application manager 713 supports the GUI. Herein, the data service is provided in the form of text, voice, graphic, still image, motion picture, and so on. The data broadcasting application manager 713 may be provided with a platform for executing the application program stored in the first memory 709. The platform may be, for example, a Java virtual machine for executing a Java program.
Hereinafter, an example of providing traffic information service to the user by having the data broadcasting application manager 713 execute the traffic information providing application program stored in the first memory 709 and, then, process the traffic information message stored in the second memory 711 will now be described in detail. The traffic information service according to the present invention is provided to the users by a receiver having only one or none of an electronic map and a GPS mounted therein in the form of at least one of a text, a voice, a graphic, a still image, and a motion picture. If the GPS module 714 is mounted on the receiving system shown in
By executing the traffic information providing application program, the data broadcasting application manager 713 provides the traffic information service requested by the user based upon the current location information acquired from the GPS module 714 and the traffic information message stored in the second memory 711. More specifically, based upon the request of the data broadcasting application manager 713, the traffic information message stored in the second memory 711 is read and inputted to the data broadcasting application manager 713. The data broadcasting application manager 713 analyses the traffic information message read from the second memory 711, thereby extracting required information and/or control signals in accordance with the contents of the message. In the description of the present invention, it is assumed that a request for a CTT service has been made by the user.
More specifically, the data broadcasting application manager 711 extracts a message ID (i.e., a message component), a message generation time, a message transmission time from the message management container 102 of each traffic information message (or TPEG message), such that it determines whether the following container is equal to a CTT-status container on the basis of information of the message component. In this case, the message component information includes a message ID and a version number. Also, the message component is requisite for all messages and is adapted to manage the messages of the data broadcasting application manager 713.
If the following container is determined to be the CTT-status container 104, the data broadcasting application manager 713 acquires (or obtains) information from the CTT status component of the CTT status container 104. The data broadcasting application manager 713 acquires (or obtains) from the TPEG location container 106 a location information corresponding to a currently-transmitted traffic-carrying information. In this case, the location information may be location coordinates (latitude and longitude) of start and end points or a link of the start and end points according to location type information of the TPEG location container. In other words, the location information may be a link ID assigned to a road section (i.e., a road link). Whenever necessary, a section may be specified as a link corresponding to the received information by referring to link- or node-information stored in the second memory 711.
Provided that the location type information is a link ID, and the location information is text data (e.g., a road name) associated with the link ID or a link, the present invention can specify a link corresponding to the received traffic-carrying status information by referring to the corresponding link information. If the location information acting as a link ID is a code for defining the link ID, the present invention can specify a link corresponding to the received traffic-carrying status information by referring to the corresponding link system stored in the second memory 711.
In the meantime, the data broadcasting application manager 713 reads data of an electronic map from the second memory 711 on the basis of current location coordinates received from the GPS module 714, and displays the read electronic map data on a display screen. In this case, a specific graphic sign is displayed at a specific point corresponding to the current location. Under the above-mentioned situation, the data broadcasting application manager 713 receives average link speed information, such that the received information is displayed at specific location coordinates of a location container following the container equipped with the average link speed information or at a link corresponding to a link ID. For the above-mentioned operation, different colors are assigned individual average link speeds.
For example, if the road on the image is determined to a current road, the red color is indicative of 0 to 10 km per hour, the orange color is indicative of 10 to 20 km per hour, the green color is indicative of 20 to 40 km per hour, and the blue color is indicative of at least 40 km per hour. If the congestion change information has a specific value “1” or “2”, a character string (“Increase” or “Reduction”) or icon assigned to the specific value “1” or “2” may also be displayed on a corresponding link along with the congestion change information. If the congestion change information has a specific value “0” or “3”, a displayed status is not updated to a new status, such that a current displayed status remains.
If the congestion change information is determined to be average speed change rate information, it is displayed on the screen according to the user's request, such that it can reduce the degree of visual confusion of a vehicle driver. For example, paths of possible routes (e.g., a predetermined traveling path and a predetermined forwarding path) may be simultaneously displayed on the screen as necessary. If the terminal does not include the second memory unit 711 equipped with the electronic map, an average link speed associated with only a forward link of a current traveling path may be displayed in different colors, or may be displayed in different numerals.
If a traveling path of the vehicle equipped with the TPEG terminal is predetermined, the average link speed information of links contained in the traveling path, instead of the forwarding links, may be displayed. If the additional information received from the data broadcasting application manager 713 is indicative of a famous restaurant or movie theater contained in the link, the corresponding points at the link may be displayed on the display screen, such that the point corresponding to the restaurant is visually distinguished from the other point corresponding to the movie theater. And, the data broadcasting application manager 713 may convert the corresponding information into text information, such that it may display the text information on the screen.
Upon receiving the user's request, the data broadcasting application manager 713 receives a link travel time, a link delay time, and congestion type information associated with individual links, such that it may display the received information, instead of the average link speed, on the display screen. If the user specifies a prediction time and requests prediction information associated with the road traffic-carrying status, the data broadcasting application manager 713 receives a prediction average speed of each link, such that it indicates the received link prediction average speed in the form of color- or numeral-data, instead of a current average speed.
Needless to say, if the user requests a display mode of a prediction travel time mode, instead of the prediction average speed, the data broadcasting application manager 713 displays the received prediction travel time information of each link on an electronic map or graphic screen of the display according to the above-mentioned user's request. In the meantime, if a function for automatically searching for a path of a destination is pre-established, the data broadcasting application manager 713 may search for or may re-search for a desirable path on the basis of the received link prediction average speed or the received link prediction travel time.
For example, in association with individual links leading to a node at which a user's vehicle will arrive after the lapse of 30 minutes from a current time at a current traveling speed, the data broadcasting application manager 713 selects a specific link having the shortest time to the destination as a traveling path using a prediction average speed or link prediction travel time acquired over the past 30 minutes, and displays the selected link on the screen. If the receiving system of
As described above, the information and/or control signals are temporarily stored in the non-volatile memory unit (not shown), and are then used in the data broadcasting application manager 713. The data broadcasting application manager 713 employs the information of the non-volatile memory unit, does not discard the employed information, and stores information created within a predetermined time (e.g., within the last 1 hour). In this case, the data broadcasting application manager 713 stores the last 1-hour information as an average speed or link travel time at intervals of 20 minutes (i.e., 0 minutes, 20 minutes, and 40 minutes). The last time may be set to other time longer or shorter than the aforementioned 1 hour according to the available memory capacity.
In this way, if the user selects a specific link on the condition that an average speed of each link is stored in the memory unit, the data broadcasting application manager 713 displays not only an average speed history and link travel time history of the selected link, but also a prediction link average speed and prediction link travel time of the selected link in the form of a graph. As a result, the graph indicating the average speed history, the link travel time history, the prediction average link speed, and the prediction link travel time of the selected link is displayed on the display screen.
In this case, if a number marked on the graph is speed information, the data broadcasting application manager 713 converts the stored information into data of units of km/h, and displays the data of km/h units on the display screen. And, current link name (e.g., a road name) is displayed at an upper part of the graph. The road name of the link is contained in the location coordinates of the TPEG location container or a rear part of a link ID, and is then received. Otherwise, the above-mentioned link road name is contained in the electronic map of the second memory 711.
At this point, the traffic information data having the traffic information message and the system information multiplexed therein may be received through the channel frequency tuned as described above. If the traffic information data are received (S724), the demultiplexer 703 may demultiplex the traffic information message and system information tables by using PID extraction and section filtering (S725). Among the system information, tables associated with channel information include the VCT or the PAT/PMT. Herein, at least one of the PMT and VCT may include the traffic information descriptor(s) according to the present invention. By parsing the system information table, information on the virtual channel can be obtained, and whether an A/V element stream is being transmitted to the corresponding virtual channel and whether the traffic information data are being transmitted can be known. If the traffic information data are transmitted to the virtual channel, an application identifier, a service component identifier, and service information can be acquired by parsing the traffic information descriptor.
More specifically, information on the virtual channel is extracted by referring to an element stream type (ES type) and PID within the system information table (i.e., VCT and/or PAT/PMT) (S726). If the channel information extracted from the system information table indicates that an A/V ES exists within the virtual channel (S727), an A/V PID of the corresponding virtual channel in the channel map is set up (S728), thereby performing. A/V demultiplexing and decoding (S729). Therefore, the user can view the broadcast program corresponding to the A/V (S730). Meanwhile, if it is indicated in Step 727 that an A/V ES does not exist in the virtual channel, the present invention verifies when the traffic information data are being transmitted to the virtual channel (S731).
A plurality of methods for verifying whether the traffic information data have been transmitted to the virtual channel may be proposed. For example, verification can be performed by parsing the system information table, and verification can also be performed by using the PID within the TS packet. When assuming that the traffic information data have been transmitted to the DSM-CC section, the existence (or presence) of the traffic information data can be known by parsing the field value of any one of the stream_type field within the PMT and the stream_type field of the service location descriptor within the VCT. In other words, if the stream type field value is ‘0x95’, this indicates that the traffic information data have been transmitted to the corresponding virtual channel. Therefore, if it is verified in Step 731 that the traffic information data are being transmitted to the virtual channel, all traffic information having the DSM-CC data format that are being transmitted to the virtual channel are received (S732), thereby providing the traffic information service desired (or requested) by the user (S733).
If it is verified, in Step 731, that neither the A/V ES nor the traffic information data exist in the virtual channel, then the corresponding virtual channel is determined to be an invalid channel. In this case, the system may display, for example, a message that no valid channel or signal exists (S736). Thereafter, the process is returned to Step 724 in order to newly receive a valid channel information table.
Meanwhile, the system verifies whether a request for changing (or switching) the channel is made during the data service or while viewing a broadcast program (S734). If a change in channel has been requested, and if the request corresponds to changing the virtual channel, the data broadcasting process is reset, and the process is returned to Step 726 in order to find a new set of virtual channel information. Further, if the request corresponds to changing the physical channel, the process is returned to Step 723 so as to tune to the corresponding physical channel.
However, if there is no request for changing the channel, the system verifies whether a channel information version has been upgraded (S735). If it is determined in Step 735 that the channel information version has been upgraded, this indicates, that the channel information has been changed (or modified) by the broadcast station. Therefore, the process is returned to Step 724 in order to receive a new channel information table. Conversely, if it is determined in Step 735 that the channel information has not been changed (or modified), then viewing of the broadcast program may be resumed.
The demodulator (reference numeral 702 of
Referring to
At this point, the known sequence detector 763 detects the known sequence location inserted by the transmitting end from the input/output data of the VSB demodulator 761 (i.e., the data prior to the demodulation or the data after the modulation). Thereafter, the location information along with the symbol sequence of the known data, which are generated from the detected location, is outputted to the VSB demodulator 761 and the equalizer 762. Further, the known sequence detector 763 outputs information related to the traffic information data additionally coded by the transmitting end and the main data that have not been additionally coded to the E-VSB block decoder 764. Herein, the information allowing the traffic information data and the main data to be differentiated (or identified) by the E-VSB block decoder 764 is outputted to the E-VSB block decoder 764. Although the connection state is not shown in
The VSB demodulator 761 uses the known data symbol sequence during the timing and/or carrier recovery, thereby enhancing the demodulating performance. Similarly, the equalizer 762 uses the known data sequence, thereby enhancing the equalizing performance. Furthermore, the decoding result of the E-VSB block decoder 764 may also be fed-back to the equalizer 762, thereby enhancing the equalizing performance. Meanwhile, when the data being inputted to the E-VSB block decoder 764, after being equalized by the equalizer 762, correspond to the traffic information data being additionally coded and trellis-encoded by the transmitting end, the equalizer 762 performs an inverse process of the transmitting end by additionally decoding and trellis-decoding the inputted enhanced data. On the other hand, when the data being inputted correspond to the main data being trellis-encoded only and not additionally coded, the equalizer 762 only performs trellis-decoding on the inputted main data.
The data group decoded by the E-VSB block decoder 764 is outputted to the E-VSB data processor 765, and the main data packet is outputted to the main data processor 766. More specifically, when the inputted data correspond to the main data, the E-VSB block decoder 764 performs Viterbi-decoding on the input data so as to output a hard decision value or to perform hard decision on a soft decision value and output the hard-decided result. Meanwhile, when the inputted data correspond to the traffic information data, the E-VSB decoder 764 outputs a hard decision value or a soft decision value on the inputted enhanced value.
More specifically, when the inputted data correspond to the traffic information data, the E-VSB block decoder 764 performs a decoding process on the data encoded by the E-VSB block processor and the trellis encoder of the transmitting system. At this point, the data outputted from the RS frame encoder of the E-VSB pre-processor included in the transmitting system may correspond to an external code, and the data outputted from each of the E-VSB block processor and the trellis encoder may correspond to an internal code. When decoding such concatenated codes, the decoder of the internal code should output a soft decision value, so that the external coding performance can be enhanced. Therefore, the E-VSB block decoder 764 may output a hard decision value on the traffic information data. However, it is more advantageous to output a soft decision value.
As an example of the present invention, the E-VSB data processor 765 includes an E-VSB data deformatter 765-1, a RS frame decoder 765-2, and an E-VSB derandomizer 765-3. It would be efficient to apply this structure in the E-VSB pre-processor of the transmitting system (shown in
Herein, the data deinterleaver 766-1, the RS decoder 766-2, and the data derandomizer 766-3 included in the main data processor 766 are blocks required for receiving the main data. Therefore, these blocks may not be required in the structure of the receiving system that only receives the traffic information data. The data deinterleaver 766-1 performs an inverse process of the data interleaver included in the transmitting end. More specifically, the data deinterleaver 766-1 deinterleaves the main data being outputted from the E-VSB block decoder 764 and outputs the deinterleaved data to the RS decoder 766-2.
The RS decoder 766-2 performs systematic RS decoding on the deinterleaved data and outputs the RS-decoded data to the data derandomizer 766-3. The data derandomizer 766-3 receives the output of the RS decoder 766-2 and generates a pseudo random data byte identical to that of the randomizer included in the transmitting system. Thereafter, the data derandomizer 766-3 performs a bitwise exclusive OR (XOR) operation on the generated pseudo random data byte, thereby inserting the MPEG synchronization bytes to the beginning of each packet so as to output the data in 188-byte main data packet units. At this point, the output of the data derandomizer 766-3 may be inputted to the demultiplexer 703 shown in
The data being outputted from the E-VSB block decoder 764 are inputted to the E-VSB data deformatter 765-1 in a data group form. At this point, the E-VSB data deformatter 765-1 already knows the configuration of the input data group. Accordingly, the E-VSB data deformatter 765-1 removes the main data, the known data that have been inserted in the data group, the trellis initialization data, the MPEG header, and the RS parity added by the RS encoder of the transmitting system that all were inserted in the main data group. Thereafter, the E-VSB data deformatter 765-1 outputs only the traffic information data to the RS frame decoder 765-2. More specifically, the RS frame decoder 765-2 receives only the traffic information data RS-coded and/or CRC-coded by the E-VSB data deformatter 765-1.
The RS frame decoder 765-2 performs an inverse process of the RS frame encoder included in the transmitting system. Accordingly, the RS frame decoder 765-2 corrects the errors within the RS frame. Thereafter, the RS frame decoder 765-2 adds a 1-byte. MPEG synchronization byte, which was removed during a RS frame coding process, to the error-corrected traffic information data packet. Then, the processed data are outputted to the E-VSB data derandomizer 766-3. At this point, if a row permutation process was performed on the traffic information data, an inverse row permutation process is also required. The E-VSB data derandomizer 766-3 performs a derandomizing process, which corresponds to an inverse process of the E-VSB randomizer included in the transmitting system, on the inputted traffic information data and outputs the processed data. Thus, the transmitting system can receive the transmitted traffic information data.
Meanwhile, if the E-VSB randomizer is positioned after the RS frame encoder in the structure of the E-VSB pre-processor included in the transmitting system, the E-VSB data processor may include only the E-VSB data deformatter and the RS frame decoder. In this case, the operation of the E-VSB data deformatter becomes partially different from that of the E-VSB data deformatter shown in
In this case, only the data derandomizing process may be performed, or the data derandomizing process may be processed along with the null data removing process. This may differ depending upon the structure and operation of the E-VSB pre-processor included in the transmitting system. More specifically, only the data derandomizing process may be performed, or the data derandomizing process and the null data removing process may both be processed depending upon the positioning order of the E-VSB block processor and the group formatter, and whether the coding process was performed only on the valid data by the E-VSB block processor.
For example, if the E-VSB block processor is positioned before the group formatter in the E-VSB pre-processor, the receiving system does not require the null data to be removed, since byte expansion has not been performed. In addition, even though a byte expansion process has been performed, if the E-VSB block processor has performed an additional coding process only on the valid data (e.g., if the coding process was performed at a coding rate of 1/2 or at a coding rate of 1/4), the receiving system does not require the process of removing the null data. Conversely, if the E-VSB block processor is positioned after the group formatter in the E-VSB pre-processor, the receiving system requires a byte expansion process to be performed. In this case, if the E-VSB block processor has performed an additional coding process all data types (e.g., if the coding process was performed at a coding rate of 1/2 or at a coding rate of 1/4), the receiving system requires the null data to be removed.
However, if the removal of the expanded byte is required, the order of the byte removal process and the derandomizing process may vary depending upon the structure of the transmitting system. More specifically, if the byte expansion is performed after the randomizing process in the transmitting system, then the byte removal process is first performed before performing the derandomizing process in the receiving system. Conversely, if the order of the process is changed in the transmitting system, the order of the respective processes in the receiving system is also changed.
When performing the derandomizing process, if the RS frame decoder requires a soft decision in a later process, and if, therefore, the E-VSB block decoder receives a soft decision value it is difficult to perform an XOR operation between the soft decision and the pseudo random bit, which is used for the derandomizing process. Accordingly, when an XOR operation is performed between the pseudo random bit and the soft decision value of the traffic information data bit, and when the pseudo random bit is equal to ‘1’, the E-VSB data deformatter changes the code of the soft decision value and then outputs the changed code. On the other hand, if the pseudo random bit is equal to ‘0’, the E-VSB data deformatter outputs the soft decision value without any change in the code. Thus, the state of the soft decision may be maintained and transmitted to the RS frame decoder.
If the pseudo random bit is equal to ‘1’ as described above, the code of the soft decision value is changed because, when an XOR operation is performed between the pseudo random bit and the input data in the randomizer of the transmitter, and when the pseudo random bit is equal to ‘1’, the code of the output data bit becomes the opposite of the input data (i.e., 0 XOR 1=1 and 1 XOR 0=0). More specifically, if the pseudo random bit generated from the E-VSB packet deformatter is equal to ‘1’, and when an XOR operation is performed on the hard decision value of the traffic information data bit, the XOR-operated value becomes the opposite value of the hard decision value. Therefore, when the soft decision value is outputted, a code opposite to that of the soft decision value is outputted.
Accordingly, the RS frame decoder performs an inverse process of the RS frame encoder included in the transmitting system. Therefore, the RS frame decoder corrects the errors within the RS frame. Subsequently, the RS frame decoder adds a 1-byte MPEG synchronization byte, which was removed during a RS frame coding process, to the error-corrected traffic information data packet. Thus, the initial traffic information data transmitted by the transmitting system can be obtained.
The Viterbi decoder 784 Viterbi-decodes the data outputted from the equalizer 782 and converts the Viterbi-decoded data to bytes. Thereafter, the converted data are outputted to the data deinterleaver 785. The data deinterleaver 785 performs an inverse process of the data interleaver of the transmitting system and outputs the deinterleaved data to the RS decoder 786. If the received data packet is the main data packet, the RS decoder 786 RS-decodes the received main data packet. Alternatively, if the received data packet is the traffic information data packet, the RS decoder 786 removes the non-systematic RS parity bytes and outputs the processed data to the data derandomizer 787.
The data derandomizer 787 performs an inverse process of the randomizer of the transmitting system on the output of the RS decoder 786. Thereafter, the data derandomizer 787 inserts the MPEG synchronization byte in the beginning of each packet, thereby outputting the data in 188-byte packet units. The output of the data derandomizer 787 is simultaneously outputted to the demultiplexer 703 (shown in
The main data packet remover 788-1 removes the 188-byte main data packet from the data outputted from the data derandomizer 787 and outputs the processed data to the E-VSB packet deformatter 788-2. The E-VSB packet deformatter 788-2 removes the 4-byte. MPEG header, known data, and trellis initialization data from the 188-byte data packet. Then, the E-VSB packet deformatter 788-2 outputs only the traffic information data to the E-VSB data processor 788-3. At this point, the E-VSB packet deformatter 788-2 may or may not remove the null data.
More specifically, when the E-VSB post-processor of the transmitting system shown in
As described above, the digital broadcast transmitting/receiving system and the method for processing data are advantageous in that when receiving traffic information data through a channel, the data are robust against error and are compatible with the conventional. VSB receiver. Furthermore, data can be received more efficiently without error even in channels having severe noise and ghost effect.
In addition, by performing additional error correction coding and error detection coding processes on the traffic information data and transmitting the processed data, robustness is provided to the traffic information data, thereby allowing the data to respond appropriately to the changes in the channel environment. Furthermore, by using link identifiers for providing the traffic information data, the transmission capacity may be minimized. And, by warning in advance the information on heavy congested traffic status, the amount of traffic may be adequately dispersed, thereby allowing the roads to be circulated efficiently. The present invention having the above-described advantages may be more efficiently used when applied in mobile and portable receiver which requires a greater degree of robustness against noise and ghost effect.
It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the inventions. Thus, it is intended that the present invention covers the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.
Claims
1. A broadcast transmitter comprising:
- a randomizer for randomizing enhanced data;
- a first encoder for Reed Solomon (RS) encoding and Cyclic Redundancy Check (CRC) encoding the randomized enhanced data;
- a block processor for encoding the RS-CRC encoded enhanced data at a coding rate of 1/H, wherein H is greater than 1;
- a group formatting unit for forming a data group including the encoded enhanced data and de-interleaving data of the data group, wherein the formed data group further includes main data place holders, known data sequences, trellis initialization data, MPEG header place holders, and RS parity data place holders;
- a packet formatter for removing the RS parity data place holders and the main data place holders from the data group in which data are deinterleaved and replacing the MPEG header place holders in the data group, in which data are deinterleaved, with MPEG headers, thereby outputting enhanced data packets;
- a first multiplexer for multiplexing the enhanced data packets with main data packets including main data;
- a second encoder for adding RS parity data to the multiplexed enhanced and main data packets by RS encoding the main data packets of the multiplexed enhanced and main data packets with a systematic RS encoding scheme and RS encoding the enhanced data packets of the multiplexed enhanced and main data packets with a non-systematic RS encoding scheme; and
- an interleaver for interleaving data of the RS-encoded enhanced and main data packets.
2. The broadcast transmitter of claim 1, wherein the interleaver is a convolutional data byte interleaver.
3. The broadcast transmitter of claim 1, further comprising:
- a trellis encoder for trellis encoding the interleaved data, wherein at least one memory included in the trellis encoder is initialized when the trellis initialization data are inputted to the trellis encoder.
4. The broadcast transmitter of claim 3, further comprising:
- a second multiplexer for multiplexing the trellis-encoded data with field synchronization data and segment synchronization data.
5. A method of processing broadcast data in a broadcast transmitter, the method comprising:
- randomizing, by a randomizer, enhanced data;
- Reed Solomon (RS) encoding and Cyclic Redundancy Check (CRC) encoding, by a first encoder, the randomized enhanced data;
- encoding, by a block processor, the RS-CRC encoded enhanced data at a coding rate of 1/H, wherein H is greater than 1;
- forming a data group including the encoded enhanced data, wherein the formed data group further includes main data place holders, known data sequences, trellis initialization data, MPEG header place holders, and RS parity data place holders;
- de-interleaving data of the data group;
- removing, by a packer formatter, the RS parity data place holders and the main data place holders from the data group in which data are deinterleaved and replacing the MPEG header place holders in the data group, in which data are deinterleaved, with MPEG headers, thereby outputting enhanced data packets;
- multiplexing the enhanced data packets with main data packets including main data;
- adding, by a second encoder, RS parity data to the multiplexed enhanced and main data packets by RS encoding the main data packets of the multiplexed enhanced and main data packets with a systematic RS encoding scheme and RS encoding the enhanced data packets of the multiplexed enhanced and main data packets with a non-systematic RS encoding scheme; and
- interleaving data of the RS-encoded enhanced and main data packets.
6. The method of claim 5, wherein the data of the RS-encoded enhanced and main data packets are interleaved by a convolutional data byte interleaver.
7. The method of claim 5, further comprising:
- trellis encoding, by a trellis encoder, the interleaved data, wherein at least one memory included in the trellis encoder is initialized when the trellis initialization data are inputted to the trellis encoder.
8. The method of claim 7, further comprising:
- multiplexing the trellis-encoded data with field synchronization data and segment synchronization data.
9. A method of processing data in a transmitting system, the method comprising:
- generating first system information and second system information, wherein the first system information includes information for acquisition of the second system information, and wherein the second system information includes service component identification information for identifying each of one or more service components, service name information and service description information;
- randomizing service data for a service;
- first encoding the randomized service data to add parity data;
- second encoding the first encoded service data at a code rate;
- interleaving the second encoded service data; and
- transmitting a broadcast signal including the interleaved service data, the first system information and the second system information and known data, wherein the known data are data for synchronization.
10. A transmitting system for processing data, the transmitting system comprising:
- a system information generator to generate first system information and second system information, wherein the first system information includes information for acquisition of the second system information, and wherein the second system information includes service component identification information for identifying each of one or more service components, service name information and service description information;
- a randomizer to randomize service data for a service;
- a first encoder to first encode the randomized service data to add parity data;
- a second encoder to second encode the first encoded service data at a code rate;
- an interleaver to interleave the second encoded service data; and
- a transmitter to transmit a broadcast signal including the interleaved service data, the first system information, the second system information and known data, wherein the known data are data for synchronization.
11. A method of processing data in a receiving system, the method comprising:
- receiving a broadcast signal including service data for a service, first system information, and second system information,
- wherein the first system information includes information for acquisition of the second system information, and
- wherein the second system information includes service component identification information for identifying each of one or more service components, service name information, and service description information;
- deinterleaving the broadcast signal;
- decoding the deinterleaved broadcast signal;
- derandomizing the decoded broadcast signal;
- acquiring the second system information based on the first system information; and
- providing the service to a user by processing the service data based on the second system information,
- wherein the broadcast signal further includes known data, wherein the known data are used for synchronization.
12. A receiving system for processing data, the receiving system comprising:
- a tuner to receive a broadcast signal including service data for a service, first system information, and second system information, wherein the first system information includes information for acquisition of the second system information, and wherein the second system information includes service component identification information for identifying each of one or more service components, service name information, and service description information;
- a deinterleaver to deinterleave the broadcast signal;
- a decoder to decode the deinterleaved broadcast signal;
- a derandomizer to derandomize the decoded broadcast signal;
- a first processor to acquire the second system information based on the first system information; and
- a second processor to provide the service to a user by processing the service data based on the second system information,
- wherein the broadcast signal further includes known data, wherein the known data are used for synchronization.
| 5208816 | May 4, 1993 | Seshardi et al. |
| 5258987 | November 2, 1993 | Wei |
| 5301167 | April 5, 1994 | Proakis et al. |
| 5502506 | March 26, 1996 | Choi |
| 5508752 | April 16, 1996 | Kim et al. |
| 5544060 | August 6, 1996 | Fujii et al. |
| 5619269 | April 8, 1997 | Lee et al. |
| 5634138 | May 27, 1997 | Ananthan et al. |
| 5649284 | July 15, 1997 | Yoshinobu |
| 5691993 | November 25, 1997 | Fredrickson |
| 5722047 | February 24, 1998 | Murayama |
| 5754651 | May 19, 1998 | Biatter et al. |
| 5757416 | May 26, 1998 | Birch et al. |
| 5787090 | July 28, 1998 | Van Niekerk et al. |
| 5841478 | November 24, 1998 | Hu et al. |
| 5841819 | November 24, 1998 | Hu et al. |
| 5867503 | February 2, 1999 | Ohsuga et al. |
| 5903324 | May 11, 1999 | Lyons et al. |
| 5909184 | June 1, 1999 | Tajima |
| 5924068 | July 13, 1999 | Richard et al. |
| 5956373 | September 21, 1999 | Goldston et al. |
| 5978424 | November 2, 1999 | Turner |
| 6021421 | February 1, 2000 | Retter et al. |
| 6049651 | April 11, 2000 | Oshima |
| 6124898 | September 26, 2000 | Patel et al. |
| 6163683 | December 19, 2000 | Dunn et al. |
| 6211800 | April 3, 2001 | Yanagihara et al. |
| 6212659 | April 3, 2001 | Zehavi |
| 6219386 | April 17, 2001 | Amrany et al. |
| 6232917 | May 15, 2001 | Baumer et al. |
| 6233295 | May 15, 2001 | Wang |
| 6243469 | June 5, 2001 | Kataoka et al. |
| 6289485 | September 11, 2001 | Shiomoto |
| 6334187 | December 25, 2001 | Kadono |
| 6339618 | January 15, 2002 | Puri |
| 6411253 | June 25, 2002 | Cox et al. |
| 6434477 | August 13, 2002 | Goss et al. |
| 6438561 | August 20, 2002 | Israni et al. |
| 6459741 | October 1, 2002 | Grabb et al. |
| 6490007 | December 3, 2002 | Bouillet et al. |
| 6498936 | December 24, 2002 | Raith |
| 6505117 | January 7, 2003 | Ratert et al. |
| 6512759 | January 28, 2003 | Hashimoto et al. |
| 6515713 | February 4, 2003 | Nam |
| 6553538 | April 22, 2003 | Zehavi |
| 6573947 | June 3, 2003 | Oh |
| 6594576 | July 15, 2003 | Fan et al. |
| 6651250 | November 18, 2003 | Takai |
| 6665343 | December 16, 2003 | Jahanghir |
| 6671002 | December 30, 2003 | Konishi et al. |
| 6686880 | February 3, 2004 | Marko et al. |
| 6724439 | April 20, 2004 | Horwitz |
| 6731700 | May 4, 2004 | Yakhnich et al. |
| 6734920 | May 11, 2004 | Ghosh et al. |
| 6744474 | June 1, 2004 | Markman |
| 6760077 | July 6, 2004 | Choi et al. |
| 6768517 | July 27, 2004 | Limberg et al. |
| 6775334 | August 10, 2004 | Liu et al. |
| 6803970 | October 12, 2004 | Limberg et al. |
| 6810084 | October 26, 2004 | Jun et al. |
| 6816204 | November 9, 2004 | Limberg |
| 6917655 | July 12, 2005 | Fimoff et al. |
| 6924753 | August 2, 2005 | Bretl et al. |
| 6927708 | August 9, 2005 | Fimoff |
| 6944242 | September 13, 2005 | Yakhnich et al. |
| 6947487 | September 20, 2005 | Choi et al. |
| 6952595 | October 4, 2005 | Ikedo et al. |
| 6956619 | October 18, 2005 | Choi et al. |
| 6973137 | December 6, 2005 | Birru et al. |
| 6975689 | December 13, 2005 | McDonald et al. |
| 6977914 | December 20, 2005 | Paila et al. |
| 6980603 | December 27, 2005 | Choi et al. |
| 6985537 | January 10, 2006 | Milbar et al. |
| 6993021 | January 31, 2006 | Chuah et al. |
| 6993062 | January 31, 2006 | Kong et al. |
| 6996133 | February 7, 2006 | Bretl et al. |
| 7010038 | March 7, 2006 | Choi et al. |
| 7016446 | March 21, 2006 | Spalink |
| 7020481 | March 28, 2006 | Kivijarvi et al. |
| 7030935 | April 18, 2006 | Choi et al. |
| 7038732 | May 2, 2006 | Limberg et al. |
| 7042949 | May 9, 2006 | Omura et al. |
| 7085324 | August 1, 2006 | Choi et al. |
| 7092370 | August 15, 2006 | Jiang et al. |
| 7092447 | August 15, 2006 | Choi et al. |
| 7092455 | August 15, 2006 | Choi et al. |
| 7096484 | August 22, 2006 | Mao et al. |
| 7102692 | September 5, 2006 | Carlsgaard et al. |
| 7110449 | September 19, 2006 | IIeo et al. |
| 7111221 | September 19, 2006 | Birru et al. |
| 7130313 | October 31, 2006 | Pekonen |
| 7148932 | December 12, 2006 | Choi et al. |
| 7151575 | December 19, 2006 | Landry et al. |
| 7161497 | January 9, 2007 | Gueziec |
| 7177909 | February 13, 2007 | Stark et al. |
| 7181417 | February 20, 2007 | Langseth et al. |
| 7194047 | March 20, 2007 | Strolle et al. |
| 7209459 | April 24, 2007 | Kangas et al. |
| 7221358 | May 22, 2007 | Sasaki |
| 7251558 | July 31, 2007 | McGrath |
| 7269505 | September 11, 2007 | Zhao et al. |
| 7277709 | October 2, 2007 | Vadgama |
| 7343487 | March 11, 2008 | Lindqvist et al. |
| 7376074 | May 20, 2008 | Jung et al. |
| 7440516 | October 21, 2008 | Kim et al. |
| 7450613 | November 11, 2008 | Choi et al. |
| 7454683 | November 18, 2008 | Vesma et al. |
| 7460606 | December 2, 2008 | Choi et al. |
| 8179982 | May 15, 2012 | Limberg |
| 20010011213 | August 2, 2001 | Hindie et al. |
| 20010028314 | October 11, 2001 | Hessing et al. |
| 20010034867 | October 25, 2001 | Jaffe et al. |
| 20020001353 | January 3, 2002 | Citta |
| 20020056103 | May 9, 2002 | Gong |
| 20020082767 | June 27, 2002 | Mintz |
| 20020085632 | July 4, 2002 | Choi et al. |
| 20020126222 | September 12, 2002 | Choi et al. |
| 20020136197 | September 26, 2002 | Owen et al. |
| 20020150246 | October 17, 2002 | Ogino |
| 20020154709 | October 24, 2002 | Choi et al. |
| 20020159520 | October 31, 2002 | Choi et al. |
| 20020172154 | November 21, 2002 | Uchida et al. |
| 20020186790 | December 12, 2002 | Choi et al. |
| 20020187767 | December 12, 2002 | Meehan |
| 20020191716 | December 19, 2002 | Xia et al. |
| 20020194570 | December 19, 2002 | Birru et al. |
| 20030007103 | January 9, 2003 | Roy |
| 20030046431 | March 6, 2003 | Belleguie |
| 20030067899 | April 10, 2003 | Chen et al. |
| 20030078930 | April 24, 2003 | Surcouf et al. |
| 20030093798 | May 15, 2003 | Rogerson |
| 20030099303 | May 29, 2003 | Birru et al. |
| 20030152107 | August 14, 2003 | Pekonen |
| 20030206053 | November 6, 2003 | Xia et al. |
| 20030223519 | December 4, 2003 | Jeong et al. |
| 20030234890 | December 25, 2003 | Bae et al. |
| 20040028076 | February 12, 2004 | Strolle |
| 20040034491 | February 19, 2004 | Kim |
| 20040061645 | April 1, 2004 | Seo et al. |
| 20040090997 | May 13, 2004 | Choi et al. |
| 20040101046 | May 27, 2004 | Yang et al. |
| 20040105507 | June 3, 2004 | Chang et al. |
| 20040110522 | June 10, 2004 | Howard et al. |
| 20040125235 | July 1, 2004 | Kim et al. |
| 20040148642 | July 29, 2004 | Park et al. |
| 20040156460 | August 12, 2004 | Kim et al. |
| 20040198339 | October 7, 2004 | Martin |
| 20040260985 | December 23, 2004 | Krieger |
| 20050024543 | February 3, 2005 | Ramaswamy et al. |
| 20050037721 | February 17, 2005 | Benz et al. |
| 20050052571 | March 10, 2005 | Ghosh |
| 20050054345 | March 10, 2005 | Lee |
| 20050090235 | April 28, 2005 | Vermola et al. |
| 20050097428 | May 5, 2005 | Chang et al. |
| 20050111586 | May 26, 2005 | Kang et al. |
| 20050129132 | June 16, 2005 | Choi et al. |
| 20050157758 | July 21, 2005 | Yoo |
| 20050162886 | July 28, 2005 | Jeong et al. |
| 20050166244 | July 28, 2005 | Moon |
| 20050168641 | August 4, 2005 | Seo |
| 20050175080 | August 11, 2005 | Bouillett |
| 20050206534 | September 22, 2005 | Yamane et al. |
| 20050249300 | November 10, 2005 | Jeong et al. |
| 20050249301 | November 10, 2005 | Jeong et al. |
| 20050271158 | December 8, 2005 | Birru |
| 20050281294 | December 22, 2005 | Gaddam et al. |
| 20060002389 | January 5, 2006 | Lee |
| 20060015914 | January 19, 2006 | Lee |
| 20060029159 | February 9, 2006 | Oh |
| 20060039460 | February 23, 2006 | Fimoff et al. |
| 20060039503 | February 23, 2006 | Choi et al. |
| 20060052052 | March 9, 2006 | Jung et al. |
| 20060072623 | April 6, 2006 | Park |
| 20060078072 | April 13, 2006 | Cheon et al. |
| 20060088119 | April 27, 2006 | Fu et al. |
| 20060104391 | May 18, 2006 | Choi et al. |
| 20060126757 | June 15, 2006 | Choi et al. |
| 20060130099 | June 15, 2006 | Van Rooyen |
| 20060133429 | June 22, 2006 | Seo et al. |
| 20060140301 | June 29, 2006 | Choi et al. |
| 20060146797 | July 6, 2006 | Lebizay |
| 20060146955 | July 6, 2006 | Choi et al. |
| 20060159183 | July 20, 2006 | Gaddam et al. |
| 20060184965 | August 17, 2006 | Lee et al. |
| 20060223461 | October 5, 2006 | Laroia et al. |
| 20060245488 | November 2, 2006 | Puputti et al. |
| 20060245505 | November 2, 2006 | Limberg |
| 20060246836 | November 2, 2006 | Simon et al. |
| 20060248563 | November 2, 2006 | Lee et al. |
| 20060253890 | November 9, 2006 | Park et al. |
| 20060262227 | November 23, 2006 | Jeong |
| 20060262744 | November 23, 2006 | Xu et al. |
| 20060262863 | November 23, 2006 | Park et al. |
| 20060268673 | November 30, 2006 | Roh et al. |
| 20060285608 | December 21, 2006 | Kim et al. |
| 20070071110 | March 29, 2007 | Choi et al. |
| 20070076584 | April 5, 2007 | Kim et al. |
| 20070076585 | April 5, 2007 | Kim et al. |
| 20070076586 | April 5, 2007 | Kim et al. |
| 20070076721 | April 5, 2007 | Kim et al. |
| 20070076758 | April 5, 2007 | Kim et al. |
| 20070076759 | April 5, 2007 | Kim et al. |
| 20070086488 | April 19, 2007 | Kim et al. |
| 20070092043 | April 26, 2007 | Yu et al. |
| 20070093943 | April 26, 2007 | Nelson et al. |
| 20070121681 | May 31, 2007 | Kang et al. |
| 20070127598 | June 7, 2007 | Kang et al. |
| 20070130495 | June 7, 2007 | Yoon et al. |
| 20070136643 | June 14, 2007 | Kang et al. |
| 20070140368 | June 21, 2007 | Kim et al. |
| 20070168844 | July 19, 2007 | Jeong et al. |
| 20070195889 | August 23, 2007 | Hong et al. |
| 20070201544 | August 30, 2007 | Zhu et al. |
| 20070230607 | October 4, 2007 | Yu et al. |
| 20070253502 | November 1, 2007 | Park et al. |
| 20070268979 | November 22, 2007 | Chang et al. |
| 20080008155 | January 10, 2008 | Yoon et al. |
| 20080095096 | April 24, 2008 | Cho et al. |
| 20080273589 | November 6, 2008 | Kim et al. |
| 20090028230 | January 29, 2009 | Leitner |
| 20090077588 | March 19, 2009 | Sugai |
| 1335019 | February 2002 | CN |
| 1505403 | June 2004 | CN |
| 1582580 | February 2005 | CN |
| 1635558 | July 2005 | CN |
| 100 60 599 | June 2002 | DE |
| 100 60 599 | June 2002 | DE |
| 0 566 330 | August 1993 | EP |
| 0 677 965 | October 1995 | EP |
| 0 912 008 | April 1999 | EP |
| 1 041 755 | October 2000 | EP |
| 1 061 746 | December 2000 | EP |
| 1 079 353 | February 2001 | EP |
| 1 085 750 | March 2001 | EP |
| 1 145 474 | October 2001 | EP |
| 1 150 265 | October 2001 | EP |
| 1 211 822 | June 2002 | EP |
| 1 445 750 | August 2004 | EP |
| 1 555 826 | July 2005 | EP |
| 1 566 905 | August 2005 | EP |
| 1 596 513 | November 2005 | EP |
| 1 628 420 | February 2006 | EP |
| 1 768 396 | March 2007 | EP |
| 2 402 307 | December 2004 | GB |
| 2 406 483 | March 2005 | GB |
| 10-322228 | December 1998 | JP |
| 2000-224136 | August 2000 | JP |
| 2001-54031 | February 2001 | JP |
| 2001-82967 | March 2001 | JP |
| 2001-274769 | October 2001 | JP |
| 2002-218339 | August 2002 | JP |
| 2003-32640 | January 2003 | JP |
| 2003-101812 | April 2003 | JP |
| 2003-134117 | May 2003 | JP |
| 2003-209525 | July 2003 | JP |
| 2003-284037 | October 2003 | JP |
| 2004-129126 | April 2004 | JP |
| 2004-140811 | May 2004 | JP |
| 2004-214829 | July 2004 | JP |
| 2005-56061 | March 2005 | JP |
| 2006-148543 | June 2006 | JP |
| 2007-010368 | January 2007 | JP |
| 2007-096403 | April 2007 | JP |
| 10-1998-007139 | March 1998 | KR |
| 10-2000-0040481 | July 2000 | KR |
| 10-2001-0055543 | July 2001 | KR |
| 10-2001-0055543 | July 2001 | KR |
| 10-2001-0111667 | December 2001 | KR |
| 10-2002-0080992 | October 2002 | KR |
| 10-2002-0082268 | October 2002 | KR |
| 10-2002-0082268 | October 2002 | KR |
| 10-2002-0089078 | November 2002 | KR |
| 10-2002-0094427 | December 2002 | KR |
| 10-2003-0026236 | March 2003 | KR |
| 10-2003-0037138 | May 2003 | KR |
| 10-2003-078354 | October 2003 | KR |
| 10-2004-0032282 | April 2004 | KR |
| 10-2004-0032283 | April 2004 | KR |
| 10-2004-0083248 | October 2004 | KR |
| 10-2004-0108314 | December 2004 | KR |
| 10-2005-0041489 | May 2005 | KR |
| 10-2005-0049923 | May 2005 | KR |
| 10-2005-0065898 | June 2005 | KR |
| 10-2005-0077255 | August 2005 | KR |
| 10-2005-0077255 | August 2005 | KR |
| 10-2005-0091057 | September 2005 | KR |
| 10-2005-0091057 | September 2005 | KR |
| 10-2005-0093921 | September 2005 | KR |
| 10-2006-0009737 | February 2006 | KR |
| 10-2006-0012510 | February 2006 | KR |
| 10-2006-0013999 | February 2006 | KR |
| 10-0565089 | March 2006 | KR |
| 10-2006-0039728 | May 2006 | KR |
| 10-2006-0057266 | May 2006 | KR |
| 10-2006-006367 | June 2006 | KR |
| 10-2006-0063867 | June 2006 | KR |
| 10-2006-0065435 | June 2006 | KR |
| 10-2006-0068449 | June 2006 | KR |
| 10-2006-0068989 | June 2006 | KR |
| 10-2006-0070665 | June 2006 | KR |
| 10-2006-0072573 | June 2006 | KR |
| 10-2006-0095126 | August 2006 | KR |
| 10-2006-0095235 | August 2006 | KR |
| 10-2006-0102160 | September 2006 | KR |
| 10-2006-112159 | October 2006 | KR |
| 10-2006-0117484 | November 2006 | KR |
| 10-2006-0133011 | December 2006 | KR |
| 10-2007-0007995 | January 2007 | KR |
| 10-2007-0034215 | March 2007 | KR |
| 10-2007-0068960 | July 2007 | KR |
| 10-2002-0089078 | November 2009 | KR |
| WO 95/16312 | June 1995 | WO |
| 00/30058 | May 2000 | WO |
| WO 01/05157 | January 2001 | WO |
| WO 2001/28246 | April 2001 | WO |
| 01/31497 | May 2001 | WO |
| WO 2002/001849 | January 2002 | WO |
| WO 02/13161 | February 2002 | WO |
| WO 02-080559 | October 2002 | WO |
| WO 2002/085014 | October 2002 | WO |
| WO 03/003747 | January 2003 | WO |
| WO 03/032148 | April 2003 | WO |
| WO 03/069885 | August 2003 | WO |
| WO 2003/092197 | November 2003 | WO |
| WO 2004/043073 | May 2004 | WO |
| WO 2004/107619 | December 2004 | WO |
| WO 2005/006759 | January 2005 | WO |
| 2005/020576 | March 2005 | WO |
| WO 2005-032034 | April 2005 | WO |
| WO 2005/045603 | May 2005 | WO |
| WO 2005/064942 | July 2005 | WO |
| 2005/071958 | August 2005 | WO |
| WO 2005/071958 | August 2005 | WO |
| WO 2005/101655 | October 2005 | WO |
| WO 2005/109877 | November 2005 | WO |
| WO 2005/109878 | November 2005 | WO |
| WO 2005/115001 | December 2005 | WO |
| WO 2005/120062 | December 2005 | WO |
| WO 2005/122573 | December 2005 | WO |
| WO 06/001635 | January 2006 | WO |
| WO 2006-003531 | January 2006 | WO |
| WO 2006/004303 | January 2006 | WO |
| WO 2006/028337 | March 2006 | WO |
| WO 2006/065071 | June 2006 | WO |
| WO 2006/126805 | November 2006 | WO |
| WO 2007/018397 | February 2007 | WO |
| WO 2007/021157 | February 2007 | WO |
| WO 2007/068294 | June 2007 | WO |
| WO 2008/105587 | September 2008 | WO |
- Notice of Allowance of Korean Patent Office in Appl'n No. 10-2006-0089736, dated May 31, 2013.
- U.S. Appl. No. 14/534,912 dated Nov. 6, 2014.
- U.S. Appl. No. 12/840,878 dated Jul. 21, 2010, (now U.S. Pat. No. 8,473,807).
- Yao et al., “IP Datacasting and Channel Error Handling with DVB-H”, Emerging Information Technology Conference, Aug. 15, 2005, pp. 61-63.
- Traffic and Travel Information (TTI)—TTI via Transport Protocol Expert Group (TPEG) data-streams—Part 2: Syntax. Semantics and Framing Structure (SSF), IOS/TS 18234-2, Jun. 2006.
- U.S. Appl. No. 14/552,652, filed Nov. 25, 2014.
- U.S. Appl. No. 14/534,912, filed Nov. 6, 2014.
- U.S. Appl. No. 12/840,878, filed Jul. 21, 2010, (now U.S. Pat. No. 8,473,807).
- Kim et al., “Enhanced-x-VSB System Development for Improving ATSC Terrestrial DTV Transmission Standard”, IEEE Transactions on Broadcasting, vol. 52, No. 2, Jun. 2006, pp. 129-131.
- Touzni et al., “Enhanced 8-VSB Transmission for North-American HDTV Terrestrial Broadcast”, IEEE International Conference on Acoustics, Speech, and Signal Processing, Apr. 6, 2003, pp. 437-440.
- Gaddam et al., “A Newly Proposed ATSC DTV System for Transmitting a Robust Bit-stream along with the Standard Bit-stream”, IEEE Transactions on Consumer Electronics, vol. 49, No. 4, Nov. 2003, pp. 933-938.
- Fimoff et al., “E_VSB Map Signaling”, IEEE Transactions on Consumer Electronics, vol. 49, No. 3, Aug. 2003, pp. 515-519.
- Uehara et al., “Transmission Scheme for the Terrestrial ISDB System”, IEEE Transaction on Consumer Electronics, vol. 45, No. 1, Feb. 1999, pp. 101-106.
- DVB Document A092 Rev. 2 (Draft v1.3.1), DVB-H Implementation Guidelines, May 2007.
- ETSI TR 102 377, V1.2.1, Digital Video Broadcasting (DBV); DVB-H Implementation Guidelines.
- ETSI EN 300 401, V1.4.1, Radio Broadcasting Systems; Digital Audio Broadcasting (DAB) to mobile, portable and fixed receivers.
- ATSC A/54A, Recommended Practice: Guide to the Use of the ATSC Digital Television Standard, including Corrigendum No. 1.
- ATSC A/53D, ATSC Standard: Digital Television Standard (A/53), Revision D, Including Amendment No. 1.
- Federal Information Processing Standards Publication 197, “Advanced Encryption Standard (AES)”, Nov. 2001.
- ISO/IEC 13818-1 Second Edition, “Information Technology Generic coding of moving pictures and associated audio information: Systems”, Dec. 2000.
- Graell, et al., “Analysis and Design of Rate Compatible Serial Concatenated Convolutional Codes”,IEEE Proceedings, International Symposium, Sep. 2005, pp. 607-611.
- ATSC Doc. A/112, “ATSC Recommended Practice: E-VSB Implementation Guidelines”, Apr. 2006.
- Bev Marks, TPEG—Standardized at Last, Oct. 2005, EBU Technical Review, 14 pages.
- Rich Chemock, PSIP Generation and ATSC Stream Monitoring, Oct. 8, 2004, Triveni Digital, WEBE SMPTE; 63 pages.
- A/53D ATSC Standard; Digital Television Standard (A/53), Revision D, Including Amendment No. 1, Jul. 27, 2005, 104 pages.
- ISO/IEC 13818-1, Second Edition, Dec. 1, 2002, Information Technology—Generic Coding of Moving Pictures and Associated Audio Information: Systems, 174 pages.
- European Broadcasting Union, Transport Protocol Experts Group (TPEG), TPEG specifications—Part 1: Introduction, Numbering and Versions, TPEG-INV/002, BPN 027-1, Oct. 29, 2002.
- European Broadcasting Union, Transport Protocol Experts Group (TPEG), TPEG specifications Part 2: Syntax, Semantics and Framing Structure, TPEG-SSF_3.0/002, BPN 027-2, Oct. 7, 2002.
- European Broadcasting Union, Transport Protocol Experts Group (TPEG), TPEG specifications—Part 3: Service and Network Information Application, TPEG-SNI_3.0/002, BPN 027-3, Oct. 8, 2002.
- European Broadcasting Union, Transport Protocol Experts Group (TPEG), TPEG specifications—Part 4: Road Traffic Message Application, TPEG-RTM_3.0/003, BPN 027-4, Oct. 29, 2002.
- European Broadcasting Union, Transport Protocol Experts Group (TPEG), TPEG specifications—Part 5: Public Transport Information Application, TPEG-PTI_3.0/001, BPN 027-5, Dec. 19, 2002.
- European Broadcasting Union, Transport Protocol Experts Group (TPEG), TPEG specifications—Part 6: Location Referencing for Applications, TPEG-Loc_3.0/001, BPN 027-6, Oct. 29, 2002.
- Traffic and Travel Information (TTI)—TTI via Transport Protocol Expert Group (TPEG) data-streams—Part 1: Introduction, numbering and versions, ISO/TS 18234-1, Jun. 2006.
- Traffic and Travel Information (TTI)—TTI via Transport Protocol Expert Group (TPEG) data-streams—Part 2: Syntax, Semantics and Framing Structure (SSF), ISO/TS 18234-2, Jun. 2006.
- Traffic and Travel Information (TTI)—TTI via Transport Protocol Expert Group (TPEG) data-streams—Part 3: Service and Network Information (SNI) application, ISO/TS 18234-3, Jun. 2006.
- Traffic and Travel Information (TTI)—TTI via Transport Protocol Expert Group (TPEG) data-streams—Part 4: Road Traffic Message (RTM) application, ISO/TS 18234-4, Jun. 2006.
- Traffic and Travel Information (TTI)—TTI via Transport Protocol Expert Group (TPEG) data-streams—Part 5: Public Transport Information (PTI) application, ISO/TS 18234-5, 2006.
- Traffic and Travel Information (TTI)—TTI via Transport Protocol Expert Group (TPEG) data-streams—Part 6: Location referencing applications, ISO/TS 18234-6, 2006.
- Transport Protocol Experts Group (TPEG), TPEG Specifications—Part xx: Congestion and Travel-Time Information, TPEG-CTT_9.0/001 (KSX6917-5).
Type: Grant
Filed: Jan 29, 2019
Date of Patent: Jul 6, 2021
Assignee: LG ELECTRONICS INC. (Seoul)
Inventors: Jin Pil Kim (Seoul), Young In Kim (Seoul), Ho Taek Hong (Seoul), In Hwan Choi (Seoul), Kook Yeon Kwak (Gyeonggi-do), Hyoung Gon Lee (Seoul), Byoung Gill Kim (Seoul), Jin Woo Kim (Seoul), Won Gyu Song (Seoul), Jong Moon Kim (Gwangmyeong-si)
Primary Examiner: Colin M Larose
Application Number: 16/260,646
International Classification: H03M 13/29 (20060101); H04H 20/55 (20080101); H04H 20/95 (20080101); H04L 1/00 (20060101);
