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

• US 6,516,356 B1
• Filed: 09/30/1997
• Issued: 02/04/2003
• Est. Priority Date: 09/30/1997
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Silva, George Francis, Belknap, William Russell, Kozina, Gerald Edward, Nguyen, Tram Thi Mai
• Primary Examiner(s): COURTENAY III, ST JOHN
• Application Number:
  US08/941,788
• Time in Patent Office: 1,953 Days
• Field of Search: 709/231, 709/302, 709/310-332, 709/100-108, 709/320, 709/328, 709/329, 709/200-219, 714/40, 395/701, 348/515, 455/5.1
• US Class Current: 719/328
• CPC Class Codes: G06F 13/10 Program control for peripheral devices G06F13/14 - G06F13/42 take precedence
• CPC Class Codes: G06F 13/126 and has means for transferring I/O instructions and statuses between control unit and main processor
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system

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.

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

The present invention also encompasses a computer program product including a computer-readable medium. The computer program product includes 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 one of the media devices.

The present invention further encompasses 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 stores media objects. The common API includes a plurality of individual APIs which each perform a specific function.

Claims

1. 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 servers which store media objects, said common API comprising a plurality of individual APIs which each perform a specific function,

wherein each of said media servers has an operating protocol which responds to said device-level commands, and

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.

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

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

4. The common application program interface defined by claim 1, 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.

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

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

7. The common application program interface defined by claim 6, 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.

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

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

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

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

12. The common application program interface defined by claim 1, 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.

13. The common application program interface defined by claim 1, 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.

14. The common application program interface defined by claim 1, 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.

15. The common application program interface defined by claim 1, 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.

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

17. The common application program interface defined by claim 1, 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.

18. The common application program interface defined by claim 1, 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.

19. The common application program interface defined by claim 1, 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.

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

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

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

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

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

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

26. The common application program interface defined by claim 1, wherein the second group of individual APIs comprises a SET_MEDIA_ATTRIBUTES API which set s media attributes of a media object.

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