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

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 the server device, a workflow is performed based on the combination of the service ID and the device ID received by the server device. Techniques such as identifying and executing specified workflows are disclosed. Further, as an execution example of the workflow, it is disclosed that the image synthesized by the server device is transmitted to the signage device.

However, Patent Document 1 does not disclose how to register an association between a service, a device, and a workflow.

The present invention has been made in view of the above points, and an object of the present invention is to make it possible to realize an association between a device and a service by a simple operation.

Therefore, in order to solve the above problem, the information processing system includes an intermediary device capable of communicating with the device and an information processing device capable of communicating with the intermediary device, and the information processing device is an identification acquired from the outside by the terminal. When information is received from the terminal, service information that provides information on candidate services associated with the device to the terminal when the device is not registered in association with any service in the information processing device. The provider and the device specified based on the information for specifying 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. It has a registration unit and a registration unit.

It is possible to realize the association between the device and the service with 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 configuration example of the server apparatus 10 in 1st Embodiment. It is a figure which shows the hardware configuration example of the user terminal 20 in 1st Embodiment. It is a figure which shows the hardware configuration example of the intermediary device 30 in 1st Embodiment. It is a figure for demonstrating the outline of the 1st Embodiment. It is a figure which shows the functional composition example of each apparatus in 1st Embodiment. It is a sequence diagram for demonstrating an example of the processing procedure executed in response to the activation of an 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 configuration example of the application information storage part 121. It is a sequence diagram for demonstrating an example of the processing procedure executed according to the proximity of a user terminal 20 with respect to a tag seal. It is a figure which shows the configuration example of the user information storage unit 123. It is a figure which shows the display example of the upload screen. It is a sequence diagram for demonstrating an example of the processing procedure of the image data distribution processing from a user terminal 20 to an 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 configuration example of the intermediary device 30 in the 2nd Embodiment. It is a figure which shows the functional composition example of each apparatus in 2nd Embodiment. It is a sequence diagram for demonstrating an example of the processing procedure of the preparatory processing in 2nd 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 demonstrating an example of the processing procedure executed according to the proximity of a user terminal 20 with respect to the origin of a message beacon. It is a figure which shows the functional composition example of each apparatus in 3rd Embodiment. It is a sequence diagram for demonstrating an example of the processing procedure executed in response to the activation of an intermediary device 30 in the 3rd Embodiment. It is a figure which shows the output example of the service unregistered 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 output example of the service unregistered screen including a passcode. It is a sequence diagram for demonstrating an example of the processing procedure executed according to the proximity of a user terminal 20 with respect to an unregistered tag seal. It is a figure which shows the configuration example of the service information storage part 125. It is a figure which shows the display example of a service menu screen. It is a figure which shows the display example of the passcode input screen. It is a figure which shows the display example of the service confirmation screen. It is a figure which shows the output example of a service confirmation notification screen.

Hereinafter, the first embodiment will be described with reference to the drawings. FIG. 1 is a diagram showing 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 one or more output devices such as projectors 40 and one or more intermediary devices 30 are installed. The projector 40 is a device that projects an input image onto 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 corresponding to the interface (for example, an HDMI (registered trademark) cable or the like). Alternatively, the connector of the intermediary device 30 corresponding to the interface and the connector of the projector 40 to the interface may be directly connected. For example, both 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.

By connecting the projector 40 and the mediation device 30 as described above, the mediation device 30 can transmit an image to be projected 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 intermediary device 30 is provided with a Web browser inside, and the Web browser executes processing in response to a processing execution request for image data transmitted from the server device 10 to control an output device such as a projector 40 (for example). The execution result of the process is output to the projector 40). Specifically, in the present embodiment, the intermediary device 30 causes the projector 40 to output (for example, project) the image data. That is, the mediation device 30 mediates the output (for example, projection) of an image by the projector 40 for the data transmitted from the server device 10. 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 able to connect to the network in the user environment E1.

The server device 10 is one or more computers that execute a process for realizing output by an output device such as a projector 40 for the image data specified in the user terminal 20 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 showing a hardware configuration example of the server device 10 according to the first embodiment. The server device 10 of FIG. 2 has a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, an interface device 105, and the like, which are connected to each other by a bus B, respectively.

The 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 in the auxiliary storage device 102 from the recording medium 101 via the drive device 100. However, the program does not necessarily have to be installed from the recording medium 101, and may be downloaded from another computer via the network. The auxiliary storage device 102 stores the installed program and also stores necessary files, data, and the like.

The memory device 103 reads and stores the program from the auxiliary storage device 102 when the program is instructed to start. The CPU 104 executes the function related to the server device 10 according to the 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 showing 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 and stores the program from the ROM 202 or the auxiliary storage device 205 when the program is instructed to start. 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, accepts input from a user, and the like. 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 is responsible for the 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 means an object that comes into contact with the contact surface (surface) of the touch panel 204. Examples of such an object include a user's finger, a dedicated or general pen, and the like. The touch panel 204 does not necessarily have to be provided, and the user terminal 20 may separately include the display device 211 and the input device 212. Further, the display device 211 may be externally connected to the user terminal 20. Further, the input device 212 is not limited to a sensor that detects contact, but also 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 NFC reader is suitable for the short-range wireless communication device 206. The digital camera 207 is a general digital camera having an image pickup 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 showing a hardware configuration example of the intermediary device 30 according to the first embodiment. The mediation device 30 in 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, data, and the like.

The memory device 302 reads and stores the program from the auxiliary storage device 301 when the program is instructed to start. The CPU 303 executes the function related to the intermediary 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 an 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 contains information including the URL that the user terminal 20 should first access (hereinafter referred to as "initial access URL") among the URLs for accessing the server device 10 (hereinafter referred to as "tag information"). Is remembered. In the tag information, a registration ID is added as optional information to the initial access URL. For example, the tag information has the following format.
https: // xxx. yyy. com /? tagid = Tag01
Here, the part of "XXX" in "tagid = XXX" (in the above, "Tag01") 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 seal, or the same registration ID may be assigned to a plurality of tag seals. On the other hand, the part (initial access URL) of "https: //xxx.yy.com/" may be common to the tag information stored in each tag seal 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, for example, the user terminal 20 on 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 tag the tag. Acquire information (S2). Subsequently, the user terminal 20 accesses the server device 10 which is the destination (“https: //xxx.yy.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 the execution of the service registered in advance in association with the registration ID. For example, if the service projects the image data captured by the user terminal 20 onto a specific projector 40, the server device 10 acquires the image data captured by the user terminal 20 from the user terminal 20 and obtains the image data captured by the user terminal 20. The image data is transmitted to the intermediary device 30 associated with the registration ID (S4). The server device 10 transmits, for example, display data of a screen prompting the upload of image data to the user terminal 20, and receives image data captured by the user terminal 20 in response to an operation by the user via the screen. The image data is acquired by receiving from.

Upon receiving the image data from the server device 10, the intermediary 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 related to the output device as described above by a simple operation such as acquiring the tag information from the outside of the user terminal 20. For example, in the example described above, the above service can be received by a simple operation such as holding (approaching) the user terminal 20 to the tag sticker arranged (attached) to the projector 40. As described above, the service to be executed according to the registration ID is specified. That is, different services can be associated with each registration ID.

In order to realize the process described in FIG. 5, the user terminal 20, the intermediary device 30, and the server device 10 have a functional configuration as shown in FIG.

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

The information acquisition unit 21 acquires tag information (initial access URL including the registration ID) from the tag seal 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 in which a part of the OS (Operating System) of the user terminal 20 is executed by the CPU 201.

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, Javascript (registered trademark)), or the like. The browser unit 22 inputs the registration ID and the like included in the tag information URL to 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. Send. The browser unit 22 also accesses the application associated with the registration ID among the applications possessed by the server device 10 according to the redirect request which 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, a script, etc.) indicating a processing execution request 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 parts is realized by a process of causing the CPU 303 to execute 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 end point on the mediation device 30 side 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 implementation). In the form of, the notification of (uploaded from the user terminal 20) can be received from the server device 10.

The browser management unit 32 starts 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 the display of a Web page. The kiosk mode is just an example, and may be another mode 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, a script, or the like. The browser unit 33 accesses the initial access URL (that is, the application determination unit 12 of the server device 10) in response to activation. At this time, the identification information of the browser unit 33 (hereinafter referred to as “browser ID”) is added as optional information to the initial access URL. The browser unit 33 accesses the application associated with the browser ID among the applications possessed by the server device 10 according to the redirect request which is the response from the application determination unit 12 in response to the access to the initial access URL. The browser unit 33 acquires data (HTML data, a script, etc.) indicating a processing execution request to the intermediary device 30 from the application. The drawing content based on the data by the browser unit 33 is output to the projector 40 via the 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 parts is realized by a process of causing 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 by using, for example, a storage device that can be connected to the auxiliary storage device 102 or 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 a 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 an application corresponding to the option information (registration ID or browser ID) given to the initial access URL with reference to the registration information storage unit 124. The application determination unit 12 transmits a response including a redirect request including a URL to the determined application to the access source to the initial access URL. In the present embodiment, for access from the user terminal 20 from which the image data is input, the URL of the upload application 13 is determined as an application corresponding to the registration ID. Further, regarding the access from the intermediary device 30 to which the image data is output, 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 included in the server device 10 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 HTML data, a script, and the like for executing uploading of image data to the user terminal 20. The output application 14 is an application for causing the intermediary device 30 to acquire (download) and output the image data uploaded from the user terminal 20. Specifically, the output application 14 transmits HTML data, a script, and the like for causing the intermediary device 30 to execute the acquisition and output to the intermediary device 30.

The application information storage unit 121 stores information (for example, URL, etc.) about each of the applications (upload application 13 and output application 14 in the present embodiment) of the server device 10.

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

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 contains identification information of an application that executes image data input processing, identification information of an application that executes image data output processing, and an intermediary device that is an input destination of image data for each registration ID. The identification information of the browser unit 33 of the 30 (that is, the identification information of the projector 40) is stored.

Hereinafter, the 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 the 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 between the distribution unit 11 and the distribution unit 11 for asynchronously receiving the request from the distribution unit 11 of the server device 10. (S102). At this time, the communication control unit 31 notifies the distribution unit 11 of the communication ID, which is the identification information of itself (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, an address information, a state information, a browser ID, a browser state, and the like in association with the tenant ID. The tenant ID is identification information of a contractor (tenant) of a service 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 related to the tenant ID. When the intermediary device 30 includes only one communication control unit 31, the communication ID may be identification information for identifying the intermediary device 30. The address information is the local IP address of the intermediary device 30. The state information is information indicating whether or not the communication control unit 31 related to the communication ID is connected to the server device 10 (a state in which a communication path is established) (“not connected”). 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 the projector 40 of the output destination of the drawing contents 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 state information corresponding to the communication ID in the device information storage unit 122 is set to "connecting" as shown in FIG. Be changed.

Subsequently, the communication control unit 31 searches for the browser management unit 32 in order to acquire the browser ID using, for example, SNMP (Simple Network Management Protocol) (S103), and from the found browser management unit 32. , Acquire the browser ID which is the identification information of the browser unit 33 which is the management target of the browser management unit 32 (S104). In the present embodiment, an example in which the communication control unit 31 and the browser management unit 32 are provided in the intermediary device 30 is shown, but the communication control unit 31 included in the intermediary device 30 is included in the other intermediary device 30. In order to make a plurality of browser management units 32 and browser units 33 available 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 indispensable, 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 notifies that the browser unit 33 (in the present embodiment, the browser unit 33 of the intermediary device 30) corresponding to the acquired browser ID is in a usable state. A 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".

Subsequently, 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 refers to the URL that the browser unit 33 should first access, and is preset in the browser management unit 32.

The browser management unit 32 activates the browser unit 33 related to the target browser ID in the kiosk mode in response to the request from the communication control unit 31 (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 HTTP request includes the target browser ID.

Upon receiving the HTTP request, the application determination unit 12 of the server device 10 transmits a response including the 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, the registration information storage unit 124 stores the registration ID, the In application ID, the Out application ID, and the browser ID in association with each other.

The In application ID is an ID of an application that controls input of image data (hereinafter referred to as "application ID") in a service corresponding to a registration 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 related to the application ID based on the relationship with the image data. “In” indicates that the application controls the input of image data (corresponding to the above-mentioned In application ID). "Out" indicates that the application controls the output of image data (corresponding to the above-mentioned Out application ID). The URL is the URL of the application related to the application ID.

Therefore, the application determination unit 12 refers to the registration information storage unit 124 to specify 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. Identify the attached URL. Here, it is assumed that the target browser ID is "BROWSER1". In this case, the URL of the application (output application 14) whose application ID is "AP_PhotoShow" (hereinafter, "output application URL") is specified.

Further, 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).

Subsequently, the browser unit 33 transmits (redirects) the HTTP request to the output application URL (that is, the output application 14) which is the redirect destination in accordance with the redirect request (S110). The HTTP request includes the communication URL and 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 execute a connection to the communication URL included in the HTTP request, and outputs image data (for example, a slide show). A response including display data (photo.http) for causing the browser unit 33 to draw a user interface for the purpose is transmitted to the browser unit 33 (S111). The script and the display data are examples of data indicating a processing execution request to the intermediary device 30. For example, the script may be a program of another format, and the display data may be data of 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 puts a screen (hereinafter, referred to as “projection screen”) based on the display data (photo.html) included in the response into a predetermined area (for example, video memory) of the memory device 103. Draw (S113). For example, the projection screen is a screen that functions as a frame to which 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 seal.

When the user brings the user terminal 20 close to the tag sticker attached to the projector 40 (for example, when the user terminal 20 is held) (S201), the information acquisition unit 21 uses the short-range wireless communication device 206 for short-range wireless communication. The tag information stored in the tag seal is acquired via 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 optional information. In this embodiment, the value of the target registration ID is "Tag01".

Subsequently, the information acquisition unit 21 starts the browser unit 22 using the tag information as input information based on the fact that the tag information includes the URL (S204).

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 which 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 user identification information 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 tenant ID can be specified. Information. For example, Cookie or the like may be used as 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. Authentication is performed, for example, by 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.

If the authentication is successful, the application determination unit 12 transmits a response (HTTP response) including a redirect request to the browser unit 22 (S206). In the redirect request, the upload application 13 related to the In application ID (“AP_Upload”) stored in the registration information storage unit 124 (FIG. 9) associated with the target registration ID (“Tag01”) as the redirect destination. A 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).

The browser unit 22 transmits an HTTP request (redirect) to the upload application URL (that is, the upload application 13) which is the redirect destination in accordance with the redirect request (S207).

The upload application 13 responds to the HTTP request by displaying data (upload.html) of a screen (hereinafter referred to as “upload screen”) related to uploading image data to the distribution unit 11 of the server device 10 and operating the upload screen. 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 processing execution request 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 receiving an instruction to start an imaging operation. The user selects button 511 to perform imaging. 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 or the like) 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). Upon receiving 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, an auxiliary storage device 102 or the like in association with (referred to as "image ID").

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

When the communication control unit 31 receives the upload notification, the communication control unit 31 establishes a communication path 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 by 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 image data (photo.jpg) 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 projection screen drawn in step S113 of FIG. 7 (for example). 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.

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

In the above, the device connected to the intermediary device 30 is the projector 40, but 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, or the like, or may be printed by a printer.

Further, in the above description, for convenience of explanation, 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, a tag sticker may be attached to an arbitrary 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 seal, and causes the intermediary device 30 to perform a preset process associated with the tag seal (registration ID). It can be executed by a connected device (for example, a projector 40). That is, since the user does not need to directly operate the projector 40 or the like and can operate the projector 40 or the like by operating the user terminal 20, the operability of the device such as the projector 40 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 dependence on the device related to the tag seal 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 each device is used by a highly unified operation across a plurality of devices. You will be able to.

Further, by interposing the intermediary device 30 between the server device 10 and the device (projector 40), even if the device does not have a network function, 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 there is no need to change the setting information in the server device 10.

Further, in the present embodiment, it is sufficient that the program possessed by a general smartphone or the like is installed in the user terminal 20, 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 by an interface for transmitting image data, for example, there is no need to make settings for a wireless LAN connection via a router or a wired LAN connection. be.

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

Alternatively, the user terminal 20 may receive a sound wave transmitted from a transmission device installed near the output device or the output device itself or a beacon described later, and acquire the received sound wave or 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 tag information from an external recording medium (for example, a sticker) on which an image is printed. In this case, the user terminal 20 may input the image by the digital camera 207 and extract the tag information from the tint block or the like embedded in the image. A known technique may be used for embedding information such as a tint block in an image and extracting information from the tint block.

Next, the second embodiment will be described. The second embodiment will explain the differences from the first embodiment. Therefore, the same as in the first embodiment may be used without particular mention.

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 seal. .. Hereinafter, the beacon is referred to as a "message beacon".

FIG. 15 is a diagram showing a configuration example of the information processing system according to the second embodiment. In FIG. 15, the same parts as those in FIG. 1 are designated by the same reference numerals, and the 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 registers as a user with the message service 50 and receives the issuance of the user ID for the message application 23.

FIG. 16 is a diagram showing a hardware configuration example of the intermediary device 30 according to the second embodiment. In FIG. 16, the same parts as those in FIG. 4 are designated by the same reference numerals, and the 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 the present embodiment, the short-range wireless communication device 306 is used for transmitting a message beacon.

FIG. 17 is a diagram showing a functional configuration example of each device according to the second embodiment. In FIG. 17, the same parts as those in FIG. 6 are designated by the same reference numerals, and the 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 also has a message bot 15. The message bot 15 is a program (Bot) that automatically executes transmission / reception of messages with / from the message application 23.

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

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

After that, the message bot ID is notified to the user of the user terminal 20 (S402). For example, an e-mail containing a 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 into the message application 23 of the user terminal 20 and instructs friend registration (S403), the message application 23 uses the user ID of the user related to the message application 23 (hereinafter, "message user"). The friend registration request including the "ID") and the input message bot ID is 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 user related to the message user ID included in the friend registration request registers as a friend with respect to the message bot 15 related to the message bot ID included in the friend registration request. Notify that it has been done (S405).

Subsequently, the message bot 15 transmits a beacon application including the message bot ID to the message service 50 in order to enable transmission of the message beacon from the intermediary device 30, and the Hardware ID (hereinafter referred to as “HID”) included in the message beacon. .) 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 related to the tenant ID corresponding to the message user ID in which the message bot 15 is registered as a friend. (S407). The registration request includes an HID, a browser ID corresponding to the tenant ID, and a 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, the message user ID is associated with each set of the tenant ID and the user ID in the user information storage unit 123. Therefore, the message bot 15 can specify the tenant ID corresponding to the message user ID by referring to the user information storage unit 123.

Further, 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. Request the transmission of (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 the 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. The processing procedure of FIG. 7 is executed before the execution of the processing procedure of FIG. 20.

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 (S501). S502), the HID (hereinafter referred to as “target HID”) and the registration ID (hereinafter referred to as “target registration ID”) included in the 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 by BLE or the like 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 message application 23 of the user terminal 20 of the contents of the message beacon (target HID and target registration ID) based on the format of the message beacon corresponding to the message application 23. (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 and the like that have 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 a one-shot ID and an 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 a 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. Further, the one-shot ID is identification information for limiting the period during which the user can log in to the server device 10, 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 deadline for logging in. If the period during which the user can log in to the server device 10 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, and responds to the message user ID stored in association with the message ID included in the response, such as the content of the response from the message bot 15. A message including (initial access URL, one-shot ID, relevant 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 an initial access URL that includes a one-shot ID, the message user ID, and a 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.

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

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 according to the activation (S512). The HTTP request includes optional 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, the authentication will fail.

If the authentication is successful, the same processing as in 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 with reference to FIG. 14 is executed in response to the image data being 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. The third embodiment will explain the differences from the first embodiment. The points not particularly mentioned in the third embodiment may be the same as those in the first embodiment.

In the first embodiment and the second embodiment, for the registration ID (tag seal or the like), the ID of the application that controls the input of the image data (In application ID) and the application that controls the output of the image data. An 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 registered IDs (tag seals) does not necessarily have to be performed before the user terminal 20 holds the tag seals. When the user terminal 20 is placed on an unregistered tag seal, these IDs may be associated with the registered ID of the tag seal. The unregistered tag seal means a tag seal in which the registration ID of the tag seal is not registered (stored) in the registration information storage unit 124 (FIG. 9). Hereinafter, an example in which the user terminal 20 is held over an unregistered tag seal will be described as a third embodiment.

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

In FIG. 21, the server device 10 further has a registration support unit 16 and a service information providing unit 17. These functions are realized by a process of causing the CPU 104 to execute one or more programs installed in the server device 10.

The registration support unit 16 executes a process for supporting the registration of an unregistered tag seal (registration ID). The service information providing unit 17 provides the user terminal 20 with information on service candidates (options) associated with the unregistered tag seal (registration ID). Here, an example in which the registration support unit 16 and the service information provision unit 17 are realized by applications (registration support application, service information provision application) will be described. 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 are the same application. May be realized by.

The server device 10 also has a service information storage unit 125. The service information storage unit 125 can be realized by using, for example, a storage device that can be connected to the auxiliary storage device 102 or 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 in response to activation of the intermediary device 30 in the third embodiment. In FIG. 22, the same steps as those in FIG. 7 are assigned the same step numbers, and the description thereof will be omitted.

When the application determination unit 12 of the server device 10 receives the URL request in step S108, a record including the target browser ID (registration ID associated with the target browser ID) is stored in the registration information storage unit 124 (FIG. 9). If it is not registered (remembered) (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 (that is, the target browser ID is not associated with any service). The URL 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) the HTTP request to the registration support application URL (that is, the access destination of the registration support unit 16) which is the redirect destination in accordance with 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 a response including screen display data (HTML, a script, etc.) indicating that the service is not registered to the tag seal to the browser unit 33 (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, video memory) of the memory device 103 (for example, a video memory). 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 unregistered 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 associated with and registered with the browser unit 33 of the intermediary device 30 that has been turned on (S125).

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

FIG. 24 is a diagram showing a configuration example of the device information storage unit 122 according to the third embodiment. In the third embodiment, the device information storage unit 122 further has a sequence of passcodes. Here, the passcode 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 associated with the passcode transmitted from the user terminal 20 in the process described later.

Each time the communication control unit 31 receives the passcode, the communication control unit 31 notifies the browser unit 33, which is received together with the passcode and 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. FIG. 25 shows an example in which the passcode is "1965".

In this way, in a state where the passcode is switched at regular time intervals, for example, when the user terminal 20 is held against the 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 seal. In FIG. 26, the same steps as those in FIG. 11 are assigned the same step numbers, and the description thereof will be omitted.

When the application determination unit 12 of the server device 10 succeeds in authenticating the account information in response to the reception of the HTTP request in step S205, the record including the target registration ID included in the HTTP request is stored in the registration information storage unit 124. If it is not stored (each ID such as a browser ID is not registered in the registration information storage unit 124 with respect to the target registration ID), the service information providing application URL is set as the redirect destination and a redirect request including the target registration ID is made. The indicated response (HTTP response) 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 subsequent steps are executed as described in FIG.

The browser unit 22 transmits an HTTP request (redirect) to the service information providing application URL (that is, the access destination of the service information providing unit 17) which is the redirect destination in accordance with the redirect request (S222). The HTTP request includes a user ID of the user of the user terminal 20 and a target registration ID.

In response to the reception of the HTTP request, the service information providing unit 17 generates display data (HTML, script, etc.) on the service menu screen with reference to the service information storage unit 125, and generates a response including the display data in the browser unit 22. (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 has a service ID, an In application ID, and an Out application ID for each service that can be provided by the server device 10 (for each service candidate associated with the registration ID). Associated and remembered. The service ID is the identification information of the service, and its value differs for each service. The In application ID is an application ID of an application that controls the 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 the 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 display data of the service menu screen so that each service ID (that is, service candidate information) stored in the service information storage unit 125 is selected as an option.

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") 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 an HTTP request including a user ID, a target registration ID, and a selection result (target service ID) to the distribution unit 11 of the server device 10 based on the definition of the display data on the service menu screen 620 (S226).

Upon receiving the HTTP request, the distribution unit 11 receives the In-appli ID and the Out-appli ID stored in the service information storage unit 125 (FIG. 27) associated 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, in order to determine the browser ID, the distribution unit 11 transmits a response including the display data (HTML, script, etc.) of the passcode input screen to the browser unit 22 (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 the passcode input screen. In FIG. 29, the passcode input screen 630 includes a passcode input area 631 and a setting button 632 and the like. 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 seal. For example, if the service unregistered screen 610 currently projected by the projector 40 is as shown in FIG. 25, the user inputs "1965" to the passcode input area 631 and presses 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 unit 22 includes the passcode input to the passcode input area 631 and the HTTP including the user ID and the target registration ID. The request is transmitted to the distribution unit 11 of the server device 10 (S230).

The distribution unit 11 searches the device information storage unit 122 (FIG. 24) for the browser ID associated with and stored in the passcode included in the HTTP request, and uses the browser ID as the "target tag information record". Register in the "Browser ID" item. As a result, the content of the target tag information record is fixed. That is, the service and the projector 40 (intermediary device 30 connected to the projector 40) corresponding to the browser ID are associated and registered with the target registration ID (target tag seal).

Subsequently, the distribution unit 11 transmits a response including the display data of the service confirmation screen indicating 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 to which the service is associated 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 intermediary device 30 to which the service is associated, a target registration ID, and a user ID of the user of the user terminal 20 (hereinafter referred to as “target browser ID”). , "Target user ID") and a service confirmation notification is transmitted to the communication control unit 31 of the intermediary device 30 (S233). Upon receiving the service confirmation notification, the communication control unit 31 transmits a 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).

Upon receiving the service confirmation notification, the browser unit 33 inputs the service confirmation notification into the script constituting the display data of the service unregistered screen 610 (FIG. 25), thereby inputting the service confirmation notification to a predetermined area (for example, for example) of the memory device 103. The drawing content of the video memory) is switched from the service unregistered screen 610 (FIG. 25) to the service confirmation notification display screen (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 to the effect that the user related to the target user ID (“Mr. A” in FIG. 31” has registered the 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 held over 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 can be confirmed that the service using the desired devices (intermediary device 30 and projector 40) has been registered for the tag seal.

As described above, according to the third embodiment, the server device 10 registers the tag seal transmitted from the user terminal 20 by holding (proximating) the user terminal 20 with respect to the unregistered tag seal. Upon receiving the ID, when the projector 40 is not registered in association with any service in the server device 10, information on service candidates associated with the projector 40 is provided to the user terminal 20 from the user terminal 20. The projector 40 specified based on the information (passcode) for specifying the projector 40 associated with the service related to the selected service of the received service, the service related to 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 embodiment may be constructed by a single computer, or each part (function or means). It may be constructed by a plurality of computers arbitrarily assigned by dividing the above.

It should be noted that each function of the embodiment described above can be realized by one or a plurality of processing circuits. Here, the "processing circuit" as used herein is a processor programmed to perform each function by software, such as a processor implemented by an electronic circuit, or a processor designed to execute each function described above. It shall include devices such as ASIC (Application Specific Integrated Circuit), DSP (digital signal processor), FPGA (field programmable gate array) and conventional circuit modules.

In each of the above embodiments, the intermediary device 30 and the server device 10 are examples 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 aspects are within the scope of the gist of the present invention described in the claims. It can be transformed and changed.

1 Information processing system 10 Server device 11 Distribution unit 12 App judgment unit 13 Upload application 14 Output application 15 Message bot 16 Registration support unit 17 Service information provision 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 App 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 Short-range wireless communication device 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 Near field communication B bus

Japanese Patent No. 6098193

Claims (7)

An information processing system including an intermediary device capable of communicating with an apparatus 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 association with any service in the information processing device, the information of the service candidate associated with the device is transmitted to the terminal. Service information provision department to provide to
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. ,
An information processing system characterized by having. The information processing device is
When a predetermined request is received from the intermediary device that can communicate with the device that is not registered in association with any service, it has a distribution unit that transmits information for identifying the device to the intermediary device. death,
The intermediary device outputs the information transmitted by the distribution unit to a device capable of communicating with the intermediary device.
The information processing system according to claim 1, wherein the information processing system is characterized by the above. When the device is registered in association with any service in the information processing device, the execution request of the process related to the service associated with the device is registered in association with the device. Send to the intermediary device,
The intermediary device is
Control the device by executing processing according to the execution request.
2. The information processing system according to claim 2. An information processing method in an information processing system including an intermediary device capable of communicating with an apparatus 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 association with any service in the information processing device, the information of the service candidate associated with the device is transmitted to the terminal. Service information provision procedure to be provided to
A registration procedure for associating and registering 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 identification information. ,
An information processing method characterized by executing. An information processing device that can communicate with an intermediary device that can communicate with the device.
When the terminal receives the identification information acquired from the outside from the terminal, if the device is not registered in association with any service in the information processing device, the information of the service candidate associated with the device is transmitted to the terminal. Service information provision department to provide to
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. ,
An information processing device characterized by having. An information processing device that can communicate with an intermediary device that can communicate with the device
When the terminal receives the identification information acquired from the outside from the terminal, if the device is not registered in association with any service in the information processing device, the information of the service candidate associated with the device is transmitted to the terminal. Service information provision procedure to be provided to
A registration procedure for associating and registering 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 identification information. ,
An information processing method characterized by executing. For information processing devices that can communicate with intermediary devices that can communicate with devices,
When the terminal receives the identification information acquired from the outside from the terminal, if the device is not registered in association with any service in the information processing device, the information of the service candidate associated with the device is transmitted to the terminal. Service information provision procedure to be provided to
A registration procedure for associating and registering 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 identification information. ,
A program characterized by executing.

Images