EP1775913A1 - Verfahren zur Steuerung eines multimedialen Mittelstückes, das Metadaten verwendet - Google Patents

Verfahren zur Steuerung eines multimedialen Mittelstückes, das Metadaten verwendet Download PDF

Info

Publication number
EP1775913A1
EP1775913A1 EP06021466A EP06021466A EP1775913A1 EP 1775913 A1 EP1775913 A1 EP 1775913A1 EP 06021466 A EP06021466 A EP 06021466A EP 06021466 A EP06021466 A EP 06021466A EP 1775913 A1 EP1775913 A1 EP 1775913A1
Authority
EP
European Patent Office
Prior art keywords
service
middleware
multimedia
metadata
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
EP06021466A
Other languages
English (en)
French (fr)
Other versions
EP1775913B1 (de
Inventor
Young-Joo Song
Ki-Ho Jung
Mun-Churl Kim
Hendry
Kook-Heui Lee
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Korea Advanced Institute of Science and Technology KAIST
Original Assignee
Samsung Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Priority to EP07024665A priority Critical patent/EP1898590B1/de
Publication of EP1775913A1 publication Critical patent/EP1775913A1/de
Application granted granted Critical
Publication of EP1775913B1 publication Critical patent/EP1775913B1/de
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1023—Media gateways
    • H04L65/1026—Media gateways at the edge
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1033—Signalling gateways
    • H04L65/1036—Signalling gateways at the edge
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H04W8/245—Transfer of terminal data from a network towards a terminal

Definitions

  • the present invention generally relates to a middleware technology for interworking between a physical network and a higher application in a wired/wireless communication network. More particularly, the present invention relates to a multimedia middleware apparatus using metadata, a control method, and a storage medium that can easily maintain and manage multimedia middleware service components.
  • Middleware is a software layer for use in interworking for a data exchange, and the like, between applications or between an application and a network for providing the services of identification, authentication, security, control, multimedia, and the like, related to devices thereon. That is, when a network connects to an application or applications directly connect to each other, codes should be added to all related applications for communicating with network devices or other applications. Because the middleware supports interworking between a network and an application or between applications, a difficult work for adding codes to the related applications can be omitted.
  • a multimedia middleware technology supports, for example, on-line content, Internet broadcast, or digital data broadcast reception.
  • a communication network using the multimedia middleware may be a mobile communication network for providing various packet services to mobile terminals like mobile phones, and the like.
  • the conventional mobile terminal manufacturers have designed, manufactured, and sold mobile terminals with hardware and software considering functions and services requested by users.
  • a design change is required at every time with the rapid development of mobile communication markets and various requests of the users, a conventional method for designing mobile terminals does not provide sufficient flexibility that can satisfy market requests.
  • the mobile terminal manufacturers have proposed a middleware technology for interfacing between a platform of a mobile terminal and a higher application while considering limitations in the conventional mobile terminal design method. Whenever a new application is embedded using the middleware technology, various middleware applications can be supported without largely changing a design of the mobile terminal.
  • the conventional multimedia middleware technology is provided in the form of a binary executable file or a binary library file in which middleware service components are simply implemented.
  • the conventional multimedia middleware is used by calling an associated binary executable file or an associated binary library file while a multimedia application runs.
  • a multimedia processing function of middleware is managed by reconfiguring service components and replacing an existing service component file when a new function is added to the service components.
  • the conventional multimedia middleware should reconfigure service components whenever a new function is added to the service components, it is difficult to maintain the service components. Further, because the existing service components should be replaced for a new multimedia application, there is a significant inconvenience in managing middleware.
  • An aspect of exemplary embodiments of the present invention is to address at least the problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of exemplary embodiments of the present invention is to provide a multimedia middleware apparatus using metadata, a control method and a storage medium that can easily maintain and manage multimedia middleware service components.
  • an aspect of exemplary embodiments of the present invention provides a multimedia middleware apparatus using metadata, a control method and a storage medium that can easily add/delete/change a service by managing a list of multimedia middleware services.
  • a multimedia middleware apparatus of a terminal for supporting a multimedia application in which a service metadata reception section receives metadata comprising middleware application programming interface (API) information as structural information of at least one multimedia middleware service to run a multimedia application, a service implementation code acquisition sectionacquires a service implementation code related to the metadata needed for the at least one multimedia middleware service, and a service management section identifies the service implementation code needed for the at least one multimedia middleware service from the received metadata and controlling an operation for applying the service implementation code acquired by the service implementation code acquisition section to an associated multimedia middleware service.
  • API middleware application programming interface
  • a method for controlling multimedia middleware of a terminal for supporting a multimedia application in which metadata comprising middleware application programming interface (API) information is received as structural information of at least one multimedia middleware service to run a multimedia application, a service implementation code related to the metadata required for the at least one multimedia middleware service is acquired, and the acquired service implementation code is applied to an associated multimedia middleware service.
  • API middleware application programming interface
  • a storage medium for recording multimedia middleware for supporting a multimedia application in which a service metadata reception section receives metadata comprising middleware application programming interface (API) information as structural information of at least one multimedia middleware service to run a multimedia application, a service implementation code acquisition section acquires a service implementation code related to the metadata required for the at least one multimedia middleware service, and a service management section identifies the service implementation code required for the at least one multimedia middleware service from the received metadata and controls an operation for applying the service implementation code acquired by the service implementation code acquisition section to an associated multimedia middleware service.
  • API middleware application programming interface
  • FIG. 1 illustrates a metadata structure for expressing a list of middleware services in accordance with an exemplary embodiment of the present invention
  • FIG. 2 illustrates an example of a metadata structure of a multimedia middleware service container illustrated in FIG. 1;
  • FIG. 3 illustrates an example of a metadata structure of multimedia middleware parameter class types illustrated in FIG. 2;
  • FIG. 4 illustrates an example of a metadata structure of a change history of a multimedia middleware application program interface (API) illustrated in FIG. 1;
  • API application program interface
  • FIG. 5 is a block diagram illustrating a structure of a network system to which multimedia middleware using metadata is applied in accordance with an exemplary embodiment of the present invention
  • FIG. 6 is a block diagram illustrating a structure of a terminal with a multimedia middleware apparatus using metadata in accordance with an exemplary embodiment of the present invention.
  • FIG. 7 is a flowchart illustrating a method for managing multimedia middleware using metadata in accordance with an exemplary embodiment of the present invention.
  • Exemplary embodiments of the present invention express a middleware service of a terminal requiring a multimedia application in the form of metadata.
  • the metadata is structured data used to describe other data, and is data assigned to contents in a regular rule such that desired information is efficiently retrieved and used from among a large amount of information.
  • the metadata includes structural information of a multimedia middleware service.
  • exemplary embodiments of the present invention propose an installation of a module for implementing a new standard or non-standard service in multimedia middleware by generating and managing metadata of a structure of standard and non-standard services and open multimedia middleware for deleting and changing a service implementation module by referring to structural lists of the standard and non-standard services such that a module for implementing the existing standard and non-standard services can be easily deleted and changed.
  • the exemplary embodiments of the present invention expresses name, configuration, version and application programming interface (API) update information in the form of an extensible markup language (XML) schema.
  • XML extensible markup language
  • the exemplary embodiments of the present invention generate metadata for a multimedia middleware service structure based on a model of the XML schema form and manage the metadata on the service structure information in multimedia middleware.
  • a service or multimedia service is a multimedia middleware service.
  • FIG. 1 illustrates a metadata (or Moving Pictures Experts Group (MPEG) multimedia middleware logical service (M3WLS)) structure for expressing a list of middleware services in accordance with an exemplary embodiment of the present invention.
  • MPEG Moving Pictures Experts Group
  • M3WLS multimedia middleware logical service
  • Metadata (M3WLS) 100 defined in an exemplary embodiment of the present invention includes elements of a multimedia middleware service container or MM services 110 and a change history 130 of a multimedia middleware application programming interface (API) as illustrated in FIG. 1.
  • the metadata (M3WLS) 100 of FIG. 1 includes attributes of version information for managing a multimedia middleware service, an issue date of multimedia middleware, and position information (or documentationRef) for referring to an associated service document.
  • An XML description for expressing a metadata structure of the multimedia middleware service in the present invention is as follows.
  • the multimedia middleware service container 110 is a set of multimedia middleware services to be supported in multimedia middleware.
  • the change history 130 of the multimedia middleware API is a container for describing addition, modification, and deletion of an item within the multimedia middleware.
  • the item includes at least one of a multimedia middleware parameter class type, a MM service, and a multimedia middleware service method as described below.
  • the "version” is version information of the associated metadata (M3WLS)
  • the "date” is an issue date of the associated metadata (M3WLS)
  • the "documentationRef” is a reference position of a document related to the associated metadata (M3WLS).
  • FIG. 2 illustrates an example of a metadata structure of the multimedia middleware service container or MM services 110 illustrated in FIG. 1.
  • the multimedia middleware service container or MM services 110 can include multimedia middleware parameter class types 111 and MM services 113.
  • the MM services 113 include attributes of a service identifier (ID) and name of each multimedia middleware service and M3W standard service information, and include element values of multimedia middleware service methods 117 and a description 115 of each multimedia middleware service method.
  • each multimedia middleware service method 119 includes elements of parameters 121.
  • each multimedia middleware service method 119 includes attributes of its name and a result (or output) type of the associated method (that is, API).
  • the multimedia middleware service method 119 describes the associated API.
  • the parameters 121 include name, type and optional attributes.
  • the parameters 121 are parameters of the associated API.
  • An XML description for expressing the multimedia middleware service is as follows.
  • FIG. 3 illustrates an example of a metadata structure of the multimedia middleware parameter class types 111 illustrated in FIG. 2.
  • the multimedia middleware parameter class types 111 are a set of class types of parameters used for each multimedia middleware service method 119.
  • Individual multimedia middleware parameter class types 1111 have an element value of a description 1113 of an associated parameter class type and have an attribute of a name of the parameter class type.
  • An XML description for expressing the multimedia middleware parameter class types 1111 is as follows.
  • FIG. 4 illustrates an example of a metadata structure of the change history of the multimedia middleware API illustrated in FIG. 1.
  • the change history 130 of the multimedia middleware API includes addition information 1301, modification information 1303, and deletion information 1305.
  • data (or object) to be added, modified or deleted includes at least one of the multimedia middleware parameter class type, the MM service, and the multimedia middleware service method as described in the following XML description.
  • the addition information 1301 has an attribute of a name of added data (or object) for indicating which data (or object) has been added among the multimedia middleware parameter class type 1111, the MM service 113, and the multimedia middleware service method 119 for describing the multimedia middleware API.
  • the modification information 1303 has an attribute of a name of modified data (or object) for indicating which data (or object) has been modified among the multimedia middleware parameter class type 1111, the MM service 113, and the multimedia middleware service method 119 for describing the multimedia middleware API.
  • deletion information 1305 has an attribute of a name of deleted data (or object) for indicating which data (or object) has been deleted among the multimedia middleware parameter class type 1111, the multimedia middleware service 113, and the multimedia middleware service method 119 for describing the multimedia middleware API.
  • FIG. 5 is a block diagram illustrating a structure of a network system to which multimedia middleware using metadata is applied in accordance with an exemplary embodiment of the present invention.
  • FIG. 5 illustrates an application framework of the system including a user terminal 510, a network 520, and a multimedia application provider 530.
  • the terminal 510 is a wired terminal (for example, a computer with a network access means) or a wireless terminal (for example, a cellular phone, personal communications service (PCS) phone, personal digital assistant (PDA), an international mobile telecommunications-2000 (IMT-2000) phone, PDA phone, or smart phone).
  • the network 520 can serve as various wired/wireless communication networks.
  • the multimedia application provider 530 may be a server for providing a multimedia application or a storage medium containing the multimedia application.
  • the application is executable codes of contents, metadata, or multimedia middleware services, that is, service implementation codes.
  • the terminal 510 includes a multimedia service application (processing) block 511 for running an application in a higher layer, a multimedia middleware block 513 for processing the metadata and service implementation codes received through the network 520 or the storage medium, and a platform block 515 in which a basic operating system (OS) for supporting the multimedia service of the terminal 510 is embedded.
  • processing processing
  • middleware processing the middleware
  • platform block 515 in which a basic operating system (OS) for supporting the multimedia service of the terminal 510 is embedded.
  • OS basic operating system
  • FIG. 6 is a block diagram illustrating a structure of the terminal 510 with multimedia middleware using metadata in accordance with an exemplary embodiment of the present invention.
  • the multimedia middleware block 513 of the terminal 510 connects to the multimedia service application block 511 through an application layer interface I1 and connects to the platform block 515 through a platform layer interface I2.
  • a service management section 5133 corresponding to a controller of the multimedia middleware block 513 manages metadata of a multimedia middleware service in accordance with an exemplary embodiment of the present invention.
  • the metadata required to run a multimedia application transmitted through the network 520 is received in a metadata transmission and reception section 5131.
  • a service metadata parser 5132 parses the received metadata and then outputs the parsed metadata to the service management section 5133.
  • the service management section 5133 identifies a service implementation code required for the associated multimedia middleware service from the parsed metadata and acquires the associated service implementation code through a service implementation code acquisition section 5134.
  • the associated service implementation code may be downloaded or copied through a storage medium.
  • the service implementation code acquired by the service implementation code acquisition section 5134 is installed/deleted/updated (or changed) in a service implementation code layer 5137 through a service implementation code installation/deletion/update (or change) section 5135.
  • the change of the service implementation code has the generic meaning for installation, deletion, and update operations.
  • the service management section 5133 determines whether the acquired service implementation code is related to a standard or non-standard service. If the acquired service implementation code is related to the standard service as a determination result, the service management section 5133 verifies validity of the code by comparing the acquired service implementation code with metadata of the standard service. If the acquired service implementation code is valid as a verification result, the service management section 5133 enables the acquired service implementation code to be installed in the service implementation code layer 5137. After the acquired service implementation code is installed, the service management section 5133 registers metadata of the associated standard service in an available service list.
  • the service management section 5133 receives metadata of the non-standard service through the service metadata transmission and reception section 5131, acquires a service implementation code of the associated non-standard service through the service implementation acquisition section 5134, applies the acquired service implementation code to the service implementation code layer 5137, and registers the metadata of the associated non-standard service in an available service list.
  • the service management section 5133 adds/deletes/updates (or changes) the associated multimedia API in the service metadata.
  • the service management section 5133 acquires a service implementation code of the changed multimedia API through the service implementation acquisition section 5134 and applies the acquired service implementation code to the service implementation code layer 5137 through the service implementation code change section 5135.
  • the multimedia middleware block 513 initializes and prepares a multimedia middleware service required to run a multimedia application through a service preparation section 5136. When the multimedia application runs, the multimedia middleware service can be called.
  • the multimedia middleware block 513 of an exemplary embodiment of the present invention can add metadata of the multimedia middleware service and can add a new service to a service list. Alternatively, the multimedia middleware block 513 can change and delete an existing service.
  • FIG. 7 is a flowchart illustrating a method for managing multimedia middleware using metadata in accordance with an exemplary embodiment of the present invention.
  • FIG. 7 illustrates an operation of the multimedia middleware block 513 of the terminal 510.
  • the service management section 5133 of the multimedia middleware block 513 identifies a type of externally received data.
  • the service metadata transmission and reception section 5131 receives the associated metadata.
  • the service management section 5133 parses the received metadata through the service metadata parser 5132.
  • the service management section 5133 determines whether the received metadata is related to a standard or non-standard service and identifies a service implementation code needed for the associated service. If the received metadata is related to the standard service, the service management section 5133 registers the metadata of the associated standard service in an available service list in step 709. On the other hand, if the received metadata is related to the non-standard service, the service management section 5133 registers the metadata of the associated non-standard service in an available service list in step 711.
  • the service management section 5133 of the multimedia middleware block 513 identifies a type of externally received data in step 701.
  • the service management section 5133 acquires the associated service implementation code through the service implementation code acquisition section 5134 in step 713.
  • the associated service implementation code is downloaded or copied through a storage medium.
  • the service management section 5133 verifies the validity of the code by comparing the service implementation code with the associated metadata. If the service implementation code is related to a standard service as a verification result in step 717, the validity of the code is verified by comparing the code with the standard service metadata in step 719.
  • the service management section 5133 enables the code to be installed in the service implementation code layer 5137 in step 723. After the acquired service implementation code is installed, the service management section 5133 registers metadata of the associated standard service in an available service list in step 709. On the other hand, if the service implementation code is related to a non-standard service as the determination result in step 717, the service management section 5133 omits a validity check. In step 718, the associated service implementation code is installed in the service implementation code layer 5137. The metadata of the associated non-standard service is registered in the available service list.
  • Step 715 in which the validity verification is performed and step 719 in which the service implementation code is compared with the metadata of the standard service can be selectively performed or integrated into one step.
  • an open multimedia middleware structure expresses name, configuration, version and API update information in the form of an XML schema such that a multimedia middleware service can be modeled.
  • Metadata for the multimedia middleware service structure based on a model of an XML schema form is generated.
  • a multimedia middleware block manages metadata of service structure information.
  • the associated service metadata and the associated service list can be referred to and updated when an implementation module (or service implementation code) of a new standard or non-standard service is installed to run a multimedia application in a terminal or when a service implementation code of an existing standard or non-standard service is deleted and changed.
  • exemplary embodiments of the present invention can record and use a program or algorithm capable of providing an open middleware structure in a storage medium capable of being embedded in a particular device such that the implementation of a standard or non-standard service can be effectively managed in multimedia middleware.
  • the storage medium can be read by a device such as a computer, and the like.
  • the exemplary embodiments of the present invention can easily add, delete or change a service and can effectively maintain and manage middleware components, by modeling an information structure of a name, configuration, version and API update of a multimedia middleware service in the form of metadata.
  • Exemplary embodiments of the present invention can also be embodied as computer-readable codes on a computer-readable recording medium.
  • the computer-readable recording medium is any data storage device that can store data which can thereafter be read by a computer system. Examples of the computer-readable recording medium include, but are not limited to, read-only memory (ROM), random-access memory (RAM), CD-ROMs, magnetic tapes, floppy disks, optical data storage devices, and carrier waves (such as data transmission through the Internet via wired or wireless transmission paths).
  • the computer-readable recording medium can also be distributed over network-coupled computer systems so that the computer-readable code is stored and executed in a distributed fashion. Also, function programs, codes, and code segments for accomplishing the present invention can be easily construed as within the scope of the invention by programmers skilled in the art to which the present invention pertains.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Databases & Information Systems (AREA)
  • Stored Programmes (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
EP06021466A 2005-10-12 2006-10-12 Verfahren zur Steuerung eines multimedialen Mittelstückes, das Metadaten verwendet Expired - Fee Related EP1775913B1 (de)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP07024665A EP1898590B1 (de) 2005-10-12 2006-10-12 Multimedia-Middleware-Vorrichtung für Metadaten mit einem Middleware-Service Container

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020050096297A KR101198583B1 (ko) 2005-10-12 2005-10-12 메타데이터를 이용한 멀티미디어 미들웨어 장치와 그 관리방법 및 기록 매체

Related Child Applications (2)

Application Number Title Priority Date Filing Date
EP07024665A Division EP1898590B1 (de) 2005-10-12 2006-10-12 Multimedia-Middleware-Vorrichtung für Metadaten mit einem Middleware-Service Container
EP07024665.7 Division-Into 2007-12-19

Publications (2)

Publication Number Publication Date
EP1775913A1 true EP1775913A1 (de) 2007-04-18
EP1775913B1 EP1775913B1 (de) 2012-02-29

Family

ID=37607428

Family Applications (2)

Application Number Title Priority Date Filing Date
EP07024665A Expired - Fee Related EP1898590B1 (de) 2005-10-12 2006-10-12 Multimedia-Middleware-Vorrichtung für Metadaten mit einem Middleware-Service Container
EP06021466A Expired - Fee Related EP1775913B1 (de) 2005-10-12 2006-10-12 Verfahren zur Steuerung eines multimedialen Mittelstückes, das Metadaten verwendet

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP07024665A Expired - Fee Related EP1898590B1 (de) 2005-10-12 2006-10-12 Multimedia-Middleware-Vorrichtung für Metadaten mit einem Middleware-Service Container

Country Status (9)

Country Link
US (1) US8775620B2 (de)
EP (2) EP1898590B1 (de)
JP (1) JP5122467B2 (de)
KR (1) KR101198583B1 (de)
CN (1) CN101305555B (de)
AU (1) AU2006300075B2 (de)
CA (1) CA2624968C (de)
RU (1) RU2376715C1 (de)
WO (1) WO2007043814A1 (de)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101405920B1 (ko) * 2007-06-26 2014-07-17 삼성전자주식회사 잡 컨트롤 장치 및 복합장치 그리고 그들의 동작 방법
US20090249190A1 (en) * 2008-03-31 2009-10-01 Kevin Jones Method and apparatus for processing structured documents
JP4922262B2 (ja) * 2008-07-30 2012-04-25 株式会社オートネットワーク技術研究所 制御装置
WO2010028501A1 (en) * 2008-09-15 2010-03-18 Research In Motion Limited Method and system for resolving indeterminate or inconsistent information for information consumers
US10089119B2 (en) 2009-12-18 2018-10-02 Microsoft Technology Licensing, Llc API namespace virtualization
CN103098484A (zh) * 2010-06-14 2013-05-08 汤姆森许可贸易公司 用于封装编码多组件视频的方法和装置
US8776094B2 (en) 2011-08-11 2014-07-08 Microsoft Corporation Runtime system
US8695021B2 (en) * 2011-08-31 2014-04-08 Microsoft Corporation Projecting native application programming interfaces of an operating system into other programming languages
US8782060B2 (en) * 2012-04-13 2014-07-15 Theplatform For Media, Inc. Multiple phase content ingest
US11593326B2 (en) * 2012-10-08 2023-02-28 GiantChair, Inc. Method and system for managing metadata
KR20140057998A (ko) * 2012-11-05 2014-05-14 삼성전자주식회사 전자 장치에서 응용프로그램의 갱신 정보를 알리기 위한 방법 및 장치
US10635504B2 (en) 2014-10-16 2020-04-28 Microsoft Technology Licensing, Llc API versioning independent of product releases
CN113473098B (zh) * 2021-08-20 2023-03-24 Vidaa(荷兰)国际控股有限公司 显示设备及显示方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10211426A1 (de) * 2002-03-15 2003-10-30 Audi Ag Verfahren zur Durchführung eines Updates von Software-Programmen oder Software-Programmteilen
WO2004114144A1 (en) * 2003-06-25 2004-12-29 Nokia Corporation Method of configuring parameters of machine-to-machine module and machine-to-machine module
WO2005031570A1 (en) * 2003-09-26 2005-04-07 Bitfone Corporation Update package catalog for update package transfer between generator and content server in a network
US20050108771A1 (en) * 2003-11-18 2005-05-19 Kim Yang-Soo Digital broadcast receiver and upgrading method thereof

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5892900A (en) * 1996-08-30 1999-04-06 Intertrust Technologies Corp. Systems and methods for secure transaction management and electronic rights protection
JPH10187456A (ja) 1996-12-27 1998-07-21 Hitachi Ltd プログラムダウンロードシステム
JP2001306581A (ja) * 2000-04-18 2001-11-02 Sony Corp ミドルウェアおよびミドルウェアを用いたメディアデータ視聴機器
JP2002099413A (ja) * 2000-09-21 2002-04-05 Kansai Electric Power Co Inc:The 監視制御システムの構築方法
JP3841169B2 (ja) 2002-08-21 2006-11-01 ソニー株式会社 通信システム、データ処理装置およびデータ処理方法、並びにプログラム
KR100493883B1 (ko) * 2003-01-02 2005-06-10 삼성전자주식회사 애플리케이션 관리 시스템 및 방법
EP1526457B1 (de) * 2003-10-22 2013-03-13 Sony Deutschland GmbH Kontextbewusste automatische Dienstedetektions- und Ausführungstreiber in mobilen ad-hoc Netzwerken
JP4305153B2 (ja) * 2003-12-04 2009-07-29 ヤマハ株式会社 音楽セッション支援方法、音楽セッション用楽器
US7617459B2 (en) 2004-01-28 2009-11-10 International Business Machines Corporation Apparatus, system, and method for automatically generating a web interface for an MFS-based IMS application
CN1588369A (zh) * 2004-09-06 2005-03-02 杭州恒生电子股份有限公司 一种关系型数据库系统及其查询和报表方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10211426A1 (de) * 2002-03-15 2003-10-30 Audi Ag Verfahren zur Durchführung eines Updates von Software-Programmen oder Software-Programmteilen
WO2004114144A1 (en) * 2003-06-25 2004-12-29 Nokia Corporation Method of configuring parameters of machine-to-machine module and machine-to-machine module
WO2005031570A1 (en) * 2003-09-26 2005-04-07 Bitfone Corporation Update package catalog for update package transfer between generator and content server in a network
US20050108771A1 (en) * 2003-11-18 2005-05-19 Kim Yang-Soo Digital broadcast receiver and upgrading method thereof

Also Published As

Publication number Publication date
JP2009512058A (ja) 2009-03-19
EP1898590A2 (de) 2008-03-12
RU2008114372A (ru) 2009-10-20
CA2624968C (en) 2014-04-29
AU2006300075A1 (en) 2007-04-19
KR101198583B1 (ko) 2012-11-06
EP1775913B1 (de) 2012-02-29
EP1898590A3 (de) 2009-06-03
KR20070040695A (ko) 2007-04-17
EP1898590B1 (de) 2012-03-07
JP5122467B2 (ja) 2013-01-16
CA2624968A1 (en) 2007-04-19
CN101305555A (zh) 2008-11-12
RU2376715C1 (ru) 2009-12-20
US8775620B2 (en) 2014-07-08
WO2007043814A1 (en) 2007-04-19
US20070088710A1 (en) 2007-04-19
AU2006300075B2 (en) 2010-08-26
CN101305555B (zh) 2013-10-16

Similar Documents

Publication Publication Date Title
EP1775913A1 (de) Verfahren zur Steuerung eines multimedialen Mittelstückes, das Metadaten verwendet
US7698223B2 (en) Pluggable file-based digital rights management API layer for applications and engines
KR101169071B1 (ko) 이동 디바이스 구성 설정들을 관리하기 위한 ｏｍａ ｄｍ확장 시스템 및 방법
US8667483B2 (en) Device dependent on-demand compiling and deployment of mobile applications
CN102413022B (zh) 一种应用调试方法和系统
US7243346B1 (en) Customized library management system
US10430510B2 (en) Method for controlling access to electronic documents based on stateless communication
TWI357248B (en) Mediated plug-in registration of client applicatio
US20090240698A1 (en) Computing environment platform
CN101335641A (zh) 一种升级设备的方法、装置及系统
CN101159764A (zh) 一种访问移动业务门户数据的方法和系统
CN101123750A (zh) 便于推送内容的后台处理的装置和相关方法
CN1886976B (zh) 用于使用动作列表及版本控制对一无线装置执行动作的方法及设备
KR100670605B1 (ko) 멀티미디어 콘텐츠 서비스 시스템과 방법 및 그 기록매체
CN101980503B (zh) 一种widget应用管理方法、装置和系统
US20060136423A1 (en) Wireless communication terminal having function for dynamically upgrading platform and method thereof
US20090037493A1 (en) Method and device for updating an object with copyright attribute
CN113535254A (zh) 一种微服务的处理方法、部署方法和相关装置
US20060161839A1 (en) Method for obtaining communication settings using an application descriptor
KR100601848B1 (ko) 이동 통신 단말에서의 다운로드 디스크립터 처리 방법
CN101957768A (zh) 一种移动Widget包的安装方法
JP4864022B2 (ja) モバイル配信フレームワークにおけるコンテンツ処理の調和のための方法およびシステム
KR20050057869A (ko) 무선 어플리케이션 관리 시스템 및 방법
CN114268941A (zh) 目标设备升级方法、装置、设备及存储介质

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20061012

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK YU

17Q First examination report despatched

Effective date: 20070626

AKX Designation fees paid

Designated state(s): DE FI FR GB IT SE

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: SAMSUNG ELECTRONICS CO., LTD.

Owner name: INFORMATION AND COMMUNICATIONS UNIVERSITY RESEARCH

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: KOREA ADVANCED INSTITUTE OF SCIENCE AND TECHNOLOGY

Owner name: SAMSUNG ELECTRONICS CO., LTD.

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE FI FR GB IT SE

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602006027881

Country of ref document: DE

Effective date: 20120426

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120229

RAP2 Party data changed (patent owner data changed or rights of a patent transferred)

Owner name: KOREA ADVANCED INSTITUTE OF SCIENCE AND TECHNOLOGY

Owner name: SAMSUNG ELECTRONICS CO., LTD.

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120229

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20121130

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602006027881

Country of ref document: DE

Effective date: 20121130

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 11

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20190923

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20190923

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20190920

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IT

Payment date: 20191015

Year of fee payment: 14

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602006027881

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20201012

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210501

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201012

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201012