CN113450164A - Information providing apparatus, storage medium, and information providing method - Google Patents

Information providing apparatus, storage medium, and information providing method Download PDF

Info

Publication number
CN113450164A
CN113450164A CN202110187390.8A CN202110187390A CN113450164A CN 113450164 A CN113450164 A CN 113450164A CN 202110187390 A CN202110187390 A CN 202110187390A CN 113450164 A CN113450164 A CN 113450164A
Authority
CN
China
Prior art keywords
data
history
information providing
identifier
transaction
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110187390.8A
Other languages
Chinese (zh)
Inventor
安田隆博
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Toshiba TEC Corp
Original Assignee
Toshiba TEC Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Toshiba TEC Corp filed Critical Toshiba TEC Corp
Publication of CN113450164A publication Critical patent/CN113450164A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems
    • G06Q20/209—Specified transaction journal output feature, e.g. printed receipt or voice output
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/04—Billing or invoicing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/33—Querying
    • G06F16/3331—Query processing
    • G06F16/334—Query execution
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/38—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • G06F16/381—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using identifiers, e.g. barcodes, RFIDs
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K7/00—Methods or arrangements for sensing record carriers, e.g. for reading patterns
    • G06K7/10—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation
    • G06K7/10544—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation by scanning of the records by radiation in the optical part of the electromagnetic spectrum
    • G06K7/10821—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation by scanning of the records by radiation in the optical part of the electromagnetic spectrum further details of bar or optical code scanning devices
    • G06K7/1095—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation by scanning of the records by radiation in the optical part of the electromagnetic spectrum further details of bar or optical code scanning devices the scanner comprising adaptations for scanning a record carrier that is displayed on a display-screen or the like
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K7/00—Methods or arrangements for sensing record carriers, e.g. for reading patterns
    • G06K7/10—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation
    • G06K7/14—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation using light without selection of wavelength, e.g. sensing reflected white light
    • G06K7/1404—Methods for optical code recognition
    • G06K7/1439—Methods for optical code recognition including a method step for retrieval of the optical code
    • G06K7/1447—Methods for optical code recognition including a method step for retrieval of the optical code extracting optical codes from image or text carrying said optical code
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/047—Payment circuits using payment protocols involving electronic receipts

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Electromagnetism (AREA)
  • Finance (AREA)
  • Toxicology (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Artificial Intelligence (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Development Economics (AREA)
  • General Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Computational Linguistics (AREA)
  • Library & Information Science (AREA)
  • Cash Registers Or Receiving Machines (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

An information providing apparatus, a storage medium, and an information providing method are provided, which can reduce the trouble of confirming a transaction history to a customer. The collecting unit collects electronic ticket data including an identifier of a commodity as a transaction target for which a transaction is completed, from the plurality of data management devices. The acquisition unit acquires the identifier. The generation unit generates history data indicating a transaction history of the commodity identified by the identifier acquired by the acquisition unit, based on the electronic ticket data collected by the collection unit. The output unit outputs the history data generated by the generation unit.

Description

Information providing apparatus, storage medium, and information providing method
The present application claims priority from japanese application having a filing date of 03-24/2020 and a filing number of JP2020-053270, and the contents of the above application are cited, the disclosures of which are incorporated herein by reference in their entirety.
Technical Field
Embodiments of the present invention relate to an information providing apparatus, a storage medium, and an information providing method.
Background
Conventionally, an electronic ticket service has been realized that enables arbitrary viewing of electronic ticket data obtained by electronizing tickets relating to transactions such as sales of commodities. Such an electronic ticket service is provided by a plurality of service providers, respectively. Further, which electronic ticket service is applied is generally determined by the situation of the seller or the like, and cannot be selected by the customer.
For example, the electronic ticket service a is applied to a transaction with a seller X of the franchised electronic ticket service a, and the electronic ticket service B is applied to a transaction with a seller Y of the franchised electronic ticket service B. In this case, customers who utilize both of the seller X and the seller Y must utilize both of the electronic ticket service a and the electronic ticket service B. Further, when the customer purchases the purchased product again for both the seller X and the seller Y, if the customer wants to confirm the past transaction history, the customer needs to confirm the transaction histories in the electronic ticket service a and the electronic ticket service B, respectively. Therefore, in order to confirm the transaction history, the trouble of the customer increases.
Under such circumstances, a technique capable of reducing the trouble of confirming the transaction history to the customer is desired.
Disclosure of Invention
In view of the above-described problems, an object of the present invention is to provide an information providing apparatus, a storage medium, and an information providing method, which can reduce the trouble of confirming a transaction history to a customer.
In order to solve the above problem, an embodiment of the present invention provides an information providing apparatus having a collection unit, an acquisition unit, a generation unit, and an output unit. The collecting unit collects electronic ticket data including an identifier of a commodity as a transaction target for which a transaction is completed, from the plurality of data management devices. The acquisition unit acquires the identifier. The generation unit generates history data indicating a transaction history of the commodity identified by the identifier acquired by the acquisition unit, based on the electronic ticket data collected by the collection unit. The output unit outputs the history data generated by the generation unit.
According to the information providing apparatus described above, it is possible to provide an information providing apparatus that can reduce the trouble of confirming the transaction history to the customer.
In the above-described information providing apparatus, the collecting unit may repeat collection of the electronic ticket data that has not been collected yet, and the information providing apparatus may further include: a storage device that stores a database indicating transaction histories related to the commodities that are objects of transactions completed in execution, respectively; and an updating unit that updates the database based on the electronic ticket data newly collected by the collecting unit, wherein the generating unit generates the history data based on the database.
According to the information providing apparatus described above, the data amount of the transaction data collected for one update can be reduced.
The information providing apparatus further includes: and a determination unit configured to determine a store to be subjected to history confirmation when the identifier acquired by the acquisition unit belongs to a unique identifier usable for identifying each product in a plurality of stores, wherein the generation unit generates the history data as a transaction history indicating the store determined by the determination unit when the identifier acquired by the acquisition unit belongs to the unique identifier.
According to the information providing device, it is possible to prevent the transaction history of various products from being mixed in the case of the special identifier.
The information providing apparatus further includes: a display device in which the output section displays a screen based on the history data.
According to the above information providing apparatus, the transaction history can be confirmed easily by the display device.
The information providing apparatus further includes: a display device in which the output section displays a screen based on the history data.
According to the above information providing apparatus, the transaction history can be confirmed easily by the display device.
The information providing apparatus further includes: and a service processing unit for executing a service of the data management apparatus.
According to the information providing apparatus described above, the service provided by the service provider can be used.
In the above-described information providing apparatus, the service processing unit may include an operation unit that instructs execution of the acquisition unit.
According to the information providing device described above, the commodity transaction history across the data management device can be acquired while using the provided service.
In the above-described information providing apparatus, the plurality of service processing units are provided to the plurality of data management apparatuses, and the services different from the plurality of data management apparatuses are executed.
According to the information providing apparatus described above, it is possible to easily confirm the transaction history across the service providers while using the services of the identified service providers.
A storage medium according to another aspect of the present invention stores an information processing program that causes a computer provided in an information processing device to function as: a collecting unit that collects electronic ticket data including an identifier of a commodity as a transaction target that has been completed, from a plurality of data management devices; an acquisition unit that acquires the identifier; a generation unit configured to generate history data indicating a transaction history of the product identified by the identifier acquired by the acquisition unit, based on the electronic ticket data collected by the collection unit; and an output unit that outputs the history data generated by the generation unit.
According to the above-described storage medium, a function capable of reducing the trouble of the customer in the transaction history confirmation can be provided to the computer.
An information providing method of another aspect of the present invention includes the steps of: collecting electronic bill data including an identifier of a commodity as a transaction target for which execution is completed from a plurality of data management devices; obtaining the identifier; generating history data representing a transaction history of the commodity identified by the acquired identifier based on the collected electronic ticket data; and outputting the generated history data.
According to the information providing method, the information providing method can reduce the trouble of confirming the transaction history to the customer.
Drawings
Fig. 1 is a block diagram showing a circuit configuration of a main part of an information providing apparatus in one embodiment.
Fig. 2 is a diagram schematically showing the structure of a data record contained in the management database in fig. 1.
Fig. 3 is a diagram schematically showing the structure of a data record contained in the history database in fig. 1.
Fig. 4 is a flow chart of the ticket client process.
Fig. 5 is a flow chart of the ticket client process.
Fig. 6 is a diagram showing an example of the designation screen.
Fig. 7 is a diagram showing an example of the purchase history screen.
Description of the reference numerals
10 … information providing device, 11 … processor, 12 … main memory, 13 … auxiliary memory unit, 14 … touch panel, 15 … camera, 16 … communication interface, 17 … transmission channel, 20 … bill server, 30 … communication network, 40 … POS system.
Detailed Description
Hereinafter, an example of an information providing apparatus according to an embodiment will be described with reference to the drawings.
Fig. 1 is a block diagram showing a circuit configuration of a main part of an information providing apparatus 10 in the present embodiment. The information providing apparatus 10 provides a transaction history of a specified product based on electronic ticket data collected from a plurality of ticket servers 20 via a communication network 30.
The ticket server 20 acquires transaction data indicating transaction contents managed in the POS system 40 via the communication network 30, and accumulates electronic ticket data based on the transaction data. The electronic bill data represents a commodity code, a number of commodities, a unit price, and the like for each transaction for each commodity to be traded. The product code is an identifier assigned to a product to identify the product. The plurality of ticket servers 20 are each operated by another service provider. The plurality of ticket servers 20 respectively provide other electronic ticket services. Note that the ticket server 20 may collect and accumulate electronic ticket data generated by the POS system 40. As described above, the ticket server 20 is an example of a data management device that manages electronic ticket data including an identifier of a product to be transacted.
The communication network 30 may be used alone or in appropriate combination with the internet, VPN (virtual private network), LAN (local area network), public communication network, mobile communication network, and the like. Note that, for example, the mobile communication network and the internet are used for communication between the information providing apparatus 10 and the ticket server 20, and for example, the internet or VPN is used for communication between the ticket server 20 and the POS system 40.
The POS system 40 performs processing for registration of transaction contents such as sales of commodities in stores, accounting, and the like. When a customer to be transacted is a user of the electronic ticket service, the POS system 40 transmits transaction data indicating the transaction content to the ticket server 20. The POS systems 40 process transactions in different stores. Further, the POS system 40 causes the ticket server 20 corresponding to the electronic ticket service affiliated with the store to acquire transaction data.
As hardware of the information providing apparatus 10, a portable information processing apparatus such as a smartphone, a mobile phone, a tablet terminal, or the like is typically used. The information providing apparatus 10 has a processor 11, a main memory 12, an auxiliary storage unit 13, a touch panel 14, a camera 15, a communication interface 16, a transmission channel 17, and the like. The processor 11, the main memory 12, the auxiliary storage unit 13, the touch panel 14, the camera 15, and the communication interface 16 are connected via a transmission channel 17.
In the information providing apparatus 10, the processor 11, the main memory 12, and the auxiliary storage unit 13 are connected by the transmission channel 17, thereby constituting a computer that performs information processing for realizing various functions as the information providing apparatus 10.
The processor 11 corresponds to a core portion of the above-described computer. The processor 11 controls each part for realizing various functions as the information providing apparatus 10 in accordance with information processing programs such as an operating system, middleware, and application programs.
The main memory 12 corresponds to a main memory portion of the above-described computer. The main memory 12 includes a nonvolatile memory area and a volatile memory area. The main memory 12 stores an information processing program in a nonvolatile memory area. The main memory 12 may store data necessary for the processor 11 to execute processing for controlling each unit in a nonvolatile or volatile memory area. The main memory 12 uses a volatile memory area as a work area to which the processor 11 appropriately rewrites data.
The auxiliary storage unit 13 corresponds to an auxiliary storage section of the computer. The auxiliary memory unit 13 is, for example, an EEPROM (electrically erasable programmable read-only memory). An HDD (hard disk drive), an SSD (solid state drive), or the like can also be used as the auxiliary storage unit 13. The auxiliary storage unit 13 holds data used by the processor 11 to perform various processes or data generated by processes in the processor 11. The auxiliary storage unit 13 stores an information processing program.
One of the information processing programs stored in the auxiliary storage unit 13 is an application program (hereinafter, referred to as a ticket client application program) APA for operating as a ticket client. However, typically, the ticket client application APA is downloaded and written into the secondary storage unit 13 via, for example, the internet in accordance with an operation performed by the user of the information providing apparatus 10. That is, in a state where the ticket client application APA is not stored in the auxiliary storage unit 13, the information providing apparatus 10 is assigned to the user of the information providing apparatus 10. However, the information providing apparatus 10 may be assigned to the user of the information providing apparatus 10 in a state where the ticket client application APA is stored in the auxiliary storage unit 13.
The touch panel 14 functions as an input device and a display device of the information providing apparatus 10.
The camera 15 captures an arbitrary object, and generates image data representing an image including the object. As the camera 15, a known image pickup apparatus using a CMOS (complementary metal oxide semiconductor) image sensor or the like can be used.
The communication interface 16 is an interface for data communication via the communication network 30. As the communication interface 16, for example, a known communication device for performing data communication via a mobile communication network can be used.
The transmission channel 17 includes an address bus, a data bus, a control signal line, and the like, and transmits data and control signals transmitted and received between the connected units.
A part of the storage area of the secondary storage unit 13 is used as the management database DBA and the history database DBB. The management database DBA is a database for managing electronic ticket services utilized by the users of the information providing apparatuses 10. The history database DBB is a database indicating the transaction history of the product purchased by the user of the information providing apparatus 10. That is, the auxiliary storage unit 13 is an example of a storage device that stores a database indicating transaction history.
Fig. 2 is a diagram schematically showing the structure of a data record DRA contained in a management database DBA.
The management database DBA is a collection of data records DRA respectively associated with a plurality of electronic ticket services respectively provided by a plurality of ticket servers 20. The data record DRA contains fields FAA, FAB, FAC, FAD, FAE. A service identifier for identifying the associated electronic ticket service is set in the field FAA. A user identifier for identifying the user in the associated electronic ticket service is set in the field FAB. The password set for the user in the associated electronic ticket service is set in the field FAC. The field FAD has address data set therein, which address data is used for accessing the ticket server 20 corresponding to the associated electronic ticket service. The address data is, for example, a URL (uniform resource locator). The latest date and time of downloading of electronic ticket data corresponding to the associated electronic ticket service is set in the field FAE.
Fig. 3 is a diagram schematically showing the structure of the data record DRB contained in the history database DBB.
The history database DBB is a collection of data records DRB associated with the respective commodities. The data record DRB comprises fields FBA, FBB. The data record DRB sometimes contains one or more fields following the field FBC. A product code for identifying the associated product is set in the field FBA. Typically, the commodity code is a JAN (Japanese commodity number) code or an in-store (in-store) code. The detailed data is set in the field FBB. The detailed data is associated with a transaction that targets the associated product, and indicates details related to the transaction. The in-store code is a product code that can be used to identify each product in a plurality of stores, and is an example of a special identifier.
In the present embodiment, the detailed data includes fields FCA, FCB, FCC, and FCD. A store identifier for identifying a store that performs the associated transaction is set in the field FCA. Data representing the date and time at which the associated transaction was made is set in field FCB. A value representing the number of transactions in the associated transaction is set in the field FCC. A value representing the unit price applied in the associated transaction is set in field FCD.
Next, the operation of the information providing apparatus 10 configured as described above will be described. The following description of the process is an example, and various processes that can achieve the same result can be appropriately used.
The user installs a ticket client application APA in an information processing apparatus such as a smartphone owned by the user, for example, and enables the information processing apparatus to function as the information providing apparatus 10. Further, the user registers the user for a service that the user desires to use among the electronic ticket services provided by the plurality of ticket servers 20, respectively. If the user utilizes a plurality of electronic bill services, the user registration is respectively carried out on the corresponding plurality of electronic bill services. By this user registration, a user identifier for identifying the user is set in the ticket server 20, and the user identifier is associated with the password. At least one of the user identifier and the password may be designated by the user, or both may be set by the ticket server 20 or the service provider.
As the usage setting of the information providing apparatus 10, the user registers the electronic ticket service used and the user identifier and password in the electronic ticket service. In accordance with the operation for this registration, the processor 11 appends a new data record DRA to the management database DBA. The processor 11 sets the service identifier of the electronic ticket service specified by the user to be utilized for the field FAA of the new data record DRA. Thereby, the new data record DRA is associated with the electronic ticket service specified by the user. The processor 11 sets a user identifier and a password, respectively, specified by the user to the fields FAB, FAC of the new data record DRA. The processor 11 sets the address of the ticket server 20 corresponding to the associated electronic ticket service to the field FAD of the new data record DRA. The processor 11 sets preset invalid data, which is data not indicating the actual date and time, to the field FAE of the new data record DRA. The processor 11 may also set the field FAE to null beforehand.
If the user uses a plurality of electronic bill services, the plurality of electronic bill services are registered respectively. Therefore, in this case, the management database DBA contains a plurality of data records DRA respectively associated with the plurality of electronic ticket services.
When the user finishes a transaction in a store affiliated with the use of the registered electronic ticket service, transaction data is transmitted from the POS system 40 provided in the store to the ticket server 20 corresponding to the electronic ticket service. The ticket server 20 stores electronic ticket data based on the transaction data transmitted in this way in association with a user identifier of the user. That is, the electronic ticket data includes a store identifier of a store that performs a transaction and a transaction date and time in association with the transaction. In addition, the electronic ticket data includes, for example, a product code, the number of products, and a unit price as the product to be traded. Further, when a user repeatedly makes a transaction in a shop affiliated with an electronic ticket service, a plurality of pieces of electronic ticket data are stored in association with the user identifier of the user in the ticket server 20 corresponding to the electronic ticket service.
In general, in an electronic ticket service, a user accesses a ticket server 20 from an arbitrary information terminal, and a ticket screen indicating details of each transaction is displayed on the information terminal, so that the user can view the ticket screen.
In this way, in the information providing apparatus 10, if the processor 11 is instructed to execute an application based on the ticket client application APA, information processing based on the ticket client application APA (hereinafter, referred to as ticket client processing) is started.
Fig. 4 and 5 are flow diagrams of the ticket client process.
In order to utilize the electronic ticket service of the ticket server 20, a dedicated application program of the ticket server 20 is installed in the information providing apparatus 10. The information providing apparatus 10 can also execute information processing (hereinafter, referred to as service processing) by the dedicated application (a service processing unit that executes a service of the data management apparatus). The service process provides different services to the respective service providers that provide the ticket server 20. For example, a point service, a coupon service, a discount service, etc. are provided at the same time as the electronic ticket is provided. The information providing apparatus 10 is capable of processing ticket client processing and service processing in parallel. In general, when a user views a product back and forth in a store, the user uses a dedicated application of the ticket server 20, and the ticket server 20 provides an electronic ticket service for operating the store. Accordingly, the service provided by the ticket server 20 can be used. On the other hand, when a history inquiry described later is made, the ticket client application APA is started. It is assumed that the operation of starting both the ticket client application APA and the dedicated application is cumbersome. Thus, the ticket client application APA may also act as a history query pattern specific application. Further, the historical query mode of the ticket client application program APA is linked with the dedicated application program. The technique of linking applications is realized by using a known technique. Specifically, in conjunction with the operation of installing the ticket client application APA, a button for calling the ticket client application APA (application dedicated to the history inquiry mode) is added to the dedicated application (the service processing unit includes an operation unit for instructing the acquisition unit for acquiring the identifier to perform an operation). This button operation causes a designation screen (ACT 6 described later) to be displayed. Further, the later-described management database is periodically updated (the ACTs 4 and 5 are executed, for example, once a day). Accordingly, the transaction history of the transaction between the seller X and the seller Y can be outputted while using the dedicated application program of the seller X providing the electronic ticket service a.
In the present embodiment, a case where the ticket client application APA is installed and the ticket client application APA is separately started is described as an example.
As the ACT1 in fig. 4, the processor 11 causes the touch panel 14 to display a home screen, for example. The home screen is a screen for starting operations of various functions provided by the ticket client process.
As the ACT2, the processor 11 confirms whether the history inquiry mode is designated. If the specification cannot be confirmed, the processor 11 determines no and proceeds to ACT 3.
As the ACT3, the processor 11 confirms whether or not other operations are performed. Further, if no valid operation is performed, the processor 11 determines "no" and returns to the ACT 2.
Thus, as ACT2 and ACT3, processor 11 waits for some active operations to be performed, including specifying a historical query pattern. Further, when some operation other than the operation for specifying the history inquiry mode is performed, the processor 11 proceeds to a process for executing a function corresponding to the operation. The processing of the processor 11 in this case is not a feature of the present embodiment, and therefore, the description thereof is omitted. The process for displaying the ticket screen showing the details of each transaction as described above may be one of the processes in this case.
When the user desires to confirm the transaction history of a certain product, for example, while looking at the product back and forth in the store, for example, a preset operation is performed on the touch panel 14 to activate the history inquiry mode. The operation is, for example, clicking of a soft key disposed on the home screen.
If the processor 11 confirms the above operation, the determination is yes in ACT2, and the process proceeds to ACT 4.
As the ACT4, the processor 11 downloads the electronic ticket data not downloaded for one of the electronic ticket services registered with the information providing apparatus 10. The processor 11 for example selects one of the data records DRA contained in the management database DBA. Further, processor 11 requests download with notification of the user identifier, password, and date and time set in fields FAB, FAC, FAE, with the address set in field FAD of the selected data record DRA as the destination. The ticket server 20 that received the request authenticates the user based on the notified user identifier and password, and downloads the electronic ticket data acquired for the user after the notified date and time to the information providing apparatus 10. In the information providing apparatus 10, when the electronic ticket data is received by the communication interface 16, the processor 11 stores the electronic ticket data in the main memory 12 or the auxiliary storage unit 13. Thus, electronic ticket data including an identifier of a product to be traded is collected from each of the ticket servers 20 corresponding to the data management devices. In this way, the processor 11 executes information processing by the ticket client application APA, and thereby a computer having the processor 11 as a core portion functions as a collecting unit (collecting means).
As the ACT5, the processor 11 updates the management database in order to reflect the download to the management. The processor 11 updates the date and time set in the field FAE of the data record DRA selected in the ACT4, for example, to indicate the latest download date and time. The processor 11 rewrites the field FAE, for example, to a numerical value indicating the date and time of the request for download.
As ACT6, the processor 11 confirms whether there is an electronic ticket service that has not been downloaded this time. For example, if the data record DRA included in the management database DBA includes a data record DRA other than the data record DRA selected in ACT4, the processor 11 determines that there is a qualified electronic ticket service, and returns to ACT 4. Further, the processor 11 repeats ACT4 and ACT5 in the same manner as described above. However, in the case where the ACT4 is executed for the second time or later, the processor 11 selects an electronic ticket service other than that selected in the ACT4 before.
In this way, the processor 11 downloads the electronic ticket data not downloaded for all registered electronic ticket services. Further, after completing the download of all the registered electronic ticket services, the processor 11 determines no in ACT6 and proceeds to ACT 7.
As the ACT7, the processor 11 updates the history database DBB based on the electronic ticket data downloaded this time. For example, if the data record DRB having the product code set in the field FBA is not included in the history database DBB for each product code included in the electronic ticket data downloaded this time, the processor 11 adds a new data record DRB to the history database DBB. The processor 11 sets the corresponding commodity code in field FBA of the new data record DRB and sets the detailed data in field FBB. The processor 11 sets the store identifier and the transaction date and time shown in the electronic ticket data and the number of times and unit price shown in the electronic ticket data for the commodity code in the fields FCA to FCD of the detailed data, respectively. For example, if the data record DRB in which the product code is set in the field FBA is already included in the history database DBB for each product code included in the electronic ticket data downloaded this time, the processor 11 adds new detailed data to the data record DRB. Further, the processor 11 sets the store identifier and the transaction date and time shown in the electronic ticket data and the number of times and unit price shown in the electronic ticket data for the product code to the fields FCA to FCD of the new detailed data, respectively. The processor 11 adds the detailed data of the transaction date and time to the data record DRB in order. In this way, the processor 11 executes information processing by the ticket client application APA, and thereby a computer having the processor 11 as a core portion functions as an update unit (update means).
As the ACT8, the processor 11 displays a designation screen on the touch panel 14, for example. The designation screen is a screen for allowing the user to designate a product to be subjected to history confirmation. Fig. 6 is a diagram showing an example of the designation screen SCA.
The designation screen SCA contains a display area ARAA, messages MEAA, MEAB, and buttons BUAA. The display area ARAA displays an image obtained by the camera 15 so as to overlap the longitudinal and transverse center lines. However, in fig. 6, the image obtained by the camera 15 is not shown. The message MEAA is a text message for communicating to the user that "the action state for confirming the transaction history of the article" is in. The message MEAB is a text message for prompting the user to scan a barcode of a commodity as a history confirmation target. The button BUAA is a soft key for the user to indicate the end of the history inquiry mode.
As the ACT9, the processor 11 confirms whether or not a commodity is designated. If the specification cannot be confirmed, the processor 11 determines "no" and proceeds to ACT 10.
As the ACT10, the processor 11 confirms whether the end history inquiry mode is instructed. If the instruction cannot be confirmed, the processor 11 determines "no" and returns to the ACT 9.
Thus, as ACT9 and ACT10, processor 11 waits for acceptance of the commodity designation or instructed termination.
The user specifies a commodity for which confirmation of the transaction history is desired by a preset operation. For example, the user directs the camera 15 to the product so that the barcode of the product is reflected on the display area ARAA.
When the designation screen SCA is displayed, the processor 11 analyzes the image obtained by the camera 15 and attempts to read the product code indicated by the barcode. The barcode may be read as processing by the ticket client application APA, or may be read as processing by an application other than the barcode reading application. Further, when the product code is read, the processor 11 determines that the product identified by the product code is designated, determines yes in ACT9, and proceeds to ACT 11. At this time, the processor 11 acquires the product code indicated by the read barcode as the identifier of the product. In this way, the processor 11 executes information processing by the ticket client application APA, and thereby a computer having the processor 11 as a core portion functions as an acquisition unit (acquisition means).
As the ACT11, the processor 11 confirms whether there is a purchase history about the specified merchandise. The processor 11 searches, for example, from the history database DBB, the data record DRB, which has set in the field FBA the product code of the specified product. If the data record DRB is not found, the processor 11 determines no and proceeds to ACT 12.
As the ACT12, the processor 11 displays an unpurchased screen in the touch panel 14, for example. The unpurchased screen is a screen set in advance for notifying the user that there is no purchase history. As for the non-purchase screen, for example, a screen displaying a text message indicating that there is no purchase history may be employed instead of the message MEAA in the designation screen SCA. Further, after that, the processor 11 returns to the wait states of ACT9 and ACT 10.
If the data record DRB of the product code of the specified product is set in the field FBA, the processor 11 regards that there is a purchase history, determines yes in ACT11, and proceeds to ACT13 in fig. 5.
As the ACT13, the processor 11 confirms whether the product code of the specified product is an in-store code. Further, if the code is not the in-store code, the processor 11 determines no, and proceeds to ACT 14.
As the ACT14, the processor 11 generates a purchase history screen and displays it in, for example, the touch panel 14. The processor 11 selects, for example, one of all the detailed data included in the data record DRB found as described above, and generates a purchase history screen so as to show the data included in the detailed data. In addition, the processor 11 selects, for example, detailed data set in the last field of the data record DRB. If so, the detailed data associated with the most recent transaction is first selected. However, the processor 11 may also select the detailed data set in the field FBB of the data record DRB. Thus, the detailed data associated with the earliest transaction is selected first. The processor 11 may select detailed data corresponding to a predetermined condition. In addition, the conditions may be appropriately determined by, for example, a creator or a user of the ticket client application APA.
Fig. 7 is a diagram showing an example of the purchase history screen SCB. In fig. 7, the same display elements as those included in the designation screen SCA shown in fig. 6 are denoted by the same reference numerals, and the description thereof is omitted.
In the present embodiment, the purchase history screen SCB includes a character string CSBA, a display area ARBA, and buttons BUBA and BUBB, instead of the message MEAA in the designation screen SCA.
The character string CSBA indicates the product name of the specified commodity. The display area ARBA indicates data included in the above detailed data. The buttons BUBA, BUBB are soft keys for the user to instruct display of other purchase histories.
As the ACT15, the processor 11 confirms whether or not a change of the displayed purchase history is instructed. If the instruction cannot be confirmed, the processor 11 determines no and proceeds to ACT 16.
As the ACT16, the processor 11 confirms whether or not a commodity is designated. If the specification cannot be confirmed, the processor 11 determines "no" and proceeds to ACT 17.
As the ACT17, the processor 11 confirms whether the end history inquiry mode is instructed. If the instruction cannot be confirmed, the processor 11 determines "no" and returns to the ACT 15.
In this way, the processor 11 waits for the ACT15 to ACT17 to accept the change or the end instruction or the commodity designation.
When the user desires to confirm a purchase history other than the purchase history indicated on the displayed purchase history screen, the user instructs to change the displayed purchase history by a preset operation such as touching one of the buttons BUBA and BUBB on the purchase history screen SCB, for example.
In this way, the processor 11 determines yes in ACT15, and returns to the wait states of ACT15 to ACT17 after executing ACT14 in the same manner as described above. In addition, when the processor 11 executes the ACT14 for the second time and thereafter, it selects detailed data other than the detailed data selected in the ACT14 for the previous time, and updates the display area ARBA so that the data included in the detailed data is displayed. The conditions for the processor 11 to newly select the detailed data may be appropriately determined by, for example, the creator or user of the ticket client application APA. As an example, the processor 11 newly selects the detailed data set in the field one after the field in which the selected detailed data is set, in accordance with the operation of the touch button BUBA. Further, as an example, the processor 11 newly selects the detailed data set in the field one before the field in which the selected detailed data is set, in response to the touch of the button BUBB. Thus, as described above, in the data record DRB, if the date and time of transaction is earlier, the detailed data is set in the earlier field, and the purchase history screen SCB is updated to display the purchase history in chronological order.
In this way, the data of the plurality of purchase history screens SCB representing the purchase history in chronological order corresponds to the history data representing the transaction history of the specified product. That is, sequentially generating data indicating the purchase history screen SCB, sequentially displaying the purchase history screen SCB corresponding to the data, corresponds to generating and outputting the purchase history data. As described above, the processor 11 executes information processing by the ticket client application APA, and thereby a computer having the processor 11 as a core portion functions as a generation unit (generation means) and an output unit (output means).
Further, when the product code of the designated product is the in-store code, the processor 11 determines yes in ACT13 and proceeds to ACT 18.
As the ACT18, the processor 11 displays a shop selection screen on the touch panel 14, for example. The shop selection screen is a screen for the user to select a shop in which a purchase history of a specified product exists. The processor 11 displays, as an option, a store name identified by a store identifier set in the field FCA of the detailed data included in the data record DRB having the product code of the specified product set in the field FBA, for example, on the store selection screen.
When a user selects a store whose purchase history is desired to be confirmed from the stores displayed as options on the store selection screen, the user performs a preset operation for specifying the store.
As an ACT19, the processor 11 waits for operation of a specified store. Further, when the shop is specified as described above, the processor 11 determines yes and proceeds to ACT 20. At this time, the processor 11 determines the designated store as a history confirmation target store. In this way, the processor 11 executes information processing by the ticket client application APA, and thereby a computer having the processor 11 as a core portion functions as a determination unit (determination means).
As the ACT20, the processor 11 reduces detailed data, which is referred to for displaying the purchase history, to be related to the specified shop. The processor 11 extracts detailed data in which the store identifier of the specified store is set in the field FCA from detailed data included in the data record DRB in which the product code of the specified product is set in the field FBA, for example, and sets data that meets the condition as the detailed data to be referred to.
As the ACT21, the processor 11 generates the purchase history screen SCB in the same manner as in the ACT14, and displays it on, for example, the touch panel 14. However, the processor 11 selects one of the detailed data reduced in the ACT20 in the ACT 21.
As the ACT22, the processor 11 confirms whether or not a change of the displayed purchase history is instructed. If the instruction cannot be confirmed, the processor 11 determines no and proceeds to ACT 23.
As the ACT23, the processor 11 confirms whether or not a commodity is designated. If the specification cannot be confirmed, the processor 11 determines "no" and proceeds to ACT 24.
As the ACT24, the processor 11 confirms whether the end history inquiry mode is instructed. If the instruction cannot be confirmed, the processor 11 determines "no" and returns to the ACT 22.
In this way, the processor 11 waits for the ACT22 to ACT24 to accept the change or the end instruction or the commodity designation.
When the user instructs to change the purchase history in the same manner as described above, the processor 11 determines yes in ACT22, and returns to the waiting state of ACTs 22 to 24 after executing ACT 21. In addition, in the case where the ACT21 is executed for the second time and thereafter, the processor 11 selects, from the detailed data reduced in the ACT20, detailed data other than the detailed data selected in the ACT14 the previous time.
When the user wishes to confirm the transaction history related to another product when the unpurchased screen is displayed, the camera 15 is directed to the product so that the barcode of the product is reflected in the display area ARAA of the unpurchased screen. In this way, the processor 11 determines yes in ACT9 in fig. 4 in the same manner as described above, and proceeds to ACT 11. When the purchase history screen SCB is displayed, if the user wishes to confirm the transaction history related to another product, the camera 15 is directed to the product so that the barcode of the product is reflected in the display area ARAA of the purchase history screen SCB. In this way, the processor 11 determines yes in ACT16 or ACT23 in fig. 5, and proceeds to ACT11 in fig. 4. Further, the processor 11 similarly performs the operations after ACT11 as described above. Thereby, the processor 11 displays the transaction history of the newly specified commodity.
When the user finishes confirming the transaction history while any one of the designation screen SCA, the non-purchase screen, and the purchase history screen SCB is displayed, the user instructs the end by a preset operation such as touching the button BUAA on each screen.
If the end is thus instructed, the processor 11 determines yes in ACT10 in fig. 4 or ACT17 or ACT24 in fig. 5, returns to ACT1 in fig. 4, and performs operations after ACT1 in the same manner as described above.
As described above, according to the information providing apparatus 10, the transaction history covering a plurality of electronic ticket services is displayed. Thus, the trouble of confirming the transaction history to the customer can be reduced. That is, a plurality of data management apparatuses are operated by other service providers, respectively. The plurality of data management apparatuses provide different electronic ticket services (services), respectively. Confirmation of transaction history across service providers can be easily made.
Further, according to the information providing apparatus 10, the history database DBB provided in the auxiliary storage unit 13 is updated one by one, and the transaction history is displayed based on the history database DBB. Therefore, the amount of transaction data collected for one update of the history database DBB can be reduced, and the update of the history database DBB and the processing time for displaying the transaction history based on the updated history database DBB can be reduced.
Further, according to the information providing apparatus 10, when the in-store code is designated to designate a product, only the transaction history related to the designated store is displayed. Thus, even if the same in-store code is used for identifying various products in a plurality of stores, the transaction history in which these are mixed is not displayed.
Further, according to the information providing apparatus 10, the user can easily confirm the transaction history through display in the attached display device.
This embodiment can be modified in various ways as follows.
The transaction may be any of, for example, selling of an article to a customer in a store, selling of an article to a customer by communication sales, providing of food and drink consumed by a customer in a store, and providing of intangible service to a customer.
The product code of the product to be displayed as a history may be acquired by any method other than barcode reading, for example, by specifying it from a product list having a purchase history.
The collected electronic bill data may be directly stored in the main memory 12 or the auxiliary storage unit 13, and a history screen may be generated based on the electronic bill data.
It is also possible to download the electronic ticket data from the ticket server 20 every time the history inquiry mode is started.
Instead of the display of the purchase history screen SCB, a transaction history screen showing a list of a plurality of transaction histories may be displayed.
Further, as for the output of the transaction history, any method other than a display method, such as outputting an audio message, printing or outputting data to another device, or the like, may be used.
When the product code of the specified product is an in-store code, the determination of the store that is the target of guiding the transaction history may be, for example, a store that the user has gone to by a known determination method.
The functions realized by the processor 11 through information processing may be partly or entirely realized by hardware such as a logic circuit that executes information processing not based on a program. Each of the functions described above can be realized by combining hardware such as the logic circuit with software control.
The programs executed by the devices of the above embodiments are provided by being embedded in ROM or the like in advance. The program executed by each device of the above-described embodiments may be provided by recording a file in an installable or executable format on a computer-readable recording medium such as a CD-ROM, a Flexible Disk (FD), or a CD-R, DVD (Digital Versatile Disk).
Further, the program executed by each device of the above-described embodiments may be stored on a computer connected to a network such as the internet and downloaded via the network to be provided. Further, the program executed by each device of the above embodiments may be provided or distributed via a network such as the internet.
Several embodiments of the present invention have been described, but these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in other various ways, and various omissions, substitutions, and changes can be made without departing from the spirit of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalent scope thereof.

Claims (10)

1. An information providing device is characterized by comprising:
a collecting unit that collects electronic ticket data including an identifier of a commodity as a transaction target that has been completed, from a plurality of data management devices;
an acquisition unit that acquires the identifier;
a generation unit configured to generate history data indicating a transaction history of the product identified by the identifier acquired by the acquisition unit, based on the electronic ticket data collected by the collection unit; and
an output unit that outputs the history data generated by the generation unit.
2. The information providing apparatus according to claim 1,
the collecting section repeats the collection of the electronic ticket data not collected yet,
the information providing device further includes:
a storage device that stores a database indicating transaction histories related to the commodities that are objects of transactions completed in execution, respectively; and
an updating section that updates the database based on the electronic ticket data newly collected by the collecting section,
the generation unit generates the history data based on the database.
3. The information providing apparatus according to claim 1 or 2, further comprising:
a determination unit that determines a store that is a target of history confirmation when the identifier acquired by the acquisition unit belongs to a special identifier that can be used to identify each product in a plurality of stores,
the generation unit generates the history data as a transaction history indicating the store determined by the determination unit, when the identifier acquired by the acquisition unit belongs to the special identifier.
4. The information providing apparatus according to claim 1 or 2, further comprising:
the display device is provided with a display device,
the output section displays a screen based on the history data in the display device.
5. The information providing apparatus according to claim 3, further comprising:
the display device is provided with a display device,
the output section displays a screen based on the history data in the display device.
6. The information providing apparatus according to claim 1, further comprising:
and a service processing unit for executing a service of the data management apparatus.
7. The information providing apparatus according to claim 6,
the service processing unit includes an operation unit that instructs execution of the acquisition unit.
8. The information providing apparatus according to claim 6 or 7,
the plurality of service processing units are provided to the plurality of data management apparatuses, and execute services different from each of the plurality of data management apparatuses.
9. A storage medium storing an information processing program, the information processing program causing a computer provided in an information processing apparatus to function as:
a collecting unit that collects electronic ticket data including an identifier of a commodity as a transaction target that has been completed, from a plurality of data management devices;
an acquisition unit that acquires the identifier;
a generation unit configured to generate history data indicating a transaction history of the product identified by the identifier acquired by the acquisition unit, based on the electronic ticket data collected by the collection unit; and
an output unit that outputs the history data generated by the generation unit.
10. An information providing method, comprising the steps of:
collecting electronic bill data including an identifier of a commodity as a transaction target for which execution is completed from a plurality of data management devices;
obtaining the identifier;
generating history data representing a transaction history of the commodity identified by the acquired identifier based on the collected electronic ticket data; and
outputting the generated history data.
CN202110187390.8A 2020-03-24 2021-02-18 Information providing apparatus, storage medium, and information providing method Pending CN113450164A (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2020-053270 2020-03-24
JP2020053270A JP2021152803A (en) 2020-03-24 2020-03-24 Information providing device, information processing program, and information providing method

Publications (1)

Publication Number Publication Date
CN113450164A true CN113450164A (en) 2021-09-28

Family

ID=77808807

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110187390.8A Pending CN113450164A (en) 2020-03-24 2021-02-18 Information providing apparatus, storage medium, and information providing method

Country Status (3)

Country Link
US (1) US11966902B2 (en)
JP (1) JP2021152803A (en)
CN (1) CN113450164A (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105787775A (en) * 2015-01-08 2016-07-20 东芝泰格有限公司 Method For Processing A Purchase Transaction Using A Plurality Of Transaction Systems
US20160300217A1 (en) * 2013-12-02 2016-10-13 Wal-Mart Stores, Inc. System and method for placing an order using a local device
CN106169141A (en) * 2015-05-22 2016-11-30 卡西欧计算机株式会社 Shopping auxiliary device and shopping householder method

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009271744A (en) 2008-05-08 2009-11-19 Seiko Epson Corp Commodity information provision device
JP2016128954A (en) 2015-01-09 2016-07-14 株式会社日立システムズ Electronic receipt system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160300217A1 (en) * 2013-12-02 2016-10-13 Wal-Mart Stores, Inc. System and method for placing an order using a local device
CN105787775A (en) * 2015-01-08 2016-07-20 东芝泰格有限公司 Method For Processing A Purchase Transaction Using A Plurality Of Transaction Systems
CN106169141A (en) * 2015-05-22 2016-11-30 卡西欧计算机株式会社 Shopping auxiliary device and shopping householder method

Also Published As

Publication number Publication date
US20210304177A1 (en) 2021-09-30
US11966902B2 (en) 2024-04-23
JP2021152803A (en) 2021-09-30

Similar Documents

Publication Publication Date Title
JP2022000823A (en) Information processing device and information processing method
US20200364687A1 (en) Settlement system including user management server
JP7483516B2 (en) Information processing device and control program thereof
EP3376457A1 (en) Order management system
JP6987936B2 (en) Electronic receipt system and electronic receipt provision method
JP2021193600A (en) Sales data registration device and program
JP2017204242A (en) Information processing apparatus, programmable device, license management system, license management method, and program
EP3118794A1 (en) Electronic receipt management system
JP6368847B1 (en) Information management apparatus, information management method and program
CN113450164A (en) Information providing apparatus, storage medium, and information providing method
EP3866091B1 (en) Transaction processing system and information processing method
EP3118802A1 (en) Electronic receipt system, server device, and program
JP6006385B2 (en) server
JP7027727B2 (en) Print management system
JP5792863B2 (en) Mobile communication terminal and program
JP6553786B1 (en) Information processing apparatus, information processing method, and information processing program
US20180357659A1 (en) Sales transaction support system
US20230259911A1 (en) Transaction processing system, transaction processing apparatus, and information processing method
JP2020126324A (en) Order system, order management device, and information processing program
JP6912618B2 (en) Server, program and product information output method
EP4344166A1 (en) Personal shopper information processing method, communication device for personal shopping, and information processing device for personal shopper services
US20230069415A1 (en) Receipt server, information processing method, and program recording medium
US20210327226A1 (en) Hand-held electronic receipt generating terminal
JP7477417B2 (en) Information processing device, receipt server, and information processing program
US11893621B2 (en) Merchandise sales processing system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination