JP2020087177A - Information processing system, information processing method, information processing device, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To realize an association between a device and a service by a simple operation. An information processing system including an intermediary device capable of communicating with an apparatus and an information processing apparatus capable of communicating with the intermediary device, wherein the information processing apparatus receives identification information acquired from the outside by the terminal. When the device is not registered in association with any service in the information processing device, a service information providing unit that provides information on a candidate service associated with the device to the terminal, and a service information providing unit, With the device specified based on the information for identifying the device associated with the service related to the selection result of the service received from the terminal, the service related to the selection result, and the registration unit for registering the identification information in association with each other. , Have. [Selection diagram] FIG. 21.

Description

The present invention relates to an information processing system, an information processing method, an information processing device, and a program.

In Patent Document 1, when a user terminal acquires a device ID and a service ID from a signage device and transmits the device ID and the service ID to a server device, a workflow is generated based on the combination of the service ID and the device ID received by the server device. A technique of identifying and executing the identified workflow is disclosed. Further, as an example of executing a workflow, it is disclosed that an image combined by a server device is transmitted to a signage device.

However, Patent Document 1 does not disclose how to register the association of services, devices, and workflows.

The present invention has been made in view of the above points, and an object of the present invention is to enable association between a device and a service with a simple operation.

Therefore, in order to solve the above problem, an information processing system including an intermediary device capable of communicating with a device and an information processing device capable of communicating with the intermediary device, wherein the information processing device is an identification that a terminal acquires from the outside. Service information that, when the information is received from the terminal, provides the terminal with information of a candidate of a service to be associated with the device when the device is not registered in association with any service in the information processing apparatus. The providing unit, the device identified based on the information for identifying the device associated with the service related to the selection result of the service received from the terminal, the service related to the selection result, and the identification information are registered in association with each other. And a registration unit that does.

The association between the device and the service can be realized by a simple operation.

It is a figure which shows the structural example of the information processing system in 1st Embodiment. It is a figure which shows the hardware structural example of the server apparatus 10 in 1st Embodiment. It is a figure which shows the hardware structural example of the user terminal 20 in 1st Embodiment. It is a figure which shows the hardware structural example of the intermediation apparatus 30 in 1st Embodiment. It is a figure for explaining the outline of a 1st embodiment. It is a figure showing an example of functional composition of each device in a 1st embodiment. FIG. 9 is a sequence diagram for explaining an example of a processing procedure executed in response to activation of the intermediary device 30. It is a figure which shows the structural example of the device information storage part 122. It is a figure which shows the structural example of the registration information storage part 124. It is a figure which shows the structural example of the application information storage part 121. It is a sequence diagram for explaining an example of a processing procedure executed according to the proximity of the user terminal 20 to the tag seal. It is a figure which shows the structural example of the user information storage part 123. It is a figure which shows the example of a display of an upload screen. FIG. 6 is a sequence diagram for explaining an example of a processing procedure of a distribution process of image data from the user terminal 20 to the intermediary device 30. It is a figure which shows the structural example of the information processing system in 2nd Embodiment. It is a figure which shows the hardware structural example of the intermediation apparatus 30 in 2nd Embodiment. It is a figure showing an example of functional composition of each device in a 2nd embodiment. It is a sequence diagram for explaining an example of a processing procedure of advance preparation processing in the second embodiment. It is a figure which shows the structural example of the user information storage part 123 in 2nd Embodiment. It is a sequence diagram for explaining an example of a processing procedure executed according to the proximity of the user terminal 20 to the sender of the message beacon. It is a figure which shows the function structural example of each apparatus in 3rd Embodiment. It is a sequence diagram for explaining an example of a processing procedure executed in response to activation of the intermediary device 30 in the third embodiment. It is a figure which shows the example of an output of a service non-registration screen. It is a figure which shows the structural example of the device information storage part 122 in 3rd Embodiment. It is a figure which shows the example of an output of the service non-registration screen containing a passcode. It is a sequence diagram for explaining an example of a processing procedure executed according to the proximity of the user terminal 20 to an unregistered tag sticker. It is a figure which shows the structural example of the service information storage part 125. It is a figure which shows the example of a display of a service menu screen. It is a figure which shows the example of a display of a passcode input screen. It is a figure which shows the example of a display of a service confirmation screen. It is a figure which shows the example of an output of a service confirmation notification screen.

The first embodiment will be described below with reference to the drawings. FIG. 1 is a diagram illustrating a configuration example of an information processing system according to the first embodiment. In the information processing system 1 shown in FIG. 1, the server device 10 and the user environment E1 can communicate with each other via a wide area network N1 such as the Internet. However, the network N1 may be a network that can be accessed within a predetermined range, such as an intranet.

The user environment E1 is a system environment in an organization such as a company in which output devices such as one or more projectors 40 and one or more intermediary devices 30 are installed. The projector 40 is a device that projects an input image on a projection surface and is an example of an output device. In the user environment E1, each projector 40 is connected to the corresponding intermediary device 30. That is, the projector 40 and the intermediary device 30 have a one-to-one correspondence. The projector 40 and the intermediary device 30 are connected via an interface conforming to a standard capable of transmitting an image, such as HDMI (registered trademark) (High-Definition Multimedia Interface). For example, the projector 40 and the intermediary device 30 may be connected by a cable (for example, an HDMI (registered trademark) cable or the like) corresponding to the interface. Alternatively, the connector corresponding to the interface included in the intermediary device 30 and the connector corresponding to the interface included in the projector 40 may be directly connected. For example, the intermediary device 30 may be connected by inserting the intermediary device 30 into the connector of the projector 40. Alternatively, the intermediary device 30 and the projector 40 may be connected by wireless communication, or may be connected via a network.

Since the projector 40 and the intermediary device 30 are connected as described above, the intermediary device 30 can transmit the image of the projection target to the projector 40.

The intermediary device 30 is connected to the network N1 via a LAN or the like in the user environment E1. The intermediary device 30 may be wirelessly connected to a LAN or the like in the user environment E1. The intermediation device 30 includes a web browser inside, and executes the process according to the execution request of the process related to the image data transmitted from the server device 10 by the web browser to control the output device such as the projector 40 (for example, The execution result of the process is output to the projector 40). Specifically, in the present embodiment, intermediary device 30 causes projector 40 to execute output (for example, projection) of the image data. That is, the intermediary device 30 mediates the output (for example, projection) of the image by the projector 40 for the data transmitted from the server device 10. In addition, for example, a computer such as an HDMI (registered trademark) dongle or a stick PC may be used as the intermediary device 30.

The user terminal 20 is an information processing terminal carried by each user in the user environment E1. For example, a smartphone, a tablet terminal, a PC, a mobile phone, or the like may be used as the user terminal 20. The user terminal 20 can be connected to the network N1 without going through a LAN or the like in the user environment E1 (for example, via a mobile communication network or the like). However, the user terminal 20 may be connectable to the network in the user environment E1.

The server device 10 is one or more computers that execute processing for realizing output of image data designated by the user terminal 20 by an output device such as the projector 40 by a simple operation using the user terminal 20. .. The server device 10 may be installed in the user environment E1.

FIG. 2 is a diagram illustrating a hardware configuration example of the server device 10 according to the first embodiment. The server device 10 in FIG. 2 includes a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, an interface device 105, etc., which are connected to each other by a bus B.

A program that realizes the processing in the server device 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 storing the program is set in the drive device 100, the program is installed from the recording medium 101 to the auxiliary storage device 102 via the drive device 100. However, it is not always necessary to install the program from the recording medium 101, and the program may be downloaded from another computer via the network. The auxiliary storage device 102 stores the installed program and also stores necessary files and data.

The memory device 103 reads the program from the auxiliary storage device 102 and stores the program when an instruction to activate the program is given. The CPU 104 executes a function related to the server device 10 according to a program stored in the memory device 103. The interface device 105 is used as an interface for connecting to a network.

FIG. 3 is a diagram illustrating a hardware configuration example of the user terminal 20 according to the first embodiment. In FIG. 3, the user terminal 20 includes a CPU 201, a ROM 202, a RAM 203, a touch panel 204, an auxiliary storage device 205, a short-range wireless communication device 206, a digital camera 207, and the like.

The ROM 202 and the auxiliary storage device 205 store programs and the like installed in the user terminal 20. The RAM 203 reads the program from the ROM 202 or the auxiliary storage device 205 and stores the program when an instruction to activate the program is given. The CPU 201 realizes the function related to the user terminal 20 according to the program stored in the RAM 203.

The touch panel 204 is an electronic component having both an input function and a display function, and displays information and receives an input from a user. The touch panel 204 includes a display device 211, an input device 212, and the like.

The display device 211 is a liquid crystal display or the like, and has a display function of the touch panel 204. The input device 212 is an electronic component including a sensor that detects contact of a contact object with the display device 211. The contact object is an object that contacts the contact surface (surface) of the touch panel 204. As an example of such an object, a user's finger, a dedicated pen, a general pen, or the like can be given. The touch panel 204 does not necessarily have to be provided, and the user terminal 20 may have the display device 211 and the input device 212 separately. The display device 211 may be externally connected to the user terminal 20. In addition, the input device 212 is not limited to a sensor that detects a contact, and includes electronic components such as a hardware key, a keyboard, and a mouse.

The short-range wireless communication device 206 is hardware for performing short-range wireless communication. In the first embodiment, the short-range wireless communication device 206 reads the information stored in the NFC tag. That is, in the first embodiment, the near field communication device 206 is preferably an NFC reader. The digital camera 207 is a general digital camera having an imaging function and may be built in the user terminal 20 as an electronic component, or may be externally connected to the user terminal 20.

FIG. 4 is a diagram illustrating a hardware configuration example of the intermediary device 30 according to the first embodiment. The intermediary device 30 of FIG. 2 includes an auxiliary storage device 301, a memory device 302, a CPU 303, a communication interface 304, an image interface 305, and the like.

The program that realizes the processing in the intermediary device 30 is installed in the auxiliary storage device 301. The auxiliary storage device 301 stores the installed program and also stores necessary files and data.

The memory device 302 reads the program from the auxiliary storage device 301 and stores the program when an instruction to activate the program is given. The CPU 303 executes the function related to the mediation device 30 according to the program stored in the memory device 302. The communication interface 304 is a physical interface for connecting to a network. The image interface 305 is a physical interface for transmitting an image to the projector 40.

FIG. 5 is a diagram for explaining the outline of the first embodiment. As shown in FIG. 5, for example, a sticker-shaped NFC tag (hereinafter, simply referred to as “tag sticker”) is attached to the projector 40. The tag seal includes information (hereinafter referred to as “tag information”) including a URL (hereinafter, referred to as “initial access URL”) that the user terminal 20 should first access among URLs for accessing the server device 10. Is remembered. In the tag information, the initial access URL has a registration ID as optional information. For example, the tag information has the following format.
https://xxx. yyy. com/? tagid=Tag01
Here, the part of "XXX"("Tag01" in the above) in "tagid=XXX" corresponds to the registration ID. The registration ID is identification information registered in the server device 10. A different registration ID may be assigned to each tag sticker, or the same registration ID may be assigned to a plurality of tag stickers. On the other hand, the part “https://xxx.yyy.com/” (initial access URL) may be common to the tag information stored in each tag sticker used in the user environment E1. The registration ID does not have to be included in the initial access URL, and may be stored separately from the initial access URL.

When the user holds the user terminal 20 over the tag sticker attached to the projector 40 (S1), the short-range wireless communication device 206 of the user terminal 20 reads the tag information stored in the tag sticker to read the tag. Information is acquired (S2). Then, the user terminal 20 accesses the server device 10 which is the destination (“https://xxx.yyy.com”) of the initial access URL included in the acquired tag information (S3). At this time, the registration ID and the like included in the acquired tag information are also transmitted to the server device 10.

The server device 10 controls execution of a service registered in advance in association with the registration ID. For example, if the service is to project the image data captured by the user terminal 20 onto the specific projector 40, the server device 10 acquires the image data captured by the user terminal 20 from the user terminal 20, and The image data is transmitted to the intermediary device 30 associated with the registration ID (S4). The server device 10 transmits, for example, the display data of the screen prompting the upload of the image data to the user terminal 20, and the image data captured by the user terminal 20 in response to the operation by the user via the screen is transmitted to the user terminal 20. The image data is acquired by receiving the image data.

When the mediation device 30 receives the image data from the server device 10, the mediation device 30 draws the image data. As a result, the drawing result is transmitted to the projector 40 (S5). The projector 40 projects the drawing result (that is, the image data).

Therefore, the user can receive the service regarding the output device as described above by a simple operation such as acquiring tag information from outside the user terminal 20. For example, in the example described above, the service as described above can be received by a simple operation such that the user terminal 20 is held (closed) to the tag sticker arranged (attached) on the projector 40. As described above, the service to be executed is specified according to the registration ID. That is, different services can be associated with each registration ID.

In order to realize the processing described in FIG. 5, the user terminal 20, the intermediary device 30, and the server device 10 have the functional configurations shown in FIG.

FIG. 6 is a diagram illustrating a functional configuration example of each device according to the first embodiment. In FIG. 6, the user terminal 20 includes an information acquisition unit 21 and a browser unit 22. Each of these units is realized by a process that causes the CPU 201 to execute one or more programs installed in the user terminal 20.

The information acquisition unit 21 acquires the tag information (initial access URL including the registration ID) from the tag sticker using the short-range wireless communication device 206, and activates the browser unit 22 using the tag information as input information. The information acquisition unit 21 may be realized by a process that a part of the OS (Operating System) of the user terminal 20 causes the CPU 201 to execute.

The browser unit 22 is, for example, a general Web browser, and executes processing according to HTML (HyperText Markup Language) data, a script (for example, Java Script (registered trademark)), and the like. The browser unit 22 informs the application determination unit 12 of the server device 10 corresponding to the initial access URL included in the tag information notified as the input information from the information acquisition unit 21 of the registration ID and the like included in the tag information URL. Send. The browser unit 22 also accesses the application associated with the registration ID among the applications included in the server device 10 according to the redirect request that is the response from the application determination unit 12 in response to the access to the initial access URL. The browser unit 22 acquires data (HTML data, script, etc.) indicating a request to execute processing to the user terminal 20 from the application.

The intermediary device 30 includes a communication control unit 31, a browser management unit 32, a browser unit 33, and the like. Each of these units is realized by a process executed by the CPU 303 by one or more programs installed in the intermediary device 30.

The communication control unit 31 connects a bidirectional communication path (establishes a communication session) with the distribution unit 11 of the server device 10, and functions as an endpoint on the side of the intermediary device 30 in the communication path (communication session). Through communication via the communication path (communication session), the state of the intermediary device 30 is notified to the server device 10, and image data to be projected by the intermediary device 30 on the projector 40 is input to the server device 10 (this embodiment). In the above form, it is possible to receive from the server device 10 a notification that it has been uploaded from the user terminal 20).

The browser management unit 32 activates the browser unit 33 in, for example, a kiosk mode. The kiosk mode is a mode in which the use of the intermediary device 30 is limited to displaying a web page. Note that the kiosk mode is merely an example, and any other mode may be used as long as it can display a web page.

The browser unit 33 is, for example, a general Web browser, and executes processing according to HTML data, scripts, and the like. The browser unit 33 accesses the initial access URL (that is, the application determination unit 12 of the server device 10) upon activation. At this time, the identification information of the browser unit 33 (hereinafter referred to as "browser ID") is added to the initial access URL as optional information. The browser unit 33 accesses the application associated with the browser ID among the applications included in the server device 10 according to the redirect request that is the response from the application determination unit 12 in response to the access to the initial access URL. The browser unit 33 acquires, from the application, data (HTML data, script, etc.) indicating a process execution request to the intermediary device 30. The drawing content based on the data by the browser unit 33 is output to the projector 40 via an HDMI (registered trademark) interface. That is, the browser unit 33 and the projector 40 have a one-to-one correspondence. Therefore, in the intermediary device 30, the browser ID can be said to be the identification information of the browser unit 33 and the identification information of the projector 40 corresponding to the browser unit 33.

The server device 10 includes a distribution unit 11, an application determination unit 12, an upload application 13, an output application 14, and the like. Each of these units is realized by a process that causes the CPU 104 to execute one or more programs installed in the server device 10. The server device 10 also uses the application information storage unit 121, the device information storage unit 122, the user information storage unit 123, the registration information storage unit 124, and the like. Each of these storage units can be realized using, for example, the auxiliary storage device 102 or a storage device that can be connected to the server device 10 via a network.

The distribution unit 11 receives the image data to be input for the service associated with the registration ID from the input source of the image data, and notifies the output destination of the image data in the service of the input of the image data. Further, the distribution unit 11 transmits the image data to the output destination in response to the request from the output destination. In the present embodiment, the input source is the user terminal 20 and the output destination is the intermediary device 30.

The application determination unit 12 determines the application corresponding to the initial access URL. In response to the access of the initial access URL, the application determination unit 12 determines the application corresponding to the option information (registration ID or browser ID) given to the initial access URL by referring to the registration information storage unit 124. The application determination unit 12 transmits a response including a redirect request including a URL for the determined application to the access source of the initial access URL. In the present embodiment, regarding the access from the user terminal 20 that is the input source of the image data, the URL of the upload application 13 is determined as the application corresponding to the registration ID. Further, regarding the access from the intermediary device 30 that is the output destination of the image data, the URL of the output application 14 is determined as the application corresponding to the browser ID.

The upload application 13 and the output application 14 are examples of applications that the server device 10 has in the present embodiment. The upload application 13 is an application for causing the user terminal 20 to upload image data. Specifically, the upload application 13 transmits to the user terminal 20, HTML data, scripts, and the like for executing the upload of image data. The output application 14 is an application for causing the intermediary device 30 to execute (download) and output the image data uploaded from the user terminal 20. Specifically, the output application 14 transmits, to the intermediary device 30, HTML data, scripts, and the like for causing the intermediary device 30 to execute the acquisition and output.

The application information storage unit 121 stores information (e.g., URL) related to each application (the upload application 13 and the output application 14 in this embodiment) included in the server device 10.

The user information storage unit 123 stores identification information of users who can use the application in the server device 10 and the like.

The device information storage unit 122 stores information indicating the state of the intermediary device 30 for each intermediary device 30 arranged in the user environment E1.

The registration information storage unit 124 stores, for each registration ID, identification information of an application that executes input processing of image data, identification information of an application that executes output processing of image data, and an intermediary device that is an input destination of image data. The identification information of the browser unit 33 of 30 (that is, the identification information of the projector 40) is stored.

Hereinafter, a processing procedure executed in the information processing system 1 will be described. FIG. 7 is a sequence diagram for explaining an example of a processing procedure executed in response to activation of the intermediary device 30.

When the power of the intermediary device 30 is turned on by the user (S101), the communication control unit 31 establishes a communication path for asynchronously receiving a request from the distribution unit 11 of the server device 10 with the distribution unit 11. (S102). At this time, the communication control unit 31 notifies the distribution unit 11 of the communication ID that is the identification information of itself (the communication control unit 31). The distribution unit 11 updates the device information storage unit 122 based on the notified communication ID (hereinafter, referred to as “target communication ID”).

FIG. 8 is a diagram showing a configuration example of the device information storage unit 122. In FIG. 8, the device information storage unit 122 stores a communication ID, address information, status information, a browser ID, a browser status, and the like in association with the tenant ID. The tenant ID is the identification information of the contractor (tenant) of the service usage contract provided by the server device 10. For example, the user environment E1 may correspond to one tenant. The communication ID is identification information of the communication control unit 31 of each intermediary device 30 arranged in the tenant associated with the tenant ID. When the intermediary device 30 includes only one communication control unit 31, the communication ID may be identification information that identifies the intermediary device 30. The address information is the local IP address of the mediation device 30. The state information is information indicating whether or not the communication control unit 31 related to the communication ID is in connection with the server device 10 (state in which a communication path is established) (“non-connection”). The browser ID is identification information of the browser unit 33 corresponding to the communication control unit 31 related to the communication ID. In the present embodiment, the browser ID is the identification information of the browser unit 33 included in the same intermediary device 30 as the communication control unit 31 related to the communication ID, and also the projector 40 of the output destination of the drawing content of the browser unit 33. It is also identification information. The browser state is information indicating the activation state of the browser unit 33 related to the browser ID.

For example, if the target communication ID notified to the distribution unit 11 is “Eg001-01”, the status information corresponding to the communication ID in the device information storage unit 122 becomes “connecting” as shown in FIG. Be changed.

Next, the communication control unit 31 searches the browser management unit 32 to acquire the browser ID by using, for example, SNMP (Simple Network Management Protocol) (S103), and from the found browser management unit 32. The browser ID, which is the identification information of the browser unit 33 that is the management target of the browser management unit 32, is acquired (S104). In the present embodiment, an example in which the intermediation device 30 includes the communication control unit 31 and the browser management unit 32 is shown, but the communication control unit 31 included in the intermediation device 30 is included in another intermediation device 30. In order to make it possible to use a plurality of browser management units 32 and browser units 33 by communicating with the browser management unit 32 via the same network, a search for the browser management unit 32 is performed using SNMP or the like. .. Therefore, the search of the browser management unit 32 is not always essential, and the acquisition destination (browser management unit 32) from which the communication control unit 31 acquires the browser ID may be set in advance.

Subsequently, the communication control unit 31 issues a notification that the browser unit 33 (the browser unit 33 of the intermediation device 30 in the present embodiment) corresponding to the acquired browser ID has become available to the browser unit. The browser ID of 33 (hereinafter referred to as "target browser ID") is designated and transmitted to the distribution unit 11 (S105). Upon receiving the notification, the distribution unit 11 updates the device information storage unit 122 (FIG. 8) based on the target browser ID specified in the notification. Specifically, in the device information storage unit 122, the value of the browser state corresponding to the target browser ID is updated from "power OFF" to "power ON".

Then, the communication control unit 31 specifies the target browser ID and the initial access URL and requests the browser management unit 32 to start the browser unit 33 related to the target browser ID (S106). As described above, the initial access URL is the URL that the browser unit 33 should access first, and is set in the browser management unit 32 in advance.

In response to the request from the communication control unit 31, the browser management unit 32 activates the browser unit 33 related to the target browser ID in the kiosk mode (S107). At this time, the browser management unit 32 inputs the initial access URL into the browser unit 33. The browser unit 33 transmits an HTTP request to the input initial access URL in response to the activation in the kiosk mode (S108). The target browser ID is included in the HTTP request.

Upon receiving the HTTP request, the application determination unit 12 of the server device 10 transmits a response including a redirect request (HTTP response) to the browser unit 33 (S109). The redirect request includes the URL of the application associated with the browser ID as the redirect destination. Further, the redirect request includes the communication URL and the target browser ID included in the HTTP request as the notification information to the redirect destination. The communication URL is the URL of the communication control unit 31.

The application determination unit 12 refers to the registration information storage unit 124 and the application information storage unit 121 to specify the URL of the application associated with the target browser ID.

FIG. 9 is a diagram showing a configuration example of the registration information storage unit 124. In FIG. 9, a registration ID, an In application ID, an Out application ID, and a browser ID are associated and stored in the registration information storage unit 124.

The In app ID is an ID of an application that controls the input of image data in the service corresponding to the registration ID (hereinafter referred to as “app ID”). “AP_Upload” indicates the application ID of the upload application 13. The Out application ID is an application ID of an application that controls the output of image data in the service corresponding to the registration ID. “AP_PhotoShow” indicates the application ID of the output application 14. The browser ID is the browser ID of the browser unit 33 corresponding to the registration ID.

Further, FIG. 10 is a diagram showing a configuration example of the application information storage unit 121. In FIG. 10, the application information storage unit 121 stores an application ID, an application type, a URL, and the like for each application included in the server device 10.

The application type indicates the type of the application associated with the application ID based on the relationship with the image data. “In” indicates an application that controls the input of image data (corresponding to the In application ID described above). “Out” indicates an application that controls the output of image data (corresponding to the Out application ID described above). The URL is the URL of the application associated with the application ID.

Therefore, the application determination unit 12 refers to the registration information storage unit 124 to identify the Out application ID associated with the target browser ID, and refers to the application information storage unit 121 to correspond to the Out application ID. Specify the attached URL. Here, it is assumed that the target browser ID is “BROWSER1”. In this case, the URL (hereinafter, “output application URL”) of the application (output application 14) whose application ID is “AP_PhotoShow” is specified.

In addition, the application determination unit 12 automatically generates the communication URL of the communication control unit 31 related to the target communication ID based on the address information associated with the target browser ID in the device information storage unit 122 (FIG. 8).

Then, the browser unit 33 transmits (redirects) an HTTP request to the output application URL (that is, the output application 14) that is the redirect destination according to the redirect request (S110). The HTTP request includes the communication URL and the browser ID included in the redirect request.

In response to the HTTP request, the output application 14 outputs a script (photo.js) for causing the browser unit 33 to connect to the communication URL included in the HTTP request and output of image data (for example, a slide show). A response including the display data (photo.html) for causing the browser unit 33 to draw a user interface for this is sent to the browser unit 33 (S111). The script and the display data are examples of data indicating a request to execute processing to the intermediary device 30. For example, the script may be a program in another format, and the display data may be data in another format.

Upon receiving the response, the browser unit 33 executes the script (photo.js) included in the response to establish a communication path with the communication control unit 31 identified by the communication URL ( S112). The communication path is a communication path for the communication control unit 31 to transmit the notification received from the server device 10 to the browser unit 33. Websocket may be used for the communication path.

Subsequently, the browser unit 33 sets a screen (hereinafter, referred to as “projection screen”) based on the display data (photo.html) included in the response in a predetermined area (for example, a video memory) of the memory device 103. Draw (S113). For example, the projection screen is a screen that functions as a frame to which the image data distributed from the server device 10 is applied. The drawing content (projection screen) by the browser unit 33 is output to the projector 40 via an interface such as HDMI (registered trademark) and is output (projected) by the projector 40.

FIG. 11 is a sequence diagram for explaining an example of a processing procedure executed according to the proximity of the user terminal 20 to the tag sticker.

For example, when the user brings the user terminal 20 close to the tag sticker attached to the projector 40 (for example, when he or she holds it) (S201), the information acquisition unit 21 causes the short-range wireless communication using the short-range wireless communication device 206. The tag information stored in the tag sticker is acquired through communication (S202, S203). The tag information includes an initial access URL to which a registration ID (hereinafter referred to as “target registration ID”) is given as option information. In this embodiment, the value of the target registration ID is “Tag01”.

Subsequently, the information acquisition unit 21 activates the browser unit 22 by using the tag information as input information based on the URL included in the tag information (S204).

Upon activation, the browser unit 22 automatically transmits an HTTP request to the application determination unit 12 corresponding to the initial access URL included in the tag information that is the input information (S205). The HTTP request includes account information as optional information in addition to the target registration ID. The account information is information including the identification information of the user of the user terminal 20 (hereinafter referred to as “user ID”) and the tenant ID of the user environment E1 to which the user belongs, or the user ID and the tenant ID can be specified. Information. For example, Cookie or the like may be used as the account information.

Upon receiving the HTTP request, the application determination unit 12 of the server device 10 authenticates the account information included in the HTTP request. If the authentication is successful, step S206 and subsequent steps are executed. The authentication is performed, for example, based on whether or not the account information included in the HTTP request is registered in the user information storage unit 123.

FIG. 12 is a diagram showing a configuration example of the user information storage unit 123. In FIG. 12, the user information storage unit 123 stores a tenant ID, a user ID, and the like for each user who is permitted to use the application of the server device 10.

When the authentication is successful, the application determination unit 12 transmits a response (HTTP response) including the redirect request to the browser unit 22 (S206). The redirect request includes the upload application 13 associated with the In application ID (“AP_Upload”) stored in the registration information storage unit 124 (FIG. 9) in association with the target registration ID (“Tag01”) as the redirect destination. The URL (hereinafter referred to as “upload application URL”) is included. The upload application URL can be specified by referring to the application information storage unit 121 (FIG. 10).

According to the redirect request, the browser unit 22 sends an HTTP request (redirect) to the upload application URL (that is, the upload application 13) that is the redirect destination (S207).

In response to the HTTP request, the upload application 13 displays display data (upload.html) of a screen (hereinafter referred to as “upload screen”) regarding upload of image data to the distribution unit 11 of the server device 10, and operates the upload screen. In response to this, a response including a script (upload.js) for causing the user terminal 20 to execute the upload is transmitted to the browser unit 22 (S208). The script and the display data are examples of data indicating a request to execute processing to the user terminal 20.

Upon receiving the response, the browser unit 22 generates an upload screen based on the display data (upload.html) and displays the upload screen on the display device 211 (S209).

FIG. 13 is a diagram showing a display example of the upload screen. In FIG. 13, the upload screen 510 includes a button 511 and the like. The button 511 is a screen for accepting an instruction to start an imaging operation. The user selects the button 511 to capture an image. As a result, the captured image data is displayed on the display device 211.

FIG. 14 is a sequence diagram for explaining an example of a processing procedure of image data distribution processing from the user terminal 20 to the intermediary device 30.

When the user performs a predetermined operation (for example, swipe) corresponding to the upload instruction on the image data (hereinafter referred to as “target image data”) displayed on the display device 211 of the user terminal 20 (S301). The browser unit 22 transmits (uploads) the target image data (photo.jpeg) and the target registration ID to the distribution unit 11 of the server device 10 according to the definition of the script (upload.js) (S302). When the distribution unit 11 receives the target image data and the target registration ID, the distribution unit 11 assigns identification information (hereinafter referred to as “image ID”) to the target image data, and assigns the target image data to the image ID (hereinafter referred to as “target”). It is stored in, for example, the auxiliary storage device 102 or the like.

Subsequently, the distribution unit 11 specifies the browser ID (target browser ID) stored in the registration information storage unit 124 (FIG. 9) in association with the target registration ID. The distribution unit 11 associates the communication path (established with the communication control unit 31 related to the communication ID (target communication ID) stored in the device information storage unit 122 (FIG. 8) in association with the target browser ID ( Using the communication path established in step S102 of FIG. 7, a notification that image data has been uploaded (hereinafter referred to as “upload notification”) is transmitted to the communication control unit 31 (S303). The upload notification includes the target image ID and the target browser ID.

When the communication control unit 31 receives the upload notification, the communication control unit 31 establishes a communication path established between the browser unit 33 corresponding to the browser ID included in the upload notification and the communication control unit 31 (step S112 in FIG. 7). The target image ID included in the upload notification is notified to the browser unit 33 using the communication path established in (S304).

In response to the notification from the communication control unit 31, the browser unit 33 transmits an image data acquisition request to the distribution unit 11 according to the definition of the script (photo.js) (S305). The acquisition request includes the target image ID. In response to the acquisition request, the distribution unit 11 transmits a response including the image data (photo.jpeg) associated with the target image ID included in the acquisition request to the browser unit 33 (S306).

Upon receiving the image data, the browser unit 33 draws the image data in a predetermined area (for example, a video memory) of the memory device 103 so as to fit the image data to the projection screen drawn in step S113 of FIG. 7 ( S307). The drawing content is transmitted to the projector 40 by the image interface 305 or the communication interface 304 of the intermediary device 30. As a result, the drawing content is projected by the projector 40.

The processing procedure described above realizes a service in which each time the user terminal 20 captures image data, the image data is output by an output device such as the projector 40. For example, by using the service at a venue such as a party, a seminar, and an exhibition, image data captured in the venue can be sequentially displayed and output on a large-sized display screen.

Although the example in which the device connected to the intermediary device 30 is the projector 40 has been described above, another device such as a digital signage, an electronic blackboard, a display, or a printer is connected to the intermediary device 30 instead of the projector 40. It may be done. In this case, the drawing content of the intermediary device 30 may be displayed on a digital signage, an electronic blackboard, a display, etc., or may be printed by a printer.

Further, in the above description, for convenience of description, an example in which the tag sticker is attached to the projector 40 associated with the tag sticker has been described, but there is no limitation on the attachment destination of the tag sticker. For example, the tag sticker may be attached to any position in the room where the projector 40 is arranged.

As described above, according to the first embodiment, the user brings the user terminal 20 close to the tag sticker so that the intermediary device 30 performs the preset process associated with the tag sticker (registration ID). It can be executed by a connected device (for example, the projector 40). That is, since the user does not need to directly operate the projector 40 and the like and can operate the projector 40 and the like by operating the user terminal 20, the operability of equipment such as the projector 40 and the like can be improved.

Further, the screen displayed on the user terminal 20 is based on display data such as HTML data distributed from the server device 10, and the degree of dependence on the device associated with the tag sticker is low. Therefore, according to the present embodiment, it is possible to reduce the opportunity for the user to operate a user interface such as an operation panel that differs depending on the device, and to use each device by a highly uniform operation across multiple devices. You will be able to.

In addition, since the intermediary device 30 is interposed between the server device 10 and the device (projector 40), even if the device does not have a network function, as long as the device has an interface for transmitting image data. The present embodiment can be applied. Further, when it is desired to switch the device to which the image data is output, the device connected to the intermediary device 30 may be switched, and it is not necessary to change the setting information in the server device 10.

Further, in the present embodiment, the user terminal 20 only needs to have a program installed in a general smartphone or the like installed therein, and it is not necessary to install a special application in the user terminal 20.

Further, since the intermediary device 30 and the device may be connected to each other through an interface for transmitting image data, for example, setting for wireless LAN connection via a router or setting for wired LAN connection is unnecessary. is there.

In the first embodiment, an example in which the NFC tag is used as an example of the external recording medium storing the tag information is shown, but it is sufficient that the user terminal 20 can acquire the tag information from the outside, and other than near field communication. The tag information may be acquired by the method. For example, a sticker on which a bar code or two-dimensional code on which tag information is recorded may be used instead of the sticker. In this case, the user terminal 20 may acquire the tag information by using the barcode reader, the two-dimensional code reader, the digital camera 207, or the like. The bar code or the two-dimensional code is not necessarily printed on the sticker, and may be displayed on the display of the output device or may be printed on the output device itself or an external recording medium other than the sticker. Good. The tag sticker of the NFC tag described above is also just an example, and similarly, an external recording medium other than the sticker may have an NFC tag.

Alternatively, the user terminal 20 may receive a sound wave transmitted from a transmitter installed in the vicinity of the output device or provided by the output device itself or a beacon described below, and acquire the received sound wave or the tag information embedded in the beacon. Good.

Alternatively, the user terminal 20 may acquire the stored tag information by accessing the device installed around the output device or the output device itself via the network.

Alternatively, the user terminal 20 may acquire the tag information from an external recording medium (for example, a sticker) on which the image is printed. In this case, the user terminal 20 may input the image with the digital camera 207 and extract the tag information from the tint block or the like embedded in the image. A publicly known technique may be used for embedding information such as a tint block in an image or extracting information from the tint block.

Next, a second embodiment will be described. In the second embodiment, the points different from the first embodiment will be described. Therefore, points that are not particularly mentioned may be the same as those in the first embodiment.

In the second embodiment, a message application such as LINE (registered trademark) is used. Further, in the second embodiment, a beacon for the message application 23 (a beacon by short-range wireless communication such as BLE (Bluetooth (registered trademark) Low Energy)) including a registration ID is used instead of the tag sticker. .. Hereinafter, the beacon is referred to as "message beacon".

FIG. 15 is a diagram illustrating a configuration example of the information processing system according to the second embodiment. 15, those parts that are the same as those corresponding parts in FIG. 1 are designated by the same reference numerals, and a description thereof will be omitted.

In FIG. 15, a message service 50 is further connected to the network N1. The message service 50 is one or more computers that provide a service to the message application 23 (function as a server for the message application 23). The user of the message application 23 performs user registration for the message service 50 and receives the issuance of the user ID for the message application 23.

FIG. 16 is a diagram illustrating a hardware configuration example of the intermediary device 30 according to the second embodiment. 16, those parts that are the same as those corresponding parts in FIG. 4 are designated by the same reference numerals, and a description thereof will be omitted. In FIG. 16, the intermediary device 30 further includes a short-range wireless communication device 306. The short-range wireless communication device 306 is hardware for performing short-range wireless communication such as BLE. In this embodiment, the short-range wireless communication device 306 is used for transmitting a message beacon.

FIG. 17 is a diagram illustrating a functional configuration example of each device according to the second embodiment. 17, those parts which are the same as those corresponding parts in FIG. 6 are designated by the same reference numerals, and a description thereof will be omitted.

In FIG. 17, the user terminal 20 further has a message application 23. The message application 23 is as described above.

The server device 10 further includes a message bot 15. The message bot 15 is a program (Bot) that automatically executes message transmission/reception with the message application 23.

FIG. 18 is a sequence diagram for explaining an example of a processing procedure of advance preparation processing according to the second embodiment. In the second embodiment, the processing procedure shown in FIG. 18 is executed as advance preparation.

In step S401, the message bot 15 is registered as a user with respect to the message service 50, and a user ID (hereinafter referred to as “message bot ID”) is issued to the message bot 15.

Then, the message bot ID is notified to the user of the user terminal 20 (S402). For example, a mail including the message bot ID, a QR code (registered trademark), or the like is transmitted to the user terminal 20.

When the user inputs the notified message bot ID to the message application 23 of the user terminal 20 to instruct friend registration (S403), the message application 23 displays the user ID of the user regarding the message application 23 (hereinafter, “message user”). ID”) and the input message bot ID are transmitted to the message service 50 (S404). By registering as a friend, the message application 23 can immediately receive the notification (message) from the message bot 15.

When the message service 50 receives the friend registration request, the message bot 15 associated with the message bot ID included in the friend registration request is registered by the user associated with the message user ID included in the friend registration request. It is notified that this has been done (S405).

Subsequently, the message bot 15 transmits a beacon application including the message bot ID to the message service 50 so that the message beacon can be transmitted from the intermediary device 30, and the hardware ID included in the message beacon (hereinafter, referred to as “HID”). Is issued from the message service 50 (S406).

Subsequently, the message bot 15 transmits a beacon registration request for transmitting a message beacon to the communication control unit 31 of the intermediary device 30 associated with the tenant ID corresponding to the message user ID that registered the message bot 15 as a friend. Yes (S407). The registration request includes the HID, the browser ID corresponding to the tenant ID, and the registration ID corresponding to the browser ID. The tenant ID corresponding to the message user ID can be specified by referring to the user information storage unit 123.

FIG. 19 is a diagram showing a configuration example of the user information storage unit 123 according to the second embodiment. As shown in FIG. 19, in the second embodiment, in the user information storage unit 123, a message user ID is associated with each set of tenant ID and user ID. Therefore, the message bot 15 can identify the tenant ID corresponding to the message user ID by referring to the user information storage unit 123.

The browser ID corresponding to the tenant ID can be specified by referring to the device information storage unit 122 (Fig. 8). Further, the registration ID corresponding to the browser ID can be specified by referring to the registration information storage unit 124 (FIG. 9).

Subsequently, when the communication control unit 31 receives the registration request, the communication control unit 31 sends a beacon including the target registration ID and the HID to the browser management unit 32 corresponding to the browser unit 33 related to the browser ID included in the registration request. Is requested (S408). Subsequently, the browser management unit 32 requests the short-range wireless communication device 306 to transmit a message beacon including the target registration ID and HID (S409). As a result, the short-range wireless communication device 306 of the intermediary device 30 starts transmitting a message beacon including the target registration ID and the HID.

FIG. 20 is a sequence diagram for explaining an example of a processing procedure executed according to the proximity of the user terminal 20 to the source of the message beacon. Note that the processing procedure of FIG. 7 is executed before the processing procedure of FIG. 20 is executed.

When the user brings the user terminal 20 closer to the intermediary device 30 that is transmitting the message beacon (S501), the information acquisition unit 21 of the user terminal 20 receives the message beacon using the short-range wireless communication device 206 (( S502), HID (henceforth "target HID") and registration ID (henceforth "target registration ID") contained in the said message beacon are acquired (S503). That is, in the second embodiment, the short-range wireless communication device 206 is hardware capable of receiving a beacon such as BLE transmitted by the short-range wireless communication device 306 of the intermediary device 30. In this embodiment, the value of the target registration ID is “Tag01”.

Subsequently, the information acquisition unit 21 notifies the content (target HID and target registration ID) of the message beacon to the message application 23 of the user terminal 20 based on that the format of the message beacon is a format corresponding to the message application 23. Yes (S504). In response to the notification of the content of the message beacon, the message application 23 transmits a notification that the message beacon has been received (hereinafter referred to as “beacon reception notification”) to the message service 50 (S505). At this time, the message application 23 includes the message user ID, the target HID, and the target registration ID of the user of the user terminal 20 in the beacon reception notification.

The message service 50 transmits the beacon reception notification to the message bot 15 corresponding to the target HID (S506). That is, in the message service 50, the message bot 15 or the like that has received the HID is managed in association with the HID. The beacon reception notification further includes a message ID for identifying the beacon reception notification. The message service 50 stores the content (message user ID, etc.) included in the beacon reception notification in association with the message ID.

Upon receiving the beacon reception notification, the message bot 15 transmits a response to the beacon reception notification to the message service 50 (S507). The response includes the one-shot ID and the initial access URL in addition to the message ID and the target registration ID included in the beacon reception notification. The initial access URL is the URL for the application determination unit 12, as described in the first embodiment. In the second embodiment, the initial access URL is set in the message bot 15 in advance. The one-shot ID is identification information for limiting the period during which the server device 10 can log in, and is automatically generated by the message bot 15. For example, the one-shot ID may be a value based on the current date and time, or may be a value based on a date and time indicating a log-in deadline. If the period during which the server device 10 can be logged in is not limited, the one-shot ID may not be generated.

Subsequently, the message service 50 responds to the response from the message bot 15 to the message user ID stored in association with the message ID included in the response, the content of the response from the message bot 15, and the like. A message including (initial access URL, one-shot ID, message user ID, target registration ID, etc.) is transmitted as a message from the message bot 15 (S508). For example, the message includes an operation button associated with a link to the initial access URL including the one-shot ID, the message user ID, and the target registration ID as optional information.

When the message application 23 of the user terminal 20 of the user corresponding to the message user ID receives the message, the message application 23 displays the message on the display device 211 (S509). As a result, the user can confirm the message.

Then, when the user presses the operation button included in the message (S510), the message application 23 automatically uses the browser unit 22 with the initial access URL indicated by the link associated with the operation button as input information. Is automatically activated (S511). When the message application 23 has a browser inside itself, the browser may be used as the browser unit 22.

Upon activation, the browser unit 22 automatically transmits an HTTP request to the application determination unit 12 corresponding to the initial access URL included in the input information (S512). The HTTP request includes option information (one-shot ID, message user ID, target registration ID) of the initial access URL.

Upon receiving the HTTP request, the application determination unit 12 of the server device 10 authenticates the message ID and the one-shot ID included in the HTTP request. For example, if the message user ID is stored as the message user ID of any user in the user information storage unit 123 (FIG. 19) and the one-shot ID has not expired, the authentication is successful. , Otherwise authentication fails.

If the authentication is successful, the same processing as steps S206 to S209 of FIG. 11 is executed (S513 to S516). As a result, the upload screen 510 (FIG. 13) is displayed on the display device 211 of the user terminal 20.

After that, the processing procedure described in FIG. 14 is executed in response to the image data captured by the user terminal 20.

As described above, according to the second embodiment, the same effect as that of the first embodiment can be obtained without using the tag seal.

Next, a third embodiment will be described. In the third embodiment, the points different from the first embodiment will be described. The points that are not particularly mentioned in the third embodiment may be the same as in the first embodiment.

In the first embodiment and the second embodiment, an application ID (In-app ID) that controls input of image data and an application that controls output of image data with respect to a registration ID (tag seal or the like) The example in which the application ID (Out application ID), the browser ID, and the like are registered in the registration information storage unit 124 (FIG. 9) in advance has been described. However, the association of these IDs (services realized by these applications) with the registration IDs (tag stickers) does not necessarily have to be performed before the user terminal 20 holds the tag stickers. When the user terminal 20 is covered by an unregistered tag sticker, these IDs may be associated with the registration ID of the tag sticker. An unregistered tag sticker is a tag sticker whose registered ID is not registered (stored) in the registration information storage unit 124 (FIG. 9). Hereinafter, an example in which the user terminal 20 is covered by an unregistered tag sticker will be described as a third embodiment.

FIG. 21 is a diagram illustrating a functional configuration example of each device according to the third embodiment. 21, those parts that are the same as those corresponding parts in FIG. 6 are designated by the same reference numerals, and a description thereof will be omitted.

In FIG. 21, the server device 10 further includes a registration support unit 16 and a service information providing unit 17. These functions are realized by the processing executed by the CPU 104 by one or more programs installed in the server device 10.

The registration support unit 16 executes a process for supporting registration of an unregistered tag sticker (registration ID). The service information providing unit 17 provides the user terminal 20 with information on service candidates (options) to be associated with unregistered tag stickers (registration IDs). Here, description will be made using an example in which the registration support unit 16 and the service information providing unit 17 are realized by applications (a registration support application and a service information providing application). The application is an example of a program format, and the registration support unit 16 and the service information providing unit 17 may be realized by a program of another format, and the registration support unit 16 and the service information providing unit 17 have the same application. May be realized by.

The server device 10 also includes a service information storage unit 125. The service information storage unit 125 can be realized using, for example, the auxiliary storage device 102 or a storage device that can be connected to the server device 10 via a network. The service information storage unit 125 stores information about each service that can be provided by the server device 10.

FIG. 22 is a sequence diagram for explaining an example of a processing procedure executed according to the activation of the intermediary device 30 in the third embodiment. 22, those steps which are the same as those corresponding steps in FIG. 7 are designated by the same step numbers, and a description thereof will be omitted.

When the application determination unit 12 of the server device 10 receives the HTTP request in step S108, a record including the target browser ID (a registration ID associated with the target browser ID) is stored in the registration information storage unit 124 (FIG. 9). If it is not registered (stored) (that is, the projector 40 related to the target browser ID is not associated with any service), a response including a redirect request including the registration support application URL, the communication URL, and the target browser ID ( The HTTP response) is transmitted to the browser unit 33 (S121). The registration support application URL is a URL corresponding to the registration support unit 16 (that is, the registration support application).

Subsequently, the browser unit 33 transmits (redirects) an HTTP request to the registration support application URL (that is, the access destination of the registration support unit 16) that is the redirect destination according to the redirect request (S122). The HTTP request includes the communication URL and the target browser ID included in the redirect request.

In response to the HTTP request, the registration support unit 16 transmits, to the browser unit 33, a response including display data (HTML, script, etc.) of a screen indicating that the service is not registered for the tag sticker (S123).

Subsequently, the browser unit 33 draws a screen based on the display data included in the response (hereinafter referred to as “service unregistered screen”) in a predetermined area (for example, a video memory) of the memory device 103 ( S124). The drawing content (projection screen) by the browser unit 33 is output to the projector 40 via an interface such as HDMI (registered trademark) and is output (projected) by the projector 40 (S125).

FIG. 23 is a diagram showing an output example of the service unregistered screen. As shown in FIG. 23, the service non-registration screen 610 includes a message indicating that there is no service associated with the browser unit 33 of the intermediary device 30.

The user refers to the service unregistered screen 610 and confirms that the service is not registered in association with the browser unit 33 of the intermediary device 30 that is powered on (S125).

On the other hand, the distribution unit 11 generates a pass code (for example, randomly) for the browser unit 33 of the intermediation device 30 at regular intervals (for example, every 15 minutes) after the communication path is established in step S102, and The pass code and the target browser ID are notified to the communication control unit 31 of the intermediary device 30 via the communication path (S126). That is, the passcode is switched at regular time intervals. The delivery unit 11 associates the passcode notified last with the target browser ID and stores the passcode in the device information storage unit 122, for example.

FIG. 24 is a diagram showing a configuration example of the device information storage unit 122 in the third embodiment. In the third embodiment, the device information storage unit 122 further includes a passcode string. Here, the passcode column last notified to the communication control unit 31 is stored in the passcode column of the record corresponding to the target browser ID. FIG. 24 shows an example in which the target browser ID is “BROWSER1” and the passcode is “1965”. The passcode functions as information for identifying the intermediary device 30 (browser unit 33) and the projector 40 that are associated with the passcode transmitted from the user terminal 20 in the process described below.

Each time the communication control unit 31 receives the passcode, the communication control unit 31 notifies the browser unit 33 that is received together with the passcode and that is related to the target browser ID of the passcode (S127). The browser unit 33 additionally displays the passcode on the service unregistered screen 610 (S128). As a result, the service unregistered screen 610 including the passcode is output (projected) by the projector 40.

FIG. 25 is a diagram showing an output example of a service unregistered screen including a passcode. In FIG. 25, an example in which the passcode is “1965” is shown.

In this way, in a state where the passcodes are switched at regular time intervals, for example, when the user terminal 20 is held over an unregistered tag sticker attached to the intermediary device 30 related to the passcode, for example, The processing procedure shown in FIG. 26 is executed.

FIG. 26 is a sequence diagram for explaining an example of a processing procedure executed according to the proximity of the user terminal 20 to an unregistered tag sticker. 26, those steps which are the same as those corresponding parts in FIG. 11 are designated by the same step numbers, and a description thereof will be omitted.

When the account information is successfully authenticated in response to the HTTP request received in step S205, the application determination unit 12 of the server device 10 stores a record including the target registration ID included in the HTTP request in the registration information storage unit 124. If not stored (each ID such as a browser ID for the target registration ID is not registered in the registration information storage unit 124), a redirect request including the target registration ID is made with the service information providing application URL as the redirect destination. The response (HTTP response) shown is transmitted to the browser unit 22 (S221). The service information providing application URL is a URL corresponding to the service information providing unit 17 (that is, the service information providing application). When the record including the target registration ID is stored in the registration information storage unit 124, step S206 and the subsequent steps are executed as described in FIG.

In response to the redirect request, the browser unit 22 sends an HTTP request (redirect) to the service information providing application URL that is the redirect destination (that is, the access destination of the service information providing unit 17) (S222). The HTTP request includes the user ID of the user of the user terminal 20 and the target registration ID.

In response to the reception of the HTTP request, the service information providing unit 17 generates the display data (HTML, script, etc.) of the service menu screen by referring to the service information storage unit 125, and the browser unit 22 generates a response including the display data. To (S223).

FIG. 27 is a diagram showing a configuration example of the service information storage unit 125. As shown in FIG. 27, the service information storage unit 125 stores a service ID, an In app ID, and an Out app ID for each service that can be provided by the server device 10 (for each service candidate associated with a registration ID). It is associated and stored. The service ID is identification information of the service, and its value is different for each service. The In app ID is an app ID of an application that controls input of image data in the service. For example, “AP_Upload” indicates the application ID of the upload application 13 as described above. The Out application ID is an application ID of an application that controls output of image data in the service. For example, “AP_PhotoShow” indicates the application ID of the output application 14 as described above.

The service information providing unit 17 generates the display data of the service menu screen so that each service ID stored in the service information storage unit 125 (that is, the information of the service candidate) is selected.

Upon receiving the response, the browser unit 22 generates a service menu screen based on the display data and displays the service menu screen on the display device 211 (S224).

FIG. 28 is a diagram showing a display example of the service menu screen. As shown in FIG. 28, the service menu screen 620 includes a list of selectable service IDs.

When the user selects a service ID (hereinafter referred to as “target service ID”) to be associated with the tag sticker (target registration ID) attached to the intermediary device 30 via the service menu screen 620 (S225), the browser unit. 22 transmits the HTTP request including the user ID, the target registration ID, and the selection result (target service ID) to the distribution unit 11 of the server device 10 based on the definition of the display data of the service menu screen 620 (S226).

Upon receiving the HTTP request, the distribution unit 11 stores the In app ID and the Out app ID stored in the service information storage unit 125 (FIG. 27) in association with the target service ID included in the HTTP request, A record including the target registration ID included in the HTTP request (hereinafter, referred to as “target tag information record”) is registered in the registration information storage unit 124. As a result, the browser ID of the target tag information record remains as undetermined information. Therefore, the delivery unit 11 sends a response including display data (HTML, script, etc.) of the passcode input screen to the browser unit 22 to confirm the browser ID (S227).

Upon receiving the response, the browser unit 22 generates a passcode input screen based on the display data and displays the passcode input screen on the display device 211 (S228).

FIG. 29 is a diagram showing a display example of a passcode input screen. In FIG. 29, the passcode input screen 630 includes a passcode input area 631 and a setting button 632. The passcode input area 631 is an area for receiving the input of the passcode projected by the projector 40 connected to the intermediary device 30 associated with the target tag sticker. For example, if the service unregistered screen 610 currently projected by the projector 40 is as shown in FIG. 25, the user inputs “1965” in the passcode input area 631 and sets the setting button. Touch 632 (S229).

The browser unit 22 responds to the touch of the setting button 632 and, based on the definition of the display data of the passcode input screen 630, the HTTP including the passcode input to the passcode input area 631 and the user ID and the target registration ID. The request is transmitted to the distribution unit 11 of the server device 10 (S230).

The delivery unit 11 searches the device information storage unit 122 (FIG. 24) for a browser ID stored in association with the passcode included in the HTTP request, and retrieves the browser ID from the target tag information record “ Register in the item of "Browser ID". As a result, the content of the target tag information record is confirmed. That is, the service and the projector 40 (the intermediary device 30 connected to the projector 40) corresponding to the browser ID are registered in association with the target registration ID (target tag sticker).

Subsequently, the distribution unit 11 transmits a response including the display data of the service confirmation screen showing the confirmation of the service registration to the browser unit 22 (S231). Upon receiving the response, the browser unit 22 generates a service confirmation screen based on the display data and displays the service confirmation screen on the display device 211 (S232).

FIG. 30 is a diagram showing a display example of the service confirmation screen. As shown in FIG. 30, the service confirmation screen 640 includes a message indicating that the browser ID of the browser unit 33 of the intermediary device 30 associated with the service and the service ID of the service are associated and registered. ..

The distribution unit 11 also has a browser ID (hereinafter, referred to as “target browser ID”) of the browser unit 33 of the intermediation device 30 associated with the service, a target registration ID, and a user ID of the user of the user terminal 20 (hereinafter, referred to as “user ID”). , "Target user ID") is transmitted to the communication control unit 31 of the mediation device 30 (S233). Upon receiving the service confirmation notification, the communication control unit 31 transmits the service confirmation notification including the target registration ID and the target user ID to the browser unit 33 related to the target browser ID (S234).

When the browser unit 33 receives the service confirmation notification, the browser unit 33 inputs the service confirmation notification into the script forming the display data of the service non-registration screen 610 (FIG. 25), so that a predetermined area of the memory device 103 (for example, The drawing content of the video memory) is switched from the service unregistered screen 610 (FIG. 25) to the display screen of the service confirmation notification (hereinafter referred to as “service confirmation notification screen”) (S235). The drawing content (projection screen) by the browser unit 33 is output to the projector 40 via an interface such as HDMI (registered trademark) and is output (projected) by the projector 40.

FIG. 31 is a diagram showing an output example of the service confirmation notification screen. As shown in FIG. 31, the service confirmation notification screen 650 includes a message indicating that the user associated with the target user ID (“Mr. A” in FIG. 31) has registered a service, a passcode, and the like.

The user who has performed the work displays the service confirmation screen 640 (FIG. 30) on the user terminal 20 that is covered by the unregistered tag sticker attached to the intermediary device 30, and the projector 40 connected to the intermediary device 30 displays the service confirmation screen 640 (FIG. 30). By outputting the service confirmation notification screen 650 (FIG. 31), it is possible to confirm that the service using the desired device (the intermediary device 30 and the projector 40) is registered for the tag sticker.

As described above, according to the third embodiment, the server device 10 registers the tag sticker transmitted from the user terminal 20 when the user terminal 20 is held (close to) the unregistered tag sticker. When the ID is received, if the projector 40 is not registered in the server device 10 in association with any of the services, the user terminal 20 is provided with information on the candidate of the service associated with the projector 40. The projector 40 identified based on the information (passcode) for identifying the projector 40 associated with the service related to the received service selection result, the service associated with the selection result, and the registration ID are registered in association with each other. Therefore, according to the present embodiment, the association between the device and the service can be realized by a simple operation.

The server device 10, the intermediary device 30, the output device such as the projector 40, the user terminal 20, and the message service 50 in the above-described embodiment may each be constructed by a single computer, or each unit (function or means). May be constructed by a plurality of computers that are divided and arbitrarily assigned.

Each function of the above-described embodiments can be realized by one or a plurality of processing circuits. Here, the “processing circuit” in the present specification is a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, or designed to execute each function described above. Devices such as ASICs (Application Specific Integrated Circuits), DSPs (digital signal processors), FPGAs (field programmable gate arrays), and conventional circuit modules are included.

In each of the above embodiments, the intermediary device 30 and the server device 10 are an example of an information processing system. The server device 10 is an example of an information processing device. The user terminal 20 is an example of a terminal. The distribution unit 11 is an example of a registration unit.

Although the embodiments of the present invention have been described in detail above, the present invention is not limited to such specific embodiments, and various modifications are possible within the scope of the gist of the present invention described in the claims. It can be modified and changed.

1 Information Processing System 10 Server Device 11 Distribution Unit 12 Application Determination Unit 13 Uploaded Application 14 Output Application 15 Message Bot 16 Registration Support Unit 17 Service Information Providing Unit 20 User Terminal 21 Information Acquisition Unit 22 Browser Unit 23 Message Application 30 Mediation Device 31 Communication Control unit 32 Browser management unit 33 Browser unit 40 Projector 50 Message service 100 Drive device 101 Recording medium 102 Auxiliary storage device 103 Memory device 104 CPU
105 interface device 121 application information storage unit 122 device information storage unit 123 user information storage unit 124 registration information storage unit 125 service information storage unit 201 CPU
202 ROM
203 RAM
204 Touch Panel 205 Auxiliary Storage Device 206 Near Field Communication 207 Digital Camera 211 Display Device 212 Input Device 301 Auxiliary Storage Device 302 Memory Device 303 CPU
304 communication interface 305 image interface 306 short-range wireless communication device B bus

Japanese Patent No. 6098193

Claims (7)

An information processing system including an intermediary device capable of communicating with a device, and an information processing device capable of communicating with the intermediary device,
The information processing device,
When the terminal receives the identification information acquired from the outside from the terminal, if the device is not registered in the information processing device in association with any service, information about a service candidate associated with the device is acquired by the terminal. A service information providing section provided to
A registration unit that registers the device identified based on the information for identifying the device associated with the service related to the service selection result received from the terminal, the service related to the selection result, and the identification information in association with each other; ,
An information processing system comprising: The information processing device,
When a predetermined request is received from the intermediary device capable of communicating with the device that is not associated with any of the services and registered, a distribution unit that transmits information for identifying the device to the intermediary device is provided. Then
The intermediary device causes the device that can communicate with the intermediary device to output the information transmitted by the distribution unit,
The information processing system according to claim 1, wherein: When the device is registered in the information processing device in association with any service, the execution request of the process related to the service associated with the device is registered in association with the device. Send it to the intermediary device,
The intermediary device is
Controlling the device by executing processing according to the execution request,
The information processing system according to claim 2, wherein: An information processing method in an information processing system including an intermediary device capable of communicating with a device, and an information processing device capable of communicating with the intermediary device,
The information processing device is
When the terminal receives the identification information acquired from the outside from the terminal, if the device is not registered in the information processing device in association with any service, information about a service candidate associated with the device is acquired by the terminal. Service information provision procedure to be provided to
A registration procedure for registering the device identified based on the information for identifying the device associated with the service related to the service selection result received from the terminal, the service related to the selection result, and the identification information in association with each other; ,
An information processing method characterized by executing. An information processing device capable of communicating with an intermediary device capable of communicating with a device,
When the terminal receives the identification information acquired from the outside from the terminal, if the device is not registered in the information processing device in association with any service, information about a service candidate associated with the device is acquired by the terminal. A service information providing section provided to
A registration unit that registers the device identified based on the information for identifying the device associated with the service related to the service selection result received from the terminal, the service related to the selection result, and the identification information in association with each other; ,
An information processing device comprising: An information processing device capable of communicating with an intermediary device capable of communicating with a device,
When the terminal receives the identification information acquired from the outside from the terminal, if the device is not registered in the information processing device in association with any service, information about a service candidate associated with the device is acquired by the terminal. Service information provision procedure to be provided to
A registration procedure for registering the device identified based on the information for identifying the device associated with the service related to the service selection result received from the terminal, the service related to the selection result, and the identification information in association with each other; ,
An information processing method characterized by executing. An information processing device capable of communicating with an intermediary device capable of communicating with a device,
When the terminal receives the identification information acquired from the outside from the terminal, if the device is not registered in the information processing device in association with any service, information about a service candidate associated with the device is acquired by the terminal. Service information provision procedure to be provided to
A registration procedure for registering the device identified based on the information for identifying the device associated with the service related to the service selection result received from the terminal, the service related to the selection result, and the identification information in association with each other; ,
A program characterized by causing to execute.

Images