Patent Application
20200097893
The invention pertains to data aggregation and distribution. It has application, by way of nonlimiting example, in making inventory data from disparate sources available over a distributed network.
The growth of e-commerce, the rise of chain stores, the internationalization of supply networks, and the popularity of just-in-time manufacturing pose a perfect storm for “connected” retailers—i.e., those with a web presence through which to advertise and sell products. No longer are prospective purchasers satisfied knowing that an item of interest is available through a retailer, they want to know that its available for shipping now and, better, that it is available for immediate pick-up at a brick-and-mortar outlet the next town over.
For the retailer, that kind of data can be hard to come by, at least with the speed demanded by today's consumers. Telling a frustrated customer that the “hurry—only three more available” message on the website was accurate 24 hours ago is not good for business. The art has suggested various solutions, but they have not proven satisfactory.
A more complete understanding of the discussion that follows may be attained by reference to the drawings, in which:
Devices 12, 14A-14C comprise conventional desktop computers, workstations, minicomputers, laptop computers, tablet computers, PDAs, mobile phones or other digital data devices of the type that are commercially available in the marketplace, all as adapted in accord with the teachings hereof. Thus, each comprises central processing, memory, and input/output subsections (not shown here) of the type known in the art and suitable for (i) executing software of the type described herein and/or known in the art (e.g., applications software, operating systems, and/or middleware, as applicable) as adapted in accord with the teachings hereof and (ii) communicating over network 16 to other devices 12, 14A-14C in the conventional manner known in the art as adapted in accord with the teachings hereof.
Examples of such software include web server 30 that executes on device 12 and that responds to requests in HTTP or other protocols from clients 14A-14C (and, more particularly, from the users thereof) for transferring web pages, downloads and other digital content to the requesting device over network 16, in the conventional manner known in the art as adapted in accord with the teachings hereof. Web server 30 includes web application 31 that includes a data-aggregating and distributing function that may be part of broader functionality provided by the web application 31 such as, for example, serving up a web site or web service (collectively, “web site”) to client devices, all per convention in the art as adapted in accord with the teachings hereof.
In the illustrated embodiment, that web site is, by way of non-limiting example, an e-commerce site of a retailer, e.g., for advertising and selling goods to its customers, and the data-aggregating and distributing function is, by way of non-limiting example, an inventory function that aggregates data regarding inventory available to those customers from the disparate sources from which the retailer obtains goods for customer order and/or purchase, all per convention in the art as adapted in accord with the teachings hereof. In the illustrated embodiment, those sources comprise brick-and-mortar outlets 50, order fulfillment, warehousing, and/or in-process manufacturing locations 52, and in-transit shipping 54, though, other embodiments may vary in this regard.
Web framework 32 comprises conventional such software known in the art (as adapted in accord with the teachings hereof) providing libraries and other reusable services that are (or can be) employed—e.g., via an applications program interface (API) or otherwise—by multiple and/or a variety of web applications executing on the platform supported by server 12, one of which applications is shown here (to wit, web application 31).
In the illustrated embodiment, web server 30 and its constituent components, web application 31 and framework 32, execute within an application layer 38 of the server architecture. That layer 38, which provides services and supports communications protocols in the conventional manner known in the art as adapted in accord with the teachings hereof, can be distinct from other layers in the server architecture—layers that provide services and, more generally, resources (a/k/a “server resources”) that are required by the web application 31 and/or framework 32 in order to process at least some of the requests received by server 30 from clients 14A-14C and to obtain inventory (and/or other) data for aggregation, e.g., from outlets 50, locations 52, and so forth, all per convention in the art as adapted in accord with the teachings hereof.
Those other layers include, for example, a data layer (which provides services supporting interaction with a database server 40, an event processing framework 62 (
Though described herein in the context of a web site, in other embodiments web server 30 and applications 31 and 32 may define a web service or other functionality (e.g., available through an API or otherwise) suitable for responding to user requests, e.g., a video server, a music server, or otherwise. And, though shown and discussed here as comprising a separate web application 31 and framework 32, in other embodiments, the web server 30 may combine the functionality of illustrated components 31 and 32 in a single component or distribute it among still more components.
With continued reference to
The devices 12, 14A-14C of the illustrated embodiment may be of the same type, though, more typically, they constitute a mix of devices of differing types. And, although only a single server digital data device 12 is depicted and described here, it will be appreciated that other embodiments may utilize a greater number of these devices, homogeneous, heterogeneous or otherwise, networked or otherwise, to perform the functions ascribed hereto to web server 30 and/or digital data processor 12. Likewise, although three client device 14A-14C are shown, it will be appreciated that other embodiments may utilize a greater or lesser number of those devices, homogeneous, heterogeneous or otherwise, running applications (e.g., 44) that are, themselves, as noted above, homogeneous, heterogeneous or otherwise. Moreover, one or more of devices 12, 14A-14C may be configured as and/or to provide a database system (including, for example, a multi-tenant database system) or other system or environment; and, although shown here in a client-server architecture, the devices 12, 14A-14C may be arranged to interrelate in a peer-to-peer, client-server or other protocol consistent with the teachings hereof.
Retail outlets 50 comprise one or more brick-and-mortar or other facilities from which customers can obtain goods per convention in the art as adapted in accord with the teachings hereof. Illustrated outlets 50 include (or are otherwise associated with) digital data processing equipment coupled to network 16 for transferring information, e.g., to server 12 or otherwise, regarding inventory availability per convention in the art as adapted in accord with the teachings hereof. The outlets can include point-of-sale (POS) terminals, back-office or other digital data processing equipment (not shown) capable of at least generating and transmitting on network 16 information to that server 12 or otherwise regarding (i) on-hand inventory, (ii) inventory subject to in-process orders (e.g., inventory on reserve for customers while awaiting order completion and/or payment), and/or (iii) inventory in reserve for demonstration or display to prospective customers and, thus, not available for purchase. Such information can be collected and generated at the respective outlets in the conventional manner known in the art as adapted in accord with the teachings hereof (e.g., via POS logging, attendant-equipped bar scanners, etc.) on a per-SKU (stock-keeping unit), per-UPC (universal product code), or other basis, again, per convention in art as adapted in accord with the teachings hereof. The transmission of such data on network 16 is within the ken of those skilled in the art as informed by the teachings hereof.
Locations 52 comprise one or more order fulfillment, warehousing, in-process manufacturing or other locations from which a retailer can obtain a supply of goods to reasonably meet customer orders. As above, illustrated locations 52 include (or are otherwise associated with) digital data processing equipment coupled with network 16 for generating and/or transferring information, e.g., to server 12 or otherwise, regarding inventory availability per convention in the art as adapted in accord with the teachings hereof. This can include inventory that is ready for shipment directly to customers and/or to retail outlets 50, as well as inventory for which manufacturing is (or can be) in-process and, thus, can also be ready for shipment in reasonable time, all per convention in the art as adapted in accord with the teachings hereof. As above, such information can be collected and generated at the respective locations 52 in the conventional manner known in the art as adapted in accord with the teachings hereof, e.g., on a per-SKU, per-UPC, or other basis, and it can be transmitted on network 16 in a conventional manner known in the art, again, too, as adapted in accord with the teachings hereof.
In transit shipping 54 comprise one or more transports via which goods are routed to and between outlets 50 and locations 52 per convention in the art as adapted in accord with the teachings hereof. These include (or are otherwise associated with) digital data processing and/or other equipment, including for example RFID-equipped or otherwise sensorized pallets, containers and the like, suitable for generating and/or transferring information, e.g., to server 12 or otherwise, regarding inventory availability per convention in the art as adapted in accord with the teachings hereof. This can include inventory that is currently en route and/or is being readied therefor, as well as inventory that has been delivered and is being readied for stocking at an outlet 50 or location 52, all per convention in the art as adapted in accord with the teachings hereof. As above, such information can be collected and generated in connection with shipping in the conventional manner known in the art as adapted in accord with the teachings hereof, e.g., on a per-SKU, per-UPC, or other basis, and it can be transmitted on network 16 in a conventional manner known in the art, again, too, as adapted in accord with the teachings hereof.
Network 16 is a distributed network comprising one or more networks suitable for supporting communications between server 12 and client device 14A-14C. The network comprises one or more arrangements of the type known in the art, e.g., local area networks (LANs), wide area networks (WANs), metropolitan area networks (MANs), and or Internet(s). Although a client-server architecture is shown in the drawing, the teachings hereof are applicable to digital data devices coupled for communications in other network architectures.
As those skilled in the art will appreciate, the “software” referred to herein—including, by way of non-limiting example, web server 30 and its constituent components, web application 31 and web application framework 32, browser 44—comprise computer programs (i.e., sets of computer instructions) stored on transitory and non-transitory machine-readable media of the type known in the art as adapted in accord with the teachings hereof, which computer programs cause the respective digital data devices, e.g., 12, 14A-14C to perform the respective operations and functions attributed thereto herein. Such machine-readable media can include, by way of non-limiting example, hard drives, solid state drives, and so forth, coupled to the respective digital data devices 12, 14A-14C in the conventional manner known in the art as adapted in accord with the teachings hereof.
Described below in connection with
Referring to
The event processing framework (or “event processor”) 62, executing in the data layer of server 12, logs and distributes those events 60 on a stream/broadcast and/or on-request basis to subscribing devices and/or processes, per convention in the art as adapted in accord with the teachings hereof. In the illustrated embodiment, the aforementioned inventory functionality of web application 31 is configured as one such a subscriber, again per convention in the art as adapted in accord with the teachings hereof. Although the illustrated embodiment utilizes event processing for transferring inventory data from outlets 50, locations 52 and transports 54 to inventory functionality/web application 31, other embodiments may utilize other data transfer methods known in the art for such purpose, instead or in addition.
The inventory functionality 31, in turn, aggregates and distributes the inventory data to requesting ones of the client devices 14A-14C. This can be in response to requests generated by their respective web browsers 44 (e.g., at the behest of their respective users or otherwise), as per convention in the art as adapted in accord with the teachings hereof. In addition to aggregating that data, functionality 31 can impose filter 64 to limit the aggregated inventory data to meet specifics of each request—e.g., for data pertaining to a specific outlet 50 or outlets, location 52 or locations, or transport 54 or transports (e.g., in a geographic area or otherwise), for data pertaining to specific goods (e.g., as specified by SKU, UPC or otherwise), as specified by such requests and as within the ken of those skilled in the art in view of the teachings hereof. Moreover, the functionality can impose adjustment 66 to reduce the amount of any aggregation to accommodate inventory required for reserve at outlets 50.
Thus, by way of example, browser 44 of client device 14C can generate a request for availability in inventory of a specific running shoe at retail outlets 50 and warehouses 52 in the Houston area. That request can be made explicitly by a user of device 14C or, alternatively, can be generated on the user's behalf by client-side code, injected or otherwise. Regardless, in response, application/functionality 31 can aggregate data 72 published to the event processing framework 62, imposing filter 64 to limit the aggregation to data 74 (i) from outlets 50 and warehouses 52 in that locale and (ii) pertaining to that shoe. The functionality 31 can, moreover, reduce 66 that filtered aggregation to accommodate inventory required for reserve at the respective retail outlets 50 (e.g., in accord with amounts published by them to the framework 62). The functionality can transfer that filtered, reduced aggregated data 76 to the requesting browser for presentation to the user via browser 44 of device 14C.
This scenario can be repeated by devices 14A-14C, each time their respective browsers request inventory data at the behest of their respective users or otherwise. Of course, those requests need not be limited to the specifics of the example above but, rather, can be for inventory data filtered in other ways, if at all, e.g., by locale, product and so forth, with or without inventory reserve reductions as per the demands of each user. The requests by those devices 14A-14C and the responses by web application/functionality 31 are identified by transactions 78-84 in the drawing.
In order to reduce contention when updating records during high load on the system, some embodiments utilize the known pattern of event sourcing. In such embodiments, the framework 62, server 12, and/or inventory module 31A store events to represent changes in inventory. These are aggregated together in insertion order, resulting in a view of inventory details at the time of the most recently aggregated event.
Some embodiments aggregate inventory availability for a group of physical facilities, e.g. locations 52 and outlets 50, in a way that minimizes the impact of selling more stock than is available. The following pseudo code describes such an implementation. ATSI represents the Available to Sell Inventory for a specific stock unit. G represents a group of physical facilities. “Physical” stock is quantity on hand, “committed” is inventory that has been purchased and may or may not yet be shipped, and “safety stock” is inventory reserves that reduce the available count as described above. Although the following pseudo code details specific algorithms by way of example, it will be appreciated that other algorithms may be utilized to achieve like results.
Described above and shown in the drawings are apparatus, systems and method for distributed inventory data aggregation and distribution. It will be appreciated that the embodiments shown here are merely examples and that others fall within the scope of the invention. Thus, by way of non-limiting example, although the discussion above refers to inventory reserves in the context of retail outlets 50, it will be appreciated such in some embodiments such reserves can be provided for vis-à-vis locations 52 and transports 52. Moreover, although in the discussion above, inventory data received from the outlets 50, locations 52 and transports 54 is aggregated and filtered before it is reduced in accord with such inventory reserves, the reduction can be implemented prior to aggregation and/or filtering without varying from the spirit hereof. Still further, although the inventory reserves are published by the outlets 50 (and, potentially, by the locations 52 and transports 54) in the embodiments described above, such reserves can implemented as default values (or otherwise) maintained, e.g., by functionality 31. These and other variations are contemplated by the claims, as set forth below.
