KR102493026B1 - Server, user device and media play device for providing seamless service - Google Patents

Abstract

A server providing a seamless service includes an app information receiving unit receiving execution information of a first app that has been executed from a user terminal, a command receiving unit receiving a command for a second app corresponding to the first app from a media playback device, A metadata generator generating metadata for allowing the executed first app to be executed on the media playback device based on the received execution information of the first app, and transmitting the generated metadata to the media playback device. A metadata transmission unit is included, and the second app is executed by the media playback device following a page of the first app being output when execution is terminated in the user terminal based on the metadata.

Description

Server, user terminal and media playback device providing seamless service {SERVER, USER DEVICE AND MEDIA PLAY DEVICE FOR PROVIDING SEAMLESS SERVICE}

The present invention relates to a server providing a seamless service, a user terminal, and a media playback device.

An intelligent personal assistant is a software agent that handles tasks requested by users and provides specialized services to users. The intelligent personal assistant collects and provides customized information to the user based on an artificial intelligence (AI) engine and voice recognition, and performs various functions such as schedule management, email transmission, and restaurant reservation according to the user's voice command. It has the advantage of improving convenience.

These intelligent personal assistants are mainly provided in the form of customized personal services in smartphones, and representatively include Apple's Siri, Google's Now, and Samsung's Bixby. In this regard, Korea Patent Publication No. 2016-0071111, which is a prior art, discloses a method for providing a personal assistant service in an electronic device.

Recently, a user can be provided with various contents such as watching TV, listening to music, and transferring an account through an intelligent personal assistant only by uttering a voice command. However, in order to use the contents used in a terminal owned by an individual such as a smartphone through a public terminal, information for linking the smartphone with the intelligent personal assistant and the contents must be created in advance. It has a disadvantage that content cannot but be provided in non-real time.

An object of the present invention is to provide a user terminal, a media playback device, and a server that provide a seamless service that allows content seen on a smartphone to be viewed through a voice recognition speaker in real time. In the past, a server-to-server interworking method was used to provide content seamlessly in heterogeneous devices, but a seamless service is provided that allows content to be seamlessly provided to heterogeneous terminals using cache information without linking servers to servers. It is intended to provide a user terminal, a media playback device, and a server for Conventionally, in order to seamlessly provide content in heterogeneous devices, a mapping table was created in advance by interlocking information on content IDs for each interlocking system, but it is possible to seamlessly provide content to heterogeneous terminals without interlocking information in advance It is intended to provide a user terminal, a media playback device, and a server that provide a seamless service. However, the technical problem to be achieved by the present embodiment is not limited to the technical problems described above, and other technical problems may exist.

As a means for achieving the above-described technical problem, an embodiment of the present invention provides an app information receiver for receiving execution information of a first app that has been executed from a user terminal, and a first app corresponding to the first app from a media playback device. 2 A command receiver for receiving a command for an app, a metadata generator for generating metadata for allowing the executed first app to be executed in the media playback device based on the received execution information of the first app, and the A metadata transmission unit for transmitting generated metadata to the media reproducing device, and the second app is displayed following a page of the first app that was output when execution was terminated in the user terminal based on the metadata. A seamless service providing server executed by the media playback device may be provided.

In another embodiment of the present invention, an input unit for receiving a command for a first app from a user, a seamless service providing server based on the input command, and a second app corresponding to the first app executed and terminated in a media playback device A seamless service requesting unit for requesting a seamless service, a metadata receiving unit receiving metadata for allowing the first app to be executed in the user terminal from the seamless service providing server, and playing the media based on the received metadata. An app execution unit that executes the first app following a page of the second app that was output when execution was terminated on the device, wherein the metadata is stored in the execution information of the second app executed on the media playback device. It is possible to provide a user terminal that is generated based on the above.

In another embodiment of the present invention, an input unit for receiving a command for a first app from a user, and a second app corresponding to the first app executed and terminated in a user terminal as a seamless service providing server based on the input command A seamless service requester for requesting a seamless service, a metadata receiver for receiving metadata allowing the first app to be executed in the media playback device from the seamless service providing server, and the user based on the received metadata An app execution unit that executes the first app following a page of the second app that was output at the time when execution was terminated in the terminal, wherein the metadata is based on execution information of the second app that has been executed in the user terminal. It is possible to provide a media playback device that is created by doing so.

The above-described means for solving the problems is only illustrative and should not be construed as limiting the present invention. In addition to the exemplary embodiments described above, there may be additional embodiments described in the drawings and detailed description.

According to any one of the problem solving means of the present invention described above, it is possible to provide a user terminal, a media playback device, and a server that provide a seamless service for viewing content seen on a smartphone through a voice recognition speaker in real time. In the past, a server-to-server interworking method was used to provide content seamlessly in heterogeneous devices, but a seamless service is provided that allows content to be seamlessly provided to heterogeneous terminals using cache information without linking servers to servers. It is possible to provide a user terminal, a media playback device, and a server for Conventionally, in order to seamlessly provide content in heterogeneous devices, a mapping table was created in advance by interlocking information on content IDs for each interlocking system, but it is possible to seamlessly provide content to heterogeneous terminals without interlocking information in advance A user terminal, a media playback device, and a server providing a seamless service may be provided.

1 is a configuration diagram of a seamless service providing system according to an embodiment of the present invention.
2 is a configuration diagram of a user terminal according to an embodiment of the present invention.
3 is a flowchart of a method for providing a seamless service in a user terminal according to an embodiment of the present invention.
4 is a configuration diagram of a media playback device according to an embodiment of the present invention.
5 is a flowchart of a method of providing a seamless service in a media playback device according to an embodiment of the present invention.
6 is a configuration diagram of a seamless service providing server according to an embodiment of the present invention.
7 is a flowchart of a method for providing a seamless service in a seamless service providing server according to an embodiment of the present invention.
8A to 8C are exemplary diagrams for explaining a process of providing a seamless service according to an embodiment of the present invention.
9 is an operational flowchart for explaining a process of providing a seamless service in a seamless service providing system according to an embodiment of the present invention.
10 is an operational flowchart for explaining a process of providing a seamless service in a seamless service providing system according to another embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail so that those skilled in the art can easily practice the present invention with reference to the accompanying drawings. However, the present invention may be embodied in many different forms and is not limited to the embodiments described herein. And in order to clearly explain the present invention in the drawings, parts irrelevant to the description are omitted, and similar reference numerals are attached to similar parts throughout the specification.

Throughout the specification, when a part is said to be "connected" to another part, this includes not only the case where it is "directly connected" but also the case where it is "electrically connected" with another element interposed therebetween. . In addition, when a part "includes" a certain component, this means that it may further include other components, not excluding other components, unless otherwise stated, and one or more other characteristics. However, it should be understood that it does not preclude the possibility of existence or addition of numbers, steps, operations, components, parts, or combinations thereof.

In this specification, a "unit" includes a unit realized by hardware, a unit realized by software, and a unit realized using both. Further, one unit may be realized using two or more hardware, and two or more units may be realized by one hardware.

In this specification, some of the operations or functions described as being performed by a terminal or device may be performed instead by a server connected to the terminal or device. Likewise, some of the operations or functions described as being performed by the server may also be performed in a terminal or device connected to the corresponding server.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

1 is a configuration diagram of a seamless service providing system according to an embodiment of the present invention. Referring to FIG. 1 , a seamless service providing system 1 may include a user terminal 110 , a media playback device 120 , a display device 125 and a seamless service providing server 130 . The user terminal 110 , the media playback device 120 , the display device 125 , and the seamless service providing server 130 are examples of components that can be controlled by the seamless service providing system 1 .

Each component of the seamless service providing system 1 of FIG. 1 is generally connected through a network. For example, as shown in FIG. 1 , the seamless service providing server 130 may be connected to the user terminal 110 or the media playback device 120 simultaneously or at intervals.

A network refers to a connection structure capable of exchanging information between nodes such as terminals and servers, such as a local area network (LAN), a wide area network (WAN), and the Internet (WWW: World Wide Web), wired and wireless data communication network, telephone network, and wired and wireless television communication network. Examples of wireless data communication networks include 3G, 4G, 5G, 3rd Generation Partnership Project (3GPP), Long Term Evolution (LTE), World Interoperability for Microwave Access (WIMAX), Wi-Fi, Bluetooth communication, infrared communication, ultrasonic communication, visible light communication (VLC: Visible Light Communication), LiFi, and the like, but are not limited thereto.

According to an embodiment, the app executed on the user terminal 110 may be executed through the media playback device 120 following the page being output at the time when execution on the user terminal 110 is terminated.

When the user terminal 110 receives an input of termination of execution of the first app from the user, the user terminal 110 may transmit execution information of the terminated execution of the first app to the seamless service providing server 130 . The execution information of the first app includes cache information about the first app and authentication information about the first app in the user terminal 110, and the authentication information about the first app includes login information and authority about the first app. information, and the cache information for the first app may include URL information of a menu accessed from the user terminal 110 in the first app.

When receiving a command for a second app corresponding to the first app from the user, the media playback device 120 may transmit the input command for the second app to the seamless service providing server 130 . Here, the command may include a voice identifier for the second app. For example, the first app and the second app may be apps that perform the same function. Also, the first app and the second app may be the same app, but may have different versions, such as a version for a user terminal or a version for a media playback device.

The media playback device 120 may receive metadata generated based on execution information of the first app that has been executed and terminated in the user terminal 110 from the seamless service providing server 130 .

Based on the received metadata, the media playback device 120 may execute the second app following the page of the first app that was output at the time when execution was terminated in the user terminal 110 .

The seamless service providing server 130 may receive execution information of the first app, which has been executed, from the user terminal 110 .

The seamless service providing server 130 determines whether the user terminal 110 has subscribed to the seamless service for the first app, and based on the determination result, the user names of the user terminal 110 and the media playback device 120 can be paired by comparing.

The seamless service providing server 130 may receive a command for a second app corresponding to the first app from the media playback device 120 .

The seamless service providing server 130 may generate metadata for allowing the first App that has been executed to be executed in the media playback device 120 based on the received execution information of the first App. For example, the seamless service providing server 130 may generate metadata by mapping a voice identifier for the second app and cache information for the first app.

The seamless service providing server 130 may transmit the generated metadata to the media playback device.

According to another embodiment, the app executed on the media playback device 120 may be executed through the user terminal 110 following the page being output at the time when execution is terminated on the media playback device 120 .

The user terminal 110 may receive a command for the first app from the user.

The user terminal 110 may request a seamless service for a second app corresponding to the first app executed and terminated in the media playback device 120 from the seamless service providing server 130 based on the input command.

The user terminal 110 may receive metadata allowing the first app to be executed in the user terminal 110 from the seamless service providing server 130 .

Based on the received metadata, the user terminal 110 may execute the first app following the page of the second app that was output at the time when execution was terminated in the media playback device 120 .

The media playback device 120 may receive an input to terminate the execution of the second app through a voice command from the user. At this time, the media playback device 120 may transmit execution information of the second app that has been executed to the seamless service providing server 130 . The voice command may include at least one predetermined intent related to the second app, and the intent may be mapped with menu information of the second app.

The seamless service providing server 130 may receive execution information of the second app that has been executed from the media playback device 120 .

The seamless service providing server 130 may receive a request for a seamless service for the second app that has been executed and terminated in the media playback device 120 based on a command input from the user terminal 110 .

The seamless service providing server 130 may generate metadata so that the second app that has been executed is executed in the user terminal 110 based on execution information of the second app. For example, the seamless service providing server 130 may generate metadata based on execution information of the second app that has been executed and terminated in the media playback device 120 .

The seamless service providing server 130 may transmit the generated metadata to the user terminal 110 .

2 is a configuration diagram of a user terminal according to an embodiment of the present invention. Referring to FIG. 2 , the user terminal 110 may include an input unit 210, a seamless service request unit 220, a metadata receiver 230, and an app execution unit 240.

The input unit 210 may receive a command for the first app from the user. For example, the input unit 210 may receive a command for the first app through a touch input or a voice recognition function from the user.

The seamless service requesting unit 220 may request a seamless service for a second app corresponding to the first app executed and terminated in the media playback device 120 from the seamless service providing server 130 based on the input command.

The metadata receiving unit 230 may receive metadata allowing the first app to be executed in the user terminal 110 from the seamless service providing server 130 . Here, the metadata may be generated based on execution information of the second app that has been executed and terminated in the media playback device 120 . The execution information of the second app includes cache information about the second app and authentication information about the second app in the media playback device 120, and the authentication information about the second app includes login information about the second app and Including authority information, the cache information on the second app may include a voice command uttered by the user in relation to the second app in the media playback device 120 . In this case, the voice command may include at least one predetermined intent related to the second app, and the intent may be mapped with menu information of the second app.

Based on the received metadata, the app execution unit 240 may execute the first app following the page being output at the time when execution is terminated in the media playback device 120 .

3 is a flowchart of a method for providing a seamless service in a user terminal according to an embodiment of the present invention. The method for providing a seamless service in the user terminal 110 shown in FIG. 3 includes steps processed time-sequentially by the seamless service providing system 1 according to the embodiment shown in FIGS. 1 and 2 . Therefore, even if the contents are omitted below, they are also applied to the method of providing a seamless service in the user terminal 110 according to the embodiment shown in FIGS. 1 and 2 .

In step S310, the user terminal 110 may receive a command for the first app from the user.

In step S320, the user terminal 110 may request a seamless service for a second app corresponding to the first app executed and terminated in the media playback device 120 from the seamless service providing server 130 based on the input command. .

In step S330 , the user terminal 110 may receive metadata allowing the first app to be executed in the user terminal 110 from the seamless service providing server 130 . Here, the metadata may be generated based on execution information of the second app that has been executed and terminated in the media playback device 120 .

In step S340, the user terminal 110 may execute the first app following the page of the second app that was being displayed at the time when execution was terminated in the media playback device 120 based on the received metadata.

In the above description, steps S310 to S340 may be further divided into additional steps or combined into fewer steps, depending on the implementation of the present invention. Also, some steps may be omitted as needed, and the order of steps may be switched.

4 is a configuration diagram of a media playback device according to an embodiment of the present invention. Referring to FIG. 4 , the media playback device 120 may include an input unit 410, a speaker identification unit 420, a seamless service request unit 430, a metadata receiver 440, and an app execution unit 450. there is.

The input unit 410 may receive a command for the first app from the user. For example, the input unit 410 may receive a command for the first app such as “GiGA Genie, seamless play!” from the user.

The speaker identification unit 420 may identify a non-audible frequency for the command received from the user and identify a speaker based on the checked non-audible frequency.

The seamless service requesting unit 430 may request a seamless service for a second app corresponding to the first app executed and terminated in the user terminal 110 from the seamless service providing server 130 based on the input command.

The metadata receiving unit 440 may receive metadata allowing the first app to be executed in the media playback device 120 from the seamless service providing server 130 . Here, the metadata may be generated based on execution information of the second app that has been terminated in the user terminal 110 . The app execution information includes cache information for the second app and authentication information for the second app in the user terminal 110, and the authentication information for the second app includes login information for the second app (for example, , Access/authentication token, etc.) and authority information (Authority), and the cache information for the second app is the URL information of the menu accessed from the user terminal 110 in the second app and the media playback device 120. It may include a voice command uttered by the user in relation to the first app. In this case, the voice command includes a voice identifier for the first app, and the metadata is generated by the seamless service providing server 130 by mapping the voice identifier for the first app and cache information for the second app. it could be For example, when the voice command is “seamless play”, “seamless play” may be mapped to information about the last menu being viewed on the user terminal 110 and the last play time of the VOD.

Based on the received metadata, the app execution unit 450 may execute the first app following the page of the second app that was being displayed at the time when execution was terminated in the user terminal 110 . For example, when a drama is played for 20 minutes on the user terminal 110 and then is terminated, and a voice command “Giga Genie, seamless play” is input from the user through the input unit 410, the app execution unit 450 displays the drama The drama can be reproduced from the point of view 20 minutes after the viewing point.

5 is a flowchart of a method of providing a seamless service in a media playback device according to an embodiment of the present invention. The method for providing a seamless service in the media playback device 120 shown in FIG. 5 includes steps processed time-sequentially by the seamless service providing system 1 according to the embodiment shown in FIGS. 1 to 4 . Therefore, even if the details are omitted below, they are also applied to the method of providing a seamless service in the media playback device 120 according to the embodiments shown in FIGS. 1 to 4 .

In step S510, the media playback device 120 may receive a command for the first app from the user.

In step S520, the media playback device 120 may request a seamless service for the second app corresponding to the first app executed and terminated in the user terminal 110 from the seamless service providing server 130 based on the input command. .

In step S530, the media playback device 120 may receive metadata allowing the first app to be executed in the media playback device 120 from the seamless service providing server 130. The metadata may be generated based on execution information of the second app that has been executed in the user terminal 110 .

In step S540, the media playback device 120 may execute the first app following the page of the second app that was being displayed at the time when execution was terminated in the user terminal 110 based on the received metadata.

In the foregoing description, steps S510 to S540 may be further divided into additional steps or combined into fewer steps, depending on an embodiment of the present invention. Also, some steps may be omitted as needed, and the order of steps may be switched.

6 is a configuration diagram of a seamless service providing server according to an embodiment of the present invention. Referring to FIG. 6 , the seamless service providing server 130 includes an app information receiver 610, a determination unit 620, a pairing unit 630, a command receiver 640, a metadata generator 650, and metadata transmission. A portion 660 may be included.

The app information receiving unit 610 may receive execution information of the first app whose execution has been terminated from the user terminal 110 . The execution information of the first app includes cache information about the first app and authentication information about the first app in the user terminal 110, and the authentication information about the first app includes login information (Access) about the first app. / authentication token) and authority information (Authority), and the cache information for the first app is URL information (eg, www.kt.com) of a menu accessed from the user terminal 110 in the first app. can include

The determination unit 620 may determine whether the user terminal 110 has subscribed to the seamless service for the first app.

The pairing unit 630 may perform pairing by comparing user names of the user terminal 110 and the media playback device 120 based on the determination result of the determination unit 620 .

The command receiving unit 640 may receive a command for a second app corresponding to the first app from the media playback device 120 . For example, the command receiving unit 640 may receive a voice command such as “Giga Genie, seamless play!”. In this case, the command may include a voice identifier for the second app.

The metadata generating unit 650 may generate metadata to allow the first app that has been executed to be executed in the media playback device 120 based on the received execution information of the first app. For example, the metadata generating unit 650 may generate metadata by mapping the voice identifier for the second app and the cache information for the first app.

The metadata transmission unit 660 may transmit the generated metadata to the media playback device 120 . At this time, when the metadata is transmitted to the media playback device 120, the second app follows the page of the first app that was output at the time when execution was terminated in the user terminal 110 based on the metadata, followed by the media playback device ( 120) can be executed.

7 is a flowchart of a method for providing a seamless service in a seamless service providing server according to an embodiment of the present invention. The seamless service providing method in the seamless service providing server 130 shown in FIG. 7 includes steps processed time-sequentially by the seamless service providing system 1 according to the embodiment shown in FIGS. 1 to 6 . . Therefore, even if the contents are omitted below, they are also applied to the method of providing the seamless service in the seamless service providing server 130 according to the embodiments shown in FIGS. 1 to 6 .

In step S710, the seamless service providing server 130 may receive execution information of the first app that has been executed from the user terminal 110.

In step S720, the seamless service providing server 130 may receive a command for a second app corresponding to the first app from the media playback device 120.

In step S730 , the seamless service providing server 130 may generate metadata for allowing the first App to be executed in the media playback device 120 based on the received execution information of the first App.

In step S740, the seamless service providing server 130 may transmit the generated metadata to the media playback device 120.

In the foregoing description, steps S710 to S740 may be further divided into additional steps or combined into fewer steps, depending on an embodiment of the present invention. Also, some steps may be omitted as needed, and the order of steps may be switched.

8A to 8C are exemplary diagrams for explaining a process of providing a seamless service according to an embodiment of the present invention.

8A is an exemplary diagram for explaining a process of providing a seamless service when a VoD app is used in a user terminal according to an embodiment of the present invention. Referring to FIG. 8A , the user terminal 801 ends watching a program called 'Infinite Challenge' through the VoD app, and the media playback device 802 receives a voice command from the user 800 saying "Giga Genie! Seamless play!" When is received, the media playback device 802 can reproduce the VoD through the display device 803 from the point of time when the user terminal 801 has finished viewing.

8B is an exemplary diagram for explaining a process of providing a seamless service when a user terminal uses a banking app according to an embodiment of the present invention. Referring to FIG. 8B , the user terminal 811 exits the account transfer menu through the banking app, and the media playback device 812 inputs a voice command from the user 810, "GiGA Genie! Seamless play!" If received, the media playback device 802 may display the corresponding menu from the point of time when the menu ends in the user terminal 811 through the display device 803 .

8C is an exemplary diagram for explaining a process of providing a seamless service when a user terminal uses a music app according to an embodiment of the present invention. Referring to FIG. 8C , the user terminal 821 terminates playback of music called 'Flower Road' through the music app, and the media playback device 822 receives a voice command from the user 820 saying "GiGA Genie! Seamless play!" When is received, the media playback device 822 can play music from the point of time when the playback in the user terminal 821 is finished.

9 is an operational flowchart for explaining a process of providing a seamless service in a seamless service providing system according to an embodiment of the present invention. Referring to FIG. 9 , a seamless service providing system 1 may include a user terminal 110 , a media playback device 120 and a seamless service providing server 130 . According to an embodiment, the seamless service providing system 1 may allow an app that has been executed in the user terminal 110 to be subsequently executed through the media playback device 120 .

When the execution of the first app in the user terminal 110 is terminated (S910), the user terminal 110 may transmit execution information of the terminated first app to the seamless service providing server 130 (S920).

When the media playback device 120 receives a command for the second app corresponding to the first app from the user (S930), it may transmit the input command for the second app to the seamless service providing server 130 (S940). ).

The seamless service providing server 130 generates metadata so that the executed first app is executed on the media playback device 120 based on the execution information of the first app (S950), and converts the generated metadata to the media playback device. It can be transmitted to (120) (S960).

Based on the received metadata, the media playback device 120 may execute the second app following the page of the first app that was output at the time when execution was terminated in the user terminal 110 (S970).

In the foregoing description, steps S910 to S970 may be further divided into additional steps or combined into fewer steps, depending on an embodiment of the present invention. Also, some steps may be omitted as needed, and the order of steps may be switched.

10 is an operational flowchart for explaining a process of providing a seamless service in a seamless service providing system according to another embodiment of the present invention. Referring to FIG. 10 , a seamless service providing system 1 may include a user terminal 110 , a media playback device 120 and a seamless service providing server 130 . According to another embodiment, the seamless service providing system 1 may allow an app that has been executed in the media playback device 120 to be subsequently executed through the user terminal 110 .

When the execution of the first app in the media playback device 120 is terminated (S1010), the media playback device 120 may transmit execution information of the terminated first app to the seamless service providing server 130 (S1020). .

When the user terminal 110 receives a command for the second app from the user (S1030), the seamless service for the first app executed and terminated in the media playback device 120 is provided based on the input command to the seamless service providing server (S1030). 130) can be requested (S1040).

The seamless service providing server 130 generates metadata so that the executed first app is executed on the user terminal 110 based on the execution information of the first app (S1050), and converts the generated metadata to the user terminal 110. ) can be transmitted (S1060).

Based on the received metadata, the user terminal 110 may execute the second app following the page of the first app being output at the time when execution is terminated in the media playback device 120 (S1070).

In the above description, steps S1010 to S1070 may be further divided into additional steps or combined into fewer steps, depending on an embodiment of the present invention. Also, some steps may be omitted if necessary, and the order of steps may be switched.

The method for providing a seamless service in a user terminal, a media playback device, and a seamless service providing server described with reference to FIGS. 1 to 10 includes a computer program stored in a medium executed by a computer or a recording medium including instructions executable by a computer. It can also be implemented in the form of. Also, the method for providing a seamless service in the user terminal, the media playback device, and the seamless service providing server described with reference to FIGS. 1 to 10 may be implemented in the form of a computer program stored in a medium executed by a computer.

Computer readable media can be any available media that can be accessed by a computer and includes both volatile and nonvolatile media, removable and non-removable media. Also, computer readable media may include computer storage media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data.

The above description of the present invention is for illustrative purposes, and those skilled in the art can understand that it can be easily modified into other specific forms without changing the technical spirit or essential features of the present invention. will be. Therefore, the embodiments described above should be understood as illustrative in all respects and not limiting. For example, each component described as a single type may be implemented in a distributed manner, and similarly, components described as distributed may be implemented in a combined form.

The scope of the present invention is indicated by the following claims rather than the detailed description above, and all changes or modifications derived from the meaning and scope of the claims and equivalent concepts should be construed as being included in the scope of the present invention. do.

110: user terminal
120: media playback device
125: display device
130: seamless service providing server
210: input unit
220: seamless service request unit
230: metadata receiver
240: app execution unit
410: input unit
420: speaker identification unit
430: seamless service request unit
440: metadata receiver
450: app execution unit
610: app information receiver
620: judgment unit
630: pairing unit
640: command receiving unit
650: metadata generation unit
660: metadata transmission unit

Claims (18)

In a server providing a seamless service,
an app information receiving unit receiving execution information of a first app whose execution has been terminated from a user terminal;
a command receiver configured to receive a command for a second app corresponding to the first app from a media playback device;
a metadata generator configured to generate metadata allowing the executed first App to be executed in the media playback device based on the received execution information of the first App; and
A metadata transmission unit for transmitting the generated metadata to the media playback device;
The second app is executed by the media playback device following the page of the first app that was being output when execution was terminated in the user terminal based on the metadata,
Wherein the metadata generating unit generates the metadata by mapping a command for the second app and execution information for the first app.
According to claim 1,
Wherein the execution information of the first app includes at least one of cache information for the first app executed in the user terminal and authentication information for the first app, seamless service providing server.
According to claim 2,
The authentication information for the first app includes at least one of login information and authority information for the first app, seamless service providing server.
According to claim 2,
The cache information for the first app includes URL information of a menu accessed from the user terminal in the first app, seamless service providing server.
According to claim 2,
The command for the second app includes a voice identifier for the second app;
Wherein the metadata generation unit generates the metadata by mapping a voice identifier for the second app and cache information for the first app.
According to claim 1,
Further comprising a determination unit for determining whether the user terminal has subscribed to the seamless service for the first app, the seamless service providing server.
According to claim 6,
The seamless service providing server further comprises a pairing unit that compares and pairs user names of the user terminal and the media playback device based on the determination result.
In a user terminal providing a seamless service,
an input unit that receives a command for the first app from a user;
a seamless service request unit requesting a seamless service for a second app corresponding to the first app that has been executed and terminated in a media playback device to a seamless service providing server based on the input command;
a metadata receiving unit receiving metadata for allowing the first app to be executed in the user terminal from the seamless service providing server; and
An app execution unit that executes the first app following a page of the second app that was being output when execution was terminated in the media playback device based on the received metadata;
The metadata is generated based on execution information of a second app that has been executed and terminated in the media playback device,
The metadata is generated by mapping a command for the first app and execution information for the second app, the user terminal.
According to claim 8,
The execution information of the second app includes at least one of cache information for the second app executed in the media playback device and authentication information for the app.
According to claim 9,
The authentication information for the second app includes at least one of login information and authority information for the second app, the user terminal.
According to claim 9,
The cache information for the second app includes at least one voice command uttered by a user in relation to the second app in the media playback device, the user terminal.
According to claim 11,
The voice command includes at least one predetermined intent related to the second app,
The intent is mapped with menu information of the second app, the user terminal.
A media playback device providing a seamless service,
an input unit that receives a command for the first app from a user;
a seamless service requesting unit requesting a seamless service for a second app corresponding to the first app that has been executed and terminated in a user terminal to a seamless service providing server based on the input command;
a metadata receiving unit receiving metadata for allowing the first app to be executed in the media playback device from the seamless service providing server; and
Based on the received metadata, an app execution unit that executes the first app following a page of the second app that was being output when execution was terminated in the user terminal,
The metadata is generated based on execution information of the second app that has been terminated in the user terminal,
Wherein the metadata is generated by mapping a command for the first app and execution information for the second app.
According to claim 13,
Wherein the execution information of the second app includes at least one of cache information on the second app executed in the user terminal and authentication information on the second app.
15. The method of claim 14,
The media playback device, wherein the authentication information for the second app includes at least one of login information and authority information for the second app.
15. The method of claim 14,
The cache information for the second app includes URL information of a menu accessed from the user terminal in the second app.
15. The method of claim 14,
The command for the first app includes a voice identifier for the first app;
Wherein the metadata is generated by the seamless service providing server by mapping a voice identifier for the first app and cache information for the second app.
According to claim 13,
and a speaker identification unit that identifies a non-audible frequency for the command received from the user and identifies a speaker based on the identified non-audible frequency.

Images