WO2009051351A2 - Method for receiving and transmitting customized content - Google Patents
Method for receiving and transmitting customized content Download PDFInfo
- Publication number
- WO2009051351A2 WO2009051351A2 PCT/KR2008/005535 KR2008005535W WO2009051351A2 WO 2009051351 A2 WO2009051351 A2 WO 2009051351A2 KR 2008005535 W KR2008005535 W KR 2008005535W WO 2009051351 A2 WO2009051351 A2 WO 2009051351A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- client
- capability
- content
- server
- message
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/303—Terminal profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
Definitions
- the present invention relates to a method for transmitting and receiving a content, and more particularly, to a method for transmitting and receiving a customized content based on a capability of a client.
- a client has to access a server that provides contents, and then select a content that can be performed by its own capability thus to install the content.
- a user of the client has a difficulty in discerning which content can be performed (e.g., THEME content for a background screen of the client) among the contents provided by the server. This may cause the user to select and download an undesired content, and thus to pay unnecessary fees.
- the content is for a user interface of the client (e.g., THEME content for a background screen) and consists of a background color, an alphabetical shape, a background size, a background image, etc.
- the client having received an undesired content has to receive a right content, again. i This may cause network resources to be wasted.
- the server has to individually manufacture contents according to a capability of the client. Besides, when a content corresponds to a user interface of the client, the content can not be real time updated.
- a method capable of allowing a client to receive, from a server, only a content that can be performed according to a capability of the client, by exchanging information on its capability with the server.
- a protocol to exchange information on a capability of a client with a server.
- a function unit configured to provide information on a capability of a client to a server, and a receiving unit configured to receive only a content that can be performed by the client.
- a server requests information on a capability of a client to receive the information from the client, and provides a content corresponding to the capability to the client.
- the server sends, to the client, a list of contents and information on a capability to performe the contents on the list, the client receives to download a suitable content based on the capability.
- a method for receiving a customized content comprising: receiving, from a server, a list of contents and a capability required to perform the contents on the list; comparing the received capability with its own capability; and requesting the content from the server when it is determined that the client is able to perform a content on the list by its own capability as a result of the comparison.
- a method for providing a customized content comprising: receiving a capability advertisement message including information on a capability of a client; checking the capability of the client included in the capability advertisement message; receiving a content request message from the client; updating a pre-stored content in correspondence to the capability of the client based on the received content request message; and providing the updated content to the client.
- the client since the client is configured to receive only a content that can be performed by its capability, fees charged to a user can be reduced. Furthermore, since a right content is sent to the client at one time, waste of network resources can be reduced.
- FIG. 1 is a block diagram showing a client and a server according to the present invention
- FIG. 2 is a flowchart showing a content receiving method according to a first embodiment of the present invention
- FIG. 3 is a flowchart showing a content receiving method according to a second embodiment of the present invention.
- FIGs. 4 to 6 are an exemplary view showing values included in a message used to exchange information on a capability of a client. MODES FOR CARRYING OUT THE PREFERRED EMBODIMENTS
- FIG. 1 is a block diagram showing a client and a server according to the present invention.
- a client according to the present invention comprises a User Management/Capability Management Unit 110.
- the client 100 of the present invention comprises a User Management/Capability Management Unit 110, a Download/Installation Unit 120, a Management Object (MO) Set/Management Unit 130, and a Status Reporter 140.
- a User Management/Capability Management Unit 110 a Download/Installation Unit 120
- a Management Object (MO) Set/Management Unit 130 a Management Object (MO) Set/Management Unit 130.
- a Status Reporter 140 a Status Reporter 140.
- the User Management/Capability Management Unit 110 performs a user management function, and a capability management function.
- the user management function allows a user to subscribe to a specific service, e.g., a user interface change service of the client, such as a content providing service or a Lock & Feel customization (LFC) service.
- the capability management function manages a capability of the client by checking whether the client is capable of performing a specific content before the client receives the specific content, and then to provide the capability to a server 200 if necessary.
- the Download/Installation Unit 120 performs a download function, and an installation function.
- the download function is executed by receiving a content from the server 200 based on a communication standard such as
- the download function is executed by reporting or ignoring an error occurring while receiving a content, to the server 200.
- the installation function by the Download/Installation Unit 210 is executed by installing a downloaded content, and by sending, to the Status Reporter 140, a response to completion of the installation.
- the installation function may be executed by performing other functions rather than the installation.
- the MO Set/Management Unit 130 manages information on the content, or information on the client, as a Management Object (MO).
- the MO Set/Management Unit 130 may manage the MO in the form of a tree.
- the MO Set/Management Unit 130 may connect a session to the server 200 thereby to receive a plurality of indications from the server 200.
- the MO Set/Management Unit 130 may receive indications such as sending, installation, removal, update, activation, and deactivation of the content, or an indication such as authentication changes of the content.
- the MO Set/Management Unit 130 may include the User Management/Capability Management Unit 110 and the Download/Installation Unit 210, or may be individually implemented therefrom.
- the Status Reporter 140 reports, to the server 200, a status of the client 100 such as whether the content has been successfully received, and whether the content has been successfully installed.
- the Status Reporter 140 may be connected to the MO Set/Management Unit 130 thereby to report many statuses of the MO to the server 200.
- the client 100 may further comprise a content protection unit.
- the content protection unit serves to safely download the content, to safely perform the content inside the client 100, and not to leak the content to outside.
- the content protection unit protects the content from undesirably corrected or performed.
- the content protection unit may be based on a standard of OMA DRM.
- the server 200 includes a User Management/Capability Management Unit 210, a Transmitting Unit 220, a Remote Controller 230, and a Status Receiver 240.
- the User Management/Capability Management Unit 210 performs a user management function, and a capability management function.
- the user management function is implemented by processing subscription request of the client to a specific service, e.g., an interface change service of the client, such as a content providing service or a Lock & Feel customization (LFC) service.
- the User Management function processes not only starting of the service, but also providing of a service. For instance, when a user subscribes to the LFC service and requests a specific LFC package, the User/Management function is implemented by managing the LFC package and charging.
- the subscription may be achieved in a various manner, e.g., on a web service or through a content purchase request.
- the charging may be also achieved in a various manner.
- the transmitting unit 220 sends, to the client 100, a content requested by the client 100.
- the transmitting unit 220 reconfigures the content based on a capability of the client.
- the remote controller 230 may perform an indication to the client 100.
- the remote controller 230 may send, to the client 100, indications such as sending, installation, removal, update, activation, and deactivation of the content, or an indication such as authentication changes of the content.
- the remote controller 230 may be divided into two parts, e.g., a sending unit and a managing unit.
- the sensing unit serves to send a message for remote management
- the managing unit serves to manage the client 100 based on a standard such as OMA DM.
- the Status/Receiver 240 receives a status report from the client 100, and processes the status report.
- FIG. 2 is a flowchart showing a content receiving method according to a first embodiment of the present invention
- FIGs. 4 to 6 are an exemplary view showing values included in a message used to exchange information on a capability of a client.
- the server 200 updates a pre-stored content such that the client 100 can perform the pre-stored content. Then, the server 200 provides the pre-stored content to the client 100, which will be explained in more detail.
- the User Management/Capability Management Unit 210 of the server 200 informs the client 100 of the service through a 'network initiated ad' message (S101).
- the advertisement may be optionally performed. That is, the server 200 may or may not advertise the service.
- the User Management/Capability Management Unit 110 of the client 100 sends, to the server 200, a message requesting subscription to the service, e.g., a Subscription Request message (S102).
- a message requesting subscription to the service e.g., a Subscription Request message (S102).
- the User Management/Capability Management Unit 210 of the server 200 sends, to the client 100, a message responding to the
- Subscription Request message e.g., a Subscription Response message (S103).
- the User Management/Capability Management Unit 110 of the client 100 sends, to the server 200, information on a capability of the client 100.
- the information on a capability of the client 100 may be sent with being included in a capability advertisement message, e.g., an 'Advertisement of Client Capability' message.
- the Advertisement of Client Capability message consists of values shown in FIG. 4. More concretely, the
- Advertisement of Client Capability includes at least one of OmaLFC, OmaLFCVersion, OmaLFPackage, Supported, OmaLFCDeliveryMethods, OmaLFCModel, OmaLFCRemovalMedia, OmaLFCAuth, OmaLFCCasheSize, OmaLFCcurrentFontSize, OmaLFCcurrentActivepart, OmaLFCSupportedArea, OmaLFCaudioformat, OmaLFCvideoformat, OmaLFCpictureformat, and OmaLFCPreference.
- the User Management/Capability Management Unit 210 of the server 200 receives a message, and checks information on a capability of the client 100 (S105). (6) The User Management/Capability Management Unit 110 of the client 100 sends, to the server 200, a message to request a content, e.g., a 'Content Request' message (S106).
- a content e.g., a 'Content Request' message (S106).
- the User Management/Capability Management Unit 210 of the server 200 sends, to the transmitting unit 220, a message requesting sending, e.g., the 'Content Request' message (S107).
- the transmitting unit 220 of the server 200 sends, to the User Management/Capability Management Unit 210 of the server 200, a message to request information on a capability of the client 100, e.g., a 'client capability list request' message (S 108).
- the User Management/Capability Management Unit 210 of the server 200 sends, to the transmitting unit 220, a message including information on a capability of the client 100, e.g., a 'client capability list response' message (S109).
- the transmitting unit 220 checks capability information of the client 100, and when a pre-stored content can not be operated by a capability of the client 100, the transmitting unit 220 updates the pre-stored content in correspondence to the capability of the client (S 110).
- the transmitting unit 220 of the server 200 sends the content to the client 100 (S111 ). Once the Download/Installation Unit 210 of the client 100 has successfully completed downloading of the content, a message indicating completion of the downloading, e.g., 'Confirmation of download' message is sent to the Status Reporter 140 (S112). Then, the
- Status Reporter 140 sends, to the server 200, a message indicating completion of the downloading, e.g., 'Download Completion' message (S113).
- the MO Set/Management Unit 130 of the client 100 may manage information on a capability of the client 100 as a management object (MO).
- MO management object
- the MO Set/Management Unit 130 may manage the MO about the information in the form of a tree. To this end, the MO Set/Management
- Unit 130 maps the information on a capability of the client onto a tree as an MO, together with the User Management/Capability Management Unit 110 (S117).
- the MO Set/Management Unit 130 of the client may manage information on a content received by the client 100 as an MO. To this end, the
- MO Set/Management Unit 130 maps the information on the content onto a tree as an MO, together with the User Management/Capability Management Unit 110 (S118).
- the Remote Controller 230 of the server 200 may manage the client 100 through the tree.
- FIG. 3 is a flowchart showing a content receiving method according to a second embodiment of the present invention.
- the server 200 sends, to the client 100, a list of contents, and information on a capability of the client required to operate the contents on the list, the client 100 can receive to download a suitable content based on the information on a capability of the client 100. This will be explained in more detail.
- the User Management/Capability Management Unit 110 of the client 100 sends, to the server 200, a message requesting a list of contents possessed by the server 220, and information on a capability requested to operate the contents on the list, e.g., a 'Content List Request with Capability Description' message (S204).
- the User Management/Capability Management Unit 210 of the server 200 sends, to the client 100, a message including a list of contents possessed by the server 200, and information on a capability requested to operate the contents on the list, e.g., a 'Content List Response with Capability Description' message (S205).
- the User Management/Capability Management Unit 110 of the client 100 checks its own capability and a capability necessary to operate the contents on the list (S206). Then, the User Management/Capability Management Unit 110 sends, to the Status Reporter 140, a message indicating that the capability has been completely checked, e.g., a 'Capability Check Notification' message (S207). The Status Reporter 140 sends, to the server 200, the 'Capability Check Notification' message (S208). Then, the Status Receiver 240 of the server 200 receives the 'Capability check Notification' message, and sends it to the User Management/Capability Management Unit 210 (S209).
- a message indicating that the capability has been completely checked e.g., a 'Capability Check Notification' message (S207).
- the Status Reporter 140 sends, to the server 200, the 'Capability Check Notification' message (S208).
- the Status Receiver 240 of the server 200 receives the 'Capability check Notification' message, and sends
- the User Management/Capability Management Unit 110 of the client 100 sends, to the server 200, a message requesting a content having been determined, as a result of the comparison, as a content that can be operated among the contents on the list, e.g., a 'Content Request' message (S210).
- the User Management/Capability Management Unit 210 of the server 200 checks capability information of the client 100. Then, when a pre-stored content can not be operated by a capability of the client 100, the User Management/Capability Management Unit 210 of the server 200 updates the pre-stored content in correspondence to the capability of the client 200 (S211 ). And, the User Management/Capability Management Unit 210 of the server 200 sends, to the transmitting unit 220, a message requesting sending of the content, e.g., a 'Content Request' message (S212). Then, the transmitting unit 220 sends the content to the client 100.
- a message requesting sending of the content e.g., a 'Content Request' message (S212).
- the Download/Installation Unit 210 of the client 100 has completed downloading of the content, a message indicating a successful downloading, e.g., a 'Confirmation of Download' message is sent to the Status Reporter 140 (S214). Then, the Status Reporter 140 sends, to the server 200, a 'Download Completion' message so as to inform a successful downloading (S215).
- the MO Set/Management Unit 130 of the client 100 maps information on a capability of the client 100 onto a tree as an MO, together with the User Management/Capability Management Unit 110 (S216), thereby managing the information on a capability of the client 100 as an MO.
- the MO Set/Management Unit 130 of the client 100 maps information on the content onto a tree as an MO, together with the User Management/Capability Management Unit 110 (S217), thereby managing information on a content received by the client 100 as an MO.
- the Remote Controller 230 of the server 200 can manage the client 100 through the tree (S218).
- the above various embodiments may be implemented by software, hardware or some combination thereof.
- the method according to the present invention may be implemented in a storage medium (e.g., memory inside a mobile device, flash memory, hard disc, etc.), or may be implemented in codes or commands inside a software program that can be executed by a processor (e.g., microprocessor inside a mobile device).
- a storage medium e.g., memory inside a mobile device, flash memory, hard disc, etc.
- a processor e.g., microprocessor inside a mobile device.
Landscapes
- Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
Abstract
A method for transmitting and receiving a customized content based on a capability of a client. Once a server sends, to a client, a list of contents and information on a capability to operate the contents on the list, the client receives to download a suitable content based on the capability. Accordingly, the client is prevented from receiving a content in the absence of a capability to operate the content.
Description
METHOD FOR RECEIVING AND TRANSMITTING CUSTOMIZED
CONTENT
TECHNICAL FIELD
The present invention relates to a method for transmitting and receiving a content, and more particularly, to a method for transmitting and receiving a customized content based on a capability of a client.
BACKGROUND ART
Generally, in the conventional method for downloading a content through a client, a client has to access a server that provides contents, and then select a content that can be performed by its own capability thus to install the content. However, a user of the client has a difficulty in discerning which content can be performed (e.g., THEME content for a background screen of the client) among the contents provided by the server. This may cause the user to select and download an undesired content, and thus to pay unnecessary fees. For instance, when the content is for a user interface of the client (e.g., THEME content for a background screen) and consists of a background color, an alphabetical shape, a background size, a background image, etc., there may occur an error that the client receives an undesired content having a font not supported by the client. In this case, the client having received an undesired content has to receive a right content, again. i
This may cause network resources to be wasted. Furthermore, the server has to individually manufacture contents according to a capability of the client. Besides, when a content corresponds to a user interface of the client, the content can not be real time updated.
DISCLOSURE OF THE INVENTION
Therefore, it is a first object of the present invention to provide a method capable of allowing a client to receive, from a server, only a content that can be performed according to a capability of the client.
It is a second object of the present invention to provide a method capable of exchanging information on a capability of a client with a server so as to allow the client to receive, from the server, only a content that can be performed according to the capability of the client.
It is a third object of the present invention to provide a method capable of providing necessary functions to a client and a server such that the client receives, from the server, only a content that can be performed according to a capability of the client. It is a fourth object of the present invention to provide a method capable of providing processing signals to be exchanged between a client and a server such that the client receives, from the server, only a content that can be performed according to a capability of the client.
According to one aspect of the present invention, there is provided a
method capable of allowing a client to receive, from a server, only a content that can be performed according to a capability of the client, by exchanging information on its capability with the server. According to another aspect of the present invention, there is provided a protocol to exchange information on a capability of a client with a server.
According to still another aspect of the present invention, there is provided a function unit configured to provide information on a capability of a client to a server, and a receiving unit configured to receive only a content that can be performed by the client.
In the present invention, a server requests information on a capability of a client to receive the information from the client, and provides a content corresponding to the capability to the client. Alternatively, once the server sends, to the client, a list of contents and information on a capability to performe the contents on the list, the client receives to download a suitable content based on the capability.
To achieve these and other advantages and in accordance with the purpose of the present invention, as embodied and broadly described herein, there is provided a method for receiving a customized content, comprising: receiving, from a server, a list of contents and a capability required to perform the contents on the list; comparing the received capability with its own capability; and requesting the content from the server when it is determined that the client is able to perform a content on the list by its own capability as a result of the comparison.
According to another aspect of the present invention, there is provided a method for providing a customized content, comprising: receiving a capability advertisement message including information on a capability of a client; checking the capability of the client included in the capability advertisement message; receiving a content request message from the client; updating a pre-stored content in correspondence to the capability of the client based on the received content request message; and providing the updated content to the client. In the present invention, since the client is configured to receive only a content that can be performed by its capability, fees charged to a user can be reduced. Furthermore, since a right content is sent to the client at one time, waste of network resources can be reduced.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram showing a client and a server according to the present invention;
FIG. 2 is a flowchart showing a content receiving method according to a first embodiment of the present invention; FIG. 3 is a flowchart showing a content receiving method according to a second embodiment of the present invention; and
FIGs. 4 to 6 are an exemplary view showing values included in a message used to exchange information on a capability of a client.
MODES FOR CARRYING OUT THE PREFERRED EMBODIMENTS
Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings.
Hereinafter, a method for transmitting and receiving a customized content will be explained in more detail with reference to the attached drawings.
FIG. 1 is a block diagram showing a client and a server according to the present invention.
Referring to FIG. 1 , a client according to the present invention comprises a User Management/Capability Management Unit 110.
More concretely, the client 100 of the present invention comprises a User Management/Capability Management Unit 110, a Download/Installation Unit 120, a Management Object (MO) Set/Management Unit 130, and a Status Reporter 140.
The User Management/Capability Management Unit 110 performs a user management function, and a capability management function. The user management function allows a user to subscribe to a specific service, e.g., a user interface change service of the client, such as a content providing service or a Lock & Feel customization (LFC) service. And, the capability management function manages a capability of the client by checking whether the client is capable of performing a specific content before the client receives the specific content, and then to provide the capability to a server 200 if
necessary.
The Download/Installation Unit 120 performs a download function, and an installation function. The download function is executed by receiving a content from the server 200 based on a communication standard such as
OMA DLOTA and OMA DM. The download function is executed by reporting or ignoring an error occurring while receiving a content, to the server 200. The installation function by the Download/Installation Unit 210 is executed by installing a downloaded content, and by sending, to the Status Reporter 140, a response to completion of the installation. The installation function may be executed by performing other functions rather than the installation.
The MO Set/Management Unit 130 manages information on the content, or information on the client, as a Management Object (MO). Here, the MO Set/Management Unit 130 may manage the MO in the form of a tree. The MO Set/Management Unit 130 may connect a session to the server 200 thereby to receive a plurality of indications from the server 200. For instance, the MO Set/Management Unit 130 may receive indications such as sending, installation, removal, update, activation, and deactivation of the content, or an indication such as authentication changes of the content. The MO Set/Management Unit 130 may include the User Management/Capability Management Unit 110 and the Download/Installation Unit 210, or may be individually implemented therefrom.
The Status Reporter 140 reports, to the server 200, a status of the client 100 such as whether the content has been successfully received, and
whether the content has been successfully installed. The Status Reporter 140 may be connected to the MO Set/Management Unit 130 thereby to report many statuses of the MO to the server 200. Although not shown, the client 100 may further comprise a content protection unit. The content protection unit serves to safely download the content, to safely perform the content inside the client 100, and not to leak the content to outside. The content protection unit protects the content from undesirably corrected or performed. The content protection unit may be based on a standard of OMA DRM.
As shown in FIG. 1 , the server 200 includes a User Management/Capability Management Unit 210, a Transmitting Unit 220, a Remote Controller 230, and a Status Receiver 240.
As aforementioned, the User Management/Capability Management Unit 210 performs a user management function, and a capability management function. The user management function is implemented by processing subscription request of the client to a specific service, e.g., an interface change service of the client, such as a content providing service or a Lock & Feel customization (LFC) service. Also, the User Management function processes not only starting of the service, but also providing of a service. For instance, when a user subscribes to the LFC service and requests a specific LFC package, the User/Management function is implemented by managing the LFC package and charging. The subscription may be achieved in a various manner, e.g., on a web service or through a
content purchase request. The charging may be also achieved in a various manner.
The transmitting unit 220 sends, to the client 100, a content requested by the client 100. Here, when reconfiguration of a pre-stored content is necessary, the transmitting unit 220 reconfigures the content based on a capability of the client.
The remote controller 230 may perform an indication to the client 100.
For instance, the remote controller 230 may send, to the client 100, indications such as sending, installation, removal, update, activation, and deactivation of the content, or an indication such as authentication changes of the content. The remote controller 230 may be divided into two parts, e.g., a sending unit and a managing unit. The sensing unit serves to send a message for remote management, and the managing unit serves to manage the client 100 based on a standard such as OMA DM.
The Status/Receiver 240 receives a status report from the client 100, and processes the status report.
Hereinafter, operations of the client 100 and the server 200 will be explained. FIG. 2 is a flowchart showing a content receiving method according to a first embodiment of the present invention, and FIGs. 4 to 6 are an exemplary view showing values included in a message used to exchange information on a capability of a client.
Referring to FIG. 2, in a content receiving method according to a first
embodiment of the present invention, once information on a capability of the client 100 is provided to the server 200, the server 200 updates a pre-stored content such that the client 100 can perform the pre-stored content. Then, the server 200 provides the pre-stored content to the client 100, which will be explained in more detail.
(1 ) The User Management/Capability Management Unit 210 of the server 200 informs the client 100 of the service through a 'network initiated ad' message (S101). The advertisement may be optionally performed. That is, the server 200 may or may not advertise the service.
(2) The User Management/Capability Management Unit 110 of the client 100 sends, to the server 200, a message requesting subscription to the service, e.g., a Subscription Request message (S102).
(3) The User Management/Capability Management Unit 210 of the server 200 sends, to the client 100, a message responding to the
Subscription Request message, e.g., a Subscription Response message (S103).
(4) The User Management/Capability Management Unit 110 of the client 100 sends, to the server 200, information on a capability of the client 100. Here, the information on a capability of the client 100 may be sent with being included in a capability advertisement message, e.g., an 'Advertisement of Client Capability' message. The Advertisement of Client Capability message consists of values shown in FIG. 4. More concretely, the
Advertisement of Client Capability includes at least one of OmaLFC,
OmaLFCVersion, OmaLFPackage, Supported, OmaLFCDeliveryMethods, OmaLFCModel, OmaLFCRemovalMedia, OmaLFCAuth, OmaLFCCasheSize, OmaLFCcurrentFontSize, OmaLFCcurrentActivepart, OmaLFCSupportedArea, OmaLFCaudioformat, OmaLFCvideoformat, OmaLFCpictureformat, and OmaLFCPreference.
(5) The User Management/Capability Management Unit 210 of the server 200 receives a message, and checks information on a capability of the client 100 (S105). (6) The User Management/Capability Management Unit 110 of the client 100 sends, to the server 200, a message to request a content, e.g., a 'Content Request' message (S106).
(7) Once receiving the 'Content Request' message, the User Management/Capability Management Unit 210 of the server 200 sends, to the transmitting unit 220, a message requesting sending, e.g., the 'Content Request' message (S107).
(8) The transmitting unit 220 of the server 200, sends, to the User Management/Capability Management Unit 210 of the server 200, a message to request information on a capability of the client 100, e.g., a 'client capability list request' message (S 108).
(9) The User Management/Capability Management Unit 210 of the server 200 sends, to the transmitting unit 220, a message including information on a capability of the client 100, e.g., a 'client capability list response' message (S109).
(10) The transmitting unit 220 checks capability information of the client 100, and when a pre-stored content can not be operated by a capability of the client 100, the transmitting unit 220 updates the pre-stored content in correspondence to the capability of the client (S 110).
(11-13) The transmitting unit 220 of the server 200 sends the content to the client 100 (S111 ). Once the Download/Installation Unit 210 of the client 100 has successfully completed downloading of the content, a message indicating completion of the downloading, e.g., 'Confirmation of download' message is sent to the Status Reporter 140 (S112). Then, the
Status Reporter 140 sends, to the server 200, a message indicating completion of the downloading, e.g., 'Download Completion' message (S113).
(14-16) Then, the Download/Installation Unit 210 installs the received content (S114). Upon completion of installation of the received content, the Download/Installation Unit 210 sends, to the Status Reporter 140, a message indicating that the received content has been successfully installed, e.g., a 'Confirmation of Installation' message (S115). Then, the Status Reporter 140 sends, to the server 200, the 'Confirmation of installation' message so as to inform a successful downloading (S116). (17) The MO Set/Management Unit 130 of the client 100 may manage information on a capability of the client 100 as a management object (MO). Here, the MO Set/Management Unit 130 may manage the MO about the information in the form of a tree. To this end, the MO Set/Management
Unit 130 maps the information on a capability of the client onto a tree as an
MO, together with the User Management/Capability Management Unit 110 (S117).
(18) The MO Set/Management Unit 130 of the client may manage information on a content received by the client 100 as an MO. To this end, the
MO Set/Management Unit 130 maps the information on the content onto a tree as an MO, together with the User Management/Capability Management Unit 110 (S118).
(19) Once the capability information and the content information are mapped onto a tree as an MO, the Remote Controller 230 of the server 200 may manage the client 100 through the tree.
FIG. 3 is a flowchart showing a content receiving method according to a second embodiment of the present invention. Referring to FIG. 3, once the server 200 sends, to the client 100, a list of contents, and information on a capability of the client required to operate the contents on the list, the client 100 can receive to download a suitable content based on the information on a capability of the client 100. This will be explained in more detail.
(1-3) Procedures of S201-S203 are same as those of S101-S103.
(4) The User Management/Capability Management Unit 110 of the client 100 sends, to the server 200, a message requesting a list of contents possessed by the server 220, and information on a capability requested to operate the contents on the list, e.g., a 'Content List Request with Capability Description' message (S204).
(5) In response to the 'Content List Request with Capability
Description' message, the User Management/Capability Management Unit 210 of the server 200 sends, to the client 100, a message including a list of contents possessed by the server 200, and information on a capability requested to operate the contents on the list, e.g., a 'Content List Response with Capability Description' message (S205).
(6-9) Once receiving the message, the User Management/Capability Management Unit 110 of the client 100 checks its own capability and a capability necessary to operate the contents on the list (S206). Then, the User Management/Capability Management Unit 110 sends, to the Status Reporter 140, a message indicating that the capability has been completely checked, e.g., a 'Capability Check Notification' message (S207). The Status Reporter 140 sends, to the server 200, the 'Capability Check Notification' message (S208). Then, the Status Receiver 240 of the server 200 receives the 'Capability check Notification' message, and sends it to the User Management/Capability Management Unit 210 (S209).
(10) The User Management/Capability Management Unit 110 of the client 100 sends, to the server 200, a message requesting a content having been determined, as a result of the comparison, as a content that can be operated among the contents on the list, e.g., a 'Content Request' message (S210).
(11-13) In response to the 'Content Request' message, the User Management/Capability Management Unit 210 of the server 200 checks capability information of the client 100. Then, when a pre-stored content can
not be operated by a capability of the client 100, the User Management/Capability Management Unit 210 of the server 200 updates the pre-stored content in correspondence to the capability of the client 200 (S211 ). And, the User Management/Capability Management Unit 210 of the server 200 sends, to the transmitting unit 220, a message requesting sending of the content, e.g., a 'Content Request' message (S212). Then, the transmitting unit 220 sends the content to the client 100.
(14-15) Once the Download/Installation Unit 210 of the client 100 has completed downloading of the content, a message indicating a successful downloading, e.g., a 'Confirmation of Download' message is sent to the Status Reporter 140 (S214). Then, the Status Reporter 140 sends, to the server 200, a 'Download Completion' message so as to inform a successful downloading (S215). (16-18) As aforementioned, the MO Set/Management Unit 130 of the client 100 maps information on a capability of the client 100 onto a tree as an MO, together with the User Management/Capability Management Unit 110 (S216), thereby managing the information on a capability of the client 100 as an MO. Furthermore, the MO Set/Management Unit 130 of the client 100 maps information on the content onto a tree as an MO, together with the User Management/Capability Management Unit 110 (S217), thereby managing information on a content received by the client 100 as an MO. Once the capability information and the content information are mapped onto a tree as an MO, the Remote Controller 230 of the server 200 can manage the client
100 through the tree (S218).
In addition, the above various embodiments may be implemented by software, hardware or some combination thereof. For instance, the method according to the present invention may be implemented in a storage medium (e.g., memory inside a mobile device, flash memory, hard disc, etc.), or may be implemented in codes or commands inside a software program that can be executed by a processor (e.g., microprocessor inside a mobile device).
It will also be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention cover modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.
Claims
1. A method for receiving a content, comprising: receiving, from a server, a list of contents and a capability required to perform the contents on the list; comparing the received capability with its own capability; and requesting the content from the server when it is determined that the client is able to perform a content on the list by its own capability as a result of the comparison.
2. The method of claim 1, further comprising requesting, from the server, the content list and a capability of the client required to perform the contents on the list.
3. The method of claim 1 , further comprising sending, to the server, a capability check ompletion message after comparing the received capability with its own capability.
4. The method of claim 1 , further comprising: receiving, from the server, an 'advertisement message about a content providing service; sending, to the server, a subscription request message; and receiving, from the server, a response message to the subscription request message.
5. The method of claim 1 , further comprising: mapping information on its own capability onto a DM(Device Management) Tree; mapping information on the received content onto the DM Tree; and receiving management from the server through the DM Tree.
6. A method for providing a content, comprising: receiving a capability advertisement message including information on a capability of a client; checking the capability of the client included in the capability advertisement message; receiving a content request message from the client; updating a pre-stored content in correspondence to the capability of the client based on the received content request message; and providing the updated content to the client.
7. The method of claim 6, further comprising: receiving, from the client, a download dompletion message about the content; and receiving, from the client, an installation completion message about the content.
8. The method of claim 6, further comprising: receiving, from the client, a subscription request message; and sending, to the client, a response message to the subscription request message.
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US98002507P | 2007-10-15 | 2007-10-15 | |
US60/980,025 | 2007-10-15 | ||
KR1020080018009A KR20090038346A (en) | 2007-10-15 | 2008-02-27 | How to send and receive customized content |
KR10-2008-0018009 | 2008-02-27 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2009051351A2 true WO2009051351A2 (en) | 2009-04-23 |
WO2009051351A3 WO2009051351A3 (en) | 2009-06-04 |
Family
ID=40567918
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2008/005535 WO2009051351A2 (en) | 2007-10-15 | 2008-09-19 | Method for receiving and transmitting customized content |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2009051351A2 (en) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050232186A1 (en) * | 2004-04-16 | 2005-10-20 | Jeyhan Karaoguz | Method and system for extended network access services advertising via a broadband access gateway |
KR20070037258A (en) * | 2005-09-30 | 2007-04-04 | 엘지전자 주식회사 | How to Play Multimedia Contents of Mobile Communication Terminal |
US20070286111A1 (en) * | 2006-01-11 | 2007-12-13 | Corson M S | Methods and apparatus for communicating device capability and/or setup information |
-
2008
- 2008-09-19 WO PCT/KR2008/005535 patent/WO2009051351A2/en active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050232186A1 (en) * | 2004-04-16 | 2005-10-20 | Jeyhan Karaoguz | Method and system for extended network access services advertising via a broadband access gateway |
KR20070037258A (en) * | 2005-09-30 | 2007-04-04 | 엘지전자 주식회사 | How to Play Multimedia Contents of Mobile Communication Terminal |
US20070286111A1 (en) * | 2006-01-11 | 2007-12-13 | Corson M S | Methods and apparatus for communicating device capability and/or setup information |
Also Published As
Publication number | Publication date |
---|---|
WO2009051351A3 (en) | 2009-06-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN106897086B (en) | Method, device and system for upgrading robot operating system | |
US8601157B2 (en) | Device, method, and system of communicating via relay device, and recording medium storing communication control program | |
US9294185B2 (en) | Device, method, and system of communicating via relay device, and recording medium storing communication control program | |
CN108769226A (en) | The OAT upgrade methods and car-mounted terminal of vehicle | |
US7280830B2 (en) | Automatic registration services provided through a home relationship established between a device and a local area network | |
CN104378391A (en) | Software updating method, system and device | |
US20090075641A1 (en) | Automated over-the-air firmware update for a wireless phone | |
CN106325818A (en) | Method, device and system for remotely upgrading firmware and air conditioner | |
CN101998227B (en) | Service routing method, device and system | |
KR20170127138A (en) | Updated software provides system and thereof method | |
US10050823B2 (en) | System and method for providing device management service to electronic device having no broadband communication module | |
EP3968668A1 (en) | Resource subscription method, device and server, and computer storage medium | |
CN101557584A (en) | Method for realizing application authority control of mobile terminal and device | |
EP2634994B1 (en) | Network system, certificate management method, and certificate management program | |
AU2015201637B2 (en) | Device management system, relay apparatus, relay method, and program | |
JP2015138297A (en) | Distribution system and control method therefor | |
KR20050001701A (en) | A method for providing a content compatibility of mutual network devices having respectively different digital right management | |
JP7513678B2 (en) | COMMUNICATION MODULE, COMMUNICATION SYSTEM, AND COMMUNICATION METHOD | |
EP3496337B1 (en) | Method and device for resetting network device to factory settings, and network device | |
US20090094593A1 (en) | Wirelessly upgrading software in a mobile computing device | |
CN101795280B (en) | Management device and management method | |
JP2018116349A (en) | Relay device, communication control method, and communication control program | |
KR100663497B1 (en) | Service Information Notification Method on Mobile Terminal | |
WO2009051351A2 (en) | Method for receiving and transmitting customized content | |
US7743173B2 (en) | Apparatus for automatically installing/uninstalling peripheral devices, and system and method for automatically detecting peripheral devices using the same |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 08839319 Country of ref document: EP Kind code of ref document: A2 |
|
NENP | Non-entry into the national phase in: |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 08839319 Country of ref document: EP Kind code of ref document: A2 |