Technical Field

[0001] Described embodiments relate to methods and systems for booking resources and access management of booked resources. Some embodiments relate to methods and systems for resource management, such as booking resources and providing access to the booked resources. Some embodiments relate to methods and systems for booking resources and accessing the booked resources. Some embodiments relate to methods and systems for managing access to booked resources and collating feedback regarding use of resources.

Background

[0002] Accessing resources and collating feedback regarding use of resources can be a time intensive and arduous process. For example, having booked accommodation in advance, in general patrons of hotels still need to undergo a check-in process at the hotel upon arriving. The check-in process is generally managed by staff at the hotel and may involve verification of identification and provision of key(s) for the booked rooms(s). Hotels may also have systems to manage and track the allocation of rooms and keys to customers checking in and manual processes to gather feedback from patrons. Similar processes are performed when booking and accessing other types of resources, such as car rentals.

[0003] It is desired to address or ameliorate some of the disadvantages associated with prior methods and systems for hotel room booking and room access management, or at least to provide a useful alternative thereto.

[0004] Any discussion of documents, acts, materials, devices, articles or the like which has been included in the present specification is not to be taken as an admission that any or all of these matters form part of the prior art base or were common general knowledge in the field relevant to the present disclosure as it existed before the priority date of each of the appended claims.

Summary

[0005] Some embodiments relate to a resource management system, the system comprising: at least one processor, a memory accessible to the at least one processor, wherein the at least one processor is in communication with a distributed ledger network configured to manage interaction reward token accounts associated with an interaction between a resource and a user, wherein the memory comprises program code executable by the at least one processor to configure the at least one processor to: transmit interaction feedback query program code to a client device, wherein the interaction feedback query program code is executable by the client device to cause the client device to transmit an interaction feedback response object encoding a response to the resource management system; receive by the resource management system the interaction feedback response object from the client device; determine a reward token value associated with feedback information encoded in the received interaction feedback response object; and execute by the resource management system an interaction reward token update program code stored in the memory to update an interaction reward token account associated with the client device, wherein the update is based on the determined reward token value.

[0006] In some embodiments, the interaction feedback query program code comprises one or more queries in relation to an interaction between the user and a resource, and the interaction feedback response object comprises responses to the query by the user and a resource identifier.

[0007] In some embodiments, the interaction between the user and the resource comprises one or more of: a request for booking of the resource by the user, a payment for the resource by the user or feedback regarding the resource by the user.

[0008] In some embodiments, the memory comprises program code executable by the at least one processor to further configure the at least one processor to: create a booking based on the resource identifier responsive to a request for booking of the resource; determine a virtual key associated with the resource identifier, wherein the virtual key is configured to cooperate with an access device co-located with the resource to permit access to the resource; and transmit a booking confirmation message to a computing device, wherein the confirmation message comprises one of (i) the virtual key and (ii) a confirmation code related to the virtual key to allow the virtual key to be retrieved.

[0009] In some embodiments, the resource management system is in communication with a resource booking system, and creating the booking comprises transmitting a booking confirmation request to a resource booking system to confirm the booking of the resource. [0010] In some embodiments, determining the virtual key associated with the resource comprises retrieving the virtual key from a virtual key database based on the resource identifier.

[0011] In some embodiments, the virtual key comprises one or more QR codes readable by the access device associated with the resource identifier.

[0012] In some embodiments, the request further comprises one or more of: (i) payment details and (ii) an indication of a duration for the booking.

[0013] In some embodiments, the interaction feedback response object comprises an image of the user’ s face, and the memory comprises program code executable by the at least one processor to further configure the at least one processor to verify an identity of the user based on the image of the user’s face and a booking information of the user stored in the memory.

[0014] In some embodiments, verifying the identity of the user comprises a comparison between the image of the user’ s face and an official identify document comprising a photograph provided in the booking information of the user.

[0015] In some embodiments, the interaction reward token update program code comprises one or more smart contract objects executable to securely update the distributed ledger network.

[0016] Some embodiments relate to a computer implemented method for resource management, the method comprising: transmitting by a resource management system an interaction feedback query program code to a client device, wherein the interaction feedback query program code is executable by the client device to cause the client device to transmit an interaction feedback response object encoding a response to the resource management system; receiving by the resource management system the interaction feedback response object from the client device; determining a reward token value associated with feedback information encoded in the received interaction feedback response object; and executing by the resource management system an interaction reward token update program code stored in the memory to update an interaction reward token account associated with the client device, wherein the update is based on the determined reward token value.

[0017] In some embodiments, the interaction feedback query program code comprises one or more queries in relation to an interaction between the user and a resource, and the interaction feedback response object comprises responses to the query by the user and a resource identifier.

[0018] In some embodiments, the interaction between the user and the resource comprises one or more of: a request for booking of the resource by the user, a payment for the resource by the user or feedback regarding the resource by the user.

[0019] The method of some embodiments further comprises: creating a booking by the resource management system based on the resource identifier responsive to a request for booking of the resource; determining by the resource management system a virtual key associated with the resource identifier, wherein the virtual key is configured to cooperate with an access device co-located with the resource to permit access to the resource; and transmitting by the resource management system a booking confirmation message to a client device, wherein the confirmation message comprises one of (i) the virtual key and (ii) a confirmation code related to the virtual key to allow the virtual key to be retrieved. [0020] In some embodiments, the resource management system is in communication with a resource booking system, and creating the booking comprises transmitting a booking confirmation request to a resource booking system to confirm the booking of the resource.

[0021] In some embodiments, the virtual key associated with the resource comprises retrieving the virtual key from a virtual key database based on the resource identifier.

[0022] In some embodiments, the virtual key comprises one or more QR codes readable by the access device associated with the resource identifier.

[0023] In some embodiments, the request further comprises one or more of: (i) payment details and (ii) an indication of a duration for the booking.

[0024] In some embodiments, the interaction feedback response object comprises an image of the user’ s face, and the method further comprises verifying an identity of the user based on the image of the user’s face and a predetermined booking information of the user.

[0025] In some embodiments, the verification of the identity of the user comprises a comparison between the image of the user’s face and an official identify document comprising a photograph provided in the predetermined booking information of the user.

[0026] In some embodiments, the interaction reward token update program code comprises one or more smart contract objects executable to securely update the distributed ledger network.

[0027] Some embodiments relate to a computer program product comprising computer readable code, which when executed by one or more processors is configured to perform the method resource management. [0028] Some embodiments relate to a client device configured to communicate with a resource management system, the client device comprising: at least one client device processor, a display and user input interface in communication with the at least one client device processor, and a client device memory accessible to the at least one client device processor, the client device memory comprising program code executable by the at least one client device processor to configure the at least one client device processor to: receive an interaction feedback query program code from the resource management system; execute the received interaction feedback query program to generate a resource interaction user interface on the display; receive user input through the user input interface responsive to the generated resource interaction user interface; generate an interaction feedback response object encoding a response based on the received user input to the resource management system; transmit the generated interaction feedback response object to the resource management system.

[0029] In some embodiments, the client device further comprises a camera in communication with the at least one client device processor, and the client device memory comprising program code executable by the at least one client device processor to further configure the at least one client device processor to capture an image and transmit the captured image to the resource management system, the captured image being encoded in the interaction feedback response object.

[0030] In some embodiments, the client device is further configured to communicate with a distributed ledger network configured to manage interaction reward token account associated with the client device, and the client device memory comprises program code executable by the at least one client device processor to further configure the at least one client device processor to communicate with the distributed ledger network.

[0031] In some embodiments, a communication with the distributed ledger network may comprise: a query of the reward token account associated with the client device, or an instruction to the distributed ledger network regarding expenditure of reward tokens comprised in the reward token account associated with the client device.

Brief Description of Drawings

[0032] Some embodiments will now be described by way of non-limiting examples with reference to the accompanying drawings.

[0033] Figure 1 is a block diagram of a system for resource management, according to some embodiments;

[0034] Figure 2 is a process flow diagram of a method of resource management according to some embodiments, the method being implemented by a resource management system of the system of Figure 1;

[0035] Figure 3 is a process flow diagram of a method of interacting with a resource, according to some embodiments, the method being implemented by a computing device of the system of Figure 1 ; [0036] Figure 4 is a process flow diagram of a method of managing access to booked resources, according to some embodiments, the method being implemented by an access device of the system of Figure 1;

[0037] Figures 5 and 6 are example screenshots of a booking management platform showing various stages involved in a booking process, according to some embodiments, the booking management platform being realised by a booking management application being executed by the resource management system of Figure l;

[0038] Figure 7 and 8 are example screenshots of an interface displayed on a screen of a computing device of the system of Figure 1 ;

[0039] Figure 9 is a process flow diagram of a method of resource management according to some embodiments, the method being implemented by the resource management system of Figure 1 ;

[0040] Figure 10 is a process flow diagram of a method of determination of a reward token value according to some embodiments, the method being implemented by the resource management system of Figure 1 ; and

[0041] Figure 11 and 12 are example screenshots of an interface displayed on a screen of the computing device of the system of Figure 1.

Detailed Description

[0042] Described embodiments relate to methods and systems for resource management, including managing interaction between users and resources, booking of resources and access management of booked resources, for example. Some embodiments relate to methods and systems for resource management, such as booking resources and providing access to the booked resources. Some embodiments relate to methods and systems for booking resources and accessing the booked resources. Some embodiments relate to methods and systems for managing access to booked resources.

[0043] For example, resources according to described embodiments may relate to resources that may be booked and for which access is required for use or benefit of the resource. For example, resources may include rooms, such as hotel or hostel rooms, houses, flats, apartments, services facilities, such as gyms, vehicles, such as cars, bicycles, motor bikes, or equipment, such as building equipment or gym equipment for example.

[0044] Some embodiments are configured to manage resources and interactions between resources and users using a distributed ledger network. In particular, some embodiments rely on a distributed ledger network to manage reward tokens awarded based on interaction between users and resources. The distributed ledger network allows the exchange of reward tokens between users or a conversion of the reward tokens to other forms of units of value, such as currency or virtual currency.

[0045] Some embodiments are configured to manage resources and interactions between resources and users using face recognition technologies. In particular, a booking process for resources according to some embodiments may involve provision of an identification document comprising an image, such as a photograph of the user. Some embodiments manage access to resources based on recognition of the face of a user in a newly captured image and comparison of the recognised face with the previously received image from the identification document.

[0046] The described systems and methods for booking resources and accessing booked resources according to the described embodiments provide significant advantages over known prior art systems and methods. In particular, the described embodiments allow for streamlined booking of resources which enable users to both book resources and acquire means necessary for accessing the booked resources, for example, using a virtual key, in one relatively straight forward process. Virtual keys according to the described embodiments may be directly obtained from a booking platform when booking a resource, thereby minimizing or eliminating further additional steps in securing and gaining access to a resource once a booking has been made. Further virtual keys according to the described embodiments may not be lost and the expenses associated with replacement of lost physical keys or access cards may be avoided. The replacement of lost physical keys or access cards according to the prior art may have adverse environmental consequences that the described embodiments help avoid. Additionally, a single virtual key according to the described embodiments may be shared across more than one mobile computing device by replication, enabling the sharing of access to a resource between more than one user, each user holding a mobile computing device and accessing the booked resource independently of other users.

[0047] The streamlining of the process for booking of resources and management of access to booked resources also reduces human intervention necessary to facilitate booking and access. With reduced need for human intervention, the described systems and methods for booking resources and accessing booked resources may be more scalable in terms of handling a larger number of resources and bookings while providing a more efficient and low-latency service requiring less human intervention. Virtual key based access to booked resources may also provide improved identity based security for managing access to booked resources. For example, access through virtual keys on mobile computing device may enable tracking the identity of the mobile device along with the virtual key. In some embodiments, the combination of the virtual key and identity of the device may be verified to permit access to a booked resource as an extra layer of security. The use of a distributed ledger by some embodiments to manage reward tokens provides a credible technical framework for issuing and facilitating the use and exchange of the issued reward tokens. The use of facial recognition techniques by some embodiments to verify an identify of a user provides an efficient mechanism for managing security and identity of users of resources.

[0048] Figure 1 illustrates a block diagram of a system 100 for booking and access management of resources 190, according to some embodiments. [0049] As illustrated, the system 100 may comprise a resource management system 102 arranged to communicate with one or more computing devices 104 and one or more resource booking systems 106 across a communications network 108. In some embodiments, the system 100 comprises a client-server architecture where the resource management system 102 is configured as a server and at least one of the computing devices 104 is configured as a client computing device.

[0050] The network 108 may include, for example, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, some combination thereof, or so forth. The network 108 may include, for example, one or more of: a wireless network, a wired network, an internet, an intranet, a public network, a packet-switched network, a circuit- switched network, an ad hoc network, an infrastructure network, a public -switched telephone network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, some combination thereof, or so forth.

[0051] In some embodiments, the computing device or client device 104 may comprise a mobile or hand-held computing device such as a smartphone or tablet, a laptop, or a PC, and may, in some embodiments, comprise multiple computing devices. The computing device 104 comprises at least one processor 143 and a memory 144 accessible to the processor. The memory comprises program code to implement a browser application 124, a resource access application 126, and a reward token wallet application 125. The computing device 104 also comprises a display 177 and a user input interface 179. The user input interface 179 may comprise one or more of: a keyboard, mouse or tactile input, such as a touch screen, for example.

[0052] The resource management system 102 may comprise one or more servers configured to provide resource management services by executing a resource management application 110 stored in a memory 129associated with the one or more servers of the resource management system 102. The memory 129 may be accessible by the at least one processor 131. The resource management system 102 may include multiple processing components or multiple virtual or physical servers operating together. In some embodiments, the resource management application 110 may comprise a booking management module 112, a virtual key management module 114, a reward management module 115, a distributed ledger integration module 117 and a face recognition module 118.

[0053] The booking management module 112, when executed by one or more processors (not shown) of one or more servers (not shown) of the resource management system 102, may be configured to communicate with the resource booking system 106 across the communication network 108 to determine availability of resources associated with the resource booking system 106 and to book specific resources, for example, for a particular user and/or for a particular duration of time.

[0054] The virtual key management module 114, when executed by one or more processors (not shown) of the one or more servers (not shown) of the resource management system 102, may be configured to interrogate a virtual key database 116 to determine a virtual key for a specific resource. In some embodiments, the virtual key associated with a particular resource is configured to cooperate with an access device 118, which may be co-located with the resource, to provide access to the resource, for example, by causing the access device 118 to deactivate a locking mechanism 120 preventing access to the resource. The virtual key database 116 may form part of or be directly connected to the resource management system 102 or may be accessed by the resource management system 102 across communications network 108 or any other suitable network.

[0055] The reward management module 115 comprises program code defining the logical rules, conditions and mathematical operations for determination of a reward token based on interactions of a user using the computing device 104 to access a resource 190. The reward tokens may be awarded to a user based on the user making a booking for the resource 190, or making a payment against the resource 190, choosing a specific payment mechanism for the resource 190, using a digital key for accessing the resource 190, or providing feedback regarding the resource 190, for example. The reward tokens awarded for interactions may be issued on instructions by the reward management module 115 and may be independently managed using a distributed ledger network 150 managing the interaction reward token account ledger 152.

[0056] The distributed ledger integration module 117 may comprise program code to allow the resource management system 102 to interact with the distributed ledger network 150. The distributed ledger integration module 117 may comprise one or more smart contracts defining the instructions for making changes to the interaction reward token account ledger 152 stored in the distributed ledger network 150.

[0057] The interaction reward token account ledger 152 is a database consisting of two or more block records (“blocks”) that are linked together and that adhere to a predetermined standard or protocol. Each block is a data structure that contains a payload and a link to a previous block. However, the link to a previous block may be omitted from the initial block.

[0058] According to a distributed ledger protocol, a block also includes a hash value for the payload and a proof of work (POW), possibly along with other hash values or other types of data. Data items such as the link to the previous block, the POW, and the hash of the payload may be collected into a block header. The payload may include one or more transaction records. For brevity, transaction records may be referred to as “transactions.” Each transaction may be timestamped and digitally signed by the participating computing entity which initiated it. After a computing entity initiates a transaction through a distributed ledger node, the distributed ledger node may send it to other Blockchain peers via the distributed ledger network 150.

[0059] The interaction reward token account ledger 152 may be considered a “distributed” database because multiple different data processing systems may obtain copies of the interaction reward token account ledger 152, and multiple different nodes such as the resource management system 102 or computing device 104 may update the interaction reward token account ledger 152. For instance, interaction reward token account ledger 152 may be made available to users of the resource management system 100 via the Internet, and users may update the interaction reward token account ledger 152 by creating a new block for the end of the interaction reward token account ledger 152 and publishing that block to other nodes of the distributed ledger network.

[0060] The interaction reward token account ledger 152 may include all valid blocks that have ever been created. Accordingly, interaction reward token account ledger 152 may contain a set of data records that is continuously growing, with each record referring to at least one previous record on the set. The interaction reward token account ledger 152 may thus be hardened against tampering and revision. Contributors to the distributed ledger, such as the resource management system 102 and other nodes, cooperate to maintain and build the distributed ledger network 150. Each node in the distributed ledger network 150 may include a copy of the entire interaction reward token account ledger 152 or a portion of the interaction reward token account ledger 152. Blocks within the interaction reward token account ledger 152 may comprise information regarding allocation of reward tokens against user accounts and transactions performed by the users using the allocated reward tokens. Records of transactions may include information regarding a sender of a reward token, a receiver of a reward token, number of reward tokens transferred, and a date and time of the transaction. The time of a transaction may include hour information, minute information and a time zone information. In some embodiments, the distributed ledger network 150 may be implemented using a private Ethereum network, or a private Hyperledger network, or a private Corda network, or a private Chain network, or a private Ripple network, for example.

[0061] The face recognition module 118 comprises program code capable of processing images comprising faces and comparing the faces in captured images to one or more images of faces stored in a booking register 137. The booking register 137 comprises information regarding bookings of resources made by users using the computing device 104. The information regarding bookings may include a unique identifier of the resource booked, an identifier of the user to whom the booking belongs, the duration or time period over which the booking is valid for and identity details of the user. Identity details of the user may comprise one or more identity documents of the user including an image of the face of the user. Images of the user from the identity documents stored in the booking register 137 may be accessible by the face recognition module 118 to verify whether a face captured in an image by the computing device 104 belongs to a particular user associated with a booking of a resource.

[0062] The face recognition module 118 may comprise program code to identify specific, distinctive details about a person’s face. These details, such as relative position, size, and/or shape of the eyes, nose, cheekbones, and jaw, may be then converted into a mathematical representation of the face and compared to data on other faces to perform face recognition. The specific, distinctive details about a person’s face may be referred to as a face template. The face template may provide a basis for determining whether a previously unseen (e.g. newly captured) image of a face of a person matches the face of the person from which the face template is derived. When a booking record is received in the booking register 137, the face recognition module 118 may analyse any photographs or other images of the user from the identity documents stored in the booking register 137 to determine a face template. The face template may be represented in the form of a mathematical vector representing all the determined distinctive features of a face. In some embodiments, the face recognition module 118 may determine the face template based on more than one photograph of a user from more than one photographic identity document. In some embodiments, the face recognition module 118 may incorporate a DeepFace face recognition framework or a FaceNet face recognition framework to perform the face recognition operations.

[0063] In some embodiments, the resource management system 102 may be configured as a web server system that is capable of serving content such as web pages and other content in accordance with a protocol such as the hypertext transfer protocol (HTTP). For example, when supported by and combined with an application framework and typical server-side functions, such as web server functions, data processing functions and data storage and retrieval function, the resource management application 110 provides a resource booking platform (an example of which is illustrated in Figures 5 and 6) which may encompass activities that may be viewed as being performed or executed at the one or more computing devices 104. However, it will be understood that activities performed or executed at the computing devices 104 are reliant on program code (including applets, where appropriate) served by the resource management system 102 to the computing devices 104 and executed by a browser application (not shown). The functionality of the booking platform is therefore driven by code executed and served by the resource management system 102.

[0064] The resource management application 110 may allow programmatic interaction of remote applications to exchange information with the resource booking system 106 via defined APIs (“application program interfaces”). The resource management services may be defined and implemented using a variety of underlying protocols and techniques. For example, some embodiments may rely on data communication in XML (“extensible Markup Language”) format using HTTP (“Hyper Text Transport Protocol”) in response to a request from the booking management module 112 specified as a URI (“Uniform Resource Identifier”), such as a URL (“Uniform Resource Locator”) that includes a specified operation and one or more query parameters. Such URI-based requests may, for example, be based on the use of XML over HTTP (e.g., as part of the Representational State Transfer, or “REST”, distributed interaction model). In some embodiments, additional underlying protocols may be used for various purposes, such as SOAP (“Simple Object Access Protocol”) for standard message exchange, WSDL (“Web Services Description Language”) for description of service invocations, and UDDI (“Universal Description, Discovery, and Integration service”) for discovery of available services.

[0065] The resource booking system 106 may comprise one or more servers (not shown) configured to provide a resource booking service by executing a resource booking application 122 stored in memory (not shown) associated with the one or more servers of the resource booking system 106. The resource booking system 106 is configured to maintain a register of resources available for booking through the resource booking system 106. The resource booking system 106 is further configured to provide or otherwise make available to the booking management module 112 of the resource management system 102 information about the availability of resources and to book a resource, i.e., to make resources unavailable for booking, in response to receiving a booking confirmation from the resource management system 102. It will, however, be appreciated, that resources may be booked with the resource booking system 106 in other ways, for example, by a computing device 104 communicating directly with the resource booking system 106 or an operator manually booking a resource in response to a request made by a person. In some embodiments, the resource booking system 106 may be configured to provide or otherwise make available to the virtual key management module 112 of the resource management system 102 information about the virtual keys associated with particular resources. In some embodiments, the resource booking system 106 may be configured to provide or otherwise make available to the resource access application 126 of the computing device 104 information about a booked resource, which may include, for example, credentials for accessing the booked resource.

[0066] The resource booking application 122 may allow programmatic interaction of remote applications to exchange information via defined APIs (“application program interfaces”). The resource booking application 122 may be defined and implemented using a variety of underlying protocols and techniques. For example, some embodiments may rely on data communication in XML (“extensible Markup Language”) format using HTTP (“Hyper Text Transport Protocol”) in response to a request from the resource access application 126 or the resource management application 110 specified as a URI (“Uniform Resource Identifier”), such as a URL (“Uniform Resource Locator”) that includes a specified operation and one or more query parameters. Such URI-based requests may, for example, be based on the use of XML over HTTP (e.g., as part of the Representational State Transfer, or “REST”, distributed interaction model). In some embodiments, additional underlying protocols may be used for various purposes, such as SOAP (“Simple Object Access Protocol”) for standard message exchange, WSDL (“Web Services Description Language”) for description of service invocations, and UDDI (“Universal Description, Discovery, and Integration service”) for discovery of available services. [0067] The one or more computing devices 104 each comprise one or more processors 143 and memory 144 which includes an operating system and a number of software applications or applets executable by the one or more processors to perform various device-related functions. For example, at least one such software application includes a browser application 124 for enabling a user to navigate to sites accessible over the communications network 108 to receive content therefrom. In some examples, the browser application 124 can be used to communicate with the resource management system 102 to request content therefrom, in the form of one or more web pages provided as program code to the browser application and executable by the processor(s) of the computing device 102. According to some embodiments, the resource management system 102 is configured to serve code to the computing device 104 to provide an online resource booking platform generated by browser application

124 and viewable on a display (not shown) of a user interface (not shown) of the computing device 104.

[0068] Memory 144 of the computing device 104 also comprises program code to implement a reward token wallet application 125. The reward token wallet application may comprise one or more security credentials such as private or public keys to allow the computing device 104 to access information in the interaction reward token account ledger 152 in the distributed ledger network 150. The reward token wallet application

125 may also comprise one or more smart contracts executable by the computing device 104 to effect a transaction on the distributed ledger network 150. Transactions may include expenditure of reward tokens or transfer of reward tokens to other users, for example.

[0069] The resource booking platform may provide user interfaces that allow a user to search for resources using particular key terms and/or criteria. For example, where the resource to be booked is a hotel room, the resource booking platform may provide user interfaces that allow a user to enter specific location(s) and/or specific date(s) to search for an available hotel room meeting the search criteria. In response to user inputting search criteria, the booking management module 112 of the resource management application 110 may determine and provide to the resource booking platform a list of available hotels. The resource booking platform may allow the user to navigate through the results and to select a particular hotel. Upon selecting a particular hotel, the user may be prompted to make a payment for the hotel booking, for example, by providing payment details. During the booking process, the user may also be queried as to whether he or she would like to avail of keyless entry to the hotel room, as discussed below in more detail.

[0070] In some embodiments, the browser application 124 may be supplemented by a special-purpose add-on or may be substituted by special-purpose client software (i.e. an “app” for a smart-phone or tablet device) in order to perform the functions described herein or to facilitate such functions. For example, for the computing device 104, a special purpose application may be downloaded from the resource management system 102 or a separate dedicated download server (not shown) and installed on the computing device 104. When such a special purpose application is executing on the computing devices 104, it may facilitate appropriate formatting, interaction, display and input to enable the user interface functionality described herein. Such a special purpose application may comprise a resource access application 126 configured to cooperate with application software running on the access device 118. In some embodiments, the resource access application 126 is configured to receive and store a virtual key associated with a particular resource, from for example, the resource management system 102, and to provide the virtual key to the access device 118 associated with the resource to deactivate a locking mechanism 120 preventing access to the resource.

[0071] The resource access application 126 may be configured to communicate with the resource management system 102 to request and/or receive information from the resource management system 102. In some embodiments, the resource access application 126 is configured to receive and store a virtual key associated with a particular resource, from the resource management system 102, for example, and to provide the virtual key to the access device 118 associated with the resource to deactivate a locking mechanism 120 preventing access to the resource. In some embodiments, the resource access application 126 is configured to receive and store booking confirmation details associated with a booked resource, for example, a resource identifier, relevant dates, payment confirmation details, etc.

[0072] The access devices 118 are configured to communicate with the resource access application 126 of the mobile computing device 104 to determine a virtual key associated with a particular resource that is being managed under the control of the access device 118. For example, the resource access application 126 of the mobile computing device 104 may be configured to communicate with the access device 118 using near field communication capability or Bluetooth based communication capability. In some embodiments, the virtual key may comprise a QR (quick response) codes or a matrix barcode or a SnapTag which is readable or scannable by the access device 118.

[0073] The access devices 118 are each associated with one or more resources and a respective one or more locking mechanisms 120. When activated by the access device 118, or otherwise, the locking mechanisms 120 prevent access to the respective resource. In some embodiments, the access devices 118 comprise one or more processors and memory comprising computing code, which when executed by the one or more processors is configured to control operations of the access device 118. For example, the access device 118 may be configured to determine a virtual key provided on or received from a mobile computing device 104, determine a validity of the virtual key for a particular resource and in response to determining that the virtual key is valid for that resource, deactivate a locking mechanism 120 associated with the resource to allow access to the resource. In some embodiments, the access devices 118 are configured to communicate with the resource booking system 106 or other servers (not shown) associated with the management of the resources to determine the validity of a virtual key for a particular resource. For example, the resource booking system 106 or other servers (not shown) may query a register of virtual keys for resources and compare the virtual key for the resource to an entry in the register to determine its validity, for example, by determining whether a booking has been made and the virtual key is active, and/or whether the virtual key matches records in the register for the particular resource. [0074] Figure 2 is a process flow diagram of a method 200 of resource management according to some embodiments. The method 200 may be implemented by a resource management system 102. In particular, one or more processors 131 of the resource management system 102 may be configured to execute the resource management application 110 to cause the resource management system 102 to perform the method 200.

[0075] Referring now to Figure 2, a request to book a resource is received at the resource management system 102 from a computing device 104, at 202. The request comprises a resource identifier and a mobile computing device identifier. In some embodiments, the request further includes one or more of an indication of a duration for booking of the resource, any particular special requests and payment details. In some embodiments, the request also comprises one or more identity images, such as images of identity documents that include an image, such as a photographic image, of the user making the booking. The photographic identity documents may include a driving licence or a passport, for example.

[0076] In some embodiments, the resource management application 110 is configured to retrieve details of resources in response to a query received from the computing device 104 and to display the details on the booking platform to allow a user to select a resource and to submit the request for a booking. In some embodiments, the booking management module 112 determines whether resources are available and any further details about the resources from a resource register 128 which may be local to or remote from the resource management system 102, and which is periodically and/or regularly updated by one or more resource booking systems 106 associated with the resources. In some embodiments, the booking management module 112 determines whether resources are available and any further details about the resources by querying one or more resource booking system 106.

[0077] For example, a resource information query may be initiated by the booking management module 112 submitting a HTTP POST request to a designated URL of the resource booking application 122 in an XML format. The resource information query may also include credentials to validate and authorize the booking of the resource by the resource booking application 122. Below is an example of a HTTP POST request in XML format:

<gethotels>

<usertoken>

<userid>xxxx</userid>

<password>yyyy</password>

</usertoken>

</gethotels>

[0078] The resource booking application 122 may return a response to the query above in the following format:

<?xml version="1.0" encoding="utf-8" ?>

<hotels>

<hotel>

<hotelid> 1 </hotelid>

<hotelname>test-hotel- 1 </hotelname>

</hotel>

</hotels>

[0079] The booking management module 112 may further query the resource booking application 122 for details of available resources with particular criteria, for example, available resources in particular locations. Below is an example of a query for hotel room types for a hotel with hotel id 71656:

<getroomtypes>

<usertoken>

<userid>xxxx</userid>

<password>yyyy</password>

<hotelid>71656</hotelid> </usertoken>

</getroomtypes >

[0080] An example of response generated by the resource booking application 122 to the above query may be in the following format:

<?xml version="1.0" encoding="utf-8" ?>

<roomtypes>

<roomtype>

<id>142790</id>

<description>standard</description>

</roomtype>

<roomtype>

<id>145612</id>

<description>2 bedroom apartment</description>

</roomtype>

<roomtype>

<id>148227</id>

<description>superior</description>

</roomtype>

<roomtype>

<id>97356</id>

< description > deluxe </de scrip tion >

</roomtype>

</roomtypes>

[0081] A user at the computing device 104 may navigate the details of the resources displayed on the booking platform and select a resource and cause the request to book the associated resource to be sent to the resource management system 102.

[0082] Referring again to Figure 2, the resource management system 102, and in particular, the booking management module 112, creates a booking based on the resource identifier, at 204. Details associated with the created booking, including unique identifiers of the booked resource, date and duration of the booking, and photographic identity documents of the user making the booking, for example, may be stored in the bookings database 137 accessible to the resource management system 102. In some embodiments, the booking management module 112 transmits a booking confirmation request to the resource booking application 122 of the resource booking system. The booking confirmation request comprises the resource identifier and may further include additional information about the booking.

[0083] Below is an example of a booking confirmation request being sent to the resource booking application 122 by the booking management module 112:

<booking>

< u sername > xxxxxx </u sername >

<password>yyyyy</password>

<bookingtime >2010-11-22 18:37:48 </bookingtime >

<bookingid>3345 </bookingid>

<bookingstatus>Confirmed</bookingstatus>

<hotelname>third party site hotel</hotelname>

<hotelid>4</hotelid>

< arrivaldate>2010- 11 -24 </arrivaldate >

<departuredate>2010- 11 -30</departuredate>

<currencycode>aud</currencycode>

<totalcost>620.00</totalcost>

<roomid>6</roomid>

<roomquantity> 1 </roomquantity>

<guestcount>2</guestcount>

< arri v altime > 02 : 00 < /arri v altime >

<guestname>guest</guestname>

<guestphone>+64-9-123456</guestphone>

<guestemail>admin@myproperties.com</guestemail&g t;

< specialrequest> Test </specialrequest>

<deposit>0</deposit>

<depositdescriptionX/depositdescription> <refer></refer>

< addons >

< addon >

<id>l</id>

<name>breakfast</name>

<unitcost> 10</unitcost> <quantity>2</quantity>

<total> 100</total>

<nights>5</nights>

</addon>

< addon >

<id>2</id>

<name>box of chocolate on arrival</name> <unitcost>20</unitcost>

<quantity> 1 </quantity>

< total > 20 < /total >

< nights > - </nights >

</addon>

<addontotal> 120</addontotal>

</addons>

</booking>

[0084] In some embodiments, the resource booking application 122 determines whether to confirm or deny the booking confirmation request and sends a response to the booking management module 112. In some embodiments, if the resource booking application 122 confirms the booking, the resource booking application 122 may update a resource register to reflect the booking and, for example, to mitigate multiple bookings for the same periods for the same resource being made. In some embodiments, the booking management module 112 updates details about the resource in the resource register 128. [0085] The resource management application 110, and in particular, the virtual key management module 114, determines a virtual key for the booked resource, at 206. In some embodiments, the virtual key management module 114 queries a virtual key database 116 using the resource identifier to determine the virtual key associated with the resource identified by the resource identifier.

[0086] In some embodiments, the resource management application 110 determines whether a mobile computing device 204 associated with the mobile computing device identifier has a resource access application 126 deployed thereon, at 208. For example, the resource management application 110 may query a resource access application register (not shown) using information about the user or the mobile computing device, such as the mobile computing device identifier, to determine whether the resource access application 126 has been downloaded to the mobile computing device 204 associated with the user, such as the mobile computing device identified by the mobile computing device identifier. In some embodiments, the resource management application 110 may send a query to the computing device 104 to determine if the resource access application 126 is deployed thereon. If it is determined that the resource access application 126 is not deployed on the mobile computing device 104, the resource management application 110 prompts the computing device 104, for example, by way of sending a link to download the resource access application 126, to obtain the resource access application 126, at 210, and the method reverts to 208.

[0087] If it is determined that the resource access application 126 is deployed on the mobile computing device 104, the resource management application 110 provides a confirmation message comprising the virtual key associated with the booked resource to the mobile computing device 104 associated with the mobile computing device identifier, at 212. In some embodiments, as opposed to providing the virtual key directly to the mobile computing device via the confirmation message, the virtual key may be provided indirectly to the mobile computing device, for example, by providing a confirmation code relating to the virtual key as opposed to the virtual key in the confirmation message. In embodiments where a confirmation code relating to a virtual key is provided, the confirmation code may be used to retrieve and download the related virtual key to the mobile computing device 104, for example, from a website, an address of which may be provided in the confirmation message.

[0088] In some embodiments, the resource management application 110 does not determine whether a mobile computing device 204 associated with the mobile computing device identifier has a resource access application 126 deployed thereon and instead either provides a confirmation message comprising the virtual key associated with the booked resource to the mobile computing device 104 associated with the mobile computing device identifier, as at 212, or provides a confirmation message comprising a confirmation code relating to the virtual key associated with the booked resource to the mobile computing device 104 associated with the mobile computing device identifier. For example, in some cases, it may be unnecessary for the mobile computing device 204 to have a resource management application 110 to receive and use a virtual key to access a resource. In embodiments where a confirmation code relating to a virtual key is provided, the confirmation code may be used to retrieve and download the related virtual key to the mobile computing device 104, for example, from a website, an address of which may be provided in the confirmation message.

[0089] Figure 3 is a process flow diagram of a method 300 of booking a resource and gaining access to the booked resource, according to some embodiments. The method 300 may be implemented by a mobile computing device 104. In particular, one or more processors of the computing device 104 may be configured to execute the browser application 124 and the resource access application to cause the computing device 102 to perform the method 300.

[0090] A request to book a resource is sent from the computing device 104 to the resource management system 102, at 302. In some embodiments, the request to book a resource may comprise one or more identity images of photographic identity documents of the user requesting the booking of the resource. The photographic identity documents may comprise a driver’s licence or a passport, for example. As described above, the computing device 104 is configured to display a booking platform to the user to allow the user to generate the request to book the resource. The request comprises a resource identifier associated with the resource to be booked and a mobile computing device identifier. In some embodiments, the mobile computing device identifier may be an identifier of the computing device 104, such as a phone number.

[0091] A confirmation message comprising a virtual key is received at the mobile computing device 104 associated with the mobile computing device identifier, at 304.

In some embodiments, instead of a virtual key, the confirmation message may comprise a confirmation code relating to the virtual key. The confirmation code may be used to retrieve and download the related virtual key thereafter.

[0092] The virtual key is used to gain access to the booked resource. The virtual key is caused to cooperate with an access device 118 associated with the booked resource to provide access to the resource, at 306. In some embodiments, the resource access application 126 is configured to communicate with the access device 118 to gain access to the resource. Responsive to the access device 118 determining that the virtual key is valid for the particular resource, the virtual key provides access to the resource.

[0093] The resource access application 126 using the virtual key may be configured to communicate with the access device using near field communication (NFC) capability or Bluetooth based communication capability. In some embodiments, the virtual key may comprise a QR codes which is readable or scannable by the access device 118.

[0094] In some embodiments, the resource management system 102 may through its reward management module 115 may communicate with the computing device 104 to seek feedback regarding an interaction between a user and a resource 190. In some embodiments, the resource management system 102 may through its face recognition module 117 may communicate with the computing device 104 to verify the identity of the user of resource 190 against the booking information stored in the booking database 137. Steps 308 to 318 relate to the seeking of feedback and verification of identity performed in coordination with the resource management system 102. [0095] At 308, the computing device 104 receives an interaction feedback query program code from the resource management system 102. The interaction feedback query program code may comprise program code executable by the processor 143 to allow a user to provide feedback regarding their interaction with the resource 190 through the computing device 104. At 310, the interaction feedback query program code is executed by the processor 143 to generate one or more graphical user interfaces on the display 177. Figure 12 illustrates an example of a graphical user interface generated at 310 according to some embodiments. The graphical user interface presented on the display 177 may comprise one or more interactive user interface elements such as checkboxes, radio icons, text boxes, select lists, for example to allow a user to efficiently provide feedback at step 312 regarding the resource 177 by interacting through the user input interface 179 in response to the graphical user interface presented on the display 177.

[0096] At 314, responsive to the gaining of access to the resource at 306, the resource access application 126 may initiate a process of identity verification. The resource access application 126 may prompt the capture of an image of the face of the user through the camera 127 provided in the computing device 104. The user may be directed to capture an image of their face and resource access application 126 may transmit the captured image to the resource management system 102 for verification of the user’s identity.

[0097] At 316, the resource access application 126 processes the user input received at 316 and collates the received feedback and the captured image (if any) into an interaction feedback response object encoding the response or feedback based on the received user input. The generated interaction feedback response object is transmitted by the computing device 104 to the resource management system 102 at 316 over network 108.

[0098] At 318, the computing device 104 may receive a message from the resource management system 102 regarding the outcome of the identify verification process. If the user’s identity is successfully verified by the resource management system 102 by comparison with one or more photographic identity documents stored in the bookings register 137, then the resource access application 126 may present a message on the display 177 indicating a confirmation of verification of the user’s identity. If the message from the resource management system 102 indicates that the user’s identity has not been successfully verified, then the resource access application 126 may present a message on the display 177 indicating a failure of verification of the user’s identity and directions to reattempt the verification of identity. Steps 304, 306, 314 and 318 may be optional steps and may not be performed by some embodiments.

[0099] The steps of the process flow 300 may be performed over an extended period. For example, step 302 may be performed well in advance of the period of time over which the resource is intended to be accessed. Step 306 may be performed just before the resource is accessed. Steps 308, 310, 312, 314, 316 and 318 may be performed after a resource has been accessed. In some embodiments, Step 314 may be performed immediately after step 306, for example.

[0100] Figure 4 is a process flow diagram of a method 400 of managing access to booked resources, according to some embodiments. The method may be implemented by an access device 118 of the system 100. In particular, one or more processors of the access device 118 may be configured to execute instructions (computer code) to cause the access device 118 to perform the method 400.

[0101] An access request for access to a resource co-located or otherwise associated with an access device 118 is received from a mobile computing device 104 at the access device 118, at 402. For example, the access request may be received from a resource access application 126 deployed on the mobile computing device 104. The access request comprises a virtual key associated with the resource. In some embodiments, the access request further comprises a resource identifier associated with the resource and the virtual key.

[0102] Validity of the virtual key for a particular resource is determined, at 404. In some embodiments, the access device 118 communicates with the resource booking system 106 or other servers (not shown) associated with the management of the resources to determine the validity of a virtual key for a particular resource. In some embodiments, relevant validity information may be stored locally in memory of the access device 118 and interrogated to determine the validity of the presented virtual key for the resource. Validity of the virtual key may depend on the date and time at which the access request was received.

[0103] In some embodiments, the access device 118 may cause the resource access application 126 to prompt the user to undertake certain identification verification or compliance steps before granting access to the resource. For example, in some embodiments, the resource access application 126 may prompt the user to provide documentation such as a proof of identification. The documentation may be communicated by the resource access application 126 to the resource booking system 106 or other relevant sever or system (not shown) for example, for record keeping purposes.

[0104] If it is determined that the virtual key is valid for the resource, at 406, access to the resource is permitted, at 410. For example, in some embodiments, the access device 118 communicates with a respective locking mechanism 120, directly or via a communications network (not shown), to deactivate the locking mechanism 120 and provide access to the resource.

[0105] If it is determined that the virtual key is not valid for the resource, at 406, access to the resource is denied, at 410. In some embodiments, the access device 118 may report to the resource booking system 106 or other associated server or system a denial of entry with the details of the presented virtual key or credential. This may assist in monitoring attempts of unauthorised entry.

[0106] Figure 5 illustrates an example screenshot 500 of a booking platform for a hotel resource as shown on an interface of a computing device 104. Region 505 allows the user to enter a desired destination to search for hotels. Through user selectable options shown at regions 510, the user may enter the relevant check-in and check-out dates. A list of all the hotels available according to the criterion entered by the user is displayed in a display window 515. A map view of the identified hotels is shown at map view window 520.

[0107] Figure 6 illustrates another example screenshot 600 of a booking platform 602 for a hotel resource as shown on an interface of a computing device 104. Region 605 of the booking platform 602 displays details of a booking made by a user. In particular, check-in and check-out dates, number of guests and rooms are displayed for confirmation and review by the user. Section 610 of the booking platform 602 displays relevant add-ons applicable to the booking. One relevant add on is the ability to make a keyless entry to the hotel room. By selecting a user selectable option 615, the user may indicate his or her interest in seeking keyless entry to the booked hotel room upon arrival.

[0108] Figure 7 illustrates an example screenshot 700 of an interface 702 of the resource access application 126, which may for example, be presented to the user when activating the resource access application 126 for a first time. The user is prompted to enter his or her phone number in region 710 and a confirmation code by the user in region 720. For example, the phone number entered by the user may correspond with the mobile computing device identified provided to the resource management system 102 at 302 of method 300 as shown in Figure 3. The confirmation code may be provided to the user’s computing device 104 when the resource access application 126 is downloaded or installed on the computing device 104. The confirmation code may be provided to the user’s computing device 104 through a messaging service such as an SMS or an MMS or an email. After entering the phone number and confirmation code in interface 700, the user may confirm the details entered using a confirm button 730. After the user presses the confirm button 730, the entered details are communicated by the resource access application 126 to the resource booking system 106 to retrieve information pertinent to the booked resource. The resource management system 102 may also return to the resource access application 126, details of the user’s booking, as illustrated in Figure 8. [0109] Figure 8 illustrates an example screenshot 800 of an interface 802 of the resource access application 126. The interface 802 displays details of a confirmed hotel room booking allowing for validation by the user of received booking information. For example, region 810 displays the relevant dates for which the booking is valid, and region 820 displays the allocated room number to the booking. In some embodiments, the room number may not be allocated immediately after a booking and there may be an intervening period between the making of a booking by the user and allocation of a room to the booking made by the user. The interface 802 also provides a button 830 associated with a virtual key for the booked resource. Pressing the button 830 while placing the mobile computing device 104 in a vicinity of the access device 118, which, in this case may be a hotel door lock device, initiates transmission of the virtual key or credential details to the access device 118 for verification. For example, this may correspond with 306 of method 300 as shown in Figure 3.

[0110] In some embodiments, the resource access application 126 may allow the sharing of the virtual key or credential across multiple mobile devices 104, each device executing the resource access application 126. The mobile device 104 registered during the booking process may be known as a primary mobile device. The primary mobile device, through the resource access application may share the received virtual key or credentials to other secondary mobile devices executing the resource access application. This may be advantageous where multiple people are to avail of the booked resource or multiple booked resources are associated with the same virtual key.

[0111] Figure 9 is a process flow diagram of a method 900 of managing interaction with a resource performed by the resource management system 102 according to some embodiments. The method 900 coordinates with parts of the method 300 of Figure 3 performed by the computing device 104 to facilitate the management of the interaction of a user with a resource.

[0112] At 902, the resource management system 102 transmits an interaction feedback query program code to the computing device 104. The interaction feedback query program code is executable by the computing device 104 to generate a graphical user interface that allows a user to provide feedback regarding an interaction with a resource 190. At 904, the resource management system 102 receives from the computing device 104 an interaction feedback response object. The interaction feedback response object is decoded by the resource management system 102 to extract the information encoded in the interaction feedback response object comprising feedback of the user. In some embodiments, the interaction feedback response object may also comprise an image captured by the computing device 104 for the purposes of the verification of identity of the user. The interaction feedback response object may also comprise booking and payment details associated with the booking of the resource 190 through the computing device 104. The received decoded interaction feedback response and any received images may be stored by the resource management system 102 in the memory 129.

[0113] At 906, the reward management module 115 of the resource management system 102 determines a reward token value based on the decoded information in the interaction feedback response object. The reward token value may be based on the amount associated with a payment for the resource 190, the payment method used, or use of a virtual key, for example. Figure 10 illustrates a process of determination of a reward token value by the resource management system 102 according to some embodiments.

[0114] At 908, the resource management system updates the interaction reward token ledger in the distributed ledger network 150 based on the reward token value determined at 906. The resource management system 102 may comprise one or more smart contract program code modules 199 provided in distributed ledger integration module 117. The smart contract program code modules may comprise necessary security credentials to allow the resource management system 102 to update the interaction reward token account ledger 152 in the distributed ledger network 150.

[0115] Steps 910 and 912 may be performed by the resource management system 102 if the interaction feedback response object received at 904 comprises an image for verification of the identity of the user of the computing device 104. At 910, the face recognition module 118 may extract an image captured by the computing device 104 from the interaction feedback response object received at 904. The extracted image may be compared with the images from the photographic identity documents stored in the bookings register 137 to verify the identity of the user based on the extracted image. The outcome of the image verification may be the determination that the captured image matches with an image from a specific photographic identity document stored in the bookings register 137 and accordingly the identity of the user may be validated. If a match is not found, the user’s photographic identity may require validation using a different image or by other alternative means. An outcome of the verification of the user’s identity based on image verification may be transmitted by the resource management system 102 to the computing device 104 at 912.

[0116] Figure 10 illustrates a process of determination of a reward token value by the resource management system 102 according to some embodiments as executed by step 906 of Figure 9. The reward token value may be determined based on several aspects of the booking or interaction of the user with the resource 190. At step 1002, a reward token value component may be determined based on an amount or price paid by the user for booking the resource 190. The reward tokens may be determined as a percentage amount of the price of the booking. In some embodiments, the reward tokens may be awarded as 0.5% or 1% or 2% of the price or amount paid for the resource, for example. In some embodiments, the reward tokens held by a user may be used for making a payment for booking a resource at step 302 of figure 3. A reward token component may be awarded for use of reward tokens for booking a resource. The reward token component may be, for example 0.5%, 1% or 2% of the price for booking the resource. At 1006, a reward token component may be awarded for a booking using a digital or virtual key. The reward token award component for using a digital key may be 0.5%, 1% or 2% of the price for booking the resource, for example. At 1008, a reward token component may be determined based on receiving a feedback from a user regarding the interaction of the user with the resource. The reward token component for providing feedback may be for example 0.5%, 1% or 2% of the price for booking the resource. The reward components may be summed up by the reward management module 115 and may be used to update the interaction reward token account ledger 152 by the resource management system 102.

[0117] Figure 11 illustrates a screenshot 1100 of a user interface provided by the reward token wallet application 125 executing on the computing device 104. In region 1101 is displayed a balance of the reward wallet token account of the user illustrating the number of reward wallet tokens hold by the user as recorded in the interaction reward token account ledger 152. A button 1102 may be pressed by the user to allow the user to buy more reward tokens. A button 1103 may be pressed by the user to send their reward tokens to an account in the interaction reward token account ledger 152 held by a different user. The reward token wallet application 125 comprises one or more smart contract program code modules 198 to facilitate the buying or transfer of reward tokens in the distributed ledger network 150. Region 1104 illustrates exemplary values of percentages used for determination of a reward token value by the reward management module 115 for the user’s reference.

[0118] Figure 12 illustrates a screenshot 1200 of a graphical user interface generated on the display 177 responsive to interaction feedback query program code received by the computing device 104. The graphical user interface of screenshot 1200 comprises several user interaction components allowing the user to respond to the interaction feedback query using the user input interface 179. For example, component 1201 comprises a set of stars or symbols to allow a user to rate their perception of a first characteristic, such as value, of a resource on a scale of 1 star to 5 stars. Similarly, component 1202 allows a user to rate their perception of a second characteristic, such as the location, of a resource on a scale of 1 star to 5 stars. After completion of feedback by the user in response to the user input interface of screenshot 1200, the user may press the submit button 1205 to initiate generation of an interaction feedback response object encoding the response to the feedback query from the user and then subsequent transmission of that object to the resource management system.

[0119] Objects as described in this specification, including recommendations object, message object and response object may be discretely identifiable computing communication constructs capable of transmission and reception over a computer network. Objects may comprise data, and an object when received by a computing device may be capable of interpretation by the computing device to access the data. Objects may comprise program code, and an object when received by a computing device may be capable of execution by the computing device to execute the program code. In some embodiments, objects may include a combination of data and program code. Object may comprise by one or more header elements and one or more payload elements. The payload elements may comprise the data or the program code or both.

[0120] The various modules or applications implemented in the memory 129 of the resource management system 102 or the memory 144 of the computing device 104 comprise program code implementing the computing or data processing capability of the respective modules or applications. In addition, the various modules or applications may also comprise or may have access to software packages, software libraries, configurations or configurations files, Application Programming Interfaces (APIs) to perform the computing or data processing functions of the respective modules or applications. In some embodiments, the various modules or applications when executed by a processor may execute as one or more processes coordinated by an operating system executing on the computing device 104 or the resource management system 102. The various modules or applications when executed as a process may comprise one or more threads executing concurrently to perform the data processing operations.

[0121] It will be appreciated by persons skilled in the art that numerous variations and/or modifications may be made to the above-described embodiments, without departing from the broad general scope of the present disclosure. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive.