US6516356B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
Application interface to a media server and a method of implementing the same
Assignee: International Business Machines Corp
•
Filing: 1997-09-30
•
Granted: 2003-02-04
•
Expires: 2017-09-30
Abstract
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.
Inventors
- 👤 William Russell Belknap
- 👤 Gerald Edward Kozina
- 👤 Tram Thi Mai Nguyen
- 👤 George Francis Silva
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-09 15:32
CPC Classifications
G; G06; G06F; G06F8/00; G06F9/00; G06F9/06; G06F9/46; G06F9/48; G06F9/4806; G06F9/4843; G06F13/00; G06F13/10; G06F13/12; G06F13/124; G06F13/126
Claims Analysis
Total Claims: 28
Claim 1
Independent Claim
134 words
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.
Claim 2
Dependent Claim
134 words
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.
Claim 3
Dependent Claim
27 words
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.
Claim 4
Dependent Claim
26 words
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.
Claim 5
Dependent Claim
39 words
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.
Claim 6
Dependent Claim
34 words
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.
Claim 7
Dependent Claim
29 words
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.
Claim 8
Dependent Claim
38 words
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.
Claim 9
Dependent Claim
27 words
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.
Claim 10
Dependent Claim
27 words
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.
Claim 11
Dependent Claim
29 words
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.
Claim 12
Dependent Claim
29 words
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.
Claim 13
Dependent Claim
34 words
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.
Claim 14
Dependent Claim
34 words
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.
Claim 15
Dependent Claim
40 words
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.
Claim 16
Dependent Claim
45 words
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.
Claim 17
Dependent Claim
31 words
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.
Claim 18
Dependent Claim
49 words
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.
Claim 19
Dependent Claim
52 words
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.
Claim 20
Dependent Claim
36 words
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.
Claim 21
Dependent Claim
29 words
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.
Claim 22
Dependent Claim
29 words
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.
Claim 23
Dependent Claim
31 words
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.
Claim 24
Dependent Claim
28 words
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.
Claim 25
Dependent Claim
32 words
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.
Claim 26
Dependent Claim
31 words
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.
Claim 27
Dependent Claim
30 words
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.
Claim 28
Dependent Claim
28 words
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.
References Cited (Backward Citations)
US4124889A
Cited
US4800523A
Cited
EP0259659A2
Cited
US5790176A
Cited
GB2273020A
Cited
US5604843A
Cited
US5544318A
Cited
US5499343A
Cited
US5642171A
Cited
US5805821A
Cited
US5668948A
Cited
US6256678B1
Cited
US5752159A
Cited
US5907704A
Cited
US5826085A
Cited
US5805796A
Cited
US6078942A
Cited
US6044408A
Cited
US6064379A
Cited
US5813014A
Cited
US5926649A
Cited
US6108695A
Cited
US6023731A
Cited
US6360368B1
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2006-02-03 | 2006-08-05 | 2007-02-04 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2010-02-03 | 2010-08-05 | 2011-02-04 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2014-02-03 | 2014-08-05 | 2015-02-04 | $7700.00 | Window Closed / Lapsed |