System and method for managing a resource

Abstract

The present invention relates to a system for managing a resource, the system comprising a data processing component, wherein the system is configured: to receive a request for allocation of an available resource, to receive data related, at least in part, to the available resource, and wherein the system is configured to allow receiving the request for allocation of the available resource after receiving the data related, at least in part, to the available resource. The present invention also relates to a corresponding method and a computer program product.

Description

SYSTEM AND METHOD FOR MANAGING A RESOURCERELATED APPLICATIONS

[0001] The present application claims priority to EP Patent Application No. 24158364.0, filed February 19, 2024, which is hereby incorporated by reference in its entirety.BACKGROUND INFORMATION

[0002] In organizations / institutions, resources are typically allocated to employees. Resources may comprise shared resources such as workspaces, hardware, or software. Resources may also comprise other resources that, though not shared, may be easy to utilize by another employee. Such resources may comprise, for example, vacation days. Some of these resources may only allow time-limited access to the employees of the organization. For example, the number of vacation days may be time-limited to a financial year and may have to be used within the financial year. Or, for example, the organization may have a license for a software that is time- limited to 3 months that may have been purchased for use by a particular employee, but the use of which by the particular employee may have been completed well before the end of the 3-month period. Further exemplarily, the institution may have purchased computing time at a high-performance computing center, and the intended use may be completed with lesser computing time than purchased.

[0003] In such situations, it may be of advantage to allow other employees access to the resource, in so far as permitted within the terms of the resource (for example, if allowed under the software license). The utilization of the resource by other employees may improve the output as well as efficiency of resource-utilization of the organization / institution. Further, any waste occurring from low utilization of the resource may be avoided. It is an aim of the present invention to provide a system and a method to allow such access to a resource.

[0004] Typical systems for management of resources as described above may be manual and, thus, prone to errors, or may not allow resources to be utilized efficiently. For example, such a system may allocate the resource to a first person making the request, without considering the efficiency of utilization of that person.BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Exemplary features of the invention are further detailed in the figures and the description of the figures below.

[0006] Figure 1 depicts an embodiment of a system for managing a resource; and

[0007] Figure 2 depicts an embodiment of a method for managing a resource.DETAILED DESCRIPTION

[0008] The present invention relates to the field of resource management. More particularly, it relates to a system and a method for re-allocation of an available resource simply and more efficiently.

[0009] The present invention seeks to overcome or at least alleviate the shortcomings and disadvantages of the prior art. More particularly, it is an object of the present invention to provide a system and a method for managing resources that may be simpler, easier to use, efficient, and that may be more reliable in that resources may be utilized with greater efficiency. The present invention also relates to a computer program product corresponding to the method.

[0010] According to a first aspect, the present invention relates to a system for managing a resource, the system configured to receive a request for allocation of an available resource. The system may be of particular advantage for managing resources in an organization, for example. The resources may have been allocated to employees of the organization. For efficient use of the resources, it may be advantageous to have a system to re-distribute / re-allocate resources among the employees. The system according to the present invention may be of particular advantage in this re-distribution / re-allocation, thereby improving the efficiency of resource consumption.

[0011] The system may be configured to assign a rank to the received request. The assignment of a rank may be of advantage in re-allocation of the resource based, at least in part, on the request.

[0012] The system may be configured to receive a plurality of requests for allocation of the available resource. In other words, multiple requests may be received for allocation of the available resource. This may be of advantage in optimizing the efficiency of consumption of the available resource as the available resource may be allocated based, at least in part, on where it may be most efficiently consumed.

[0013] The system may be configured to assign a rank to each of the plurality of received requests.

[0014] The system may be configured to store the request.

[0015] The system may be configured to assign the rank based, at least in part, on a request stored previously. The storage of requests may be of advantage in allowing ranks to be assigned. In particular, the system 1 may compare a request stored previously, and the current request, and determine the rank to be assigned to the current request, viz., whether to assign a rank equal to or higher or lower than that of the previously stored request.

[0016] The system may be configured, in absence of a request stored previously, to assign the rank based, at least in part, on a random value. The random value may be of advantage in assignment of rank to a first request. Subsequent requests may be ranked based on the rank assigned to the first request.

[0017] The system may comprise a memory component configured to store the request. The memory component may be further configured to store the rank assigned to the request.Generally, the memory component may store requests and the rank assigned to each of the requests.

[0018] The system may comprise a data processing component.

[0019] The data processing component may be configured to assign the rank to the received request.

[0020] The data processing component may be configured to retrieve the previously stored request. For example, the data processing component may retrieve a previously stored request, and the rank assigned thereto, from the memory component and compare the current request to the retrieved request. Based, at least in part, on the comparison, the data processing component may assign a rank to the current request. The data processing component may be further configured to send the current request together with the assigned rank to the memory component.

[0021] The system may comprise a communication component. The communication component may be of advantage in communicating with a resource database, a sender database, a receiver database, or a user, as described further below. The communication component may also be of advantage in enabling communication between different components of the system as described herein. In some embodiments, the system may comprise a first communication component for communication between components of the system, and a second communication component for communication with an external system. The first and the second communication component may provide different levels of data security and privacy.

[0022] The communication component may be configured to communicate with the data processing component.

[0023] The communication component may be configured to communicate with the memory component. Thus, the communication component may allow the data processing component and the memory component to communicate with each other. In some embodiments, the data processing component and the memory component may communicate with each other, without the aid of a communication component.

[0024] The system may be configured to receive data related, at least in part, to the available resource. The data related, at least in part, to the available resource may comprise data indicating an availability status of the resource - for example, that the resource is available. Further data related, at least in part, to the available resource is described below. For example, the system may comprise a user interface component that may be used to receive the data related, at least in part, to the available resource.

[0025] The system may be configured to store the data, or at least a part thereof, related, at least in part, to the available resource. Storage of the data may be of advantage in associating (minimum) values with resources that become available in future, or in identifying similar resources previously available, as described further below.

[0026] The system may be configured to allow receiving the request for allocation of the available resource after receiving the data related, at least in part, to the available resource. Thus, the receiving of the data related, at least in part, to the available resource may indicate that the resource is available for re-allocation.

[0027] The system may be configured to allow receiving the request for allocation of the available resource within a defined time interval after receiving the data related, at least in part, to the available resource. For example, the defined time interval may comprise a time interval of 1 week, such that requests for allocation of the available resource may be received within 1 week of the data related, at least in part, to the available resource being received.

[0028] The system may be configured, in response to receiving the request for allocation of the available resource after the defined time interval has elapsed, to disallow the request. In other words, requests for allocation of the available resource may only be received by the system within the defined time interval. This may be of advantage in ensuring that the available resource can be re-allocated for consumption. For example, the resource may only become available at a starting time in future. Then, the defined time interval may be such that requests may only be received before the starting time, otherwise the resource may not be efficiently consumed.

[0029] The system may be configured to receive data related, at least in part, to the defined time interval. For example, the data related to the defined time interval may comprise a starting time from which and / or an ending time until which requests for allocation of the available resource may be received.

[0030] The request may be associated with a receiver.

[0031] The receiver may be associated with a unique receiver identifier. The receiver identifier may be of advantage for protecting the privacy of the receiver.

[0032] The system may be configured to determine if the request satisfies an allocation condition. The allocation condition may be of advantage in defining, at least in part, the condition for allocation of the available resource. For example, the allocation condition may be based, at least in part, on the receiver identifier associated with a request such that a request may satisfy the allocation condition only if the receiver identifier corresponds to one of a pre-defined group of receiver identifiers. This may be of advantage in improving the robustness of the resource allocation as resources may only be allocated, for example, to receivers that can use them efficiently.

[0033] The system may be configured to assign the rank based, at least in part, on a result of the determination if the request satisfies an allocation condition. In particular, a rank may not be assigned if the request does not satisfy an allocation condition. Alternatively, or additionally, the available resource may not be allocated to a receiver associated with a request that does not satisfy the allocation condition. Not assigning a rank to such a request may then be of advantage in improving the efficiency of the system according to the present invention.

[0034] The system may be configured to allocate the available resource based, at least in part, on a result of the determination if the request satisfies an allocation condition. For example, in some embodiments, the available resource may be allocated to the receiver associated with the first request (temporally) that satisfies the allocation condition.

[0035] The system may be configured to allocate the available resource based, at least in part, on the assigned rank.

[0036] The system may be configured to allocate the available resource to the receiver associated with a request.

[0037] The system may be configured to determine the request with the highest rank.

[0038] The system may be configured to allocate the available resource to the receiver associated with the request with the highest rank. Thus, the system may be configured to determine the request with the highest rank, for example, at the end of the defined time intervalas described above. The receiver or receiver identifier associated with the request with the highest rank may be determined and the system may be configured to allocate the available resource to the receiver or the receiver identifier.

[0039] The available resource may be associated with a sender. The available resource may have been allocated to the sender. The sender may not be able to use the resource and may, thus, decide to make it available. The system as described herein may allow the sender to allow the resource to be re-allocated easily and simply.

[0040] The sender may be associated with a unique sender identifier. This may also be of advantage in enhancing privacy protection for the sender.

[0041] The system may be configured to receive the data related, at least in part, to the available resource from the sender.

[0042] The system may be configured to receive data related, at least in part, to the allocation condition. The data related, at least in part, to the allocation condition may comprise, for example, providing the pre-defined group of receiver identifiers as described above.Alternatively, or additionally, the data related, at least in part, to the allocation condition may comprise a selection if the resource is allocated to the first request that satisfies the allocation condition.

[0043] The system may be configured to receive the data related, at least in part, to the allocation condition from the sender.

[0044] The system may be configured to communicate with a resource database. The resource database may be of advantage in recording the allocation of resources. The system may send requests indicating re-allocation of resources to the resource database. The resource database may be queried to retrieve the identifier associated with a resource.

[0045] The resource database may comprise data related, at least in part, to the sender identifier.

[0046] The resource database may comprise data related, at least in part, to the association between the sender identifier and the available resource. For example, the association may be stored by means of a look-up table, such that all the resources allocated to a sender may be retrieved by providing the sender identifier.

[0047] In embodiments of the present invention, the look-up table may be implemented by, for example, a tree, a hash map, or by any other suitable data structures.

[0048] The resource database may comprise data related, at least in part, to the receiver identifier. In other words, the resource may only be allocated to receivers whose identifiers arealso stored in the resource database. For example, as described above, the system may be of particular advantage for managing resources in an organization. The senders and receivers may both be required to be employees of the organization. The resource database may then comprise a database with employee identifiers for employees of the organization.

[0049] The system may be configured, in order to allocate the available resource, to send a request to the resource database to associate the available resource with the receiver identifier associated with the request for allocation of the available resource. In other words, the system may be configured to determine the request based, at least in part, on which the available resource is to be allocated. Subsequently, the system may be configured to determine the receiver identifier associated with the said request. Then, the system may be configured to send a request to the resource database to associate the available resource with the receiver identifier of the said request.

[0050] The resource database may be appropriately configured to receive such a request from the system.

[0051] The system may be configured, in response to sending the request to the resource database, to receive a notification relating to a result of processing of the request by the resource database. In other words, the resource database may associate the available resource with the receiver identifier based, at least in part, on the request received from the system, and send a notification confirming the association back to the system.

[0052] The data related, at least in part, to the available resource may comprise a starting time corresponding to a first time that the resource is available.

[0053] The data related, at least in part, to the available resource may comprise an ending time corresponding to a last time that the resource is available.

[0054] The starting time and / or the ending time may correspond to a day.

[0055] The system may be configured to determine a time at which the data related, at least in part, to the available resource is received. The starting time, as described above, may correspond, at least significantly, to the time at which the data related, at least in part, to the available resource is received. The said time may also be referred to as a resource-reception time.

[0056] The system may be configured to determine an expiry time corresponding to a time interval between the starting time and the time at which the data related, at least in part, to the available resource is received.

[0057] The expiry time may correspond to a number of days between the day on which the data related, at least in part, to the available resource is received and the day corresponding to the starting time.

[0058] The defined time interval as described above may be at most equal to the expiry time. In other words, the request for allocation of the available resource may be received no later than the starting time. This may, as described above, be of advantage in ensuring that the resource may be efficiently consumed.

[0059] The resource may comprise a quantifiable resource, and the data related, at least in part, to the available resource may comprise a quantity of the resource available.

[0060] The system may be configured to associate a value with the available resource. The value associated with the available resource may be of advantage in ensuring efficient utilization of the resource. In some embodiments, for example, the determination if the request satisfies an allocation condition may be based, at least in part, on the value associated with the available resource. Thus, the associated value may allow filtering of received requests to determine which receiver can utilize the resource most efficiently.

[0061] The system may be configured to associate a minimum value with the available resource. The associated minimum value may, similar to the associated value, allow filtering of the received requests, thereby improving the efficiency of resource utilization.

[0062] The system may be configured to receive the (minimum) value to be associated with the available resource. For example, the sender may send the (minimum) value to be associated with the available resource.

[0063] The system may, alternatively, or additionally, be configured to determine the (minimum) value to be associated with the available resource. The determination of the (minimum) value may be of advantage in allowing the allocation of the available resource more simply and easily as, for example, the sender may not have to determine the (minimum) value.

[0064] The system may be configured to determine the (minimum) value based, at least in part, on the data related, at least in part, to the available resource.

[0065] The system may be configured to determine the (minimum) value based, at least in part, on the starting time and / or the ending time. For example, the (minimum) value may be inversely proportional to a difference between the resource-reception time and the ending time.

[0066] The starting time may comprise a starting date. For example, the (minimum) value may be inversely proportional to a difference between the starting date and a date of a local holiday.

[0067] The system may be configured to determine the (minimum) value based, at least in part, on the starting date.

[0068] The system may be configured to determine the (minimum) value based, at least in part, on the expiry time. For example, the (minimum) value may be directly proportional to the expiry time.

[0069] The system may be configured to adjust the (minimum) value associated with the available resource. The adjustment may be based, at least in part, on the data related, at least in part, to the available resource. The adjustment may be based on any of the starting time, the ending time, and the resource-reception time.

[0070] The system may be configured to store the (minimum) value associated with the available resource. The stored (minimum) value may be of advantage in determining the (minimum) value to be associated with resources that become available in future.

[0071] The system may be configured to store an association between the (minimum) value and the data, or the part thereof, related, at least in part, to the available resource. The association may be stored, for example, as a look-up table. For example, the system may store any, preferably at least two, of the starting time, the ending time, and the resource-reception time, as key(s) and the associated (minimum) value as the value corresponding to the key(s).

[0072] The system may be configured to determine the (minimum) value associated with the available resource based, at least in part, on the (minimum) value(s) associated with previously available resource(s) and the data, or the part(s) thereof, related, at least in part, to the previously available resource(s). For example, the (minimum) value may be at least as large as a minimum of the (minimum) value(s) associated with previously available resource(s).

[0073] The system may be configured to identify previously available resource(s) similar to the available resource. Identification of similar resource(s) previously available may be of advantage in determining the (minimum) value to be associated with the available resource. For example, it may be of advantage that the (minimum) value to be associated with the available resource is similar to the (minimum) value(s) associated with similar resource(s) previously available. By allowing for identification of similar resource(s) previously available, the system may, thus, allow the association of a (minimum) value that may be more reliable.

[0074] Identifying the similar resource(s) previously available may comprise comparing the data, or the part(s) thereof, related, at least in part, to previously available resource(s) with the data, or at least a part thereof, related, at least in part, to the available resource. For example, the comparison may comprise comparing the starting and / or ending and / or resource-reception time(s) of the previously available resource(s) and of the available resource.

[0075] The system may be configured to determine the (minimum) value based, at least in part, on the (minimum) value(s) associated with the similar previously available resource(s).

[0076] The request for allocation of the available resource may comprise a proposed value.

[0077] The assigned rank may be based, at least in part, on the proposed value. For example, the assigned rank may be based, at least in part, on a difference between the proposed value and the minimum value associated with the available resource. In particular, the assigned rank may be directly proportional to the difference between the proposed value and the minimum value.

[0078] The allocation condition may comprise the proposed value being greater than the value associated with the available resource. This may be of advantage in enhancing the efficiency of the allocation process. For example, the available resource may be allocated to the first request with a proposed value greater than the value associated with the available resource.

[0079] The allocation condition may comprise the proposed value being greater than the minimum value associated with the available resource. This may also be of advantage in enhancing the efficiency of the allocation process as requests with proposed values lower than the minimum value may be rejected without a rank being assigned to them.

[0080] The available resource may be allocated based, at least in part, on a request for allocation of the available resource, and wherein the system may be configured to store an allocation value corresponding to the proposed value comprised in the request. In other words, the system may determine the request based, at least in part, on which the available resource is to be allocated. For example, the request may correspond to a request with the highest rank. The system may additionally store the proposed value, that may be referred to as the allocation value, comprised in the said request.

[0081] The system may be configured to store an association between the allocation value and the data, or the part thereof, related, at least in part, to the available resource. The association may be stored, for example, as a look-up table.

[0082] The (minimum) value may be determined based, at least in part, on the allocation value(s) associated with previously available resource(s).

[0083] The (minimum) value may be determined based, at least in part, on the allocation value(s) associated with the similar previously available resource(s). For example, the minimum value may correspond to the least allocation value of similar resource(s) previously available. Further exemplarily, the value may correspond to an average of the allocation value(s) of similar resource(s) previously available.

[0084] The system may be configured to receive sender data.

[0085] The system may be configured to determine sender data based, at least in part, on the sender identifier. For example, the system may be configured to communicate with a sender database. The system may be configured to receive sender data from the sender data from the sender database by sending a request to the sender database, the request comprising the sender identifier.

[0086] The (minimum) value as described above may be determined based, at least in part, on the sender data. For example, the sender database may comprise data related, at least in part, to an efficiency of resource utilization of the sender. The system may receive the data from the sender database and based, at least in part, thereon, determine the (minimum) value. For example, the minimum value may be at least as large as the received data, adjusted for the quantity of resource made available.

[0087] The system may be configured to communicate with a sender data database. The communication between the system and the sender data database may, preferably, be encrypted. This may be of advantage in enhancing the privacy of the sender.

[0088] The system may be configured to receive receiver data.

[0089] The system may be configured to determine receiver data based, at least in part, on the receiver identifier.

[0090] The system may be configured to communicate with a receiver data database. The communication between the system and the receiver data database may, preferably, be encrypted. For example, the system may send a request to the receiver database for the receiver data. The request may comprise the receiver identifier.

[0091] The system may be configured to determine if the request satisfies a permissibility condition. The permissibility condition may be of further advantage in ensuring a more efficient utilization of the resource, if allocated. For example, the permissibility condition may require an efficiency of resource utilization of a receiver to be greater than a pre-defined threshold in order for the available resource to be allocated to them. Further, the receiver database may comprise data related, at least in part, to an efficiency of resource utilization of the receiver. The system may receive the data related, at least in part, to an efficiency of resource utilization of the receiver. Thus, the permissibility condition may allow the available resource to be allocated only to receivers with a defined efficiency of resource utilization.

[0092] Further exemplarily, the permissibility condition may require the receiver identifier to be in a pre-defined group of receiver identifiers, for allocation of the available resource. The pre-defined group of receiver identifiers, or at least data related thereto, may be received from the receiver database.

[0093] The system may be configured to receive data related, at least in part, to the permissibility condition. The data may comprise, for example, the pre-defined threshold and / or the condition greater than, or the pre-defined group of receiver identifiers and / or the condition belongs to, as described above.

[0094] The determination if the request satisfies a permissibility condition may be based, at least in part, on the receiver data.

[0095] The system may be configured to determine if the data related, at least in part, to the available resource satisfies an allowability condition.

[0096] The determination if the data satisfies an allowability condition is based, at least in part, on the sender data.

[0097] The system may be configured to allow receiving the request for allocation of the available resource based, at least in part, on a result of the determination if the data related, at least in part, to the available resource satisfies an allowability condition. For example, the system may not allow receiving the request for allocation of the available resource if the data related, at least in part, to the available resource does not satisfy the allowability condition.Further exemplarily, the system may only allow receiving requests for allocation of an available resource associated with a sender identifier that belongs in a pre-defined group of sender identifiers.

[0098] The system may be configured to receive data related, at least in part, to the allowability condition.

[0099] The system may comprise a user interface component.

[0100] The communication component may be configured to communicate with the user interface component.

[0101] Any of the allocation condition, the permissibility condition, and the allowability condition may comprise a rule, and the data processing component may be configured to receive the rule.

[0102] The user interface component may be used to provide the rule. For example, the user interface component may comprise a web / smartphone application that may be used to provide the rule to the system.

[0103] Determining if any of the allocation condition, the permissibility condition, and the allowability condition are satisfied may be based, at least in part, on an artificial intelligencebased model.

[0104] The system may be configured to determine the (minimum) value associated with the available resource based, at least in part, on an artificial intelligence-based model.

[0105] The artificial intelligence-based model may comprise a supervised learning-based model.

[0106] An output of the artificial intelligence-based model may comprise the (minimum) value to be associated with the available resource.

[0107] An input to the supervised learning-based model may comprise the starting date.

[0108] An input to the supervised learning-based model may comprise the sender data, or at least a part thereof.

[0109] The system may be configured to train the supervised learning-based model by means of training data.

[0110] The training data may comprise the (minimum) value associated with previously allocated resources.

[0111] The training data may comprise the starting date and / or the sender data, or at least a part thereof, of previously allocated resources.

[0112] According to a second aspect, the present invention relates to a resource database configured to communicate with a system.

[0113] The system may comprise a system as described above.

[0114] The resource database may be configured to store data related, at least in part, to a sender identifier.

[0115] The resource database may be configured to store data related, at least in part, to an available resource.

[0116] The resource database may be configured to store data related, at least in part, to an association between the sender identifier and an available resource.

[0117] The resource database may be configured to store data related, at least in part, to a receiver identifier.

[0118] The resource database may be configured to receive a request from the system for allocation of an available resource.

[0119] The resource database may be configured, in response to receiving the request, to delete the data related, at least in part, to the association between the sender identifier and the available resource.

[0120] The resource database may be configured, in response to receiving the request, to store data related, at least in part, to an association between the receiver identifier and the available resource.

[0121] According to a third aspect, the present invention relates to a method comprising receiving a request for allocation of an available resource.

[0122] The method may comprise assigning a rank to the received request.

[0123] The method may comprise receiving a plurality of requests for allocation of the available resource.

[0124] The method may comprise assigning a rank to each of the plurality of received requests.

[0125] The method may comprise storing the request.

[0126] The method may comprise assigning the rank based, at least in part, on a request stored previously.

[0127] The method may comprise, in absence of a request stored previously, assigning the rank based, at least in part, on a random value.

[0128] The method may comprise storing the request in a memory component.

[0129] The method may comprise using a data processing component.

[0130] The method may comprise the data processing component assigning the rank to the received request.

[0131] The method may comprise the data processing component retrieving the previously stored request.

[0132] The method may comprise using a communication component.

[0133] The method may comprise the communication component communicating with the data processing component.

[0134] The method may comprise the communication component communicating with the memory component.

[0135] The method may comprise receiving data related, at least in part, to the available resource.

[0136] The method may comprise storing the data, or at least a part thereof, related, at least in part, to the available resource.

[0137] The method may comprise allowing receiving the request for allocation of the available resource after receiving the data related, at least in part, to the available resource.

[0138] The method may comprise allowing receiving the request for allocation of the available resource within a defined time interval after receiving the data related, at least in part, to the available resource.

[0139] The method may comprise, in response to receiving the request for allocation of the available resource after the defined time interval has elapsed, disallowing the request.

[0140] The method may comprise receiving data related, at least in part, to the defined time interval.

[0141] The request may be associated with a receiver.

[0142] The receiver may be associated with a unique receiver identifier.

[0143] The method may comprise determining if the request satisfies an allocation condition.

[0144] The method may comprise assigning the rank based, at least in part, on a result of the determination if the request satisfies an allocation condition.

[0145] The method may comprise allocating the available resource based, at least in part, on a result of the determination if the request satisfies an allocation condition.

[0146] The method may comprise allocating the available resource based, at least in part, on the assigned rank.

[0147] The method may comprise allocating the available resource to the receiver associated with a request.

[0148] The method may comprise determining the request with the highest rank.

[0149] The method may comprise allocating the available resource to the receiver associated with the request with the highest rank.

[0150] The available resource may be associated with a sender.

[0151] The sender may be associated with a unique sender identifier.

[0152] The method may comprise receiving the data related, at least in part, to the available resource from the sender.

[0153] The method may comprise receiving data related, at least in part, to the allocation condition.

[0154] The method may comprise receiving the data related, at least in part, to the allocation condition from the sender.

[0155] The method may comprise communicating with a resource database.

[0156] The resource database may comprise data related, at least in part, to the sender identifier.

[0157] The resource database may comprise data related, at least in part, to the association between the sender identifier and the available resource.

[0158] The resource database may comprise data related, at least in part, to the receiver identifier.

[0159] The method may comprise, in order to allocate the available resource, sending a request to the resource database to associate the available resource with the receiver identifier associated with the request for allocation of the available resource.

[0160] The method may comprise, in response to sending the request to the resource database, receiving a notification relating to a result of processing of the request by the resource database.

[0161] The data related, at least in part, to the available resource may comprise a starting time corresponding to a first time that the resource is available.

[0162] The data related, at least in part, to the available resource may comprise an ending time corresponding to a last time that the resource is available.

[0163] The starting time and / or the ending time may correspond to a day.

[0164] The method may comprise determining a time at which the data related, at least in part, to the available resource is received.

[0165] The method may comprise determining an expiry time corresponding to a time interval between the starting time and the time at which the data related, at least in part, to the available resource is received.

[0166] The expiry time may correspond to a number of days between the day on which the data related, at least in part, to the available resource is received and the day corresponding to the starting time.

[0167] The defined time interval may be at most equal to the expiry time.

[0168] The method may comprise associating a value with the available resource.

[0169] The method may comprise associating a minimum value with the available resource.

[0170] The method may comprise receiving the (minimum) value to be associated with the available resource.

[0171] The method may comprise determining the (minimum) value to be associated with the available resource.

[0172] The method may comprise determining the (minimum) value based, at least in part, on the data related, at least in part, to the available resource.

[0173] The method may comprise determining the (minimum) value based, at least in part, on the starting time.

[0174] The starting time may comprise a starting date.

[0175] The method may comprise determining the (minimum) value based, at least in part, on the starting date.

[0176] The method may comprise determining the (minimum) value based, at least in part, on the expiry time.

[0177] The method may comprise storing the (minimum) value associated with the available resource.

[0178] The method may comprise storing an association between the (minimum) value and the data, or the part thereof, related, at least in part, to the available resource.

[0179] The method may comprise determining the (minimum) value associated with the available resource based, at least in part, on the (minimum) value(s) associated with previously available resource(s) and the data, or the part(s) thereof, related, at least in part, to the previously available resource(s).

[0180] The method may comprise identifying previously available resource(s) similar to the available resource.

[0181] Identifying the similar resource(s) previously available may comprise comparing the data, or the part(s) thereof, related, at least in part, to previously available resource(s) with the data, or at least a part thereof, related, at least in part, to the available resource.

[0182] The method may comprise determining the (minimum) value based, at least in part, on the (minimum) value(s) associated with the similar previously available resource(s).

[0183] The request for allocation of the available resource may comprise a proposed value.

[0184] The assigned rank may be based, at least in part, on the proposed value.

[0185] The allocation condition may comprise the proposed value being greater than the value associated with the available resource.

[0186] The allocation condition may comprise the proposed value being greater than the minimum value associated with the available resource.

[0187] The available resource may be allocated based, at least in part, on a request for allocation of the available resource, and the method may comprise storing an allocation value corresponding to the proposed value comprised in the request.

[0188] The method may comprise storing an association between the allocation value and the data, or the part thereof, related, at least in part, to the available resource.

[0189] The (minimum) value may be determined based, at least in part, on the allocation value(s) associated with previously available resource(s).

[0190] The (minimum) value may be determined based, at least in part, on the allocation value(s) associated with the similar previously available resource(s).

[0191] The method may comprise receiving sender data.

[0192] The method may comprise determining sender data based, at least in part, on the sender identifier.

[0193] The (minimum) value may be determined based, at least in part, on the sender data.

[0194] The method may comprise communicating with a sender data database.

[0195] The method may comprise receiving receiver data.

[0196] The method may comprise determining receiver data based, at least in part, on the receiver identifier.

[0197] The method may comprise communicating with a receiver data database.

[0198] The method may comprise determining if the request satisfies a permissibility condition.

[0199] The method may comprise receiving data related, at least in part, to the permissibility condition.

[0200] The determination if the request satisfies a permissibility condition may be based, at least in part, on the receiver data.

[0201] The method may comprise determining if the data related, at least in part, to the available resource satisfies an allowability condition.

[0202] The determination if the data satisfies an allowability condition may be based, at least in part, on the sender data.

[0203] The method may comprise allowing receiving the request for allocation of the available resource based, at least in part, on a result of the determination if the data related, at least in part, to the available resource satisfies an allowability condition.

[0204] The method may comprise receiving data related, at least in part, to the allowability condition.

[0205] The method may comprise using a user interface component.

[0206] The method may comprise the communication component communicating with the user interface component.

[0207] Any of the allocation condition, the permissibility condition, and the allowability condition may comprise a rule, and the method may comprise the data processing component receiving the rule.

[0208] The user interface component may be used to provide the rule.

[0209] Determining if any of the allocation condition, the permissibility condition, and the allowability condition are satisfied may be based, at least in part, on an artificial intelligencebased model.

[0210] The method may comprise determining the (minimum) value associated with the available resource based, at least in part, on an artificial intelligence-based model.

[0211] The artificial intelligence-based model may comprise a supervised learning-based model.

[0212] An output of the artificial intelligence-based model may comprise the (minimum) value to be associated with the available resource.

[0213] An input to the supervised learning-based model may comprise the starting date.

[0214] An input to the supervised learning-based model may comprise the sender data, or at least a part thereof.

[0215] The method may comprise training the supervised learning-based model by means of training data.

[0216] The training data may comprise the (minimum) value associated with previously allocated resources.

[0217] The training data may comprise the starting date and / or the sender data, or at least a part thereof, of previously allocated resources.

[0218] The system as described above may be configured to perform the method as described above.

[0219] According to a fourth aspect, the present invention relates to a computer program product comprising instructions, when run on a system as described above, to perform the method as described above.

[0220] According to a fifth aspect, the present invention relates to a computer program product comprising instructions, when run on a data processing component of a system as described above, particularly a system comprising a data processing component, to perform the method as described above.

[0221] The present invention is also described by the following numbered embodiments.

[0222] Below system embodiments will be discussed. These are abbreviated by the letter “S” followed by a number. Whenever reference is herein made to the system embodiments, the following embodiments are meant.

[0223] S1. A system for managing a resource, wherein the system is configured:

[0224] to receive a request for allocation of an available resource.

[0225] S2. The system according to the preceding embodiment, wherein the system is configured to assign a rank to the received request.

[0226] S3. The system according to any of the preceding system embodiments, wherein the system is configured to receive a plurality of requests for allocation of the available resource.

[0227] S4. The system according to the preceding embodiment and with the features of embodiment S2, wherein the system is configured to assign a rank to each of the plurality of received requests.

[0228] S5. The system according to any of the preceding system embodiments, wherein the system is configured to store the request.

[0229] S6. The system according to the preceding embodiment and with the features of embodiment S2, wherein the system is configured to assign the rank based, at least in part, on a request stored previously.

[0230] S7. The system according to the preceding embodiment, wherein the system is configured, in absence of a request stored previously, to assign the rank based, at least in part, on a random value.

[0231] S8. The system according to any of the 3 preceding embodiments, wherein the system comprises a memory component configured to store the request.

[0232] S9. The system according to any of the preceding system embodiments, wherein the system comprises a data processing component.

[0233] S10. The system according to the preceding embodiment and with the features of embodiment S2, wherein the data processing component is configured to assign the rank to the received request.

[0234] S11. The system according to any of the 2 preceding embodiments and with the features of embodiment S6, wherein the data processing component is configured to retrieve the previously stored request.

[0235] S12. The system according to any of the preceding system embodiments, wherein the system comprises a communication component.

[0236] S13. The system according to the preceding embodiment and with the features of embodiment S9, wherein the communication component is configured to communicate with the data processing component.

[0237] S14. The system according to any of the 2 preceding embodiments and with the features of embodiment S8, wherein the communication component is configured to communicate with the memory component.

[0238] S15. The system according to any of the preceding system embodiments, wherein the system is configured to receive data related, at least in part, to the available resource.

[0239] S16. The system according to the preceding embodiment, wherein the system is configured to store the data, or at least a part thereof, related, at least in part, to the available resource.

[0240] S17. The system according to any of the 2 preceding embodiments, wherein the system is configured to allow receiving the request for allocation of the available resource after receiving the data related, at least in part, to the available resource.

[0241] S18. The system according to the preceding embodiment, wherein the system is configured to allow receiving the request for allocation of the available resource within a defined time interval after receiving the data related, at least in part, to the available resource.

[0242] S19. The system according to the preceding embodiment, wherein the system is configured, in response to receiving the request for allocation of the available resource after the defined time interval has elapsed, to disallow the request.

[0243] S20. The system according to any of the 2 preceding embodiments, wherein the system is configured to receive data related, at least in part, to the defined time interval.

[0244] S21. The system according to any of the preceding system embodiments, wherein the request is associated with a receiver.

[0245] S22. The system according to the preceding embodiment, wherein the receiver is associated with a unique receiver identifier.

[0246] S23. The system according to any of the preceding system embodiments, wherein the system is configured to determine if the request satisfies an allocation condition.

[0247] S24. The system according to the preceding embodiment and with the features of embodiment S2, wherein the system is configured to assign the rank based, at least in part, on a result of the determination if the request satisfies an allocation condition.

[0248] S25. The system according to any of the 2 preceding embodiments, wherein the system is configured to allocate the available resource based, at least in part, on a result of the determination if the request satisfies an allocation condition.

[0249] S26. The system according to any of the preceding system embodiments and with the features of embodiment S2, wherein the system is configured to allocate the available resource based, at least in part, on the assigned rank.

[0250] S27. The system according to any of the preceding system embodiments and with the features of embodiment S21, wherein the system is configured to allocate the available resource to the receiver associated with a request.

[0251] S28. The system according to any of the preceding system embodiments and with the features of embodiment S2, wherein the system is configured to determine the request with the highest rank.

[0252] S29. The system according to the preceding embodiment and with the features of embodiments S26, and S27, wherein the system is configured to allocate the available resource to the receiver associated with the request with the highest rank.

[0253] S30. The system according to any of the preceding system embodiments, wherein the available resource is associated with a sender.

[0254] S31. The system according to the preceding embodiment, wherein the sender is associated with a unique sender identifier.

[0255] S32. The system according to any of the 2 preceding embodiments and with the features of embodiment S15, wherein the system is configured to receive the data related, at least in part, to the available resource from the sender.

[0256] S33. The system according to any of the preceding system embodiments and with the features of embodiment S23, wherein the system is configured to receive data related, at least in part, to the allocation condition.

[0257] S34. The system according to the preceding embodiment and with the features of embodiment S30, wherein the system is configured to receive the data related, at least in part, to the allocation condition from the sender.

[0258] S35. The system according to any of the preceding system embodiments, wherein the system is configured to communicate with a resource database.

[0259] S36. The system according to the preceding embodiment and with the features of embodiment S31, wherein the resource database comprises data related, at least in part, to the sender identifier.

[0260] S37. The system according to any of the 2 preceding embodiments and with the features of embodiment S31 , wherein the resource database comprises data related, at least in part, to the association between the sender identifier and the available resource.

[0261] S38. The system according to any of the 3 preceding embodiments and with the features of embodiment S22, wherein the resource database comprises data related, at least in part, to the receiver identifier.

[0262] S39. The system according to the preceding embodiment and with the features of embodiment S27, wherein the system is configured, in order to allocate the available resource, to send a request to the resource database to associate the available resource with the receiver identifier associated with the request for allocation of the available resource.

[0263] S40. The system according to the preceding embodiment, wherein the system is configured, in response to sending the request to the resource database, to receive a notification relating to a result of processing of the request by the resource database.

[0264] S41. The system according to any of the preceding system embodiments and with the features of embodiment S15, wherein the data related, at least in part, to the available resource comprises a starting time corresponding to a first time that the resource is available.

[0265] S42. The system according to any of the preceding system embodiments and with the features of embodiment S15, wherein the data related, at least in part, to the available resource comprises an ending time corresponding to a last time that the resource is available.

[0266] S43. The system according to any of the 2 preceding embodiments, wherein the starting time and / or the ending time corresponds to a day.

[0267] S44. The system according to any of the preceding system embodiments and with the features of embodiment S15, wherein the system is configured to determine a time at which the data related, at least in part, to the available resource is received.

[0268] S45. The system according to the preceding embodiment and with the features of embodiment S41 , wherein the system is configured to determine an expiry time corresponding to a time interval between the starting time and the time at which the data related, at least in part, to the available resource is received.

[0269] S46. The system according to the preceding embodiment and with the features of embodiment S43, wherein the expiry time corresponds to a number of days between the day on which the data related, at least in part, to the available resource is received and the day corresponding to the starting time.

[0270] S47. The system according to any of the 2 preceding embodiments and with the features of embodiment S18, wherein the defined time interval is at most equal to the expiry time.

[0271] S48. The system according to any of the preceding system embodiments, wherein the system is configured to associate a value with the available resource.

[0272] S49. The system according to any of the preceding system embodiments, wherein the system is configured to associate a minimum value with the available resource.

[0273] S50. The system according to any of the 2 preceding embodiments, wherein the system is configured to receive the (minimum) value to be associated with the available resource.

[0274] S51. The system according to any of the preceding system embodiments and with the features of any of embodiments S48, and S49, but without the features of the preceding embodiment, wherein the system is configured to determine the (minimum) value to be associated with the available resource.

[0275] S52. The system according to the preceding embodiment and with the features of embodiment S15, wherein the system is configured to determine the (minimum) value based, at least in part, on the data related, at least in part, to the available resource.

[0276] S53. The system according to the preceding embodiment and with the features of embodiment S41, wherein the system is configured to determine the (minimum) value based, at least in part, on the starting time.

[0277] S54. The system according to any of the preceding system embodiments and with the features of embodiment S41, wherein the starting time comprises a starting date.

[0278] S55. The system according to the preceding embodiment and with the features of the embodiment S53, wherein the system is configured to determine the (minimum) value based, at least in part, on the starting date.

[0279] S56. The system according to any of the preceding system embodiments and with the features of embodiments S45, and S51 , wherein the system is configured to determine the (minimum) value based, at least in part, on the expiry time.

[0280] S57. The system according to any of the preceding system embodiments and with the features of any of embodiments S48, and S49, wherein the system is configured to store the (minimum) value associated with the available resource.

[0281] S58. The system according to the preceding embodiment and with the features of embodiment S16, wherein the system is configured to store an association between the(minimum) value and the data, or the part thereof, related, at least in part, to the available resource.

[0282] S59. The system according to the preceding embodiment and with the features of embodiment S51, wherein the system is configured to determine the (minimum) value associated with the available resource based, at least in part, on the (minimum) value(s) associated with previously available resource(s) and the data, or the part(s) thereof, related, at least in part, to the previously available resource(s).

[0283] S60. The system according to any of the preceding system embodiments, wherein the system is configured to identify previously available resource(s) similar to the available resource.

[0284] S61. The system according to the preceding embodiment and with the features of embodiment S16, wherein identifying the similar resource(s) previously available comprises comparing the data, or the part(s) thereof, related, at least in part, to previously available resource(s) with the data, or at least a part thereof, related, at least in part, to the available resource.

[0285] S62. The system according to any of the 2 preceding embodiments and with the features of embodiments S51 , and S58, wherein the system is configured to determine the (minimum) value based, at least in part, on the (minimum) value(s) associated with the similar previously available resource(s).

[0286] S63. The system according to any of the preceding system embodiments, wherein the request for allocation of the available resource comprises a proposed value.

[0287] S64. The system according to the preceding embodiment and with the features of embodiment S2, wherein the assigned rank is based, at least in part, on the proposed value.

[0288] S65. The system according to any of the 2 preceding embodiments and with the features of embodiments S23, and S48, wherein the allocation condition comprises the proposed value being greater than the value associated with the available resource.

[0289] S66. The system according to any of the 3 preceding embodiments and with the features of embodiments S23, and S49, wherein the allocation condition comprises the proposed value being greater than the minimum value associated with the available resource.

[0290] S67. The system according to any of the preceding system embodiments and with the features of embodiment S63, wherein the available resource is allocated based, at least in part, on a defined request for allocation of the available resource, and wherein the system is configured to store an allocation value corresponding to the proposed value comprised in the defined request.

[0291] S68. The system according to the preceding embodiment and with the features of embodiment S16, wherein the system is configured to store an association between the allocation value and the data, or the part thereof, related, at least in part, to the available resource.

[0292] S69. The system according to the preceding embodiment and with the features of embodiment S51, wherein the (minimum) value is determined based, at least in part, on the allocation value(s) associated with previously available resource(s).

[0293] S70. The system according to the preceding embodiment and with the features of embodiment S60, wherein the (minimum) value is determined based, at least in part, on the allocation value(s) associated with the similar previously available resource(s).

[0294] S71. The system according to any of the preceding system embodiments and with the features of embodiment S34, wherein the system is configured to receive sender data.

[0295] S72. The system according to any of the preceding system embodiments and with the features of embodiment S34, wherein the system is configured to determine sender data based, at least in part, on the sender identifier.

[0296] S73. The system according to any of the 2 preceding embodiments and with the features of embodiment S51, wherein the (minimum) value is determined based, at least in part, on the sender data.

[0297] S74. The system according to any of the 3 preceding embodiments, wherein the system is configured to communicate with a sender data database.

[0298] S75. The system according to any of the preceding system embodiments and with the features of embodiment S22, wherein the system is configured to receive receiver data.

[0299] S76. The system according to any of the preceding system embodiments and with the features of embodiment S22, wherein the system is configured to determine receiver data based, at least in part, on the receiver identifier.

[0300] S77. The system according to any of the 2 preceding embodiments, wherein the system is configured to communicate with a receiver data database.

[0301] S78. The system according to any of the preceding system embodiments, wherein the system is configured to determine if the request satisfies a permissibility condition.

[0302] S79. The system according to the preceding embodiment, wherein the system is configured to receive data related, at least in part, to the permissibility condition.

[0303] S80. The system according to any of the 2 preceding embodiments and with the features of any of embodiments S75, and S76, wherein the determination if the request satisfies a permissibility condition is based, at least in part, on the receiver data.

[0304] S81. The system according to any of the preceding system embodiments and with the features of embodiment S15, wherein the system is configured to determine if the data related, at least in part, to the available resource satisfies an allowability condition.

[0305] S82. The system according to the preceding embodiment and with the features of any of embodiments S71, and S72, wherein the determination if the data satisfies an allowability condition is based, at least in part, on the sender data.

[0306] S83. The system according to any of the 2 preceding embodiments, wherein the system is configured to allow receiving the request for allocation of the available resource based, at least in part, on a result of the determination if the data related, at least in part, to the available resource satisfies an allowability condition.

[0307] S84. The system according to any of the 3 preceding embodiments, wherein the system is configured to receive data related, at least in part, to the allowability condition.

[0308] S85. The system according to any of the preceding system embodiments, wherein the system comprises a user interface component.

[0309] S86. The system according to the preceding embodiment and with the features of embodiment S12, wherein the communication component is configured to communicate with the user interface component.

[0310] S87. The system according to any of the preceding system embodiments and with the features of embodiment S9, and any of embodiments S23, S78, and S83, wherein any of the allocation condition, the permissibility condition, and the allowability condition comprises a rule, and wherein the data processing component is configured to receive the rule.

[0311] S88. The system according to the preceding embodiment and with the features of embodiment S85, wherein the user interface component is used to provide the rule.

[0312] S89. The system according to any of the preceding system embodiments and with the features of embodiment S9, and any of embodiments S23, S78, and S83, wherein determining if any of the allocation condition, the permissibility condition, and the allowability condition are satisfied is based, at least in part, on an artificial intelligence-based model.

[0313] S90. The system according to any of the preceding system embodiments and with the features of embodiment S51, wherein the system is configured to determine the (minimum)value associated with the available resource based, at least in part, on an artificial intelligencebased model.

[0314] S91. The system according to the preceding embodiment, wherein the artificial intelligence- based model comprises a supervised learning-based model.

[0315] S92. The system according to any of the 2 preceding embodiments, wherein an output of the artificial intelligence-based model comprises the (minimum) value to be associated with the available resource.

[0316] S93. The system according to any of the preceding system embodiments and with the features of embodiments S55, and S91 , wherein an input to the supervised learning-based model comprises the starting date.

[0317] S94. The system according to any of the preceding system embodiments and with the features of embodiments S73, and S91 , wherein an input to the supervised learning-based model comprises the sender data, or at least a part thereof.

[0318] S95. The system according to any of the preceding system embodiments and with the features of embodiment S91, wherein the system is configured to train the supervised learning-based model by means of training data.

[0319] S96. The system according to the preceding embodiment and with the features of embodiment S57, wherein the training data comprises the (minimum) value associated with a previously available resource.

[0320] S97. The system according to any of the 2 preceding embodiments and with the features of any of embodiments S55, and S73, wherein the training data comprises the starting date and / or the sender data, or at least a part thereof, of previously allocated resources.

[0321] Below database embodiments will be discussed. These are abbreviated by the letter “D” followed by a number. Whenever reference is herein made to the database embodiments, the following embodiments are meant.

[0322] D1. A resource database for managing a resource, wherein the resource database is configured to communicate with a system.

[0323] D2. The resource database according to the preceding embodiment, wherein the system comprises a system according to any of the preceding system embodiments.

[0324] D3. The resource database according to any of the preceding database embodiments, wherein the resource database is configured to store data related, at least in part, to a sender identifier.

[0325] D4. The resource database according to any of the preceding database embodiments, wherein the resource database is configured to store data related, at least in part, to an available resource.

[0326] D5. The resource database according to any of the preceding database embodiments and with the features of embodiment D3, wherein the resource database is configured to store data related, at least in part, to an association between the sender identifier and an available resource.

[0327] D6. The resource database according to any of the preceding database embodiments, wherein the resource database is configured to store data related, at least in part, to a receiver identifier.

[0328] D7. The resource database according to any of the preceding database embodiments, wherein the resource database is configured to receive a request from the system for allocation of an available resource.

[0329] D8. The resource database according to the preceding embodiment and with the features of embodiment D5, wherein the resource database is configured, in response to receiving the request, to delete the data related, at least in part, to the association between the sender identifier and the available resource.

[0330] D9. The resource database according to any of the 2 preceding embodiments and with the features of embodiments D5, and D6, wherein the resource database is configured, in response to receiving the request, to store data related, at least in part, to an association between the receiver identifier and the available resource.

[0331] S98. The system according to any of the preceding system embodiments and with the features of embodiment S23, wherein the resource database comprises a resource database according to any of the preceding database embodiments.

[0332] Below method embodiments will be discussed. These are abbreviated by the letter “M” followed by a number. Whenever reference is herein made to the method embodiments, the following embodiments are meant.

[0333] M1. A method for managing a resource, wherein the method comprises:

[0334] receiving a request for allocation of an available resource.

[0335] M2. The method according to the preceding embodiment, wherein the method comprises assigning a rank to the received request.

[0336] M3. The method according to any of the preceding method embodiments, wherein the method comprises receiving a plurality of requests for allocation of the available resource.

[0337] M4. The method according to the preceding embodiment and with the features of embodiment M2, wherein the method comprises assigning a rank to each of the plurality of received requests.

[0338] M5. The method according to any of the preceding method embodiments, wherein the method comprises storing the request.

[0339] M6. The method according to the preceding embodiment and with the features of embodiment M2, wherein the method comprises assigning the rank based, at least in part, on a request stored previously.

[0340] M7. The method according to the preceding embodiment, wherein the method comprises, in absence of a request stored previously, assigning the rank based, at least in part, on a random value.

[0341] M8. The method according to any of the 3 preceding embodiments, wherein the method comprises storing the request in a memory component.

[0342] M9. The method according to any of the preceding method embodiments, wherein the method comprises using a data processing component.

[0343] M10. The method according to the preceding embodiment and with the features of embodiment M2, wherein the method comprises the data processing component assigning the rank to the received request.

[0344] M11. The method according to any of the 2 preceding embodiments and with the features of embodiment M6, wherein the method comprises the data processing component retrieving the previously stored request.

[0345] M12. The method according to any of the preceding method embodiments, wherein the method comprises using a communication component.

[0346] M13. The method according to the preceding embodiment and with the features of embodiment M9, wherein the method comprises the communication component communicating with the data processing component.

[0347] M14. The method according to any of the 2 preceding embodiments and with the features of embodiment M8, wherein the method comprises the communication component communicating with the memory component.

[0348] M15. The method according to any of the preceding method embodiments, wherein the method comprises receiving data related, at least in part, to the available resource.

[0349] M16. The method according to the preceding embodiment, wherein the method comprises storing the data, or at least a part thereof, related, at least in part, to the available resource.

[0350] M17. The method according to any of the 2 preceding embodiments, wherein the method comprises receiving the request for allocation of the available resource after receiving the data related, at least in part, to the available resource.

[0351] M18. The method according to the preceding embodiment, wherein the method comprises allowing receiving the request for allocation of the available resource within a defined time interval after receiving the data related, at least in part, to the available resource.

[0352] M19. The method according to the preceding embodiment, wherein the method comprises, in response to receiving the request for allocation of the available resource after the defined time interval has elapsed, disallowing the request.

[0353] M20. The method according to any of the 2 preceding embodiments, wherein the method comprises receiving data related, at least in part, to the defined time interval.

[0354] M21. The method according to any of the preceding method embodiments, wherein the request is associated with a receiver.

[0355] M22. The method according to the preceding embodiment, wherein the receiver is associated with a unique receiver identifier.

[0356] M23. The method according to any of the preceding method embodiments, wherein the method comprises determining if the request satisfies an allocation condition.

[0357] M24. The method according to the preceding embodiment and with the features of embodiment M2, wherein the method comprises assigning the rank based, at least in part, on a result of the determination if the request satisfies an allocation condition.

[0358] M25. The method according to any of the 2 preceding embodiments, wherein the method comprises allocating the available resource based, at least in part, on a result of the determination if the request satisfies an allocation condition.

[0359] M26. The method according to any of the preceding method embodiments and with the features of embodiment M2, wherein the method comprises allocating the available resource based, at least in part, on the assigned rank.

[0360] M27. The method according to any of the preceding method embodiments and with the features of embodiment M21, wherein the method comprises allocating the available resource to the receiver associated with a request.

[0361] M28. The method according to any of the preceding method embodiments and with the features of embodiment M2, wherein the method comprises determining the request with the highest rank.

[0362] M29. The method according to the preceding embodiment and with the features of embodiments M26, and M27, wherein the method comprises allocating the available resource to the receiver associated with the request with the highest rank.

[0363] M30. The method according to any of the preceding method embodiments, wherein the available resource is associated with a sender.

[0364] M31. The method according to the preceding embodiment, wherein the sender is associated with a unique sender identifier.

[0365] M32. The method according to any of the 2 preceding embodiments and with the features of embodiment M15, wherein the method comprises receiving the data related, at least in part, to the available resource from the sender.

[0366] M33. The method according to any of the preceding method embodiments and with the features of embodiment M23, wherein the method comprises receiving data related, at least in part, to the allocation condition.

[0367] M34. The method according to the preceding embodiment and with the features of embodiment M30, wherein the method comprises receiving the data related, at least in part, to the allocation condition from the sender.

[0368] M35. The method according to any of the preceding method embodiments, wherein the method comprises communicating with a resource database.

[0369] M36. The method according to the preceding embodiment and with the features of embodiment M31, wherein the resource database comprises data related, at least in part, to the sender identifier.

[0370] M37. The method according to any of the 2 preceding embodiments and with the features of embodiment M31 , wherein the resource database comprises data related, at least in part, to the association between the sender identifier and the available resource.

[0371] M38. The method according to any of the 3 preceding embodiments and with the features of embodiment M22, wherein the resource database comprises data related, at least in part, to the receiver identifier.

[0372] M39. The method according to the preceding embodiment and with the features of embodiment M27, wherein the method comprises, in order to allocate the available resource,sending a request to the resource database to associate the available resource with the receiver identifier associated with the request for allocation of the available resource.

[0373] M40. The method according to the preceding embodiment, wherein the method comprises, in response to sending the request to the resource database, receiving a notification relating to a result of processing of the request by the resource database.

[0374] M41. The method according to any of the preceding method embodiments and with the features of embodiment M15, wherein the data related, at least in part, to the available resource comprises a starting time corresponding to a first time that the resource is available.

[0375] M42. The method according to any of the preceding method embodiments and with the features of embodiment M15, wherein the data related, at least in part, to the available resource comprises an ending time corresponding to a last time that the resource is available.

[0376] M43. The method according to any of the 2 preceding embodiments, wherein the starting time and / or the ending time corresponds to a day.

[0377] M44. The method according to any of the preceding method embodiments and with the features of embodiment M15, wherein the method comprises determining a time at which the data related, at least in part, to the available resource is received.

[0378] M45. The method according to the preceding embodiment and with the features of embodiment M41, wherein the method comprises determining an expiry time corresponding to a time interval between the starting time and the time at which the data related, at least in part, to the available resource is received.

[0379] M46. The method according to the preceding embodiment and with the features of embodiment M43, wherein the expiry time corresponds to a number of days between the day on which the data related, at least in part, to the available resource is received and the day corresponding to the starting time.

[0380] M47. The method according to any of the 2 preceding embodiments and with the features of embodiment M18, wherein the defined time interval is at most equal to the expiry time.

[0381] M48. The method according to any of the preceding method embodiments, wherein the method comprises associating a value with the available resource.

[0382] M49. The method according to any of the preceding method embodiments, wherein the method comprises associating a minimum value with the available resource.

[0383] M50. The method according to any of the 2 preceding embodiments, wherein the method comprises receiving the (minimum) value to be associated with the available resource.

[0384] M51. The method according to any of the preceding method embodiments and with the features of any of embodiments M48, and M49, but without the features of the preceding embodiment, wherein the method comprises determining the (minimum) value to be associated with the available resource.

[0385] M52. The method according to the preceding embodiment and with the features of embodiment M15, wherein the method comprises determining the (minimum) value based, at least in part, on the data related, at least in part, to the available resource.

[0386] M53. The method according to the preceding embodiment and with the features of embodiment M41, wherein the method comprises determining the (minimum) value based, at least in part, on the starting time.

[0387] M54. The method according to any of the preceding method embodiments and with the features of embodiment M41, wherein the starting time comprises a starting date.

[0388] M55. The method according to the preceding embodiment and with the features of the embodiment M53, wherein the method comprises determining the (minimum) value based, at least in part, on the starting date.

[0389] M56. The method according to any of the preceding method embodiments and with the features of embodiments M45, and M51, wherein the method comprises determining the (minimum) value based, at least in part, on the expiry time.

[0390] M57. The method according to any of the preceding method embodiments and with the features of any of embodiments M48, and M49, wherein the method comprises storing the (minimum) value associated with the available resource.

[0391] M58. The method according to the preceding embodiment and with the features of embodiment M16, wherein the method comprises storing an association between the (minimum) value and the data, or the part thereof, related, at least in part, to the available resource.

[0392] M59. The method according to the preceding embodiment and with the features of embodiment M51, wherein the method comprises determining the (minimum) value associated with the available resource based, at least in part, on the (minimum) value(s) associated with previously available resource(s) and the data, or the part(s) thereof, related, at least in part, to the previously available resource(s).

[0393] M60. The method according to any of the preceding method embodiments, wherein the method comprises identifying previously available resource(s) similar to the available resource.

[0394] M61. The method according to the preceding embodiment and with the features of embodiment M16, wherein identifying the similar resource(s) previously available comprises comparing the data, or the part(s) thereof, related, at least in part, to previously available

[0395] resource(s) with the data, or at least a part thereof, related, at least in part, to the available resource.

[0396] M62. The method according to any of the 2 preceding embodiments and with the features of embodiments M51, and M58, wherein the method comprises determining the (minimum) value based, at least in part, on the (minimum) value(s) associated with the similar previously available resource(s).

[0397] M63. The method according to any of the preceding method embodiments, wherein the request for allocation of the available resource comprises a proposed value.

[0398] M64. The method according to the preceding embodiment and with the features of embodiment M2, wherein the assigned rank is based, at least in part, on the proposed value.

[0399] M65. The method according to any of the 2 preceding embodiments and with the features of embodiments M23, and M48, wherein the allocation condition comprises the proposed value being greater than the value associated with the available resource.

[0400] M66. The method according to any of the 3 preceding embodiments and with the features of embodiments M23, and M49, wherein the allocation condition comprises the proposed value being greater than the minimum value associated with the available resource.

[0401] M67. The method according to any of the preceding method embodiments and with the features of embodiment M63, wherein the available resource is allocated based, at least in part, on a defined request for allocation of the available resource, and wherein the method comprises storing an allocation value corresponding to the proposed value comprised in the defined request.

[0402] M68. The method according to the preceding embodiment and with the features of embodiment M16, wherein the method comprises storing an association between the allocation value and the data, or the part thereof, related, at least in part, to the available resource.

[0403] M69. The method according to the preceding embodiment and with the features of embodiment M51, wherein the (minimum) value is determined based, at least in part, on the allocation value(s) associated with previously available resource(s).

[0404] M70. The method according to the preceding embodiment and with the features of embodiment M60, wherein the (minimum) value is determined based, at least in part, on the allocation value(s) associated with the similar previously available resource(s).

[0405] M71. The method according to any of the preceding method embodiments and with the features of embodiment M34, wherein the method comprises receiving sender data.

[0406] M72. The method according to any of the preceding method embodiments and with the features of embodiment M34, wherein the method comprises determining sender data based, at least in part, on the sender identifier.

[0407] M73. The method according to any of the 2 preceding embodiments and with the features of embodiment M51, wherein the (minimum) value is determined based, at least in part, on the sender data.

[0408] M74. The method according to any of the 3 preceding embodiments, wherein the method comprises communicating with a sender data database.

[0409] M75. The method according to any of the preceding method embodiments and with the features of embodiment M22, wherein the method comprises receiving receiver data.

[0410] M76. The method according to any of the preceding method embodiments and with the features of embodiment M22, wherein the method comprises determining receiver data based, at least in part, on the receiver identifier.

[0411] M77. The method according to any of the 2 preceding embodiments, wherein the method comprises communicating with a receiver data database.

[0412] M78. The method according to any of the preceding method embodiments, wherein the method comprises determining if the request satisfies a permissibility condition.

[0413] M79. The method according to the preceding embodiment, wherein the method comprises receiving data related, at least in part, to the permissibility condition.

[0414] M80. The method according to any of the 2 preceding embodiments and with the features of any of embodiments M75, and M76, wherein the determination if the request satisfies a permissibility condition is based, at least in part, on the receiver data.

[0415] M81. The method according to any of the preceding method embodiments and with the features of embodiment M15, wherein the method comprises determining if the data related, at least in part, to the available resource satisfies an allowability condition.

[0416] M82. The method according to the preceding embodiment and with the features of any of embodiments M71, and M72, wherein the determination if the data satisfies an allowability condition is based, at least in part, on the sender data.

[0417] M83. The method according to any of the 2 preceding embodiments, wherein the method comprises allowing receiving the request for allocation of the available resource based, at least in part, on a result of the determination if the data related, at least in part, to the available resource satisfies an allowability condition.

[0418] M84. The method according to any of the 3 preceding embodiments, wherein the method comprises receiving data related, at least in part, to the allowability condition.

[0419] M85. The method according to any of the preceding method embodiments, wherein the method comprises using a user interface component.

[0420] M86. The method according to the preceding embodiment and with the features of embodiment M12, wherein the method comprises the communication component communicating with the user interface component.

[0421] M87. The method according to any of the preceding method embodiments and with the features of embodiment M9, and any of embodiments M23, M78, and M83, wherein any of the allocation condition, the permissibility condition, and the allowability condition comprises a rule, and wherein the method comprises the data processing component receiving the rule.

[0422] M88. The method according to the preceding embodiment and with the features of embodiment M85, wherein the user interface component is used to provide the rule.

[0423] M89. The method according to any of the preceding method embodiments and with the features of embodiment M9, and any of embodiments M23, M78, and M83, wherein determining if any of the allocation condition, the permissibility condition, and the allowability condition are satisfied is based, at least in part, on an artificial intelligence-based model.

[0424] M90. The method according to any of the preceding method embodiments and with the features of embodiment M51, wherein the method comprises determining the (minimum) value associated with the available resource based, at least in part, on an artificial intelligencebased model.

[0425] M91. The method according to the preceding embodiment, wherein the artificial intelligence- based model comprises a supervised learning-based model.

[0426] M92. The method according to any of the 2 preceding embodiments, wherein an output of the artificial intelligence-based model comprises the (minimum) value to be associated with the available resource.

[0427] M93. The method according to any of the preceding method embodiments and with the features of embodiments M55, and M91, wherein an input to the supervised learning-based model comprises the starting date.

[0428] M94. The method according to any of the preceding method embodiments and with the features of embodiments M73, and M91, wherein an input to the supervised learning-based model comprises the sender data, or at least a part thereof.

[0429] M95. The method according to any of the preceding method embodiments and with the features of embodiment M91, wherein the method comprises training the supervised learning- based model by means of training data.

[0430] M96. The method according to the preceding embodiment and with the features of embodiment M57, wherein the training data comprises the (minimum) value associated with a previously available resource.

[0431] M97. The method according to any of the 2 preceding embodiments and with the features of any of embodiments M55, and M73, wherein the training data comprises the starting date and / or the sender data, or at least a part thereof, of previously allocated resources.

[0432] S99. The system according to any of the preceding system embodiments, wherein the system is configured to perform the method according to any of the preceding method embodiments.

[0433] Below computer program product embodiments will be discussed. These are abbreviated by the letter “P” followed by a number. Whenever reference is herein made to computer program product embodiments, the following embodiments are meant.

[0434] P1. A computer program product comprising instructions, when run on a system according to any of the preceding system embodiments, to perform the method according to any of the preceding method embodiments.

[0435] P2. A computer program product comprising instructions, when run on a data processing component of a system according to any of the preceding system embodiments and with the features of embodiment S5, to perform the method according to any of the preceding method embodiments.

[0436] Figure 1 depicts an embodiment of a system 1 according to the present invention. The system 1 may comprise a data processing component 101 configured to communicate with a communication component 103. The communication component 103 may be further configured to communicate with a user interface component 105. The communication component may further communicate with a memory component 107. Communication may, herein, be understood to comprise exchange of data between any two components of the system 1.

[0437] Generally, as depicted in Figure 1, the communication may always be mediated via the communication component 103. However, in some embodiments, the data processing component 101 may communicate with the user interface component 105 and / or the memory component 107 directly, i.e., without communication with the communication component 103 as an intermediary.

[0438] The system 1, particularly the user interface component 105 thereof, may be configured to receive data from a user 3. For example, the user interface component 105 may comprise means for allowing inputs from the user 3 such as a keyboard, a mouse, a joystick, a touchscreen, or any other suitable means for input.

[0439] The user interface component 105 may be configured to also send data to the user 3. For example, the user interface component 105 may comprise a display that may be of advantage for displaying information to the user 3.

[0440] It may be understood that the components of the system 1 may or may not be colocated, i.e., located in close proximity with one another such as being comprised in the same device. For example, the communication component 103 and the data processing component 101 may be co-located at one location, the user interface component 105 be located at another location, while the memory component 107 be located at yet another location. Further, in some other embodiments, all the four components may be located at different locations.

[0441] Thus, communication between any of the components may be wired or wireless. Wireless communication may be mediated by any suitable technologies such as Bluetooth, WiFi, or other means.

[0442] The system 1 may be particularly advantageous for management of a resource. In particular, the system 1, particularly the communication component 103 thereof, may be configured to communicate with a resource database 2. Further details of the resource database 2 are described below in context of the present invention.

[0443] Figure 2 depicts one embodiment of a method according to the present invention. The method may be of particular relevance for management of a resource as will now be described. Note that, in the following, one embodiment of the method comprising a plurality of steps is described. However, it may be understood, that the order of mention of the steps need not correspond to the order in which the steps have to be carried out according to the present technology. In some embodiments some of the steps may be carried out before the others, even if described in another order herein.

[0444] Note, further, that, whenever reference is herein made to a receiver or a sender, the method may be carried out by means of receiver or sender identifiers respectively, without reference to the receiver or the sender, such that data privacy is improved.

[0445] In a first step, P1, the system 1 may receive data related, at least in part, to an available resource. The data related, at least in part, to the available resource may be received from a sender 31. For example, the data may be received via the user interface component 105.

[0446] The data related, at least in part, to the available resource may comprise a starting time corresponding, at least in part, to a first time that the resource is available. The starting time may comprise any of a day, a month, a year, an hour, and a minute. Preferably, the starting time comprises a day, a month, and a year. In other words, the starting time may preferably comprise a starting date.

[0447] The data related, at least in part, to the available resource may comprise an ending time corresponding, at least in part, to a last time that the resource is available. The ending time may comprise any of a day, a month, a year, an hour, and a minute. Preferably, the ending time comprises a day, a month, and a year. In other words, the ending time may preferably comprise an ending date.

[0448] Thus, generally, it may be understood, that the data related, at least in part, to the available resource may define a period of availability of the resource. For example, the resource may have been made available / allocated to the sender 31, for example, to be used within a specific period of time. The sender 31 may, however, be unable to use the resource within the specific period. It may then be of advantage to allocate the resource to a receiver 33 to allow efficient consumption of the resource. The system 1 may advantageously allow this re-allocation of the resource simply and efficiently as described herein.

[0449] The sender 31 may be associated with a sender identifier. The sender identifier may comprise a string comprising alphanumeric characters.

[0450] The system 1 may be configured to receive the sender identifier. For example, the data related, at least in part, to the available resource may comprise the sender identifier. Alternatively, the system 1 may be configured to require the sender 31 to authenticate themselves, and the sender identifier may be received as part of the authentication process. Generally, it may be understood that, at the end of step P1, the sender identifier is available to the system 1.

[0451] In a step, P2, the system 1 may be configured to receive / determine / retrieve sender data related, at least in part to the sender 31, based, at least in part, on the sender identifier. The sender data may comprise data related to a profession of the sender, a position in and / or adepartment of a company where the sender is employed. For example, the sender identifier may comprise a defined format and the defined format of the sender identifier may be of advantage in determining the sender data.

[0452] Alternatively, or additionally, the system 1 may be configured to determine the sender data based, at least in part, on the sender identifier. For example, the system 1 , particularly the communication component 103 thereof, may communicate with a sender database that may be configured to provide the sender data. For example, the system 1 may send the sender identifier to the sender database, and the sender database may, in response, send the sender data back to the system 1. The sender database may be configured to allow requests for sender data only after an access condition has been satisfied. For example, the access condition may comprise successful authorization of the system 1. Thus, data privacy and security may be enhanced.

[0453] Thus, at the end of step P2, the system 1 may have access to the sender identifier, and preferably, the sender data related, at least in part to the sender 31. The sender data may be of particular advantage in efficiently managing the resource as will be described further below.

[0454] In a step, P3, the system 1 may be configured to receive data related, at least in part, to an allowability condition. The data related to the allowability condition may comprise, for example, any of a sender identifier, sender data, and a maximum number of days.

[0455] In a step P4, the system 1 may be configured to determine if the data related, at least in part, to the available resource satisfies the allowability condition. The determination if the data related, at least in part, to the available resource satisfies the allowability condition may be based, at least in part, on the data related, at least in part, to the allowability condition. The allowability condition may be of advantage in determining if the system 1 may allow a request for allocation of the available resource.

[0456] The determination if the system 1 may allow a request for allocation of the available resource may be based, at least in part, on any of the data related, at least in part, to the available resource, the sender identifier, or the sender data, as described above. In other words, the allowability condition may be used to determine based, at least in part, on any of the data

[0457] related, at least in part, to the available resource, the sender identifier, or the sender data, if a request for allocation of the available resource may be allowed.

[0458] For example, the allowability condition may comprise the maximum number of days and the system 1 may be configured to compare the data related, at least in part, to the available resource with the maximum number of days. If the difference between the ending time and the starting time, as described above, is larger than the maximum number of days,corresponding to the allowability condition not being satisfied, the system 1 may be configured, for example, to not carry out some subsequent steps of the method as described below. Additionally, or alternatively, the system 1 may generate a notification indicative of the result of the comparison.

[0459] In a further step, P5, the system 1, particularly the memory component 107 thereof, may be configured to store the data related, at least in part, to the available resource, or at least a part thereof. Storing the data may comprise, in particular, storing the starting and / or ending times of the available resource and / or the sender identifier.

[0460] Step P5 may be carried out regardless of the data related, at least in part, to the available resource satisfying the allowability condition. In particular, the system 1 may be further configured to store the result of the determination if the data related, at least in part, to the available resource satisfies the allowability condition. This may be of advantage for analysis of the allowability condition - for example, whether or not the allowability condition should be changed.

[0461] The further steps may only be carried out if the data related, at least in part, to the available resource satisfies the allowability condition. This may be of advantage in improving the efficiency of the management of resources using the system 1.

[0462] In a step, P6, the system 1 may be configured to associate a value with the available resource. The system 1 may be configured to receive the value to be associated with the available resource. Alternatively, the system 1 may be configured to determine the value to be associated with the available resource. Further details of how the value may be determined are described below.

[0463] In a step, P7, the system 1 may be configured to associate a minimum value with the available resource. The system 1 may be configured to receive the minimum value to be associated with the available resource. Alternatively, the system 1 may be configured to determine the minimum value to be associated with the available resource. Further details of how the minimum value may be determined are described below.

[0464] The system 1, particularly the memory component 107 thereof, may be further configured, in a step P8, to store the (minimum) value associated with the available resource. Storing the (minimum) value associated with the available resource may be of advantage in determining the (minimum) value to be associated with a subsequent available resource as described further below.

[0465] In a further step, P9, the system 1 may be configured to receive a request for allocation of the available resource. The request for allocation of the available resource may beassociated with a receiver 33. The receiver 33 may be associated with a receiver identifier and the system 1 may be configured to receive the receiver identifier. The receiver identifier may comprise a string comprising alphanumeric characters. For example, the request may comprise the receiver identifier. Alternatively, the system 1 may be configured to require the receiver 33 to authenticate themselves before being able to send the request for allocation of the available resource, and the receiver identifier may be received as part of the receiver identifier.

[0466] The request for allocation of the available resource may comprise a proposed value.

[0467] In a step, P10, the system 1 may be configured to receive / determine / retrieve receiver data related, at least in part to the receiver 33, based, at least in part, on the receiver identifier. The receiver data may comprise data related to a profession of the receiver, a position in and / or a department of a company where the receiver is employed. For example, the receiver identifier may comprise a defined format and the defined format of the receiver identifier may be of advantage in determining the receiver data.

[0468] Alternatively, or additionally, the system 1 may be configured to determine the receiver data based, at least in part, on the receiver identifier. For example, the system 1, particularly the communication component 103 thereof, may communicate with a receiver database that may be configured to provide the receiver data. For example, the system 1 may send the receiver identifier to the receiver database, and the receiver database may, in response, send the receiver data back to the system 1. The receiver database may be configured to allow requests for receiver data only after an access condition has been satisfied. For example, the access condition may comprise successful authorization of the system 1.Thus, data privacy and security may be enhanced. The receiver database may or may not be identical to the sender database.

[0469] Thus, at the end of step P10, the system 1 may have access to the receiver identifier, and preferably, the receiver data related, at least in part to the receiver 33. The receiver data may be of particular advantage in efficiently managing the resource as will be described further below.

[0470] The system 1 may be configured to receive a plurality of requests for allocation of the available resource. A plurality of the plurality of requests may each be associated with a unique receiver 33. The system 1 may be configured to allocate the available resource to a receiver 33 based, at least in part, on the request associated with the receiver 33. In other words, the system 1

[0471] may be configured to allocate the available resource to one of the plurality of receivers 33 that have sent requests for allocation of the available resource. The determinationof the receiver 33 to whom the available resource is allocated may be carried out by the system 1 as follows.

[0472] In a next step, P11, the system 1 may be configured to determine if the request satisfies a permissibility condition. The permissibility condition may be pre-defined in the system 1. For example, the permissibility condition may be defined as a function that takes input comprising the request, or at least a part thereof, and sends a Boolean output comprising true if the request satisfies the permissibility condition or false if the request does not.

[0473] Alternatively, or additionally, the system 1 may be configured to receive data related, at least in part, to the permissibility condition that may allow the system 1 to determine if the request satisfies the permissibility condition.

[0474] The data related to the permissibility condition may comprise any of a receiver identifier, receiver data, a time period in a year comprising a starting date and an ending date, or other suitable conditions. For example, it may be desirable to not allow requests for allocation of the available resource from a defined set of receivers. The permissibility condition may then comprise the receiver identifiers corresponding to each of the receivers in the defined set of receivers. Or, for example, it may be desirable to not allow requests for allocation of the available resource from a defined set of receivers within a defined time period of the year. The permissibility condition may then comprise the receiver identifiers corresponding to each of the receivers in the defined set of receivers and the time period of the year.

[0475] If the request satisfies the permissibility condition, in a step, P12, the system 1 may determine if the request for allocation of the available resource satisfies an allocation condition. The allocation condition may be pre-defined in the system 1, particularly the data processing component 101 thereof. For example, the allocation condition may be defined as a function that may take input comprising the request for allocation of the available resource, or at least a part thereof, and output a Boolean value indicative of whether or not the request satisfies the allocation condition.

[0476] In some embodiments, the system 1 may receive data related, at least in part, to the allocation condition, as a step, P13. This may allow further customization of the process of managing the resource using the system 1.

[0477] The determination if the request satisfies the allocation condition may be based, at least in part, on the (minimum) value associated with the available resource, as described above. Alternatively, or additionally, the determination if the request satisfies the allocation condition may be based, at least in part, on the proposed value comprised in the request, asdescribed above. For example, the allocation condition may be satisfied if the proposed value is greater than or equal to the (minimum) value associated with the available resource.

[0478] Based, at least in part, on a result of the determination if the request satisfies the allocation condition, the system 1 may store the request, or at least a part thereof, in the memory component 107 based, at least in part, of the determination. In particular, the request, or the part thereof, may be stored if the request is determined to satisfy the allocation condition. Storing the request may comprise storing, in particular, the proposed value comprised in the request, and / or the receiver identifier. This may comprise a step, P14, of the method.

[0479] The memory component 107 may be configured for efficient storage and retrieval of the stored requests. For example, the requests may be stored in the memory component 107 as look-up tables. This may be of advantage in allowing fast access to requests, for example, based on the proposed value or on the receiver identifier.

[0480] The system 1 may be configured to allocate the available resource based, at least in part, on a result of the determination if the request satisfies the allocation condition. In particular, the system 1 may be configured to allocate the available resource to a receiver 33 if the proposed value comprised in the request by the receiver 33 is greater than or equal to the value associated with the available resource. This may comprise a step, P15, of the method.

[0481] Allocation of the available resource may comprise the system 1 sending a request to the remote database 2 to associate the resource with the receiver 33. In particular, the resource database 2 may be configured to store data related, at least in part, to the sender identifier and data related, at least in part, to the available resource. Further, the resource database 2 may be configured to store data related, at least in part, to an association between the sender identifier and the available resource. Further, the resource database 2 may be configured to store data related, at least in part, to the receiver identifier. The resource database 2 may be configured, in response to receiving the request from the system 1, to delete the data related, at least in part, to the association between the sender identifier and the available resource. Further, the resource database 2 may be configured, in response to receiving the request from the system 1 , to store data related, at least in part, to an association between the receiver identifier and the available resource.

[0482] In some embodiments, the system 1 may be configured to assign a rank to the request. This may comprise a step, P16, of the method. The assignment of the rank may be performed based, at least in part, on a result of the determination if the request satisfies the allocation condition. In particular, the rank may be assigned if the proposed value comprised inthe request is greater than or equal to the minimum value associated with the available resource but less than the value associated with the available resource.

[0483] The rank assigned to the request may be based, at least in part, on the rank assigned to other requests for allocation of the available resource. For example, the ranks may be assigned by comparing the proposed values of the requests such that a higher rank may be assigned to a request with a higher proposed value.

[0484] The system 1 may be configured to allocate the available resource based, at least in part, on the rank assigned to the request, in a next step, P17. For example, the available resource may be allocated to the receiver 33 associated with the request of the highest rank.

[0485] The system 1 may be configured to allow receiving requests for allocation of the available resource within a defined time interval after receiving the data related, at least in part, to the available resource. The system 1 may be configured to disallow receiving requests for allocation of the available resource after the defined time interval has elapsed. The system 1 may be configured to receive data related, at least in part, to the defined time interval. The data may comprise, for example, a value for the defined time interval. This may be of advantage in further customization of the method according to the present invention.

[0486] The available resource may be allocated to the receiver associated with the request with the highest rank received within the defined time interval.

[0487] In a step, P18, the system 1 may store an allocation value associated with the available resource or the data related, at least in part, thereto. The allocation value may correspond to the proposed value comprised in the request based, at least in part, on which the available resource is allocated.

[0488] Generally, the system 1, particularly the data processing component 101 thereof, may be configured for analyzing the data, particularly the requests for allocation of a current or previously available resource, the (minimum) value(s) associated with previously available resource(s), the starting and / or ending time(s) of previously available resource(s), and the allocation value(s) of previously available resource(s), stored in the memory component 107.

[0489] For example, the data comprising requests with the same receiver identifier may be indicative of a propensity of the receiver 33 associated with the same receiver identifier to request allocation of available resources. The system 1 may be configured, for example, to determine a measure of the propensity based on the previous requests sent by the receiver 33. This may be of advantage, for example, in improving an efficiency of the allocation of the available resource. For example, the system 1 may be configured to send a notification to the receiver 33 when a resource becomes available. Further exemplarily, the system 1 may beconfigured to send a notification to all the receivers 33 with a propensity larger than a threshold value when a resource becomes available.

[0490] The system 1 may be configured to identify previously available resource(s) similar to the available resource. Identification of similar resource(s) previously available may be based, at least in part, on the data related, at least in part, to the previously available resource(s). For example, the system 1, particularly the data processing component 101 thereof, may be configured to execute a clustering algorithm to determine similar previously available resource(s).

[0491] The system 1 may, additionally, or alternatively, determine a degree of similarity between the available resource and any of the resource(s) previously available. The identification of similar resource(s) previously available may, for example, be based, at least in part, on the degree of similarity between the resource(s) previously available and the available resource.

[0492] The system 1 may be configured to receive holiday data. Holiday data may comprise data relating to public holidays and / or other holidays offered by an organization in a year. The holiday data may be based, at least in part, on a location of any of the data processing component 101, the resource database 2, the receiver database, or the sender database. Identification of similar resource(s) previously available may be based, at least in part, on the holiday data.

[0493] The system 1 may be configured to identify the receiver(s) 33 with a propensity greater than a threshold to request the available resource based, at least in part, on the similar resource(s) previously available. For example, the system 1 may be configured, for each of the similar resource(s) previously available, to determine the propensity of all the receivers 33 for requesting the resource previously available. The propensity for each receiver 33 may be weighted by a degree of similarity between the resource previously available and the available resource. The resulting propensity may then be used to identify the receiver(s) 33 to whom a notification about availability of the available resource, as described above, may be sent.

[0494] The (minimum) value to be associated with the available resource may be based, at least in part, on the (minimum) value(s) associated with the similar resource(s) previously available. For example, the (minimum) value associated with the available resource may be a weighted average of the (minimum) value(s) associated with the similar resource(s) previously available, with a weight corresponding to a level of similarity of the resource previously available being assigned to the (minimum) value associated with the previously available resource.

[0495] The (minimum) value to be associated with the available resource may be based, at least in part, on the allocation value(s) associated with the similar resource(s) previously available.

[0496] Alternatively, or additionally, the system 1 , particularly the data processing component 101 thereof, may be configured for analysis of the data comprising the proposed values. For example, the system 1 may be configured to determine a frequency distribution of the proposed values for the similar resource(s) previously available. The frequency distribution may be used, at least in part, to determine the (minimum) value to be associated with the available resource.

[0497] Overall, embodiments of the system and method as disclosed herein may thus allow management of a resource more simply and efficiently, thereby increasing an efficiency of consumption of the resource.

[0498] Whenever a relative term, such as “about”, “substantially” or “approximately” is used in this specification, such a term should also be construed to also include the exact term. That is, e.g., “substantially straight” should be construed to also include “(exactly) straight”.

[0499] Whenever steps were recited in the above or also in the appended claims, it should be noted that the order in which the steps are recited in this text may be accidental. That is, unless otherwise specified or unless clear to the skilled person, the order in which steps are recited may be accidental. That is, when the present document states, e.g., that a method comprises steps (A) and (B), this does not necessarily mean that step (A) precedes step (B), but it is also possible that step (A) is performed (at least partly) simultaneously with step (B) or that step (B) precedes step (A). Furthermore, when a step (X) is said to precede another step (Z), this does not imply that there is no step between steps (X) and (Z). That is, step (X) preceding step (Z) encompasses the situation that step (X) is performed directly before step (Z), but also the situation that (X) is performed before one or more steps (Y1), ..., followed by step (Z). Corresponding considerations apply when terms like “after” or “before” are used.

[0500] While in the above, preferred embodiments have been described with reference to the accompanying drawings, the skilled person will understand that these embodiments were provided for illustrative purpose only and should by no means be construed to limit the scope of the present invention, which is defined by the claims.

Claims

CLAIMSWhat is claimed is:

1. A system for managing a resource, the system comprising a data processing component, wherein the system is configured: to receive a request for allocation of an available resource, to receive data related, at least in part, to the available resource, and wherein the system is configured to allow receiving the request for allocation of the available resource after receiving the data related, at least in part, to the available resource.

2. The system according to claim 1 , wherein the request is associated with a receiver, and wherein the receiver is associated with a unique receiver identifier.

3. The system according to claim 1 , wherein the system is configured to allocate the available resource to the receiver associated with a request.

4. The system according to claim 1 , wherein the system is configured to determine if the request satisfies an allocation condition, and wherein the system is configured to allocate the available resource based, at least in part, on a result of the determination if the request satisfies an allocation condition.

5. The system according to claim 1 , wherein the available resource is associated with a sender, and wherein the sender is associated with a unique sender identifier.

6. The system according to claim 5, wherein the system is configured to communicate with a resource database, and wherein the resource database comprises data related, at least in part, to the sender identifier.

7. The system according to claim 6, wherein the resource database comprises data related, at least in part, to the association between the sender identifier and the available resource.

8. The system according to claim 6 or 7 and with the features of claim 2, wherein the resource database comprises data related, at least in part, to the receiver identifier.

9. The system according to claim 8, wherein the system is configured to allocate the available resource to the receiver associated with a request, and wherein the system is configured, in order to allocate the available resource, to send a request to the resource database to associate the available resource with the receiver identifier associated with the request for allocation of the available resource.

10. The system according to claim 1, wherein the system is configured to receive data related, at least in part, to the available resource.

11. The system according to claim 1 , wherein the system is configured to identify previously available resource(s) similar to the available resource.

12. The system according to claim 11 and with the features of claim 10, wherein the system is configured to store the data, or at least a part thereof, related, at least in part, to the available resource, and wherein identifying the similar resource(s) previously available comprises comparing the data, or the part(s) thereof, related, at least in part, to previously available resource(s) with the data, or at least a part thereof, related, at least in part, to the available resource.

13. The system according to claim 1 , wherein the system is configured to associate a value and / or a minimum value with the available resource.

14. A method for managing a resource, wherein the method comprises: receiving a request for allocation of an available resource, receiving data related, at least in part, to the available resource, and allowing receiving the request for allocation of the available resource after receiving the data related, at least in part, to the available resource.

15. A computer program product comprising instructions, when run on a data processing component of a system according to any of claims 1 to 7 and 10 to 13, to perform the method according to claim 14.

Images