JP6145469B2 - Management device, management system, management method, and IC tag manufacturing method - Google Patents

Description

  The present invention relates to a management device, a management system, a management method, and an IC tag manufacturing method.

  Conventionally, an IC tag is attached to an article, and content is displayed on the mobile terminal in response to the mobile terminal reading a URL stored in the IC tag.

  For example, Patent Document 1 discloses a system that distributes content corresponding to a received URL to a mobile terminal in response to the management server of the content distribution company receiving the URL from the mobile terminal. In the conventional system, the tag issuer prepares the IC tag in which the URL of the management server is written in advance, and the content distribution operator registers the URL written in the IC tag in the management server. In the management server, the URL read from the IC tag by the mobile terminal can be associated with the content.

JP 2013-250934 A

  However, in the system described in Patent Document 1, it is necessary for the content distribution company to perform a registration operation for associating the URL stored in the IC tag with the URL indicating the content. For content distributors, the registration work is complicated, and there is a risk that the association between the IC tag, the URL, and the content is mistaken. In addition, when the number of IC tags is large, it takes a long time for registration work, so it may take a long time to start providing services using the IC tags.

  Therefore, the present invention has been made in view of these points, and provides a management device, a management system, a management method, and an IC tag manufacturing method that can efficiently associate a URL of a content with an IC tag. With the goal.

  The management apparatus according to the first aspect of the present invention includes a reception unit that receives a main URL corresponding to one main content and the number of issued IC tags for accessing the main content, and the number of IC tags corresponding to the number of issued items. A generation unit that generates a tag URL that includes information for identifying the IC tag and is stored in the storage unit in association with the main URL and the tag URL. And a receiving unit that receives the tag URL read from the IC tag by the terminal from the terminal, and a redirect unit that redirects the terminal to the main URL associated with the tag URL.

  The accepting unit accepts a sub-URL corresponding to sub-content different from the main content and a condition for accessing the sub-content, and the storage control unit accepts the sub-URL and the condition as the main URL and The terminal is associated with the tag URL and stored in the storage unit, and the redirection unit determines that the condition is satisfied based on a situation when the reception unit receives the tag URL. May be redirected to the sub URL, and if it is determined that the condition is not satisfied, the terminal may be redirected to the main URL.

  The accepting unit accepts, as the condition, a time zone for allowing the terminal to access the sub-content, and the redirect unit includes the time when the receiving unit receives the tag URL included in the condition. The terminal may be redirected to the sub URL when corresponding to a time zone.

  The reception unit receives, as the condition, a language used in a terminal that accesses the sub-content, and the reception unit receives language information indicating a language used in the terminal from the terminal, and the redirect The unit may redirect the terminal to the sub-URL when the language information received by the receiving unit corresponds to the language included in the condition.

  The accepting unit accepts, as the condition, permitted location information indicating a location of the terminal when allowing the terminal to access the sub-content, and the receiving unit receives the location of the terminal from the terminal. Terminal position information is received, and the redirection unit, when the terminal position information received by the reception unit corresponds to the permitted position information included in the condition, May be redirected to the sub-URL corresponding to.

  The accepting unit accepts reference position information indicating a reference position and distance information indicating a distance from the reference position as the permitted position information, and the redirect unit includes the terminal position information received by the receiving unit. When the corresponding position is included in an area within the distance from the reference position, the terminal may be redirected to the sub URL corresponding to the permitted position information.

  The accepting unit accepts the number of touches to the IC tag of the terminal as the condition, and the redirect unit is based on log information indicating a situation when the receiving unit receives the tag URL. If the number of touches to the IC tag of the terminal that has transmitted the tag URL is specified, and the specified number of touches is equal to or greater than the number of touches included in the condition, the terminal may be redirected to the sub URL. Good.

  The management apparatus may further include a log storage control unit that causes the storage unit to store log information indicating a situation when the reception unit receives the tag URL.

  The management device identifies the number of touches for each of the plurality of IC tags based on the log information, and displays the number of touches of the IC tag at each of the positions where the plurality of IC tags are installed. You may further provide the display control part which displays a map on a display part.

  The storage unit further stores the type of the object to which the IC tag corresponding to the tag URL is associated in association with the tag URL, and the management device stores the object based on the log information. You may further provide the total part which totals the number of touches corresponding to each of a some position for every classification.

  The storage control unit stores an advertisement URL corresponding to an advertisement to be displayed on the terminal in association with the tag URL, and the redirect unit stores the advertisement URL in the advertisement URL before redirecting the terminal. Corresponding advertisement content may be displayed on the terminal.

  A management system according to a second aspect of the present invention is a management system including a management device and a terminal, and the management device has a main URL corresponding to one main content and an IC for accessing the main content. A reception unit that receives the number of issued tags, a generation unit that generates information for identifying a tag that is written to each of the IC tags corresponding to the number of issues, and the main tag, A storage control unit that associates the URL with the tag URL and stores the URL in the storage unit, a reception unit that receives the tag URL read from the IC tag by the terminal, and the tag URL. A redirect unit that redirects the terminal to the main URL, and the terminal reads before reading from the IC tag. It has an access unit for accessing the management apparatus based on the tag URL, and a content acquisition unit for acquiring the main content on the basis of the main URL notified from the management device.

  The management method according to the third aspect of the present invention includes a step of receiving a main URL corresponding to one main content and an issuance number of an IC tag for accessing the main content, which is executed by a computer, and the issuance number And generating a tag URL including information for identifying the IC tag written to each of the IC tags, and storing the main URL and the tag URL in association with each other And a step of receiving the tag URL read from the IC tag by the terminal from the terminal and a step of redirecting the terminal to the main URL associated with the tag URL.

  In the IC tag manufacturing method according to the fourth aspect of the present invention, the management device receives a main URL corresponding to one main content and the number of IC tags issued for accessing the main content, and the management device Generating a tag URL including information for identifying the IC tag, which is written to each of the IC tags for the number of issued items, and in the management device, the main URL and the tag Storing the URL for association in the storage unit, and writing the tag URL in each of the IC tags for the number of issued items in the device for generating the IC tag.

  According to the present invention, it is possible to efficiently associate a content URL with an IC tag.

It is a figure which shows the outline | summary of the management system which concerns on 1st Embodiment. It is a figure which shows the structure of the management server which concerns on 1st Embodiment. It is a sequence diagram which shows the flow of a process until the management server which concerns on 1st Embodiment makes an issue request of an IC tag to a tag issuer. It is a figure which shows an example of the reception screen which concerns on 1st Embodiment. It is a figure which shows an example of the information memorize | stored in the redirect information storage part which concerns on 1st Embodiment. It is a sequence diagram which shows the flow of a process after the user terminal which concerns on 1st Embodiment adjoins to an IC tag until a main content is displayed on the said user terminal. FIG. 7 is a sequence diagram following FIG. 6. It is a figure which shows the log information memorize | stored in the log information storage part which concerns on 1st Embodiment. It is a sequence diagram which shows the flow of a process when the management server which concerns on 1st Embodiment displays the information which shows the number of touches on a management terminal. It is a figure which shows an example of the reception screen which receives the conditions for accessing the sub content which concerns on 2nd Embodiment. It is a figure explaining the access conditions regarding the position which concerns on 2nd Embodiment. It is a sequence diagram which shows the flow of a process after the management server which concerns on 2nd Embodiment records log information until a content is displayed on a user terminal. It is a flowchart which shows the flow of the transition destination URL selection process which concerns on 2nd Embodiment. It is a figure which shows the structure of the management server which concerns on 3rd Embodiment.

Hereinafter, embodiments of the present invention will be described.
<First Embodiment>
[Outline of Management System S]
FIG. 1 is a diagram illustrating an overview of a management system S according to the first embodiment. The management system S includes a management server 1 as a management device, a management terminal 2, an IC tag 3, a user terminal 4, and a content server 5.

  In the present embodiment, the IC tag 3 and the user terminal 4 support near field communication such as NFC (Near Field Communication). In response to the fact that the user terminal 4, which is a mobile phone such as a smartphone, has read the URL stored in the IC tag 3 by short-range wireless communication, the management system S sends the content corresponding to the URL to the user terminal 4. It is a system that displays.

  The management server 1 receives a request for issuing the IC tag 3 from the management terminal 2 used by the content provider ((1) in FIG. 1). The management server 1 accepts the number of IC tags 3 issued and one URL (main URL) for accessing the user terminal 4 via the IC tag 3. Here, the access destination indicated by the main URL is the content server 5. In FIG. 1, only one content server 5 is shown. However, the present invention is not limited to this, and a plurality of content servers 5 may be provided.

  When the management server 1 receives the request for issuing the IC tag 3, the management server 1 generates tag URLs to be written in the IC tags 3 corresponding to the number of issued tags ((2) in FIG. 1). The access destination indicated by the tag URL is the management server 1. The tag URL includes information for identifying the IC tag 3.

  The management server 1 associates the main URL received from the management terminal 2 with the generated tag URL and stores it in the storage unit ((3) in FIG. 1), and sends the IC tag 3 to the tag issuer. A request for issuing the tag 3 is made ((4) in FIG. 1). Tag issuers are notified of tag URLs generated by the management server 1 for the number of tag issuances.

The tag issuer issues as many IC tags 3 in which one tag URL is written among the notified tag URLs as many as the number of tag issuances and delivers them to the content provider ((5 in FIG. 1). )).
The content provider places the IC tag 3 by attaching the received IC tag 3 to a desired location ((6) in FIG. 1). The IC tag 3 is disposed at a place where many people gather, such as a store, a transportation facility (train, bus, taxi), a government office, a movie theater, and a theater.

When the user of the user terminal 4 brings the user terminal 4 close to the IC tag 3, the user terminal 4 reads the tag URL from the IC tag 3 ((7) in FIG. 1), and based on the tag URL, the management server 1 is accessed ((8) in FIG. 1).
The management server 1 receives the tag URL from the user terminal 4 when accepting access from the user terminal 4. The management server 1 specifies the main URL stored in the storage unit in association with the tag URL ((9) in FIG. 1), and transmits redirection information instructing redirection to the main URL to the user terminal 4. ((10) in FIG. 1). When receiving the redirect information, the user terminal 4 accesses the content server 5 based on the main URL indicating the redirect destination ((11) in FIG. 1), and acquires the main content corresponding to the main URL from the content server 5 (FIG. 1). 1 (12)).

  By doing in this way, the user terminal 4 can access the main content provided by the content provider by reading the IC tag 3, so that the content provider allows the user to view the provided content. Can do. In addition, the content provider designates the main URL corresponding to the main content and the number of IC tags 3 to be issued, so that the number of IC tags 3 corresponding to the content and budget is arranged in various places. People can watch the content.

By using this management system S, for example, a passenger of a circulation bus simply touches the user terminal 4 on the IC tag 3 affixed in the circulation bus, and nearby tourist attractions, restaurants, stores of special products Various information such as these can be displayed on the user terminal 4. In addition, by attaching the IC tag 3 to the bus stop, the timetable and the bus operation status can be distributed. In addition, by attaching the IC tag 3 on a menu distributed in a restaurant or on a table in the store, it is possible to provide profit information, a coupon, and the like to a user who touches the IC tag 3 with the user terminal 4.
Hereinafter, the configuration and operation of the management server 1 will be described.

[Configuration Example of Management Server 1]
FIG. 2 is a diagram illustrating a configuration of the management server 1 according to the present embodiment.
The management server 1 includes a storage unit 11 and a control unit 12.

  The storage unit 11 includes, for example, a ROM, a RAM, a hard disk, and the like. The storage unit 11 stores various programs for causing the management server 1 to function. The storage unit 11 includes a redirect information storage unit 111 and a log information storage unit 112. Details of the redirect information storage unit 111 and the log information storage unit 112 will be described later.

  The control part 12 is comprised by CPU, for example. The control unit 12 controls functions related to the management server 1 by executing various programs stored in the storage unit 11. The control unit 12 includes a reception unit 121, a generation unit 122, a storage control unit 123, an issue request unit 124, a reception unit 125, a redirect unit 126, a log storage control unit 127, and a display control unit 128. Prepare.

[Processing until tag issuer issues IC tag 3 issue request]
Next, details of various processes executed by the control unit 12 will be described with reference to sequence diagrams.
First, processing until a request for issuing an IC tag 3 is issued to a tag issuer will be described. The reception unit 121, the generation unit 122, the storage control unit 123, and the issue request unit 124 of the management server 1 cooperate to issue a request for issuing the IC tag 3 to the tag issuer.

  FIG. 3 is a sequence diagram showing a flow of processing until the management server 1 according to the first embodiment makes a request for issuing the IC tag 3 to the tag issuer. It is assumed that the management terminal 2 has logged in to the management server 1 in advance.

  First, the reception unit 121 transmits a menu page to the management terminal 2 to display a menu screen (not shown). The accepting unit 121 accepts a request information registration request regarding the IC tag 3 issuance request from the management terminal 2 via the menu screen.

  Upon receiving the request information registration request, the reception unit 121 transmits a registration reception page to the management terminal 2 and causes the management terminal 2 to display a reception screen. Then, the reception unit 121 receives a main URL corresponding to one main content and the number of issued IC tags 3 for accessing the main content via the reception screen.

The management terminal 2 receives the issue request information of the IC tag 3 from the content provider via the reception screen (S1).
FIG. 4 is a diagram illustrating an example of the reception screen 20 according to the first embodiment. In the reception screen 20 shown in FIG. 4, input fields 201 to 206 and a registration button 207 are provided.

The input field 201 accepts input of a distribution name. Here, the distribution name is used to identify information distributed via the IC tag 3.
The input column 202 receives an input of the number of IC tags 3 issued.
The input field 203 accepts selection of the type of the IC tag 3. In the input field 203, one type can be selected from a plurality of predetermined types such as a card type, a print sticker type, and a key chain type.

The input field 204 receives an input of a main URL corresponding to one main content.
The input field 205 receives selection of advertisement content to be displayed on the user terminal 4 before redirecting the user terminal 4 to the main URL. The input to the input field 205 is arbitrary. Here, the content name of the advertising content registered in advance by the content provider is selected, but the URL of the advertising content may be input.

  The input field 206 receives a setting as to whether or not to acquire position information from the user terminal 4 when the user terminal 4 approaches the IC tag 3. The setting contents of the input field 206 may be made effective when content such as an advertisement is specified in the input field 205.

  When the input operation is completed on the reception screen 20 and the registration button 207 is pressed, the management terminal 2 transmits issuance request information including the contents input in the input fields 201 to 206 to the management server 1. The accepting unit 121 accepts an issue request for the IC tag 3 by receiving issue request information.

  The generation unit 122 generates a tag URL including information for identifying the IC tag 3 that is written to each of the number of IC tags 3 issued by the reception unit 121 (S2). Specifically, the generation unit 122 generates unique IDs (tag IDs) for the number of issues included in the issue request information as information for identifying the IC tag 3. The generation unit 122 generates a tag URL by attaching a tag ID as a parameter to a URL destined for the management server 1.

  The storage control unit 123 stores the main URL received by the reception unit 121 and the tag URL generated by the generation unit 122 in the storage unit 11 in association with each other (S3). Specifically, the storage control unit 123 associates the content provider name, the tag URL, the distribution name, the main URL, the advertisement URL corresponding to the advertisement content, and the presence / absence of acquisition of the position information, to redirect information. The data is stored in the storage unit 111.

  FIG. 5 is a diagram illustrating an example of information stored in the redirect information storage unit 111 according to the first embodiment. As shown in FIG. 5, the redirect information storage unit 111 stores a content provider name, a distribution name, a tag URL, and basic distribution information in association with each other. Here, the basic distribution information is information in which the main URL, the advertisement URL, and the presence / absence of position information are associated. In the example shown in FIG. 5, it can be confirmed that a plurality of tag URLs are associated with one main URL.

  The issue request unit 124 notifies the tag issuer that an issue request has been made in response to the reception unit 121 receiving an issue request from the management terminal 2 (S4). For example, the issuance request unit 124 notifies the issuance request by sending a mail including a tag URL for the number of issuances in the message to the tag issuer's terminal.

  Based on the received mail, the tag issuer issues the same number of IC tags 3 in which one tag URL is written. Specifically, the tag issuer inputs the received tag URL to the device that generates the IC tag, and writes the tag URL to each of the issued IC tags. The number of IC tags 3 in which the tag URLs are written is issued by the number of issued.

  The issue request unit 124 may output a file such as Excel (registered trademark) including tag URLs for the number of issues. Then, even if the operator of the management server 1 sends the file to the tag issuer's terminal by e-mail or mails a document printed with the tag URL included in the file to the tag issuer. Good. In this embodiment, the tag issuer inputs the tag URL to the device that generates the IC tag. However, the present invention is not limited to this. For example, a device that generates IC tags receives directly from the management server 1 a mail including tag URLs for the number of issues in the message, and issues IC tags 3 in which one tag URL is written for the number of issues. May be. The IC tag may be attached with a two-dimensional barcode in which a tag URL is embedded. By doing in this way, even if the user terminal 4 does not support short-range wireless communication, the user terminal 4 can read the tag URL if it has a function of reading a two-dimensional barcode. The device that generates the IC tag issues as many IC tags 3 as the number of issued IC tags 3 and attaches a two-dimensional barcode in which the tag URL is embedded to an article such as paper or a seal different from the IC tag 3. May be. In this way, the content provider can use the IC tag 3 with the same tag URL and the article with the two-dimensional barcode separately.

The tag issuer delivers as many IC tags 3 as is issued to the content provider.
When the content provider receives as many IC tags 3 as is issued, the content provider places the IC tags 3 on the place or object desired by the content provider.

[Process of displaying main content on user terminal 4]
Next, a process from when the user terminal 4 comes close to the IC tag 3 until the main content is displayed on the user terminal 4 will be described. The receiving unit 125 and the redirect unit 126 of the management server 1 display the main content on the user terminal 4 by cooperating.

FIG. 6 is a sequence diagram showing a flow of processing from when the user terminal 4 according to the first embodiment approaches the IC tag 3 until main content is displayed on the user terminal 4. FIG. 7 is a sequence diagram following FIG.
First, when the user terminal 4 comes close to the IC tag 3 with an application for reading the IC tag 3 being executed, the user terminal 4 reads the tag URL from the IC tag 3 by short-range wireless communication (S11). The user terminal 4 functions as an access unit, and accesses the management server 1 based on the read tag URL.

When receiving the access from the user terminal 4, the receiving unit 125 of the management server 1 receives the tag URL read from the IC tag 3 by the user terminal 4 from the user terminal 4.
Subsequently, the redirect unit 126 refers to the redirect information storage unit 111 and identifies the main URL associated with the tag URL (S12).

Subsequently, the redirect unit 126 refers to the redirect information storage unit 111 and determines whether or not acquisition of position information is specified (S13). When the redirect unit 126 determines that acquisition of position information is specified, the redirect unit 126 requests the user terminal 4 for position information. If the redirection unit 126 determines that acquisition of position information is not specified, the process proceeds to S15. When a request for position information is made, the user terminal 4 acquires terminal position information indicating its own position using, for example, a GPS (Global Positioning System) function (S14), and transmits the terminal position information to the management server 1 To do. Here, the terminal position information is composed of, for example, latitude information indicating latitude and longitude information indicating longitude. Note that the user terminal 4 may acquire terminal location information at all times and transmit the latest terminal location information to the management server 1 in response to a request for location information.
The receiving unit 125 receives terminal position information indicating its own position from the user terminal 4.

  Subsequently, the log storage control unit 127 causes the log information storage unit 112 of the storage unit 11 to store log information indicating a situation when the reception unit 125 receives the tag URL (S15). Specifically, the log storage control unit 127 associates the tag ID included in the tag URL, the time when the tag URL is received, and the location information received from the user terminal 4 and stores them in the log information storage unit 112. Let FIG. 8 is a diagram illustrating log information stored in the log information storage unit 112. As illustrated in FIG. 8, the log information storage unit 112 stores a tag ID, a reception time, and position information in association with each other. Note that the log storage control unit 127 may store the log information in the log information storage unit 112 when the reception interval of the tag URL from the same user terminal 4 is equal to or longer than a predetermined time. In addition, the log storage control unit 127, when the receiving unit 125 is able to receive information indicating user attributes from the user terminal 4 and model information such as the model name and manufacturer name of the user terminal 4, these information. May be stored in the log information storage unit 112 as log information.

  Subsequently, the redirect unit 126 refers to the redirect information storage unit 111 and determines whether to display the advertisement content before displaying the main content on the user terminal 4 (S21 in FIG. 7). Specifically, the redirect unit 126 determines to display the advertisement content when the advertisement URL is stored in association with the main URL, and when the advertisement URL is not stored in association with the main URL. It is determined that the advertisement content is not displayed.

  When the redirect unit 126 determines to display the advertisement content, the redirect unit 126 transmits the advertisement URL corresponding to the advertisement content and the main URL that is the transition destination URL to the user terminal 4, and before the user terminal 4 is redirected, the advertisement content. Is displayed on the user terminal 4. Specifically, when it is determined that the advertising content is to be displayed, the redirect unit 126 displays the advertising content corresponding to the advertising URL and includes an instruction to redirect to the main URL after a preset time. A redirect page is generated, and the redirect page is transmitted to the user terminal 4. Thereby, based on the advertisement URL included in the redirect page, the user terminal 4 displays the advertisement content on its display unit, then redirects to the main URL and displays the content corresponding to the main URL (S22). .

  If the redirect unit 126 determines not to display the advertising content, the redirect unit 126 transmits only the main URL that is the transition destination URL to the user terminal 4, and the user is added to the main URL associated with the tag URL received by the receiving unit 125. The terminal 4 is redirected. Specifically, when it is determined that the advertising content is not displayed, the redirect unit 126 generates a redirect page that redirects to the main URL, and transmits the redirect page to the user terminal 4.

  The user terminal 4 functions as a content acquisition unit, accesses the content server 5 based on the main URL notified by the redirect page, and acquires the main content corresponding to the main URL from the content server 5. Then, the user terminal 4 displays the received main content on its own display unit (S23).

[Process for displaying the number of times IC tag 3 is touched on user terminal 4]
Next, a process for displaying the number of times the IC tag 3 has been touched on the user terminal 4 (hereinafter referred to as the number of touches) on the management terminal 2 of the content provider will be described. The display control unit 128 of the management server 1 specifies the number of touches of the issued IC tag 3 based on the log information stored in the log information storage unit 112, and sends information indicating the number of touches to the management terminal 2. Display. The number of touches indicates the number of times the user terminal 4 has read the tag URL when the user terminal 4 approaches the IC tag 3.

  FIG. 9 is a sequence diagram illustrating a processing flow when the management server 1 according to the first embodiment displays information indicating the number of touches on the management terminal 2. It is assumed that the management terminal 2 has logged in to the management server 1 in advance.

First, the display control unit 128 receives a display request for the number of touches from the management terminal 2. It is assumed that the display request includes the distribution name specified when the IC tag 3 is issued and the start date and end date of the period for which the number of touches is to be counted.
Subsequently, the display control unit 128 specifies the tag ID based on the tag URL stored in the redirect information storage unit 111 in association with the distribution name included in the display request (S31).

  Subsequently, the display control unit 128 counts the number of touches for each identified tag ID based on the log information stored in the log information storage unit 112 (S32). Specifically, the display control unit 128 targets information whose reception time is after the start date included in the display request and before the end date among the log information stored in the log information storage unit 112. The number of touches for each identified tag ID is totaled.

Subsequently, the display control unit 128 generates a map in which the position of the IC tag 3 and the total number of touches are displayed on the map in association with each other (S33), and transmits the map to the management terminal 2 to manage the map. It is displayed on the display unit of the terminal 2.
When receiving the map, the management terminal 2 displays the map on its own display unit (S34). As a result, the content provider can confirm the number of touches for each IC tag 3 issued, and can also confirm the relationship between the number of touches and the position.

  In the description of the sequence in FIG. 9, the display control unit 128 displays a map displaying the number of IC tag touches on the management terminal 2, but is not limited thereto. For example, the display control unit 128 receives from the management terminal 2 the start date and end date of the period for which the number of touches is to be counted, generates information indicating the result of counting the log information within the period, 2 may be transmitted.

[Effect in the first embodiment]
As described above, the management server 1 according to the present embodiment receives a main URL corresponding to one main content and the number of IC tags 3 issued for accessing the main content, and each of the IC tags 3 corresponding to the number of issued IC tags 3 is received. A tag URL including information for identifying the IC tag 3 written to the tag is generated, and the main URL and the tag URL are associated with each other and stored in the storage unit 11.

  By doing so, the content provider can efficiently associate the main URL with the IC tag 3 by designating the main URL corresponding to one main content and the number of IC tags 3 issued. . Further, since the content provider does not need to perform a registration operation for associating the main URL with the tag URL stored in the IC tag 3 after the IC tag 3 is issued, other contents are mistakenly stored in the IC tag 3. It is possible to prevent association. Further, even when the number of issued IC tags 3 is large, it is possible to prevent a delay in the time taken to provide a service using the IC tag 3.

<Second Embodiment>
[Redirect to sub-content depending on the situation when receiving the tag URL]
Next, the second embodiment will be described. In the first embodiment, the management server 1 associates the tag URL stored in the IC tag 3 with the main URL so that the user terminal 4 reads the tag URL from the IC tag 3. Accordingly, the main contents corresponding to the main URL can be accessed. However, the content provider may want the user terminal 4 to access sub-content different from the main content depending on the situation when the IC tag 3 is read. Therefore, the second embodiment is the first in that the management server 1 redirects the user terminal 4 to the sub URL corresponding to the sub content based on the situation when the tag URL is received from the user terminal 4. Different from the embodiment. Hereinafter, the management system S according to the second embodiment will be described with reference to the drawings. In addition, about the structure similar to 1st Embodiment, the same code | symbol is attached | subjected and detailed description is abbreviate | omitted.

  In the second embodiment, the accepting unit 121 accepts a sub-URL corresponding to a sub-content different from the main content and a condition for accessing the sub-content (hereinafter also referred to as an access condition). Specifically, the reception unit 121 displays a reception screen 21 on the management terminal 2 and receives a sub URL and access conditions from the management terminal 2 via the reception screen 21.

FIG. 10 is a diagram illustrating an example of a reception screen 21 that receives conditions for accessing sub-contents.
On the reception screen 21, a sub URL corresponding to each of a plurality of sub contents and access conditions can be set. Specifically, when the add button 211 shown in FIG. 10 is pressed, an input area corresponding to one sub-content is displayed. In the example shown in FIG. 10, it can be confirmed that the input area 210A and the input area 210B corresponding to each of the two sub contents are displayed.

  As shown in FIG. 10, the receiving screen 21 is provided with an input item 212 corresponding to the sub URL, and the receiving unit 121 receives the input of the sub URL via the input item 212. Here, it is assumed that the address indicated by the sub URL indicates an address on the content server 5 that is different from the main URL.

As shown in FIG. 10, the reception screen 21 is provided with input items 213 to 217 corresponding to access conditions for accessing sub-contents.
The input item 213 is an input item for receiving an access condition related to time. For example, the input item 213 is provided with an input field corresponding to the date, an input field corresponding to the time, and a check box corresponding to the day of the week. You can specify the access time zone. The accepting unit 121 accepts a time period during which the user terminal 4 accesses the sub-content as an access condition via the input item 213.

  The input item 214 is an input item for receiving an access condition related to a language. For example, the input item 214 is provided with check boxes corresponding to a plurality of languages, and the content provider can specify one or more languages as access conditions. The accepting unit 121 accepts a language used in the user terminal 4 for accessing the sub-content as an access condition via the input item 214.

  The input item 215 is an input item for receiving an access condition regarding the number of touches of the user terminal 4, and the receiving unit 121 receives the number of touches to the IC tag 3 of the user terminal 4 as an access condition via the input item 215. Accept. Here, when the number of accesses from the user terminal 4 matches the number of touches input in the input item 215 or exceeds the number of touches input, it is determined that the access condition regarding the number of touches is satisfied.

  The input item 216 is an input item for receiving selection of advertisement content to be displayed before displaying the sub content on the user terminal 4. The accepting unit 121 accepts selection of advertisement content to be displayed before displaying the sub content via the input item 216.

  The input item 217 is an item for receiving permission position information indicating the position of the user terminal 4 when allowing the user terminal 4 to access the sub-content. For example, the IC tag 3 may be attached not only to a fixed position but also to a moving body such as a car or a train. In this case, the content provider may want to provide different sub-contents to the user terminal 4 according to each passing position of the mobile object.

  Correspondingly, the input item 217 is provided with an input field for receiving input of reference position information indicating the reference position and an input field for receiving input of distance information indicating the distance from the reference position. The accepting unit 121 accepts permitted position information including reference position information and distance information as an access condition via the input item 217.

The delete button 218 is a button for deleting a sub URL and access conditions set for one sub content.
When the input operation is completed on the reception screen 21 and the registration button 219 is pressed, the management terminal 2 transmits setting information including the contents input in the input area illustrated in FIG. 10 to the management server 1. When the management server 1 receives the setting information, the storage control unit 123 stores the sub URL and the access condition included in the setting information in the redirect information storage unit 111 in association with the main URL and the tag URL. Here, in the reception screen 21, when a sub URL and access conditions are input corresponding to each of a plurality of sub contents, a plurality of sub URLs and access conditions are stored in association with one main URL. Is done.

  When the redirecting unit 126 determines that the access condition corresponding to the sub URL is satisfied based on the situation when the receiving unit 125 receives the tag URL, the redirecting unit 126 redirects the user terminal 4 to the sub URL and accesses the sub URL. If it is determined that the condition is not satisfied, the user terminal 4 is redirected to the main URL.

  Specifically, the redirecting unit 126 redirects the user terminal 4 to the sub URL when the time when the receiving unit 125 receives the tag URL from the user terminal 4 corresponds to the time zone included in the access condition. Let The content corresponding to the sub URL in this case is, for example, advertising content including time sale information. Using this access condition is suitable for a store that wants to attract customers at a specific time.

  Also, the redirect unit 126 redirects the user terminal 4 to the sub URL when the language information received by the receiving unit 125 from the user terminal 4 corresponds to the language included in the access condition. The content corresponding to the sub URL in this case is, for example, content created in a language included in the access condition. Use of this access condition is suitable for providing tourist guide information to a user in a sightseeing spot.

  Further, the redirect unit 126 identifies the number of touches to the IC tag 3 of the terminal that transmitted the tag URL based on the log information stored in the log information storage unit 112, and the identified number of touches is used as the access condition. When the number of touches is greater than or equal to the number included, the user terminal 4 is redirected to the sub URL. When a different sub URL is assigned for each touch count, the redirect unit 126 may redirect the user terminal 4 to the sub URL corresponding to the specified touch count. The content corresponding to the sub URL in this case is, for example, content that changes every time it is touched. Using this access condition is suitable when the content provider wants to provide various information to the user step by step.

  The redirect unit 126 redirects the user terminal 4 to the sub URL corresponding to the permitted position information when the terminal position information received by the receiving unit 125 corresponds to the permitted position information included in the access condition. . Specifically, when the position corresponding to the terminal position information received by the receiving unit 125 is included in an area within the distance indicated by the distance information from the reference position indicated by the reference position information, the redirect unit 126 includes: The user terminal 4 is redirected to the sub URL corresponding to the permitted position information. The content corresponding to the sub URL in this case is, for example, content including a commentary on an article installed near the position where the user of the user terminal 4 is located. Use of this access condition is suitable when the IC tag 3 is attached to a sightseeing bus.

  For example, as shown in FIG. 11, the reference position BP1 (X3, Y3) and the distance 500 m from the reference position are set as the permitted position information of the first sub-content, and the second sub-content Assume that the reference position BP2 (X4, Y4) and the distance 700 m from the reference position are set as the permitted position information. It is assumed that no other access conditions are set.

  Assume that the user terminal 4 reads the tag URL from the IC tag 3 when the vehicle C to which the IC tag 3 is attached is located at the position P1. In this case, the redirect unit 126 determines that the user terminal 4 is located in the area corresponding to the first sub-content, and redirects the user terminal 4 to the sub-URL corresponding to the first sub-content. Let

  On the other hand, it is assumed that the user terminal 4 reads the tag URL from the IC tag 3 when the vehicle C to which the IC tag 3 is attached is located at the position P2. In this case, the redirect unit 126 determines that the user terminal 4 is located in the area corresponding to the second sub-content, and redirects the user terminal 4 to the sub-URL corresponding to the second sub-content. Let By doing so, for example, when a tourist on a sightseeing bus with an IC tag 3 sees an interesting building or landscape, the IC tag attached to the window of the sightseeing bus By touching the user terminal 4 to 3, the user terminal 4 can display a commentary on the building or landscape that has been seen.

[Redirect processing according to access conditions]
Next, a process from when the user terminal 4 in the second embodiment approaches the IC tag 3 until the sub content is displayed on the user terminal 4 will be described.

  The basic flow of processing of the management server 1 from when the user terminal 4 reads the tag URL from the IC tag 3 until the management server 1 records the log information is the first implementation shown in FIG. It is the same as the processing in the form. However, the second embodiment is different in that the reception unit 125 receives language information indicating the language used in the user terminal 4 from the user terminal 4 when accepting access from the user terminal 4. Hereinafter, a process after recording the log information (that is, a process after S15 in FIG. 6) will be described.

FIG. 12 is a sequence diagram showing a flow of processing from when the management server 1 according to the second embodiment records log information until content corresponding to the access condition is displayed on the user terminal 4.
First, the redirect unit 126 executes a transition destination URL selection process for selecting a transition destination URL to be redirected according to an access condition (S20), and selects a transition destination URL to be accessed by the user terminal 4.

  In the transition destination URL selection process, the redirect unit 126 determines that there is a sub URL that satisfies all access conditions corresponding to time, language, number of touches, and position from a plurality of sub URLs stored in association with the main URL. The sub URL is selected, and when the sub URL does not exist, the main URL is selected. Accordingly, when the redirecting unit 126 determines that there is a sub URL that satisfies the access condition based on the situation when the receiving unit 125 receives the tag URL, the redirect unit 126 corresponds the user terminal 4 to the access condition. If it is redirected to a sub URL and it is determined that there is no sub URL satisfying the access condition, the user terminal 4 is redirected to the main URL. Details of the transition destination URL selection processing will be described later.

  Subsequently, the redirect unit 126 refers to the redirect information storage unit 111 and determines whether or not to display the advertisement content before displaying the content corresponding to the transition destination URL on the user terminal 4 (S21).

  When the redirect unit 126 determines to display the advertisement content, the redirect unit 126 transmits the advertisement URL corresponding to the advertisement content and the transition destination URL to the user terminal 4. Thereby, the user terminal 4 displays advertisement content on its own display unit based on the advertisement URL (S22).

If the redirect unit 126 determines not to display the advertisement content, the redirect unit 126 transmits only the transition destination URL to the user terminal 4.
The user terminal 4 accesses the content server 5 based on the transition destination URL received from the management server 1 and receives the content corresponding to the transition URL from the content server 5. Then, the user terminal 4 displays the received content on its own display unit (S23).

[Flowchart of transition destination URL selection processing]
Next, details of the transition destination URL selection process will be described. FIG. 13 is a flowchart showing the flow of a transition destination URL selection process according to the second embodiment.

  First, the redirect unit 126 identifies a sub URL that uses the language indicated by the language information received from the user terminal 4 as an access condition from a plurality of sub URLs associated with the main URL (S201).

  Subsequently, the redirect unit 126 determines whether or not the sub URL specified in S201 exists (S202). If the corresponding sub URL exists, the redirect unit 126 moves the process to S204. If the corresponding sub URL does not exist, the redirect unit 126 moves the process to S203 and selects a sub URL for which an access condition related to language setting is not set.

  Subsequently, the redirect unit 126 specifies the current date and day of the week (S204), and the sub URL specified in S201 or the sub URL selected in S203 has the current date and day of the week as an access condition. The URL is specified (S205).

  Subsequently, the redirect unit 126 refers to the log information storage unit 112 and specifies the number of touches to the IC tag 3 of the user terminal 4 (S206). The redirect unit 126 identifies a sub URL that permits access to the identified number of touches among the sub URLs identified in S205 (S207).

  Subsequently, the redirecting unit 126 identifies a sub URL that permits access at the position indicated by the terminal position information among the sub URLs identified in S207 (S208). Specifically, when the position indicated by the terminal position information is included in the circular area within the distance received as the access condition from the reference position received as the access condition, the redirect unit 126 sets the access condition as the access condition. The corresponding sub URL is identified as a sub URL that permits access at the position indicated by the terminal position information.

  Subsequently, the redirect unit 126 determines whether or not the sub URL specified in S208 exists (S209). The redirect unit 126 selects the sub URL as the transition destination URL when the corresponding sub URL exists (S210), and selects the main URL as the transition destination URL when the corresponding sub URL does not exist. (S211). If there are a plurality of corresponding sub URLs, the redirect unit 126 may select one sub URL selected at random from these sub URLs as the transition destination URL.

[Effects of Second Embodiment]
As described above, when the management server 1 according to the second embodiment receives a sub URL corresponding to a sub content different from the main content and an access condition for accessing the sub content, and receives a tag URL. If it is determined that the access condition is satisfied based on the situation, the user terminal 4 is redirected to the sub URL, and if it is determined that the access condition is not satisfied, the user terminal 4 is redirected to the main URL.
By doing in this way, the content provider can make the said user terminal 4 access a subcontent according to the condition when the user terminal 4 reads the IC tag 3. FIG.

<Third Embodiment>
[Total number of touches for each type of object with IC tag 3 attached]
Subsequently, a third embodiment will be described. As described in the second embodiment, the IC tag 3 may be attached to a moving body such as a vehicle. In this case, the content provider may want to manage the number of touches on the IC tag 3 depending on the type of vehicle. The third embodiment is different from the first embodiment in that the number of touches is totaled for each type of object to which the IC tag 3 is attached.

FIG. 14 is a diagram illustrating a configuration of the management server 1 according to the third embodiment. In the third embodiment, the control unit 12 of the management server 1 further includes a counting unit 129.
In the third embodiment, the redirect information storage unit 111 stores the type of the object to which the IC tag 3 corresponding to the tag URL is attached in association with the tag URL. Specifically, when the content provider attaches the IC tag 3 to an object, the storage control unit 123 receives a tag URL and type information indicating the type of the object from the management terminal 2. The type of the object is, for example, a bus type (route bus or sightseeing bus) or a bus or train grade type (normal vehicle, luxury vehicle, etc.). Then, the storage control unit 123 causes the redirect information storage unit 111 to store the tag URL and the type information in association with each other.

  The totaling unit 129 counts the number of touches for each object type based on the log information. Specifically, the counting unit 129 receives a display request for the number of touches from the management terminal 2. It is assumed that the display request includes the distribution name specified when the IC tag 3 is issued.

  The totaling unit 129 specifies the tag ID based on the tag URL stored in the redirect information storage unit 111 in association with the distribution name included in the display request, and the type associated with the tag ID. Identify information.

  Subsequently, the totaling unit 129 counts the number of touches for each identified tag ID based on the log information stored in the log information storage unit 112. Then, the totaling unit 129 counts the number of touches for each tag ID for each type information corresponding to the tag ID.

  Note that the totaling unit 129 may total the number of touches corresponding to each of a plurality of positions for each type of object. In this case, based on the log information stored in the log information storage unit 112, the number of touches for each identified tag ID is totaled for each position. Then, the counting unit 129 further counts the tag ID and the number of touches for each position based on the type information corresponding to the tag ID.

  Subsequently, the display control unit 128 causes the display unit of the management terminal 2 to display the tabulated results. Thereby, the content provider can confirm the number of touches of the IC tag 3 corresponding to each type of object, and can also confirm the relevance between the number of touches and the position.

[Effect in the third embodiment]
As described above, since the management server 1 according to the third embodiment totals the number of touches for each object type, the content provider can select the number of touches corresponding to each of the object types to which the IC tag 3 is attached. Can be confirmed. Moreover, since the management server 1 totals the number of touches corresponding to each of a plurality of positions for each type of object, the management server 1 can confirm at which position the number of touches is large for each type of object. Thereby, the content provider can estimate the attribute of the user of the user terminal 4, and can consider a new service based on the estimated attribute.

  As mentioned above, although this invention was demonstrated using embodiment, the technical scope of this invention is not limited to the range as described in the said embodiment. It will be apparent to those skilled in the art that various modifications or improvements can be added to the above embodiment. In particular, the specific embodiments of the distribution / integration of the devices are not limited to those illustrated above, and all or a part thereof may be added in arbitrary units according to various additions or according to functional loads. It can be configured functionally or physically distributed and integrated.

DESCRIPTION OF SYMBOLS 1 ... Management server, 11 ... Storage part, 111 ... Redirect information storage part, 112 ... Log information storage part, 12 ... Control part, 121 ... Reception part, 122 ... Generation unit, 123... Storage control unit, 124... Issuance request unit, 125... Reception unit, 126 .. redirect unit, 127... Log storage control unit, 128. 129 ... Totaling unit, 2 ... Management terminal, 3 ... IC tag, 4 ... User terminal, 5 ... Content server, S ... Support system

Claims (14)

A management device that associates a content URL with an IC tag,
A reception unit that receives a main URL corresponding to one main content and the number of IC tags issued to access the main content;
Written for each of the IC tag of the issuing minutes, looking contains the information for identifying the IC tag as a parameter, and a generating unit that generates a tag URL to the management device and the destination,
A storage control unit for storing the main URL and the tag URL in a storage unit in association with each other;
A receiving unit for receiving the tag URL read from the IC tag by the terminal from the terminal;
A redirect unit that redirects the terminal to the main URL associated with the tag URL;
A management device comprising: The accepting unit accepts a sub URL corresponding to a sub content different from the main content and a condition for accessing the sub content,
The storage control unit stores the sub URL and the condition in the storage unit in association with the main URL and the tag URL,
When the redirection unit determines that the condition is satisfied based on a situation when the reception unit receives the tag URL, the redirection unit redirects the terminal to the sub URL, and the condition is satisfied. If not, the terminal is redirected to the main URL.
The management apparatus according to claim 1. The accepting unit accepts a time period for allowing the terminal to access the sub-content as the condition,
The redirect unit redirects the terminal to the sub URL when the time when the receiving unit receives the tag URL corresponds to the time zone included in the condition.
The management device according to claim 2. The accepting unit accepts a language used in a terminal for accessing the sub-content as the condition,
The receiving unit receives language information indicating a language used in the terminal from the terminal;
The redirection unit redirects the terminal to the sub URL when the language information received by the reception unit corresponds to the language included in the condition.
The management device according to claim 2 or 3. The accepting unit accepts permitted position information indicating the position of the terminal when allowing the terminal to access the sub-content as the condition,
The receiving unit receives terminal position information indicating a position of the terminal from the terminal;
The redirect unit redirects the terminal to the sub URL corresponding to the permitted position information when the terminal position information received by the receiving unit corresponds to the permitted position information included in the condition. Let
The management apparatus of any one of Claim 2 to 4. The reception unit receives, as the permitted position information, reference position information indicating a reference position and distance information indicating a distance from the reference position,
The redirection unit, when a position corresponding to the terminal position information received by the reception unit is included in an area within the distance from the reference position, the redirection unit, the terminal corresponding to the permitted position information Redirect to a sub URL,
The management device according to claim 5. The accepting unit accepts the number of touches to the IC tag of the terminal as the condition,
The redirect unit identifies and identifies the number of touches to the IC tag of the terminal that has transmitted the tag URL based on log information indicating a situation when the reception unit receives the tag URL. When the number of touches is equal to or greater than the number of touches included in the condition, the terminal is redirected to the sub URL.
The management apparatus according to any one of claims 2 to 6. A log storage control unit that stores log information indicating a situation when the reception unit receives the tag URL in the storage unit;
The management apparatus of any one of Claim 1 to 7. Based on the log information, the number of touches for each of the plurality of IC tags is specified, and a map displaying the number of touches of the IC tags at each of the positions where the plurality of IC tags are installed is displayed on the display unit. A display control unit for displaying
The management device according to claim 7 or 8. The storage unit further stores the type of the object to which the IC tag corresponding to the tag URL is associated in association with the tag URL;
Based on the log information, for each type of the object, further comprises a totaling unit that totalizes the number of touches corresponding to each of a plurality of positions,
The management apparatus according to any one of claims 7 to 9. The storage control unit stores an advertisement URL corresponding to an advertisement to be displayed on the terminal in the storage unit in association with the tag URL,
The redirect unit displays advertisement content corresponding to the advertisement URL on the terminal before redirecting the terminal.
The management apparatus according to any one of claims 1 to 10. A management system comprising a management device and a terminal,
The management device
A reception unit that receives a main URL corresponding to one main content and the number of IC tags issued to access the main content;
Written for each of the IC tag of the issuing minutes, looking contains the information for identifying the IC tag as a parameter, and a generating unit that generates a tag URL to the management device and the destination,
A storage control unit for storing the main URL and the tag URL in a storage unit in association with each other;
A receiving unit for receiving the tag URL read from the IC tag by the terminal from the terminal;
A redirect unit that redirects the terminal to the main URL associated with the tag URL;
The terminal
An access unit for accessing the management device based on the tag URL read from the IC tag;
A content acquisition unit that acquires the main content based on the main URL notified from the management device;
Management system. Executed by the computer,
Receiving a main URL corresponding to one main content and the number of IC tags issued for accessing the main content;
A step of said written for each of the IC tag issue several minutes, looking contains the information for identifying the IC tag as a parameter, it generates a tag URL to the computer and the destination,
Storing the main URL and the tag URL in association with each other in a storage unit;
Receiving the tag URL read from the IC tag by the terminal from the terminal;
Redirecting the terminal to the main URL associated with the tag URL;
A management method comprising: In the management device, receiving a main URL corresponding to one main content and the number of IC tags issued for accessing the main content;
In the management apparatus, the step of the written for each of the IC tag issue several minutes, looking contains the information for identifying the IC tag as a parameter, it generates a tag URL to the management device and the destination When,
In the management device, associating the main URL with the tag URL and storing them in a storage unit;
In the device for generating an IC tag, writing the tag URL to each of the issued number of the IC tags;
An IC tag manufacturing method comprising:

Images