JP4900415B2 - Service providing system, terminal device, server, scenario server, service providing method and program - Google Patents

Description

  The present invention relates to a service providing system, a terminal device, a server, a scenario server, a service providing method, and a program, and in particular, a service providing system and a terminal for providing a service using a print medium or an electronic medium distributed to a user. The present invention relates to an apparatus, a server, a scenario server, a service providing method, and a program.

  I-CODE SLI (ISO15693), Tag-It HF-I (ISO15693), FeliCa (ISO18092 compliant), MIFARE Ultralight, MIFARE Standard, MIFARE Desfire, whose types of wireless ID tags (hereinafter referred to as “RFID”) are 13.56 MHz. Or 2.45 GHz μ Chip, Intellitag (ISO 18000-4), 952 to 955 MHz EPC global Class 1 Gen 2 (ISO 18000-6 Type C) and μ Chip Hibiki (ISO 18000-6 Type C based) The tag can be read and written by one reader.

  Also, mobile phone terminals, small store terminals, etc. have been proposed that have an RFID reader function and a non-contact IC card communication function in addition to a barcode (including two-dimensional barcode) reading function. .

  As described above, various media ranging from two-dimensional barcodes to RFIDs and non-contact IC cards and reader / writers for reading them are provided. For example, membership cards for identifying customers and products attached to products Customer relationship management is performed using tag information such as RFID.

  Although different from the RFID reader, Patent Document 1 is cited as a related technique. Patent Document 1 expands to a plurality of access control processes necessary for executing an access request for a non-contact IC card received from an information processing means, and selects and accesses an access control process program corresponding to the access control process. A contactless communication system that configures and executes procedures is disclosed.

JP 2006-31604 A

  However, in the system that reads data from the plurality of media described above and transmits the data to the server and provides the service to the customer, each time data is read from one medium, a method of transmitting to the server side is adopted. There is a problem that the response deteriorates as the number of media increases. For example, if data is read from a plurality of media at a cash register terminal of a retail store and transmitted to the server, the waiting time of subsequent customers is increased.

  In addition, there is a method of reading a plurality of data and then sending them to the server in a batch. However, in this method, the combination of service items and data items such as personal ID and product ID are fixed. Therefore, there is a problem that it cannot cope with diversified services. In addition, in this system, there is a problem that it is necessary to newly install a dedicated reader or terminal device capable of reading these data items in each store in order to provide one service.

  The present invention has been made in view of the above-described circumstances, and the object of the present invention is to provide a service that can flexibly cope with diversified services without preparing the dedicated system or reader. To provide a system.

  According to the first aspect of the present invention, for each service, a scenario for setting a data item for requesting a user to perform a read operation based on scenario data (setting data) describing a combination of data items to be transmitted to the server side When the setting unit and the user are requested to read the set data item from an arbitrary medium, and the reading of the set data item is completed, the ID and data of the scenario data for the server There is provided a terminal device including a reading completion determination unit that starts transmission of an item.

  According to the second aspect of the present invention, based on the scenario data ID (scenario ID) received from the terminal device described above, a service server that determines the service requested by the terminal device and provides the determined service On the other hand, a server is provided that transfers data items received from the terminal device and returns a response from the service server to the terminal device.

  According to the 3rd viewpoint of this invention, the service provision system containing an above-described terminal device and an above-described server is provided.

  According to the 4th viewpoint of this invention, the scenario server provided with the function which transmits scenario data with respect to an above-described terminal device is provided.

  According to a fifth aspect of the present invention, for each service, a step for setting a data item for requesting a user to perform a read operation based on scenario data describing a combination of data items to be transmitted to the server side; On the other hand, when the reading operation of the set data item from an arbitrary medium is requested and the reading of the set data item is completed, the data items are collected together with the scenario data ID to the server. Transmitting, and based on the scenario data ID, the service requested by the terminal device is determined, and the data item received from the terminal device is transferred to the service server that provides the determined service. Returning a response from the service server to the terminal device. Test method is provided.

  According to the sixth aspect of the present invention, for each service, a process for setting a data item for requesting a user to perform a read operation based on scenario data describing a combination of data items to be transmitted to the server side; On the other hand, when the reading operation of the set data item from an arbitrary medium is requested and the reading of the set data item is completed, the data items are collected together with the scenario data ID to the server. A program for causing a computer having data reading means to execute the transmission process is provided.

  According to the seventh aspect of the present invention, based on the scenario data ID received from the terminal device described above, the service requested by the terminal device is determined, and the service server that provides the determined service, There is provided a program for causing a computer that has received data from the terminal device to execute processing for transferring a data item received from the terminal device and processing for returning a response from the service server to the terminal device. Note that these programs can be recorded on a computer-readable storage medium.

  According to the present invention, it is possible to flexibly cope with diversified services without preparing a dedicated system or reader. The reason is that a configuration is adopted in which the input of data items necessary for providing the service is received and transferred to the server using the scenario data, and the data items received by the server are transferred to an appropriate service server.

It is a figure for demonstrating the outline | summary of this invention. It is a figure showing the structure of the 1st Embodiment of this invention. It is a figure for demonstrating the scenario data used in the 1st Embodiment of this invention. It is a figure for demonstrating the mechanism of discrimination | determination of the data classification of the terminal device of the 1st Embodiment of this invention. It is a figure for demonstrating the data hold | maintained at the data storage part of the terminal device of the 1st Embodiment of this invention. It is an example of the map table hold | maintained at the server of the 1st Embodiment of this invention. It is a sequence diagram showing operation | movement of the terminal device of the 1st Embodiment of this invention. It is a sequence diagram showing operation | movement by the side of the server of the 1st Embodiment of this invention. It is a figure for demonstrating the mechanism of discrimination | determination of the data classification of the terminal device of the 2nd Embodiment of this invention.

  Next, the outline of the present invention will be described in detail with reference to the drawings. FIG. 1 is a diagram for explaining the outline of the present invention. Referring to FIG. 1, a configuration in which a terminal device 1, a server 2, and service servers 4a and 4b are connected via a network 100 is shown.

  The scenario setting unit 16 of the terminal device 1 sets, for each service, a data item that requests a user to perform a reading operation based on scenario data that describes a combination of data items to be transmitted.

  For example, the service server 4a provides a present lottery reception service as a campaign for a product purchase user, and the member ID stored in the RFID 9 built in the member card 32 is provided to provide the present lottery reception service. It is assumed that product serial information stored in the RFID attached to the product 33a is necessary.

  The scenario setting unit 16 of the terminal device 1 receives the member ID stored in the RFID 9 built in the member card 32 and the product serial information stored in the RFID attached to the product 33a via the reader unit 6. The scenario data determined to be requested by the user is read from the RFID 9 built in the scenario card 31, and these are set as data items for requesting the user to perform a reading operation.

  The reading completion determination unit 14 of the terminal device 1 requests the user to read the data item set as described above, and when the reading of the set data item is completed, a transmission / reception unit (not shown) To the server 2 together with an ID (scenario ID) for specifying the scenario data read from the scenario card 31.

  The map table 23 of the server 2 stores a correspondence relationship with the URL (Uniform Resource Locator) of the service server 4a corresponding to the scenario data. The dispatch unit 21 of the server 2 that has received the scenario ID, the member ID, and the product serial information as described above reads the URL corresponding to the scenario ID received from the map table 23, and sends the member ID to the service server 4a. The product serial information is transmitted, and the response from the service server 4a is returned to the terminal device 1.

  Thereafter, a case is considered in which the service server 4b is used to provide a present lottery reception service as a campaign for another product purchase user. In order to provide the present lottery reception service, the member ID stored in the RFID 9 built in the member card 32 and the product serial information that can be read from the two-dimensional barcode 10 printed on the product 33b are used. And

  The scenario setting unit 16 of the terminal device 1 can read from the member ID stored in the RFID 9 built in the member card 32 and the two-dimensional barcode 10 printed on the product 33b via the reader unit 6. Another scenario data that is required to request the serial information from the user is read from an RFID built in another scenario card, and these are set as data items for requesting the user to perform a reading operation.

  Similarly, the terminal device 1 requests the user to read the data item set as described above, and transmits the data item to the server 2 together with the other scenario ID.

  The dispatch unit 21 of the server 2 that has received the scenario ID, the member ID, and the product serial information as described above reads the URL corresponding to the other scenario ID received from the map table 23, and sends it to the service server 4b. The member ID and product serial information are transmitted, and the response from the service server 4b is returned to the terminal device 1.

  As described above, according to the present invention, distribution of scenario data makes it possible to flexibly cope with addition or change of services or change of data items that require input from the user.

  The service provided by the present invention is not particularly limited as long as it uses a medium readable by the terminal device. For example, provision of further detailed information for information read from the medium, user authentication using the information read from the medium, and services derived therefrom (permission for use of server resources, granting of privileges, acceptance of various applications, etc.) It is done.

[First Embodiment]
Next, a first embodiment of the present invention will be described in detail with reference to the drawings. FIG. 2 is a diagram showing the configuration of the first exemplary embodiment of the present invention. Referring to FIG. 2, a terminal device 1, a server 2, service sites 41 to 46, and a network 100 such as the Internet connecting them are shown.

  Hereinafter, in this embodiment, a user who operates the terminal device 1 records a scenario card 31 in which an RFID 9 in which a scenario ID is recorded, a member card 32 in which an RFID 9 in which a member ID is recorded, and a product ID are recorded. It is assumed that the product 33a to which the RFID 9 is attached can be held over the reader unit 6. The scenario card 31 does not need to be held by the user. For example, a plurality of scenario cards are prepared in a store where the terminal device 1 is installed, and the necessary scenario card is provided from the store. It may be in the form of receiving.

  Specifically, the service sites 41 to 46 include a maintenance site 41, a store introduction site 42, a campaign site 43, a store visit point site 44, a product introduction site 45, and a member site 46. Each of the service sites 41 to 46 is realized by a service server that provides a unique URL and provides a service in response to a request from a client.

  In the present embodiment, the maintenance site 41 is a site that provides a function of performing user authentication with a member ID and maintaining a dedicated page of the user.

  In addition, the store introduction site 42 is a site that provides detailed information of a store where the terminal device 1 is installed.

  Further, the campaign site 43 is a site that accumulates a member ID and a product ID in association with each other as marketing information indicating which member has purchased what kind of product, and gives points to the member. It shall be.

  In addition, the store visit point site 44 is a site that specifies a member by a member ID and gives points to members who have visited the store.

  In addition, the product introduction site 45 introduces information on the origin of raw materials related to the product specified by the product ID, introduces producers, introduces distribution routes, introduces nutritional components, and provides support information including product manuals and correction programs. It is assumed that the site provides information to customers such as information that can be offered or purchased as a set, and information on other products that fit well with the product.

  In addition, the member site 46 is a site for confirming the points that the member has accumulated and accepting registration / change of the delivery address of the product.

  The terminal device 1 is a computer to which a reader unit 6 such as an RFID reader can be connected. The terminal device 1 includes a scenario management unit 18, a display unit 11, a primary reading unit 12, a data storage unit 13, a reading completion determination unit 14, a secondary reading unit 15, a scenario setting unit 16, and a transmission / reception unit. 17.

  The display unit 11 is configured by a liquid crystal display device or the like for displaying various messages to the user.

  The primary reading unit 12 and the secondary reading unit 15 control the connected reader unit 6 to read data recorded on the scenario card 31, the membership card 32, and the RFID 9 built in or attached to the product 33, and set the scenario To the unit 16 side.

  The data storage unit 13 includes a memory or auxiliary storage device that uses data read from the RFID 9 as a temporary storage destination.

  The reading completion determination unit 14 refers to the data storage unit 13 and determines whether reading of the data item set by the scenario setting unit 16 has been completed. When it is determined that the reading of the data item set by the scenario setting unit 16 is completed, the reading completion determination unit 14 instructs the transmission / reception unit 17 to transmit the data stored in the data storage unit 13. When the reading of the data item set by the scenario setting unit 16 is not completed, the reading completion determination unit 14 displays a message on the display unit 11 that prompts the user to read the data item that has not been read. .

  The scenario setting unit 16 determines the data type input via the reader unit 6 and the primary reading unit 12 or the secondary reading unit 15 and stores it in the data storage unit 13. Further, when the input data is a scenario ID, the scenario setting unit 16 stores the scenario ID in the data storage unit 13 and corresponds to the scenario ID from the scenario data stored in the scenario management unit 18. The scenario data is read, and data items requested from the user are set in the data storage unit 13. In the scenario setting unit 16. A method for determining the input data type will be described in detail later.

  The transmission / reception unit 17 is configured by, for example, a browser that transmits data stored in the data storage unit 13 to the server 2 and receives a response from the server 2.

  The scenario management unit 18 stores scenario data distributed regularly or irregularly from the server 2. Further, the scenario management unit 18 can be configured by a recording medium that can be connected to the terminal device 1 and portable. In this case, the scenario data can be updated or rewritten by replacing the recording medium on which the scenario data is recorded.

  Note that the above-described reading completion determination unit 14 and scenario setting unit 16 can be realized by a program that causes a computer that configures the terminal device 1 to execute the above-described processing in addition to the configuration by hardware.

  The server 2 includes a dispatch unit 21, a scenario management unit 22, and a map table 23.

  The dispatch unit 21 refers to the map table 23, and based on the scenario ID included in the data transmitted from the transmission / reception unit 17 of the terminal device 1 or a combination of other data items, the transmission / reception unit of the terminal device 1 The service site to which the data transmitted from 17 is to be transmitted is determined. Then, the dispatch unit 21 transmits the data received from the transmission / reception unit 17 of the terminal device 1 to the determined service site, and returns the response returned from the service site to the terminal device 1.

  The scenario management unit 22 stores scenario data distributed to the terminal device 1. Further, the scenario management unit 22 may provide a scenario data management function such as new addition or change of scenario data to the operator on the server 2 side. Details of the scenario data will be described later.

  The map table 23 is a table in which URLs of service sites that are connection destinations are mapped by scenario IDs or combinations of other data items. Details of the map table 23 will be described later.

[Scenario data]
Here, scenario data stored in the scenario management unit 18 of the terminal device 1 or the scenario management unit 22 of the server 2 will be described. FIG. 3 is a diagram showing scenario data stored in the scenario management units 18 and 22 in a table format. For example, scenario data with a scenario ID “0000” indicates scenario data for receiving a service from the maintenance site 41. In the scenario data with the scenario ID “0000”, it is defined that the member ID is “◯” (necessary) and the product ID is “x” (unnecessary). This indicates that a member ID is required to receive a service from the maintenance site 41, and a product ID is not required.

  In the example of FIG. 3, only the member ID and the necessity of the product ID are defined, but other necessary data items can be added as appropriate.

[Determination of data type (data item)]
Next, the mechanism for determining the data type (data item) in this embodiment will be described. FIG. 4 shows data to be referred to when determining the data type (data item) input by the scenario setting unit 16 in a table format. For example, the scenario ID has a numerical value range 135 of 0000-0020, and if the input data is in the range of 0000-0020, the scenario setting unit 16 determines that the scenario ID is the scenario ID, and the corresponding data storage unit 13 Save to area. Similarly, if the input data is in the range of 1000-1999, the scenario setting unit 16 determines that the member ID has been input and stores it in the corresponding area of the data storage unit 13. Thus, by determining the numerical range 135 of the data type (data item) to be input, the determination of the data type in the scenario setting unit 16 is simplified.

  FIG. 5 shows the contents set in the data storage unit 13 using the scenario data of scenario ID “0003” in FIG. 3 and the data in FIG. According to the scenario data of scenario ID “0003” in FIG. 3, it is defined that the member ID is “◯” (necessary) and the product ID is “x” (unnecessary). In the storage area (necessity) 133, the member ID is set to “◯” (necessary) and the product ID is set to “x” (unnecessary). In the message storage area 132 of the data storage unit 13, a message used when requesting a read operation of each data type is set with reference to the data in FIG. The actual data storage area 134 is used as a primary storage destination of the value of the input data type (data item).

  Further, the reading completion determination unit 14 inserts the message in the message storage area of the data storage unit into the standard sentence “Please hold over” and displays, for example, “Your membership card” on the display unit 11. Please hold it over ".

[Map Table]
Next, the map table 23 in the present embodiment will be described. FIG. 6 is an example of a map table held in the server 2. The map table of FIG. 6 corresponds to the scenario data stored in the general scenario management units 18 and 22, and the scenario ID of 0000 to 0004 is included in the data received from the terminal device 1. Defines the URL of the service site to which the data is to be transmitted. In the map table in FIG. 5, the URL of the service site when the scenario ID is not included in the data received from the terminal device 1 is also defined. Thereby, for example, a user who has transmitted only the member ID can access the member site, and a user who has transmitted only the product ID can access the product introduction site.

  Next, the operation of this embodiment will be described in detail with reference to the drawings. First, the operation of the terminal device 1 will be described. FIG. 7 is a sequence diagram showing the operation of the terminal device 1 of the present embodiment. Referring to FIG. 7, first, when a process start request operation is performed by the user of the terminal device 1, the scenario setting unit 16 initializes data in the data storage unit 13 (step. For example, as shown in FIG. When the setting contents and the actual data are left, the scenario setting unit 16 deletes the actual data and initializes the necessity determination storage area (necessity) 133 to an unnecessary state (×). In the example of FIG. 7, this initialization processing is executed by the scenario setting unit 16, but may be executed by the primary reading unit 12 or the like.

  Next, when the user brings a card or the like in which the RFID 9 is built close to the reader unit 6, the primary reading unit 12 reads data from the card or the like held by the user and outputs it to the scenario setting unit 16 (step A02).

  The scenario setting unit 16 determines the input data type (data item) (step A03). Here, when the scenario ID is input, the scenario setting unit 16 stores the scenario ID in the actual data storage area 134 of the scenario ID of the data storage unit 13 and the scenario with the corresponding scenario ID from the scenario management unit 18. Data is read and the necessity determination storage area (necessity) 133 of the data storage unit 13 is set (step A04).

  On the other hand, when the member ID or product ID is input, the scenario setting unit 16 stores the member ID or product ID in the actual data storage area 134 of the member ID or product ID of the data storage unit 13 (step A05).

  Next, the reading completion determination unit 14 determines whether all numerical values have been read in the actual data storage area 134 of items having “◯” in the necessity determination storage area (necessity) 133 of the data storage unit 13. It is determined whether or not the necessary data type (data item) has been read (step A06). The reading completion determination unit 14 similarly determines that reading has been completed when an operation for transmitting data to the server 2 is performed by a user or the like who does not have the scenario card 31.

  Here, when it is determined that the necessary data type (data item) has been read, the read completion determination unit 14 instructs the transmission / reception unit 17 to collectively transmit the data stored in the data storage unit 13 (Step S1). A07).

  On the other hand, when a data type (data item) that has not been read is found, the read completion determination unit 14 determines the character string in the message storage area 132 of the data type (data item) that has not been read by the data storage unit 13. "Please pass over" is added to the message to create a message requesting the read operation of the insufficient data type (data item) and output it to the display unit 11 (step A08).

  For example, if the member ID is set to be necessary but has not yet been read, the reading completion determination unit 14 reads the “customer ID” read from the member ID message storage area 132 of the data storage unit 13. "Member card" is combined with "Hold your card" to generate a request message "Hold your customer card".

  The display unit 11 displays a message indicating the data type (data item) which is output from the reading completion determination unit 14 and which is insufficient (Step A09).

  When the user who has viewed the message brings a card or the like on which the lacking data type (data item) is recorded close to the reader unit 6, the secondary reading unit 15 reads data from the card or the like held by the user, and the scenario It outputs to the setting part 16 (step A10).

  In this way, when reading of the necessary data type (data item) is completed, the transmission / reception unit 17 transmits the data stored in the data storage unit 13 to the server 2 (step A11).

  Next, the operation on the server 2 side after the data transmission will be described with reference to FIG. When the transmission / reception unit 17 of the terminal device 1 transmits data to the server 2 (step A11), the dispatch unit 21 of the server 2 refers to the scenario management unit 22, and the data type received from the transmission / reception unit 17 is the data type according to the scenario data. It is confirmed whether or not (data item) is correctly entered (step B01). If it is found that the necessary data type (data item) is not entered, the dispatch unit 21 returns an error screen to the transmission / reception unit 17 of the terminal device 1 (step B06). As a result, the user of the terminal device 1 performs the reading operation again.

  On the other hand, when the received data includes a necessary data type (data item), the dispatch unit 21 compares the received data with the map table 23 and determines the URL of the transfer destination site to which the data is transferred. Extract (step B02). For example, when the map table 23 as shown in FIG. 6 is set, the scenario ID is “0000”, the URL to the maintenance site 41, and the scenario ID “0001” is the URL to the store introduction site 42. Thus, the URL corresponding to the scenario ID is extracted. If there is no scenario ID value, and there is either a member ID or a product ID, the URL to the member site 46 or the product introduction site is extracted as shown in FIG.

  Next, the dispatch unit 21 includes the data received from the terminal device 1 as a parameter of the extracted URL and transmits it to any of the service sites 41 to 46 (step B03).

The service site that has received the data among the service sites 41 to 46 executes processing unique to each service site using the member ID and product ID included in the received data (step B04), and the processing result is obtained. The screen data shown is returned (step B05)
.

  For example, the maintenance site 41 performs user authentication processing to determine whether or not the user is a maintenance administrator based on the member ID read by the terminal device 1 transferred via the server 2. If the user authentication is successful, the maintenance screen is displayed. Return to the terminal device 1.

  Further, for example, since the store introduction site 42 does not particularly require a member ID or product ID, the store information site returns a privilege information display screen to the visiting user for the store where the terminal device 1 is installed.

  Further, for example, the campaign site 43 returns a point balance confirmation screen including the points awarded this time after performing the point granting process according to the purchase price of the user using the member ID and the product ID. Similarly, the store visit point site 44 uses the member ID to perform point grant processing according to the purchase amount of the user, and then returns a point balance confirmation screen including the points granted this time.

  In addition, for example, the product introduction site 45 can provide information on the origin of raw materials related to the product specified by the product ID, the introduction of the producer, the introduction of the distribution route, the introduction of the nutritional component, or information that can be purchased as a set. Or display a display screen for other products that match the product.

  Further, for example, the member site 46 returns a screen for confirming the member's point balance specified by the member ID and a display / display screen for registering / changing the delivery address of the product.

  The dispatch unit 21 returns the received screen data to the transmission / reception unit 17 of the terminal device 1 (step B06).

  With reference to FIG. 7 again, the operation of the terminal device 1 after returning the data will be described. When the transmission / reception unit 17 outputs the screen data received from the server 2 to the display unit 11 (step A12), the display unit 11 displays the screen data received from the server 2 (step A13).

  As described above, in the present embodiment, scenario data corresponding to a plurality of service sites is created in advance, and based on the scenario data selected by the user, the user is prompted to perform a necessary data reading operation. It can be transferred to an appropriate service site and processed appropriately.

[Second Embodiment]
Next, a second embodiment in which the method of determining the scenario data and the data type (data item) in the scenario setting unit according to the first embodiment of the present invention has been changed will be described in detail with reference to the drawings.

  The second embodiment of the present invention can be realized with the same configuration as that of the first embodiment described above, and has almost the same operation. Therefore, the difference will be mainly described below.

  In this embodiment, a scenario card (31 in FIG. 1) containing a scenario ID is equipped with an ISO 18000-4 RFID, and a member card (32 in FIG. 1) is ISO 18092. It is assumed that an RFID is mounted, and the product ID is recorded in an EPC Global Class 2 RFID.

  FIG. 9 shows, in a table format, data referred to when the scenario setting unit 16 of the terminal device 1 according to the second embodiment of the present invention determines the input data type (data item). The difference from FIG. 4 used in the description of the method for determining the data type (data item) in the first embodiment is that the protocol used for each data type (data item) is defined instead of the numerical value range. It is a point.

  In the example of FIG. 9, the data type (data item) of the input data can be determined by the RFID type in which the scenario ID, member ID, and product ID are recorded.

  The scenario setting unit 16 refers to the data as shown in FIG. 9 and determines the data type of the input data depending on the type of protocol used in the reader unit 6 obtained via the primary reading unit 12 or the secondary reading unit 15. (Data item) is determined and stored in the corresponding area of the data storage unit 13.

  As described above, in this embodiment, there is no need to limit the numerical ranges of the scenario ID, member ID, and product ID as in the first embodiment. For this reason, it is possible to use the entire writable range of each type of RFID, and it is possible to deal with a large number of products and members.

  Although the embodiments of the present invention have been described above, the present invention is not limited to the above-described embodiments, and further modifications, substitutions, and adjustments may be made without departing from the basic technical idea of the present invention. Can be added.

  For example, in the above-described embodiment, two items of the member ID and the product ID are read in addition to the scenario ID. However, a data type (data item) required by the service site (service server) is appropriately added. It is possible.

  Further, for example, in the first embodiment described above, an example in which a numeric value range is set for each data type (data item) on the assumption that the effective digit of RFID is four digits has been described. Of course, it is not limited to the above example. For example, the data type (data item) may be determined based on the difference in whether the read data is an RFID or a two-dimensional barcode, the data format, or the like.

  For example, in the above-described embodiment, the server 2 has been described as including the scenario management unit 22, but it is also possible to provide a scenario server that includes the scenario management unit 22 and distributes scenario data to the terminal device 1. Each terminal device may be provided with an automatic update function for scenario data received from the server 2 or such a scenario server and stored in the scenario management unit.

  For example, in the above-described embodiment, the terminal device 1 includes the scenario management unit 18 and reads the scenario ID from the scenario card. However, the scenario device reads the scenario data from the scenario card and develops the scenario data on the terminal device 1. It is also possible.

  Further, for example, in the above-described embodiment, the scenario ID, the member ID, and the product ID are all read from the RFID, but it is not always necessary to use the RFID.

  Further, for example, in the above-described embodiment, the terminal device 1 has been described as including the two reading units of the primary reading unit 12 and the secondary reading unit 15, but it is also possible to realize these with a single reading unit. is there.

DESCRIPTION OF SYMBOLS 1 Terminal device 2 Server 4a, 4b Service server 6 Reader part 9 RFID
DESCRIPTION OF SYMBOLS 10 Two-dimensional barcode 11 Display part 12 Primary reading part 13 Data storage part 14 Reading completion judgment part 15 Secondary reading part 16 Scenario setting part 17 Transmission / reception part 18 Scenario management part 21 Dispatch part 22 Scenario management part 23 Map table 31 Scenario card 32 Member card 33, 33a, 33b Product 41 Service site (maintenance site)
42 Service site (Store introduction site)
43 Service site (campaign site)
44 Service Site (Visiting Point Site)
45 Service site (product introduction site)
46 Service site (member site)
100 Network 131 Data type (data item)
132 Message storage area 133 Necessity determination storage area (necessity)
134 Actual data storage area 135 Numerical range

Claims (14)

For each service, based on scenario data describing a combination of data items to be transmitted to the server side, a scenario setting unit that sets a data item that requests a read operation from the user;
When the user is requested to read the set data item from an arbitrary medium, and the reading of the set data item is completed, the scenario data ID and the data item are transmitted to the server. A terminal device including a reading completion determination unit to start;
Based on the scenario data ID (scenario ID) received from the terminal device, the service requested by the terminal device is determined, and the data item received from the terminal device to the service server that provides the determined service. And a server that returns a response from the service server to the terminal device. In the scenario data, a numerical range that each data item can take is set,
The service providing system according to claim 1, wherein the reading completion determination unit determines whether reading of the set data item is completed based on whether the read data value is within a preset numerical range. In the scenario data, a protocol or data format for acquiring each data item is set,
2. The service providing system according to claim 1, wherein the reading completion determination unit determines whether reading of the set data item is completed according to a protocol or a data format. The terminal device further includes a scenario management unit that stores a plurality of scenario data,
The scenario setting unit
The service providing system according to any one of claims 1 to 3, wherein a data item for requesting the user to perform a read operation is set based on scenario data corresponding to a scenario ID input by the user.   The service providing system according to claim 4, wherein the terminal device has a function of receiving the scenario data from the server or a predetermined scenario server and updating the scenario data stored in the scenario management unit.   6. The service providing system according to claim 4 or 5, wherein a plurality of types of terminal devices are created for each service, read the card medium on which the scenario data or the scenario ID is recorded, and inputs the scenario data or the scenario ID. The terminal device, the Rukoto reading the RFID obtained by recording the scenario data and the scenario ID, receives an input of a scenario ID from the user, according to claim 4 or 5 of the service providing system to enter the scenario data or the scenario ID .   The server determines a service requested by the terminal device based on a combination of data items received from the terminal device instead of the scenario data ID (scenario ID) received from the terminal device. 8. The service providing system according to claim 1, wherein a data item received from the terminal device is transferred to a service server that provides a service, and a response from the service server is returned to the terminal device. For each service, based on scenario data describing a combination of data items to be transmitted to the server side, a scenario setting unit that sets a data item that requests a read operation from the user;
When the user is requested to read the set data item from an arbitrary medium, and the reading of the set data item is completed, the scenario data ID and the data item are transmitted to the server. And a read completion determination unit for starting the communication.   A data item received from the terminal device for a service server that determines the service requested by the terminal device based on the scenario data ID received from the terminal device according to claim 9 and provides the determined service. A server that transfers the response from the service server to the terminal device.   A scenario server having a function of transmitting scenario data to the terminal device of the service providing system according to claim 5. For each service, based on scenario data describing a combination of data items to be transmitted to the server side, setting a data item for requesting a read operation from the user;
When the user is requested to read the set data item from an arbitrary medium and the reading of the set data item is completed, the data item is sent to the server together with the scenario data ID. Sending in bulk,
Based on the scenario data ID, the service requested by the terminal device is determined, and the data item received from the terminal device is transferred to the service server that provides the determined service. Returning a response to the terminal device. A service providing method comprising: For each service, based on scenario data describing a combination of data items to be transmitted to the server side, a process for setting a data item for requesting the user to perform a read operation;
When the user is requested to read the set data item from an arbitrary medium and the reading of the set data item is completed, the data item is sent to the server together with the scenario data ID. A program that causes a computer equipped with a data reading means to execute a process of transmitting data collectively. Based on the scenario data ID received from the terminal device of claim 9 , the service requested by the terminal device is determined, and the data item received from the terminal device is provided to the service server providing the determined service. Process to transfer,
The program which makes the computer which received data from the terminal device of Claim 9 perform the process which returns the response from the said service server to the said terminal device.

Images