EP1836630A1

EP1836630A1 - Recoding medium for point of information/news information service frame structure, and apparatus for processing application service based on tpeg protocol using the same

Info

Publication number: EP1836630A1
Application number: EP05821288A
Authority: EP
Inventors: Young-Ho Jeong; Sam-Mo Cho; Geon Kim; Chung-Hyun Ahn; Young-Kwon Hahm; Kyu-Heon Kim; Soo-In Lee
Original assignee: Electronics and Telecommunications Research Institute ETRI
Current assignee: Electronics and Telecommunications Research Institute ETRI
Priority date: 2004-12-06
Filing date: 2005-12-06
Publication date: 2007-09-26
Also published as: WO2006062324A1; EP1836630A4

Abstract

Provided are a recording medium for a point of interest/news information service frame and an apparatus for processing a TPEG based application service using the same. The apparatus includes: a receiver for receiving a TPEG protocol based broadcasting stream related to traffic and travel information (TTI) through a broadcasting communication network; an analyzer for analyzing the received broadcasting frame, discarding frame having errors and extracting frames having no errors; a decoder for classifying the extracted frames by TTI related data through analyzing characteristics of service components of the extracted frame; a storing unit for storing and managing the classified TTI related data into corresponding TTI related database; a controller for receiving a TTI service request from a user, searching a corresponding TTI related database according to the TTI service request and outputting the searched TTI related data; and an outputting unit for outputting the corresponding TTI related data.7.

Description

RECODING MEDIUM FOR POINT OF INFORMATION/NEWS INFORMATION

SERVICE FRAME STRUCTURE, AND APPARATUS FOR PROCESSING APPLICATION SERVICE BASED ON TPEG PROTOCOL USING THE SAME

Description Technical Field

The present invention relates to a recording medium for a point of interest/news information service frame and an apparatus for processing a TPEG based application service using the same; and more particular to, a recording medium for a point of interest/news information service frame and an apparatus for processing a TPEG based application service using the same by defining a frame structure to provide a high value added application service such as the point of interest (POI) information and news information based on the transport protocol experts group (TPEG) protocol and providing the high value added application service based on the defined frame structure through a digital broadcasting system.

Background Art

A digital broadcasting system generally provides a digital television broadcasting service, a digital satellite broadcasting service and a digital audio broadcasting service. Recently, the digital broadcasting system begins to provide multimedia data broadcasting service such as traffic and travel information (TTI), an electric program guide (EPG) and game contents. Among the multimedia data broadcasting services, the TTI service has been spotlighted in aspects of economic influence and information usability. For example, the demand of TTI service has dramatically increased due to rapid increase in the number of vehicles and population of frequently traveling on long-weekends. In order to satisfy such a demand, a transport protocol experts group (TPEG) protocol was introduced. One of objects of the TPEG is to provide effective traffic and travel information through the digital broadcasting system. However, there are few specifications, i.e., a road traffic message (RTM) and public transport information (PTI), defined as TTI application service up to now. And, they are in the process of standardizing specifications for parking information (PKI), congestion and travel time information (CTT), weather information (WEA) and environment information alerts (EIA) in TPEG Forum.

However, there is no consideration to standardize new service specifications for providing point of interest (POI) or news information, which are very valuable for drivers and travelers and no effort to develop a high value added TTI service through extending typical application service specifications.

The TTI is transmitted through various transmission medium such as FM radio broadcasting, Internet and mobile communication. However, such a TTI must be classified and modified into a standardized system for time limitation and accuracy. Accordingly, the TTI transmission may be basically divided into classification, modification and transmission. Fig. 1 is a block diagram illustrating conventional TPEG data transmitter and receiver that are developed to provide traffic and travel information (TTI) through various transmission mediums such as a digital broadcasting network. The conventional TPEG based data transmitter and receives communicates one another through TPEG data transmission structure shown in Fig. 2.

In 1997, Europe broadcasting union (EBU) constitutes a B/TPEG project group to develop a new protocol for transmitting TTI in multimedia environment. After one year later, the B/TPEG group officially introduces a specification for TPEG-SSF (Part 2) and TPEG-RTM (Part 4). Herein, the TPEG-SSF is used for entire TPEG protocol, and the TPEG-SSF defines syntax, semantic and a frame structure, Also, the TPEG-RTM defines specifications for transmitting traffic information message.

Meanwhile, CEN TC 278 WG 4 constitutes another project group including the B/TPEG members in 1999 and develops two specifications TPEG-SNI (Part 3) and TPEG-INV (Part 1) for supporting services. The TPEG-SNI (Part 3) describes information about services and networks and the TPEG-INV (Part 1) defines information management for introduction, numbering system and version development.

The B/TPEG group announced revision of specifications Part 1 through Part 4 in Apr., 2000. Also, the B/TPEG group introduces TPEG-Loc specification as a reference plan for locating information and TPEG-PTI (Part 5) specification for transmitting public transport information. TPEG can be applied into various digital transmission media having proper stack structure and TPEG messages are used to deliver TTI information from a database of a service provider to a terminal of a user.

TPEG allows to be modified or to be added with new functions without disturbing existing receivers and decoders. For example, TPEG may be widely used for applications requiring effective information transmission in one-to-many manner. Also, TPEG is proper to be adopted into one-to-one manner or multicast application.

Specifications for TPEG protocol defined up to now are as follows. - TPEG-INV (Part 1): management for introduction, numbering system and version

TPEG-SSF (Part 2): grammar, semantic and frame structure for TPEG

TPEG-SNI (Part 3): information management for service and network information - TPEG-RTM (Part 4): definitions for traffic information transmission

- TPEG-PTI (Part 5): definitions for public transport information transmission - TPEG-Loc (Part 6): definition of structure for related information and linked positioning information

In the TPEG forum, it is in the progress for standardizing specifications for parking information (PKI), congestion and travel time information (CTT), weather information (WEA) and environment information alerts (EIA) . However, TTI application services defined in the TPEG protocol are provided within boundaries of traffic information such as RTM and PTI. In order to breakthrough such a limitation of typical TPEG based TTI service, there is a great demand to develop a new TTI service specifications for effectively provides new TTI service related information such as point of interest and news information through broadcasting data channel which has limited data transfer rate while maintaining application service and compatibility with the existing specifications defined in TPEG.

Disclosure Technical Problem

It is, therefore, an object of the present invention to provide an apparatus for processing a TPEG based application service in order to overcome various limitations of TPEG based application services and to provide an high value added application services such as the POI and news information by defining a frame structure for effectively provide the high value added service through a digital broadcasting system while maintaining compatibility to a conventional TPEG protocol, and a computer readable recording medium having data of the frame structure.

Technical Solution

In accordance with one aspect of the present invention, there is provided an apparatus for processing a transport protocol experts group (TPEG) based application service, including: a receiving unit for receiving a TPEG protocol based broadcasting stream related to traffic and travel information (TTI) through a broadcasting communication network; an analyzing unit for analyzing the received broadcasting frame, discarding frame having errors and extracting frames having no errors; a decoding unit for classifying the extracted frames by TTI related data through analyzing characteristics of service components of the extracted frame; a storing unit for storing and managing the classified TTI related data into corresponding TTI related database; a controlling unit for receiving a TTI service request from a user, searching a corresponding TTI related database according to the TTI service request and outputting the searched TTI related data; and an outputting unit for outputting the corresponding TTI related data in response to the controlling unit. In accordance with another aspect of the present invention, there is provided a computer readable recording medium recording a data of a transport protocol experts group (TPEG) frame including: a component data field in a service component frame for defining a point of interest (POI) information or a road traffic message (RTM) information, wherein the component data field includes a message management container subfield for managing a POI message, a POI/RTM event container subfield for transmitting the POI and a TPEG-LOC component subfield for storing location information related to the POI. In accordance with still another aspect of the present invention, there is provided a computer readable recording medium recording a data of a transport protocol experts group (TPEG) frame including: a component data field in a service component frame includes a message management container subfield for managing a new message and a news information event container subfield for transmitting news information.

In order to overcome various limitations of a conventional TPEG protocol based TTI service such as RTM and PTI services, the present invention introduces a method of effective providing a high value added TTI services such as a POI and news information services while maintaining compatibility with a conventional TPEG protocol in order to effectively provide various TTI services through limited data broadcasting channel and satisfy the compatibility with a TPEG based TTI receiver.

Herein, it is an object of the POI service to provide a high value added information and reservation information such as travel information, cultural information, public facilities, accommodations and hospitals to a driver, a pedestrian or a person who travels to a particular destination. It is an object of the news information service to provide current news information collected from various media including politics, economy, society and entertainment to a user.

Advantageous Effects

According to the present invention, a transmission mechanism is introduced for overcoming various limitations of a conventional TPEG based TTI service, effectively transmitting a high value added service such as POI and news information service while maintaining a compatibility with a conventional TPEG protocol. Therefore, various types of high value added TTI services can be provide through a limited data broadcasting channel.

Description of Drawings

The above and other objects and features of the present invention will become apparent from the following description of the preferred embodiments given in conjunction with the accompanying drawings, in which: Fig. 1 is a block diagram illustrating conventional TPEG data transmitter and receiver;

Fig. 2 shows transmission of traffic and travel information source and TPEG services;

Fig. 3 is a block diagram of a new component based TPEG frame structure for transmitting POI information in accordance with a preferred embodiment of the present invention;

Fig. 4 is a block diagram of a RTM component based TPEG frame structure for transmitting POI information in accordance with a preferred embodiment of the present invention;

Fig. 5 is a block diagram of a RTM component based TPEG frame structure for transmitting POI information in accordance with another embodiment of the present invention;

Fig. 6 is a block diagram of a new component based TPEG frame structure for transmitting news information in accordance with a preferred embodiment of the present invention; Fig. 7 is a block diagram of an apparatus for transmitting a TPEG based application service in accordance with a preferred embodiment of the present invention;

Fig. 8 is a flowchart of a method of processing a POI and news information stream in an apparatus of processing a TPEG based application service in accordance with a preferred embodiment of the present invention;

Fig. 9 is a flowchart of a method of calling a POI and news information stream in an apparatus of processing a TPEG based application service in accordance with a preferred embodiment of the present invention;

Fig. 10 shows a graphic user interface (GUI) of a receiver (navigation system) for TPEG service in accordance with a preferred embodiment of the present invention;

Fig. 11 shows GUIs of a POI service of a receiver in accordance with a preferred embodiment of the present invention; and

Fig. 12 shows GUIs of a news information service of a receiver in accordance with a preferred embodiment of the present invention.

Best Mode for the Invention

Other objects and aspects of the invention will become apparent from the following description of the embodiments with reference to the accompanying drawings, which is set forth hereinafter.

In order to effectively service point of interest (POI) and news information through a digital broadcasting system, new TPEG application services for POI and new information is disclosed. In the present invention, the POI service is provided by extending a typical RTM service transmission specification, and both of the POI service and news information service are designed to have compatibility with all of typical TPEG protocols. Hereinafter, new TPEG application service frame structure for effectively providing services while maintaining compatibility to typical TPEG protocol will be described with reference to Figs. 3 through 6.

Fig. 3 is diagram of a new component based TPEG frame structure for POI information transmission in accordance with a preferred embodiment of the present invention.

As shown in Fig. 3, a transport frame is composed of a plurality of fields including a Sync Word, a Field Length, a cyclic redundancy check (CRC), a Frame Type and a Service Frame.

Among those fields, the service frame field further includes a plurality of service identification fields SID-A to SID-C, an Encryption Indicator field, a component multi- flex (fn) field having a plurality of Service Component Frame fields 1 to n.

Herein, each field of the Service Component Frame 1 through n also includes a service Component Identifier field, a Field Length field, a cyclic redundancy check (CRC) field and a component data field. The component data filed, which is new POI component, includes a message management container field for managing a POI message, an event container field for transmitting POI information and a TPEG-Loc component field having POI related location information. The POI component is composed of the elements shown in following Table. 1, that is, Mandatory elements, Data and Time, Effect and reliability and Event descriptive.

Table 1

Mandatory elements

POI Message (mid, ver , ) Date and time elements

Message generation time

Start tune

Stop time

Message expiry time Effect and reliability elements

Seventy factor

Unverified information Event descπptive elements

Classification

Description

Reservation

Time Info

Parking Info In Table 1, ^λEvent descriptive elements' contains real POI information and thus it is called as an Event container. The ^ΛEvent descriptive elements' is configured of sub- elements, i.e., ^Classification' , ^Description' , Reservation' , ^λTime Info' and ^Parking Info' . Each of sub-elements includes details shown in following Table 2.

Table 2

Classification Description

Image data Reservation

Reservation description lime Info

Time instance

Service day type

Timetable type Parking

Parking Space

Rate Info

Basic rate 1 ime limit Additional rate

A coding method forO POI application service to maintain compatibility with a TPEG protocol and POI application primitives are shown in following Table 3.

Table 3

1. Message Management Container

: It is identical to components of RTM and PTI services of a conventional TPEG

1.2 Coding of the Message Management Container

1.2.1 Point of interest

<point_of_interest> :=

<intunli>(mid), Message ID

<intunti>(ver), Version number <intunli> Number of bytes following the length indicator

<bitswitch>(selector), Message elements supplied if (selector = xxxxxxxl) <time_t>, Message generation time if (selector = xxxxxxlx) <time_t>, Start time if (selector = xxxxxlxx) <time_t>, Stop time if (selector = xxxxlxxx) <time_t>, Message expiry time if (selector = xxxlxxxx) <poi23>, Severity factor, see TPEG table poi23 if (selector = xxlxxxxx) <intunlo>, Reserved for future use if (selector = xlxxxxxx) <poi24>, Unverified information, see TPEG table poi24 if (selector = lxxxxxxx) <poL_components>; Point Of Interest components

- it is a management container of POI which contains entire information of POI

- whether a message is updated or not is indicated by mid and ver

- <time_t> denotes a time of making a message , a time of begin or end a message : , or a time of expire .

- service factor and unverified information denote priority of message

1 .2 .2 POI components template

<poi_components>:=

<intunti>(n), : Number of components n*<poi_component()>; : Point of interest component

1.2 .3 POI component template

<poi_component(x)>:= : Point of interest component template

<intunti>(id), '• Identifier (id)

<intunli>(n), : Length, n, if component data in bytes n*<byte>; : Component data

1.2 .4 POI component - TPEG-Loc link

<poi_component(DO)> : = TPEG-Location Referencing (see TPEG-Loc)

<intunti>(id), Identifier, id = DO hex

<intunli>(n), Length, n, of component data in bytes

<tpeg_loc_container>; TPEG-Location Container - TPEG-Loc component denotes location information of POI

2. Event Container

2.1 Coding of Event Container 2.1.1 Classification

<poLcomponent(C0) > : = Classification

<intuntiXid), Identifier, id = CO hex

<intunli>(n), Length, n, of component data in bytes

<poi01>(type), classification of POI

< intunti> (subtype) , sub-classification of POI, see table in section 2 3 1 m* <classif ication_component() > ; classification components

- it is classification of POI

- a type is defined as poiOl table and subtype thereof is defined according to table of section 2.2.1

2.1.1.1 Classification component template

<classif ication_component(x)> : = • Classification component

<intuntiXid), : Identifier, id = CO hex

<intunli>(n), Length, n, of component data in bytes

N*<byte>; • component data

2.1.2 Description

<poi_component(C2) > : = • Description

<intunti>(id), : Identifier, id = C2 hex

<intunli>(n), • Length, n, of component data in bytes

<poi25>, • language code

<poil7>, • type of description

<short_string>, ' description

M*<description_component()>; • description components

- a language of string to be displayed at description is indicated with reference to poi25 a type of string' s contents is indicated by value of poil7 2.1.2.1 Description component template

<description_component(x)> : = : Description component template

<intunti>(id), '• Identifier, id = x hex

<intunli>(n), : Length, n, of component data in bytes n*<byte>; : component data

2.1.2.2 Image data

<description_component(01)> : = '■ Image data of description component

<intunti>(id), : Identifier, id = 01 hex

<intunli>(n), : Length, n, of component data in bytes

<graph_type>, : type of graphic file n*<byte>; : graphic file

- it denotes image related to the description

- <graph_type>

<graph_type>:= : Graphic type

<intunti>; : Entry number in graphics type selection table

2.1.3 Reservation

<poi_component(C3)> : = : Reservation <intunti>(id), : Identifier, id = C3 hex <intunli>(n), : Length, n, of component data in bytes <poil8>, : status of POI for reservation m*<reservation_component()>; : Reservation components

- it denotes information related to reservation

- the pos sibility of reservation is indicated by a value of poi l 8

2.1 . 3.1 Reservation component template

<reservation_component(x) > : = Reservation component template

<intunti>(id), Identifier, id = x hex

<intunli>(n), Length, n, of component data in bytes n*<byte>; component data

2.1 . 3.2 description of reservation

< reservation _component(01)>:= Description of reservation component

<intunti>(id), Identifier, id = 01 hex

<intunliXn), Length, n, of component data in bytes

<poi25>, language code of description

<poi27>, type of description

<short_string>; description it denotes details related to reservation

- a type of contents is indicated by poi27

2.1. - \ Time information

<poi_component(C4)>:= : Time Information

<intunti>(id), : Identifier, id = C4 hex

<intunli>(n), '■ Length, n, of component data in bytes

<poil9>, : scheduled or predicted m*<time_information_component()>; : Time information components

- it denotes time information related to poi

2.1 ." \Λ Time information component template

<time_information_component(x)>:= : Time information component template

<intunti>(id), : Identifier, id = x hex

<intunli>(n), : Length, n, of component data in bytes n*<byte>; '■ component data

_{J CV} 2.1 .4.2 time instance

< time_information _component(01)>:= ■ time instance

<intunti>(id), : Identifier, id = 01 hex

<intunli>(n), : Length, n, of component data in bytes

<poi20>, : time type

<time_local>; : Time including local offset

- it denotes each of time information

- a type of time information is indicated by poi20

2. 1. 4.3 Service day type

< time_information _component(02)>:= : Service day type

<intunti>(id), : Identifier, id = 02 hex

<intunli>(n), : Length, n, of component data in bytes

<poi21>; : Service day type

- it denotes a type of service data weekdays /weekends /holiday ) of time instance

2. 1 . 5.4 Timetable type

< time_information _component(03)>:= : Timetable ype

<intunti>(id), : Identifier, id = 03 hex

<intunli>(n), : Length, n, of component data in bytes

<poi22>; : Timetable type

- it denotes types of scheduler

1 . 5 Parking Information

<poi_component(C 1)> : = : Parking information

<intunti>(id), : Identifier, id = Cl hex

<intunli>(n), : Length, n, of component data in bytes m* <parking_inf ormation_component() > I : parking information components

- denotes parking information of POI

2. 1 ., 5.1 Parking information component template

<parking_inf ormation_component(x) > : = : Parking information component template

<intunti>(id), : Identifier, id = x hex

<intunli>(n), : Length, n, of component data in bytes n*<byte>; component data

2. 1. 5.2 Parking space information

<parking_information_component(01)>:= Parking space information component

<intunti>(id), Identifier, id = 01 hex

<intunli>(n), Length, n, of component data in bytes

<poil6>, type of parking place

<intunli>; amount of parking lot it denotes type of parking lot ( poil β ) and available spaces of parking lot

2. 1. 5.3 Rate Information

< parking_information_component (02)>:= Rate Information component

<intunti>(id), Identifier, id = 02 hex

<intunh>(n), Length, n, of component data in bytes

<poi26>, Currency type m*<rate_information_component()>; rate information components

2. 1 . 5.3.1 Rate information component template

<rate_inf ormation_component(x) > : = Rate information component template

<intunti>(id), Identifier, id = x hex

<intunli>(n), Length, n, of component data in bytes

N*<byte>; component data

2. 1., 5.3.2 Basic rate information

<r ate_inf ormation_component(01) > : = Basic rate information component

<intunti>(id), Identifier, id = 01 hex

<intunli>(n), Length, n, of component data in bytes

<intunli>; Basic rate

- it denotes bas ic fee of parking lot.

2. 1 .J 5.3.3 Time limit information

<rate_information_component(02)>:= Time limit information component

<intunti>(id), Identifier, id = 02 hex

<intunli>(n), Length, n, of component data in bytes

Differently from Fig. 3 that shows the new component based on TPEG frame structure, Figs. 4 and 5 shown a RTM component based on TPEG frame structure for transmitting POI information.

As shown in Fig. 4, a transport frame is configured of a plurality of fields including a Sync Word, a Field Length, a Cyclic Redundancy Check (CRC), a Frame Type and a Service Frame. Among those fields, the service frame field further includes a plurality of service identification fields SID-A to SID-C, an Encryption Indicator field, a component multiplex (fn) field having a plurality of Service Component Frame fields 1 to n. Herein, each field of the Service Component Frames 1 through n also includes a Service Component Identifier field, a Field Length field, a Cyclic Redundancy Check (CRC) field and a component data field.

Especially, the component data field, which is RTM component, includes a message management container field for managing a POI message, an RTM event container field for transmitting POI information and a TPEG-Loc component field having POI related location information.

Among those fields, a POI event class is defined as 8D (ID=8D) in the RTM event container field after conventional RTM components, that is, 'accident (ID=80)', 'obstructions (ID=81)', 'activities (ID=82)', 'road conditions (ID=83)' , 'network performance (ID=84)', 'network conditions (ID=85)', 'facilities performance (ID=86)' , 'moving hazard (ID=87)' , 'security alert (ID=88)', 'public transport information (ID=89)', 'visibility (ID=8A)' , 'weather (ID=8B)' and 'diversion advice (ID=8C)'.

Referring to Fig. 5, a transport frame is configured of a plurality of fields including a Sync Word, a Field

Length, a Cyclic Redundancy Check (CRC), a Frame Type and a

Service Frame. Among those fields, the service frame field further includes a plurality of service identification fields SID-A to SID-C, an Encryption Indicator field, a component multiplex (fn) field having a plurality of

Service Component Frame fields 1 to n.

Herein, each field of the Service Component Frames 1 through n also includes a service Component Identifier field, a Field Length field, a c Cyclic Redundancy Check (CRC) field and a component data field.

Especially, the component data filed, which is RTM component, includes a message management container field for managing a POI message, an RTM event container field for transmitting POI information and a TPEG-Loc component field having POI related location information.

Among those fields, the RTM event container field includes 'Facilities Performance' component of RTM that has similar characteristics to the POI information and the

'Facilities Performance' event class is defined as ID=86. 'Roadside Service' component is defined as ID=02 in the

'Facilities Performance (ID=86)' component. The POI information is inserted in the 'Roadside Service (ID=02)' component. Herein, a size of the POI information is limited by 256 bytes since the size of the 'Roadside Service' component is one byte. As described above, various POI information can be included in the TPEG frame by inserting the new POI information component for transmitting the POI information.

Examples of inserting various POI information are shown in Tables 4 through 8.

Table 4 shows an example of inserting POI information related to a fuel station in the POI information component.

Table 4

Message Management Container

Classification

Type(poiOlrCar), Subtype(poi02:fuel state) : classification (car/fuel station)

Description

Type(poil7:Name) String("Shell station") : define a type by a name of fuel station

Description

Type(poil7: Information) String("cost of fuel")

: provide related information such as a cost of fuel

Also, Table 5 shows an example of inserting POI information related to a restaurant.

Table 5

Message Management Container

Classification

Type(poiO 1 :restaurant), Subtype(poi05 : Korean) : classification (restaurant/Korean)

Parking

Parking space

Type (poilό: free) : free parking

Amount: 40 : parking space for 40 cars

Description

Type(Name) : name of restaurant

Image data : map image Description

Type(Menu) : menu information

Image data : picture for food

Reservation Info.

Status(poil8 available) : available for reservation

Description

Type(telephone) : telephone number for reservation

Description

Type(Address) : Address of restaurant

Furthermore, Table 6 shows an example of inserting POI information related to an accommodation.

Table 6

Message Management Container

Classification

Type(poi01:3), Subtype(poi04: hotel): classification (accommodation/hotel)

Description

Type (Name) : Hotel name

Image data : Picture for Hotel

Parking Info

Parking space

Type (free) : free parking

Amount: 100 : parking space for 100 cars

Reservation Info

Status(poil8:available(today not available) : vacancy for reservation (no vacancy)

Description

Type (Web link) : web URL for reservation

Description

Type (telephone) : telephone number for reservation

Description

Type (Address) : Hotel Address Moreover, Table 7 shows an example of inserting POI information related to cultural places.

Table 7

Message Management Container

Classification

Type (poi01:ll), Subtype(poil2: movie theater) : Classification (cultural facility/movie theater)

Description

Type(Name) : name of movie theater

Description

Type (Title) : title of movie

Image data : posters of movie

Time Info

Scheduled

Service day type

Type(poi21: weekdays) : schedule for weekdays

Timetable type

Type(poi22 : summer) : schedule for summer

Time instance(l)

Type(poi20: play time) : movie play time(l)

Time(2004-10-25 90:00.. .) : movie begin times

Time instance(2)

Type(poi20: play time) : movie play time(2)

Time(2004-10-25 11:30.. .) : movie begin times

Time instance(n)

Type(poi20: play time) : movie play time(n)

Time(2004-10-25 23:30... .) : movie begin times

Time Info

Scheduled

Service day type

Type(poi21: weekends) : schedule for weekends

Timetable type

Type(poi22:summer) : schedule for summer Time instance(l)

Type(poi20: play time) Time(2004-10-25 90:00....) Time instance(2)

Type(poi20: play time) Time(2004-10-25 11:30....) Time instance(n)

Type(poi20: play time) Time(2004-10-25 23:30....) Parking Info

Parking space

Type(Toll parking lot(indoor)) Amount: 200 Rate info

Basic info

Rate: 50(won*100) Time limit info

Limit: 12(min*10) Additional rate info

Rate:10(wan/min*10) Reservation Info

Status(poil8:available) : availability of reservation

Description

Type(Web link) : Web link for reservation

Description

Type(telephone) : telephone number for reservation

Description

Type(Address) : Address

Table 8 shows an example of inserting POI information related to tourist attractions.

Table 8

Message Management Container Classification

Type(poi01:02),

Subtype(poi03: tourist attraction/scenery : classification(leisure/tourist attraction)

Description

Type(name) : name of tourist attraction

Description

Type(Information) : information for tourist attraction

Image data : pictures for tourist attraction

Description

Type(outline map) : map for tourist attraction

Image data : image for tourist attraction

Parking Info

Parking space

Type(free) : availability of parking

Amount: 150 : parking space for 150 cars

Fig. 6 shows a TPEG frame structure having new component for transmitting news information in accordance with a preferred embodiment of the present invention. As shown in Fig. 6, a transport frame is configured of a plurality of fields including a Sync Word, a Field Length, a Cyclic Redundancy Check (CRC), a Frame Type and a Service Frame.

Among those fields, the service frame field further includes a plurality of service identification fields SID-A to SID-C, an Encryption Indicator field, a component multiplex (fn) field having a plurality of Service

Component Frame fields 1 to n.

Herein, each field of the Service Component Frame 1 through n also includes a service Component Identifier field, a Field Length field, a Cyclic Redundancy Check (CRC) field and a component data field.

Especially, the component data filed, which is news information component field, includes a message management container field for managing news information and a news event container field for transmitting news information. Herein, the new information component field does not include a TPEG-Loc component field due to the characteristics of the news unlike the RTM, PTI and POI information services. Geographical classification is identified through element classification defined in ^λClassification' element.

Herein, the news information event container includes a classification field for identifying types of news, a time information field for time information related news, an article field for containing news data to be transmitted and an authorship field for copyright of the news .

The news information component, which is the article field, is configured of a text field, an image field and a related link field. Also, the news information component is defined by objects of ^Mandatory elements' , ^λData and time elements' , ^Effect and reliability elements' , and ^λEvent descriptive elements' as shown in following Table 9.

Table 9

Mandatory elements

News Message (mid, ver , Date and time elements

Message generation time

Start time

Stop time

Message expiry time Effect and reliability elements

Seventy factor

Unverified information Event descriptive elements

Classification([])

Time_Information( [] )

Article([])

Authorsmp([J)

In Table 9, the object of "Event descriptive elements', which is called an event container, practically contains news information data. The ^ΛEvent descriptive elements' includes attributes of the related news information such as 'Classification' , 'Time_information' , 'Article' and 'Authorship' . Table 10 describes the attributes of the object 'Event descriptive elements' in detail.

Table 10

Classification

• news information is classified by 'type' , 'subtype' or 'status'

• 'type' and 'subtype' denote a type of news information and are used to classify the news by corresponding categories

• 'subtype' is dependable to 'type' and selectable 'subtype's are defined according to each of the 'type's.

• 'status' denotes a current state of news information, and thus it can be used as other reference of classification different from the 'type' and 'subtype'

Time information

• denotes time of making out news information

Article contains articles of news information include components of a 'text' , an 'image' and a 'location information' related to news

'text' describes titles of news information and contents thereof

'Image' includes pictures, drawings related to news information

'Article' component provides links of other information related the news information related information are a web link, other article component or location information

'Web link' denotes web addresses of news information to see entire contents or related information of the news information. It is provided to allow a platform to two-way communicate through the web link.

• TPEG-Loc component is used as location information

Authorship

• denotes a company having a copyright of the news information and information about journalist who makes out the news information

Table 11 shows a coding method of the news information service while maintaining comparability with a TPEG protocol and primitives of the news information service.

Table 11

1 . Message Management Container

: it is identical to components of RTM, PTI service of a conventional TPEG

1 .2 Coding of the Message Management Container

1 .2.1 News

<News>:=

<intunli>(mid), Message ID

<intunti>(ver), Version number

<intunli> Number of bytes following the length indicator

<bitswitch>(selector), Message elements supplied if (selector = xxxxxxxl) <time_t>, Message generation time if (selector = xxxxxxlx) <time_t>, Start time if (selector = xxxxxlxx) <time_t>, Stop time if (selector = xxxxlxxx) <time_t>, Message expiry time if (selector = xxxlxxxx) <newsO3>, Seventy factor, see TPEG table news 03 if (selector = xxlxxxxx) <intunlo>, Reserved for future use if (selector = xlxxxxxx) <newsO4>, Unverified information see TPEG table newsO4 if (selector = lxxxxxxx) <news_components>, News components

-it is a management container of news, which contains entire information of news

- <time_t> denotes a time of making out massage, a time of begin and end of message, and an expiry time

- severity factor and unverified information denote priority of message

1.2.2 News components template

<news_components>:=

<intunti>(n), Number of components n*<news_component()>; News component

- it is a template of news component and denotes the number of inside components

1.2.3 News component template

<news_component(x) > : = News component template

<intunti>(id), Identifier (id)

<intunli>(n), Length, n, if component data in bytes n*<byte>; Component data

- it denotes template of each of news components

2. Event Container

2.1 Coding of Event Container 2.1.1 Classification

<news_component(EO)> : = Classification

<intunti>(id), Identifier, id = EO hex

<intunli>(n), Length, n, of component data in bytes

<newsO5>(type), type of news

<intunti> (subtype) , subtype of news, see table in section 2 3 1

<newsθl> status of news

- it contains classification information of news - news category is decided by type and subtype 2.1.2 Time Information

<ne ws_component(E 1 ) > : = : Time information

<intunti>(id), : Identifier, id = El hex

<intunli>(n), : Length, n, of component data in bytes

<local_time>, : reported time m*<time_information_component()>; : time information components

2.1.3.1 Time information component template

<time_information_component(x)>:= : time information component template

<intunti>(id), : Identifier, id = x hex

<intunli>(n), : Length, n, of component data in bytes

N*<byte>; : component data

2.1.4 Article

- it contains real contents of news

- it stores title and contents as string

2.1.4.1 Article component template

<article_component(x)>:= : Article component template

<intunti>(id), : Identifier, id = x hex

<intunli>(n), : Length, n, of component data in bytes

N*<byte>; : component data

2.1.4.2 Image data

<article_component(01)> : = : Image data of article component

<intuntiXid), : Identifier, id = 01 hex

<intunli>(n), : Length, n, of component data in bytes <graph_type>, : type of graphic file N*<byte>; : graphic file

- it stores image or picture related to the news

- <graph_type>

<graph_type>:= : Graphic type

<intunti>; : Entry number in graphics type selection table

2.1.4.3 Related Link

<article_component(02)> : = : related link of article component

<intunti>(id), : Identifier, id = 02 hex

<intunli>(n), : Length, n, of component data in bytes

M*<related_link_component()> ; : Related link components

- it denotes related news, web link, location information related to news

2.1.4.3.1 Related Link component template

<related_link_component(x) > : = : Related link component template

<intunti>(id), : Identifier, id = x hex

<intunli>(n), : Length, n, of component data in bytes

N*<byte>; : component data

2.1.4.3.2 Original text web link

<related_link_component(01 ) > : = : Original text web link component <intunti>(id), : Identifier, id = 01 hex

<intunli>(n), : Length, n, of component data in bytes

<short_string>; : URL of web link

- it denotes Web link information

2.1 .4.3.3 Related article link

<related_link_component(02)> := : Related article link component

<intuntiXid), : Identifier, id = 01 hex

<intunli>(n), : Length, n, of component data in bytes m*<news_component()>; : Link of related article

- it shows related news using other new components

2.1.4.3.4 TPEG-Loc link

<news_component(03) > : = : TPEG-Location Referencing (see TPEG-Loc)

<intunti>(id), : Identifier, id = FO hex

<intunli>(n), : Length, n, of component data in bytes

<tpeg_loc_container> I : TPEG-Location Container

- it shows location information related to news using

TPEG-Loc component

2.1 .5 Authorship

<news_component(E3)> : = : Authorship

<intuntiXid), : Identifier, id = E3 hex

<intunli>(n), : Length, n, of component data in bytes m*<authorship_component()> ; ■ ' authorship components

- it denotes author information of news

2.1 .5.1 Authorship component template

< author ship_component(x) > : = : Authorship component template

<intunti>(id), : Identifier, id = x hex

<intunti>(n), ■ ' Length, n, of component data in bytes n*<byte>; '■ component data

2.1 .5.2 Authorship Information

<authorship_component(01)>:- = : Authorship information component

255

Code IWord (English) Word I Comments [Examples

Fig. 7 is a block diagram of an apparatus for processing a TPEG based application service in accordance with a preferred embodiment of the present invention. As shown in Fig. 7, the apparatus for processing a TPEG based application service includes: a broadcasting stream receiving module 10 for receiving a TPEG protocol based broadcasting stream related to point of interest (POI) information, i.e., POI broadcasting stream, news information broadcasting stream, or POI and news information broadcasting service, through broadcasting and communication network; a parser 20 for analyzing the received broadcasting stream, discarding frames having errors, extracting frames having no error and outputting the extracted frames; a decoder 30 for receiving the extracted frames from the parser 20, analyzing service component characteristics of the extracted frames, and classifying the received POI/news information related data according to the service component characteristics; a global list 40 for storing the POI information related data in a POI list 41, a location information (Loc) list 43 and a system network information (SNI), storing the news information related data into a news information (NWS) list 42 and a system network information (SNI) list 44, and managing the POI/news information related data according to characteristics thereof; a controller 50 for receiving a request of POI/news information from a user, searching the global list 40 to find corresponding POI/news information and outputting the found POI/news information; and an output unit 60 for outputting the found corresponding POI/news information in response to the controller 50.

The broadcasting stream may include one of the POI information or the news information. Also, the broadcasting stream may include both of the POI information and the news information. The frame for transmitting the POI must includes a TPEG-Loc component representing location information related to the POI information at the rear of the event container field as shown in Figs. 3 through 6. However, the frame for transmitting the news information does not include the TPEG-Loc component field unlike RTM, PTI and POI service due to the characteristics of the news. The geographical classification is proved through the Classification' . Hereinafter, detailed configuration and operations of the apparatus for processing a TPEG based application service according to the present embodiment will be described.

At first, the broadcasting stream receiving module 10 receives a TPEG based broadcasting stream having POI, news information and traffic information through the broadcasting communication network. Then, the parser 20 and the decoder 30 analyzes the received broadcasting stream, and stores the received broadcasting stream into the global list 40, i.e., the POI list, the NWS list, the LOC list or the SNI list, according to the characteristics of service components based on the analysis result.

Herein, the parser 20 discards frames having errors and extracts frames having no error among the frames of the received TPEG broadcasting stream. Then, the parser 20 transfers the extracted frames to the decoder 30. The decoder 30 classifies the extracted frames by checking a message ID in order to classify the extracted frames and to differently store into corresponding database lists, i.e., the POI list, the NWS list, the LOC list and the SNI list, according to the characteristic of frame information.

The classified data including the POI and the news information are stored into corresponding database as a list such as the POI list, the NWS list, the LOC list and the SNI list according to the service component characteristics through the parser 20 and the decoder 30.

For example, the database includes the point of interest (POI) information list 41, the news information (NWS) information 42, location information (LOC) list 43 and system network information (SNI) list 44. The data are stored in the corresponding database as a list format. The traffic information included in the TPEG broadcasting stream may be stored in the RTM list or the PTI list. Since storing and managing of the RTM list and the PTI list are well-known to those skilled in the art, details thereof are omitted herein.

The POI list 41 is a database for storing information about fuel stations, restaurants, accommodations, cultural information and tourist attractions, and so forth. The NWS list 42 is a database for storing information related to news information such as a type, an article, a time of making out and an author. The LOC list 43 is a database for storing location information related to the POI information or the new information data. The SNI list 44 stores information related to a frame structure and a service structure based on a protocol for transmitting POI/news information.

The global list 40 includes the POI list 41, the news information list 42, the LOC list 43 and the SNI list 44 which are independently stored in corresponding databases.

According to the present invention, a receiver such as a navigation system extracts a list of data, i.e., the POI or the news information, from the global list 40 having the POI list 41, the news information list 42, the LOC list 43 and the SNI list 44 according to the characteristics of data requested by a driver or a pedestrian, and provides related services to the driver or the pedestrian. While providing the services, the receiver rapidly provides the accurate POI and news information through a display as images or a speaker as voices.

Hereinafter, a method of processing POI and news information services included in a TPEG broadcasting stream will be described.

Fig. 8 is a flowchart of a method of processing POI and news information stream in an apparatus of processing a TPEG based application service in accordance with a preferred embodiment of the present invention. A receiver, i.e., a navigation system, begins to receive the broadcasting stream when the receiver is turned on and stops receiving the broadcasting stream when the receiver is turned off. While receiving the broadcasting streams, the receivers classifies the received broadcasting stream by checking a version and a message ID and stores each of the components to corresponding component lists. Before describing the method of processing the POI and the news information, the TPEG broadcasting stream will be explained briefly. The TPEG broadcasting stream denotes continuous flow of data of the POI information, the news information and the traffic information which are receivable to a receiver, i.e., a navigation system, through a broadcasting and communication network. Accordingly, such a TPEG broadcasting stream may be valuable information while the receiver is in on. However, the TPEG broadcasting steam is only data flows un-storable after the receiver is turned off. The traffic information included in the TPEG broadcasting stream may be stored in the RTM list or the PTI list.

At first, the receiver, i.e., a navigation system, is turned on by the user at step S801, the receiver initializes variables of the broadcasting receiving module 10 and controls the broadcasting receiving module 10 to begin to receive the broadcasting stream at step S802. Herein, the controller 50 controls the broadcasting stream receiving module 10. A receiving thread is performed for operating the broadcasting stream receiving module 10 at step S803, the receiving thread analyzes the TPEG broadcasting stream at step S804, and the received frames are added into a list at step S805. That is, each of the received frames is decoded and a frame message ID thereof is checked. If the received frame is the POI data at stop S806, it is stored in the POI list 41 at step S807. If the received frame is the news information data at step S808, it is stored in the NWS list 42 at step S809, and if the received frame is the LOC data at step S810, it is stored in the LOC list 43 at step S811. Furthermore, if the received frame is SNI data at step S812, it is stored in the SNI list 44.

Herein, if the received frame is not included any one of the POI information data, the news information data, the LOC data and the SNI data, data of the received frame is not added into the global list 40.

Then, the receiving thread continuously and repeatedly analyzes and stores the broadcasting stream into corresponding lists while the user uses the services. When the user stops using the service at step S814, the receiver ends to receive the broadcasting stream at step S815 and the receiver, i.e., the navigation system, is turned off at step S816.

Fig. 9 is a flowchart of a method of calling POI information and news information in an apparatus for processing a TPEG based application service in accordance with a preferred embodiment of the present invention. The receiver, i.e., a navigation system, determines whether the received broadcasting stream includes the POI information and the news information data or not, calls the stored component lists 41 to 44 and provides the request information of POI or news information to a user.

As described above, the global list 40 stores the POI list 41, the new information list 42, the LOC list 43 and the SNI list 44. The RTM list and the PTI list may be stored in the global list 40. Since the RTM list and the PTI list are well-known to those skilled in the art, the details thereof are omitted.

At first, the user executes a TTI service function of the receiver, i.e., a navigation system, in order to see a POI and news information and selects a POI information menu or a news information menu among the TPEG service menu displayed on a display, i.e., a LCD, of the receiver as shown in Fig. 10 at step S901. Then, the POI list 41 or the NWS list 42, which are included in the global list 40, is loaded at step S902.

At step S903, the loaded lists are displayed on the display. That is, basic information of the loaded POI list 41 or NWS list 42 is only outputted on the display as a list format. For example, titles of the loaded lists are displayed as the basic information.

Herein, if the user does not select any one of basic information of the loaded lists, the receiver waits for a next command inputted from the user at step S910. If the user selects one of basic information of the loaded lists at step S904, the receiver searches whether or not detailed information related to the selected basic information is received or not at step S905. For example, the search operation may be achieved by checking a version. If it determines that the received POI information or news information are not stored in the lists by checking the version at step S905, detailed information thereof is not displayed and to see the POI and news information is terminated at step S909. If it determines that the received POI information or news information are stored in the lists through checking the version at step S905, corresponding data are read from the database list at step S906 and it determines whether the ID of the selected component is identical to the ID of corresponding component stored in the DB at step S907. Herein, the message ID is checked to determine whether the stored list is information requested by a driver or a pedestrian.

If the message ID of extracted data from the list is not identical at step S907, the step S905 is performed again for determining whether the POI or the news information are in the list or not. However, it may perform the step 910 for waiting for the next command inputted from the user. If the message ID of extracted data from the list is identical at step S907, the detailed information of the POI information or the news information is displayed on the display or is outputted as voice through a speaker.

It is possible to end to see the POI and news information anytime by selecting a corresponding menu, and to return to the previous GUI for selecting the basic list by selecting a corresponding menu.

Fig. 10 shows examples of a GUI of TPEG services in a receiver, i.e., a navigation system, in accordance with a preferred embodiment of the present invention.

Referring to Fig. 10, a TPEG menu 101 displayed on a basic GUI of the receiver is a main menu to see traffic information, point of interest information (POI) and news information. For example, the TPEG menu 101 includes five sub-menus such as a traffic information menu 102, a public traffic information menu 103, a point of interest information menu 104, a news information menu 105 and an option menu 106.

The traffic information menu 102 is to receive a service of real-time traffic condition such as a traffic accident, and the public traffic menu 103 is to have a service receiving information related to train, bus or ship. The POI menu 104 is to use a service receiving information related to restaurants or hospitals and the news information menu 105 is to have a service of receiving headline news. The option menu 106 is for setting environments of TPEG service.

Fig. 11 shows GUIs for the POI when the POI menu 104 is selected for describing a procedure of processing the POI service. Referring to Fig. 11, if the POI menu 104 displayed on the GUI of TPEG service shown in Fig. 10 is selected,

POI components related to the POI service are displayed as shown in Fig. 11. If the user selects a ^λSeoul spaghetti' among the displayed POI components, detail information of

^ΛSeoul spaghetti' restaurant is displayed. That is, information abuts parking lots, menus and images of the

Seoul spaghetti restaurant are displayed. Herein, voice messages about ^ΛSeoul spaghetti' restaurant may be outputted.

Also, the POI information can be filtered according to the request of the user for classifying the POI information into a hospital, a restaurant or an accommodation. The selected POI information is shown with a map.

Fig. 12 shows GUIs for the news information when the news menu 104 is selected for describing a procedure of processing the news information.

Referring to Fig. 12, if the news menu 105 displayed on the GUI of TPEG service shown in Fig. 10 is selected, news components related to the news information service are displayed as shown in Fig. 12. If the user selects a ^Λcold wave hit the Seoul' among the news components, an article, a journalist and a copyright related to the selected new ^Λcold wave hit the Seoul' are displayed with corresponding images. Also, the voice messages related to the selected news is outputted through the speaker.

Also, the news information can be filtered according to the request of the user for classifying the news information into a region, a usage and a weather.

The above described method according to the present invention can be embodied as a program and stored on a computer readable recording medium. The computer readable recording medium is any data storage device that can store data which can be thereafter read by the computer system. The computer readable recording medium includes a read-only memory (ROM), a random-access memory (RAM), a CD-ROM, a floppy disk, a hard disk and an optical magnetic disk.

The present application contains subject matter related to Korean patent application No. 2004-0101833, filed in the Korean Intellectual Property Office on December 6, 2004, and Korean patent application No. 2005- 0082083, filed in the Korean Intellectual Property Office on September 5, 2005, the entire contents of which is incorporated herein by reference.

While the present invention has been described with respect to certain preferred embodiments, it will be apparent to those skilled in the art that various changes and modifications may be made without departing from the scope of the invention as defined in the following claims.

Claims

What is claimed is:

1. An apparatus for processing a transport protocol experts group (TPEG) based application service, comprising: a receiving means for receiving a TPEG protocol based broadcasting stream related to traffic and travel information (TTI) through a broadcasting communication network; an analyzing means for analyzing the received broadcasting frame, discarding frame having errors and extracting frames having no errors; a decoding means for classifying the extracted frames by TTI related data through analyzing characteristics of service components of the extracted frame; a storing means for storing and managing the classified TTI related data into corresponding TTI related database; a controlling means for receiving a TTI service request from a user, searching a corresponding TTI related database according to the TTI service request and outputting the searched TTI related data; and an outputting means for outputting the corresponding TTI related data in response to the controlling means.

2. The apparatus as recited in claim 1, wherein the TTI is point of interest (POI) information and a TPEG frame is configured by defining a POI component or a road traffic message (RTM) in a component data field in a service component frame for providing the POI service through the POI information related TPEG protocol based broadcasting stream.

3. The apparatus as recited in claim 2, wherein a

TPEG frame is configured by defining the RTM component in a component data field in a service component frame and a POI event class is defined in a RTM event container field for providing the POI service through the POI related TPEG protocol based broadcasting stream.

4. The apparatus as recited in claim 2, wherein a TPEG frame is configured by defining a RTM component in a component data field in a service component frame, defining a facilities performance component in a RTM event container field of a RTM component, by defining a roadside service component in a facilities performance component field and defining a POI event class in a roadside service component field for providing the POI service through the POI related TPEG based broadcasting stream.

5. The apparatus as recited in claim 2, wherein each of the P0I/RTM components includes a message management container for managing POI message, a POI/RTM event container for transmitting the POI and a TPEG-LOC component having location information related to the POI.

6. The apparatus as recited in clam 5, wherein the POI event container includes a 'Classification' element denoting classification of the POI, a 'Description' element representing detail information, a 'Reservation' element denoting information related to reservation, a 'Time information' element representing time information related to the POI and a 'parking' element denoting parking information related to the POI.

7. The apparatus as recited in claim 6, wherein the 'Classification' element in configured of information related to a car, a leisure/tourism, a hotel, a restaurant, a medical care, a bank/finance, public facilities, educational facilities, a private organization, a living facilities, cultural facilities, a major building, an industrial facilities and transport facilities.

8. The apparatus as recited in claim 1, wherein the TTI is news information, and a TPEG frame is configured by defining a news information component in a component data field of a service component frame for servicing the news information through the news information related TPEG protocol based broadcasting stream.

9. The apparatus as recited in claim 8, wherein the news information component is configured of a message management container for managing news messages and a news information event container for transmitting news information.

10. The apparatus as recited in claim 9, wherein the news information event container includes a ^λClassification' element for classifying the news information according to characteristics thereof, a ^Λtime information' element denoting time information related to the news or made out the news information, an ^λarticle' element for describing contents of news, and an ^λauthorship' element representing information related to the author of the news•

11. The apparatus as recited in claim 10, wherein the ^Classification' element is configured of information related to a society, a politics, a living and arts, an entertainment, sports, a business, a national, a Tech/IT, an Editorial/Op-Ed, a news photos, and a cartoon/comic.

12. The apparatus as recited in claim 1, wherein the storing means stores the POI/news information data into the POl/news information database, stores location information related to the POI/news information into a location information database, stores a system network information data related to a frame/service structure based on a POI/news information transmit protocol into a system network information database and manages each database as a list independently.

13. A computer readable recording medium recording a data of a transport protocol experts group (TPEG) frame comprising: a component data field in a service component frame for defining a point of interest (POI) information or a road traffic message (RTM) information, wherein the component data field includes a message management container subfield for managing a POI message, a POI/RTM event container subfield for transmitting the POI and a TPEG-LOC component subfield for storing location information related to the POI .

14. The computer readable recording medium as recited in claim 13, wherein a POI event class is defined in the

RTM event container subfield.

15. The computer readable recording medium as recited in claim 13, wherein a facilities performance event class of a RTM having a POI characteristic is defined in the RTM event container subfield, a roadside service event class is defined in the facilities performance component subfield, and a POI event class is defined in the roadside service component subfield.

16. A computer readable recording medium recording a data of a transport protocol experts group (TPEG) frame comprising: a component data field in a service component frame includes a message management container subfield for managing a new message and a news information event container subfield for transmitting news information.

17. The computer readable recording medium as recited in claim 16, wherein the news information event container subfield includes a classification subfield for classifying a characteristic of news, a time information subfield for time information related to the news information, an article subfield for storing article of news information and an authorship subfield for copyright information of news, and the article subfield includes a text element, an image element and a related link element.