WO2022264469A1 - 計算機システム及びテナントの登録支援方法 - Google Patents
計算機システム及びテナントの登録支援方法 Download PDFInfo
- Publication number
- WO2022264469A1 WO2022264469A1 PCT/JP2022/001473 JP2022001473W WO2022264469A1 WO 2022264469 A1 WO2022264469 A1 WO 2022264469A1 JP 2022001473 W JP2022001473 W JP 2022001473W WO 2022264469 A1 WO2022264469 A1 WO 2022264469A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- tenant
- information
- space
- sales
- sns
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 25
- 239000000284 extract Substances 0.000 claims abstract description 9
- 238000003058 natural language processing Methods 0.000 claims description 3
- 238000010801 machine learning Methods 0.000 claims 4
- 238000000605 extraction Methods 0.000 description 38
- 238000010586 diagram Methods 0.000 description 19
- 230000006870 function Effects 0.000 description 10
- 230000008569 process Effects 0.000 description 7
- 230000008901 benefit Effects 0.000 description 4
- 230000004044 response Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 238000004088 simulation Methods 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 230000001174 ascending effect Effects 0.000 description 1
- 239000000470 constituent Substances 0.000 description 1
- 238000010191 image analysis Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/04—Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem"
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
- G06Q50/16—Real estate
Definitions
- the present invention relates to a system and method that support registration for a service that matches tenants and spaces.
- Patent Document 1 the technology described in Patent Document 1 is known as a matching system that matches spaces managed by commercial facilities such as malls with businesses (tenants) who wish to open stores.
- the content matching system stores the desired date and time of the booth exhibition input by the user, the content keyword of the content to be exhibited in the booth, the target customer attribute targeted by the user, and the matching data table.
- the content keywords of each booth, the exhibition date and time of the booth, the number of visitors of each booth calculated, and the number of people who stopped and paid attention to the booth while the content was being exhibited were calculated.
- Attention level which is the ratio of attention, attention attribute ratio such as gender and age of attention, high interest, high interest, which is the ratio of people who entered the booth to attention, high interest Recommended booth candidates are selected based on the attribute ratio of highly interested persons, which is the attribute of interested persons.”
- the purpose of the present invention is to provide a system and method for presenting information that encourages the use of a matching system.
- a representative example of the invention disclosed in the present application is as follows. That is, a computer system that supports registration to a service that performs matching between a tenant and a space used by the tenant, manages space features that represent the characteristics of the space, and receives information from the tenant on the SNS used by the tenant Acquire the account information of, access the SNS using the account information, extract the keyword contained in the posted information as SNS information, and estimate the tenant attribute representing the business characteristics of the tenant based on the SNS information. Then, for each combination of the tenant attributes and the space characteristics, the sales when using the space are estimated, and the estimated sales for each space are presented to the tenant.
- FIG. 1 is a diagram illustrating an example of a configuration of a system of Example 1;
- FIG. 3 is a diagram illustrating an example of a hardware configuration of a registration support server of Example 1;
- FIG. 4 is a diagram illustrating an example of information managed by the SNS information storage unit of Example 1;
- FIG. 4 is a diagram showing an example of information managed by a tenant attribute storage unit of Example 1.
- FIG. 4 is a diagram illustrating an example of information managed by a space information storage unit of Example 1;
- FIG. 4 is a diagram showing an example of information managed by a store opening history information storage unit of Example 1.
- FIG. 1 is a diagram illustrating an example of a configuration of a system of Example 1;
- FIG. 3 is a diagram illustrating an example of a hardware configuration of a registration support server of Example 1;
- FIG. 4 is a diagram illustrating an example of information managed by the SNS information storage unit of Example 1;
- FIG. 4 is a diagram showing an example of information managed by
- FIG. 4 is a diagram showing an example of information managed by a store opening condition information storage unit of Example 1.
- FIG. 4 is a diagram showing an example of information managed by a sales information storage unit of Example 1;
- FIG. 4 is a diagram showing an example of information managed by a space feature information storage unit of Example 1;
- FIG. 7 is a flowchart illustrating an example of space feature information extraction processing executed by the edge server of Example 1;
- 6 is a flow chart showing an example of tenant attribute estimation processing executed by the registration support server of Example 1.
- FIG. 8 is a flow chart showing an example of tenant attribute update processing executed by the registration support server of Embodiment 1.
- FIG. 7 is a flowchart illustrating an example of sales estimation processing executed by the registration support server of Example 1;
- FIG. 1 is a diagram for explaining the outline of the present invention.
- the system consists of a registration support server 100, a tenant 101, and an SNS (Social Networking Service) 102.
- SNS Social Networking Service
- a tenant 101 represents a business operator (either an individual or a corporation) who wishes to open a store.
- the tenant 101 uses the terminal 105 to input information to the registration support server 100 and refer to information output from the registration support server 100 .
- the tenant 101 inputs account information for accessing the SNS 102, past store opening information, store opening condition information (store opening space related information and store opening date and time related information), etc., tenant attributes from the registration support server 100, Receive information about space and sales forecasts.
- the registration support server 100 is a system that supports the registration of the tenant 101 in a matching system (not shown), estimates tenant attributes, and predicts sales when the tenant 101 opens a store in an arbitrary space.
- the tenant attribute is an attribute representing the business characteristics of the tenant 101, such as products and services handled by the tenant 101, target customer segments, and the like.
- the matching system is a system that matches the tenant 101 with the space.
- the registration support server 100 has an SNS information extraction unit 220, a tenant attribute estimation model storage unit 216, and a sales estimation model storage unit 217.
- the SNS information extraction unit 220 extracts a predetermined keyword as SNS information from the posted information of the tenant 101 posted on the SNS 102 using the account information.
- the SNS information is not limited to keywords.
- an image posted on the SNS 102 or information extracted from the image may be used.
- the tenant attribute estimation model storage unit 216 stores tenant attribute estimation models. Tenant attributes are estimated by inputting SNS information into the tenant attribute estimation model. The estimated tenant attributes are transmitted to the sales estimation model storage unit 217 and terminal 105 .
- the screen 110 of the terminal 105 displays the estimated tenant attributes.
- the screen 110 includes an operation button for correcting tenant attributes and an operation button for confirming tenant attributes.
- the sales estimation model storage unit 217 stores sales estimation models. Sales are estimated by inputting tenant attributes into the sales estimation model. The sales estimation result is transmitted to the terminal 105 . A screen 110 of the terminal 105 displays a space where a large amount of sales is expected and estimated sales.
- the registration support server 100 estimates the tenant attributes from the posted information on the SNS 102 using the account information and presents them to the tenant 101, thereby reducing the time and effort required to input information when registering the tenant 101 in the matching system. In addition, by presenting the sales forecast and the space, the tenant 101 can perform a business simulation when using the matching system.
- FIG. 2 is a diagram showing an example of the system configuration of the first embodiment.
- FIG. 3 is a diagram illustrating an example of the hardware configuration of the registration support server 100 according to the first embodiment.
- the system includes a registration support server 100, a terminal 105, an edge server 200, and a sensor group 201.
- the registration support server 100 , terminal 105 , edge server 200 , and sensor group 201 are interconnected via a network 202 .
- the network 202 is, for example, a WAN (Wide Area Network), a LAN (Local Area Network), or the like, and the connection method may be either wired or wireless.
- the network connecting the registration support server 100 and the terminal 105, the network connecting the registration support server 100 and the edge server 200, and the network connecting the edge server 200 and the sensor group 201 may be different.
- the registration support server 100 is a computer with a hardware configuration as shown in FIG. Specifically, the registration support server 100 has a CPU 300 , a memory 301 , a storage device 302 , a network interface 303 , an input device 304 and an output device 305 .
- the hardware configuration of the registration support server 100 shown in FIG. 3 is an example and is not limited to this.
- the registration support server 100 does not have to have the input device 304 and the output device 305 .
- the CPU 300 is an arithmetic device that controls the entire registration support server 100 and executes programs stored in the memory 301 .
- CPU 300 operates as a functional unit (module) that implements a specific function by executing processing according to a program.
- a functional unit module
- the memory 301 is a storage device that stores programs executed by the CPU 300 and information used by the programs. Memory 301 is also used as a work area.
- the storage device 302 is a storage device that permanently stores data, such as a HDD (Hard Disk Drive) and an SSD (Solid State Drive).
- the programs and information stored in memory 301 may be stored in storage device 302 .
- CPU 300 reads programs and information from storage device 302 and loads them into memory 301 .
- a network interface 303 is an interface for communicating with an external device or an external system via a network.
- the input device 304 is a device for inputting data, commands, etc. to the registration support server 100, and is, for example, a keyboard, a mouse, a touch panel, and the like.
- the output device 305 is a device for outputting information, such as a display.
- the registration support server 100 includes an SNS information storage unit 210, a tenant attribute storage unit 211, a space information storage unit 212, a store opening history information storage unit 213, a store opening condition information storage unit 214, a sales information storage unit 215, and a tenant attribute estimation model storage unit. 216, sales estimation model storage unit 217, SNS information extraction unit 220, sales estimation unit 221, new posting determination unit 222, input data generation unit (for tenant attribute learning) 223, tenant attribute estimation model learning unit 224, input data generation unit (for sales estimation learning) 225 and a sales estimation model learning unit 226 .
- the SNS information storage unit 210 manages SNS information extracted from posted information on the SNS 102 .
- the tenant attribute storage unit 211 manages tenant attributes estimated from SNS information.
- the space information storage unit 212 manages information on spaces handled by the matching system.
- the store opening history information storage unit 213 manages information (store opening history information) related to sales of past store openings.
- the store opening condition information storage unit 214 manages information (store opening condition information) related to store opening conditions such as the conditions of the space desired by the tenant 101 .
- the sales information storage unit 215 manages sales estimation results.
- the tenant attribute estimation model storage unit 216 manages models for estimating tenant attributes (tenant attribute estimation models).
- the tenant attribute estimation model of this embodiment receives SNS information as input and outputs tenant attributes.
- a model that accepts information other than SNS information as an input may also be used.
- the sales estimation model storage unit 217 manages models for estimating sales (sales estimation models).
- the sales estimation model of this embodiment accepts tenant attributes and space features as inputs and outputs sales. Note that a model that accepts store opening conditions as an input may also be used.
- the SNS information extraction unit 220 extracts SNS information from posted information on the SNS 102 .
- the sales estimation unit 221 estimates sales using a sales estimation model.
- the new posting determination unit 222 searches for new posted information on the SNS 102 .
- the input data generation unit (for tenant attribute learning) 223 generates input data for learning the tenant attribute estimation model.
- the input data generation unit 223 generates input data using information managed by the SNS information storage unit 210 and the tenant attribute storage unit 211.
- the tenant attribute estimation model learning unit 224 learns the tenant attribute estimation model using the input data, and outputs the tenant attribute estimation model, which is the learning result, to the tenant attribute estimation model storage unit 216 .
- the input data generation unit (for sales estimation learning) 225 generates input data for learning the sales estimation model.
- the input data generation unit 225 generates input data using information managed by the space information storage unit 212 and the shop opening history information storage unit 213 .
- the sales estimation model learning unit 226 learns a sales estimation model using the input data, and outputs the sales estimation model, which is the learning result, to the sales estimation model storage unit 217 .
- a plurality of functional units may be integrated into one functional unit, or one functional unit may be divided into multiple functional units for each function.
- the registration support server 100 may be a registration support system composed of a plurality of computers.
- the terminal 105 is a terminal operated by the tenant 101, and includes a tenant attribute input unit 230, an SNS account information input unit 231, a store opening condition information input unit 232, a store opening history information input unit 233, a screen output unit 234, and a user interface processing unit. 235.
- the tenant attribute input unit 230 inputs correction and addition contents of tenant attributes to the registration support server 100 .
- the tenant 101 refers to the tenant attributes estimated by the registration support server 100, and uses the tenant attribute input unit 230 to modify and add tenant attributes.
- the SNS account information input unit 231 inputs account information of the SNS 102 used by the tenant 101 to the registration support server 100 .
- the store opening condition information input unit 232 inputs store opening condition information to the registration support server 100 .
- the store opening history information input unit 233 inputs store opening history information to the registration support server 100 .
- the screen output unit 234 outputs a screen.
- the user interface processing unit 235 performs processing related to the user interface.
- a plurality of functional units may be integrated into one functional unit, or one functional unit may be divided into multiple functional units for each function.
- the sensor group 201 is a sensor group installed in the space where the space exists, and acquires sensor data, etc. regarding people who use the space.
- the sensor group 201 acquires images, for example.
- the edge server 200 analyzes and manages the characteristics of spaces.
- the edge server 200 has a space feature information storage unit 240 , a sensor control unit 250 and a space feature information extraction unit 251 .
- the space feature information storage unit 240 manages information on space features (space feature information). In this embodiment, information on people passing through or using the space is managed as space features.
- a sensor control unit 250 controls the sensor group 201 .
- the edge server 200 has a storage unit for managing sensor data, it is omitted.
- the space feature information extraction unit 251 extracts space feature information of each space by analyzing the sensor data, and outputs the extracted space feature information to the space feature information storage unit 240 .
- each functional unit of the edge server 200 a plurality of functional units may be integrated into one functional unit, or one functional unit may be divided into multiple functional units for each function.
- the registration support server 100 is configured to be able to grasp space features by communicating with the edge server 200, but is not limited to this.
- the edge server 200 may transmit the space feature information to the registration support server 100 in advance.
- FIG. 4 Next, information managed by the registration support server 100 and the edge server 200 will be described using FIGS. 4 to 10.
- FIG. 4 is a diagrammatic representation of the registration support server 100 and the edge server 200.
- FIG. 4 is a diagram showing an example of information managed by the SNS information storage unit 210 of the first embodiment.
- the SNS information storage unit 210 manages a table 400 as shown in FIG. Table 400 stores entries including account ID 401 and tag 402 . There is one entry for one account information. Note that the fields included in the entry are not limited to those described above. Any of the fields described above may not be included, or other fields may be included.
- the account ID 401 is a field that stores an account ID, which is account information for accessing the SNS 102 used by the tenant 101.
- a tag 402 is a field group for storing hash tags, which are SNS information extracted from posted information on the SNS 102 .
- Tag 402 includes multiple fields that store hashtags.
- hash tags are extracted as SNS information, but it is not limited to this. Words related to products, users, and the like may be extracted as SNS information.
- the data format of the information managed by the SNS information storage unit 210 may be a format other than the table.
- CSV, XML, or the like may be used.
- FIG. 5 is a diagram showing an example of information managed by the tenant attribute storage unit 211 of the first embodiment.
- the tenant attribute storage unit 211 manages a table 500 as shown in FIG.
- Table 500 stores entries including ID 501 , tenant name 502 , account ID 503 and tenant attributes 504 .
- the fields included in the entry are not limited to those described above. Any of the fields described above may not be included, or other fields may be included.
- the ID 501 is a field that stores the identification information of the entry in the table 500.
- a tenant name 502 is a field for storing identification information of the tenant 101 . In this embodiment, the name of the tenant 101 is stored.
- Account ID 503 is the same field as account ID 401 .
- the tenant attribute 504 is a group of fields that store tenant attributes of the tenant 101 . Tenant attributes 504 include items for sale 511 , target gender 512 , and target age group 513 . Note that the tenant attribute 504 may include fields other than those described above.
- the data format of the information managed by the tenant attribute storage unit 211 may be a format other than a table.
- CSV CSV
- XML XML
- FIG. 6 is a diagram showing an example of information managed by the space information storage unit 212 of the first embodiment.
- the space information storage unit 212 manages a table 600 as shown in FIG. Table 600 stores entries including space name 601 , address 602 , space attributes 603 , facilities 604 , and subscription/usage status 605 . There is one entry per space. Note that the fields included in the entry are not limited to those described above. Any of the fields described above may not be included, or other fields may be included.
- a space name 601 is a field that stores space identification information. In this embodiment, the name of the space is stored.
- Address 602 is a field that stores information indicating where the space exists. In this embodiment, the address of the facility that provides the space is stored.
- a space attribute 603 is a field for storing usage patterns of the space.
- Equipment 604 is a field that stores information about equipment that is available or installed in the space.
- the application/usage status 605 is a field that stores the application status and usage status of the space. For example, the usage period of the space is stored.
- the data format of the information managed by the space information storage unit 212 may be a format other than the table.
- CSV, XML, or the like may be used.
- FIG. 7 is a diagram showing an example of information managed by the store opening history information storage unit 213 of the first embodiment.
- the store opening history information storage unit 213 manages a table 700 as shown in FIG. Table 700 stores entries including tenant name 701 , items for sale 702 , space name 703 , duration 704 and sales 705 . There is one entry for one store opening history. Note that the fields included in the entry are not limited to those described above. Any of the fields described above may not be included, or other fields may be included.
- the tenant name 701 is the same field as the tenant name 502.
- Sale Item 702 is the same field as Sale Item 511 .
- Space name 703 is the same field as space name 601 .
- a period 704 is a field for storing the store opening period.
- Sales 705 is a field for storing sales.
- the data format of the information managed by the store opening history information storage unit 213 may be a format other than the table.
- CSV CSV, XML, or the like may be used.
- FIG. 8 is a diagram showing an example of information managed by the store opening condition information storage unit 214 of the first embodiment.
- the store opening condition information storage unit 214 manages a table 800 as shown in FIG. Due to the margin of the drawing, it is shown in two stages.
- Table 800 stores entries including ID 801 , tenant name 802 , region 803 , item for sale 804 , passerby attributes 805 , facility 806 , duration 807 and time 808 .
- An ID 801 is a field that stores identification information of entries in the table 800 .
- Tenant name 802 is the same field as tenant name 502 .
- a region 803 is a field for storing the region in which the store is desired to open.
- the area 803 stores the name, address, etc. of the area.
- the item for sale 804 is a field for storing items to be sold or services to be provided.
- the passerby attribute 805 is a group of fields that store desired space characteristics. Passerby attributes 805 include number 811 , gender 812 , and age 813 . Note that the passer-by attribute 805 may include fields other than those described above.
- the number of people 811 is a field that stores the number of people who pass through or use the space per unit time.
- Gender 812 is a field that specifies the distribution of the genders of people passing through or using the space. If the gender 812 is "male", it indicates that the user wishes to increase the ratio of males passing through or using the space.
- Age 813 is a field that specifies the age distribution of people who pass through or use the space. When the age 813 is "thirties", it indicates that it is desired that a large percentage of people who pass through or use the space are in their thirties.
- a facility 806 is a field for storing desired facilities.
- a period 807 is a field for storing the desired period of use of the space.
- the time 808 is a field for storing the usage time (business hours) of the desired space.
- the data format of the information managed by the store opening condition information storage unit 214 may be a format other than the table.
- CSV CSV
- XML XML
- FIG. 9 is a diagram showing an example of information managed by the sales information storage unit 215 of the first embodiment.
- the sales information storage unit 215 manages a table 900 as shown in FIG.
- Table 900 is a field that stores entries including tenant name 901 , sort number 902 , space name 903 , estimated sales 904 , past sales 905 , and store opening condition information ID 906 .
- the fields included in the entry are not limited to those described above. Any of the fields described above may not be included, or other fields may be included.
- the tenant name 901 is the same field as the tenant name 502.
- a sort number 902 is a field for storing the display order of estimated sales.
- Space name 903 is the same field as space name 601 .
- Estimated sales 904 is a field that stores estimated sales.
- Past sales 905 is a field that stores past sales.
- a store opening condition information ID 906 is a field for storing identification information of entries in the table 800 .
- a value corresponding to the ID 801 is stored in the store opening condition information ID 906 .
- the data format of the information managed by the sales information storage unit 215 may be a format other than the table.
- CSV, XML, or the like may be used.
- FIG. 10 is a diagram showing an example of information managed by the space feature information storage unit 240 of the first embodiment.
- the space feature information storage unit 240 manages a table 1000 as shown in FIG.
- a table 1000 is a field that stores entries including space names 1001 and passerby attributes 1002 . There is one entry per space. Note that the fields included in the entry are not limited to those described above. Any of the fields described above may not be included, or other fields may be included.
- the space name 1001 is the same field as the space name 601.
- the passerby attribute 1002 is a group of fields that store the passerby attribute 1002 representing the characteristics of the space.
- Passerby attributes 1002 include number 1011 , gender 1012 , and age 1013 .
- the number of people 1011 is a field that stores the number of people who pass through or use the space per unit time.
- Gender 1012 is a field that stores the gender distribution of people who pass through or use the space.
- Age 1013 is a field that stores the age distribution of people who pass through or use the space.
- FIG. 11 the processing executed in the system will be explained using FIGS. 11 to 14.
- FIG. 11 the processing executed in the system will be explained using FIGS. 11 to 14.
- FIG. 11 is a flow chart showing an example of space feature information extraction processing executed by the edge server 200 of the first embodiment.
- the edge server 200 starts space feature information extraction processing periodically or when an execution instruction is received. It should be noted that FIG. 11 describes the processing executed for one space. If there are multiple spaces, similar processing is performed for each space.
- the space feature information extraction unit 251 determines whether the space is currently open for business (step S1101).
- the space feature information extraction unit 251 terminates the space feature information extraction process.
- the space feature information extraction unit 251 starts measuring elapsed time (step S1102).
- the space feature information extraction unit 251 determines whether or not the elapsed time is greater than the threshold T1 (step S1103).
- the threshold T1 is a preset value and can be set arbitrarily.
- the space feature information extraction unit 251 returns to step S1103 after a certain period of time has passed.
- the space feature information extraction unit 251 analyzes the sensor data acquired from the sensor group 201 and outputs passerby attributes (step S1104). For example, the space feature information extraction unit 251 identifies the gender, age, and number of people who pass through or use the space by performing known image analysis.
- the sensor data is acquired and managed by the sensor control unit 250.
- the space feature information extraction unit 251 updates the space feature information (step S1105), and then returns to step S101. At this time, the space feature information extraction unit 251 initializes the elapsed time.
- the space feature information extraction unit 251 outputs space identification information and passerby attributes to the space feature information storage unit 240 .
- the space characteristic information storage unit 240 searches for an entry in which the identification information of the accepted space is stored in the space name 1001 . If the entry exists, the space feature information storage unit 240 overwrites the passerby attribute 1002 of the entry with the received passerby attribute. If the entry does not exist, the space feature information storage unit 240 adds the entry to the table 1000 and sets the accepted values to the space name 1001 and passerby attribute 1002 of the entry.
- FIG. 12 is a flow chart showing an example of tenant attribute estimation processing executed by the registration support server 100 of the first embodiment.
- the registration support server 100 When the registration support server 100 receives an operation from the terminal 105, it starts tenant attribute estimation processing.
- the SNS information extraction unit 220 presents a screen for inputting account information on the terminal 105 and waits for input of account information.
- the SNS information extraction unit 220 receives account information via the SNS account information input unit 231 of the terminal 105 (step S1201).
- the SNS information extraction unit 220 accesses the SNS 102 using the account information and extracts SNS information from the posted information of the tenant 101 on the SNS 102 (step S1202). At this time, the SNS information extraction unit 220 outputs the account information and the extracted SNS information to the SNS information storage unit 210 .
- the SNS information storage unit 210 searches for an entry in which the received account information is stored in the account ID 401 . If the entry exists, the SNS information storage unit 210 overwrites the tag 402 of the entry with the received SNS information. If the entry does not exist, the SNS information storage unit 210 adds the entry to the table 400 and sets the received values to the account ID 401 and tag 402 of the entry.
- hash tags are extracted as SNS information, but keywords related to items handled and customers may be acquired as SNS information using known natural language processing technology.
- the SNS information extraction unit 220 acquires tenant attributes by inputting SNS information into the tenant attribute estimation model (step S1203).
- the SNS information extraction unit 220 displays the estimated tenant attribute via the screen of the terminal 105 (step S1204) and waits for the tenant 101's operation.
- the SNS information extraction unit 220 When the SNS information extraction unit 220 receives an operation via the tenant attribute input unit 230 of the tenant 101, it determines whether the operation is a correction request (step S1205).
- the correction request includes correction contents.
- the SNS information extraction unit 220 corrects the tenant attribute according to the correction request (step S1206), and then returns to step S1204.
- the SNS information extraction unit 220 outputs the account information and the modified contents of the tenant attributes to the tenant attribute storage unit 211.
- the tenant attribute storage unit 211 searches for an entry in which the account information received in the account ID 503 is stored, and reflects the modified content of the tenant attribute in the tenant attribute 504 of the entry.
- the SNS information extraction unit 220 registers tenant attributes (step S1207). After that, the SNS information extraction unit 220 ends the tenant attribute estimation process.
- the SNS information extraction unit 220 outputs identification information, account information, and tenant attributes of the tenant 101 to the tenant attribute storage unit 211.
- the tenant attribute storage unit 211 stores the data in the tenant attribute 504 of the entry. Override the included tenant attributes. If the above entry does not exist, the tenant attribute storage unit 211 adds an entry, sets identification information in the ID 501, sets identification information and account information of the tenant 101 in the tenant name 502 and account ID 503, and sets the tenant attribute 504. set the tenant attribute included in the data. The tenant attribute storage unit 211 starts measuring elapsed time.
- FIG. 13 is a flow chart showing an example of tenant attribute update processing executed by the registration support server 100 of the first embodiment.
- the registration support server 100 After being activated, the registration support server 100 starts tenant attribute update processing.
- the tenant attribute storage unit 211 determines whether or not the elapsed time is greater than the threshold T2 (step S1301).
- the tenant attribute storage unit 211 returns to step S1301 after a certain period of time has passed.
- the tenant attribute storage unit 211 calls the new posting determination unit 222.
- the new posting determination unit 222 accesses the SNS information storage unit 210 and acquires account information (step S1302).
- the new posting determination unit 222 starts loop processing of account information (step S1303). Specifically, the new posting determination unit 222 selects one piece of account information from the acquired account information.
- the new posting determination unit 222 accesses the SNS 102 using the selected account information and determines whether or not there is new posted information of the tenant 101 corresponding to the account information (step S1304). For example, the new posting determination unit 222 determines whether or not there is posted information posted after the date and time obtained by subtracting the elapsed time from the current date and time.
- step S1310 When it is determined that the tenant 101's newly posted information does not exist, the newly posted determination unit 222 proceeds to step S1310.
- the new posting determining unit 222 calls the SNS information extracting unit 220. At this time, the new posting determining unit 222 outputs the selected account information to the SNS information extracting unit 220 .
- the SNS information extraction unit 220 accesses the SNS 102 using the account information, and extracts SNS information from the posted information of the tenant 101 from the SNS 102 (step S1305).
- the processing in step S1305 is the same as the processing in step S1202.
- the SNS information extraction unit 220 inputs SNS information into the tenant attribute estimation model (step S1306) and acquires tenant attributes.
- the processing in step S1306 is the same as the processing in step S1203. Note that the previously extracted SNS information and the newly extracted SNS information are input to the tenant attribute estimation.
- the SNS information extraction unit 220 displays the estimated tenant attribute via the screen of the terminal 105 (step S1307) and waits for the tenant 101's operation.
- the processing in step S1307 is the same as the processing in step S1204.
- the SNS information extraction unit 220 When the SNS information extraction unit 220 receives an operation via the tenant attribute input unit 230 of the tenant 101, it determines whether the operation is a correction request (step S1308).
- the correction request includes correction contents.
- the processing in step S1308 is the same as the processing in step S1205.
- step S1309 is the same as the processing in step S1206.
- the SNS information extraction unit 220 When it is determined that the received operation is a completion request, the SNS information extraction unit 220 notifies the new post determination unit 222 of the completion of processing.
- step S1310 the new posting determination unit 222 determines whether or not processing has been completed for all account information acquired in step S1302 (step S1310).
- the new posting determination unit 222 returns to step S1303 and performs similar processing.
- the new posting determination unit 222 calls the sales estimation unit 221 (step S1311), and then returns to step S1301. At this time, the new posting determining unit 222 outputs the account information of the tenant 101 that made the new posting to the sales estimating unit 221 .
- the new post determination unit 222 ends the process without calling the sales estimation unit 221.
- FIG. 14 is a flow chart showing an example of sales estimation processing executed by the registration support server 100 of the first embodiment.
- FIG. 14 describes sales estimation processing that is executed when an execution instruction is received from terminal 105 .
- the sales estimation unit 221 acquires the store opening condition information of the tenant 101 from the store opening condition information storage unit 214 (step S1401). Specifically, the sales estimation unit 221 outputs the identification information of the tenant 101 to the store opening condition information storage unit 214 .
- the store opening condition information storage unit 214 searches for an entry in which the identification information of the received tenant 101 is stored in the tenant name 802 and outputs the entry to the sales estimation unit 221 .
- the sales estimation unit 221 may prompt the tenant 101 to enter store opening condition information.
- the sales estimation unit 221 starts space loop processing (step S1402). Specifically, the sales estimation unit 221 acquires space information from the space information storage unit 212 and selects one piece of space information from the acquired space information.
- the sales estimation unit 221 acquires the space characteristics of the selected space from the space characteristics information storage unit 240 of the edge server 200 (step S1403).
- the sales estimation unit 221 transmits an acquisition request including space identification information to the edge server 200 .
- the space feature information storage unit 240 searches for an entry in which the identification information of the space included in the acquisition request is stored in the space name 1001, and transmits a response including the value stored in the passerby attribute 1002 of the searched entry. do.
- the sales estimation unit 221 acquires estimated sales by inputting tenant attributes and space characteristics into the sales estimation model (step S1404).
- the sales estimation unit 221 refers to store opening history information (step S1405).
- the sales estimation unit 221 outputs the items for sale included in the space identification information and the store opening condition information to the store opening history information storage unit 213 .
- the store opening history information storage unit 213 searches for entries where the combination of the values of the item for sale 702 and the space name 703 matches the combination of the received identification information for the item for sale and the space. If the entry exists, store opening history information storage unit 213 outputs the value stored in sales 705 of the entry to sales estimation unit 221 as a response. If the entry does not exist, store opening history information storage section 213 outputs the fact that the entry does not exist to sales estimation section 221 as a response.
- the sales estimation unit 221 may output the identification information of the tenant 101 , the identification information of the space, and the items for sale to the store opening history information storage unit 213 .
- the sales estimation unit 221 updates the sales information (step S1406). Specifically, the sales estimation unit 221 outputs the identification information of the tenant 101 , the identification information of the space, the identification information of the store opening condition information, the estimated sales, and the past sales to the sales information storage unit 215 .
- the combination of the values of the tenant name 901, the space name 903, and the store opening condition information ID 906 matches the received combination of the identification information of the tenant 101, the space identification information, and the store opening condition information. Search for entries. If the entry exists, the sales information storage unit 215 overwrites the estimated sales 904 of the entry with the estimated sales, and overwrites the past sales 905 with the past sales. At this time, the sort number 902 is deleted. If the entry does not exist, the sales information storage unit 215 adds the entry and sets the received values to the tenant name 901, space name 903, estimated sales, past sales 905, and store opening condition information ID 906 of the entry.
- the sales estimation unit 221 determines whether or not processing has been completed for all spaces (step S1407).
- the sales estimation unit 221 returns to step S1402 and performs similar processing.
- the sales estimation unit 221 identifies spaces that match the store opening conditions, and sorts the entries in the table 900 corresponding to the identified spaces in descending order of estimated sales. (step S1408).
- the sales estimation unit 221 identifies spaces whose space features match or are similar to passerby attributes included in the store opening condition information. Sales estimation unit 221 also acquires entries corresponding to the specified space from sales information storage unit 215 , sorts them in descending order of estimated sales, and outputs the sorting result to sales information storage unit 215 .
- the sales information storage unit 215 sets a value to the sort number 902 of the entry corresponding to the identified space based on the sort result.
- the sales estimation unit 221 presents the estimation result to the terminal 105 (step S1409), and terminates the sales estimation process.
- the sales estimation unit 221 acquires a predetermined number of entries in ascending order of sort number from the sales information storage unit 215, and presents the estimation results to the terminal 105 based on the entries.
- the estimation result may include space features.
- the registration support server 100 can present a space that meets the conditions desired by the tenant 101 and a sales forecast for opening a store in that space.
- the sales estimation unit 221 may specify a space that matches the store opening condition information and execute loop processing for the specified space before starting the space loop processing. In this case, in step S1408, the sales estimation unit 221 performs only sorting based on estimated sales. This makes it possible to propose a more effective space to the tenant 101 .
- step S1408 the sales estimation unit 221 may sort without limiting the space. In this case, there is no need to enter store opening conditions. As a result, the estimated sales can be presented while reducing the input burden on the tenant 101 .
- the sales estimating unit 221 executes the processing shown in FIG. 14 for the tenant 101 that has newly posted. In this case, presentation of the estimation result to the terminal 105 may not be performed.
- the registration support server 100 executes the tenant attribute estimation model learning process and the sales estimation model learning process at any timing. Since the model may use a known learning method, detailed description is omitted.
- the tenant 101 can know the space with high store opening effect and the estimated sales when using the space by inputting the account information. Thereby, the tenant 101 can perform a business simulation when using the matching system.
- the present invention is not limited to the above-described embodiments, and includes various modifications. Further, for example, the above-described embodiments are detailed descriptions of the configurations for easy understanding of the present invention, and are not necessarily limited to those having all the described configurations. Moreover, it is possible to add, delete, or replace a part of the configuration of each embodiment with another configuration.
- each of the above configurations, functions, processing units, processing means, etc. may be realized in hardware, for example, by designing a part or all of them with an integrated circuit.
- the present invention can also be implemented by software program code that implements the functions of the embodiments.
- a computer is provided with a storage medium recording the program code, and a processor included in the computer reads the program code stored in the storage medium.
- the program code itself read from the storage medium implements the functions of the above-described embodiments, and the program code itself and the storage medium storing it constitute the present invention.
- Examples of storage media for supplying such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs (Solid State Drives), optical disks, magneto-optical disks, CD-Rs, magnetic tapes, A nonvolatile memory card, ROM, or the like is used.
- program code that implements the functions described in this embodiment can be implemented in a wide range of programs or script languages, such as assembler, C/C++, perl, Shell, PHP, Python, and Java.
- the program code of the software that implements the functions of the embodiment can be stored in storage means such as a hard disk or memory of a computer, or in a storage medium such as a CD-RW or CD-R.
- a processor provided in the computer may read and execute the program code stored in the storage means or the storage medium.
- control lines and information lines indicate those that are considered necessary for explanation, and not all the control lines and information lines are necessarily indicated on the product. All configurations may be interconnected.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Human Resources & Organizations (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Marketing (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Development Economics (AREA)
- Game Theory and Decision Science (AREA)
- Primary Health Care (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Educational Administration (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (15)
- テナントと前記テナントが使用するスペースとのマッチングを行うサービスへの登録を支援する計算機システムであって、
前記スペースの特性を表すスペース特徴を管理し、
前記テナントから、当該テナントが使用するSNSのアカウント情報を取得し、
前記アカウント情報を用いて前記SNSにアクセスし、投稿情報に含まれるキーワードをSNS情報として抽出し、
前記SNS情報に基づいて、前記テナントの事業特性を表すテナント属性を推定し、
前記テナント属性及び前記スペース特徴の組合せごとに、前記スペースを利用した場合の売上を推定し、
前記テナントに、前記スペースごとの前記売上の推定結果を提示することを特徴とする計算機システム。 - 請求項1に記載の計算機システムであって、
ハッシュタグを前記SNS情報として抽出することを特徴とする計算機システム。 - 請求項1に記載の計算機システムであって、
前記投稿情報に対して自然言語処理を実行することによって抽出された単語を、前記SNS情報として抽出することを特徴とする計算機システム。 - 請求項1に記載の計算機システムであって、
機械学習によって生成された売上予測モデルを保持し、
前記テナント属性及び前記スペース特徴を前記売上予測モデルに入力することによって売上を推定することを特徴とする計算機システム。 - 請求項1に記載の計算機システムであって、
機械学習によって生成されたテナント属性推定モデルを保持し、
前記SNS情報を前記テナント属性推定モデルに入力することによって前記テナント属性を推定することを特徴とする計算機システム。 - 請求項1に記載の計算機システムであって、
前記SNS情報及び前記売上の推定結果を管理する記憶部を備え、
前記SNSへの新規の投稿情報の有無を判定し、
前記SNSへの新規の投稿情報が存在する場合、前記新規の投稿情報から新たな前記SNS情報を抽出し、前記記憶部に格納し、
前記記憶部に格納される前記テナントの前記SNS情報を用いて、前記スペースごとの前記売上を推定し、前記記憶部に格納することを特徴とする計算機システム。 - 請求項1に記載の計算機システムであって、
前記テナントから、出店条件の入力を受け付け、
前記出店条件を満たす前記スペースの前記売上の推定結果を提示することを特徴とする計算機システム。 - 請求項1に記載の計算機システムであって、
前記スペースのスペース特徴とともに前記売上の推定結果を提示することを特徴とする計算機システム。 - 計算機システムが実行する、テナントと前記テナントが使用するスペースとのマッチングを行うサービスへのテナントの登録支援方法であって、
前記計算機システムは、
プロセッサ、前記プロセッサに接続される記憶装置、及び前記プロセッサに接続されるネットワークインタフェースを有する、少なくとも一つの計算機を備え、
前記スペースの特性を表すスペース特徴を管理し、
前記テナントの登録支援方法は、
前記少なくとも一つの計算機が、前記テナントから、当該テナントが使用するSNSのアカウント情報を取得する第1のステップと、
前記少なくとも一つの計算機が、前記アカウント情報を用いて前記SNSにアクセスし、投稿情報に含まれるキーワードをSNS情報として抽出する第2のステップと、
前記少なくとも一つの計算機が、前記SNS情報に基づいて、前記テナントの事業特性を表すテナント属性を推定する第3のステップと、
前記少なくとも一つの計算機が、前記テナント属性及び前記スペース特徴の組合せごとに、前記スペースを利用した場合の売上を推定する第4のステップと、
前記少なくとも一つの計算機が、前記テナントに、前記スペースごとの前記売上の推定結果を提示する第5のステップと、を含むことを特徴とするテナントの登録支援方法。 - 請求項9に記載のテナントの登録支援方法であって、
前記第2のステップは、前記少なくとも一つの計算機が、ハッシュタグを前記SNS情報として抽出するステップを含むことを特徴とするテナントの登録支援方法。 - 請求項9に記載のテナントの登録支援方法であって、
前記第2のステップは、前記少なくとも一つの計算機が、前記投稿情報に対して自然言語処理を実行することによって抽出された単語を、前記SNS情報として抽出するステップを含むことを特徴とするテナントの登録支援方法。 - 請求項9に記載のテナントの登録支援方法であって、
前記計算機システムは、機械学習によって生成された売上予測モデルを保持し、
前記第4のステップは、前記少なくとも一つの計算機が、前記テナント属性及び前記スペース特徴を前記売上予測モデルに入力することによって売上を推定するステップを含むことを特徴とするテナントの登録支援方法。 - 請求項9に記載のテナントの登録支援方法であって、
前記計算機システムは、機械学習によって生成されたテナント属性推定モデルを保持し、
前記第3のステップは、前記少なくとも一つの計算機が、前記SNS情報を前記テナント属性推定モデルに入力することによって前記テナント属性を推定するステップを含むことを特徴とするテナントの登録支援方法。 - 請求項9に記載のテナントの登録支援方法であって、
前記計算機システムは、前記SNS情報及び前記売上の推定結果を管理する記憶部を備え、
前記テナントの登録支援方法は、
前記少なくとも一つの計算機が、前記SNSへの新規の投稿情報の有無を判定するステップと、
前記少なくとも一つの計算機が、前記SNSへの新規の投稿情報が存在する場合、前記新規の投稿情報から新たな前記SNS情報を抽出し、前記記憶部に格納するステップと、
前記少なくとも一つの計算機が、前記記憶部に格納される前記テナントの前記SNS情報を用いて前記スペースごとの前記売上を推定し、前記記憶部に格納するステップと、を含むことを特徴とするテナントの登録支援方法。 - テナントと前記テナントが使用するスペースとのマッチングを行うサービスへの登録を支援する計算機システムであって、
前記スペースの特性を表すスペース特徴を管理し、
前記テナントから、当該テナントが使用するSNSのアカウント情報を取得し、
前記アカウント情報を用いて前記SNSにアクセスし、投稿情報に含まれるキーワードをSNS情報として抽出し、
前記SNS情報に基づいて、前記テナントの事業特性を表すテナント属性を推定し、
前記テナントから、出店条件の入力を受け付け、
前記テナント属性及び前記出店条件の入力に該当する前記スペースの前記スペース特徴との組合せごとに、前記スペースを利用した場合の売上を推定し、
前記テナントに、前記スペースごとの前記売上の推定結果を提示することを特徴とする計算機システム。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2022294329A AU2022294329A1 (en) | 2021-06-15 | 2022-01-17 | Computer system and method for assisting tenant registration |
CN202280035836.8A CN117321612A (zh) | 2021-06-15 | 2022-01-17 | 计算机系统以及租户的登记辅助方法 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2021099404A JP2022190893A (ja) | 2021-06-15 | 2021-06-15 | 計算機システム及びテナントの登録支援方法 |
JP2021-099404 | 2021-06-15 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022264469A1 true WO2022264469A1 (ja) | 2022-12-22 |
Family
ID=84526960
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2022/001473 WO2022264469A1 (ja) | 2021-06-15 | 2022-01-17 | 計算機システム及びテナントの登録支援方法 |
Country Status (4)
Country | Link |
---|---|
JP (1) | JP2022190893A (ja) |
CN (1) | CN117321612A (ja) |
AU (1) | AU2022294329A1 (ja) |
WO (1) | WO2022264469A1 (ja) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2013175114A (ja) * | 2012-02-27 | 2013-09-05 | Yoko Ono | 出店支援システム及び出店支援方法 |
JP2014115948A (ja) * | 2012-12-12 | 2014-06-26 | Nippon Telegr & Teleph Corp <Ntt> | ユーザ属性推定器構築装置、方法、ユーザ属性推定装置、及びプログラム |
WO2020087180A1 (en) * | 2018-11-01 | 2020-05-07 | Webber Cole | Method and system for organizing events |
JP2021051368A (ja) * | 2019-09-20 | 2021-04-01 | ヤフー株式会社 | 提供装置、提供方法及び提供プログラム |
-
2021
- 2021-06-15 JP JP2021099404A patent/JP2022190893A/ja active Pending
-
2022
- 2022-01-17 CN CN202280035836.8A patent/CN117321612A/zh active Pending
- 2022-01-17 AU AU2022294329A patent/AU2022294329A1/en active Pending
- 2022-01-17 WO PCT/JP2022/001473 patent/WO2022264469A1/ja active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2013175114A (ja) * | 2012-02-27 | 2013-09-05 | Yoko Ono | 出店支援システム及び出店支援方法 |
JP2014115948A (ja) * | 2012-12-12 | 2014-06-26 | Nippon Telegr & Teleph Corp <Ntt> | ユーザ属性推定器構築装置、方法、ユーザ属性推定装置、及びプログラム |
WO2020087180A1 (en) * | 2018-11-01 | 2020-05-07 | Webber Cole | Method and system for organizing events |
JP2021051368A (ja) * | 2019-09-20 | 2021-04-01 | ヤフー株式会社 | 提供装置、提供方法及び提供プログラム |
Also Published As
Publication number | Publication date |
---|---|
AU2022294329A1 (en) | 2023-12-21 |
JP2022190893A (ja) | 2022-12-27 |
CN117321612A (zh) | 2023-12-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20150016675A1 (en) | Terminal apparatus, information processing system, and information processing method | |
TW202001736A (zh) | 分類模型的訓練方法、店鋪分類的方法及裝置 | |
JP6851894B2 (ja) | 対話システム、対話方法及び対話プログラム | |
US20160155158A1 (en) | Information distribution server and information distribution method | |
US10872324B2 (en) | Shopping support computing device | |
JP5670787B2 (ja) | 情報処理装置、帳票種別推定方法および帳票種別推定用プログラム | |
US20180068369A1 (en) | Shopping support device and shopping support method | |
US20150112834A1 (en) | Shopping support device and shopping support method | |
US20150108213A1 (en) | Shopping support device and shopping support method | |
JP2018536947A (ja) | ターゲットクラスタリング手法を利用して、属性タイプが混合した顧客をセグメント化するためのシステムおよび方法 | |
TW201601100A (zh) | 資訊處理裝置、資訊處理方法、記憶媒體 | |
CN115907868A (zh) | 一种广告投放分析方法及装置 | |
JP7070745B2 (ja) | 情報処理装置、情報表示方法及びプログラム | |
CN113807066A (zh) | 一种图表生成方法、装置及电子设备 | |
US10133706B2 (en) | Electronic book system, electronic book provision method, recording medium, and program | |
US8257091B2 (en) | Matching learning objects with a user profile using top-level concept complexity | |
WO2022264469A1 (ja) | 計算機システム及びテナントの登録支援方法 | |
CN114730435A (zh) | 管理服务器以及商品搜索方法 | |
JP6670051B2 (ja) | 情報処理装置、情報処理方法、およびプログラム | |
US20180121536A1 (en) | Verification Assistance System and Method | |
WO2021059848A1 (ja) | 情報処理装置、情報処理方法及び情報処理プログラム | |
US11275729B2 (en) | Template search system and template search method | |
JP6584486B2 (ja) | 予測装置、予測方法、及び予測プログラム | |
CN113127597A (zh) | 搜索信息的处理方法、装置及电子设备 | |
JP7295173B2 (ja) | コンテンツ管理装置、プログラム、コンテンツ管理システム、及びコンテンツ管理方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22824472 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202280035836.8 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2301007584 Country of ref document: TH |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022294329 Country of ref document: AU Ref document number: AU2022294329 Country of ref document: AU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18567605 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 2022294329 Country of ref document: AU Date of ref document: 20220117 Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |