WO2022008967A1 - Fourniture de produit d'utilisation de réseau par le biais d'une plate-forme de portefeuille mobile - Google Patents

Fourniture de produit d'utilisation de réseau par le biais d'une plate-forme de portefeuille mobile Download PDF

Info

Publication number
WO2022008967A1
WO2022008967A1 PCT/IB2020/061925 IB2020061925W WO2022008967A1 WO 2022008967 A1 WO2022008967 A1 WO 2022008967A1 IB 2020061925 W IB2020061925 W IB 2020061925W WO 2022008967 A1 WO2022008967 A1 WO 2022008967A1
Authority
WO
WIPO (PCT)
Prior art keywords
network usage
subscriber
mobile wallet
product
platform
Prior art date
Application number
PCT/IB2020/061925
Other languages
English (en)
Inventor
Antonios CHATZISTAMATIOU
Original Assignee
Channel Technologies Fze
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Channel Technologies Fze filed Critical Channel Technologies Fze
Priority to MX2023000413A priority Critical patent/MX2023000413A/es
Publication of WO2022008967A1 publication Critical patent/WO2022008967A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/16—Payments settled via telecommunication systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3223—Realising banking transactions through M-devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/325—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks
    • G06Q20/3255—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks using mobile network messaging services for payment, e.g. SMS
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/367—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
    • G06Q20/3672—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes initialising or reloading thereof
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4016—Transaction verification involving fraud or risk level assessment in transaction processing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0241—Advertisements
    • G06Q30/0251—Targeted advertisements
    • G06Q30/0267—Wireless devices

Definitions

  • MNO mobile network operator
  • mobile wallet also termed “mobile money”
  • mobile money for managing mobile wallets on behalf of subscribers and via which individual subscribers can store, transfer and withdraw money, pay merchants, utility providers and the like as well as use and access other financial services.
  • Some such mobile wallet platforms include features by way of which subscribers can purchase network usage products, such as airtime, voice minute bundles, data bundles, SMS bundles or the like. This can be convenient for subscribers who have sufficient funds in their mobile wallet to fund the purchase of the network usage product. For subscribers having insufficient funds, some mobile wallet platforms include features by way of which cash loans can be obtained and disbursed into the subscriber’s mobile wallet and then used to purchase the relevant network usage product. However, this is a tedious process for the subscriber and amounts to an inefficient use of the MNO platform and network infrastructure. 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.
  • a computer-implemented method comprising: obtaining data elements generated based on credit data associated with a subscriber identifier which uniquely identifies a mobile subscriber; transmitting a network usage offer based on or including the data elements to a communication device associated with the subscriber identifier via a subscriber channel of a mobile wallet platform in which the subscriber identifier is associated with a mobile wallet; receiving an acceptance of the network usage offer from the communication device via the subscriber channel, the acceptance being associated with a network usage product; and, transmitting an instruction to cause provisioning of the network usage product to an account maintained by an intelligent network and associated with the subscriber identifier.
  • the method may include receiving a request for a network usage product in advance of received payment from the communication device via the subscriber channel of the mobile wallet platform; the data elements may include one or more network usage products available in advance of received payment for acceptance by the mobile subscriber; transmitting the network usage offer includes transmitting the one or more network usage products available in advance of received payment; and receiving an acceptance of the network usage offer includes receiving a selected network usage product.
  • the method may include detecting a transaction failure associated with an attempt to purchase a network usage product against the mobile wallet, the transaction failure being triggered due to an insufficient balance of the mobile wallet; the data elements may include a credit limit value, and if the credit limit value and the balance of the mobile wallet together are sufficient, transmitting the network usage offer may include transmitting an offer to advance the difference between the value of the network usage product and the balance of the mobile wallet.
  • the method may include determining the difference between the value of the network usage product and the balance of the mobile wallet; and comparing the difference to the credit limit value to determine whether the difference can be advanced.
  • the method may include recording a value associated with the accepted network usage offer as outstanding against one or both of the mobile wallet and the account, wherein the value is either a value of the network usage product provisioned in advance of received payment or a difference between the value of the network usage product and a balance of the mobile wallet.
  • the method may include waiting a predefined time period before recording the value as outstanding. Recording the value as outstanding may include recording a lien configured for automatic recovery of at least part of the value, wherein automatic recovery is in response to a top-up event being detected at the mobile wallet or the account.
  • the method may be conducted at the mobile wallet platform, wherein obtaining the data elements includes requesting and receiving the data elements from a service provider platform; and, transmitting the instruction includes transmitting the instruction to the service provider platform.
  • the method may be conducted at a service provider platform, wherein the method includes receiving a request for data elements associated with the subscriber identifier from the mobile wallet platform; transmitting the data elements to the mobile wallet platform; and, receiving and forwarding the instruction from the mobile wallet platform to the intelligent network.
  • a computer-implemented method conducted at a mobile wallet platform in which a subscriber identifier which uniquely identifies a mobile subscriber is associated with a mobile wallet comprising: obtaining data elements generated based on credit data associated with the subscriber identifier; identifying a network usage product associated with the data elements; and, transmitting an instruction to cause provisioning of the network usage product to an account maintained by an intelligent network and associated with the subscriber identifier.
  • a system including a memory for storing computer-readable program code and a processor for executing the computer- readable program code, the system comprising: a data element obtaining component for obtaining data elements generated based on credit data associated with a subscriber identifier which uniquely identifies a mobile subscriber; an offer transmitting component for transmitting a network usage offer based on or including the data elements to a communication device associated with the subscriber identifier via a subscriber channel of a mobile wallet platform in which the subscriber identifier is associated with a mobile wallet; an acceptance receiving component for receiving an acceptance of the network usage offer from the communication device via the subscriber channel, the acceptance being associated with a network usage product; and, a transmitting component for transmitting an instruction to cause provisioning of the network usage product to an account maintained by an intelligent network and associated with the subscriber identifier.
  • a computer program product comprising a computer-readable medium having stored computer-readable program code for performing the steps of: obtaining data elements generated based on credit data associated with a subscriber identifier which uniquely identifies a mobile subscriber; transmitting a network usage offer based on or including the data elements to a communication device associated with the subscriber identifier via a subscriber channel of a mobile wallet platform in which the subscriber identifier is associated with a mobile wallet; receiving an acceptance of the network usage offer from the communication device via the subscriber channel, the acceptance being associated with a network usage product; and, transmitting an instruction to cause provisioning of the network usage product to an account maintained by an intelligent network and associated with the subscriber identifier.
  • Figure 1 shows a schematic diagram which illustrates a system for network usage product provisioning via a mobile wallet platform according to aspects of the present disclosure
  • Figure 2 is a swim-lane flow diagram which illustrates an example method for network usage product provisioning via a mobile wallet platform, where a subscriber requests a network usage product in advance of making payment
  • Figure 3 is a schematic diagram which illustrates an example user experience where a subscriber requests a network usage product in advance of making payment
  • Figure 4 is swim-lane flow diagram which illustrates an example method for network usage product provisioning via a mobile wallet platform, where a transaction failure associated with an attempt to purchase a network usage product against the mobile wallet is detected
  • Figure 5 is a schematic diagram which illustrates an example user experience where a transaction failure associated with an attempt to purchase a network usage product against the mobile wallet is detected
  • Figure 6 is a block diagram which illustrates exemplary components which may be provided by a system for network usage product provisioning via a mobile wallet platform according to aspects of the present disclosure
  • aspects of the present disclosure relate to a system and method for network usage product provisioning via a mobile wallet platform.
  • aspects of the present disclosure provide a mobile wallet platform that obtains data elements generated based on credit data associated with a subscriber identifier, identifies a network usage product associated with the data elements, and transmits an instruction to cause provisioning of the network usage product to an account maintained by an intelligent network and associated with the subscriber identifier.
  • the data elements may include a credit limit value or one or more network usage products available in advance of received payment.
  • identifying the network usage product may include receiving a subscriber’s selection of one of the network usage products available for provision in advance of received payment.
  • identifying the network usage product may include determining or even generating a suitable network usage product to be provisioned in advance of received payment based on the credit limit value and optionally other data (such as a balance of a mobile wallet associated with the subscriber identifier).
  • An example system for network usage product provisioning via a mobile wallet platform is illustrated in Figure 1.
  • the system (100) may include a service provider platform (102) and an MNO platform (104).
  • the service provider platform (102) may be provided by a third-party service provider which provides services to the MNO and its subscribers. 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 a mobile network operator (MNO) which provides access to a mobile network (110) by mobile subscribers.
  • MNO mobile network operator
  • 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 mobile network (110).
  • the MNO platform (104) and mobile network (110) may collectively provide the infrastructure by way of which communication devices can communicate with each other and the broader public switched telephone network (PSTN) and the Internet.
  • the mobile 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 a mobile wallet platform (112), a prepaid gateway (113), an intelligent network (IN) (114) and a charging system (116).
  • the mobile wallet platform (112) may be configured to manage mobile wallets 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 (112) may include a subscriber channel (112A) via which the mobile wallet platform interfaces with the mobile network (110) and in turn the communication devices (106) of individual subscribers.
  • the subscriber channel (112A) may provide access to the mobile wallet platform via SMS, IVR, USSD, software application or web channels.
  • the mobile wallet platform (112) may transmit and receive data and/or messages to and from the respective communication devices (106) via the subscriber channel (112A) and the mobile network (110).
  • the mobile wallet platform (112) may for example be configured to receive requests and/or instructions from the communication devices (106) via the subscriber channel (112A) and to transmit offers and/or notifications to the communication devices via the subscriber channel.
  • the mobile wallet platform (112) may have access to and/or maintain a wallet database (112B) in which individual mobile wallets (112C) are stored.
  • Each mobile wallet (112C) may be associated with a subscriber identifier and may store balance and/or transaction information.
  • Each mobile wallet (112C) may be configured for transacting against by its associated subscriber via the subscriber channel (112A) so as to enable the mobile wallet platform functionality.
  • the mobile wallet platform (112) may include a lien component (112D) configured to record and monitor liens against individual accounts associated with subscriber identifiers.
  • the lien component (112D) may be configured to redirect the inflow of funds to a mobile wallet (112C) against which a lien is recorded towards partial or full recovery of an outstanding amount associated with the subscriber identifier.
  • the prepaid gateway (113) may be configured, amongst other things, to detect requested usage of the mobile network (110) by a subscriber associated with a subscriber identifier, to capture information associated with the requested usage, such as the subscriber identifier, to transmit the captured information to the charging system (116), to receive permitted usage information from the charging system, to permit and monitor usage of the mobile network in accordance with the permitted usage information and to report actual usage information to the charging system.
  • the IN (114) may be implemented according to any suitable network architecture (e.g.
  • the IN (114) 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 (114) 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 may be supported by the Signalling System #7 (SS7) protocol between network switching centres and other network nodes owned by network operators.
  • the charging system (116) may be implemented as a node within the IN (114) that is responsible for collecting data on service usage and to generate reports thereon for billing, either on demand or automatically.
  • the charging system may be an online charging system (OCS).
  • OCS online charging system
  • the charging system (116) may be configured to authenticate and authorize network usage requests associated with subscriber identifiers received from the prepaid gateway (113), determine and transmit permitted usage information (such as a maximum call duration, etc.) to the prepaid gateway and to receive and charge the subscriber in accordance with actual usage information from the prepaid gateway (113).
  • the charging system (116) may be implemented as or have access to 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, in some cases upon request by the service provider.
  • Each subscriber may be associated with one or more of: a main account, a dedicated account, a loan tracking account (also referred to as a principal tracking account) and a fee tracking account. These accounts may be airtime accounts in that their value is denominated in airtime (which is typically equivalent to a value of currency, such as ZAR, USD, NGN, etc.). Each subscriber may further be associated with one or more data bundle, SMS bundle and voice minute bundle accounts which accounts may have their values denominated in bytes, a number of SMS messages and a number of minutes and seconds, respectively.
  • Airtime top-ups, recharges or purchases may be provisioned to the main account and usage of the mobile network (110) (such as making phone calls, sending SMS messages, transmitting and receiving data packets) by the subscriber may typically be charged against the main account.
  • Network usage advances (such as airtime advances) may be provisioned to the main account or the dedicated account, depending on the implementation. Once the network usage advance has been provisioned, further use of the mobile network (110) may be charged against the account to which the network usage advance was provisioned until the balance thereof has been depleted.
  • Data bundles purchased by the subscriber may be provisioned to a main data bundle account after which the transmission and reception of data packets by the subscriber’s communication device (106) via the mobile network (110) may be recorded against (or deducted from) the main data bundle account.
  • Data bundle advances may be provisioned either to the main data bundle account or, in some implementations, to a dedicated data bundle account. Once provisioned, further transmission/reception of data packets may be recorded against the main data bundle account or the dedicated data bundle account, as the case may be, until the balance thereof has been depleted to zero. The same may apply, mutatis mutandis, for the SMS and voice minute bundle accounts.
  • the tracking accounts may be used to keep track of amounts owed by subscribers in respect of advances (or loans) that the subscribers have requested and received.
  • a non-zero balance of any one of the tracking accounts (be it loan tracking or fee tracking) may indicate an outstanding advance or an outstanding amount.
  • the value or amount of balance may indicate the amount owed by the subscriber.
  • the accounts described herein may be implemented as fields of a high-throughput database. The fields may be associated with a subscriber identifier and can be updated or modified in real-time in response to network usage or top-up events. Different fields of the database may represent different accounts associated with a particular subscriber.
  • the charging system (116) may include or be embodied by a data structure, such as a table maintained by relational database management system (RDBMS), having rows which are associated with subscribers (identified by way of a subscriber identifier, such as an MSISDN or other suitable identifier) and columns which are associated with account identifiers which identify and correspond to different types of accounts, such as each of the respective accounts described in the foregoing.
  • the system (100) may include a provisioning and recovery node (120), which may be provided by a node of the IN (114).
  • the provisioning and recovery node (120) may be configured to provision network usage products to appropriate accounts of subscribers pursuant to associated events, such as network usage product purchases, network usage product advances, top-up events and the like.
  • the provisioning and recovery node (120) may be configured to manipulate or adjust (e.g. access, change and/or update) fields of the charging system (116) so as to effect the provisioning of airtime and/or mobile bundles.
  • the provisioning and recovery node (120) may be configured to query one or both of the loan tracking account and fee tracking account upon a subscriber top-up event or other inflow of funds and to divert some or all of the amount associated with the top-up or inflow in order to effect partial or complete recovery of the outstanding amount represented by these accounts.
  • the MNO platform (104) may include one or more front-end APIs by way of which the service provider platform may interface with components or nodes of the MNO platform, such as the mobile wallet platform (112), the intelligent network (114), the charging system (116), the provisioning and recovery node (120) and the like.
  • the MNO platform may for example include a wallet platform API (126) and an IN integration API (127) which may interface with or provide access to an IN-integration component for aspects of the interface.
  • the service provider platform (102) may be provided by any suitable computing device or devices and may for example include a server computer (121).
  • the service provider platform (102) and/or the server computer (121) may be configured to interface and/or integrate with aspects of the MNO platform (104), for example the mobile wallet platform (112) and the intelligent network (114).
  • the server computer may be configured to interface with the mobile wallet platform, intelligent network (IN) and/or charging system of the MNO platform via an appropriate front-end API, an appropriate IN-integration component or the like.
  • the service provider platform (102) and/or the server computer (121) may for example be able to transact against mobile wallets maintained by the mobile wallet platform and adjust account balances of accounts stored in the charging system.
  • the service provider platform (102) and/or the server computer (121) may utilise IN-integration (e.g.
  • the service provider platform (102) and/or the server computer (121) may utilise mobile wallet platform integration (e.g. via the wallet platform API (126)) for: receiving mobile wallet related subscriber data; crediting loan amounts; setting/updating/removing a lien against the mobile wallets; and, receiving loan payments.
  • the service provider platform (102) may have access to a subscriber database (122) in which a record (124) associated with each subscriber is stored.
  • Each subscriber record (124) may include and be associated with a subscriber identifier.
  • each subscriber record includes one or more sets of credit data, such as a credit score, an outstanding network usage advance status, a network usage advance 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 subscriber.
  • a high credit score may indicate low risk while a low credit score may indicate a high- risk subscriber.
  • the total credit limit may be a total credit limit value denominated in a value of airtime.
  • the credit limit value represents a value of a network usage advance for which a subscriber associated with the subscriber identifier is eligible in advance of payment.
  • the credit score and credit limit value may be determined by the service provider platform using MNO related subscriber data (including Call Detail Records (CDRs), calling/messaging history, airtime balances and top-up history, KYC data, length of service with the MNO and the like).
  • MNO related subscriber data including Call Detail Records (CDRs), calling/messaging history, airtime balances and top-up history, KYC data, length of service with the MNO and the like.
  • the service provider platform (102) may be configured to perform credit scoring and risk management operations using data received from the MNO platform and/or other sources and to maintain and update credit data and/or risk data stored in subscriber records accordingly.
  • the service provider platform may for example be configured to utilize/process available MNO and mobile wallet service data available from the mobile money service provider.
  • the system (100) may be configured to obtain data elements generated based on credit data associated with a subscriber identifier which uniquely identifies a mobile subscriber; transmit a network usage offer based on or including the data elements to a communication device associated with the subscriber identifier via the subscriber channel of the mobile wallet platform in which the subscriber identifier is associated with a mobile wallet; receive an acceptance of the network usage offer from the communication device via the subscriber channel, the acceptance being associated with a network usage product; and, transmit an instruction to cause provisioning of the network usage product to an account maintained by the intelligent network and associated with the subscriber identifier.
  • the system (100) may be configured to receive a request for a network usage product in advance of received payment from the communication device via the subscriber channel of the mobile wallet platform.
  • the data elements may include one or more network usage products available in advance of received payment for acceptance by the mobile subscriber.
  • the system may be configured to transmit the one or more network usage products available in advance of received payment; and to receive selection of a network usage product.
  • the system (100) may also be configured to detect a transaction failure associated with an attempt to purchase a network usage product against the mobile wallet of a particular subscriber, the transaction failure being triggered due to an insufficient balance of the mobile wallet.
  • the data elements may include a credit limit value, and if the credit limit value and the balance of the mobile wallet together are sufficient, the system may be configured to transmit an offer to advance the difference between the value of the network usage product and the balance of the mobile wallet.
  • the system (100) described above may implement a method for network usage product provisioning via the mobile wallet platform (112).
  • An exemplary method for network usage product provisioning via a mobile wallet platform (112) is illustrated in the swim-lane flow diagram of Figure 2 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.
  • Figure 2 is described with reference to an example scenario in which a subscriber requests a network usage product in advance of making payment.
  • An example user experience corresponding to the method of Figure 2 is illustrated in Figure 3.
  • the subscriber may use his or her communication device (106) to access (200) the mobile wallet platform (112) via the subscriber channel (112A).
  • the access may be via USSD, SMS messaging, IVR, a website, or a mobile wallet application installed on the communication device (106).
  • the communication device (106), and hence the subscriber may be identifiable to the mobile wallet platform (112) via the subscriber channel, such that communications between the communication device and mobile wallet platform are associated with a subscriber identifier.
  • the subscriber may access (202), for example, a ‘Borrow Network Usage Product’ option via the subscriber channel. Accessing the Borrow Network Usage Product option may cause the communication device (106) to transmit (203) a request for a network usage product to the mobile money platform (112) via the subscriber channel.
  • the request is a request for the product in advance of received payment.
  • the mobile wallet platform (112) may receive (204) the request for the network usage product in advance of received payment from the communication device (106) via the subscriber channel (112A).
  • the request may be associated with the subscriber identifier, which uniquely identifies a mobile subscriber.
  • the mobile wallet platform (112) may obtain (216) data elements generated based on credit data associated with the subscriber identifier. This may include transmitting a data element request message to a service provider platform (102).
  • the data element request may include the subscriber identifier and particulars associated with the request (e.g., in the illustrated embodiment, that the subscriber has selected a borrow network usage product option via the subscriber channel).
  • the service provider platform (102) may receive the request and may obtain or determine (218) the data elements associated with the request.
  • Determining the data elements may include checking if the subscriber associated with the subscriber identifier is eligible and/or checking a credit profile associated with the subscriber identifier.
  • the service provider platform (102) may for example use the subscriber identifier to query a subscriber database (122) and access and evaluate relevant data stored in a corresponding subscriber record (124).
  • determining the data elements (218) includes determining or identifying network usage products for which the subscriber is eligible in advance of received payment based on credit data stored in the subscriber record. For example, based on the credit data and/or risk profile, the subscriber may be allowed to borrow multiple products up to his/her credit limit value at the same time.
  • the service provider platform (102) may return (220) the data elements to the mobile wallet platform (112).
  • the data elements may constitute an offer by the service provider platform for acceptance by the subscriber via the subscriber channel.
  • the data elements include one or more network usage products which are available to the subscriber in advance of received payment. The products may be unique to the particular subscriber based on his/her credit data.
  • the mobile wallet platform (112) transmits (222) a network usage offer based on or including the data elements to the communication device (106) associated with the subscriber identifier. The transmission may be via the subscriber channel (112A).
  • the offer includes a list of the one or more network usage products (e.g.
  • the communication device (106) may receive and display (223) the network usage offer, which in the illustrated scenario includes a list of network usage products available for selection by the subscriber.
  • the offer may be presented to the subscriber along with the product and loan terms (which in some cases may occur after a selection is input by the subscriber).
  • Product terms may include bundle details and expiry.
  • Loan terms may include fee, duration/ term, etc.
  • the subscriber may input his or her selection into the communication device, which receives (225) the input and transmits an acceptance of the network usage offer to the mobile wallet platform (112) via the subscriber channel (112A).
  • the acceptance is associated with a network usage product, in this scenario being the product selected by the subscriber.
  • the mobile wallet platform (112) receives (227) acceptance of the network usage offer and requests (228) provision of the relevant network usage product.
  • receiving acceptance of the network usage advance offer includes receiving a selection of a network usage product from the list of one or more network usage products that are available to the subscriber in advance of received payment.
  • the mobile wallet platform may identify a suitable network usage product based on the data elements without reaching out to the subscriber. This may enable so called auto-refill functionality and may be applicable in cases in which the subscriber has opted in to auto-refill.
  • requesting (228) provision of the network usage product may include the mobile wallet platform (112) transmitting an instruction to the service provider platform (102) to cause provisioning of the network usage product to an account maintained by an intelligent network and associated with the subscriber identifier.
  • requesting provision of the network usage product may include the service provider platform instructing the IN to provision the network usage product.
  • the service provider platform (102) receives the instruction and provisions (230) the network usage product.
  • the service provider platform (102) may also register the advance (or register provision of the advance), including for example updating the subscriber record and/or associated data points (e.g.
  • Provisioning the network usage product may include instructing the intelligent network (114) to provision the network usage product to an account associated with the subscriber identifier in the charging system.
  • the intelligent network (114) may for example adjust (232), e.g. using a provisioning and recovery node, balances of one or more accounts associated with the subscriber identifier in the charging system so as to provision the network usage product.
  • the service provider platform (102) records (234A, 234B) a value associated with the accepted network usage offer as outstanding against one or both of the mobile wallet (112C) and the account associated with the subscriber identifier in the IN.
  • Recording the value may record the value as an amount due to be repaid by the subscriber.
  • the value associated with the network usage product may include a fee portion and a principal portion corresponding to the value loaned to the subscriber.
  • the value associated with the accepted network usage product includes a fee of USD1 and the value of the network usage product provisioned in advance of received payment, being USD10.
  • Recording the value as outstanding may include recording a lien configured for automatic recovery of the or part of the value, wherein automatic recovery is in response to a top-up event being detected at the mobile wallet or the account.
  • the service provider platform (102) may instruct the intelligent network (114) to adjust one or more account balances in order to record the value as outstanding, for example by recording a principal amount against a loan tracking account associated with the subscriber identifier in the charging system and recording a fee amount against a fee tracking account associated with the subscriber identifier in the charging system.
  • the intelligent network may record the outstanding value in other ways, for example using a negative balance feature or the like.
  • the IN and/or charging system is configured to divert incoming funds into an account associated with the subscriber to the recovery of the outstanding value, for example by applying the incoming funds towards reducing the balance of the tracking account and/or fee accounts associated with the subscriber main account.
  • the service provider platform may for example instruct a lien component (112D) of the mobile wallet platform to record a lien against the mobile wallet (112C) associated with the subscriber identifier such that any inflow of funds into the mobile wallet can be redirected towards recovery of the outstanding value. This may include applying a rule to the mobile wallet (112C) associated with the subscriber that automatically diverts incoming funds towards the recovery of the outstanding value.
  • the service provider platform (102) may wait a predefined time period before recording the value as outstanding. The time period may be configurable on a per-subscriber basis and may vary from hours to days or even weeks.
  • a subscriber is able to request a network usage product in advance of received payment via a subscriber channel of a mobile wallet platform.
  • the subscriber can follow these steps for borrowing a product from the mobile wallet service menu: Select the Product, Borrow Product offers will be presented based on subscriber’s eligibility and credit data; Accept Loan Terms, A summary of application (Fees, Repayment term / duration) and other T&C’s are shown; Submit Request, Borrow Product request submitted for processing.
  • the service provider platform will receive the product loan request and then it will provision the product and register (or record) the advance as being outstanding.
  • a lien may be activated on one or both of the mobile wallet and an account associated with the subscriber in the IN. This can be done immediately or after a maturity period of a few days.
  • Another example method for network usage product provisioning via a mobile wallet platform is illustrated in the swim-lane flow diagram of Figure 4, which is described with reference to an example scenario in which a transaction failure associated with an attempt to purchase a network usage product against the mobile wallet is detected.
  • Figure 5 illustrates a corresponding example user experience. The scenario illustrated with reference to Figures 4 and 5 differs primarily in the loan product that is offered to the subscriber (e.g. purchase completion versus advance product).
  • the flow of data and/or messages between devices and operations performed by the respective devices remains substantially the same as the scenario described above with reference to Figures 2 and 3.
  • the same reference numerals are used for corresponding operations in Figures 2 and 4 to reflect this similarity, although the exact operations or content of the messages may differ slightly in the different scenarios.
  • the subscriber may use his or her communication device (106) to access (200) the mobile wallet platform (112) via the subscriber channel.
  • the subscriber accesses (201) a ‘Purchase Network Usage Product’ option via the subscriber channel and selects (205) the network usage product that he/she wants to purchase.
  • the communication device transmits (206) a request to purchase a network usage product to the mobile money platform (112) via the subscriber channel.
  • the mobile money platform (112) receives the request to purchase the network usage product associated with the subscriber identifier and checks the balance of the mobile wallet associated with the subscriber identifier. If the balance is sufficient to fund the purchase, the purchase may be allowed to continue. If not, the mobile wallet platform may detect (208) a transaction failure associated with an attempt to purchase a network usage product against the mobile wallet, the transaction failure being triggered due to an insufficient balance of the mobile wallet associated with the subscriber identifier.
  • the mobile wallet platform (112) may obtain (216) data elements generated based on credit data associated with the subscriber identifier.
  • This may include transmitting a data element request message to a service provider platform (102).
  • the data element request may include the subscriber identifier and particulars associated with the request (e.g., in the illustrated scenario, that a transaction failure is detected against a mobile wallet associated with the subscriber identifier).
  • the service provider platform (102) may receive the request and may determine (218) the data elements associated with the request. Determining (218) the data elements may include checking if the subscriber associated with the subscriber identifier is eligible and/or checking a credit profile associated with the subscriber identifier.
  • the service provider platform (102) may for example use the subscriber identifier to query a subscriber database (122) and access and evaluate relevant data stored in a corresponding subscriber record (124).
  • determining the data elements includes determining a credit limit value associated with the subscriber identifier which corresponds to a maximum value which may be loaned to the subscriber associated with the subscriber identifier.
  • the service provider platform (102) may return (220) the data elements to the mobile wallet platform (112).
  • the data elements include the credit limit value or maximum loan value associated with the subscriber identifier.
  • the service provider platform may therefore return the maximum loan offer up to subscriber’s credit limit based on the risk profile and/or credit data (taking into account any outstanding advances) associated with the subscriber identifier.
  • the mobile wallet platform (112) may determine the difference between the value of the network usage product and the balance of the mobile wallet and compare the difference to the credit limit value to determine whether the difference can be advanced to the subscriber (e.g. whether a loan can be registered in favour of the subscriber in respect of the difference). If the credit limit value and the balance of the mobile wallet together are sufficient, the mobile wallet platform (112) transmits (222) a network usage offer based on or including the data elements to the communication device (106) via the subscriber channel. In this scenario, the network usage offer is based on the data elements (e.g.
  • the communication device (106) may receive and display (224) the network usage offer, which in the illustrated scenario includes an offer to advance the difference (e.g. provide a loan in respect of the difference) such that the purchase of the selected network usage product can continue.
  • the offer may be presented to the subscriber along with the product and loan terms.
  • Product terms may include bundle details and expiry.
  • Loan terms may include fee, duration/term, etc.
  • the subscriber may input his or her acceptance into the communication device, which receives (226) the input and transmits the acceptance of the network usage offer to the mobile wallet platform (112) via the subscriber channel (112A).
  • the acceptance is associated with a network usage product, in this scenario being the product selected for purchase by the subscriber.
  • the mobile wallet platform (112) receives (227) acceptance of the network usage offer and requests (228) provision of the relevant network usage product.
  • requesting (228) provision of the network usage product may include the mobile wallet platform (112) transmitting an instruction to the service provider platform to cause provisioning of the network usage product to an account maintained by an intelligent network and associated with the subscriber identifier.
  • requesting provision of the network usage product may include the service provider platform instructing the IN to provision the network usage product.
  • the service provider platform (102) receives the instruction and provisions (230) the network usage product.
  • the service provider platform may collect the balance of the mobile wallet, for example by requesting the mobile wallet platform to transfer the remaining balance of the mobile wallet associated with the subscriber identifier to an account associated with the service provider.
  • the service provider platform may also register the advance, including for example updating the subscriber record and/or associated data points (e.g. the total credit limit value) to reflect the value advanced in respect of the network usage offer, in this scenario being the value of the difference between the balance of the mobile wallet and the network usage product purchased by the subscriber.
  • Provisioning the network usage product may include instructing the intelligent network (114) to provision the network usage product to an account associated with the subscriber identifier in the charging system.
  • the intelligent network (114) may for example adjust (232) balances of one or more accounts associated with the subscriber identifier in the charging system so as to provision the network usage product.
  • the service provider platform (102) records (234A, 234B) a value associated with the accepted network usage offer as outstanding against one or both of the mobile wallet (112C) and the account associated with the subscriber identifier. Recording the value may record the value as an amount due to be repaid by the subscriber.
  • the value associated with the network usage product may include a fee portion and a principal portion corresponding to the value loaned to the subscriber.
  • the value associated with the accepted network usage product includes a fee of USD2 and the value of the difference between the balance of the mobile wallet and the value of the network usage product selected for purchase by the subscriber (e.g. USD20).
  • recording the value as outstanding may include recording a lien configured for automatic recovery of the or part of the value, wherein automatic recovery is in response to a top-up event being detected at the mobile wallet or the account. This may be effected by applying one or more rules to each of the mobile wallet and account in the IN.
  • the service provider platform may wait a predefined time period before recording the value as outstanding. The time period may be configurable on a per-subscriber basis and may vary from hours to days or even weeks.
  • the subscriber wants to purchase a network usage (or ‘telco’) product (e.g. a Bundle or Airtime) but the mobile wallet balance is insufficient to complete the purchase.
  • a loan will be offered during the checkout process to complete the purchase.
  • the subscriber will access the ‘Purchase Network Usage Product’ option via any of the existing access channels offered by the mobile wallet menu and select his product of preference.
  • the mobile wallet platform checks with the service provider loan service of the maximum loan offer. The combination of mobile wallet balance and loan offer is checked for sufficiency to complete the product purchase and present the offer to the subscriber.
  • FIG. 6 is a block diagram which illustrates exemplary components which may be provided by a system for network usage product provisioning via a mobile wallet platform.
  • the system includes a server computer (121), which may form part of a service provider platform or an MNO platform, depending on the implementation.
  • the server computer (121) 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 server computer (121).
  • 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.
  • software units arranged to manage and/or process data on behalf of the server computer (121) may be provided remotely.
  • the server computer (121) may include a data element obtaining component (506) arranged to obtain data elements generated based on credit data associated with a subscriber identifier which uniquely identifies a mobile subscriber.
  • the data element obtaining component may obtain the data elements by determining the data elements based on data stored in a subscriber record. In embodiments in which the server computer forms part of the MNO platform, the data elements obtaining component may obtain the data elements from a service provider platform.
  • the server computer (121) may include an offer transmitting component (508) arranged to transmit a network usage offer based on or including the data elements to a communication device associated with the subscriber identifier. The offer may be transmitted via a subscriber channel of a mobile wallet platform in which the subscriber identifier is associated with a mobile wallet.
  • the server computer (121) may include an acceptance receiving component (510) arranged to receive an acceptance of the network usage offer from the communication device via the subscriber channel.
  • the acceptance may be associated with a network usage product in the manner described in the foregoing.
  • the server computer (121) may include a transmitting component (512) arranged to transmit an instruction to cause provisioning of the network usage product to an account maintained by an intelligent network and associated with the subscriber identifier.
  • the systems and methods described herein enable network usage product provisioning via a mobile wallet platform.
  • the systems and methods described herein may reduce the steps required to purchase network usage products via a subscriber channel of a mobile wallet platform, which may in turn lead to improved efficiency of MNO resources in that, for example, fewer messages or instructions need to be relayed between the subscriber and the relevant platforms.
  • 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 systems and methods described herein provide a telco loan service for mobile wallets.
  • This is a special purpose loan service that only covers telecommunication product purchases. It is a new type of loan that empowers the subscribers of the mobile money wallet to purchase telco, or network usage, products (like airtime, bundles, etc.) when his/her wallet does not have enough balance.
  • the main characteristics of the telco loan are: - very short term in duration; - very simple fee structure; and, - the ability to be repaid from both the mobile wallet and the main telco account.
  • the “Telco Loan Service” described herein allows mobile money or mobile wallet service providers to offer the optimal solution to their customers for buying Telecommunication services including airtime, data and bundles on credit.
  • the service provides: • short duration loans • which can be used only for the purchase of telecommunication (or ‘network usage’) products, and • which can be repaid from the mobile money wallet and/or the Telco’s Airtime account.
  • the service can be delivered via: a new menu option in the existing mobile wallet menu; or, a payment option during purchase of a telco product. These options can be captured in the following use cases: borrowing a Telco product on request; or, completion of purchase of a telco product (loan on checkout).
  • the value of the loan may include: • the principal amount which typically matches the value of the telco service to be purchased. It is a dynamic value to cover any price of telco service; and, • the fee which is the charge for the credit facility. It can be either a percentage of the principal amount (with or without cap) or, fixed per loan (regardless of the principal amount or in buckets of principal amount). The amount due is the sum of the principal amount and the fee.
  • the lifecycle of the Telco Loan product is divided in the two (2) main phases: maturity phase; and, collection phase.
  • the loan date is the date that the loan was provisioned, and it is considered as the 0-day (day zero) of the loan. Due date is the last date of the maturity phase and marks the date when the subscriber should fully repay the loan.
  • the proposed service accepts partial payments.
  • the Telco Loan can be repaid from either of the following channels: the subscriber’s Mobile wallet; the subscriber’s Telco Airtime account (e.g. maintained by the IN).
  • a lien will be applied to both accounts.
  • the liens on both mobile wallet and airtime accounts we will be either updated, if it is a partial repayment or removed, if it is a full repayment.
  • the bellow table shows example balance adjustments of the Mobile wallet and Telco’s Main Account when a subscriber gets a Telco Product as a loan and when the loan is repaid. Subscribers with outstanding loans in collection phase may receive regular reminders of their loan until the loan is fully repaid.
  • FIG. 7 illustrates an example of a computing device (700) in which various aspects of the disclosure may be implemented.
  • the computing device (700) 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.
  • a mobile phone e.g. cellular telephone
  • satellite phone e.g. cellular telephone
  • tablet computer e.g. cellular telephone
  • the computing device (700) 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 (700) to facilitate the functions described herein.
  • the computing device (700) may include subsystems or components interconnected via a communication infrastructure (705) (for example, a communications bus, a network, etc.).
  • the computing device (700) may include one or more processors (710) and at least one memory component in the form of computer-readable media.
  • the one or more processors (710) 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.
  • various subsystems or components of the computing device (700) 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 (715), which may include read only memory (ROM) and random access memory (RAM).
  • ROM read only memory
  • RAM random access memory
  • a basic input/output system (BIOS) may be stored in ROM.
  • System software may be stored in the system memory (715) including operating system software.
  • the memory components may also include secondary memory (720).
  • the secondary memory (720) may include a fixed disk (721), such as a hard disk drive, and, optionally, one or more storage interfaces (722) for interfacing with storage components (723), 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 (700) may include an external communications interface (730) for operation of the computing device (700) in a networked environment enabling transfer of data between multiple computing devices (700) and/or the Internet. Data transferred via the external communications interface (730) may be in the form of signals, which may be electronic, electromagnetic, optical, radio, or other types of signal.
  • the external communications interface (730) may enable communication of data between the computing device (700) and other computing devices including servers and external storage facilities. Web services may be accessible by and/or from the computing device (700) via the communications interface (730).
  • the external communications interface (730) may be configured for connection to wireless communication channels (e.g., a cellular telephone network, wireless local area network (e.g. using Wi-FiTM), 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 (730) 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 (700).
  • SIM subscriber identity module
  • One or more subscriber identity modules may be removable from or embedded in the computing device (700).
  • 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 (710).
  • 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 (730). Interconnection via the communication infrastructure (705) allows the one or more processors (710) 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
  • input/output (I/O) devices such as a mouse, touchpad, keyboard, microphone, touch-sensitive display, input buttons, speakers and the like
  • One or more displays (745) may be coupled to or integrally formed with the computing device (700) via a display or video adapter (740).
  • 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, JavaTM, C++, or PerlTM 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.
  • 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.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Computer Security & Cryptography (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un système et un procédé de fourniture de produit d'utilisation de réseau par le biais d'une plate-forme de portefeuille mobile. Dans un procédé, des éléments de données générés sur la base de données de crédit qui sont associées à un identifiant d'abonné qui identifie de manière unique un abonné mobile sont obtenus. Une offre d'utilisation de réseau basée sur les éléments de données, ou comprenant ceux-ci, est transmise à un dispositif de communication associé à l'identifiant d'abonné par le biais d'un canal d'abonné d'une plate-forme de portefeuille mobile dans laquelle l'identifiant d'abonné est associé à un portefeuille mobile. L'acceptation de l'offre d'utilisation de réseau est reçue en provenance du dispositif de communication par le biais du canal d'abonné. L'acceptation reçue en provenance du dispositif de communication est associée à un produit d'utilisation de réseau sélectionné. Une instruction est transmise pour provoquer la fourniture du produit d'utilisation de réseau à un compte qui est maintenu par un réseau intelligent et associé à l'identifiant d'abonné.
PCT/IB2020/061925 2020-07-07 2020-12-15 Fourniture de produit d'utilisation de réseau par le biais d'une plate-forme de portefeuille mobile WO2022008967A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
MX2023000413A MX2023000413A (es) 2020-07-07 2020-12-15 Aprovisionamiento de producto de uso de red por medio de plataforma de cartera movil.

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
ZA202004132 2020-07-07
ZA2020/04132 2020-07-07

Publications (1)

Publication Number Publication Date
WO2022008967A1 true WO2022008967A1 (fr) 2022-01-13

Family

ID=77271585

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2020/061925 WO2022008967A1 (fr) 2020-07-07 2020-12-15 Fourniture de produit d'utilisation de réseau par le biais d'une plate-forme de portefeuille mobile

Country Status (3)

Country Link
MX (1) MX2023000413A (fr)
WO (1) WO2022008967A1 (fr)
ZA (1) ZA202004712B (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007120117A2 (fr) * 2006-04-19 2007-10-25 Veritas Mobile Solutions Pte. Ltd. Procédé et système d'octroi de crédit aux abonnés d'un service prépayé fourni par un réseau de télécommunications
KR100773918B1 (ko) * 2005-04-12 2007-11-07 주식회사 하렉스인포텍 모바일 전자지갑의 결제기능을 이용한 대금 청구 및 납부서비스 방법 및 그 시스템
US20120310824A1 (en) * 2011-06-03 2012-12-06 Liberty Michael A Monetary transaction system
US20180293572A1 (en) * 2017-04-10 2018-10-11 Mastercard Asia/Pacific Pte. Ltd. System and method for administering a user account
WO2019229650A1 (fr) * 2018-05-30 2019-12-05 Channel Technologies Fze Systèmes et procédés de provisionnement et récupération concernant un abonné mobile

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100773918B1 (ko) * 2005-04-12 2007-11-07 주식회사 하렉스인포텍 모바일 전자지갑의 결제기능을 이용한 대금 청구 및 납부서비스 방법 및 그 시스템
WO2007120117A2 (fr) * 2006-04-19 2007-10-25 Veritas Mobile Solutions Pte. Ltd. Procédé et système d'octroi de crédit aux abonnés d'un service prépayé fourni par un réseau de télécommunications
US20120310824A1 (en) * 2011-06-03 2012-12-06 Liberty Michael A Monetary transaction system
US20180293572A1 (en) * 2017-04-10 2018-10-11 Mastercard Asia/Pacific Pte. Ltd. System and method for administering a user account
WO2019229650A1 (fr) * 2018-05-30 2019-12-05 Channel Technologies Fze Systèmes et procédés de provisionnement et récupération concernant un abonné mobile

Also Published As

Publication number Publication date
ZA202004712B (en) 2021-07-28
MX2023000413A (es) 2023-02-02

Similar Documents

Publication Publication Date Title
US10706415B2 (en) Money transfer smart phone methods and systems
US8799092B2 (en) Methods, apparatus, and systems for supporting purchases of goods and services via prepaid telecommunication accounts
RU2706180C2 (ru) Обработка финансовых транзакций
US20180197167A1 (en) System and method for person-to-person payments
US20120173396A1 (en) Bill division and group payment systems and methods
US20140089188A1 (en) System for funds transfer using source atm and delivering atm
EP2974258A1 (fr) Procédé, appareil et support lisible par ordinateur pour une avance de crédit prépayé
WO2020008384A1 (fr) Provision et recouvrement d'avances sur une utilisation de réseau
WO2019229655A1 (fr) Fourniture d'avances d'utilisation de réseau basée sur une limite de crédit
WO2022038455A1 (fr) Système et procédé de fourniture de produit d'utilisation de réseau
WO2022008967A1 (fr) Fourniture de produit d'utilisation de réseau par le biais d'une plate-forme de portefeuille mobile
OA19720A (en) Network usage product provisioning via a mobile wallet platform
WO2019229650A1 (fr) Systèmes et procédés de provisionnement et récupération concernant un abonné mobile
US20180096320A1 (en) Account top-up feature to interface with a vendor application programming interface
WO2022200881A1 (fr) Gestion intégrée de comptes multiplateformes
OA21014A (en) Integrated cross-platform account management.
WO2021240253A1 (fr) Provisionnement, en fonction de la classification de type, d'avances d'utilisation du réseau dans un réseau mobile
OA20072A (en) Electronic voucher distribution account management.
OA19727A (en) Type classification-based provisioning of network usage advances in a mobile network
WO2022008988A1 (fr) Fourniture de différents services d'avance d'utilisation de réseau pour différentes catégories d'abonnés
OA19726A (en) Provision of different network usage advance services to different categories of subscribers
OA21159A (en) System and method for remote provision, disbursement and collection of secured loans.
WO2022038431A1 (fr) Système et procédé d'approvisionnement, de versement et de recouvrement à distance de prêts garantis
OA21158A (en) System and method for network usage product provisioning.
OA18625A (en) Systems and methods for mobile subscriber provisioning

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20943843

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 04/05/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20943843

Country of ref document: EP

Kind code of ref document: A1