JP6786656B2 - Information processing terminal, control method and program of information processing terminal - Google Patents

Description

The present invention relates to a technique for providing a service using a mechanism such as Web Intents.

Conventionally, when delegating processing between WEB sites, the side that calls the function needs to know how to call the function such as API (application programming interface) and REST interface of the side that provides the function. was there. Therefore, in order to realize cooperation with different websites, the caller of the function needs to process the caller according to each calling convention. Further, in order for the caller of the function to use the function, it is often necessary to authenticate to the side that provides the function. For this reason, the side that uses the function needs to hold the authentication information of the side that provides the function, or use an authentication infrastructure such as SAML. However, if you have authentication information, you need to manage those authentication information correctly and safely, and in order to use the authentication infrastructure such as SAML, it is necessary to agree in advance between the function provider and the user, and the function It was a burden on the users. Patent Document 1 discloses a technique for using a service conventionally provided on the Web.

There is also a mechanism for linking with an arbitrary web service (or web application) without using a dedicated API. As an example, a mechanism called Web Intents has been proposed in which the service receiving side and the providing side are loosely coupled by runtime delay binding and their cooperation is realized.

Japanese Unexamined Patent Publication No. 2009-199369

In the above-mentioned new cooperation mechanism such as WebIntents, in order to use the provided function provided by the service of the mechanism, the user agent (UA) processes the HTML document including the markup for registration of the function information of the provided function. Then, the function information is registered as a Web Intent. The UA can connect to the service using the function information registered in itself and request the execution of the provided function. However, when a plurality of relay functions exist in the information processing terminal, the function information is registered individually for each relay function and managed individually. Therefore, even if a certain function information is registered in a certain relay function, the function information cannot be used from another relay function. Therefore, even if the user has the same function information, it is necessary to repeat the registration process for each relay function, which is not always easy to use. Therefore, it can be said that various improvements for improving usability will be required in the future regarding the request for the service using this Web Intent and the registration of the Web Intent.

Therefore, an object of the present invention is to add a flexible improvement for improving usability to a new cooperation mechanism such as Web Intents, which is currently proposed.

The present invention communicates over a network with a website that provides page data, including descriptions of data to be shared and shared objects to be displayed, and information that the operating system (OS) and web browser perform. It is a processing terminal, and as a function of the OS, it has a providing means for providing information of a plurality of services for sharing data managed by the OS to the web browser, and as a function of the web browser. , The plurality of services are provided based on the information provided by the providing means in response to the user instruction to the shared object being given via the page displayed based on the page data received from the website. It is characterized in that a selection screen for selecting one from the including list is displayed.

According to the present invention, improvements are provided for improving usability of new cooperation mechanisms such as Web Intents . More specifically, a user to a shared object in a page displayed on a web browser based on the page data with specific content such as text or image in the page according to the intention of the website providing the page data. Depending on the operation, the service managed by the OS often used by the user of the information processing terminal can be selected as the sharing destination and easily shared.

The figure which exemplifies the basic system configuration of Web Intents. A sequence diagram illustrating an outline of the basic operation of Web Intents. The figure which illustrates the markup for registration of Web Intents and the processing request. An example of the UI of an information processing terminal that has multiple browsers installed. The figure which illustrates the hardware configuration of a client and a service 103. The figure which illustrates the hardware composition of the information processing terminal including UA. The figure which illustrates the software configuration of the information processing terminal including UA. The figure which illustrates the function information managed by the Web browser. FIG. 5 is a sequence diagram of an operation in which functional information is mutually used in the first embodiment. The figure which illustrates the screen displayed on the Web browser. A detailed sequence diagram of a part of the sequence of FIG. A detailed sequence diagram of a part of the sequence of FIG. The figure which illustrates the definition file of the function information. The flowchart of the process which mutually uses the functional information in Example 1. A detailed flowchart of the process of acquiring function information using an intent. FIG. 6 is a sequence diagram of an operation in which functional information is mutually used in the second embodiment. A detailed sequence diagram of a part of the sequence of FIG. FIG. 5 is a flowchart of a process for mutually using functional information in the second embodiment.

Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.

<Basic mechanism of Web Intents>
First, a basic mechanism related to Web Intents, which is an example of a mechanism for linking with an arbitrary Web service (or Web application) without using a dedicated API, will be described with reference to FIGS. 1 to 3. In the present invention, Web Intents is given as a specific example, but other similar mechanisms can be applied as a technique for linking with an arbitrary Web service (or Web application).

FIG. 1 is a diagram showing an overall configuration of Web Intents.
In FIG. 1, reference numeral 103 denotes a Web Intents service (hereinafter referred to as a service) that provides services and functions by using the Web Intents technology. Reference numeral 101 denotes a Web Intents client (hereinafter referred to as a client) that uses the service 103. Reference numeral 106 denotes a User Agent (user agent; hereinafter referred to as UA), which serves to pass the request from the client 101 to the service 103 and the result from the service 103 to the client. The UA 106 can be said to be a relay function for executing a request and passing data between the client 101 and the service 103. Further, in the UA 106, Web INT which is the function information for calling the providing function of the service 103 is registered.

In this mechanism, for example, the client 101 is a website on which data is managed and buttons for calling services are arranged, and the UA 106 is a web browser (web browser) that displays the website. Further, the service 103 is a linked website of the client 101 that receives and processes the data managed by the client 101 via the UA 106.

For example, when this mechanism is applied to an SNS (social networking service), the service 103 becomes a posting destination service that accepts postings of photos and comments managed by a client and constitutes a browsing site. If you compare social buttons such as "Like", "Check", and "Share" of an SNS site with the mechanism of Web Intents, the client 101 will be the site where the buttons are arranged, the UA106 will be the Web browser, and the service 103 will be "Good". It will be a posting service such as "Ne". When the service 103 provides a function and requires user authentication or an operation by the user, the user performs the operation on the UA 106.

The UA 106 can be realized by an operating system (OS) or an application running on an information processing terminal, in addition to a Web browser, as long as it has a function for linking with a service described later. Here, examples of the information processing terminal include a personal computer, a smartphone, a tablet computer, a car navigation device, and the like.

Regarding the service 103, in addition to the service provider on the Internet such as the above-mentioned posting destination service, a device such as a camera, a printer, or a scanner built in an information processing terminal can also be a service provider. As for the service 103, peripheral devices such as printers, scanners, and network cameras connected by a network, and home appliances such as refrigerators and televisions can also be service providers. Similarly, for the client 101, various devices and applications built in the information processing terminal, peripheral devices and home appliances on the network, programs running on the peripheral devices, and the like can also be users who call the service. The client 101, the UA 106, and the service 103 may operate in any combination thereof in the same system. Specifically, it is conceivable that a document editing application or the like having the same function as a web browser operates as a configuration including the client 101 and the UA 106. Further, any one of the client 101, the UA 106, and the service 103 may have a function of operating on the same device.

<Web Intents sequence diagram and data example>
FIG. 2 is a sequence diagram for explaining a basic operation related to service provision using Web Intents.

In S201, the UA 106 accesses the service 103 by a user operation. In S202, the service 103 returns an HTML (HyperText Markup Language) response including a registration markup for registering the function provided by the service to the UA 106 to the UA 106.

FIG. 3A is a diagram illustrating an HTML document returned from the service 103 to the UA 106 in S202. Hereinafter, the contents of the HTML document returned from the service 103 to the UA 106 will be described with reference to the example of FIG. 3A.

In the <intent> tag, function information for specifying the function provided by the service 103 and calling the function provided by the service 103 is described. The action indicates the classification information (category) of the provided function. That is, action indicates the classification information of what kind of function and service the provided function provides. The classification information of the provided function includes, for example, the classification information "Share" corresponding to the function of sharing data, the classification information "Edit" corresponding to the function of editing data, and the classification information corresponding to the function of browsing data. "View", classification information "Pick" corresponding to the function of acquiring data, classification information "Save" corresponding to the function of saving data, and the like are included. That is, in the above-mentioned functional information, as the classification information, for example, any one of Share, Edit, View, Pick, and Save is described.

type indicates the type of data or the like that can be handled by the provided function. That is, type indicates a data type or the like that can be handled for action. ref indicates the connection destination (URL) of the provided function. title indicates the title of the provided function. Also, the disposition indicates how the called provided function is displayed.

In the example of FIG. 3A, the category of the provided function is "share", the type of data that can be handled is "image data of all formats (*)", and the connection destination is "share.html". Is. The title is "Share image using e-mail". Furthermore, it shows that this function is displayed in a separate window via UA106.

Upon receiving the HTML response of S202, the UA 106 confirms with the user whether or not to register the function of providing the service 103 in the UA 106. For example, if the UA 106 is a Web browser, a pop-up window is displayed to prompt the user to select whether or not to register. When the user chooses to register this provided function as a Web Intent, the UA 106 executes a registration process for internally storing the information received in S202. Specifically, the information received in S202 is stored in the storage area of the information processing terminal on which the UA 106 operates, and is registered in the UA 106 as Web Intents.

In S203, the UA 106 accesses the client 101 by a user operation. In S204, the client 101 returns to the UA 106 an HTML document stating that the service 103 is to be used by the Web Intent. For example, when an image and a "share" button are displayed on a website as a client 101, the website contains an HTML document containing ECMAScript as shown in FIG. 3 (b), which is a processing request of the Web Intent. Return to UA106.

FIG. 3B is a diagram illustrating an HTML document returned from the client 101 to the UA106 in S204. Hereinafter, the contents of the HTML document returned from the client 101 to the UA 106 will be described with reference to the example of FIG. 3 (b).

ECMAScript indicates that when a button with the ID "share-photo" in HTML is clicked, it will execute the specified anonymous function. The anonymous function first creates a new INT object and calls the startActivity () function with this as an argument. When this function is executed, the UA 106 extracts from the Web Intents registered in itself the ones whose action and type match the specified Web Intent object, and requests the user to select by displaying a list. Further, the UA 106 acquires the image data possessed by the client 101 by executing the getImageFrom () function called in the anonymous function.

In S204, the UA 106 receives the HTML document transmitted from the client 101 and displays a screen based on the HTML document. When the UA106 detects that the user presses the "share" button on the screen in S205, it executes ECMAScript for starting Web Intents as described above, and in S206, acquires the image data possessed by the client 101. Further, when the pressing of the "Share" button is detected in S205, the UA 106 displays a list of Web Intents registered in itself. When the UA 106 detects that the user has selected the Web Intent indicating the providing function of the service 103 from this list, the UA 106 makes an HTTP request (Web Intent processing request) to the service 103 that provides the selected providing function in S207. Send. At that time, the UA 106 includes the contents of the Web Intent object created by ECMAScript in FIG. 3B in the transmission data.

When the service 103 receives the HTTP request transmitted from the UA 106 in the above S207, the service 103 takes out the Web Client object from the HTTP request in the S208 and interacts with the user via the UA 106 to provide the selected function (here). Then, the use of the image data of the client 101 (“sharing”) is realized.

For example, a user visits a site provided with a Web Intents call button of a web storage (client 101) that manages photo data with a Web browser (UA106), and presses the button. Then, the Web browser (UA106) displays a pop-up window including a list of registered services. If the user selects the Webmail function as a service in the pop-up window, the site that provides the function is displayed in a separate window, and as a result of processing, a new mail with photo data attached is created on that window. .. This allows the user to send an email.

When the processing related to the providing function is completed, the service 103 returns a response including ECMAScript for transmitting the processing result to the client 101 to the UA 106 in S209. Upon receiving the response in S209, the UA 106 executes ECMAScript included in the response in S210 and calls the callback function onSuccess () specified by the argument of the startActivity () function in S205. In S211 the UA 106 returns the processing result to the client 101 by the callback function onSuccess ().

Through the above processing, the client 101 can call the Web Intents function (“sharing” of the image in this example) provided by the service 103 via the UA 106.

<UI example of information processing terminal in this example>
FIG. 4 is a diagram showing a UI example of an information processing terminal showing an embodiment of the present invention.
In FIG. 4, 501 shows an information processing terminal such as a normal mobile terminal or a smartphone. An OS (operating system) such as android (registered trademark), which is a platform developed for mobile information terminals, is installed in the information processing terminal 501.

In the example of FIG. 4, a plurality of Web browsers (browserA, browserB, browserC) are installed as application programs in the information processing terminal 501. Each of these Web browsers corresponds to UA106 in FIG. 1, and Web Intents can be used respectively. That is, the information processing terminal 501 is provided with a plurality of Web Intents relay functions.

When the user discovers the service corresponding to 103 in FIG. 1 when using the Web browser, the user registers the service in the Web browser as necessary. The list of a plurality of services managed by the Web browser is for each Web browser. Therefore, the Web Intents registered in the Web browser are usually different for each Web browser.

Further, in this embodiment, a smartphone-type information processing terminal as shown in FIG. 4 will be used for description, but there is no limitation on the form of the information processing terminal as a platform, and a general computer (for example, a personal computer) can be used. The present invention is also applicable.

<Hardware configuration example of client 101 and service 103>
FIG. 5 is a block diagram showing a hardware configuration example of the client 101 and the service 103 in FIG.
The client 101 and the service 103 can be configured by a general-purpose computer or the like. The client 101 and the service 103 include a CPU 602, a ROM 603, and a RAM 604. The CPU 602 collectively controls the entire device by reading and executing a program stored in the ROM 603 or the storage device 608 described later. The ROM 603 is a read-only memory for storing a boot program required for booting the system. The RAM 604 is a working memory required when executing a program on the CPU 602.

The network interface (Network I / F) 605 communicates via the network (Network). The display control unit 606 controls the display of the display device 609. For example, the display control unit 606 controls the screen display for managing the Web server and the like. The display device 609 displays the output signal controlled by the display control unit 606 to the operator who is the Web server administrator. The input control unit 607 controls the input signal received from the input devices 610 and 611. The input device 610 is, for example, a pointing device such as a mouse, and the input device 611 is a keyboard or the like, and receives input from an operator.

The storage device 608 is a non-volatile storage device such as a magnetic disk or a flash memory that stores a program executed by the CPU 602 and various information. In the case of the client 101, the storage device 608 also stores the content information and the like provided by the client 101. Further, in the case of the service 103, the storage device 608 also stores data and programs necessary for the service 103 to provide a function.

The processing of the client 101 and the service 103 shown in this embodiment is realized by the CPU 602 of the client 101 and the service 103 reading and executing the program stored in the storage device 608, respectively.

<Hardware configuration example of information processing terminal 501>
FIG. 6 is a block diagram showing a hardware configuration of the information processing terminal 501, and UA106 in FIG. 1 is executed on this hardware. The information processing terminal 501 shown in FIG. 6 is an ordinary mobile terminal or smartphone, and an operating system for a small terminal and a program for controlling a call and data communication are running.

Each component of the hardware of the information processing terminal 501 is connected to the system bus 801. The ROM 803 stores an operating system in the information processing terminal 501, an application for controlling a call and data communication, and the like, and is read and executed by the CPU 802. Applications that control data communication include, for example, Mail software and Web browsers.

The RAM 804 is a work memory area for executing a program. The RAM 804 is also a memory for temporarily storing Web page data acquired by the Web browser from the Web server, authentication information for accessing the Web service, and the like. The storage device 809 is a non-volatile storage device, and stores various operation mode settings and operation logs that need to be retained even after the information processing terminal 501 is restarted.

The network controller (Network Controller) 805 controls communication between the wireless LAN communication unit 811 for participating in the wireless LAN and the mobile phone data communication unit 812 for participating in the network provided by the mobile carrier. Generally, when the network controller 805 can participate in the wireless LAN network, the network controller 805 gives priority to the wireless LAN connection via the wireless LAN communication unit 811. When the information processing terminal 501 is out of the wireless LAN network area, the network controller 805 via the mobile phone data communication unit 812 participates in the wireless communication network provided by the mobile carrier.

The voice control unit 806 is mainly used when the call application is activated and the user is making a call. The microphone / speaker 813 inputs / outputs voice data, and the voice control unit 806 mediates with the control program. The display control unit 807 controls the information output on the display 814 of the information processing terminal 501. The input control unit 808 controls the information instructed by the user via the buttons of the information processing terminal 501 and the touch panel 815. Using these voice control units 806, display control units 807, and input control units 808, the application on the information processing terminal 501 provides the user with network communication information and various information of the information processing terminal 501. The position detection control unit 810 acquires the position information of the information processing terminal 501 from the GPS sensor 816 and provides it to the operating system. These controls are controlled by an operating system powered by CPU 802.

The UA106 shown in this embodiment is realized by the CPU 802 of the information processing terminal 501 reading and executing the program stored in the ROM 803.

<Software configuration example of information processing terminal 501>
FIG. 7 is a block diagram showing a software configuration of the information processing terminal 501 in FIG. FIG. 7 mainly describes a technique related to issuing a Web Intents request of an application related to the present invention and a function related to mutual use of functional information using intents. Intent is a technique for transmitting and receiving data between arbitrary applications. This is a technology that can be used on android (registered trademark), which is a platform developed targeting personal digital assistants. Further, similar technology is implemented in other platforms, but in this embodiment, the technology for transmitting and receiving data between applications in the information processing terminal is called an intent.

In FIG. 7, 501 is the information processing terminal shown in FIG. Here, the information processing terminal 501 will be described as a mobile terminal or a smartphone. An operating system (hereinafter referred to as an OS) for controlling a device is generally operated in the information processing terminal, and is represented as an OS unit 901 in FIG. 7. Further, a plurality of applications can be installed on the information processing terminal 501. This application is represented as an application unit 902 in FIG. Although only one application unit is shown in FIG. 7, a plurality of applications are actually installed in the information processing terminal 501.

In the present invention, it is assumed that a plurality of applications operating as UA106 in FIG. 1 on the operating system of the information processing terminal 501 operate in the information processing terminal 501. In this embodiment, a Web browser will be used as an example of an application that operates as UA106, but any application that operates as UA106 may be used. For example, an application such as spreadsheet software may provide the functions of UA106. Further, the case where the OS operates as UA106 is also included in the present invention.

The application assumed in this embodiment is an application that can control Web Intents as a UA106, such as a Web browser, and at the same time, is an application that can send and receive data between applications. In addition to intents, there are Web Intents and the like as technologies for transmitting and receiving data between applications. In the first embodiment, an embodiment in which data is transmitted and received between applications by using an intent is shown. Further, in the second embodiment described later, an embodiment in which data is transmitted / received between applications using Web Intents will be shown. However, the application assumed here is not limited to Intents and Web Intents as long as data can be transmitted and received between arbitrary applications.

The OS unit 901 and the application unit 902 shown in FIG. 7 are realized by the CPU 802 of the information processing terminal 501 reading and executing the OS and the application program stored in the ROM 803.

First, the OS unit 901 will be described.
In the OS unit 901, 906 is a network control unit. The network control unit 906 controls the network controller 805 of FIG. Since the information processing terminal 501 is a small mobile terminal, it is assumed that it will be moved and used, and the network control unit 906 automatically connects to an accessible network according to the location. In addition, communication is performed to the outside in response to a communication request from the application unit 902. Further, the network control unit 906 responds to the network connection request from the outside and distributes the connection request to the appropriate application unit 902.

Reference numeral 904 is an intent information input / output unit, and reference numeral 905 is an application information storage unit. When the OS unit 901 receives an intent request from the application unit 902 together with information on an action or type (hereinafter, data type), the OS unit 901 requests the intent information input / output unit 904 for an application corresponding to the action and the data type. Upon receiving the intent request, the intent information input / output unit 904 acquires a list of applications corresponding to the received action and data type from the application information storage unit 905. Then, the intent information input / output unit 904 transmits the acquired list of applications to the application unit 902.

Further, 903 is a user input / output unit, which collectively manages the voice control unit 806, the display control unit 807, and the input control unit 808 of FIG. When the application unit 902 gives a display instruction to the user, the user input / output unit 903 displays on the display 814 via the display control unit 807. Further, when the user inputs an input via the touch panel 815, the user input / output unit 903 transmits the input signal controlled by the input control unit 808 to the application unit 902.

Next, the application unit 902 will be described.
The application unit 902 includes a service information management unit 908, a central processing unit 907, a service information detection unit 909, a service information input / output unit 910, and a service information storage unit 911.

907 is a central processing unit, which plays a central role as a Web browser. The basic role of the central processing unit 907 is UA106 in Web Intents. In addition, the central processing unit 907 also performs basic browsing processing, detection of service 103, and transmission / reception of data through an intent. Further, when the central processing unit 907 does not use the intent of the OS unit 901, the service information management unit 908 is used to acquire or provide the service information (functional information) of the Web Intents from another application. It is also possible. The service information management unit 908 will be described in the second embodiment described later.

The service information detection unit 909 detects the <intent> tag included in the Web page received from the service 103 at the time of access, and recognizes the function information for registering the function provided by the service 103. The service information input / output unit 910 controls the input / output of functional information to the service information storage unit 911. Information as shown in FIG. 8 is stored in the service information storage unit 911.

FIG. 8 is a diagram illustrating functional information managed by a Web browser as a UA.
For example, the example shown in FIG. 8 includes the name 1401 of the provided function provided by the service, the URI1402 that accepts the provided function by the service, the action 1403 when accepting the Web Intents request, the data type (type) 1404, and the like. The information is stored in the service information storage unit 911.

Hereinafter, the operation of each module of the application unit 902 will be briefly described.
A user uses a Web browser (corresponding to UA106), which is an application of the information processing terminal 501, to access a certain service (Web site) using the mechanism of Web Intents. Then, the service information detection unit 909 of the application unit 902 detects the <intent> tag included in the Web page received from the service at the time of access, and the function information for registering the function provided by the service (Web Intents service information). Recognize. Upon recognizing the function information of the accessed service, the central processing unit 907 asks the user via the user input / output unit 903 to select whether or not to register this function information as Web Intent. Here, when the registration is instructed by the user, the central processing unit 907 issues an instruction to the service information input / output unit 910 to store the function information specified by the above <intent> tag. When the service information input / output unit 910 receives the storage instruction of the function information, the service information input / output unit 910 stores the function information in the service information storage unit 911.

Further, when the user requests the service for processing, the central processing unit 907 acquires the function information from the service information storage unit 911 via the service information input / output unit 910. Then, the central processing unit 907 displays the list of the acquired function information, and transmits the Web Intents processing request and the content information to the service corresponding to the function information selected from the list.

If there is no function information corresponding to the function that the user wants to use in the list of function information acquired from the service information storage unit 911, the Web browser uses the intent to provide the function information from another Web browser. Can be obtained. In this case, the central processing unit 907 of the Web browser issues a request to the intent information input / output unit 904 of the OS unit 901 to acquire a list of applications that can provide functional information. Then, the central processing unit 907 receives a list of applications that provide functional information as a result of the request. When the user selects an arbitrary application from the list of the applications, the central processing unit 907 requests the selected application to acquire the function information by using the intent, and acquires the function information.

Further, when the central processing unit 907 receives a function information provision request (acquisition request) from an external application by an intent, the central processing unit 907 acquires the function information from the service information storage unit 911 via the service information input / output 910. Then, the central processing unit 907 provides the acquired functional information to the external application.

<Example of sequence diagram for mutual use of functional information>
FIG. 9 is a sequence diagram illustrating an operation of referring to and using a list of function information managed by another Web browser when a user uses Web Intents using a certain Web browser. Note that FIG. 9 is an extension of the basic sequence of Web Intents described with reference to FIG. In FIG. 9, 902 represents a Web browser in the information processing terminal 501, and the role of Web Intents is UA. In FIG. 9, a plurality of UAs exist, the Web browser on the side requesting the function information is User Agent.1 (hereinafter, UA.1), and the Web browser on the side providing the function information is User Agent.2 (hereinafter, UA. 2).
Note that FIG. 10 is a diagram illustrating a screen displayed on the UA.1 Web browser screen.
11 and 12 are detailed sequence diagrams of a part of the sequence of FIG. 9.

In S1001 of FIG. 9, UA.1 accesses the client 101 in response to a user instruction. Then, in S1002, UA.1 receives HTML information including ECMAScript whose processing is started by the "Share" button from the client 101. Then, on the UA.1 Web browser screen, a screen as shown in FIG. 10A is displayed. On this screen, it is possible to issue a request to share the photo content information to any service by providing the photo content information and pressing the "Share" button 1101.

When the user instructed to use the service by pressing the "Share" button 1101 in S1003, UA.1 detects that the "Share" button 1101 has been pressed. When UA.1 detects that the "Share" button 1101 is pressed and determines that the user has instructed to use the service, it shifts the process to S1004. In S1004, UA.1 acquires a list of function information registered in the service information storage unit 911 (FIG. 7) based on the action indicating sharing for the photo content and the data type of the file, and obtains the acquisition. A selection screen as shown in FIG. 10 (b) including a list (list) of the function information is displayed and presented to the user.

On the screen displayed by S1004, as shown in FIG. 10B, the function information list 1102 and the link button 1103 described as "service import" that can refer to the function information registered in other UAs are described. Is displayed. Further, on this screen, an OK button 1104 for determining the selected function information and a Cancel button 1105 for canceling the selection of the function information are also displayed.

When the user does not have the function information to be used in the function information list 1102 on the screen as shown in FIG. 10B displayed in S1004, the user uses the function information registered in another browser. Can be done. In this case, the user presses the "service import" link button 1103 on the screen of FIG. 10B in S1005.

When UA.1 detects that the "service import" link button 1103 is pressed, it searches the information processing terminal 501 for another application that can provide functional information (S1006 to S1007). In the first embodiment, as an example, a processing sequence for acquiring functional information using an intent of android (registered trademark) will be described. Similar to Web Intents, the intent enables data transfer between appropriate applications by the OS mediating the data type to be transferred and the action of what to do with the data.

Hereinafter, S1006 to S1007 will be described in detail with reference to FIG. 11A.
As shown in FIG. 11A, in S1006, UA.1 sets the data type to "application / Web Intents Service", sets the action to "pic" to search for an application that can request data provision, and sets the OS unit. Issue an intent request to 901. In S1007, the OS unit 901 acquires a list of applications that can provide the function information of the service from the application information storage unit 905 by intent. Then, it is returned to UA.1 as a list of UAs via the intent information input / output unit 904.

The UA.1 that has acquired the UA list in S1007 displays a screen including the UA list in S1008 and presents it to the user. On this screen, the user selects UA.2 when he / she wants to use the function information registered in a certain UA (here, UA.2). When UA.1 detects that UA.2 is selected in S1009, UA.1 issues a request for acquisition of a list of function information registered in UA.2 in S1010.

Hereinafter, S101 to S1013 will be described in detail with reference to FIG. 11 (b).
As shown in FIG. 11B, in S1010, UA.1 makes an intent call to UA.2, sets the data type to "application / Web Interests Service", and requests processing with the action set to "pick". To do. In response to this request, UA.2 provides UA.1 with a list of functional information that can be provided as an interim response. The transmission / reception of this data is actually performed via OS901, but here, it will be simplified.

When UA.1 receives the function information list from UA.2 in S1011, the UA.1 displays the function information list (list) of UA.2 in S1013. An example of the screen displayed on the information processing terminal 501 in S1013 is shown as FIG. 10 (c). In FIG. 10C, the parent-child relationship between the list of UAs and the list of functional information managed by the UAs is displayed so as to be understood. For example, in FIG. 10 (c), "PhotoServiceD" and "PhotoServiceE" are displayed as functional information managed by "browserB" as a UA (1106). However, the parent-child relationship may not be displayed, and only the list of function information not registered in UA.1 may be displayed as it is. The user confirms the selection of the function information by pressing the OK button 1107 in the state where any one or a plurality of function information is selected. At this time, UA.1 detects that the function information has been selected.

The process of detecting the selection of the UA shown in S1009 to S1013 and acquiring and displaying the function information list registered in the selected UA is repeated the number of times the user selects the UA (S1012). ..

When UA.1 detects in S1014 that the function information registered in UA.2 is selected from the function information list, in S1015, the selected function information is selected with respect to UA.2. Is issued to acquire the above-selected function information (S10115 to S1016).

Hereinafter, S1015 to S1016 will be described in detail with reference to FIG. 12A.
As shown in FIG. 12A, in S1015, UA.1 specifies the function information to be acquired by using the intent "pick", and uses the intent mechanism to change to UA.2. Issue an acquisition request to it. In response to this acquisition request, UA.2 transmits the specified function information in S1016 as a response to the intent of 1015. The function information transmitted here is a definition file in which the function information is defined, as shown in FIG.

FIG. 13 is a diagram illustrating a definition file of functional information transmitted from UA.2 in S1016.
As shown in FIG. 13, in the function information definition file, the name of the provided function, the URI for accepting the provided function, the action when providing the provided function, and the data type (type) are described. ing.

Hereinafter, the description of the sequence diagram of FIG. 9 will be returned to.
When UA.1 acquires the information necessary for registering the function information in S1016, the UA.1 registers the acquired function information in itself in S1017. That is, the central processing unit 907 of UA.1 stores the function information acquired in S1016 in the service information storage unit 911 via the service information input / output unit 910. After that, in S1018, UA.1 displays the selection screen as shown in FIG. 10B again and presents the list of the function information registered in itself to the user. When UA.1 detects in S1019 that a certain function information has been selected from the function information list displayed in S1018 by the user, the process proceeds to S1020. In S1020, UA.1 transmits an HTTP request (Web INTent processing request) for processing "share" to the service (here, service 103) corresponding to the selected function information.

Hereinafter, S1020 to S1021 will be described in detail with reference to FIG. 12B.
As shown in FIG. 12B, in S1020, UA.1 issues a Web Intents processing request of the data type "image / jpg" and the action "share" to the service 103. In response to the Web Intents processing request, the service 103 executes the processing for the Web Intents processing request in S1021 and returns the execution result to UA.1 as a response. Then, UA.1 receives the response of S1021.

<Example of UA processing flowchart of Example 1>
FIG. 14 is a flowchart illustrating a software process from when the UA receives ECMAScript from the client to when the function information is acquired from the outside and the request is issued to the service. The processing of this flowchart shows a part of the processing of the software in the information processing terminal 501 shown in FIG. 7. The processing of this flowchart is realized by the CPU 802 of the information processing terminal 501 expanding the program stored in the ROM 803, the storage device 809, or the like into the RAM 804 as needed and executing the program.

In S1701, when the network control unit 906 of the information processing terminal 501 receives HTML including ECMAScript for issuing a Web Intents request from the client 101, the process proceeds to S1702.

In S1702, the central processing unit 907 configures a screen based on the received HTML information, displays the screen as shown in FIG. 10A via the user input / output unit 903, and presents the received information to the user. The process proceeds to S1703. In S1703, the central processing unit 907 determines whether or not a Web Intents request issuance instruction has been received from the user by operating the screen. When the central processing unit 907 detects that the "share" button 1101 is pressed, it determines that the Web Intents request issuance instruction has been received.

When it is determined that the Web Intents request issuance instruction has not been received (No in S1703), the central processing unit 907 returns the processing of S1703 and waits for the issuance instruction from the user. Although not shown, when a request to move to another Web page is received according to a user's instruction, the central processing unit 907 deviates from the processing of this flowchart and performs processing according to the request.

On the other hand, when it is determined that the Web Intents request issuance instruction has been received (Yes in S1703), the central processing unit 907 proceeds to S1704. In S1704, the central processing unit 907 inquires the service information input / output unit 910 to register the function information corresponding to the Web Intents request. If the corresponding function information is registered here, the central processing unit 907 displays the list 1102 of the function information as shown in FIG. 10B via the user input / output unit 903 and presents it to the user. .. Then, the process proceeds to S1705.

In S1705, the central processing unit 907 determines whether or not the "service import" link button 1103 is pressed on the screen shown in FIG. 10B. Then, when it is determined that the "service import" link button 1103 has been pressed (Yes in S1705), the central processing unit 907 proceeds to S1706. In S1706, the function information list acquisition / registration process is executed. The details of S1706 in Example 1 are shown in FIG. 15 described later. Then, when the processing of S1706 is completed, the central processing unit 907 proceeds to S1704 and displays a selection screen (screen as shown in FIG. 10B) of the list of functional information including the information acquired in S1706. To do.

On the other hand, if it is determined that the "service import" link button 1103 has not been pressed (No in S1705), the central processing unit 907 proceeds to S1707. In S1707, when the central processing unit 907 detects the user's selection of functional information, the central processing unit 907 advances the processing to S1708. In S1708, the central processing unit 907 creates a Web Intents request using the content information for which the issuance instruction was issued in S1703, and proceeds to process in S1709. In S1709, the central processing unit 907 issues the Web Intents request created in S1708 to the service corresponding to the function information selected and detected in S1705, and ends the processing of this flowchart.

<Flowchart of function information list acquisition / registration process>
FIG. 15 is a flowchart showing details of the function information list acquisition / registration process (S1706 in FIG. 14) in the first embodiment. The processing of this flowchart is realized by the CPU 802 of the information processing terminal 501 expanding the program stored in the ROM 803, the storage device 809, or the like into the RAM 804 as needed and executing the program.

When the function information list acquisition / registration process shown in S1706 of FIG. 14 is started (S1721), the central processing unit 907 proceeds to S1722. In S1722, the central processing unit 907 issues an intent request to the OS unit 901 with the action set to "pick" and the data type set to "Web Intents Service", and proceeds to processing in S1723.

In S1723, the central processing unit 907 determines whether or not the list of applications has been received as the response requested by the OS unit 901 in the intent. Then, when it is determined that the list of applications could not be received from the OS unit 901 (No in S1723), the central processing unit 907 proceeds to S1724. In S1724, the corresponding application is searched for in the intent, but the user is notified that the corresponding application does not exist in the device (for example, a message is displayed), and the function information list acquisition / registration process is terminated (S1735). ..

On the other hand, when it is determined that the list of applications has been received from the OS unit 901 (Yes in S1723), the central processing unit 907 proceeds to S1725. In S1725, the central processing unit 907 displays the list of applications acquired in S1723 on the display 814 via the user input / output 903 and presents it to the user. Then, the process proceeds to S1726.

In S1726, when the central processing unit 907 detects that one application has been selected by the user from the list of applications displayed in S1725, the processing proceeds to S1727. In S1727, the central processing unit 907 requests the application selected in S1726 to list the function information corresponding to the action "pick" and the data type "Web Insights Service" by using the intent. Then, the process proceeds to S1728.

In S1728, the central processing unit 907 receives the list of functional information requested in S1727 and proceeds to process in S1729. In S1729, the central processing unit 907 compares the list of function information received in S1728 with the function information already registered in the service information storage unit 911. As a result of the comparison, the central processing unit 907 excludes the already registered functional information and proceeds to the processing to S1730.

In S1730, the central processing unit 907 displays a list of functional information received via the user input / output unit 903 on the display 814. The screen displayed here is a screen as shown in FIG. 10 (c).

In the example of FIG. 10C, the central processing unit 907 displays a list of applications including "browserB" and "browserC" in S1726. The user touches "browserB" when acquiring the function information list registered in "browserB". Then, in S1730, the central processing unit 907 tilts the triangle on the left side of the screen showing the directory structure like 1108, and displays the function information list 1106 registered in "browserB". From this function information list 1106, the user selects one or more function information to be incorporated into the application.

Hereinafter, the description of the flowchart of FIG. 15 will be returned.
When the operation on the screen displayed in S1730 is detected, the central processing unit 907 proceeds to process in S1731. In S1731, the central processing unit 907 determines whether or not it has detected that the functional information to be captured has been selected from the functional information list displayed in S1730. Then, when it is determined that the function information is not selected and the application (for example, "browserC") is selected (No in S1731), the central processing unit 907 proceeds to S1726.

On the other hand, when it is determined that the function information to be captured has been selected from the function information list displayed in S1730 (Yes in S1731), the central processing unit 907 advances the processing to S1732. In S1732, the central processing unit 907 requests the selected function information from the application that manages the selected function information by using the intent, and advances the processing to S1733.

In S1733, the central processing unit 907 receives the selected function information from the target application and advances the processing to S1734. In S1734, the central processing unit 907 registers the function information received in the service information storage unit 911 via the service information input / output unit 910. Then, the acquisition / registration process of the function information is completed (S1735).

As shown above, when multiple UAs exist in the same information processing terminal, the function information of the service registered in the other UA is acquired from the other UA and used by using the intent mechanism. can do. Therefore, when a plurality of UAs exist in the same information processing terminal, it is possible to share the function information of the service registered separately in each UA.

In the first embodiment, for example, a configuration for acquiring functional information managed by another UA by using an intent of an android (registered trademark) platform has been described. On the other hand, in the second embodiment, the configuration of acquiring the function information from another UA by using the Web Intents of W3C without using the intent will be described.

The service information management unit 908 of the application unit 902 shown in FIG. 7 has an HTTP client function. The service information management unit 908 issues a function information acquisition request to an external application. Further, when the service information management unit 908 receives the function information from the external application in response to the acquisition request, the service information management unit 908 issues a WebIntents service information storage request to the service information input / output unit 910 via the central processing unit 907.

In addition, the service information management unit 908 has a function of the Web Intents service. When the service information management unit 908 receives a request for acquisition of function information from an external application together with action and data type information using the mechanism of Web Intents, the service information management unit 908 stores the service information via the central processing unit 907 and the service information input / output 910. Function information is acquired from the unit 911, and the acquired function information is provided to the requester.

<Examples of other sequence diagrams related to mutual use of functional information>
FIG. 16 is a sequence diagram illustrating another operation used by referring to a list of function information managed by another Web browser in the second embodiment. The same steps as in FIG. 9 are given the same step numbers. Hereinafter, only the parts different from FIG. 9 will be described.
Note that FIG. 17 is a detailed sequence diagram of a part of the sequence of FIG.

Since the processing of S1001 to S1005 is the same as that of FIG. 9, the description thereof will be omitted. In the information processing terminal 501 of the second embodiment, if there is no function information corresponding to the function that the user wants to use in the list of function information acquired from the service information storage unit 911, the function is performed from the local area network (Local Network) 1501. Search for applications or services that can provide information (hereinafter referred to simply as services). Specifically, in S1005, when the user detects that the user presses the "service import" link button 1103 (FIG. 10B), the UA.1 searches for a service for the Local Network 1501 in S1601. Run. This network search will be described in detail below with reference to FIG.

As shown in FIG. 17, UA.1 searches for a service for Local Network 1501 in S1601. Here, for example, a network service in the link local is searched by using a technology such as MulticastDNS in Bonjour, which is Apple's zero configuration technology.
At S1602, UA.1 receives a response from each service. In this embodiment, since the search is performed in the Local Network 1501, the response can be received not only from the service in the same information processing terminal but also from the service within the reach of the network.

Next, in S1603, UA.1 detects and lists the services that provide "application / Web Elements Service" as the data type and "pic" as the action from the services that received the response in S1602. At this time, if the information required for detection is insufficient, each service that received the response in S1602 may be accessed and acquired. By such processing, it is possible to search for a service that can provide functional information existing in the local area network.
Next, in S1604, UA.1 displays the list of services detected in S1603 and presents it to the user, and proceeds to process in S1009. Subsequent processing is the same as in FIG. 9, and the description thereof will be omitted.

<Flowchart of function information list acquisition / registration process of Example 2>
FIG. 18 is a flowchart showing details of the function information list acquisition / registration process (S1706 in FIG. 14) in the second embodiment. The processing of this flowchart is realized by the CPU 802 of the information processing terminal 501 expanding the program stored in the ROM 803, the storage device 809, or the like into the RAM 804 as needed and executing the program.

When the function information list acquisition / registration process shown in S1706 of FIG. 14 is started (S1741), the central processing unit 907 instructs the service information management unit 908 to execute the process of S1742. In S1742, the service information management unit 908 searches for an application or service (hereinafter, simply a service) that provides a function using the mechanism of Web Intents to the Local Network 1501 (S1601 in FIGS. 16 and 17). Corresponds to S1604). The search target is a service whose action is "pick" and whose data type is "Web Elements Service". The search request is issued by using a service search protocol such as multicastDNS used by Apple's Bonjour or the like.

Next, in S1743, the service information management unit 908 determines whether or not one or more corresponding services have been found as a result of the search in S1742. Then, when the service information management unit 908 determines that the corresponding service could not be found (No in S1743), the process proceeds to S1744. In S1744, the service information management unit 908 notifies the user (for example, displaying a message) that the corresponding service does not exist within the network search range as a result of searching for the service via the central processing unit 907. The function information list acquisition / registration process is terminated (S1755).

On the other hand, when the service information management unit 908 determines that one or more corresponding services have been found (yes in S1743), the process proceeds to S1745. In S1745, the service information management unit 908 displays a list of services acquired via the user input / output 903 in the above S1743 via the central processing unit 907, and advances the processing to S1746.

In S1746, when the service information management unit 908 detects that one service has been selected by the user from the list of services displayed in S1745, the service information management unit 908 proceeds to S1747 via the central processing unit 907. In S1747, the service information management unit 908 requests the service selected in S1746 to list the function information with the action "pick" and the data type "Web Intents Service" by using Web Intents. .. Then, the process proceeds to S1748.

In S1748, when the service information management unit 908 receives the function information list requested in S1747, the process proceeds to S1749. In S1749, the service information management unit 908 compares the list of function information received in S1748 with the function information already registered in the service information storage unit 911 via the central processing unit 907. As a result of the comparison, the function information already registered is excluded, and the process proceeds to S1750.

In S1750, the service information management unit 908 displays the list of the above-mentioned function information via the central processing unit 907 and the user input / output unit 903. Here, for example, a screen as shown in FIG. 10 (c) is displayed. The user touches "browserB" when acquiring a list of function information registered in a certain application. Then, the triangle on the left side of the screen showing the directory structure is tilted like 1108, and the function information list 1106 shown in S1750 is displayed. From this function information list 1106, the user selects one or more function information to be incorporated into the application.

The following returns to the explanation of the flowchart.
When the operation on the screen displayed in S1750 is detected, the service information management unit 908 proceeds to S1751 for processing. In S1751, the service information management unit 908 determines, via the central processing unit 907, whether or not it has detected that the function information to be imported has been selected from the function information list displayed in S1750. Then, when it is determined that the function information is not selected and the application (for example, "browserC") is selected (No in S1751), the service information management unit 908 proceeds to S1746.

On the other hand, when it is determined that the function information to be imported is selected from the function information list displayed in S1750 (Yes in S1751), the service information management unit 908 proceeds to S1752. In S1752, the service information management unit 908 requests the service that manages the selected function information for the function information by using Web intents, and proceeds to the process in S1753.

In S1753, the service information management unit 908 receives the selected function information from the target service, and proceeds to process in S1754. In S1754, the service information management unit 908 registers the function information received in the service information storage unit 911 via the central processing unit 907 and the service information input / output unit 910. Then, the acquisition / registration process of the function information is completed (S1755).

As shown above, when there are multiple UAs in the same information processing terminal, it is possible to acquire and use the function information of the service registered separately for each UA by using the mechanism of Web intents. Become.

In the first embodiment, an example is shown in which the functional information of the function provided by the service is mutually used between the applications inside the information processing terminal 501 by using the intent. Further, in the second embodiment, an example in which the application and the function information on the local network are mutually used by using Web Intents is shown.

However, when the user tries to acquire the function information, the mutual use partner does not necessarily have to be an application or service on the internal or local network, but may be a service on the Internet. For example, when registering function information in a Web browser as a UA, the above function information is also registered in a service that manages a list of function information on the Internet. Next, the user considers the use of the service with another Web browser, and presses the "service import" link button 1103 in FIG. 10 (b). Then, the Web browser connects to the service that manages the function information list on the Internet and issues a request for acquiring the function information list. By doing so, the mutual use destination of the function information list is possible even if the applications are not in the local network, and the same effect as in the first and second embodiments can be obtained.

As shown in the second embodiment, when an attempt is made to acquire a function information list using Web Intents, there are cases where the function information that can be used by a certain Web browser cannot be used by the own Web browser. For example, it is assumed that the URL of the function provided by the service existing in the information processing terminal 501 is the URL indicating the local loopback address (http://127.0.0.1/ ~). Even if the function information including such a URL is provided to the requesting Web browser, the provided Web browser (requesting Web browser) provides a service providing function corresponding to the function information via the network. Cannot be used.

In such a case, the Web browser on the providing side is configured to provide only the available function information according to the conditions of the side requesting the function information (requesting side). In addition, in the function provided by the service, not only the URL but also a special action or type may be specified and used. Therefore, the provider is configured to provide only the available functional information of the requester according to the action or type requested by the requester. With the above configuration, it is possible to prevent the function information that cannot be used by the requester from being unnecessarily registered as described above, and it is possible to improve the convenience of the user.

In addition, when the Web browser provided with the function information acquires the function information, it determines whether it can be used by itself, and if the function information is not available, the function information is displayed to the user as an option. A workaround such as not doing so is also conceivable. Similarly, with this configuration, it is possible to prevent the function information that cannot be used by the requester from being unnecessarily registered, and it is possible to improve the convenience of the user.

As described above, according to the present invention, it is possible to improve the usability of a new cooperation mechanism such as Web Intents currently proposed. For example, when a plurality of relay functions necessary for providing a mechanism for linking new web services such as Web Intents are provided in one information processing terminal, at least a part of the function information is appropriately shared among the relay functions. It is possible to do. As a result, the user does not have to repeat the registration of the same provided function for each relay function, and the convenience of the user is improved.

It should be noted that the structure and contents of the various data described above are not limited to this, and it goes without saying that the structure and contents are various depending on the intended use and purpose.
Although one embodiment has been described above, the present invention can take an embodiment as, for example, a system, an apparatus, a method, a program, a storage medium, or the like. Specifically, it may be applied to a system composed of a plurality of devices, or may be applied to a device composed of one device.
Further, all the configurations in which the above examples are combined are also included in the present invention.

(Other Examples)
The present invention is also realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiment is supplied to the system or device via a network or various storage media, and the computer (or CPU, MPU, etc.) of the system or device reads the program. This is the process to be executed.
Further, the present invention may be applied to a system composed of a plurality of devices or a device composed of one device.
The present invention is not limited to the above examples, and various modifications (including organic combinations of each example) are possible based on the gist of the present invention, and these are excluded from the scope of the present invention. is not. That is, all the configurations in which each of the above-described examples and modifications thereof are combined are also included in the present invention.

Claims (19)

An information processing terminal operating system and (OS) and the web browser is executed,
A receiving means for receiving page data provided by a website via a network,
A page display using the web browser based on the page data received from the website, including a description of data to be shared as part of the page data and shared objects to be displayed. Correspondingly , the first display means for displaying the page in which the shared object is arranged in the page , and
In response to a user instruction is issued to said shared object arranged in front Symbol the displayed page based on the page data is information that is managed by the OS, shared data to be the shared A second display means for displaying a selection screen for selecting one from a list containing the information related to the service for the purpose of
A sharing means for sharing the data to be shared provided by the website for a service corresponding to the selection according to the selection via the selection screen.
An information processing terminal characterized by having. Wherein as a function of a web browser, the information processing terminal according to claim 1, the user instruction to the shared object after being made, characterized in that the request for sharing data to be the shared is issued. Installation When the user instruction is performed for the previous SL shared object, by calling a predetermined function of the web browser is included in the description of the page data is managed by the OS, and, to the information processing terminal The information processing terminal according to claim 1 or 2 , wherein the selection screen is displayed based on information on a plurality of services. The information processing terminal according to claim 3 , wherein the description included in the page data includes a description using a navigator interface corresponding to the predetermined function for sharing the data to be shared. .. The information processing terminal according to any one of claims 1 to 4 , wherein the network is the Internet. The information processing terminal according to any one of claims 1 to 5 , wherein the OS is Android (registered trademark). The information processing terminal according to any one of claims 1 to 6 , wherein the information processing terminal is a smartphone. A control method in an information processing terminal in which an operating system (OS) and a web browser are executed.
A reception step that receives page data provided by the website via the network,
A page display using the web browser based on the page data received from the website, including a description of data to be shared as part of the page data and shared objects to be displayed. Correspondingly, the first display step of displaying the page in which the shared object is arranged in the page, and
In response to a user instruction for the shared object arranged in the page displayed based on the page data, the information managed by the OS and the data to be shared is shared. A second display step that displays a selection screen for selecting one from a list containing the information related to the service for
A sharing step of sharing the data to be shared provided by the website for a service corresponding to the selection according to the selection via the selection screen.
A control method characterized by having. The control method according to claim 8, wherein as a function of the web browser, a request for sharing the data to be shared is issued after a user instruction is given to the shared object. When a user instruction is given to the shared object, the web browser is managed by the OS and installed in the information processing terminal by calling a predetermined function included in the description of the page data. The control method according to claim 8 or 9, wherein the selection screen is displayed based on the information of the plurality of services. The control method according to claim 10, wherein the description included in the page data includes a description using a navigator interface corresponding to the predetermined function for sharing the data to be shared. The control method according to any one of claims 8 to 11, wherein the network is the Internet. The control method according to any one of claims 8 to 12, wherein the OS is Android (registered trademark). The control method according to any one of claims 8 to 13, wherein the information processing terminal is a smartphone. On the computer running the web browser,
A page displayed using the web browser based on the page data provided by the website received from the website via the network, and should be displayed as data to be shared as a part of the page data. Information managed by the operating system (OS) in response to user instructions for the shared object placed within the page that is displayed in response to the inclusion of a description of the shared object. A step of displaying a selection screen for selecting one from a list including the information related to the service for sharing the data to be shared.
In response to the selection via the selection screen, the step of sharing the data to be shared provided by the website to the service corresponding to the selection, and
A program to execute. The program according to claim 15, wherein as a function of the web browser, a request for sharing the data to be shared is issued after a user instruction is given to the shared object. When a user instruction is given to the shared object, the web browser is managed by the OS and installed on the computer by calling a predetermined function included in the description of the page data. The program according to claim 15 or 16, wherein the selection screen is displayed based on information of a plurality of services. The program according to claim 17, wherein the description included in the page data includes a description using a navigator interface corresponding to the predetermined function for sharing the data to be shared. The program according to any one of claims 15 to 18, wherein the network is the Internet.

Images