EP2181526A1

EP2181526A1 - System and method for music management

Info

Publication number: EP2181526A1
Application number: EP08831943A
Authority: EP
Inventors: Bhavana Bhat; Ankur Mehrotra; Naveen Papanna
Original assignee: Motorola Inc
Current assignee: Motorola Mobility LLC
Priority date: 2007-09-18
Filing date: 2008-09-10
Publication date: 2010-05-05
Also published as: CN101803292A; RU2010115325A; BRPI0816840A8; WO2009039008A1; KR20100053669A; MX2010002847A; BRPI0816840A2

Abstract

A network device (102) and a method for providing a multi-media service in a communication network by using Real Time Streaming Protocol (RTSP) is provided. The communication network includes a client device (104) and the network device. The method at the network device includes receiving (404) a request for the service from the client device. Further, the method includes, transmitting (406) a set of attributes and sub-attributes corresponding to each attribute of the set of attributes to the client device based on the request. Each attribute and each sub-attribute is associated with one or more datafiles. Furthermore, the method includes substantially continually transmitting (408) a set of metadata associated with the one or more datafiles until an intervention from the client device. Each datafile of the one or more datafiles is selected based on a response of the client device to the transmitted set of attributes and sub-attributes.

Description

Motorola Docket No. CML04487ED

SYSTEM AND METHOD FOR MUSIC MANAGEMENT

FIELD OF THE INVENTION

[0001] The present invention generally relates to field of information processing and more specifically, to method and system for music management.

BACKGROUND

[0002] With the progress of information technology, many emerging technologies have come up according to the needs of users. Multi-media service management is one of the emerging technologies in the multimedia domain. Recently, the need of music management for playing back music has increased. The primary focus is on music distribution services. Such services enable users to listen to music online when they purchase music data over the Internet. Further, music can be categorized based on different mood, singer, composer, language etc. Moreover, a user may want to store his/her favorite list of songs at a common place on a server. Sometimes, the user may want to give ratings to some songs. These ratings can be used to select the songs to be played next time the user requests for the music. One aspect of music management is to have an integrated, continuous music service. These services include, for example, rating the songs, listing the songs to be played, storing list of favorite songs of users etc. The music data is stored at a music distribution server for distribution. A user can download the music data using a client device. Further, various services desired by the user at the client device can be catered to by the music distribution server. However, when the number of items in music data increases, it is necessary for the user to search the desired music data from Motorola Docket No. CML04487ED

a large number of items of music data. The process of searching the music data from the large number of items of music data is time consuming and complex.

[0003] For reducing time/complexity searching music data, conventional music management methods use categories such as name of the artist, title of music piece, genre and age etc. to search the desired music data. In case the title of a music piece or name of an artist is not known, the method uses the lyrics of the music or the year of music release. Another conventional music management system uses searching based on sensitivity information to images and impressions felt when the music is listened to. The impressions can be for example, "comfortable", "exhilarating", "cheerful" etc that defines the mood of a listener when the listener listens to the music.

[0004] However, the above mentioned conventional music management methods may not always allow searches for the music data suitable to the current preferences of the user Further, the tracks are streamed from predefined music channels using Real Time Streaming Protocol - Real Time Protocol (RTSP-RTP) protocols and the metadata of the music are retrieved separately using HTTP protocols. This results in a large number of message exchanges between the client device and the music distribution server. Furthermore, the use of RTSP-RTP and HTTP message exchange causes synchronization problems in case a corrupt music data is encountered during streaming.

BRIEF DESCRIPTION OF THE FIGURES Motorola Docket No. CML04487ED

[0005] The accompanying figures, where like reference numerals refer to identical or functionally similar elements throughout the separate views, and which, together with the detailed description below, are incorporated in and form part of the specification, serve to further illustrate various embodiments and explain various principles and advantages, all in accordance with the present invention.

[0006] FIG. 1 illustrates an exemplary environment, where various embodiments of the present invention can be practiced;

[0007] FIG. 2 illustrates a block diagram of an exemplary network device, in accordance with an embodiment of the present invention;

[0008] FIG. 3 illustrates a call-flow diagram, in accordance with an embodiment of the present invention; and

[0009] FIG. 4 is a flow diagram illustrating a method for music management, in accordance with an embodiment of the present invention.

[0010] Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated, relative to other elements, to help to in improving an understanding of the embodiments of the present invention.

DETAILED DESCRIPTION

[0011] Before describing in detail the particular system for music management, in accordance with various embodiments of the present invention, it Motorola Docket No. CML04487ED

should be observed that the present invention resides primarily in combinations of method steps related to music management. Accordingly, the system components and method steps have been represented, where appropriate, by conventional symbols in the drawings, showing only those specific details that are pertinent for an understanding of the present invention, so as not to obscure the disclosure with details that will be readily apparent to those with ordinary skill in the art, having the benefit of the description herein.

[0012] In this document, the terms "comprises," "comprising", or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article or apparatus that comprises a list of elements does not include only those elements but may include other elements that are not expressly listed or inherent in such a process, method, article or apparatus. An element proceeded by "comprises ... a" does not, without more constraints, preclude the existence of additional identical elements in the process, method, article or apparatus that comprises the element. The term "another," as used in this document, is defined as at least a second or more. The terms "includes" and/or "having", as used herein, are defined as comprising.

[0013] In the description herein, numerous specific examples are given to provide a thorough understanding of various embodiments of the invention. The examples are included for illustrative purpose only and are not intended to be exhaustive or to limit the invention in any way. It should be noted that various equivalent modifications are possible within the spirit and scope of the present invention. One skilled in the relevant art will recognize, however, that an Motorola Docket No. CML04487ED

embodiment of the invention can be practiced with or without the apparatuses, systems, assemblies, methods, components mentioned in the description.

[0014] For one embodiment, a method for providing a multi-media service in a communication network by using Real Time Streaming Protocol (RTSP) is provided. The communication network includes a client device and a network device. The method at the network device includes receiving a request for the service from the client device. Further, the method at the network device includes, transmitting a set of attributes and sub-attributes corresponding to each attribute of the set of attributes to the client device based on the request. Each attribute and each sub- attribute is associated with one or more datafϊles. Furthermore, the method at the network device includes substantially continually transmitting a set of metadata associated with the one or more datafϊles until an intervention from the client device. Each datafϊle of the one or more datafϊles is selected based on a response of the client device to the transmitted set of attributes and sub-attributes.

[0015] For another embodiment, a network device is provided. The network device includes a receiving module for receiving a request from the client device for a multi-media service in a communication network. Further, the network device includes a transmitting module. The transmitting module is configured for transmitting a set of attributed and sub-attributes corresponding to each attribute of the set of attributes to the client device based on the request. Each attribute and each sub-attribute is associated with one or more datafϊles. Further, the transmitting Motorola Docket No. CML04487ED

module is configured for substantially continually transmitting metadata associated with the one or more datafiles until an intervention from the client device. Each datafile of the one or more datafiles is selected based on a response of the client device to the transmitted set of attributes.

[0016] The term "substantially continually" refers to continual transmission of metadata with respect to time for which the metadata is transmitted. The data entry in the metadata can have one or more null data value in between other data values. Hereinafter, the use of the term "substantially continually" is used with respect to the above stated definition with respect to the transmission of metadata.

[0017] The present invention provides a solution to the synchronization problem as suffered in the conventional methods for multi-media service distribution. The invention transmits the metadata for the one or more datafiles proactively. In the conventional methods, the metadata of each datafile of the one or more datafiles has to be requested by the client device.

[0018] FIG. 1 illustrates an exemplary environment 100, where various embodiments of the present invention can be practised. The environment 100 can include a network device 102 and at least one client device 104. Hereinafter, the at least one client device 104 will be referred to as the client device 104 for the sake of clarity. The network device 102 provides a multi-media service to the client device 104. The network device 102 and the client device 104 are represented here as block diagrams. The network device 102 can be any electronic device that can serve the purpose of a server. The client device 104 can be any electronic device that can Motorola Docket No. CML04487ED

communicate with the server represented as the network device 102. Examples of the network device 102 include, but not limited to, streaming servers, stream management servers, computers, and integrated servers. Further, the network device 102 can be a combination of two or more servers. Examples of the client device 104 include but not limited to computers, mobile phones, music players, radio etc.

[0019] For example, Ben can be a user of the client device 104 who wants to listen to the song tracks of 60s of the band "Guns n Roses". For the music service, Ben can send a request using the client device 104 to the network device 102. The network device 102 can send a list of services to the client device 104. Ben can select the service he wants to avail and based on his selection, the network device 102 can send a set of attributes and sub-attributes to him. The sub-attributes correspond to each attribute of the set of attributes. He can then select the attributes 'year of music release' and 'rock'. The sub-attributes of his choice can be 'decade 60s'and 'Guns n Roses'. Ben can also select the number of song tracks he wants to listen. The network device 102 can transmit the selected song tracks to the client device 104. Thus, Ben can listen to the songs of his choice at his client device by using the multimedia music service. Further, the client device 104 and the network device 102 can communicate by using standard communication protocols known in the art. For one embodiment, the standard communication protocol can be a Real Time Streaming Protocol (RTSP).

[0020] FIG. 2 illustrates a block diagram of a network device 102, in accordance with an embodiment of the present invention. The network device 102 is a server to provide a multi-media service to the client device 104. The network Motorola Docket No. CML04487ED

device 102 can be a dedicated server, a computer, an integrated server with a combination or two or more servers, a wireless device capable of acting as a server, a wired device capable of acting as a server and so forth. The network device 102 includes a receiving module 202 and a transmitting module 204. The receiving module 202 can receive a request from a client device for the multi-media service. For one embodiment, the multi-media service can be a music service. For example, a user can request the network device 102 for the music service by using a client device. The user can request for a list of songs for a particular attribute, such as genre, available at the network device 102. For the sake of describing the present invention, the requesting client device can be the client device 104.

[0021] For one embodiment, the client device 104 can communicate with the network device 102 by using Real Time Streaming Protocol (RTSP). Typically RTSP communication methods can be used for controlling streaming media over a communication network, for example, the Internet. In an RTSP communication method, an RTSP command can be sent by the client device 104 to request a set of attributes and sub-attributes for multi-media datafϊles from the network device 102. After receiving the RTSP request, the network device 102 can transmit a list of attributes and sub-attributes to the client device 104 in accordance with the RTSP communication method. Further, one or more multi-media datafϊles are selected by the network device 102 based on the selection of attributes and sub-attributes by the client device 104. Further, the network device 102 can substantially continually transmit a set of metadata corresponding to the one or more datafϊles to the client device 104. Motorola Docket No. CML04487ED

[0022] The client device 104 can send a request for the multi-media service by using a GET PLAYLIST ATTRIBUTE command in accordance with the RTSP method. The receiving module 202 receives the request for the multi-media service. For one embodiment, the receiving module 202 can be configured to receive all subsequent communications from the client device 104 to the network device 102. The transmitting module 204 can be configured to transmit music data to the client device 104 in response to the multi-media request. For one embodiment, the transmitting module 204 can transmit a set of attributes and sub-attributes to the client device 104 based on the request for the multi-media service. The sub-attributes correspond to each attribute of the set of attributes. For example, if the request is for a list of songs, the transmitting module will provide a list of songs with attributes like, genre, title, name of artist, year of music release, etc. The sub-attributes can correspond to each of these attributes. For example, the sub-attribute for year of music release can be decades 60s, 70s etc. Further, each attribute and sub-attribute is associated with one or more datafiles. Each datafile corresponds to a song. For one embodiment, the client device 104 is required to send the GET PLAYLIST ATTRIBUTE command in accordance with the RSTP method only once, at the time of establishing a session. Also, the network device 102 can transmit the set of attributes and the sub-attributes only once, at the beginning of the session. A session can be defined as an interaction between the client device 104 and the network device 102 which can include requesting and subsequent serving of the multi-media service. Motorola Docket No. CML04487ED

[0023] Further, the transmitting module 204 can be configured to substantially continually transmit a set of metadata associated with one or more datafiles until there is an intervention from the client device 104. Metadata is an essential data which is used to process a datafile. For example, in case a datafile is a song, the metadata of the song can contain data which is essential for processing the datafile and enables a user to play the song over a media player. For one embodiment, the transmitting module 204 can transmit the metadata after the transmission of the set of attributes and the associated sub-attributes. The one or more datafiles for which the metadata is transmitted is selected based on a response of the client device 104 to transmitted set of attributes and sub-attributes. For example, when the client device 104 requests for songs of decades 60s, the transmitting module 204 can transmit one or more songs which were released in the 60s along with their metadata. Further, the transmitting module 204 can substantially continuously transmit the datafiles and the associated metadata until there is an intervention from the user of the client device 104. When there is an intervention from the client device 104 with a DESCRIBE PLAYLIST method, the network device 102 sends a response to the DESCRIBE PLAYLIST method. For one embodiment, the DESCRIBE PLAYLIST method has information of the particular datafile for which the client device 104 had intervened. For example, in music service, the DESCRIBE PLAYLIST method will provide information related to the song for which the client device 104 has intervened. After transmitting the information, transmission of the metadata for the subsequent datafiles is resumed by the network device 102. The response to the DESCRIBE PLAYLIST provides the information related to the type of the media, the bitrate used in encoding the media Motorola Docket No. CML04487ED

and the other media specific information. This invention is proposing to provide the metadata information also in the DESCRIBE PLA YLIST response.

[0024] Hereinafter, the term 'multi-media service', which is served by the network device 102 on the request of the client device 104 has been used interchangeably with the term 'music service', which is a particular type of multimedia service, for the sake of clarity of the description.

[0025] FIG. 3 illustrates a call-flow diagram between the network device 102 and the client device 104, in accordance with an embodiment of the present invention. A user at the client device 104 can request a multi-media service which the user desires from the network device 102. The user can initiate a session with the network device 102 by using the client device 104 for the multi-media service. To initiate the session for receiving the multi-media service, for example the music service, the client device 104 sends a service initiation request 302 to the network device 102. For one embodiment, the service initiation request 302 can be a GET PLAYLIST ATTRIBUTE command in accordance with RTSP communication method. The GET PLAYLIST ATTRIBUTE command can be used for requesting the network device 102 to obtain the set of attributes and sub-attributes. For another embodiment, the service initiation request 302 can serve as an indication to the network device 102 that the client device 104 supports RTSP communication method.

[0026] In response to the service initiation request 302, the network device

102 transmits a confirmation message 304 to the client device 104. For one embodiment, the confirmation message 304 can be a service confirmation message to Motorola Docket No. CML04487ED

confirm the receipt of the service initiation request 302 from the client device 104. For another embodiment, the confirmation message 304 can be a message to provide the client device 104 with a list of multi-media services available with the network device 102. For yet another embodiment, transmission of the confirmation message 304 can indicate that the network device is ready to serve the service initiation request 302.

[0027] For one embodiment, after receiving the confirmation message 304, the client device sends a first response 306 to the network device 102. For one embodiment, the first response 306 can serve as an indication to the network device 102 that the client device 104 is ready to receive data from the network device 102. For another embodiment, the first response 306 can be a GET PLAYLIST ATTRIBUTE command in accordance with RTSP communication method. The GET PLAYLIST ATTRIBUTE command can be used for requesting the network device 102 to obtain the set of attributes and sub-attributes. For yet another embodiment, the first response 306 can be included in the service initiation request 302. In some cases, one of, the service initiation request 302 and the first response 306 can include information about the number of song tracks to be transmitted by the network device 102 during the service. For some embodiments, if the number of song tracks in not specified in the service initiation request 302 or the first response 306, then the network device 102 selects a default number of song tracks for transmission. Further, if the client device 104 does not select any attribute, then the network device 102 selects datafiles for a predefined set of attributes. Motorola Docket No. CML04487ED

Further, the network device 102 transmits metadata for the predefined set of attributes.

[0028] Further, the network device 102 transmits an attribute-content 308 to the client device 104. For one embodiment, the attribute-content 308 can provide a set of attributes and sub-attributes corresponding to each attribute based on one of the service initiation request 302 and the first response 306, from the client device 104. For the music service requested by the client device 104, the set of attributes and sub- attributes can be a list of songs with attributes like, genre, title, name of artist, year of music release, etc. The sub-attributes can correspond to each of these attributes. For example, the sub-attribute for year of music release can be decades 60s, 70s etc. Further, each attribute and sub-attribute is associated with one or more datafiles. Each datafile can correspond to one song. Thus, a set of attributes and sub-attributes can be transmitted by the network device 102 by using the attribute-content 308.

[0029] After receiving the attribute-content 308, the client device 104 sends a second response 310 to the network device 102. For one embodiment, the second response 310 can be a confirmation message to confirm the receipt of the attribute- content 308. For another embodiment, the second response 310 can be a DESCRIBE PLAYLIST method. The DESCRIBE PLAYLIST method can be a set of attributes and sub-attributes as selected by the client device 104. Based on this selection by the client device 104, the network device 102 can transmit a data-content 312. For yet another embodiment, the second response 310 can indicate a selection of a particular set of songs or datafiles based on the transmitted attribute-content 308 to Motorola Docket No. CML04487ED

the client device 104. For yet another embodiment, the client device 104 need not send the second response 310 to the network device 102.

[0030] Further, the network device 102 can transmit a data-content 312 to the client device 104. For one embodiment, the network device 102 substantially continually transmits the data-content 312 until there is an intervention from the client device 104. The data-content 312 can include a set of metadata for the one or more datafiles associated with the set of attributes and sub-attributes transmitted in the attribute-content 308. The one or more datafiles can be selected based on one of the service initiation request 302 and the first response 306 from the client device 104. For one embodiment, the set of metadata transmitted for the one or more datafiles by using the data-content 312 can be a Session Description Protocol (SDP) file. For another embodiment, the data-content 312 can be a DESCRIBE PLAYLIST method in accordance with the RTSP communication method. The DESCRIBE PLAYLIST method can provide information about a datafile desired by the client device 104. For example, the DESCRIB E PLA YLIST method can include information about metadata and streaming Uniform Resource Locators (URLs) for a set of song tracks.

[0031] Further, the client device 104 can send a service request 314 to the network device 102. The service request 314 can be, for example, a stream-media request. For one embodiment, the service request 314 can be an intervention from the client device 104 during the transmission of the data-content 312. The intervention can send an indication to the network device 102 to send a description of a datafile associated with the metadata, during the transmission of which, the service request 314 was sent. For example, while receiving metadata for a song track 'son of a gun', Motorola Docket No. CML04487ED

a user of the client device 104 can send an intervention by using the service request 314. After receiving the intervention, the network device 102 can send description of the requested song track by using a stream media content 316. For another embodiment, the service request 314 can send an indication to the network device 102 to start streaming music. In this embodiment, the network device 102 can stream music to the client device 104 by using the stream media content 316. For example, the stream media content 316 can start streaming datafϊles to the client device 104. By using the streamed datafϊles and the received metadata, the client device 104 can process the received datafϊles. Further, the network device 102 keeps substantially continually transmitting the set of metadata to the client device 104.

[0032] In some cases, any datafile transmitted from the network device 102 to the client device 104 may have an error or may be corrupt. As a result, the client device 104 may not be able to process the corrupt datafile. In accordance with the conventional methods for multi-media service distribution, this can result in synchronization problems between the client device 104 and the network device 102. Conventionally, a client device has to send separate requests for metadata of every datafile to a network device, as conventional methods do not employ substantially continually transmission of metadata to the client device 104. In such cases, when a datafile is corrupt, the metadata for the subsequent datafile may not be available to the client device 104. As a result, the subsequent datafϊles may not be processed because of non-availability of the corresponding metadata. The present invention proactively substantially continually transmits the metadata for each datafile of the one or more datafϊles. In this case, the client device 104 does not need to request separately for Motorola Docket No. CML04487ED

metadata for subsequent datafϊles when a corrupt datafϊle is encountered. Further, in case of a corrupt datafϊle, the client device 104 can process subsequent datafϊles as the metadata of the subsequent datafϊles is proactively transmitted by the network device 102 to the client device 104. Further, the metadata information can be sent as an SDP file which eliminates the need for the client device 104 to send additional requests for other information related to each datafϊle. For example, in case of a music service, the other information can be pictures, album art etc. associated with a song track played at the client device 104.

[0033] FIG. 4 is a flow diagram illustrating a method for music management, in accordance with an embodiment of the present invention. To describe the method, references will be made to FIGs 1, 2, and 3 although it will be apparent that the method can be implemented in any other suitable system. At step 402, the method for music management is initiated. At step 404, the network device 102 receives a request from the client device 104 for initiating a multi-media service. For one embodiment, the multi-media service can be a music service. For another embodiment, the request from the client device 104 can be service initiation request 302. The communication between the network device 102 and the client device 104 can be by using RTSP communication method. For one embodiment, the request for the multi-media service can be a GET PLAYLIST ATTRIBUTE command in accordance with RTSP communication method. Motorola Docket No. CML04487ED

[0034] At step 406, the network device 102 can transmit a set of attributes and sub-attributes to the client device 104. The sub-attributes correspond to each attribute of the set of attributes. The set of attributes can be transmitted based on the request from the client device 104. Further, each attribute and each sub-attribute is associated with one or more datafiles. For one embodiment, the datafiles can be song or music files. Further, for the music service requested by the client device 104, the set of attributes and sub-attributes can be a list of songs with attributes like, genre, title, name of artist, year of music release, etc. The sub-attributes can correspond to each of these attributes. For example, the sub-attribute for the year of music release can be decades 60s, 70s etc. Thus, a set of attributes and sub-attributes for a list of songs can be transmitted by the network device 102 at step 406.

[0035] At step 408, the network device 102 substantially continually transmits a set of metadata associated with the one or more datafiles until there is an intervention from the client device 104. The one or more datafiles can be selected based on a response to the set of attributes and sub-attributes from the client device 104. For example, if the response of the client device 104 for the music service is songs of decade 60s, then the one or more datafiles can be those songs that were released in the 60s. For one embodiment, the metadata can be transmitted as an SDP file. The metadata is an essential data which is used to process a datafile.

[0036] Various embodiments of the present invention offer one or more advantages. The present invention can be implemented by any communication device which can support RTSP/RTP communication methods. Further, there is faster response to the request for service of client device 104 from the network device 102 Motorola Docket No. CML04487ED

as the client device 104 does not need to send separate requests for metadata of each datafϊle. Further, as the metadata is transmitted substantially continually from the

network device 102 to the client device 104, the number of messages exchanged between them is substantially reduced. Furthermore, the present invention provides more flexibility to the communication device due to easy adaptability to various

changes to RTSP communication method due to evolving technology.

[0037] It will be appreciated that the system and method for music management, described herein, may comprise one or more conventional processors and unique stored program instructions that control the one or more processors, to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the system described herein. The non-processor circuits may include, but are not limited to, signal drivers, clock circuits, power-source circuits, and user- input devices. As such, these functions may be interpreted as steps of the method and system for transmitting a message in the communication network. Alternatively, some or all the functions can be implemented by a state machine that has no stored program instructions, or in one or more application-specific integrated circuits (ASICs), in which each function, or some combinations of certain of the functions, are implemented as custom logic. Of course, a combination of the two approaches can also be used. Thus, methods and means for these functions have been described herein.

[0038] It is expected that one with ordinary skill, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology and economic considerations, when guided by the concepts and principles disclosed herein, will be readily capable of generating such software instructions, programs and ICs with minimal experimentation.

[0039] In the foregoing specification, the invention and its benefits and advantages have been described with reference to specific embodiments. However, one with ordinary skill in the art would appreciate that various modifications and Motorola Docket No. CML04487ED

changes can be made, without departing from the scope of the present invention, as set forth in the claims below. Accordingly, the specification and the figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of the present invention. The benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage or solution to occur or become more pronounced are not to be construed as critical, required or essential features or elements of any or all the claims. The invention is defined solely by the appended claims, including any amendments made during the pendency of this application, and all equivalents of those claims, as issued.

[0040] The Abstract of the Disclosure is provided to comply with 37 CF. R.

§1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.

Claims

Motorola Docket No. CML04487EDCLAIMSWhat is claimed is:

1. A method for providing a multi-media service in a communication network by using Real Time Streaming Protocol (RTSP), the communication network comprising a client device and a network device, the method at the network device comprising: receiving a request for the service from the client device; transmitting a set of attributes and sub-attributes corresponding to each attribute of the set of attributes to the client device based on the request, wherein each attribute and each sub-attribute is associated with one or more datafϊles; and substantially continually transmitting a set of metadata associated with the one or more datafϊles until an intervention from the client device, wherein each datafϊle of the one or more datafϊles is selected based on a response of the client device to the transmitted set of attributes and sub-attributes.

2. The method as recited in claim 1 further comprising transmitting a confirmation message to the client device from the network device after receiving the request.

3. The method as recited in claim 2 further comprising receiving a first response from the client device for the confirmation message at the Motorola Docket No. CML04487ED

network device, prior to transmitting the set of attributes and sub- attributes.

4. The method as recited in claim 3 further comprising categorizing the one or more datafiles based on the first response from the client device.

5. The method as recited in claim 1 further comprising receiving a second response from the client device at the network device to the transmitted set of attributes and sub-attributes, prior to continually transmitting the set of metadata.

6. The method as recited in claim 4, wherein the set of metadata is continually transmitted for a predefined set of attributes when no attribute from the set of attributes is selected by the client device .

7. The method as recited in claim 1, wherein the service is a music service.

8. The method as recited in claim 1, wherein the set of metadata file is a Session Description Protocol (SDP) file.

9. The method as recited in claim 1 further comprising receiving a stream- media request from the client device at the network device. Motorola Docket No. CML04487ED

10. A network device comprising: a receiving module for receiving a request from a client device for a multi-media service in a communication network; and a transmitting module configured for: transmitting a set of attributes and sub -attributes corresponding to each attribute of the set of attributes to the client device based on the request, wherein each attribute and each sub- attribute is associated with one or more datafiles; and substantially continually transmitting a set of metadata associated with the one or more datafiles until an intervention from the client device, wherein each datafile of the one or more datafiles is selected based on a response of the client device to the transmitted set of attributes.

11. The network device as recited in claim 10, wherein the multi-media service is a music service.

12. The network device as recited in claim 10, wherein the network device is selected from a group comprising a streaming server and a stream management server.

13. The network device as recited in claim 10, wherein the set of metadata is a Session Description Protocol (SDP) file. Motorola Docket No. CML04487ED

14. The network device as recited in claim 10, wherein the transmitter is further configured for transmitting a confirmation message to the client device after receiving the request.

15. The network device as recited in claim 14, wherein the receiving module is configured to receive a first response from the client device for the confirmation message, prior to transmitting the set of attributes and sub- attributes.

16. The network device as recited in claim 10, wherein the receiving module is configured to receive a second response from the client device to the transmitted set of attributes and sub-attributes, prior to continually transmitting the set of metadata.

17. The network device as recited in claim 10, wherein the receiving module is configured to receive a stream-media request from the client device.