Device, system and method for providing provider objects from a cache

1. A method comprising:

receiving, at one or more servers, provider objects representing items provided by one or more provider systems;

categorizing, at the one or more servers, the provider objects by one or more of reusability and context characteristics;

storing, by the one or more servers, at one or more memories, the provider objects as categorized;

receiving, at the one or more servers, from a requesting device, a request for one or more items provided by the one or more provider systems;

determining at the one or more servers, that a provider object, stored at the one or more memories, meets criteria associated with the request, including one or more of a respective reusability and respective context characteristics of the provider object; and

in response to determining that the provider object, that meets the criteria, is estimated to be currently valid, providing, by the one or more servers, to the requesting device, a response corresponding to the provider object,

wherein determining that the provider object, that meets the criteria, is estimated to be currently valid comprises: determining that a current time does not exceed one or more of an estimated expiry time and an estimated Time-To-Live (TTL) value of the provider object.

2. The method of claim 1 , wherein categorizing the provider objects by reusability comprises: categorizing the provider objects by one or more of respective characteristics and respective combinations of one or more respective items represented by the provider objects; and

determining that the respective reusability of the provider object meets the criteria associated with the request comprises: determining that the provider object represents one or more of same characteristics and a same combination of the one or more items requested by the request.

3. The method of claim 1 , wherein categorizing the provider objects by the context characteristics comprises:

categorizing the provider objects by one or more of a respective context in which a respective provider object was requested, a customization, a geographic location, a customer type, and a category of respective items represented by the provider objects; and

determining that the respective context of the provider object meets the criteria associated with the request comprises: determining that the provider object represents one or more of a same respective context of the request, a same customization, a same geographic location, a same customer type, and a same category of the one or more items requested by the request.

4. The method of claim 1 , wherein the provider objects comprise one or more of New Distribution Capability (NDC) offers and Edifact recommendations.

5. The method of claim 1 , further comprising:

using, at the one or more servers, a reusability determining machine learning model and a context determining machine learning model to respectively categorize the provider objects by the reusability and the context characteristics.

6. The method of claim 1 , further comprising:

using, at the one or more servers, a validity estimation machine learning model to determine that the provider object is estimated to be currently valid.

7. A server comprising:

one or more memories;

a communication interface; and

a controller configured to:

receive, via the communication interface, provider objects representing items provided by one or more provider systems;

categorize the provider objects by one or more of reusability and context characteristics;

store, at the one or more memories, the provider objects as categorized;

receive, via the communication interface, from a requesting device, a request for one or more items provided by the one or more provider systems;

determine that a provider object, stored at the one or more memories, meets criteria associated with the request, including one or more of a respective reusability and respective context characteristics of the provider object; and

in response to determining that the provider object, that meets the criteria, is estimated to be currently valid, provide, via the communication interface, to the requesting device, a response corresponding to the provider object,

wherein the controller is further configured to determine that the provider object, that meets the criteria, is estimated to be currently valid by: determining that a current time does not exceed one or more of an estimated expiry time and an estimated Time-To-Live (TTL) value of the provider object.

8. The server of claim 7 , wherein the controller is further configured to categorize the provider objects by reusability by:

categorizing the provider objects by one or more of respective characteristics and respective combinations of one or more respective items represented by the provider objects; and

determining that the respective reusability of the provider object meets the criteria associated with the request comprises: determining that the provider object represents one or more of same characteristics and a same combination of the one or more items requested by the request.

9. The server of claim 7 , wherein the controller is further configured to categorize the provider objects by context characteristics by:

categorizing the provider objects by one or more of a respective context in which a respective provider object was requested, a customization, a geographic location, a customer type, and a category of respective items represented by the provider objects; and

determining that the respective context of the provider object meets the criteria associated with the request comprises: determining that the provider object represents one or more of a same respective context of the request, a same customization, a same geographic location, a same customer type, and a same category of the one or more items requested by the request.

10. The server of claim 7 , wherein the provider objects comprise one or more of New Distribution Capability (NDC) offers and Edifact recommendations.

11. The server of claim 7 , wherein the controller is further configured to:

use a reusability determining machine learning model and a context determining machine learning model to respectively categorize the provider objects by the reusability and the context characteristics.

12. The server of claim 7 , wherein the controller is further configured to:

use a validity estimation machine learning model to determine that the provider object is estimated to be currently valid.

13. A non-transitory computer-readable medium storing a computer program, wherein execution of the computer program is for:

receiving, at one or more servers, provider objects representing items provided by one or more provider systems;

categorizing, at the one or more servers, the provider objects by one or more of reusability and context characteristics;

storing, by the one or more servers, at one or more memories, the provider objects as categorized;

receiving, at the one or more servers, from a requesting device, a request for one or more items provided by the one or more provider systems;

determining at the one or more servers, that a provider object, stored at the one or more memories, meets criteria associated with the request, including one or more of a respective reusability and respective context characteristics of the provider object; and

in response to determining that the provider object, that meets the criteria, is estimated to be currently valid, providing, by the one or more servers, to the requesting device, a response corresponding to the provider object,

wherein determining that the provider object, that meets the criteria, is estimated to be currently valid comprises: determining that a current time does not exceed one or more of an estimated expiry time and an estimated Time-To-Live (TTL) value of the provider object.

14. The non-transitory computer-readable medium of claim 13 , wherein categorizing the provider objects by reusability comprises:

categorizing the provider objects by one or more of respective characteristics and respective combinations of one or more respective items represented by the provider objects; and

determining that the respective reusability of the provider object meets the criteria associated with the request comprises: determining that the provider object represents one or more of same characteristics and a same combination of the one or more items requested by the request.

15. The non-transitory computer-readable medium of claim 13 , wherein categorizing the provider objects by the context characteristics comprises:

categorizing the provider objects by one or more of a respective context in which a respective provider object was requested, a customization, a geographic location, a customer type, and a category of respective items represented by the provider objects; and

determining that the respective context of the provider object meets the criteria associated with the request comprises: determining that the provider object represents one or more of a same respective context of the request, a same customization, a same geographic location, a same customer type, and a same category of the one or more items requested by the request.

16. The non-transitory computer-readable medium of claim 13 , wherein, wherein the provider objects comprise one or more of New Distribution Capability (NDC) offers and Edifact recommendations.

17. The non-transitory computer-readable medium of claim 13 , wherein execution of the computer program is further for:

using, at the one or more servers, a reusability determining machine learning model and a context determining machine learning model to respectively categorize the provider objects by the reusability and the context characteristics.