Application interface to a media server and a method of implementing the same

Abstract

According to the present invention, a media manager is provided which incorporates an application program interface (API) for converting high-level generic commands into device-level commands for output to a media device. The inventive media manager includes a high-level command processor which decodes the high-level generic commands and device-specific code mapping modules which convert the high-level generic commands decoded by the high-level command processor into device-level commands. Each of the device-level commands is output from one of the device-specific code-mapping modules to a corresponding one of the media devices.

Description

BACKGROUND OF THE INVENTION

[0001] 1. Field of the Invention

[0002] The present invention relates to an application interface, and more particularly to an application interface to a media server and a method of implementing the same.

[0003] 2. Description of the Related Art

[0004] Conventional multimedia data storage systems are often employed to retain large amounts of multimedia data which are made available for multimedia applications. These conventional multimedia data storage systems may also incorporate a digital library, such as that which is described in U.S. Pat. No. 5,649,185 to Antognini et al. A problem that arises with conventional multimedia data storage systems stems from the fact that they often employ multiple media servers which deliver specific types of data to a client media output station such as a client viewer including a display. However, because each media server supports only its own device-level commands, it is difficult for applications running within the conventional multimedia data storage system to interact with multiple media servers. Accordingly, each application communicating with a particular media server must take into account the unique characteristics of that media server. However, such a scheme can become burdensome when there are numerous media servers. Moreover, such a scheme requires that applications be continuously updated when new media servers are incorporated into the multimedia data storage system.

SUMMARY OF THE INVENTION

[0005] It is an object of the present invention to provide a robust management scheme which provides a common interface to media servers.

[0006] It is another object of the present invention to provide a common interface to media servers which conceals the media server specific device commands from applications which interact with the media servers included within the system.

[0007] To achieve the above-mentioned objectives of the present invention, a media manager is provided which incorporates an application program interface (API) for converting high-level generic commands into device level commands for output to a plurality of media devices. The inventive media manager includes a high-level command processor which decodes the high-level generic commands, and a plurality of device specific code mapping modules which convert the high-level generic commands decoded by the high-level command processor into device-level commands. Each of the device-level commands is output from one of the plurality of device specific code mapping modules to a corresponding one of the plurality of media devices.

[0008] The present invention also encompasses a method of implementing an application program interface (API) for a plurality of media devices. The method includes receiving a plurality of high-level generic commands from a computer application, converting the plurality of high-level generic commands into device-level commands, and outputting each of the device-level commands to one of the plurality of media devices.

[0009] The present invention also encompasses a computer program product including a computer-readable medium. The computer program product includes means for decoding a high-level generic command, means for converting the high-level generic command into one or more device level command, and means for outputting the converted device level commands to a corresponding one of the plurality of media devices.

[0010] The present invention further encompasses a common application program interface (API) which converts a high-level generic command received from a computer application into one or more device-level commands which are output to a plurality of media devices including media servers which store media objects. The common API includes a plurality of individual APIs which each perform a specific function.

[0011] According to one aspect of the invention, the plurality of individual APIs comprise first and second groups of individual APIs. The first group of the individual APIs corresponds to a first group of member functions associated with a class defining objects which represent media servers. The second group of the individual APIs corresponds to a second group of member functions associated with a class defining objects which represent a logical description of a physical format of media objects.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The above objects and advantages of the present invention will become more apparent by describing in detail preferred embodiments thereof with reference to the attached drawings in which:

[0013] FIG. 1 shows a media manager which incorporates the common application program interface (API) of the present invention.

[0014] FIG. 2 shows a flow chart diagram related to the operation of the inventive media manager.

[0015] FIG. 3 shows a multimedia data storage system incorporating the inventive media manager.

[0016] FIG. 4 shows the elements of the multimedia data storage system shown in FIG. 3.

DETAILED DESCRIPTION OF THE INVENTION

[0017] The present invention is directed to a media manager, which is preferably implemented in a multimedia data storage system, that provides a common application program interface to media servers included within the system. The media manager incorporates a management scheme which facilitates communication between applications running within the multimedia data storage system and the media device(s).

[0018] FIG. 1 depicts a media manager 5 which receives high-level commands from a requesting application 8. The media manager 5 converts the high-level commands into device specific commands which are output to first through N-TH media devices 25, which may be a media archive or a media server for handling specific types of media data such as video or audio data. Using the media manager 5, the requesting application 8 can request that a specific function be performed by the media devices 25 without having to take into account the idiosyncracies of those media devices 25. In addition, the media manager 5 also shields the requesting application 8 from having to account for internal changes to the media devices 25.

[0019] The media manager 5 includes a high-level command processor 10 which receives the high-level commands from the requesting application 8 and identifies whether a command corresponds to a particular type of media server which the media manager 5 supports. If the high-level command processor 10 determines that the command issued by the requesting application 8 corresponds to a media device 25 supported by the media manager 5, the processor 10 passes the request to a device-specific code-mapping module 15 which handles the high-level commands destined for that media device 25.

[0020] The device specific code mapping module 15 will map each high-level command into a device-level command for the module's corresponding media device 25 and transfer the device-level command to the media device 25 via a device interface 20 which includes multiple device level interfaces 22. Alternatively, the device-specific code-mapping module 15 will convert each high-level command into a series of actions, which may correspond to at least one of the above-mentioned high-level commands. These actions are then converted into device-level commands by the device-specific code-mapping module 15 for the corresponding media device 25.

[0021] The media manager 5 may include multiple device-specific code-mapping modules 15 in order to support more than one type of media device 25. Accordingly, the media manager 5 includes first through N-TH device-specific code-mapping modules 15 in order to support the first through N-TH media devices 25.

[0022] The media manager 5 preferably is implemented with the common application program interface (API) of the present invention. However, the high-level command processor 10 actually supports a number of individual APIs which together constitute the common API of the present invention. The media manger 5 may be implemented in software which is stored in machine readable from on, for example, a computer-readable disk.

[0023] The individual APIs correspond to member functions of at least two classes. The first class, SERVER, defines objects which represent the media servers 130 shown in FIG. 3. However, the SERVER class may be derived from a third class, MEDIA_DEVICE, in order to accommodate both media servers and media archives. Thus, a fourth class, ARCHIVE, may be provided which defines objects that represent the media archives 140. However, discussion of the ARCHIVE class is omitted because the member functions which make up the class are similar to those provided in the SERVER class. A discussion of a media archive can be found in U.S. Application, entitled “A MULTIMEDIA DATA STORAGE SYSTEM INCLUDING A MEDIA SERVER AND MEDIA ARCHIVE AND A METHOD OF MANAGING THE MEDIA SERVER AS A CACHE DEVICE FOR THE MEDIA ARCHIVE”, which is incorporated herein by reference and filed concurrently with the present application.

[0024] The second class, CONTENT, defines objects which represent a logical description of the physical format of an object or part thereof. By way of example, objects with the same format may share a CONTENT class. The requesting application can interact with any of the media devices 25 via the member functions of the CONTENT class in order to acquire information about objects stored within those media devices 25.

[0025] The above-mentioned member functions are described in greater detail in the attached APPENDIX. The individual APIs which incorporate those member functions are described in detail below.

[0026] Server Application Program Interfaces

[0027] A CLOSE API is provided in order to close an open media object. In addition, the CLOSE API destroys an instance of the CONTENT class.

[0028] A CLOSE_SESSION API is provided in order to close an open session. All resources allocated to the session will be released with the use of the CLOSE_SESSION API.

[0029] A COPY_MEDIA API is provided to copy a media object from one server to one or more other servers.

[0030] A DELETE API is provided in order to remove a media object from the server subsystem.

[0031] An EVENT_HANDLER API is provided to conditionally receive control for asynchronous events. An event mask, set with a REGISTER_CALL_BACK API, allows the specification of events to be passed to the EVENT_HANDLER API.

[0032] An EVENT_MASK API is provided to return the current event mask.

[0033] A GET_META_DATA API is provided to build and return a meta data file.

[0034] A GET_MEDIA_STATUS API is provided to obtain the status of a media object.

[0035] An INIT_SERVER API is provided to initialize a media manager client library. However, the INIT_SERVER API must be the first API that the requesting application calls before requesting another media manager service.

[0036] A LIST_MEDIA_GROUPS API is provided to obtain a list of configured media group names.

[0037] A LIST_MEDIA_NAMES API is provided to obtain a list of names of media objects associated with a particular media group of media objects.

[0038] An OPEN API is provided to return an instance of the CONTENT class that is used in subsequent calls to read or write data from or to a media object.

[0039] An OPEN_SESSION API is provided to open a session from the application to the video server subsystem.

[0040] A REGISTER_CALL_BACK API is provided to register the EVENT_HANDLER API with the Media Manager library. Once registered, the application may receive asynchronous event notification from the media device when necessary.

[0041] A C_SERVER API is provided as a constructor to create an instance of the SERVER class for a specific media server type.

[0042] A D_SERVER API is provided as a default destructor to destroy an instance of the SERVER class for a specific media server type.

[0043] An UN_REGISTER_CALL_BACK API is used to un-register the application event handler. When the event handler is unregistered, the application will not receive asynchronous event notifications.

[0044] Content Application Program Interfaces

[0045] A DESTAGE API is provided to destage (i.e. transfer) a media object from a media server to a media archive.

[0046] A GET_MEDIA_ATTRIBUTE API is provided to obtain the media attributes of a media object.

[0047] A GET_MEDIA_STATUS API is provided to obtain the status of a media object.

[0048] A LOAD API is provided to copy an existing media object to a media device. The media object must be open in write mode. The LOAD API is asynchronous in nature (i.e. it returns after initiating the load operation). The progress of the load function can be determined by calling the GET_MEDIA_STATUS API. In addition, an invocation of the LOAD API may be cancelled by using the CLOSE API.

[0049] A READ API is provided to read data of the media object. Each successive use of the READ API reads a sequential number of bytes from a current position within the media object. The media object must be open to invoke the READ API.

[0050] A RETRIEVE API is provided to retrieve a media object from a media server. The RETRIEVE API is used in conjunction with the GET_META_DATA API.

[0051] A SEEK API is provided to set the current byte position within the media object. However, the SEEK API can only be used in conjunction with the READ API. Therefore, it cannot be used in conjunction with the WRITE API described below. In addition, the media object must be open in read mode.

[0052] A SET_MEDIA_ATTRIBUTES API is provided to set the media attributes of a media object. However, to invoke the SET_MEDIA_ATTRIBUTES API, the media object must be opened in write mode.

[0053] A WRITE API is used to write data to the media object. Each successive use of the WRITE API writes a sequential number of bytes to the media object. However, the media object must be open to use the WRITE API.

[0054] Depending on the type of media device employed, some of the individual APIs described above may need to be converted into a number of actions which may include the use of some of the other individual APIs mentioned above. By way of example, the LOAD API may be converted into a group of actions which require the use of the OPEN API, the COPY_MEDIA API, the SET_MEDIA_ATTRIBUTE API and the CLOSE API. The group of actions would then be converted into corresponding device level commands corresponding to a particular media device 25. Depending on the particular hardware implementation of the media device 25, these device level commands may correspond, one-to-one, to the individual APIs mentioned above in connection with the group of actions. Accordingly, device level commands associated with the LOAD API may include an OPEN command, a COPY command, at least one SET_ATTRIBUTES command and a CLOSE command which correspond to the individual APIs mentioned above.

[0055] The operation of the media manager 5 will now be discussed in connection with FIG. 2. In step 50, a high-level command is received by the media manager 5 from the requesting application 8 along with a target media device. Thereafter, in step 55, the video server type is determined by the high-level command processor 10 of the media manager 5 based on the information provided by the requesting application 8. Subsequently, in step 60, the request for the specific machine type is validated by the high-level command processor 10.

[0056] In step 60, the high-level commands are decoded and broken down into specific actions by the high-level command processor 10. In step 70, the specific actions are executed. Thereafter, in step 75, the device-level commands can be generated from the specific actions by one of the device-specific code-mapping modules 15. Then, in step 80, the device-level commands are output via the device interface 20 to a corresponding media device 25.

[0057] An exemplary multimedia data storage system which incorporates the inventive media manager shown in FIG. 1 is described below with reference to FIGS. 3 and 4 in which the common API of the present invention is used in a digital library environment. The multimedia data storage system includes a library client 100, a client media output station 110, a digital library 120, media servers 130 and a media archive 140 which are implemented in a computer based system. The relationship between the client 100 and the digital library 120 is explained in greater detail below with reference to FIG. 4 which also shows the internal elements of the digital library 120. The internal structure of the digital library 120 is further described in U.S. Pat. No. 5,649,185, as noted above.

[0058] As shown in FIG. 4, the digital library 120 includes a library server 210 and at least one media object server 220 which interact with the library client 100. In addition, a communications isolator is provided in the digital library which allows the library server 210, the media object server 220 and the library client 100 to communicate with one another without concern for complex communications protocols. The library server 210, the media object server 220 and the library client 100 are connected by a communications network, such as a local area network (LAN) or a wide area network (WAN).

[0059] Although the media object server 220 and the client 100 output commands to the media server 130 generated by applications running on those platforms, those commands must be converted to device-level commands in order to control the particular media server 130 receiving them. Accordingly, the commands are transferred to the media server 130 via a common API which is incorporated in the media manager 5. Although the media manager 5 is shown in FIG. 4 as being included in the media object server 220, the media manager 5 may be included in the media servers 130.

[0060] As noted above, the common application program interface allows the media object server 220 to interact with media servers 130 having different operational characteristics. The interface achieves this objective by translating the generic instructions or commands generated by applications running on the media object server 220 or client 100 into specific actions that are mapped to device-level commands which are output to a particular media server 130. Thus, the common application program interface ensures that applications need not account for the idiosyncrasies of a particular media server 130 in order to generate commands for that media server 130.

[0061] In addition, as noted above, applications can interact with each of the media servers 130 via the member functions of the CONTENT class in order to acquire information about objects stored within those media servers 130.

[0062] The above-mentioned individual APIs will usually be used in conjunction with a request, which is sent by the library client 100 to the library server 210, to store, retrieve, and update media objects. The storage, retrieval and updating of media objects within the multimedia data storage system is described in greater detail below.

[0063] When a request to retrieve or update a particular media object is generated by the library client 100, the library server 210 determines whether the media object is located within the multimedia data storage system by searching an index of media objects stored within the system.

[0064] Once the library server 210 determines that the media object is stored within the multimedia data storage system, it passes the request to that media object server 220 which retains control over the physical location of the media object. The media object may be stored in the media object server 220 itself, or in the media servers 130 or the media archive 140 associated with the media object server 220. Thereafter, the library server 210 may update the media object indexes and descriptive information stored in the library catalog 212 to which the library server 220 is connected to reflect the request.

[0065] After receiving the request to retrieve or update the media object, the media object server 220 identifies the specific type of media object (i.e. audio or video based file) based on an identifier included in the request. Thereafter, the object server 220 will identify whether the media object is located locally within the object store 222 or at a remote location within the media archive 140 or one of the media servers 130.

[0066] If the media object server 220 determines that the media object is located in the media archive 140, then depending on the type of the media object, the media object server 220 will output a command via the media manager 5 to the media archive 140 which instructs the media archive 140 to transfer the media object to the appropriate media server 130.

[0067] Thereafter, the media server 130 receiving the media object will output the same to the client media output station 110 upon receipt of a command to do so from the media object server 220 via the media manager 5. By way of example, the client media output station 110 may be a video display such as a television, broadcast monitor or a computer monitor including a CRT tube or flat panel display.

[0068] In an alternative scheme, once the media object is stored in the media server 130, the media object server 220 passes control information concerning the media object to the client 100, which then commands the media server 130 via the media manager 5 to output the media object to the client media output station 110. By way of example, the media object may be output as an asynchronous transfer mode (ATM) based video stream. In addition, the client media output station 110 may be separate from, or included within the client 100.

[0069] If the client 100 requests that a media object be stored or loaded into the multimedia data storage system, then the library server 210 catalogs indexing information concerning the media object. Subsequently, the library server 210 will request that the object server 220 store control information corresponding to the media object. Thereafter, the media object server 220 issues a command via the media manger 5 to the media server 130. In response to the command, the media server 130 will load the media object into itself from the client 100. The client 100 will then transfer the media object to the media server 130 completing the loading process.

[0070] Although the above-mentioned multimedia data storage system was described in connection with a digital library, the media management scheme of the present invention may be employed in a multimedia data storage system which is configured differently. In addition, other modifications and variations to the inventive media management scheme will be apparent to those skilled in the art from the foregoing disclosure and teachings. Thus, while only certain embodiments of the invention have been specifically described herein, it will be apparent that numerous modifications may be made thereto without departing from the spirit and scope of the invention.

[0071] Server Class Member Functions

[0072] CLOSE

[0073] Closes an open media object and destroys a CONTENT class instance.

[0074] Parameters:

[0075] An indicator of an instance of the CONTENT class.

[0076] Return Codes:

[0077] A first code indicates whether the operation was performed successfully.

[0078] A second code indicates whether the media server reported an error.

[0079] A third code indicates whether the operation failed.

[0080] CLOSE_SESSION

[0081] Closes an open session. All resources allocated to the session will be released.

[0082] Parameters:

[0083] None

[0084] Return Codes:

[0085] A first code indicates that the operation was successfully completed.

[0086] A second code indicates that the media server reported an error.

[0087] A third code indicates that an invalid media group was specified.

[0088] A fourth code indicates that the media server cannot be located.

[0089] A fifth code indicates that the operation failed.

[0090] COPY_MEDIA

[0091] Copies a media object from one media server to one or more other media servers.

[0092] Due to the length of time that a copy operation may take, the COPY_MEDIA member function method works asynchronously. That is, it is returned after initiating the copy operation. The progress of the copy operation may be determined by calling the GET_MEDIA_STATUS member function. The copy operation may be cancelled by calling the CLOSE member function.

[0093] Parameters:

[0094] An indicator of a media name.

[0095] An indicator of a byte offset, at which to begin the copy operation.

[0096] An indicator of a byte offset, at which to end copy operations. A zero value can be specified to indicate the end of the media object.

[0097] An indicator of an array of MEDIA_LOCATION structures. Each MEDIA_LOCATION structure specifies one target location for a particular copy operation. The MEDIA_LOCATION structure indicates the size of the structure, the number of users, the media server name, the media group name, and the media object name.

[0098] A number of locations to which a media object will be copied.

[0099] An indicator of a CONTENT instance pointer.

[0100] Return Codes:

[0101] A first code indicates that the operation was successfully performed.

[0102] A second code indicates that the media server reported an error.

[0103] A third code indicates that the media name is invalid.

[0104] A fourth code indicates that an invalid media group (i.e. group of media objects) has been specified.

[0105] A fifth code indicates that a specified media name cannot be found.

[0106] A sixth code indicates that a copy operation has failed.

[0107] DELETE

[0108] Removes an media object from the media server.

[0109] Parameters:

[0110] An indicator of a media name.

[0111] A condition for deleting the media object. By way of example, this parameter may specify that the media object is to be deleted only if all of the resources are inactive.

[0112] Alternatively, this parameter may mark the asset as unavailable, and defer deletion until media object is no longer in use.

[0113] Return Codes:

[0114] A first code indicates that the operation was performed successfully.

[0115] A second code indicates that the media server reported an error.

[0116] A third code indicates that the specified media name was not found.

[0117] A fourth code indicates that the specified media object is in use.

[0118] A fifth code indicates that the specified media name is invalid.

[0119] A sixth code indicates that delete operation has failed.

[0120] EVENT_HANDLER

[0121] Conditionally receives control for asynchronous events. An event mask, set with the REGISTER_CALL_BACK member function, allows specified events to be passed to the EVENT_HANDLER member function.

[0122] Parameters:

[0123] An indicator of an event structure.

[0124] By way of example, the event structure may specify the size of the event structure, an event type, a media event, and an error event. The media event structure specifies an indicator of the CONTENT class, an event type, an index into a specific location or file array. The error event structure specifies the specific event associated with the occurrence of an error.

[0125] Events are asynchronous messages sent to the media manager by the media server.

[0126] Return Codes:

[0127] This member function has no return type.

[0128] GET_EVENT_MASK

[0129] Returns the current event mask.

[0130] Parameters:

[0131] An indicator of an event mask.

[0132] Return Codes

[0133] A first code indicates that the operation was successfully completed.

[0134] A second code indicates that the event mask is not defined.

[0135] GET_META_DATA

[0136] Builds and returns a metadata file.

[0137] Parameters:

[0138] An indicator of a media name.

[0139] A value which indicates whether playback should begin automatically, or delayed until play action.

[0140] A size of user data.

[0141] An indicator of a user defined data value.

[0142] An indicator of a MEDIA_STATUS structure to receive status information. The MEDIA_STATUS structure specifies the size of the structure, the current length (bytes), the media copy rate, a media open mode, a creation date, the date of the most recent modification, and the date of the most recent access.

[0143] An indicator of a buffer to receive metadata information.

[0144] The size of buffer.

[0145] Return Codes:

[0146] A first code indicates whether the operation was successfully performed.

[0147] A second code indicates that the media server reported an error.

[0148] A third code indicates whether the specified media name is invalid.

[0149] A fourth code indicates whether the specified media name is valid.

[0150] A fifth code indicates that a specified media name was not found.

[0151] A sixth code indicates that the operation has failed.

[0152] A seventh code indicates that there is insufficient disk bandwidth for the operation.

[0153] An eighth code indicates that an invalid media group has been specified.

[0154] A ninth code indicates that the operation is not available on the media server specified.

[0155] GET_MEDIA_STATUS

[0156] Obtains the status of a media object.

[0157] Parameters:

[0158] An indicator of a media name.

[0159] An indicator of a MEDIA_STATUS structure which is used to receive status information. The MEDIA_STATUS structure specifies the size of the structure, a current length in bytes of the media object, a media copy rate, a media open mode, the creation date of the media object, the last modification date of the media object, and the last access date of the media object.

[0160] Return Codes:

[0161] A first code indicates whether the operation was successfully completed.

[0162] A second code indicates whether the media server reported an error.

[0163] A third code indicates whether the specified media name is invalid.

[0164] A fourth code indicates whether the operation has failed.

[0165] INIT_SERVER

[0166] Initializes the Media Manager client library. This member function has to be the first call the application issues before requesting other Media Manager services.

[0167] Parameters:

[0168] The maximum number of sessions to be supported by the Media Manager.

[0169] An indicator of a current version.

[0170] Return Codes:

[0171] A first code indicates whether the operation was performed successfully.

[0172] A second code indicates that no more resources are available.

[0173] A third code indicates that the operation has failed.

[0174] LIST_MEDIA_GROUPS

[0175] Obtains a list of configured media group names.

[0176] Parameters:

[0177] An indicator of an array of MEDIA_GROUP_ATTRIBUTES structures that will specify the media group name and type. A media group name is a variable-length string. The media group type includes default and current media groups.

[0178] An indicator of the size in bytes of a group array.

[0179] Return Codes:

[0180] A first code indicates that the operation was successfully completed.

[0181] A second code indicates that the media server has reported an error.

[0182] A third code indicates that the media server cannot be located.

[0183] A fourth code indicates that the operation has failed.

[0184] LIST_MEDIA_NAMES

[0185] Obtains a list of media names associated with a media group.

[0186] Parameters:

[0187] An indicator of a media group name.

[0188] An indicator which specifies a buffer of media names. Each media name in the buffer is a variable length string.

[0189] An indicator of the number of entries returned in the buffer. an indicator of the buffer size.

[0190] An indicator of a position that is the start of a list of media names.

[0191] Return Codes:

[0192] A first code indicates that the operation was successfully completed.

[0193] A second code indicates that the media server has reported an error.

[0194] A third code indicates that the operation has failed.

[0195] OPEN

[0196] Returns an instance of the CONTENT class that is used in subsequent calls to read or write data from or to a media object.

[0197] Parameters:

[0198] An indicator of a media name.

[0199] A mode of operation which corresponds to a read or write mode of operation. There are several options which can be specified along with this parameter. Namely, an indication can be provided of whether the media object is provided for exclusive use. An indication can also be provided that the media object should be created if it does not already exist. An indication can also be provided of whether content should be truncated from the media object. In addition, an indicator can be provided of the location of the end of the media object. The rate in bits per second that the media object will be read from or written to.

[0200] A location of a pointer to an instance of the CONTENT class.

[0201] Return Codes:

[0202] A first code indicates that the operation was successfully completed.

[0203] A second code indicates that the media server has reported an error.

[0204] A third code indicates that the specified media name was not found.

[0205] A fourth code indicates that an invalid mode was specified.

[0206] A fifth code indicates that an invalid copy-rate was specified.

[0207] A sixth code indicates that a media object cannot be shared.

[0208] A seventh code indicates that a request for exclusive use is denied, because a particular media object is in use.

[0209] An eighth code indicates that a media name already exists.

[0210] A ninth code indicates that the operation has failed.

[0211] OPEN_SESSION

[0212] Opens a session from the application to the media server.

[0213] Parameters:

[0214] A host name of a media server with which to establish a session.

[0215] A name of a media group.

[0216] Return Codes:

[0217] A first code indicates that the operation was successfully completed.

[0218] A second code indicates that the media server has reported an error.

[0219] A third code indicates that the operation has failed.

[0220] A fourth code indicates that the media server cannot be located.

[0221] A fifth code indicates that an invalid media group has been specified.

[0222] A sixth code indicates that an invalid server name has been specified.

[0223] REGISTER_CALL_BACK

[0224] Registers the application event handler with the media manager. Once registered, the application may receive asynchronous event notification from the media server when necessary.

[0225] Parameters:

[0226] An event mask (i.e. bit mask) which is used to select which events are to be sent to the EVENT_HANDLER method function.

[0227] The event mask is developed using a logical operation involving the following event masks. A first event mask indicates a change in the state of a port. A second event mask indicates a change in the state of a media object. A third event mask indicates that an error has occurred. A fourth event mask indicates a change in the state of a media stream. A fourth event mask indicates a report of an event.

[0228] Return Codes:

[0229] A first code indicates that the operation was successfully completed.

[0230] A second code indicates that the media server has reported an error.

[0231] A third code indicates that an invalid event type has been specified.

[0232] A fourth code indicates that the operation has failed.

[0233] C_SERVER

[0234] Acts as a constructor which creates an instance of the SERVER class for a specific media server type.

[0235] Parameters:

[0236] A support level to be created within a SERVER class instance.

[0237] Return Codes:

[0238] None

[0239] D_SERVER

[0240] Acts as a destructor with respect to an instance of the SERVER class.

[0241] Parameters:

[0242] None

[0243] Return Codes:

[0244] None

[0245] UN_REGISTER_CALL_BACK

[0246] Unregisters an application event handler. When the event handler is unregistered, the application will not receive asynchronous event notifications.

[0247] Parameters:

[0248] none

[0249] Return Codes:

[0250] A first code indicates that the operation was successfully completed.

[0251] A second code indicates that the media server has reported an error.

[0252] A third code indicates that the session handler is corrupt.

[0253] A fourth code indicates that the operation has failed.

[0254] Content Class Member Functions

[0255] DESTAGE

[0256] Transfers a media object from the media server to the media archive.

[0257] This member function relies on other member functions. In particular, the member function calls the DELETE member function to delete a media object from the media archive if it exists, and then calls the COPY function to deliver the media object to the video archive. GET_MEDIA_ATTRIBUTE

[0258] Obtains media attributes of a specified media object.

[0259] Parameters:

[0260] An indicator of a MEDIA_ATTRIBUTES structure. The MEDIA_ATTRIBUTES structure specifies the size of the structure, the play back rate in frames/sec, the play back rate in bits/sec, the expected number of users, the type of the media object, and the duration of the media object during playback.

[0261] Return Codes:

[0262] A first code indicates whether the operation was successfully completed.

[0263] A second code indicates whether the media server reported an error.

[0264] A third code indicates whether the operation has failed.

[0265] GET_MEDIA_STATUS

[0266] Obtains a status of a media object.

[0267] Parameters:

[0268] An indicator of a MEDIA_STATUS structure to receive status information. The MEDIA_STATUS structure specifies the size of this structure, the current length (bytes), the media copy rate, the media open mode, the creation date, the date the media object was last modified, the date the media object was last accessed.

[0269] Return Codes:

[0270] A first code indicates whether the operation was successfully completed.

[0271] A second code indicates whether the media server reported an error.

[0272] A third code indicates whether the operation has failed.

[0273] LOAD

[0274] Copies an existing media object from a client to a media Server. The media object must be open in write mode. This member function is an asynchronous function, i.e., it returns after initiating the load operation. The progress of this member function can be determined by calling the GET_MEDIA_STATUS member function. However, the operation may be cancelled by calling the CLOSE member function.

[0275] Parameters:

[0276] An indicator of a MEDIA_ATTRIBUTES structure. The MEDIA_ATTRIBUTES structure defines the size of the structure, the type of the media object, the duration of the media object during playback, the play back rate in frames/sec, the playback rate in bits/sec, the expected number of users, and the name of the media object.

[0277] A host name from which media object(s) are transferred.

[0278] A user ID of the host specified by the hostname parameter.

[0279] A password of the user ID specified by the user ID parameter.

[0280] A file name array. All the files in the array can be joined together to form a single media object. This allows very large media objects to be created even if a particular media server does not support very large files.

[0281] A number of file names in the file name array.

[0282] An indicator of a MEDIA_STATUS structure used to receive status information. The MEDIA_STATUS specifies a size of the structure, the current length (bytes), the media object copy rate, a media object open mode, a creation date of the media object, the date that the media object was last modified, and the date that the media object was last accessed.

[0283] Return Codes:

[0284] A first code indicates whether the operation was successfully completed.

[0285] A second code indicates whether the media server reported an error.

[0286] A third code indicated that an invalid media server name has been specified.

[0287] A fourth code indicates that an invalid server name has been specified.

[0288] A fifth code indicates that the operation has failed.

[0289] A sixth code indicates that there is insufficient space available in Media Server.

[0290] A seventh code indicates that there is insufficient disk bandwidth in the media server.

[0291] READ

[0292] Reads data of a specified media object. Each successive call to the member function reads a sequential number of bytes from the current position. The media object must be open in read mode in order to call this member function.

[0293] Parameters:

[0294] An indicator of a pointer to which data is transferred.

[0295] A number of bytes to be read.

[0296] A number of bytes that have actually been read.

[0297] Return Codes:

[0298] A first code indicates whether the operation was successfully completed.

[0299] A second code indicates whether the media server reported an error.

[0300] A third code indicates that the operation has failed.

[0301] RETRIEVE

[0302] Retrieves a media object from the media server. This member function calls other member functions. In particular, the COPY member function is called if a media object is not already stored in the media server. Subsequently, the GET META_DATA member function is called to retrieve metadata information.

[0303] SEEK

[0304] Sets a current byte position within the media object. This member function only works in conjunction with the READ member function. The media object must be open in read mode in order for the operation to be initiated. It has no effect during a write operation.

[0305] Parameters:

[0306] An indicator of how an offset parameter is used. The following support options may also be specified. A first support option sets a media byte position to the value of the offset parameter. A second support option sets the media byte position to its current position plus the offset parameter. A third support option sets the media byte position to the end of the media.

[0307] An indicator of the byte offset into the media object being read.

[0308] Return Codes:

[0309] A first code indicates whether the operation was successfully completed.

[0310] A second code indicates whether the media server reported an error.

[0311] A third code indicates that the operation has failed.

[0312] SET_MEDIA_ATTRIBUTE

[0313] Sets the media attributes of a media object. The media object must be opened in write mode to employ this member function.

[0314] Parameters:

[0315] An indicator of a MEDIA_ATTRIBUTES structure. The MEDIA_ATTRIBUTES structure specifies the size of this structure, an attributes flag, the type of the media object, the duration of the media object, the play back rate in frames/sec, the play back rate in bits/sec, the expected number of users, and the name of the media object.

[0316] The attributes flag is a bit mask built up using a combination of basic attribute flags. The basic attribute flags specify which values in the structure are being set. The basic asset attribute flags set the media object name, the media object type, the duration of the media object, the media object, frame rate, the media object bit rate, the expected number of users, and all the attributes of the media object.

[0317] Return Codes:

[0318] A first code indicates whether the operation was successfully completed.

[0319] A second code indicates whether the media server reported an error.

[0320] A third code indicates that the operation has failed.

[0321] WRITE

[0322] Writes data to the media object. Each successive call to this member function writes a sequential number of bytes. The media must be open in write mode.

[0323] Parameters:

[0324] An indicator of a pointer from which data is written.

[0325] A number of bytes to be written.

[0326] A number of bytes that have actually been written.

[0327] Return Codes:

[0328] A first code indicates whether the operation was successfully completed.

[0329] A second code indicates whether the media server reported an error.

[0330] A third code indicates that the operation has failed.

Claims

1. A media manager which incorporates an application program interface (API) for converting high-level generic commands into device level commands for output to a plurality of media devices, said media manager comprising: a high-level command processor which decodes the high-level generic commands; and a plurality of device specific code mapping modules which convert the high-level generic commands by said high-level command processor into device level commands, each of the device-level commands being output from one of the plurality of device specific code mapping modules to a corresponding one of the plurality of media devices.

2. The media manager defined by claim 1, wherein said high-level command processor includes a plurality of individual APIs which correspond to the common API, the individual APIs each handling a specific function.

3. The media manager defined by claim 1, further comprising a device interface which receives each of the device level commands output from the plurality of device specific code mapping modules and outputs each of the device-level commands to a corresponding one of the plurality of media devices.

4. The media manager defined by claim 2, wherein said each of said media devices comprises a media archive and at least one media server, each of said media devices storing media objects.

5. The media manager defined by claim 4, wherein said media archive and media server are included in a multimedia data storage system including a digital library.

6. The media manager defined by claim 4, wherein said individual application program interfaces represent member functions associated with classes which define objects representing media servers and objects representing a logical description of a physical format of a media object.

7. The media manager defined by claim 1, wherein said plurality of device-specific code-mapping modules convert high-level generic commands into specific actions and convert the specific actions into device level commands.

8. A method of implementing an application program interface (API) for a plurality of media devices comprising: receiving a plurality of high-level generic commands from a computer application; converting the plurality of high-level generic commands into device-level commands; and outputting each of the device level commands to one of the media devices.

9. The method defined by claim 8, wherein said converting comprises converting the plurality of high-level generic commands using a plurality of individual APIs which each perform a specific function.

10. The method defined by claim 8, wherein said converting comprises converting the plurality of high-level generic commands into specific actions; and converting the specific actions into device-level commands.

11. The method defined by claim 8, wherein each one of the high-level generic commands is received along with a media device type identifier; wherein prior to said converting, it is determined whether the media device type corresponds to one of the media devices; and wherein each of the device level commands is output to a corresponding one of the plurality of media devices which is of the media device type.

12. A computer program product including a computer-readable medium, comprising: means for decoding high-level generic commands; means for converting the high-level generic commands into device-level commands; and means for outputting each of the device-level commands to a corresponding media devices.

13. The computer program product defined by claim 12, wherein said means for converting converts high-level generic commands into specific actions and converts said specific actions into the device-level commands.

14. A common application program interface (API) which converts high-level generic commands received from a computer application into device-level commands which are output to a plurality of media devices including media servers which store media objects, said common API comprising a plurality of individual APIs which each perform a specific function.

15. The common application program interface defined by claim 14, wherein said plurality of individual APIs comprise first and second groups of individual APIs, the first group of individual APIs corresponding to a first group of member functions associated with a class defining objects which represent media servers, the second group of individual APIs corresponding to a second group of member functions associated with a class defining objects which represent a logical description of a physical format of media objects.

16. The common application program interface defined by claim 15, wherein the first group of individual APIs comprises a CLOSE API which closes an open media object.

17. The common application program interface defined by claim 15, wherein the first group of individual APIs comprises a CLOSE_SESSION API which closes an open session.

18. The common application program interface defined by claim 15, wherein the first group of individual APIs comprises a COPY_MEDIA API which copies a media object from one of the media servers to another one of the media servers.

19. The common application program interface defined by claim 15, wherein the first group of individual APIs comprises a DELETE API which removes a media object from one of the plurality of media servers.

20. The common application program interface defined by claim 15, wherein the first group of individual APIs comprises an EVENT_HANDLER API which conditionally receives control for handling asynchronous events.

21. The common application program interface defined by claim 15, wherein the first group of individual APIs comprises an EVENT_MASK API which returns a current event mask.

22. The common application program interface defined by claim 15, wherein the first group of individual APIs comprises a GET_META_DATA API which builds and return a meta data file.

23. The common application program interface defined by claim 15, wherein the first group of individual APIs comprises a GET_MEDIA_STATUS API which obtains a status of a media object.

24. The common application program interface defined by claim 15, wherein the first group of individual APIs comprises an INIT_SERVER API which initializes a client library of a media manager containing the common API.

25. The common application program interface defined by claim 15, wherein the first group of individual APIs comprises a LIST_MEDIA_GROUPS API which obtains a list of names corresponding to configured groups of media objects.

26. The common application program interface defined by claim 15, wherein the first group of individual APIs comprises a LIST_MEDIA_NAMES API which obtains a list of the names of media objects associated with a particular media group of media objects.

27. The common application program interface defined by claim 15, wherein the first group of individual APIs comprises an OPEN API which returns an instance of the second class which is then used to read or write data from or to a media object, respectively.

28. The common application program interface defined by claim 15, wherein the first group of individual APIs comprises an OPEN_SESSION API which opens a session to one of the media servers.

29. The common application program interface defined by claim 20, wherein the first group of individual APIs comprises a REGISTER_CALL_BACK API which registers the EVENT_HANDLER API with a media manager which corresponds to the common application program interface.

30. The common application program interface defined by claim 15, wherein the first group of individual APIs comprises a C_SERVER API which is a constructor used to create an instance of the first class for a type of media server corresponding to at least one of the media servers.

31. The common application program interface defined by claim 15, wherein the first group of individual APIs comprises a D_SERVER API which is a default destructor used to destroy an instance of the first class for a specific server type of media server corresponding to at least one of the media servers.

32. The common application program interface defined by claim 20, wherein the first group of individual APIs comprises an UN_REGISTER_CALL_BACK API which un-registers an application event handler.

33. The common application program interface defined by claim 15, wherein the second group of individual APIs comprises a DESTAGE API which transfers a media object from one of the media servers to a media archive.

34. The common application program interface defined by claim 15, wherein the second group of individual APIs comprises a GET_MEDIA_ATTRIBUTE API which obtains media attributes of a media object.

35. The common application program interface defined by claim 15, wherein the second group of individual APIs comprises a GET_MEDIA_STATUS API which obtains the status of a media object.

36. The common application program interface defined by claim 15, wherein the second group of individual APIs comprises a LOAD API which copies an existing media object to a media device.

37. The common application program interface defined by claim 15, wherein the second group of individual APIs comprises a READ API which reads data of a media object.

38. The common application program interface defined by claim 15, wherein the second group of individual APIs comprises a RETRIEVE API which retrieves a media object from one of the media servers.

39. The common application program interface defined by claim 15, wherein the second group of individual APIs comprises a SEEK API which sets a current byte position within a media object.

40. The common application program interface defined by claim 15, wherein the second group of individual APIs comprises a SET_MEDIA_ATTRIBUTES API which sets media attributes of a media object.

41. The common application program interface defined by claim 15, wherein the second group of individual APIs comprises a WRITE API which writes data to a media object.