[go: up one dir, main page]

WO2015138789A1 - Procédé et appareil de récapitulation et de personnalisation de données massives - Google Patents

Procédé et appareil de récapitulation et de personnalisation de données massives Download PDF

Info

Publication number
WO2015138789A1
WO2015138789A1 PCT/US2015/020271 US2015020271W WO2015138789A1 WO 2015138789 A1 WO2015138789 A1 WO 2015138789A1 US 2015020271 W US2015020271 W US 2015020271W WO 2015138789 A1 WO2015138789 A1 WO 2015138789A1
Authority
WO
WIPO (PCT)
Prior art keywords
product
user
price
products
block
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2015/020271
Other languages
English (en)
Inventor
Praveen Selvam
Sanjay Parthasarathy
Satyanarayana Rao KALIKIVAYI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
INDIX Corp
Original Assignee
INDIX Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by INDIX Corp filed Critical INDIX Corp
Publication of WO2015138789A1 publication Critical patent/WO2015138789A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0631—Recommending goods or services

Definitions

  • This disclosure is directed to the field of software, and more particularly, to a user interface for a computer, which user interface summarizes and personalizes a very large set of data relating to price and product information.
  • Indix Corporation collects and analyses a large amount of longitudinal data regarding products, product attributes, prices, and price attributes. To be understood by a person, this large amount of data and analytic output derived therefrom must be summarized, personalized, and organized in relevant terms. The summarization and personalization of such a large and complex set of data presents challenges in the selection and refinement of information as well as with respect to identification of patterns and arrangement of information in a user interface.
  • Figure 1 illustrates a computing environment configured according to an embodiment.
  • gure 2 illustrates an embodiment of Indix Server
  • gure 3 illustrates an embodiment of Indix Server Database
  • gure 4 illustrates an embodiment of User Interface Process
  • gure 5 illustrates an embodiment of Create User Home Items
  • gure 6 illustrates an embodiment of Create List Process
  • gure 7 illustrates an embodiment of Alert Process.
  • gure 8 illustrates an embodiment of Report Process.
  • gure 10 illustrates an embodiment of Quick View Process.
  • gure 11 illustrates an embodiment of Show Products Process.
  • gure 12 illustrates an embodiment of Show Promotions Process.
  • gure 13 illustrates an embodiment of Show Social Process.
  • gure 14 illustrates an embodiment of Show Analysis Process.
  • gure 15A illustrates a portion of an embodiment of Recommendation Process.
  • gure 15B illustrates a portion of an embodiment of Recommendation Process.
  • Ul Routine 400 allows users to pick a Brand or Merchant (referred to as "User Home 305"), one or more competitors thereof (referred to as “Competitor 310"), and to create lists of products and categories of products (referred to as “User Lists 320"). Ul Routine 400 selectively displays information regarding and comparisons among User Home 305, Competitor 310, User Lists and other user selections in relation to Products 327, Categories 335 of Products 327, Brands, and Merchants. The information regarding these items may be obtained from "Insights.” Briefly (a longer description is provided herein), Insights are analytic processes which identify, for example, price changes, and what product and price attributes across the datasets are associated with changes in price.
  • Selections and arrangements of information may be saved to a personalized dashboard.
  • colors are used in relation to various information items, to aid the user in quickly ascertaining, by color, what information is being displayed. For example (in other embodiments, different colors or other approaches to distinguishing items may be used), Brands are orange, Merchants are green, categories are yellow, quickviews are red, smart lists are violet, custom lists are blue, and alerts are black.
  • Ul Routine 400 performs one or more of the following processes: Create User Home Items 500, Create List Process 600, Alert Process 700, Report Process 800, Summary Process 900, Quick View Process 1000, Show Products Process 1100, Show Promotions Process 1200, Show Social Process 1300, Show Analysis Process 1400, and Recommendation Process 1500.
  • User Home Items are created.
  • User Home Items may comprise a selection of a Brand or Merchant (referred to as "User Home 305") as well as a selection of a competitor of the User Home 305 (referred to as “Competitor 310").
  • a "Brand” may be understood as a trademark under which products or services are sold; products and services are referred to herein as Product(s) 327.
  • Products 327 are unique products or services made by a manufacturer or provided by a service provider, each separate Product 327 generally being sold under a SKU number, Universal Product Code (“UPC”), product or service name, or the like.
  • UPC Universal Product Code
  • I ndix Corporation has crawlers, such as Crawl Agent 110, and data analysis methods and systems which identify Products 327, Price Attributes 340, and Product Attributes 345 (discussed at greater length in US Application Serial Numbers 13/951,248 and 13/951,244).
  • Price Attributes 340 and Product Attribute 345 are both referred to as "product information”.
  • User Home Items are used in other of the processes discussed herein to present information to the user, generally, though not exclusively, relating to the User Home 305 and/or the Competitor 310.
  • Create User Home Items 500 also allows a user to identify Products 327 as Linked Products 315.
  • a search engine routine executed by the I ndix Server 200 may increase the frequency with which the Crawl Agent 110 access websites which contain information regarding the Linked Products 315.
  • Other processes executed by the I ndix Server 200 such as "Substitution Routine 800" described in US Application Serial N umber 13/951,248, may identify the Linked Products 315 as "Substitutes", which, generally, indicates two Products 327 have similar Product Attributes 345 and may be substituted, one for the other.
  • User List(s) 320 may be created.
  • User List(s) 320 may comprise Custom Lists and Smart Lists.
  • User List(s) 320 may comprise a User Home 305, a Category 335, a Product 315 and/or a list of Products 315 (not necessarily part of the User Home 305) which are selected by the user and/or uploaded to the Create List Process 600.
  • Alert(s) 355 may be created relative to User Home Items and/or User List(s) 320. The Alert(s) 355 may be triggered, for example, when the relative or absolute price of a Product 327, a Category 335 of Products 327, Products 327 at a Merchant or the like changes or passes a threshold.
  • Report(s) 350 may be created relative to User Home Items and/or User List 320 (User List 320 is described further herein). Report(s) 350 (discussed further herein) may be setup to trigger actions, such as to re-price or order more of a Product 327.
  • I nsight Information 330 may be provided relative to User Home Items and/or User List 320.
  • "Insight Information 330" is the output of analytic processes ("Insights 375" determined by "Insights Routine 600" as described in US Patent Application Serial Number 13/951,248) which analytic processes identify, for example, price changes, and what Product Attributes 345 and Price Attributes 340 across the datasets are associated with changes in price.
  • I nsight I nformation 330 may comprise the output of analysis directed to determining at least, for example, the following: i) the volatility of prices relative to Attributes 345, Price Attributes 340, and other data available to the Indix Server 200; ii) Substitutes for Products 327 and Categories 335 of Products 327; iii) the number of Products 327, Brands, and Categories 335 of Products 327 in the many datasets available to the I ndix Server 200; iv) predicting the future price of Products 327; v) competitors relative to a Merchant, Store or Brand, vi) promotions of Products, Stores, or Brands; vii) which Products lead or follow others in terms of price changes; viii) which Products in a Category 335 charge higher (premium) prices; ix) the number of price ranges and maximum and minimum for Products and Categories 335 of products; and x) the reach of Products 327 in terms of the number of people who visit a physical or online sales venue.
  • Insight Information 330 may be provided relative to User List 320, in color coded tiles and with recommendations generated by Recommendation Process 1500.
  • Quick View Process 1000 may also provide information refining functions to a user.
  • promotion information relative to Products 327 may be provided to a user.
  • Insight Information 330 may be obtained, patterns therein may be identified, a scale may be selected to fit the observed patterns, the Insight Information 330 may be output in graphical or textual form, user criteria to refine the output may be received and implemented, and the output may be assigned to a Dashboard.
  • Figure 1 illustrates a computing environment 100 configured according to an embodiment.
  • I ndix Server 200 connects to Indix Database 300 and Network 150.
  • Network 150 Also connected to Network 150 are Client Device 105, Crawl Agent 110, and Ecommerce Platform 115.
  • Network 150 comprises computers, network connections among the computers, and software routines to enable communication between the computers over the network connections.
  • Network 150 may comprise, for example, an Ethernet network and/or the I nternet.
  • Communication among the various computers and routines may utilize various data tra nsmission standards and protocols such as, for example, the application protocol HTTP.
  • Transmitted data may encode documents, files, and data in various formats such as, for example, HTM L, XM L, flat files, and JSON . Connection between Indix Server 200 and I ndix Database 300 may be via Network 150.
  • Figure 2 illustrates several components of an exemplary I ndix Server 200 in accordance with one embodiment.
  • Indix Server 200 may include a desktop PC, server, workstation, mobile phone, laptop, tablet, set-top box, appliance, or other computing device that is capable of performing operations such as those described herein.
  • Indix Server 200 may include many more components than those shown in Figure 2. However, it is not necessary that all of these components be shown in order to disclose an illustrative embodiment.
  • I ndix Server 200 may comprise one or more physical and/or logical devices that collectively provide the functionalities described herein.
  • Indix Server 200 may comprise one or more replicated and/or distributed physical or logical devices and/or components.
  • Indix Server 200 may comprise one or more computing resources provisioned from a "cloud computing" provider, for exam ple, Amazon Elastic Compute Cloud ("Amazon EC2"), provided by Amazon.com, Inc. of Seattle, Washington; Sun Cloud Compute Utility, provided by Sun Microsystems, Inc. of Santa Clara, California; Windows Azure, provided by Microsoft Corporation of Redmond, Washington, and the like.
  • Amazon Elastic Compute Cloud (“Amazon EC2")
  • Sun Cloud Compute Utility provided by Sun Microsystems, Inc. of Santa Clara, California
  • Windows Azure provided by Microsoft Corporation of Redmond, Washington, and the like.
  • Indix Server 200 includes bus 220 interconnecting several components including network interface 230, optional display 240, optional input 245, central processing unit 210, and memory 250.
  • Memory 250 generally comprises a random access memory (“RAM”) and permanent non-transitory mass storage device, such as a hard disk drive or solid-state drive.
  • Memory 250 stores program code for the following processes: Ul Routine 400 for managing the other processes discussed herein; Create User Home Items 500; Create List Process 600; Alert Process 700; Report Process 800; Summary Process 900; Quick View Process 1000; Show Products Process 1100; Show Promotions Process 1200; Show Social Process 1300; Show Analysis Process 1400, and Recommendation Process 1500.
  • memory 250 also stores operating system 255.
  • medium 295 such as a floppy disc, tape, DVD/CD-ROM drive, memory card, or the like.
  • Memory 250 also includes Indix Database 300, illustrated further in Figure 3.
  • Indix Server 200 may communicate with Indix Database 300 via network interface 230, a storage area network ("SAN"), a high-speed serial bus, and/or via the other suitable communication technology.
  • SAN storage area network
  • the browser routine referred to above may provide an interface for interacting with other computers through, for example, a webserver and a web browser routine (which may serve and request data and information in the form of webpages).
  • the web browsers and webservers are meant to illustrate or refer to user- and machine-interface and user- and machine-interface enabling routines generally, and may be replaced by equivalent routines for obtaining information from, serving information to, and rendering information in a user or device interface.
  • An application program interface (or "API" may be used to facilitate communication among computers and routines executed by computers.
  • Login credentials and local instances of user or device profiles may be stored in or be accessible to Indix Server 200, Client Device 105, Ecommerce Platform 115, and Crawl Agent 110. Such user or device profiles may be utilized to provide secure communication between the computers.
  • Client Device 105 may be provided by computing devices similar to Indix Server 200.
  • I ndix Database 300 illustrated in Figure 3, illustrates data groups used by routines. I n addition to the data groups explicitly illustrated, additional data groups may also be present on and/or executed by this device, such as routines for databases, webservers, and web browsers, and routines to enable communication with other computers.
  • the data groups used by routines may be represented by a cell in a column or a value separated from other values in a defined structure in a digital document or file. Though referred to herein as individual records or entries, the records may comprise more than one database entry.
  • the database entries may be, represent, or encode numbers, numerical operators, binary values, logical values, text, string operators, joins, conditional logic, tests, and similar.
  • Demand Signal 301 is a record recording demand signals for a Product.
  • Demand Signal 301 is generally intended to comprise signals indicative of demand for a Product, such as whether demand for a Product is increasing or decreasing, whether demand is elastic or inelastic, and the like.
  • Demand Signal 301 may be based on the availability and/or availability delta of a Product, the traffic to websites selling the Product, and the like.
  • Demand Signal 301 may be determined as described in US Provisional Patent Application Serial N umber 61/952,029 and child applications thereof in relation to "Demand Signal Determination Process 500". I n the claims, Demand Signal 201 is part of the group which are referred to as the result of analysis of the set of product information.
  • Social Signal 303 is a record recording social media response to a Product, such as a number of “likes”, “follows”, positive and negative “tweets", “mentions”, and the like, which number may be normalized relative to all Products or Products within a Category 335 in which the Product may be found.
  • User Home 305 is a record recording a Brand, Merchant, or Store selected by the user, selected according to an employer of the user, or in which the user is otherwise interested. User Home 305 may be created during execution of Create User Home Items 500 routine.
  • Competitor 310 is a record of one or more competitors of User Home 305 and may comprise a Brand, Merchant, or Store. Competitor 310 may be selected by a user or may be provided, optionally with confirmation, to the user. Who are competitors of User Home 305 may be determined by, for example, "Competition Routine 1100" described in Application Serial Number 13/951,248. I n brief, with respect to Stores, Brands, and Merchants,
  • Competitors 310 may be determined by identifying Stores, Brands, and Merchants which share a threshold level of the same Products 327, such as 70%.
  • Linked Products 315 is a record recording Products 327 which have been linked pursuant to Create User Home Items 500 routing. Linked Products 315 is described further in relation to Figure 5.
  • User List 320 is a record recording the result of Create List Process 600. User List 320 is described further in relation to Figure 6.
  • Parse Result 325 is a record recording content obtained from a URI by "Crawl Agent 400" as described in US Application Serial N um ber 13/951,248 (corresponding to Crawl Agent 110).
  • Parse Result 325 (described at greater length in US Application Serial numbers 13/951,248 and 13/951,244) may comprise a Product name, available in number of Stores, Product graphic, Store, price, promotion status, availability and the like.
  • I nformation in Parse Result 325 records may be stored in, for exam ple, Price Attribute 340 or Product
  • Attribute 345 records.
  • Product 327 is a record recording a particular Product and may comprise a Product name, a product identifier (such as a UPC, SKU), and the like.
  • Product name such as a UPC, SKU
  • Product identifier such as a UPC, SKU
  • M PI D a product identifier
  • M PID 332 is an identifier generally meant to identify a single Product, generally produced by a common manufacturer, though the Product may be distributed and sold by multiple parties.
  • Product 327 as used herein is similar to "M PI D" and M PI Ds may be assigned as Products 327, though Product 327 may also include an identifier, such as a name, trademark, or the like.
  • Product 327 may also be understood as a value within a Product Attribute 340 record, as discussed in Application Serial numbers 13/951,248 and 13/951,244.
  • I nsight Information 330 is a record recording the result of analytic processes ("Insights 375" determined by "I nsights Routine 600" as described in US Patent Application Serial Number 13/951,248) which analytic processes identify, for example, price changes, and what Product Attributes 345 and Price Attributes 340 across the datasets are associated with changes in price.
  • Insight Information 330 may comprise the output of analysis directed to determining at least the following: i) the volatility of prices relative to Attributes 345, Price Attributes 340, and other data available to the Indix Server 200; ii) Substitutes for Products 327 and Categories 335 of Products 327; iii) the number of Products 327, Brands, and Categories 335 of Products 327 in the many datasets available to the Indix Server 200; iv) predicting the future price of Products 327; v) competitors relative to Product, Store, or Brand, vi) promotions of Products, Stores, or Brands; vii) which Products lead or follow others in terms of price changes; viii) which Products in a Category 335 cha rge higher (premium) prices; ix) the number of price ranges and maximum and minimum for Products and Categories 335 of products; and x) the reach of Products 327 in terms of the number of people who visit a physical or online sales venue.
  • Category 335 is defined further in US Application Serial N umbers 13/951,248 and 13/951,244 and, generally, is an entry in a hierarchical categorization or taxonomy in which Products 327 are arranged.
  • a hierarchical categorization or taxonomy may take the following form : ⁇ clothing/shoes/dress shoes/high heels>. I n this example, ⁇ high heels> may be recorded in a Category 335 record. The record may refer or be locatable in the location in the taxonomy represented by ⁇ clothing/shoes/dress shoes/high heels>.
  • Price Attributes 340 and Product Attribute 345 records may record information derived from Parse Result 325 records. Price Attribute 340 and Product Attribute 345 records are further defined in US Application Serial Numbers 13/951,248 and 13/951,244. Generally, a Price Attribute 340 record may comprise one or more records recording , for exam ple, a price observed at a particular time, a Product Name (a "Product Name” value in this record may also be referred to herein as "Product” and "Product 327”), a Product identifier (such as a SKU number), a Standard Price, a Sale, a Price, a Rebate amount, a Price Instructions record
  • a Currency Type (containing special instructions relating to a price, such as that the price only applies to students), a Currency Type, a Date and Time Stamp, a Tax record, a Shipping record (indicating costs relating to shipping to different locations, whether tax is calculated on shipping costs, etc.), a Price Validity Start Date, a Price Validity End Date, a Quantity, a Unit of Measure Type, a Unit of Measure Value, a Merchant Name (with the name of a merchant from whom the Product is available; a "Merchant Name” value in this record may also be referred to herein as a "Merchant”), a Store Name (a Merchant may have multiple stores; a "Store Name” value in this record may also be referred to herein as a "Store”), a User ID, a Data Channel (indicating the source of Price Attribute 340 record, such as an online crawl, a crowdsource, a licensed supplier of price information, or from a merchant), a Source Details record (for example, indicating a URI, a
  • a Votes/Likes record (indicating a number of “likes”, “follows” and similar which a Price or Product has received), a Price Rank record, a Visibility Indicator record (indicating whether the price is visible to the public, whether it is only visible to a Merchant, or the like), a Supply Chain Reference record (indicating whether the price was obtained from a retailer, a wholesaler, or another party in a supply chain), a Sale Location (indicating a geographic location where the product is available at the price), a Manufactured Location record (indicating where the product was produced or manufactured), a Launch Date record (indicating how long the product has been on the market), and an Age of Product record (indicating how long the product was used by the user).
  • the foregoing terms (such as Product, Price, Merchant, Store, Source Details, etc.) are meant to refer to values in a Price Attribute 340 or Product Attribute 345 record.
  • a Product Attribute 345 record may comprise, for example, values encoding features of or describing a Product.
  • the entire Product Attribute 345 schema may comprise thousands of columns, though only tens or hundreds of the columns may be applicable to any given Product.
  • An example set of values in a Product Attribute 345 record for a ring is as follows: Title, “Sterling Silver Diamond & Blue Topaz Ring;” Brand, “Blue Nile;” Category (such as, for example, a Category 335 in a category schema), “rings;” Metal Name, “silver;” Stone Shape, “cushion;” Stone Name, “topaz;” Width, “3 mm;” Stone Color, “blue;” Product Type, "rings," birthstone, “September;” and Setting Type, “prong.”
  • An example set of Product Attributes 345 for a shoe is as follows: Brand, "Asics;” Category (such as, for example, a
  • Category 335 in a category schema or taxonomy "Men's Sneakers & Athletic;” Shoe Size, “8;” Product Type, “wrestling shoes,” Color, “black;” Shoe Style, “sneakers;” Sports, “athletic;” Upper Material, “mesh.”
  • Brand "Men's Sneakers & Athletic;” Shoe Size, “8;” Product Type, “wrestling shoes,” Color, “black;” Shoe Style, “sneakers;” Sports, “athletic;” Upper Material, “mesh.”
  • Report 350 record may be produced during execution of Report Process 800. Report 350 record is discussed further in relation to Figure 8.
  • Alert 355 record may be produced during execution of Alert Process 700. Alert 355 record is discussed further in relation to Figure 7.
  • User Tag 380 record records an identifier assigned to a User List 320 by a user pursuant to Create List Process 600. User Tag 380 is discussed further in relation to Figure 6.
  • Promotions 382 record records the number, length, date/time, and magnitude of promotions (discounts) of a Product, either as advertised or relative to an external criteria, such as an average or mean price. Information in Promotions 382 record may be obtained by, for example, "Promotion Routine 1200" described in US Patent Application Serial Number
  • Promotions 382 is part of the group which are referred to as the result of analysis of the set of product information.
  • Figure 4 illustrates an embodiment of User Interface Process 400.
  • Client Device 105 may log into, for example, User Interface Process 400. Any of processes 500 through 1400 may be executed independently by User Interface Process 400, not necessarily in the order presented in Figure 4. Processes 500 through 1500 are discussed at great length herein.
  • Create User Home Items 500 may be executed.
  • Create User Home Items 500 may receive, for example, user selection of User Home 305.
  • User Home 305 may be a Brand, Merchant, or Store selected by the user, selected according to an employer of the user, or in which the user is otherwise interested.
  • Create User Home Items 500 may also receive identification and/or selection of Competitor 310, Products 327 of interest to the user, and user designation of link(s) between Products 327.
  • Create User Home Items 500 may also set two or more Products 327 as "Substitutes" if the number of user designated links between the Products 327 exceeds a threshold. Create User Home Items 500 is described further in relation to Figure 5.
  • Create List Process 600 may be executed.
  • Create List Process 600 may receive a list of Products 327— a "custom list”— and/or criteria for including Products 327 in a list— a "smart list”.
  • the criteria for including Products 327 in a list may comprise a Category, a Brand, a Store or the like.
  • Create List Process 600 is described further in relation to Figure 6.
  • Alert Process 700 may be executed.
  • Alert Process 700 is a process wherein users can set alerts to occur when one or more targets (such as a Product 327 or a Category 335 of Products 327) obtains a specified criteria, such as an absolute or relative change in price, or price ratio relative to another target, or changes availability at a Store (such as becomes available or is no longer available).
  • targets such as a Product 327 or a Category 335 of Products 327) obtains a specified criteria, such as an absolute or relative change in price, or price ratio relative to another target, or changes availability at a Store (such as becomes available or is no longer available).
  • a specified criteria such as an absolute or relative change in price, or price ratio relative to another target, or changes availability at a Store (such as becomes available or is no longer available).
  • Report Process 800 may be executed.
  • Repot Process 800 is a process wherein users can create customized reports and set re-pricing commands.
  • Report Process 800 is described further in relation to Figure 8.
  • Summary Process 900 may be executed.
  • Summary Process 900 is a process wherein summaries of I nsight I nformation 330 records may be customized for and presented to a user. Summary Process 900 is described further in relation to Figure 9.
  • Quick View Process 1000 may be executed.
  • Quick View Process 1000 is a process wherein a user may obtain multiple types of I nsight Information 330 records and output them with color.
  • Quick View Process 1000 is described further in relation to Figure 10.
  • Show Products Process 1100 may be executed. Show Products Process 1100 is a process wherein a user may obtain, refine, and sort information relating to User Home Items and User Lists, as described further in relation to Figure 11.
  • Show Promotions Process 1200 may be executed. Show Promotions Process 1200 is a process wherein information regarding Products 327 on sale may be output to a user. Show Promotions Process 1200 is described further in relation to Figure 12.
  • Show Social Process 1300 may be executed. Show Social Process 1300 is a process wherein information regarding social network events may be output to a user. Show Social Process 1300 is described further in relation to Figure 13.
  • Show Analysis Process 1400 may be executed.
  • Show Analysis Process 1400 is a process wherein Insight Information 330 relating to a Brand,
  • Recommendation Process 1500 may be executed to produce recommendations to increase or decrease a price, to add or remove a Product from inventory, or to increase or decrease promotion of a Product.
  • FIG. 5 illustrates an embodiment of Create User Home Items 500 routine.
  • User Home 305 such as a Brand, Merchant, and/or Store with which the user is associated or in which the user is interested— is received, such as from the user via Client Device 105, and stored. If the user is employed by a corporation or another organization, and if the corporation is obtaining services from Indix Server 200, User Home 305 may be set by the employer.
  • an identifier may be assigned to the User Home 305 of block 505, which identifier may be recorded in a User Home 305 record associated with the user.
  • Competitor 310 may be determined by, for example, "Competition Routine 1100" described in US Patent Application Serial Number 13/951,248. In brief, with respect to Stores, Brands, and Merchants, Competitors 310 may be determined by identifying Stores, Brands, and Merchants which share a threshold level of the same Products 327, such as 70%.
  • Create User Home Items 500 process may receive an assigned Competitor 310 from the user or Create user Home Items 500 may suggest or assign
  • Competitor 310 identifier may be assigned to or associated with the competitors of User Home 305 received at block 515.
  • first and second Products 327 may be received.
  • a designation may be received to link the first and second Products 327 of block 525.
  • the first and second Products 327 of block 525 may be linked as Linked Products 315.
  • crawling performed by the Crawl Agent 110 may be increased (such as to the maximum) for one or both of the Linked Products 315 with respect to URI's associated with the Linked Products 315. The increase may have a temporal effect on the behavior of the Crawl Agent 110 and may be influenced by the frequency with which the first and second Products 327 of block 525 are also Linked Products 315 by the same or different users.
  • a determination may be made regarding whether the link count is above a threshold. If so, then at block 555, the Linked Products 315 may be set as "Substitutes" in, for example, "Insights Routine 700" described in US Patent Application Serial Number 13/951,248. If not, then at block 560, the below-threshold link count may be ignored.
  • Create User Home Items 500 ends or returns to Figure 4, block 500, or to another process which may have called Create User Home Items 500.
  • Figure 6 illustrates an embodiment of Create List Process 600.
  • a create list command may be received from a user or another process.
  • the create list command may create a User List 320 record.
  • a determination may be made (or equivalent logic implemented) regarding whether the create list command is in relation to a custom list or a smart list; a custom list may be a list of Products 327 or another list uploaded by the user, an employer, or the like while a smart list may be a selection by a user, employer, or the like of a User Home 305 or a Category 335.
  • the user's product selection for inclusion in the custom list may be received.
  • Products 327 may be selected by the user (or an employer) from a list or catalog, via search results, via browsing a catalog, and the like; the product selection may be in relation to a User Home 305 or a Competitor 310, such as Products 327 associated with the user's User Home 305 or Competitor 310; the product selection may further be in relation to a list of products uploaded to the Create List Process 600 by the user.
  • the uploaded list may be normalized relative to the Products 327 maintained in the Indix Database 300, which normalization may involve interaction with the user to clarify any ambiguous or undeterminable items, with the output thereof being used in the relevant process.
  • the selected or identified products may be saved as a draft, which may allow the list to be refined by the user at a later date.
  • a submit command or equivalent may be received from the user and, at block 630, the product list may be saved as or in association with a User List 320 record.
  • a determination may be made regarding whether the smart list is in relation to a Brand or Merchant (or Store) or a Category 335.
  • the Brand or Merchant may be a User Home 305, User Home Item or a selection of a Brand or Merchant from a navigable list presented to the user for this purpose.
  • An example Category 335 record may be as follows:
  • the user's selection of a Category 335 may be received.
  • additional criteria which may be used to limit or refine Category 335 or block 640 may be received. For example, if the user selected a "high heel" Category 335, the user may further be able to refine the list according to a Brand within this Category 335 or all items in the Category 335 over a certain price level (such as all high heels over $50), or available by or from a certain Brand or Merchant, or at a Store, or within a sub-category with Category 335.
  • the selected Brand or Merchant (which may be a User Home 305) may be received.
  • the user's criteria within the Brand or Merchant may be received. For example, if the user selected a Merchant , the user may further be able to refine the list according to a Brand sold by the Merchant, Brands at a particular Store of the Merchant, or Products over a certain price level; if the user selected a Brand, the user may further be able to refine the list according to specific products within the Brand or products within the Brand over a certain price level.
  • the selected and refined Brand or Merchant information may be saved as a smart list.
  • a user tag, name, or identifier may be received from the User, saved as User Tag 380, and assigned to User List 320.
  • User Tag 380 may be used to identify the User List in other routines.
  • Create List Process 600 ends or returns to Figure 4, block 600, or to another process which may have called Create List Process 600.
  • FIG. 7 illustrates an embodiment of Alert Process 700.
  • a create alert command may be received from a user or another process.
  • an alert type selection may be received.
  • the alert types may be, for example, an alert based on a price change of a Product 327, Products in a Category 335, a User Home 305, a Competitor 310, a User List 320, based on a price comparison between two or more Products 327, Categories 335, User Home 305, Competitor 310, Products in a User List 320, based on a promotion or withdrawal of promotion of (such as advertised or actual percentage change in price) a Product 327, User Home 305, Competitor 310, or a User List 320, and the like.
  • the alert type may be responsive to, for example, the output of Recommendation Process 1500 and a recommendation of a type or with a specified value.
  • Alert Process 700 may receive and save the first target of the alert command, such as a Product 327, User Home 305, Competitor 310, User List 320, or a user selection of a Brand, Merchant, or Category 335.
  • the criteria for the alert may be received and saved, such as whether the alert will be triggered upon an increase or decrease of a price of the first target, either absolutely relative to an earlier value, as a percentage relative to an earlier value, or absolutely or as a percentage relative to a second target, whether a product has gone on a promotion, has been discontinued, is not available, or based on a defined recommendation being generated by Recommendation Process 1500, or the like.
  • the second target if any (as in the case of a comparison between products), may be received and saved.
  • the notification window, frequency, and other notification criteria of the alert may be received and saved.
  • the alert may be executed or may be set to be executed and notifications resulting therefrom may be sent.
  • Alert Process 700 ends or returns to Figure 4 and block 700 or to another process which may have called Alert Process 700.
  • Figure 8 illustrates an embodiment of Report Process 800.
  • a create report command may be received from a user or another process.
  • a report type selection may be received from a user or another process.
  • the report types may be, for example, a "MAP" report in relation to products that are priced below a minimum advertised price, a pricing opportunity report in relation to products that are priced above or below a competitor's price, or a product availability report in relation to products that are out of stock.
  • the report type may be based on a result of Recommendation Process 1500.
  • a data selection for the report may be received from a user or another process.
  • the data selection may be a User List 320, such as a Custom or Smart List, a selection of a Brand, Category 335, or Merchant, Store, an uploaded list, or the like.
  • data refinement selections may be received from a user or another process.
  • the data refinements may comprise criteria such as, for example, "where the price of X product at Y Store is higher/lower than the minimum or maximum of a price for X product at Competitor 310 by at least a specified amount.”
  • report column configuration settings may be received, such as to include or not include in the report a product title, a product SKU, a Brand name, an MPN, a UPC, a difference from lowest competitor, a "my sale price", a sale price across competitors, and the like.
  • a re-price command may be an instruction to re-price, add, or remove a product in response to conditions or information in a report. If so, then at block 825, a user instruction to match, price higher than or price lower than may be received.
  • a user instruction may be received that the re-price instruction is relative to a minimum or maximum of a competitor's price or a sale price at a selected competitor.
  • delivery options for the report may be received from a user or another process.
  • the delivery options may be, for example, whether the report is to be emailed when ready (which may include emailing a spreadsheet or a link to a spreadsheet or the like) or provided on a schedule, or the like.
  • the report may be saved as or in, for example, a Report 350 record.
  • Report Process 800 ends or returns to Figure 4 and block 800 or to another process which may have called Report Process 800.
  • Figure 9 illustrates an embodiment of Summary Process 900.
  • a summary command may be received from a user or another process.
  • the summary may be a default setting of the user interface.
  • Summary Process 900 processes each User Home Item, User List 320, favorite or other user selection in turn.
  • Insight Information 330 for each item of block 910 may be obtained.
  • Insight Information 330 is the output of analytic processes ("Insights 375"
  • Insight Information 330 may comprise, for example, a number of products, number of categories or subcategories, number of Brands, number of Merchants, number of Stores, number of price increases or decreases, number added in the last week or other date-time unit, number out of stock, number on sale, or the like.
  • tiles comprising a numeric value of the Insight Information 330 of block 915 may be output.
  • graphs comprising a graphical representation of the Insight Information 330 of block 915 may be output.
  • Summary Process 900 iterates back to opening loop block 910 to process the next User Home Item, User List 320, favorite or other user selection, if any.
  • Summary Process 900 ends or returns to Figure 4 and block 900 or to another process which may have called Summary Process 900.
  • Figure 10 illustrates an embodiment of Quick View Process 1000.
  • a quick view command may be received from a user or another process.
  • Quick View Process 1000 processes each User Home Item, User List 320, favorite or other user selection in turn.
  • Insight Information 330 for each item of block 1010 may be obtained.
  • the Insight Information 330 is described in relation to block 915 and elsewhere and may comprise, for example, a number of products, number of categories or subcategories, number of Brands, number of Stores, number of price increases or decreases, number added in the last week or other date-time unit, number out of stock, number on sale, or the like.
  • Price-related Insight Information 330 may be output in
  • assortment-related Insight Information 330 may be output in association with a color B.
  • promotion-related Insight Information 330 may be output in association with a color C.
  • Linked Products 315 may be output in association with a color D.
  • Quick View Process 1000 iterates back to opening loop block 1010 to process the next item, if any.
  • the recommendations generated at block 1500 may be output, for example, to Client Device 105.
  • a user selection or deselection of an output detail of blocks 1010 to 1040 and of 1042 may be received.
  • the user selection or deselection may, for example, allow the output detail to be shown or not shown.
  • the output may be updated to reflect the selection or deselection of block 1050.
  • Quick View Process 1000 ends or returns to Figure 4 and block 1000 or to another process which may have called Quick View Process 1000.
  • Figure 11 illustrates an embodiment of Show Products Process 1100.
  • a show product information command may be received from a user or another process.
  • Show Products Process 1100 processes each User Home Item, User List 320, favorite or other user selection in turn.
  • the product name, available in number of Stores, product graphic, Store, price, promotion status, availability and the like information may be obtained, such as from Price Attribute 340, Product Attribute 345, or Parse Result 325 records (described at greater length in US Patent Application Serial numbers 13/951,248 and 13/951,244).
  • the information of block 1115 may be output, for example, to Client Device 105.
  • user sort criteria may be received, such as sort-by relevance, price, name, date, or the like.
  • the output may be updated according to the user sort criteria.
  • Show Products Process 1100 iterates back to opening loop block 1110 to process the next item, if any.
  • Show Products Process 1100 ends or returns to Figure 4 and block 1100 or to another process which may have called Show Products Process 1100.
  • Figure 12 illustrates an embodiment of Show Promotions Process 1200.
  • a show promotion information command may be received from a user or another process.
  • Show Promotions Process 1200 processes each User Home Item, User List 320, favorite or other user selection in turn.
  • Show Promotions Process 1200 gets the products which are on sale, as may be advertised by the merchant or Store or as may be determined relative to a standard or average retail price. Determination of whether a product is on promotion may be performed, for example, by a "Promotions Insight", as described in US Patent Application Serial Number 13/951,248, for example, in relation to "Promotion Routine 1200" therein).
  • the Show Promotions Process 1200 gets the products which are on sale by various percentage amounts (such as 10%, 20%, 30%, etc.), as may be advertised by the merchant or Store or as may be determined relative to a standard or average retail price.
  • the products which are on sale may be output, such as to the Client Device 105.
  • the products which are on sale by various percentage amounts may be output.
  • the output may comprise a line graph of zero to one-hundred with circles at each of 10-unit increments, with the size of the circle determined by the number of products within that sale percentage band.
  • Show Promotions Process 1200 ends or returns to Figure 4 and block 1200 or to another process which may have called Show Promotions Process 1200.
  • Figure 13 illustrates an embodiment of Show Social Process 1300.
  • a show social information command may be received from a user or another process.
  • Show Social Process 1300 processes each User Home Item, User List 320, favorite or other user selection in turn.
  • Show Social Process 1300 may obtain the total number and type of social network events associated with the item of block 1310. This may include, for example, a number of "friends", “likes”, “shares”, “follows”, “tweets", messages mentioning the item, or the like. This information may be normalized relative to all of the items of block 1310 or relative to such events occurring with respect to a Category, such as a Category 335 of an item of block 1310 or a Category 335 selected by the user. This may be referred to in the claims as a "social metric". As an alternative, Social Signal 303 with respect to the items of block may be obtained. Social Signal 303 may be determined as described in US Provisional Patent
  • the information of block 1315 may be output, such as to Client Device 105.
  • Show Social Process 1300 iterates back to opening loop block 1310 to process the next item, if any.
  • Show Social Process 1300 ends or returns to Figure 4 and block 1300 or to another process which may have called Show Social Process 1300.
  • Figure 14 illustrates an embodiment of Show Analysis Process 1400.
  • a show analysis center command may be received from a user or from another process.
  • a user selection of a Brand, Merchant, Store, User Home 305, User Home Item, a Category 335, a User List 320, or a quick view may be received. More than one such selection may be received, each of which may be added to a separate tab in the Ul for Show Analysis Process 1400.
  • the selection(s) may be saved.
  • Insight Information 330 relating to the user selection(s) of block 1410 may be obtained.
  • Insight Information 330 and examples thereof are discussed above, in relation to Summary Process 900. Which Insight Information 330 to obtain may be a default setting or may be specified by the user.
  • signals may be obtained, such as Demand Signal 301, Supply Signal 302, Social Signal 303, Quality Signal 304, and Product-Type Quantity Signal 306. These Signals may be determined as described in US Provisional Patent Application Serial Number 61/952,029 and child applications thereof, such as in relation to Figures 5-11 therein. These Signals may also be referred to in the claims as “metrics”, such as “demand metric", “social metric”, etc.
  • the scale of the graph for Insight Information 330 and signal information of block 1420 may be selected, such as to present the information in a compact form without excessive blank area.
  • the information may then be output, such as to the Client Device 105, as one or more graphs.
  • the output may allow the user to select an item of block 1415 to be displayed or not displayed in the graph (which may cause the graph to be re-sized).
  • patterns may be identified in the Insight Information 330 or signal information for the user selection(s) of block 1410, such as repeating patterns and/or patterns where a first pattern with respect to a first Insight Information 330 or first Signal is preceded or followed by a second pattern in a second Insight Information 330 or second Signal. Patterns which occur across more than one Insight Information 330 or Signal may require that the more than one Insight Information 330 or Signal share a common x-axis, such as that they each are part of a time-series. Pattern identification may be according to a continuous probability distribution function or another statistical analysis. Where no pattern can be identified with respect to either a single Insight Information330/Signal or between more than one Insight Information 330/Signal, the pattern detection may return no result or may return a message indicating that no pattern was detected.
  • a user may select a price of a Category 335, such as "impact wrenches" across all Merchants or with respect to a single Merchant, and a Social Signal with respect to the same Category 335 at the Merchant(s).
  • Pattern identification may reveal that there are repeating patterns in both data sets (in the price data and in the social metric). Pattern identification may further reveal that there is a pattern between the repeating patterns in both data sets, such as that when the price for the Category "impact wrenches" is high, there is also a higher Social Signal 303. Pattern identification may reveal that the higher Social Signal 303 follows the increase in price.
  • the scale of the Insight Information 330 may be adjusted to adequately encompass patterns identified in block 1421, for example, such that the units cover the entire range, without excess empty space, and the result may be output, such as to Client Device 105.
  • the Products 327 in the user selection of block 1410 may be output to the user or another process. These may be output under a separate tab or the like.
  • user refinement of the display may be received.
  • User refinement may comprise limiting the output to specific Brands, Merchants, Stores, Products 327, price ranges, and the like.
  • the display at the Client Device 105 may be updated to reflect the refinement of block 1435.
  • the output of block 1440 may be saved as a User Analysis 385 record. This may be in response to a command received from the user or a process.
  • a command may be received from the user or a process to assign the User Analysis 385 record of block 1445 to the "Dashboard" of the user.
  • the item may be assigned to the user's Dashboard.
  • the data underlying the output of block 1440 may be updated and, as the user visits the user's Dashboard, the updated data may be visible.
  • items, not just those in the Analysis Center may be assigned to a user Dashboard, for quick access to data relating to the updated version of the item.
  • a user Dashboard may be an element in a user interface which quickly and/or persistently presents information.
  • Show Analysis Process 1400 ends or returns to Figure 4 and block 1400 or to another process which may have called Show Analysis Process 1400.
  • Figure 15 illustrates an embodiment of Recommendation Process 1500.
  • parties "A” and “B” are discussed.
  • a user in a given interaction may be represented by one of these parties, in which case a recommendation to the other party may not be output.
  • a recommendation made (or proposed to be made) to "Party B” may not be output to the user (Party A).
  • Blocks 1505 to 1575 may iterate for Product pairs such as a selected i) User Home Item (comprising User Home 305 and Competitor 310) or ii) a User List comprising at least two different Merchants, Stores, Brands, or Products.
  • Recommendation Process 1500 may proceed to block 1515, where a determination may be made regarding whether Demand Signal 301 is different between the two items (or groups of items) of blocks 1505 to 1575.
  • Demand Signal 301 may be generated as described in US Provisional Patent Application Serial Number 61/952,029 and child applications thereof. Generally, Demand Signal 301 encodes the demand for a Product or set of Products in a Brand or sold by a Store, Merchant, or the like.
  • Determination of a difference may be based on a statistically significant difference, such as two standard deviations in a probability distribution function, or a difference above a threshold.
  • Recommendation Process 1500 may recommend that the items be removed.
  • a determination may be made regarding whether or not there is a price difference between the items (or groups of items). For example, a price difference may be found when there is greater than two-standard deviations in a continuous probability distribution function. If affirmative at block 1525, then at block 1530, a determination may be made regarding whether or not there is difference in promotions between the items (or groups of items). The number of promotions, the magnitude of promotions, and the duration of promotions may be generated as described in US Patent Application Serial Number 13/951,248 in relation to "Promotion Routine 1200" described therein, and may use data in Promotions 382 record.
  • blocks 1545-1555 describe a matrix.
  • Recommendation Process 1500 may recommend to Party A that Party A has an opportunity to increase price and may recommend to Party B that Party B lower the price and/or increase promotion of the item.
  • Recommendation Process 1500 may recommend to Party A that Party A has an opportunity to increase price and/or decrease promotion and may recommend to Party B that Party B lower the price and/or increase promotion of the item.
  • Block 1555 if Party A has greater demand, lower promotion, and a higher price, then
  • Recommendation Process 1500 may recommend to Party A that Party A has an opportunity to increase price and may recommend to Party B that Party B remove the item from inventory.
  • blocks 1535 and 1540 describe a matrix.
  • Recommendation Process 1500 may recommend to Party A that Party A has an opportunity to increase price and may recommend to Party B that Party B increase promotion of the item.
  • Recommendation Process 1500 may recommend to Party A that Party A has an opportunity to increase price and may recommend to Party B that Party B increase promotion of the item or remove the item from inventory.
  • Recommendation Process 1500 may return to block 1505 to iterate over the next Product in the User Home 305 and a corresponding Competitor 310 or the next pair in the User List(s).
  • Recommendation Process 1500 may return to Quick View Process 1000 or to another routine which may have called Recommendation Process 1500.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention concerne des systèmes et des procédés permettant à une interface utilisateur de récapituler et de personnaliser une grande quantité d'informations de prix et de produits, d'identifier des modèles dans celles-ci, et de générer des recommandations par rapport à celles-ci.
PCT/US2015/020271 2014-03-12 2015-03-12 Procédé et appareil de récapitulation et de personnalisation de données massives Ceased WO2015138789A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201461952004P 2014-03-12 2014-03-12
US61/952,004 2014-03-12

Publications (1)

Publication Number Publication Date
WO2015138789A1 true WO2015138789A1 (fr) 2015-09-17

Family

ID=54072420

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/020271 Ceased WO2015138789A1 (fr) 2014-03-12 2015-03-12 Procédé et appareil de récapitulation et de personnalisation de données massives

Country Status (1)

Country Link
WO (1) WO2015138789A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10936637B2 (en) 2016-04-14 2021-03-02 Hewlett Packard Enterprise Development Lp Associating insights with data

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020091566A1 (en) * 2001-01-10 2002-07-11 Catalina Marketing International, Inc. Method and system for utilizing a telephone as a consumer request device for issuing promotions
JP2002222317A (ja) * 2001-01-26 2002-08-09 Daiwa Securities Group Inc 価格変動報知方法及び価格変動報知装置
US20120254063A1 (en) * 2011-04-04 2012-10-04 Investlab Technology Limited Researching exchange-listed products using sentiment
US20130191723A1 (en) * 2012-01-05 2013-07-25 Derek Edwin Pappas Web Browser Device for Structured Data Extraction and Sharing via a Social Network
US20140032264A1 (en) * 2012-07-25 2014-01-30 Indix Corporation Data refining engine for high performance analysis system and method

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020091566A1 (en) * 2001-01-10 2002-07-11 Catalina Marketing International, Inc. Method and system for utilizing a telephone as a consumer request device for issuing promotions
JP2002222317A (ja) * 2001-01-26 2002-08-09 Daiwa Securities Group Inc 価格変動報知方法及び価格変動報知装置
US20120254063A1 (en) * 2011-04-04 2012-10-04 Investlab Technology Limited Researching exchange-listed products using sentiment
US20130191723A1 (en) * 2012-01-05 2013-07-25 Derek Edwin Pappas Web Browser Device for Structured Data Extraction and Sharing via a Social Network
US20140032264A1 (en) * 2012-07-25 2014-01-30 Indix Corporation Data refining engine for high performance analysis system and method

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10936637B2 (en) 2016-04-14 2021-03-02 Hewlett Packard Enterprise Development Lp Associating insights with data

Similar Documents

Publication Publication Date Title
US20230230128A1 (en) Predictive recommendation system
US8626602B2 (en) Consumer shopping and purchase support system and marketplace
US8595049B2 (en) Method and system for monitoring internet information for group notification, marketing, purchasing and/or sales
US20200273054A1 (en) Digital receipts economy
US20170337614A1 (en) Method and System for Recommending Products Based on a Ranking Cocktail
US20170236160A1 (en) System and method for specifying targeted content for customers
AU2015218438A1 (en) System architecture for customer genome construction and analysis
CN110727843B (zh) 适配搜索结果的系统和方法
JP2014508333A (ja) ウェブサイト横断情報を表示する方法およびシステム
WO2015130833A1 (fr) Procédé et système de ventes à partir de médias sociaux
US11062352B2 (en) Deal program life cycle
US20150371283A1 (en) System and method for managing or distributing promotional offers
JP5957164B1 (ja) 情報処理装置、情報処理方法、及び情報処理プログラム
JP5824602B1 (ja) 情報処理装置、情報処理方法、及び情報処理プログラム
AU2018211215A1 (en) Method and system for modifying a webpage
US20190325475A1 (en) Predictive Recommendation System Using Tiered Feature Data
US11514496B2 (en) Summarization and personalization of big data method and apparatus
JP6698730B2 (ja) 抽出装置、抽出方法及び抽出プログラム
JP7145823B2 (ja) 提供装置、提供方法および提供プログラム
JP6644988B2 (ja) システム、プログラム、方法およびコンピュータ可読媒体
JP5824601B1 (ja) 情報処理装置、情報処理方法、及び情報処理プログラム
US12346946B2 (en) Summarization and personalization of big data method and apparatus
WO2015138789A1 (fr) Procédé et appareil de récapitulation et de personnalisation de données massives
JP6059597B2 (ja) コンテンツ検索結果提供装置、コンテンツ検索結果提供方法、及びコンテンツ検索結果提供システム
JP6564114B1 (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: 15760672

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15760672

Country of ref document: EP

Kind code of ref document: A1