Resource exchange auction system

Abstract

A computer-implemented method, when executed by data processing hardware, causes the data processing hardware to perform operations. Operations include: initiating a request at a first ecosystem, the first ecosystem being one of a provider and a requester; discovering, by a second ecosystem, the initiated request, the second ecosystem being the other of the provider and the requester; and executing a resource exchange auction protocol (REAP) at one of the first ecosystem and the second ecosystem. REAP includes: controlling access to a resource; evaluating the other of the first ecosystem and the second ecosystem; selecting the other one of the first ecosystem and the second ecosystem; and sharing resources of one of the first ecosystem and the second ecosystem with the other of the first ecosystem and the second ecosystem.

Description

Technical Field

[0001] This disclosure generally relates to resource exchange auction systems used between two or more ecosystems. Background Technology

[0002] The information provided in this section is intended to provide a general overview of the background of this disclosure. To the extent described in this section, the work of the currently named inventors, and aspects of the description that may not conform to the prior art at the time of submission, are neither explicitly nor implicitly acknowledged as prior art relative to this disclosure.

[0003] Many ecosystems are equipped with communication resources (such as available bandwidth) that are used by various devices connected as part of the respective ecosystem. For example, a vehicle ecosystem may include vehicles communicating with charging stations via data resources through cloud networks. However, ecosystems often have limitations or caps on their data resources, making it possible that there may not be enough data available for communication between devices. Depletion of data resources can lead to an inactive ecosystem or the unavailability of certain functions until data resources are replenished. Therefore, there is a need to improve data resource sharing between ecosystems with surplus data resources. Summary of the Invention

[0004] In some aspects, a computer-implemented method, when executed by data processing hardware, causes the data processing hardware to perform operations. The operations include: initiating a request at a first ecosystem, which is one of a provider and a requester; discovering the initiated request by a second ecosystem, which is the other of a provider and a requester; and executing a Resource Exchange Auction Protocol (REAP) at one of the first and second ecosystems. The REAP includes: controlling access to resources; evaluating the other of the first and second ecosystems; selecting the other of the first and second ecosystems; and sharing the resources of one of the first and second ecosystems with the other of the first and second ecosystems.

[0005] In some examples, evaluating one of the first and second ecosystems may include scoring the other of the first and second ecosystems using the bidder network score of the REAP. In some configurations, the Internet of Things (IoT) controller may be configured to perform the REAP, and the IoT controller may communicate with the first ecosystem controller and the second ecosystem controller. Optionally, the first ecosystem may be a requester, and initiating a request may include the IoT controller informing the first ecosystem of the resource surplus of the second ecosystem. In some cases, the first ecosystem may be a provider, and initiating a request may include the IoT controller informing the second ecosystem of the resource surplus of the first ecosystem.

[0006] The IoT controller can be configured to perform a REAP based on requests from a second ecosystem to access resource surplus in a first ecosystem. Optionally, the REAP may include admission control logic, and controlling access to resources includes performing the admission control logic. In some examples, performing a REAP may include performing a reverse auction. Alternatively, performing a REAP may include performing a real auction.

[0007] In other aspects, a system includes data processing hardware and memory hardware in communication with the data processing hardware. The memory hardware stores instructions that, when executed on the data processing hardware, cause the data processing hardware to perform operations. The operations include: initiating a request at a first ecosystem, which is one of a provider and a requester; discovering the initiated request by a second ecosystem, which is the other of a provider and a requester; and executing a Resource Exchange Auction Protocol (REAP) via one of the first and second ecosystems. The REAP includes: controlling access to resources; evaluating the other of the first and second ecosystems; selecting the other of the first and second ecosystems; and sharing resources of one of the first and second ecosystems with the other of the first and second ecosystems.

[0008] In some examples, evaluating the other of the first and second ecosystems may include scoring the other of the first and second ecosystems using the bidder network score of the REAP. In some configurations, the Internet of Things (IoT) controller may be configured to perform the REAP, and the IoT controller may communicate with the first ecosystem controller and the second ecosystem controller. Optionally, the first ecosystem may be a requester, and initiating a request may include the IoT controller informing the first ecosystem of the resource surplus of the second ecosystem. In some cases, the first ecosystem may be a provider, and initiating a request may include the IoT controller informing the second ecosystem of the resource surplus of the first ecosystem.

[0009] The IoT controller can be configured to perform a REAP based on requests from a second ecosystem to access resource surplus in a first ecosystem. Optionally, the REAP may include admission control logic, and controlling access to resources may include performing the admission control logic. In some examples, performing a REAP may include performing a reverse auction. Alternatively, performing a REAP may include performing a real auction.

[0010] In a further aspect, a computer-implemented method, when executed by data processing hardware, causes the data processing hardware to perform operations. The operations include: initiating a request at a first ecosystem, which is one of a provider and a requester; discovering a request initiated by a second ecosystem, which is the other of the provider and requester; and executing a Resource Exchange Auction Protocol (REAP) at one of the first and second ecosystems, the REAP including admission control logic. Executing the REAP includes controlling access to resources via the admission control logic, scoring the first ecosystem using a bidder network score of the REAP, selecting the other of the first and second ecosystems, and sharing resources in one of the first and second ecosystems with the other.

[0011] Optionally, a vehicle may include a controller configured to perform the methods described above. Attached Figure Description

[0012] The accompanying drawings described herein are for illustrative purposes only and are not intended to limit the scope of this disclosure.

[0013] Figure 1 This is a schematic diagram of the first vehicle ecosystem of the resource exchange auction system disclosed herein, which communicates with the back-end server and IoT data storage.

[0014] Figure 2 This is another schematic diagram of a resource exchange auction system according to the present disclosure, which includes a first vehicle ecosystem communicating with a second vehicle ecosystem and a back-end server;

[0015] Figure 3 This is an exemplary block diagram of a resource exchange auction system based on this disclosure;

[0016] Figure 4 This is another exemplary block diagram of a resource exchange auction system according to this disclosure;

[0017] Figure 5 This is a schematic diagram illustrating the first ecosystem of the resource exchange auction system receiving a request from the second ecosystem of the resource exchange auction system according to this disclosure;

[0018] Figure 6 This is a schematic diagram illustrating a request from the first ecosystem of the resource exchange auction system to the second ecosystem of the resource exchange auction system according to this disclosure;

[0019] Figure 7 This is an exemplary flowchart of a real auction in the resource exchange auction system disclosed herein; and

[0020] Figure 8This is an exemplary flowchart of a reverse auction in the resource exchange auction system disclosed herein.

[0021] In all the accompanying drawings, the corresponding reference numerals indicate the corresponding parts. Detailed Implementation

[0022] The example configuration will now be described more fully with reference to the accompanying drawings. The example configuration is provided so that this disclosure will be thorough and will fully communicate the scope of this disclosure to those skilled in the art. Specific details, such as examples of specific components, devices, and methods, are set forth to provide a thorough understanding of the configuration of this disclosure. It will be apparent to those skilled in the art that the specific details are not required, that the example configuration may be implemented in many different forms, and that the specific details and exemplary configuration should not be construed as limiting the scope of this disclosure.

[0023] The terminology used herein is for the purpose of describing specific exemplary configurations only and is not intended to be limiting. As used herein, the singular articles “a,” “an,” and “the” may also be intended to include plural forms unless the context clearly indicates otherwise. The terms “comprising,” “including,” “containing,” and “having” are inclusive, thus specifying the presence of features, steps, operations, elements, and / or components, but not excluding the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof. The method steps, processes, and operations described herein should not be construed as requiring them to be performed in the specific order discussed or shown, unless specifically identified as such. Additional or alternative steps may be employed.

[0024] When an element or layer is referred to as “on another element or layer,” “joined to,” “connected to,” “attached to,” or “linked to” another element or layer, it may be directly on, joined to, connected to, attached to, or linked to the other element or layer, or there may be intermediate elements or layers present. Conversely, when an element is referred to as “directly on another element or layer,” “directly joined to,” “directly connected to,” “directly attached to,” or “directly linked to” another element or layer, there may be no intermediate elements or layers present. Other terms used to describe relationships between elements should be interpreted in a similar manner (e.g., “between” vs. “directly between,” “adjacent” vs. “directly adjacent,” etc.). As used herein, the term “and / or” includes any and all combinations of one or more of the related listed items.

[0025] The terms first, second, third, etc., may be used herein to describe various elements, components, regions, layers, and / or parts. These elements, components, regions, layers, and / or parts should not be limited by these terms. These terms are used only to distinguish individual elements, components, regions, layers, or parts. Terms such as “first,” “second,” and other numerical terms do not imply order or sequence unless the context clearly indicates otherwise. Therefore, the first element, component, region, layer, or part discussed below may be referred to as the second element, component, region, layer, or part without departing from the teachings of the example configuration.

[0026] In this application, including the following definitions, the term "module" may be replaced by the term "circuit". The term "module" may refer to or be a part of an application-specific integrated circuit (ASIC), or include ASICs; digital, analog, or mixed-signal analog / digital discrete circuits; digital, analog, or mixed-signal analog / digital integrated circuits; combinational logic circuits; field-programmable gate arrays (FPGAs); processors (shared, dedicated, or grouped) that execute code; memory (shared, dedicated, or grouped) that stores code executed by the processor; other suitable hardware components that provide the functions described; or some or all of the above, such as in a system-on-a-chip.

[0027] The term "code" as used above can include software, firmware, and / or microcode, and can refer to programs, routines, functions, classes, and / or objects. The term "shared processor" includes a single processor that executes some or all of the code from multiple modules. The term "group processor" includes a processor, in conjunction with an additional processor, that executes some or all of the code from one or more modules. The term "shared memory" includes a single memory that stores some or all of the code from multiple modules. The term "group memory" includes memory, in conjunction with additional memory, that stores some or all of the code from one or more modules. The term "memory" can be a subset of the term "computer-readable medium." The term "computer-readable medium" does not include transient electrical and electromagnetic signals propagating through the medium and can therefore be considered tangible, non-transitory memory. Non-limiting examples of non-transitory memory include tangible computer-readable media, including non-volatile memory, magnetic memory, and optical memory.

[0028] The apparatus and methods described in this application may be implemented, in whole or in part, by one or more computer programs executed by one or more processors. The computer program includes processor-executable instructions stored on at least one non-transitory tangible computer-readable medium. The computer program may also include and / or depend on stored data.

[0029] A software application (i.e., a software resource) can refer to computer software that enables a computing device to perform tasks. In some examples, a software application may be referred to as an "application," "app," or "program." Example applications include, but are not limited to, system diagnostic applications, system management applications, system maintenance applications, word processing applications, spreadsheet applications, messaging applications, media streaming applications, social networking applications, and game applications.

[0030] Non-transitory memory can be a physical device used for temporary or permanent storage of programs (e.g., instruction sequences) or data (e.g., program state information) for use by a computing device. Non-transitory memory can be volatile and / or non-volatile addressable semiconductor memory. Examples of non-volatile memory include, but are not limited to, flash memory and read-only memory (ROM) / programmable read-only memory (PROM) / erasable programmable read-only memory (EPROM) / electrically erasable programmable read-only memory (EEPROM) (e.g., commonly used in firmware, such as bootloaders). Examples of volatile memory include, but are not limited to, random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), phase-change memory (PCM), and magnetic disks or magnetic tapes.

[0031] These computer programs (also referred to as programs, software, software applications, or code) include machine instructions for a programmable processor and can be implemented using high-level procedural and / or object-oriented programming languages ​​and / or assembly / machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, non-transitory computer-readable medium, apparatus, and / or device (e.g., disk, optical disk, memory, programmable logic device (PLD)) used to provide machine instructions and / or data to a programmable processor, including machine-readable media that receive machine instructions as machine-readable signals. The term "machine-readable signal" refers to any signal used to provide machine instructions and / or data to a programmable processor.

[0032] Various implementations of the systems and techniques described herein can be implemented in digital electronic and / or optical circuits, integrated circuits, specially designed ASICs (Application-Specific Integrated Circuits), computer hardware, firmware, software, and / or combinations thereof. These different implementations may include implementations in one or more computer programs executable and / or interpretable on a programmable system, the programmable system including at least one programmable processor, at least one input device, and at least one output device, the programmable processor being dedicated or general-purpose, coupled to receive data and instructions from and send data and instructions to the storage system.

[0033] The processes and logic flows described in this specification can be executed by one or more programmable processors, also known as data processing hardware, which execute one or more computer programs to perform functions by manipulating input data and generating output. These processes and logic flows can also be executed by special-purpose logic circuits, such as FPGAs (Field-Programmable Gate Arrays) or ASICs (Application-Specific Integrated Circuits). For example, processors suitable for executing computer programs include general-purpose and special-purpose microprocessors, as well as any one or more processors of any kind of digital computer. Typically, the processor receives instructions and data from read-only memory or random access memory, or both. The basic components of a computer are a processor for executing instructions and one or more storage devices for storing instructions and data. Typically, a computer will also include or be operatively coupled to one or more mass storage devices for storing data, such as magnetic disks, magneto-optical disks, or optical disks, to receive data from or transfer data to, or both. However, a computer does not need to have such devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and storage devices, including, for example, semiconductor storage devices such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks or removable disks; magneto-optical disks; and CD-ROMs and DVD-ROMs. Processors and memory may be supplemented or incorporated therein by dedicated logic circuitry.

[0034] To provide interaction with the user, one or more aspects of this disclosure can be implemented on a computer having a display device for displaying information to the user, such as a CRT (cathode ray tube), LCD (liquid crystal display) monitor, or touchscreen, and optional keyboard and pointing device, such as a mouse or trackball, through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback, such as visual, auditory, or tactile feedback; and input from the user can be received in any form, including sound, speech, or tactile input. Furthermore, the computer can interact with the user by sending documents to and receiving documents from the device used by the user; for example, by sending a webpage to a web browser on the user's client device in response to a request received from a web browser.

[0035] refer to Figure 1-3The resource exchange auction system 10 is configured to exchange and direct resources 12 between a first ecosystem 100 and a second ecosystem 200. As described herein, ecosystems 100 and 200 are associated with various vehicle ecosystems. However, it is also conceivable that ecosystems 100 and 200 can be configured to utilize resources 12 to perform various functions of ecosystems 100 and 200. For example, ecosystems 100 and 200 can include, but are not limited to, vehicle-to-cloud / edge, roadside unit (RSU)-to-cloud, smart charger-to-cloud, etc. Resources 12 can include, but are not limited to, bandwidth, computing, processing, communication, etc. The resource exchange auction system 10 is configured to interconnect ecosystems 100, 200, 200a-n with a resource 12 surplus with ecosystem 200 with a resource 12 deficit. For example, the resource exchange auction system 10 is configured to manage end-to-end sharing of resources 12 from one ecosystem provider to one ecosystem receiver.

[0036] The resource exchange auction system 10 is configured to facilitate the Resource Exchange Auction Protocol (REAP) 14 via an Internet of Things (IoT) controller 16, which is configured to communicate with controllers 102 and 202 of each respective ecosystem 100, 200. For example, ecosystems 100, 200 may be configured with a controller network, and the IoT controller 16 is designed to execute REAP 14 between each ecosystem 100, 200.

[0037] For descriptive purposes, the features described with respect to the first ecosystem controller 102 may also be configured as part of the second ecosystem controller 202, such that the reference numerals used in association with the first ecosystem controller 102 can be understood as being combined with the second ecosystem controller 202 plus one hundred (100). It is also conceivable that the reference numerals used for the second ecosystem 200 substantially incorporate additional ecosystems 200a-n that can operate within the resource exchange auction system 10, such that the same reference numerals can be extended using letters.

[0038] REAP14 can be configured as the Real Auction 18 described in this article. Figure 5 ) or reverse auction 20 ( Figure 6 The data processing hardware 104 of the IoT controller 16 is executed. The IoT controller 16 also includes memory hardware 106 that communicates with the data processing hardware 104. The memory hardware 106 stores instructions that, when executed on the data processing hardware 104, cause the data processing hardware 104 to perform the operations described herein. The memory hardware 106 also stores a resource log 108 of the corresponding resource 12 of the first ecosystem 100. The resource log 108 may store resource deficits 22 and resource surpluses 24 based on the resources 12 available to the corresponding ecosystem 100. The resource log 108 may also store resources 12.

[0039] Now for reference Figure 2-5 REAP 14 can be triggered by identifying one of a resource deficit 22 and a resource surplus 24 at one of ecosystems 100 and 200, and is executed by IoT controller 16. In some cases, IoT controller 16 can identify that the first ecosystem 100 has a resource surplus 24 and can trigger REAP 14 to execute a real auction 18. Real auction 18 is defined as a resource-sharing transaction initiated by resource provider 102 (e.g., first ecosystem controller 102) that advertises to multiple bidders 200, 200a-n requesting resource 12. In this example, first ecosystem controller 102 can act as a provider configured to auction the resource surplus 24 to other ecosystems (i.e., second ecosystem 200) that may have a resource deficit 22 via IoT controller 16. Although this document describes the first ecosystem 100 and the second ecosystem 200, it is conceivable that REAP 14 can be executed among multiple ecosystems 200, 200a-n. For example, a real auction 18 can present the resource surplus 24 of the first ecosystem 100 to multiple second ecosystems 200 that may compete for the surplus resource 12.

[0040] The IoT controller 16 can receive one or more requests 26 for surplus resources 12. For example, request 26 may be initiated at a first ecosystem 100, which may be a provider or a requester, as described in more detail below. In some examples, REAP 14 may be executed by the IoT controller 16 to advertise resource surplus 24 to nearby ecosystems 200. For example, second ecosystems 200, 200a-n may discover request 26 such that second ecosystems 200, 200a-n are another of the providers or requesters described herein. In the example of Real Auction 18, resource surplus 24 may arise as a result of the first ecosystem 100 satisfying or exceeding the allocated amount of resource 12 available for use by the first ecosystem 100. The resource exchange auction system 10 advantageously facilitates the first ecosystem 100 sharing unused resource 12 (i.e., resource surplus 24) with nearby ecosystems 200 that may benefit from additional resource 12.

[0041] In other examples, IoT controller 16 can identify that the first ecosystem 100 has a resource deficit 22, allowing the first ecosystem 100 to benefit from additional resources 12. Therefore, IoT controller 16 can execute a reverse auction 20 of REAP 14 to find additional resources 12. Reverse auction 20 is defined as a resource-sharing transaction initiated by a requesting ecosystem 100 (e.g., the first ecosystem 100), where multiple provider ecosystems 200, 200a-n bid to share their respective resources 12. In one example of a reverse auction, IoT controller 16 acts as a requester configured to request resources 12 from other ecosystems 200, 200a-n. In reverse auction 20, REAP 14 advertises via request 26 that the first ecosystem 100 is looking for additional resources 12. Nearby ecosystems 200, 200a-n can receive request 26 and can issue bids 28 for reverse auction 20.

[0042] For example, the first ecosystem 100 may have access to high-speed communication bandwidth (i.e., resource 12) up to 200 (200) megabytes per second (Mbps) and has already reached the limit 110. Therefore, the first ecosystem 100 may seek additional bandwidth from ecosystem 200 that may have surplus resources (i.e., resource surplus 24). For example, a nearby ecosystem 200 may have a resource surplus of 50 (50) Mbps 24 and may offer 50 Mbps of resource surplus 24 to the first ecosystem 100 in the form of bid 28. Another ecosystem 200a may have a resource surplus of 100 (100) Mbps 24 and may also submit a bid to the first ecosystem 100 corresponding to 100 Mbps. As described in more detail below, REAP 14 is configured to compare bids 26 before selection. In either the real auction 18 or the reverse auction 20, the IoT controller 16 selects a single bidder 200, 200a-n to share or receive resource 12.

[0043] refer to Figure 3-6In response to the initiation of a real auction 18 or a reverse auction 20, REAP14 executes a bidder network score 30. The bidder network score 30 is used to rank and evaluate the various ecosystems 200, 200a-n that have bid for or provided resource 12. However, the term "bidder" can be used in either auction 20, 22, where a bidder is a potential provider or potential recipient of resource 12. Depending on whether REAP14 is executing a real auction 18 or a reverse auction 20, the bidder network score 30 may have different criteria. Depending on whether REAP14 is executing a real auction 16 or a reverse auction 18, REAP14 uses the bidder network score 30 to identify the ecosystems 100, 200, 200a-n that have the greatest demand for resource 12 or the greatest availability of resource 12. The bidder network score 30 may be a market-driven score, allowing the IoT controller 16 to assess the supply and demand for resource 12. For example, in a real auction 20, the bidder with the highest bidder network score 30 is the ecosystem 200, 200a-n with the greatest demand for resources. In contrast, in a reverse auction 22, the bidder with the highest bidder network score 30 is the ecosystem 200, 200a-n with the largest available resource 12. Therefore, the bidder network score 30 provides a degree of leverage for the receiver and / or provider (e.g., the first ecosystem 100).

[0044] The bidder network score 30 is based on the urgency, mobility, location, availability, congestion, and energy of the corresponding bidders 200, 200a-n. For example, the first ecosystem controller 100 evaluates each application threshold and requirement to identify which bidder ecosystems 200, 200a-n are compatible with request 26. Although the initiation of REAP 14 on IoT controller 16 can be based on a real auction 18 or a reverse auction 20, REAP 14 includes the same procedural steps used for both real auction 18 and reverse auction 20. As described above, REAP 14 is executed by IoT controller 16 in response to initiation. As described above, the initiation steps depend on whether ecosystem 100 is in a resource deficit 22 or a resource surplus 24.

[0045] Once initiated, REAP14 identifies the relevant bidders (e.g., provider ecosystems 200, 200a-n or requester ecosystems 200, 200a-n). REAP14 can advertise resource states 20, 22 via service discovery 32. The advertisement by REAP14 may include resource parameters 34, which clarify the conditions considered for use in resource exchange transactions. For example, REAP14 may indicate the costs associated with resource 12. Service discovery 32 uses each layer 32a-32c to identify bidders 200, 200a-n for the auctioned resource 12. Again, note that bidders 200, 200a-n can bid on resource 12 (i.e., a real auction 18) or have the opportunity to bid on shared resource 12 (i.e., a reverse auction 20).

[0046] REAP14 then executes bidder authorization 36 to identify bidders 200, 200a-n using appropriate criteria. These criteria can be set by the IoT controller 16 based on available resources 12 and / or on resources 12 required by the first ecosystem 100. Bidder authorization 36 is the initial permission to ensure that bidders 200, 200a-n match the criteria and are able to make a selection. Therefore, bidder authorization 36 is independent of the selection by bidders 200, 200a-n.

[0047] Further reference Figure 3-6 The IoT controller 16 is configured to control access to resource 12 after authorizing bidders 200, 200a-n, such that admission control logic 38 executes REAP 14. For example, admission control logic 38 may execute a connection mode 40, which evaluates the network associated with bidders 200, 200a-n and a relevant score 30a from the bidder network score 30. Furthermore, connection mode 40 may evaluate the proximity 42 of bidders 200, 200a-n. It is also conceivable that admission control logic 38 may utilize other modes to determine access for bidders 200, 200a-n, and those mentioned herein are examples of condition types considered for allowing access.

[0048] Regarding the score 30a of bidders 200, 200a-n, in the case of a real auction 18, REAP 14 can adjust the price associated with resource 12. For example, if score 30a is high, then score 30a indicates a higher demand for resource 12. In this example, IoT controller 16 can increase the price or cost associated with resource 12 to maximize profit. Therefore, REAP 14 can be configured to identify bidders 200, 200a-n with the highest score 30a in order to select bidders 200, 200a-n. In the case of a reverse auction 20, IoT controller 16 executes admission control logic 38 to determine which provider—bidder 200, 200a-n—is capable of providing the most resource 12.

[0049] In some examples, REAP14 can provide the ability to share tangible and intangible resources 12. For example, in reverse auction scenario 18, if the first bidders 200, 200a are a charging ecosystem equipped with a cellular network, then the first ecosystem 100 can utilize both charging resources 12 and cellular network resources 12. In contrast, the second bidders 200, 200b can provide charging resources 12 but not cellular resources. In reverse auction 16, the IoT controller 16 can select the first bidders 200, 200a based on the quantity and / or type of available resources 12. In this example, as a result of the diverse resources 12 available from the first bidders 200, 200a, the first bidders 200, 200a will have a higher score 30a than the second bidders 200, 200b.

[0050] In the real auction example 18, due to the established relationship between the first bidders 200, 200a and the first ecosystem 100, the first bidders 200, 200a may have a higher score 30a compared to the second bidders 200, 200a. For example, the first bidders 200, 200a and the second bidders 200, 200b may have equal need or urgency for the resource 12 advertised by the IoT controller 16, but the first bidders 200, 200a have established trust with the first ecosystem 100 (e.g., an established trusted entity). As a result, REAP 14 can assign a higher score 30a when performing bidder network scoring 30 to prioritize bidders 200, 200a with existing relationships. Established or existing relationships can be brand or other contractual relationships that are programmed into REAP 14 or are known to the IoT controller 16.

[0051] Once bidders 200 and 200a have been certified, evaluated, and selected, resource 12 is shared between the first ecosystem 100 and bidder ecosystems 200 and 200a-n via IoT controller 16. As described above, individual bidder ecosystems 200 and 200a-n are selected for sharing resources between the selected bidder ecosystems 200 and 200a-n and the first ecosystem 100.

[0052] Now for reference Figure 7 and Figure 8 This shows a real auction 18 of the resource exchange auction system 10. Figure 7 ) and reverse auction ( Figure 8 An exemplary flowchart. (About) Figure 7At 500, IoT controller 16 advertises resource 12 as resource surplus 24 and receives request 26 for the resource at 502. At 504, REAP 14 determines whether bidders 200, 200a-n are authorized. If bidders 200, 200a-n are not authorized, REAP 14 evaluates other requests 26 at 506. If bidders 200, 200a-n are authorized, REAP 14 controls access to the resource at 508 and evaluates bidders 200, 200a-n at 510. After evaluation, REAP 14 selects bidders 200, 200a-n at 512 and receives payment for resource 12 at 514. Once payment is complete, IoT controller 16 provides access to the resource at 516.

[0053] refer to Figure 8 At 600, IoT controller 16 advertises request 26 for resource 12 and at 602 identifies resource provider bidders 200, 200a-n. REAP 14 at 604 determines whether provider bidders 200, 200a-n are authorized. If provider bidders 200, 200a-n are not authorized, REAP 14 evaluates another provider bidder 200, 200a-n at 606. If provider bidders 200, 200a-n are authorized, REAP 14 controls access to resource 12 at 608 and evaluates provider bidders 200, 200a-n at 610. IoT controller 16 can then select a provider at 612 and receive resource 12 at 614. In some examples, IoT controller 16 also proceeds to a payment step to exchange the received resource 12.

[0054] Refer again Figure 1-8 The resource exchange auction system 10 advantageously assists ecosystems 100, 200, 200a-n in sharing and exchanging resources 12 to maximize the available resources 12 for a given ecosystem 100, 200, 200a-n. REAP 14 provides the IoT controller 16 with the ability to evaluate and compare the structures of bidders 200, 200a-n based on one of resource surplus 24 and resource deficit 22, to identify the compatibility and suitability of resources 12 by performing bidder network scoring 30. Furthermore, the execution of admission control logic 38 further facilitates the comparison of scores 30a of bidders 200, 200a-n and the setting of potential payout ratios based on scores 30a. Additionally, in some examples, REAP 14 can advantageously assist the IoT controller 16 in prioritizing bidders 200, 200a-n who have established relationships with ecosystems 100, 200a-n associated with the IoT controller 16. Therefore, by allocating unused resources 12 to ecosystems 100 and 200 that may experience resource deficits 22, all ecosystems 100 and 200 can benefit from the implementation of the resource exchange system 10.

[0055] Many embodiments have been described. However, it should be understood that various modifications can be made without departing from the spirit and scope of this disclosure. Therefore, other embodiments are also within the scope of the following claims.

[0056] The foregoing description has been provided for purposes of illustration and description. It is not intended to be exhaustive or limiting of this disclosure. Individual elements or features of a particular configuration are generally not limited to that particular configuration, but where applicable, they are interchangeable and can be used in selected configurations, even if not specifically shown or described. This can also be varied in many ways. Such variations should not be considered as departing from this disclosure, and all such modifications are intended to be included within the scope of this disclosure.

Claims

1. A computer-implemented method, when executed by data processing hardware, to cause the data processing hardware to perform operations including: The request is initiated at the first ecosystem, which is one of the providers and the requester; The request was initiated by the second ecosystem, which is another of the providers and requesters; and A resource exchange auction protocol (REAP) is executed at one of the first and second ecosystems, the REAP comprising: Control access to resources; Evaluate the other of the first and second ecosystems; Choose the other of the first and second ecosystems; and It shares resources of one of the first and second ecosystems with another in the first and second ecosystems.

2. The method according to claim 1, wherein, Evaluating the other of the first and second ecosystems includes scoring the other of the first and second ecosystems using the bidder network score of the REAP.

3. The method according to claim 1, wherein, The Internet of Things (IoT) controller is configured to execute the REAP, and the IoT controller communicates with the first ecosystem controller and the second ecosystem controller.

4. The method according to claim 3, wherein, The first ecosystem is the requester, and initiating the request includes the IoT controller notifying the first ecosystem of the resource surplus of the second ecosystem.

5. The method according to claim 3, wherein, The first ecosystem is a provider, and initiating the request includes the IoT controller notifying the second ecosystem of the resource surplus of the first ecosystem.

6. The method according to claim 5, wherein, The IoT controller is configured to execute the REAP based on a request from the second ecosystem to access the resource surplus of the first ecosystem.

7. The method according to claim 1, wherein, The REAP includes admission control logic, and controlling access to resources includes executing the admission control logic.

8. The method according to claim 1, wherein, Executing the aforementioned REAP includes performing a reverse auction.

9. The method according to claim 1, wherein, Performing the aforementioned REAP includes performing a real auction.

10. A vehicle including a controller configured to perform the method of claim 1.

Images