KR102566262B1 - Service server and operating method thereof - Google Patents

Abstract

An operating method of a service server according to an embodiment includes receiving an execution request of a web app from a user terminal; providing a screen to the user terminal based on the execution request and access information corresponding to the user terminal; and transmitting information corresponding to the type of key input signal received from the user terminal to the user terminal while providing the screen to the user terminal, and establishing a session connection with the user terminal based on the type of the key input signal. It may include an operation of determining whether to keep . In addition, various embodiments may be possible.

Description

Service server and its operating method {SERVICE SERVER AND OPERATING METHOD THEREOF}

Various embodiments of the present disclosure relate to a service server and an operating method thereof, and more particularly, to a service server providing a screen to a user terminal and an operating method thereof.

Recently, with the development of cloud streaming technology, virtualization technology capable of driving high-specification applications with low-specification user terminals has been proposed mainly for game services.

As a related prior art, there is Korean Patent Registration No. 10-1795537 (title of invention: network environment adaptive cloud streaming service providing system and method, applicant: Kyungpook National University Industry-University Cooperation Foundation). According to the registered patent publication, the reproduction quality of the video output through the user terminal is improved by setting the video quality to be transmitted to the user terminal by considering both the network status between the video server and the cloud server and the network status between the cloud server and the user terminal in the cloud server. A network environment adaptive cloud streaming system and method for improving are disclosed.

In the case of a cloud streaming-based service, since a service is provided to a large number of users, managing sessions of connected users may have a significant impact on service quality.

Even if the user does not need to maintain a session connection with the cloud server, if the connection is maintained, a waste of resources occurs in the server and the service may not be provided to more people.

However, the technical challenges are not limited to the above-described technical challenges, and other technical challenges may exist.

According to one embodiment, the service server includes a database for storing access information for each user terminal; a browser that determines the type of key input signal received from the user terminal and executes a web app; and a processor, wherein the processor receives an execution request of a web app from the user terminal; providing a screen to the user terminal based on the execution request and the access information corresponding to the user terminal; and transmitting information corresponding to the type of key input signal received from the user terminal to the user terminal while providing the screen to the user terminal, and establishing a session connection with the user terminal based on the type of the key input signal. It is possible to perform an operation to determine whether to keep .

According to an embodiment, when the key input signal is a focusing movement signal within the web app, the processor transmits a screen according to the focusing movement to the user terminal and establishes a session connection with the user terminal. maintenance can be performed.

According to an embodiment, the processor may further include: storing access information corresponding to the user terminal when the key input signal is a native app execution request; and transmitting the native app execution signal to the user terminal and stopping the session connection with the user terminal.

According to an embodiment, the processor may include: connecting a session with the user terminal when the execution of the native app is terminated in the user terminal and a session connection request is received from the user terminal; and providing a screen to the user terminal based on the access information corresponding to the user terminal.

According to one embodiment, the processor, when the key input signal is a web app execution request different from the web app, storing access information corresponding to the user terminal; and transmitting an execution signal for the other web app to the user terminal and stopping the session connection with the user terminal.

According to one embodiment, the processor, when receiving the other web app execution request from the user terminal, the operation of connecting the session with the user terminal; and providing a screen to the user terminal based on the execution request and the access information corresponding to the user terminal.

According to an embodiment, the access information includes user terminal information, information about a web app previously provided to the user terminal, screen information about the final screen of each of the apps provided to the user terminal, and the final screen information. Includes focusing information on a location of a pointer on a screen, and the screen information identifies any one of an initial screen, a primary screen according to an input on the initial screen, and a secondary screen according to an input on the primary screen. may be information.

According to an embodiment, the processor may capture an image of a region changed from a previous screen among rendered images of the web app executed in the browser and provide the screen to the user terminal.

According to an embodiment, a method of operating a service server may include receiving an execution request of a web app from a user terminal; providing a screen to the user terminal based on the execution request and access information corresponding to the user terminal; and transmitting information corresponding to the type of key input signal received from the user terminal to the user terminal while providing the screen to the user terminal, and establishing a session connection with the user terminal based on the type of the key input signal. It may include an operation of determining whether to keep .

According to an embodiment, the operating method of the service server may include, when the key input signal is a focusing movement signal in the web app, transmits a screen according to the focusing movement to the user terminal, and transmits a screen corresponding to the focusing movement to the user terminal and It may include an operation to maintain the session connection of.

According to one embodiment, the operating method of the service server may include: storing access information corresponding to the user terminal when the key input signal is a native app execution request; and transmitting the native app execution signal to the user terminal and stopping the session connection with the user terminal.

According to an embodiment, the operating method of the service server may include: connecting a session with the user terminal when execution of the native app is terminated in the user terminal and a session connection request is received from the user terminal; and providing a screen to the user terminal based on the access information corresponding to the user terminal.

According to one embodiment, the operating method of the service server may include, when the key input signal is a request to execute a web app different from the web app, storing access information corresponding to the user terminal; and transmitting an execution signal for the other web app to the user terminal and stopping the session connection with the user terminal.

According to an embodiment, the operating method of the service server may include: connecting a session with the user terminal when receiving a request to run another web app from the user terminal; and providing a screen to the user terminal based on the execution request and the access information corresponding to the user terminal.

According to an embodiment, the access information includes user terminal information, information about a web app previously provided to the user terminal, screen information about the final screen of each of the apps provided to the user terminal, and the final screen information. Includes focusing information on a location of a pointer on a screen, and the screen information identifies any one of an initial screen, a primary screen according to an input on the initial screen, and a secondary screen according to an input on the primary screen. may be information.

According to an embodiment, the operation of providing a screen to the user terminal based on the execution request and the access information corresponding to the user terminal is a change from a previous screen among rendered images of the web app executed in the browser. An operation of capturing an image of an area and providing a screen to the user terminal may be included.

According to various embodiments, the service server may provide a previous access screen of the user terminal more quickly by utilizing access information in providing the screen to the user terminal.

According to various embodiments, the service server determines the type of a user's key input signal received while providing a screen to a user terminal through screen virtualization, and determines whether or not to maintain a session connection with the user terminal according to the type, so that multiple users can simultaneously A service considering the connection environment can be provided.

In addition to this, various effects identified directly or indirectly through this document may be provided.

1 is a configuration diagram of a service server according to various embodiments.
2 is a diagram for explaining an operation of connecting a session between a user terminal and a service server through a session server according to various embodiments.
3A and 3B are diagrams for explaining screen information included in an access information database according to various embodiments.
4A and 4B are diagrams for explaining types of key input signals according to various embodiments.
5 is a flowchart illustrating a method of providing a screen when a key input signal is a focusing movement signal according to various embodiments of the present disclosure.
6 is a flowchart illustrating a method of providing a screen when a key input signal is a request to execute a native app, according to various embodiments.
7 is a flowchart illustrating a method of providing a screen when a key input signal is a request to execute another web app according to various embodiments.
8 is a flowchart illustrating a method of determining whether a service server maintains a session connection with a user terminal according to various embodiments.
9 is a flowchart illustrating an operation method of a service server when a key input signal is a focusing movement signal according to various embodiments.
10 is a flowchart illustrating a method of operating a service server when a key input signal is a native app execution request according to various embodiments.
11 is a flowchart illustrating an operation method of a service server when a key input signal is a request to execute another web app according to various embodiments.

Specific structural or functional descriptions of the embodiments are disclosed for illustrative purposes only, and may be changed and implemented in various forms. Therefore, the form actually implemented is not limited only to the specific embodiments disclosed, and the scope of the present specification includes changes, equivalents, or substitutes included in the technical idea described in the embodiments.

Although terms such as first or second may be used to describe various components, such terms should only be construed for the purpose of distinguishing one component from another. For example, a first element may be termed a second element, and similarly, a second element may be termed a first element.

It should be understood that when an element is referred to as being “connected” to another element, it may be directly connected or connected to the other element, but other elements may exist in the middle.

Singular expressions include plural expressions unless the context clearly dictates otherwise. In this specification, terms such as "comprise" or "have" are intended to designate that the described feature, number, step, operation, component, part, or combination thereof exists, but one or more other features or numbers, It should be understood that the presence or addition of steps, operations, components, parts, or combinations thereof is not precluded.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related art, and unless explicitly defined in this specification, it should not be interpreted in an ideal or excessively formal meaning. don't

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. In the description with reference to the accompanying drawings, the same reference numerals are given to the same components regardless of reference numerals, and overlapping descriptions thereof will be omitted.

<service server>

1 is a configuration diagram of a service server according to various embodiments.

Referring to FIG. 1 , a configuration diagram of a service server 100 providing services through a network is shown. According to an embodiment, the service server 100 may provide a virtualized user interface (UI) screen to the user terminal 180 through a network. According to an embodiment, the service server 100 determines the type of key input signal received from the access information database 130 that stores access information for each user terminal, the user terminal 180, and the web It may include a browser and a processor 120 that executes an app (web app).

According to an embodiment, the service server 100 provides a screen to the user terminal 180 in a cloud streaming method, and allows only input and output to be performed in the user terminal 180, thereby performing the performance of the user terminal 180. Regardless, high-end services can be provided. Specifically, the same user experience as executed in the user terminal 180 may be provided by implementing an execution screen in the service server 100 connected to the user terminal 180 through a network. According to an embodiment, the service server 100 executes various applications such as a user interface (UI) application and a game application, captures the execution screen, generates a captured image, encodes it, and converts it into a streaming method. It can be transmitted to the user terminal 180. The service server 100 may drive an application according to a user input transmitted from the user terminal 180 and may capture and transmit the changed execution screen to the user terminal 180 in a streaming manner.

Although not shown in FIG. 1 , the service server 100 may provide content to the user terminal 180 in conjunction with a media platform. The media platform may provide predetermined content in a streaming method separately from the service server 100 . For example, real-time broadcasting or video content such as VOD may be provided, and this media platform may be operated by a service provider different from the service server 100 .

According to an embodiment, content provided by a media platform (not shown) is fused with content provided by the service server 100 through interworking between the user terminal 180 and the service server 100, and thus the user terminal 180 can be provided as For example, a user interface screen provided by the service server 100 may be fused with video images of real-time broadcasting or VOD provided by a media platform. However, it is not limited thereto, and according to the service server 100 according to various embodiments, various types of different contents may be converged.

According to various embodiments, applications driven by the service server 100 according to user input transmitted from the user terminal 180 may include web apps and native apps. There may be a difference in that a web app is executed through the browser 150 and a native app is developed in a language optimized for the user terminal 180 and executed in the user terminal 180. .

According to an embodiment, when a web app execution request is received from the user terminal 180, the processor 120 requests the browser 150 to execute the web app, and the processor 120 requests the browser 150 to execute the web app. ) may capture and provide the captured image to the user terminal 180 in a streaming manner.

According to an embodiment, when a request to run a native app is received from the user terminal 180, the processor 120 transmits information related to running the native app to the user terminal 180, and the user terminal 180 transmits the native app execution request. this can be executed. For example, when a request for playing VOD content is received from the user terminal 180, the processor 120 receives corresponding VOD content information from a media platform (not shown) and transmits it to the user terminal 180, and In 180, the corresponding VOD content can be played through the VOD player, which is a native app.

The network according to an embodiment is a configuration for transferring data by connecting the user terminal 180 and the service server 100, and may be implemented as various types of communication networks. For example, a wireless communication method such as WLAN (Wireless LAN), Wi-Fi, Wibro, Wimax, HSDPA (High Speed Downlink Packet Access) or Ethernet, xDSL (ADSL, VDSL) , HFC (Hybrid Fiber Coaxial Cable), FTTC (Fiber to The Curb), FTTH (Fiber To The Home), etc. may be used. In addition, in addition to the above-described communication methods, all types of communication methods that are widely known or will be developed in the future may be included.

According to an embodiment, the user terminal 180 refers to a device capable of transmitting and receiving various information to and from the service server 100 over a network, and includes a cloud UI client, program, and protocol for transmitting and receiving information. It may include a memory (not shown) for storing, a processor (not shown) for executing a program, and the like. According to an embodiment, the user terminal 180 includes a communication module for communicating with the service server 100 or a media platform (not shown), an input module for receiving information from a user, and a service server 100 or a media platform. A display module for displaying the provided screen or content may be further included.

According to an embodiment, when the user terminal 180 is a set-top box of a smart TV, a user input input through a remote control may be received and transmitted to the service server 100 . The user terminal 180 may transmit a request to the service server 100 through a user input, and receive and reproduce streaming data from the service server 100 in response thereto. The user terminal 100 may receive and decode the encoded streaming data, and render and output the decoded data. The user terminal 100 may be implemented in various forms, for example, smart phone (smart phone), tablet (tablet), PDA (personal digital assistants), PMP (portable multimedia player), smart TV (smart tv) It may be a set-top box, desktop computer, laptop computer, or the like.

According to an embodiment, the processor 120 may request the browser 150 to execute a web app based on a request received from the user terminal 180, and the browser 150 may request the execution of a web app from the processor 120 ( web app) The web app can be executed according to the execution request. According to one embodiment, the browser 150 may render and parse data of a web application, for example, HTML-based web code, and the processor 120 may capture an image rendered by the browser 150 in real time ( capture), and encoding the captured image to provide it to the user terminal 180 in a streaming manner.

According to one embodiment, the service server 100 may include an access information database 130 that stores access information for each user terminal 180 . The access information database 130 is illustrated as being included in the service server 100 in FIG. 1 , but is not limited thereto and may be implemented to be included in a separate server from the service server 100 .

According to an embodiment, when receiving a web app execution request from the user terminal 180, the processor 120 may provide a screen to the user terminal 180 by referring to the access information database 130. . According to an embodiment, the access information database 130 includes user terminal information 132, information on web apps previously provided to the user terminal 134, and screens for final screens in each of the apps provided to the user terminal. Information (or ID) 136 and focusing information (or ID) 138 about the position of the pointer in the final screen may be included. Screen information 136 according to various embodiments will be described in detail with reference to FIGS. 3A and 3B.

According to an embodiment, the user terminal information 132, app information 134, screen information 136, and focusing information 138 may be interlocked and stored. That is, a list of web apps accessed previously for one user terminal may be mapped, final screen information for each web app may be mapped, and focusing information for each final screen may be mapped and stored.

For example, when a home app execution request is received from the user terminal 180, the processor 120 refers to the user terminal information 132 to determine app information 134 previously provided to the user terminal 180. If the home app has been previously provided to the user terminal 180, information 136 on the final screen (eg, the main screen of the home app) provided among the screens in the home app and the position of the pointer in the final screen (eg : The focusing information 138 for the coordinates of the arrow in the main screen of the home app) can be checked. Based on this, the processor 120 may request the browser 150 to execute the main screen of the home app, and may capture an image rendered in the browser 150 and provide the screen to the user terminal 180 .

By providing a screen based on access information according to various embodiments, a user can access a previously accessed screen more directly, and the service server 100 can reduce resources.

According to one embodiment, the processor 120 may capture and transmit only the changed area, not all of the rendered images of the web app executed in the browser 150. Specifically, the processor 120 may divide the previous screen and the current screen with respect to the image rendered by the browser 150 (for example, divide into 40 tiles), compare them, and transmit only the image of the changed area.

According to an embodiment, the processor 120 may operate differently according to the type of key input signal received from the user terminal 180 while providing a virtualized screen to the user terminal 180 . According to an embodiment, the type of key input signal may include a focusing movement signal within a currently provided web app, a request to execute a native app, and a request to execute another web app. The type of key input signal received from the user terminal 180 may be determined by the browser 150 . The service server 100 according to various embodiments may determine whether or not to maintain a session connection with a user terminal according to the type of a key input signal to provide a service considering a simultaneous access environment of multiple users. Types of key input signals according to various embodiments are described in detail with reference to FIGS. 4A and 4B.

According to an embodiment, when the key input signal is a focusing movement signal within the web app being provided, the processor 120 transmits a screen according to the focusing movement and establishes a session connection with the user terminal 180. can keep A flowchart in which a screen is provided when a key input signal is a focusing movement within a web app being provided according to various embodiments will be described in detail with reference to FIG. 5 .

According to an embodiment, when the key input signal is a native app execution request, the processor 120 stores access information corresponding to the user terminal 180 in the access information database 130, and the user A native app execution signal may be transmitted to the terminal, and a session connection with the user terminal 180 may be stopped. When the execution of the native app is terminated in the user terminal 180 and a session connection request is transmitted to the service server 100 again, the processor 120 connects the user terminal and the session, and provides access information corresponding to the user terminal 180. Based on this, a screen may be provided to the user terminal 180 . A flowchart of providing a screen when a key input signal is a native app execution request according to various embodiments will be described in detail with reference to FIG. 6 .

According to an embodiment, when the key input signal is an execution request for a web app different from the web app being provided, the processor 120 stores access information corresponding to the user terminal 180, Another web app execution signal may be transmitted to the user terminal, and a session connection with the user terminal 180 may be stopped. When a request to execute another web app is received from the user terminal 180 to the service server 100 again after the session connection is interrupted, the processor 120 connects the session with the user terminal and accesses the user terminal 180 A screen may be provided to the user terminal 180 based on the information. A flowchart of providing a screen when a key input signal is a request to execute another web app according to various embodiments will be described in detail with reference to FIG. 7 .

2 is a diagram for explaining an operation of connecting a session between a user terminal and a service server through a session server according to various embodiments.

Referring to FIG. 2 , the service server 100 described in FIG. 1 may be connected to a user terminal 180 through a session server 200 . According to an embodiment, the session server 200 may frequently or periodically update a policy related to a node of the service server 100, and may determine a service server based on the policy. According to an embodiment, when a server allocation request is received from the user terminal 180, the session server 200 selects a plurality of (eg, three) service servers 100 determined based on the policy, and The IP of the server 100 may be transmitted to the user terminal 180 . The user terminal 180 may request a session connection to one service server 100 among the plurality of service server 100 IPs received, and may receive a screen from the connected service server 100 in a streaming manner.

In other words, although the service servers 100 in FIG. 2 are shown to be connected to the session server 200 and the session server 200 is only connected to the user terminal 180, the user terminal 180 is connected to the session server ( When IPs of service servers are received from 200) and session connection is requested to one service server, the user terminal 180 and the corresponding service server can be connected.

According to an embodiment, each of the plurality of service servers 100 may include an access information database 130 for each user terminal or check access information through a separate server including the access information database 130. . According to an embodiment, access information may be commonly updated and managed among a plurality of service servers.

According to an embodiment, when the session connection between the user terminal 180 and the service server 100 is interrupted and then the session is reconnected, the IP of the service server provided by the session server 200 is changed to the previous service server according to the policy. may be different from the IP of, and the user terminal 180 may be connected to a service server that has not previously been connected. Even if a session is connected to a new service server that has not been previously connected, all service servers 100 can check access information for each user terminal that is commonly managed. As described in FIG. Based on this, a screen may be provided.

For example, when the type of key input signal received from the user terminal 180 is determined to be a native app execution request or a web app execution request other than the web app being provided, the processor 120 of the service server 100 Access information corresponding to the user terminal 180 is stored and session connection with the user terminal 180 is terminated. Even if the user terminal 180 requests server allocation again and receives the IP of a service server different from the previously connected service server from the session server 200, the other service server refers to the access information and displays the screen to the user terminal 180. can provide

Although the operation of the session server 200 may be omitted for concise description in the connection between the user terminal 180 and the service server 100 described below, when the user terminal 180 is connected to the service server again, the session server Based on the node policy of (200), a service server different from the existing service server may be connected.

3A and 3B are diagrams for explaining screen information included in an access information database according to various embodiments.

Referring to FIG. 3A , to explain the screen information 136 included in the access information database 130, the hierarchy between screens is shown. According to an embodiment, a web app execution request received from the user terminal 180 and executed through the browser 150 may have hierarchies between screens.

According to an embodiment, the first screen 330 may be provided by a user's input (eg, selection) from the initial screen 310 of the application to the next screen.

According to an embodiment, the initial screen 310 may be provided as a user input to return to the previous screen from the primary screen 330 (eg, input to a higher screen, back, to a previous screen, etc.), and to the next screen. A second screen may be provided by a user's input (eg, selection).

According to an embodiment, the first screen 330 may be provided as a user input (eg, an input to a higher screen, back, to a previous screen, etc.) to return to the previous screen from the second screen 350, and the initial screen The initial screen 310 may be provided as a user input (eg, input to the top screen, to the initial screen, to the beginning, etc.) to return to .

Referring to FIG. 3B , an initial screen, a first screen, and a second screen displayed through the user terminal 180 are illustrated. According to an embodiment, when a home app execution request (eg, a home app execution request through a remote control) is received from the user terminal 180 (eg, a set-top box of a smart TV), the service server 100 The processor 120 of may provide the initial screen 360 to the user terminal 180 . According to an embodiment, when a user input for the movie tab 365 is received on the initial screen 360, the processor 120 may provide the first screen 370 to the user terminal 180. According to an embodiment, when a user input for a specific movie content 375 is received on the primary screen 370, the processor 120 may provide the secondary screen 380 to the user terminal 180. .

According to an embodiment, although the first screen and the second screen are illustrated in FIGS. 3A and 3B , more hierarchical screens may exist without being limited thereto. The screen information 136 included in the access information database 130 may include identification information for screens of each layer (310, 330, 350 in FIG. 3A or 360, 370, and 380 in FIG. 3B), and specifically In the access information database 130 , information on a web app previously accessed for each user terminal 180 and identification information on a final screen within the app may be mapped and stored.

4A and 4B are diagrams for explaining types of key input signals according to various embodiments.

Referring to FIGS. 4A and 4B , a screen of a web app executed in the service server 100 through the browser 150 and rendered and provided to the user terminal 180 is shown. According to an embodiment, as described in FIG. 1, the processor 120 receives a key input signal from the user terminal 180 while providing the screen as shown in FIGS. 4A and 4B to the user terminal 180 in a streaming manner, and browser 150 may determine the type of key input signal.

According to an embodiment, the received key input signal may be a focusing movement signal of the pointer 410 within the web app being provided. For example, when the user terminal 180 is a set-top box of a smart TV, upon receiving a direction key input from a remote control, the browser 150 may determine the type of the key input signal as a focusing movement signal. Referring to FIG. 4A , the browser 150 may move the focus of the pointer 410 within the screen according to a direction key input based on a reference point (eg, the upper left corner of the screen) within the screen of the web app being provided.

According to an embodiment, the received key input signal may be an execution request for a web app other than the web app being provided. For example, when the user terminal 180 is a set-top box of a smart TV, the browser 150 receives a shortcut button input for a kids app through a remote control while providing a home app screen, or the initial home app as shown in FIG. 4a. When an input through the pointer 410 (for example, an 'OK' button input) is received at the kids app execution position 430 on the screen, the type of key input signal is provided to the home app, which is a web app, and the other web app, that is, the kids app. It can be decided that it is an execution request for

According to an embodiment, the received key input signal may be an execution request for a native app. According to an embodiment, as described in FIG. 1 , a VOD player, which is a native app, may be executed in the user terminal 180 based on content information transmitted from the service server 100 . For example, referring to FIG. 4B , when the user terminal 180 is a set-top box of a smart TV, the browser 150 inputs through a pointer at the position of the play movie button 450 (eg, inputting the 'confirm' button). When this is received, the type of key input signal is determined as a native app execution request, and the processor 120 may receive content information from the media platform and transmit the corresponding content information and the VOD player execution request to the user terminal 180 . In the user terminal 180, a VOD player, which is a native app, may be executed based on corresponding content information.

5 is a flowchart illustrating a method of providing a screen when a key input signal is a focusing movement signal according to various embodiments of the present disclosure.

As described with reference to FIG. 2 , an operation in which the user terminal 180 is connected to the service server 100 through the session server 200 is described at reference number 510 . The user terminal 180 may request allocation of a service server to the session server 200 (515), and the session server 200 selects a plurality of (eg, three) service servers based on a node policy. 520) to transmit the IP of the server to the user terminal 180 (525).

Referring to FIG. 5 , an operation of transmitting an image from the service server 100 to the user terminal 180 in a streaming manner as described in FIG. 1 with reference to reference numerals 530 to 570 will be described.

According to an embodiment, the user terminal 180 may request execution of a web app to the service server 100 based on the received IP of the service server (530). The processor 120 of the service server 100 checks access information corresponding to the user terminal 180 (535), and requests the browser 150 to execute the web app based on the received web app execution request and access information. can (540).

For example, the user terminal 180 previously selects a movie tab (eg, reference number 365 in FIG. 3B) on the initial screen (eg, reference number 360 of FIG. 3B) of the home app to view the home app. Session connection may be interrupted while being provided to the first screen (eg, reference numeral 370 in FIG. 3B). When receiving a home app execution request from the user terminal 180 at reference number 530, the processor 120 may check access information at reference number 535 based on the information on the user terminal 180 and the home app. there is. As described in FIG. 1 in relation to the access information database 130, the processor 120 is a user terminal based on the terminal information 132, the app information 134, the screen information 136, and the focusing information 138 ( 180), the browser 150 may be requested to execute the first screen (eg, reference numeral 370 in FIG. 3B), which is the final screen of the home app that has been previously provided.

As described for the operation of the session server 200 in FIG. 2, the IP of the service server 100 receiving the execution request at reference number 530 may be different from the service server to which the user terminal 180 was previously connected. Since the access information database 130 is commonly managed among a plurality of service servers, a newly connected service server can access access information stored in a previously connected service server.

According to an embodiment, the browser 150 may execute a web app based on the access information and render an image (550), and the processor 120 may capture a result rendered by the browser 150 (560) An image may be transmitted to the user terminal 180 (570). As described in FIG. 1, the processor 120 compares the image rendered by the browser 150 by dividing the previous screen and the current screen (for example, into 40 tiles), and transmits only the image of the changed area. can By providing a screen based on access information according to various embodiments, a user can access a previous access screen more directly, and the service server 100 can reduce resources.

According to an embodiment, a key input signal may be received from the user terminal 180 while providing a screen 570 from the service server 100 to the user terminal 180 . Reference numerals 575 and 585 in FIG. 5 indicate a case in which a key input signal is a focusing movement within a web app being provided, in FIG. 6 a case in which a key input signal is a request to execute a native app, and in FIG. It is a flow chart in the case of

According to an embodiment, an in-app focusing movement signal may be received from the user terminal 180 (575). As described in FIG. 4A, when the user terminal 180 is a set-top box of a smart TV and receives a direction key input through a remote control, the browser 150 determines that the received key input signal is a focusing movement signal within the web app screen being provided. can Although omitted for brevity in FIG. 5 , the browser 150 renders the screen according to the focusing movement, and the processor 120 compares it with the previous screen and provides only the image of the changed area to the user terminal 180. (585).

6 is a flowchart illustrating a method of providing a screen when a key input signal is a request to execute a native app, according to various embodiments.

Referring to FIG. 6 , while a screen is provided from the service server 100 to the user terminal 180 as described in FIG. 5 , a request to execute a native app (eg, a VOD player) may be received from the user terminal 180 ( 615). For example, as described in FIG. 4B, the user terminal 180 is a set-top box of a smart TV, and an input through a pointer (eg, an 'OK' button) at a location of a movie play button (eg, reference numeral 450 in FIG. 4B) input) is received, the browser 150 may determine the type of the received key input signal as a native app execution request. Although omitted for brevity in FIG. 6 , the key input signal is received ( 615 ) and the browser 150 may determine that the key input signal is a native app execution request.

According to an embodiment, when the received key input signal is a native app execution request, the processor 120 may store access information of the user terminal 180 (620). According to an embodiment, when the native app execution request 615 is a content playback request through the home app screen as described in the second screen 380 of FIG. 3B and FIG. 180) may be stored in association with the access information database 130. For example, the processor 120 transmits terminal identification information of the user terminal 180 to terminal information 132 and information about a home app, which is a web app that has been provided to the user terminal 180, to app information 134 and the corresponding home screen. Screen identification information indicating that the screen provided within the app is a secondary screen (eg, the secondary screen 380 in FIG. ) can be stored in conjunction with.

According to an embodiment, the processor 120 stores access information on the user terminal 180 (620), transmits a native app execution signal to the user terminal 180 (625), and then the user terminal 180 A session connection with may be terminated (630). When the processor 120 transmits the native app execution signal (625), the corresponding content information may be transmitted together with the user terminal 180, and the processor 120 may terminate the session connection with the user terminal (630). . According to an embodiment, content information may be transmitted from an external media platform as described in FIG. 1 .

According to an embodiment, the user terminal 180 may execute a native app based on the received signal (635). For example, when the user terminal 180 requests (615) the execution of a VOD player to play content such as a movie, the user terminal 180 receives (625) a VOD player execution signal together with corresponding content information and Based on the information, a VOD player, which is a native app, may be executed (635).

Since the service server 100 stops (630) the session connection with the user terminal 180 after transmitting the native app execution signal (625), while the native app is running (635) on the user terminal 180, the service server 100 may provide a session occupied by the user terminal 180 to a plurality of concurrently connected users. As described in FIG. 1, since the native app is an application running on a user terminal and does not need to be connected to the service server 100, the service server 100 is more than a case where the session is uniformly connected to the user terminal 180. Since resources can be allocated dynamically, an efficient multi-simultaneous access environment can be provided.

According to an embodiment, when the execution of the native app 635 in the user terminal 180 is terminated, the user terminal may request session connection again to the service server 100 (660). In this case, the operation of the session server 200 at reference number 640 may connect to a service server having an IP different from that of the existing service server. A description of the operation of the session server 200 and connection to other service servers is duplicated with that described at reference numeral 510 in FIGS. 2 and 5 , so detailed descriptions are omitted.

According to an embodiment, a session connection request is received from the user terminal 180 (660), and the processor 120 checks (665) access information to refer to information stored in (620) the access information in the previous service server. The final screen of the web app previously provided to the user terminal 180 may be transmitted based on this (670).

For example, in reference number 670, based on the access information stored in reference number 620, a second screen in the home app provided to the user terminal 180 prior to the execution request 615 of a native app (eg, a VOD player) (eg, : The secondary screen 380 of FIG. 3B) may be provided to the user terminal 180. According to an embodiment, since the coordinates of the pointer within the screen are also stored in the focusing information, the location of the pointer can also be transmitted identically to that of the previous access screen.

7 is a flowchart illustrating a method of providing a screen when a key input signal is a request to execute another web app according to various embodiments.

Referring to FIG. 7 , while the service server 100 is providing a web app (eg, home app) screen from the service server 100 to the user terminal 180, another web app (eg, kids app) is provided from the user terminal 180. ) execution request may be received (715). For example, as described with reference to FIG. 4A , the user terminal 180 is a set-top box of a smart TV and an input through a pointer (eg, 'confirm' at the Kids App execution location (eg, reference number 430 in FIG. 4A) button input) or Kids App shortcut button input on the remote controller is received, the browser 150 may determine the type of the received key input signal as an execution request for another web app, Kids App. Although omitted for brevity in FIG. 7 , the key input signal is received (715) and the browser 150 may determine that the key input signal is another web app execution request.

According to an embodiment, when the received key input signal is another web app execution request, the processor 120 may store access information of the user terminal 180 (720). According to one embodiment, when the other web app execution request 715 is a request to execute the kids app through the initial screen of the home app as described in FIG. It can be stored in the access information database 130. For example, the processor 120 transmits terminal identification information of the user terminal 180 to terminal information 132 and information about a home app, which is a web app that has been provided to the user terminal 180, to app information 134 and the corresponding home screen. Screen identification information indicating that the screen provided within the app is the initial screen (e.g., initial screen 360 in FIG. 3B) is linked to screen information 136, and the location of the pointer within the initial screen is linked to focusing information 138. and can be saved.

According to an embodiment, the processor 120 stores access information on the user terminal 180 (720), transmits another web app execution signal to the user terminal 180 (725), and then returns the user terminal 180 The connection with the session may be terminated (730).

According to an embodiment, the user terminal 180 may request execution of another web app again based on the received signal (760). For example, when the user terminal 180 receives a signal to execute the kids app (725), the service server 100 may be requested to run the kids app again (760).

When the service server 100 receives another web app execution request from the user terminal 180 (715), the session connection with the user terminal is terminated (730), and the corresponding other web app execution request is again sent from the user terminal 180. The reason for receiving is that only one web app can be executed at a time in the browser 150 that executes the web app of the service server 100 . Further, according to an embodiment, the service server 100 stops the session with the user terminal 180 (730) and receives another web execution request again, thereby preventing the same user terminal 180 from using multiple sessions. By doing so, resources can be saved, and a multi-simultaneous access environment for more people can be provided.

According to an embodiment, when the user terminal 180 requests the service server 100 to run another web app, the session server 200 operates at reference number 740 to connect to a service server having an IP different from that of the existing service server. can A description of the operation of the session server 200 and connection to other service servers is duplicated with that described at reference numeral 510 in FIGS. 2 and 5 , so detailed descriptions are omitted.

According to an embodiment, another web app execution request is received from the user terminal 180 (760), and the processor 120 checks the access information (765) to refer to information that stored the access information in the previous service server. and, based on this, the final screen of the corresponding other web app previously provided to the user terminal 180 may be transmitted (770).

For example, in reference number 770, the user terminal 180 previously accessed the Kids App, but the session connection was interrupted, and based on the stored access information, the final screen of the Kids App previously accessed by the user terminal 180. and the location of the pointer may be provided.

<How to operate the service server>

8 to 11 are flowcharts for explaining an operation method of a service server according to various embodiments, and are diagrams for explaining the screen providing method described in FIGS. 1 to 7 from the side of the service server. The operating method is described centering on the service server, but parts overlapping those described in FIGS. 1 to 7 are omitted for concise description.

8 is a flowchart illustrating a method of determining whether a service server maintains a session connection with a user terminal according to various embodiments.

Operations 810 to 850 may be performed by the processor 120 of the service server 100 described above with reference to FIG. 1 .

Referring to FIG. 8 , in operation 810, the processor 120 receives a web app execution request from the user terminal 180, and in operation 820, the user terminal based on the execution request and access information corresponding to the user terminal 180. screen can be provided. Before operation 810, the user terminal receives the IP of the service server through the session server 200 as described in reference numeral 510 of FIG. 5 and requests a session connection to the service server 100 to be connected to the service server 100. can

According to one embodiment, as described in reference numerals 530 to 570 of FIG. 5, in operation 820, the processor 120 refers to the access information database 130 for the web app requested to be executed from the user terminal 180, The user terminal 180 may provide the previously provided final screen to the user terminal 180 . According to one embodiment, the service server 100 executes a web app based on the access information in the browser 150, renders an image, and the processor 120 divides the previous screen and the current screen for the rendering result ( For example, 40 tiles may be divided into 40 tiles) for comparison, and only the image of the changed area may be transmitted. By providing a screen based on the access information in operation 820, the user can more directly access a previously accessed screen, and the service server 100 can reduce resources.

According to an embodiment, in operation 830, the processor 120 may receive a key input signal from the user terminal and determine the type of the key input signal in operation 840. According to an embodiment, the type of key input signal may include a focusing movement signal within a currently provided web app, a native app execution request, and another web app execution request, and as described in FIGS. 4A and 4B , the service server 100 The type of key input signal may be determined by the browser 150 of ).

According to an embodiment, in operation 850, the processor 120 may transmit information corresponding to the type of the key input signal to the user terminal 180 and determine whether to maintain a session with the user terminal 180.

According to various embodiments, whether to maintain the session connection may be changed in operation 850 according to the type of the key input signal determined in operation 840, and other operations may be further included when the session connection is stopped. 9 to 11, operations according to the type of key input signals are described in detail.

9 is a flowchart illustrating an operation method of a service server when a key input signal is a focusing movement signal according to various embodiments.

Operations 910 to 940 may be performed by the processor 120 of the service server 100 described above with reference to FIG. 1 . According to an embodiment, operations 910 to 940 transmit information corresponding to the type of key input signal described with reference to FIG. 8 and determine whether to maintain a session connection with a user terminal (eg, operation 850 of FIG. 8 ) can respond to

Referring to FIG. 9 , when the key input signal determined in operation 840 is a focusing movement signal within the web app being provided, the browser 150 may render the web app image after the focusing movement in operation 910 . According to an embodiment, in operation 920, the processor 120 may capture a region changed from a previous screen among the rendered images, and may provide the image captured in operation 930 to the user terminal 180. Specifically, as described in reference numerals 550 to 570 of FIG. 5 , the previous screen and the current screen may be divided and compared, and only images of the changed area may be transmitted.

According to an embodiment, in operation 940, the processor 120 may determine to maintain a session connection with the user terminal 180 and continuously provide a screen to the user terminal 180.

10 is a flowchart illustrating a method of operating a service server when a key input signal is a native app execution request according to various embodiments.

Operations 1010 to 1060 may be performed by the processor 120 of the service server 100 described above with reference to FIG. 1 . According to an embodiment, operations 1010 to 1030 transmit information corresponding to the type of key input signal described with reference to FIG. 8 and determine whether to maintain a session connection with a user terminal (eg, operation 850 of FIG. 8 ) can respond to

Referring to FIG. 10 , when the key input signal determined in operation 840 is a native app execution request, in operation 1010, the processor 120 may store access information corresponding to the user terminal 180 in the access information database 130.

According to an embodiment, in operation 1020, the processor 120 may transmit a native app execution signal to the user terminal 180. According to one embodiment, when the native app execution request is a VOD player execution request, as described at reference number 625 of FIG. 6 , the processor 120 transmits the content information received from the external media platform in operation 1020 to the VOD player execution signal and It can be transmitted to the user terminal 180 together.

According to an embodiment, in operation 1030, the processor 120 may terminate the session connection with the user terminal 180.

According to an embodiment, in operation 1040, the processor 120 may receive a session connection request from the user terminal 180 in which execution of the native app is terminated, and in operation 1050 may connect the session with the user terminal 180 again. As described in reference numeral 640 of FIG. 6 and reference numeral 510 of FIG. 5 , the service server receiving the connection request in operation 1040 may be different from the service server performing the previous operation, but for the sake of simplicity, the service server is the same. explain the case.

According to an embodiment, in operation 1060, the processor 120 of the service server 100 connected again refers to the access information database 130 and establishes a session connection in operation 1030 based on the access information of the user terminal stored in operation 1010. A screen before interruption may be provided to the user terminal 180 .

For example, in the case of the user terminal 180 requesting execution of a VOD player, which is a native app, while the home app is running, based on the access information stored in operation 1010, within the home app provided to the user terminal 180 prior to the VOD player execution request. A secondary screen (eg, the secondary screen 380 of FIG. 3B) may be provided. According to an embodiment, since the coordinates of the pointer in the screen are also stored in the focusing information 138, the position of the pointer can be provided the same as that of the previous access screen.

11 is a flowchart illustrating an operation method of a service server when a key input signal is a request to execute another web app according to various embodiments.

Operations 1110 to 1160 may be performed by the processor 120 of the service server 100 described above with reference to FIG. 1 . According to an embodiment, operations 1110 to 1130 transmit information corresponding to the type of key input signal described with reference to FIG. 8 and determine whether to maintain a session connection with a user terminal (eg, operation 850 of FIG. 8 ) can respond to

Referring to FIG. 11 , when the key input signal determined in operation 840 is a web app execution request different from the web app being provided, in operation 1110, the processor 120 transfers access information corresponding to the user terminal 180 to the access information database 130. ) can be stored.

According to an embodiment, in operation 1120, the processor 120 may transmit another web app execution signal to the user terminal 180, and in operation 1130, the session connection with the user terminal 180 may be terminated.

According to an embodiment, in operation 1140, the processor 120 receives another web app execution request from the user terminal 180, and connects a session with the user terminal 180 in operation 1150. As described by reference numeral 740 in FIG. 7 and reference numeral 510 in FIG. 5 , the service server receiving the connection request in operation 1140 may be different from the service server performing the previous operation, but for the sake of brevity, the service server is the same. explain the case.

According to an embodiment, in operation 1160, the processor 120 of the service server 100 connected again refers to the access information database 130 and based on the access information of the user terminal, the corresponding service server 180 previously provided to the user terminal 180. You can provide end screens for other web apps.

For example, in the case of the user terminal 180 requesting the execution of another web app, the Kids App, while the Home App is running, in operation 1160, the session connection was interrupted after previously accessing the Kids App, and the previous access was made based on the stored access information. The final screen of the previously used Kids App and the location of the pointer can be provided.

The embodiments described above may be implemented as hardware components, software components, and/or a combination of hardware components and software components. For example, the devices, methods and components described in the embodiments may include, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate (FPGA). array), programmable logic units (PLUs), microprocessors, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and software applications running on the operating system. A processing device may also access, store, manipulate, process, and generate data in response to execution of software. For convenience of understanding, there are cases in which one processing device is used, but those skilled in the art will understand 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 can include. For example, a processing device may include a plurality of processors or a processor and a controller. Other processing configurations are also possible, such as parallel processors.

Software may include a computer program, code, instructions, or a combination of one or more of the foregoing, which configures a processing device to operate as desired or processes independently or collectively. The device can be commanded. Software and/or data may be any tangible machine, component, physical device, virtual equipment, computer storage medium or device, intended to be interpreted by or provide instructions or data to a processing device. , or may be permanently or temporarily embodied in a transmitted signal wave. Software may be distributed on networked computer systems and stored or executed in a distributed manner. Software and data may be stored on computer readable media.

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer readable medium. The computer readable medium may include program instructions, data files, data structures, etc. alone or in combination, and the program instructions recorded on the medium may be specially designed and configured for the embodiment or may be known and usable to those skilled in the art of computer software. may be Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks and magnetic tapes, optical media such as CD-ROMs and DVDs, and magnetic media such as floptical disks. - includes hardware devices specially configured to store and execute program instructions, such as magneto-optical media, and ROM, RAM, flash memory, and the like. Examples of program instructions include high-level language codes that can be executed by a computer using an interpreter, as well as machine language codes such as those produced by a compiler.

The hardware device described above may be configured to operate as one or a plurality of software modules to perform the operations of the embodiments, and vice versa.

As described above, although the embodiments have been described with limited drawings, those skilled in the art can apply various technical modifications and variations based on this. For example, the described techniques may be performed in an order different from the method described, and/or the components of the described system, structure, device, circuit, etc. may be combined or combined in a different form than the method described, or other components may be used. Or even if it is replaced or substituted by equivalents, appropriate results can be achieved.

Therefore, other implementations, other embodiments, and equivalents of the claims are within the scope of the following claims.

Claims (17)

a database for storing access information for each user terminal;
a browser that determines the type of key input signal received from the user terminal and executes a web app; and
contains a processor;
the processor,
Receiving an execution request of a web app from the user terminal;
providing a final screen of the web app provided before session connection is interrupted to the user terminal based on the access information corresponding to the user terminal with reference to the user terminal information included in the execution request; and
While providing the screen to the user terminal, information corresponding to the type of key input signal received from the user terminal is transmitted to the user terminal, and a session connection with the user terminal is established based on the type of the key input signal. action to decide whether to keep
to do,
service server.
According to claim 1,
the processor,
When the key input signal is a focusing movement signal within the web app,
An operation of transmitting a screen according to the focusing movement to the user terminal and maintaining a session connection with the user terminal
to do,
service server.
According to claim 1,
the processor,
When the key input signal is a native app execution request,
storing access information corresponding to the user terminal; and
Transmitting the native app execution signal to the user terminal and stopping the session connection with the user terminal
to do,
service server.
According to claim 3,
the processor,
When the execution of the native app is terminated in the user terminal and a session connection request is received from the user terminal,
connecting a session with the user terminal; and
Providing a screen to the user terminal based on the access information corresponding to the user terminal
to do more,
service server.
According to claim 1,
the processor,
When the key input signal is a request to execute a web app different from the web app,
storing access information corresponding to the user terminal; and
Transmitting an execution signal for the other web app to the user terminal and stopping the session connection with the user terminal
to do,
service server.
According to claim 5,
the processor,
When receiving the other web app execution request from the user terminal,
connecting a session with the user terminal; and
Providing a screen to the user terminal based on the execution request and the access information corresponding to the user terminal
to do more,
service server.
According to claim 1,
The access information,
Includes user terminal information, information about web apps previously provided to the user terminal, screen information about the final screen of each app provided to the user terminal, and focusing information about the position of the pointer in the final screen do,
The screen information is identification information for any one of an initial screen, a first screen according to an input on the initial screen, and a second screen according to an input on the first screen,
service server.
According to claim 1,
the processor,
Of the rendered images of the web app executed in the browser, capturing an image of a region changed from a previous screen and providing the screen to the user terminal,
service server.
Receiving an execution request of a web app from a user terminal;
providing a final screen of the web app provided before session connection is interrupted to the user terminal based on access information corresponding to the user terminal with reference to the user terminal information included in the execution request; and
While providing the screen to the user terminal, information corresponding to the type of key input signal received from the user terminal is transmitted to the user terminal, and a session connection with the user terminal is established based on the type of the key input signal. action to decide whether to keep
including,
How the service server works.
According to claim 9,
When the key input signal is a focusing movement signal within the web app,
An operation of transmitting a screen according to the focusing movement to the user terminal and maintaining a session connection with the user terminal
including,
How the service server works.
According to claim 9,
When the key input signal is a native app execution request,
storing access information corresponding to the user terminal; and
Transmitting the native app execution signal to the user terminal and stopping the session connection with the user terminal
including,
How the service server works.
According to claim 11,
When the execution of the native app is terminated in the user terminal and a session connection request is received from the user terminal,
connecting a session with the user terminal; and
Providing a screen to the user terminal based on access information corresponding to the user terminal
Including more,
How the service server works.
According to claim 9,
When the key input signal is a request to execute a web app different from the web app,
storing access information corresponding to the user terminal; and
Transmitting an execution signal for the other web app to the user terminal and stopping the session connection with the user terminal
including,
How the service server works.
According to claim 13,
When receiving the other web app execution request from the user terminal,
connecting a session with the user terminal; and
Providing a screen to the user terminal based on the execution request and access information corresponding to the user terminal
Including more,
How the service server works.
According to claim 9,
The access information,
Includes user terminal information, information about web apps previously provided to the user terminal, screen information about the final screen of each app provided to the user terminal, and focusing information about the position of the pointer in the final screen do,
The screen information is identification information for any one of an initial screen, a first screen according to an input on the initial screen, and a second screen according to an input on the first screen,
How the service server works.
According to claim 9,
The operation of providing a screen to the user terminal based on the execution request and the access information corresponding to the user terminal,
An operation of capturing an image of a region changed from a previous screen among rendered images of the web app executed in a browser and providing the screen to the user terminal.
including,
How the service server works.
A computer program stored in a computer readable recording medium in order to execute the method of any one of claims 9 to 16 in combination with hardware.

Images