JP6235741B2 - Terminal device, information transmission method, and information transmission program - Google Patents

Description

  The present invention relates to a terminal device, an information transmission method, and an information transmission program.

  In recent years, smart devices such as smartphones and tablet terminals have become widespread. A user who uses such a terminal device such as a smart device acquires information using an application or a web browser installed in the terminal device. Therefore, a technique for estimating the identity of a terminal device based on information regarding the terminal device that requests acquisition of information is provided.

Japanese Patent No. 5580372

  However, in the above-described conventional technology, it is not always possible to appropriately estimate the same terminal device and appropriately associate information collected from the same terminal device. For example, even when the information regarding the terminal device is similar, there is a possibility that the terminal device is different, and information collected from the same terminal device cannot always be appropriately associated.

  The present application has been made in view of the above, and an object thereof is to provide a terminal device, an information transmission method, and an information transmission program that appropriately associate information collected from the same terminal device.

  A terminal device according to the present application is a terminal device having an application and a browser, and the application sends the terminal device acquired by the application to the browser instructed to perform predetermined processing from the application. A providing unit that provides terminal information for identification at a timing based on an instruction of the predetermined process, and the browser includes the terminal information provided by the providing unit and a cookie corresponding to a predetermined server device; And a transmission unit that transmits information to the predetermined server device when the application transits to the browser.

  According to one aspect of the embodiment, there is an effect that information collected from the same terminal device can be appropriately associated.

FIG. 1 is a diagram illustrating an example of a pegging process according to the embodiment. FIG. 2 is a diagram illustrating an example of the associating process according to the embodiment. FIG. 3 is a diagram illustrating a configuration example of the terminal device according to the embodiment. FIG. 4 is a diagram illustrating an example of a terminal information storage unit according to the embodiment. FIG. 5 is a diagram illustrating an example of the cookie information storage unit according to the embodiment. FIG. 6 is a diagram illustrating a configuration example of the server apparatus according to the embodiment. FIG. 7 is a diagram illustrating an example of a tied information storage unit according to the embodiment. FIG. 8 is a diagram illustrating an example of the cookie information storage unit according to the embodiment. FIG. 9 is a sequence diagram illustrating a linking process procedure according to the embodiment. FIG. 10 is a sequence diagram illustrating a pegging process procedure according to the embodiment. FIG. 11 is a diagram illustrating an example of the associating process at the first activation of the application according to the embodiment. FIG. 12 is a diagram illustrating an example of the associating process according to the modification. FIG. 13 is a diagram illustrating an example of the associating process according to the modification. FIG. 14 is a hardware configuration diagram illustrating an example of a computer that realizes the function of the terminal device.

  Hereinafter, a terminal device, an information transmission method, an information providing program, and an embodiment for implementing an information transmission program (hereinafter referred to as “embodiment”) according to the present application will be described in detail with reference to the drawings. Note that the terminal device, the information transmission method, the information providing program, and the information transmission program according to the present application are not limited by this embodiment. In the following embodiments, the same portions are denoted by the same reference numerals, and redundant description is omitted.

(Embodiment)
[1. (Pegging process)
First, an example of the pegging process according to the embodiment will be described with reference to FIGS. 1 and 2. 1 and 2 are diagrams illustrating an example of a pegging process according to the embodiment. Specifically, FIG. 1 is a diagram illustrating an example of a linking process when a transition is made from an application (hereinafter, sometimes referred to as “app”) to a browser. FIG. 2 is a diagram illustrating an example of the associating process when transitioning from a browser to an application. The terminal device 100 illustrated in FIGS. 1 and 2 transmits information associated with the transition between the application and the browser (hereinafter, may be referred to as “association information”) to the server device 10.

  As shown in FIGS. 1 and 2, the associating system 1 includes a terminal device 100 and a server device 10. The terminal device 100 and the server device 10 are connected to be communicable by wire or wireless via a predetermined communication network (not shown). 1 and FIG. 2 may include a plurality of terminal devices 100 and a plurality of server devices 10.

  The terminal device 100 is an information processing device used by a user. The terminal device 100 activates an application or browser installed in the terminal device 100 or performs various processes in accordance with a user operation. Also, the terminal device 100 transmits information associated with the transition between the application and the browser to the server device 10. Hereinafter, the terminal device 100 may be referred to as a user. That is, hereinafter, the user can be read as the terminal device 100. In the present embodiment, a case where a smartphone is used as the terminal device 100 will be described as an example. The terminal device 100 described above is not limited to a smartphone, and may be, for example, a tablet terminal, a notebook PC (Personal Computer), a desktop PC, a mobile phone, a PDA (Personal Digital Assistant), or the like. .

  The server device 10 is an information processing device that performs a linking process for registering the linking information received from the terminal device 100. The server device 10 may provide the association information to an external information processing device, for example, an advertisement distribution device. The server device 10 may be an advertisement distribution device that distributes advertisements based on the association information.

  From here, based on FIG. 1, the association process in the case of transition from an application to a browser will be described. In the terminal device 100 shown on the left side in FIG. 1, the application A (hereinafter referred to as “application A11”) is activated, and the application A11 is displayed on the terminal device 100. Here, the application A11 installed in the terminal device 100 includes a predetermined SDK (Software Development Kit). Hereinafter, the SDK of the application A11 is referred to as a development kit SD11. Here, the development kit SD11 of the application A11 can acquire terminal information for identifying the terminal device 100 from the storage unit 120 (terminal information storage unit 121) of the terminal device 100. Details of the storage unit 120 and the terminal information storage unit 121 will be described later. Hereinafter, terminal information for identifying the terminal device 100 is referred to as a terminal ID.

  As shown in FIG. 1, the user presses the button AB11 of the application A11 displayed on the terminal device 100 (step S11). In the example illustrated in FIG. 1, the user presses a button AB <b> 11 labeled “Get App B” displayed on the terminal device 100. And application A11 acquires terminal ID from the terminal information storage part 121 of the terminal device 100 (step S12). Note that the application A11 may acquire the terminal ID before step S11.

  After the button AB11 of the application A11 is pressed, the terminal device 100 transitions from the application A11 to the browser B11 (step S13). For example, if the browser B11 is not activated, the terminal device 100 activates the browser B11. Here, when the application A11 transitions to the browser B11 in step S13, the application A11 provides the terminal ID to the browser B11.

  Thereafter, in the example illustrated in FIG. 1, the browser B <b> 11 is displayed on the terminal device 100. The browser B11 associates the cookie information extracted from the HTTP (HyperText Transfer Protocol) cookie (hereinafter also referred to as “cookie”) C11 with the terminal ID provided by the application A11 (step S14). . For example, the browser B11 extracts cookie information related to a server device specified by the application A11 (hereinafter may be simply referred to as “server”), and associates it with the terminal ID provided by the application A11.

  Thereafter, the browser B11 transmits the terminal ID provided by the application A11 and the extracted cookie information as association information to the server device 10 (step S15). When the browser B11 transitions from the application A11 to the browser B11, for example, the browser B11 transmits the cookie information and the terminal ID to the server device 10 by a function such as a redirector.

  The server device 10 that has received the association information from the terminal device 100 registers the received association information (step S16). For example, when the terminal ID in the received association information has already been registered, the server device 10 adds the cookie information in the received association information as cookie information corresponding to the registered terminal ID. Specifically, when the terminal ID in the received association information is “TID01”, the server device 10 uses the cookie information in the received association information as cookie information corresponding to the registered terminal ID “TID01”. to add. Thereby, the server device 10 associates the terminal ID with the cookie information.

  Further, the terminal device 100 transitions the display of the browser B11 (step S17). In the example illustrated in FIG. 1, a web page W11 that prompts the user to download the application B is displayed on the browser B11. Note that step S17 may be performed simultaneously with step S15 or before step S15. Further, the terminal device 100 is not limited to the display transition of the browser B11, and may start an application that downloads the application B and display the application that downloads the application B.

  Next, based on FIG. 2, the association process in the case of transition from the browser to the application will be described. In the terminal device 100 shown on the left side in FIG. 2, the browser is activated, and the browser B11 is displayed on the terminal device 100.

  As shown in FIG. 2, the user presses the button BB11 of the browser B11 displayed on the terminal device 100 (step S21). In the example illustrated in FIG. 2, the user presses a button BB11 that is displayed on the terminal device 100 and is labeled “View with application C”.

  After the button BB11 of the browser B11 is pressed, the terminal device 100 transitions from the browser B11 to the application C (hereinafter referred to as “application A21”) (step S22). For example, when the application A21 is not activated, the terminal device 100 activates the application A21. Note that when the OS (Operating System) of the terminal device 100 is Android (registered trademark) or iOS (registered trademark), the application A21 may be activated by a URL scheme. Here, when the browser B11 transitions to the application A21 in step S22, the browser B11 provides the cookie information of the cookie C11 to the application A21. For example, the browser B11 may extract the cookie information related to the server corresponding to the domain name of the Web page displaying the button BB11 from the cookie C11, and provide the extracted cookie information to the application A21.

  Thereafter, in the example illustrated in FIG. 2, the application A <b> 21 is displayed on the terminal device 100. If the application A21 is not installed in the terminal device 100, the terminal device 100 may display a Web page that prompts the user to install the application A21 on the browser B11 or activate an application that prompts the user to install the application A21. Good.

  Here, the application A21 installed in the terminal device 100 includes a predetermined SDK. Hereinafter, the SDK of the application A21 is referred to as a development kit SD21. Here, the development kit SD21 of the application A21 can obtain a terminal ID for identifying the terminal device 100 from the terminal information storage unit 121 of the terminal device 100.

  After the transition from the browser B11 to the application A21, the application A21 acquires a terminal ID from the terminal information storage unit 121 of the terminal device 100 (step S23). The application A21 associates the cookie information provided from the browser B11 with the terminal ID acquired in step S23 (step S24).

  Thereafter, the application A21 transmits the cookie information provided from the browser B11 and the terminal ID acquired in step S23 as association information to the server device 10 (step S25). When the application A21 transitions from the browser B11 to the application A21, for example, the application A21 transmits the cookie information and the terminal ID to the server device 10 by using a function such as the development kit SD21.

  The server device 10 that has received the association information from the terminal device 100 registers the received association information (step S26). Accordingly, the server device 10 associates the terminal ID with the cookie information.

  As described above, in the association system 1 according to the embodiment, the terminal device 100 associates the terminal ID with the cookie information at the time of transition between the application and the browser. The terminal device 100 transmits the association information obtained by associating the terminal ID and the cookie information to the server device 10. Thereby, the terminal device 100 can appropriately associate information collected from the same terminal device 100.

  In addition, the server device 10 registers the association information received from the terminal device 100. For example, when the terminal ID in the received association information has already been registered, the server device 10 adds the cookie information in the received association information as cookie information corresponding to the registered terminal ID. Thereby, the server apparatus 10 can link the terminal ID and the cookie information. For example, the server apparatus 10 provides the association information to an external information processing apparatus, for example, an advertisement distribution apparatus included in the association system 1. Thereby, the associating system 1 can perform appropriate advertisement delivery to the user. Therefore, the associating system 1 can enhance the advertising effect. The server device 10 may be an advertisement distribution device that distributes advertisements based on the association information. Thereby, the associating system 1 can perform appropriate advertisement delivery to the user. Therefore, the associating system 1 can enhance the advertising effect.

[2. Configuration of terminal device]
Next, the configuration of the terminal device 100 according to the embodiment will be described with reference to FIG. FIG. 3 is a diagram illustrating a configuration example of the terminal device according to the embodiment. As illustrated in FIG. 3, the terminal device 100 includes a communication unit 110, a storage unit 120, and a control unit 130. Although not shown, the terminal device 100 includes an input unit that receives various operations from the user and an output unit that outputs various types of information. For example, when the terminal device 100 has a touch panel function, the input unit receives various operations from the user via the display screen of the terminal device 100. Moreover, an output part is provided with the display screen of the terminal device 100 implement | achieved by a liquid crystal display, an organic EL (Electro Luminescence) display, etc., for example, and displays various information.

(Communication unit 110)
The communication unit 110 is realized by a communication circuit or the like, for example. The communication unit 110 is connected to a predetermined communication network (not shown) by wire or wireless, and transmits / receives information to / from the server device 10.

(Storage unit 120)
The storage unit 120 is realized by, for example, a semiconductor memory device such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. For example, the storage unit 120 stores information related to the OS, such as a program, in the terminal device 100. As illustrated in FIG. 3, the storage unit 120 according to the embodiment includes a terminal information storage unit 121, an application information storage unit 120A, and a browser information storage unit 120B.

(Terminal information storage unit 121)
The terminal information storage unit 121 according to the embodiment stores various types of information regarding the terminal device 100. FIG. 4 is a diagram illustrating an example of a terminal information storage unit according to the embodiment. The terminal information storage unit 121 illustrated in FIG. 4 includes items such as “terminal ID”, “OS”, and “version”.

  “Terminal ID” indicates identification information for identifying the terminal device 100. In the example shown in FIG. 4, “TID01” is stored as the terminal ID. “OS” indicates an OS (Operating System) installed in the terminal device 100. In the example shown in FIG. 4, “XXX” is stored as the OS. That is, the terminal device 100 indicates that the OS “XXX” is installed. “Version” indicates the version of the OS installed in the terminal device 100. In the example shown in FIG. 4, “8.1.1” is stored as the version. That is, the OS “XXX” installed in the terminal device 100 is the version “8.1.1”. The terminal information storage unit 121 is not limited to the above, and may store various types of information according to the purpose as long as the information is related to the terminal device 100.

  The application information storage unit 120A stores information related to applications installed in the terminal device 100, such as programs. The browser information storage unit 120B stores information related to the browser installed in the terminal device 100, such as a program. The browser information storage unit 120B includes a cookie information storage unit 121B. FIG. 5 is a diagram illustrating an example of the cookie information storage unit according to the embodiment. As shown in FIG. 5, the cookie information storage unit 121B stores information related to browser cookies for each server. In the example illustrated in FIG. 5, the cookie information storage unit 121B stores cookie information for each corresponding server (domain) such as cookie information related to the server A, cookie information related to the server B, and cookie information related to the server C.

(Control unit 130)
Returning to the description of FIG. 3, the control unit 130 uses, for example, a CPU or MPU to store various programs (applications installed in the terminal device 100, An information providing program or an information transmission program executed by the browser is executed by using the RAM as a work area. For example, the various programs include installed application programs. The control unit 130 is realized by an integrated circuit such as an ASIC or FPGA, for example.

  As shown in FIG. 3, the control unit 130 includes an application control unit 130A and a browser control unit 130B. In addition, the internal structure of the control part 130 is not restricted to the structure shown in FIG. 3, The terminal device 100 contains the other structure for implement | achieving the function as a smart phone.

(Application control unit 130A)
First, the application control unit 130A will be described. The application control unit 130A is a control unit corresponding to the application A11, and performs processing such as association processing by the development kit SD11 of the application A11 and various processing of the application A11. In the example shown in FIG. 3, the application control unit 130A and the application information storage unit 120A correspond to the application A11, and other areas in the storage unit 120 can be accessed only in areas connected by connection lines. To do.

  The application control unit 130A has a reception unit 131A, a providing unit 132A, an acquisition unit 133A, a linking unit 134A, and a transmission unit 135A, particularly as closely related to the present embodiment. Realize or execute the function and operation of the pegging process. Note that the internal configuration of the application control unit 130A is not limited to the configuration illustrated in FIG. 3, and may be another configuration as long as the configuration is performed as described later. Further, the internal configuration of the application control unit 130A is not limited to the configuration illustrated in FIG. 3, and includes other configurations for realizing various processes of the application A11.

  The accepting unit 131A accepts instructions and information related to the application. For example, the accepting unit 131A accepts various operations from the user via the input unit. The accepting unit 131A accepts information related to application updates via the communication unit 110.

  The providing unit 132A provides a terminal ID for identifying the terminal device 100 acquired by the application to a browser instructed to perform predetermined processing by the application. As shown in FIG. 3, the providing unit 132A accesses the terminal information storage unit 121 and acquires the terminal ID. For example, in the example illustrated in FIG. 1, the providing unit 132A provides the terminal ID to the browser B11 when the application A11 transitions to the browser B11.

  When the acquisition unit 133A is instructed to perform predetermined processing from the browser, the acquisition unit 133A acquires cookie information corresponding to a predetermined server device provided from the browser. For example, the acquisition unit 133A acquires cookie information corresponding to the server device 10 provided from the browser B11 when the browser B11 transitions to the application A11.

  The associating unit 134A associates the cookie information acquired by the acquiring unit 133A with the terminal ID acquired from the terminal information storage unit 121. As shown in FIG. 3, the associating unit 134A accesses the terminal information storage unit 121 and acquires the terminal ID.

  The transmission unit 135A transmits the cookie information associated with the association unit 134A and the terminal ID to the server device 10 as association information.

  In the example illustrated in FIG. 3, only the application control unit 130A and the application information storage unit 120A corresponding to the application A11 are illustrated, but the terminal device 100 is not limited to the application A11 and is installed in the terminal device 100. Each application has an application control unit and an application information storage unit. For example, the terminal device 100 includes a plurality of application control units and application information storage units. Note that the processing such as the association processing by the application control unit 130A described above may be realized by, for example, JavaScript (registered trademark).

(Browser control unit 130B)
First, the browser control unit 130B will be described. The browser control unit 130B is a control unit corresponding to the browser B11, and performs processing such as association processing by the browser B11 and various processing of the browser B11. In the example shown in FIG. 3, the browser control unit 130B and the browser information storage unit 120B correspond to the browser B11, and other areas in the storage unit 120 can be accessed only in areas connected by connection lines. To do. Therefore, in this embodiment, the browser control unit 130B cannot access the terminal information storage unit 121, and the browser control unit 130B cannot acquire the terminal ID.

  The browser control unit 130B has a reception unit 131B, a providing unit 132B, an acquisition unit 133B, a linking unit 134B, and a transmission unit 135B, particularly as closely related to the present embodiment, and will be described below. Realize or execute the function and operation of the pegging process. Note that the internal configuration of the browser control unit 130B is not limited to the configuration illustrated in FIG. 3, and may be another configuration as long as it performs a linking process described later. Further, the internal configuration of the browser control unit 130B is not limited to the configuration shown in FIG. 3, and includes other configurations for realizing various processes of the browser B11.

  The accepting unit 131B accepts instructions and information related to the browser. For example, the reception unit 131B receives various operations from the user via the input unit. The accepting unit 131B accepts information related to browser updates and the like via the communication unit 110.

  The providing unit 132B provides cookie information corresponding to a predetermined server device to an application instructed to perform predetermined processing from the browser. As shown in FIG. 3, the providing unit 132B accesses the cookie information storage unit 121B and acquires cookie information corresponding to a predetermined server device. For example, in the example illustrated in FIG. 2, the providing unit 132B provides cookie information corresponding to the server device 10 to the application A21 when the browser B11 changes to the application A21.

  When the acquisition unit 133B is instructed to perform predetermined processing by the application, the acquisition unit 133B acquires a terminal ID for identifying the terminal device 100 provided by the application. For example, the acquisition unit 133B acquires the terminal ID provided from the application A11 when the application A11 transitions to the browser B11.

  The associating unit 134B associates the terminal ID acquired by the acquiring unit 133B with the cookie information acquired from the cookie information storage unit 121B. As shown in FIG. 3, the associating unit 134B accesses the cookie information storage unit 121B and acquires cookie information corresponding to a predetermined server device. For example, in the example illustrated in FIG. 1, the association unit 134B associates the terminal ID acquired by the acquisition unit 133B with the cookie information corresponding to the server device 10 when the application A11 transitions to the browser B11.

  The transmission unit 135B transmits the cookie information associated with the association unit 134B and the terminal ID to the server device 10 as association information.

  In the example illustrated in FIG. 3, only the browser control unit 130B and the browser information storage unit 120B corresponding to the browser B11 are illustrated. However, the terminal device 100 is not limited to the browser B11 and is installed in the terminal device 100. Each browser has a browser control unit and a browser information storage unit. Note that the processing such as the association processing by the browser control unit 130B described above may be realized by, for example, JavaScript (registered trademark).

[3. Configuration of server device]
Next, the configuration of the server device 10 according to the embodiment will be described with reference to FIG. FIG. 6 is a diagram illustrating a configuration example of the server apparatus according to the embodiment. As illustrated in FIG. 6, the server device 10 includes a communication unit 11, a storage unit 12, and a control unit 13. The server device 10 includes an input unit (for example, a keyboard and a mouse) that receives various operations from an administrator of the server device 10 and a display unit (for example, a liquid crystal display) for displaying various types of information. May be.

  The communication part 11 is implement | achieved by NIC etc., for example. The communication unit 11 is connected to the network by wire or wirelessly and transmits / receives information to / from the terminal device 100.

(Storage unit 12)
The storage unit 12 is realized by, for example, a semiconductor memory element such as a RAM or a flash memory, or a storage device such as a hard disk or an optical disk. As shown in FIG. 6, the storage unit 12 according to the embodiment includes an association information storage unit 14 and a cookie information storage unit 15.

(Linking information storage unit 14)
The association information storage unit 14 according to the embodiment stores association information. For example, the association information storage unit 14 stores association information received from the terminal device 100. FIG. 7 is a diagram illustrating an example of a tied information storage unit according to the embodiment. The association information storage unit 14 illustrated in FIG. 7 includes items such as “terminal ID” and “cookie ID”.

  “Terminal ID” indicates identification information for identifying the terminal device 100. The “cookie ID” indicates identification information for identifying cookie information. In the example illustrated in FIG. 7, the terminal ID “TID01” is stored in association with the cookie ID “CID11”, the terminal ID “TID02” is stored in association with the cookie ID “CID12”, and the terminal ID Cookie ID “CID13” is stored in association with “TID03”. For example, the cookie information corresponding to the terminal ID “TID01” and the cookie ID “CID11” is received from the terminal device 100 as the association information.

(Cookie information storage unit 15)
The cookie information storage unit 15 according to the embodiment stores cookie information. For example, the cookie information storage unit 15 stores the cookie information in the association information received from the terminal device 100 in association with the cookie ID. FIG. 8 is a diagram illustrating an example of the cookie information storage unit according to the embodiment. The cookie information storage unit 15 illustrated in FIG. 8 includes items such as “cookie ID” and “cookie information”.

  “Cookie ID” indicates identification information for identifying cookie information. “Cookie information” indicates cookie information. In the example shown in FIG. 8, cookie information “CID11” is stored in association with cookie information A, cookie ID “CID12” is stored in association with cookie information B, and cookie ID “CID13” is stored in cookie ID “CID13”. Is stored in association with the cookie information C. In the example illustrated in FIGS. 7 and 8, for example, the cookie information A identified by the terminal ID “TID01” and the cookie ID “CID11” is received from the terminal device 100 as the association information. The “cookie information” may be a file path indicating an area in which corresponding cookie information is stored.

(Control unit 13)
Returning to the description of FIG. 6, the control unit 13 is realized by, for example, a CPU, an MPU, or the like executing various programs stored in the storage device inside the server device 10 using the RAM as a work area. The control unit 13 is realized by an integrated circuit such as an ASIC or FPGA, for example.

  As shown in FIG. 6, the control unit 13 includes a reception unit 16, a registration unit 17, and a transmission unit 18, and realizes or executes functions and operations of information processing described below. The internal configuration of the control unit 13 is not limited to the configuration illustrated in FIG. 6, and may be other configurations as long as the configuration performs information processing described later. In addition, the connection relationship between the processing units included in the control unit 13 is not limited to the connection relationship illustrated in FIG. 6, and may be another connection relationship.

  The receiving unit 16 receives the association information from the terminal device 100. For example, the receiving unit 16 receives the terminal ID and cookie information received from the terminal device 100 as association information.

  The registration unit 17 registers the association information received by the reception unit 16 in the association information storage unit 14 and the cookie information storage unit 15. For example, when the terminal ID in the association information received from the terminal device 100 is already registered in the association information storage unit 14, the registration unit 17 corresponds to the terminal ID in which the cookie information in the received association information is registered. Add as cookie information. In addition, when the terminal ID in the association information received from the terminal device 100 is not registered in the association information storage unit 14, the registration unit 17 associates the terminal ID with the cookie ID that identifies the received cookie information. The information is stored in the information storage unit 14. Also, the registration unit 17 adds the cookie information in the association information received from the terminal device 100 to the cookie information storage unit 15 in association with the cookie ID.

  The transmission unit 18 transmits various information to an external information processing apparatus. For example, the transmission unit 18 transmits the association information to the advertisement distribution device. For example, the transmission unit 18 may transmit information that instructs the terminal device 100 to transmit the association information. In addition, when the server device 10 is an advertisement distribution device, the transmission unit 18 may distribute an advertisement based on the association information to the terminal device 10.

[4. (Pegging process flow)
Next, the procedure of the pegging process by the pegging system 1 according to the embodiment will be described with reference to FIGS. 9 and 10 are sequence diagrams illustrating a linking process procedure by the linking system 1 according to the embodiment. Specifically, FIG. 9 is a sequence diagram illustrating a linking process procedure when transitioning from an application to a browser. FIG. 10 is a sequence diagram showing a linking process procedure when transitioning from a browser to an application.

  First, with reference to FIG. 9, a description will be given of a linking process procedure in the case of transition from an application to a browser. As shown in FIG. 9, when the button is pressed (step S101), the application A11 displayed on the terminal device 100 acquires the terminal ID from the terminal information storage unit 121 of the terminal device 100 (step S102). Note that the application A11 may acquire the terminal ID before step S101.

  Thereafter, the terminal device 100 transitions from the application A11 to the browser B11 (step S103). For example, if the browser B11 is not activated, the terminal device 100 activates the browser B11. Here, when the application A11 transitions to the browser B11 in step S13, the application A11 provides the terminal ID to the browser B11.

  Thereafter, the browser B11 is displayed on the terminal device 100. The browser B11 associates the cookie information extracted from the cookie information storage unit 121B with the terminal ID provided by the application A11 in step S103 (step S104). For example, the browser B11 extracts cookie information related to the server device 10 from the cookie information storage unit 121B, and associates the extracted cookie information with the terminal ID provided by the application A11 in step S103. Thereafter, the browser B11 transmits the terminal ID and cookie information associated in step S104 to the server device 10 as association information (step S105).

  Thereafter, the server device 10 registers the association information received from the terminal device 100 (step S106). For example, when the terminal ID in the received association information has already been registered, the server device 10 adds the cookie information in the received association information as cookie information corresponding to the registered terminal ID.

  Further, the terminal device 100 transitions the display of the browser B11 (step S107). Note that step S107 may be performed simultaneously with step S105 or step S106 or before step S105 or step S106.

  Next, with reference to FIG. 10, a description will be given of a linking process procedure when transitioning from a browser to an application. As shown in FIG. 10, when the button is pressed (step S201), the browser B11 displayed on the terminal device 100 transitions from the browser B11 to the application A11 (step S202). For example, when the application A11 is not activated, the terminal device 100 activates the application A11. Here, when the browser B11 transitions to the application A11 in step S202, the browser B11 provides the application A11 with the cookie information extracted from the cookie information storage unit 121B. For example, the browser B11 may extract cookie information related to the server device 10 from the cookie information storage unit 121B, and provide the extracted cookie information to the application A11.

  Thereafter, the application A11 is displayed on the terminal device 100. Then, after the transition from the browser B11 to the app A11, the app A11 acquires the terminal ID from the terminal information storage unit 121 of the terminal device 100 (step S203). The application A11 associates the cookie information provided from the browser B11 in step S202 with the terminal ID acquired in step S203 (step S204). Thereafter, the application A11 transmits the terminal ID and cookie information associated in step S204 to the server device 10 as association information (step S205).

  Thereafter, the server device 10 registers the association information received from the terminal device 100 (step S206). For example, when the terminal ID in the received association information has already been registered, the server device 10 adds the cookie information in the received association information as cookie information corresponding to the registered terminal ID.

[5. (Pegging process at first application startup)
The associating system 1 according to the embodiment may perform the associating process even when the terminal device 100 is activated for the first time. This point will be described with reference to FIG. FIG. 11 is a diagram illustrating an example of the associating process at the first activation of the application according to the embodiment.

  First, in the terminal device 100 shown on the left side in FIG. 11, the app B (hereinafter referred to as “app A31”) is activated for the first time (step S31). For example, after the application A31 is installed in the terminal device 100, the application A31 is activated for the first time. Here, the application A31 activated for the first time in the terminal device 100 includes a predetermined SDK. Hereinafter, the SDK of the application A31 is referred to as a development kit SD31. Here, the development kit SD31 of the application A31 can acquire a terminal ID for identifying the terminal device 100 from the terminal information storage unit 121 of the terminal device 100.

  When the application A31 is activated for the first time in the terminal device 100, the terminal device 100 transitions from the application A31 to the browser B11 (step S32). For example, if the browser B11 is not activated, the terminal device 100 activates the browser B11.

  Thereafter, the terminal device 100 transitions from the browser B11 to the application A31 (step S33). Here, when making a transition from the browser B11 to the application A31 in step S33, the browser B11 provides the cookie information of the cookie C11 to the application A31. For example, the browser B11 may extract the cookie information related to the server device 10 from the cookie C11 and provide the extracted cookie information to the application A31.

  Thereafter, in the example illustrated in FIG. 11, the terminal device 100 displays the start screen AD31 of the application A31. After the transition from the browser B11 to the app A31, the app A31 acquires the terminal ID from the terminal information storage unit 121 of the terminal device 100 (step S34). Then, the application A31 associates the cookie information provided from the browser B11 with the terminal ID acquired in step S34 (step S35).

  Thereafter, the application A31 transmits the cookie information provided from the browser B11 and the terminal ID acquired in step S34 as association information to the server device 10 (step S36). In addition, when the application A31 transits from the browser B11 to the application A31, for example, the cookie information and the terminal ID are transmitted to the server device 10 by a function such as the development kit SD31.

  The server device 10 that has received the association information from the terminal device 100 registers the received association information (step S37). As a result, the server device 10 associates the terminal ID with the cookie information even when the application is activated for the first time.

[6. (Modification)
The stringing system 1 according to the above-described embodiment may be implemented in various different forms other than the above-described embodiment. For example, the associating system 2 according to the modification also performs associating processing on the cookie information of the in-app browser that is the browser included in the application. This point will be described with reference to FIGS. In addition, the same code | symbol is attached | subjected to the part same as embodiment, and description is abbreviate | omitted.

  12 and 13 are diagrams illustrating an example of the associating process according to the modification. Specifically, FIG. 12 is a diagram illustrating an example of the associating process including the cookie information of the in-app browser when transitioning from the app to the browser. FIG. 13 is a diagram illustrating an example of the associating process including the cookie information of the in-app browser when transitioning from the browser to the app. The terminal device 100 illustrated in FIGS. 12 and 13 transmits the association information associated with the transition between the application and the browser to the server device 10A. The server device 10A shown in FIGS. 12 and 13 is the same as the server device 10 except that it differs from the server device 10 of the embodiment in that the in-app cookie ID is stored in association with the terminal ID as the association information. It is the same composition.

  First, with reference to FIG. 12, the association process including the cookie information of the in-app browser when transitioning from the app to the browser will be described. In terminal device 100 shown on the left side in FIG. 12, application D (hereinafter referred to as “application A41”) is activated, and application A41 is displayed on terminal device 100. Here, the application A41 installed in the terminal device 100 includes a predetermined SDK. Hereinafter, the SDK of the application A41 is referred to as a development kit SD41. Here, the development kit SD41 of the application A41 can acquire a terminal ID for identifying the terminal device 100 from the terminal information storage unit 121 of the terminal device 100.

  The application A41 includes an in-app browser, and the terminal device 100 shown on the left side of FIG. 12 displays the in-app web screen AW41 by the function of the in-app browser. The application information storage unit corresponding to the application A41 in the storage unit 120 stores an in-app cookie (hereinafter referred to as “in-app cookie”) AC41 of the in-app browser.

  As shown in FIG. 12, the user presses the button AB41 of the application A41 displayed on the terminal device 100 (step S41). In the example illustrated in FIG. 12, the user presses a button AB <b> 41 displayed as “Get App B” displayed on the terminal device 100. And application A41 acquires terminal ID from the terminal information storage part 121 of the terminal device 100 (step S42). Then, the application A41 extracts in-app cookie information from the in-app cookie AC41 (step S43). Note that the app A41 may acquire the terminal ID and the in-app cookie information before step S41. Further, step S43 may be performed before step S42.

  After the button AB41 of the application A41 is pressed, the terminal device 100 transitions from the application A41 to the browser B11 (step S44). For example, if the browser B11 is not activated, the terminal device 100 activates the browser B11. Here, when the application A41 transitions to the browser B11 in step S44, the application A41 provides the terminal ID and the in-app cookie information to the browser B11.

  Thereafter, in the example illustrated in FIG. 12, the browser B <b> 11 is displayed on the terminal device 100. Then, the browser B11 associates the cookie information extracted from the cookie C11 with the terminal ID provided by the application A41 and the in-app cookie information (step S45). For example, cookie information related to the server designated by the application A41 is extracted and associated with the terminal ID and the in-app cookie information provided by the application A41.

  Thereafter, the browser B11 transmits the terminal ID and in-app cookie information provided by the app A41 and the extracted cookie information to the server device 10A as association information (step S46). When the browser B11 transits from the application A41 to the browser B11, for example, the browser B11 transmits a terminal ID, cookie information, and in-app cookie information to the server device 10A by a function such as a redirector.

  The server device 10A that has received the association information from the terminal device 100 registers the received association information (step S47). For example, when the terminal ID in the received association information has already been registered, the server device 10A adds the cookie information in the received association information as cookie information corresponding to the registered terminal ID. For example, when the terminal ID in the received association information has already been registered, the server device 10A uses the in-app cookie information in the received association information as the in-app cookie information corresponding to the registered terminal ID. to add.

  Further, the terminal device 100 shifts the display of the browser B11 (step S48). In the example illustrated in FIG. 12, the browser B11 displays a web page W11 that prompts the user to download the application B. Note that step S48 may be performed simultaneously with step S46 or step S47 or before step S46 or step S47.

  Next, based on FIG. 13, a description will be given of the associating process including the cookie information of the in-app browser when the browser changes to the app. In the terminal device 100 shown on the left side in FIG. 13, the browser is activated, and the browser B11 is displayed on the terminal device 100.

  As shown in FIG. 13, the user presses the button BB21 of the browser B11 displayed on the terminal device 100 (step S51). In the example illustrated in FIG. 13, the user presses the button BB21 that is displayed on the terminal device 100 and is labeled “View with application E”.

  After the button BB21 of the browser B11 is pressed, the terminal device 100 transitions from the browser B11 to the app E (hereinafter referred to as “app A51”) (step S52). For example, if the application A51 is not activated, the terminal device 100 activates the application A51. Here, when the browser B11 transits to the application A51 in step S52, the browser B11 provides the cookie information of the cookie C11 to the application A51. For example, the browser B11 may extract the cookie information related to the server device 10A from the cookie C11 and provide the extracted cookie information to the application A51.

  Thereafter, in the example illustrated in FIG. 13, the application A <b> 51 is displayed on the terminal device 100. When the application A51 is not installed in the terminal device 100, the terminal device 100 may display a web page that prompts the user to install the application A51 on the browser B11 or activate an application that prompts the user to install the application A51. Good.

  Here, the application A51 installed in the terminal device 100 includes a predetermined SDK. Hereinafter, the SDK of the application A51 is referred to as a development kit SD51. Here, the development kit SD51 of the application A51 can obtain a terminal ID for identifying the terminal device 100 from the terminal information storage unit 121 of the terminal device 100.

  Further, the application A51 includes an in-app browser, and the terminal device 100 shown on the right side of FIG. 13 displays the in-app web screen AW51 by the function of the in-app browser. The application information storage unit corresponding to the application A51 in the storage unit 120 stores the in-app cookie AC51 of the in-app browser.

  After the transition from the browser B11 to the app A51, the app A51 acquires the terminal ID from the terminal information storage unit 121 of the terminal device 100 (step S53). Further, the application A51 extracts the in-app cookie information from the in-app cookie AC51 (step S54). Note that step S54 may be performed before step S53. Then, the application A51 associates the cookie information provided from the browser B11 in step S52, the terminal ID acquired in step S53, and the in-app cookie information extracted in step S54 (step S55).

  Thereafter, the application A51 transmits the terminal ID, cookie information, and in-app cookie information associated in step S55 as association information to the server device 10A (step S56). When the application A51 transits from the browser B11 to the application A51, for example, the application A51 transmits the cookie information and the terminal ID to the server device 10A by a function such as the development kit SD51.

  The server device 10A that has received the association information from the terminal device 100 registers the received association information (step S57). Accordingly, the server device 10A associates the terminal ID, the cookie information, and the in-app cookie information.

[7. effect〕
As described above, the terminal device 100 according to the embodiment includes the application A11 (130A) and the browser B11 (130B). The application A11 includes a providing unit 132A that provides terminal information for identifying the terminal device 100 acquired by the application A11 to the browser B11 that is instructed to perform predetermined processing by the application A11. In addition, the browser B11 receives the terminal information provided by the providing unit 132A (in the embodiment, “terminal ID”; the same applies hereinafter) and the cookie information corresponding to the predetermined server device 10 in the predetermined server device 10. A transmission unit 135B for transmission is included.

  Thereby, the terminal device 100 according to the embodiment can appropriately associate information collected from the same terminal device. Further, the server device 10 can associate the terminal ID with the cookie information. For example, the server apparatus 10 provides the association information to an external information processing apparatus, for example, an advertisement distribution apparatus included in the association system 1. Thereby, the associating system 1 can perform appropriate advertisement delivery to the user. Therefore, the associating system 1 can enhance the advertising effect. The server device 10 may be an advertisement distribution device that distributes advertisements based on the association information. Thereby, the associating system 1 can perform appropriate advertisement delivery to the user. Therefore, the associating system 1 can enhance the advertising effect.

  In the terminal device 100 according to the embodiment, the providing unit 132A provides in-app cookie information corresponding to the in-app browser that is a browser included in the application A11, together with the terminal information, to the browser B11.

  Thereby, the terminal device 100 according to the embodiment can appropriately associate the in-app cookie information collected from the same terminal device. Further, the server device 10 can link the terminal ID, the cookie information, and the in-app cookie information.

  In the server device 10 according to the embodiment, the application A11 instructs the browser B11 to access the predetermined server device 10 as a predetermined process.

  Thereby, the terminal device 100 according to the embodiment can appropriately associate the cookie information corresponding to the server device 10. Further, the terminal device 100 according to the embodiment can appropriately associate information collected from the same terminal device.

  The terminal device 100 according to the embodiment includes an application A11 (130A) and a browser B11 (130B). The browser B11 includes a providing unit 132B that provides cookie information corresponding to the predetermined server device 10 to the application A11 instructed to perform predetermined processing from the browser B11. In addition, the application A11 includes a transmission unit 135A that transmits the cookie information provided by the providing unit 132B and the terminal information acquired by the application A11 to a predetermined server device 10.

  Thereby, the terminal device 100 according to the embodiment can appropriately associate information collected from the same terminal device. Further, the server device 10 can associate the terminal ID with the cookie information. For example, the server apparatus 10 provides the association information to an external information processing apparatus, for example, an advertisement distribution apparatus included in the association system 1. Thereby, the associating system 1 can perform appropriate advertisement delivery to the user. Therefore, the associating system 1 can enhance the advertising effect. The server device 10 may be an advertisement distribution device that distributes advertisements based on the association information. Thereby, the associating system 1 can perform appropriate advertisement delivery to the user. Therefore, the associating system 1 can enhance the advertising effect.

  In the terminal device 100 according to the embodiment, the transmission unit 135A transmits in-app cookie information corresponding to the in-app browser, which is a browser included in the application A11, to the predetermined server device 10 together with the terminal information.

  Thereby, the terminal device 100 according to the embodiment can appropriately associate the in-app cookie information collected from the same terminal device. Further, the server device 10 can link the terminal ID, the cookie information, and the in-app cookie information.

  In the server device 10 according to the embodiment, the providing unit 132B provides cookie information corresponding to the server device 10 accessed by the browser B11.

  Thereby, the terminal device 100 according to the embodiment can appropriately associate the cookie information corresponding to the server device 10. Further, the terminal device 100 according to the embodiment can appropriately associate information collected from the same terminal device.

[8. Hardware configuration)
The server apparatus 10 according to the embodiment described above is realized by a computer 1000 having a configuration as shown in FIG. 14, for example. FIG. 14 is a hardware configuration diagram illustrating an example of a computer 1000 that implements the functions of the terminal device 100. The computer 1000 includes a CPU 1100, RAM 1200, ROM 1300, HDD 1400, communication interface (I / F) 1500, input / output interface (I / F) 1600, and media interface (I / F) 1700.

  The CPU 1100 operates based on a program stored in the ROM 1300 or the HDD 1400 and controls each unit. The ROM 1300 stores a boot program executed by the CPU 1100 when the computer 1000 is started up, a program depending on the hardware of the computer 1000, and the like.

  The HDD 1400 stores programs executed by the CPU 1100, data used by the programs, and the like. The communication interface 1500 receives data from other devices via the network N and sends the data to the CPU 1100, and transmits data generated by the CPU 1100 to other devices via the network N.

  The CPU 1100 controls an output device such as a display and a printer and an input device such as a keyboard and a mouse via the input / output interface 1600. The CPU 1100 acquires data from the input device via the input / output interface 1600. In addition, the CPU 1100 outputs the generated data to the output device via the input / output interface 1600.

  The media interface 1700 reads a program or data stored in the recording medium 1800 and provides it to the CPU 1100 via the RAM 1200. The CPU 1100 loads such a program from the recording medium 1800 onto the RAM 1200 via the media interface 1700, and executes the loaded program. The recording medium 1800 is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or PD (Phase change rewritable disk), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory. Etc.

  For example, when the computer 1000 functions as the server device 10 according to the embodiment, the CPU 1100 of the computer 1000 implements the function of the control unit 130 by executing a program loaded on the RAM 1200. The CPU 1100 of the computer 1000 reads these programs from the recording medium 1800 and executes them. However, as another example, these programs may be acquired from other devices via the network N.

  As described above, some of the embodiments of the present application have been described in detail with reference to the drawings. It is possible to implement the present invention in other forms with improvements.

[9. Others]
In addition, among the processes described in the above embodiments, all or a part of the processes described as being automatically performed can be manually performed, or the processes described as being manually performed All or a part of the above can be automatically performed by a known method. In addition, the processing procedures, specific names, and information including various data and parameters shown in the document and drawings can be arbitrarily changed unless otherwise specified. For example, the various types of information illustrated in each drawing is not limited to the illustrated information.

  Further, each component of each illustrated apparatus is functionally conceptual, and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured.

  Moreover, each embodiment mentioned above can be combined suitably in the range which does not contradict a process content.

  In addition, the “section (module, unit)” described above can be read as “means” or “circuit”. For example, the reception unit can be read as reception means or a reception circuit.

DESCRIPTION OF SYMBOLS 1 Linking system 100 Terminal device 120 Storage unit 121 Terminal information storage unit 120A Application information storage unit 120B Browser information storage unit 121B Cookie information storage unit 130 Control unit 130A Application control unit 131A Reception unit 132A Provision unit 133A Acquisition unit 134A Association unit 135A Transmission Unit 130B browser control unit 131B reception unit 132B provision unit 133B acquisition unit 134B association unit 135B transmission unit 10 server device 14 association information storage unit 15 cookie information storage unit 16 reception unit 17 registration unit 18 transmission unit A11 application B11 browser N network

Claims (14)

A terminal device having an application and a browser,
The application is
A providing unit that provides terminal information for identifying the terminal device acquired by the application to the browser instructed to perform predetermined processing by the application at a timing based on the instruction of the predetermined processing; Have
The browser
A transmission unit that transmits the terminal information provided by the providing unit and cookie information corresponding to a predetermined server device to the predetermined server device when the application is changed to the browser;
A terminal device characterized by that. The providing unit includes:
Providing the terminal information to the browser at a timing of transition from the application to the browser in accordance with the predetermined processing instruction;
The terminal device according to claim 1. The providing unit includes:
Providing the terminal information to the browser at a timing when the browser is activated by an instruction of the predetermined processing;
The terminal device according to claim 1, wherein the terminal device is a terminal device. The providing unit includes:
Providing in-app cookie information corresponding to an in-app browser that is a browser included in the application together with the terminal information to the browser;
The terminal device according to any one of claims 1 to 3. The application is
Instructing the browser to access the predetermined server device as the predetermined process,
The terminal device according to claim 1, wherein: A terminal device having an application and a browser,
The browser
A provision unit that provides cookie information corresponding to a predetermined server device to the application instructed to perform a predetermined process from the browser at a timing based on the instruction of the predetermined process;
The application is
A transmission unit that transmits the cookie information provided by the providing unit and the terminal information acquired by the application to the predetermined server device when the browser transits to the application;
A terminal device characterized by that. The providing unit includes:
Providing the cookie information to the application at the timing of transition from the browser to the application according to the predetermined processing instruction;
The terminal device according to claim 6 . The providing unit includes:
Providing the cookie information to the application at a timing at which the application is activated by an instruction of the predetermined process;
8. The terminal device according to claim 6 or 7 , wherein: The transmitter is
Transmitting in-app cookie information corresponding to an in-app browser that is a browser included in the application to the predetermined server device together with the terminal information;
The terminal device according to any one of claims 6 to 8 . The providing unit includes:
Providing cookie information corresponding to the server device accessed by the browser;
The terminal device according to any one of claims 6 to 9 . An information transmission method executed by a terminal device having an application and a browser,
The application provides terminal information for identifying the terminal device acquired by the application to the browser instructed to perform a predetermined process by the application at a timing based on the instruction of the predetermined process. Providing process to
A transmission step in which the browser transmits the terminal information provided in the providing step and cookie information corresponding to a predetermined server device to the predetermined server device when the browser transitions from the application to the browser; ,
An information transmission method comprising: An information transmission method executed by a terminal device having an application and a browser,
A providing step in which the browser provides cookie information corresponding to a predetermined server device to the application instructed to perform a predetermined process from the browser at a timing based on the instruction of the predetermined process;
A transmitting step of transmitting the cookie information provided by the providing step and the terminal information acquired by the application to the predetermined server device when the application makes a transition from the browser to the application;
An information transmission method comprising: An information transmission program executed by a terminal device having an application and a browser,
An acquisition procedure for acquiring terminal information for identifying the terminal device provided by the application from the application at a timing instructed to perform a predetermined process by the application;
A transmission procedure for transmitting the terminal information acquired by the acquisition procedure and cookie information corresponding to a predetermined server device to the predetermined server device when the application transits to the browser;
The terminal device executes the information transmission program. An information transmission program executed by a terminal device having an application and a browser,
An acquisition procedure for acquiring cookie information corresponding to a predetermined server device provided by a browser from the browser at a timing instructed to perform predetermined processing by the browser;
A transmission procedure for transmitting the cookie information acquired by the acquisition procedure and terminal information for identifying the terminal device to the predetermined server device when the browser makes a transition to the application;
The terminal device executes the information transmission program.

Images