JP7163348B2 - System, information processing terminal, its control method and program, operating system. - Google Patents

Description

The present invention relates to technology for providing services using mechanisms such as Web Intents.

Conventionally, when delegating processing between web sites, the caller of the function needs to know how to call the API (application programming interface) of the function provider, REST interface, etc. was there. Therefore, in order to realize cooperation with different web sites, it is necessary for the calling side of the function to process the calling side according to the respective calling conventions. Also, in order for the caller to use the function, it is often necessary to authenticate the provider of the function. For this reason, the side using the function needs to hold the authentication information of the side providing the function, or use an authentication infrastructure such as SAML. However, once you have authentication information, it is necessary to manage those authentication information correctly and safely. users. Japanese Unexamined Patent Application Publication No. 2002-200000 discloses a technique for using services provided on the Web.

There is also a mechanism for cooperating with any web service (or web application) without using a dedicated API. As an example, a mechanism called Web Intents has been proposed in which a service receiver and a service provider are loosely coupled by runtime late binding and their cooperation is realized.

JP 2009-199369 A

In a new cooperation mechanism such as WebIntents described above, a user agent (UA) processes an HTML document containing markup for registering function information of the provided function in order to use the function provided by the service of the mechanism. and register the function information as Web Intent. A UA can connect to a service using its registered function information and request execution of a provided function. However, if the information processing terminal has a plurality of relay functions, the function information is registered and managed individually for each relay function. Therefore, even if certain function information is registered in a certain relay function, the function information cannot be used from other relay functions. Therefore, even if the function information is the same, the user has to repeat the registration process for each relay function, which is not always convenient. Therefore, it can be said that there will be a demand for various improvements in order to improve the usability of requests for services using this Web Intent and registration of the Web Intent.

Accordingly, an object of the present invention is to flexibly improve the usability of a new cooperation mechanism such as Web Intents, which is currently being proposed.

The present invention provides a system that includes a website, and an information processing terminal that executes a web browser that can access the website via a network and an operating system (OS), wherein the website is the a providing means for providing a web browser with page data containing a description of data to be shared and a shared object to be displayed by the web browser, wherein the information processing terminal uses the web browser; a first control means for controlling display of the page on which the shared object is arranged based on the page data provided from the website; Select one from a list containing the names of a plurality of services that are installed in an information processing terminal , registered in the OS as shared destination candidates , and managed , and that correspond to information on the service. a second control means for controlling the display of a selection screen for sharing, a sharing means for sharing the data to be shared with a service corresponding to the selection according to the selection via the selection screen; characterized by having

ADVANTAGE OF THE INVENTION According to this invention, the improvement for improving usability is provided about the mechanism of new cooperation, such as Web Intents. More specifically, specific content such as text and images in the page that is intended by the website that provides the page data is transferred to the shared object in the page displayed based on the page data in the web browser. According to the operation, a service managed by an OS frequently used by the user of the information processing terminal can be selected as a sharing destination and easily shared.

The figure which illustrates the basic system configuration|structure of Web Intents. 4 is a sequence diagram illustrating an overview of basic operations of Web Intents; FIG. FIG. 4 illustrates Web Intents registration markup and processing requests. A UI example of an information processing terminal in which multiple browsers are installed. 4 is a diagram exemplifying the hardware configuration of a client and a service 103; FIG. FIG. 2 is a diagram exemplifying the hardware configuration of an information processing terminal including a UA; FIG. 4 is a diagram exemplifying the software configuration of an information processing terminal including a UA; FIG. 4 is a diagram exemplifying function information managed by a web browser; FIG. 10 is a sequence diagram of operations for mutual use of function information in the first embodiment; FIG. 4 is a diagram illustrating an example of a screen displayed on a web browser; FIG. 10 is a detailed sequence diagram of part of the sequence of FIG. 9; FIG. 10 is a detailed sequence diagram of part of the sequence of FIG. 9; 4 is a diagram exemplifying a definition file of function information; FIG. 6 is a flowchart of processing for mutual use of function information in the first embodiment; 4 is a detailed flowchart of processing for acquiring function information using an intent; FIG. 11 is a sequence diagram of operations for mutual use of function information in the second embodiment; FIG. 17 is a detailed sequence diagram of part of the sequence of FIG. 16; 10 is a flowchart of processing for mutual use of function information in the second embodiment;

EMBODIMENT OF THE INVENTION Hereinafter, the form for implementing this invention is demonstrated using drawing.

<Basic mechanism of Web Intents>
First, a basic mechanism regarding Web Intents, which is an example of a mechanism for cooperating with an arbitrary web service (or web application) without using a dedicated API, will be described with reference to FIGS. 1 to 3. FIG. In the present invention, Web Intents is given as a specific example, but it is also possible to apply other similar mechanisms as a technique for cooperating with any web service (or web application).

FIG. 1 is a diagram showing the overall configuration of Web Intents.
In FIG. 1, reference numeral 103 denotes a Web Intents service (hereinafter referred to as service) that provides services and functions using Web Intents technology. Reference numeral 101 denotes a Web Intents client (hereinafter referred to as client) that uses the service 103 . Reference numeral 106 denotes a UserAgent (user agent; hereinafter referred to as UA) that passes requests from the client 101 to the service 103 and passes results from the service 103 to the client. The UA 106 can be said to be a relay function for executing requests and passing data between the client 101 and the service 103 . Also, a Web Intent, which is function information for calling a function provided by the service 103, is registered in the UA 106. FIG.

In this mechanism, for example, the client 101 is a website that manages data and arranges buttons for calling services, and the UA 106 is a web browser that displays the website. The service 103 is a website linked to the client 101 that receives and processes 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 serves as a posting destination service that accepts posting of photos and comments managed by the client and constitutes a browsing site. If the social buttons such as "Like", "Check", and "Share" on SNS sites are compared to the mechanism of Web Intents, the client 101 is the site where the buttons are arranged, the UA 106 is the web browser, and the service 103 is "like". It will be a posting destination service such as. When the service 103 provides a function and user authentication or user operation is required, the user performs the operation on the UA 106 .

It should be noted that the UA 106 can be realized by an operating system (OS) or an application that operates on an information processing terminal other than a Web browser, as long as it has a function for cooperating with a service to be described later. Examples of information processing terminals include personal computers, smart phones, tablet computers, and car navigation devices.

As for the service 103, devices such as cameras, printers, and scanners built in information processing terminals can serve as service providers in addition to service providers on the Internet such as the posting destination service described above. As for the service 103, service providers can be peripheral devices such as printers, scanners, and network cameras connected via a network, and household appliances such as refrigerators and televisions. Similarly, with respect to the client 101, various devices and applications built in the information processing terminal, peripheral devices and home appliances on the network, programs running thereon, and the like can be users who call the service. Any combination of the client 101, UA 106 and service 103 may operate within the same system. Specifically, it is conceivable that a document editing application or the like having functions equivalent to those of a web browser operates as a configuration including the client 101 and UA 106 . Also, any one of the client 101, UA 106, and service 103 may be a function that operates on the same device.

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

In S201, the UA 106 accesses the service 103 by user's operation. In S202, the service 103 returns to the UA 106 an HTML (HyperText Markup Language) response including registration markup for having the UA 106 register the functions provided by itself.

FIG. 3A is a diagram illustrating an HTML document returned from the service 103 to the UA 106 in S202. The content of the HTML document returned from the service 103 to the UA 106 will be described below using the example of FIG.

The <intent> tag describes function information for identifying a function provided by the service 103 and calling the function provided by the service 103 . Action indicates classification information (category) of the provided function. That is, action indicates classification information of what kind of function and service the provided function provides. Note that the classification information of the provided functions includes, for example, classification information "Share" corresponding to the function of sharing data, classification information "Edit" corresponding to the function of editing data, and 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 function information, classification information such as Share, Edit, View, Pick, and Save is described as classification information.

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

In the example of FIG. 3A, the provided function category is "share", the type of data that can be handled is "image data in any format (*)", and the connection destination is "share.html". is. Also, the title is "Share image using e-mail". Furthermore, it indicates that this function is displayed in a separate window via the UA 106. FIG.

Upon receiving the HTML response in S202, the UA 106 confirms with the user whether or not the function provided by the service 103 is to be registered 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 to register. When the user selects to register this provided function as a Web Intent, the UA 106 executes registration processing for internally storing the information received in S202 above. Specifically, the information received in S202 is stored in the storage area of the information processing terminal on which the UA 106 operates, and registered in the UA 106 as Web Intents.

In S203, the UA 106 accesses the client 101 by user's operation. In S<b>204 , the client 101 sends back to the UA 106 an HTML document describing the use of the function (Web Intent) provided by the service 103 . For example, when an image and a "share" button are displayed on a website serving as the client 101, the website transmits an HTML document containing ECMAScript as shown in FIG. 3B, which is a Web Intent processing request. Return to UA 106 .

FIG. 3B is a diagram illustrating an HTML document returned from the client 101 to the UA 106 in S204. The content of the HTML document returned from the client 101 to the UA 106 will be described below using the example of FIG. 3(b).

ECMAScript indicates that when the button with the ID "share-photo" in the HTML is clicked, the specified anonymous function is executed. The anonymous function first creates a new Intent object and calls the startActivity( ) function with this as an argument. When this function is executed, the UA 106 extracts Web Intents that match the action and type of the specified Web Intent object from the Web Intents registered by itself, and displays a list of them to request the user to make a selection. Also, the UA 106 acquires the image data held by the client 101 by executing the getImageFrom( ) function called within the anonymous function.

At S204, the UA 106 receives the HTML document transmitted from the client 101 and displays a screen based on the HTML document. In S205, when the UA 106 detects that the user has pressed the "share" button on the screen, it executes ECMAScript for starting Web Intents as described above, and acquires image data held by the client 101 in S206. Also, upon detecting the pressing of the “Share” button in S205, the UA 106 displays a list of Web Intents registered to itself. When the UA 106 detects that the user has selected a Web Intent indicating a function provided by the service 103 from this list, in S207, the UA 106 sends an HTTP request (Web Intent processing request) to the service 103 that provides the selected function. 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.

Upon receiving the HTTP request sent from the UA 106 in S207, the service 103 extracts the Web Intent object from the HTTP request in S208, interacts with the user via the UA 106, and provides the selected provided function (here Then, use of image data of the client 101 (“sharing”) is realized.

For example, the user uses the Web browser (UA 106) to visit a site provided with a Web Intents call button of the Web storage (client 101) that manages photo data, and presses the button. Then, the web browser (UA 106) displays a pop-up window containing a list of registered services. If the user selects a web mail function as a service in the pop-up window, a 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 e-mail.

After completing the processing related to the provided function, the service 103 returns a response including ECMAScript for conveying the processing result to the client 101 to the UA 106 in S209. Upon receiving the response in S209, the UA 106 executes the ECMAScript included in the response in S210, and calls the callback function onSuccess() specified by the argument of the startActivity() function in S205. At S211, the UA 106 returns the processing result to the client 101 by the callback function onSuccess().

With the above processing, the client 101 can call the Web Intents function (“sharing” of images 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 denotes an information processing terminal such as a normal mobile terminal or smart phone. The information processing terminal 501 is installed with an OS (operating system) such as android (registered trademark), which is a platform developed for portable information terminals.

In the example of FIG. 4, a plurality of web browsers (browserA, browserB, browserC) are installed in the information processing terminal 501 as application programs. Each of these web browsers corresponds to the UA 106 in FIG. 1 and can use Web Intents. That is, the information processing terminal 501 has a plurality of Web Intents relay functions.

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

In addition, in this embodiment, a smartphone type information processing terminal as shown in FIG. 4 is used for explanation, 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 service 103 in FIG.
The client 101 and the service 103 can be composed of a general-purpose computer or the like. The client 101 and service 103 include CPU 602 , ROM 603 and RAM 604 . The CPU 602 reads out and executes programs stored in the ROM 603 and a storage device 608, which will be described later, to centrally control the entire apparatus. A ROM 603 is a read-only memory for storing a boot program required for system startup. A RAM 604 is a working memory required when the CPU 602 executes a program.

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

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

Note that 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 respectively reading and executing programs stored in the storage device 608 .

<Hardware Configuration Example of Information Processing Terminal 501>
FIG. 6 is a block diagram showing the hardware configuration of information processing terminal 501, and UA 106 in FIG. 1 is executed on this hardware. The information processing terminal 501 shown in FIG. 6 is a normal mobile terminal or smart phone, and an operating system for small terminals and a program for controlling telephone calls and data communication are running.

Each hardware component 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 and applications for controlling telephone calls and data communication, etc., which are read and executed by the CPU 802 . Applications that control data communication include, for example, Mail software and web browsers.

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

A network controller 805 controls communication of a wireless LAN communication unit 811 for joining a wireless LAN and a mobile phone data communication unit 812 for joining a network provided by a mobile carrier. In general, the network controller 805 gives priority to wireless LAN connection via the wireless LAN communication unit 811 when it is possible to participate in a wireless LAN network. Note that 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 running and the user is making a call. Audio data is input/output through the microphone/speaker 813, and the audio control unit 806 mediates with the control program. A display control unit 807 controls information output on the display 814 of the information processing terminal 501 . The input control unit 808 controls information specified by the user via the buttons of the information processing terminal 501 or the touch panel 815 . Applications on the information processing terminal 501 provide network communication information and various information of the information processing terminal 501 to the user by using the voice control unit 806 , the display control unit 807 , and the input control unit 808 . 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 running on the CPU 802 .

Note that the UA 106 shown in this embodiment is implemented by reading and executing a program stored in the ROM 803 by the CPU 802 of the information processing terminal 501 .

<Software Configuration Example of Information Processing Terminal 501>
FIG. 7 is a block diagram showing the software configuration of information processing terminal 501 in FIG. FIG. 7 mainly describes a technology related to Web Intents request issuance of an application related to the present invention and a function related to mutual use of function 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 for portable information terminals. Similar technology is also implemented on 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 smart phone. The information processing terminal generally runs an operating system (hereinafter referred to as OS) for controlling the device, which is represented as an OS section 901 in FIG. 7 . Also, a plurality of applications can be installed in the information processing terminal 501 . This application is represented as application section 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 .

The present invention assumes an environment in which a plurality of applications that operate as the UA 106 in FIG. In this embodiment, a web browser is used as an example of an application that operates as the UA 106, but any application that operates as the UA 106 may be used. For example, an application such as spreadsheet software may provide the functions of the UA 106 . Also, the case where the OS operates as the UA 106 is also included in the present invention.

The application assumed in this embodiment is an application that can control Web Intents such as a Web browser as the UA 106, and at the same time, is an application that can transmit and receive data between applications. Technologies for transmitting and receiving data between applications include Web Intents in addition to intents. Example 1 shows an example in which data is transmitted and received between applications using intents. A second embodiment, which will be described later, shows an embodiment in which data is transmitted and received between applications using Web Intents. However, the applications assumed here are not particularly limited to intents or Web Intents as long as they can transmit and receive data between arbitrary applications.

Note that the OS section 901 and the application section 902 shown in FIG. 7 are implemented by the CPU 802 of the information processing terminal 501 reading and executing the OS and application programs stored in the ROM 803 .

First, the OS section 901 will be described.
In the OS section 901, 906 is a network control section. A network control unit 906 controls the network controller 805 in FIG. Since the information processing terminal 501 is a small portable terminal, it is assumed to be used while moving, and the network control unit 906 automatically connects to an accessible network according to the location. Also, it communicates with the outside according to a communication request from the application unit 902 . Also, the network control unit 906 responds to network connection requests from the outside and distributes the connection requests to appropriate application units 902 .

904 is an intent information input/output unit, and 905 is an application information storage unit. When the OS unit 901 receives an intent request from the application unit 902 along with action and type (hereinafter referred to as data type) information, it requests the intent information input/output unit 904 for an application corresponding to the action and data type. Upon receiving an 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 . The intent information input/output unit 904 then transmits the obtained application list to the application unit 902 .

A user input/output unit 903 controls the voice control unit 806, the display control unit 807, and the input control unit 808 shown in FIG. The user input/output unit 903 performs display on the display 814 via the display control unit 807 when there is a display instruction from the application unit 902 to the user. Also, when the user makes an input via the touch panel 815 , the user input/output unit 903 transmits an 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 has 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 .

A central processing unit 907 plays a central role as a web browser. The basic role of this central processing unit 907 is the UA 106 in Web Intents. In addition, the central processing unit 907 performs basic browsing processing, detection of the service 103, transmission and reception of data through intents, and the like. When the intent of the OS unit 901 is not used, the central processing unit 907 uses the service information management unit 908 to acquire or provide Web Intents service information (function information) from other applications. is also possible. Note that the service information management unit 908 will be described in a second embodiment, which will be described later.

A service information detection unit 909 detects an <intent> tag included in a Web page received from the service 103 at the time of access, and recognizes function information for registering functions provided by the service 103 . The service information input/output unit 910 controls input/output of function information to/from 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 exemplifying function information managed by a web browser as a UA.
For example, in the example shown in FIG. 8, the name 1401 of the function provided by the service, the URI 1402 for receiving the function provided by the service, the action 1403 when receiving the Web Intents request, the data type 1404, etc. are included. Information is stored in the service information storage unit 911 .

The operation of each module of the application unit 902 will be briefly described below.
A user uses a web browser (compatible with the UA 106), which is an application of the information processing terminal 501, to access a certain service (website) 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 detects function information (Web Intents service information) for registering functions provided by the service. to 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 whether or not to register this function information as Web Intent. When the user instructs registration, the central processing unit 907 issues an instruction to the service information input/output unit 910 to store the function information specified by the <intent> tag. The service information input/output unit 910 stores the function information in the service information storage unit 911 upon receiving the instruction to store the function information.

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

If the list of function information acquired from the service information storage unit 911 does not contain the function information corresponding to the function that the user wants to use, the web browser uses the intent to retrieve 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 obtain a list of applications capable of providing function information. Then, the central processing unit 907 receives a list of applications that provide function information as a result of the request. When the user selects an arbitrary application from this application list, the central processing unit 907 requests the selected application to acquire function information using an intent, and acquires the function information.

When the central processing unit 907 receives a function information provision request (acquisition request) from an external application with an intent, the central processing unit 907 acquires 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 function 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 function information list managed by another web browser when a user uses a web browser to use Web Intents. 9, the basic sequence of Web Intents described in FIG. 2 is expanded. In FIG. 9, reference numeral 902 denotes a web browser within the information processing terminal 501, which serves as a UA as a role of web intents. In FIG. 9, there are multiple UAs, the web browser requesting the functional information is UserAgent.1 (hereinafter referred to as UA.1), and the web browser providing the functional information is UserAgent.2 (hereinafter referred to as UA. 2) do.
FIG. 10 shows an example of a screen displayed on the web browser screen of UA.1.
11 and 12 are detailed sequence diagrams of part of the sequence of FIG.

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

In S1003, when the user presses the "Share" button 1101 to instruct to use the service, UA.1 detects that the "Share" button 1101 has been pressed. When UA.1 detects that the "Share" button 1101 has been pressed and determines that the user has instructed to use the service, the process proceeds to S1004. At 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 of the photo content and the data type of the file. A selection screen such as that shown in FIG. 10B, which includes a list of function information that has been selected, is displayed and presented to the user.

As shown in FIG. 10B, the screen displayed in S1004 includes a list of function information 1102 and a link button 1103 indicating "Import Service" for referring to function information registered in another UA. is displayed. This screen also displays an OK button 1104 for confirming the selected function information and a Cancel button 1105 for canceling the selection of the function information.

If the user does not find the desired function information in the function information list 1102 on the screen as shown in FIG. can be done. In this case, the user presses the "service import" link button 1103 on the screen in FIG. 10B in S1005.

When UA.1 detects that the "service import" link button 1103 has been pressed, it searches for other applications capable of providing functional information in the information processing terminal 501 (S1006-S1007). In the first embodiment, as an example, a processing sequence for acquiring function information using an android (registered trademark) intent will be described. Intents, like Web Intents, enable data transfer between appropriate applications by mediating the data type to be transferred and the action of what to do with the data by the OS.

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

After acquiring the UA list in S1007, UA.1 displays a screen including the UA list and presents it to the user in S1008. The user selects UA.2 on this screen if he or she wants to use function information registered in a certain UA (here, UA.2). When UA.1 detects in S1009 that UA.2 has been selected, in S1010 UA.1 issues a request to obtain a list of function information registered in UA.2.

S1010 to S1013 will be described in detail below with reference to FIG. 11(b).
As shown in FIG. 11(b), in S1010, UA.1 makes an intent call to UA.2 and requests processing with the data type as "application/Web IntentsService" and the action as "pick". do. In response to this request, UA.2 provides UA.1 with a list of capability information it can provide as an intermediate response. Although this data transmission/reception is actually performed via the OS 901, the explanation is simplified here.

Upon receiving the function information list from UA.2 in S1011, UA.1 displays the function information list (list) of UA.2 in S1013. FIG. 10C shows an example of the screen displayed on the information processing terminal 501 in S1013. In FIG. 10C, the parent-child relationship between the list of UAs and the list of function information managed by the UAs is displayed so as to be understood. For example, in FIG. 10C, "PhotoServiceD" and "PhotoServiceE" are displayed as function 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 with one or more function information selected. At this time, UA.1 detects that function information has been selected.

The process of detecting the selection of a 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 has been selected from the function information list, in S1015 the selected function information is transferred to UA.2. is issued to acquire the selected function information (S10115-S1016).

S1015 and S1016 will be described in detail below with reference to FIG. 12(a).
As shown in FIG. 12(a), in S1015, UA.1 uses the intent "pick" to specify the function information to be acquired, and uses the intent mechanism to send UA.2 Issue an acquisition request to In response to this acquisition request, UA.2 transmits the specified function information as a response to the intent of 1015 in S1016. 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 exemplifying the function information definition file transmitted from UA.2 in S1016.
As shown in FIG. 13, the function information definition file describes the name of the provided function, the URI for accepting the provided function, and the action and data type when providing the provided function. ing.

The description of the sequence diagram in FIG. 9 will be returned to below.
When UA.1 acquires the information necessary for registering the function information in S1016, it 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, at S1018, UA.1 presents the list of function information registered to itself to the user again by displaying the selection screen as shown in FIG. 10(b). When UA.1 detects in S1019 that the user has selected certain function information from the function information list displayed in S1018, the process advances 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.

S1020 to S1021 will be described in detail below with reference to FIG. 12(b).
As shown in FIG. 12B, in S1020, UA.1 issues a Web Intents processing request of data type "image/jpeg" and action "share" to the service 103. As shown in FIG. In response to this Web Intents processing request, the service 103 executes 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 embodiment 1>
FIG. 14 is a flowchart illustrating software processing from when the UA receives ECMAScript from a client to when it acquires function information from the outside and issues a request to a service. It should be noted that the processing of this flowchart shows part of the processing of the software in the information processing terminal 501 shown in FIG. The processing of this flow chart is realized by the CPU 802 of the information processing terminal 501 developing programs stored in the ROM 803, the storage device 809, etc. into the RAM 804 as necessary and executing the programs.

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 advances to S1702.

In S1702, the central processing unit 907 composes a screen based on the received HTML information, displays a screen as shown in FIG. 10A through the user input/output unit 903, presents the received information to the user, The process advances to S1703. In S1703, the central processing unit 907 determines whether or not an instruction to issue a Web Intents request has been received from the user through a screen operation. Note that the central processing unit 907 determines that it has received an instruction to issue a Web Intents request when it detects that the "share" button 1101 has been pressed.

If it is determined that an instruction to issue a Web Intents request has not been received (No in S1703), the central processing unit 907 returns the process of S1703 and waits for an instruction to issue from the user. Although not shown, when receiving a request to move to another web page 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 determining that an instruction to issue a Web Intents request has been received (Yes in S1703), the central processing unit 907 advances the processing to S1704. In S1704, the central processing unit 907 inquires of the service information input/output unit 910 about registration of function information corresponding to the Web Intents request. If there is registration of the corresponding function information, the central processing unit 907 displays the function information list 1102 as shown in FIG. . Then, the process advances to S1705.

In S1705, the central processing unit 907 determines whether or not the "service import" link button 1103 has been pressed on the screen shown in FIG. 10B. If it is determined that the "service/import" link button 1103 has been pressed (Yes in S1705), the central processing unit 907 advances the processing to S1706. In S1706, function information list acquisition/registration processing is executed. Details of S1706 in the first embodiment are shown in FIG. 15 described later. After completing the processing of S1706, the central processing unit 907 advances the processing to S1704, and displays a function information list selection screen (such as the screen in FIG. 10B) including the information acquired in S1706. 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 advances the processing to S1707. In S1707, when the central processing unit 907 detects selection of function information by the user, the process advances 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 advances the process to 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 Processing>
FIG. 15 is a flowchart showing the details of the function information list acquisition/registration process (S1706 in FIG. 14) according to the first embodiment. The processing of this flow chart is realized by the CPU 802 of the information processing terminal 501 developing programs stored in the ROM 803, the storage device 809, etc. into the RAM 804 as necessary and executing the programs.

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

In S<b>1723 , the central processing unit 907 determines whether or not the application list has been received as a response to the intent request from the OS unit 901 . If it is determined that the application list could not be received from the OS unit 901 (No in S1723), the central processing unit 907 advances the processing to S1724. In S1724, the user is notified (for example, by displaying a message) that the corresponding application is not found in the device even though the intent is searched for, and this function information list acquisition/registration process is terminated (S1735). .

On the other hand, when determining that the application list has been received from the OS unit 901 (Yes in S1723), the central processing unit 907 advances the processing to S1725. In S1725, the central processing unit 907 displays the application list 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 the user has selected one application from the application list displayed in S1725, the process advances to S1727. In S1727, the central processing unit 907 uses the intent to request the application selected in S1726 to list the function information corresponding to the action "pick" and the data type "Web IntentsService". Then, the process advances to S1728.

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

At S<b>1730 , central processing unit 907 displays the list of function information received via user input/output unit 903 on display 814 . The screen displayed here becomes a screen like FIG.10(c).

In the example of FIG. 10C, the central processing unit 907 displays a list of applications consisting of "browserB" and "browserC" in S1726. When the user acquires the function information list registered in "browserB", the user touches "browserB". Then, in S1730, the central processing unit 907 tilts the triangle on the left side of the screen indicating the directory structure as indicated by 1108, and displays the function information list 1106 registered in "browserB". From this function information list 1106, the user selects one or a plurality of function information to be incorporated into the application.

Hereinafter, the description will return to the flowchart of FIG. 15 .
Upon detecting an operation on the screen displayed in S1730, the central processing unit 907 advances the process to S1731. In S1731, the central processing unit 907 determines whether or not it has detected that the function information to be acquired has been selected from the function information list displayed in S1730. If it is determined that an application (for example, “browserC”) has been selected without selecting function information (No in S1731), the central processing unit 907 advances the process to S1726.

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

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

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

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

The service information management unit 908 of the application unit 902 shown in FIG. 7 has HTTP client functions. A service information management unit 908 issues a function information acquisition request to an external application. Further, when the service information management unit 908 receives function information from an 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 .

Further, the service information management unit 908 has a function of Web Intents service. The service information management unit 908 stores service information via the central processing unit 907 and the service information input/output 910 when it receives a request to acquire function information together with action and data type information from an external application using the mechanism of Web Intents. The function information is acquired from the unit 911, and the acquired function information is provided to the request source.

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

The processing of S1001 to S1005 is the same as that of FIG. 9, so the description is 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 function information list acquired from the service information storage unit 911, the function is retrieved from the local area network (Local Network) 1501. Search for an application or service (hereinafter simply referred to as service) that can provide information. Specifically, in S1005, when UA.1 detects that the user has pressed the "service import" link button 1103 (FIG. 10(b)), in S1601 UA.1 searches the Local Network 1501 for a service. Run. This network search will be described in detail below with reference to FIG.

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

Next, in S1603, UA.1 detects and lists services that provide "application/Web IntentsService" as the data type and "pick" as the action from the services that received the response in S1602. At this time, if the information necessary for detection is insufficient, the information may be obtained by accessing each service that received a response in S1602. Through such processing, it is possible to search for a service capable of providing function information existing within the local area network.
Next, in S1604, UA.1 displays the list of services detected in S1603 and presents it to the user, and advances the process to S1009. The subsequent processing is the same as in FIG. 9, so the description is omitted.

<Flowchart of Function Information List Acquisition/Registration Processing of Embodiment 2>
FIG. 18 is a flow chart showing the details of the function information list acquisition/registration process (S1706 in FIG. 14) according to the second embodiment. The processing of this flow chart is realized by the CPU 802 of the information processing terminal 501 developing programs stored in the ROM 803, the storage device 809, etc. into the RAM 804 as necessary and executing the programs.

14 (S1741), the central processing unit 907 instructs the service information management unit 908 to execute the processing of S1742. In S1742, the service information management unit 908 searches the Local Network 1501 for an application or service (hereinafter simply referred to as service) that provides a function using the Web Intents mechanism (searches S1601 to S1601 in FIGS. 16 and 17). corresponding to S1604). The search target is a service having an action of "pick" and a data type of "Web IntentsService". The search request is issued using a service search protocol such as multicastDNS used in Apple Inc.'s bonjour.

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. When the service information management unit 908 determines that no corresponding service has been found (No in S1743), the process proceeds to S1744. In S1744, the service information management unit 908 notifies the user via the central processing unit 907 that, as a result of searching for a service, there is no corresponding service within the network search range (for example, by displaying a message), The function information list acquisition/registration process ends (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 the list of services acquired through the user input/output 903 in S1743 via the central processing unit 907, and advances the process to S1746.

In S1746, when the service information management unit 908 detects, via the central processing unit 907, that one service has been selected by the user from the service list displayed in S1745, the process advances to S1747. In S1747, the service information management unit 908 uses Web Intents for the service selected in S1746 to request a function information list with an action of "pick" and a data type of "Web IntentsService". . Then, the process advances to S1748.

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

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

Now, let us return to the description of the flowchart.
Upon detecting an operation on the screen displayed in S1750, the service information management unit 908 advances the process to S1751. In S1751, the service information management unit 908 determines, via the central processing unit 907, whether it has detected that the function information to be acquired has been selected from the function information list displayed in S1750. If it is determined that an application (for example, “browserC”) has been selected without selecting function information (No in S1751), the service information management unit 908 advances the process to S1746.

On the other hand, if it is determined that the function information to be acquired has been selected from the function information list displayed in S1750 (Yes in S1751), the service information management unit 908 advances the process to S1752. In S1752, the service information management unit 908 requests function information from the service managing the selected function information using Web intents, and advances the process to S1753.

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

As described above, when multiple UAs exist in the same information processing terminal, it is possible to obtain and use function information of services registered separately for each UA using the mechanism of Web intents. Become.

In the first embodiment, an example was shown in which intents are used to mutually use function information of functions provided by services between applications inside the information processing terminal 501 . In addition, in the second embodiment, an example of using Web Intents to mutually use an application and function information on a local network has been shown.

However, when the user attempts to acquire function information, the interoperable partner does not necessarily have to be an application or service on an internal or local network, and may be a service on the Internet. For example, when registering function information in a web browser as a UA, the function information is also registered in a service that manages a function information list on the Internet. Next, the user considers using a service on another Web browser, and presses the "service/import" link button 1103 in FIG. 10(b). The web browser then connects to a service that manages the function information list on the Internet and issues a function information list acquisition request. By doing so, mutual use of the function information list does not have to be between applications 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 trying to acquire a function information list using Web Intents, there are cases where function information that can be used by a certain web browser cannot be used by the own web browser. For example, assume 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 the URL is provided to the requesting web browser, the provided web browser (requesting web browser) cannot provide the service 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 usable function information according to the conditions of the side requesting the function information (requesting side). Moreover, in the function provided by the service, not only the URL but also a special action or type may be defined and used. Therefore, the provider is configured to provide only function information available to the requester according to the action or type requested by the requester. With the configuration as described above, it is possible to prevent unnecessary registration of function information that cannot be used by the request source, thereby improving convenience for the user.

Further, when the Web browser that receives 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 is also possible. With this configuration, similarly, it is possible to prevent unnecessary registration of function information that cannot be used by the requesting party, thereby improving convenience for 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, which is currently being proposed. For example, when multiple relay functions necessary for providing a new web service linkage mechanism such as Web Intents are provided in one information processing terminal, at least part of the function information is appropriately shared among the relay functions. make it possible to As a result, the user does not have to repeat the registration of the same provided function for each relay function, which improves user convenience.

It goes without saying that the configuration and content of the various data described above are not limited to this, and may be configured in various configurations and content according to the application and purpose.
Although one embodiment has been described above, the present invention can be embodied as, for example, a system, device, method, program, storage medium, or the like. Specifically, it may be applied to a system composed of a plurality of devices, or may be applied to an apparatus composed of a single device.
In addition, all configurations obtained by combining the above embodiments are also included in the present invention.

(Other examples)
The present invention is also realized by executing the following processing. That is, the software (program) that realizes the functions of the above-described embodiments is supplied to a 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.
Moreover, the present invention may be applied to a system composed of a plurality of devices or to an apparatus composed of a single 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 spirit of the present invention, and they are excluded from the scope of the present invention. is not. In other words, the present invention includes all configurations obtained by combining each of the above-described embodiments and modifications thereof.

Claims (43)

A system that includes a website and an information processing terminal that executes a web browser and an operating system (OS) that can access the website via a network,
the website has providing means for providing page data to the web browser containing a description of data to be shared and shared objects to be displayed by the web browser;
The information processing terminal
a first control means for controlling display of a page on which the shared object is arranged based on the page data provided from the website using the web browser;
A service corresponding to function information that is installed in the information processing terminal, registered in the OS as a shared destination candidate, and managed in response to a user instruction to the shared object. a second control means for controlling display of a selection screen for selecting one from a list including the respective names of a plurality of services corresponding to function information;
a sharing means for sharing the data to be shared with a service corresponding to the selection according to the selection through the selection screen;
A system characterized by comprising: 2. The system of claim 1, wherein the web browser is a function of issuing a request to share the data to be shared after a user instruction to the shared object is made. The display of the selection screen is controlled by the web browser calling a predetermined function included in the description of the page data when the user instructs the shared object. 3. The system according to Item 1 or 2. 4. The system of 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. 5. A system as claimed in any preceding claim, wherein the network is the Internet. 6. The system according to any one of claims 1 to 5, wherein said OS is Android (registered trademark). 7. The system according to any one of claims 1 to 6, wherein said information processing terminal is a smart phone. 8. A system according to any preceding claim, wherein the data to be shared is image data. 9. The system according to any one of claims 1 to 8, wherein the service information included in the list includes service information for using a printer. A control method in a system that includes a website, and an information processing terminal that executes a web browser and an operating system (OS) that can access the website via a network,
the website providing page data to the web browser containing a description of the data to be shared and the shared object to be displayed by the web browser;
The information processing terminal
a first control step of controlling display of a page on which the shared object is arranged, using the web browser, based on the page data provided from the website;
a service installed in the information processing terminal in response to a user instruction to the shared object , registered in the OS as a shared destination candidate , and managed; a plurality of services corresponding to information of the service ; a second control step for controlling the display of a selection screen for selecting one from a list containing the names of each of the services of
a sharing step of sharing the data to be shared with a service corresponding to the selection in response to the selection through the selection screen;
A control method characterized by having 11. The control method according to claim 10, wherein a request for sharing the data to be shared is issued after a user instruction to the shared object is given as a function of the web browser. The display of the selection screen is controlled by the web browser calling a predetermined function included in the description of the page data when the user instructs the shared object. 12. A control method according to Item 10 or 11. 13. The control method according to claim 12, wherein said description included in said page data includes a description using a navigator interface corresponding to said predetermined function for sharing said data to be shared. 14. The control method according to any one of claims 10 to 13, wherein said network is the Internet. 15. The control method according to any one of claims 10 to 14, wherein the OS is Android (registered trademark). 16. The control method according to any one of claims 10 to 15, wherein the information processing terminal is a smart phone. 17. A control method according to any one of claims 10 to 16, wherein said data to be shared is image data. 18. The control method according to claim 10, wherein the service information included in the list includes service information for using a printer. An information processing terminal that runs a web browser and an operating system (OS) that can access a website via a network,
a user to the shared object on a page displayed using the web browser based on page data provided by the website and containing a description of the data to be shared and the shared object to be displayed by the web browser; Each of a plurality of services corresponding to information of the service installed in the information processing terminal, registered in the OS as a shared destination candidate, and managed in response to the instruction. Control means for controlling display of a selection screen for selecting one from a list containing names;
a sharing means for sharing the data to be shared with a service corresponding to the selection according to the selection through the selection screen;
An information processing terminal characterized by having 20. Information according to claim 19 , wherein said description of said page data includes a predetermined function called by said web browser for displaying said selection screen in response to user instructions for said shared object. processing terminal. 21. The information processing terminal according to claim 20 , wherein said description included in said page data includes a description using a navigator interface corresponding to said predetermined function for sharing said data to be shared. . The information processing terminal according to any one of claims 19 to 21 , wherein the information processing terminal is a smart phone. 23. The information processing terminal according to claim 19 , wherein said data to be shared corresponding to said description included in said page data is image data. A control method for an information processing terminal on which a web browser and an operating system (OS) capable of accessing a website via a network are executed,
a user to the shared object on a page displayed using the web browser based on page data provided by the website and containing a description of the data to be shared and the shared object to be displayed by the web browser; A plurality of services corresponding to function information of the service installed in the information processing terminal in response to the instruction, registered in the OS as a shared destination candidate, and corresponding to the managed function information. controlling the display of a selection screen for selecting one from a list containing the names of each of the services of
responsive to a selection via the selection screen, sharing the data to be shared with a service corresponding to the selection;
A control method characterized by having 25. The control of claim 24 , wherein the description of the page data includes a predetermined function called by the web browser to display the selection screen in response to user instructions for the shared object. Method. 26. The control method according to claim 25 , wherein said description included in said page data includes a description using a navigator interface corresponding to said predetermined function for sharing said data to be shared. 27. The control method according to any one of claims 24 to 26 , wherein said information processing terminal is a smart phone. 28. A control method according to any one of claims 24 to 27 , wherein said data to be shared corresponding to said description contained in said page data is image data. In an information processing terminal running a web browser and an operating system (OS) that can access a website via a network, the computer:
a user to the shared object on a page displayed using the web browser based on page data provided by the website and containing a description of the data to be shared and the shared object to be displayed by the web browser; Corresponding to the functional information of the service, which is installed in the information processing terminal in response to the instruction, is registered in the OS as a candidate for the sharing destination, and corresponds to the managed functional information. controlling display of a selection screen for selecting one from a list containing respective names of a plurality of services;
responsive to a selection via the selection screen, sharing the data to be shared with a service corresponding to the selection;
program to run the 30. The program of claim 29 , wherein said description of said page data includes a predetermined function called by said web browser for displaying said selection screen in response to user instructions for said shared object. . 31. The program according to claim 30 , wherein said description included in said page data includes a description using a navigator interface corresponding to said predetermined function for sharing said data to be shared. 32. The program according to any one of claims 29 to 31 , wherein said information processing terminal is a smart phone. 33. A program according to any one of claims 29 to 32 , wherein said data to be shared corresponding to said description included in said page data is image data. An operating system for an information processing terminal installed with a web browser capable of accessing a website via a network,
a user to the shared object on a page displayed using the web browser based on page data provided by the website and containing a description of the data to be shared and the shared object to be displayed by the web browser; means for displaying, on a display means, information identifying each of a plurality of services installed in the information processing terminal and registered in the operating system as candidates for sharing destinations in response to an operation;
as means for sharing the data to be shared with one service in response to a user's selection of predetermined information identifying one service from information identifying each of the plurality of services An operating system to make it work. 35. An operating system as recited in claim 34, wherein said information is the name of a service. wherein said description of said page data includes a predetermined function called by said web browser to display information identifying each of said plurality of services in response to a user instruction to said shared object. 36. An operating system according to claim 34 or 35. 37. An operating system according to any one of claims 34 to 36, wherein said information processing terminal is a smart phone. 38. An operating system as claimed in any one of claims 34 to 37, wherein the data to be shared corresponding to the description contained in the page data is image data. An information processing terminal installed with a web browser that can access a website via a network and an operating system,
a user to the shared object on a page displayed using the web browser based on page data provided by the website and containing a description of the data to be shared and the shared object to be displayed by the web browser; means for displaying, on a display means, information identifying each of a plurality of services installed in the information processing terminal and registered in the operating system as sharing destination candidates in response to an operation;
means for sharing the data to be shared with one service in response to a user selecting information identifying one service from information identifying each of the plurality of services; An information processing terminal characterized by: 40. An information processing terminal according to claim 39, wherein said information is the name of a service. wherein said description of said page data includes a predetermined function called by said web browser to display information identifying each of said plurality of services in response to a user instruction to said shared object. The information processing terminal according to claim 39 or 40. 42. The information processing terminal according to any one of claims 39 to 41, wherein said information processing terminal is a smart phone. 43. An information processing terminal according to any one of claims 39 to 42, wherein said data to be shared corresponding to said description included in said page data is image data.

Images