KR20190118946A - System and method for providing editable visual object based on schema - Google Patents

Abstract

The present invention provides a system and a method for providing an editable image object based on a schema which automatically edit an editable image object based on user information. According to an embodiment of the present invention, the method for providing an editable image object based on a schema comprises: a step of constructing an image object database where a plurality of editable image objects are matched to a plurality of image object IDs to be stored on memories included in a user terminal and a target terminal; a step of responding to a user input made on a user interface provided by the user terminal to edit one editable image object among the plurality of editable image objects stored in the image object database included in the user terminal; a step of extracting an image object ID corresponding to the one editable image object from the image object database included in the user terminal as the one editable image object is edited, and acquiring editing information in which the one editable image object is edited; a step of transferring the image object ID and the editing information to the target terminal; a step of extracting an editable image object corresponding to the image object ID from the image object database included in the target terminal; and a step of applying the editing information to the extracted editable image object to supply the editing information to the target terminal.

Description

Scheme-based method and system for providing editable image objects {SYSTEM AND METHOD FOR PROVIDING EDITABLE VISUAL OBJECT BASED ON SCHEMA}

The following description relates to a schema-based editable video object providing system and a method thereof, and more particularly, to a technology for editing an edited video object based on a user's emotion and providing the same to a target terminal.

Emoticons, flash cones or avatars (hereinafter referred to as emoticons, flash cones or avatars as Visual Objects), which are widely used in screen golf, 4D cinemas, virtual fitting systems or online messengers, are not limited to the virtual world. By being implemented as a character, the situation is being extended to offline.

Since the video object is provided between an application installed in the user terminal and an application installed in the target terminal, editing is not possible due to limitations such as transmission capacity and transmission speed of the image object supported by the application. In addition, since the image object is not editable, there is a disadvantage in that the expression desired by the user cannot be expressed in detail and freely.

Accordingly, the following embodiments propose a technique for providing (creating, transmitting and playing) an image object that can be edited to reflect the user's emotion, under the constraints of the transmission capacity and the transmission speed supported by the application of the terminal.

According to an embodiment of the present invention, an editable video object is designed in an XML format and a MPEG Binary Format (BiM) technique is used in a process of delivering the edited video object to the target terminal, thereby limiting transmission / reception capacity and transmission / reception speed supported by the user terminal and the target terminal. Below, we propose a method and system for providing an editable image object.

Specifically, in an embodiment, a user constructs and maintains an image object database in which a plurality of editable image objects are respectively matched and stored with a plurality of image object IDs on a memory included in each of the user terminal and the target terminal. In response to editing an editable video object in a terminal, a method and system for providing an editable video object service to a user terminal and a target terminal by transmitting and receiving only the video object ID and the edit information between the user terminal and the target terminal.

At this time, one embodiment proposes a method and system for editing an editable video object in response to a user manual edit input or automatically editing the editable video object based on user information.

In addition, embodiments of the present disclosure may consider a playback method supported by a target terminal in a process in which a reproduced video object generated by editing an editable image object is transferred from a user terminal to a target terminal and / or played in the target terminal. We propose a method and system.

According to an embodiment, the schema-based editing type video object providing method includes an image in which a plurality of editing type video objects are matched with a plurality of image object IDs and stored on a memory included in each of a user terminal and a target terminal. Building and maintaining an object database; In response to a user input generated on a user interface provided by the user terminal, editing any one of the plurality of editable image objects stored in the image object database included in the user terminal; As the edited video object is edited, the video object ID corresponding to the edited video object is extracted from the video object database included in the user terminal, and the edited video object is Obtaining edited edit information; Transmitting the image object ID and the edit information to the target terminal; Extracting an editable image object corresponding to the image object ID from the image object database included in the target terminal; And applying the edit information to the extracted editable video object and providing the edited information to the target terminal.

According to one side, the plurality of editable image objects and the plurality of image object IDs, can be designed in a schema of XML format.

According to another aspect of the present invention, the transmitting of the video object ID and the editing information to the target terminal comprises: transmitting the video object ID and the editing information to the target terminal based on a MPEG Binary Format (BiM) technique. Can be.

According to another aspect of the present invention, each of the plurality of editable image objects includes at least one element representing at least one of an expression, an action, a state, or an environment of each of the plurality of editable image objects, and the image object The establishing and maintaining of the database may include storing and maintaining the at least one element with the at least one element ID, respectively, in the image object database.

According to another aspect, the editing of any one of the edited image object of the plurality of editable image object stored in the image object database included in the user terminal, is included in the one edited image object Selecting any one element; And changing the one edited video object based on the selected element, wherein acquiring the edited information edited by the one edited video object comprises: selecting the selected element from the video object database. Extracting an element ID corresponding to the ID; And acquiring the extracted element ID as the edit information.

According to another aspect of the present invention, the changing of the one edited video object based on the selected element comprises: generating a playable video object by changing the one edited video object; And reproducing the reproducible video object on the user terminal based on a reproduction scheme supported by the user terminal.

According to another aspect of the present invention, the editing of any one of the editable video object of the plurality of editable video objects stored in the video object database included in the user terminal, automatic image input generated on the user interface In response to obtaining at least one of location information, environment information, body sensing information, schedule information, or image object usage history information of a user who uses the user terminal; And selecting and editing any one of the plurality of editable image objects based on the obtained at least one information.

According to another aspect, the editing of any one of the edited video object of the plurality of editable video object stored in the video object database included in the user terminal, the user manual editing input generated on the user interface In response, the method may include selecting and editing any one of the plurality of editable image objects.

According to another aspect, the step of applying the editing information to the extracted editable video object to provide to the target terminal, by applying the edit information to the extracted editable video object to generate a playable video object step; And providing the playback type video object to the target terminal.

According to another aspect, the providing of the playback type video object to the target terminal may include playing the playback type video object on the target terminal based on a playback method supported by the target terminal. .

According to an embodiment, in a computer program stored in a computer readable medium for executing a schema-based editable video object providing method, the editable video object providing method is included in each of a user terminal and a target terminal. Constructing and maintaining a video object database in which a plurality of editable video objects are respectively matched and stored with a plurality of video object IDs in a memory; In response to a user input generated on a user interface provided by the user terminal, editing any one of the plurality of editable image objects stored in the image object database included in the user terminal; As the edited video object is edited, the video object ID corresponding to the edited video object is extracted from the video object database included in the user terminal, and the edited video object is Obtaining edited edit information; Transmitting the image object ID and the edit information to the target terminal; Extracting an editable image object corresponding to the image object ID from the image object database included in the target terminal; And applying the edit information to the extracted editable video object and providing the edited information to the target terminal.

According to an embodiment, the schema-based editable video object providing server may include an image in which a plurality of editable video objects are matched with a plurality of video object IDs and stored on a memory included in each of a user terminal and a target terminal. An image object database construction / maintenance unit for constructing and maintaining an object database; In response to a user input generated on a user interface provided by the user terminal, an image object of any one of the plurality of editable image objects stored in the image object database included in the user terminal; editorial department; As the edited video object is edited, the video object ID corresponding to the edited video object is extracted from the video object database included in the user terminal, and the edited video object is An ID extracting / editing information obtaining unit for obtaining the edited editing information; A transmission unit for transmitting the image object ID and the edit information to the target terminal; A video object extracting unit for extracting an editable video object corresponding to the video object ID from the video object database included in the target terminal; And an image object providing unit applying the edit information to the extracted editable image object and providing the edited image object to the target terminal.

According to one side, the plurality of editable image objects and the plurality of image object IDs, can be designed in a schema of XML format.

According to another aspect, the transfer unit may transmit the image object ID and the edit information to the target terminal based on a MPEG Binary Format (Bim) technique.

According to one embodiment, a schema-based editing image object providing system, the user terminal; Target terminal; And an editable video object providing server, wherein the editable video object providing server includes a plurality of editable video objects corresponding to a plurality of video object IDs on a memory included in each of the user terminal and the target terminal. A video object database construction / maintenance unit for constructing and maintaining a video object database that is matched and stored; In response to a user input generated on a user interface provided by the user terminal, an image object of any one of the plurality of editable image objects stored in the image object database included in the user terminal; editorial department; As the edited video object is edited, the video object ID corresponding to the edited video object is extracted from the video object database included in the user terminal, and the edited video object is An ID extracting / editing information obtaining unit for obtaining the edited editing information; A transmission unit for transmitting the image object ID and the edit information to the target terminal; A video object extracting unit for extracting an editable video object corresponding to the video object ID from the video object database included in the target terminal; And an image object providing unit applying the edit information to the extracted editable image object and providing the edited image object to the target terminal.

According to an embodiment of the present invention, an editable video object is designed in an XML format and a MPEG Binary Format (BiM) technique is used in a process of delivering the edited video object to the target terminal, thereby limiting transmission / reception capacity and transmission / reception speed supported by the user terminal and the target terminal. Below, a method and system for providing an editable image object may be proposed.

Specifically, in an embodiment, a user constructs and maintains an image object database in which a plurality of editable image objects are respectively matched and stored with a plurality of image object IDs on a memory included in each of the user terminal and the target terminal. In response to editing the editable video object in the terminal, a method and system for providing an editable video object service to the user terminal and the target terminal by transmitting and receiving only the video object ID and the edit information between the user terminal and the target terminal can be proposed. have.

In this case, one embodiment may propose a method and system for editing an editable video object in response to a user manual editing input or automatically editing the editable video object based on user information.

In addition, embodiments of the present disclosure may consider a playback method supported by a target terminal in a process in which a reproduced video object generated by editing an editable image object is transferred from a user terminal to a target terminal and / or played in the target terminal. Methods and systems can be proposed.

1 is a diagram illustrating a schema-based editing type video object providing system according to an exemplary embodiment.
2 is a block diagram illustrating a configuration of a schema-based editable video object providing server according to an exemplary embodiment.
3 is a diagram for describing an image object database, according to an exemplary embodiment.
4 is a diagram illustrating a data transfer process between a user terminal and a target terminal for providing an editable video object to a target terminal according to an exemplary embodiment.
5 is a diagram for describing a process of editing an editable image object, according to an exemplary embodiment.
6 is a diagram for describing a process of editing an editable image object, according to another exemplary embodiment.
FIG. 7 is a diagram for describing a process of applying editing information to an editable video object and providing the same to the target terminal according to an exemplary embodiment.
8 is a diagram for describing a process of applying editing information to an editable video object and providing the same to the target terminal according to another exemplary embodiment.
9 is a flowchart illustrating a method of providing a schema-based editable video object, according to an exemplary embodiment.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited or limited by the embodiments. Also, like reference numerals in the drawings denote like elements.

Also, the terminology used herein is a term used to properly express a preferred embodiment of the present invention, which may vary depending on a viewer, an operator's intention, or customs in the field to which the present invention belongs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

1 is a diagram illustrating a schema-based editing type video object providing system according to an exemplary embodiment.

Referring to FIG. 1, an editable video object providing system 100 according to an embodiment includes a network 120 including an editable video object providing server 110, a user terminal 130, and a target terminal 140. By connecting the editable video object providing server 110, the user terminal 130, and the target terminal 140 to each other, the editable video object service is provided to the user terminal 130 and the target terminal 140.

Hereinafter, the editable video object service edits any edited video object in response to a user input generated on the user interface provided by the user terminal 130, and converts the edited video object to the target terminal. Means the service provided. Such an editable video object service may be provided by a request of a user of the user terminal 130 to transmit an editable video object to the target terminal 140. In addition, hereinafter, the editable video object refers to content data in which a still image and a motion of a still image are combined, such as an emoticon, a flash cone, or an avatar.

Each of the user terminal 130 and the target terminal 140 is a PC, a notebook computer, a smart phone, a tablet, a wearable computer, or the like, and is an editable type of the editable video object providing system 100. For the image object service, this may mean all terminal devices capable of accessing a web / mobile site related to the editable image object service or installing and executing a dedicated application. Thus, each of the user terminal 130 and the target terminal 140 may perform overall service operations such as service screen configuration, data input / output, data transmission and reception, and data storage under the control of a web / mobile site or a dedicated application.

In the drawing, although each of the user terminal 130 and the target terminal 140 is a smartphone, the present invention is not limited thereto, and the present invention is not limited thereto, and may be various devices capable of editing or reproducing an editable image object. In particular, the target terminal 140 may be a device such as a doll, a bracelet, a watch, a pendant, etc., in which a reproducible image object generated by editing an editable image object in the user terminal 130 may be reproduced.

Hereinafter, the user terminal 130 may substantially mean 'user' using the user terminal 130, and the target terminal 140 may substantially mean 'user' using the target terminal 140. have.

The editable video object providing server 110, the user terminal 130, and the target terminal 140 may transmit and receive data through the network 120.

Here, network 120 may be a medium used to provide communication links between data processing systems, computers, servers, and various devices. The network 120 uses a transmission control protocol internet protocol (TCP / IP) suite of protocols for the editable video object providing server 110, the user terminal 130, and the target terminal 140 to communicate with each other. To represent a world wide collection of networks and gateways. In some examples, network 120 may include or be an intranet, a local area network (LAN), or a wide area network (WAN). Also, in some examples, network 120 may be part of the Internet.

The communication method between the editable image object providing server 110, the user terminal 130, and the target terminal 140 is not limited, and a communication method utilizing a communication network that the network 120 may include, as well as between devices. The short range wireless communication may also include. For example, the network 120 may include a personal area network (PAN), a local area network (LAN), a campus area network (CAN), a metropolitan area network (MAN), a wide area network (WAN), a broadband network (BBN), One or more of networks such as the Internet. In addition, the network 120 may include any one or more of network topologies including a bus network, a star network, a ring network, a mesh network, a star-bus network, a tree, or a hierarchical network. It is not limited.

The editable video object providing server 110 is a subject that provides an editable video object service to the user terminal 130 and the target terminal 140. The editable video object providing server 110 provides a user terminal 130, a target terminal 140, and a network 120. It may be implemented as a computer device or a plurality of computer devices that communicate through and provide commands, codes, files, contents, services, and the like.

In this case, the editable video object providing server 110 is implemented in a form included in the platform of the server providing the editable video object service, and is edited by the client terminal 130 and the target terminal 140. Type video object service can be provided. However, the present disclosure is not limited thereto, and the editable video object providing server 110 may be configured in the form of a dedicated application in which at least some components or all components are installed on the user terminal 130 and the target terminal 140. It may also be implemented as a form of inclusion in a platform that provides services in a client-server environment.

The editable video object providing server 110 stores a plurality of editable video objects that are matched with a plurality of video object IDs on a memory included in each of the user terminal 130 and the target terminal 140. In response to editing the editable video object in the user terminal 130 while building and maintaining the video object database, only the video object ID and the editing information are transmitted and received between the user terminal 130 and the target terminal 140. The terminal 130 and the target terminal 140 provide an editable video object service. Detailed description thereof will be described with reference to FIG. 2.

In particular, the editable video object providing server 110 designs an image object database constructed and maintained on a memory included in each of the user terminal 130 and the target terminal 140 in a schema of XML format (in the image object database). By designating a plurality of stored editable image objects in an XML format), by transmitting and receiving image object ID and edit information between the user terminal 130 and the target terminal 140 based on the MPEG Binary Format (Bim) technique, An editable image object may be provided under constraints of transmission / reception capacity and transmission / reception rate supported by the user terminal 130 and the target terminal 140. Detailed description thereof will be described with reference to FIGS. 3 to 4.

2 is a block diagram illustrating a configuration of a schema-based editable video object providing server according to an exemplary embodiment.

Referring to FIG. 2, the editable video object providing server 200 according to an embodiment is included in the editable video object providing system described above with reference to FIG. 1, and includes a processor 210, a bus 220, and a network. It may include an interface 230, a memory 240, and a database 250. The memory 240 may include an operating system 241 and a service providing routine 242. The processor 210 is an image object database construction / maintenance unit 211, an image object editing unit 212, an ID extraction / editing information acquisition unit 213, a transfer unit 214, an image object extraction unit 215, and an image object. It includes a providing unit 216. In other embodiments, the editable image object providing server 200 may include more components or fewer components than the components shown in the drawing. However, it is not necessary to clearly show most of the prior art components. For example, the editable image object providing server 200 may include other components such as a display or a transceiver.

The memory 240 is a computer-readable recording medium and may include a permanent mass storage device such as random access memory (RAM), read only memory (ROM), and a disk drive. In addition, the memory 240 may store program codes for the operating system 241 and the service providing routine 242. These software components may be loaded from a computer readable recording medium separate from the memory 240 using a drive mechanism (not shown). Such a separate computer-readable recording medium may include a computer-readable recording medium (not shown) such as a floppy drive, a disk, a tape, a DVD / CD-ROM drive, a memory card, and the like. In other embodiments, the software components may be loaded into the memory 240 via the network interface 230 rather than the computer readable recording medium.

The bus 220 may enable communication and data transmission between components of the editable video object providing server 200. The bus 220 may be configured using a high-speed serial bus, a parallel bus, a storage area network and / or other suitable communication technology.

The network interface 230 may be a computer hardware component for connecting the editable video object providing server 200 to a computer network. The network interface 230 may be a network interface card such as an Ethernet card, an optical transceiver, a radio frequency transceiver, or any other type of device capable of transmitting and receiving information. Other examples of such network interfaces may be mobile computing devices and wireless devices including Bluetooth in USB, low power wide area networks, 3G and WiFi, and the like. In some examples, computing device may use network interface 230 to wirelessly communicate with an external device, such as a server, mobile phone, or other networked computing device. In particular, the network interface 230 may connect the editable video object providing server 200 to a user terminal and a target terminal through a network.

The database 250 may serve to store and maintain data for providing an editable video object service. For example, the plurality of editable image objects may be matched with the plurality of image object IDs and stored in the database 250. Therefore, the database 250 may be used in the process of constructing and / or updating the image object database on the memory of each of the user terminal and the target terminal described below with reference to FIG. 3.

In the drawing, although the database 250 is built and included in the editable video object providing server 200, the present invention is not limited thereto and may be omitted according to a system implementation method or environment, or may be omitted in whole or in part. It is also possible for the database to exist as an external database built on a separate, different system.

The processor 210 may be configured to process instructions of a computer program by performing input / output operations of the basic arithmetic, logic, and editable image object providing server 200. The instructions may be provided to the processor 210 by the memory 240 or the network interface 230 and via the bus 220. The processor 210 is an image object database construction / maintenance unit 211, an image object editing unit 212, an ID extraction / editing information acquisition unit 213, a transfer unit 214, an image object extraction unit 215, and an image object. It can be configured to execute the program code for the provider 216. Such program code may be stored in a recording device such as memory 240.

The image object database construction / maintenance unit 211 constructs and maintains an image object database in which a plurality of editable image objects are matched with a plurality of image object IDs and stored on a memory included in each of the user terminal and the target terminal. do.

Here, each of the plurality of editable video objects includes an editable video object image. Accordingly, the plurality of editable video object images are matched and stored with the plurality of video object IDs, respectively, and the plurality of editable video object images are matched with the plurality of video object IDs, respectively.

Each of the plurality of editable video objects may include an element representing at least one of an expression, an action, a state, or an environment of the editable video object (the edited video object image). Accordingly, the plurality of editable image objects may be matched and stored with the plurality of image object IDs, respectively, and may mean that the plurality of elements are matched with the plurality of element IDs and stored.

That is, the image object database construction / maintenance unit 211 stores the plurality of editable image object images by matching each of the plurality of image object IDs and stores the plurality of elements by matching each of the plurality of element IDs. A video object database in which a plurality of editable image objects are matched with and stored in a plurality of image object IDs may be constructed and maintained.

In particular, the image object database construction / maintenance unit 211 designs a plurality of editable image objects and a plurality of image object IDs in an XML format, so that the plurality of editable image objects and the plurality of image object IDs are respectively. The image object database that is matched and stored can be constructed and maintained at low capacity. Similarly, the plurality of elements and the plurality of element IDs may also be designed in an XML format schema.

As such, the image object database construction / maintenance unit 211 designs a plurality of editable image objects and a plurality of image object IDs in an XML format, so that the transmission unit 214, which will be described later, is used for the image object ID and editing information. In transmitting to the target terminal, it is possible to use the BiM technique to minimize the transmission capacity and maximize the transmission speed. Detailed description thereof will be described with reference to FIGS. 3 to 4.

In addition, the image object database construction / maintenance unit 211 may update the image object database constructed and maintained on a memory included in each of the user terminal and the target terminal.

The image object editing unit 212 edits any one of the plurality of editable image objects stored in the image object database included in the user terminal in response to a user input generated on the user interface provided by the user terminal. do.

In detail, the image object editing unit 212 may edit an image of any one of a plurality of editable image objects stored in an image object database included in the user terminal in response to a user input generated on a user interface provided by the user terminal. After selecting an object and selecting one element included in one editable image object, the editable image object may be changed and edited based on the selected element.

In this case, selecting one of the plurality of editable image objects may mean selecting one of the plurality of editable image object images. Accordingly, the image object editing unit 212 selects any one of the editable image object images among the plurality of editable image object images stored in the image object database included in the user terminal, and is associated with any one of the editable image object images. One of a plurality of elements (a plurality of elements included in one selected editable image object) may be selected. Accordingly, the image object editing unit 212 changes at least one editable image object by reflecting at least one of an expression, an operation, a state, or an environment indicated by any one selected element in the selected image object. You can edit to create a playable video object.

Here, selecting one of the plurality of editable video objects and selecting one of the elements included in the selected one of the edited video objects is provided by the user terminal. The image may be manually performed in response to a user manual edit input generated on the user interface, or may be automatically performed in response to an image object automatic generation input generated on the user interface. Detailed description thereof will be described with reference to FIGS. 5 and 6.

In addition, the image object editing unit 212 may play back the reproduced image object generated by editing one of the editable image objects on the user terminal, so that the user of the user terminal may confirm the editing result of the editable image object. .

The ID extracting / editing information obtaining unit 213 corresponds to any one editable video object from the video object database included in the user terminal as any edited video object is edited by the video object editing unit 212. The video object ID is extracted, and the edited edit information of any one editable video object is obtained. In this case, the edit information is information indicating how the editable video object is edited and changed when the editable video object is edited and changed to generate a playable video object. Like the video object ID, the edited information is designed as an XML schema. Can be.

In detail, the ID extracting / editing information obtaining unit 213 responds to the image object editing unit 212 selecting one of the editable image objects from the image object database included in the user terminal, and the image object included in the user terminal. After extracting the video object ID corresponding to one of the editable video objects from the database, the video object editor 212 is included in the user terminal in response to selecting one element included in one of the edited video objects. An element ID corresponding to any one element may be extracted from the image object database, and the extracted element ID may be obtained as edit information.

That is, the edit information in which any editable video object is edited may be an element ID corresponding to any one element selected by the video object editing unit 212.

Since the operations of each of the above-described image object editing unit 212 and the ID extracting / editing information obtaining unit 213 are performed based on the image object database constructed and maintained on the memory included in the user terminal, the image object editing unit ( 212) and each of the ID extracting / editing information obtaining unit 213 may have a right to access a memory of the user terminal, and a part of each of the image object editing unit 212 and the ID extracting / editing information obtaining unit 213. The operation may be performed by the processor of the user terminal as the subject of execution under the control of each of the image object editing unit 212 and the ID extracting / editing information obtaining unit 213.

The transfer unit 214 transfers the image object ID extracted from the ID extracting / editing information obtaining unit 213 and the obtained edited information to the target terminal. Here, since the video object ID and the edit information are designed in the form of XML, the transmission unit 214 transmits the video object ID and the edit information to the target terminal based on the BiM scheme, thereby minimizing the transmission capacity and transmitting the You can maximize speed.

In addition, the transfer unit 214 may transfer the video object ID and the edit information to the target terminal in consideration of a reproduction scheme supported by the target terminal. For example, when the target terminal is a device that supports reproducing the reproducible video object only in a sound system, the delivery unit 214 may transmit only some information related to the reproduction of the sound system to the target terminal. Therefore, the transmission unit 214 may maximize the data transmission speed by minimizing the data transmission capacity between the user terminal and the target terminal.

The image object extractor 215 transmits the editable image object corresponding to the image object ID from the image object database included in the target terminal in response to the delivery unit 214 transmitting the image object ID and the edit information to the target terminal. Extract. In this case, since the image object database included in the target terminal is the same database including the same data as the image object database included in the user terminal, the editable image corresponding to the corresponding image object ID on the image object database included in the target terminal. The object may be the same as the editable video object (editable video object edited by the user terminal) used by the ID extracting / editing information obtaining unit 213 to extract the corresponding video object ID from the video object database included in the user terminal. Can be.

Here, since the editable video object extracted by the video object extractor 215 includes an image of the editable video object, the video object providing unit 216 extracts the editable video object extracted by the video object extractor 215. By applying the edit information (the edit information transmitted from the delivery unit 214) to the (correctly, the editable video object image), the reproduced video identical to the reproduced video object generated by editing the edited video object in the user terminal. After the object is created, it may be provided to the target terminal.

In this case, the video object extractor 215 may play back the playback type video object on the target terminal based on the playback scheme supported by the target terminal. Detailed description thereof will be described with reference to FIGS. 7 to 8.

Since the operations of the above-described image object extracting unit 215 and the image object providing unit 216 are performed based on the image object database constructed and maintained on the memory included in the target terminal, the image object extracting unit 215 ) And the image object providing unit 216 may have a right to access the memory of the target terminal, and some operations of the image object extracting unit 215 and the image object providing unit 216 may be performed by the image object extracting unit. The processor of the target terminal may be executed as the subject of execution under the control of each of the control unit 215 and the image object providing unit 216.

As described above, the editable image object providing server 200 includes the processor 210, the bus 220, the network interface 230, the memory 240, and the database 250, but is not limited thereto. Core components of the processor 210 (image object database construction / maintenance unit 211, image object editing unit 212, ID extraction / editing information acquisition unit 213, transfer unit 214, image object extraction unit) 215 and the image object providing unit 216 may be included only.

3 is a diagram for describing an image object database, according to an exemplary embodiment.

Referring to FIG. 3, an editable video object providing server according to an embodiment may build and maintain an image object database 300 on a memory included in each of a user terminal and a target terminal.

In detail, the editable video object providing server may construct the video object database 300 by matching and storing the plurality of editable video objects 320 and 330 with the plurality of video object IDs 310, respectively. .

In this case, each of the plurality of editable image objects 320 and 330 includes an editable image object image (still image) 320 and a plurality of elements 330 associated with the editable image object image 320. Since the editable video object providing server stores the plurality of editable video object images 320 by matching each of the plurality of video object IDs 310 and stores the plurality of editable video object images 320, respectively. ) The image object database 300 may be constructed by matching and storing the plurality of elements 330 associated with each element with the plurality of element IDs 340, respectively.

Here, each of the plurality of elements 330 means data representing at least one of an expression, an operation, a state, or an environment of each of the plurality of editable image object images 320 which are still images.

For example, the editable video object providing server stores the first editable video object image representing a still image of a person by matching the first video object ID '001' and then stores the first edited video object image. A first-first element representing an associated 'laugh' expression and storing the first-first element corresponding to the first-first element ID '001' and storing the first-second element representing the expression of 'cry' associated with the first edited image object image. To store the first and second element ID '002', and match the first and third elements representing the expression of 'angry' associated with the first editable image object image to the first and second element ID '003'. Can be stored. Here, the first-first element, the first-second element, and the first-third element may be matched with and stored in the first editable image object image.

As such, the plurality of image object IDs 310, the plurality of editable image object images 320, the plurality of elements 330, and the plurality of element IDs 340 stored in the image object database 300 may be provided. All can be designed as XML type schemas. Therefore, the image object database 300 itself is a database that supports an XML-type schema. Since the image object database 300 stores and maintains data designed in the XML-type schema, the image object database 300 may be constructed at a low capacity.

In this case, the editable video object providing server may store a database (database shown in FIG. 2) stored in the server itself by matching the plurality of editable video objects 320 and 330 with the plurality of video object IDs 310, respectively. When the user terminal and the target terminal are registered and registered to use the editable video object service, the database stored in the server itself is copied into the memory of the user terminal and the memory of the target terminal, thereby constructing the user terminal and the target terminal. The target terminal may maintain the same image object database 300.

In addition, the editable image object providing server may update the image object database 300 which is constructed and maintained in each of the user terminal and the target terminal, in the same manner as the above-described process of constructing the image object database 300. The update process may be performed by the editable video object providing server connected to the user terminal and the target terminal by wireless or wired communication, and the data stored in the image object database 300 are all designed in an XML format. As a result, the speed and efficiency of the update process can be increased.

4 is a diagram illustrating a data transfer process between a user terminal and a target terminal for providing an editable video object to a target terminal according to an exemplary embodiment.

Referring to FIG. 4, the editable video object providing server according to an embodiment may include a video object database included in the user terminal 410 as one of the plurality of editable video objects is edited. Only the extracted image object ID and the obtained edited information 430 corresponding to any one editable image object are transmitted to the target terminal 420.

At this time, the edit information is information indicating how the editable video object is edited and changed in any one editable video object being edited and changed to generate a playable video object. It may be an element ID corresponding to any one selected element included.

For example, in the image object database 411 included in the user terminal 410, a first editable image object image representing a still image of a person is selected, and a 'laugh' associated with the first edited image object image is selected. If the first editable video object has been edited by selecting the 1-1 element representing the facial expression of, the editable video object providing server provides a first video object corresponding to the first editable video object image from the video object database 411. The ID '001' may be extracted, and the first-first element ID '001' corresponding to the first-first element may be obtained as edit information. Accordingly, the editable video object providing server may transmit the ID data 430 of '001001' in which the first video object ID '001' and the 1-1 element ID '001' are combined to the target terminal 420.

Since the video object ID and the editing information 430 are designed in the form of XML, the data volume is very low and can be transmitted and received based on the BiM technique, thereby minimizing the transmission capacity and maximizing the transmission speed. Accordingly, the editable video object providing server satisfies the constraints of the transmission / reception capacity and the transmission / reception speed supported by the user terminal 410 and the target terminal 420, and may provide an editable video object to the target terminal 420.

In response to the target terminal 420 receiving the image object ID and the editing information 430, the editable image object providing server edits corresponding to the image object ID from the image object database 421 included in the target terminal 420. After extracting the type image object (exactly the editable image object image) and applying the editing information to the extracted editable image object (exactly the editable image object image), after generating the reproduction image object, the target terminal ( 420.

Here, the application of the editing information to the editable video object may be performed by applying at least one of a facial expression, an action, a state, or an environment indicated by an element corresponding to an element ID, which is the edit information, to the editable video object image. This means that the moving content data is generated as a playable image object.

For example, as described in the above example, the ID data 430 of '001001' in which the first image object ID '001' and the 1-1 element ID '001' are combined is transmitted to the target terminal 420. In response, the editable video object providing server extracts a first editable video object image representing a still image of a 'person' corresponding to the first video object ID '001' from the video object database 421, and first-first-first. 1 After selecting the 1-1 element representing the expression of 'laugh' corresponding to the element ID '001', the expression of the 1-1 element 'laugh' is applied to the 'person' which is the first editable video object image. As a result, the reproduction type video object that is the content of which the person is smiling may be generated and provided to the target terminal 420.

5 is a diagram for describing a process of editing an editable image object, according to an exemplary embodiment.

Referring to FIG. 5, in response to a user manual edit input 511 generated on a user interface 510 provided by a user terminal, the editable video object providing server according to an embodiment may include a plurality of editable video objects ( One of 521, 522, 523, 524, and 525 may be selected and edited.

For example, when a user input is generated from the 'manual generation' button 511 displayed on the user interface 510, the editable video object providing server may load the manual editing user interface 520 on the user terminal. . Here, a plurality of editable image objects 521, 522, 523, 524, and 525 are displayed on the manual editing user interface 520 so that a user can directly select and edit any editable image object. Can support

More specifically, for example, the first editable image object image 521 representing a still image of 'person' and the second editable image object image representing a still image of 'bear' displayed in the manual editing user interface 520. The first editable video object image 521 is selected by a user selection input of 525, and the first-first element 522 indicating an expression of 'laugh' associated with the first editable video object image 521. When the first-first element 522 is selected by a user selection input from the first-second element 523 representing the expression of anger and the third element 524 representing the expression of crying, The editable video object providing server changes the first editable video object image 521 based on the selected first-first element 522 to display a playable video object that is 'content smiling by a person' (not shown in the drawing). ) To be provided to the user terminal. There.

At this time, the editable video object providing server reproduces the reproduced video object generated by editing the editable video objects 521 and 522 on the user interface of the user terminal, so that the user of the user terminal can directly check the editing result. can do

6 is a diagram for describing a process of editing an editable image object, according to another exemplary embodiment.

Referring to FIG. 6, the editable video object providing server according to another exemplary embodiment responds to the video object automatic generation input 611 generated on the user interface 610 provided by the user terminal, and uses the user terminal. Editing of any one of a plurality of editable image objects based on the at least one information obtained by obtaining at least one of position information, environmental information, body sensing information, schedule information or image object usage history information of the You can select and edit video objects.

For example, when a user input is generated from the 'auto generation' button 611 displayed on the user interface 610, the editable image object providing server may load the auto generation user interface 620 into the user terminal. . Here, in the auto-generated user interface 620, any editable image object is edited and generated based on the user's location information and the user's location information and the body sensing information 621 along with the user's location information and body sensing information 621. The playback image object 622 may be displayed.

More specifically, when the location information of the user indicates 'North Seoul forest' and the heart rate, which is the user's body sensing information, is '150', the editable video object providing server recognizes that the user is currently exercising and the user After selecting one image object image related to 'movement' from the image object database included in the terminal and recognizing that the current location of the user is 'North Seoul forest', the user selects one element representing the environment of 'forest' , By automatically applying one of the elements representing the environment of the 'forest' to any one of the image object image associated with the 'selected movement', automatically generating a reproducible image object 622, which is 'content that the person is exercising in the forest' The display may be displayed on the user interface 620 of the user terminal.

FIG. 7 is a diagram for describing a process of applying editing information to an editable video object and providing the same to the target terminal according to an exemplary embodiment.

Referring to FIG. 7, in response to a user input generated on a user interface 711 provided by the user terminal 710, the editable video object providing server according to an embodiment may edit an edited video object. After generating and displaying the playable video object 712 on the user interface 711, the video object ID and the edit information corresponding to one of the edited video objects may be transmitted to the target terminal 720.

Accordingly, the editable video object providing server extracts an editable video object corresponding to the video object ID from the video object database included in the target terminal 720, and applies the edit information to the extracted edited video object to reproduce the playable video. After generating the object 722, the playback type video object 722 may be displayed on the user interface 721 provided by the target terminal 720.

Here, the reproduced video object 712 displayed on the user terminal 710 is generated based on the image object database included in the user terminal 710 and is displayed on the target terminal 720. Is generated based on the image object database included in the target terminal 720. Therefore, since the image object database included in the user terminal 710 and the image object database included in the target terminal 720 are identically constructed, the reproduced image object 712 and the target terminal displayed on the user terminal 710 are the same. The reproducible video object 722 displayed at 720 may be identical content.

In this case, the editing type video object providing server displays the playback type video object 712 on the user interface 711 of the user terminal 710 based on the playback method supported by the user terminal 710. The video object 712 can be played back, and the playback type video object 722 is displayed on the user interface 721 of the target terminal 720 based on the playback method supported by the target terminal 720. The video object 722 may be played.

For example, as shown in the drawing, when both the user terminal 710 and the target terminal 720 are smartphones and the playback type video objects 712 and 722 can be reproduced in a graphic manner and a sound type, the editable image object is provided. The server provides the reproduced video object 712 to the user terminal 710 using both the graphic method and the sound method, and the reproduced video object 722 using both the graphic method and the sound method to the target terminal 720. Can be provided.

For another example, both the user terminal 710 and the target terminal 720 are smartphones, and the user terminal 710 may reproduce the playable image object 712 in a graphic manner and a sound manner, but the target terminal 720 If the playable video object 722 can be reproduced only in a graphical manner, the editable video object providing server provides the reproduced video object 712 to the user terminal 710 using both a graphical method and a sound method. In addition, the reproduction type video object 722 may be provided to the target terminal 720 using only a graphic method.

In addition, even when the target terminal 720 is a device such as a doll, a bracelet, a watch pendant, or the like, the editable video object providing server provides the playable video object 722 based on the playback method supported by the target terminal 720. can do. Detailed description thereof will be described below.

8 is a diagram for describing a process of applying editing information to an editable video object and providing the same to the target terminal according to another exemplary embodiment.

Referring to FIG. 8, the editable video object providing server according to another exemplary embodiment plays back by editing any one editable video object in response to a user input generated on a user interface provided by the user terminal 810. After generating and displaying the type image object 811 on the user interface, the image object ID and the edit information corresponding to one of the editable image objects may be transmitted to the target terminal 820.

Accordingly, the editable video object providing server extracts an editable video object corresponding to the video object ID from the video object database included in the target terminal 780, and applies edit information to the extracted edited video object to reproduce the playable video. After generating the object 821, the playback type video object 821 may be provided based on a playback method supported by the target terminal 820.

At this time, since the target terminal 820 is a doll as shown in the drawing, the target terminal 820 is a play method through the facial expression interface of the doll, a play method through the operation interface of the body movement, a play method of the body vibration, Sound system can be supported.

Accordingly, the editable video object providing server may provide the playable video object 821 through the doll's facial expression interface as shown in the figure.

As described above, the target terminal 820 is a doll, but is not limited thereto, and may be various devices capable of playing the reproducible video object 821, for example, a bracelet, a clock, a pendant, and the like. Here, the reproductionable video object 821 may include reproducing only some information (eg, some information of any one of vibration, sound, graphics, etc.) of the reproductionable video object 821.

9 is a flowchart illustrating a method of providing a schema-based editable video object, according to an exemplary embodiment.

Referring to FIG. 9, the method for providing an editable video object according to an embodiment may include the editable video object providing system described above with reference to FIGS. 1 to 2 (in particular, the editable video object included in the editable video object providing system). Providing server).

The editable video object providing system constructs and maintains a video object database in which a plurality of editable video objects are respectively matched and stored with a plurality of video object IDs in a memory included in each of the user terminal and the target terminal (910). ).

Here, the plurality of editable image objects and the plurality of image object IDs may be designed in a schema of XML. Therefore, the image object database may be a database supporting a schema of XML format.

In this case, each of the plurality of editable image objects may include an editable image object image and at least one element. The editable video object image refers to a still image on which the editable video object is based, and at least one element represents at least one of an expression, an action, a state, or an environment of the editable video object (exactly, the editable video object image). Indicates. Accordingly, the plurality of editable image object images and the plurality of elements may also be designed in a schema of XML.

In addition, the image object database may include a plurality of element IDs. Here, the plurality of element IDs may serve as identifiers that are respectively matched and stored with the plurality of elements. Similarly, the plurality of element IDs may also be designed in a schema of XML.

Accordingly, in operation 910, the editable video object providing system may match and store the plurality of editable video object images with the plurality of video object IDs, respectively, in the video object database, and the plurality of editable video object images. At least one element associated with the at least one element ID may be matched with each of at least one element ID, and stored and maintained in the image object database.

Subsequently, the editable video object providing system, in response to a user input generated on a user interface provided by the user terminal, edited image of any one of a plurality of editable video objects stored in a video object database included in the user terminal. The object is edited (920).

In detail, in operation 920, the editable video object providing system selects one editable video object from among a plurality of editable video objects from a video object database included in the user terminal (a plurality of editable video object images). Select one of the editable video object images), select one element included in one of the editable video objects (select one of the elements associated with one of the editable video object images), By changing one of the editable video objects based on the selected element (applying the selected element to one of the edited video object images), the playable video object may be generated.

In operation 920, the editable video object providing system may play back the generated playback video object to the user terminal based on a playback method supported by the user terminal.

Such an editing process may be performed manually or automatically according to a user input generated on a user interface provided by the user terminal. For example, the editable image object providing system, in response to an automatic image object generation input generated on a user interface, records location information, environment information, body sensing information, schedule information, or image object usage history of a user using a user terminal. By acquiring at least one piece of information, one of the plurality of editable image objects may be selected and edited based on the obtained at least one information.

For another example, the editable video object providing system may select and edit any one of a plurality of editable video objects in response to a user manual edit input generated on a user interface.

Next, as the editable video object providing system is edited, the editable video object providing system extracts a video object ID corresponding to any one of the edited video objects from the video object database included in the user terminal. One editable image object obtains edited edit information (930).

In this case, in operation 930, the editable image object providing system extracts an element ID corresponding to the element selected in operation 920 from the image object database included in the user terminal, thereby obtaining the extracted element ID as edit information. .

Next, the editable video object providing system transmits the video object ID and the edit information to the target terminal (940).

Here, since both the video object ID and the edit information are designed in the XML format schema, the editable video object providing system transmits the video object ID and the edit information to the target terminal in step 940 based on the MPEG Binary Format (BiM) technique. I can deliver it.

In operation 940, the editable video object providing system may deliver only some of the edited information to the target terminal in consideration of a reproduction scheme supported by the target terminal.

Next, the editable video object providing system extracts the editable video object corresponding to the video object ID from the video object database included in the target terminal (950).

Thereafter, the editable video object providing system applies edit information to the extracted edited video object and provides the edited video object to the target terminal (960).

In detail, in operation 960, the editable image object providing system is restored by applying the editing information to the edited image object (exactly, the editable image object image) extracted in step 950, thereby generating a reproduced image object. The playback type video object may be provided to the target terminal.

In operation 960, the editable video object providing system may play back the playable video object to the target terminal terminal based on a playback method supported by the target terminal.

According to an aspect of the invention, the service description providing unit for storing a service description; A communication interface for receiving a service recommendation request; And a recommendation engine that obtains a service description corresponding to the service recommendation request from the service description providing unit, and generates a recommendation description with reference to the service description, wherein the service description is a service general description. Format Type (FormatType), Service Target Information Type (ServiceTargetInformationType), Service Target Model Type (ServiceTargetModelType), Vocabulary Set Type (VocabularySetType), Service Interface Type (ServiceInterfaceType), Required Input Data Type (RequiredInputDataType), Internal Services Type ( Include at least one of InternalServicesType, InternalServiceType, Lossless AudioDBType, LossAudioDBType, LossyAudioDBType, VideoDBType, VideoDBType, Service ObjectType (ServiceObjectType), and ObjectType (ObjectType). Book A service recommendation device is provided.

According to an aspect of the present invention, a user description providing unit for storing a user description; A communication interface for receiving a service recommendation request; And a recommendation engine that obtains a user description corresponding to the service recommendation request from the user description provider, and generates a recommendation description with reference to the user description, wherein the user description includes a user profile type (UserProfileType), an individual. Profile type (PersonProfileType), Organization profile type (OrganizationProfileType), Device profile type (DeviceProfileType), Grouping profile type (GroupedProfileType), Usage history type (UsageHistoryTyp), Event type (EventType), Interaction atom type (interactionAtomType), Artifact type (artefactType), observableType, stateType, preference type, preference type, emotion type, lexical set type (VocabularySetType), schedule type (ScheduleType), activity type (ActivityType), intention type (IntentionType), LanguageType, SpecialtyType, Access A service recommendation apparatus including at least one of an accessibility type, a social information type, and an object sharing type is provided.

The usage history type (UsageHistoryTyp) may include a multimedia experience type and a user interaction type.

The preference type is one of a user preference type, an audio presentation preference type, a display presentation preference type, a graphic presentation preference type, a service preference type, an audio presentation preference information type, a translation preference type, an interest media type, and a web link preference type. It may include one or more.

The language type may include one or more of a name type, a language capability reference type, a language region type, a language type, a reading level type, a writing level type, a speaking level type, and a listening level type.

The language capability reference type may include a capability test name type, a competency level type (CompetenceLevelType), a capability test URI type, and a capability test date type.

The schedule type may include one or more of an event type, a schedule description type, a shared user type, a time type, and a description method type.

According to another aspect of the present invention, a method for recommending a service by a service recommendation apparatus, the method comprising: receiving a service recommendation request; Obtaining a user description corresponding to the service recommendation request; Generating a recommendation description with reference to the user description; The user description may include a user profile type (UserProfileType), a personal profile type (PersonProfileType), an organization profile type (OrganizationProfileType), a device profile type (DeviceProfileType), a grouped profile type (GroupedProfileType), a usage history type (UsageHistoryTyp), Event Type, Interaction Atom Type, Artifact Type, Observable Type, State Type, Preference Type, Emotion Type, VocabularySetType ), Schedule type (ScheduleType), activity type (ActivityType), intention type (IntentionType), language type (LanguageType), specialty type (SpecialtyType), accessibility type (AccessibilityType), social information type (SocialInformationType), and object sharing type (ObjectSharingType). Service recommendation method comprising one or more of the following.

The usage history type (UsageHistoryTyp) may include a multimedia experience type and a user interaction type.

The preference type is one of a user preference type, an audio presentation preference type, a display presentation preference type, a graphic presentation preference type, a service preference type, an audio presentation preference information type, a translation preference type, an interest media type, and a web link preference type. It may include one or more.

The language type may include one or more of a name type, a language capability reference type, a language region type, a language type, a reading level type, a writing level type, a speaking level type, and a listening level type.

The language capability reference type may include a capability test name type, a competency level type (CompetenceLevelType), a capability test URI type, and a capability test date type.

The schedule type may include one or more of an event type, a schedule description type, a shared user type, a time type, and a description method type.

According to an aspect of the invention, the service description providing unit for storing the context description; A communication interface for receiving a service recommendation request; And a recommendation engine that obtains the context description corresponding to the service recommendation request from the context description providing unit, and generates a recommendation description with reference to the context description, wherein the context description includes a context description type (ContextDescriptionType), Context Identification Type (ContextIdentificationType), Device Characteristic Type (DeviceCharacteristicsType), Network Information Type (NewworkInfoType), Location Type (LocationType), Weather Type (WeatherType), Additional Environment Information Type (OtherEnvironmentalInfoType), Audio Environment Type (AudioEnvironment), Recording Environment Provided is a service recommendation apparatus comprising one or more of a type (RecordingEnvironmentType) and a context priority type (ContextPriorityType).

The SYNTAX of the user description is:

<complexType name = "UD">

<sequence>

<element name = "ClassificationSchemeAlias" type = "ct: ClassificationSchemeAliasType" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "UserID" type = "mpeg7: UniqueIDType" />

<element name = "UserProfile" type = "ud: UserProfileType" minOccurs = "0" />

<element name = "UsageHistory" type = "ud: UsageHistoryType" minOccurs = "0" />

<element name = "Preference" type = "ud: PreferenceType" minOccurs = "0" />

<element name = "Emotion" type = "ud: EmotionType" minOccurs = "0" />

<element name = "Schedule" type = "ud: ScheduleType" minOccurs = "0" />

<element name = "Activity" type = "ud: ActivityType" minOccurs = "0" />

<element name = "Representation" type = "ct: ObjectType" minOccurs = "0" />

<element name = "Intention" type = "ud: IntentionType" minOccurs = "0" />

<element name = "Knowledge" type = "ud: KnowledgeType" minOccurs = "0" />

<element name = "ObjectSharing" type = "ud: ObjectSharingType" minOccurs = "0" />

<element name = "ServiceUsagePattern" type = "ud: UsagePatternType" minOccurs = "0" />

<element name = "LoudnessPreferences" type = "ud: LoudnessPreferencesType" />

<element name = "VisualExpressionPreference" type = "ud: VisualExpressionPreferenceType" />

</ sequence>

<attributeGroup ref = "ct: commonAttributes" />

</ complexType>

SEMANTIC is as follows.

Name Definition UD Serves as the root element of the MPEG-21 UD Format. The UD element shall be used as the topmost element to make user description in an instance of MPEG-21 UD Format. UserDescriptionType Specifies the syntax of the root element. This datataype is a set of descriptions which may contain static and dynamic information about user. Within this Type, UserProfile, Preference, Emotion, Schedule or Activity element shall be instantiated. ClassificationSchemeAlias Specifies an alias for a ClassificationScheme to be referenced within the UserDescriptionType by a simplified URI. UserID Describes the unique identifier of a user. UserProfile Describes user profile based on UserProfileType UsageHistory Describes usage history based onUsageHistoryType. This element can represent user's history for a given service, such as searching or movie recommendations. Preference Describes Preference based on PreferenceType. Emotion Describes Emotion based on EmotionType.This type representsuser's emotion, including its changes over time. Schedule Describes schedule based on ScheduleType. Activity Describes user activity based on ActivityType. Representation Describes the representation such as user character and image used by the user. This element can be used to describe user character on the social network. Intention Describes a list of intentions related to specific actions which a given user may perform with a multimedia object. Knowledge Describes a piece of knowledge that the user wants to share for recommendation purposes. ObjectSharing Describes the condition of authority (e.g. ID, ownership and accessibility of object) for the sharing and accessing of object to user or external service. UsagePattern Describes various patterns about usage of user based on UsagePatternType. Users use a lot of applications and services for a variety of reasons. Usagepattern might be used to figure out user's characteristics. commonAttributes Describes a group of attributes for the CommonAttributes.The syntax and semanticsof commonAttributes are specified in Common Type Loudnessreferences Describes static or dynamic personal and group audio preferences (e.g. audio levels, audio level history, and song preferences) and the usage history which helps with selecting appropriate audio service. VisualExpressionPreference A set of data edited by User's intention / emotion or created by recognizing User's situation / condition.

The SYNTAX of UsageHistoryType describing the history of the consumption and interaction of multimedia is as follows.

<complexType name = "UsageHistoryType">

<sequence>

<element name = "DetailedUserInteraction" type = "ud: DetailedUserInteractionType" minOccurs = "0" />

<element name = "ServiceUsageInformation" type = "ud: ServiceUsageInformationType" minOccurs = "0" />

</ sequence>

</ complexType>

<complexType name = "DetailedUserInteractionType">

<annotation>

<documentation> The main complex type describing detailed interaction with multimedia items </ documentation>

</ annotation>

<sequence>

<element name = "MultimediaExperiences">

<complexType>

<sequence>

<element name = "MultimediaExperience" type = "ud: MultimediaExperienceType" maxOccurs = "unbounded" />

</ sequence>

</ complexType>

</ element>

</ sequence>

</ complexType>

<complexType name = "ServiceUsageInformationType">

<sequence>

<element name = "ServiceID" type = "sd: ServiceDescriptionType" />

<element name = "UsageTime" type = "ct: TimeType" />

</ sequence>

</ complexType>

SEMANTIC is as follows.

Name Definition UsageHistoryType Specifies the history of interaction and consumption of multimedia MultimediaExperiences The set of multimedia experiences of the user ServiceUsageInformation Describes information about service usage based on ServiceUsageInformationType. Users use a lot of applications and services for a variety of reasons. When encountering a problem such as storage limitation and program errors, it might be difficult to describe usage history completely. In this case, ServiceUsageInformation element can be used to helps to summarize information about usage history. DetailedUserInteraction Structure containing information about the multimedia experiences of the user. UsageInformationType Describies a general information related to usage Annex NA SeiviceID Describes the service used by the user UsageTime Describes time duration for service usage. The syntax and semantics of TimeType are specified in Common Type (4.0 General Description).

An example is as follows.

<ud: UsageHistory>

<ud: ServiceUsageInformation>

<ud: ServiceID xmlns: ct = "urn: mpeg: mpeg21: UD: CT: 2016" xmlns: sd = "urn: mpeg: mpeg21: UD: SD: 2016">

<sd: ServiceID> 13243 </ sd: ServiceID>

<sd: ServiceGeneralInformation>

<sd: ServiceName> Service1 </ sd: ServiceName> <sd: ServiceProviderName> ServiceProvider </ sd: ServiceProviderName>

</ sd: ServiceGeneralInformation>

<sd: ServiceTargetInformation> </ sd: ServiceTargetInformation>

<sd: IsServiceAvailable> true </ sd: IsServiceAvailable>

</ ud: ServiceID>

<ud: UsageTime>

<startTime xmlns = "urn: mpeg: mpeg21: UD: CT: 2016"> 2016-01-03T09: 00: 00Z </ startTime>

<endTime xmlns = "urn: mpeg: mpeg21: UD: CT: 2016"> 2016-01-03T09: 40: 00Z </ endTime>

</ ud: UsageTime>

</ ud: ServiceUsageInformation>

</ ud: UsageHistory>

PreferenceType is as follows.

PreferenceType describes the preference related to the various services. Preference could be conceived of as an individual ’s attitude towards a set of objects. Interested topics, preference on presentation style, sensory effects preference, score of satisfaction, service usage preferences, preference on service provider, interested topics and multimedia can be a preference.

SYNTAX is as follows.

<complexType name = "PreferenceType">

<sequence>

<element name = "UserPreferences" type = "mpeg7: UserPreferencesType" minOccurs = "0" />

<element name = "AudioPresentationPreferences" type = "ud: AudioPresentationPreferencesType" minOccurs = "0" />

<element name = "DisplayPresentationPreferences" type = "mpeg21: DisplayPresentationPreferencesType" minOccurs = "0" />

<element name = "GraphicsPresentationPreferences" type = "mpeg21: GraphicsPresentationPreferencesType" minOccurs = "0" />

<element name = "TextPresentationPreferences" type = "ud: TextPresentationPreferencesType" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "ServicePreference" type = "ud: ServicePreferencesType" minOccurs = "0" />

<element name = "TranslationPreference" type = "ud: TranslationPreferenceType" minOccurs = "0" />

<element name = "WebLinkPreferences" type = "ud: WebLinkPreferenceType" minOccurs = "0" maxOccurs = "unbounded" />

</ sequence>

</ complexType>

SEMANTIC is as follows.

Name Definition PreferenceType Describes the preference related to the various services. Preference could be conceived of as an individual's attitude towards a set of objects. Interested topics, preference on presentation style, sensory effects preference, score of satisfaction, service usage preferences, preference on service provider, interested topics and media can be a Preference. UserPreferences Describes the user's preferences pertaining to consumption of multimedia content, in particular, filtering, searching and browsing of multimedia content. The mpeg7: UserPreferencesType contains FilteringAndSearchPreferences, BrowsingPreferences and RecordingPreferences, and contains an attribute indicating whether the user's preferences may be updated automatically. AudioPresentationPreferences Describes the preferences of a user regarding the presentation or rendering or audio resources. This element refers AudioPresentationPreferencesType. DisplayPresentationPreferences Describes preferences of a User regarding the presentation or rendering of images and videos. This mpeg21: DisplayPresentationPreferencesType includes descriptors of preferences related to the color and the conversion of stereoscopic video. The ColorTemperaturePreference, the BrightnessPreference, the SaturationPreference and the ContrastPreference describe the preferences of a User regarding the color of the displayed visual contents in terms of color temperature, brightness, saturation and contrast, each of which is a usual color attribute of images. Stereoscopic Video Conversion describes the preferences of a User related to the conversion of 2D video to 3D stereoscopic video and also the conversion of 3D stereoscopic video to 2D video. GraphicsPresentationPreferences Describes presentation preferences related to graphics media. This mpeg21: GraphicsPresentationPreferencesType contains GeometryEmphasis, TextureEmphasis and AnimationEmphasis element. TextPresentationPreferences Describes user's presentation preference related to text to be presented in the display device. ServicePreference Describes the level of preferences for specific services. TranslationPreference Describes the preferences for translation services. WebLinkPreferences Describes the preference related to the various weblinks

TextPresentationPreferencesType is as follows.

This TextPresentationPreferencesType describes user's presentation preference related to text to be presented in the display device.

SYNTAX is as follows.

<complexType name = "TextPresentationPreferencesType">

<sequence>

<element name = "TextPropertyPreference" type = "ud: TextPropertyPreferenceType" />

<element name = "TargetDisplayDeviceCapability" type = "mpeg21: DisplayCapabilityType" minOccurs = "0" />

</ sequence>

</ complexType>

<complexType name = "TextPropertyPreferenceType">

<complexContent>

<extension base = "mpeg21: FontType">

<attribute name = "italic" type = "boolean" use = "optional" default = "false" />

<attribute name = "oblique" type = "boolean" use = "optional" default = "false" />

<attribute name = "bold" type = "boolean" use = "optional" default = "false" />

<attribute name = "smallcap" type = "boolean" use = "optional" default = "false" />

<attribute name = "underline" type = "boolean" use = "optional" default = "false" />

<attribute name = "overline" type = "boolean" use = "optional" default = "false" />

</ extension>

</ complexContent>

</ complexType>

SEMANTIC is as follows.

Name Definition TextPropertyPreference Describes user's preference of text properties such as font type, font color, font size, font style, etc. TargetDisplayDevicCapability Describes the capabilities of the target display device to which text presentation preferences describing in TextPropertyPreference element are applied. The syntax and semantics of Display Capability Type are specified in ISO / IEC 21000-7. italic oblique Specifies whether oblique style is used or not. The default value is "false". The oblique style is slightly slanted but the letterforms do not change shape. bold smallCap Specifies whether small-cap style is used or not. The default value is "false". The small-cap style is that all lowercase letters are converted to uppercase letters. underline overline

An example follows.

<ud: UD>

<ud: UserID> keti </ ud: UserID>

<ud: Preference>

<ud: TextPresentationPreferences>

<ud: TextPropertyPreference fontColor = "black" fontSize = "10" fontType = "arial" italic = "true" underline = "true" />

<ud: TargetDisplayDeviceCapability>

<mpeg21: Mode>

<mpeg21: Resolution horizontal = "720" vertical = "480" />

</ mpeg21: Mode>

<mpeg21: ScreenSize horizontal = "49" vertical = "52" />

</ ud: TargetDisplayDeviceCapability>

</ ud: TextPresentationPreferences>

</ ud: Preference>

</ ud: UD>

WebLinkPreferenceType is as follows.

ebLinkPreferenceType type describes the preference related to the various weblinks.

WebLinkPreferenceType type is composed of WebLinkAddress element, WebLinkUsageHistoryType element and preferenceLevel attribute for that link.

SYNTAX is as follows.

<complexType name = "WebLinkPreferenceType">

<sequence>

<element name = "WebLinkAddress" type = "anyURI" />

<element name = "WebLinkUsageHistory" type = "ud: WebLinkUsageHistoryType" minOccurs = "0" maxOccurs = "unbounded" />

</ sequence>

<attribute name = "preferenceLevel" type = "ct: ZeroToOnehundredRatioType" use = "optional" default = "50" />

</ complexType>

SEMANTIC is as follows.

Name Definition WebLinkPreferenceType Describes the preference related to the specific weblink. WebLinkAddress Describes the URI of the preferred weblink. WebLinkUsageHistory Describes the Usage History of a specific WebLink preferenceLevel Describes a ranking of the weblink preference. Value ranges from 0 to 100 and default value is 50.

An example follows.

<ud: Preference>

<ud: WebLinkPreferences>

<ud: WebLinkAddress> </ ud: WebLinkAddress>

<ud: WebLinkUsageHistory feedback = "true">

<ud: Coordinates>

<ud: Time>

<ct: startTime xmlns: ct = "urn: mpeg: mpeg21: UD: CT: 2016"> 2015-06-04T18: 13: 51.0Z </ ct: startTime>

</ ud: Time>

</ ud: Coordinates>

</ ud: WebLinkUsageHistory>

</ ud: WebLinkPreferences>

</ ud: Preference>

WebLinkUsageHistoryType is as follows.

WebLinkUsageHistoryType type describes the usage history of a specific weblink.

SYNTAX is as follows.

<complexType name = "WebLinkUsageHistoryType">

<complexContent>

<extension base = "ud: EventType">

<attribute name = "feedback" type = "boolean" />

</ extension>

</ complexContent>

</ complexType>

SEMANTIC is as follows

Name Definition WebLinkUsageHistoryType Describes the usage history of a specific weblink. feedback Describes the user feedback of a specific weblink. It represents one of two values: TRUE or FALSE. (TRUE: Positive feedback, False: Negative feedback)

SocialInformationType is as follows.

SYNTAX is as follows.

<complexType name = "SocialInformationType">

<sequence>

<element name = "ServiceID" type = "sd: ServiceDescriptionType" minOccurs = "0" />

<element name = "LoginID" type = "ud: UserDescriptionType" />

<element name = "LoginPassword">

<simpleType>

<restriction base = "string">

<minLength value = "8" />

<maxLength value = "512" />

</ restriction>

</ simpleType>

</ element>

<element name = "Nickname" type = "Name" minOccurs = "0" />

<element name = "GroupID" type = "mpeg7: UserIdentifierType" minOccurs = "0" />

<element name = "FriendUserID" type = "mpeg7: UserIdentifierType" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "PrivateInformationAccessID" type = "mpeg7: UserIdentifierType" minOccurs = "0" maxOccurs = "unbounded" />

</ sequence>

</ complexType>

SEMANTIC is as follows

Name Definition socialinformationType Describes a specific information of a given user, provided to a specific service, mainly referred to a social community. ServiceID Describes the service used by the user. LoginID Describes the login id of the user. LoginPassword Describes the password. Nickname Describes the nickname of the user if any. GroupID Describes the group which the user belongs to. FriendUserID Describes the list of friends. PrivateInformationAccessID Describes the list of other users who can access private information of a given user.

KnowledgeType is as follows.

We propose to add the following complex type: This complex type describes knowledge that the user wants to share for recommendation purposes.

SYNTAX is as follows.

<complexType name = "KnowledgeType">

<choice maxOccurs = "unbounded">

<element name = "KnowledgeGraph">

<complexType>

<sequence>

<any namespace = "http://www.w3.org/1999/02/22-rdf-syntax-ns#" processContents = "skip" />

</ sequence>

<attribute name = "IRI" type = "anyURI" />

</ complexType>

</ element>

<element name = "KnowledgeGrpahRef">

<complexType>

<attribute name = "url" type = "anyURI" />

</ complexType>

</ element>

</ choice>

</ complexType>

SEMANTIC is as follows

The following example illustrates a case in which a user shares the knowledge about Wolfgang Amadeus Mozart. A Recommendation Engine can exploit this knowledge by e.g. exploring other entities in DBPedia of one or more of the categories stated in the Knowledge Graph about W.A. Mozart. For example, by exploring one of the dct: subject statements (namely the one pointing at the resource http://dbpedia.org/resource/Category:Austrian_classical_composers) the engine will discover that Joseph Haydn is also an Austrian classical composer, and thus can decide to recommend Haydn's compositions to the user.

<UD xmlns = "urn: mpeg: mpeg21: UD: UD: 2016" xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" xsi: schemaLocation = "urn: mpeg: mpeg21: UD : UD: 2016 1.MPEG_21_UD_UD.xsd "xmlns: rdf =" http://www.w3.org/1999/02/22-rdf-syntax-ns# ">

<UserID> U100 </ UserID>

<UserProfile>

[...]

</ UserProfile>

[...]

<Knowledge>

<KnowledgeGraph>

<rdf: RDF xmlns: rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns: rdfs = "http://www.w3.org/2000/01 / rdf-schema # "xmlns: dbo =" http://dbpedia.org/ontology/ "xmlns: dct =" http://purl.org/dc/terms/ "xmlns: owl =" http: // www .w3.org / 2002/07 / owl # "xmlns: dbp =" http://dbpedia.org/property/ "xmlns: foaf =" http://xmlns.com/foaf/0.1/ "xmlns: dc = "http://purl.org/dc/elements/1.1/" xmlns: prov = "http://www.w3.org/ns/prov#">

<rdf: Description rdf: about = "http://dbpedia.org/resource/Wolfgang_Amadeus_Mozart">

<rdf: type rdf: resource = "http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Agent" />

<rdf: type rdf: resource = "http://xmlns.com/foaf/0.1/Person" />

<rdf: type rdf: resource = "http://schema.org/Person" />

<rdf: type rdf: resource = "http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#NaturalPerson" />

<rdf: type rdf: resource = "http://dbpedia.org/ontology/Person" />

<rdf: type rdf: resource = "http://dbpedia.org/ontology/Agent" />

<dbo: deathPlace rdf: resource = "http://dbpedia.org/resource/Austria" />

<dbo: deathPlace rdf: resource = "http://dbpedia.org/resource/Vienna" />

<dbo: deathDate rdf: datatype = "http://www.w3.org/2001/XMLSchema#date"> 1791-12-05 </ dbo: deathDate>

<dbo: birthPlace rdf: resource = "http://dbpedia.org/resource/Salzburg" />

<dbo: birthPlace rdf: resource = "http://dbpedia.org/resource/Austria" />

<dbo: birthDate rdf: datatype = "http://www.w3.org/2001/XMLSchema#date"> 1756-01-27 </ dbo: birthDate>

<dct: subject rdf: resource = "http://dbpedia.org/resource/Category:Knights_of_the_Golden_Spur" />

<dct: subject rdf: resource = "http://dbpedia.org/resource/Category:German_male_classical_composers" />

<dct: subject rdf: resource = "http://dbpedia.org/resource/Category:German_opera_composers" />

<dct: subject rdf: resource = "http://dbpedia.org/resource/Category:Classical-period_composers" />

<dct: subject rdf: resource = "http://dbpedia.org/resource/Category:Austrian_opera_composers" />

<dct: subject rdf: resource = "http://dbpedia.org/resource/Category:Child_classical_musicians" />

<dct: subject rdf: resource = "http://dbpedia.org/resource/Category:Composers_for_pedal_piano" />

<dct: subject rdf: resource = "http://dbpedia.org/resource/Category:Austrian_classical_composers" />

</ rdf: Description>

</ rdf: RDF>

</ KnowledgeGraph>

</ Knowledge>

[...]

</ UD>

UsagePatternType

The UsagePatternType describes varioususages patterns ofuser.

SYNTAX is as follows.

<complexType name = "UsagePatternType">

<sequence>

<element name = "WebUsage">

<complexType>

<sequence>

<element name = "AverageTimeOfUsage" type = "duration" minOccurs = "0" />

<element name = "AverageNumberOfUsage" type = "integer" minOccurs = "0" />

</ sequence>

</ complexType>

</ element>

<!-<element name = "ApplicationUsage" type = "ud: ApplicatoinUsageType" /> TBC->

</ sequence>

</ complexType>

SEMANTIC is as follows

Name Definition UsagePatternType Specifies variouspatterns about usage pattern of user. WebUsage Specifies web usage pattern of user. AverageTimeOfUsage Describes a period of using web per day on average. AverageNumberOfUsage Describes a number of using web per day on average.

<ud: UsagePattern>

<ud: WebUsage>

<ud: AverageTimeOfUsage> P50M </ ud: AverageTimeOfUsage>

<ud: AverageNumberOfUsage> 3 </ ud: AverageNumberOfUsage>

</ ud: WebUsage>

</ ud: UsagePattern>

ContextDescriptionType

SYNTAX is as follows.

<complexType name = "CD" abstract = "true">

<attribute name = "InfoSource" type = "anyURI" />

</ complexType>

<complexType name = "ContextDescriptionType">

<sequence>

<element name = "ClassificationSchemeAlias" type = "ct: ClassificationSchemeAliasType" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "ContextIdentification" type = "cd: ContextIdentificationType" minOccurs = "0" />

<element name = "ValidTimeDuration" type = "ct: TimeType" minOccurs = "0" />

<element name = "Season" type = "mpeg7: termReferenceType" minOccurs = "0" />

<element name = "DeviceCharacteristics" type = "cd: DeviceCharacteristicsType" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "NetworkInfo" type = "cd: NetworkInfoType" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "Location" type = "ct: LocationType" minOccurs = "0" />

<element name = "Weather" type = "cd: WeatherType" minOccurs = "0" />

<element name = "OtherEnvironmentalInfo" type = "cd: OtherEnvironmentalInfoType" minOccurs = "0" />

<element name = "OtherContextInfo" type = "anyType" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "LoudnessEnvironment" type = "cd: LoudnessEnvironmentType" />

<element name = "VisualExpressionEnvironment" type = "cd: VisualExpressionEnvironmentType" />

</ sequence>

<attributeGroup ref = "ct: commonAttributes" />

<attribute name = "Priority" type = "ct: ZeroToOnehundredOrdinalType" use = "optional" />

</ complexType>

SEMANTIC is as follows

Name Definition CD This data element is the root element of the Context Description. ContextDescriptionType This data type contains static and dynamic information about the user context. ClassificationSchemeAlias Specifies an alias for a ClassificationScheme to be referenced within the UserDescriptionType by a simplified URI. ValidTimeDuration Describes valid time duration for context description. The syntax and semantics of PeriodOfTimeType are specified in Common Type (4.0 General Description). Season Describes current season information according to the region. Terms for the Season are specified by the CS Season (urn: mpeg: mpeg21: UD: CS: SeasonCS: 2016). DeviceCharacteristics Describes general characteristics of the terminal. NetworkInfo Describes network related information. Location Describes current location when a service is requested. The syntax and semantics of PlaceType are specified in ISO / IEC 15938-5. Weather Describes current weather when a service is requested. OtherEnvironmentalInfo Describes environmental information of noise or illumination characteristics around user. commonAttributes Describes a group of attributes for the CommonAttributes. The syntax and semantics of commonAttributes are specified in Common Type. Priority Describes the level of priority of the context description by using the ct: ZeroToOnehundredOrdinalType. OtherContextInfo A placeholder for other context-related information outside the standard namespace. LoudnessControlContextDescription Loudness Control Context Description describes the existing audio environment (e.g. natural noise, music from other audio sources, audio device's locations) which may be useful in recommending volume level and audio output devices in a heterogeneous audio environment. VisualExpressionContextDescription A set of data acquired from sensors or sensory devices about User's environment or body condition

8.1.1 ServiceDescriptionType

This subclause describes a structure of ServiceDescriptionType data type. The ServiceDescriptionType contains several elements, such as ServiceGeneralInformation, ServiceTargetInformation, ServiceInterfaces, InternalServices, Priority, IsServiceAvailable and ServiceObjectsInformation each of which is used for describing service ’s information.

8.1.1.1 Syntax

<complexType name = "SD">

<sequence>

<element name = "ClassificationSchemeAlias" type = "ct: ClassificationSchemeAliasType" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "ServiceID" type = "mpeg7: UniqueIDType" />

<element name = "ServiceGeneralInformation" type = "sd: ServiceGeneralInformationType" />

<element name = "ServiceTargetInformation" type = "sd: ServiceTargetInformationType" />

<element name = "ServiceInterfaces" type = "sd: ServiceInterfacesType" minOccurs = "0" />

<element name = "InternalServices" type = "sd: InternalServicesType" minOccurs = "0" />

<element name = "Priority" type = "ct: ZeroToOnehundredOrdinalType" minOccurs = "0" />

<element name = "IsServiceAvailable" type = "boolean" />

<element name = "ServiceObjectsInformation" type = "sd: ServiceObjectType" minOccurs = "0" />

<element name = "LoudnessControlServiceDescription" type = "LoudnessInfoType" />

<element name = "VisualExpressionServiceDescription" type = "SD: VisualExpression" />

<element name = "PrivacyProtectionServiceDescription" type = "SD: PrivacyProtection" />

<element name = "CompanionScreenServiceServiceDescription" type = "SD: CompanionScreenService" />

</ sequence>

</ complexType>

Name Definition ^SD Specifies the root element of the Service Description. ^{ClassificationSchemeAlias} The Classification scheme aliasinformation ServiceID Describes the unique ID of the service ServiceGeneralInformation Describes general information about a given service. ServiceTargetInformation Describes user's preferred service. ServiceInterfaces Describes interfaces used for exchanging information among the InternalServices Describes an internal service. Priority Specifies the priority level associated to a given service. IsServiceAvailable Specifies availability of the service. LoudnessControlServiceDescription Loudness Control Service Description shall describe set of supported audio services (e.g. audio output formats, volume levels, list of accessible copyright protected materials) available to the user in order to ensure continuous and smooth audio services while adhering to copyright protection and applicable laws. VisualExpressionServiceDescription A set of base visual objects for expressing human's emotion, intention, situation and condition.

VisualExpressionInfoType

<complexType name = "SD: VisualExpression">

<sequence>

<element name = "VisualObject" type = "VOType" />

</ sequence>

</ complexType>

<complexType name = "VOType">

<choice minOccurs = "0" maxOccurs = "unbounded">

<element name = "Face" type = "Face" />

<element name = "Clock" type = "Clock" />

<element name = "Animal" type = "Animal" />

<element name = "Fruit" type = "Fruit" />

<element name = "Weather" type = "Weather" />

<element name = "Food" type = "Food" />

<element name = "Vehicle" type = "Vehicle" />

<element name = "Plant" type = "Plant" />

<element name = "Building" type = "Building" />

</ choice>

</ complexType>

<complexType name = "Face">

<sequence>

<element name = "FaceOutline" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "Eye" type = "VOComponentInfo" maxOccurs = "unbounded" />

<element name = "Nose" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "Mouth" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "Hair" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "Ear" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "FacialHair" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "Eyebrows" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<\ sequence>

<\ complexType>

<complexType name = "Clock">

<sequence>

<element name = "Frame" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "HourNeedle" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "MinuteNeedle" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<\ sequence>

<\ complexType>

<complexType name = "Animal">

<extension base = "Face">

<sequence>

<element name = "Head" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "Body" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "Leg" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "Tail" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "Clothing" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "Horn" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "Wings" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<\ sequence>

<\ extension>

<\ complexType>

<complexType name = "Fruit">

<sequence>

<element name = "Body" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Leaf" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Stem" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<\ sequence>

<\ complexType>

<complexType name = "Weather">

<sequence>

<element name = "Sun" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "Cloud" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "Fog" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "Rain" type = "VOComponentInfo" minOccurs = "0" maxOccurs = "unbounded" />

<element name = "Snow" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Wind" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<\ sequence>

<\ complexType>

<complexType name = "Food">

<sequence>

<element name = "Rice" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Bread" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Hamburger" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Sandwich" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Steak" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Hotdog" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Fish" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Soup" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Curry" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Noodle" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Cake" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Fries" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Beer" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Wine" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Plate" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Cutlery" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<\ sequence>

<\ complexType>

<complexType name = "Vehicle">

<sequence>

<element name = "Body" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Wheel" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Wing" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Sail" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Door" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<\ sequence>

<\ complexType>

<complexType name = "Plant">

<sequence>

<element name = "Body" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Leaf" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Stem" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Fruit" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Root" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<\ sequence>

<\ complexType>

<complexType name = "Building">

<sequence>

<element name = "Structure" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Window" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Door" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<element name = "Roof" type = "VOComponentInfo" "minOccurs =" 0 "maxOccurs =" unbounded "/>

<\ sequence>

<\ complexType>

<complexType name = "VOComponentInfo" />

<sequence>

<element name = "PlacementX" type = "integer" maxOccurs = "1" />

<element name = "PlacementY" type = "integer" maxOccurs = "1" />

<element name = "Size" type = "integer" maxOccurs = "1" />

<element name = "Color" type = "string" maxOccurs = "1" />

<element name = "Rotation" type = "integer" maxOccurs = "1" />

<element name = "PlacementOrder" type = "integer" maxOccurs = "1" />

<sequence \>

<\ complexType>

The apparatus described above may be implemented as a hardware component, a software component, and / or a combination of hardware components and software components. For example, the devices and components described in the embodiments are, for example, processors, controllers, arithmetic logic units (ALUs), digital signal processors, microcomputers, field programmable gate arrays (FPGAs). Can be implemented using one or more general purpose or special purpose computers, such as a programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to the execution of the software. For convenience of explanation, one processing device may be described as being used, but one of ordinary skill in the art will appreciate that the processing device includes a plurality of processing elements and / or a plurality of types of processing elements. It can be seen that it may include. For example, the processing device may include a plurality of processors or one processor and one controller. In addition, other processing configurations are possible, such as parallel processors.

The software may include a computer program, code, instructions, or a combination of one or more of the above, and configure the processing device to operate as desired, or process it independently or collectively. You can command the device. Software and / or data may be any type of machine, component, physical device, virtual equipment, computer storage medium or device for the purpose of interpreting or providing instructions or data to the processing device. Or may be permanently or temporarily embodied in a signal wave to be transmitted. The software may be distributed over networked computer systems so that they may be stored or executed in a distributed manner. Software and data may be stored on one or more computer readable recording media.

The method according to the embodiment may be embodied in the form of program instructions that can be executed by various computer means and recorded in a computer readable medium. The computer readable medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the media may be those specially designed and constructed for the purposes of the embodiments, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs, DVDs, and magnetic disks, such as floppy disks. Magneto-optical media, and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. The hardware device described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

Although the embodiments have been described by the limited embodiments and the drawings as described above, various modifications and variations are possible to those skilled in the art from the above description. For example, the described techniques may be performed in a different order than the described method, and / or components of the described systems, structures, devices, circuits, etc. may be combined or combined in a different manner than the described method, or other components. Or even if replaced or substituted by equivalents, an appropriate result can be achieved.

Therefore, other implementations, other embodiments, and equivalents to the claims are within the scope of the claims that follow.

Claims (11)

In the schema-based editing image object providing method,
Constructing and maintaining a video object database in which a plurality of editable video objects are matched and stored with a plurality of video object IDs, respectively, on a memory included in each of the user terminal and the target terminal;
In response to a user input generated on a user interface provided by the user terminal, editing any one of the plurality of editable image objects stored in the image object database included in the user terminal;
As the edited video object is edited, the video object ID corresponding to the edited video object is extracted from the video object database included in the user terminal, and the edited video object is Obtaining edited edit information;
Transmitting the image object ID and the edit information to the target terminal;
Extracting an editable image object corresponding to the image object ID from the image object database included in the target terminal; And
Applying the edit information to the extracted editable video object and providing the edited information to the target terminal;
Including,
The one or more editable image objects include a face and a plurality of elements included in the face. The method of claim 1,
The plurality of elements
And an eyebrow, wherein the editing information for the eyebrow is provided to the target terminal. In the schema-based editing image object providing method,
Constructing and maintaining a video object database in which a plurality of editable video objects are matched and stored with a plurality of video object IDs, respectively, on a memory included in each of the user terminal and the target terminal;
In response to a user input generated on a user interface provided by the user terminal, editing any one of the plurality of editable image objects stored in the image object database included in the user terminal;
As the edited video object is edited, the video object ID corresponding to the edited video object is extracted from the video object database included in the user terminal, and the edited video object is Obtaining edited edit information;
Transmitting the image object ID and the edit information to the target terminal;
Extracting an editable image object corresponding to the image object ID from the image object database included in the target terminal; And
Applying the edit information to the extracted editable video object and providing the edited information to the target terminal;
Including,
The one or more editable video objects include an animal and a plurality of elements included in the animal. The method of claim 1,
The plurality of elements
And a head or wing, wherein the editing information for the head or wing is provided to the target terminal. The method of claim 1,
Each of the plurality of editable image objects,
At least one element representing at least one of an expression, an action, a state, or an environment of each of the plurality of editable image objects,
Building and maintaining the image object database,
Matching each of the at least one element with at least one element ID and storing and maintaining the at least one element in the image object database.
Editing image object providing method comprising a. The method of claim 5,
Editing an edited video object of any one of the plurality of editable video objects stored in the video object database included in the user terminal,
Selecting one element included in one of the editable video objects; And
Changing any one of the editable image objects based on the selected element
Including,
Acquiring the edited information edited by any one of the editable video objects,
Extracting an element ID corresponding to the selected element from the image object database; And
Acquiring the extracted element ID as the edit information;
Editing image object providing method comprising a. The method of claim 6,
Changing the one edited video object based on the selected element,
Generating a playable video object by changing one of the editable video objects; And
Playing the playback type video object on the user terminal based on a playback method supported by the user terminal;
Editing image object providing method further comprising. The method of claim 1,
Editing an edited video object of any one of the plurality of editable video objects stored in the video object database included in the user terminal,
Acquiring at least one of position information, environment information, body sensing information, schedule information, or image object usage history information of a user who uses the user terminal in response to an image object automatic generation input generated on the user interface; ; And
Selecting and editing any one of the plurality of editable image objects based on the obtained at least one information.
Editing image object providing method comprising a. The method of claim 1,
Editing an edited video object of any one of the plurality of editable video objects stored in the video object database included in the user terminal,
In response to a user manual edit input generated on the user interface, selecting and editing one of the editable video objects from among the plurality of editable video objects
Editing image object providing method comprising a. The method of claim 1,
The applying of the editing information to the extracted editable video object and providing the edited information to the target terminal may include:
Generating a playable video object by applying the edit information to the extracted editable video object; And
Providing the playback type video object to the target terminal
Editing image object providing method comprising a. The method of claim 10,
Providing the playback type video object to the target terminal,
Playing the playback type video object on the target terminal based on a playback scheme supported by the target terminal;
Editing image object providing method comprising a.

Images