System

Abstract

A system is provided.SOLUTION: The system includes a means for remitting electronic money from a parent account to a child account, a means for storing a purchase history of the child account in a server, a means for displaying the child purchase history on a parent terminal, and a means for transmitting an alert based on a condition set by the parent.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The technology of the present disclosure relates to a system. [Background technology]

[0002] Patent document 1 discloses a persona chatbot control method performed by at least one processor, the method including the steps of receiving a user utterance, adding the user utterance to a prompt including an instruction sentence related to a description of the chatbot character, encoding the prompt, and inputting the encoded prompt into a language model to generate a chatbot utterance in response to the user utterance. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-180282 Summary of the Invention [Problem to be solved by the invention]

[0004] In recent years, with the spread of smartphones, it has become common for children to own smartphones at a young age. However, there are limited ways to manage pocket money without giving children cash, making it difficult for parents to keep track of how their children spend their money. Furthermore, in order for children to develop independent financial awareness, they need an environment where they can use their money freely while still being properly supervised by their parents. Against this background, there is a need for a system that allows parents to give their children pocket money with peace of mind and manage how it is spent. To solve the above-mentioned problems, the present invention provides a system that allows parents to provide their children with electronic pocket money and manage how it is spent. [Means for solving the problem]

[0005] The present invention provides a system including a means for transferring electronic money from a parent's account to a child's account, a means for storing the child's account's purchase history on a server, a means for displaying the child's purchase history on the parent's device, and a means for sending alerts based on conditions set by the parent. More specifically, the system further includes a means for collecting payment information on the child's device and sending the information to a server, and a means for the parent's device and the child's device to communicate via an application. This allows parents to safely give their children pocket money, monitor their children's spending in real time, and receive alerts when certain conditions are met. This allows parents to safely supervise their children while promoting the development of their children's financial management skills.

[0006] "Parent Account" means an account owned and managed by a parent for transferring electronic money and monitoring a child's financial use.

[0007] A "child's account" is an account linked to a parent's account and is used to receive and spend electronic money.

[0008] "Electronic money" is a form of money that is managed electronically and is used in place of actual paper money and coins.

[0009] "Remittance" is the act of moving electronic money from a parent's account to a child's account.

[0010] "Purchase History" refers to the records and details of payments made by a Child's account.

[0011] A "server" is a computer system that manages data and stores and transmits data in response to various requests.

[0012] "Devices" are devices such as smartphones and tablets used by parents and children.

[0013] An "application" is software that runs on a device and is used by both parents and children.

[0014] An "alert" is a notification sent to the parent's device when a specific condition is met. [Brief explanation of the drawings]

[0015] [Figure 1] 1 is a conceptual diagram showing an example of the configuration of a data processing system according to a first embodiment. [Figure 2] 1 is a conceptual diagram showing an example of main functions of a data processing device and a smart device according to a first embodiment. [Figure 3] FIG. 10 is a conceptual diagram showing an example of the configuration of a data processing system according to a second embodiment. [Figure 4] FIG. 10 is a conceptual diagram showing an example of main functions of a data processing device and smart glasses according to a second embodiment. [Figure 5] FIG. 10 is a conceptual diagram showing an example of the configuration of a data processing system according to a third embodiment. [Figure 6] FIG. 11 is a conceptual diagram showing an example of main functions of a data processing device and a headset-type terminal according to a third embodiment. [Figure 7] FIG. 10 is a conceptual diagram showing an example of the configuration of a data processing system according to a fourth embodiment. [Figure 8] FIG. 10 is a conceptual diagram showing an example of main functions of a data processing device and a robot according to a fourth embodiment. [Figure 9] 1 shows an emotion map onto which multiple emotions are mapped. [Figure 10] 1 shows an emotion map onto which multiple emotions are mapped. [Figure 11] FIG. 3 is a sequence diagram showing a processing flow of the data processing system according to the first embodiment. [Figure 12] FIG. 10 is a sequence diagram showing the flow of processing in the data processing system in Application Example 1. [Figure 13]FIG. 10 is a sequence diagram showing the flow of processing in the data processing system according to the second embodiment when an emotion engine is combined. [Figure 14] FIG. 10 is a sequence diagram showing the flow of processing in the data processing system in Application Example 2 when an emotion engine is combined. DETAILED DESCRIPTION OF THE INVENTION

[0016] An example of an embodiment of a system according to the technology of the present disclosure will be described below with reference to the accompanying drawings.

[0017] First, the terms used in the following description will be explained.

[0018] In the following embodiments, a coded processor (hereinafter simply referred to as a "processor") may be a single arithmetic device or a combination of multiple arithmetic devices. Furthermore, a processor may be a single type of arithmetic device or a combination of multiple types of arithmetic devices. Examples of arithmetic devices include a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), a GPGPU (General-Purpose computing on Graphics Processing Units), and an APU (Accelerated Processing Unit).

[0019] In the following embodiments, a coded RAM (Random Access Memory) is a memory in which information is temporarily stored and is used as a working memory by a processor.

[0020] In the following embodiments, the coded storage is one or more non-volatile storage devices that store various programs, various parameters, etc. Examples of non-volatile storage devices include flash memory (SSD (Solid State Drive)), magnetic disks (e.g., hard disks), and magnetic tapes.

[0021] In the following embodiments, a communication I / F (Interface) with a symbol is an interface including a communication processor, an antenna, etc. The communication I / F controls communication between multiple computers. Examples of communication standards applied to the communication I / F include wireless communication standards including 5G (5th Generation Mobile Communication System), Wi-Fi (registered trademark), Bluetooth (registered trademark), etc.

[0022] In the following embodiments, "A and / or B" is synonymous with "at least one of A and B." In other words, "A and / or B" means that it may be only A, only B, or a combination of A and B. Furthermore, in this specification, the same concept as "A and / or B" is also applied when three or more things are expressed connected by "and / or."

[0023] [First embodiment]

[0024] FIG. 1 shows an example of the configuration of a data processing system 10 according to the first embodiment.

[0025] 1, a data processing system 10 includes a data processing device 12 and a smart device 14. An example of the data processing device 12 is a server.

[0026] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[0027] The smart device 14 includes a computer 36, a reception device 38, an output device 40, a camera 42, and a communication I / F 44. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The reception device 38, the output device 40, and the camera 42 are also connected to the bus 52.

[0028] The reception device 38 includes a touch panel 38A, a microphone 38B, and the like, and receives user input. The touch panel 38A detects contact with an indicator (for example, a pen or a finger) to receive user input by the touch of the indicator. The microphone 38B detects the user's voice to receive user input by voice. The control unit 46A transmits data indicating the user input received by the touch panel 38A and the microphone 38B to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the data indicating the user input.

[0029] The output device 40 includes a display 40A and a speaker 40B, and presents data to the user 20 by outputting the data in a form of expression that the user 20 can perceive (for example, audio and / or text). The display 40A displays visible information such as text and images in accordance with instructions from the processor 46. The speaker 40B outputs audio in accordance with instructions from the processor 46. The camera 42 is a compact digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor.

[0030] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 control the exchange of various information between the processor 46 and the processor 28 via the network 54.

[0031] FIG. 2 shows an example of the main functions of the data processing device 12 and the smart device 14.

[0032] 2, in the data processing device 12, a specific process is performed by the processor 28. A specific processing program 56 is stored in the storage 32. The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific process is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[0033] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[0034] In the smart device 14, the processor 46 performs the reception output process. The storage 50 stores a reception output program 60. The reception output program 60 is used in conjunction with the specific processing program 56 by the data processing system 10. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[0035] Next, a description will be given of the specific processing performed by the specific processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0036] The present invention is a system for parents to give electronic pocket money to their children and manage how the money is spent. Specific processing contents based on an embodiment of the present invention will be described below.

[0037] System Configuration

[0038] The system consists of the following elements:

[0039] 1. Smartphone apps (devices) for parents and children

[0040] 2. Central Management Server (Server)

[0041] User registration and account linking

[0042] 1. The user (parent) installs the app and registers as a new user.

[0043] 2. The user (parent) creates an account for the child and links it to their own account.

[0044] 3. The server stores the parent and child account information in a database.

[0045] Distribution of pocket money

[0046] 1. The user (parent) accesses the app and enters the amount to transfer to their child's account.

[0047] 2. The terminal sends a remittance request to the server.

[0048] 3. The server receives the request and credits the specified amount to the child's account.

[0049] 4. Your child's device will notify you of a new transfer.

[0050] Check your purchase history

[0051] 1. When a user (child) makes a payment with PayPay, the terminal sends the payment information to the server.

[0052] 2. The server stores the payment information in a database.

[0053] 3. Users (parents) can check their children's purchase history in real time through the app.

[0054] 4. The parent's device will notify them of their latest purchase history.

[0055] Alert Settings

[0056] 1. The user (parent) sets up alerts in the app based on specific usage conditions (e.g., when payments exceed a certain amount).

[0057] 2. The server monitors the purchase history based on the set conditions.

[0058] 3. If the condition is met, the server sends an alert to the parent device.

[0059] 4. The parent's device notifies the parent of the alert and displays detailed information.

[0060] Specific examples

[0061] User registration and account linking

[0062] The user (parent) installed the app and created an account. Then, the user (parent) created a child account and linked the two accounts.

[0063] The server stored the parent and child information in a database.

[0064] Distribution of pocket money

[0065] The user (parent) accessed the app to send their child 500 yen in pocket money, entered the amount, and sent it.

[0066] The server added 500 yen to the child's account and sent the child a notification of the transfer.

[0067] Check your purchase history

[0068] The user (child) paid 200 yen with PayPay at a stationery store.

[0069] The server received this payment information and stored it in a database.

[0070] The user (parent) checked their child's most recent purchase history in the app and confirmed the payment at the stationery store.

[0071] Alert Settings

[0072] The user (parent) set it up so that an alert would be sent if their child spent more than 500 yen at one time.

[0073] A few days later, I spent 600 yen on my child's device to buy a toy.

[0074] When the server met the alert conditions, it sent a notification to the parent's device, and the user (parent) received the alert.

[0075] This system provides parents with a more transparent and secure environment for managing their children's finances, and allows children to safely use their pocket money without having to carry cash.

[0076] The processing flow will be explained below.

[0077] User registration and account linking

[0078] Step 1:

[0079] The user (parent) installs the app and opens the new user registration screen.

[0080] The user (parent) enters information such as name, email address, and password.

[0081] Step 2:

[0082] The terminal transmits the input information to the server.

[0083] Step 3:

[0084] The server receives the information and registers the new user in its database.

[0085] The server generates an account ID and returns it to the device.

[0086] Step 4:

[0087] The user (parent) selects the option to create a child account.

[0088] The user (parent) enters the child's name and user ID.

[0089] Step 5:

[0090] The terminal sends a request to create a child account to the server.

[0091] Step 6:

[0092] The server receives the request, creates a child account, and associates it with the parent account.

[0093] The server generates a child account ID and returns it to the device.

[0094] Distribution of pocket money

[0095] Step 1:

[0096] The user (parent) logs into the app and selects the option to transfer pocket money.

[0097] The user (parent) enters the remittance amount.

[0098] Step 2:

[0099] The device sends a transfer request to the server, which includes the parent's account ID, the child's account ID, and the transfer amount.

[0100] Step 3:

[0101] The server receives the transfer request and checks the parent and child account information in its database.

[0102] The server adds the transfer amount to the child's account and updates the database.

[0103] The server returns a successful transfer information and notifies the child account of the update.

[0104] Step 4:

[0105] The device receives a notification from the server and notifies the child's app that a new transfer has been made.

[0106] Check your purchase history

[0107] Step 1:

[0108] The user (child) makes purchases using PayPay. Payments are made through the app.

[0109] Step 2:

[0110] Once the payment is complete, the terminal sends the payment information (store name, amount, date and time, etc.) to the server.

[0111] Step 3:

[0112] The server receives the payment information and stores it in a database, including the child's account ID.

[0113] Step 4:

[0114] The user (parent) selects the option to view their child's purchase history within the app.

[0115] Step 5:

[0116] The terminal sends a history request to the server.

[0117] Step 6:

[0118] The server retrieves the child's latest payment information from the database and sends it back to the parent's device.

[0119] Step 7:

[0120] The device displays the received history information in the parent's app.

[0121] Alert Settings

[0122] Step 1:

[0123] The user (parent) selects the alert setting option and enters specific conditions (e.g., a single payment of 500 yen or more).

[0124] Step 2:

[0125] The device sends an alert setting request to the server, which includes the parent account ID and the alert conditions.

[0126] Step 3:

[0127] The server receives the alert conditions and stores them in a database.

[0128] Step 4:

[0129] As the server saves each payment entry to the database, it checks it against pre-defined alert conditions.

[0130] Step 5:

[0131] When a condition is met (e.g., when a child pays more than 500 yen), the server sends an alert notification to the parent's device.

[0132] Step 6:

[0133] The device receives an alert notification and displays the alert content in the parent's app.

[0134] Example 1

[0135] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0136] Today's children are increasingly using electronic money instead of carrying cash, but to make it easier for parents to manage their children's finances, a transparent and safe system is needed. It is also desirable for parents to monitor their children's spending in real time and set alerts as necessary. However, current systems do not adequately provide such functionality.

[0137] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[0138] In this invention, the server includes means for transferring electronic money from a parent's account to a child's account, means for storing the purchase history of the child's account on the server, means for displaying the child's purchase history on the parent's terminal, means for sending alerts based on conditions set by the parent, means for storing the parent and child's account information in a database, means for sending a remittance request to the server using HTTPS, and means for the server to send a remittance notification via a push notification API. This allows parents to keep track of their child's financial management in real time and receive appropriate alerts.

[0139] "Parent Account" means an account used by a parent to transfer and manage electronic money to a child.

[0140] A "child's account" is an account used by a child to receive electronic money transferred from a parent and use it for payments, etc.

[0141] "Electronic money" refers to currency exchanged electronically in place of cash, and is used for online or offline payments.

[0142] A "transfer request" is a request to transfer electronic money from a parent's account to a child's account.

[0143] A "parent's device" is an electronic device such as a smartphone or tablet used by the parent to transfer electronic money and check purchase history.

[0144] A "child's device" is an electronic device such as a smartphone or tablet used by a child, which is used to make payments using electronic money.

[0145] A "server" is a central management system that receives requests from multiple terminals and stores and processes data.

[0146] "Database" refers to a system for storing and managing data such as parent and child account information and purchase history.

[0147] "HTTPS" is a communication protocol for encrypting and sending data over the Internet, enabling secure data transmission.

[0148] "Push notifications" are notifications that are sent in real time from a server to a device, and are used to instantly inform users of important information such as money transfers, purchase history, and alerts.

[0149] MODE FOR CARRYING OUT THE INVENTION

[0150] The present invention is a system that allows parents to give electronic pocket money to their children and manage how that money is spent. Specific processing details of the present invention will be described below.

[0151] System Configuration

[0152] The system consists of the following elements:

[0153] 1. Smartphone apps (devices) for parents and children

[0154] 2. Central Management Server (Server)

[0155] 3. Database System

[0156] 4. Communication Protocol (HTTPS)

[0157] 5. Push notification services

[0158] User registration and account linking

[0159] The user (parent) installs a dedicated app on their smartphone.

[0160] Hardware used: Smartphone (e.g. iPhone (registered trademark), ANDROID (registered trademark) smartphone)

[0161] Software used: Dedicated app (e.g. PocketMoneyApp)

[0162] Parents launch the app and enter their name, email address, and password to register.

[0163] Parents then enter their child's information (name, age) to create an account for their child and link it to their own account.

[0164] The server receives this information and stores it in a database (e.g., MySQL (registered trademark)).

[0165] Distribution of pocket money

[0166] The user (parent) accesses the app and enters the amount they want to send to their child.

[0167] The terminal sends the transfer request to the server using HTTPS.

[0168] The server receives the request and credits the child's account with the specified amount, and the credited transfer information is saved in a database.

[0169] The server uses a push notification service to send a remittance notification to the child's device.

[0170] Check your purchase history

[0171] When a user (child) makes a payment at a store using electronic money (e.g., PayPay), the child's terminal collects payment information and sends it to the server.

[0172] The server receives the payment information and stores it in a database.

[0173] Users (parents) can check their children's purchase history in real time through the app.

[0174] The server also notifies the parent's device of the latest purchase history.

[0175] Alert Settings

[0176] Users (parents) can set alerts within the app when certain usage conditions are met (e.g., payments of 500 yen or more).

[0177] The server monitors the purchase history based on set conditions.

[0178] If the condition is met, the server sends an alert to the parent device.

[0179] The parent's device notifies the parent of the received alert and displays detailed information.

[0180] Specific examples

[0181] User registration and account linking

[0182] The user (parent) installs the dedicated app, creates an account, then creates a child account and links the two accounts.

[0183] The server stores parent and child information in a database.

[0184] Distribution of pocket money

[0185] The user (parent) accessed the app and sent 500 yen to their child.

[0186] The server adds 500 yen to the child's account and notifies the child of the transfer via push notification.

[0187] Check your purchase history

[0188] The user (child) paid 200 yen using electronic money at a stationery store.

[0189] The server receives this payment information and stores it in a database.

[0190] The user (parent) checks their child's latest purchase history in the app and confirms payments at the stationery store.

[0191] Alert Settings

[0192] The user (parent) sets an alert in the app for payments over 500 yen.

[0193] A few days later, when a 600 yen purchase is made on the child's device, the server will send a notification to the parent's device, as the alert conditions have been met.

[0194] The user (parent) will receive an alert to check the details.

[0195] The above is a specific embodiment of the present invention, and by using this system, parents can easily manage how their children's pocket money is spent. In addition, the real-time monitoring and alert functions allow parents to manage their children's pocket money with peace of mind.

[0196] The flow of the identification process in the first embodiment will be described with reference to FIG.

[0197] User registration and account linking

[0198] Step 1:

[0199] The user (parent) installs a dedicated app.

[0200] Input: Download the app from the App Store or GOOGLE PLAY(R)

[0201] Output: The app is installed on your phone.

[0202] Specific actions: Operate your smartphone to search for and download the app, and complete the installation.

[0203] Step 2:

[0204] The user (parent) registers a new user on the app.

[0205] Input: Name, Email Address, Password

[0206] Output: New account created

[0207] Specific actions: Launch the app, enter your name, email address, and password, and press the "Register" button.

[0208] Step 3:

[0209] The user (parent) creates an account for their child and links it to their own account.

[0210] Input: Child's name, age

[0211] Output: Child account created and linked to parent account

[0212] Specific actions: Select the "Create a child account" option in the app, enter the required information and press the "Create" button.

[0213] Step 4:

[0214] The server stores parent and child account information in a database.

[0215] Input: Parent and child account information

[0216] Output: Information is saved in the database

[0217] Specific behavior: Receives HTTP requests and executes queries to insert information into a database.

[0218] Distribution of pocket money

[0219] Step 1:

[0220] The user (parent) accesses the app and enters the amount to be transferred.

[0221] Input: Amount you want to send

[0222] Output: A transfer request is generated.

[0223] Specific actions: Enter the amount to send in the app's text field and press the "Send" button.

[0224] Step 2:

[0225] The terminal sends a remittance request to the server.

[0226] Input: Transfer request

[0227] Output: The request arrives at the server

[0228] What it does: Creates and sends a money transfer request using HTTPS.

[0229] Step 3:

[0230] The server will credit the specified amount to the child's account.

[0231] Input: Transfer request

[0232] Output: The child's account balance is updated.

[0233] What it does: Executes a query that updates the appropriate records in the database, adding the specified amount.

[0234] Step 4:

[0235] The server sends a notification of the transfer.

[0236] Input: Remittance information

[0237] Output: A notification is sent to the child's device.

[0238] Specific operation: Sends notifications using the push notification API.

[0239] Check your purchase history

[0240] Step 1:

[0241] The user (child) makes a payment using PayPay.

[0242] Input: Purchase amount, payment information

[0243] Output: PayPay payment completed

[0244] Specific operations: Scan the QR code (registered trademark) with the PayPay app, enter the amount, and confirm the payment.

[0245] Step 2:

[0246] The terminal sends the payment information to the server.

[0247] Input: Payment information

[0248] Output: Payment information arrives at the server

[0249] Specific operation: After payment is completed, an HTTP request containing payment information is sent to the server.

[0250] Step 3:

[0251] The server stores the purchase history.

[0252] Input: Payment information

[0253] Output: Purchase history stored in the database

[0254] Specific Actions: Executes a query to insert payment information into the database.

[0255] Step 4:

[0256] The server notifies the parent's device of the purchase history.

[0257] Input: Purchase history

[0258] Output: A notification is sent to the parent's device.

[0259] Specific operation: Sends notifications to the parent's device using the push notification API.

[0260] Alert Settings

[0261] Step 1:

[0262] User (parent) sets alerts based on usage conditions.

[0263] Input: Alert condition, e.g., payment of 500 yen or more

[0264] Output: Save alert settings

[0265] Specific actions: Enter conditions on the "Alert Settings" page in the app and press the "Save" button.

[0266] Step 2:

[0267] The server monitors the purchase history.

[0268] Input: purchase history, alert conditions

[0269] Output: Monitoring results

[0270] Specific behavior: Periodically runs monitoring queries against the database.

[0271] Step 3:

[0272] The server notifies you when the condition is met.

[0273] Input: Monitoring results

[0274] Output: Alert notification on parent device

[0275] Specific behavior: When the conditions are met, an alert is sent using the push notification API.

[0276] Step 4:

[0277] The parent device receives the alert.

[0278] Input: Alert notification

[0279] Output: Display of alert notification

[0280] Specific behavior: Displays an alert as a pop-up notification on the device.

[0281] (Application example 1)

[0282] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0283] Traditionally, when managing pocket money with cash, it is difficult for parents to keep track of how their children spend their money in detail, and it is also difficult to record where and how the child spends the money. This makes it difficult for parents to properly manage their children's money and for children to develop a healthy sense of money. Furthermore, with the spread of electronic money, there is a need for a safe and efficient way for parents to give pocket money to their children.

[0284] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[0285] In this invention, the server includes means for transferring electronic money from a parent's account to a child's account, means for storing the purchase history of the child's account in a central management device, means for displaying the child's purchase history on the parent's mobile information terminal, means for sending alerts based on conditions set by the parent, means for setting alerts based on changes in the balance of the child's account, and means for scheduling transfers from the parent's account to the child's account. This allows parents to manage their children's money efficiently and safely, and enables children to develop sound financial skills.

[0286] "Parent Account" refers to an online account used by a parent to manage electronic money.

[0287] A "child's account" is an online account used by a child to manage electronic money.

[0288] "Electronic money" is currency used in electronic form in place of cash.

[0289] A "means of transfer" is a means for transferring electronic money from a parent's account to a child's account.

[0290] "Purchase history" is a record of purchases made by a child using electronic money.

[0291] The "central management device" is a server that centrally manages all account information and transaction history.

[0292] A "personal digital assistant" is a mobile device such as a smartphone or tablet.

[0293] A "warning" is a notification issued to call attention when a set condition is met.

[0294] "Balance fluctuation" refers to the increase or decrease in the amount of electronic money in an account.

[0295] A "means for scheduling remittances" is a means for automatically sending remittances based on specified dates and conditions.

[0296] The present invention is a system for parents to give electronic pocket money to their children and manage how the money is spent. Specific embodiments of the present invention will be described in detail below.

[0297] System configuration

[0298] The system consists of the following elements:

[0299] 1. Parent and child mobile devices (smartphones, tablets, etc.)

[0300] 2. Central management device (server)

[0301] Hardware and Software

[0302] Hardware: Smartphones (iOS, Android), tablets

[0303] software:

[0304] Python: Programming Language

[0305] Flask: a web framework for building server-side APIs

[0306] SQLite: Manage users and purchase history as a database

[0307] User registration and account linking

[0308] The parent installs the application on their mobile device and registers as a new user. The parent then creates an account for the child and links it to their own account. The central management device (server) stores the parent and child account information in a database.

[0309] Distribution of pocket money

[0310] The parent accesses the application and enters the amount to transfer to the child's account. The device sends the transfer request to the server, which then updates the child's account with the specified amount. The child's device notifies them of the new transfer.

[0311] Check your purchase history

[0312] When a child makes a payment using an electronic payment service such as PayPay, the device sends the payment information to a server, which stores it in a database, allowing parents to check their child's most recent purchase history in real time through the app.

[0313] Alert Settings

[0314] Parents can set alerts based on specific usage conditions in the application, such as when a certain amount of money is spent. The server monitors the purchase history based on the set conditions and sends an alert to the parent's device when the condition is met.

[0315] Monitor balance fluctuations

[0316] Parents can set alerts based on changes in their child's account balance, such as when the balance exceeds or falls below a certain amount, allowing parents to monitor their child's spending behavior more closely.

[0317] Schedule a transfer

[0318] Parents can manage the account and schedule transfers, for example, to be sent automatically, such as a set amount at a certain time each month.

[0319] Specific examples

[0320] User registration and account linking: Parents install the application and create an account. Then, they create a child account and link it to the parent's account.

[0321] Distributing pocket money: A parent uses the application to send their child 500 yen in electronic money, enters the amount, and submits it. The server then credits the amount to the child's account.

[0322] Checking purchase history: When a child spends 200 yen at a stationery store, the information is sent to the server and stored in a database. Parents can check this information in the application.

[0323] Alert settings: If a parent sets the option to "send an alert if more than 500 yen is spent at once," and their child makes a purchase of 600 yen, an alert will be sent to the parent's device.

[0324] Prompt Sentence Examples

[0325] Remittance: Parent sends 500 yen to child.

[0326] Purchase history: A child spends 200 yen at the stationery store at school.

[0327] Alert: If a parent sets up a notification for purchases over 500 yen, a notification will be sent when the child makes a purchase of 600 yen.

[0328] The present invention enables parents to manage their children's finances efficiently and safely, and enables children to acquire a sound financial sense.

[0329] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[0330] Step 1:

[0331] The application is installed on the parent's mobile information terminal and a new user registration is performed.

[0332] Input: Parent's personal information, account creation information

[0333] Output: New user ID, parent account information

[0334] Specific behavior:

[0335] Parent downloads and launches the application.

[0336] The parent enters personal information (name, email address, password, etc.) and presses the account creation button.

[0337] The server stores the received information in a database and generates a new user ID.

[0338] Step 2:

[0339] Parents create accounts for their children and link them to their own accounts.

[0340] Input: Child's personal information, link information

[0341] Output: Child's new user ID, parent and child link information

[0342] Specific behavior:

[0343] A parent selects the "Create a Child Account" feature on the application.

[0344] Parents enter their child's personal information and press the link button.

[0345] The server stores the received information in a database and generates a new child ID.

[0346] The server links the parent's account with the child's account.

[0347] Step 3:

[0348] Parents use the application to transfer money to their children's accounts.

[0349] Input: Transfer amount, child's account ID

[0350] Output: Transfer completion notification, updated balance

[0351] Specific behavior:

[0352] The parent selects the transfer function in the application and enters the amount to transfer.

[0353] When the parent presses the send button, the terminal sends a remittance request to the server.

[0354] The server adds the transfer amount to the child's account and updates the database.

[0355] The server sends a notification of the completion of the remittance to the child's device.

[0356] Step 4:

[0357] The child makes the payment using an electronic payment service such as PayPay.

[0358] Input: payment amount, payment store information

[0359] Output: Purchase history, updated balance

[0360] Specific behavior:

[0361] The child makes an electronic payment at the store and completes the payment.

[0362] The child's device sends payment information (payment amount, store information) to the server.

[0363] The server stores the information in a database and updates the child's account balance.

[0364] Step 5:

[0365] Parents can view their child's purchase history in the app.

[0366] Input: Parent account ID, Child account ID

[0367] Output: Purchase history, purchase details

[0368] Specific behavior:

[0369] A parent selects the "Purchase History" feature in the application.

[0370] The server receives the parent's request and retrieves the child's purchase history from the database.

[0371] The server sends the acquired purchase history to the parent's device.

[0372] Step 6:

[0373] Parents can set alerts based on specific conditions.

[0374] Input: Warning condition (e.g., payment above a certain amount)

[0375] Output: Set warning conditions

[0376] Specific behavior:

[0377] Parents select the "Warning Settings" feature in the application.

[0378] The parent enters the warning conditions and presses the setting button.

[0379] The server stores the received alert conditions in a database.

[0380] Step 7:

[0381] The server monitors the purchase history based on the set conditions and sends an alert when the conditions are met.

[0382] Input: purchase history, warning conditions

[0383] Output: Warning notice

[0384] Specific behavior:

[0385] The server periodically checks the purchase history in the database.

[0386] If the set warning conditions are met, a warning notification will be sent to the parent device.

[0387] Step 8:

[0388] Parents schedule transfers to their children's accounts.

[0389] Input: remittance amount, schedule information (date, time, cycle)

[0390] Output: Scheduled transfer information

[0391] Specific behavior:

[0392] The parent selects the transfer schedule feature in the application.

[0393] The parent enters the transfer amount and schedule information and presses the setting button.

[0394] The server stores the received schedule information in a database.

[0395] The remittance will be processed automatically at the set date and time.

[0396] Furthermore, an emotion engine that estimates the user's emotion may be combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59 and perform identification processing using the user's emotion.

[0397] The present invention is a system that allows parents to give their children electronic pocket money and manage how it is spent, and further combines it with an emotion engine that recognizes the user's emotions and provides various notifications and advice based on that data. Specific processing content based on an embodiment of the present invention will be described below.

[0398] System Configuration

[0399] The system consists of the following elements:

[0400] 1. Smartphone apps (devices) for parents and children

[0401] 2. Central Management Server (Server)

[0402] 3. Emotion Engine

[0403] User registration and account linking

[0404] 1. The user (parent) installs the app and opens the new user registration screen.

[0405] 2. The user (parent) enters information such as name, email address, and password.

[0406] 3. The terminal sends the entered information to the server.

[0407] 4. The server receives the information, registers the new user in the database, generates an account ID, and returns it to the device.

[0408] 5. The user (parent) selects the option to create a child account and enters the child's name and user ID.

[0409] 6. The device sends a child account creation request to the server.

[0410] 7. The server receives the request, creates a child account, links it to the parent account, generates a child account ID, and returns it to the device.

[0411] Distribution of pocket money

[0412] 1. The user (parent) logs into the app and selects the option to send pocket money.

[0413] 2. The user (parent) enters the amount to be transferred.

[0414] 3. The device sends a transfer request to the server, which includes the parent's account ID, the child's account ID, and the transfer amount.

[0415] 4. The server receives the transfer request, checks the parent and child account information in the database, adds the transfer amount to the child's account, updates the database, and returns a successful transfer notification to notify the child's account of the update.

[0416] 5. The device receives a notification from the server and notifies the child's app that a new transfer has been made.

[0417] Check your purchase history

[0418] 1. The user (child) makes a purchase using PayPay. Payments are made through the PayPay app.

[0419] 2. Once the payment is complete, the terminal sends the payment information (store name, amount, date and time, etc.) to the server.

[0420] 3. The server receives the payment information and stores it in a database, including the child's account ID.

[0421] 4. The user (parent) selects the option to view their child's purchase history within the app.

[0422] 5. The device sends a history request to the server.

[0423] 6. The server retrieves the child's latest payment information from the database and sends it back to the parent's device.

[0424] 7. The device displays the received history information in the parent app.

[0425] Alert Settings

[0426] 1. The user (parent) selects the alert setting option and enters a specific condition (e.g., a single payment of 500 yen or more).

[0427] 2. The device sends an alert setting request to the server, including the parent account ID and the alert conditions.

[0428] 3. The server receives the alert conditions and stores them in a database.

[0429] 4. As the server saves each payment entry to the database, it checks it against pre-defined alert conditions.

[0430] 5. When the condition is met (e.g., when the child spends more than 500 yen), the server sends an alert notification to the parent's device.

[0431] 6. The device receives the alert notification and displays the alert content in the parent's app.

[0432] Introducing the Emotion Engine

[0433] The terminal and server are equipped with an emotion engine that collects and analyzes the emotion data of users (parents and children).

[0434] Based on the emotional data obtained by the emotion engine, an alert is sent to the parent's device when certain conditions are met.

[0435] The server uses emotional data to analyze purchase history and provide appropriate advice and alerts to parents.

[0436] Specific examples

[0437] User registration and account linking

[0438] The user (parent) installed the app and created an account. Then, the user (parent) created a child account and linked the two accounts.

[0439] The server stored the parent and child information in a database.

[0440] Distribution of pocket money

[0441] The user (parent) accessed the app to send their child 500 yen in pocket money, entered the amount, and sent it.

[0442] The server added 500 yen to the child's account and sent the child a notification of the transfer.

[0443] Check your purchase history

[0444] The user (child) paid 200 yen with PayPay at a stationery store.

[0445] The server received this payment information and stored it in a database.

[0446] The user (parent) checked their child's most recent purchase history in the app and confirmed the payment at the stationery store.

[0447] Alert Settings

[0448] The user (parent) set it up so that an alert would be sent if their child spent more than 500 yen at one time.

[0449] A few days later, I spent 600 yen on my child's device to buy a toy.

[0450] When the server met the alert conditions, it sent a notification to the parent's device, and the user (parent) received the alert.

[0451] Examples of emotion engines

[0452] The user (child) was shopping at a toy store and the emotion engine recognized that the child was feeling very happy.

[0453] Based on this emotional data, the emotion engine notified the parents that their child had purchased an expensive item and was very happy.

[0454] Sarver offered some advice to parents: "If these kinds of expensive purchases are frequent, we recommend reconsidering your budget."

[0455] This system provides an environment where parents can manage their children's finances more transparently and with peace of mind, and children can safely use their pocket money without carrying cash. Furthermore, by combining it with an emotion engine, parents can receive monitoring and advice based on their children's emotional state, enabling them to provide more appropriate financial education.

[0456] The processing flow will be explained below.

[0457] User registration and account linking

[0458] Step 1:

[0459] The user (parent) installs the app and opens the new user registration screen.

[0460] Step 2:

[0461] The user (parent) enters information such as name, email address, and password.

[0462] Step 3:

[0463] The terminal transmits the input information to the server.

[0464] Step 4:

[0465] The server receives the information, registers the new user in the database, generates an account ID, and returns it to the device.

[0466] Step 5:

[0467] The user (parent) selects the option to create a child account.

[0468] Step 6:

[0469] The user (parent) enters the child's name and user ID.

[0470] Step 7:

[0471] The terminal sends a request to create a child account to the server.

[0472] Step 8:

[0473] The server receives the request, creates a child account, links it to the parent's account, generates a child account ID, and returns it to the device.

[0474] Distribution of pocket money

[0475] Step 1:

[0476] The user (parent) logs into the app and selects the option to transfer pocket money.

[0477] Step 2:

[0478] The user (parent) enters the remittance amount.

[0479] Step 3:

[0480] The device sends a transfer request to the server, which includes the parent's account ID, the child's account ID, and the transfer amount.

[0481] Step 4:

[0482] The server receives the transfer request and checks the parent and child account information in its database.

[0483] Step 5:

[0484] The server adds the transfer amount to the child's account and updates the database.

[0485] Step 6:

[0486] The server returns a successful transfer information and notifies the child account of the update.

[0487] Step 7:

[0488] The device receives a notification from the server and notifies the child's app that a new transfer has been made.

[0489] Check your purchase history

[0490] Step 1:

[0491] The user (child) makes purchases using PayPay. Payments are made through the app.

[0492] Step 2:

[0493] Once the payment is complete, the terminal sends the payment information (store name, amount, date and time, etc.) to the server.

[0494] Step 3:

[0495] The server receives the payment information and stores it in a database, including the child's account ID.

[0496] Step 4:

[0497] The user (parent) selects the option to view their child's purchase history within the app.

[0498] Step 5:

[0499] The terminal sends a history request to the server.

[0500] Step 6:

[0501] The server retrieves the child's latest payment information from the database and sends it back to the parent's device.

[0502] Step 7:

[0503] The device displays the received history information in the parent's app.

[0504] Alert Settings

[0505] Step 1:

[0506] The user (parent) selects the alert setting option and enters specific conditions (e.g., a single payment of 500 yen or more).

[0507] Step 2:

[0508] The device sends an alert setting request to the server, which includes the parent account ID and the alert conditions.

[0509] Step 3:

[0510] The server receives the alert conditions and stores them in a database.

[0511] Step 4:

[0512] As the server saves each payment entry to the database, it checks it against pre-defined alert conditions.

[0513] Step 5:

[0514] When a condition is met (e.g., when a child pays more than 500 yen), the server sends an alert notification to the parent's device.

[0515] Step 6:

[0516] The device receives an alert notification and displays the alert content in the parent's app.

[0517] Introducing the Emotion Engine

[0518] Step 1:

[0519] The terminal and the server are equipped with an emotion engine to collect emotion data from users (parents and children).

[0520] Step 2:

[0521] The emotion engine analyzes the user's facial expressions, voice, text input, etc. to recognize their current emotional state.

[0522] Step 3:

[0523] The terminal transmits the emotion data to the server.

[0524] Step 4:

[0525] The server receives the emotion data and stores it in a database.

[0526] Step 5:

[0527] The server analyzes purchase history and payment data based on emotional data and provides appropriate advice and alerts to parents.

[0528] Step 6:

[0529] The server sends an alert to the parent's device when a certain condition is met (for example, when a child makes an expensive purchase and is very happy).

[0530] Step 7:

[0531] The device receives an alert notification and displays the alert content in the parent's app.

[0532] Specific examples

[0533] Examples of emotion engines

[0534] Step 1:

[0535] A user (child) is shopping at a toy store, and the emotion engine recognizes that the child is feeling very happy.

[0536] Step 2:

[0537] The emotion engine sends information to the server based on this emotion data.

[0538] Step 3:

[0539] The server receives the emotion data and sends a notification to the parent's account.

[0540] Step 4:

[0541] The device will display a notification in the parent's app saying, "Your child has purchased an expensive item and is very happy."

[0542] Step 5:

[0543] The server offers parents advice: "If these kinds of expensive purchases are frequent, we recommend reconsidering your budget."

[0544] Example 2

[0545] Next, a description will be given of Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0546] Until now, parents have had limited means to manage their children's spending and purchasing history, and this lack of transparency and efficiency has made it difficult to understand children's emotions and spending trends in real time, making it difficult to provide appropriate financial education.

[0547] The specific processing by the specific processing unit 290 of the data processing device 12 in Example 2 is realized by the following means. In this invention, the server includes means for transferring digital currency from a parent's account to a child's account, means for storing the purchase history of the child's account on the server, means for displaying the child's purchase history on the parent's terminal, means for sending alerts based on conditions set by the parent, and means for collecting and analyzing user emotion data and notifying the user based on the results. This allows parents to manage their children's finances transparently and efficiently, and also allows them to understand their children's emotions and payment trends, making it possible to provide more appropriate financial education to their children.

[0548] "Parent Account" means an electronic account owned by a Parent that contains Personally Identifiable Information for managing and transferring Digital Currency.

[0549] A "child's account" is an electronic account owned by a child that contains personally identifiable information for the purpose of receiving digital currency from a parent and managing purchase history.

[0550] "Digital currency" is currency that exists in electronic form and is used for online transactions and transfers.

[0551] "Purchase History" means a history of payments made on a Child's account, including details such as the location, amount, date and time of the payment.

[0552] "Server" refers to a centralized management system for storing, processing, and managing data, and is a device that stores and manages user account information and purchase history.

[0553] "Device" refers to a device used by parents and children, such as a smartphone or tablet, that is capable of communication.

[0554] An "alert" refers to a notification or warning sent to a parent's device when certain conditions are met, such as to warn them about a large expenditure made by their child.

[0555] "Emotional data" refers to information indicative of a user's emotional state, and is data collected and analyzed using an emotion engine.

[0556] An "emotion engine" refers to technology that recognizes emotions from a user's facial expressions and behavior, and collects and analyzes the data.

[0557] "Notification" refers to the act of sending important information or alerts to a parent's device, and is a way for parents to keep track of their child's situation.

[0558] "Application program" refers to software that enables communication between parent and child devices, and generally refers to smartphone applications.

[0559] This invention is a system that allows parents to electronically give pocket money to their children and manage their child's spending. It also incorporates an emotion engine that recognizes the user's emotions in real time and provides notifications and advice based on those emotions. This system makes money management transparent and efficient for parents and children, and allows parents to understand their children's emotions and spending habits.

[0560] System Configuration

[0561] The system consists of the following elements:

[0562] 1. Smartphone apps (devices) used by parents and children

[0563] 2. Central Management Server (Server)

[0564] 3. Emotion Engine (emotion data collection and analysis system)

[0565] User registration and account linking

[0566] 1. The user (parent) installs the app on their smartphone and opens the new user registration screen.

[0567] 2. The user (parent) enters information such as name, email address, and password.

[0568] 3. The terminal sends the entered information to a central management server (for example, AWS (registered trademark) EC2).

[0569] 4. The server receives the information, registers the new user in a database (e.g., MySQL), generates an account ID, and returns it to the device.

[0570] 5. The user (parent) selects the Create Child Account option and enters the child's name and user ID.

[0571] 6. The device sends a child account creation request to the server.

[0572] 7. The server receives the request, creates a child account, links it to the parent account, generates a child account ID, and returns it to the device.

[0573] Distribution of pocket money

[0574] 1. The user (parent) logs into the app and selects the option to send pocket money.

[0575] 2. The user (parent) enters the amount to be transferred.

[0576] 3. The device sends a transfer request to the server, which includes the parent's account ID, the child's account ID, and the transfer amount.

[0577] 4. The server receives the transfer request, checks the parent and child account information in the database, adds the transfer amount to the child's account, and updates the database.

[0578] 5. The server returns a successful transfer information and notifies the child account of the update.

[0579] 6. The device receives a notification from the server and notifies the child's app that a new transfer has been made.

[0580] Check your purchase history

[0581] 1. The user (child) makes a purchase using an electronic payment system such as PayPay. PayPay payments are made through the app.

[0582] 2. Once the payment is complete, the terminal sends the payment information (store name, amount, date and time, etc.) to the server.

[0583] 3. The server receives the payment information and stores it in a database, including the child's account ID.

[0584] 4. The user (parent) selects the option to view their child's purchase history within the app.

[0585] 5. The device sends a history request to the server.

[0586] 6. The server retrieves the child's latest payment information from the database and sends it back to the parent's device.

[0587] 7. The device displays the received history information in the parent app.

[0588] Alert Settings

[0589] 1. The user (parent) selects the alert setting option and enters a specific condition (e.g., a single payment of 500 yen or more).

[0590] 2. The device sends an alert setting request to the server, including the parent account ID and the alert conditions.

[0591] 3. The server receives the alert conditions and stores them in a database.

[0592] 4. As the server saves each payment entry to the database, it checks it against pre-defined alert conditions.

[0593] 5. When the condition is met (e.g., when the child spends more than 500 yen), the server sends an alert notification to the parent's device.

[0594] 6. The device receives the alert notification and displays the alert content in the parent's app.

[0595] Introducing the Emotion Engine

[0596] 1. The terminal and the server use an emotion engine (e.g., Microsoft® Azure® Emotion API) to collect emotion data from users (parents and children).

[0597] 2. The device sends the acquired emotion data to the server.

[0598] 3. The server receives the emotion data and stores it in a database.

[0599] 4. The server analyzes the emotion data for specific conditions (e.g., high levels of joy or anger).

[0600] 5. Based on the analysis results, the server sends appropriate advice and alerts to the parent's device.

[0601] 6. The device receives a notification and displays advice or alert details in the parent's app.

[0602] Examples of concrete examples and prompts

[0603] Specific examples

[0604] The user (parent) installed the app and created an account, then created a child account and linked the two accounts.

[0605] The user (parent) accessed the app, entered the amount, and sent it to send 500 yen pocket money to their child.

[0606] The user (child) paid 200 yen with PayPay at a stationery store.

[0607] The server received this payment information and stored it in a database.

[0608] The user (parent) checked their child's most recent purchase history in the app and confirmed the payment at the stationery store.

[0609] The user (parent) set it up so that an alert would be sent if their child spent more than 500 yen at one time.

[0610] A few days later, the user (child) uses 600 yen to buy a toy.

[0611] When the server met the alert conditions, it sent a notification to the parent's device, and the user (parent) received the alert.

[0612] The user (child) was shopping at a toy store and the emotion engine recognized that the child was feeling very happy.

[0613] Sarver offered some advice to parents: "If these kinds of expensive purchases are frequent, we recommend reconsidering your budget."

[0614] Prompt Sentence Examples

[0615] User Registration and Account Linking:

[0616] "Parents open the new user registration screen and create an account by entering their name, email address, and password. They then enter their child's name and user ID to create and link their child's account."

[0617] Pocket money distribution:

[0618] "Parents simply log into the app, select the option to send pocket money, enter the amount to send and send."

[0619] Check your purchase history:

[0620] "A child pays 200 yen at a stationery store with PayPay, and the parent checks the purchase history on the app."

[0621] Alert Settings:

[0622] "Parents can set up an alert to be sent if more than 500 yen is spent in a single transaction."

[0623] Introducing the Emotion Engine:

[0624] "When a child is shopping in a toy store, the emotion engine recognizes the child's joy and notifies the parent."

[0625] This invention allows parents to manage their children's money transparently and efficiently, and by understanding their children's emotions and spending habits, they can provide them with appropriate financial education, allowing the whole family to manage their pocket money with greater peace of mind.

[0626] The flow of the identification process in the second embodiment will be described with reference to FIG.

[0627] User registration and account linking

[0628] Step 1:

[0629] The user (parent) installs the app on their smartphone and opens the new user registration screen. Input: Parent's personal information (name, email address, password). Output: A new user registration request is generated on the device.

[0630] Step 2:

[0631] The device sends the entered information to a central server. Input: New user registration request including parent's personal information. Output: Data sent to the server.

[0632] Step 3:

[0633] The server receives the information and registers the new user in the database. Input: New user registration request. Output: New account ID generated and registered.

[0634] Step 4:

[0635] The server returns the generated account ID to the terminal. Input: New account ID. Output: Return of account ID.

[0636] Step 5:

[0637] The user (parent) selects the Create Child Account option and enters the child's name and user ID. Input: Child's personal information. Output: A child account creation request is generated on the device.

[0638] Step 6:

[0639] The device sends a request to the server to create a child account. Input: The request, including the child's personal information. Output: The data sent to the server.

[0640] Step 7:

[0641] The server receives the request, creates a child account, and associates it with the parent's account. Input: Child account creation request. Output: New child account ID is generated and registered in the database.

[0642] Step 8:

[0643] The server returns the generated child account ID to the device. Input: New child account ID. Output: Return of account ID.

[0644] Distribution of pocket money

[0645] Step 1:

[0646] The user (parent) logs in to the app and selects the option to transfer pocket money. Input: User authentication information (login ID, password). Output: Notification of successful login authentication.

[0647] Step 2:

[0648] The user (parent) inputs the amount to be transferred. Input: Amount to be transferred. Output: A transfer request is generated on the terminal.

[0649] Step 3:

[0650] The device sends a transfer request to the server. Input: A request containing the parent's account ID, the child's account ID, and the amount to transfer. Output: The data sent to the server.

[0651] Step 4:

[0652] The server receives the transfer request and checks the parent and child account information in the database. Input: Transfer request. Output: Start of the process to update the transfer record in the database.

[0653] Step 5:

[0654] The server adds the transfer amount to the child's account and updates the database. Input: Parent and child account information and transfer amount. Output: Database update.

[0655] Step 6:

[0656] The server returns a successful transfer information to the terminal and notifies the update of the child account. Input: Successful transfer information. Output: Notification of transfer completion sent to the terminal.

[0657] Step 7:

[0658] The device receives a notification from the server and notifies the child's app that a new transfer has been made. Input: Notification of transfer completion. Output: Notification displayed in the child's app.

[0659] Check your purchase history

[0660] Step 1:

[0661] The user (child) makes a purchase using an electronic payment system such as PayPay. Input: PayPay account information and payment information. Output: Receipt information after payment is completed.

[0662] Step 2:

[0663] Once the payment is complete, the terminal sends the payment information to the server. Input: Payment information such as store name, amount, date and time. Output: Data sent to the server.

[0664] Step 3:

[0665] The server receives the payment information and stores it in a database. Input: Payment information. Output: Payment information stored in a database.

[0666] Step 4:

[0667] User (parent) selects option within app to review child's purchase history. Input: Purchase history review request. Output: Request generated on device.

[0668] Step 5:

[0669] The device sends a history request to the server. Input: Purchase history confirmation request. Output: Data sent to the server.

[0670] Step 6:

[0671] The server retrieves the child's latest payment information from the database and sends it back to the parent's device. Input: Purchase history confirmation request. Output: Extraction and return of purchase history data.

[0672] Step 7:

[0673] The device displays the received history information in the parent app. Input: Purchase history data. Output: Purchase history displayed in the parent app.

[0674] Alert Settings

[0675] Step 1:

[0676] The user (parent) selects the alert setting option and enters the specific condition. Input: Alert condition (e.g., single payment of 500 yen or more). Output: An alert setting request is generated on the terminal.

[0677] Step 2:

[0678] The device sends an alert setting request to the server. Input: Parent account ID, request containing alert conditions. Output: Data sent to the server.

[0679] Step 3:

[0680] The server receives the alert conditions and stores them in the database. Input: Alert configuration request. Output: Alert conditions stored in the database.

[0681] Step 4:

[0682] When the server saves each payment information to the database, it checks it against the pre-defined alert conditions. Input: Payment information and alert conditions. Output: Alert condition check results.

[0683] Step 5:

[0684] The server sends an alert notification to the parent device when the condition is met. Input: Payment information that meets the condition. Output: Sending an alert notification.

[0685] Step 6:

[0686] The device receives the alert notification and displays the alert content in the parent app. Input: Alert notification. Output: Alert content displayed in the app.

[0687] Introducing the Emotion Engine

[0688] Step 1:

[0689] The device and server use an emotion engine to collect user emotion data. Input: User's facial expression, voice, and behavior data. Output: Acquisition of emotion data.

[0690] Step 2:

[0691] The device sends the acquired emotion data to the server. Input: Emotion data. Output: Data sent to the server.

[0692] Step 3:

[0693] The server receives the emotion data and stores it in a database. Input: Emotion data. Output: Emotion data stored in a database.

[0694] Step 4:

[0695] The server analyzes specific conditions based on emotion data. Input: Emotion data. Output: Generates analysis results.

[0696] Step 5:

[0697] The server sends appropriate advice or alerts to the parent device based on the analysis results. Input: Analysis results. Output: Sending advice or alerts.

[0698] Step 6:

[0699] The device receives the notification and displays the advice or alert content in the parent app. Input: Advice or alert notification. Output: Advice or alert content displayed in the app.

[0700] (Application example 2)

[0701] Next, a description will be given of Application Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0702] Today's parents need a way to efficiently monitor their children's financial management and spending habits. However, while many systems on the market can electronically transfer pocket money and manage spending histories, they lack the functionality to provide advice and notifications based on the child's emotional state. As a result, parents find it difficult to consider not only their spending habits but also their children's emotions when providing sound financial education. This means that there is a need to solve the problem of children not being able to learn appropriate financial management in an environment that is not conducive to financial management.

[0703] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 2 is realized by the following means.

[0704] In this invention, the server includes means for transferring electronic money from the parent's account to the child's account, means for storing the purchase history of the child's account on the server, means for displaying the child's purchase history on the parent's terminal, means for sending alerts based on conditions set by the parent, and means for analyzing emotional data and providing notifications and advice based on that data. This allows parents to not only efficiently manage their children's finances, but also receive appropriate advice and notifications based on their children's emotional state.

[0705] "Parent Account" means an electronic money account managed by a parent and used to transfer electronic pocket money to a child.

[0706] A "child's account" is an electronic money account managed by a child, and is used to receive and use pocket money sent by a parent.

[0707] "Electronic money" is a digital form of currency that can be used via the Internet or dedicated terminals, and is used to purchase goods and services in the same way as cash.

[0708] "Purchase history" is a record of payments made by a child, and includes information such as the date and time of the payment, the amount, and the name of the store.

[0709] "Server" refers to a computer system that stores, processes, and manages data and serves as the central control for this invention.

[0710] A "terminal" is an electronic device that a user operates, and includes smartphones, tablets, computers, etc.

[0711] An "alert" is a feature that notifies users when a set condition is met, and issues a warning based on a specific action or condition.

[0712] "Emotion data" is digital information that represents the user's emotional state and is collected and analyzed by the emotion engine.

[0713] An "emotion engine" is a software system that recognizes a user's emotional state and collects and analyzes it as data.

[0714] A "notification" is a message or warning sent by the system to a user based on a specific condition.

[0715] "Advice" is a recommendation or advice provided based on emotional data and spending history, and is useful information for parents to support their children in managing their finances.

[0716] This invention is a system that allows parents to give their children electronic pocket money and manage how it is spent, and it also combines an emotion engine that recognizes the user's emotions and provides various notifications and advice based on that data. Specific processing content based on an embodiment of the present invention will be described below.

[0717] System Configuration

[0718] The system consists of the following elements:

[0719] 1. Parent and child devices (smartphones, tablets, etc.)

[0720] 2. Central Management Server

[0721] 3. Emotion Engine

[0722] User registration and account linking

[0723] The parent's device installs the application and opens the new user registration screen. The parent enters information such as name, email address, and password, and the device sends this information to the server. The server receives this information and registers the new user in its database. The parent then selects the option to create a child account and enters the child's name and user ID. The device sends this information to the server, and the server links the parent and child accounts.

[0724] Distribution of pocket money

[0725] The parent logs into the application and selects the option to transfer pocket money. The transfer amount is entered and the device sends a transfer request to the server. The server receives the transfer request and checks the parent and child's account information in the database. The server adds the transfer amount to the child's account and updates the database. The parent's device is notified of the successful transfer and notifies the child's account of the update.

[0726] Check your purchase history

[0727] When a child uses a device to make a purchase using electronic money, payment information (store name, amount, date and time, etc.) is sent from the device to the server. The server receives this payment information and stores it in a database. Parents can check their child's purchase history within the application, and the server sends the latest payment information back to the parent's device.

[0728] Alert Settings

[0729] The parent device selects the alert setting option and enters a specific condition (e.g., a single payment of 500 yen or more). The device sends an alert setting request to the server, which stores the alert condition in a database. When the child makes a payment, the server checks the payment information and sends an alert notification to the parent device if the condition is met.

[0730] Introducing the Emotion Engine

[0731] The device and server are equipped with an emotion engine that collects and analyzes the emotion data of users (parents and children). The server uses the emotion data to analyze purchase history and provide appropriate advice and alerts to parents.

[0732] Specific examples

[0733] User Registration and Account Linking:

[0734] The parent installed the app and created an account, then created a child account and linked the two accounts.

[0735] The server stored the parent and child information in a database.

[0736] Pocket money distribution:

[0737] A parent accessed the app to send their child 500 yen in pocket money, entered the amount, and sent it.

[0738] The server added 500 yen to the child's account and sent the child a notification of the transfer.

[0739] Check your purchase history:

[0740] My child paid 200 yen at a stationery store using electronic money.

[0741] The server received this payment information and stored it in a database.

[0742] The parent checked their child's recent purchase history in the app and confirmed the payment at the stationery store.

[0743] Alert Settings:

[0744] Parents set up an alert to be sent if their children spent more than 500 yen at one time.

[0745] A few days later, my child spent 600 yen on the device to buy a toy.

[0746] When the server met the alert conditions, it sent a notification to the parent's device, and the parent received the alert.

[0747] Examples of emotion engines:

[0748] A child is shopping at a toy store and the emotion engine recognizes that the child is feeling very happy.

[0749] The server notified the parents that their child had purchased an expensive item and was very happy.

[0750] Sarver offered some advice to parents: "If these kinds of expensive purchases are frequent, we recommend reconsidering your budget."

[0751] Prompt Sentence Examples

[0752] "A user registers as a parent (parent1), links a child (child1), and then sends 1,000 yen in pocket money. When the child buys a toy for 600 yen and feels very happy at the time, simulate using Python what kind of notification will be sent to the parent."

[0753] By implementing the invention in this way, parents can not only manage their children's finances efficiently, but also receive appropriate advice and notifications based on emotional data.

[0754] The flow of the specific processing in the application example 2 will be described with reference to FIG.

[0755] Step 1:

[0756] The user (parent) installs the application on their device and opens the new user registration screen. The parent enters information such as their name, email address, and password. The entered information is sent to the server, which receives it and registers it as the parent's account in its database. The parent then selects the option to create a child account and enters the child's name and user ID. This causes the device to send a request to create a child account to the server.

[0757] Input: Parent's name, email address, password, child's name, user ID

[0758] Output: Parent and child account registration in database, account linking

[0759] Step 2:

[0760] The server receives the child account creation request and links the parent and child accounts. It generates account IDs for both the parent and child and stores the linking information in the database. It notifies the device that the parent and child accounts have been successfully linked.

[0761] Input: Child account creation request

[0762] Output: Account linking information saved in the database, notification of link completion

[0763] Step 3:

[0764] The user (parent) logs into the application on their device and selects the option to transfer pocket money. The parent enters the amount to transfer and the device sends this transfer request to the server. The server receives the transfer request and checks the parent and child account information in the database. It adds the transfer amount to the child's account and updates the database.

[0765] Input: Transfer amount, parent and child account information

[0766] Output: Transfer amount added to child account, database updated

[0767] Step 4:

[0768] The server notifies the parent's device of the successful transfer and updates the child's account. The parent's device receives this notification and displays the new transfer.

[0769] Input: Remittance success information

[0770] Output: Remittance notification to parent and child devices

[0771] Step 5:

[0772] When purchasing a product, the child's device pays with electronic money. Payment information (store name, amount, date and time, etc.) is sent from the device to the server. The server receives the payment information and stores it in a database. The payment information also includes automatically generated emotion data.

[0773] Input: Payment information (store name, amount, date and time, etc.), emotional data

[0774] Output: Payment information saved in database

[0775] Step 6:

[0776] The parent selects the option to check the purchase history within the application and retrieves the child's latest payment information from the server. The server searches the database for the relevant payment information and sends it back to the parent's device. The parent's device receives this information and displays the purchase history.

[0777] Input: Purchase history request

[0778] Output: Provides up-to-date payment information and displays purchase history

[0779] Step 7:

[0780] The parent device selects the alert setting option and enters a specific condition (e.g., a single payment of 500 yen or more). The device sends this alert setting request to the server, which stores this alert condition in its database.

[0781] Input: Alert Condition

[0782] Output: Alert conditions saved in database

[0783] Step 8:

[0784] When the server saves each payment in the database, it checks it against pre-defined alert conditions, and if a condition is met (e.g., when a child spends more than 500 yen), it sends an alert notification to the parent's device.

[0785] Input: Payment information, Alert conditions

[0786] Output: Alert notification when the condition is met

[0787] Step 9:

[0788] The device and server are equipped with an emotion engine that collects and analyzes the user's emotion data. The server uses the emotion data to analyze purchase history and provide appropriate advice and alerts to parents.

[0789] Input: Emotional data, purchase history

[0790] Output: Providing advice and alerts based on sentiment analysis

[0791] Prompt Sentence Examples

[0792] "A user registers as a parent (parent1), links a child (child1), and then sends 1,000 yen in pocket money. When the child buys a toy for 600 yen and feels very happy at the time, simulate using Python what kind of notification will be sent to the parent."

[0793] The specific processing unit 290 transmits the result of the specific processing to the smart device 14. In the smart device 14, the control unit 46A causes the output device 40 to output the result of the specific processing. The microphone 38B acquires audio indicating a user input regarding the result of the specific processing. The control unit 46A transmits audio data indicating the user input acquired by the microphone 38B to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the audio data.

[0794] The data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of the data generation model 58 is ChatGPT (registered trademark) (Internet search engine).<URL: https: / / openai.com / blog / chatgpt> ), Gemini (registered trademark) (Internet search <url: https: gemini.google.com ?hl="ja">) and other generation AIs. The data generation model 58 is obtained by performing deep learning on a neural network. A prompt including an instruction is input to the data generation model 58, and inference data such as voice data indicating voice, text data indicating text, and image data indicating an image is also input. The data generation model 58 performs inference on the input inference data in accordance with the instruction indicated by the prompt, and outputs the inference result in a data format such as voice data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[0795] In the above embodiment, an example in which the specific process is performed by the data processing device 12 has been given, but the technology of the present disclosure is not limited to this, and the specific process may be performed by the smart device 14.

[0796] [Second embodiment]

[0797] FIG. 3 shows an example of the configuration of a data processing system 210 according to the second embodiment.

[0798] 3, the data processing system 210 includes the data processing device 12 and smart glasses 214. An example of the data processing device 12 is a server.

[0799] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[0800] The smart glasses 214 include a computer 36, a microphone 238, a speaker 240, a camera 42, and a communication I / F 44. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The microphone 238, the speaker 240, and the camera 42 are also connected to the bus 52.

[0801] The microphone 238 receives instructions and the like from the user 20 by receiving voice uttered by the user 20. The microphone 238 captures the voice uttered by the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio in accordance with instructions from the processor 46.

[0802] Camera 42 is a small digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor, and captures images of the surroundings of user 20 (for example, an imaging range defined by an angle of view equivalent to the field of vision of a typical healthy person).

[0803] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 control the exchange of various information between the processor 46 and the processor 28 via the network 54. The exchange of various information between the processor 46 and the processor 28 using the communication I / Fs 44 and 26 is carried out in a secure state.

[0804] Fig. 4 shows an example of the main functions of the data processing device 12 and the smart glasses 214. As shown in Fig. 4, in the data processing device 12, a specific process is performed by the processor 28. A specific process program 56 is stored in the storage 32.

[0805] The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific processing is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[0806] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[0807] In the smart glasses 214, the reception output process is performed by the processor 46. A reception output program 60 is stored in the storage 50. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[0808] Next, a description will be given of the identification process performed by the identification processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as the "server" and the smart glasses 214 will be referred to as the "terminal."

[0809] The present invention is a system for parents to give electronic pocket money to their children and manage how the money is spent. Specific processing contents based on an embodiment of the present invention will be described below.

[0810] System Configuration

[0811] The system consists of the following elements:

[0812] 1. Smartphone apps (devices) for parents and children

[0813] 2. Central Management Server (Server)

[0814] User registration and account linking

[0815] 1. The user (parent) installs the app and registers as a new user.

[0816] 2. The user (parent) creates an account for the child and links it to their own account.

[0817] 3. The server stores the parent and child account information in a database.

[0818] Distribution of pocket money

[0819] 1. The user (parent) accesses the app and enters the amount to transfer to their child's account.

[0820] 2. The terminal sends a remittance request to the server.

[0821] 3. The server receives the request and credits the specified amount to the child's account.

[0822] 4. Your child's device will notify you of a new transfer.

[0823] Check your purchase history

[0824] 1. When a user (child) makes a payment with PayPay, the terminal sends the payment information to the server.

[0825] 2. The server stores the payment information in a database.

[0826] 3. Users (parents) can check their children's purchase history in real time through the app.

[0827] 4. The parent's device will notify them of their latest purchase history.

[0828] Alert Settings

[0829] 1. The user (parent) sets up alerts in the app based on specific usage conditions (e.g., when payments exceed a certain amount).

[0830] 2. The server monitors the purchase history based on the set conditions.

[0831] 3. If the condition is met, the server sends an alert to the parent device.

[0832] 4. The parent's device notifies the parent of the alert and displays detailed information.

[0833] Specific examples

[0834] User registration and account linking

[0835] The user (parent) installed the app and created an account. Then, the user (parent) created a child account and linked the two accounts.

[0836] The server stored the parent and child information in a database.

[0837] Distribution of pocket money

[0838] The user (parent) accessed the app to send their child 500 yen in pocket money, entered the amount, and sent it.

[0839] The server added 500 yen to the child's account and sent the child a notification of the transfer.

[0840] Check your purchase history

[0841] The user (child) paid 200 yen with PayPay at a stationery store.

[0842] The server received this payment information and stored it in a database.

[0843] The user (parent) checked their child's most recent purchase history in the app and confirmed the payment at the stationery store.

[0844] Alert Settings

[0845] The user (parent) set it up so that an alert would be sent if their child spent more than 500 yen at one time.

[0846] A few days later, I spent 600 yen on my child's device to buy a toy.

[0847] When the server met the alert conditions, it sent a notification to the parent's device, and the user (parent) received the alert.

[0848] This system provides parents with a more transparent and secure environment for managing their children's finances, and allows children to safely use their pocket money without having to carry cash.

[0849] The processing flow will be explained below.

[0850] User registration and account linking

[0851] Step 1:

[0852] The user (parent) installs the app and opens the new user registration screen.

[0853] The user (parent) enters information such as name, email address, and password.

[0854] Step 2:

[0855] The terminal transmits the input information to the server.

[0856] Step 3:

[0857] The server receives the information and registers the new user in its database.

[0858] The server generates an account ID and returns it to the device.

[0859] Step 4:

[0860] The user (parent) selects the option to create a child account.

[0861] The user (parent) enters the child's name and user ID.

[0862] Step 5:

[0863] The terminal sends a request to create a child account to the server.

[0864] Step 6:

[0865] The server receives the request, creates a child account, and associates it with the parent account.

[0866] The server generates a child account ID and returns it to the device.

[0867] Distribution of pocket money

[0868] Step 1:

[0869] The user (parent) logs into the app and selects the option to transfer pocket money.

[0870] The user (parent) enters the remittance amount.

[0871] Step 2:

[0872] The device sends a transfer request to the server, which includes the parent's account ID, the child's account ID, and the transfer amount.

[0873] Step 3:

[0874] The server receives the transfer request and checks the parent and child account information in its database.

[0875] The server adds the transfer amount to the child's account and updates the database.

[0876] The server returns a successful transfer information and notifies the child account of the update.

[0877] Step 4:

[0878] The device receives a notification from the server and notifies the child's app that a new transfer has been made.

[0879] Check your purchase history

[0880] Step 1:

[0881] The user (child) makes purchases using PayPay. Payments are made through the app.

[0882] Step 2:

[0883] Once the payment is complete, the terminal sends the payment information (store name, amount, date and time, etc.) to the server.

[0884] Step 3:

[0885] The server receives the payment information and stores it in a database, including the child's account ID.

[0886] Step 4:

[0887] The user (parent) selects the option to view their child's purchase history within the app.

[0888] Step 5:

[0889] The terminal sends a history request to the server.

[0890] Step 6:

[0891] The server retrieves the child's latest payment information from the database and sends it back to the parent's device.

[0892] Step 7:

[0893] The device displays the received history information in the parent's app.

[0894] Alert Settings

[0895] Step 1:

[0896] The user (parent) selects the alert setting option and enters specific conditions (e.g., a single payment of 500 yen or more).

[0897] Step 2:

[0898] The device sends an alert setting request to the server, which includes the parent account ID and the alert conditions.

[0899] Step 3:

[0900] The server receives the alert conditions and stores them in a database.

[0901] Step 4:

[0902] As the server saves each payment entry to the database, it checks it against pre-defined alert conditions.

[0903] Step 5:

[0904] When a condition is met (e.g., when a child pays more than 500 yen), the server sends an alert notification to the parent's device.

[0905] Step 6:

[0906] The device receives an alert notification and displays the alert content in the parent's app.

[0907] Example 1

[0908] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[0909] Today's children are increasingly using electronic money instead of carrying cash, but to make it easier for parents to manage their children's finances, a transparent and safe system is needed. It is also desirable for parents to monitor their children's spending in real time and set alerts as necessary. However, current systems do not adequately provide such functionality.

[0910] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[0911] In this invention, the server includes means for transferring electronic money from a parent's account to a child's account, means for storing the purchase history of the child's account on the server, means for displaying the child's purchase history on the parent's terminal, means for sending alerts based on conditions set by the parent, means for storing the parent and child's account information in a database, means for sending a remittance request to the server using HTTPS, and means for the server to send a remittance notification via a push notification API. This allows parents to keep track of their child's financial management in real time and receive appropriate alerts.

[0912] "Parent Account" means an account used by a parent to transfer and manage electronic money to a child.

[0913] A "child's account" is an account used by a child to receive electronic money transferred from a parent and use it for payments, etc.

[0914] "Electronic money" refers to currency exchanged electronically in place of cash, and is used for online or offline payments.

[0915] A "transfer request" is a request to transfer electronic money from a parent's account to a child's account.

[0916] A "parent's device" is an electronic device such as a smartphone or tablet used by the parent to transfer electronic money and check purchase history.

[0917] A "child's device" is an electronic device such as a smartphone or tablet used by a child, which is used to make payments using electronic money.

[0918] A "server" is a central management system that receives requests from multiple terminals and stores and processes data.

[0919] "Database" refers to a system for storing and managing data such as parent and child account information and purchase history.

[0920] "HTTPS" is a communication protocol for encrypting and sending data over the Internet, enabling secure data transmission.

[0921] "Push notifications" are notifications that are sent in real time from a server to a device, and are used to instantly inform users of important information such as money transfers, purchase history, and alerts.

[0922] MODE FOR CARRYING OUT THE INVENTION

[0923] The present invention is a system that allows parents to give electronic pocket money to their children and manage how that money is spent. Specific processing details of the present invention will be described below.

[0924] System Configuration

[0925] The system consists of the following elements:

[0926] 1. Smartphone apps (devices) for parents and children

[0927] 2. Central Management Server (Server)

[0928] 3. Database System

[0929] 4. Communication Protocol (HTTPS)

[0930] 5. Push notification services

[0931] User registration and account linking

[0932] The user (parent) installs a dedicated app on their smartphone.

[0933] Hardware used: Smartphone (e.g. iPhone, Android smartphone)

[0934] Software used: Dedicated app (e.g. PocketMoneyApp)

[0935] Parents launch the app and enter their name, email address, and password to register.

[0936] Parents then enter their child's information (name, age) to create an account for their child and link it to their own account.

[0937] The server receives this information and stores it in a database (e.g. MySQL).

[0938] Distribution of pocket money

[0939] The user (parent) accesses the app and enters the amount they want to send to their child.

[0940] The terminal sends the transfer request to the server using HTTPS.

[0941] The server receives the request and credits the child's account with the specified amount, and the credited transfer information is saved in a database.

[0942] The server uses a push notification service to send a remittance notification to the child's device.

[0943] Check your purchase history

[0944] When a user (child) makes a payment at a store using electronic money (e.g., PayPay), the child's terminal collects payment information and sends it to the server.

[0945] The server receives the payment information and stores it in a database.

[0946] Users (parents) can check their children's purchase history in real time through the app.

[0947] The server also notifies the parent's device of the latest purchase history.

[0948] Alert Settings

[0949] Users (parents) can set alerts within the app when certain usage conditions are met (e.g., payments of 500 yen or more).

[0950] The server monitors the purchase history based on set conditions.

[0951] If the condition is met, the server sends an alert to the parent device.

[0952] The parent's device notifies the parent of the received alert and displays detailed information.

[0953] Specific examples

[0954] User registration and account linking

[0955] The user (parent) installs the dedicated app, creates an account, then creates a child account and links the two accounts.

[0956] The server stores parent and child information in a database.

[0957] Distribution of pocket money

[0958] The user (parent) accessed the app and sent 500 yen to their child.

[0959] The server adds 500 yen to the child's account and notifies the child of the transfer via push notification.

[0960] Check your purchase history

[0961] The user (child) paid 200 yen using electronic money at a stationery store.

[0962] The server receives this payment information and stores it in a database.

[0963] The user (parent) checks their child's latest purchase history in the app and confirms payments at the stationery store.

[0964] Alert Settings

[0965] The user (parent) sets an alert in the app for payments over 500 yen.

[0966] A few days later, when a 600 yen purchase is made on the child's device, the server will send a notification to the parent's device, as the alert conditions have been met.

[0967] The user (parent) will receive an alert to check the details.

[0968] The above is a specific embodiment of the present invention, and by using this system, parents can easily manage how their children's pocket money is spent. In addition, the real-time monitoring and alert functions allow parents to manage their children's pocket money with peace of mind.

[0969] The flow of the identification process in the first embodiment will be described with reference to FIG.

[0970] User registration and account linking

[0971] Step 1:

[0972] The user (parent) installs a dedicated app.

[0973] Input: Download the app from the App Store or Google Play

[0974] Output: The app is installed on your phone.

[0975] Specific actions: Operate your smartphone to search for and download the app, and complete the installation.

[0976] Step 2:

[0977] The user (parent) registers a new user on the app.

[0978] Input: Name, Email Address, Password

[0979] Output: New account created

[0980] Specific actions: Launch the app, enter your name, email address, and password, and press the "Register" button.

[0981] Step 3:

[0982] The user (parent) creates an account for their child and links it to their own account.

[0983] Input: Child's name, age

[0984] Output: Child account created and linked to parent account

[0985] Specific actions: Select the "Create a child account" option in the app, enter the required information and press the "Create" button.

[0986] Step 4:

[0987] The server stores parent and child account information in a database.

[0988] Input: Parent and child account information

[0989] Output: Information is saved in the database

[0990] Specific behavior: Receives HTTP requests and executes queries to insert information into a database.

[0991] Distribution of pocket money

[0992] Step 1:

[0993] The user (parent) accesses the app and enters the amount to be transferred.

[0994] Input: Amount you want to send

[0995] Output: A transfer request is generated.

[0996] Specific actions: Enter the amount to send in the app's text field and press the "Send" button.

[0997] Step 2:

[0998] The terminal sends a remittance request to the server.

[0999] Input: Transfer request

[1000] Output: The request arrives at the server

[1001] What it does: Creates and sends a money transfer request using HTTPS.

[1002] Step 3:

[1003] The server will credit the specified amount to the child's account.

[1004] Input: Transfer request

[1005] Output: The child's account balance is updated.

[1006] What it does: Executes a query that updates the appropriate records in the database, adding the specified amount.

[1007] Step 4:

[1008] The server sends a notification of the transfer.

[1009] Input: Remittance information

[1010] Output: A notification is sent to the child's device.

[1011] Specific operation: Sends notifications using the push notification API.

[1012] Check your purchase history

[1013] Step 1:

[1014] The user (child) makes a payment using PayPay.

[1015] Input: Purchase amount, payment information

[1016] Output: PayPay payment completed

[1017] Specific operations: Scan the QR code with the PayPay app, enter the amount, and confirm the payment.

[1018] Step 2:

[1019] The terminal sends the payment information to the server.

[1020] Input: Payment information

[1021] Output: Payment information arrives at the server

[1022] Specific operation: After payment is completed, an HTTP request containing payment information is sent to the server.

[1023] Step 3:

[1024] The server stores the purchase history.

[1025] Input: Payment information

[1026] Output: Purchase history stored in the database

[1027] Specific Actions: Executes a query to insert payment information into the database.

[1028] Step 4:

[1029] The server notifies the parent's device of the purchase history.

[1030] Input: Purchase history

[1031] Output: A notification is sent to the parent's device.

[1032] Specific operation: Sends notifications to the parent's device using the push notification API.

[1033] Alert Settings

[1034] Step 1:

[1035] User (parent) sets alerts based on usage conditions.

[1036] Input: Alert condition, e.g., payment of 500 yen or more

[1037] Output: Save alert settings

[1038] Specific actions: Enter conditions on the "Alert Settings" page in the app and press the "Save" button.

[1039] Step 2:

[1040] The server monitors the purchase history.

[1041] Input: purchase history, alert conditions

[1042] Output: Monitoring results

[1043] Specific behavior: Periodically runs monitoring queries against the database.

[1044] Step 3:

[1045] The server notifies you when the condition is met.

[1046] Input: Monitoring results

[1047] Output: Alert notification on parent device

[1048] Specific behavior: When the conditions are met, an alert is sent using the push notification API.

[1049] Step 4:

[1050] The parent device receives the alert.

[1051] Input: Alert notification

[1052] Output: Display of alert notification

[1053] Specific behavior: Displays an alert as a pop-up notification on the device.

[1054] (Application example 1)

[1055] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[1056] Traditionally, when managing pocket money with cash, it is difficult for parents to keep track of how their children spend their money in detail, and it is also difficult to record where and how the child spends the money. This makes it difficult for parents to properly manage their children's money and for children to develop a healthy sense of money. Furthermore, with the spread of electronic money, there is a need for a safe and efficient way for parents to give pocket money to their children.

[1057] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[1058] In this invention, the server includes means for transferring electronic money from a parent's account to a child's account, means for storing the purchase history of the child's account in a central management device, means for displaying the child's purchase history on the parent's mobile information terminal, means for sending alerts based on conditions set by the parent, means for setting alerts based on changes in the balance of the child's account, and means for scheduling transfers from the parent's account to the child's account. This allows parents to manage their children's money efficiently and safely, and enables children to develop sound financial skills.

[1059] "Parent Account" refers to an online account used by a parent to manage electronic money.

[1060] A "child's account" is an online account used by a child to manage electronic money.

[1061] "Electronic money" is currency used in electronic form in place of cash.

[1062] A "means of transfer" is a means for transferring electronic money from a parent's account to a child's account.

[1063] "Purchase history" is a record of purchases made by a child using electronic money.

[1064] The "central management device" is a server that centrally manages all account information and transaction history.

[1065] A "personal digital assistant" is a mobile device such as a smartphone or tablet.

[1066] A "warning" is a notification issued to call attention when a set condition is met.

[1067] "Balance fluctuation" refers to the increase or decrease in the amount of electronic money in an account.

[1068] A "means for scheduling remittances" is a means for automatically sending remittances based on specified dates and conditions.

[1069] The present invention is a system for parents to give electronic pocket money to their children and manage how the money is spent. Specific embodiments of the present invention will be described in detail below.

[1070] System configuration

[1071] The system consists of the following elements:

[1072] 1. Parent and child mobile devices (smartphones, tablets, etc.)

[1073] 2. Central management device (server)

[1074] Hardware and Software

[1075] Hardware: Smartphones (iOS, Android), tablets

[1076] software:

[1077] Python: Programming Language

[1078] Flask: a web framework for building server-side APIs

[1079] SQLite: Manage users and purchase history as a database

[1080] User registration and account linking

[1081] The parent installs the application on their mobile device and registers as a new user. The parent then creates an account for the child and links it to their own account. The central management device (server) stores the parent and child account information in a database.

[1082] Distribution of pocket money

[1083] The parent accesses the application and enters the amount to transfer to the child's account. The device sends the transfer request to the server, which then updates the child's account with the specified amount. The child's device notifies them of the new transfer.

[1084] Check your purchase history

[1085] When a child makes a payment using an electronic payment service such as PayPay, the device sends the payment information to a server, which stores it in a database, allowing parents to check their child's most recent purchase history in real time through the app.

[1086] Alert Settings

[1087] Parents can set alerts based on specific usage conditions in the application, such as when a certain amount of money is spent. The server monitors the purchase history based on the set conditions and sends an alert to the parent's device when the condition is met.

[1088] Monitor balance fluctuations

[1089] Parents can set alerts based on changes in their child's account balance, such as when the balance exceeds or falls below a certain amount, allowing parents to monitor their child's spending behavior more closely.

[1090] Schedule a transfer

[1091] Parents can manage the account and schedule transfers, for example, to be sent automatically, such as a set amount at a certain time each month.

[1092] Specific examples

[1093] User registration and account linking: Parents install the application and create an account. Then, they create a child account and link it to the parent's account.

[1094] Distributing pocket money: A parent uses the application to send their child 500 yen in electronic money, enters the amount, and submits it. The server then credits the amount to the child's account.

[1095] Checking purchase history: When a child spends 200 yen at a stationery store, the information is sent to the server and stored in a database. Parents can check this information in the application.

[1096] Alert settings: If a parent sets the option to "send an alert if more than 500 yen is spent at once," and their child makes a purchase of 600 yen, an alert will be sent to the parent's device.

[1097] Prompt Sentence Examples

[1098] Remittance: Parent sends 500 yen to child.

[1099] Purchase history: A child spends 200 yen at the stationery store at school.

[1100] Alert: If a parent sets up a notification for purchases over 500 yen, a notification will be sent when the child makes a purchase of 600 yen.

[1101] The present invention enables parents to manage their children's finances efficiently and safely, and enables children to acquire a sound financial sense.

[1102] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[1103] Step 1:

[1104] The application is installed on the parent's mobile information terminal and a new user registration is performed.

[1105] Input: Parent's personal information, account creation information

[1106] Output: New user ID, parent account information

[1107] Specific behavior:

[1108] Parent downloads and launches the application.

[1109] The parent enters personal information (name, email address, password, etc.) and presses the account creation button.

[1110] The server stores the received information in a database and generates a new user ID.

[1111] Step 2:

[1112] Parents create accounts for their children and link them to their own accounts.

[1113] Input: Child's personal information, link information

[1114] Output: Child's new user ID, parent and child link information

[1115] Specific behavior:

[1116] A parent selects the "Create a Child Account" feature on the application.

[1117] Parents enter their child's personal information and press the link button.

[1118] The server stores the received information in a database and generates a new child ID.

[1119] The server links the parent's account with the child's account.

[1120] Step 3:

[1121] Parents use the application to transfer money to their children's accounts.

[1122] Input: Transfer amount, child's account ID

[1123] Output: Transfer completion notification, updated balance

[1124] Specific behavior:

[1125] The parent selects the transfer function in the application and enters the amount to transfer.

[1126] When the parent presses the send button, the terminal sends a remittance request to the server.

[1127] The server adds the transfer amount to the child's account and updates the database.

[1128] The server sends a notification of the completion of the remittance to the child's device.

[1129] Step 4:

[1130] The child makes the payment using an electronic payment service such as PayPay.

[1131] Input: payment amount, payment store information

[1132] Output: Purchase history, updated balance

[1133] Specific behavior:

[1134] The child makes an electronic payment at the store and completes the payment.

[1135] The child's device sends payment information (payment amount, store information) to the server.

[1136] The server stores the information in a database and updates the child's account balance.

[1137] Step 5:

[1138] Parents can view their child's purchase history in the app.

[1139] Input: Parent account ID, Child account ID

[1140] Output: Purchase history, purchase details

[1141] Specific behavior:

[1142] A parent selects the "Purchase History" feature in the application.

[1143] The server receives the parent's request and retrieves the child's purchase history from the database.

[1144] The server sends the acquired purchase history to the parent's device.

[1145] Step 6:

[1146] Parents can set alerts based on specific conditions.

[1147] Input: Warning condition (e.g., payment above a certain amount)

[1148] Output: Set warning conditions

[1149] Specific behavior:

[1150] Parents select the "Warning Settings" feature in the application.

[1151] The parent enters the warning conditions and presses the setting button.

[1152] The server stores the received alert conditions in a database.

[1153] Step 7:

[1154] The server monitors the purchase history based on the set conditions and sends an alert when the conditions are met.

[1155] Input: purchase history, warning conditions

[1156] Output: Warning notice

[1157] Specific behavior:

[1158] The server periodically checks the purchase history in the database.

[1159] If the set warning conditions are met, a warning notification will be sent to the parent device.

[1160] Step 8:

[1161] Parents schedule transfers to their children's accounts.

[1162] Input: remittance amount, schedule information (date, time, cycle)

[1163] Output: Scheduled transfer information

[1164] Specific behavior:

[1165] The parent selects the transfer schedule feature in the application.

[1166] The parent enters the transfer amount and schedule information and presses the setting button.

[1167] The server stores the received schedule information in a database.

[1168] The remittance will be processed automatically at the set date and time.

[1169] Furthermore, an emotion engine that estimates the user's emotion may be further combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59, and perform identification processing using the user's emotion.

[1170] The present invention is a system that allows parents to give their children electronic pocket money and manage how it is spent, and further combines it with an emotion engine that recognizes the user's emotions and provides various notifications and advice based on that data. Specific processing content based on an embodiment of the present invention will be described below.

[1171] System Configuration

[1172] The system consists of the following elements:

[1173] 1. Smartphone apps (devices) for parents and children

[1174] 2. Central Management Server (Server)

[1175] 3. Emotion Engine

[1176] User registration and account linking

[1177] 1. The user (parent) installs the app and opens the new user registration screen.

[1178] 2. The user (parent) enters information such as name, email address, and password.

[1179] 3. The terminal sends the entered information to the server.

[1180] 4. The server receives the information, registers the new user in the database, generates an account ID, and returns it to the device.

[1181] 5. The user (parent) selects the option to create a child account and enters the child's name and user ID.

[1182] 6. The device sends a child account creation request to the server.

[1183] 7. The server receives the request, creates a child account, links it to the parent account, generates a child account ID, and returns it to the device.

[1184] Distribution of pocket money

[1185] 1. The user (parent) logs into the app and selects the option to send pocket money.

[1186] 2. The user (parent) enters the amount to be transferred.

[1187] 3. The device sends a transfer request to the server, which includes the parent's account ID, the child's account ID, and the transfer amount.

[1188] 4. The server receives the transfer request, checks the parent and child account information in the database, adds the transfer amount to the child's account, updates the database, and returns a successful transfer notification to notify the child's account of the update.

[1189] 5. The device receives a notification from the server and notifies the child's app that a new transfer has been made.

[1190] Check your purchase history

[1191] 1. The user (child) makes a purchase using PayPay. Payments are made through the PayPay app.

[1192] 2. Once the payment is complete, the terminal sends the payment information (store name, amount, date and time, etc.) to the server.

[1193] 3. The server receives the payment information and stores it in a database, including the child's account ID.

[1194] 4. The user (parent) selects the option to view their child's purchase history within the app.

[1195] 5. The device sends a history request to the server.

[1196] 6. The server retrieves the child's latest payment information from the database and sends it back to the parent's device.

[1197] 7. The device displays the received history information in the parent app.

[1198] Alert Settings

[1199] 1. The user (parent) selects the alert setting option and enters a specific condition (e.g., a single payment of 500 yen or more).

[1200] 2. The device sends an alert setting request to the server, including the parent account ID and the alert conditions.

[1201] 3. The server receives the alert conditions and stores them in a database.

[1202] 4. As the server saves each payment entry to the database, it checks it against pre-defined alert conditions.

[1203] 5. When the condition is met (e.g., when the child spends more than 500 yen), the server sends an alert notification to the parent's device.

[1204] 6. The device receives the alert notification and displays the alert content in the parent's app.

[1205] Introducing the Emotion Engine

[1206] The terminal and server are equipped with an emotion engine that collects and analyzes the emotion data of users (parents and children).

[1207] Based on the emotional data obtained by the emotion engine, an alert is sent to the parent's device when certain conditions are met.

[1208] The server uses emotional data to analyze purchase history and provide appropriate advice and alerts to parents.

[1209] Specific examples

[1210] User registration and account linking

[1211] The user (parent) installed the app and created an account. Then, the user (parent) created a child account and linked the two accounts.

[1212] The server stored the parent and child information in a database.

[1213] Distribution of pocket money

[1214] The user (parent) accessed the app to send their child 500 yen in pocket money, entered the amount, and sent it.

[1215] The server added 500 yen to the child's account and sent the child a notification of the transfer.

[1216] Check your purchase history

[1217] The user (child) paid 200 yen with PayPay at a stationery store.

[1218] The server received this payment information and stored it in a database.

[1219] The user (parent) checked their child's most recent purchase history in the app and confirmed the payment at the stationery store.

[1220] Alert Settings

[1221] The user (parent) set it up so that an alert would be sent if their child spent more than 500 yen at one time.

[1222] A few days later, I spent 600 yen on my child's device to buy a toy.

[1223] When the server met the alert conditions, it sent a notification to the parent's device, and the user (parent) received the alert.

[1224] Examples of emotion engines

[1225] The user (child) was shopping at a toy store and the emotion engine recognized that the child was feeling very happy.

[1226] Based on this emotional data, the emotion engine notified the parents that their child had purchased an expensive item and was very happy.

[1227] Sarver offered some advice to parents: "If these kinds of expensive purchases are frequent, we recommend reconsidering your budget."

[1228] This system provides an environment where parents can manage their children's finances more transparently and with peace of mind, and children can safely use their pocket money without carrying cash. Furthermore, by combining it with an emotion engine, parents can receive monitoring and advice based on their children's emotional state, enabling them to provide more appropriate financial education.

[1229] The processing flow will be explained below.

[1230] User registration and account linking

[1231] Step 1:

[1232] The user (parent) installs the app and opens the new user registration screen.

[1233] Step 2:

[1234] The user (parent) enters information such as name, email address, and password.

[1235] Step 3:

[1236] The terminal transmits the input information to the server.

[1237] Step 4:

[1238] The server receives the information, registers the new user in the database, generates an account ID, and returns it to the device.

[1239] Step 5:

[1240] The user (parent) selects the option to create a child account.

[1241] Step 6:

[1242] The user (parent) enters the child's name and user ID.

[1243] Step 7:

[1244] The terminal sends a request to create a child account to the server.

[1245] Step 8:

[1246] The server receives the request, creates a child account, links it to the parent's account, generates a child account ID, and returns it to the device.

[1247] Distribution of pocket money

[1248] Step 1:

[1249] The user (parent) logs into the app and selects the option to transfer pocket money.

[1250] Step 2:

[1251] The user (parent) enters the remittance amount.

[1252] Step 3:

[1253] The device sends a transfer request to the server, which includes the parent's account ID, the child's account ID, and the transfer amount.

[1254] Step 4:

[1255] The server receives the transfer request and checks the parent and child account information in its database.

[1256] Step 5:

[1257] The server adds the transfer amount to the child's account and updates the database.

[1258] Step 6:

[1259] The server returns a successful transfer information and notifies the child account of the update.

[1260] Step 7:

[1261] The device receives a notification from the server and notifies the child's app that a new transfer has been made.

[1262] Check your purchase history

[1263] Step 1:

[1264] The user (child) makes purchases using PayPay. Payments are made through the app.

[1265] Step 2:

[1266] Once the payment is complete, the terminal sends the payment information (store name, amount, date and time, etc.) to the server.

[1267] Step 3:

[1268] The server receives the payment information and stores it in a database, including the child's account ID.

[1269] Step 4:

[1270] The user (parent) selects the option to view their child's purchase history within the app.

[1271] Step 5:

[1272] The terminal sends a history request to the server.

[1273] Step 6:

[1274] The server retrieves the child's latest payment information from the database and sends it back to the parent's device.

[1275] Step 7:

[1276] The device displays the received history information in the parent's app.

[1277] Alert Settings

[1278] Step 1:

[1279] The user (parent) selects the alert setting option and enters specific conditions (e.g., a single payment of 500 yen or more).

[1280] Step 2:

[1281] The device sends an alert setting request to the server, which includes the parent account ID and the alert conditions.

[1282] Step 3:

[1283] The server receives the alert conditions and stores them in a database.

[1284] Step 4:

[1285] As the server saves each payment entry to the database, it checks it against pre-defined alert conditions.

[1286] Step 5:

[1287] When a condition is met (e.g., when a child pays more than 500 yen), the server sends an alert notification to the parent's device.

[1288] Step 6:

[1289] The device receives an alert notification and displays the alert content in the parent's app.

[1290] Introducing the Emotion Engine

[1291] Step 1:

[1292] The terminal and the server are equipped with an emotion engine to collect emotion data from users (parents and children).

[1293] Step 2:

[1294] The emotion engine analyzes the user's facial expressions, voice, text input, etc. to recognize their current emotional state.

[1295] Step 3:

[1296] The terminal transmits the emotion data to the server.

[1297] Step 4:

[1298] The server receives the emotion data and stores it in a database.

[1299] Step 5:

[1300] The server analyzes purchase history and payment data based on emotional data and provides appropriate advice and alerts to parents.

[1301] Step 6:

[1302] The server sends an alert to the parent's device when a certain condition is met (for example, when a child makes an expensive purchase and is very happy).

[1303] Step 7:

[1304] The device receives an alert notification and displays the alert content in the parent's app.

[1305] Specific examples

[1306] Examples of emotion engines

[1307] Step 1:

[1308] A user (child) is shopping at a toy store, and the emotion engine recognizes that the child is feeling very happy.

[1309] Step 2:

[1310] The emotion engine sends information to the server based on this emotion data.

[1311] Step 3:

[1312] The server receives the emotion data and sends a notification to the parent's account.

[1313] Step 4:

[1314] The device will display a notification in the parent's app saying, "Your child has purchased an expensive item and is very happy."

[1315] Step 5:

[1316] The server offers parents advice: "If these kinds of expensive purchases are frequent, we recommend reconsidering your budget."

[1317] Example 2

[1318] Next, a description will be given of Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[1319] Until now, parents have had limited means to manage their children's spending and purchasing history, and this lack of transparency and efficiency has made it difficult to understand children's emotions and spending trends in real time, making it difficult to provide appropriate financial education.

[1320] The specific processing by the specific processing unit 290 of the data processing device 12 in Example 2 is realized by the following means. In this invention, the server includes means for transferring digital currency from a parent's account to a child's account, means for storing the purchase history of the child's account on the server, means for displaying the child's purchase history on the parent's terminal, means for sending alerts based on conditions set by the parent, and means for collecting and analyzing user emotion data and notifying the user based on the results. This allows parents to manage their children's finances transparently and efficiently, and also allows them to understand their children's emotions and payment trends, making it possible to provide more appropriate financial education to their children.

[1321] "Parent Account" means an electronic account owned by a Parent that contains Personally Identifiable Information for managing and transferring Digital Currency.

[1322] A "child's account" is an electronic account owned by a child that contains personally identifiable information for the purpose of receiving digital currency from a parent and managing purchase history.

[1323] "Digital currency" is currency that exists in electronic form and is used for online transactions and transfers.

[1324] "Purchase History" means a history of payments made on a Child's account, including details such as the location, amount, date and time of the payment.

[1325] "Server" refers to a centralized management system for storing, processing, and managing data, and is a device that stores and manages user account information and purchase history.

[1326] "Device" refers to a device used by parents and children, such as a smartphone or tablet, that is capable of communication.

[1327] An "alert" refers to a notification or warning sent to a parent's device when certain conditions are met, such as to warn them about a large expenditure made by their child.

[1328] "Emotional data" refers to information indicative of a user's emotional state, and is data collected and analyzed using an emotion engine.

[1329] An "emotion engine" refers to technology that recognizes emotions from a user's facial expressions and behavior, and collects and analyzes the data.

[1330] "Notification" refers to the act of sending important information or alerts to a parent's device, and is a way for parents to keep track of their child's situation.

[1331] "Application program" refers to software that enables communication between parent and child devices, and generally refers to smartphone applications.

[1332] This invention is a system that allows parents to electronically give pocket money to their children and manage their child's spending. It also incorporates an emotion engine that recognizes the user's emotions in real time and provides notifications and advice based on those emotions. This system makes money management transparent and efficient for parents and children, and allows parents to understand their children's emotions and spending habits.

[1333] System Configuration

[1334] The system consists of the following elements:

[1335] 1. Smartphone apps (devices) used by parents and children

[1336] 2. Central Management Server (Server)

[1337] 3. Emotion Engine (emotion data collection and analysis system)

[1338] User registration and account linking

[1339] 1. The user (parent) installs the app on their smartphone and opens the new user registration screen.

[1340] 2. The user (parent) enters information such as name, email address, and password.

[1341] 3. The terminal sends the entered information to a central management server (e.g., AWS EC2).

[1342] 4. The server receives the information, registers the new user in a database (e.g., MySQL), generates an account ID, and returns it to the device.

[1343] 5. The user (parent) selects the Create Child Account option and enters the child's name and user ID.

[1344] 6. The device sends a child account creation request to the server.

[1345] 7. The server receives the request, creates a child account, links it to the parent account, generates a child account ID, and returns it to the device.

[1346] Distribution of pocket money

[1347] 1. The user (parent) logs into the app and selects the option to send pocket money.

[1348] 2. The user (parent) enters the amount to be transferred.

[1349] 3. The device sends a transfer request to the server, which includes the parent's account ID, the child's account ID, and the transfer amount.

[1350] 4. The server receives the transfer request, checks the parent and child account information in the database, adds the transfer amount to the child's account, and updates the database.

[1351] 5. The server returns a successful transfer information and notifies the child account of the update.

[1352] 6. The device receives a notification from the server and notifies the child's app that a new transfer has been made.

[1353] Check your purchase history

[1354] 1. The user (child) makes a purchase using an electronic payment system such as PayPay. PayPay payments are made through the app.

[1355] 2. Once the payment is complete, the terminal sends the payment information (store name, amount, date and time, etc.) to the server.

[1356] 3. The server receives the payment information and stores it in a database, including the child's account ID.

[1357] 4. The user (parent) selects the option to view their child's purchase history within the app.

[1358] 5. The device sends a history request to the server.

[1359] 6. The server retrieves the child's latest payment information from the database and sends it back to the parent's device.

[1360] 7. The device displays the received history information in the parent app.

[1361] Alert Settings

[1362] 1. The user (parent) selects the alert setting option and enters a specific condition (e.g., a single payment of 500 yen or more).

[1363] 2. The device sends an alert setting request to the server, including the parent account ID and the alert conditions.

[1364] 3. The server receives the alert conditions and stores them in a database.

[1365] 4. As the server saves each payment entry to the database, it checks it against pre-defined alert conditions.

[1366] 5. When the condition is met (e.g., when the child spends more than 500 yen), the server sends an alert notification to the parent's device.

[1367] 6. The device receives the alert notification and displays the alert content in the parent's app.

[1368] Introducing the Emotion Engine

[1369] 1. The device and server use an emotion engine (e.g., Microsoft Azure Emotion API) to collect emotion data from users (parents and children).

[1370] 2. The device sends the acquired emotion data to the server.

[1371] 3. The server receives the emotion data and stores it in a database.

[1372] 4. The server analyzes the emotion data for specific conditions (e.g., high levels of joy or anger).

[1373] 5. Based on the analysis results, the server sends appropriate advice and alerts to the parent's device.

[1374] 6. The device receives a notification and displays advice or alert details in the parent's app.

[1375] Examples of concrete examples and prompts

[1376] Specific examples

[1377] The user (parent) installed the app and created an account, then created a child account and linked the two accounts.

[1378] The user (parent) accessed the app, entered the amount, and sent it to send 500 yen pocket money to their child.

[1379] The user (child) paid 200 yen with PayPay at a stationery store.

[1380] The server received this payment information and stored it in a database.

[1381] The user (parent) checked their child's most recent purchase history in the app and confirmed the payment at the stationery store.

[1382] The user (parent) set it up so that an alert would be sent if their child spent more than 500 yen at one time.

[1383] A few days later, the user (child) uses 600 yen to buy a toy.

[1384] When the server met the alert conditions, it sent a notification to the parent's device, and the user (parent) received the alert.

[1385] The user (child) was shopping at a toy store and the emotion engine recognized that the child was feeling very happy.

[1386] Sarver offered some advice to parents: "If these kinds of expensive purchases are frequent, we recommend reconsidering your budget."

[1387] Prompt Sentence Examples

[1388] User Registration and Account Linking:

[1389] "Parents open the new user registration screen and create an account by entering their name, email address, and password. They then enter their child's name and user ID to create and link their child's account."

[1390] Pocket money distribution:

[1391] "Parents simply log into the app, select the option to send pocket money, enter the amount to send and send."

[1392] Check your purchase history:

[1393] "A child pays 200 yen at a stationery store with PayPay, and the parent checks the purchase history on the app."

[1394] Alert Settings:

[1395] "Parents can set up an alert to be sent if more than 500 yen is spent in a single transaction."

[1396] Introducing the Emotion Engine:

[1397] "When a child is shopping in a toy store, the emotion engine recognizes the child's joy and notifies the parent."

[1398] This invention allows parents to manage their children's money transparently and efficiently, and by understanding their children's emotions and spending habits, they can provide them with appropriate financial education, allowing the whole family to manage their pocket money with greater peace of mind.

[1399] The flow of the identification process in the second embodiment will be described with reference to FIG.

[1400] User registration and account linking

[1401] Step 1:

[1402] The user (parent) installs the app on their smartphone and opens the new user registration screen. Input: Parent's personal information (name, email address, password). Output: A new user registration request is generated on the device.

[1403] Step 2:

[1404] The device sends the entered information to a central server. Input: New user registration request including parent's personal information. Output: Data sent to the server.

[1405] Step 3:

[1406] The server receives the information and registers the new user in the database. Input: New user registration request. Output: New account ID generated and registered.

[1407] Step 4:

[1408] The server returns the generated account ID to the terminal. Input: New account ID. Output: Return of account ID.

[1409] Step 5:

[1410] The user (parent) selects the Create Child Account option and enters the child's name and user ID. Input: Child's personal information. Output: A child account creation request is generated on the device.

[1411] Step 6:

[1412] The device sends a request to the server to create a child account. Input: The request, including the child's personal information. Output: The data sent to the server.

[1413] Step 7:

[1414] The server receives the request, creates a child account, and associates it with the parent's account. Input: Child account creation request. Output: New child account ID is generated and registered in the database.

[1415] Step 8:

[1416] The server returns the generated child account ID to the device. Input: New child account ID. Output: Return of account ID.

[1417] Distribution of pocket money

[1418] Step 1:

[1419] The user (parent) logs in to the app and selects the option to transfer pocket money. Input: User authentication information (login ID, password). Output: Notification of successful login authentication.

[1420] Step 2:

[1421] The user (parent) inputs the amount to be transferred. Input: Amount to be transferred. Output: A transfer request is generated on the terminal.

[1422] Step 3:

[1423] The device sends a transfer request to the server. Input: A request containing the parent's account ID, the child's account ID, and the amount to transfer. Output: The data sent to the server.

[1424] Step 4:

[1425] The server receives the transfer request and checks the parent and child account information in the database. Input: Transfer request. Output: Start of the process to update the transfer record in the database.

[1426] Step 5:

[1427] The server adds the transfer amount to the child's account and updates the database. Input: Parent and child account information and transfer amount. Output: Database update.

[1428] Step 6:

[1429] The server returns a successful transfer information to the terminal and notifies the update of the child account. Input: Successful transfer information. Output: Notification of transfer completion sent to the terminal.

[1430] Step 7:

[1431] The device receives a notification from the server and notifies the child's app that a new transfer has been made. Input: Notification of transfer completion. Output: Notification displayed in the child's app.

[1432] Check your purchase history

[1433] Step 1:

[1434] The user (child) makes a purchase using an electronic payment system such as PayPay. Input: PayPay account information and payment information. Output: Receipt information after payment is completed.

[1435] Step 2:

[1436] Once the payment is complete, the terminal sends the payment information to the server. Input: Payment information such as store name, amount, date and time. Output: Data sent to the server.

[1437] Step 3:

[1438] The server receives the payment information and stores it in a database. Input: Payment information. Output: Payment information stored in a database.

[1439] Step 4:

[1440] User (parent) selects option within app to review child's purchase history. Input: Purchase history review request. Output: Request generated on device.

[1441] Step 5:

[1442] The device sends a history request to the server. Input: Purchase history confirmation request. Output: Data sent to the server.

[1443] Step 6:

[1444] The server retrieves the child's latest payment information from the database and sends it back to the parent's device. Input: Purchase history confirmation request. Output: Extraction and return of purchase history data.

[1445] Step 7:

[1446] The device displays the received history information in the parent app. Input: Purchase history data. Output: Purchase history displayed in the parent app.

[1447] Alert Settings

[1448] Step 1:

[1449] The user (parent) selects the alert setting option and enters the specific condition. Input: Alert condition (e.g., single payment of 500 yen or more). Output: An alert setting request is generated on the terminal.

[1450] Step 2:

[1451] The device sends an alert setting request to the server. Input: Parent account ID, request containing alert conditions. Output: Data sent to the server.

[1452] Step 3:

[1453] The server receives the alert conditions and stores them in the database. Input: Alert configuration request. Output: Alert conditions stored in the database.

[1454] Step 4:

[1455] When the server saves each payment information to the database, it checks it against the pre-defined alert conditions. Input: Payment information and alert conditions. Output: Alert condition check results.

[1456] Step 5:

[1457] The server sends an alert notification to the parent device when the condition is met. Input: Payment information that meets the condition. Output: Sending an alert notification.

[1458] Step 6:

[1459] The device receives the alert notification and displays the alert content in the parent app. Input: Alert notification. Output: Alert content displayed in the app.

[1460] Introducing the Emotion Engine

[1461] Step 1:

[1462] The device and server use an emotion engine to collect user emotion data. Input: User's facial expression, voice, and behavior data. Output: Acquisition of emotion data.

[1463] Step 2:

[1464] The device sends the acquired emotion data to the server. Input: Emotion data. Output: Data sent to the server.

[1465] Step 3:

[1466] The server receives the emotion data and stores it in a database. Input: Emotion data. Output: Emotion data stored in a database.

[1467] Step 4:

[1468] The server analyzes specific conditions based on emotion data. Input: Emotion data. Output: Generates analysis results.

[1469] Step 5:

[1470] The server sends appropriate advice or alerts to the parent device based on the analysis results. Input: Analysis results. Output: Sending advice or alerts.

[1471] Step 6:

[1472] The device receives the notification and displays the advice or alert content in the parent app. Input: Advice or alert notification. Output: Advice or alert content displayed in the app.

[1473] (Application example 2)

[1474] Next, a description will be given of Application Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[1475] Today's parents need a way to efficiently monitor their children's financial management and spending habits. However, while many systems on the market can electronically transfer pocket money and manage spending histories, they lack the functionality to provide advice and notifications based on the child's emotional state. As a result, parents find it difficult to consider not only their spending habits but also their children's emotions when providing sound financial education. This means that there is a need to solve the problem of children not being able to learn appropriate financial management in an environment that is not conducive to financial management.

[1476] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 2 is realized by the following means.

[1477] In this invention, the server includes means for transferring electronic money from the parent's account to the child's account, means for storing the purchase history of the child's account on the server, means for displaying the child's purchase history on the parent's terminal, means for sending alerts based on conditions set by the parent, and means for analyzing emotional data and providing notifications and advice based on that data. This allows parents to not only efficiently manage their children's finances, but also receive appropriate advice and notifications based on their children's emotional state.

[1478] "Parent Account" means an electronic money account managed by a parent and used to transfer electronic pocket money to a child.

[1479] A "child's account" is an electronic money account managed by a child, and is used to receive and use pocket money sent by a parent.

[1480] "Electronic money" is a digital form of currency that can be used via the Internet or dedicated terminals, and is used to purchase goods and services in the same way as cash.

[1481] "Purchase history" is a record of payments made by a child, and includes information such as the date and time of the payment, the amount, and the name of the store.

[1482] "Server" refers to a computer system that stores, processes, and manages data and serves as the central control for this invention.

[1483] A "terminal" is an electronic device that a user operates, and includes smartphones, tablets, computers, etc.

[1484] An "alert" is a feature that notifies users when a set condition is met, and issues a warning based on a specific action or condition.

[1485] "Emotion data" is digital information that represents the user's emotional state and is collected and analyzed by the emotion engine.

[1486] An "emotion engine" is a software system that recognizes a user's emotional state and collects and analyzes it as data.

[1487] A "notification" is a message or warning sent by the system to a user based on a specific condition.

[1488] "Advice" is a recommendation or advice provided based on emotional data and spending history, and is useful information for parents to support their children in managing their finances.

[1489] This invention is a system that allows parents to give their children electronic pocket money and manage how it is spent, and it also combines an emotion engine that recognizes the user's emotions and provides various notifications and advice based on that data. Specific processing content based on an embodiment of the present invention will be described below.

[1490] System Configuration

[1491] The system consists of the following elements:

[1492] 1. Parent and child devices (smartphones, tablets, etc.)

[1493] 2. Central Management Server

[1494] 3. Emotion Engine

[1495] User registration and account linking

[1496] The parent's device installs the application and opens the new user registration screen. The parent enters information such as name, email address, and password, and the device sends this information to the server. The server receives this information and registers the new user in its database. The parent then selects the option to create a child account and enters the child's name and user ID. The device sends this information to the server, and the server links the parent and child accounts.

[1497] Distribution of pocket money

[1498] The parent logs into the application and selects the option to transfer pocket money. The transfer amount is entered and the device sends a transfer request to the server. The server receives the transfer request and checks the parent and child's account information in the database. The server adds the transfer amount to the child's account and updates the database. The parent's device is notified of the successful transfer and notifies the child's account of the update.

[1499] Check your purchase history

[1500] When a child uses a device to make a purchase using electronic money, payment information (store name, amount, date and time, etc.) is sent from the device to the server. The server receives this payment information and stores it in a database. Parents can check their child's purchase history within the application, and the server sends the latest payment information back to the parent's device.

[1501] Alert Settings

[1502] The parent device selects the alert setting option and enters a specific condition (e.g., a single payment of 500 yen or more). The device sends an alert setting request to the server, which stores the alert condition in a database. When the child makes a payment, the server checks the payment information and sends an alert notification to the parent device if the condition is met.

[1503] Introducing the Emotion Engine

[1504] The device and server are equipped with an emotion engine that collects and analyzes the emotion data of users (parents and children). The server uses the emotion data to analyze purchase history and provide appropriate advice and alerts to parents.

[1505] Specific examples

[1506] User Registration and Account Linking:

[1507] The parent installed the app and created an account, then created a child account and linked the two accounts.

[1508] The server stored the parent and child information in a database.

[1509] Pocket money distribution:

[1510] A parent accessed the app to send their child 500 yen in pocket money, entered the amount, and sent it.

[1511] The server added 500 yen to the child's account and sent the child a notification of the transfer.

[1512] Check your purchase history:

[1513] My child paid 200 yen at a stationery store using electronic money.

[1514] The server received this payment information and stored it in a database.

[1515] The parent checked their child's recent purchase history in the app and confirmed the payment at the stationery store.

[1516] Alert Settings:

[1517] Parents set up an alert to be sent if their children spent more than 500 yen at one time.

[1518] A few days later, my child spent 600 yen on the device to buy a toy.

[1519] When the server met the alert conditions, it sent a notification to the parent's device, and the parent received the alert.

[1520] Examples of emotion engines:

[1521] A child is shopping at a toy store and the emotion engine recognizes that the child is feeling very happy.

[1522] The server notified the parents that their child had purchased an expensive item and was very happy.

[1523] Sarver offered some advice to parents: "If these kinds of expensive purchases are frequent, we recommend reconsidering your budget."

[1524] Prompt Sentence Examples

[1525] "A user registers as a parent (parent1), links a child (child1), and then sends 1,000 yen in pocket money. When the child buys a toy for 600 yen and feels very happy at the time, simulate using Python what kind of notification will be sent to the parent."

[1526] By implementing the invention in this way, parents can not only manage their children's finances efficiently, but also receive appropriate advice and notifications based on emotional data.

[1527] The flow of the specific processing in the application example 2 will be described with reference to FIG.

[1528] Step 1:

[1529] The user (parent) installs the application on their device and opens the new user registration screen. The parent enters information such as their name, email address, and password. The entered information is sent to the server, which receives it and registers it as the parent's account in its database. The parent then selects the option to create a child account and enters the child's name and user ID. This causes the device to send a request to create a child account to the server.

[1530] Input: Parent's name, email address, password, child's name, user ID

[1531] Output: Parent and child account registration in database, account linking

[1532] Step 2:

[1533] The server receives the child account creation request and links the parent and child accounts. It generates account IDs for both the parent and child and stores the linking information in the database. It notifies the device that the parent and child accounts have been successfully linked.

[1534] Input: Child account creation request

[1535] Output: Account linking information saved in the database, notification of link completion

[1536] Step 3:

[1537] The user (parent) logs into the application on their device and selects the option to transfer pocket money. The parent enters the amount to transfer and the device sends this transfer request to the server. The server receives the transfer request and checks the parent and child account information in the database. It adds the transfer amount to the child's account and updates the database.

[1538] Input: Transfer amount, parent and child account information

[1539] Output: Transfer amount added to child account, database updated

[1540] Step 4:

[1541] The server notifies the parent's device of the successful transfer and updates the child's account. The parent's device receives this notification and displays the new transfer.

[1542] Input: Remittance success information

[1543] Output: Remittance notification to parent and child devices

[1544] Step 5:

[1545] When purchasing a product, the child's device pays with electronic money. Payment information (store name, amount, date and time, etc.) is sent from the device to the server. The server receives the payment information and stores it in a database. The payment information also includes automatically generated emotion data.

[1546] Input: Payment information (store name, amount, date and time, etc.), emotional data

[1547] Output: Payment information saved in database

[1548] Step 6:

[1549] The parent selects the option to check the purchase history within the application and retrieves the child's latest payment information from the server. The server searches the database for the relevant payment information and sends it back to the parent's device. The parent's device receives this information and displays the purchase history.

[1550] Input: Purchase history request

[1551] Output: Provides up-to-date payment information and displays purchase history

[1552] Step 7:

[1553] The parent device selects the alert setting option and enters a specific condition (e.g., a single payment of 500 yen or more). The device sends this alert setting request to the server, which stores this alert condition in its database.

[1554] Input: Alert Condition

[1555] Output: Alert conditions saved in database

[1556] Step 8:

[1557] When the server saves each payment in the database, it checks it against pre-defined alert conditions, and if a condition is met (e.g., when a child spends more than 500 yen), it sends an alert notification to the parent's device.

[1558] Input: Payment information, Alert conditions

[1559] Output: Alert notification when the condition is met

[1560] Step 9:

[1561] The device and server are equipped with an emotion engine that collects and analyzes the user's emotion data. The server uses the emotion data to analyze purchase history and provide appropriate advice and alerts to parents.

[1562] Input: Emotional data, purchase history

[1563] Output: Providing advice and alerts based on sentiment analysis

[1564] Prompt Sentence Examples

[1565] "A user registers as a parent (parent1), links a child (child1), and then sends 1,000 yen in pocket money. When the child buys a toy for 600 yen and feels very happy at the time, simulate using Python what kind of notification will be sent to the parent."

[1566] The specific processing unit 290 transmits the result of the specific processing to the smart glasses 214. In the smart glasses 214, the control unit 46A causes the speaker 240 to output the result of the specific processing. The microphone 238 acquires audio indicating a user input regarding the result of the specific processing. The control unit 46A transmits audio data indicating the user input acquired by the microphone 238 to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the audio data.

[1567] The data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of the data generation model 58 is ChatGPT (Internet Search<URL: https: / / openai.com / blog / chatgpt> ), Gemini (Internet search <url: https: gemini.google.com ?hl="ja">) and other generation AIs. The data generation model 58 is obtained by performing deep learning on a neural network. A prompt including an instruction is input to the data generation model 58, and inference data such as voice data indicating voice, text data indicating text, and image data indicating an image is also input. The data generation model 58 performs inference on the input inference data in accordance with the instruction indicated by the prompt, and outputs the inference result in a data format such as voice data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[1568] In the above embodiment, an example in which the specific processing is performed by the data processing device 12 has been given, but the technology of the present disclosure is not limited to this, and the specific processing may be performed by the smart glasses 214.

[1569] [Third embodiment]

[1570] FIG. 5 shows an example of the configuration of a data processing system 310 according to the third embodiment.

[1571] 5, the data processing system 310 includes the data processing device 12 and a headset type terminal 314. An example of the data processing device 12 is a server.

[1572] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[1573] The headset type terminal 314 includes a computer 36, a microphone 238, a speaker 240, a camera 42, a communication I / F 44, and a display 343. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The microphone 238, the speaker 240, the camera 42, and the display 343 are also connected to the bus 52.

[1574] The microphone 238 receives instructions and the like from the user 20 by receiving voice uttered by the user 20. The microphone 238 captures the voice uttered by the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio in accordance with instructions from the processor 46.

[1575] Camera 42 is a small digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor, and captures images of the surroundings of user 20 (for example, an imaging range defined by an angle of view equivalent to the field of vision of a typical healthy person).

[1576] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 control the exchange of various information between the processor 46 and the processor 28 via the network 54. The exchange of various information between the processor 46 and the processor 28 using the communication I / Fs 44 and 26 is carried out in a secure state.

[1577] Fig. 6 shows an example of the main functions of the data processing device 12 and the headset type terminal 314. As shown in Fig. 6, in the data processing device 12, a specific process is performed by the processor 28. A specific process program 56 is stored in the storage 32.

[1578] The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific processing is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[1579] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[1580] In the headset type terminal 314, a reception output process is performed by the processor 46. A reception output program 60 is stored in the storage 50. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[1581] Next, a description will be given of the identification process performed by the identification processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as the "server" and the headset type terminal 314 will be referred to as the "terminal."

[1582] The present invention is a system for parents to give electronic pocket money to their children and manage how the money is spent. Specific processing contents based on an embodiment of the present invention will be described below.

[1583] System Configuration

[1584] The system consists of the following elements:

[1585] 1. Smartphone apps (devices) for parents and children

[1586] 2. Central Management Server (Server)

[1587] User registration and account linking

[1588] 1. The user (parent) installs the app and registers as a new user.

[1589] 2. The user (parent) creates an account for the child and links it to their own account.

[1590] 3. The server stores the parent and child account information in a database.

[1591] Distribution of pocket money

[1592] 1. The user (parent) accesses the app and enters the amount to transfer to their child's account.

[1593] 2. The terminal sends a remittance request to the server.

[1594] 3. The server receives the request and credits the specified amount to the child's account.

[1595] 4. Your child's device will notify you of a new transfer.

[1596] Check your purchase history

[1597] 1. When a user (child) makes a payment with PayPay, the terminal sends the payment information to the server.

[1598] 2. The server stores the payment information in a database.

[1599] 3. Users (parents) can check their children's purchase history in real time through the app.

[1600] 4. The parent's device will notify them of their latest purchase history.

[1601] Alert Settings

[1602] 1. The user (parent) sets up alerts in the app based on specific usage conditions (e.g., when payments exceed a certain amount).

[1603] 2. The server monitors the purchase history based on the set conditions.

[1604] 3. If the condition is met, the server sends an alert to the parent device.

[1605] 4. The parent's device notifies the parent of the alert and displays detailed information.

[1606] Specific examples

[1607] User registration and account linking

[1608] The user (parent) installed the app and created an account. Then, the user (parent) created a child account and linked the two accounts.

[1609] The server stored the parent and child information in a database.

[1610] Distribution of pocket money

[1611] The user (parent) accessed the app to send their child 500 yen in pocket money, entered the amount, and sent it.

[1612] The server added 500 yen to the child's account and sent the child a notification of the transfer.

[1613] Check your purchase history

[1614] The user (child) paid 200 yen with PayPay at a stationery store.

[1615] The server received this payment information and stored it in a database.

[1616] The user (parent) checked their child's most recent purchase history in the app and confirmed the payment at the stationery store.

[1617] Alert Settings

[1618] The user (parent) set it up so that an alert would be sent if their child spent more than 500 yen at one time.

[1619] A few days later, I spent 600 yen on my child's device to buy a toy.

[1620] When the server met the alert conditions, it sent a notification to the parent's device, and the user (parent) received the alert.

[1621] This system provides parents with a more transparent and secure environment for managing their children's finances, and allows children to safely use their pocket money without having to carry cash.

[1622] The processing flow will be explained below.

[1623] User registration and account linking

[1624] Step 1:

[1625] The user (parent) installs the app and opens the new user registration screen.

[1626] The user (parent) enters information such as name, email address, and password.

[1627] Step 2:

[1628] The terminal transmits the input information to the server.

[1629] Step 3:

[1630] The server receives the information and registers the new user in its database.

[1631] The server generates an account ID and returns it to the device.

[1632] Step 4:

[1633] The user (parent) selects the option to create a child account.

[1634] The user (parent) enters the child's name and user ID.

[1635] Step 5:

[1636] The terminal sends a request to create a child account to the server.

[1637] Step 6:

[1638] The server receives the request, creates a child account, and associates it with the parent account.

[1639] The server generates a child account ID and returns it to the device.

[1640] Distribution of pocket money

[1641] Step 1:

[1642] The user (parent) logs into the app and selects the option to transfer pocket money.

[1643] The user (parent) enters the remittance amount.

[1644] Step 2:

[1645] The device sends a transfer request to the server, which includes the parent's account ID, the child's account ID, and the transfer amount.

[1646] Step 3:

[1647] The server receives the transfer request and checks the parent and child account information in its database.

[1648] The server adds the transfer amount to the child's account and updates the database.

[1649] The server returns a successful transfer information and notifies the child account of the update.

[1650] Step 4:

[1651] The device receives a notification from the server and notifies the child's app that a new transfer has been made.

[1652] Check your purchase history

[1653] Step 1:

[1654] The user (child) makes purchases using PayPay. Payments are made through the app.

[1655] Step 2:

[1656] Once the payment is complete, the terminal sends the payment information (store name, amount, date and time, etc.) to the server.

[1657] Step 3:

[1658] The server receives the payment information and stores it in a database, including the child's account ID.

[1659] Step 4:

[1660] The user (parent) selects the option to view their child's purchase history within the app.

[1661] Step 5:

[1662] The terminal sends a history request to the server.

[1663] Step 6:

[1664] The server retrieves the child's latest payment information from the database and sends it back to the parent's device.

[1665] Step 7:

[1666] The device displays the received history information in the parent's app.

[1667] Alert Settings

[1668] Step 1:

[1669] The user (parent) selects the alert setting option and enters specific conditions (e.g., a single payment of 500 yen or more).

[1670] Step 2:

[1671] The device sends an alert setting request to the server, which includes the parent account ID and the alert conditions.

[1672] Step 3:

[1673] The server receives the alert conditions and stores them in a database.

[1674] Step 4:

[1675] As the server saves each payment entry to the database, it checks it against pre-defined alert conditions.

[1676] Step 5:

[1677] When a condition is met (e.g., when a child pays more than 500 yen), the server sends an alert notification to the parent's device.

[1678] Step 6:

[1679] The device receives an alert notification and displays the alert content in the parent's app.

[1680] Example 1

[1681] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[1682] Today's children are increasingly using electronic money instead of carrying cash, but to make it easier for parents to manage their children's finances, a transparent and safe system is needed. It is also desirable for parents to monitor their children's spending in real time and set alerts as necessary. However, current systems do not adequately provide such functionality.

[1683] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[1684] In this invention, the server includes means for transferring electronic money from a parent's account to a child's account, means for storing the purchase history of the child's account on the server, means for displaying the child's purchase history on the parent's terminal, means for sending alerts based on conditions set by the parent, means for storing the parent and child's account information in a database, means for sending a remittance request to the server using HTTPS, and means for the server to send a remittance notification via a push notification API. This allows parents to keep track of their child's financial management in real time and receive appropriate alerts.

[1685] "Parent Account" means an account used by a parent to transfer and manage electronic money to a child.

[1686] A "child's account" is an account used by a child to receive electronic money transferred from a parent and use it for payments, etc.

[1687] "Electronic money" refers to currency exchanged electronically in place of cash, and is used for online or offline payments.

[1688] A "transfer request" is a request to transfer electronic money from a parent's account to a child's account.

[1689] A "parent's device" is an electronic device such as a smartphone or tablet used by the parent to transfer electronic money and check purchase history.

[1690] A "child's device" is an electronic device such as a smartphone or tablet used by a child, which is used to make payments using electronic money.

[1691] A "server" is a central management system that receives requests from multiple terminals and stores and processes data.

[1692] "Database" refers to a system for storing and managing data such as parent and child account information and purchase history.

[1693] "HTTPS" is a communication protocol for encrypting and sending data over the Internet, enabling secure data transmission.

[1694] "Push notifications" are notifications that are sent in real time from a server to a device, and are used to instantly inform users of important information such as money transfers, purchase history, and alerts.

[1695] MODE FOR CARRYING OUT THE INVENTION

[1696] The present invention is a system that allows parents to give electronic pocket money to their children and manage how that money is spent. Specific processing details of the present invention will be described below.

[1697] System Configuration

[1698] The system consists of the following elements:

[1699] 1. Smartphone apps (devices) for parents and children

[1700] 2. Central Management Server (Server)

[1701] 3. Database System

[1702] 4. Communication Protocol (HTTPS)

[1703] 5. Push notification services

[1704] User registration and account linking

[1705] The user (parent) installs a dedicated app on their smartphone.

[1706] Hardware used: Smartphone (e.g. iPhone, Android smartphone)

[1707] Software used: Dedicated app (e.g. PocketMoneyApp)

[1708] Parents launch the app and enter their name, email address, and password to register.

[1709] Parents then enter their child's information (name, age) to create an account for their child and link it to their own account.

[1710] The server receives this information and stores it in a database (e.g. MySQL).

[1711] Distribution of pocket money

[1712] The user (parent) accesses the app and enters the amount they want to send to their child.

[1713] The terminal sends the transfer request to the server using HTTPS.

[1714] The server receives the request and credits the child's account with the specified amount, and the credited transfer information is saved in a database.

[1715] The server uses a push notification service to send a remittance notification to the child's device.

[1716] Check your purchase history

[1717] When a user (child) makes a payment at a store using electronic money (e.g., PayPay), the child's terminal collects payment information and sends it to the server.

[1718] The server receives the payment information and stores it in a database.

[1719] Users (parents) can check their children's purchase history in real time through the app.

[1720] The server also notifies the parent's device of the latest purchase history.

[1721] Alert Settings

[1722] Users (parents) can set alerts within the app when certain usage conditions are met (e.g., payments of 500 yen or more).

[1723] The server monitors the purchase history based on set conditions.

[1724] If the condition is met, the server sends an alert to the parent device.

[1725] The parent's device notifies the parent of the received alert and displays detailed information.

[1726] Specific examples

[1727] User registration and account linking

[1728] The user (parent) installs the dedicated app, creates an account, then creates a child account and links the two accounts.

[1729] The server stores parent and child information in a database.

[1730] Distribution of pocket money

[1731] The user (parent) accessed the app and sent 500 yen to their child.

[1732] The server adds 500 yen to the child's account and notifies the child of the transfer via push notification.

[1733] Check your purchase history

[1734] The user (child) paid 200 yen using electronic money at a stationery store.

[1735] The server receives this payment information and stores it in a database.

[1736] The user (parent) checks their child's latest purchase history in the app and confirms payments at the stationery store.

[1737] Alert Settings

[1738] The user (parent) sets an alert in the app for payments over 500 yen.

[1739] A few days later, when a 600 yen purchase is made on the child's device, the server will send a notification to the parent's device, as the alert conditions have been met.

[1740] The user (parent) will receive an alert to check the details.

[1741] The above is a specific embodiment of the present invention, and by using this system, parents can easily manage how their children's pocket money is spent. In addition, the real-time monitoring and alert functions allow parents to manage their children's pocket money with peace of mind.

[1742] The flow of the identification process in the first embodiment will be described with reference to FIG.

[1743] User registration and account linking

[1744] Step 1:

[1745] The user (parent) installs a dedicated app.

[1746] Input: Download the app from the App Store or Google Play

[1747] Output: The app is installed on your phone.

[1748] Specific actions: Operate your smartphone to search for and download the app, and complete the installation.

[1749] Step 2:

[1750] The user (parent) registers a new user on the app.

[1751] Input: Name, Email Address, Password

[1752] Output: New account created

[1753] Specific actions: Launch the app, enter your name, email address, and password, and press the "Register" button.

[1754] Step 3:

[1755] The user (parent) creates an account for their child and links it to their own account.

[1756] Input: Child's name, age

[1757] Output: Child account created and linked to parent account

[1758] Specific actions: Select the "Create a child account" option in the app, enter the required information and press the "Create" button.

[1759] Step 4:

[1760] The server stores parent and child account information in a database.

[1761] Input: Parent and child account information

[1762] Output: Information is saved in the database

[1763] Specific behavior: Receives HTTP requests and executes queries to insert information into a database.

[1764] Distribution of pocket money

[1765] Step 1:

[1766] The user (parent) accesses the app and enters the amount to be transferred.

[1767] Input: Amount you want to send

[1768] Output: A transfer request is generated.

[1769] Specific actions: Enter the amount to send in the app's text field and press the "Send" button.

[1770] Step 2:

[1771] The terminal sends a remittance request to the server.

[1772] Input: Transfer request

[1773] Output: The request arrives at the server

[1774] What it does: Creates and sends a money transfer request using HTTPS.

[1775] Step 3:

[1776] The server will credit the specified amount to the child's account.

[1777] Input: Transfer request

[1778] Output: The child's account balance is updated.

[1779] What it does: Executes a query that updates the appropriate records in the database, adding the specified amount.

[1780] Step 4:

[1781] The server sends a notification of the transfer.

[1782] Input: Remittance information

[1783] Output: A notification is sent to the child's device.

[1784] Specific operation: Sends notifications using the push notification API.

[1785] Check your purchase history

[1786] Step 1:

[1787] The user (child) makes a payment using PayPay.

[1788] Input: Purchase amount, payment information

[1789] Output: PayPay payment completed

[1790] Specific operations: Scan the QR code with the PayPay app, enter the amount, and confirm the payment.

[1791] Step 2:

[1792] The terminal sends the payment information to the server.

[1793] Input: Payment information

[1794] Output: Payment information arrives at the server

[1795] Specific operation: After payment is completed, an HTTP request containing payment information is sent to the server.

[1796] Step 3:

[1797] The server stores the purchase history.

[1798] Input: Payment information

[1799] Output: Purchase history stored in the database

[1800] Specific Actions: Executes a query to insert payment information into the database.

[1801] Step 4:

[1802] The server notifies the parent's device of the purchase history.

[1803] Input: Purchase history

[1804] Output: A notification is sent to the parent's device.

[1805] Specific operation: Sends notifications to the parent's device using the push notification API.

[1806] Alert Settings

[1807] Step 1:

[1808] User (parent) sets alerts based on usage conditions.

[1809] Input: Alert condition, e.g., payment of 500 yen or more

[1810] Output: Save alert settings

[1811] Specific actions: Enter conditions on the "Alert Settings" page in the app and press the "Save" button.

[1812] Step 2:

[1813] The server monitors the purchase history.

[1814] Input: purchase history, alert conditions

[1815] Output: Monitoring results

[1816] Specific behavior: Periodically runs monitoring queries against the database.

[1817] Step 3:

[1818] The server notifies you when the condition is met.

[1819] Input: Monitoring results

[1820] Output: Alert notification on parent device

[1821] Specific behavior: When the conditions are met, an alert is sent using the push notification API.

[1822] Step 4:

[1823] The parent device receives the alert.

[1824] Input: Alert notification

[1825] Output: Display of alert notification

[1826] Specific behavior: Displays an alert as a pop-up notification on the device.

[1827] (Application example 1)

[1828] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[1829] Traditionally, when managing pocket money with cash, it is difficult for parents to keep track of how their children spend their money in detail, and it is also difficult to record where and how the child spends the money. This makes it difficult for parents to properly manage their children's money and for children to develop a healthy sense of money. Furthermore, with the spread of electronic money, there is a need for a safe and efficient way for parents to give pocket money to their children.

[1830] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[1831] In this invention, the server includes means for transferring electronic money from a parent's account to a child's account, means for storing the purchase history of the child's account in a central management device, means for displaying the child's purchase history on the parent's mobile information terminal, means for sending alerts based on conditions set by the parent, means for setting alerts based on changes in the balance of the child's account, and means for scheduling transfers from the parent's account to the child's account. This allows parents to manage their children's money efficiently and safely, and enables children to develop sound financial skills.

[1832] "Parent Account" refers to an online account used by a parent to manage electronic money.

[1833] A "child's account" is an online account used by a child to manage electronic money.

[1834] "Electronic money" is currency used in electronic form in place of cash.

[1835] A "means of transfer" is a means for transferring electronic money from a parent's account to a child's account.

[1836] "Purchase history" is a record of purchases made by a child using electronic money.

[1837] The "central management device" is a server that centrally manages all account information and transaction history.

[1838] A "personal digital assistant" is a mobile device such as a smartphone or tablet.

[1839] A "warning" is a notification issued to call attention when a set condition is met.

[1840] "Balance fluctuation" refers to the increase or decrease in the amount of electronic money in an account.

[1841] A "means for scheduling remittances" is a means for automatically sending remittances based on specified dates and conditions.

[1842] The present invention is a system for parents to give electronic pocket money to their children and manage how the money is spent. Specific embodiments of the present invention will be described in detail below.

[1843] System configuration

[1844] The system consists of the following elements:

[1845] 1. Parent and child mobile devices (smartphones, tablets, etc.)

[1846] 2. Central management device (server)

[1847] Hardware and Software

[1848] Hardware: Smartphones (iOS, Android), tablets

[1849] software:

[1850] Python: Programming Language

[1851] Flask: a web framework for building server-side APIs

[1852] SQLite: Manage users and purchase history as a database

[1853] User registration and account linking

[1854] The parent installs the application on their mobile device and registers as a new user. The parent then creates an account for the child and links it to their own account. The central management device (server) stores the parent and child account information in a database.

[1855] Distribution of pocket money

[1856] The parent accesses the application and enters the amount to transfer to the child's account. The device sends the transfer request to the server, which then updates the child's account with the specified amount. The child's device notifies them of the new transfer.

[1857] Check your purchase history

[1858] When a child makes a payment using an electronic payment service such as PayPay, the device sends the payment information to a server, which stores it in a database, allowing parents to check their child's most recent purchase history in real time through the app.

[1859] Alert Settings

[1860] Parents can set alerts based on specific usage conditions in the application, such as when a certain amount of money is spent. The server monitors the purchase history based on the set conditions and sends an alert to the parent's device when the condition is met.

[1861] Monitor balance fluctuations

[1862] Parents can set alerts based on changes in their child's account balance, such as when the balance exceeds or falls below a certain amount, allowing parents to monitor their child's spending behavior more closely.

[1863] Schedule a transfer

[1864] Parents can manage the account and schedule transfers, for example, to be sent automatically, such as a set amount at a certain time each month.

[1865] Specific examples

[1866] User registration and account linking: Parents install the application and create an account. Then, they create a child account and link it to the parent's account.

[1867] Distributing pocket money: A parent uses the application to send their child 500 yen in electronic money, enters the amount, and submits it. The server then credits the amount to the child's account.

[1868] Checking purchase history: When a child spends 200 yen at a stationery store, the information is sent to the server and stored in a database. Parents can check this information in the application.

[1869] Alert settings: If a parent sets the option to "send an alert if more than 500 yen is spent at once," and their child makes a purchase of 600 yen, an alert will be sent to the parent's device.

[1870] Prompt Sentence Examples

[1871] Remittance: Parent sends 500 yen to child.

[1872] Purchase history: A child spends 200 yen at the stationery store at school.

[1873] Alert: If a parent sets up a notification for purchases over 500 yen, a notification will be sent when the child makes a purchase of 600 yen.

[1874] The present invention enables parents to manage their children's finances efficiently and safely, and enables children to acquire a sound financial sense.

[1875] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[1876] Step 1:

[1877] The application is installed on the parent's mobile information terminal and a new user registration is performed.

[1878] Input: Parent's personal information, account creation information

[1879] Output: New user ID, parent account information

[1880] Specific behavior:

[1881] Parent downloads and launches the application.

[1882] The parent enters personal information (name, email address, password, etc.) and presses the account creation button.

[1883] The server stores the received information in a database and generates a new user ID.

[1884] Step 2:

[1885] Parents create accounts for their children and link them to their own accounts.

[1886] Input: Child's personal information, link information

[1887] Output: Child's new user ID, parent and child link information

[1888] Specific behavior:

[1889] A parent selects the "Create a Child Account" feature on the application.

[1890] Parents enter their child's personal information and press the link button.

[1891] The server stores the received information in a database and generates a new child ID.

[1892] The server links the parent's account with the child's account.

[1893] Step 3:

[1894] Parents use the application to transfer money to their children's accounts.

[1895] Input: Transfer amount, child's account ID

[1896] Output: Transfer completion notification, updated balance

[1897] Specific behavior:

[1898] The parent selects the transfer function in the application and enters the amount to transfer.

[1899] When the parent presses the send button, the terminal sends a remittance request to the server.

[1900] The server adds the transfer amount to the child's account and updates the database.

[1901] The server sends a notification of the completion of the remittance to the child's device.

[1902] Step 4:

[1903] The child makes the payment using an electronic payment service such as PayPay.

[1904] Input: payment amount, payment store information

[1905] Output: Purchase history, updated balance

[1906] Specific behavior:

[1907] The child makes an electronic payment at the store and completes the payment.

[1908] The child's device sends payment information (payment amount, store information) to the server.

[1909] The server stores the information in a database and updates the child's account balance.

[1910] Step 5:

[1911] Parents can view their child's purchase history in the app.

[1912] Input: Parent account ID, Child account ID

[1913] Output: Purchase history, purchase details

[1914] Specific behavior:

[1915] A parent selects the "Purchase History" feature in the application.

[1916] The server receives the parent's request and retrieves the child's purchase history from the database.

[1917] The server sends the acquired purchase history to the parent's device.

[1918] Step 6:

[1919] Parents can set alerts based on specific conditions.

[1920] Input: Warning condition (e.g., payment above a certain amount)

[1921] Output: Set warning conditions

[1922] Specific behavior:

[1923] Parents select the "Warning Settings" feature in the application.

[1924] The parent enters the warning conditions and presses the setting button.

[1925] The server stores the received alert conditions in a database.

[1926] Step 7:

[1927] The server monitors the purchase history based on the set conditions and sends an alert when the conditions are met.

[1928] Input: purchase history, warning conditions

[1929] Output: Warning notice

[1930] Specific behavior:

[1931] The server periodically checks the purchase history in the database.

[1932] If the set warning conditions are met, a warning notification will be sent to the parent device.

[1933] Step 8:

[1934] Parents schedule transfers to their children's accounts.

[1935] Input: remittance amount, schedule information (date, time, cycle)

[1936] Output: Scheduled transfer information

[1937] Specific behavior:

[1938] The parent selects the transfer schedule feature in the application.

[1939] The parent enters the transfer amount and schedule information and presses the setting button.

[1940] The server stores the received schedule information in a database.

[1941] The remittance will be processed automatically at the set date and time.

[1942] Furthermore, an emotion engine that estimates the user's emotion may be further combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59, and perform identification processing using the user's emotion.

[1943] The present invention is a system that allows parents to give their children electronic pocket money and manage how it is spent, and further combines it with an emotion engine that recognizes the user's emotions and provides various notifications and advice based on that data. Specific processing content based on an embodiment of the present invention will be described below.

[1944] System Configuration

[1945] The system consists of the following elements:

[1946] 1. Smartphone apps (devices) for parents and children

[1947] 2. Central Management Server (Server)

[1948] 3. Emotion Engine

[1949] User registration and account linking

[1950] 1. The user (parent) installs the app and opens the new user registration screen.

[1951] 2. The user (parent) enters information such as name, email address, and password.

[1952] 3. The terminal sends the entered information to the server.

[1953] 4. The server receives the information, registers the new user in the database, generates an account ID, and returns it to the device.

[1954] 5. The user (parent) selects the option to create a child account and enters the child's name and user ID.

[1955] 6. The device sends a child account creation request to the server.

[1956] 7. The server receives the request, creates a child account, links it to the parent account, generates a child account ID, and returns it to the device.

[1957] Distribution of pocket money

[1958] 1. The user (parent) logs into the app and selects the option to send pocket money.

[1959] 2. The user (parent) enters the amount to be transferred.

[1960] 3. The device sends a transfer request to the server, which includes the parent's account ID, the child's account ID, and the transfer amount.

[1961] 4. The server receives the transfer request, checks the parent and child account information in the database, adds the transfer amount to the child's account, updates the database, and returns a successful transfer notification to notify the child's account of the update.

[1962] 5. The device receives a notification from the server and notifies the child's app that a new transfer has been made.

[1963] Check your purchase history

[1964] 1. The user (child) makes a purchase using PayPay. Payments are made through the PayPay app.

[1965] 2. Once the payment is complete, the terminal sends the payment information (store name, amount, date and time, etc.) to the server.

[1966] 3. The server receives the payment information and stores it in a database, including the child's account ID.

[1967] 4. The user (parent) selects the option to view their child's purchase history within the app.

[1968] 5. The device sends a history request to the server.

[1969] 6. The server retrieves the child's latest payment information from the database and sends it back to the parent's device.

[1970] 7. The device displays the received history information in the parent app.

[1971] Alert Settings

[1972] 1. The user (parent) selects the alert setting option and enters a specific condition (e.g., a single payment of 500 yen or more).

[1973] 2. The device sends an alert setting request to the server, including the parent account ID and the alert conditions.

[1974] 3. The server receives the alert conditions and stores them in a database.

[1975] 4. As the server saves each payment entry to the database, it checks it against pre-defined alert conditions.

[1976] 5. When the condition is met (e.g., when the child spends more than 500 yen), the server sends an alert notification to the parent's device.

[1977] 6. The device receives the alert notification and displays the alert content in the parent's app.

[1978] Introducing the Emotion Engine

[1979] The terminal and server are equipped with an emotion engine that collects and analyzes the emotion data of users (parents and children).

[1980] Based on the emotional data obtained by the emotion engine, an alert is sent to the parent's device when certain conditions are met.

[1981] The server uses emotional data to analyze purchase history and provide appropriate advice and alerts to parents.

[1982] Specific examples

[1983] User registration and account linking

[1984] The user (parent) installed the app and created an account. Then, the user (parent) created a child account and linked the two accounts.

[1985] The server stored the parent and child information in a database.

[1986] Distribution of pocket money

[1987] The user (parent) accessed the app to send their child 500 yen in pocket money, entered the amount, and sent it.

[1988] The server added 500 yen to the child's account and sent the child a notification of the transfer.

[1989] Check your purchase history

[1990] The user (child) paid 200 yen with PayPay at a stationery store.

[1991] The server received this payment information and stored it in a database.

[1992] The user (parent) checked their child's most recent purchase history in the app and confirmed the payment at the stationery store.

[1993] Alert Settings

[1994] The user (parent) set it up so that an alert would be sent if their child spent more than 500 yen at one time.

[1995] A few days later, I spent 600 yen on my child's device to buy a toy.

[1996] When the server met the alert conditions, it sent a notification to the parent's device, and the user (parent) received the alert.

[1997] Examples of emotion engines

[1998] The user (child) was shopping at a toy store and the emotion engine recognized that the child was feeling very happy.

[1999] Based on this emotional data, the emotion engine notified the parents that their child had purchased an expensive item and was very happy.

[2000] Sarver offered some advice to parents: "If these kinds of expensive purchases are frequent, we recommend reconsidering your budget."

[2001] This system provides an environment where parents can manage their children's finances more transparently and with peace of mind, and children can safely use their pocket money without carrying cash. Furthermore, by combining it with an emotion engine, parents can receive monitoring and advice based on their children's emotional state, enabling them to provide more appropriate financial education.

[2002] The processing flow will be explained below.

[2003] User registration and account linking

[2004] Step 1:

[2005] The user (parent) installs the app and opens the new user registration screen.

[2006] Step 2:

[2007] The user (parent) enters information such as name, email address, and password.

[2008] Step 3:

[2009] The terminal transmits the input information to the server.

[2010] Step 4:

[2011] The server receives the information, registers the new user in the database, generates an account ID, and returns it to the device.

[2012] Step 5:

[2013] The user (parent) selects the option to create a child account.

[2014] Step 6:

[2015] The user (parent) enters the child's name and user ID.

[2016] Step 7:

[2017] The terminal sends a request to create a child account to the server.

[2018] Step 8:

[2019] The server receives the request, creates a child account, links it to the parent's account, generates a child account ID, and returns it to the device.

[2020] Distribution of pocket money

[2021] Step 1:

[2022] The user (parent) logs into the app and selects the option to transfer pocket money.

[2023] Step 2:

[2024] The user (parent) enters the remittance amount.

[2025] Step 3:

[2026] The device sends a transfer request to the server, which includes the parent's account ID, the child's account ID, and the transfer amount.

[2027] Step 4:

[2028] The server receives the transfer request and checks the parent and child account information in its database.

[2029] Step 5:

[2030] The server adds the transfer amount to the child's account and updates the database.

[2031] Step 6:

[2032] The server returns a successful transfer information and notifies the child account of the update.

[2033] Step 7:

[2034] The device receives a notification from the server and notifies the child's app that a new transfer has been made.

[2035] Check your purchase history

[2036] Step 1:

[2037] The user (child) makes purchases using PayPay. Payments are made through the app.

[2038] Step 2:

[2039] Once the payment is complete, the terminal sends the payment information (store name, amount, date and time, etc.) to the server.

[2040] Step 3:

[2041] The server receives the payment information and stores it in a database, including the child's account ID.

[2042] Step 4:

[2043] The user (parent) selects the option to view their child's purchase history within the app.

[2044] Step 5:

[2045] The terminal sends a history request to the server.

[2046] Step 6:

[2047] The server retrieves the child's latest payment information from the database and sends it back to the parent's device.

[2048] Step 7:

[2049] The device displays the received history information in the parent's app.

[2050] Alert Settings

[2051] Step 1:

[2052] The user (parent) selects the alert setting option and enters specific conditions (e.g., a single payment of 500 yen or more).

[2053] Step 2:

[2054] The device sends an alert setting request to the server, which includes the parent account ID and the alert conditions.

[2055] Step 3:

[2056] The server receives the alert conditions and stores them in a database.

[2057] Step 4:

[2058] As the server saves each payment entry to the database, it checks it against pre-defined alert conditions.

[2059] Step 5:

[2060] When a condition is met (e.g., when a child pays more than 500 yen), the server sends an alert notification to the parent's device.

[2061] Step 6:

[2062] The device receives an alert notification and displays the alert content in the parent's app.

[2063] Introducing the Emotion Engine

[2064] Step 1:

[2065] The terminal and the server are equipped with an emotion engine to collect emotion data from users (parents and children).

[2066] Step 2:

[2067] The emotion engine analyzes the user's facial expressions, voice, text input, etc. to recognize their current emotional state.

[2068] Step 3:

[2069] The terminal transmits the emotion data to the server.

[2070] Step 4:

[2071] The server receives the emotion data and stores it in a database.

[2072] Step 5:

[2073] The server analyzes purchase history and payment data based on emotional data and provides appropriate advice and alerts to parents.

[2074] Step 6:

[2075] The server sends an alert to the parent's device when a certain condition is met (for example, when a child makes an expensive purchase and is very happy).

[2076] Step 7:

[2077] The device receives an alert notification and displays the alert content in the parent's app.

[2078] Specific examples

[2079] Examples of emotion engines

[2080] Step 1:

[2081] A user (child) is shopping at a toy store, and the emotion engine recognizes that the child is feeling very happy.

[2082] Step 2:

[2083] The emotion engine sends information to the server based on this emotion data.

[2084] Step 3:

[2085] The server receives the emotion data and sends a notification to the parent's account.

[2086] Step 4:

[2087] The device will display a notification in the parent's app saying, "Your child has purchased an expensive item and is very happy."

[2088] Step 5:

[2089] The server offers parents advice: "If these kinds of expensive purchases are frequent, we recommend reconsidering your budget."

[2090] Example 2

[2091] Next, a description will be given of Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[2092] Until now, parents have had limited means to manage their children's spending and purchasing history, and this lack of transparency and efficiency has made it difficult to understand children's emotions and spending trends in real time, making it difficult to provide appropriate financial education.

[2093] The specific processing by the specific processing unit 290 of the data processing device 12 in Example 2 is realized by the following means. In this invention, the server includes means for transferring digital currency from a parent's account to a child's account, means for storing the purchase history of the child's account on the server, means for displaying the child's purchase history on the parent's terminal, means for sending alerts based on conditions set by the parent, and means for collecting and analyzing user emotion data and notifying the user based on the results. This allows parents to manage their children's finances transparently and efficiently, and also allows them to understand their children's emotions and payment trends, making it possible to provide more appropriate financial education to their children.

[2094] "Parent Account" means an electronic account owned by a Parent that contains Personally Identifiable Information for managing and transferring Digital Currency.

[2095] A "child's account" is an electronic account owned by a child that contains personally identifiable information for the purpose of receiving digital currency from a parent and managing purchase history.

[2096] "Digital currency" is currency that exists in electronic form and is used for online transactions and transfers.

[2097] "Purchase History" means a history of payments made on a Child's account, including details such as the location, amount, date and time of the payment.

[2098] "Server" refers to a centralized management system for storing, processing, and managing data, and is a device that stores and manages user account information and purchase history.

[2099] "Device" refers to a device used by parents and children, such as a smartphone or tablet, that is capable of communication.

[2100] An "alert" refers to a notification or warning sent to a parent's device when certain conditions are met, such as to warn them about a large expenditure made by their child.

[2101] "Emotional data" refers to information indicative of a user's emotional state, and is data collected and analyzed using an emotion engine.

[2102] An "emotion engine" refers to technology that recognizes emotions from a user's facial expressions and behavior, and collects and analyzes the data.

[2103] "Notification" refers to the act of sending important information or alerts to a parent's device, and is a way for parents to keep track of their child's situation.

[2104] "Application program" refers to software that enables communication between parent and child devices, and generally refers to smartphone applications.

[2105] This invention is a system that allows parents to electronically give pocket money to their children and manage their child's spending. It also incorporates an emotion engine that recognizes the user's emotions in real time and provides notifications and advice based on those emotions. This system makes money management transparent and efficient for parents and children, and allows parents to understand their children's emotions and spending habits.

[2106] System Configuration

[2107] The system consists of the following elements:

[2108] 1. Smartphone apps (devices) used by parents and children

[2109] 2. Central Management Server (Server)

[2110] 3. Emotion Engine (emotion data collection and analysis system)

[2111] User registration and account linking

[2112] 1. The user (parent) installs the app on their smartphone and opens the new user registration screen.

[2113] 2. The user (parent) enters information such as name, email address, and password.

[2114] 3. The terminal sends the entered information to a central management server (e.g., AWS EC2).

[2115] 4. The server receives the information, registers the new user in a database (e.g., MySQL), generates an account ID, and returns it to the device.

[2116] 5. The user (parent) selects the Create Child Account option and enters the child's name and user ID.

[2117] 6. The device sends a child account creation request to the server.

[2118] 7. The server receives the request, creates a child account, links it to the parent account, generates a child account ID, and returns it to the device.

[2119] Distribution of pocket money

[2120] 1. The user (parent) logs into the app and selects the option to send pocket money.

[2121] 2. The user (parent) enters the amount to be transferred.

[2122] 3. The device sends a transfer request to the server, which includes the parent's account ID, the child's account ID, and the transfer amount.

[2123] 4. The server receives the transfer request, checks the parent and child account information in the database, adds the transfer amount to the child's account, and updates the database.

[2124] 5. The server returns a successful transfer information and notifies the child account of the update.

[2125] 6. The device receives a notification from the server and notifies the child's app that a new transfer has been made.

[2126] Check your purchase history

[2127] 1. The user (child) makes a purchase using an electronic payment system such as PayPay. PayPay payments are made through the app.

[2128] 2. Once the payment is complete, the terminal sends the payment information (store name, amount, date and time, etc.) to the server.

[2129] 3. The server receives the payment information and stores it in a database, including the child's account ID.

[2130] 4. The user (parent) selects the option to view their child's purchase history within the app.

[2131] 5. The device sends a history request to the server.

[2132] 6. The server retrieves the child's latest payment information from the database and sends it back to the parent's device.

[2133] 7. The device displays the received history information in the parent app.

[2134] Alert Settings

[2135] 1. The user (parent) selects the alert setting option and enters a specific condition (e.g., a single payment of 500 yen or more).

[2136] 2. The device sends an alert setting request to the server, including the parent account ID and the alert conditions.

[2137] 3. The server receives the alert conditions and stores them in a database.

[2138] 4. As the server saves each payment entry to the database, it checks it against pre-defined alert conditions.

[2139] 5. When the condition is met (e.g., when the child spends more than 500 yen), the server sends an alert notification to the parent's device.

[2140] 6. The device receives the alert notification and displays the alert content in the parent's app.

[2141] Introducing the Emotion Engine

[2142] 1. The device and server use an emotion engine (e.g., Microsoft Azure Emotion API) to collect emotion data from users (parents and children).

[2143] 2. The device sends the acquired emotion data to the server.

[2144] 3. The server receives the emotion data and stores it in a database.

[2145] 4. The server analyzes the emotion data for specific conditions (e.g., high levels of joy or anger).

[2146] 5. Based on the analysis results, the server sends appropriate advice and alerts to the parent's device.

[2147] 6. The device receives a notification and displays advice or alert details in the parent's app.

[2148] Examples of concrete examples and prompts

[2149] Specific examples

[2150] The user (parent) installed the app and created an account, then created a child account and linked the two accounts.

[2151] The user (parent) accessed the app, entered the amount, and sent it to send 500 yen pocket money to their child.

[2152] The user (child) paid 200 yen with PayPay at a stationery store.

[2153] The server received this payment information and stored it in a database.

[2154] The user (parent) checked their child's most recent purchase history in the app and confirmed the payment at the stationery store.

[2155] The user (parent) set it up so that an alert would be sent if their child spent more than 500 yen at one time.

[2156] A few days later, the user (child) uses 600 yen to buy a toy.

[2157] When the server met the alert conditions, it sent a notification to the parent's device, and the user (parent) received the alert.

[2158] The user (child) was shopping at a toy store and the emotion engine recognized that the child was feeling very happy.

[2159] Sarver offered some advice to parents: "If these kinds of expensive purchases are frequent, we recommend reconsidering your budget."

[2160] Prompt Sentence Examples

[2161] User Registration and Account Linking:

[2162] "Parents open the new user registration screen and create an account by entering their name, email address, and password. They then enter their child's name and user ID to create and link their child's account."

[2163] Pocket money distribution:

[2164] "Parents simply log into the app, select the option to send pocket money, enter the amount to send and send."

[2165] Check your purchase history:

[2166] "A child pays 200 yen at a stationery store with PayPay, and the parent checks the purchase history on the app."

[2167] Alert Settings:

[2168] "Parents can set up an alert to be sent if more than 500 yen is spent in a single transaction."

[2169] Introducing the Emotion Engine:

[2170] "When a child is shopping in a toy store, the emotion engine recognizes the child's joy and notifies the parent."

[2171] This invention allows parents to manage their children's money transparently and efficiently, and by understanding their children's emotions and spending habits, they can provide them with appropriate financial education, allowing the whole family to manage their pocket money with greater peace of mind.

[2172] The flow of the identification process in the second embodiment will be described with reference to FIG.

[2173] User registration and account linking

[2174] Step 1:

[2175] The user (parent) installs the app on their smartphone and opens the new user registration screen. Input: Parent's personal information (name, email address, password). Output: A new user registration request is generated on the device.

[2176] Step 2:

[2177] The device sends the entered information to a central server. Input: New user registration request including parent's personal information. Output: Data sent to the server.

[2178] Step 3:

[2179] The server receives the information and registers the new user in the database. Input: New user registration request. Output: New account ID generated and registered.

[2180] Step 4:

[2181] The server returns the generated account ID to the terminal. Input: New account ID. Output: Return of account ID.

[2182] Step 5:

[2183] The user (parent) selects the Create Child Account option and enters the child's name and user ID. Input: Child's personal information. Output: A child account creation request is generated on the device.

[2184] Step 6:

[2185] The device sends a request to the server to create a child account. Input: The request, including the child's personal information. Output: The data sent to the server.

[2186] Step 7:

[2187] The server receives the request, creates a child account, and associates it with the parent's account. Input: Child account creation request. Output: New child account ID is generated and registered in the database.

[2188] Step 8:

[2189] The server returns the generated child account ID to the device. Input: New child account ID. Output: Return of account ID.

[2190] Distribution of pocket money

[2191] Step 1:

[2192] The user (parent) logs in to the app and selects the option to transfer pocket money. Input: User authentication information (login ID, password). Output: Notification of successful login authentication.

[2193] Step 2:

[2194] The user (parent) inputs the amount to be transferred. Input: Amount to be transferred. Output: A transfer request is generated on the terminal.

[2195] Step 3:

[2196] The device sends a transfer request to the server. Input: A request containing the parent's account ID, the child's account ID, and the amount to transfer. Output: The data sent to the server.

[2197] Step 4:

[2198] The server receives the transfer request and checks the parent and child account information in the database. Input: Transfer request. Output: Start of the process to update the transfer record in the database.

[2199] Step 5:

[2200] The server adds the transfer amount to the child's account and updates the database. Input: Parent and child account information and transfer amount. Output: Database update.

[2201] Step 6:

[2202] The server returns a successful transfer information to the terminal and notifies the update of the child account. Input: Successful transfer information. Output: Notification of transfer completion sent to the terminal.

[2203] Step 7:

[2204] The device receives a notification from the server and notifies the child's app that a new transfer has been made. Input: Notification of transfer completion. Output: Notification displayed in the child's app.

[2205] Check your purchase history

[2206] Step 1:

[2207] The user (child) makes a purchase using an electronic payment system such as PayPay. Input: PayPay account information and payment information. Output: Receipt information after payment is completed.

[2208] Step 2:

[2209] Once the payment is complete, the terminal sends the payment information to the server. Input: Payment information such as store name, amount, date and time. Output: Data sent to the server.

[2210] Step 3:

[2211] The server receives the payment information and stores it in a database. Input: Payment information. Output: Payment information stored in a database.

[2212] Step 4:

[2213] User (parent) selects option within app to review child's purchase history. Input: Purchase history review request. Output: Request generated on device.

[2214] Step 5:

[2215] The device sends a history request to the server. Input: Purchase history confirmation request. Output: Data sent to the server.

[2216] Step 6:

[2217] The server retrieves the child's latest payment information from the database and sends it back to the parent's device. Input: Purchase history confirmation request. Output: Extraction and return of purchase history data.

[2218] Step 7:

[2219] The device displays the received history information in the parent app. Input: Purchase history data. Output: Purchase history displayed in the parent app.

[2220] Alert Settings

[2221] Step 1:

[2222] The user (parent) selects the alert setting option and enters the specific condition. Input: Alert condition (e.g., single payment of 500 yen or more). Output: An alert setting request is generated on the terminal.

[2223] Step 2:

[2224] The device sends an alert setting request to the server. Input: Parent account ID, request containing alert conditions. Output: Data sent to the server.

[2225] Step 3:

[2226] The server receives the alert conditions and stores them in the database. Input: Alert configuration request. Output: Alert conditions stored in the database.

[2227] Step 4:

[2228] When the server saves each payment information to the database, it checks it against the pre-defined alert conditions. Input: Payment information and alert conditions. Output: Alert condition check results.

[2229] Step 5:

[2230] The server sends an alert notification to the parent device when the condition is met. Input: Payment information that meets the condition. Output: Sending an alert notification.

[2231] Step 6:

[2232] The device receives the alert notification and displays the alert content in the parent app. Input: Alert notification. Output: Alert content displayed in the app.

[2233] Introducing the Emotion Engine

[2234] Step 1:

[2235] The device and server use an emotion engine to collect user emotion data. Input: User's facial expression, voice, and behavior data. Output: Acquisition of emotion data.

[2236] Step 2:

[2237] The device sends the acquired emotion data to the server. Input: Emotion data. Output: Data sent to the server.

[2238] Step 3:

[2239] The server receives the emotion data and stores it in a database. Input: Emotion data. Output: Emotion data stored in a database.

[2240] Step 4:

[2241] The server analyzes specific conditions based on emotion data. Input: Emotion data. Output: Generates analysis results.

[2242] Step 5:

[2243] The server sends appropriate advice or alerts to the parent device based on the analysis results. Input: Analysis results. Output: Sending advice or alerts.

[2244] Step 6:

[2245] The device receives the notification and displays the advice or alert content in the parent app. Input: Advice or alert notification. Output: Advice or alert content displayed in the app.

[2246] (Application example 2)

[2247] Next, a description will be given of Application Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[2248] Today's parents need a way to efficiently monitor their children's financial management and spending habits. However, while many systems on the market can electronically transfer pocket money and manage spending histories, they lack the functionality to provide advice and notifications based on the child's emotional state. As a result, parents find it difficult to consider not only their spending habits but also their children's emotions when providing sound financial education. This means that there is a need to solve the problem of children not being able to learn appropriate financial management in an environment that is not conducive to financial management.

[2249] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 2 is realized by the following means.

[2250] In this invention, the server includes means for transferring electronic money from the parent's account to the child's account, means for storing the purchase history of the child's account on the server, means for displaying the child's purchase history on the parent's terminal, means for sending alerts based on conditions set by the parent, and means for analyzing emotional data and providing notifications and advice based on that data. This allows parents to not only efficiently manage their children's finances, but also receive appropriate advice and notifications based on their children's emotional state.

[2251] "Parent Account" means an electronic money account managed by a parent and used to transfer electronic pocket money to a child.

[2252] A "child's account" is an electronic money account managed by a child, and is used to receive and use pocket money sent by a parent.

[2253] "Electronic money" is a digital form of currency that can be used via the Internet or dedicated terminals, and is used to purchase goods and services in the same way as cash.

[2254] "Purchase history" is a record of payments made by a child, and includes information such as the date and time of the payment, the amount, and the name of the store.

[2255] "Server" refers to a computer system that stores, processes, and manages data and serves as the central control for this invention.

[2256] A "terminal" is an electronic device that a user operates, and includes smartphones, tablets, computers, etc.

[2257] An "alert" is a feature that notifies users when a set condition is met, and issues a warning based on a specific action or condition.

[2258] "Emotion data" is digital information that represents the user's emotional state and is collected and analyzed by the emotion engine.

[2259] An "emotion engine" is a software system that recognizes a user's emotional state and collects and analyzes it as data.

[2260] A "notification" is a message or warning sent by the system to a user based on a specific condition.

[2261] "Advice" is a recommendation or advice provided based on emotional data and spending history, and is useful information for parents to support their children in managing their finances.

[2262] This invention is a system that allows parents to give their children electronic pocket money and manage how it is spent, and it also combines an emotion engine that recognizes the user's emotions and provides various notifications and advice based on that data. Specific processing content based on an embodiment of the present invention will be described below.

[2263] System Configuration

[2264] The system consists of the following elements:

[2265] 1. Parent and child devices (smartphones, tablets, etc.)

[2266] 2. Central Management Server

[2267] 3. Emotion Engine

[2268] User registration and account linking

[2269] The parent's device installs the application and opens the new user registration screen. The parent enters information such as name, email address, and password, and the device sends this information to the server. The server receives this information and registers the new user in its database. The parent then selects the option to create a child account and enters the child's name and user ID. The device sends this information to the server, and the server links the parent and child accounts.

[2270] Distribution of pocket money

[2271] The parent logs into the application and selects the option to transfer pocket money. The transfer amount is entered and the device sends a transfer request to the server. The server receives the transfer request and checks the parent and child's account information in the database. The server adds the transfer amount to the child's account and updates the database. The parent's device is notified of the successful transfer and notifies the child's account of the update.

[2272] Check your purchase history

[2273] When a child uses a device to make a purchase using electronic money, payment information (store name, amount, date and time, etc.) is sent from the device to the server. The server receives this payment information and stores it in a database. Parents can check their child's purchase history within the application, and the server sends the latest payment information back to the parent's device.

[2274] Alert Settings

[2275] The parent device selects the alert setting option and enters a specific condition (e.g., a single payment of 500 yen or more). The device sends an alert setting request to the server, which stores the alert condition in a database. When the child makes a payment, the server checks the payment information and sends an alert notification to the parent device if the condition is met.

[2276] Introducing the Emotion Engine

[2277] The device and server are equipped with an emotion engine that collects and analyzes the emotion data of users (parents and children). The server uses the emotion data to analyze purchase history and provide appropriate advice and alerts to parents.

[2278] Specific examples

[2279] User Registration and Account Linking:

[2280] The parent installed the app and created an account, then created a child account and linked the two accounts.

[2281] The server stored the parent and child information in a database.

[2282] Pocket money distribution:

[2283] A parent accessed the app to send their child 500 yen in pocket money, entered the amount, and sent it.

[2284] The server added 500 yen to the child's account and sent the child a notification of the transfer.

[2285] Check your purchase history:

[2286] My child paid 200 yen at a stationery store using electronic money.

[2287] The server received this payment information and stored it in a database.

[2288] The parent checked their child's recent purchase history in the app and confirmed the payment at the stationery store.

[2289] Alert Settings:

[2290] Parents set up an alert to be sent if their children spent more than 500 yen at one time.

[2291] A few days later, my child spent 600 yen on the device to buy a toy.

[2292] When the server met the alert conditions, it sent a notification to the parent's device, and the parent received the alert.

[2293] Examples of emotion engines:

[2294] A child is shopping at a toy store and the emotion engine recognizes that the child is feeling very happy.

[2295] The server notified the parents that their child had purchased an expensive item and was very happy.

[2296] Sarver offered some advice to parents: "If these kinds of expensive purchases are frequent, we recommend reconsidering your budget."

[2297] Prompt Sentence Examples

[2298] "A user registers as a parent (parent1), links a child (child1), and then sends 1,000 yen in pocket money. When the child buys a toy for 600 yen and feels very happy at the time, simulate using Python what kind of notification will be sent to the parent."

[2299] By implementing the invention in this way, parents can not only manage their children's finances efficiently, but also receive appropriate advice and notifications based on emotional data.

[2300] The flow of the specific processing in the application example 2 will be described with reference to FIG.

[2301] Step 1:

[2302] The user (parent) installs the application on their device and opens the new user registration screen. The parent enters information such as their name, email address, and password. The entered information is sent to the server, which receives it and registers it as the parent's account in its database. The parent then selects the option to create a child account and enters the child's name and user ID. This causes the device to send a request to create a child account to the server.

[2303] Input: Parent's name, email address, password, child's name, user ID

[2304] Output: Parent and child account registration in database, account linking

[2305] Step 2:

[2306] The server receives the child account creation request and links the parent and child accounts. It generates account IDs for both the parent and child and stores the linking information in the database. It notifies the device that the parent and child accounts have been successfully linked.

[2307] Input: Child account creation request

[2308] Output: Account linking information saved in the database, notification of link completion

[2309] Step 3:

[2310] The user (parent) logs into the application on their device and selects the option to transfer pocket money. The parent enters the amount to transfer and the device sends this transfer request to the server. The server receives the transfer request and checks the parent and child account information in the database. It adds the transfer amount to the child's account and updates the database.

[2311] Input: Transfer amount, parent and child account information

[2312] Output: Transfer amount added to child account, database updated

[2313] Step 4:

[2314] The server notifies the parent's device of the successful transfer and updates the child's account. The parent's device receives this notification and displays the new transfer.

[2315] Input: Remittance success information

[2316] Output: Remittance notification to parent and child devices

[2317] Step 5:

[2318] When purchasing a product, the child's device pays with electronic money. Payment information (store name, amount, date and time, etc.) is sent from the device to the server. The server receives the payment information and stores it in a database. The payment information also includes automatically generated emotion data.

[2319] Input: Payment information (store name, amount, date and time, etc.), emotional data

[2320] Output: Payment information saved in database

[2321] Step 6:

[2322] The parent selects the option to check the purchase history within the application and retrieves the child's latest payment information from the server. The server searches the database for the relevant payment information and sends it back to the parent's device. The parent's device receives this information and displays the purchase history.

[2323] Input: Purchase history request

[2324] Output: Provides up-to-date payment information and displays purchase history

[2325] Step 7:

[2326] The parent device selects the alert setting option and enters a specific condition (e.g., a single payment of 500 yen or more). The device sends this alert setting request to the server, which stores this alert condition in its database.

[2327] Input: Alert Condition

[2328] Output: Alert conditions saved in database

[2329] Step 8:

[2330] When the server saves each payment in the database, it checks it against pre-defined alert conditions, and if a condition is met (e.g., when a child spends more than 500 yen), it sends an alert notification to the parent's device.

[2331] Input: Payment information, Alert conditions

[2332] Output: Alert notification when the condition is met

[2333] Step 9:

[2334] The device and server are equipped with an emotion engine that collects and analyzes the user's emotion data. The server uses the emotion data to analyze purchase history and provide appropriate advice and alerts to parents.

[2335] Input: Emotional data, purchase history

[2336] Output: Providing advice and alerts based on sentiment analysis

[2337] Prompt Sentence Examples

[2338] "A user registers as a parent (parent1), links a child (child1), and then sends 1,000 yen in pocket money. When the child buys a toy for 600 yen and feels very happy at the time, simulate using Python what kind of notification will be sent to the parent."

[2339] The specific processing unit 290 transmits the result of the specific processing to the headset type terminal 314. In the headset type terminal 314, the control unit 46A causes the speaker 240 and the display 343 to output the result of the specific processing. The microphone 238 acquires audio indicating a user input regarding the result of the specific processing. The control unit 46A transmits audio data indicating the user input acquired by the microphone 238 to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the audio data.

[2340] The data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of the data generation model 58 is ChatGPT (Internet Search<URL: https: / / openai.com / blog / chatgpt> ), Gemini (Internet search <url: https: gemini.google.com ?hl="ja">) and other generation AIs. The data generation model 58 is obtained by performing deep learning on a neural network. A prompt including an instruction is input to the data generation model 58, and inference data such as voice data indicating voice, text data indicating text, and image data indicating an image is also input. The data generation model 58 performs inference on the input inference data in accordance with the instruction indicated by the prompt, and outputs the inference result in a data format such as voice data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[2341] In the above embodiment, an example was given in which the specific processing is performed by the data processing device 12, but the technology of the present disclosure is not limited to this, and the specific processing may be performed by the headset type terminal 314.

[2342] [Fourth embodiment]

[2343] FIG. 7 shows an example of the configuration of a data processing system 410 according to the fourth embodiment.

[2344] 7, a data processing system 410 includes a data processing device 12 and a robot 414. An example of the data processing device 12 is a server.

[2345] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[2346] The robot 414 includes a computer 36, a microphone 238, a speaker 240, a camera 42, a communication I / F 44, and a control target 443. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The microphone 238, the speaker 240, the camera 42, and the control target 443 are also connected to the bus 52.

[2347] The microphone 238 receives instructions and the like from the user 20 by receiving voice uttered by the user 20. The microphone 238 captures the voice uttered by the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio in accordance with instructions from the processor 46.

[2348] Camera 42 is a small digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor, and captures images of the surroundings of user 20 (for example, an imaging range defined by an angle of view equivalent to the field of vision of a typical healthy person).

[2349] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 control the exchange of various information between the processor 46 and the processor 28 via the network 54. The exchange of various information between the processor 46 and the processor 28 using the communication I / Fs 44 and 26 is carried out in a secure state.

[2350] The control object 443 includes a display device, LEDs in the eyes, and motors for driving the arms, hands, and feet. The posture and gestures of the robot 414 are controlled by controlling the motors of the arms, hands, and feet. Some of the emotions of the robot 414 can be expressed by controlling these motors. In addition, the facial expressions of the robot 414 can also be expressed by controlling the light emission state of the LEDs in the eyes of the robot 414.

[2351] Fig. 8 shows an example of the main functions of the data processing device 12 and the robot 414. As shown in Fig. 8, in the data processing device 12, a specific process is performed by the processor 28. A specific process program 56 is stored in the storage 32.

[2352] The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific processing is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[2353] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[2354] In the robot 414, the processor 46 performs the reception output process. A reception output program 60 is stored in the storage 50. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[2355] Next, a description will be given of the specific processing performed by the specific processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[2356] The present invention is a system for parents to give electronic pocket money to their children and manage how the money is spent. Specific processing contents based on an embodiment of the present invention will be described below.

[2357] System Configuration

[2358] The system consists of the following elements:

[2359] 1. Smartphone apps (devices) for parents and children

[2360] 2. Central Management Server (Server)

[2361] User registration and account linking

[2362] 1. The user (parent) installs the app and registers as a new user.

[2363] 2. The user (parent) creates an account for the child and links it to their own account.

[2364] 3. The server stores the parent and child account information in a database.

[2365] Distribution of pocket money

[2366] 1. The user (parent) accesses the app and enters the amount to transfer to their child's account.

[2367] 2. The terminal sends a remittance request to the server.

[2368] 3. The server receives the request and credits the specified amount to the child's account.

[2369] 4. Your child's device will notify you of a new transfer.

[2370] Check your purchase history

[2371] 1. When a user (child) makes a payment with PayPay, the terminal sends the payment information to the server.

[2372] 2. The server stores the payment information in a database.

[2373] 3. Users (parents) can check their children's purchase history in real time through the app.

[2374] 4. The parent's device will notify them of their latest purchase history.

[2375] Alert Settings

[2376] 1. The user (parent) sets up alerts in the app based on specific usage conditions (e.g., when payments exceed a certain amount).

[2377] 2. The server monitors the purchase history based on the set conditions.

[2378] 3. If the condition is met, the server sends an alert to the parent device.

[2379] 4. The parent's device notifies the parent of the alert and displays detailed information.

[2380] Specific examples

[2381] User registration and account linking

[2382] The user (parent) installed the app and created an account. Then, the user (parent) created a child account and linked the two accounts.

[2383] The server stored the parent and child information in a database.

[2384] Distribution of pocket money

[2385] The user (parent) accessed the app to send their child 500 yen in pocket money, entered the amount, and sent it.

[2386] The server added 500 yen to the child's account and sent the child a notification of the transfer.

[2387] Check your purchase history

[2388] The user (child) paid 200 yen with PayPay at a stationery store.

[2389] The server received this payment information and stored it in a database.

[2390] The user (parent) checked their child's most recent purchase history in the app and confirmed the payment at the stationery store.

[2391] Alert Settings

[2392] The user (parent) set it up so that an alert would be sent if their child spent more than 500 yen at one time.

[2393] A few days later, I spent 600 yen on my child's device to buy a toy.

[2394] When the server met the alert conditions, it sent a notification to the parent's device, and the user (parent) received the alert.

[2395] This system provides parents with a more transparent and secure environment for managing their children's finances, and allows children to safely use their pocket money without having to carry cash.

[2396] The processing flow will be explained below.

[2397] User registration and account linking

[2398] Step 1:

[2399] The user (parent) installs the app and opens the new user registration screen.

[2400] The user (parent) enters information such as name, email address, and password.

[2401] Step 2:

[2402] The terminal transmits the input information to the server.

[2403] Step 3:

[2404] The server receives the information and registers the new user in its database.

[2405] The server generates an account ID and returns it to the device.

[2406] Step 4:

[2407] The user (parent) selects the option to create a child account.

[2408] The user (parent) enters the child's name and user ID.

[2409] Step 5:

[2410] The terminal sends a request to create a child account to the server.

[2411] Step 6:

[2412] The server receives the request, creates a child account, and associates it with the parent account.

[2413] The server generates a child account ID and returns it to the device.

[2414] Distribution of pocket money

[2415] Step 1:

[2416] The user (parent) logs into the app and selects the option to transfer pocket money.

[2417] The user (parent) enters the remittance amount.

[2418] Step 2:

[2419] The device sends a transfer request to the server, which includes the parent's account ID, the child's account ID, and the transfer amount.

[2420] Step 3:

[2421] The server receives the transfer request and checks the parent and child account information in its database.

[2422] The server adds the transfer amount to the child's account and updates the database.

[2423] The server returns a successful transfer information and notifies the child account of the update.

[2424] Step 4:

[2425] The device receives a notification from the server and notifies the child's app that a new transfer has been made.

[2426] Check your purchase history

[2427] Step 1:

[2428] The user (child) makes purchases using PayPay. Payments are made through the app.

[2429] Step 2:

[2430] Once the payment is complete, the terminal sends the payment information (store name, amount, date and time, etc.) to the server.

[2431] Step 3:

[2432] The server receives the payment information and stores it in a database, including the child's account ID.

[2433] Step 4:

[2434] The user (parent) selects the option to view their child's purchase history within the app.

[2435] Step 5:

[2436] The terminal sends a history request to the server.

[2437] Step 6:

[2438] The server retrieves the child's latest payment information from the database and sends it back to the parent's device.

[2439] Step 7:

[2440] The device displays the received history information in the parent's app.

[2441] Alert Settings

[2442] Step 1:

[2443] The user (parent) selects the alert setting option and enters specific conditions (e.g., a single payment of 500 yen or more).

[2444] Step 2:

[2445] The device sends an alert setting request to the server, which includes the parent account ID and the alert conditions.

[2446] Step 3:

[2447] The server receives the alert conditions and stores them in a database.

[2448] Step 4:

[2449] As the server saves each payment entry to the database, it checks it against pre-defined alert conditions.

[2450] Step 5:

[2451] When a condition is met (e.g., when a child pays more than 500 yen), the server sends an alert notification to the parent's device.

[2452] Step 6:

[2453] The device receives an alert notification and displays the alert content in the parent's app.

[2454] Example 1

[2455] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[2456] Today's children are increasingly using electronic money instead of carrying cash, but to make it easier for parents to manage their children's finances, a transparent and safe system is needed. It is also desirable for parents to monitor their children's spending in real time and set alerts as necessary. However, current systems do not adequately provide such functionality.

[2457] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[2458] In this invention, the server includes means for transferring electronic money from a parent's account to a child's account, means for storing the purchase history of the child's account on the server, means for displaying the child's purchase history on the parent's terminal, means for sending alerts based on conditions set by the parent, means for storing the parent and child's account information in a database, means for sending a remittance request to the server using HTTPS, and means for the server to send a remittance notification via a push notification API. This allows parents to keep track of their child's financial management in real time and receive appropriate alerts.

[2459] "Parent Account" means an account used by a parent to transfer and manage electronic money to a child.

[2460] A "child's account" is an account used by a child to receive electronic money transferred from a parent and use it for payments, etc.

[2461] "Electronic money" refers to currency exchanged electronically in place of cash, and is used for online or offline payments.

[2462] A "transfer request" is a request to transfer electronic money from a parent's account to a child's account.

[2463] A "parent's device" is an electronic device such as a smartphone or tablet used by the parent to transfer electronic money and check purchase history.

[2464] A "child's device" is an electronic device such as a smartphone or tablet used by a child, which is used to make payments using electronic money.

[2465] A "server" is a central management system that receives requests from multiple terminals and stores and processes data.

[2466] "Database" refers to a system for storing and managing data such as parent and child account information and purchase history.

[2467] "HTTPS" is a communication protocol for encrypting and sending data over the Internet, enabling secure data transmission.

[2468] "Push notifications" are notifications that are sent in real time from a server to a device, and are used to instantly inform users of important information such as money transfers, purchase history, and alerts.

[2469] MODE FOR CARRYING OUT THE INVENTION

[2470] The present invention is a system that allows parents to give electronic pocket money to their children and manage how that money is spent. Specific processing details of the present invention will be described below.

[2471] System Configuration

[2472] The system consists of the following elements:

[2473] 1. Smartphone apps (devices) for parents and children

[2474] 2. Central Management Server (Server)

[2475] 3. Database System

[2476] 4. Communication Protocol (HTTPS)

[2477] 5. Push notification services

[2478] User registration and account linking

[2479] The user (parent) installs a dedicated app on their smartphone.

[2480] Hardware used: Smartphone (e.g. iPhone, Android smartphone)

[2481] Software used: Dedicated app (e.g. PocketMoneyApp)

[2482] Parents launch the app and enter their name, email address, and password to register.

[2483] Parents then enter their child's information (name, age) to create an account for their child and link it to their own account.

[2484] The server receives this information and stores it in a database (e.g. MySQL).

[2485] Distribution of pocket money

[2486] The user (parent) accesses the app and enters the amount they want to send to their child.

[2487] The terminal sends the transfer request to the server using HTTPS.

[2488] The server receives the request and credits the child's account with the specified amount, and the credited transfer information is saved in a database.

[2489] The server uses a push notification service to send a remittance notification to the child's device.

[2490] Check your purchase history

[2491] When a user (child) makes a payment at a store using electronic money (e.g., PayPay), the child's terminal collects payment information and sends it to the server.

[2492] The server receives the payment information and stores it in a database.

[2493] Users (parents) can check their children's purchase history in real time through the app.

[2494] The server also notifies the parent's device of the latest purchase history.

[2495] Alert Settings

[2496] Users (parents) can set alerts within the app when certain usage conditions are met (e.g., payments of 500 yen or more).

[2497] The server monitors the purchase history based on set conditions.

[2498] If the condition is met, the server sends an alert to the parent device.

[2499] The parent's device notifies the parent of the received alert and displays detailed information.

[2500] Specific examples

[2501] User registration and account linking

[2502] The user (parent) installs the dedicated app, creates an account, then creates a child account and links the two accounts.

[2503] The server stores parent and child information in a database.

[2504] Distribution of pocket money

[2505] The user (parent) accessed the app and sent 500 yen to their child.

[2506] The server adds 500 yen to the child's account and notifies the child of the transfer via push notification.

[2507] Check your purchase history

[2508] The user (child) paid 200 yen using electronic money at a stationery store.

[2509] The server receives this payment information and stores it in a database.

[2510] The user (parent) checks their child's latest purchase history in the app and confirms payments at the stationery store.

[2511] Alert Settings

[2512] The user (parent) sets an alert in the app for payments over 500 yen.

[2513] A few days later, when a 600 yen purchase is made on the child's device, the server will send a notification to the parent's device, as the alert conditions have been met.

[2514] The user (parent) will receive an alert to check the details.

[2515] The above is a specific embodiment of the present invention, and by using this system, parents can easily manage how their children's pocket money is spent. In addition, the real-time monitoring and alert functions allow parents to manage their children's pocket money with peace of mind.

[2516] The flow of the identification process in the first embodiment will be described with reference to FIG.

[2517] User registration and account linking

[2518] Step 1:

[2519] The user (parent) installs a dedicated app.

[2520] Input: Download the app from the App Store or Google Play

[2521] Output: The app is installed on your phone.

[2522] Specific actions: Operate your smartphone to search for and download the app, and complete the installation.

[2523] Step 2:

[2524] The user (parent) registers a new user on the app.

[2525] Input: Name, Email Address, Password

[2526] Output: New account created

[2527] Specific actions: Launch the app, enter your name, email address, and password, and press the "Register" button.

[2528] Step 3:

[2529] The user (parent) creates an account for their child and links it to their own account.

[2530] Input: Child's name, age

[2531] Output: Child account created and linked to parent account

[2532] Specific actions: Select the "Create a child account" option in the app, enter the required information and press the "Create" button.

[2533] Step 4:

[2534] The server stores parent and child account information in a database.

[2535] Input: Parent and child account information

[2536] Output: Information is saved in the database

[2537] Specific behavior: Receives HTTP requests and executes queries to insert information into a database.

[2538] Distribution of pocket money

[2539] Step 1:

[2540] The user (parent) accesses the app and enters the amount to be transferred.

[2541] Input: Amount you want to send

[2542] Output: A transfer request is generated.

[2543] Specific actions: Enter the amount to send in the app's text field and press the "Send" button.

[2544] Step 2:

[2545] The terminal sends a remittance request to the server.

[2546] Input: Transfer request

[2547] Output: The request arrives at the server

[2548] What it does: Creates and sends a money transfer request using HTTPS.

[2549] Step 3:

[2550] The server will credit the specified amount to the child's account.

[2551] Input: Transfer request

[2552] Output: The child's account balance is updated.

[2553] What it does: Executes a query that updates the appropriate records in the database, adding the specified amount.

[2554] Step 4:

[2555] The server sends a notification of the transfer.

[2556] Input: Remittance information

[2557] Output: A notification is sent to the child's device.

[2558] Specific operation: Sends notifications using the push notification API.

[2559] Check your purchase history

[2560] Step 1:

[2561] The user (child) makes a payment using PayPay.

[2562] Input: Purchase amount, payment information

[2563] Output: PayPay payment completed

[2564] Specific operations: Scan the QR code with the PayPay app, enter the amount, and confirm the payment.

[2565] Step 2:

[2566] The terminal sends the payment information to the server.

[2567] Input: Payment information

[2568] Output: Payment information arrives at the server

[2569] Specific operation: After payment is completed, an HTTP request containing payment information is sent to the server.

[2570] Step 3:

[2571] The server stores the purchase history.

[2572] Input: Payment information

[2573] Output: Purchase history stored in the database

[2574] Specific Actions: Executes a query to insert payment information into the database.

[2575] Step 4:

[2576] The server notifies the parent's device of the purchase history.

[2577] Input: Purchase history

[2578] Output: A notification is sent to the parent's device.

[2579] Specific operation: Sends notifications to the parent's device using the push notification API.

[2580] Alert Settings

[2581] Step 1:

[2582] User (parent) sets alerts based on usage conditions.

[2583] Input: Alert condition, e.g., payment of 500 yen or more

[2584] Output: Save alert settings

[2585] Specific actions: Enter conditions on the "Alert Settings" page in the app and press the "Save" button.

[2586] Step 2:

[2587] The server monitors the purchase history.

[2588] Input: purchase history, alert conditions

[2589] Output: Monitoring results

[2590] Specific behavior: Periodically runs monitoring queries against the database.

[2591] Step 3:

[2592] The server notifies you when the condition is met.

[2593] Input: Monitoring results

[2594] Output: Alert notification on parent device

[2595] Specific behavior: When the conditions are met, an alert is sent using the push notification API.

[2596] Step 4:

[2597] The parent device receives the alert.

[2598] Input: Alert notification

[2599] Output: Display of alert notification

[2600] Specific behavior: Displays an alert as a pop-up notification on the device.

[2601] (Application example 1)

[2602] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[2603] Traditionally, when managing pocket money with cash, it is difficult for parents to keep track of how their children spend their money in detail, and it is also difficult to record where and how the child spends the money. This makes it difficult for parents to properly manage their children's money and for children to develop a healthy sense of money. Furthermore, with the spread of electronic money, there is a need for a safe and efficient way for parents to give pocket money to their children.

[2604] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[2605] In this invention, the server includes means for transferring electronic money from a parent's account to a child's account, means for storing the purchase history of the child's account in a central management device, means for displaying the child's purchase history on the parent's mobile information terminal, means for sending alerts based on conditions set by the parent, means for setting alerts based on changes in the balance of the child's account, and means for scheduling transfers from the parent's account to the child's account. This allows parents to manage their children's money efficiently and safely, and enables children to develop sound financial skills.

[2606] "Parent Account" refers to an online account used by a parent to manage electronic money.

[2607] A "child's account" is an online account used by a child to manage electronic money.

[2608] "Electronic money" is currency used in electronic form in place of cash.

[2609] A "means of transfer" is a means for transferring electronic money from a parent's account to a child's account.

[2610] "Purchase history" is a record of purchases made by a child using electronic money.

[2611] The "central management device" is a server that centrally manages all account information and transaction history.

[2612] A "personal digital assistant" is a mobile device such as a smartphone or tablet.

[2613] A "warning" is a notification issued to call attention when a set condition is met.

[2614] "Balance fluctuation" refers to the increase or decrease in the amount of electronic money in an account.

[2615] A "means for scheduling remittances" is a means for automatically sending remittances based on specified dates and conditions.

[2616] The present invention is a system for parents to give electronic pocket money to their children and manage how the money is spent. Specific embodiments of the present invention will be described in detail below.

[2617] System configuration

[2618] The system consists of the following elements:

[2619] 1. Parent and child mobile devices (smartphones, tablets, etc.)

[2620] 2. Central management device (server)

[2621] Hardware and Software

[2622] Hardware: Smartphones (iOS, Android), tablets

[2623] software:

[2624] Python: Programming Language

[2625] Flask: a web framework for building server-side APIs

[2626] SQLite: Manage users and purchase history as a database

[2627] User registration and account linking

[2628] The parent installs the application on their mobile device and registers as a new user. The parent then creates an account for the child and links it to their own account. The central management device (server) stores the parent and child account information in a database.

[2629] Distribution of pocket money

[2630] The parent accesses the application and enters the amount to transfer to the child's account. The device sends the transfer request to the server, which then updates the child's account with the specified amount. The child's device notifies them of the new transfer.

[2631] Check your purchase history

[2632] When a child makes a payment using an electronic payment service such as PayPay, the device sends the payment information to a server, which stores it in a database, allowing parents to check their child's most recent purchase history in real time through the app.

[2633] Alert Settings

[2634] Parents can set alerts based on specific usage conditions in the application, such as when a certain amount of money is spent. The server monitors the purchase history based on the set conditions and sends an alert to the parent's device when the condition is met.

[2635] Monitor balance fluctuations

[2636] Parents can set alerts based on changes in their child's account balance, such as when the balance exceeds or falls below a certain amount, allowing parents to monitor their child's spending behavior more closely.

[2637] Schedule a transfer

[2638] Parents can manage the account and schedule transfers, for example, to be sent automatically, such as a set amount at a certain time each month.

[2639] Specific examples

[2640] User registration and account linking: Parents install the application and create an account. Then, they create a child account and link it to the parent's account.

[2641] Distributing pocket money: A parent uses the application to send their child 500 yen in electronic money, enters the amount, and submits it. The server then credits the amount to the child's account.

[2642] Checking purchase history: When a child spends 200 yen at a stationery store, the information is sent to the server and stored in a database. Parents can check this information in the application.

[2643] Alert settings: If a parent sets the option to "send an alert if more than 500 yen is spent at once," and their child makes a purchase of 600 yen, an alert will be sent to the parent's device.

[2644] Prompt Sentence Examples

[2645] Remittance: Parent sends 500 yen to child.

[2646] Purchase history: A child spends 200 yen at the stationery store at school.

[2647] Alert: If a parent sets up a notification for purchases over 500 yen, a notification will be sent when the child makes a purchase of 600 yen.

[2648] The present invention enables parents to manage their children's finances efficiently and safely, and enables children to acquire a sound financial sense.

[2649] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[2650] Step 1:

[2651] The application is installed on the parent's mobile information terminal and a new user registration is performed.

[2652] Input: Parent's personal information, account creation information

[2653] Output: New user ID, parent account information

[2654] Specific behavior:

[2655] Parent downloads and launches the application.

[2656] The parent enters personal information (name, email address, password, etc.) and presses the account creation button.

[2657] The server stores the received information in a database and generates a new user ID.

[2658] Step 2:

[2659] Parents create accounts for their children and link them to their own accounts.

[2660] Input: Child's personal information, link information

[2661] Output: Child's new user ID, parent and child link information

[2662] Specific behavior:

[2663] A parent selects the "Create a Child Account" feature on the application.

[2664] Parents enter their child's personal information and press the link button.

[2665] The server stores the received information in a database and generates a new child ID.

[2666] The server links the parent's account with the child's account.

[2667] Step 3:

[2668] Parents use the application to transfer money to their children's accounts.

[2669] Input: Transfer amount, child's account ID

[2670] Output: Transfer completion notification, updated balance

[2671] Specific behavior:

[2672] The parent selects the transfer function in the application and enters the amount to transfer.

[2673] When the parent presses the send button, the terminal sends a remittance request to the server.

[2674] The server adds the transfer amount to the child's account and updates the database.

[2675] The server sends a notification of the completion of the remittance to the child's device.

[2676] Step 4:

[2677] The child makes the payment using an electronic payment service such as PayPay.

[2678] Input: payment amount, payment store information

[2679] Output: Purchase history, updated balance

[2680] Specific behavior:

[2681] The child makes an electronic payment at the store and completes the payment.

[2682] The child's device sends payment information (payment amount, store information) to the server.

[2683] The server stores the information in a database and updates the child's account balance.

[2684] Step 5:

[2685] Parents can view their child's purchase history in the app.

[2686] Input: Parent account ID, Child account ID

[2687] Output: Purchase history, purchase details

[2688] Specific behavior:

[2689] A parent selects the "Purchase History" feature in the application.

[2690] The server receives the parent's request and retrieves the child's purchase history from the database.

[2691] The server sends the acquired purchase history to the parent's device.

[2692] Step 6:

[2693] Parents can set alerts based on specific conditions.

[2694] Input: Warning condition (e.g., payment above a certain amount)

[2695] Output: Set warning conditions

[2696] Specific behavior:

[2697] Parents select the "Warning Settings" feature in the application.

[2698] The parent enters the warning conditions and presses the setting button.

[2699] The server stores the received alert conditions in a database.

[2700] Step 7:

[2701] The server monitors the purchase history based on the set conditions and sends an alert when the conditions are met.

[2702] Input: purchase history, warning conditions

[2703] Output: Warning notice

[2704] Specific behavior:

[2705] The server periodically checks the purchase history in the database.

[2706] If the set warning conditions are met, a warning notification will be sent to the parent device.

[2707] Step 8:

[2708] Parents schedule transfers to their children's accounts.

[2709] Input: remittance amount, schedule information (date, time, cycle)

[2710] Output: Scheduled transfer information

[2711] Specific behavior:

[2712] The parent selects the transfer schedule feature in the application.

[2713] The parent enters the transfer amount and schedule information and presses the setting button.

[2714] The server stores the received schedule information in a database.

[2715] The remittance will be processed automatically at the set date and time.

[2716] Furthermore, an emotion engine that estimates the user's emotion may be further combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59, and perform identification processing using the user's emotion.

[2717] The present invention is a system that allows parents to give their children electronic pocket money and manage how it is spent, and further combines it with an emotion engine that recognizes the user's emotions and provides various notifications and advice based on that data. Specific processing content based on an embodiment of the present invention will be described below.

[2718] System Configuration

[2719] The system consists of the following elements:

[2720] 1. Smartphone apps (devices) for parents and children

[2721] 2. Central Management Server (Server)

[2722] 3. Emotion Engine

[2723] User registration and account linking

[2724] 1. The user (parent) installs the app and opens the new user registration screen.

[2725] 2. The user (parent) enters information such as name, email address, and password.

[2726] 3. The terminal sends the entered information to the server.

[2727] 4. The server receives the information, registers the new user in the database, generates an account ID, and returns it to the device.

[2728] 5. The user (parent) selects the option to create a child account and enters the child's name and user ID.

[2729] 6. The device sends a child account creation request to the server.

[2730] 7. The server receives the request, creates a child account, links it to the parent account, generates a child account ID, and returns it to the device.

[2731] Distribution of pocket money

[2732] 1. The user (parent) logs into the app and selects the option to send pocket money.

[2733] 2. The user (parent) enters the amount to be transferred.

[2734] 3. The device sends a transfer request to the server, which includes the parent's account ID, the child's account ID, and the transfer amount.

[2735] 4. The server receives the transfer request, checks the parent and child account information in the database, adds the transfer amount to the child's account, updates the database, and returns a successful transfer notification to notify the child's account of the update.

[2736] 5. The device receives a notification from the server and notifies the child's app that a new transfer has been made.

[2737] Check your purchase history

[2738] 1. The user (child) makes a purchase using PayPay. Payments are made through the PayPay app.

[2739] 2. Once the payment is complete, the terminal sends the payment information (store name, amount, date and time, etc.) to the server.

[2740] 3. The server receives the payment information and stores it in a database, including the child's account ID.

[2741] 4. The user (parent) selects the option to view their child's purchase history within the app.

[2742] 5. The device sends a history request to the server.

[2743] 6. The server retrieves the child's latest payment information from the database and sends it back to the parent's device.

[2744] 7. The device displays the received history information in the parent app.

[2745] Alert Settings

[2746] 1. The user (parent) selects the alert setting option and enters a specific condition (e.g., a single payment of 500 yen or more).

[2747] 2. The device sends an alert setting request to the server, including the parent account ID and the alert conditions.

[2748] 3. The server receives the alert conditions and stores them in a database.

[2749] 4. As the server saves each payment entry to the database, it checks it against pre-defined alert conditions.

[2750] 5. When the condition is met (e.g., when the child spends more than 500 yen), the server sends an alert notification to the parent's device.

[2751] 6. The device receives the alert notification and displays the alert content in the parent's app.

[2752] Introducing the Emotion Engine

[2753] The terminal and server are equipped with an emotion engine that collects and analyzes the emotion data of users (parents and children).

[2754] Based on the emotional data obtained by the emotion engine, an alert is sent to the parent's device when certain conditions are met.

[2755] The server uses emotional data to analyze purchase history and provide appropriate advice and alerts to parents.

[2756] Specific examples

[2757] User registration and account linking

[2758] The user (parent) installed the app and created an account. Then, the user (parent) created a child account and linked the two accounts.

[2759] The server stored the parent and child information in a database.

[2760] Distribution of pocket money

[2761] The user (parent) accessed the app to send their child 500 yen in pocket money, entered the amount, and sent it.

[2762] The server added 500 yen to the child's account and sent the child a notification of the transfer.

[2763] Check your purchase history

[2764] The user (child) paid 200 yen with PayPay at a stationery store.

[2765] The server received this payment information and stored it in a database.

[2766] The user (parent) checked their child's most recent purchase history in the app and confirmed the payment at the stationery store.

[2767] Alert Settings

[2768] The user (parent) set it up so that an alert would be sent if their child spent more than 500 yen at one time.

[2769] A few days later, I spent 600 yen on my child's device to buy a toy.

[2770] When the server met the alert conditions, it sent a notification to the parent's device, and the user (parent) received the alert.

[2771] Examples of emotion engines

[2772] The user (child) was shopping at a toy store and the emotion engine recognized that the child was feeling very happy.

[2773] Based on this emotional data, the emotion engine notified the parents that their child had purchased an expensive item and was very happy.

[2774] Sarver offered some advice to parents: "If these kinds of expensive purchases are frequent, we recommend reconsidering your budget."

[2775] This system provides an environment where parents can manage their children's finances more transparently and with peace of mind, and children can safely use their pocket money without carrying cash. Furthermore, by combining it with an emotion engine, parents can receive monitoring and advice based on their children's emotional state, enabling them to provide more appropriate financial education.

[2776] The processing flow will be explained below.

[2777] User registration and account linking

[2778] Step 1:

[2779] The user (parent) installs the app and opens the new user registration screen.

[2780] Step 2:

[2781] The user (parent) enters information such as name, email address, and password.

[2782] Step 3:

[2783] The terminal transmits the input information to the server.

[2784] Step 4:

[2785] The server receives the information, registers the new user in the database, generates an account ID, and returns it to the device.

[2786] Step 5:

[2787] The user (parent) selects the option to create a child account.

[2788] Step 6:

[2789] The user (parent) enters the child's name and user ID.

[2790] Step 7:

[2791] The terminal sends a request to create a child account to the server.

[2792] Step 8:

[2793] The server receives the request, creates a child account, links it to the parent's account, generates a child account ID, and returns it to the device.

[2794] Distribution of pocket money

[2795] Step 1:

[2796] The user (parent) logs into the app and selects the option to transfer pocket money.

[2797] Step 2:

[2798] The user (parent) enters the remittance amount.

[2799] Step 3:

[2800] The device sends a transfer request to the server, which includes the parent's account ID, the child's account ID, and the transfer amount.

[2801] Step 4:

[2802] The server receives the transfer request and checks the parent and child account information in its database.

[2803] Step 5:

[2804] The server adds the transfer amount to the child's account and updates the database.

[2805] Step 6:

[2806] The server returns a successful transfer information and notifies the child account of the update.

[2807] Step 7:

[2808] The device receives a notification from the server and notifies the child's app that a new transfer has been made.

[2809] Check your purchase history

[2810] Step 1:

[2811] The user (child) makes purchases using PayPay. Payments are made through the app.

[2812] Step 2:

[2813] Once the payment is complete, the terminal sends the payment information (store name, amount, date and time, etc.) to the server.

[2814] Step 3:

[2815] The server receives the payment information and stores it in a database, including the child's account ID.

[2816] Step 4:

[2817] The user (parent) selects the option to view their child's purchase history within the app.

[2818] Step 5:

[2819] The terminal sends a history request to the server.

[2820] Step 6:

[2821] The server retrieves the child's latest payment information from the database and sends it back to the parent's device.

[2822] Step 7:

[2823] The device displays the received history information in the parent's app.

[2824] Alert Settings

[2825] Step 1:

[2826] The user (parent) selects the alert setting option and enters specific conditions (e.g., a single payment of 500 yen or more).

[2827] Step 2:

[2828] The device sends an alert setting request to the server, which includes the parent account ID and the alert conditions.

[2829] Step 3:

[2830] The server receives the alert conditions and stores them in a database.

[2831] Step 4:

[2832] As the server saves each payment entry to the database, it checks it against pre-defined alert conditions.

[2833] Step 5:

[2834] When a condition is met (e.g., when a child pays more than 500 yen), the server sends an alert notification to the parent's device.

[2835] Step 6:

[2836] The device receives an alert notification and displays the alert content in the parent's app.

[2837] Introducing the Emotion Engine

[2838] Step 1:

[2839] The terminal and the server are equipped with an emotion engine to collect emotion data from users (parent...

Claims

1. A means of transferring electronic money from a parent's account to a child's account, A means to store the purchase history of the child's account on the server, A way to view a child's purchase history on a parent's device, a means of sending alerts based on conditions set by the parent; A system including:

2. 10. The system of claim 1, further comprising means for collecting payment information at the child's terminal and transmitting the information to the server.

3. 2. The system according to claim 1, further comprising means for the parent terminal and the child terminal to communicate via an application.

Images