Terminal device, data sharing method and program

Abstract

To improve user convenience when sharing data between multiple applications.SOLUTION: A terminal device includes an acquisition part that acquires a specified data while another application is launched and a notification part that notifies the specified application of an instruction to launch a function corresponding to the attribute of the specified data among a plurality of functions possessed by application specified by a user and to which the specified data corresponds.SELECTED DRAWING: Figure 11

Description

[Technical field]

[0001] The present disclosure relates to a terminal device, a data sharing method, and a program. [Background technology]

[0002] Conventionally, a data sharing function of an OS (Operating System) has been known, such as Shared Extension, etc. Shared Extension is a function that allows data selected by a user while another application is running to be shared in the application desired by the user.

[0003] By using such a data sharing function, for example, a user can share data between a plurality of applications. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 6524276 Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the case of the data sharing function, a specific function of the application is launched and data is shared in that function. Therefore, even if an application has multiple functions, for example, it is not possible to switch the function to be launched depending on the situation and share data in another function, which is inconvenient for the user.

[0006] An object of the present disclosure is to improve user convenience when sharing data among a plurality of applications. [Means for solving the problem]

[0007] A terminal device according to an embodiment of the present disclosure has, for example, the following configuration. A terminal device, An acquisition unit that acquires the specified data in a state where another application is launched; By user Prescribed application When the attribute of the specified data is determined by specifying Among the multiple functions possessed by attribute an instruction to launch a function according to the specified data, A generating unit that generates , The instructions, The above Prescribed A notification unit that notifies an application, When the specified data is image data, the number of the image data and / or property information included in the image data are determined based on the number of the image data and / or property information included in the image data. In the given application Differentiate the functions that are launched. Effect of the Invention

[0008] According to the present disclosure, it is possible to improve user convenience when sharing data among a plurality of applications. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a first diagram showing an example of a system configuration of a service utilization system. [Diagram 2] FIG. 2 illustrates an example of a hardware configuration of a server device. [Diagram 3] FIG. 2 illustrates an example of a hardware configuration of a terminal device. [Figure 4] FIG. 2 is a diagram for explaining the operation of software in a terminal device. [Diagram 5] FIG. 11 is a first diagram showing a specific example of processing contents of a terminal device. [Figure 6] FIG. 2 is a second diagram showing a specific example of the processing contents of the terminal device. [Figure 7] FIG. 3 is a third diagram showing a specific example of the processing contents of the terminal device. [Figure 8] FIG. 4 is a fourth diagram showing a specific example of the processing contents of the terminal device. [Figure 9] FIG. 5 is a fifth diagram showing a specific example of the processing contents of the terminal device. [Figure 10] FIG. 11 is a diagram showing a specific example of specific data. [Figure 11] FIG. 1 is a first diagram showing details of the functional configuration of a data sharing function application and a data sharing application 2. [Figure 12] FIG. 11 is a first diagram showing an example of a screen corresponding to each functional unit. [Figure 13] FIG. 11 is an example of a first sequence diagram showing a flow of a service usage process. [Figure 14] 13 is an example of a flowchart showing the flow of a data sharing process. [Figure 15] 13 is a flowchart showing the flow of a start-up process. [Figure 16] FIG. 2 is a second diagram showing an example of the system configuration of the service utilization system. [Figure 17] FIG. 6 is a sixth diagram showing a specific example of the processing contents of the terminal device. [Figure 18] FIG. 2 is a second diagram showing details of the functional configuration of the application for the data sharing function and the data sharing application 2. [Figure 19] FIG. 2 is a second diagram showing an example of a screen corresponding to each functional unit. [Figure 20] FIG. 11 is an example of a second sequence diagram showing the flow of a service usage process. [Figure 21] FIG. 3 is a third diagram showing details of the functional configuration of the application for the data sharing function and the data sharing application 2. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Each embodiment will be described in detail below. In describing the specification and drawings of each embodiment, components having substantially the same functional configurations are denoted by the same reference numerals to avoid redundant description.

[0011] [First embodiment] <System configuration of the service usage system> First, a system configuration of a service utilization system for utilizing various services provided by a server device via a terminal device will be described. Fig. 1 is a first diagram showing an example of the system configuration of the service utilization system.

[0012] 1, the service utilization system 100 includes a server device 110 and a terminal device 120 used by a user 140. The terminal device 120 is connected to the server device 110 via a network 130 so as to be able to communicate with the server device 110.

[0013] The server device 110 is a device that provides service contents to the terminal device 120 in response to a service utilization request from the terminal device 120 .

[0014] The terminal device 120 is a device used by a user 140, and has various applications installed thereon. As shown in Fig. 1, on the home screen of the terminal device 120, various icons 121 to 123 that accept launch operations for launching various applications installed in the terminal device 120 are displayed.

[0015] In this embodiment, the various applications installed in the terminal device 120 can be roughly divided into the following three types.

[0016] i) General purpose applications It is an application that specifies data to be shared with other applications (data sharing applications). In this embodiment, the general-purpose application includes, for example, a camera application (an application for taking image data) and an album application (an application for viewing taken image data). Alternatively, it includes an SNS application (an application for using an SNS) and a browser (software for viewing various sites).

[0017] The camera application may specify image data to be shared, for example, by photographing an object. The album application may specify image data to be shared, for example, by selecting image data. The SNS application and browser may specify image data to be shared, for example, by photographing a corresponding screen (screenshot operation). The SNS application and browser may specify text data to be shared, for example, by selecting a portion of text data in a corresponding screen.

[0018] ii) Data Sharing Application 1 The data sharing application 1 is an application that shares and uses data specified in a general-purpose application (specific data (image data or text data)). In this embodiment, the data sharing application 1 includes, for example, an email application (an application that sends specific data as the body of an email, or sends specific data as an attachment to an email). Alternatively, it includes a message application (an application that sends specific data as a message, or sends specific data as an attachment).

[0019] The data sharing application 1 is an application that starts up a specific function of each application to share specific data. For example, an email application starts up an email sending function to share specific data. For example, a message application starts up a message sending function to share specific data.

[0020] iii) Data sharing application 2 The data sharing application 2 is an application that shares and uses specific data specified in a general-purpose application. In this embodiment, the data sharing application 2 includes, for example, a service use application (an application that uses the specific data to use a service provided by the server device 110).

[0021] In the data sharing application 2, when launching various functions corresponding to various services provided by the server device 110, the function to be launched is switched according to the attribute of the specific data. In addition, in the data sharing application 2, the switched function is launched to share the specific data.

[0022] Specifically, the user 140 launches the general-purpose application by tapping the icon 121, and while the general-purpose application is launched, specifies data to be shared in another application (data sharing application 2 in this embodiment).Then, the user 140 uses a data sharing function (not shown in FIG. 1) of the OS of the terminal device 120 to launch a function corresponding to the attribute of the specific data, among various functions of the data sharing application 2, and share the specific data.

[0023] In this way, when data is shared between a general-purpose application and the data sharing application 2, the terminal device 120 can switch the function to be launched depending on the attribute of the specific data.

[0024] This allows the user 140 to receive service content according to the attributes of the specific data from among various services provided by the server device 110. As a result, the terminal device 120 can improve the convenience for the user 140 when sharing data between a general-purpose application and the data sharing application 2.

[0025] In the following description, "launching an application" means that a launch command is input. The application transitions from a not running state to a running state, and the screen corresponding to the application transitions from a not being displayed to the user to a being displayed; or A transition from a state in which an application is running and the screen corresponding to the application is not displayed to the user to a state in which the application is running and the screen corresponding to the application is displayed to the user; This refers to the following.

[0026] However, the transition from a state in which an application is not running to a state in which it is running refers to the application program being loaded into the memory of the terminal device.

[0027] In the following explanation, "an application is launched" means The application is running and the screen corresponding to the application is displayed to the user. This refers to the following.

[0028] Note that the state in which an application is running refers to the state in which the application program is loaded into memory.

[0029] <Server hardware configuration> Next, a description will be given of the hardware configuration of the server device 110. Fig. 2 is a diagram showing an example of the hardware configuration of the server device.

[0030] 2, the server device 110 includes a processor 201, a memory 202, an auxiliary storage device 203, a display device 204, an operation device 205, a communication device 206, and a drive device 207. The hardware components of the server device 110 are connected to each other via a bus 208.

[0031] The processor 201 includes various arithmetic devices such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), etc. The processor 201 reads various programs onto the memory 202 and executes them.

[0032] The memory 202 has a main storage device such as a Read Only Memory (ROM) and a Random Access Memory (RAM). The processor 201 and the memory 202 form a so-called computer, and the processor 201 executes various programs read onto the memory 202, causing the computer to realize various functions.

[0033] The example in FIG. 2 shows a case in which the processor 201 executes a service providing program read onto the memory 202, causing the computer to function as a service providing unit 210.

[0034] The auxiliary storage device 203 stores various programs and various information used when the various programs are executed by the processor 201. The example of Fig. 2 shows that service information used when the service providing unit 210 provides various services is stored in the service information storage unit 230 realized in the auxiliary storage device 203.

[0035] The display device 204 is a display device that displays the internal state of the server device 110. The operation device 205 is an input device that is used when an administrator of the server device 110 inputs various instructions to the server device 110. The communication device 206 is a communication device that is connected to the network 130 and communicates with the terminal device 120.

[0036] The drive device 207 is a device for setting the recording medium 240. The recording medium 240 here includes media that record information optically, electrically, or magnetically, such as a CD-ROM, a flexible disk, a magneto-optical disk, etc. The recording medium 240 may also include semiconductor memories that record information electrically, such as ROM, flash memory, etc.

[0037] The various programs to be installed in the auxiliary storage device 203 are installed, for example, by setting the distributed recording medium 240 in the drive device 207 and reading out the various programs recorded in the recording medium 240 by the drive device 207. Alternatively, the various programs to be installed in the auxiliary storage device 203 may be installed by being downloaded from the network 130 via the communication device 206.

[0038] <Hardware configuration of terminal device> Next, a description will be given of the hardware configuration of the terminal device 120. Fig. 3 is a diagram showing an example of the hardware configuration of the terminal device.

[0039] 3, the terminal device 120 includes a processor 301, a memory 302, an auxiliary storage device 303, an operation device 304, a display device 305, a communication device 306, and an imaging device 307. The hardware components of the terminal device 120 are connected to each other via a bus 308.

[0040] As shown in FIG. 3, each piece of hardware in terminal device 120 is generally the same as each piece of hardware in server device 110 shown in FIG. 2, so the following description will focus on the differences from FIG.

[0041] As shown in FIG. 3, in the case of the terminal device 120, various programs (various software programs that run on an OS) that are loaded onto a memory 302 and run on an OS (Operating System) 350 include, for example, General purpose applications (code 310), Data sharing application 1 (code 320), - an application for data sharing function (reference number 330); Data sharing application 2 (code 340), Includes:

[0042] 3, the terminal device 120 includes an imaging device 307. The imaging device 307 captures an image of a subject at a predetermined frame rate and outputs image data.

[0043] <Software operation in terminal device> Next, a description will be given of the contents of processing that is realized by the processor 301 reading the various software programs into the memory 302 and running them on the OS 350 in the terminal device 120. Fig. 4 is a diagram for explaining the operation of the software programs in the terminal device.

[0044] As shown in FIG. 4, the OS 350 includes a data sharing function unit 351 (eg, a Shared Extension) and a link initiation unit 352.

[0045] The data sharing function unit 351 allows specific data (image data or text data) specified by the user 140 while the general-purpose application (reference numeral 310) is running to be shared with an application desired by the user 140.

[0046] The data sharing function unit 351 operates when specific data (image data or text data) is notified from the general-purpose application (reference number 310). When the user 140 desires to share data with, for example, a data sharing application 1 (reference number 320), the data sharing function unit 351 notifies the data sharing application 1 (reference number 320) of an instruction to launch the data sharing application and also notifies the specific data.

[0047] Furthermore, when the user 140 desires to share data with, for example, a data sharing application 2 (reference number 340), the data sharing function unit 351 notifies the application for the data sharing function (reference number 330) of the specific data.

[0048] The link launching unit 352 launches an application (in this embodiment, data sharing application 2) by specifying the application in the form of a link. When the link launching unit 352 receives a launch instruction specified in the form of a link (e.g., a deep link) from the data sharing function application (reference number 330), the link launching unit 352 notifies the data sharing application 2 (reference number 340).

[0049] The general-purpose application (reference number 310) is launched when the user 140 performs a launch operation and receives a launch instruction from the OS 350. In addition, the general-purpose application (reference number 310) notifies the data sharing function unit 351 of specific data specified by the user 140 in the launched state.

[0050] The data sharing application 1 (reference number 320) is launched, for example, when a launch instruction is notified from the data sharing function unit 351. Furthermore, when the data sharing application 1 (reference number 320) is launched, it sets the specific data notified in association with the launch instruction and shares the specific data. Furthermore, the data sharing application 1 (reference number 320) executes a specific function using the specific data to be shared, and notifies the OS 350 of the execution result. As a result, the execution result executed using the specific data to be shared is displayed, for example, on the display device 305.

[0051] The data sharing function application (reference number 330) is an example of an extension program. When specific data is notified from the data sharing function unit 351, the data sharing function application (reference number 330) determines the attributes of the notified specific data. Based on the attribute determination result, the data sharing function application (reference number 330) determines which of a plurality of functions of the data sharing application 2 (reference number 340) to launch.

[0052] Furthermore, the application for the data sharing function (reference number 330) generates a launch instruction corresponding to the determined function and notifies the link launch unit 352. As a result, the link launch unit 352 notifies the data sharing application 2 (reference number 340) of the launch instruction notified by the application for the data sharing function (reference number 330).

[0053] When the data sharing application 2 (reference number 340) receives the launch instruction from the link launch unit 352, it launches a function corresponding to the launch instruction from among a plurality of functions possessed by the data sharing application 2 (reference number 340).

[0054] Furthermore, the data sharing application 2 (reference numeral 340) extracts specific data (image data or text data) from the notified launch instruction, and sets the extracted specific data, thereby sharing the specific data.

[0055] Furthermore, the data sharing application 2 (reference numeral 340) executes a function launched using the specific data to be shared, and notifies the OS 350 of a service utilization request corresponding to the launched function. As a result, a service utilization request corresponding to the attribute of the specific data to be shared is transmitted to the server device 110.

[0056] <Description of the processing contents in the terminal device> Next, the details of the processing contents processed in terminal device 120 by the operation of various software will be described with specific examples. Fig. 5 to Fig. 9 are first to fifth diagrams showing specific examples of the processing contents of the terminal device.

[0057] 5 shows a state in which, with a home screen 500 displayed on the display device 305 of the terminal device 120, the user 140 selects an icon 121 to launch a general-purpose application (reference number 310). When the general-purpose application (reference number 310) is launched in response to a launch instruction sent from the OS 350, a general-purpose app screen corresponding to the general-purpose application (reference number 310) is displayed on the display device 305.

[0058] FIG. 6 shows a general-purpose application (reference numeral 310): Case (a-1) in which the camera application is launched and the camera application screen 610 is displayed. Case (a-2) in which the album application is launched and the album application screen 620 is displayed. Case (a-3) in which an SNS application is launched and an SNS application screen 630 including SNS information received via the communication device 306 is displayed; Case (a-4) in which a browser is launched and a browser screen 640 including site information received via the communication device 306 is displayed. are shown respectively.

[0059] 6 also shows a state in which a specific operation for specifying data to be shared is performed on a general-purpose application screen corresponding to a general-purpose application (reference numeral 310). A case in which image data is acquired as specific data by pressing the shutter button while the camera application screen 610 is displayed, A case in which multiple image data are acquired as specific data by selecting image data while the album application screen 620 is displayed, A case in which image data is acquired as specific data by taking a screenshot while the SNS application screen 630 is displayed, A case where text data is acquired as specific data by selecting a character string while the browser screen 640 is displayed, are shown respectively.

[0060] The specific data (image data or text data) specified on the general-purpose application screen corresponding to the general-purpose application (reference numeral 310) is notified to the data sharing function unit 351. As a result, the data sharing function unit 351 displays a share button on the display device 305.

[0061] 7 shows a state in which a data sharing operation is performed by displaying a share button 700 on the display device 305 by the data sharing function unit 351 and pressing the share button 700 by the user 140. When a data sharing operation is performed, the data sharing function unit 351 displays on the display device 305 a list of data sharing applications that can share specific data.

[0062] Fig. 8 shows a state in which a list 800 of data sharing applications capable of sharing specific data is displayed on the display device 305. Note that, for the sake of simplicity, Fig. 8(a) shows a case in which the list 800 of data sharing applications is displayed on the album application screen 620.

[0063] In this embodiment, the data sharing applications capable of sharing specific data include a data sharing application 1 (reference number 320) and a data sharing application 2 (reference number 340). Therefore, icons 122 and 123 corresponding to these applications are displayed in the data sharing application list 800.

[0064] 8 shows a state in which the user 140 performs a data sharing application selection operation by selecting the icon 123 in a list 800 of data sharing applications. Note that at the time when the user 140 selects the icon 123, the data sharing application 2 (reference number 340) has not yet been launched. Therefore, when the user 140 selects the icon 123, the data sharing function unit 351, the link launching unit 352, and the application for the data sharing function (reference number 330) perform processing to launch the data sharing application 2 (reference number 340).

[0065] Fig. 9 shows a state in which a process for launching a data sharing application 2 (reference numeral 340) is performed. As shown in Fig. 9(b), a data sharing function unit 351 notifies a data sharing function application (reference numeral 330) of specific data (image data or text data).

[0066] As a result, the application for data sharing function (reference number 330) determines the attributes of the notified specific data. The application for data sharing function (reference number 330) also determines which of the multiple functions of the data sharing application 2 (reference number 340) to launch based on the determined attributes of the specific data, and generates a launch instruction. The application for data sharing function (reference number 330) also notifies the link launch unit 352 of the generated launch instruction.

[0067] When a launch instruction is notified from the data share function application (reference number 330), the link launch unit 352 notifies the notified launch instruction to the data share application 2 (reference number 340).

[0068] As a result, the data sharing application 2 (reference number 340) launches one of the multiple functions corresponding to the launch instruction. At this time, the data sharing application 2 (reference number 340) extracts specific data from the notified launch instruction and sets the extracted specific data, thereby sharing the specific data.

[0069] 9(a) shows a state in which a function corresponding to a launch instruction is launched in the data sharing application 2 (reference symbol 340), and a screen 900 for the data sharing application 2 (any of the screens for functional units A to D) is displayed on the display device 305. In this embodiment, the data sharing application 2 (reference symbol 340) has four types of functional units (functional units A to D).

[0070] The example in FIG. 9(a) shows a state in which image data 901 to 903 are set as specific data when any one of the screens for functional part A to D is displayed.

[0071] Any of the functional parts A to D of the data sharing application 2 (reference symbol 340) executes a corresponding function using the set specific data (image data 901 to 903). As a result, the data sharing application 2 (reference symbol 340) notifies the OS 350 of a service utilization request corresponding to the function. Furthermore, the OS 350 transmits a service utilization request corresponding to the launched function to the server device 110 via the communication device 306.

[0072] <Specific examples of specific data> Next, a specific example of the specific data notified to the data sharing function application (reference numeral 330) will be described. Fig. 10 is a diagram showing a specific example of the specific data. Among these, Fig. 10(a) shows a specific example in which the specific data is image data.

[0073] 10(a), image data 1010 includes properties 1011 and a body 1012. The properties 1011 store various attribute information such as the file name, image type, file size, shooting date and time, shooting location, image size, etc. Meanwhile, the body 1012 stores image information (pixel value of each pixel).

[0074] In this way, the image data 1010 includes the property 1011, and the application for the data sharing function (reference numeral 330) uses various attribute information stored in the property 1011 when determining the attributes of the image data.

[0075] 10B shows a specific example in which the specific data is text data. Text data is made up of a plurality of letters, numbers, symbols, or a combination thereof.

[0076] <Functional configuration of the application for data sharing function and data sharing application 2> Next, the detailed functional configuration of the application for the data share function (reference number 330) and the data share application 2 (reference number 340) will be described. Fig. 11 is a first diagram showing the detailed functional configuration of the application for the data share function and the data share application 2.

[0077] As shown in FIG. 11, the application for the data sharing function (reference numeral 330 ) includes an acquisition unit 1101 , an attribute determination unit 1102 , an image conversion unit 1103 , a URL generation unit 1104 , and a notification unit 1105 .

[0078] The acquisition unit 1101 acquires specific data (image data or text data) notified by the data sharing function unit 351. The acquisition unit 1101 also notifies the attribute determination unit 1102 of the acquired specific data.

[0079] The attribute determination unit 1102 is an example of a determination unit, and determines the attributes of the specific data notified by the acquisition unit 1101. The attribute determination unit 1102 first determines whether the notified specific data is image data or text data. Next, when the attribute determination unit 1102 determines that the specific data is image data, it determines detailed attributes of the image data.

[0080] Also, attribute determination unit 1102 notifies URL generation unit 1104 of the determination result. Furthermore, if attribute determination unit 1102 determines that the specific data is image data, it notifies image conversion unit 1103 of the image data, and if it determines that the specific data is text data, it notifies URL generation unit 1104 of the text data.

[0081] Image conversion unit 1103 is an example of a conversion unit, and converts the image data notified by attribute determination unit 1102 into a character string using a predetermined conversion method (for example, Base64). In addition, image conversion unit 1103 notifies URL generation unit 1104 of the converted character string.

[0082] Based on the determination result notified by the attribute determination unit 1102, the URL generation unit 1104 generates a URL (Uniform Resource Locator) for launching a function according to the attribute of the specific data.

[0083] The URL generated by URL generating section 1104 includes information for launching any one of functional sections A to D, and information indicating the type of specific data (image data or text data).

[0084] Furthermore, when the specified data is text data, URL generation unit 1104 incorporates the text data notified by attribute determination unit 1102 into the generated URL. On the other hand, when the specified data is image data, URL generation unit 1104 incorporates the character string notified by image conversion unit 1103 into the generated URL.

[0085] Furthermore, URL generating unit 1104 notifies notification unit 1105 of the URL in which the text data or the character string is embedded.

[0086] The notification unit 1105 notifies the link launching unit 352 of the URL notified by the URL generation unit 1104 as a launch instruction. When the link launching unit 352 is notified of the URL by the notification unit 1105, it notifies the notified URL as a launch instruction to the data sharing application 2 (reference numeral 340).

[0087] On the other hand, as shown in FIG. 11, a data sharing application 2 (reference numeral 340) has a screen generating section 1111, an image restoring section 1112, and functional sections 1113 (functional sections A to D).

[0088] The screen generating unit 1111 acquires the URL notified by the link launching unit 352 as a launch instruction.

[0089] Furthermore, when the information indicating the type of specific data included in the acquired URL is image data, screen generation unit 1111 extracts a character string embedded in the acquired URL and notifies image restoration unit 1112. Furthermore, screen generation unit 1111 acquires image data from image restoration unit 1112 in response to the notification of the character string.

[0090] Furthermore, if the information indicating the type of specific data included in the acquired URL is text data, screen generating unit 1111 extracts the text data embedded in the acquired URL.

[0091] Furthermore, the screen generating unit 1111 notifies the specific data (image data or text data) to a functional unit 1113 (any of functional units A to D) that has been launched based on the URL.

[0092] Furthermore, the screen generation unit 1111 notifies the OS 350 of a screen for the data share application 2 corresponding to the launched functional unit (any of the screens for functional units A to D). As a result, any of the screens for functional units A to D is displayed on the display device 305.

[0093] The image restoration unit 1112 is an example of a restoration unit, and when a character string is notified from the screen generation unit 1111, the image restoration unit 1112 restores image data from the notified character string using a predetermined restoration method (for example, Base64). In addition, the image restoration unit 1112 notifies the screen generation unit 1111 of the restored image data.

[0094] The functional units 1113 (functional units A to D) are functional units that realize the functions of the data sharing application 2 (reference symbol 340). The functional units 1113 (functional units A to D) realize each function using specific data notified by the screen generation unit 1111. The functional units 1113 (functional units A to D) notify the OS 350 of a service usage request according to the specific data to be shared.

[0095] <Examples of screens corresponding to each function> Next, a specific example of screens for data sharing application 2 (screens for functional parts A to D) corresponding to functional parts A to D will be described. Note that, here, an example will be described in which the service provided by server device 110 is a product buying and selling service, and functional parts A to D each have a function corresponding to the product buying and selling service.

[0096] Specifically, an example will be described in which functional unit A has an image search function for searching for products similar to image data from among products traded in a product trading service.

[0097] Also, an example will be described in which functional unit B has a keyword search function for searching for products matching a keyword including text data from among products traded in the product trading service.

[0098] Also, an example will be described in which the functional unit C has a listing function for carrying out procedures for listing a product to be bought and sold in the product buying and selling service.

[0099] In addition, an example will be described in which functional unit D has a sellability check function for checking whether a product included in image data is sellable when the product is put up for sale in a product buying and selling service.

[0100] Fig. 12 shows examples of screens for the data share application 2 corresponding to the respective functional units, of which Fig. 12(a) shows an image search screen 1210 corresponding to the image search function being displayed.

[0101] Image data including products similar to the shared image data is displayed in an area 1211 of the image search screen 1210. The image data displayed in the area 1211 is image data obtained as a search result by the server device 110 searching the service information storage unit 230 based on a service utilization request that uses the shared image data as a search key.

[0102] The image search function is launched based on the URL indicated by the reference numeral 1215. As shown in Fig. 12(a), the URL indicated by the reference numeral 1215 includes information for launching the image search function, information indicating the type of specific data, and a character string obtained by converting the image data.

[0103] FIG. 12(b) shows a keyword search screen 1220 corresponding to the keyword search function.

[0104] Image data including products associated with keywords matching the shared text data is displayed in an area 1221 of the keyword search screen 1220. The image data displayed in the area 1221 is image data obtained as a search result by the server device 110 searching the service information storage unit 230 based on a service utilization request that uses the shared text data as a search key.

[0105] The keyword search function is launched based on the URL indicated by the reference numeral 1225. As shown in Fig. 12(b), the URL indicated by the reference numeral 1225 includes information for launching the keyword search function, information indicating the type of specific data, and text data.

[0106] FIG. 12(c) shows a listing screen 1230 corresponding to the listing function.

[0107] The shared image data is displayed in an area 1231 of the listing screen 1230. Furthermore, detailed information of the product included in the shared image data is displayed in an area 1232 of the listing screen 1230. Furthermore, the name and description of the product included in the shared image data are displayed in an area 1233 of the listing screen 1230. The listing request including the image data and various information displayed in the areas 1231 to 1233 is transmitted to the server device 110 as a service usage request.

[0108] The auction display function is launched based on the URL indicated by the reference numeral 1235. As shown in Fig. 12(c), the URL indicated by the reference numeral 1235 includes information for launching the auction display function, information indicating the type of specific data, and a character string obtained by converting the image data.

[0109] FIG. 12(d) shows a sellability check screen 1240 displayed, which corresponds to the sellability check function.

[0110] Area 1241 of sellability check screen 1240 displays the average selling price of products similar to the shared image data. Area 1242 of sellability check screen 1240 displays images of sold-out products and the sold-out prices of the sold-out products among products similar to the shared image data. Area 1243 of sellability check screen 1240 displays images of products currently on sale and the prices of the products currently on sale among products similar to the shared image data.

[0111] The information displayed in the areas 1241 to 1243 is information obtained by the server device 110 searching the service information storage unit 230 based on a service utilization request that uses the shared image data as a search key.

[0112] The sellability check function is launched based on the URL indicated by reference numeral 1245. As shown in Fig. 12(d), the URL indicated by reference numeral 1245 contains information for launching the sellability check function, information indicating the type of specific data, and a character string obtained by converting the image data.

[0113] <Service usage process flow> Next, a description will be given of the flow of a service usage process in the service usage system 100. Fig. 13 is an example of a first sequence diagram showing the flow of a service usage process.

[0114] In step S1301, the general-purpose application (reference numeral 310) performs a launch process based on a launch operation by the user 140.

[0115] In step S1302, the general-purpose application (reference numeral 310) acquires specific data based on a specific operation by the user 140, and notifies the OS 350 of the specific data.

[0116] In step S1303, in response to the notification of the specific data, the OS 350 displays a share button and accepts a share instruction. In response to the acceptance of the share instruction, the OS 350 displays a list of data share applications and accepts a data share application selection operation by the user 140. Furthermore, in response to the acceptance of the data share application selection operation, the OS 350 notifies the application for data share function (reference numeral 330) of the specific data.

[0117] In step S1304, when the application for the data sharing function (reference numeral 330) acquires the specific data, it executes a data sharing process to notify a launch instruction (URL) to the OS 350. Details of the data sharing process will be described later with reference to FIG.

[0118] In step S1305, the OS 350 notifies the data sharing application 2 (reference numeral 340) of the launch command (URL).

[0119] In step S1306, the data sharing application 2 (reference numeral 340) executes a launch process to notify the OS 350 of a service usage request. In response to the service usage request being notified to the OS 350, the data sharing application 2 receives service content from the OS 350. Details of the launch process will be described later with reference to FIG.

[0120] In step S1307, the OS 350 transmits a service utilization request to the server device 110.

[0121] In step S1308, server device 110 executes a service providing process in response to the transmitted service utilization request, and also transmits the service content obtained by executing the service providing process.

[0122] In step S1309, the OS 350 receives the service content and notifies the data sharing application 2 (reference numeral 340).

[0123] <Details of data sharing process> Next, the data sharing process (step S1304 in FIG. 13) will be described in detail. FIG. 14 is an example of a flowchart showing the flow of the data sharing process.

[0124] In step S 1401 , the acquisition unit 1101 acquires specific data from the OS 350 .

[0125] In step S1402, the attribute determination unit 1102 determines the type of the specified data. If it is determined in step S1402 that the type of the specified data is image data, the process proceeds to step S1403.

[0126] In step S1403, the attribute determination unit 1102 determines whether the number of image data (number of images) is more than one. If it is determined in step S1403 that the number is more than one (Yes in step S1403), the process proceeds to step S1404.

[0127] In step S1404, the attribute determining unit 1102 determines that the function to be launched is an "auction function."

[0128] In step S1405, the image conversion unit 1103 converts the image data into a character string.

[0129] In step S1406, URL generating unit 1104 incorporates the character string obtained by converting the image data into a URL including information for launching the auction display function and information indicating the type of specific data (image data), and proceeds to step S1441.

[0130] On the other hand, if it is determined in step S1403 that the number of the images is not multiple (No in step S1403), the process proceeds to step S1411.

[0131] In step S1411, the attribute determination unit 1102 determines whether or not the image data is image data output from the imaging device 307. If it is determined in step S1411 that the image data is image data output from the imaging device 307 (Yes in step S1411), the process proceeds to step S1412.

[0132] In step S1412, the attribute determining unit 1102 determines that the function to be launched is a "sales check function."

[0133] In step S1413, the image conversion unit 1103 converts the image data into a character string.

[0134] In step S1414, URL generating unit 1104 incorporates the character string obtained by converting the image data into a URL including information for launching a sellability check function and information indicating the type of specific data (image data), and proceeds to step S1441.

[0135] On the other hand, if it is determined in step S1411 that the image data is not image data output from the imaging device 307 (No in step S1411), the process proceeds to step S1421.

[0136] In step S1421, the attribute determining unit 1102 determines that the function to be launched is an "image search function."

[0137] In step S1422, the image conversion unit 1103 converts the image data into a character string.

[0138] In step S1423, URL generating unit 1104 incorporates the character string obtained by converting the image data into a URL including information for starting up an image search function and information indicating the type of specific data (image data), and proceeds to step S1441.

[0139] On the other hand, if it is determined in step S1402 that the type of the specific data is text data, the process proceeds to step S1431.

[0140] In step S1431, the attribute determining unit 1102 determines that the function to be launched is a "keyword search function."

[0141] In step S1432, URL generating section 1104 incorporates the text data into a URL including information for starting up a keyword search function and information indicating the type of specific data (text data), and proceeds to step S1441.

[0142] In step S1441, the notification unit 1105 notifies the OS 350 of the URL, and the process returns to step S1305 (FIG. 13).

[0143] <Details of launch process> Next, the start-up process (step S1306 in FIG. 13) will be described in detail. FIG. 15 is a flowchart showing the flow of the start-up process.

[0144] In step S 1501 , the screen generation unit 1111 acquires the URL notified by the OS 350 .

[0145] In step S1502, the screen generating unit 1111 determines the type of the specific data based on the information indicating the type of the specific data included in the URL. If it is determined in step S1502 that the type of the specific data is image data, the process proceeds to step S1503.

[0146] In step S1503, the screen generating unit 1111 determines whether the URL includes information for launching the listing function. If it is determined in step S1503 that the URL includes information for launching the listing function (Yes in step S1503), the process proceeds to step S1504.

[0147] In step S1504, the screen generation unit 1111 extracts a character string from the URL, and the image restoration unit 1112 restores the extracted character string to generate image data.

[0148] In step S1505, the auction function is launched and image data is set.

[0149] In step S1506, the screen generating unit 1111 generates and displays a listing screen corresponding to the listing function.

[0150] In step S1507, the functional unit 1113 (functional unit C in this case) transmits a listing request for listing the product to the server device 110 as a service use request.

[0151] On the other hand, if it is determined in step S1503 that the information for launching the auction display function is not included (No in step S1503), the process proceeds to step S1511.

[0152] In step S1511, the screen generating unit 1111 determines whether the URL includes information for starting up a sellability check function. If it is determined in step S1511 that the URL includes information for starting up a sellability check function (Yes in step S1511), the process proceeds to step S1512.

[0153] In step S1512, the screen generation unit 1111 extracts a character string from the URL, and the image restoration unit 1112 restores the extracted character string to generate image data.

[0154] In step S1513, a sellability check function is started and image data is set.

[0155] In step S1514, the functional unit 1113 (here, functional unit D) transmits a service utilization request for checking whether the product included in the set image data can be sold to the server device 110. In addition, the functional unit 1113 acquires the service content in response to transmitting the service utilization request.

[0156] In step S1515, the screen generating unit 1111 generates and displays a sellability check screen based on the acquired service details.

[0157] On the other hand, if it is determined in step S1511 that the information for starting up the sellability check function is not included (No in step S1511), the process proceeds to step S1521.

[0158] In step S1521, the screen generation unit 1111 extracts a character string from the URL, and the image restoration unit 1112 restores the extracted character string to generate image data.

[0159] In step S1522, the image search function is launched and image data is set.

[0160] In step S1523, the functional unit 1113 (here, functional unit A) transmits a service utilization request for searching image data including a product similar to the set image data to the server device 110. In addition, the functional unit 1113 acquires the service content in response to transmitting the service utilization request.

[0161] In step S1524, the screen generating unit 1111 generates and displays an image search screen based on the acquired service content.

[0162] On the other hand, if it is determined in step S1502 that the type of the specified data is text data, the process proceeds to step S1531.

[0163] In step S1531, the screen generating unit 1111 extracts text data. Furthermore, when the keyword search function is started, the screen generating unit 1111 sets the extracted text data in the functional unit 1113 (functional unit A).

[0164] In step S1532, the functional unit 1113 transmits a service usage request for searching image data including a product associated with a keyword matching the set text data to the server device 110. In addition, the functional unit 1113 acquires the service content in response to transmitting the service usage request.

[0165] In step S1533, the screen generating unit 1111 generates and displays a keyword search screen based on the acquired service content.

[0166] <Summary> As is clear from the above description, the terminal device according to the first embodiment The device has an acquisition unit that acquires specific data that is identified when the general-purpose application is launched. The data sharing application 2 includes a notification unit that notifies the data sharing application 2 of a launch instruction to launch a function corresponding to an attribute of specific data, among a plurality of functions of the data sharing application 2 specified by a user, the launch instruction being associated with the specific data.

[0167] In this way, according to the terminal device according to the first embodiment, when specific data is shared between a general-purpose application and the data sharing application 2, the function to be launched can be switched depending on the attribute of the specific data.

[0168] As a result, the terminal device according to the first embodiment allows the user to receive service content according to the attributes of the specific data. As a result, the terminal device according to the first embodiment can improve the convenience for the user when sharing data among a plurality of applications.

[0169] [Second embodiment] In the above first embodiment, an example has been described in which, when a launch instruction is notified from the data sharing function application (reference numeral 330), the link launch unit 352 notifies the data sharing application 2 of the launch instruction.

[0170] That is, in the case of the above-described first embodiment, an example has been described in which the launch instruction notified from the application for data sharing function (reference numeral 330) is a URL indicating the data sharing application 2. Also, an example has been described in which the link launch unit 352 notifies the data sharing application of the launch instruction directly.

[0171] In contrast, in the second embodiment, the application for the data sharing function (reference numeral 330) once transmits a start-up instruction to the server device. After that, the server device notifies the data sharing application 2 of the start-up instruction. Note that the server device referred to here may be the server device 110 described in the first embodiment above, or any other server device different from the server device 110 described in the first embodiment above. However, in the second embodiment, a case will be described in which a CDN (Content Delivery Network) server device is used as the other server device different from the server device 110 described in the first embodiment above.

[0172] In this way, by going through the server device, even if the OS 350 is designed not to accept a launch instruction directly specifying a data sharing application from the data sharing function application (reference numeral 330), it can be launched indirectly.

[0173] In the second embodiment, in order to distinguish between a start-up instruction for a CDN server device and a start-up instruction for the data sharing application 2, the following definitions are used. · Web launch instruction: A launch instruction sent to a CDN server device, which includes a URL indicating a Web page (Web URL). · Application launch instruction: A launch instruction notified to the data sharing application 2, which includes a URL indicating the application (URL for the application).

[0174] The second embodiment will be described below, focusing on the differences from the first embodiment.

[0175] <System configuration of the service usage system> First, the system configuration of the service utilization system will be described. Fig. 16 is a second diagram showing an example of the system configuration of the service utilization system.

[0176] 16 differs from the system configuration of the service utilization system described with reference to Fig. 1 in that the service utilization system 1600 shown in Fig. 16 includes a CDN server device 1610. When the CDN server device 1610 receives a Web launch instruction including a Web URL from the terminal device 120, it replaces the Web URL with an application URL and transmits an application launch instruction to the terminal device 120.

[0177] <Processing details in the terminal device> Next, details of the processing contents processed in the terminal device 120 will be described. As in the first embodiment, in the second embodiment, the terminal device 120 performs the processing shown in Fig. 5 to Fig. 8. Meanwhile, in the case of the terminal device 120 in the second embodiment, instead of the processing shown in Fig. 9, the processing shown in Fig. 17 is performed.

[0178] Fig. 17 is a sixth diagram showing a specific example of the processing contents of the terminal device. As shown in Fig. 17, when the data sharing function application (reference number 1710) is notified of specific data, it determines the attribute of the specific data. Furthermore, the data sharing function application (reference number 1710) determines which of a plurality of functions of the data sharing application 2 (reference number 340) is to be launched based on the determined attribute of the specific data. Furthermore, the data sharing function application (reference number 1710) generates a Web launch instruction including a Web URL based on the determined function. Furthermore, the data sharing function application (reference number 1710) notifies the launching unit 1720 of the generated Web launch instruction.

[0179] When a Web launch instruction is notified from the data sharing function application (reference numeral 1710), the launch unit 1720 notifies the CDN server device 1610 of the notified Web launch instruction.

[0180] As a result, the CDN server device 1610 replaces the Web URL included in the Web launch instruction with an application URL indicating the data sharing application 2, and generates an application launch instruction. The application launch instruction generated by the CDN server device 1610 is notified to the launch unit 1720.

[0181] When the launch unit 1720 receives an application launch instruction from the CDN server device 1610, it notifies the data sharing application 2 (reference numeral 340) of the application launch instruction.

[0182] As a result, the data sharing application 2 (reference number 340) launches a function corresponding to the application launch instruction from among a plurality of functions. At this time, the data sharing application 2 (reference number 340) extracts specific data from the notified application launch instruction and sets the extracted specific data, thereby sharing the specific data.

[0183] <Functional configuration of the application for data sharing function and data sharing application 2> Next, a detailed description will be given of the functional configuration of the application for the data share function (reference number 1710) and the data share application 2 (reference number 340). Fig. 18 is a diagram showing the detailed functional configuration of the application for the data share function and the data share application 2.

[0184] The difference from Figure 11 is that in Figure 18, URL generation unit 1804 generates a Web URL for launching a function corresponding to the attributes of the specific data based on the judgment result notified by attribute judgment unit 1102.

[0185] The Web URL generated by URL generation unit 1804 is equivalent to the URL generated by URL generation unit 1104 in FIG. 11 in that it contains information for launching one of the functions of functional units A to D and information indicating the type of specific data.

[0186] Also, the Web URL generated by the URL generation unit 1804 is equal to the URL generated by the URL generation unit 1104 in FIG. 11 in that the text data notified by the attribute determination unit 1102 or the character string notified by the image conversion unit 1103 is incorporated therein.

[0187] However, as described above, the URL generated by the URL generation unit 1104 in FIG. 11 is a URL indicating an app, while the URL generated by the URL generation unit 1804 in FIG. 18 is different in that it is a URL indicating a web page.

[0188] The notification unit 1105 notifies the start-up unit 1720 of the Web URL notified by the URL generation unit 1804 as a Web start-up instruction. In the start-up unit 1720, when the Web URL is notified by the notification unit 1105, the notified Web URL is transmitted to the CDN server device 1610.

[0189] In response to transmitting the Web URL to the CDN server device 1610, the start-up unit 1720 acquires the app URL as an app start-up instruction from the CDN server device 1610. When the app URL is acquired, the start-up unit 1720 notifies the data sharing application 2 (reference numeral 340) of the acquired app URL as an app start-up instruction.

[0190] <Specific Examples of Web Start-Up Instruction and App Start-Up Instruction> Next, specific examples of the Web start-up instruction and the app start-up instruction for starting up functional units A to D will be described. Here, as in the first embodiment, the service provided by the server device 110 is a product trading service, and the case where the functional units A to D correspond to, for example, an image search function, a keyword search function, a listing function, and a sellability check function will be described.

[0191] 19(a), when launching the image search function, the application for the data sharing function (reference number 1710) notifies the launching unit 1720 of a Web URL indicated by reference number 1915. Reference number 1915 is configured from a URL indicating a Web page. On the other hand, the application URL acquired by the launching unit 1720 from the CDN server device 1610 is configured from a URL indicating an application, as indicated by reference number 1215.

[0192] 19(b), when launching the keyword search function, the data sharing function application (reference number 1710) notifies the launching unit 1720 of a Web URL indicated by reference number 1925. Reference number 1925 is configured from a URL indicating a Web page. On the other hand, the application URL acquired by the launching unit 1720 from the CDN server device 1610 is configured from a URL indicating an application, as indicated by reference number 1225.

[0193] 19(c), when launching the auction display function, the data sharing function application (reference number 1710) notifies the launching unit 1720 of a Web URL indicated by reference number 1935. Reference number 1935 is configured from a URL indicating a Web page. On the other hand, the application URL acquired by the launching unit 1720 from the CDN server device 1610 is configured from a URL indicating an application, as indicated by reference number 1235.

[0194] 19(d), when launching the sellability check function, the data sharing function application (reference number 1710) notifies the launching unit 1720 of a Web URL indicated by reference number 1945. Reference number 1945 is configured from a URL indicating a Web page. On the other hand, the application URL acquired by the launching unit 1720 from the CDN server device 1610 is configured from a URL indicating an application, as indicated by reference number 1245.

[0195] <Service usage process flow> Next, a description will be given of the flow of service usage processing in the service usage system 1600. Fig. 20 is an example of a second sequence diagram showing the flow of the service usage processing. Note that the difference from the first sequence diagram shown in Fig. 13 is steps S2000 to S2003.

[0196] In step S2000, the application for the data sharing function (reference numeral 330) acquires the specific data and then executes a data sharing process to notify the OS 350 of a Web launch instruction.

[0197] In step S 2001 , the OS 350 transmits a Web launch instruction to the CDN server device 1610 .

[0198] In step S 2002 , upon receiving the Web launch instruction, the CDN server device 1610 performs a replacement process of replacing the Web URL with the application URL, and transmits the application URL to the OS 350 .

[0199] In step S2003, the OS 350 notifies the data sharing application 2 (reference numeral 340) of the application URL as an instruction to launch the application.

[0200] <Summary> As is clear from the above description, the terminal device according to the second embodiment The device has an acquisition unit that acquires specific data that is identified when the general-purpose application is launched. The data sharing application 2 includes a notification unit that notifies the data sharing application 2 of a launch instruction to launch a function corresponding to an attribute of specific data, among a plurality of functions of the data sharing application 2 specified by a user, the launch instruction being associated with the specific data. When a launch instruction is notified to the data sharing application 2, a launch instruction including a URL indicating a Web page is notified. The launch instruction including the URL indicating the Web page is replaced by a URL indicating the data sharing application 2 in the CDN server device, and is notified to the data sharing application 2.

[0201] In this way, the terminal device according to the second embodiment can switch the function to be launched according to the attribute of the specific data when specific data is shared between a general-purpose application and the data sharing application 2. At that time, the terminal device according to the second embodiment can notify the launch instruction via the CDN server device.

[0202] As a result, in the terminal device according to the second embodiment, even if the launch unit 1720 of the OS 350 is designed not to accept a launch instruction including an application URL, it is possible to indirectly launch the data sharing application.

[0203] As a result, the terminal device according to the second embodiment can provide the same effects as those of the first embodiment.

[0204] [Third embodiment] In the above first and second embodiments, an example has been described in which the attribute of specific data is determined in the data sharing function application (reference number 330). In contrast, in the third embodiment, an example will be described in which the attribute of specific data is determined in the data sharing application 2 (reference number 340).

[0205] <Functional configuration of the application for data sharing function and data sharing application 2> Fig. 21 is a third diagram showing details of the functional configuration of the data share function application and the data share application 2. The difference from Fig. 11 is that Fig. 22 does not have the attribute determination unit 1102.

[0206] As shown in FIG. 21, the application for the data sharing function (reference numeral 330 ) includes an acquisition unit 1101 , an image conversion unit 1103 , a URL generation unit 1104 , and a notification unit 1105 .

[0207] Acquiring unit 1101 acquires specific data (image data or text data) notified by data sharing function unit 351. If the acquired specific data is text data, acquiring unit 1101 notifies URL generating unit 1104 of the acquired specific data, and if the acquired specific data is image data, acquiring unit 1101 notifies image converting unit 1103 of the acquired specific data.

[0208] The image conversion unit 1103 converts the image data into a character string using a predetermined conversion method (for example, Base64), and notifies the URL generation unit 1104 of the converted character string.

[0209] The URL generating unit 1104 generates a URL for launching the data sharing application 2 (reference number 340). The URL for launching the data sharing application 2 (reference number 340) includes the following: -It does not contain information for starting up any of the functions from functional unit A to functional unit D. Contains information indicating the type of specific data (image data or text data).

[0210] Furthermore, if the specified data is text data, URL generating unit 1104 incorporates the text data into the generated URL. On the other hand, if the specified data is image data, URL generating unit 1104 incorporates the character string notified by image conversion unit 1103 into the generated URL.

[0211] Furthermore, URL generating unit 1104 notifies notification unit 1105 of the URL in which the text data or character string is embedded and in which no function is specified.

[0212] The notification unit 1105 notifies the link launching unit 352 of the URL with no function specified, notified by the URL generation unit 1104, as a launch instruction. When the link launching unit 352 is notified of the URL with no function specified by the notification unit 1105, it notifies the notified URL with no function specified to the data sharing application 2 (reference symbol 340) as a launch instruction.

[0213] On the other hand, as shown in FIG. 21, a data sharing application 2 (reference numeral 340) has a screen generating unit 1111, an image restoring unit 1112, an attribute determining unit 2101, and functional units 1113 (functional units A to D).

[0214] The screen generating unit 1111 acquires the URL with no function specified that has been notified by the link launching unit 352 as a launch instruction.

[0215] Furthermore, when the information indicating the type of specific data included in the acquired URL with no function specified is image data, screen generation unit 1111 extracts a character string embedded in the acquired URL with no function specified, and notifies image restoration unit 1112. Furthermore, screen generation unit 1111 acquires image data from image restoration unit 1112 in response to the notification of the character string.

[0216] Furthermore, if the information indicating the type of specific data included in the acquired function-unspecified URL is text data, screen generating unit 1111 extracts the text data embedded in the acquired URL.

[0217] In addition, the screen generation unit 1111 - Information indicating the type of specific data contained in the acquired function-unspecified URL; A determination result obtained from the attribute determination unit 2101 in response to notification of the image data obtained from the image restoration unit 1112 to the attribute determination unit 2101; Based on this, a function to be started up is determined. As a result, one of the functional units A to D is started up.

[0218] Moreover, the screen generation unit 1111 notifies the launched functional unit of specific data (image data or text data).

[0219] Furthermore, the screen generation unit 1111 notifies the OS 350 of a screen for the data share application 2 corresponding to the launched functional unit (any of the screens for functional units A to D). As a result, any of the screens for functional units A to D is displayed on the display device 305.

[0220] The attribute determination unit 2101 is an example of a determination unit, which determines the attributes of image data notified by the screen generation unit 1111, and notifies the screen generation unit 1111 of the determination result.

[0221] <Summary> As is clear from the above description, the terminal device according to the third embodiment The device has an acquisition unit that acquires specific data that is identified when the general-purpose application is launched. The device has a notification unit that notifies the data sharing application 2 of a launch instruction to launch the data sharing application 2 designated by the user, the launch instruction being associated with specific data. The data sharing application 2 includes a determination unit that, when a launch instruction is notified to the data sharing application 2, determines a function corresponding to the attribute of the specific data associated with the launch instruction, from among a plurality of functions that the data sharing application 2 has. Of the multiple functions possessed by the data sharing application 2, the determined function is launched.

[0222] In this way, according to the terminal device of the third embodiment, when specific data is shared between a general-purpose application and a data sharing application 2, the function to be launched can be switched depending on the attributes of the specific data, as in the first embodiment.

[0223] As a result, the terminal device according to the third embodiment allows the user to receive service content according to the attributes of the specific data. As a result, the terminal device according to the third embodiment can improve the convenience for the user when sharing data among a plurality of applications.

[0224] [Fourth embodiment] In the above first to third embodiments, an example has been described in which a character string obtained by converting text data or image data is incorporated into a URL. However, instead of incorporating the text data or image data into a URL, the text data or image data may be stored in a predetermined area in memory 302. In such a configuration, when a launch instruction is notified, data sharing application 2 (reference symbol 340) acquires the text data or image data by referring to a predetermined area in memory 302.

[0225] Alternatively, information indicating the storage location in memory 302 where the text data or image data is stored may be incorporated into the launch instruction and notified to data sharing application 2 (reference numeral 340). However, the storage location of image data is not limited to memory 302 and may be, for example, any external server device.

[0226] Furthermore, in the first to third embodiments, a camera application, an album application, an SNS application, and a browser are given as examples of general-purpose applications, but the general-purpose applications are not limited to these.

[0227] In the above first to third embodiments, the data-sharing application 2 has been described as an application used when using a product buying and selling service. However, the data-sharing application 2 is not limited to an application used when using a product buying and selling service.

[0228] The present invention is not limited to the configurations shown here, such as the configurations described in the above embodiments, and combinations with other elements. These points can be changed without departing from the spirit of the present invention, and can be appropriately determined according to the application form. [Explanation of symbols]

[0229] 100: Service usage system 110: Server device 120: Terminal device 210: Service Department 350:OS 351:Data sharing function section 352: Link launch section 500: Home screen 610: Camera app screen 620: Album app screen 630: SNS app screen 640: Browser screen 700: Share button 800: List of data sharing applications 1101: Acquisition Department 1102: Attribute determination section 1103: Image conversion unit 1104 :URL generation part 1105: Notification Department 1111: Screen generation section 1112: Image restoration unit 1113: Functional section 1210: Image search screen 1220: Keyword search screen 1230: Listing screen 1240: Selling check screen 1610: CDN server device 1720: Start-up Department 1804 :URL generation part 2101: Attribute judgment section

Claims

1. An acquisition unit that acquires the specified data in a state where another application is launched; a generation unit that generates, when a user designates a specific application and an attribute of the specified data is determined, an instruction to launch a function corresponding to the attribute among a plurality of functions of the specific application, the instruction being associated with the specified data; a notification unit that notifies the predetermined application of the instruction, When the specified data is image data, a function to be launched in the predetermined application is changed depending on at least one of the number of the image data and property information included in the image data. Terminal device.

2. When the specified data is image data, Whether the number of image data satisfies a predetermined condition, or Whether the image data is image data output from an imaging device included in the terminal device; A function to be launched in the predetermined application is changed depending on at least one of the above. The terminal device according to claim 1 .

3. The terminal device according to claim 1 , wherein, when the instruction is notified, a function corresponding to the instruction is started up among a plurality of functions of the predetermined application.

4. The terminal device according to claim 3, wherein, upon notification of the instruction, a function corresponding to the instruction transitions from a not activated state to an activated state, and a screen corresponding to the function corresponding to the instruction transitions from a not displayed state to a displayed state to a user.

5. The terminal device of claim 3, wherein, upon notification of the instruction, a state transition occurs from a state in which a function corresponding to the instruction is activated and a screen corresponding to the function corresponding to the instruction is not displayed to the user to a state in which a function corresponding to the instruction is activated and a screen corresponding to the function corresponding to the instruction is displayed to the user.

6. The terminal device according to claim 1 , wherein the predetermined application includes an application that is not running at the time when the instruction is notified.

7. A conversion unit that converts the specified data into a predetermined character string when the specified data is image data, The terminal device according to claim 1 , wherein the notification unit notifies the predetermined application of the instruction associated with the converted character string.

8. a restoration unit that restores image data from the character string associated with the instruction, 8. The terminal device according to claim 7, wherein the restored image data is set to a function according to the instruction.

9. The terminal device according to claim 1 , wherein the property information includes any one of a file name, an image type, a file size, a shooting location, a shooting date and time, and an image size of the image data.

10. The terminal device according to claim 1 , wherein the instruction includes a URL indicating the predetermined application.

11. 2. The terminal device according to claim 1, wherein the instruction includes a URL indicating a Web page, and the specific application is notified of the replaced instruction in which the URL indicating the Web page has been replaced by the URL indicating the specific application by the server device.

12. A computer of a terminal device, An acquisition step of acquiring the specified data in a state where another application is launched; a generating step of generating an instruction to launch a function corresponding to the attribute of the specified data among a plurality of functions of the specified application when an attribute of the specified data is determined by designating a specific application by a user, the instruction being associated with the specified data; a notification step of notifying the predetermined application of the instruction; When the specified data is image data, a function to be launched in the predetermined application is changed depending on at least one of the number of the image data and property information included in the image data. How to share data.

13. The terminal device computer An acquisition step of acquiring the specified data in a state where another application is launched; a generating step of generating an instruction to launch a function corresponding to the attribute of the specified data among a plurality of functions of the specified application when an attribute of the specified data is determined by designating a specific application by a user, the instruction being associated with the specified data; a notification step of notifying the predetermined application of the instruction; When the specified data is image data, a function to be launched in the predetermined application is changed depending on at least one of the number of the image data and property information included in the image data. program.

Images