KR20090010649A - Dcd server for providing terminal with dynamic content delivery - Google Patents

Abstract

A dynamic content delivery server for providing terminal with dynamic content delivery is provided to perform transmission scheduling about a corresponding contents. The DCD server envelope reception management unit(131) performs the function of receiving the DCD server envelope from the DCD content control server. The package process management part(132) removes server contents meta data included in the DCD server envelope, and performs a function of creating with the DCD client envelope. The server contents meta data store manager(133) performs the function of server contents meta data removed from the DCD server envelope being stored. The transmission scheduler(134) perform the scheduling of transmitting the corresponding contents according to the content type ID information. The DCD client envelope transmission administration unit(135) removes server contents meta data included in the DCD server envelope, and performs the function of transmitting the generated DCD client envelope with the DCD client.

Description

DCD server for providing dynamic content delivery service to a terminal {DCD Server for Providing Terminal with Dynamic Content Delivery}

The present invention relates to a DCD server for providing a dynamic content transmission service to a terminal. More specifically, the DCD server for providing a dynamic content delivery (DCD) service to the terminal manages user information, content related information, and fee related information of a user of the DCD service using newly defined server content metadata. And a DCD server that provides a dynamic content delivery service to a terminal having an effect of providing a satisfactory dynamic content delivery service to a user by performing transmission scheduling for corresponding content.

Nowadays, due to the expansion of network infrastructure, there are many content providers that produce and store the contents that users want, and users can receive the contents by visiting the relevant sites operated by these contents providers. .

In order to effectively deliver such contents, Web Syndication is desperately needed as a way to deliver information that is produced and changed in real time on the Internet, and RSS (Really Simple) is a kind of Web Syndication. Syndication), ATOM, and the like have been proposed and become standard. Such RSS (Really Simple Syndication), ATOM, and the like make it possible to distribute content, and the collection of content through a program such as RSS Reader is also much smoother.

However, in a relatively resource-constrained mobile environment, access to content distributed using RSS / ATOM as in a PC environment is limited. In order to solve this problem, there is a demand for a method for delivering the collected content in an optimized form for mobile terminals, and a representative example is Dynamic Content Delivery (DCD), which is being promoted by the Open Mobile Alliance (OMA). "DCD"). DCD seeks to deliver the user's desired contents to the terminal user in the most effective way by reflecting the user's preference. As a content delivery technique, the DCD server sends a content update (transmission) notification message to the terminal. A push method using a DCD-2 interface for receiving a content update (transmission) request message from a terminal and transmitting the corresponding content to the terminal has been proposed. By the push method using the DCD-2 interface, the user's terminal accesses the site on the wireless Internet in the existing mobile service and goes through the various steps to find the content, thereby making it difficult for the user to visit the content. The purpose of DCD can be achieved by delivering to a user's terminal and providing contents desired by the user by maximizing reflection of the user's preference. In addition, the DCD also accepts a pull method using a DCD-1 interface in which a DCD server transmits content to a terminal by a content updater (transmission) request from an existing user's terminal.

This dynamic content delivery (DCD) technology is a client server model, which is performed by interworking with a DCD server serving as a server for delivering content and a DCD client in a terminal serving as a client for receiving content. It defines the message exchanged between the DCD server and the DCD client, and defines the protocol for the contents and the way of sending and receiving messages.

However, in the conventional DCD technology, there is a problem in that user information, content related information, and fee related information for the DCD service user are not managed.

In addition, in the conventional DCD technology, the user information, content related information, and fee related information for the DCD service user are not managed, and thus there is a problem in that a satisfactory dynamic content transmission service cannot be provided to the user.

In order to solve this problem, the present invention, the DCD server for providing a dynamic content delivery (DCD) service to the terminal using the newly defined server content metadata, the user information, content related information, and charges of the user of the DCD service The purpose of the present invention is to provide a satisfactory dynamic content transmission service to a user by managing related information and scheduling transmission of corresponding content.

According to an aspect of the present invention for achieving the above object, the present invention provides a DCD content in a dynamic content delivery (DCD) system consisting of a terminal including a DCD content providing server (DCD CP), DCD server, DCD client In the DCD server receiving a DCD server envelope containing server content metadata from a server (DCD CP), the server content metadata is a content ID which is an identifier for content. Information, content name information, content type ID information for identifying a content type according to a transmission type, rate type information for transmitting separate content according to a user's plan information, and whether a content is paid or not Charge Flag ID information, Charge Rate information for paid content, and charge information information of the content provided to the user Not to the device characterized in that it comprises one or more of user information for a user to receive (String Charge) information, and a content providing server for providing a dynamic content delivery service.

As described above, according to the present invention, a DCD server for providing a dynamic content transfer (DCD) service to a terminal uses a newly defined server content metadata, user information of a DCD service user, content related information, and There is an effect of providing a satisfactory dynamic content transmission service to a user by managing charge related information and scheduling a corresponding content.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. First of all, in adding reference numerals to the components of each drawing, it should be noted that the same reference numerals are used as much as possible even if displayed on different drawings. In addition, in describing the present invention, when it is determined that the detailed description of the related well-known configuration or function is obvious to those skilled in the art or may obscure the gist of the present invention, the detailed description thereof will be omitted.

1 is a diagram illustrating content packaging for providing a dynamic content delivery (DCD) service to a terminal.

Referring to FIG. 1, a DCD system for providing a Dynamic Content Delivery (DCD) service is referred to as a DCD application 110 and a DCD client 120. The terminal 100, the DCD server 130, and a DCD content provider server (DCD Content Provider: DCD CP, hereinafter referred to as "DCD CP") 140 are configured.

The DCD service can be described as a client server model, and the content stored in the DCD CP 140 is interworked with the DCD client 120 acting as a client and the DCD server 130 acting as a server. The DCD server 130 is transferred to the DCD client 120 in the terminal 100. The delivered content is delivered to the DCD application 110 in the terminal 100 and displayed on the standby screen or the screen display unit of the terminal 100.

The DCD CP server 140 generates server content metadata newly defined in the present invention, and the DCD server envelope and content including the server content metadata to the DCD server 130. It is a device to transmit.

Referring to FIG. 1, when a DCD service is provided, content is packaged using a layered "envelope model" and then the terminal (DC) from the DCD CP 140 via the DCD server 130. To DCD client 120 and DCD application 110. Each "Layer" is a device or DCD module in a DCD system on a path through which content is transmitted, in which each layer starts a content delivery, the DCD CP 140 corresponding to the highest layer, and the DCD server of the next layer. 130, the DCD client 120, which is the next layer of the DCD server 130, and the DCD application 110 corresponding to the lowest layer in content delivery. Each layer is packaged with a unique envelope. The "envelope" of each layer is defined as "Content Metadata" and "next" for the next layer. Nested Envelope ".

There are three types of envelopes according to the reception layer. First, the DCD CP 140 is packaged and delivered from the DCD server 130 to the DCD server envelope 200, and the DCD server 130 is transferred from the DCD server 130 to the DCD client 120. It is packaged and delivered to the DCD Client Envelope "220. From the DCD Client 120 to the DCD Application 110, the" DCD Content Envelope "222 is transmitted. It is packaged and delivered.

First, the DCD Server Envelope 200 is an envelope generated (packaged) in the DCD CP 140 and delivered to the DCD server 130. The DCD Server Envelope 200 receives the DCD server 130 as a reception layer. A "Server Content Metadata" 210 and a "DCD Client Envelope" 220 that is a Nested Envelope.

The DCD server 130 receiving the DCD server envelope 200 removes the server content metadata 210 from the DCD server envelope 200, opens only the server content metadata 210, and utilizes only the information. The DCD client envelope 220 from which the server content metadata 210 has been removed from the DCD server envelope 200 cannot be opened and read by the DCD server 130 and is only sent to the DCD client 120.

The "Server Content Metadata" 210 newly defined in the present invention is a rule for delivering the corresponding content to the DCD client 120, which is the next layer of the DCD server 130, and a rule for processing method. Is defined.

Second, the DCD Client Envelope 200 is an envelope delivered from the DCD server 130 to the DCD client 120, and is a "client content" for the DCD client 120, which is a reception layer. Client content metadata ”221 and a nested envelope“ DCD Content Envelope ”222.

The DCD client 120 receiving the DCD client envelope 220 removes the client content metadata 221 from the DCD client envelope 220 to open only the client content metadata 221 and utilize only the information. The DCD content envelope 222 from which the client content metadata 221 has been removed from the DCD client envelope 220 can not be opened and read by the DCD client 120 and is only sent to the DCD application 110.

The client content metadata 221 defines a rule for delivering the content to the DCD application 110, which is the next layer of the DCD client 120, and a rule about a processing method.

Third, the DCD Content Envelope 222 is an envelope delivered from the DCD client 120 to the DCD application 110, and is an "application content meta" for the DCD application 110, which is a receiving layer. "Server Content Metadata" 2221 and "Content Payload" 2222.

The DCD application 110 that receives the DCD content envelope 222 processes the content payload 2222 based on the application content metadata 2221. In addition, the content payload 2222 may be associated with application content metadata 2221 that the DCD application 110 may use when processing the content, and the content and application content metadata 2221 may be DCD technology. Is outside the range of.

As described above, the present invention is performed by the DCD CP 140 and the DCD server 130 among the three envelopes, the content metadata included in each envelope, and the nested envelope. The server content metadata (210) information contained in the DCD server envelope 200 to be delivered to the newly defined, and the DCD server 130 for providing a dynamic content delivery (DCD) service to the terminal according to the present invention is Receives and stores the newly defined server content metadata 210, and manages the user information, content usage information, and fee information of the DCD service user based on the stored server content metadata 210, By performing scheduling on the transmission, the corresponding content is transmitted to the terminal.

The transmission scheduling method may include various methods such as a scheduling method according to a user's plan, a scheduling method according to a content type (push content, pull content, urgent content), and the like. It can be implemented as various elements in (210). Various elements in the server content metadata 210 proposed by the present invention will be described in detail with reference to FIG. 4.

FIG. 2 is a diagram for describing server content metadata for dynamic content delivery (DCD).

FIG. 2 is a DCD server envelope packaged for transmission from a DCD CP 140 to a DCD server 130 during content packaging for dynamic content transmission described above with reference to FIG. 1. FIG. 2 is a diagram for describing in detail the server content metadata 210 included in the 200.

2, the server content metadata 210 included in the DCD server envelope 200 transmitted from the DCD CP 140 to the DCD server 130 is a postal service. Explain in analogy to

Referring to FIG. 2, the DCD CP 140 transmits the DCD server envelope 200 to the DCD server 130 as a letter including a letter and an envelope. The DCD server 130 separates the envelope server content metadata 210 included in the received DCD server envelope 200 and the DCD client envelope 220 which is a letter, among which the DCD client is a letter. The envelope 220 is sent to the DCD client, and the envelope server content metadata 210 is stored on the DCD server 130 and the information specified in the envelope server content metadata 210 delivers the content. Used as information for

3 and 4 illustrate elements in Server Content Metadata for Dynamic Content Delivery (DCD), and FIG. 3 illustrates Server Content Metadata including a previously defined element. Metadata), and FIG. 4 is a diagram showing Server Content Metadata including an element newly defined in the present invention.

FIG. 3 is a diagram of elements on server content metadata established by a conventional Open Mobile Alliance (OMA) standardization organization.

Referring to FIG. 3, the server content metadata 210 includes an expiration time 2101, an operation after expiration 2102, a priority 2103, a terminal profile 2104, a location 2105, and a state. 2106, and a plurality of elements, including fragmentation 2107.

The expiration time 2101 information is information about an expiry time for the corresponding content and is used as information for identifying content that has not expired.

The post-expiration operation 2102 information is operation information for processing the content when the DCD server expires and may be defined as a removal or replacement operation. If the information corresponding to the removal operation is defined in the post-expiration 2102 information, the DCD server removes the corresponding content that has expired. If the information corresponding to the replacement operation is defined in the post-expiration operation 2102 information, the DCD server replaces the corresponding content that has expired with another content and transmits it to the corresponding terminal.

The priority 2103 information is priority information for the transmission of the corresponding content, and the DCD server is first transmitted to the terminal as the content set to have a high priority.

The terminal profile 2104 information is profile information of a terminal that will receive the corresponding content. When the terminal profile is set, the corresponding content is transmitted only to the terminal corresponding to the terminal profile, and the terminal profile is not set. The corresponding content is transmitted to all terminals.

The location 2105 information is information on a zone of the corresponding terminal. If the terminal is connected to a mobile communication network, the location 2105 information of the corresponding terminal indicates the location information of a base station that is communicating. Can be.

The state 2106 information is information on the current state (Presence) of the DCD client in the terminal.

The fragmentation 2107 information is identification information on whether the corresponding content is fragmented. If the corresponding content is fragmented, it may be set to an information value specific to the fragmentation 2107 information.

FIG. 4 is a diagram illustrating server content metadata including a newly defined element in the present invention.

Referring to FIG. 4, server content metadata including an element newly defined in the present invention includes content ID 2108 information, content name 2109 information, and content according to a transmission type. Content type ID 2110 information for identifying a type, Rate Type 2111 information for transmitting a separate content according to user's plan information, and a charge flag for identifying whether a content is paid ( Charge Flag ID 2112 information, Charge Rate 2113 information for paid content, Charge String message 2114 information of the content provided to the user, and the user who will receive the content. It contains information of one or more of the user information (2115, 2116, 2117).

The content type ID 2110 information is information for identifying a content type according to a delivery type. The content type according to the delivery type includes push content according to a push transmission method and pull content according to a pull delivery method. ), There is emergency content according to the emergency transmission method, and a unique content type ID may be set according to each content type, and the DCD server assigns the corresponding content to the content type ID according to the set content type ID value. The service is provided to the terminal by scheduling in a corresponding transmission method.

For the content set as the content type ID of the push content, the DCD server pushes a content update notification message to the DCD client, receives a content update request message for the corresponding content from the DCD client, and transmits the content. For the content set with the content type ID, the DCD server receives the content update request message for the corresponding content from the DCD client and transmits it. do. The transmission method according to this content type (push content, pull content, urgent content) is called "scheduled transmission method according to the content type".

The rate type 2111 information is information for transmitting a separate content according to the user's plan information. If the specific plan information is set in the rate type 2111 information, the DCD server schedules the content corresponding to the rate type only to the terminal of the specific user who subscribed to the specific plan. Scheduling) to transmit. If the line type information is omitted, the DCD server transmits the corresponding content to all user terminals. Such a transmission method is called a "scheduled transmission method according to a plan."

The charge flag ID 2112 information is information for identifying whether the corresponding content is paid content or free content. The charge flag ID 2112 information may be set to a unique charge flag value for the paid content and the free content.

The charge rate 2113 information is information on a charge rate for the content in which the charge flag ID 2112 is set as an ID value for the paid content.

The charge information message (Charge String) 2114 information is information related to charge information about content provided to a user.

User information (2115, 2116, 2117) is information about a user to receive the content, user ID (2115) information defining a specific user to receive the content, user age (2116) for the specific user to receive the content ) Information, user gender 2116 information for a specific user who will receive the content.

The DCD server 130 for providing a dynamic content delivery (DCD) service to a terminal according to the present invention described above with reference to FIG. 4 receives and stores newly defined server content metadata 210 and stores the server. Based on the content metadata 210, the user information 2115, 2116, 2117, content related information 2108, 2109, 2110, and fee related information 2111, 2112, 2113, 2114 of the user of the DCD service may be used. This content is transmitted to the terminal by performing management and scheduling of the corresponding content.

FIG. 5 is a diagram illustrating an internal configuration diagram of a DCD server that provides a dynamic content delivery (DCD) service using server content metadata including a newly defined element in the present invention.

Referring to FIG. 5, the DCD server 130 that provides a dynamic content delivery (DCD) service using server content metadata including an element newly defined in the present invention is a DCD server envelope reception management unit. 131, a package processing manager 132, a server content metadata storage manager 133, a transmission scheduler 134, and a DCD client envelope transmission manager 135.

The DCD server envelope reception management unit 131 performs a function of receiving a DCD server envelope from a DCD content providing server (DCD CP).

The package processing manager 132 performs a function of generating a DCD client envelope by removing server content metadata included in the DCD server envelope.

The server content metadata storage management unit 133 stores the server content metadata removed from the DCD server envelope.

The transmission scheduler 134 performs scheduling to transmit the corresponding content according to the content type ID information included in the server content metadata stored in the server content metadata storage management unit 133.

The DCD client envelope transmission management unit 135 performs a function of transmitting the generated DCD client envelope to the DCD client by removing the server content metadata included in the DCD server envelope.

The above description is merely illustrative of the technical idea of the present invention, and those skilled in the art to which the present invention pertains may make various modifications and changes without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention but to describe the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The protection scope of the present invention should be interpreted by the following claims, and all technical ideas within the equivalent scope should be interpreted as being included in the scope of the present invention.

As described above, the present invention is applied to a dynamic content delivery (DDC) technology, and a DCD server for providing a dynamic content delivery (DCD) service to a terminal uses a newly defined server content metadata. This is a very useful invention that has the effect of providing a satisfactory dynamic content transmission service to a user by performing management of user information, content related information, and fee related information of a DCD service user and scheduling transmission of the corresponding content.

1 is a diagram illustrating content packaging for providing a dynamic content delivery (DCD) service to a terminal;

FIG. 2 is a diagram for describing server content metadata for dynamic content delivery (DCD); FIG.

FIG. 3 is a diagram illustrating server content metadata including a conventionally defined element; FIG.

4 is a diagram illustrating server content metadata including a newly defined element in the present invention;

FIG. 5 is a diagram illustrating an internal configuration diagram of a DCD server that provides a dynamic content delivery (DCD) service using server content metadata including a newly defined element in the present invention.

<Description of Symbols for Main Parts of Drawings>

100: terminal

110: DCD Application

120: DCD Client

130: DCD Server

140: DCD CP

200: DCD Server Envelope

210: Server Content Metadata

Claims (13)

In a DCD system including a DCD CP, a DCD server, and a terminal including a DCD client, a DCD server envelope including server content metadata from the DCD CP. In the DCD server receiving (DCD Server Envelope), The server content metadata (Server Content Metadata), Content type ID information for identifying a content type according to a transmission type, rate type information for transmitting a separate content according to user's plan information, and a charge flag for identifying whether a content is paid or not Flag) IDD, Charge Rate (Charge Rate) information for the paid content, and Charge Information Message (Charge String) information of the content provided to the user DCD for providing a dynamic content delivery service to the terminal server. The method of claim 1, The server content metadata (Server Content Metadata), And a content ID information, content name information, and user information on a user who will receive the content. The method of claim 1, The DCD content providing server (DCD CP), A DCD server for providing a dynamic content transmission service to a terminal, wherein the server content metadata is generated and the DCD server envelope including the server content metadata is transmitted to the DCD server. . The method of claim 1, The DCD server envelope (DCD Server Envelope), Packaged data transmitted from the DCD content providing server to the DCD server, the server content metadata including a server content metadata and a DCD client envelope. DCD server for providing dynamic content delivery services. The method of claim 4, wherein The DCD Client Envelope, Packaged data transmitted from the DCD server to the DCD client, the dynamic content transmission to the terminal comprising a client content metadata, and a DCD content envelope. DCD server to provide services. The method of claim 5, The DCD server, A DCD server envelope reception management unit configured to receive the DCD server envelope from the DCD content providing server (DCD CP); A package processing manager configured to remove the server content metadata included in the DCD server envelope to generate the DCD client envelope; A server content metadata storage manager configured to store the server content metadata removed from the DCD server envelope; A transmission scheduler configured to perform a scheduling for transmitting the corresponding content according to the content type ID information included in the server content metadata stored in the server content metadata storage management unit; And A DCD client envelope transmission management unit for transmitting the DCD client envelope generated by removing the server content metadata included in the DCD server envelope to the DCD client. DCD server for providing a dynamic content transmission service to the terminal comprising a. The method of claim 1, The content type ID information is, DCD server for providing a dynamic content transmission service to the terminal, characterized in that the ID information for one of the push content (Pull Content), pull content (Pull Content), emergency content (Emergency Content). The method of claim 7, wherein The push content (Push Content), The DCD server pushes a content update notification message to the DCD client, and receives a content update request message from the DCD client. server. The method of claim 7, wherein The pull content (Pull Content), DCD server for providing a dynamic content transmission service to a terminal, characterized in that the DCD server is a content type for receiving and transmitting a content update request message from the DCD client. The method of claim 7, wherein The emergency content (Emergency Content), DCD server for providing a dynamic content transmission service to a terminal, characterized in that the DCD server is a content type that is immediately transmitted to the DCD client. The method of claim 1, The rate type information (Rate Type), In order to transmit separate content according to user's plan information, if the lat type information is omitted, the DCD server transmits the content to all the user's terminals. DCD server. The method of claim 1, The user information, DCD server for providing a dynamic content transmission service to a terminal, characterized in that it comprises at least one of user ID information, user age information, user gender information defining a specific user to receive the content. The method of claim 1, The server content metadata, Expiration time 2101, post-expiration action 2102, priority 2103, terminal profile 2104, location 2105, state 2106, and fragmentation as defined by the Open Mobile Alliance (OMA) standardization organization. (Dragmentation) 2D (DC) server for providing a dynamic content delivery service to the terminal, characterized in that it further comprises an element.

Images