JP6513244B2 - INFORMATION PROCESSING TERMINAL, CONTROL METHOD, AND PROGRAM - Google Patents

Description

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

  Conventionally, when delegating processing between WEB (web) sites, the side that calls the function needs to know how to call the function such as the API (application programming interface) or REST interface on 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. Also, in order for the side calling the function to use the function, authentication to the side providing the function is often required. For this purpose, the side using the function needs to hold the authentication information of the side providing the function and use the authentication infrastructure such as SAML. However, if you have authentication information, it is necessary to manage the authentication information correctly and safely, and in order to use the authentication infrastructure such as SAML, an agreement is required in advance between the provider of the function and the user, It was burdened by users of Patent Document 1 discloses a technology for using a service conventionally provided on the Web.

  There is also a mechanism that works with any web service (or web application) without using a dedicated API. As an example, a mechanism called Web Intents (Web Intents) has been proposed, in which the service receiving side and the providing side are loosely coupled by run-time delayed binding, and their cooperation is realized.

JP, 2009-199369, A

In the new collaboration scheme such as WebIntents described above, the user agent (UA) processes an HTML document containing the markup for registration of the feature information of the provision function in order to use the provision function provided by the service of the scheme. And register the function information as Web Intent. The UA can connect to the service using the function information registered in itself to request execution of the provided function. However, when there are a plurality of relay functions in the information processing terminal, registration processing of function information is performed individually for each relay function and managed individually. For this reason, even if certain function information is registered by a certain relay function, that function information can not be used from other relay functions. Therefore, even if the user has the same function information, it is necessary to repeat the registration process for each relay function, and it is not always convenient.
Therefore, with regard to the request for services using Web Intent and the registration of Web Intent, it can be said that various improvements for improving usability are required in the future.

  Therefore, the present invention aims to add a flexible improvement for improving usability to a new cooperation mechanism such as Web Intents currently proposed.

The present invention communicates via a network with a web site that provides page data including a description of data to be shared and shared objects to be displayed, and information on which an operating system (OS) and web browser are executed. A processing unit that displays, as a function of the web browser, a page including the shared object based on page data received from the website;
Request means for executing a request for function information from the web browser to the OS when a user instruction to the shared object is made via the displayed page; and receiving from the OS based on the request In response to providing means for providing a selection screen for selecting one of a plurality of functions as the function of the web browser using the function information to be selected, and the selection via the selection screen; And issuing means for issuing, as a function of the web browser, a request for sharing the data to be shared using a function corresponding to a selection.

  According to the present invention, when there are a plurality of relay functions for providing a new cooperation mechanism such as Web Intents in the information processing terminal, it is possible to appropriately share at least a part of the function information among the relay functions. I assume. As a result, the user does not have to repeat registration of the same function information for each relay function, and the convenience of the user is improved. Therefore, the usability can be improved with respect to the new cooperation mechanism such as the currently proposed Web Intents.

The figure which illustrates the basic system configuration of Web Intents. The sequence diagram which illustrates the outline | summary of the basic operation | movement of Web Intents. The figure which illustrates the markup for registration of Web Intents, and a processing request. Example UI of an information processing terminal with multiple browsers installed. The figure which illustrates the hardware constitutions of a client and service 103. FIG. The figure which illustrates the hardware constitutions of the information processing terminal containing UA. The figure which illustrates the software configuration of the information processing terminal containing UA. The figure which illustrates the function information managed by the web browser. FIG. 7 is a sequence diagram of an operation of mutually using function information in the first embodiment. The figure which illustrates the screen displayed on a web browser. FIG. 10 is a detailed sequence diagram of a portion of the sequence of FIG. 9; FIG. 10 is a detailed sequence diagram of a portion of the sequence of FIG. 9; The figure which illustrates the definition file of functional information. 6 is a flowchart of processing of mutually using function information in the first embodiment. The detailed flow chart of processing which acquires functional information using an intent. FIG. 10 is a sequence diagram of operations for mutually using function information in the second embodiment. FIG. 17 is a detailed sequence diagram of a portion of the sequence of FIG. 16; 10 is a flowchart of processing of mutually using function information in the second embodiment.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

<Basic structure of Web Intents>
First, a basic mechanism relating to Web Intents, which is an example of a mechanism for collaborating with an arbitrary web service (or web application) without using a dedicated API, will be described using FIGS. 1 to 3. In the present invention, Web Intents is given as a specific example, but it is also possible to apply another similar mechanism as a technology to cooperate 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 a service) that provides services and functions using the Web Intents technology. Reference numeral 101 denotes a Web Intents client (hereinafter, client) using the service 103. Reference numeral 106 denotes a UserAgent (user agent; hereinafter, UA) that is responsible for passing the request from the client 101 to the service 103 and passing the result from the service 103 to the client. The UA 106 can be said to be a relay function for executing a request or passing data between the client 101 and the service 103. Further, in the UA 106, Web Intent, which is function information for calling a providing function of the service 103, is registered.

  In the present system, for example, the client 101 is a website that manages data and arranges a button for calling a service, and the UA 106 is a web browser (web browser) that displays the website. Also, the service 103 is a web site of a collaboration destination of the client 101 that receives data processed by the client 101 via the UA 106 and processes the data.

  For example, when the present system is applied to an SNS (social networking service), the service 103 becomes a posting destination service that accepts posting of photos and comments managed by the client and configures a browsing site. If social buttons such as "Like", "Check" and "Share" of SNS site are compared with the mechanism of Web Intents, client 101 becomes a site where buttons are arranged, UA 106 becomes a web browser, service 103 is good It becomes post service such as "N". When the service 103 requires the user authentication or the user's operation to provide the function, the user performs the operation on the UA 106.

  Note that the UA 106 can also be realized by an operating system (OS) or an application operating on the information processing terminal, as well as the web browser, as long as it has a function to cooperate with a service described later. Here, examples of the information processing terminal include a personal computer, a smartphone, a tablet computer, and a car navigation device.

  In addition to the service provider on the Internet, the service 103 may be, for example, a device such as a camera, a printer, or a scanner built in the information processing terminal, besides the service provider on the Internet. In addition, with regard to the service 103, peripheral devices such as a printer, a scanner, and a network camera connected via a network, and household appliances such as a refrigerator and a television can also be service providers. Similarly, for the client 101, various devices and applications incorporated in the information processing terminal, peripheral devices and home appliances on the network, programs running thereon, 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 of them 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. Also, any of the client 101, the UA 106, and the 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 describing a basic operation regarding service provision using Web Intents.

  In S201, the UA 106 accesses the service 103 by the operation of the user. In S202, the service 103 sends back to the UA 106 an HTML (HyperText Markup Language) response including markup for registration for causing the UA 106 to register the function provided by itself.

  FIG. 3A illustrates the HTML document returned from the service 103 to the UA 106 in S202. The contents of the HTML document returned from the service 103 to the UA 106 will be described below using the example of FIG. 3A.

  In the <intent> tag, function information for specifying a function provided by the service 103 and for calling a function provided by the service 103 is described. action indicates classification information (category) of the provided function. That is, action indicates classification information of what function and service the providing function provides. The classification information of the provided function includes, for example, classification information "Share" corresponding to the function sharing data, classification information "Edit" corresponding to the function editing data, and classification information corresponding to the function browsing data It includes “View”, classification information “Pick” corresponding to the function of acquiring data, and classification information “Save” corresponding to the function of storing data. That is, in the function information, for example, classification information of any one of Share, Edit, View, Pick, and Save is described as classification information.

  type indicates the type of data that the provided function can handle. 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. Disposition also indicates how the provided function called is displayed.

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

  When the UA 106 receives the HTML response in S202, it confirms to the user whether to register the providing function of the service 103 with the UA 106 or not. 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 or not. When the user selects to register the 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 operates, and is registered in the UA as Web Intents.

  In step S203, the UA 106 accesses the client 101 by the operation of the user. In step S204, the client 101 returns, to the UA 106, an HTML document in which it is described to use the providing function (Web Intent) of the service 103. For example, when an image and a “share” button are displayed on a web site as the client 101, the web site is an HTML document including an ECMA Script as shown in FIG. 3B which is a processing request of Web Intent. Return to UA106.

  FIG. 3B is a view exemplifying the HTML document returned from the client 101 to the UA 106 in S204. The contents of the HTML document returned from the client 101 to the UA 106 will be described below using the example of FIG. 3B.

  ECMAScript indicates that the specified anonymous function is executed when the button having the ID "share-photo" in HTML is clicked. The anonymous function first creates a new Intent object and calls the startActivety () function with this as an argument. When this function is executed, the UA 106 extracts, from the Web Intents registered in itself, one having the same action and type as the designated Web Intent object, and displays a list to request the user to make a selection. Also, the UA 106 acquires image data of the client 101 by executing the getImageFrom () function called in 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 step S205, when the UA 106 detects that the user has pressed the “share” button on the screen, it executes the ECMA Script for Web Intents activation as described above, and acquires the image data of the client 101 in step S206. Also, upon detecting that the “share” button has been pressed in S205, the UA 106 displays a list of Web Intents registered in itself. When the UA 106 detects from the list that the user has selected the Web Intent indicating the providing function of the service 103, in S207, the HTTP request (Web Intent processing request) is sent to the service 103 providing the selected providing function. Send. At this time, the UA 106 includes the content of the Web Intent object created by the ECMA Script of FIG. 3B in the transmission data.

  When the service 103 receives the HTTP request sent from the UA 106 in S207, it extracts the Web Intent object from the HTTP request in S208 and selects the provided function (here, while interacting with the user via the UA 106). In this case, utilization of “sharing” of the image data of the client 101 is realized.

  For example, the user visits a site provided with a call button of Web Intents of a web storage (client 101) for managing photograph data with a web browser (UA 106), and presses the button. Then, the web browser (UA 106) displays a pop-up window including the registered service list. If the user selects the web mail function as a service in the pop-up window, the site providing the function is displayed in a separate window, and as a result of processing, a new mail with attached picture data is created on the window . This allows the user to send an e-mail.

  When the processing relating to the providing function is completed, the service 103 returns a response including the ECMA Script for notifying the client 101 of the processing result to the UA 106 in S209. When the UA 106 receives the response in S209, it executes the ECMA Script contained in the response in S210, and calls the callback function onSuccess () specified by the argument of the startActivety () function in S205. In S211, the UA 106 returns the processing result to the client 101 by the callback function onSuccess ().

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

<Example UI of Information Processing Terminal in this Example>
FIG. 4 is a diagram showing an example of the UI of the information processing terminal according to an embodiment of the present invention.
In FIG. 4, reference numeral 501 denotes an information processing terminal such as a normal mobile terminal or a smartphone. In the information processing terminal 501, an OS (Operating System) such as android (registered trademark), which is a platform developed with a portable information terminal as a target, is installed.

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

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

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

<Hardware Configuration Example of Client 101 and Service 103>
FIG. 5 is a block diagram showing an example of the hardware configuration 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 centrally controls the entire apparatus by reading and executing programs stored in the ROM 603 and a storage device 608 described later. The ROM 603 is a read only memory for storing a boot program necessary 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 communicates via a network (Network). The display control unit 606 controls the display of the display device 609. For example, the display control unit 606 controls screen display such as for managing a web server. 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 input signals 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 an 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 programs executed by the CPU 602 and various information. In the case of the client 101, the storage device 608 also stores content information and the like provided by the client 101. In the case of the service 103, the storage device 608 also stores data, programs, and the like necessary for the service 103 to provide a function.

  The processes of the client 101 and the service 103 shown in the present embodiment are realized by the CPU of the client 101 and the service 103 reading and executing programs stored in the storage device 608, respectively.

<Hardware Configuration Example of Information Processing Terminal 501>
FIG. 6 is a block diagram showing the hardware configuration of the information processing terminal 501, and the 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 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, data communication, and the like, and is read and executed by the CPU 802. Examples of applications that control data communication include Mail software and a web browser.

  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 from the web server by the web browser, authentication information for accessing the web service, and the like. A storage device 809 is a non-volatile storage device, and stores various operation mode settings that need to be held even after the information processing terminal 501 is restarted, operation logs, and the like.

  A network controller (Network Controller) 805 performs communication control of a wireless LAN communication unit 811 for participating in a wireless LAN and a mobile phone data communication unit 812 for participating in a network provided by a mobile carrier. In general, when it is possible to join a wireless LAN network, the network controller 805 gives priority to connection of the wireless LAN 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 a call application is activated and the user is calling. Audio data is input / output via the microphone / speaker 813, and the audio control unit 806 mediates with the control program. The display control unit 807 controls information output on the display 814 of the information processing terminal 501. The input control unit 808 controls information instructed by the user via the button of the information processing terminal 501 or the touch panel 815. Using the voice control unit 806, the display control unit 807, and the input control unit 808, the application on the information processing terminal 501 provides the user with network communication information and various information on 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 operated by the CPU 802.

  The UA 106 shown in the present embodiment is realized by the CPU 802 of the information processing terminal 501 reading and executing a program stored in the ROM 803.

<Example of Software Configuration of Information Processing Terminal 501>
FIG. 7 is a block diagram showing the software configuration of the information processing terminal 501 in FIG. FIG. 7 mainly describes the technology related to Web Intents request issuance of the application related to the present invention and the function related to mutual use of function information using intent. Intent is a technology for transmitting and receiving data between arbitrary applications. This is a technology available on android (registered trademark) which is a platform developed targeting a portable information terminal. Although similar technology is implemented in other platforms, in the present embodiment, technology for transmitting and receiving data between applications in the information processing terminal is called intent.

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

  In the present invention, an environment in which a plurality of applications operating as the UA 106 of FIG. 1 on the operating system of the information processing terminal 501 operate in the information processing terminal 501 is assumed. In the present embodiment, a web browser is used as an example of the application operating as the UA 106. However, any application may be used as long as the application operates as the UA 106. For example, an application such as spreadsheet software may provide the function of the UA 106. Further, 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 is also an application that can transmit and receive data between applications. As a technology for transmitting and receiving data between applications, in addition to intents, there are Web Intents and the like. The first embodiment shows an embodiment in which data is transmitted and received between applications using an intent. Further, in a second embodiment to be described later, an embodiment is shown in which data is transmitted and received between applications using Web Intents. However, the application assumed here only needs to be able to transmit and receive data between arbitrary applications, and is not particularly limited to intents and Web Intents.

  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 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. A network control unit 906 controls the network controller 805 in FIG. The information processing terminal 501 is assumed to be moved and used because it is a small portable terminal, and the network control unit 906 automatically connects to an accessible network according to the location. Further, in response to a communication request from the application unit 902, communication is performed to the outside. Further, the network control unit 906 distributes the connection request to an appropriate application unit 902 in response to a network connection request from the outside.

  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 together with information on action and type (hereinafter, data type), the OS unit 901 requests the intent information input / output unit 904 for an application corresponding to the action and data type. When the intent information input / output unit 904 receives 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. Then, the intent information input / output unit 904 transmits the acquired list of applications to the application unit 902.

  A user input / output unit 903 integrally manages the voice control unit 806, the display control unit 807, and the input control unit 808 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. Further, when the user performs 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 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.

  A central processing unit 907 functions as a Web browser. The basic role of the central processing unit 907 is the UA 106 in Web Intents. In addition, the central processing unit 907 also performs basic browsing processing, detection of the service 103, and transmission / reception of data through an intent. Further, when not using the intent of the OS unit 901, the central processing unit 907 acquires service information (functional information) of Web Intents from another application using the service information management unit 908. It is also possible. The service information management unit 908 will be described in a second embodiment described later.

  The service information detection unit 909 detects an <intent> tag included in the Web page received from the service 103 at the time of access, and recognizes function information for registering a function provided by the service 103. The service information input / output unit 910 controls input / output of function 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 exemplifying function information managed by the web browser as the UA.
For example, in the example shown in FIG. 8, the name 1401 of the provided function provided by the service, the URI 1402 for accepting the provided function by the service, the action 1403 for accepting 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 accesses a certain service (web site) using the mechanism of Web Intents, using a web browser (corresponding to the UA 106) which is an application of the information processing terminal 501. Then, the service information detection unit 909 of the application unit 902 detects an <intent> tag included in the Web page received from the service at the time of access, and function information (Web Intents service information) for registering a function provided by the service. Recognize When recognizing the function information of the accessed service, the central processing unit 907 asks the user via the user input / output unit 903 whether to register the function information as Web Intent. Here, 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. When receiving 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 a 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.

  Note that 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 execute the function information from the other Web browser. You can get In this case, the central processing unit 907 of the Web browser issues, to the intent information input / output unit 904 of the OS unit 901, a request for acquiring a list of applications that can provide functional information. Then, as a result of the request, the central processing unit 907 receives a list of applications for providing the function information. When the user selects an arbitrary application from the list of applications, the central processing unit 907 requests acquisition of function information to the selected application using an intent, and acquires function information.

  Further, when the central processing unit 907 receives a provision request (acquisition request) of function information 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 function information to the external application.

<Example of Sequence Diagram for Mutual Use of Function Information>
FIG. 9 is a sequence diagram illustrating an operation of referring to a list of function information managed by another Web browser when the user uses the Web Intents using a certain Web browser. In FIG. 9, the basic sequence of Web Intents described in FIG. 2 is expanded. In FIG. 9, reference numeral 902 denotes a web browser in the information processing terminal 501, and the role of Web Intents is UA. In FIG. 9, there are a plurality of UAs, and the Web browser requesting functional information is UserAgent.1 (hereinafter, UA.1), and the Web browser providing functional information is UserAgent.2 (hereinafter UA.1). 2) Do.
FIG. 10 is a view exemplifying a screen displayed on the web browser screen of UA.1.
11 and 12 are detailed sequence diagrams of a part of the sequence of FIG.

  In S1001 of FIG. 9, the UA.1 accesses the client 101 in accordance with a user instruction. Then, in S1002, the UA.1 receives, from the client 101, HTML information including EMCA Script whose processing is started by the “Share” button. Then, on the web browser screen of UA.1, a screen as shown in FIG. 10A is displayed. In this screen, it is possible to issue a request for sharing the photo content information to any service by providing the photo content information and the “Share” button 1101.

  When the user presses the “Share” button 1101 and instructs to use the service in S1003, the UA.1 detects that the “Share” button 1101 is pressed. The UA. 1 detects that the “Share” button 1101 has been pressed, and if it is determined that the user instructs to use the service, the process proceeds to step S 1004. 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 of photo content and the data type of the file, and acquires the list. The selection screen as shown in FIG. 10B including the list (list) of the functional information is displayed and presented to the user.

  In the screen displayed in S1004, as shown in FIG. 10B, a link button 1103 described as a list 1102 of function information and "service import" capable of referring to function information registered in another UA. Is displayed. Also displayed on this screen are an OK button 1104 for determining the selected function information and a Cancel button 1105 for canceling the selection of the function information.

  If there is no function information to be used in the list 1102 of function information on the screen as shown in FIG. 10B displayed in S1004, the user uses the function information registered by another browser. Can. In this case, the user presses the “service / import” link button 1103 on the screen of FIG. 10B in S1005.

  When detecting that the “service / import” link button 1103 is pressed, the UA. 1 searches for other applications capable of providing the function information in the information processing terminal 501 (S1006 to S1007). In the first embodiment, a processing sequence for acquiring function information using an intent of android (registered trademark) as an example will be described. Similar to Web Intents, the intent also enables data transfer between appropriate applications by the OS intermediaries the data type to be transferred and the action of what to do with that data.

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

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

Hereinafter, S1010 to S1013 will be described in detail with reference to FIG.
As shown in FIG. 11B, at S1010, UA.1 makes an intent call to UA.2, sets the data type to "application / Web IntentsService", and sets the action to "pick" and requests processing. Do. In response to this request, UA.2 provides UA.1 with a list of function information that can be provided as an intermediate response. In addition, although transmission and reception of this data are actually performed via OS91, it simplifies and demonstrates here.

  When UA.1 receives the function information list from UA.2 in S1011, it displays the function information list (list) of UA.2 in S1013. An example of a screen displayed on the information processing terminal 501 in S1013 is shown as FIG. In FIG. 10C, a parent-child relationship between a list of UAs and a 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 the UA (1106). However, the parent-child relationship may not be displayed, and only a list of functional 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 while selecting any one or more pieces of function information. At this time, UA.1 detects that the function information has been selected.

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

  When UA.1 detects that the function information registered in UA.2 is selected from the function information list in S1014, the function information selected for UA.2 in S1015 is selected. Issue a request for acquiring the selected function information and acquire the selected function information (S10115 to S1016).

Hereinafter, S1015 to S1016 will be described in detail with reference to FIG.
As shown in FIG. 12A, in S1015, UA.1 designates the function information of the acquisition target using the "pick" of the intent, and uses the mechanism of the intent to specify UA.2 to the function information. Issue an acquisition request to the client. In response to the acquisition request, the UA. 2 transmits the designated 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 illustrates the definition file of the function information transmitted from the UA. 2 in S1016.
As shown in FIG. 13, in the definition file of function information, the name of the provided function, the URI for accepting the provided function, and the action (type of action) and data for providing the provided function are described. ing.

Hereinafter, the description returns to the sequence diagram of FIG.
Upon acquiring 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 the 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 a list of function information registered in itself to the user by displaying a selection screen as shown in FIG. 10B again. When it is detected in S1019 that the user has selected certain function information from the function information list displayed in S1018, the UA.1 advances the process to S1020. In S1020, the UA.1 transmits an HTTP request (Web Intent processing request) for processing "share" to the service (here, the service 103) corresponding to the selected function information.

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

<Example of Processing Flowchart of UA in Embodiment 1>
FIG. 14 is a flowchart illustrating an example of software processing from when the UA receives ECMA Script from the client to when the UA acquires functional information from the outside and issues a request to the service. The process of this flowchart shows a part of the process of software in the information processing terminal 501 shown in FIG. The processing of this flowchart is realized by the CPU 802 of the information processing terminal 501 expanding a program stored in the ROM 803, the storage device 809 or the like into the RAM 804 as needed, and executing it.

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

  In S1702, the central processing unit 907 constructs a screen based on the received HTML information, displays a screen as shown in FIG. 10A via the user input / output unit 903 and presents the received information to the user, The process advances to step S1703. In step S1703, the central processing unit 907 determines whether an instruction to issue a Web Intents request has been received from the user by screen operation. When the central processing unit 907 detects that the “share” button 1101 is pressed, the central processing unit 907 determines that the Web Intents request issuance instruction has been received.

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

  On the other hand, if it is determined that the Web Intents request issuance instruction has been received (S1703: Yes), the central processing unit 907 advances the process to S1704. In step S1704, the central processing unit 907 queries the service information input / output unit 910 for registration of the function information corresponding to the Web Intents request. Here, if there is registration of the corresponding function information, 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 advances to step S1705.

  In step S1705, the central processing unit 907 determines whether the “service / import” link button 1103 is pressed on the screen illustrated in FIG. 10B. When it is determined that the “service import” link button 1103 is pressed (Yes in S1705), the central processing unit 907 advances the process to S1706. In S1706, a function information list acquisition / registration process is executed. Details of S1706 in the first embodiment are shown in FIG. 15 described later. Then, when the process of S1706 ends, the central processing unit 907 advances the process to S1704 and displays a screen for selecting a list of function information including the information acquired in S1706 (a screen as shown in FIG. 10B). 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 process to S1707. In S1707, when the central processing unit 907 detects the selection of the function information by the user, the central processing unit 907 advances the process to S1708. In step S1708, the central processing unit 907 creates a Web Intents request using the content information for which the issuance instruction has been issued in step S1703 and proceeds to step S1709. In step S1709, the central processing unit 907 issues the Web Intents request created in step S1708 to the service corresponding to the function information selected and detected in step 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 a program stored in the ROM 803, the storage device 809 or the like into the RAM 804 as needed, and executing it.

  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 with the action “pick” and the data type “Web Intents Service” to the OS unit 901, and advances the process to S1723.

  In step S1723, the central processing unit 907 determines whether a list of applications has been received as a response requested by the OS unit 901 as an intent. When it is determined that the list of applications can not be received from the OS unit 901 (No in S1723), the central processing unit 907 advances the process to S1724. In S1724, the user searches for a corresponding application by intent, but notifies the user that there is no corresponding application in the device (for example, displays a message), and ends this function information list acquisition / registration process (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 advances the process 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 the list to the user. Then, the process advances to step 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, it advances the process to S1727. In step S1727, the central processing unit 907 uses the intent of the application selected in step S1726 to request a list of function information corresponding to the action "pick" and the data type "Web Intents Service". Then, the process proceeds to step 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 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 function information, and advances the processing to step S1730.

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

  In the example of FIG. 10C, the central processing unit 907 displays a list of applications consisting of “browser B” and “browser C” in S1726. When acquiring the function information list registered in “browser B”, the user touches “browser B”. Then, in S1730, the central processing unit 907 inclines the triangle on the left side of the screen indicating the directory structure as in 1108, and displays the function information list 1106 registered in "browser B". From the function information list 1106, the user selects one or more pieces of function information to be taken into the application.

Hereinafter, the description returns to the flowchart of FIG.
When detecting the operation on the screen displayed in S1730, the central processing unit 907 advances the process to S1731. In step S1731, the central processing unit 907 determines whether it has detected that the function information to be fetched is selected from the function information list displayed in step S1730. When it is determined that the function information is not selected and it is detected that the application (for example, “browser C”) is selected (No in S1731), the central processing unit 907 advances the process to S1726.

  On the other hand, when it is determined that it is detected that the function information to be fetched is 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. At S1734, 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 is ended (S1735).

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

  In the first embodiment, for example, the configuration for acquiring the function information managed by another UA using the intent of the android (registered trademark) based 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 using Web Intents of W3C without using intent.

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

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

<Example of another sequence diagram related to mutual use of functional information>
FIG. 16 is a sequence diagram illustrating another operation used with reference to the list of function information managed by another Web browser in the second embodiment. The same steps as in FIG. 9 are assigned the same step numbers. Hereinafter, only differences from FIG. 9 will be described.
FIG. 17 is a detailed sequence diagram of a part of the sequence of FIG.

  The processing of S1001 to S1005 is the same as that of FIG. In the information processing terminal 501 of the second embodiment, when 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 started from the local area network (Local Network) 1501. Search for applications or services that can provide information (hereinafter simply referred to as services). Specifically, when the user detects that the “service import” link button 1103 (FIG. 10 (b)) is pressed in S1005, UA.1 searches for a service against the Local Network 1501 in S1601. Run. The network search will be described in detail below with reference to FIG.

As shown in FIG. 17, UA.1 searches for a service with respect to the Local Network 1501 in S1601. Here, for example, a network service in link local is searched using a technology such as Multicast DNS in Bonjour which is an 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, in addition to receiving a response from the service in the same information processing terminal, it is possible to receive a response from a service within the reach of the network.

Next, at S1603, UA.1 detects and lists the services providing the data type "application / Web Intents Service" and the action "pick" from the services received at S1602 above. At this time, when the information necessary for the detection is insufficient, each service which has received the response in the above S1602 may be accessed and acquired. Such processing makes it possible to search for services that can provide function information existing in the local area network.
Next, in S1604, the UA.1 displays the list of services detected in S1603 and presents the list to the user, and advances the process to S1009. The subsequent processing is the same as that of FIG.

<Flowchart of Function Information List Acquisition / Registration Process of Second Embodiment>
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 a program stored in the ROM 803, the storage device 809 or the like into the RAM 804 as needed, and executing it.

  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 the Local Network 1501 for an application or service (hereinafter simply referred to as a service) that provides a function using the Web Intents mechanism (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 IntentsService". The search request issues a request 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 the corresponding one or more services have been found as a result of the search in S1742. Then, if the service information management unit 908 determines that the corresponding service could not be found (in the case of No in S1743), it advances the process to S1744. In S1744, the service information management unit 908 notifies the user that there is no corresponding service within the network search range (for example, displays a message) as a result of searching for the service via the central processing unit 907, The function information list acquisition / registration process is ended (S1755).

  On the other hand, if the service information management unit 908 determines that one or more corresponding services have been found (in the case of Yes in S1743), it advances the process to S1745. In S1745, the service information management unit 908 displays the list of services acquired through the user input / output 903 in S1743 through the central processing unit 907, and advances the process 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 through the central processing unit 907, the process proceeds to S1747. In step S1747, the service information management unit 908 requests, for the service selected in step S1746, a list of function information whose action type is "pick" and whose data type is "Web Intents Service" using Web Intents. . Then, the process proceeds to step 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 the 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 function information via the central processing unit 907 and the user input / output unit 903. Here, for example, a screen as shown in FIG. 10C is displayed. The user touches “browser B” when acquiring a list of function information registered in a certain application. Then, the triangle on the left side of the screen indicating the directory structure is inclined as shown by 1108, and the function information list 1106 shown in S1750 is displayed. From the function information list 1106, the user selects one or more pieces of function information to be taken into the application.

Hereinafter, the description will return to the flowchart.
When the operation on the screen displayed in S1750 is detected, the service information management unit 908 advances the process to S1751. In S1751, the service information management unit 908 determines, through the central processing unit 907, whether it has detected that the function information to be fetched is selected from the function information list displayed in S1750. When it is determined that the function information is not selected and it is detected that the application (for example, “browser C”) is selected (S1751: No), the service information management unit 908 advances the process to S1746.

  On the other hand, when it is determined that it has been detected that the function information to be fetched is 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 the service information managing the selected function information using the 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 S1754, 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 is ended (S1755).

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

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

  However, when the user tries to acquire the function information, the partner of mutual use 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 the function information is registered in the web browser as the UA, the function information is also registered in the service for managing the function information list on the Internet. Next, the user considers using the service with another web browser, and presses the “service / import” link button 1103 in FIG. 10B. Then, the web browser connects to a 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 becomes possible even if the applications in the local network are not one another, and the same effect as in the first embodiment and the second embodiment can be obtained.

  As described in the second embodiment, when it is attempted to acquire the function information list using Web Intents, there is a case where the function information usable by a certain web browser can not be used by the own web browser. For example, it is assumed that the URL of the function provided by the service present in the information processing terminal 501 is a URL indicating a 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 (the requesting Web browser) provides the function of providing the service corresponding to the function information via the network. It can not 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 condition of the side requesting the function information (the request side). In addition, 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 the available function information of the requester according to the action or type requested by the requester. With the above configuration, it is possible to prevent unnecessary registration of function information that can not be used by the request source as described above, and it is possible to improve the convenience of the user.

  In addition, the Web browser that has received the provision of the function information determines whether the function information can be used by itself when acquiring the function information, and when the function information is unavailable, the function information is displayed as an option to the user It is also conceivable to avoid it. In this configuration as well, it is possible to prevent unnecessary registration of function information that can not be used at the request source, etc., and to improve the convenience of the user.

  As described above, according to the present invention, the usability can be improved with respect to a new cooperation mechanism such as currently proposed Web Intents. For example, when a plurality of relay functions required to provide a new Web service linkage mechanism 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. Make it possible to As a result, the user does not have to repeat registration of the same provided function for each relay function, and the convenience of the user is improved.

The configuration of the various data described above and the contents thereof are not limited to this, and it is needless to say that they are configured in various configurations and contents depending on the application and purpose.
Although the embodiment has been described above, the present invention can be embodied as, for example, a system, an apparatus, a method, a program, or a storage medium. Specifically, the present invention may be applied to a system constituted by a plurality of devices, or may be applied to an apparatus comprising a single device.
Further, all the configurations obtained by combining the above-described embodiments are also included in the present invention.

(Other embodiments)
The present invention is also realized by executing the following processing. That is, software (program) for realizing the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU or the like) of the system or apparatus reads the program. It is a process to execute.
Further, the present invention may be applied to a system constituted by a plurality of devices or to an apparatus comprising a single device.
The present invention is not limited to the above embodiments, and various modifications (including organic combinations of the respective embodiments) are possible based on the spirit of the present invention, which are excluded from the scope of the present invention is not. That is, the configuration in which each of the above-described embodiments and their modifications are combined is also included in the present invention.

Claims (20)

An information processing terminal that communicates via a network with a website that provides page data including a description of data to be shared and a shared object to be displayed, and an operating system (OS) and a web browser are executed. ,
Display means for displaying a page including the shared object as a function of the web browser based on page data received from the website;
Request means for executing a request for function information from the web browser to the OS when a user instruction to the shared object is performed via the displayed page;
Providing means for providing a selection screen for selecting one of a plurality of functions using the function information received from the OS based on the request, as the function of the web browser;
Issuing means for issuing, as a function of the web browser, a request for sharing the data to be shared using a function corresponding to the selection in response to the selection via the selection screen;
An information processing terminal characterized by having:   The function corresponding to the selection via the selection screen indicates a function provided by a web application executed by a device connected to the information processing terminal via a network. Information processing terminal.   The information processing terminal according to claim 1, wherein the function corresponding to the selection via the selection screen indicates a function provided by a printer incorporated in the information processing terminal.   The said description contained in the page data received from the client contains the description using the navigator interface which calls the function for sharing the said data to be shared. The information processing terminal described in.   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 smart phone. A control method implemented by a web browser in an information processing terminal on which an operating system (OS) is executed,
Displaying the page including the shared object based on the page data received via the network from the website providing the page data including the description regarding the data to be shared and the shared object to be displayed;
A request step of executing a request for function information to the OS when a user instruction to the shared object is performed via the displayed page;
Providing a selection screen for selecting one of a plurality of functions using the function information received from the OS based on the request;
Issuing a request for sharing the data to be shared, using a function corresponding to the selection, in response to the selection via the selection screen;
A control method characterized by comprising:   The function according to claim 8, wherein the function corresponding to the selection via the selection screen indicates a function provided by a web application executed by a device connected to the information processing terminal via a network. Control method.   The control method according to claim 8, wherein the function corresponding to the selection via the selection screen indicates a function provided by a printer incorporated in the information processing terminal.   11. The method according to any one of claims 8 to 10, wherein the description included in page data received from a client includes a description using a navigator interface that calls a function for sharing the data to be shared. Control method described in.   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 smart phone. On a computer running an operating system (OS),
Displaying the page including the shared object based on the page data received via the network from the website providing the page data including the description regarding the data to be shared and the shared object to be displayed;
A request step of executing a request for function information to the OS when a user instruction to the shared object is performed via the displayed page;
Providing a selection screen for selecting one of a plurality of functions using the function information received from the OS based on the request;
Issuing a request for sharing the data to be shared, using a function corresponding to the selection, in response to the selection via the selection screen;
A program to run a program.   The program according to claim 15, wherein the function corresponding to the selection via the selection screen indicates a function provided by a web application executed on a device connected via the network.   The program according to claim 15, wherein the function corresponding to the selection via the selection screen indicates a function provided by a printer incorporated in the computer. The description contained in the page data received from the client, any one of claims 15 to 1 7, characterized in that it comprises a description using the navigator interface to call a function for sharing the data to be the shared 1 The program described in Section.   The program according to any one of claims 15 to 18, wherein the network is the Internet.   The program according to any one of claims 15 to 19, wherein the OS is Android (registered trademark).

Images