KR20140017715A - Method and apparatus for web service supporting movability of web object - Google Patents

Abstract

A method and apparatus for a web service supporting the movability of a web object are provided. A web server creates movability information for a movable web object in a webpage in order to process the movement of the web object. The web server inserts a link indicative of the movability information into a header of the webpage and transmits the webpage with the link inserted thereinto to a primary device. The primary device obtains the movability information for the web object from the web server using the link. [Reference numerals] (1710) Load web page; (1715) Generate mobility information; (1720) Insert a link; (1725) Webpage; (1730) Request an object; (1735) Object; (1740) Confirm the mobility Information of the object; (1745) Obtain primary device information; (1750) Request the registration of the information; (1760) Information of a secondary device and information of capability thereof; (1765) Register the secondary device and the capability thereof; (1770) Information of the capability; (1775) Request web object movement information; (1780) Generate the web object movement information; (1785) Web object movement information; (1790) Web object-related data; (1795) Update the web object; (310) Web server; (320) Primary device; (350) Secondary device

Description

[0001] METHOD AND APPARATUS FOR WEB SERVICE SUPPORTING MOVABILITY OF WEB OBJECT [0002]

The following embodiments relate to a method, apparatus and system for providing a web service, and more particularly, to a web service method and apparatus for supporting the mobility of a web object.

A web object refers to an object that can be accessed via the Web. A web service can provide one or more web objects. A user of a web service can receive a web service by accessing a web object provided through a web browser installed on his device.

[0003] As various devices capable of web browsing such as a personal computer (PC), a smart phone, a tablet and a smart television (TV) are popularized, Can be provided. A user may be provided with a plurality of screens associated with a web service through a plurality of devices using an N-screen service. At this time, a plurality of screens can display contents related to each other.

When a user is provided with a web service through a plurality of devices, the screen of the web browser of one device can be named as the primary screen, and the screen of the web browser of the other device can be named as the second screen . In addition, among the plurality of devices, a device that outputs a main screen may be referred to as a main device, and a device that outputs a secondary screen may be referred to as an auxiliary device.

For the provision of web services, interworking between the main screen and the secondary screen may be required. That is to say, the information displayed on the main screen and the information displayed on the secondary screen can be correlated. Here, the information may include web objects, and contents such as images, moving pictures, voice, and music represented through web objects. For example, the main screen output by the main device may display the content, and the secondary screen output by the auxiliary device may output the metadata of the content, such as title, genre, and cast.

A provider of a web service can build a web service that provides the user with associated information through multiple devices. For example, when the main device outputting the main screen is connected to the web server and the service is provided, the auxiliary device outputting the secondary screen may also be connected to the web server, and the information associated with the service provided to the main device Can be provided from a web server of

One embodiment may provide a web service method and apparatus supporting mobility of a web object.

One embodiment may provide a method and apparatus for inserting mobility information for a movable web object in a web page into a header of the web page.

According to one aspect, there is provided a method for a web server to handle movement of a web object, the method comprising: generating mobility information for a movable web object in the web page; inserting a link pointing to the mobility information into a header of the web page And transferring the web page to the main device, wherein the web server provides movement of the web object.

The mobility information may include an intent tag.

The mobility information may be generated as a script file.

The link may point to the script file in the web server.

The method for providing the movement of the web object by the web server may further include receiving a request of the entity in the web server indicated by the link from the main device and transmitting the entity to the main device .

The method for providing the movement of the web object by the web server may further include registering information on the main device transmitted from the main device.

The information on the main device may include at least one of an identifier of a web service provided by the web server and an internet protocol address of the main device.

The method for providing web server movement of a web object comprises receiving information of a secondary device and information of the capabilities of the secondary device, based on information of the secondary device and capability of the secondary device Registering capabilities of the secondary device and the secondary device, and transmitting information of the capabilities of each of the registered devices to the primary device.

The main device and the secondary device may be N-screen devices of a web service providing the web page.

A method for providing web object movement comprises receiving a request for information to move the web object from a secondary device, generating information for moving the web object, And transferring the information for moving to the secondary device.

The method for providing web server movement of the web server may further include receiving data related to the web object from a secondary device and updating the web page based on data associated with the web object have.

The method for providing the movement of the web object by the web server may further include transmitting the updated web page to the main device.

According to another aspect, there is provided a recording medium providing a method for a web server to process a movement of a web object, the recording medium comprising code for generating mobility information for a movable web object in the web page, A recording medium readable in an electronic device in which a program including a code for inserting code into a header of a page and a code for transmitting the web page to a main device can be provided.

According to another aspect of the present invention, there is provided a method for a web server for processing a movement of a web object, the method comprising: generating mobility information for a movable web object in a web page; inserting a link pointing to the mobility information into a header of the web page; And a transmission / reception unit for transmitting the web page to the main device.

A web service method and apparatus supporting mobility of a web object are provided.

There is provided a method and apparatus for inserting mobility information for a movable web object in a web page into a header of the web page.

Figure 1 illustrates an intent according to an example.
2 illustrates a web intent according to an example.
FIG. 3 illustrates a system that supports mobility of a web object according to one embodiment and uses a moved web object.
4 is a block diagram of a web server according to one embodiment.
5 is a block diagram of a main device according to one embodiment.
6 is a block diagram of a secondary device in accordance with one embodiment.
7 is a signal flow diagram of a method by which a primary device moves a web object according to one embodiment.
8 is a signal flow diagram of a method of processing a web object in which a secondary device according to an embodiment moves to a secondary device.
9 shows a screen displaying a plurality of connectable secondary devices according to an example.
10 is a flowchart illustrating a method for selecting a secondary device to transmit a web object among a plurality of connectable secondary devices according to an exemplary embodiment.
FIG. 11 shows a screen for selecting a web object to be moved among a plurality of web objects according to an example.
12 is a flowchart illustrating a method for selecting a web object to be transmitted to a secondary device among a plurality of web objects according to an exemplary embodiment.
FIG. 13 shows a screen for receiving a user's approval for a request for movement of a web object according to an example.
14 shows a screen for manipulating a web object moved to a secondary device according to an example.
15 illustrates a rendered web page after moving a web object according to an embodiment.
16 is a flowchart of a method of rendering a web page after moving a web object according to an example according to an embodiment.
17 is a flow diagram of a method by which a web server in accordance with one embodiment processes movement of a web object.
18 shows a code used for invoking an intent according to an example.
19 shows a code used for registering an intent according to an example.
20 is a page showing information of a main device according to an example.
21 is a flow diagram of a method for discovering a secondary device according to an example.
22 is a page showing the capabilities of the secondary device according to an example.
23 is a block diagram of a push server according to an embodiment.
24 is a signal flow diagram of a method in which a primary device moves a web object using a push server in one embodiment.

In the following, embodiments will be described in detail with reference to the accompanying drawings. Like reference symbols in the drawings denote like elements.

Hereinafter, the terms "Uniform Resource Locator (URL)" and "Uniform Resource Identifier (URI)" may be used interchangeably and may be interchanged.

In the following, "request" may mean a message indicating a request. The "response" may mean a message indicating a response to the request. "Web page" may mean data of a web page.

In the following, "script" may include any script used within a web page, such as a Java (JAVA) script.

Hereinafter, the "web object" may be an object representing the contents of the web service.

The secondary screen can be utilized through the movement of web objects. Movement of the web object may mean moving the web object accessed via the main screen of the main device to be accessible via the secondary screen of the auxiliary device.

In utilizing the secondary screen, the following problems need to be examined.

First, a web service that can be accessed or controlled through a secondary screen of the web services that can be provided to the user must be identifiable by the user. If there is a web service that can be accessed or controlled via the secondary screen, the connected secondary screen must be identifiable. That is, an auxiliary device capable of providing a secondary screen connected to a web server providing the web service can be identified by the user, or a list of auxiliary devices can be provided to the user.

In addition, a web object that can operate on the secondary screen of the web objects of the web service that can be accessed or controlled on the secondary screen must be identifiable by the user. Here, the web object that can operate may be determined according to the type, characteristics and specifications of the secondary screen or the auxiliary device connected to the web server.

In addition, a method for moving a web object operating on the main screen to a secondary screen desired by the user should be provided. When the web object is moved, a method of receiving a request for movement of the web object and a request for movement of the web object to the user should be provided by the auxiliary device providing the secondary screen.

In the following, embodiments related to supporting the mobility of a web object are described.

Figure 1 illustrates an intent according to an example.

In order for a single application or a component of an application to invoke another application or a component of an application, information about the application or component needs to be registered in the operating system, system, or platform.

An intent registers an application or component to be invoked with an operating system (OS), a system or a platform and allows the registered application or component in a specific situation to be used through invocation Quot; service " or " service " An intent may also refer to an object used for such a service.

In Fig. 1, applications or components registered in a mobile terminal platform for use as an intent are enumerated. "Google Buzz", "Google+", and "Mail" are names of registered applications or components, respectively.

An intent may be used for calling between applications or components or for returning the result value for the above call.

An intent may include information for invoking an application or a component. The above information may include the name of the application or component to be invoked and may include properties of the application or component being invoked. The intent may also include information for communicating the results of the called application or component to the application or component that called it.

2 illustrates a web intent according to an example.

A Web Intent can refer to an Intent that extends to a Web or Web Services environment. The Web Intent can be a Frame Week for interworking between Web-based applications and discovering available Web services.

The web intent can provide a connection to the registered web service in the web browsing environment. That is to say, a web intent can provide a connection between an event of a web page and a registered web service. The web intent allows a web service associated with the specific event to react when a specific event occurs.

In Figure 2, registered web services for use by a Web Intent are enumerated. "Delicious "," Twitter ", "Blinklist ", and" Digg " Under the name, a description of the web service is displayed.

A web action may be an action to another web site or application taken by a visitor to a visited web site or web application. For example, an example of a web action is to click on the "twitter" button below an article on a blog to view the article on the Twitter service. It can be shared. Here, the web site providing the blog may be the visited web site. Also, the web site providing the Twitter service may be the other web site.

You can remove, disable, or enable an action for a web service using the "remove", "disable" and "enable" buttons under the description of the web service .

Web intents enable rich integration between web applications. Services available on the web need to exchange rich data to perform their jobs.

A web page providing a web intent can be named a service page. The page that invites and uses the web intent can be named a client page.

In the following, a web intent can be outlined as an intent. The terms "web intent" and "intent" may be used interchangeably.

FIG. 3 illustrates a system that supports mobility of a web object according to one embodiment and uses a moved web object.

The system 300 supporting the mobility of the web object includes a web server 310, a main device 320, a mobility registration server 330, a notification server 340, and a secondary device 350).

Web server 310 may be requested web content from main device 320 and secondary device 350, respectively. The web content may be a web page of the web service. Alternatively, the web page may include web content. Web server 310 may provide web pages to main device 320 and secondary device 350, respectively. A web page may include web content.

The main device 320 may provide a main screen. The main device 320 may be a device on which the web service provided by the web server 310 is first executed. The primary device 320 may register the web intent described above and may move the web object to the secondary device 350 by calling the web intent. Thus, the primary device 320 may be referred to as a web intent device.

The main device 320 may register the mobility information of the web object in the web page to the mobility registration server 330. [ After the web browser of the main device 320 loads the web page, it may determine whether the web page supports the mobility or intent of the web object. The web browser may register mobility or intent information in the mobility registration server 330 if mobility or intent is supported.

The mobility registration server 330 may be an application server. The mobility registration server 330 can register mobility information or intent information in real time according to the use of the user's web service, and can transmit information on the mobility or intent to the main device 320 and / The secondary device 350 and the like. In addition, the mobility registration server 330 may provide for registration of the capabilities of the primary device 320 and the secondary device 350, respectively, and an inquiry function for the registered capabilities.

The secondary device 350 may provide a secondary screen. The primary device 320 and the secondary device 350 may be N-screen devices of the web service provided by the web server 310.

The secondary device 350 may register the capabilities of the secondary device 350 with the mobility registration server 330. The mobility registration server 330 may provide information to the primary device 320 about the capabilities of the secondary device 350. [ The primary device 320 may use the information of the capabilities of the secondary device 350 to determine whether the web object can be moved to the secondary device 350. [

The main device 320 may request the notification server 340 to move the web object. The notification server 340 may forward the request to the secondary device 350. [

The notification server 340 may provide the secondary device 350 with a function of calling a web service or receiving a web page or a web object based on the information of the intent.

The heterogeneous devices of the Web server 310, the primary device 320, the mobility registration server 330, the notification server 340 and the secondary device 350 may be implemented as a DLNA or an Endpoint Discovery Protocol, And so on.

When a web service is provided on the main screen of the main device 320, the following procedure may be required to connect the secondary device 350 to the web service.

First, registration for the web service may be required. The service may be registered in the mobility registration server 330 or the application server. For example, information about the web service function that can be supported on the secondary screen of the secondary device 350 among the web services provided on the main screen of the main device 320 may be registered. Here, the web service function may be a web object in a web page providing a web service. In addition, the availability of the secondary device 350 can be registered. Here, the availability of the secondary device 350 may be the connectivity of the secondary device 350 to the web service.

Next, device discovery may be required. The device discovery may be that the primary device 320 discovers a secondary device 350 that is capable of moving a movable web object. For device discovery, 1) a specific application interworking type, 2) an application server interworking type, and 3) a network protocol interworking type can be used.

Examples of specific application interworking types include Universal Plug-and-Play (UPNP) and DLNA. In the particular application interworking type, a specific application may be installed in the secondary device 350. [ The main device 320 can determine whether the secondary device 350 is connected by connecting to a home network server or a designated application server. The secondary device 350 can connect to a home network server or a designated application server and provide a connection to a defined function.

An application server interworking type can be used for a specific service provided in conjunction with an application server.

The network protocol interworking type may be a method of receiving a configuration document type definition (DTD) element from an entry point and linking it to the information represented by the configuration DTD element. A networked provisioning option, a service discovery standard of Internet Protocol Television (IPTV), may be used to receive the configuration DTD element. Alternatively, the network protocol interworking type may be a method using a Domain Name Space (DNS) mechanism using Dynamic Host Configuration Protocol (DHCP) option 15. Alternatively, the network protocol interworking type may be a method using a multicast address registered in the Internet Assigned Numbers Authority (IANA).

The device selection may be in a manner for selecting a secondary screen of the secondary device 350 to connect the web object of the web service. The web object may be output on the main screen of the main device 320.

4 is a block diagram of a web server according to one embodiment.

The web server 310 may include a transmission / reception unit 410, a processing unit 420, and a storage unit 430.

The transceiver 410 may be a hardware module such as a network interface card, a network interface chip and a networking interface port, and may be a network device ) Driver or a software module such as a networking program. The transmission / reception unit 410 may receive information or data transmitted to the web server 310 and may transmit information or data transmitted by the web server 310. In addition, the transceiver 410 may receive a signal or information input from a user.

The processing unit 420 may be at least one processor or at least one core in the processor. The processing unit 420 may perform operations necessary for the operation of the web server 310. [ Here, the execution of the operation may mean executing the program code stored in the storage unit.

The storage unit 430 may store data necessary for the operation of the web server 310. [ For example, the storage unit 430 may store a web page. The storage unit 430 is a hardware module for storing information such as a hard disk drive (HDD), a solid state drive (SSD), a random access memory (RAM), and a flash And may be a software module for storing information such as a database (DB), a file system, and a table.

5 is a block diagram of a main device according to one embodiment.

The main device 320 may include a transmission / reception unit 510 and a processing unit 520.

The transceiver 510 may be a hardware module such as a network interface card, a network interface chip, and a networking interface port, and may be a software module such as a network device driver or a networking program. The transceiver 510 may receive information or data transmitted to the main device 320 and may transmit information or data transmitted by the main device 320. [ The transmitting / receiving unit 510 may receive a signal or information input from a user.

The processing unit 520 may be at least one processor or at least one core in the processor. The processing unit 520 can perform an operation required for the operation of the main device 320. [

6 is a block diagram of a secondary device in accordance with one embodiment.

The secondary device 350 may include a transceiver 610 and a processing unit 620.

The transceiver 610 may be a hardware module such as a network interface card, a network interface chip, and a networking interface port, and may be a software module such as a network device driver or a networking program. The transceiver 610 may receive information or data transmitted to the secondary device 350 and may transmit information or data transmitted by the secondary device 350. [ The transmitting / receiving unit 610 may receive a signal or information input from a user.

The processing unit 620 may be at least one processor or at least one core in the processor. The processing unit 620 may perform an operation required for the operation of the secondary device 350. [

7 is a signal flow diagram of a method by which a primary device moves a web object according to one embodiment.

The processing unit 520 of the main device 320 may load the web page from the web server 310 via the transmitting and receiving unit 510 in step 710. Step 710 may include steps 712, 714, and 716. The web page may be a service page of the web service provided by the web server 310.

In step 712, the transceiver 510 of the main device 320 may transmit a request for a web page to the transceiver 410 of the web server 310. The request of the web page may be generated by the processing unit 520 of the main device 320. [

The processing unit 420 of the web server 310 can read the requested web page from the storage unit 430 and transmit the web page read from the storage unit 430 to the main device 320, And may be edited or processed to be suitable for providing to the main device 320 prior to transmission to the device 510. One example of the above editing or processing will be described in detail below with reference to Fig.

In step 716, the transceiver 510 of the main device 320 may receive the requested web page from the transceiver 410 of the web server 310.

At step 718, the processing unit 520 of the primary device 320 may render the received web page in a web browser.

At step 720, the processing unit 520 of the primary device 320 may identify a web object that supports mobility among the web objects in the loaded web page. There can be more than one web object supporting mobility.

The processing unit 520 may identify a web object supporting mobility based on a mobility tag that represents characteristics of the web object in the web page. The mobility tag may define additional information about web objects supporting mobility within a web page or web content. That is, in addition to the existing HTML code used for the representation of the web object, the mobility tag may be additional information embedded in the web page or web content to indicate that the web object is mobile.

The mobility tag may be an intent tag of the web object. An intent tag of a web object may indicate that the web object supports mobility or that the web object is included in a region of content that supports mobility.

Intent tags can be used in duplicate within a web page. Accordingly, the plurality of intent tags can express the characteristics of the plurality of web objects.

The processing unit 520 of the main device 320 can identify the web object having the intent tag among the web objects in the loaded web page as a web object supporting mobility.

At step 730, the transceiver 510 of the primary device 320 may register 1) the mobility information of the identified web object and 2) the information about the primary device 320 with the mobility registration server 330 . Here, the mobility information of the web object may be the intent support information of the web object indicating the details of supporting the intent by the web object. The information about the primary device 320 includes an identifier of the web service provided by the web server 310, an Internet Protocol (IP) address of the primary device 320, Of addresses.

For the above registration, the transceiver 510 of the main device 320 sends a request for 1) information about the mobility support of the identified web object and 2) a request for registration of the information about the main device 320 to the mobility registration server 330).

Steps 720 and 730 described above may be performed based on the script in the web page. That is, the processing unit 520 of the main device 320 can check whether or not the mobility tag is used in the web page by processing the script in the web page. If the mobility tag exists, the mobility information of the web object represented by the mobility tag And registers it in the mobility registration server 330. In addition, the main device 520 may wait for an event until step 735, which will be described later, is performed by a script. Here, the event may be a user's request for movement of the web-sieve.

At step 735, the transceiver 510 of the primary device 320 may receive the user's request for movement of the web object. The processing unit 520 of the main device 320 may recognize the user's request for movement of the web object.

At step 740, the processing unit 520 of the primary device 320 may determine whether the identified web object can be moved to the secondary device 350 based on the mobility information of the identified web object. Here, the main device 320 and the secondary device 350 may be N-screen devices of a web service providing a web page.

If the identified web object can be moved to the secondary device 350, then in step 750, the transceiver 510 of the primary device 320 determines whether the identified web object has been moved to the secondary device 350 The request can be sent. The transceiver 510 of the primary device 320 may send a request for movement of the identified web object to the secondary device 350 to the notification server 340 or the secondary device 350. A request for movement of the identified web object to the secondary device 350 may be generated by the processing unit 520. [

The processing unit 520 may move the identified web object supporting the mobility in the web page to the secondary device 350 through the transceiver 510.

A request for movement of the identified web object to the secondary device 350 may be performed by calling an intent that the secondary device 350 provides.

At step 760, the processing unit 520 of the primary device 320 may update the web page after the identified web object is moved. The processing unit 520 may re-render the web page in the web browser. Here, re-rendering may mean rendering within a web browser, except for a web object that supports mobility that maintains the overall layout of the web page. That is, the processing unit 520 can re-render the web page in the web browser, except for the web object supporting mobility while maintaining the overall layout of the web page.

8 is a signal flow diagram of a method of processing a web object in which a secondary device according to an embodiment moves to a secondary device.

The processing unit 620 of the secondary device 350 may register the capabilities of the secondary secondary device 350 and the secondary device 350 via the transceiver 610. In step 810, Step 810 may include steps 812, 814, and 816. The capabilities of the secondary device 350 and the secondary device 350 may be registered in the mobility registration server 330 or the primary device 320.

The capability of the secondary device 350 is determined by whether the global positioning system (GPS) location of the secondary device 350 is provided, the unique address of the network card assigned to the secondary device 350, The resolution of the secondary device 350, the version of the web browser of the secondary device 350, the application supporting the intent of the secondary device 350, and the intent of the secondary device 350 Lt; / RTI > or a list of supporting applications.

The transceiver 610 of the secondary device 350 sends the information of the secondary device 350 and the capability of the secondary device 350 to the mobility registration server 330 or the primary device 320 To the transmission / reception unit 510 of FIG.

At step 814, the mobility registration server 330 or the processing unit 520 of the primary device 320 may determine whether the received information of the secondary device 350 based on the information of the received secondary device 350 and the capability of the received secondary device 350 The capabilities of the secondary device 350 and the secondary device 350 can be registered. If the capabilities of the secondary device 350 and the secondary device 350 are registered with the mobility registration server 330, the mobility registration server 330 may request the secondary device 350 And information about the capabilities of the secondary device 350 to the primary device 320. [

In step 816, the transceiver 610 of the secondary device 350 receives the information of the secondary device 350 from the mobility registration server 330 or the primary device 320 and the information of the secondary device 350 of the received secondary device 350 A response to the information of the capability can be received.

The capabilities of the registered secondary device 350 and secondary device 350 in step 810 may be used in steps 1210 through 1230 described below with reference to FIG.

The secondary device 350 may be plural. When there are a plurality of secondary devices 350, the above-described step 810 may be performed for each of the plurality of secondary devices. The mobility registration server 330 or the processing unit 520 of the main device 320 may generate a list of the registered plurality of secondary devices and information on the capability of each of the registered plurality of secondary devices. In addition, the mobility registration server 330 may provide the main device 320 with a list of a plurality of registered secondary devices and information on the capabilities of each of the registered devices at the request of the main device 320.

After step 810 is performed, the secondary device 350 may wait for a request for movement of the web object.

At step 820, the transceiver 610 of the secondary device 350 may receive a request for movement of the web object. The movement request of the web object may be output from the transmission / reception unit 510 of the main device 320. The request for movement of the web object can be directly transmitted from the transmitting and receiving unit 510 of the main device 320 to the transmitting and receiving unit 610 of the secondary device 350 and transmitted to the secondary device 350 via the notification server 340. [ To the transceiver 610 of the base station 350. The request for movement of the web object may be transmitted to the transmission / reception unit 610 as a notification message.

The request for movement of the web object may be a call to an intent provided by the secondary device 350. The request for movement of the web object may be an intent notification of the intent. The secondary device 350 may receive notification of the intent and execute a service or application corresponding to the received intent. Here, executing the service may be to load the web page within the web browser and display the loaded web page.

At step 825, the transceiver 610 of the secondary device 350 may receive the user's approval for a request for movement of the web object. The processing unit 620 of the secondary device 350 may recognize that the request for movement of the web object has been approved by the user.

At step 830, the processing unit 620 of the secondary device 350 may request information for moving the web object through the transceiver 610.

Here, the web object may be determined to be movable to the secondary device 350 by the processing unit 520 of the primary device 320 based on the information of the capabilities of the secondary device 350. [

 The transceiver 610 may send a request for information to move the web object. Here, a request for information for moving the web object may be transmitted to the transmission / reception unit 410 of the web server 310 or the transmission / reception unit 510 of the main device 320.

If the request for information for moving the web object is transmitted to the transmitting and receiving unit 410 of the web server 310, the processing unit 420 of the web server 310, in step 832, Lt; / RTI > Here, the information for moving the web object may include information of the web object, and may include a web page including the web object.

If the request for information for moving the web object is transmitted to the transmitting and receiving unit 510 of the main device 320, the processing unit 520 of the main device 320, at step 834, Lt; / RTI > Here, the information for moving the web object may include the information of the web object supporting the mobility identified in the step 720 described above with reference to Fig. 7, and in the step 710 described above with reference to Fig. 7 And may include all or some of the loaded web pages.

The transmitting and receiving unit 610 of the secondary device 350 transmits information for moving the web object from the transmitting and receiving unit 410 of the web server 310 or the transmitting and receiving unit 510 of the main device 320 in step 840, Lt; / RTI >

At step 850, the processing unit 620 of the secondary device 350 may execute an entity for rendering the moved web object. Here, the object may be at least one of a running web browser, a new window of a running web browser, a new web browser, and an application.

For example, the processing unit 620 of the secondary device 350 may execute a web browser. In addition, the processing unit 620 of the secondary device 350 may create a new window of the web browser running in the secondary device 350. In addition, the processing unit 620 can execute an application. Here, the executed application may be an application capable of processing the request for movement of the web object in step 820. [

In step 860, the processing unit 620 of the secondary device 350 may render the web object based on information for moving the received web object. The processing unit 620 may process the movement of the web object by rendering the web object.

For example, if the web browser is executed in the previous step 850, the processing unit 620 may render the moved web object in the web browser. If a new window of the running web browser is created in the previous step 850, the processing unit 620 may render the moved web object in the new window of the web browser. If an application was previously executed in step 850, the processing unit 620 may render the web object moved in the application.

In step 870, the processing unit 620 of the secondary device 350 may use the web object according to the user's manipulation. For example, the processing unit 620 transmits data related to the web object to the transmitting / receiving unit 410 of the web server 310 or the transmitting / receiving unit of the main device 320 through the transmitting / receiving unit 610 by using the function provided by the web object 510).

9 shows a screen displaying a plurality of connectable secondary devices according to an example.

The first state 900 may represent the primary device 320 in which the web page is rendered within the main screen 910. The first state 900 may be a received web page rendered in a web browser at step 718 described above with reference to Fig.

The second state 950 may indicate a primary device 320 that is displayed within the web browser in the main screen 910 by a plurality of connectable secondary devices.

In FIG. 9, the web page includes a first web object 920, a second web object 925, and a third web object 930. Here, the first web object 920, the second web object 925, and the third web object 930 are each associated with a loaded web, identified by the processing unit 520 in step 720, And may be a web object supporting mobility among the web objects in the page.

The web page may include a device discovery button 940. For example, when the device discovery button 940 is pressed by the user, the state of the main device 320 can be changed from the first state 900 to the second state 950. [

In the second state 950, a list of registered devices 960 in the web browser is displayed. Each of the items in the list of registered devices 960 may represent one of the plurality of secondary devices. In FIG. 8, in the list of registered devices 960, an item 970-1 representing the first secondary device, an item 970-2 representing the second secondary device, An item 970-3 and an item 970-4 indicating a fourth secondary device are respectively shown.

Each item may include one or more of an icon, an image, and a photograph representing the secondary device 350 corresponding to the item; and 2) the owner or user of the secondary device 350 corresponding to the item Symbols, letters and strings representing the type of secondary device 350 corresponding to the item; and 3) one or more of icons, symbols, characters and strings representing the type of secondary device 350 corresponding to the item. An icon, an image or a photograph representing the secondary device 350 may be selected based on the type of the secondary device 350. For example, in FIG. 1, in item 970-1 representing the first secondary device, 1) "User 1", which is the user of the first secondary device, 2) "And 3) An image representing the first secondary device was displayed.

Each of the registered devices 960 of the registered devices 960 can be displayed separately according to whether or not the web object can be moved. For example, the border of the item corresponding to the registered device to which the web object can be moved may be a bold border, and the border of the item corresponding to the registered device to which the web object can not be moved may be a thin border. Also, among the registered devices list 960, the registered device to which the web object can be moved is distinguished from 1) a registered device in which the web object can not be moved, 2) is displayed in a color indicating that it is activated .

10 is a flowchart illustrating a method for selecting a secondary device to transmit a web object among a plurality of connectable secondary devices according to an exemplary embodiment.

The method by which the main device described above with reference to FIG. 7 moves the web object may include steps 1010 through 1044 described below. For example, steps 1010 through 1044 described below may be performed after step 735 described above with reference to FIG. 7 and may be performed prior to step 750 described above with reference to FIG.

Further, the reception of the user's request in step 735 may be that the device find button 925 described above with reference to FIG. 9 is pressed. The processing unit 520 of the main device 320 can recognize that the device discovery button 925 is pressed as a user's request for movement of the web object.

In step 1010, the processing unit 520 of the main device 320 may obtain information on the list of registered devices via the transceiver 510. [ Step 1010 may include steps 1012 and 1024

The registered devices may be the secondary device 350 that is receivable for the intent being executed in the primary device 320. [ The registered devices may be devices registered in the mobility registration server 330 for receiving an intent for the web service running in the main device 320. [

The transceiver 510 of the main device 320 transmits a request for information of the registered devices 960 to the transceiver 610 of the mobility registration server 330 or the secondary device 350, Lt; / RTI >

In step 1014, the transceiver 510 of the main device 320 receives information of the registered devices 960 from the transceiver 610 of the mobility registration server 330 or the secondary device 350 can do.

The information in the list of registered devices 960 may include information about the capabilities of each of the registered devices. The capabilities of each device include, but are not limited to, whether to provide a GPS location, the unique address of the network card assigned to the device, the resolution of the device, the version of the device's web browser, the name of the application supporting the device's intent, Lt; RTI ID = 0.0 > applications. ≪ / RTI >

At step 1020, the processing unit 520 of the primary device 320 may display a list of registered devices 960 in the web browser based on information in the list of received registered devices. The secondary device 350 may be a device corresponding to one item of the list of registered devices 960. As described above with reference to FIG. 9, the processing unit 520 may display information of each of the registered devices together with the list of registered devices 960.

The processing unit 520 can display each registered device among the registered devices list 960 according to whether the web object can be moved or not. For example, the processing unit 520 may display an item corresponding to a registered device to which the web object can be moved using a bold border, and an item corresponding to a device to which the web object can not be moved using a narrow border Can be displayed. Alternatively, the processing unit 520 may determine that the registered device to which the web object is to be moved among the registered devices list 960 is 1) distinguished from the registered device in which the web object can not be moved, 2) Can be displayed separately.

In step 1030, the transceiver 510 of the primary device 320 may receive an input of a user selecting the secondary device 350 of the list of registered devices 960. The processing unit 520 of the main device 320 may recognize that the secondary device 350 of the list of registered registered devices 960 is selected by the user. Here, the user's selection may be to click or touch an item representing the secondary device 350 in the list of registered devices 960.

That is to say, the secondary device 350 may be the device selected as the device to move the web object by the user among the devices in the list of registered devices 960.

In step 1040, the processing unit 520 of the primary device 320 may obtain information on the capabilities of each of the devices registered through the transceiver 510, or on the capabilities of the secondary device 350. Step 1040 may include steps 1042 and 1044

At step 1042, the transceiver 510 of the primary device 320 may transmit a request for information on the capabilities of each of the registered devices to the mobility registration server 330 or each of the registered devices. Alternatively, the transmitting / receiving unit 510 of the main device 320 may transmit a request for information on the capability of the secondary device 350 to the transmitting / receiving unit 610 of the secondary device 350.

At step 1044, the transceiver 510 of the primary device 320 can receive information of the capabilities of each of the registered devices from the mobility registration server 330 or each of the registered devices. Alternatively, the transmitting / receiving unit 510 of the main device 320 may receive information of the capabilities of the secondary device 350 from the secondary device 350. [

Information on the capabilities of each of the registered registered devices and information on the capabilities of the secondary device 350 may be used to identify web objects that can be moved to each of the registered devices or to the secondary device of the plurality of web- Can be used.

FIG. 11 shows a screen for selecting a web object to be moved among a plurality of web objects according to an example.

There may be a plurality of web objects supporting mobility identified in step 720 described above with reference to Fig. 11, a first web object 920, a second web object 925, and a third web object 930 are shown as a plurality of web objects, respectively. 11, it is shown that the first secondary device 970-1 is selected as the secondary device 350 to which the web object is to be moved.

If the secondary device 350 to which the web object is to be moved is selected from the list of registered devices 960, the web objects that can be transmitted to the selected secondary device 350 among the plurality of web objects can be distinguished. Each of the plurality of web objects may be displayed separately depending on whether they can be moved to the secondary device 350 or not. For example, an activated button can be displayed inside a web object that can be moved to the secondary device 350, and a disabled button can be displayed inside a web object that can be moved to the secondary device 350 have. 11, in the interior of the first web object 920 and in the third web object 30 that can be moved to the secondary device 350 and in addition to the activated web object button 1120 and the activated web object 920, A move button 1130 is displayed. Meanwhile, a deactivated web object move button 1125 is displayed inside the second web object 925 that can not be moved to the secondary device 350.

The user may select a web object to be transmitted to the secondary device 350 among the web objects marked as being able to be transmitted to the secondary device 350. [ Where the user's selection may be to click or touch a web object of one of the web objects or one of the web objects marked as being able to be sent to the secondary device 350. [

12 is a flowchart illustrating a method for selecting a web object to be transmitted to a secondary device among a plurality of web objects according to an exemplary embodiment.

The method by which the main device described above with reference to FIG. 7 moves the web object may include steps 1210 through 1230 described below. For example, steps 1210 through 1230 to be described later may be performed after step 735 described above with reference to FIG. 7 or after steps 1010 through 1044 described above with reference to FIG. 10, May be performed before the above-described step 750 with reference to FIG.

For the connectable secondary device 350, not all web objects in the web page may be moved. A method for determining whether a web object can be moved to the secondary device 350 will be described below.

At step 1210, the processing unit 520 of the primary device 320 may determine whether each of a plurality of identified web objects can be moved to the secondary device 350. [ Here, the plurality of identified web objects may be the web objects identified in step 720 described above with reference to Fig. 7, respectively. That is, the number of web objects identified in step 720 may be plural.

The processing unit 520 may determine whether each of the plurality of identified web objects can be moved to the secondary device 350 based on the capabilities of the secondary device 350. [ The processing unit 520 can determine whether each of a plurality of identified web objects can be represented or reproduced on the secondary screen of the secondary device 350 based on the capabilities of the secondary device 350. [

For example, if the secondary device 350 can not provide a GPS location, the web object requesting the GPS location can not be moved to the secondary device 350. Or, the web object may require a minimum resolution to be rendered, and if the resolution of the secondary device 350 does not reach the minimum resolution above, the web object may not be moved to the secondary device 350.

The processing unit 520 can determine the capability of the secondary device 350 by referring to the Web Intent device description described later with reference to FIG. The web intent device description may indicate whether the secondary screen of the secondary device 350 can represent or reproduce the web object.

In addition, the processing unit 520 can determine whether the secondary device 350 can represent the web object by using the values of the action attribute and the type attribute in the intent tags of the web object have. The attributes in the intent tag and the intent tag will be described in detail below with reference to Fig.

The web object that may be represented in the secondary device 350 may be a web object that can be moved to the secondary device 350. That is, the processing unit 520 moves each of the plurality of identified web objects to the secondary device 350 based on the value of the action attribute and the type attribute of the intent tag of each of the plurality of identified web objects It is possible to judge whether or not it is possible.

The script can check whether the action attribute and the type attribute exist in the intent tag of the web object.

The processing unit 520 also compares the value of the action attribute of the intent tag of the web object and the value of the type attribute with the capability of the secondary device 350 to determine whether the secondary device 350 can represent the web object Can be determined. The processing unit 520 compares the value of the action attribute value and the value of the type attribute of each of the plurality of identified web objects with the capabilities of the secondary device 350 so that each of the plurality of identified web objects is associated with the secondary device 350. [ It can be judged whether or not it can be moved to the < RTI ID = 0.0 >

In step 1220, the processing unit 520 of the primary device 320 may separately display each of the plurality of identified web objects according to whether they can be moved to the secondary device. For example, the processing unit 520 may display an activated button within a web object that may be moved to the secondary device 350, and may include an inactive Button can be displayed. In addition, the processing unit 520 may use different colors to display each of the plurality of identified web objects according to whether they can be moved to the secondary device 350 or not. The first color used for the web object that can be moved to the secondary device 350 among the plurality of identified web objects and the second color used for the web object that can not be moved to the secondary device 350 They may be different from each other. In addition, the processing unit 520 can distinguish and display each of the plurality of identified web objects according to whether they can be moved to the secondary device 350 by using frames of different thickness.

The above-described steps 1210 and 1220 may be performed based on a script in a web page. That is, the processor 520 of the main device 320 may determine whether each of the plurality of identified web objects can be moved to the secondary device 350 by processing a script in the web page. In addition, the processing unit of the main device 320 can divide and display each of the plurality of identified web objects according to whether they can be moved to the secondary device 350 by processing a script in the web page.

In step 1230, the transceiver 510 of the primary device 320 may receive an input of a user selecting one of the plurality of identified web objects. The processing unit 520 of the main device 320 may recognize a selected web object among a plurality of identified web objects. Here, the user's selection may be to click or touch one web object of the displayed plurality of identified web objects.

The selected web object may be a web object to be moved to the secondary device 350 in step 750 described above with reference to FIG. 7 of the plurality of web objects. That is, in step 750, the transceiver 510 of the primary device 320 may send a request for movement of the selected web object of the plurality of identified web objects to the secondary device 350.

FIG. 13 shows a screen for receiving a user's approval for a request for movement of a web object according to an example.

Receiver 610 of the secondary device 350 receives a request for movement of the web object in step 820 described above with reference to Figure 8, A window 1320 indicating a request for movement of the web object may be output.

In window 1320, a message may be output indicating that a request to move web object from main device 320 has been received. In Fig. 13, the request for movement of the web object is indicated as a request to share a screen of the area represented by the web object. The main device 320 is indicated as the PC of the first user.

The window 1320 may include buttons that allow the user to approve the request for movement of the web object. The window 1320 may include an OK button 1330 and a Cancel button 1340.

When the confirmation button 1330 is clicked or touched by the user, step 825 described above with reference to Fig. 8 may be performed. If the cancel button 1340 is clicked by the user, the method of processing the web object moving to the secondary device 350 described with reference to Fig. 8 may be discontinued.

14 illustrates a screen for manipulating a web object moved to a secondary device according to an example.

In FIG. 14, the moved web object 1420 is output to the screen 1410 of the secondary device 350. The moved web object 1420 may be the third object 930 described above with reference to FIG. The moved web object 1420 may include an input window 1430, a popup button 1440, and a cancel button 1450. The input window 1430, the upload button 1440 and the cancel button 1450 may be considered functions, operations, functions or methods provided by the moved web object 1420, respectively.

In step 870 described above with reference to FIG. 8, the user may manipulate the moved web object 1420. For example, the user may enter a comment on the web service in the input window 1430. The user can use the functions provided by the web object by pressing the upload button 1440 and the cancel button 1450. [ When the user presses the upload button 1440, the processing unit 620 of the secondary device 350 transmits the comment input in the input window 1430 through the transmission / reception unit 610 to the transmission / reception unit 410 of the web server 310, (510) of the main device (320). When the user presses the cancel button 1450, the processing unit 620 of the secondary device 350 transmits information indicating that the comment has been canceled through the transmitting / receiving unit 610 to the transmitting / receiving unit 410 of the web server 310 To the transmission / reception unit 510 of the main device 320. FIG.

15 illustrates a rendered web page after moving a web object according to an embodiment.

In Figure 15, a replaced image 1510 is shown after the web object has moved to the secondary device 350. [ The image 1520 includes 1) the capture 1530 of the web object, 2) the name 1530 of the user of the secondary device 350, 3) the name 1540 of the type of web object, and 4) (1550). ≪ / RTI >

After the web page is loaded in step 710 described above with reference to Fig. 7, the web page loaded in step 718 may be rendered within the web browser.

After the web object is moved to the secondary device 350, if the web browser is re-rendered after the web object is simply deleted within the web page, the area occupied by the web object disappears, so that the overall layout of the web page is lost. Can cause problems. Thus, as described above in step 760, the processing unit 520 may re-render the web page in the web browser, except for the web object supporting mobility, while maintaining the overall layout of the web page.

At step 760 for re-rendering, the processing unit 520 may maintain the overall layout of the web page by replacing the area of the web object supporting mobility with the image 1510. [ The area occupied by the image 1510 in the web page may correspond to the area occupied by the web object before movement.

A specific method of replacing the area of the web object supporting mobility with the image 1510 will be described in detail below with reference to FIG.

16 is a flowchart of a method of rendering a web page after moving a web object according to an example according to an embodiment.

Step 760 described above with reference to FIG. 7 may include the following steps 1610 - 1630.

In operation 1610, the processor 520 of the main device 320 may capture an area corresponding to the web object as the image 1510.

At step 1612, the processing unit 520 of the primary device 320 may add the user's name 1530 of the secondary device 350 to the image 1510.

In step 1614, the processing unit 520 of the primary device 320 may add the name 1540 of the type of web object to the image 1510.

In operation 1616, the processor 520 of the primary device 320 may add the name 1550 of the secondary device 350 to the image 1510.

At step 1620, the processing unit 520 of the primary device 320 may set the web object not to be displayed within the web browser. The processing unit 520 of the main device 320 may set the value of the visibility style of the web object to be hidden so that the web object is not displayed in the web browser.

At step 1630, the processing unit 520 of the primary device 320 may display an image 1510 in an area corresponding to the web object. Here, the area corresponding to the web object may be a part occupied by the contents of the web object in the web browser.

17 is a flow diagram of a method by which a web server in accordance with one embodiment processes movement of a web object.

The web server 310 may perform functions of the mobility registration server 330 and the notification server 340. The steps described as being performed by the mobility registration server 330 or the notification server 340 in Figs. 7, 8, 10, etc. may be performed by the web server 310. [

Step 710 described above with reference to FIG. 7 may include steps 1710 through 1735 described below. For example, step 710 may be replaced by steps 1710-1735 described below.

In step 1710, the processing unit 420 of the web server 310 may load the web page from the storage unit 430. [

In step 1715, the processing unit 420 of the web server 310 may generate mobility information for a web object supporting mobility among the web objects in the web page. The above mobility information can be generated as a script file. The mobility information may include a mobility tag or an intent tag. The script file may include information necessary for the main device 320 to acquire information, such as the address of the web server 310 or the address of the mobility registration server 330.

In step 1720, the processing unit 420 of the web server 310 may insert a link indicating mobility information on the web object supporting mobility in the header of the web page. The link may point to a script file in the web server 310.

The transmitting and receiving unit 410 of the web server 310 may transmit the web page in which the link is inserted to the transmitting and receiving unit 510 of the main device 320 in step 1725. The processing unit 520 of the main device 320 can load the web page into which the link is inserted through the transmission /

The transmitting and receiving unit 510 of the main device 320 may transmit the request of the entity in the web server 310 indicated by the link to the transmitting and receiving unit 410 of the web server 310 in step 1730. Here, the object may be a file or a script including mobility information about the web object.

In step 1735, the transceiver 410 of the web server 310 may transmit the requested entity to the transceiver 510 of the primary device 320.

Through steps 1730 and 1740 described above, the processing unit 520 of the main device 320 can obtain mobility information for the web object by additionally loading the object to which the link points.

At step 1740, the processing unit 520 of the primary device 320 may determine whether the entity represents mobility information for the web object. If the entity does not represent mobility information for a web object, the processing unit 520 may process the entity as a script or file independent of mobility information.

At step 1745, the processing unit 520 of the primary device 320 may obtain information about the primary device 320. [ Here, the information on the main device 320 may include one or more of the ID of the web service provided by the web server 310, the IP address of the main device 320, and the IP address of the secondary device 350 have.

In step 1750, the transceiver 510 of the primary device 320 sends a request to the web server 310 to register 1) information about the mobility support of the identified web object and 2) To the transmission / reception unit 410 of FIG. The processing unit 420 of the Web server 310 may register one or more of 1) information on the mobility support of the identified web object transmitted from the main device 320 and 2) information on the main device 320 . Step 1750 may correspond to step 730 described above with reference to FIG.

The steps 1740, 1745, and 1750 described above may be performed by the entity to which the link points. For example, the script file may be a script library for operating an intent function within a web page. The processing unit 520 of the main device 320 may perform the steps 1740, 1745, and 1750 described above by executing the script library. 2) a function of acquiring information of the Web server 310; and 3) a function of acquiring information on the main device 320 Can be described.

The transmitting and receiving unit 410 of the web server 310 transmits the information of the secondary device 350 and the capability of the secondary device 350 to the transmitting and receiving unit 610 of the secondary device 350, Lt; / RTI > Step 1760 may correspond to step 812 described above with reference to FIG.

At step 1765, the processing unit 420 of the web server 310 determines whether the secondary device 350 and / or the secondary device 350 are enabled based on the information of the received secondary device 350 and the capability of the received secondary device 350 The capability of the secondary device 350 can be registered. Step 1765 may correspond to step 814 described above with reference to FIG.

The transmitting and receiving unit 410 of the web server 310 transmits the information on the capability of each of the registered devices or the capability of the secondary device 350 to the transmitting and receiving unit 510 of the main device 320, Lt; / RTI > Step 1770 may correspond to step 1040 described above with reference to FIG.

In step 1775, the transceiver 410 of the web server 310 may receive a request for information to move the web object from the transceiver 610 of the secondary device 350. Step 1775 may correspond to step 830 described above with reference to FIG.

In step 1780, the processing unit 420 of the web server 310 may generate information for moving the web object. Here, the information for moving the web object may include information of the web object, and may include a web page including the web object. Step 1780 may correspond to step 830 described above with reference to FIG.

The transmitting and receiving unit 410 of the web server 310 may transmit the information for moving the web object to the transmitting and receiving unit 610 of the secondary device 350 in step 1785. Step 1785 may correspond to step 840 described above with reference to FIG.

In step 1790, the transceiver 410 of the web server 310 may receive data related to the web object from the transceiver 610 of the secondary device 350. Step 1790 may correspond to step 870 described above with reference to FIG.

In step 1795, the processing unit 420 of the web server 320 may update the web object based on data associated with the web object. The web server 320 may update the web page based on the data related to the web object. For example, if the web object is the third object 930 described above with reference to FIG. 9 and the data associated with the web object is a comment for the web service, the processing unit 420 may add the comment to the web page . When the step 710 is repeated, the transmitting / receiving unit 410 of the web server 320 may transmit the updated web page to the transmitting / receiving unit 510 of the main device 320.

18 shows a code used for invoking an intent according to an example.

As described above, the primary device 320 may move the identified web object to the secondary device 350 by invoking the intent that the secondary device 350 provides.

The code 1800 in FIG. 18 may be an example of a code used for invoking an intent.

The first row 1810 may indicate assigning the generated intent object to the variable "intent ".

Second row 1820 may indicate that the action of the generated intent object is "http://webintents.org/edit. &Quot; That is, in Fig. 18, the intent action is shown as an edit action provided at "http://webintent.org. &Quot; In addition to editing, the intent's actions can be share, view, pack, subscribe and save.

Third row 1830 may indicate the type of object that is the subject of the action. That is, in Fig. 18, the intent action is shown as an "html5" type of web object.

The fourth row 1840 may indicate a point at which the action is to be loaded. In FIG. 18, the action is shown as being performed in "http://kaisqure.kaist.ac.kr/pages/commentBox.php?cid=c1234&textBoxType-multipleLine".

Secondary device 250 may perform editing on the "webObject / html5" object at "http://kaisqure.kaist.ac.kr/pages/commentBox.php?cid=c1234&textBoxType-multipleLine&quot ;.

The fifth row 1850 may be code that calls the generated intent.

19 illustrates a code used for registration of an intent according to an example.

In the code 1900 of FIG. 19, "<intent" and "/ >" may indicate the beginning and end of the code used for registering the intent, respectively. "< intent &gt; and" / > "may indicate the start and end of an intent tag for registration of an intent, respectively. The intent tag may be a string from "<intent" to "/ &quot;.

The web page provided by the web server 310 provides the handling functionality for the type of intent and action of a specific intent by using the "<intent>" tag by declaring the web page itself declaratively declaratively mark it.

"Action", "type", "href (hypertext reference)", "title" and "disposition" shown in FIG. 19 are respectively referred to as Document Object Model String; DOMString) type attribute.

The action attribute of the first row 1910 may be a string indicating a behavior class supported by the service. The string may be an opaque string.

The value of the action attribute may be the URI or URL to which the action is to be delivered. For example, the value of the action attribute may indicate the application of the secondary device 350 to which the intent call is applied.

The type attribute of the second row 1920 may be a string specifying the type of payload data of the intent. The value of the type attribute may be one of the HTML5 tags.

The type attribute can be a list of type specifiers separated by whitespace. When type specifiers are parsed as 1) mime type or 2) a mime wildcard type such as "* / *" or "*", type specifiers are mime type or mime wildcard Can be interpreted as a type. If the type specifiers are not parsed as a mime type and a mime wildcard type, then the typing specifiers can be interpreted as a string literal type specifier. In Figure 19, the value of the type attribute is shown as being text.

The value of the hypertext reference attribute of the third row 1930 may be the URI of the service. The value of the hypertext reference attribute may be the URI or URL of the source that should be loaded when the intent is invoked. The value of the hypertext reference attribute may be a fully qualified URI. If the hypertext reference attribute does not exist, the URI of the service may be the URI for which the tag for registering the intent was found. Here, the URI in which the tag for registering the intent is found may be the URI of the web page including the intent tag.

The value of the title attribute of the fourth row 1940 may be a title readable by the user indicating the service provided to the user. The value of the title attribute may be the name of a web object that the user can read. If the title attribute does not exist, the title of the page of the registered service can be used as the title of the service.

The temperament attribute of the fifth row 1950 may allow the service to select where the context of the intent invocation will be opened. The user's device may not allow the value of the substrate attribute to be changed by the web page.

Among the values of the temperament property, "window" may mean that the service is opened in a new tab or window context of the web browser. Among the values of the temperament attribute, "inline" may mean that the user's device opens in a context that is directly related to the context of the client page in a way that overlaps the service. The temperament attribute may not be an essential attribute. If the substrate attribute is absent, the "window" value can be applied as the default.

20 is a page showing information of a main device according to an example.

1) the mobility information of the identified web object and 2) the information about the main device 320 of step 730 described above with reference to FIG. 7 may be generated as an XML document 2000.

The XML document 2000 is an example of a file including information on the main device 320 and mobility information of the identified web object. That is to say, at step 730, the processing unit 520 of the primary device 320 may generate 1) an XML document 2000 that represents the mobility information of the identified web object and 2) information about the primary device 320 have. The transmitting and receiving unit 510 of the main device 320 can transmit the generated XML document 2000 to the mobility registration server 330 or the transmitting and receiving unit 410 of the web server 310.

The XML document 2000 may include information 2010 of the type of the main device 320 as information on the main device 320. [ In addition, the XML document 2000 may include registration information 2020 of the intent as mobility information of the identified web object. The details of the intent registration information 2020 are described above with reference to FIG. The intent registration information 2020 may be plural.

In addition, the XML document 2000 may include information indicating the namespace of the XML, information indicating the version of the XML specification, and the like.

21 is a flow diagram of a method for discovering a secondary device according to an example.

The manner in which the main device 320 described above with reference to FIG. 7 moves the web object may include steps 2110 and 2120 described below. For example, steps 2110 and 2120 to be described later may be performed after step 735 described above with reference to FIG. 7 and may be performed prior to step 750 described above with reference to FIG.

The method of finding the secondary device 350 may be performed in place of the step 1010 described above with reference to FIG. That is, the primary device 320 may search the secondary device 350 directly instead of receiving the list of registered devices.

In the following steps 2010 and 2120, the secondary device 350 may be replaced with an application server.

In step 2110, the transceiver 510 of the primary device 320 may send a discovery message to the transceiver 610 of the secondary device 350. The transmission may be a broadcast transmission.

The code in Table 1 below may be an example of a discovery message.

[ Discovery Message ]
D-SEARCH * HTTP / 1.1
Host: 192.168.126.3: 2460
UDD: urn: schemas-kaist-org: device: WebIntents: 1
LDD: discover
MaxRetry: 3

In step 2120, when the secondary device 350 receives the discovery message, the transmitting / receiving unit 610 of the secondary device 350 transmits a device response corresponding to the discovery message to the transmitting / receiving unit 510 of the primary device 320 ).

The code in Table 2 below may be an example of a device response.

[Device Response]
HTTP / 1.1 200 OK
UDD: urn: schemas-kaist-org: device: WebIntents: 1
Host: 192.168.126.3: 2460
LDD: urn: http: //mnlab.kaist.ac.kr/userID/dke00988-slk48wej-3jfna-87329 :: urn: schemas-kaist-org: device: WebIntents: 1
SERVER: Windows NT / 5.0
LOCATION: http: 179.143.248.17/5432/
Content-Length: 0

In steps 2110 and 2120 described above, there may be a plurality of secondary devices 350 that have received the discovery message and sent a device response. The list of registered devices 960 may refer to discovery messages sent from a plurality of secondary devices or some of the discovery messages.

22 is a page showing the capabilities of the secondary device according to an example.

Information on the capabilities of the secondary device 350 of step 1040 described above with reference to FIG. 10 may be generated as an XML document 2200. The XML document 2200 may represent a Web Intent device description that describes the capabilities of the Web Intent device.

The XML document 2200 is an example of a file that contains information of the secondary device 350 and information of the capabilities of the secondary device 350.

For example, at step 1042, the processing unit 620 of the secondary device 350 may generate an XML document 2200 that represents the information of the secondary device 350 and the capabilities of the secondary device 350. The transmitting and receiving unit 610 of the secondary device 350 can transmit the generated XML document 2200 to the transmitting and receiving unit 510 of the main device 320. [

The XML document 2200 includes at least one of a general description 2210 for the secondary device, a name 2220 of the secondary device, a type 2230 of the secondary device, and an intent 2240 supported by the secondary device . The intents 2240 supported by the secondary device may be plural.

In addition, the XML document 2200 may include information indicating the namespace of the XML, information indicating the version of the XML specification, and the like.

23 is a block diagram of a push server according to an embodiment.

The push server 2300 may include a transmission / reception unit 2310 and a processing unit 2320.

The transceiver 2310 may be a hardware module such as a network interface card, a network interface chip, and a networking interface port, and may be a software module such as a network device driver or a networking program. The transmission / reception unit 2310 can receive information or data transmitted to the push server 2300, and can transmit information or data transmitted by the push server 2300. [ The transmission / reception unit 2310 may receive a signal or information input from a user.

The processing unit 2320 may be at least one processor or at least one core in the processor. The processing unit 2320 can perform operations necessary for the operation of the push server 2300. [

24 is a signal flow diagram of a method in which a primary device moves a web object using a push server in one embodiment.

Step 750 described above with reference to FIG. 7 may be replaced by steps 2410 through 2460 described below. The request for movement of the web object may be performed using the push server 2300 rather than the notification server 340. [ Steps 2410 through 2460 may be incorporated into the manner in which the main device 320 described above with reference to FIG. 7 moves the web object.

The processing unit 520 of the primary device 320 notifies the push server 2300 that the web object identified through the transceiver 510 can be moved to the secondary device 250. In step 2410, The user can push the movement of the web object to the server 350. The sending and receiving unit 2310 of the push server 2300 can receive a push of the movement of the web object to the secondary device 350. [

If there are a plurality of identified web objects, a selected one of the plurality of identified web objects may be recognized in step 1230 described above with reference to FIG. At this time, in step 2410, the processing unit 520 of the main device 320 may push a request for movement of the selected web object among the plurality of identified web objects to the secondary device 350. [

In step 2420, the processing unit 2320 of the push server 2300 may invoke the URL or application of the secondary device 350 through the transceiver 2310. [ The call may be a call to an intent that the secondary device 350 provides. That is to say, the intents provided by the secondary device 350 may be invoked by a push applied by the push server 2300.

In step 2430, the transceiver 2310 of the push server 2300 may receive a response to the call. That is, the push may be that the push server 2300 calls the URL or application of the secondary device 350 and receives a response to the call.

In step 2440, the transceiver 510 of the main device 320 may receive a response to the push from the transceiver 2310 of the push server 2300.

In step 2450, the transceiver 510 of the primary device 320 may receive a request for a web page from the transceiver 610 of the secondary device 350.

In step 2460, the transceiver 510 of the primary device 320 may transmit the requested web page to the transceiver 610 of the secondary device 350.

The above-described steps may represent computer program code that performs the functions of the steps. Each of the above-described steps can be performed by the execution subject of the step executing the code of the recording medium on which the program is recorded. The executing entity may be a web server 310, a main device 320, a mobility registration server 330, a connection server 340, or a secondary device 350. The recording medium may include codes corresponding to the steps performed by a particular executing entity. The executing entity can perform the steps by executing the codes in the recording medium.

The apparatus described above may be implemented as a hardware component, a software component, and / or a combination of hardware components and software components. For example, the apparatus and components described in the embodiments may be implemented within a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable array (FPA) A programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system and one or more software applications executing on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to execution of the software. For ease of understanding, the processing apparatus may be described as being used singly, but those skilled in the art will recognize that the processing apparatus may have a plurality of processing elements and / As shown in FIG. For example, the processing unit may comprise a plurality of processors or one processor and one controller. Other processing configurations are also possible, such as a parallel processor.

The software may include a computer program, code, instructions, or a combination of one or more of the foregoing, and may be configured to configure the processing device to operate as desired or to process it collectively or collectively Device can be commanded. The software and / or data may be in the form of any type of machine, component, physical device, virtual equipment, computer storage media, or device , Or may be permanently or temporarily embodied in a transmitted signal wave. The software may be distributed over a networked computer system and stored or executed in a distributed manner. The software and data may be stored on one or more computer readable recording media.

The method according to an embodiment may be implemented in the form of a program command that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions to be recorded on the medium may be those specially designed and configured for the embodiments or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

   While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. For example, it is to be understood that the techniques described may be performed in a different order than the described methods, and / or that components of the described systems, structures, devices, circuits, Lt; / RTI &gt; or equivalents, even if it is replaced or replaced.

310: main device
320: Web server
330: mobility registration server
340: Notification Server
350: Secondary device

Claims (13)

A method for a web server to handle movement of a web object,
Generating mobility information for a movable web object in a web page;
Inserting a link pointing to the mobility information into the header of the web page; And
Sending the web page to a primary device
And a web server providing movement of the web object. The method of claim 1,
Wherein the mobility information comprises an intent tag, wherein the web server provides movement of the web object. The method of claim 1,
And wherein said mobility information is generated as a script file. The method of claim 3,
And wherein the link points to the script file in the web server. The method of claim 1,
Receiving a request from the primary device of an entity in the web server to which the link points; And
Transmitting the entity to the primary device
Wherein the web server provides movement of the web object. The method of claim 1,
Registering information on the main device transferred from the main device
Further comprising:
Wherein the information about the principal device comprises at least one of an identifier of the web service provided by the web server and an internet protocol address of the main device. The method according to claim 1,
Receiving information of the secondary device and information of the capabilities of the secondary device;
Registering the capabilities of the secondary device and the secondary device based on the information of the secondary device and the information of the capabilities of the secondary device; And
Transmitting information on the capabilities of each of the registered devices to the main device
Wherein the web server provides movement of the web object. The method of claim 7, wherein
Wherein the primary device and the secondary device are N-screen devices of a web service providing the web page, wherein the web server provides movement of the web object. The method of claim 1,
Receiving a request for information to move the web object from a secondary device;
Generating information for moving the web object; And
Transmitting information for moving the web object to the secondary device
Wherein the web server provides movement of the web object. The method of claim 1,
Receiving data related to the web object from a secondary device; And
Updating the web page based on data related to the web object
Wherein the web server provides movement of the web object. 11. The method of claim 10,
Transmitting the updated web page to the main device
Wherein the web server provides movement of the web object. A recording medium providing a method for a web server to process movement of a web object,
Code for generating mobility information for a movable web object within a web page;
Code for inserting a link pointing to the mobility information into the header of the web page; And
Code to send the web page to the primary device
And the program is recorded on the recording medium. A method in a web server for handling movement of a web object,
A processing unit for generating mobility information for a movable web object in a web page and inserting a link indicating the mobility information into a header of the web page; And
A transmitting / receiving unit for transmitting the web page to the main device
Including, a web server.

Images