SYSTEM AND METHOD FOR REMOTE PROVISION, DISBURSEMENT AND COLLECTION OF SECURED LOANS CROSS-REFERENCE(S) TO RELATED APPLICATIONS This application claims priority from South African provisional patent application number 2020/05065 filed on 17 August 2020, which is incorporated by reference herein. FIELD OF THE INVENTION This invention relates to a system and method for remote provision, disbursement and collection of secured loans. BACKGROUND TO THE INVENTION A secured loan typically refers to a loan in which a borrower or consumer pledges some asset as collateral for the loan, which then becomes a secured debt owed to the creditor who gives the loan. The debt is thus secured against the collateral, and if the borrower defaults, the creditor takes possession of the asset used as collateral and may sell it to regain some or all of the amount originally loaned to the borrower. By extending the loan through securing the debt, the creditor is relieved of most of the financial risks involved because it allows the creditor to take ownership of the property in the event that the debt is not properly repaid. In exchange, the borrower may receive loans on more favourable terms than that available for unsecured debt, or may be extended credit under circumstances when credit under terms of unsecured debt would not be extended at all. The creditor may for example offer a loan with attractive interest rates and repayment periods for the secured debt. There are however circumstances or regions in which extending secure loans is not practicable, for example due to the borrower being geographically remote from the creditor's premises, the borrower having little to no assets to provide as collateral or inefficiency in the process of registering the asset as collateral relative to the value of the loan. For example, a borrower whose only securable asset is his or her mobile phone, tablet or smart watch might have to travel to the premises of the creditor in order to hand over the communication device as collateral for a loan. For rural borrowers, this might entail a significant amount of travel. It may also leave the borrower without their communication device until the loan has been repaid. Furthermore, a borrower's location may limit the number of creditors available as lending options, resulting in poor loan tenure, available interest rates or available loan amounts. These physical limitations restrict access to the benefits of secured loans to such borrowers. Without the option of loan security, creditors in such regions might for example turn to credit scoring using network and user data, such as Call Detail Records (CDR) or Event Data Records (EDR), and the limited demographic data in the form of KYC data to determine loan eligibility and risk. These types of data may involve a vast number of records which change on an ongoing basis and usually do not follow a well-defined format. Processing for credit scoring and other uses of such records may therefore be difficult and computationally burdensome. The inefficiencies caused by a credit system requiring the physical presence of the borrower may also result in a significant lag between when the loan is needed and the loan's disbursement. This lag, coupled with the potential of being separated from his or her communication device, may cause the borrower unnecessary hardship. There is accordingly scope for improvement. The preceding discussion of the background to the invention is intended only to facilitate an understanding of the present invention. It should be appreciated that the discussion is not an acknowledgment or admission that any of the material referred to was part of the common general knowledge in the art as at the priority date of the application. SUMMARY OF THE INVENTION In accordance with an aspect of the invention there is provided a computer implemented method conducted at a server computer comprising: receiving a loan registration request including a consumer identifier associated with a consumer record and with a communication device identifier which uniquely identifies a communication device; interacting with a software module executing on the communication device to enable a lock-ready state, and receiving confirmation of the lock- ready state being enabled, wherein in the lock-ready state predefined functionality of the communication device can be disabled remotely by initiating a lock action and receiving confirmation of the lock-ready state being enabled; registering the loan against the consumer record; detecting occurrence of a first condition or a second condition associated with the loan registered against the consumer record; and, in response to detecting the occurrence of the second condition, initiating a lock action to disable the predefined functionality of the communication device. The method may include, in response to detecting the occurrence of the first condition, interacting with the software module to disable the lock-ready state. The software module may be a Unified Endpoint Management (UEM) module and wherein interacting with the software module may include interacting with the software module via a software application installed on the communication device. The method may include: receiving an initiation message from a software application installed on a communication device, the initiation message including a unique identifier; linking the communication device to a consumer record using the unique identifier; and, transmitting notification of linking the communication device to the consumer record. Interacting with the software module on the communication device to enable the lock-ready state may include transmitting a 'lock-ready' instruction message to the communication device. Initiating the lock action may include initiating locking of the communication device by causing the software module to disable predefined functionality of the communication device. Registering the loan against the consumer record may include recording a value associated with the loan product as outstanding against an account associated with the consumer identifier in the consumer record. Recording the value may include recording the value as an amount due to be repaid by the consumer. Registering the loan against the consumer record may be in response to receiving confirmation of the lock-ready state. Initiating the lock action upon detection of the occurrence of the second condition may include transmitting a 'lock' instruction to the software module which causes the software module to disable predefined functionality of the communication device. Enabling the lock-ready state may include configuring the software module to lock the device if a 'do not lock' instruction is not received within a predetermined time period. The method may include: periodically sending a 'do not lock' instruction to the communication device until occurrence of the second condition is detected; and, wherein initiating the lock action upon detection of the occurrence of the second condition may include withholding transmission of the 'do not lock' instruction so as to initiate locking of the communication device upon expiry of the predetermined time period at the communication device. Detecting occurrence of the second condition may include detecting a data element representative of one or more of the following events: missed loan repayment deadline; late loan repayment; insufficient loan repayment; unexpected interference with the software module or a software application; suspicious behaviour by the consumer on the network; and detecting loan repayment failure. Detecting loan repayment failure may include monitoring an account for a loan repayment or instalment event by a particular time and date. The method may include receiving, from the software application, data elements collected from the communication device by the software application; and for the data elements to include one or more of: a communication device identifier; a software application identifier; location data; the consumer identifier; a timestamp; and one or more third party account identifiers. The unique identifier may include or be a function of one or more of the data elements. The data elements may include an MSISDN and an IMEI, and the method may include mapping the MSISDN to the IMEI. The data elements may include a third party account identifier, and the method may include mapping the third party account identifier to one or both of the MSISDN and the IMEI. The method may include determining a net present value of the communication device; and, for determining the net present value to include using one or more of the data elements received from the software application. Determining the net present value may include querying a net present value table using one or more of the data elements received from the software application. The method may include determining loan eligibility status of the consumer associated with the consumer record. Determining the loan eligibility status may include using one or both of: the data elements received from the software application and a net present value data element of the consumer device. The method may include determining a credit limit for which the consumer associated with the consumer record is eligible; and for determining the credit limit for which the consumer associated with the consumer record is eligible to include using one or both of: data elements received from the software application and a net present value data element of the consumer device. In accordance with another aspect of the invention there is provided a system including a server computer having a memory for storing computer-readable program code and a processor for executing the computer-readable program code, the server computer comprising: a loan registration request receiving component for receiving a loan registration request including a consumer identifier associated with a consumer record and with a communication device identifier which uniquely identifies a communication device; a lock-ready state enabling/disabling component for interacting with a software module executing on the communication device to enable a lock-ready state, and receiving confirmation of the lock-ready state being enabled, wherein in the lock-ready state predefined functionality of the communication device can be disabled remotely by initiating a lock action and receiving confirmation of the lock-ready state being enabled; a loan registration component for registering the loan against the consumer record; an occurrence detecting component for detecting occurrence of a first condition or a second condition associated with the loan registered against the consumer record; and, a lock/unlock initiating component for, in response to detecting the occurrence of the second condition, initiating a lock action to disable the predefined functionality of the communication device. The system may include the communication device having a memory for storing computer- readable program code and a processor for executing the computer-readable program code, the communication device comprising: a software module for enabling a lock-ready state in which predefined functionality of the communication device can be disabled remotely; and, a disabling component for, in response to initiation of a lock action, disabling predefined functionality. In accordance with another aspect of the invention there is provided a computer program product comprising a computer-readable medium having stored computer-readable program code for performing the steps of: receiving a loan registration request including a consumer identifier associated with a consumer record and with a communication device identifier which uniquely identifies a communication device; interacting with a software module executing on the communication device to enable a lock-ready state, and receiving confirmation of the lock-ready state being enabled, wherein in the lock-ready state predefined functionality of the communication device can be disabled remotely by initiating a lock action and receiving confirmation of the lock- ready state being enabled; registering the loan against the consumer record; detecting occurrence of a first condition or a second condition associated with the loan registered against the consumer record; and, in response to detecting the occurrence of the second condition, initiating a lock action to disable the predefined functionality of the communication device. Further features provide for the computer-readable medium to be a non-transitory computer- readable medium and for the computer-readable program code to be executable by a processing circuit. In accordance with another aspect of the invention there is provided a computer-implemented method conducted at a server computer comprising: receiving an initiation message from a software application installed on a consumer communication device, the initiation message including a unique identifier; linking the communication device to a consumer record using the unique identifier; detecting occurrence of a condition associated with a loan registered against the consumer record; and, in response to detecting the condition, initiating locking of the consumer communication device by causing the software module to disable predefined functionality of the consumer communication device. Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS In the drawings: Figure 1A is a schematic diagram which illustrates a locking and loan ecosystem according to aspects of the present disclosure; Figure 1B shows a schematic diagram which illustrates a system for remote provision, disbursement and collection of secured loans according to aspects of the present disclosure; Figure 2A is a swim-lane flow diagram which illustrates an example method for remote provision, disbursement and collection of secured loans according to aspects of the present disclosure; Figure 2B is a swim-lane flow diagram which illustrates example steps for initiating locking and unlocking of a communication device according to aspects of the present disclosure; Figure 3 is a flow diagram which illustrates an example method of determining a risk profile associated with the consumer; Figure 4 is a block diagram which illustrates exemplary components which may be provided by a system for remote provision, disbursement and collection of secured loans according to aspects of the present disclosure; Figure 5 illustrates an exemplary timeline showing different recovery and collection stages according to aspects of the present disclosure; and Figure 6 illustrates an example of a computing device in which various aspects of the disclosure may be implemented. DETAILED DESCRIPTION WITH REFERENCE TO THE DRAWINGS Aspects of the present disclosure relate to a system and method for remote provision, disbursement and collection of secured loans. Aspects of the present disclosure further relate to a system and method for remotely locking a communication device in response to detecting a condition. One example of a condition may be failure to comply with loan repayment terms and conditions. Aspects of the present disclosure provide receiving, at a server computer, an initiation message from a software application installed on a consumer communication device. The initiation message may include a unique identifier which uniquely identifies one or more of: the communication device, software application installed on the communication device, and the consumer. The unique identifier may be used to link the communication device (or the software application executing on the communication device) to a consumer record. The method further includes detecting the occurrence of a condition associated with a loan registered against the consumer record. In some cases, the condition may for example include a consumer defaulting on loan payments, only making part payment of a personal loan, etc. If the condition is detected, a lock instruction may be transmitted to the software application. This lock instruction may cause the software application to lock or disable predefined functionality of the consumer communication device. For example, in some cases, the lock instruction may lock call functionality on the device thereby preventing a consumer to make phone calls, possibly apart from emergency calls. In some cases, the lock instruction may disable access to social media accounts via the consumer communication device when the condition is detected. In some cases, the consumer communication device may be locked or disabled completely, apart from functionality allowing the consumer to remedy the condition (e.g. to make the overdue payment). Figure 1A is a schematic diagram which illustrates a high-level representation of a locking and loan ecosystem (1) according to aspects of the present disclosure. The ecosystem (1) includes a network domain (3), a web domain (5), a device domain (7) and a locking domain (9). The ecosystem (1) leverages these domains to provide remote device mortgaging (11) as described herein. For example, the network domain (3) may be used to associate a user to a unique mobile number, location, call and data trends and the like. This may for example enable mapping a unique network ID to a user and/or to a device. Other User IDs may also be used, such as Facebook ID or similar. The web domain (5) may be used to identify all key information that can project the real value of a user's device through a number of sites and links. It may also be used for user scoring in combination with user data. The device domain (7) includes system and data extracted from a user's device after receiving the user's permission. Such data may be used to identify the device model and interconnect with hardware for user identification (for example fingerprint or face unlock IDs). The locking domain (9) provides a locking solution environment in which the device will operate depending on the manufacturer and vendor that is used. This domain may include applications used, cloud administrative systems, hardware locking setup and the like. The domains could be considered descriptors under which the components of this disclosure may reside. An example locking and loan ecosystem for remote provision, disbursement and collection of secured loans is illustrated in Figure 1B. The system (100) may include a service provider platform (102) and a mobile network operator (MNO) platform (104). The system is one example implementation of the ecosystem (1) described above with reference to Figure 1A. Other implementations may have other arrangements of hardware and software. In some embodiments the system may include a third party credit provider (105) from which a consumer may request a loan or purchase products or services on credit. The third party credit provider (105) may be a financial institution, such as a bank, a merchant, or the like and may include a platform via which the third party credit provider may interface with one or both of the service provider platform (102) and the MNO platform (104). Although only one third party credit provider is shown, it should be appreciated that in a practical implementation there may be a plurality of each of these. The service provider platform (102) may be provided by a third-party service provider which provides services to an MNO and its subscribers (being consumers). In other implementations, the functionality of the service provider platform may be incorporated into the MNO platform. The MNO platform (104) may be provided by an MNO which maintains and provides mobile subscribers with access to a communication network (110). The system (100) may further include communication devices (106), such as mobile handsets, associated with mobile subscribers who subscribe to the MNO and make use of the communication network (110). The service provider platform (102) may be provided by any suitable computing device and configured to interface with the MNO platform (104) and the third party credit provider (105). For example, the service provider platform may be configured to interface with an intelligent network (IN) (112) and/or charging system (114) of the MNO platform (104) via an appropriate IN integration component. Interfacing with the IN (112) and/or charging system (114) may enable the service provider platform (102) to access and update selected data records stored therein. The service provider platform (102) may be in communication with the communication devices (106) via the communication network (110) via which data and/or messages may be transmitted to and received from the respective communication devices (106). The service provider platform (102) may for example be configured to receive loan requests from the communication devices (106) and to transmit notifications relating to the loan requests to the communication devices (106). The MNO platform (104) and communication network (110) may collectively provide the infrastructure by way of which communication devices (106) can communicate with each other and the broader public switched telephone network (PSTN) and the Internet. The communication network (110) may for example include one or more base station subsystems while the MNO platform (104) may provide back-end systems such as a USSD/GPRS gateway, SMSC and associated components (VLR, HLR, etc.). The MNO platform (104) may include an Intelligent Network (IN) (112), a charging system (114) and a mobile wallet platform (116). The mobile wallet platform (116) may be configured to manage mobile wallets (117) on behalf of subscribers and provide functionality by way of which individual subscribers can transact against their wallets, for example by storing, transferring and withdrawing money, paying merchants, utility providers and other beneficiaries and optionally use and access other financial services. The mobile wallet platform (116) may include a designated channel via which the mobile wallet platform interfaces with the communication network (110) and in turn the communication devices (106) of individual subscribers. The designated channel may provide access to the mobile wallet platform via SMS, IVR, USSD, software application or web channels. The mobile wallet platform (116) may transmit and receive data and/or messages to and from the respective communication devices (106) via the designated channel and the communication network (110). The mobile wallet platform (116) may for example be configured to receive requests and/or instructions from the communication devices (106) via the designated channel and to transmit offers and/or notifications to the communication devices (106) via the designated channel. The mobile wallet platform (116) may have access to and/or maintain a wallet database in which individual mobile wallets (117) are stored. Each mobile wallet (117) may be associated with a subscriber (or consumer) identifier and may store balance and/or transaction information. Each mobile wallet (117) may be configured for transacting against by its associated subscriber via the designated channel to enable the mobile wallet platform functionality. The IN (112) may be implemented according to any suitable network architecture (e.g. that specified in the ITU-T Q.1200 series recommendations, or the like). The IN (112) may allow the MNO to provide various value-added services, such as network usage advance services, in addition to the standard telecom services such as PSTN, GSM, etc. The IN (112) may include one or more network nodes on the service layer, distinct from the switching layer of the core network, as opposed to solutions based on intelligence in the core switches or equipment. The IN (112) may be supported by the Signalling System #7 (SS7) protocol between network switching centers and other network nodes owned by network operators. The charging system (114) may be implemented as a node within the IN (112) that is responsible for collecting data on service usage and to generate reports thereon for billing, either on demand or automatically. In some implementations, the charging system (114) may be an online charging system (OCS). The charging system (114) may be implemented as a high-throughput database that maintains multiple accounts for each subscriber. The purpose, type and usage of the accounts may be defined by the MNO. The system may include a net present value (NPV) database (130) in which an NPV table (131) providing an NPV associated with each consumer communication device (106) is stored. The NPV database (130) may be accessible to one or more of: the service provider platform (102), mobile network operator platform (104) and third party credit providers (105) via the communication network (110). The NPV table (131) may be updated continually such that an NPV for each communication device (106) is updated continually. In some embodiments, the MNO platform (104) may maintain the NPV database (130) while in other embodiments it (130) may be maintained by the service provider platform (102) or another entity. Each communication device (106) may have an NPV associated therewith which may be determined based on one or more of the make, model, age of the device and number of years owned by the consumer. This NPV may be stored in the NPV table (131). By, for example, using the device identifier, the NPV associated with the communication device (106) may be determined or obtained from the NPV table (131). In other indications, other device characteristics may be used to determine an NPV for a consumer communication device (106) (e.g. by querying the table using device make, model and age). The NPV may be a good indication of a credit score or a loan eligibility status of a consumer. For example, the NPV gives the value of the communication device (106), and therefore the value of the collateral for the loan. Accordingly, the NPV table (131) may be useful in determining a credit score and loan eligibility associated with a consumer. For example, by using the NPV table (131), the need for performing credit scoring operations may be reduced substantially. Performing credit scoring operations may be very computationally intensive due to large scale data sets having to be processed. Therefore, by using an NPV table (131), the process of determining a credit score of each consumer may be improved and more efficient. The service provider platform (102) may be provided by any suitable computing device or devices and may for example include a server computer (120). The service provider platform (102) and/or the server computer (120) may be configured to interface and/or integrate with the MNO platform (104), for example the intelligent network (112) and the mobile wallet platform (116). For example, the server computer (120) may be configured to interface with the mobile wallet platform (116), intelligent network (IN) (112) and/or charging system (114) of the MNO platform (104) via an appropriate front-end API, an appropriate IN integration component or the like. The service provider platform (102) and/or the server computer (120) may for example be able to transact against mobile wallets (117) maintained by the mobile wallet platform (116) and adjust account balances of accounts stored in the charging system (114). In some embodiments, the service provider platform (102) may be configured to interface and/or integrate with the third party credit provider (105) via, for example, an appropriate API. The service provider platform (102) and/or the server computer (120) may utilise IN integration for: receiving MNO related subscriber data; provisioning loan products; setting/updating/removing liens against accounts maintained by the IN; and, receiving loan payments. The service provider platform (102) may have access to a consumer database (122) in which a record (124) associated with each consumer is stored. Each consumer record (124) may include and be associated with a consumer identifier. In some implementations, each consumer record includes one or more sets of credit data, such as a credit score, an outstanding loan status, a loan eligibility, a total credit limit and the like. The credit score may be an indication of credit worthiness, or an indication of the risk associated with the consumer. A high credit score may indicate low risk while a low credit score may indicate a high-risk consumer. The total credit limit may be a total credit limit value denominated in a value of airtime or local currency. The credit limit value represents a value of a loan for which a consumer associated with the consumer identifier is eligible. The service provider platform (102) may be configured to perform credit scoring and risk management operations using data received from the MNO platform (104), the third party credit provider (105), the communication device (106) and/or other sources and to maintain and update credit data and/or risk data stored in consumer records (124) accordingly. For credit scoring and risk management, the service provider platform (102) may for example be configured to utilize/process available MNO service data and/or the credit history of the consumer from available third party credit provider data. For example, the credit score of a consumer may be determined by using data such as KYC (know your customer) data, timestamps associated with consumer registration and other third party systems such as a Google ID. The consumer communication device (106) may be any suitable electronic device with a communication functionality, such as a mobile handset (e.g., a feature phone, a smartphone, tablet computer, etc.), a desktop or laptop computer, a wearable computing device, a smart appliance or other internet-of-things (IoT) device or the like. The consumer communication device (106) may be uniquely identifiable by way of a communication device identifier. The communication device (which may also be termed a 'connected device') (106) may be configured to enable a consumer to install a software application on the device. The software application may have a software application identifier for uniquely identifying the software application. The consumer may be required to enrol the software application to access some of its functions. The consumer may be required to provide consent to the software application to obtain data elements associated with the consumer. The data elements may include one or more of: a consumer communication device identifier (such as an international mobile equipment identity (IMEI), a media access control address (MAC address), or other suitable hardware identifier); a software application identifier; location data; a consumer identifier (such as MSISDN or an international mobile subscriber identity (IMSI)); a timestamp; and, one or more third party account identifiers (such as a Google^ ID, Facebook^ login details, etc.). In some instances, a third party account identifier may be provided or used as a consumer identifier. The software application may include a Unified Endpoint Management (UEM) module (which may also be termed a mobile device management module), or at least have access to a UEM module executing on the communication device. The UEM module may be configured for remote locking or disabling of predefined functionality of the consumer communication device (106) upon instruction by the service provider platform (102). The UEM module may also be configured to allow unlocking or enabling of the predefined functionality upon instruction from the service provider platform. In the present embodiment the UEM module is provided by the software application; however, it should be appreciated that in an alternative embodiment the UEM module may be a component of another software application, or it may be a component of the operating system of the communication device (106). The software application may operate to configure the communication device (106) on which it is installed to operate under a certain policy, which enables remote locking in the event of the detection of a first or second condition. This may not require real-time communication with the device as it is for example in offline locking condition. Some conditions may be set online and run due to events occurring. The software application may include or be provided by an SDK (software development kit). The SDK may be configured to provide the locking functionality of the software application in response to detecting a predetermined condition. The SDK may be built into a third party application such as a mobile banking application to which the consumer has access. The software application may be linked to a particular consumer record and consumer account. The software application may be configured to display the consumer account, or the one or more sub accounts, to the consumer via the communication device and enable a consumer to select a sub account to which he/she would want a loan to be provisioned. For example, the consumer may select an account, such as a mobile wallet account, network usage account, bank account, or the like, from the list of accounts displayed to the consumer. In some embodiments the consumer may provide details, such as an account number, of the account to which he or she may want the loan to be provisioned. The account details provided may be verified by consulting one or more of the consumer record, the third party credit provider and the MNO platform. The system (100) described above may implement a method for remote provision, disbursement and collection of secured loans. In use of the system, the consumer agrees to offer his or her device as collateral, thus entering the device into a lock-ready state. Locking of the device may only be applied in cases where a loan is approved, disbursed and then not paid or missed payments by the consumer. An exemplary method of remotely locking the communication device in response to detecting a condition is illustrated in the swim-lane flow diagram of Figure 2A, in which respective swim-lanes delineate steps, operations or procedures performed by respective entities or devices. The delineation illustrates one example embodiment and in other embodiments other delineations may be applied. The service provider platform (102) may provide the consumer communication device (106) with access to a software application. The software application may be downloaded onto the communication device (106) by clicking on a link, visiting an online store, such as Google Play^, or the like. Alternatively, the application may be pre-installed on the communication device (106) when the device is purchased. A consumer may use his or her communication device (106) to install the software application on his or her device. The software application may include or have access to a UEM module configured to provide remote locking or disabling of predefined functionality associated with the communication device (106). The UEM module may also be configured to allow unlocking or enabling of the predefined functionality when required. During initial use of the software application the consumer may be required to register or link the software application to a consumer record. The consumer may further be required to provide KYC information (e.g., the date a consumer joined a Mobile Network, consumer location, etc.) during a registration process, which is a standard requirement for credit applications. The KYC information may be verified by means of one or more third-party systems. At any stage after installation, the software application may collect (201) data elements from the consumer communication device (106). The data elements may include one or more of: a communication device identifier which uniquely identifies the consumer communication device; a software application identifier; location data; a consumer identifier; a timestamp; and, the one or more third party account identifiers (such as a Google ^TM ID). The data elements may be transmitted (202) to the service provider platform (102) in the form of a payload. The data elements may be received (203) by the service provider platform (102). The method may include linking/mapping the consumer identifier to the device identifier so as to associate the consumer with the communication device (106). The third-party account identifier may be mapped to one or both of the consumer identifier and the device identifier. The third-party account identifier may include information regarding the consumer which may be used to determine a credit score and risk associated with the consumer as will be explained in more detail below. The communication device (106) may transmit (204) an initiation message to the service provider platform (102). The initiation message may include a consumer identifier uniquely identifying the consumer and a unique identifier which may include one or both of the communication device identifier and a software application identifier. The service provider platform (102) may receive (205) the initiation message and link (206) the communication device (106) to the consumer record by using the unique identifier and the consumer identifier. In some embodiments, linking (206) the communication device (106) includes linking the software application executing on the communication device (106) to the consumer record. In some implementations, the initiation message may include the data elements and/or the data elements may include the unique identifier. The service provider platform (102) may link (206) the communication device/software application to the consumer record by, for example, storing the unique identifier in the consumer record. A particular consumer record, and therefore the consumer, may be associated with the communication device (106) and/or the software application executing on the communication device (106) by means of the unique identifier. The method may include transmitting notification of linking the communication device (106) to the consumer record. The notification may be transmitted to the consumer communication device (106) and/or the entities who may provision loan products to the consumer. Steps (201) through to (206) may form part of an enrolment procedure of the software application with the service provider platform. Such enrolment may be required for a user to request and receive provision of a loan. Enrolment may be confirmed by checking the consumer record for linking to the consumer communication device and/or software application executing thereon. At some later stage, the consumer may request a loan from either the MNO platform or a third party credit provider. The MNO platform and/or one or more credit providers may, subject to their own respective authorisation process, either accept or refuse the loan request from the consumer. If the loan request is accepted either the MNO or the third party credit provider, whichever the lender may be, may provision the loan to the relevant consumer account. The MNO platform or third party credit provider may notify the service provider platform (102) that a loan has been provisioned to the relevant consumer account, for example by transmitting to the service provider platform (102) a loan registration request including notification of provisioning (or intended provisioning) of a loan product to the consumer. The service provider platform (102) may for example receive (208) a loan registration request. The loan registration request may be received from, for example, any one of: the MNO platform; a third party credit provider (e.g. a device of a loan agent, a device of a call centre agent, etc.); the consumer communication device (106) (or from the software application executing thereon); or the like. The loan registration request may include one or both of: the consumer identifier associated with the consumer record (and with hence with the communication device identifier) and the communication device identifier. The service provider platform (102) may interact (210) with a software module executing on the communication device (106) to enable a lock-ready state in which predefined functionality of the communication device (106) can be disabled remotely by initiating a lock action. The communication device (106) may confirm (212) to the service provider platform (102) that the lock-ready state is enabled. The software module may be the UEM module and interacting with the software module may include interacting with the software module via a software application installed on the communication device (106). This may include transmitting a lock-ready instruction to the device (106) which receives and executes the instruction to enable the lock- ready state. The lock-ready state may be a state in which the device (106) can lock or disable predefined functionality in response to the service provider platform (102) initiating locking. In some embodiments, the device may only be set into a lock-ready state upon the provision of a loan, while in other cases provision of the loan may be contingent on the device being in a lock ready state. The method may include transmitting notification of enabling/setting of the lock-ready state. The notification may be transmitted to the consumer communication device and/or the entities who may provision loan products to the consumer. The service provider platform may register (214) the loan against the consumer record. Registering the loan may be in response to one or more of: receiving the loan registration request; receiving confirmation of the lock-ready state being enabled; and, receiving the notification of, or otherwise detecting, provisioning of the loan product to the consumer. Registering the loan against the consumer record may include recording (216) a value associated with the loan product as outstanding against an account associated with the consumer identifier in the consumer record. Recording the value may include recording the value as an amount due to be repaid by the consumer. The value associated with the loan product may include a fee portion and a principal portion corresponding to the value of the loan product provisioned to the consumer. In other implementations the loan product may include a principle portion and interest corresponding to the loan value, as described in more detail below. In some embodiments, the service provider platform (102) may detect and record a value associated with a loan product, provisioned to the consumer, as outstanding against an account associated with the consumer identifier in the consumer record. In some cases the software application may be configured to detect when a loan has been provisioned to the consumer and update the relevant consumer record. In some implementations the consumer may request the loan via the software application installed on the communication device. Requesting the loan may include the consumer selecting an account to which he or she wants the loan to be provisioned. It should also be appreciated that in some embodiments the MNO platform or the third party credit provider may have access to the consumer record maintained by the service provider platform or vice versa. This may allow the MNO platform or the third party credit provider to register the loan against the consumer record, update the sets of credit data in real time, etc., and may eliminate the need to inform the service provider platform (102) of any activity, such as newly provisioned loans, outstanding loan payments, loan payments, etc. If the device (106) has not yet been set in a lock-ready state, the method may include setting the device (106) into a lock-ready state in response to the recording of the outstanding value associated with the loan product. The method may include transmitting an instalment reminder from the service provider platform (102) to the communication device (106) to remind the consumer to pay loan instalments due. The reminders may be in the form of push notifications received via the software application executing on the consumer communication device (106), or it may be in the form of data messages, SMS messages or the like received from the service provider platform (102). The instalment reminders may be transmitted to the consumer communication device (106) at pre- defined intervals which may be calculated from the time and date at which the loan offer was accepted or when the loan product was provisioned. At some stage, the service provider platform (102) may detect (220) the occurrence of either a first condition or a second condition associated with the loan registered against the consumer record. The conditions may be predefined. Detecting (220) the occurrence of the condition may include the service provider platform (102) receiving a notification from the MNO platform or the third party credit provider that the condition (first or second, as the case may be) has occurred. In some embodiments the method may include monitoring the consumer account and/or consumer record in order to determine if a first or second condition has occurred. In some embodiments, the method may also include monitoring interactions with the communication device so as to detect unexpected interference or suspicious behaviour on the network. The interactions may include interactions by the consumer. Unexpected interference may include any interference: malicious, intentional or accidental, which unexpectedly reads, transfers, delays, blocks or changes one or more of: instructions, data or communication protocol associated with the steps in the method. Suspicious behaviour may include any activity considered beyond the ordinary scope of use, implementation or maintenance. Events which constitute unexpected interference and suspicious behaviour may be designated by a predefined list or derived by machine learning techniques. Detecting occurrence of the first condition may include detecting that the outstanding value of the loan has been repaid in full. In response to detecting (220) that the first condition has occurred, the service provider platform may interact (222) with the software module to disable the lock- ready state. The communication device (106) may confirm (224) disabling the lock-ready state to the service provider platform (102). In this way, upon loan closure, when there is no outstanding payment left, the communication device (106) may be released and the UEM module of the communication device (106) may be deactivated. Detecting occurrence of the second condition may include detecting one or more of the following example conditions: missed loan repayment deadline; late loan repayment; insufficient loan repayment; unexpected interference with software application; suspicious behaviour on the network; and the like. In response to detecting (220) that the second condition has occurred, the method may include initiating a lock action to disable the predefined functionality of the communication device. This may include initiating locking (230) of the consumer communication device. Initiating locking of the communication device causes the communication device to lock (232) predefined or all functionality such that the communication device (106) is unusable or substantially unusable to the consumer. The predefined functionality may include one or more of making and receiving of phone calls, sending and receiving messages, browser functionality, initiating or use of predefined software applications, predefined functionality of the software application and the like. In some embodiments, the lock instruction is transmitted to the software module via a UEM protocol. In some implementations the service provider platform (102) may continuously monitor the consumer account and/or consumer record to determine if the loan product has been repaid, or at least partially repaid. If the loan product has been repaid, the service provider platform (102) may initiate unlocking (234) which may cause the communication device to unlock (236) the predefined functionality. It should also be appreciated that with partial repayment of the loan product, certain predefined functionality may be restored while other remain locked or disabled until the full loan product has been repaid. In some implementations monitoring the consumer account and/or consumer record may include determining if the second condition associated with the loan registered with the consumer record persists past an allowed grace period before initiating locking. It should further be appreciated that locking the communication device (or predefined functionality thereof) may not prevent the consumer from accessing payment systems, such as banking apps or a mobile wallet, to allow the consumer to repay the loan during the period in which the predefined functionality is at least partially locked or disabled. The method may include updating or determining a credit score or risk profile associated with the consumer using advanced credit and scoring algorithms to predict with high accuracy the probability that a consumer will default on a loan or a credit service. For example, a credit score associated with a particular consumer may be determined by using data elements and/or other data associated with the consumer retrieved from other data stores (e.g. telco data retrieved from the MNO). Credit scoring models can be developed following statistical, machine learning and artificial intelligence methods and are selected based on their performance. The credit scoring model can then be used to calculate the credit score of each consumer and assign an appropriate credit limit to each consumer. When provided the credit score, multiple ways can be used to assign a credit limit. For example, consumers with a higher credit score (and therefore more credit worthy) will receive a higher credit limit, while consumers with a lower score will receive a lower credit limit. Consumers with the lowest score may not be allowed to borrow. The credit score may be determined in response to a loan request from a consumer. Alternatively, in some embodiments, the credit score may be determined upon registration of the consumer and updated or simply recalled from the consumer record when a loan is requested. It should also be appreciated that the credit score may be determined by the third party credit provider or the MNO platform and stored in the consumer record. The service provider platform (102) may obtain the credit score of the consumer by accessing the consumer record. The service provider platform (102) may further also determine whether a consumer is eligible for a loan by determining a loan eligibility status (described in more detail below). In some embodiments, referring now to Figure 2B, initiating locking (230) of the consumer communication device includes transmitting (256) a lock instruction from the service provider platform (102) to the software application executing on the consumer communication device (106). The lock instruction may be an instruction which causes the software application to lock or disable (258) predefined functionality of the consumer communication device (106). In some embodiments transmitting (256) the lock instruction to the software application may include transmitting a lock instruction via a UEM module and a corresponding UEM protocol. The UEM module receives the instruction and relays the instruction to the communication device (106) via the UEM protocol to cause locking or disabling (258) of the predefined functionality of the communication device (106). In some embodiments the UEM module may require verification of the communication device (106) prior to locking or disabling (258) of the predefined functionality. The communication device (106) may be verified at the service provider platform (102) by means of a payload received from the software application. In response to verifying the communication device (106), the service provider platform (102) may transmit (256) the lock instruction to the UEM protocol. The consumer communication device (106) may receive (257) the lock instruction and lock or disable (258) the predefined functionality. Receiving (257) the lock instruction and locking or disabling (258) the predefined functionality may include interacting with the UEM module so as to lock the communication device (106) and disable the predefined functionality. If a lock instruction to disable the predefined functionality is received (257), the communication device (106) may transmit location information, such as geographic location data, of the communication device (106) to the service provider platform (102). The location information may be transmitted to the service provider platform (102) at pre-defined intervals. Transmitting the location information to the service provider platform (102) may facilitate recovery of the device by the service provider. For example, the service provider may want to recover the communication device (106) in response to failure of the consumer to make timeously loan payments. Once the loan product has been repaid (or the second condition has diminished), the service provider platform (102) may transmit (260) an unlock instruction to the software application executing on the communication device (106). The communication device (106) may receive (262) the unlock instruction and unlock or enable (264) the predefined functionality so as to restore the communication device to its normal functionality. In other embodiments, setting the device in a lock-ready state may include configuring the software application to lock the device if a 'do not lock' instruction is not received within a predetermined time period. In such an embodiment, the method may include periodically sending a 'do not lock' instruction to the consumer communication device (e.g. daily, hourly, or the like) until occurrence of the second condition is established. Upon detection of the occurrence of the second condition, the method may include withholding transmission of the 'do not lock instruction' so as to initiate locking of the consumer communication device upon expiry of the predetermined time period at the consumer communication device. This may enable initiating locking of the communication device if it is offline (e.g. if the consumer takes the device off line in anticipation of locking as a result of loan repayment defaulting). As mentioned, aspects of the present disclosure provide for determining whether a consumer is eligible for a loan by determining a loan eligibility status. An exemplary method (300) of determining a risk profile associated with a consumer is illustrated in the flow diagram of Figure 3. The method may be conducted by the service provider platform (102). The method may include receiving (302) data elements from a consumer communication device (106) and storing the data elements in a record (124) associated with the consumer. The method (300) may include determining (304) the credit score associated with the consumer. Determining the credit score associated with the consumer may include determining (306) a net present value (NPV) of the communication device (106). Determining (306) the NPV of the communication device (106) may include using one or more data elements received from the software application. In some implementations determining (306) the NPV may include querying the NPV table (131) maintained by the MNO platform (104) using the one or more data elements. For example, by using the device identifier, the NPV corresponding to the communication device (106) may be determined using the NPV table (131). The method (300) may include updating the NPV in response to detecting a change of the NPV in the NPV table (131), or in response to receiving a notification from the MNO platform (104) that the NPV associated with the communication device (106) has been updated. In some implementations the credit score may be dynamically updated based on a change in the NPV of the communication device (106) maintained in the NPV table (131). For example, each year the NPV of the communication device (106) may be reduced as the communication device (106) becomes older and more obsolete. In some implementations the credit score may be updated based on behavioural characteristics of the consumer. For example, a consumer may be rewarded for positive behaviour, such as maintaining a short loan recovery time, by increasing the consumer score. Updating the credit score may include updating the consumer record (124) associated with the consumer. The method (300) may include determining (308) a loan eligibility status of a consumer associated with the consumer record. In some embodiments, determining loan status eligibility includes determining loan eligibility as a yes/no rule and may form a part or condition of determining the credit score. Determining (308) the loan eligibility status of a consumer may include using one or both data elements received from the software application and an NPV data element of the consumer communication device. In some implementations an NPV which is too low may result in a consumer not being eligible for a loan as the security offered by the device (106) is of too little value. The data elements may be used to access the consumer record providing information, such as other ongoing loans associated with the consumer, which may also influence the loan eligibility of the consumer. The method (300) may further include determining (310) a credit limit for which the consumer associated with the consumer record is eligible. Determining (310) the credit limit may include using one or both of data elements from the software application and the NPV of the consumer communication device (106). The higher the credit score determined, given the NPV and data elements, the higher the credit limit for which the consumer is eligible and vice versa. It should further be appreciated that in some embodiments the method may include re-evaluating the maximum loan limit amount in response to a change in the credit score. For example, if the NPV of the consumer communication device changes, the credit score and therewith the maximum loan limit, may be updated accordingly. In some embodiments the maximum credit limit for which the consumer is eligible may be based on the NPV. In such an embodiment the communication device (106) effectively serves as collateral for the loan. The method (300) may include storing (312) the credit score, loan eligibility status and/or credit limit in the consumer record (124) for subsequent retrieval for provisioning of a loan product. For example, in some embodiments the service provider platform (102) may retrieve one or more of the credit score, loan eligibility status and credit limit in order to determine a loan product should be provisioned to a consumer in response to a loan request from the consumer. The credit score, loan eligibility status and/or credit limit, which may be used to determine the risk profile, may for example determine how frequently loans may be requested by a particular consumer. It may also enable the service provider platform to inform a third party, such as a credit provider, of the likelihood that the consumer would pay back the loan product within an allocated period and adhere to the terms of the loan, etc. Various components may be provided for implementing the methods described above. Figure 4 shows a block diagram which illustrates exemplary components which may be provided by a system (400) for remote provision, disbursement and collection of secured loans. The system includes a server computer (120), which may form part of a service provider platform or an MNO platform, depending on the implementation. The server computer (120) may include a processor (402) for executing the functions of components described below, which may be provided by hardware or by software units executing on the server computer (120). The software units may be stored in a memory component (404) and instructions may be provided to the processor (402) to carry out the functionality of the described components. In some cases, for example in a cloud computing implementation, software units arranged to manage and/or process data on behalf of the server computer (120) may be provided remotely. The server computer (120) may include an initiation message receiving component (406) arranged to receive an initiation message from a software application installed on a consumer communication device (106). The initiation message may include a unique identifier which includes one or both of a communication device identifier which uniquely identifies the communication device (106) and a consumer identifier for uniquely identifying the consumer. The server computer (120) may include a linking component (408) arranged to link the consumer communication device (106) and/or software application executing thereon to a consumer record using the unique identifier. Linking the software application to a particular consumer record may enable monitoring of data elements associated with the particular consumer record via the software application. The server computer (120) may include a loan registration request receiving component (409A) arranged to receive a loan registration request including a consumer identifier associated with a consumer record and with a communication device identifier which uniquely identifies a communication device. The server computer may include a lock-ready state enabling/disabling component (409B) arranged to interact with a software module executing on the communication device to enable or disable a lock-ready state in which predefined functionality of the communication device can be disabled remotely by initiating a lock action and receiving confirmation of the lock-ready state being enabled. The server computer may include a loan registration component (409C) arranged to register the loan against the consumer record. The server computer (120) may include an occurrence detecting component (410) arranged to detecting occurrence of a first condition or a second condition associated with the loan registered against the consumer record. The server computer (120) may include a lock/unlock initiating component (412) arranged to, in response to detecting a second condition, transmit a lock instruction to the software application. The lock instruction may cause the software application to lock or disable predefined functionality of the consumer communication device (106). In some implementations, the linking component (408) and the lock/unlock initiating component (412) may be provided by a UEM module (414) configured as a UEM server for implementing a UEM protocol (416) between the service provider platform and the consumer communication device (106). The UEM protocol (416) may provide a way for the service provider platform to transmit device management instructions to the communication device. The UEM protocol (416) may allow the server computer (120) to cause locking or disabling of the predefined functionality. For example, the UEM protocol (416) allows the server computer (120) to inspect, install, remove profiles, remove passcodes and begin secure erase on the communication device. The UEM protocol (416) may be built on top of Hypertext Transfer Protocol (HTTP), Transport Layer Security (TLS/SSL), and push notification type communications and may include a check-in protocol which may be configured to delegate registration to a separate system. The system may further include a consumer communication device (106). The communication device (106) may include a processor (502) for executing the functions of components described below, which may be provided by hardware or by software units executing on the communication device. The software units may be stored in a memory component (504) and instructions may be provided to the processor (502) to carry out the functionality of the described components. In some cases, for example in a cloud computing implementation, software units arranged to manage and/or process data on behalf of the communication device (106) may be provided remotely. The communication device (106) may include a software application (505) installed on the device. The software application (505) may be configured to interface with the service provider platform, the MNO platform and/or the one or more loan credit providers. The software application (505) may include an initiation message transmitting component (506) for transmitting an initiation message including a unique identifier to a server computer (120). The software application may include a payload transmitting component (507) for transmitting a payload including data elements to the server computer (120). The software application may include a lock instruction or 'do not lock' instruction receiving component (508) arranged to receive instructions from the server computer (120) for initiating locking of the communication device (106). A lock instruction may be received in response to the server computer (120) detecting a condition associated with a loan registered against the consumer record. A 'do not lock' instruction may be associated with a time to live and may be received periodically to prevent the communication device from automatically locking. The software application (505) may include a locking or disabling component (509) arranged to, in response to receiving a lock instruction or in response to not receiving a 'do not lock' instruction within a predetermined time interval, as the case may be, lock or disable predefined functionality of the communication device (106) until an unlock instruction is received from the service provider platform (102). The communication device (106) may further include a UEM module (510) arranged to enable remote locking or disabling of the predefined functionality. The UEM module (510) may be arranged to enable and disable a lock-ready state in which predefined functionality of the communication device can be disabled remotely in response to the server computer initiating a locking action. The UEM module may be a UEM software module which may execute on the communication device. The UEM module may enable the server computer (120) to manage and control at least certain functionality of the communication device. For example, the UEM module may enable the service provider platform to block/lock certain applications to run on the communication device (106), restrict access to certain predefined web servers and prevent the sharing of documents and data. In the present embodiment the server computer (120) may interface with the UEM module, via the software application or directly, as the case may be, and cause locking or disabling of functionality in response to determining a condition associated with the loan registered against the consumer record. In some embodiments the UEM module may be provided by the operating system (OS) of the communication device (106). For example, the UEM module may be a component of the OS of the communication device that enables a corresponding UEM protocol (416) (which may include one or more of a Mobile Device Management (MDM) protocol, a Mobile Application Management (MAM) protocol, an Enterprise Mobility Management (EMM) protocol or the like). Some communications (e.g. lock/disable instructions, initiation messages) between the software application and the server computer may be via the UEM module (510) and the corresponding UEM protocol (416). The UEM module (510) may communicate with the server computer's (120) UEM module (414) via the UEM protocol (416). The systems and methods described herein enable remote provision, disbursement and collection of secured loans. The systems and methods described herein may further enable remotely locking a communication device in response to detecting a condition associated with a loan. The systems and methods described herein may reduce the steps required to provide security or collateral for a loan, especially to consumers in remote areas, which may in turn lead to more loan requests from consumer and therefore generate higher fees from interest and fee payments. Recovery options and/or efficiency may also be improved as the loan value can be recovered from the mobile wallet or an account in the IN. The following strategy may be deployed to recover maximum outstanding: · Instalments: Based on the risk profile of the consumer, he/she may be offered instalments to repay the outstanding amount. · User Initiated Payments: the consumer will be able to pay for any outstanding loan amount using the payment functionality available on the software application installed in the communication device. The user will be able to self-initiate the following: · Full Payment (Early Loan Closure): At any time during the loan lifecycle, the consumer will have flexibility to pay all the outstanding amount and close the loan. The consumer will receive a notification for the transaction. · Partial Payment: At any time during the loan lifecycle, the consumer will have flexibility to pay a partial amount. This will be adjusted with based on the outstanding amount. The consumer will receive notifications regarding the updated outstanding loan amount. The consumer will receive notification for the transaction. · Instalment Payment: On the instalment due date the consumer can pay the instalment amount. The consumer will receive notification for the transaction. · Auto-Debit / Direct Debit and Lien: The consumer's repayment account may be auto/direct debited before the maturity/end-date, as per the loan terms, or a lien may be applied on the repayment account. It should be appreciated that the consumer may confirm a repayment method from a selection of available options. For example, the consumer may select to repay the loan provisioned by using a debit/credit card associated with the consumer, an online banking application or a mobile wallet. The service provider may in some implementations use various collection strategies in order to facilitate collection of the outstanding loan amount before the maturity/end-date as per the loan terms. This may include auto/direct debit transactions against the consumer account or applying a lien on the loan account associated with the consumer. A loan request once successfully processed and provisioned goes through different recovery and collection stages, depending on the repayment behaviour of the consumer, as shown in Figure 5. The fees and the consumer payment notifications may be based on these loan lifecycle stages. In an example embodiment, each loan product, depending on the stage of the loan cycle, may have the following fee structure and periods: · Service Fee (also referred to as a setup, processing or origination fee): This is a fixed amount charged to the borrower for every loan. It could either be a flat amount or a percentage of the principal loan amount. The service fee is collected in addition to the principle loan amount (exclusive) and in addition to the chargeable interest. The service fee is calculated at the moment of loan disbursement and charged at the moment of loan repayment. · Loan Principal: This is the principle loan amount which may be referred to as the disbursement amount. Interest: An amount charged to the borrower, calculated by implementing the interest rate percentage to the outstanding loan balance. Interest is calculated in addition to the principal loan amount (exclusive). · Loan Tenure/ Term/ Duration (552): This is the period given to the consumer to repay a loan. It is the guaranteed period that the lending institution must offer. All other states/periods (grace, rollover, collection) are optional. · Loan Start Date (554): This is the date on which the loan amount is received in the loan account. · Loan End-Date (Maturity/Due-Date) (556): This is the date up to which the consumer agrees to repay the loan. In the case of missed payment, an auto-debit or lien may start from the end date / maturity of the loan. · Grace Period (558): This is a set length of time after the due date during which payment may be made without penalty. It is an optional period after the maturity, which is given to the user to close the loan without attracting any penalty. If the loan is not fully repaid by the expiry of the grace period, the consumer's communication device may be locked (559) as described in the foregoing. · Roll-Over Period (560): This is a period of paid extension to a due date. To''Rollover' a'loan'means to extend the'loan's'due date by paying an additional fee/penalty. The roll- over period is the extended duration after the grace period. A consumer may be offered multiple roll-over periods. · Roll-Over Fee / Penalty: This is an additional fee / penalty charged to the borrower for not clearing the debt on time. The fee is charged at the start of each roll-over period. This fee could be a flat amount or percentage of the outstanding principal loan amount. · Roll-Over Interest: This is the interest charged on the outstanding principal loan amount during the roll-over period. · Collection Period (562): This is the period which starts after roll-over. During the collection period, the consumer is not charged any further fee/interest, however the lender/service provider keeps trying to recover the outstanding loan amount. An integrated communication strategy may be implemented to deliver loan product notifications to the consumer across available access/service channels, for collecting the outstanding payment over the loan duration. Product event triggers may include: loan request submitted; UEM profile activation or extended and loan provisioning; payment reminder (x days prior to anniversary or due date); payment request submitted (consumer-initiated); payment processed (successful or unsuccessful) for all payment or collection events; loan maturity alert; grace period start and end; rollover penalty alert (x days prior); rollover start (penalty event) and end; and default. The terms 'borrower,' 'consumer' and 'subscriber' are used interchangeably herein, and all should be construed to mean an end-user of the systems and methods described herein who makes use of the loans and other such financial products via their associated communication device. Figure 6 illustrates an example of a computing device (600) in which various aspects of the disclosure may be implemented. The computing device (600) may be embodied as any form of data processing device including a personal computing device (e.g. laptop or desktop computer), a server computer (which may be self-contained, physically distributed over a number of locations), a client computer, or a communication device, such as a mobile phone (e.g. cellular telephone), satellite phone, tablet computer, personal digital assistant or the like. Different embodiments of the computing device may dictate the inclusion or exclusion of various components or subsystems described below. The computing device (600) may be suitable for storing and executing computer program code. The various participants and elements in the previously described system diagrams may use any suitable number of subsystems or components of the computing device (600) to facilitate the functions described herein. The computing device (600) may include subsystems or components interconnected via a communication infrastructure (605) (for example, a communications bus, a network, etc.). The computing device (600) may include one or more processors (610) and at least one memory component in the form of computer-readable media. The one or more processors (610) may include one or more of: CPUs, graphical processing units (GPUs), microprocessors, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs) and the like. In some configurations, a number of processors may be provided and may be arranged to carry out calculations simultaneously. In some implementations various subsystems or components of the computing device (600) may be distributed over a number of physical locations (e.g. in a distributed, cluster or cloud-based computing configuration) and appropriate software units may be arranged to manage and/or process data on behalf of remote devices. The memory components may include system memory (615), which may include read only memory (ROM) and random access memory (RAM). A basic input/output system (BIOS) may be stored in ROM. System software may be stored in the system memory (615) including operating system software. The memory components may also include secondary memory (620). The secondary memory (620) may include a fixed disk (621), such as a hard disk drive, and, optionally, one or more storage interfaces (622) for interfacing with storage components (623), such as removable storage components (e.g. magnetic tape, optical disk, flash memory drive, external hard drive, removable memory chip, etc.), network attached storage components (e.g. NAS drives), remote storage components (e.g. cloud-based storage) or the like. The computing device (600) may include an external communications interface (630) for operation of the computing device (600) in a networked environment enabling transfer of data between multiple computing devices (600) and/or the Internet. Data transferred via the external communications interface (630) may be in the form of signals, which may be electronic, electromagnetic, optical, radio, or other types of signal. The external communications interface (630) may enable communication of data between the computing device (600) and other computing devices including servers and external storage facilities. Web services may be accessible by and/or from the computing device (600) via the communications interface (630). The external communications interface (630) may be configured for connection to wireless communication channels (e.g., a cellular telephone network, wireless local area network (e.g. using Wi-Fi^), satellite-phone network, Satellite Internet Network, etc.) and may include an associated wireless transfer element, such as an antenna and associated circuitry. The external communications interface (630) may include a subscriber identity module (SIM) in the form of an integrated circuit that stores an international mobile subscriber identity and the related key used to identify and authenticate a subscriber using the computing device (600). One or more subscriber identity modules may be removable from or embedded in the computing device (600). The computer-readable media in the form of the various memory components may provide storage of computer-executable instructions, data structures, program modules, software units and other data. A computer program product may be provided by a computer-readable medium having stored computer-readable program code executable by the central processor (610). A computer program product may be provided by a non-transient or non-transitory computer- readable medium, or may be provided via a signal or other transient or transitory means via the communications interface (630). Interconnection via the communication infrastructure (605) allows the one or more processors (610) to communicate with each subsystem or component and to control the execution of instructions from the memory components, as well as the exchange of information between subsystems or components. Peripherals (such as printers, scanners, cameras, or the like) and input/output (I/O) devices (such as a mouse, touchpad, keyboard, microphone, touch-sensitive display, input buttons, speakers and the like) may couple to or be integrally formed with the computing device (600) either directly or via an I/O controller (635). One or more displays (645) (which may be touch-sensitive displays) may be coupled to or integrally formed with the computing device (600) via a display or video adapter (640). The computing device (600) may include a geographical location element (655) which is arranged to determine the geographical location of the computing device (600). The geographical location element (655) may for example be implemented by way of a global positioning system (GPS), or similar, receiver module. In some implementations the geographical location element (655) may implement an indoor positioning system, using for example communication channels such as cellular telephone or Wi-Fi^ networks and/or beacons (e.g. Bluetooth^ Low Energy (BLE) beacons, iBeacons^, etc.) to determine or approximate the geographical location of the computing device (600). In some implementations, the geographical location element (655) may implement inertial navigation to track and determine the geographical location of the communication device using an initial set point and inertial measurement data. The foregoing description has been presented for the purpose of illustration; it is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Persons skilled in the relevant art can appreciate that many modifications and variations are possible in light of the above disclosure. Any of the steps, operations, components or processes described herein may be performed or implemented with one or more hardware or software units, alone or in combination with other devices. In one embodiment, a software unit is implemented with a computer program product comprising a non-transient or non-transitory computer-readable medium containing computer program code, which can be executed by a processor for performing any or all of the steps, operations, or processes described. Software units or functions described in this application may be implemented as computer program code using any suitable computer language such as, for example, Java^, C++, or Perl^ using, for example, conventional or object-oriented techniques. The computer program code may be stored as a series of instructions, or commands on a non- transitory computer-readable medium, such as a random access memory (RAM), a read-only memory (ROM), a magnetic medium such as a hard-drive, or an optical medium such as a CD- ROM. Any such computer-readable medium may also reside on or within a single computational apparatus, and may be present on or within different computational apparatuses within a system or network. Flowchart illustrations and block diagrams of methods, systems, and computer program products according to embodiments are used herein. Each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, may provide functions which may be implemented by computer readable program instructions. In some alternative implementations, the functions identified by the blocks may take place in a different order to that shown in the flowchart illustrations. Some portions of this description describe the embodiments of the invention in terms of algorithms and symbolic representations of operations on information. These algorithmic descriptions and representations, such as accompanying flow diagrams, are commonly used by those skilled in the data processing arts to convey the substance of their work effectively to others skilled in the art. These operations, while described functionally, computationally, or logically, are understood to be implemented by computer programs or equivalent electrical circuits, microcode, or the like. The described operations may be embodied in software, firmware, hardware, or any combinations thereof. The language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based hereon. Accordingly, the disclosure of the embodiments of the invention is intended to be illustrative, but not limiting, of the scope of the invention set forth in any accompanying claims. Finally, throughout the specification and any accompanying claims, unless the context requires otherwise, the word 'comprise' or variations such as 'comprises' or 'comprising' will be understood to imply the inclusion of a stated integer or group of integers but not the exclusion of any other integer or group of integers.