Multimedia middleware apparatus using metadata, method for controlling multimedia middleware, and storage medium thereof
View Patent ↗A multimedia middleware apparatus using metadata, a control method and a storage medium are provided which can receive metadata in multimedia middleware provided in a terminal, easily add/delete/change a service, and effectively maintain and manage middleware components. When an open multimedia terminal processes multimedia contents, a multimedia middleware service structure for expressing information of a name, configuration, version and application programming interface (API) update is configured in the form of metadata. Lists of standard and non-standard services of multimedia middleware are then generated and managed.
1. A multimedia middleware apparatus of a terminal for supporting a multimedia application, the apparatus comprising:
a receiver for receiving metadata comprising middleware application programming interface (API) information as structural information of a multimedia middleware service to run a multimedia application; and
a processor for
parsing the metadata,
identifying a service implementation code for the multimedia middleware service from the received metadata,
acquiring the service implementation code,
determining whether the metadata and the service implementation code are related to at least one of a standard service and a non-standard service, and
according to the determination result, applying the acquired service implementation code to change the multimedia application based on the acquired service implementation code and the metadata,
wherein the processor is further configured to verify validity by comparing the service implementation code with associated metadata when the service implementation code is related to the standard service and to apply a valid service implementation code to an associated multimedia middleware service.
2. The multimedia middleware apparatus of claim 1 , wherein the receiver receives the metadata from a server of a multimedia application provider connected through a communication network.
3. The multimedia middleware apparatus of claim 1 , wherein the receiver downloads the metadata through a storage medium.
4. The multimedia middleware apparatus of claim 1 , wherein the metadata further comprises change information of a middleware API corresponding to at least one of installation, deletion and update information of the middleware API, the change information of the middleware API being applied to an associated multimedia middleware service by the processor.
5. The multimedia middleware apparatus of claim 1 , wherein the metadata further comprises a middleware service container for providing information regarding a set of the multimedia middleware service.
6. The multimedia middleware apparatus of claim 5 , wherein the middleware service container comprises multimedia middleware service method information for describing associated API information and parameter information for describing an associated parameter in each multimedia middleware service.
7. The multimedia middleware apparatus of claim 1 , wherein the metadata further comprises change history information comprising at least one of addition information, modification information and deletion information.
8. The multimedia middleware apparatus of claim 7 , wherein the middleware API information to be at least one of added, modified and deleted in the change history information comprises at least one of information regarding multimedia middleware service parameter class types, information regarding multimedia middleware services to be supported, and information regarding multimedia middleware service methods.
9. A method for controlling multimedia middleware of a terminal for supporting a multimedia application, the method comprising:
receiving metadata comprising middleware application programming interface (API) information as structural information of a multimedia middleware service to run a multimedia application on the terminal, wherein the middleware API information is related to changing the multimedia application;
parsing the metadata, identifying a service implementation code for the multimedia middleware service from the parsed metadata, and acquiring the service implementation code;
determining whether the metadata and the service implementation code are related to at least one of a standard service and a non-standard service;
verifying validity by comparing the service implementation code with associated metadata when the service implementation code is related to the standard service; and
according to the determination result, applying the acquired service implementation code to change the multimedia application based on the acquired service implementation code and the metadata.
10. The method of claim 9 , wherein the metadata is received from a server of a multimedia application provider connected through a communication network.
11. The method of claim 9 , wherein the metadata is downloaded through a storage medium.
12. The method of claim 9 , wherein the metadata further comprises change information of a middleware API corresponding to at least one of installation, deletion and update information of the middleware API, and the method further comprising applying the change information of the middleware API to an associated multimedia middleware service.
13. The method of claim 9 , wherein the metadata further comprises a middleware service container for providing information regarding a set of the multimedia middleware service.
14. The method of claim 13 , wherein the middleware service container comprises multimedia middleware service method information for describing associated API information and parameter information for describing an associated parameter in each multimedia middleware service.
15. The method of claim 9 , wherein the metadata further comprises change history information comprising at least one of addition information, modification information and deletion information.
16. The method of claim 15 , wherein the middleware API information to be at least one of added, modified and deleted in the change history information comprises at least one of information regarding multimedia middleware service parameter class types, information regarding multimedia middleware services to be supported, and information regarding multimedia middleware service methods.
17. A non-transitory storage medium for recording multimedia middleware for supporting a multimedia application comprising:
a service metadata reception section for receiving metadata comprising middleware application programming interface (API) information as structural information of a multimedia middleware service to run a multimedia application on the terminal, wherein the middleware API information is related to changing the multimedia application;
a service implementation code acquisition section for parsing the metadata and acquiring the service implementation code; and
a service management section for identifying the service implementation code for the multimedia middleware service from the metadata, determining whether the metadata and the service implementation code are related to at least one of a standard service and a non-standard service, and according to the determination result, controlling an operation for applying the service implementation code to change the multimedia application based on the acquired service implementation code and the metadata,
wherein the service management section is further configured to verify validity by comparing the service implementation code with associated metadata when the service implementation code is related to the standard service and to apply a valid service implementation code to an associated multimedia middleware service.
18. The storage medium of claim 17 , wherein the service metadata reception section is implemented to receive the metadata from a server of a multimedia application provider connected through a communication network.
19. The storage medium of claim 17 , wherein the service metadata reception section is implemented to download the metadata through a storage medium.
20. The storage medium of claim 17 , wherein the metadata further comprises change information of a middleware API corresponding to at least one of installation, deletion and update information of the middleware API, the change information of the middleware API being applied to an associated multimedia middleware service by the service management section.
21. The storage medium of claim 17 , wherein the metadata further comprises a middleware service container for providing information regarding a set of the multimedia middleware service.
22. The storage medium of claim 21 , wherein the middleware service container comprises multimedia middleware service method information for describing associated API information and parameter information for describing an associated parameter in each multimedia middleware service.
23. The storage medium of claim 17 , wherein the metadata further comprises change history information comprising at least one of addition information, modification information and deletion information.
24. The storage medium of claim 23 , wherein the middleware API information to be at least one of added, modified and deleted in the change history information comprises at least one of information regarding multimedia middleware service parameter class types, information regarding multimedia middleware services to be supported, and information regarding multimedia middleware service methods.
25. A non-transitory computer-readable recording medium storing a computer program code for performing a method for controlling multimedia middleware of a terminal for supporting a multimedia application, the code comprising executable instructions for:
receiving metadata comprising middleware application programming interface (API) information as structural information of a multimedia middleware service to run a multimedia application on the terminal, wherein the middleware API information is related to changing the multimedia application;
parsing the metadata, identifying a service implementation code for the at least one multimedia middleware service from the parsed metadata, and acquiring the service implementation code;
determining whether the metadata and the service implementation code are related to at least one of a standard service and a non-standard service;
verifying validity by comparing the service implementation code with associated metadata when the service implementation code is related to the standard service; and
according to the determination result, applying the acquired service implementation code to change the multimedia application based on the acquired service implementation code and the metadata.