This disclosure relates to granting access to accounts, to other financial institution services and to wider information-exchange services under circumstances in which such access may not typically be available, such as in the wake of a regional disaster. More specifically, this invention relates to issuing financial instruments capable of accessing an account, such issuing being to a client requesting access to the accounts but not in possession of physical documentation of being a holder of the account.
A financial institution accountholder typically uses one or more channels to access funds that the accountholder maintains in a financial institution account. The channels may include a brick-and-mortar banking institution customer service office, a telephone-based banking institution customer service agency, a self-service device (such as an automated teller machine (“ATM”)) and an on-line banking portal. The accountholder may interact with the on-line banking portal via a fixed communication device or a mobile communication device.
The banking institution (hereinafter, “bank”) may typically require that a customer present to the bank information authenticating the identification of the customer as the accountholder before the bank grants the customer access to the account. The bank may require that the customer present the authentication information through the one or more channels.
Exemplary identity-authentication information may include: a physical article of documentation that the customer possesses (e.g., an ATM card or photograph-bearing identification, such as a driver's license); a knowledge-item that the customer knows (e.g., a personal identification number (“PIN”) or a correct answer to an accountholder-chosen security question); and a biometric feature of the customer (e.g., a handprint or DNA). A typical granting of access to the account may include the customer confirming his/her being the accountholder by proffering the physical article of documentation (e.g., an ATM card) and also presenting the knowledge-item (e.g., a PIN).
There are circumstances under which an accountholder may not be in possession of any physical article of identity-authentication. Such circumstances may include calamitous events affecting primarily the accountholder, such as being the victim of pickpocketing, home-burglary or a house-fire. Without the physical article of identity-authentication, the accountholder's ability to access his/her account may be reduced, but may not be eliminated.
Under such circumstances, the accountholder may present to the bank alternate identity-authentication information, such as the accountholder's PIN and answers to account security questions. The accountholder may present the person of the accountholder to the bank for biometric readings. PINs, answers to security questions, and biometric readings may be checked against a bank database of accountholder information. Given a sufficient number of confirming matches of the customer's alternate identity-authentication information with bank database accountholder information, the bank may grant the client access to the account in the absence of client-borne physical identity-authentication documentation. On the basis of such alternate identity-authentication information confirmation, the bank may reissue to the accountholder an article of identity-authentication documentation, such as an ATM or bank credit card.
However, there are circumstances under which the bank customer without physical identity-authentication documentation may have difficulty making use of alternate identity-authentication information to gain access to his/her account. Such circumstances include a widespread calamity that severely impacts the accountholder's locale, impacting the accountholder as well as locale-based brick-and-mortar banks, among other locale-associated individuals and institutions impacted. Extreme environmental conditions (e.g., earthquakes, tsunamis, gale-force winds, blizzards, and flooding) and man-made disasters (e.g., devastating terrorist attacks and accidental catastrophes) may result in a banking customer having neither physical identity-authentication documentation nor functional locale-based banks at which to present identity-authentication information. Such widespread calamities may also severely impair infrastructure that would otherwise enable an accountholder to contact the bank via transportation means and/or via communication devices; such impairment of infrastructure may drastically reduce or effectively eliminate access to banking channels. The customer may be cut off from banking services both inside and outside the locale of the calamity.
Impairment of transportation infrastructure and/or of communications infrastructure in the wake of events such as regional disasters may be detrimental to the economy and welfare of persons and institutions of the locale. Such impairment of infrastructure within the region may also hamper coordination and implementation of disaster-relief efforts of community groups and of local governments and law-enforcement, and of larger-scale efforts such as those of the Federal Emergency Management Agency (“FEMA”) and the Red Cross.
It would be desirable, therefore, to provide apparatus and methods for granting customers access to their accounts under circumstances such as disasters that may dispossess the customers of physical identity-authenticating documentation and/or that may disrupt usual banking operations. It would also be desirable to have such granting include the opening of new accounts by customers.
It would also be desirable, therefore, to provide to those impacted by impairment of locale infrastructure in the wake of such disasters—accountholders, the general public and institutions—apparatus and methods that facilitate electronic communication and information-exchange. It would also be desirable to have such electronic communication and information-exchange serve to support impacted locale-business.
It would also be desirable, therefore, to provide apparatus and methods that facilitate electronic communication and information-exchange to support locale disaster-relief efforts of locale-based groups and of groups such as FEMA and the Red Cross.
It is an object of this invention to provide apparatus and methods for accountholders to access their accounts in the wake of an event—such as a regional disaster—that may dispossess accountholders of identity-authentication documentation and/or that may disrupt usual banking operations. It is also an object of this invention to provide apparatus and methods for persons and institutions of the affected locale to have access to electronic communication and information-exchange in the wake of an event that impairs local and regional electronic communications infrastructure. It is also an object of this invention to provide apparatus and methods to aid in coordination and implementation of local and regional relief efforts.
The apparatus and methods of this invention that may provide accountholders access to their accounts may accommodate banking customers opening new accounts and performing other banking operations. The apparatus and methods of this invention that provide access to electronic communication and information-exchange functions may support locale-based business operations. The apparatus and methods of this invention that support banking and/or business operations may accommodate utilization as part of local and regional relief efforts.
The apparatus of this invention may include, and the methods may involve, a mobile platform. The mobile platform may comprise a Mobile Banking Unit (“MBU”). The MBU may be capable of performing standard banking operations that may have been disrupted by the event. The MBU may be capable of performing non-standard banking operations and/or non-banking operations, either independently from or as part of the mobile platform.
The mobile platform may be capable of deployment to and within the locale of a disaster. The deployment may involve translocation to and within the locale.
The mobile platform may include a power-supplying unit, conferring on the mobile platform independence from power infrastructure of the locale in which it is deployed. The power-supplying unit may be capable of utilizing available locale-based power.
The mobile platform may include a communications unit for secure communication via satellite and/or other wireless-communication-enabling means, conferring on the mobile platform independence from communications infrastructure of the locale in which it is deployed. Thus, the mobile platform may be capable of securely exchanging information with sites within and/or beyond the deployment locale.
The mobile platform may be unstaffed in the deployment locale. Performance of functions of the mobile platform may be monitored remotely from within and/or beyond the deployment locale. Performance of functions of the mobile platform may be controlled remotely from within and/or beyond the deployment locale.
The mobile platform may be staffed by staff to facilitate MBU functions and other functions of the mobile platform. The staff may at least in part be locale-based. The locale-based staff may at least in part include, and draw on the talents and training of, available locale-based bank employees.
Functions of the mobile platform—carried out by the staff and/or through apparatus and methods of the invention—may include maintenance, transport, security, banking operations, business-support, communications, and interfacing with and between the locale-residents/citizenry and an appropriate disaster-relief agency.
The appropriate agency for interfacing may be a local governing body, a state law-enforcement body, the National Guard, FEMA or some other agency/body with authority over the locale. The appropriate agency for interfacing may be the Red Cross, an insurance company handling claims from the locale or some other agency/body with authority over relief efforts that may be provided by the mobile platform. The appropriate authoritative agency (hereinafter, “authority/agency”) for interfacing may change in the course of the deployment of the mobile platform. There may be more than one authority/agency with which the mobile platform may interface in performing its functions.
A pre-deployment interface function of the mobile platform with the authority/agency may involve a determination of practicality and safety of deployment. A pre-deployment interface function of the mobile platform with the authority/agency may involve a determination of timing and/or location of the deployment. A pre-deployment interface function of the mobile platform with the authority/agency may involve a determination of a selection and extent of functions of the mobile platform to be activated upon deployment.
Such determinations may change in the course of the deployment of the mobile platform. The change may depend on assessment of the impairment of locale-infrastructure in severity, extent and forecasted duration. The change may depend on assessment of availability of resources within the locale. The change may depend on assessment of the capabilities of the deployed mobile platform. Such assessments may involve interface functions of the mobile platform with the authority/agency. Such interfacing may involve the exchange of information from the deployed mobile platform and/or from the relevant authority/agency.
The mobile platform may serve at least in part as a locale-deployed hub for some operations of the authority/agency. The mobile platform may serve at least in part as a locale-deployed hub for supporting some operations of locale-based business. The mobile platform may serve at least in part as a locale-deployed hub at which bank customers may perform some banking operations.
The objects and advantages of the invention will be apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings, in which like reference characters refer to like parts throughout, and in which:
Apparatus, methods and media for providing locale-associated disaster-relief services are provided. The apparatus may include, and the methods and media may involve, components and functions that provide disaster-relief functions to locale-associated residents/citizenry and institutions. The disaster-relief functions provided may involve banking, business-support and/or interfacing with the authority/agency.
In the wake of the disaster, locale-infrastructure may be impaired. Functioning of the invention despite impairment of locale-infrastructure, may involve activation of the mobile platform in the locale. The mobile platform may be associated with an entity. The mobile platform may be activated by the entity. The entity may be a bank. The mobile unit may include an ATM. The mobile platform may serve as a platform for other apparatus, methods and media of the invention.
The apparatus may include, and the methods and media may involve, a receiver for receiving information involved in the functioning of the invention. The receiver may be configured to receive information from a client. The information received from the client may be identification information. The identification information may be associated with an identity claimed by the client. The client may be a locale-associated resident/citizen, banking customer, entity-accountholder, institution and/or business. The client may have been impacted by the disaster. The client may have been dispossessed of client-borne documentation of client-identification.
The identification information received by the receiver may comprise information contained in client-borne documentation such as a driver's license. The identification information received by the receiver may comprise an item of client-knowledge (e.g., a Social Security number). The identification information received by the receiver may comprise biometric information pertaining to the client (e.g., a fingerprint, a voiceprint). The identification information received by the receiver may include the client's name, address, photograph, biometric data and/or any other suitable identifying information. The identification information received by the receiver may include bank-relevant information (e.g., an account number, a PIN, an answer to a bank security question).
The apparatus may include, and the methods and media may involve, a logic processing unit for processing information involved in the functioning of the invention. The logic processing unit may process the identification information received by the receiver.
Processing of the identification information of the client may include correlation of the identification information with stored information accessible to the mobile platform. Stored information accessible to the mobile platform may be resident on the mobile platform and/or may be accessed via the communications unit of the mobile platform. Stored information used in such correlation may include information contained in bank records, property ownership records, credit-rating files, government files, disaster rolls, law-enforcement records, national security alert lists and/or in any other suitable source of information. Such other source of information may include the mobile platform; informational data may be received, processed and/or stored in the course of the functioning of the mobile platform. Mobile platform informational data may pertain to the client; mobile platform informational data may be pertinent to correlation of identification information of the client. The correlation may be performed at the mobile platform and/or at a site accessible to the mobile platform.
The correlation may disconfirm the identity claimed by the client. The correlation may neither disconfirm nor confirm the identity claimed by the client. The correlation may confirm the identity claimed by the client. Confirmed identity of the client may be associated with other information pertaining to the client. The other information may pertain to the client's finances, to the client's legal status and/or to another suitable information-set pertaining to the client. Results of the correlation may supplement the identification information received from the client.
Processing of the identification information of the client may include the identification information being registered in a registry. The registry may be a database. The registry may be resident on the mobile platform and/or at a site accessible to the mobile platform. The registered identification information may include the results of the correlation. The registered identification information may be updated. Updating of the registered identification information may involve information associated with a subsequent correlation. Updating of the registered identification information may involve client-pertaining information not available prior to the subsequent correlation.
Updating of the registered identification information may involve the receiver subsequently receiving information. Updating of the registered identification information may involve the processor subsequently processing information. Updating of the registered identification information may involve previously received and/or processed information. Information of an update may include information descriptive of an impact of the event. Information descriptive of the impact of the event may be subject to confirmatory correlation with other information. The information of the update may include information from the client and/or pertinent to the client. The information of the update may be descriptive of the impact of the event upon the client
Other information received from the client may involve a request from the client that a disaster-relief function of the invention be provided. The identification information of the client may serve as a basis for providing disaster-relief functions of the invention to the client.
The apparatus may include, and the methods and media may involve, a unit for producing a physical article of client-identification. Representative apparatus for production of the article of client-identification are Zebra ZXP Series 8 ID Card Printers available from Zebra Technologies Corporation (Lincolnshire, Ill.).
The article of client-identification may be an ATM card, a check and bank card, a credit card, a debit card, a stored-value card, a card with a magnetic strip, a bar-coded article, an instrument or device that includes a contactless chip, such as an ISO14443-compliant contactless chip, a cell phone, a personal data assistant or any other suitable electronic, encoded or information-bearing article.
The article of client-identification may feature a photographic identifier of the client. The article of client-identification may feature biometric data of the client.
The article of client-identification may incorporate an identification code, symbol, brand, mark and/or number unique to the article of client-identification. The article of client-identification may incorporate some or all of the registered identification information of the client. The article of client-identification may be produced for the client. The client-article of identification may be issued to the client. The issuing may involve physically associating the client-article of identification with the client.
The article of client-identification may be issued activated. The article of client-identification may be issued unactivated. Activation of the unactivated article of client-identification may require an activation step. The activation step may be a lapse of a delay period from issue.
The registered identification information and/or another stored client-related information-set may be updated to incorporate the issuing and/or activation of the article of client-identification. Updating of the information may involve the code, symbol, brand, mark and/or number unique to the article of client-identification. The issued article of client-identification may be deactivated.
The issued, activated article of client-identification may be used by the client. Use of the article of client-identification may require presentation of confirming input such as a knowledge-item (e.g., a PIN) and/or a biometric datum (e.g., an iris scan). Use of the article of client-identification may be limited to a designated location and/or time-period. Use of the article of client-identification may be limited to a designated usage. The designated limit(s) of location, time-period and/or usage may be updated. The article of client-identification may maintain a record of its location and/or use. The article of client-identification may transmit a record of its location and/or use.
The article of client-identification may at least in part authenticate the client for the client to be provided a disaster-relief function of the mobile platform. Presentation of the article of client-identification at the mobile platform may be required for the client to be provided the disaster-relief function. The client may request to be provided the disaster-relief function. The request may be received by the receiver. Information of the article of client-identification may be received by the receiver. The request and/or the information of the article of client-identification may be processed by the logic processing unit. The processing may involve the registered client-related identification information. The client may be provided the disaster-relief function. The registered client-related identification information may be updated to incorporate the request for, and/or the providing of, the disaster-relief function.
Banking Disaster-Relief
The requested disaster-relief function that may be provided the client may involve banking. The client that may be provided the banking disaster-relief functions may be a locale-associated resident/citizen, banking customer, entity-accountholder or any other suitable client. The banking disaster-relief function that may be provided the client may involve the MBU.
The banking disaster-relief function that the client may be provided may involve receiving from the client a request for access to a bank account. The request from the client for access to the account may be processed.
The request from the client for access to the account may be through the ATM. The processing of the request through the ATM may involve the authentication of the client as the accountholder. The processing of the request may involve the logic processing unit. The processing of the request may involve the communications unit.
The account may be a non-entity account. The client may be in possession of a non-entity account-associated ATM card. The request for access to the account may be processed as typical of use of an entity ATM by a non-entity ATM card-holder. The request for access to the non-entity account may be processed with a limit not typical of use of an entity ATM by a non-entity card-holder.
The account may be an entity account. The client may be in possession, from before the event, of an entity account-associated ATM card. Alternatively or additionally, the client may be in possession of an entity account-associated ATM card issued after the event. The entity account-associated ATM card issued after the event may be the issued article of client-identification. The request for access to the account may be processed as typical of use of an entity ATM by an entity ATM card-holder. The request for access to the entity account may be processed with a limit not typical of use of an entity ATM by an entity ATM card-holder.
The ATM may provide a full range of banking functions typical of ATMs. The range of banking functions provided by the ATM may be subject to a limit.
The limit on ATM use may be imposed by the entity; e.g., the amount of ATM funds withdrawn and/or deposited per transaction may be limited by the entity. The limit on ATM use may be imposed by a banking institution that is not the entity; e.g., a non-entity bank administering the account that the non-entity ATM card-holder client requests to access, may limit the frequency of ATM fund-withdrawal. The limit on ATM use may be imposed by the staff and/or the apparatus and methods of the mobile platform; e.g., the hours of ATM availability may be limited by a security function of the mobile platform. The limit on ATM use may be imposed by the authority/agency; e.g., the issued article of client-identification may have to be presented for the client to access the account through the ATM. The limit on ATM use may be subject to revision. The revision may correspond to review of the impact of the event on the locale. The review may be conducted in coordination with the authority/agency.
The request from the client for access to the account may be a request to establish an account to be administered by the entity; i.e., the request may be to open a new entity account, with the client as accountholder. The client opening the account may be outside the locale (e.g., the client may be an evacuee from the locale and/or a relative, friend or other benefactor of a party within the locale) and may designate an accountholder within the locale.
The client may be within the locale. The client may be in possession, from before the event, of assets that the client may wish to deposit in the new entity account. The assets may be cash in-hand. The assets may be bank-transferred from an existing account of which the client is an accountholder. The assets may be funds allotted to the client through the authority/agency (e.g., from FEMA and/or from an insurance company of the client).
The request from the client for access to the account may be a request to access banking functions offered by the entity account. Accessing banking functions offered by the entity account may involve the entity servicing the entity account.
Access to the banking functions of the account may require authentication of the client as the accountholder. Authentication of the client may require presentation by the client of accountholder-identification. Authentication of the client may require presentation by the client of the issued article of client-identification.
Authentication may result in granting the requested access to the account. Access to the account may offer a full range of banking functions typical of entity accounts. The account may offer banking functions with an extent in funds, location and/or time typical of entity accounts. The range and/or extent of banking functions offered by the entity account may be subject to a limit (e.g., the account may not feature overdraft privileges; the account may be accessible only at the mobile platform during specific hours). Another feature of banking functions offered by the entity account may be subject to a limit (e.g., client-bank confidentiality may be limited; informational data pertaining to the account may be selectively shared with the authority/agency). The limit on banking functions offered by the entity account may be imposed by the entity and/or the authority/agency. The limit on banking functions offered by the entity account may be imposed by the staff and/or by the apparatus and methods of the mobile platform.
The account may offer use of a banking card. The banking card may serve as a stored-value card. The account may offer ATM services; the account may offer use of an ATM card. The account may offer account checking; the account may offer use of a check card. The account may offer use of a debit card. The accountholder may be in possession, from before the event, of a banking, ATM, check and/or debit card associated with the entity account. Alternatively and/or additionally a banking, ATM, check and/or debit card associated with the entity account may be issued through the apparatus, methods and media, of the mobile platform. Use of the banking, ATM, check and/or debit card may require the issued article of client-identification. Use of the banking, ATM, check and/or debit card may be incorporated in the registry. The banking, ATM, check and/or debit card may be the issued article of client-identification.
Informational data generated—received, processed, registered, updated and/or stored—in the course of providing banking functions may reflect on a value of available and/or total funds resident on the mobile platform. Such informational data may be integrated with other informational data accessible to the mobile platform. Such integrated information may be used to assess current and projected resource-availability/need of the mobile platform and/or of the locale. Such assessment may be used to inform functions of the mobile platform. Such assessment may be shared with the authority/agency.
Business Disaster-Relief
The requested disaster-relief function that may be provided the client may involve business-support. The client that may be provided the business-support disaster-relief function may be a locale-associated business, institution, business banking customer, business entity-accountholder or any other suitable client. The issued article of client-identification and/or the registry may incorporate information related to the client being authorized to be provided business-support by the entity. The authorization may be arranged between the client and the entity before the event; e.g., a national chain of stores may have a standing financial arrangement with the entity for the entity to provide business-support to a chain-store in a disaster-impacted locale, the chain-store being the locale-associated client. The authorization may be arranged between the client and the entity and/or the mobile platform after the event; e.g., a locale-associated business may identify itself to the entity through the staff and/or apparatus and methods of the mobile platform, requesting business-support authorization that may be granted contingent upon confirmatory correlation of its platform-received information with other information.
The business-support disaster-relief function may be subject to a limit imposed by the entity and/or the authority/agency. The limit on the business-support disaster-relief function may be imposed by a body with authority over the locale-based business-support client; e.g., a regional franchiser may limit the business-support the entity may provide a locale-based franchisee; a state school system may limit the business-support the entity may provide a locale-based school's business office. The limit on the business-support disaster-relief function may be imposed by the staff and/or by the apparatus and methods of the mobile platform.
The business-support provided the client may involve banking. The business-support provided may be opening of a business entity account. The business-support provided may be servicing of a business entity account. Servicing of the business entity account may involve the entity extending loans to the client.
The business-support provided the client may involve electronic merchant services. The apparatus may include, and the methods and media may involve, a unit for providing electronic merchant services. The electronic merchant services provided by the staff and/or the apparatus, methods and media of the mobile platform may include card-transaction processing, check processing and/or any other suitable electronic merchant service.
Other electronic merchant service may include the staff and/or the apparatus, methods and media of the mobile platform providing the client with communications capabilities. The communications capabilities provided may involve the communications unit of the mobile platform for secure exchange of information between the mobile platform and sites within and/or beyond the locale.
The communications capabilities provided may include transmitting and/or receiving business wires. The communications capabilities provided may include business-to-business internet connectivity. Business-to-business internet connectivity may provide for critical business-to-business activity, such as inventory management and asset condition/capability reporting.
The communications capabilities provided may involve the issuing to the client of a remote communicating unit. The remote communicating unit may be configured for translocation to the client's site. The remote communicating unit may comprise a power-supplying unit. The remote communicating unit may be capable of using power supplied by the client. The remote communicating unit may be capable of securely communicating with client-site electronic merchant service equipment. The remote communicating unit may include a computer. The remote communicating unit may be configured to provide an electronic merchant service.
The remote communicating unit may be configured for communication with the mobile platform. The remote communicating unit may comprise its own transmitting and/or receiving unit. The remote communicating unit may communicate with the mobile platform as part of a local area network (LAN). The remote communicating unit may be capable of wireless communication via satellite to and/or from the mobile platform.
Use of the remote communicating unit may require presentation of the issued article of client-identification. Use of the remote communicating unit may enable the client to perform an electronic merchant service at the client's site despite impairment of locale-infrastructure. The electronic merchant service may include card-transaction processing and/or business-to-business internet connectivity.
Informational data generated in the course of providing business-support functions may allow for an estimate of the value of purchases made within the locale via entity banking cards, a tracking of goods and services moving into and/or sold within the locale and/or other business-related evaluations. Such informational data may be integrated with other informational data accessible to the mobile platform. Such integrated information may be used to assess current and projected resource-availability/need of the mobile platform and/or of the locale. Such assessment of may be used to inform functions of the mobile platform. Such assessment may be shared with the authority/agency.
Other Disaster-Relief
The requested disaster-relief function that may be provided the client may involve other disaster-relief functions. The other disaster-relief function may not be directly related to banking and/or business-support disaster-relief functions such as the aforementioned. The client that may be provided the other disaster-relief function may be a locale-associated citizen/resident, institution or any other suitable client. The issued article of client-identification and/or the registry may incorporate information related to the client being authorized to be provided other disaster-relief by the entity. The issued article of client-identification and/or the registry may incorporate information related to the client being provided disaster relief by the entity.
The disaster-relief may include providing the client capabilities of interfacing. The interfacing may involve the communications unit of the mobile platform for secure exchange of information between the mobile platform and sites within and/or beyond the locale. The interfacing may be with the authority/agency and/or with any other suitable party. Other parties with which interfacing may be provided may include a hospital, a church group and a relative of the client.
The interfacing may involve client-information being received and/or presented. The interfacing may involve the client receiving and/or presenting information. The client-information may involve the registered client-related identification information; e.g., client-status information sought by the authority/agency, the client's blood-type information sought by the hospital. The client-information may involve information sought by the client; e.g., information regarding welfare of the client's relative, information on the authority/agency's assessment of the impact of the event, information on filing an insurance claim.
The disaster-relief may include providing the client a service related to a non-entity body. The service provided the client may be a service of the non-entity body. The service may be issuing to the client a stored-value card. The value stored in the card may correspond to funds allotted the client by the non-entity body. The value stored in the card may be updated by the non-entity body. The value stored in the card may be deactivated by the non-entity body. The non-entity body may be the authority/agency, a charitable organization and/or any other suitable body. The stored-value card may be used by the client to pay for purchases of goods and/or services.
The stored-value card may be subject to a limit. The limit may be imposed by the entity and/or by the non-entity body. The stored-value card may be limited in the card's value, frequency of use, amount per use, location of use and in any other suitable limitable factor. Other limitable factors may include a duration of the card's activation and an identity of goods or services purchasable with the card. Limitable factors may be determined through assessment of availability of resources within the locale. The limit on the limitable factor may be subject to revision.
The disaster-relief may include providing the client an instrument by which the authority/agency may identify the client. The provided instrument may record and/or signal its location. The authority/agency may have a capability of tracking the client bearing the instrument. The provided instrument may be the stored-value card. The provided instrument may record and/or signal its use. The authority/agency may have a capability of following a buying pattern of the client using the instrument. Use of the instrument may require presentation of the issued article of client-identification. The instrument may be the issued article of client-identification.
The disaster-relief may involve maintaining a database of the impact of the event. The database may be updated in the course of the deployment of the mobile platform. The disaster-relief may involve providing information in the database to the client.
Informational data generated in the course of providing disaster-relief functions may allow for an estimate of the value of purchases made within the locale via stored-value cards, a tracking of client-movement within the locale, a measure of client-departure from the locale and/or other disaster-relief-related evaluations. Such informational data may be integrated with other informational data accessible to the mobile platform. Such integrated information may be used to assess current and projected resource-availability/need of the mobile platform and/or of the locale. Such assessment may be used to inform functions of the mobile platform. Such assessment may be shared with the authority/agency.
Illustrative embodiments of apparatus and methods in accordance with the principles of the invention may be described with reference to the accompanying drawings, which form a part hereof. It is to be understood that other embodiments may be utilized and structural, functional and procedural modifications may be made without departing from the scope and spirit of the present invention.
I/O module 109 may include a microphone, keypad, touch screen, fingerprint reader, biometric scanner, camera and/or stylus through which a user of device 101 may provide input, and may also include one or more of a speaker for providing audio output and a video display device for providing textual, audiovisual and/or graphical output. Software may be stored within memory 115 and/or storage (not shown) to provide instructions to processor 103 for enabling server 101 to perform various functions. For example, memory 115 may store software used by server 101, such as an operating system 117, application programs 119, and an associated database 111. Alternatively, some or all of server 101 computer executable instructions may be embodied in hardware or firmware (not shown).
Application programs 119 used by server 101 may contain, according to an illustrative embodiment of the invention, computer executable instructions for supporting disaster-relief functions.
Database 111 used by server 101 may provide, according to an illustrative embodiment of the invention, centralized storage of the informational data comprising the registry, facilitating interoperability of varied disaster-relief functions between different elements of the entity residing at different physical locations.
Server 101 may operate in a networked environment supporting connections to one or more remote elements, such as communication unit (“Comm. Unit”) 141 and non-locale site 151. Remote elements 141 and 151 may include personal computers or servers that comprise many or all of the elements described above relative to server 101. The network connections depicted in
Additionally, application programs 119 used by server 101, according to an illustrative embodiment of the invention, may include computer executable instructions for invoking user functionality related to communication, such as email, short message service (SMS), and voice input and speech recognition applications.
Computing device 101 and/or remote elements 141 or 151 may also be mobile terminals including various other components, such as a battery, speaker, and antennas (not shown).
Server 101, according to an illustrative embodiment of the invention, may implement disaster-relief functions as a process or set of processes within server 101 and/or distributed over one or more remote network-linked computers, such as may be included in remote elements 141 and 151.
Business Interface module 271 may provide several modes of business-support disaster-relief functions. Modes of business-support disaster-relief of Business Interface module 271 shown in
Agency Interface module 281 may provide several modes of agency interfacing disaster-relief functions. Modes of agency interfacing disaster-relief of Agency Interface module 281 shown in
Processes in accordance with the principles of the invention may include one or more features of the processes illustrated in
Activation of the mobile platform at step 304 may be performed as a single step activating all functionalities of the mobile platform. Activation of the mobile platform may be performed in discrete steps. Activation of the mobile platform may be partial, activating selected functionalities. The activated mobile platform may be deactivated. The deactivated mobile platform may be re-activated. Activation, deactivation and re-activation may be coordinated with the authority/agency, may be determined by locale-associated “facts on the ground” at the time and/or location of deployment, and/or may carried out in response to any suitable circumstance.
At step 306, the system may provide locale-associated disaster-relief services in accord with the extent of activation of step 304. Step 308 may be common to all disaster-relief services that the system may provide in step 306: At step 308, identification and registration may be carried out of locale-associated individuals and institutions. Locale-associated individuals and institutions that may be processed in step 308 may include those that may request banking disaster-relief services (depicted by Clients 310a); those that may request business-support disaster-relief services (depicted by Business 310b); and those that may request other disaster-relief services (depicted by Citizenry 310c). Identification may require confirmatory correlation with other information (not shown). Identification of Business individuals and institutions may require authorization (not shown). Identification may be accompanied or followed by registration of the individual or institution. Registration of the identification information of individuals and/or institutions may be updated (not shown).
At step 320, the system may provide banking disaster-relief services to Clients 310a. Provide Banking Services 320 may provide individuals and institutions access to bank accounts and other banking functions. Provide Banking Services 320 may comprise: ATM 322 (at which step, access to entity accounts and/or to non-entity accounts may be provided via ATM); Establish New Accounts 324 (at which step, new entity banking accounts may be opened); Service Existing Accounts 326 (at which step, a range of entity account bank services may be provided); and Issue Banking/ID Instrument 328 (at which step, access to accounts may be provided through issuance of a banking instrument such as a check/debit card and/or an identification card by which an individual or institution may be identified by the mobile platform without requiring re-processing via 310a of step 308).
At step 330, the system may provide business-support disaster-relief services to Business 310b. Provide Electronic Merchant Services 330 may provide individuals and institutions access to business bank accounts and other business-support functions. Provide Electronic Merchant Services 330 may comprise: Supply/Service Remote Platform-Communicating Units 332 (at which step, mobile platform-networked communication units that may be supplied to Business 310b sites distinct from the location of deployment may provide business-site-based access to electronic merchant services such as those depicted in steps 334, 336 and 338); Card-Transaction Processing 334 (at which step, business transactions that may be executed through credit/debit cards or similar purchase instruments may be processed at the mobile platform or, via the communication units of step 332, at business-sites); Check Processing 336 (at which step, business transactions that may be executed through checks or similar purchase instruments may be processed at the mobile platform or, via the communication units of step 332, at business-sites); and Business-to-Business Internet Connectivity 338 (at which step, access may be provided to internet and other sources of communication/information via the communication units of step 332 and/or communication functionalities of the mobile platform (not shown)).
At step 340, the system may provide banking disaster-relief services to Citizenry 310c. Provide Authority/Agency Interfacing Services 340 may provide locale-associated individuals and institutions access to information associated with the authority/agency and may provide the authority/agency access to informational-data pertaining to locale-associated individuals and institutions. Provide Authority/Agency Interfacing Services 340 may comprise: Maintain Event-Impact Database 342 (at which step, event-impact informational data associated with Citizenry 310c and associated with the authority/agency may be stored, correlated together with other event-impact information, and updated); Issue ID/Tracking Instrument 344 (at which step, interfacing with the authority/agency may be provided through issuance of an instrument such as a programmed cell phone and/or an identification card by which an individual or institution may be identified by the authority/agency without requiring re-processing via 310c of step 308; such instrument may feature tracking functions providing the authority/agency information associated with location and activity of the instrument); Issue Stored-Value Card 346 (at which step, interfacing with the authority/agency may be provided through issuance of an instrument such as a pre-loaded check/debit card for disbursement of authority/agency funds; such instrument may feature tracking functions providing the authority/agency information associated with location and activity of the instrument); and Provide Communication with Authority/Agency, Insurance Carrier 348 (at which step, Citizenry 310c may be provided interfacing with the authority/agency—which may comprise insurance companies handling locale-associated claims—allowing for information-exchange that may pertain to event-impact, the authority/agency and/or Citizenry 310c.)
At step 350, informational data generated in steps 320, 330 and 340 may be collected and correlated. Such collected and correlated informational data may be pertinent to availability of resources at the mobile platform and/or within the locale. Such collected and correlated data may inform the functions of steps 320, 330 and 340, as depicted by the double-headed arrows between those steps and step 350.
The system may use Integrate/Update/Share Resource-Availability Information 350 to inform other steps of process 300, such as steps 304 (e.g., triggering deactivation/re-activation) and step 306 (e.g., modifying the range of disaster-relief functions provided) (not shown).
As will be appreciated by one of skill in the art, the invention described in the aforementioned steps and parts of the figures and in the specification herein may be embodied in whole or in part as a method, a data processing system, or a computer program product. Accordingly, the invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software, hardware and any other suitable approach or apparatus.
Furthermore, such aspects may take the form of a computer program product stored by one or more computer-readable storage media having computer-readable program code, or instructions, embodied in or on the storage media. Any suitable computer readable storage media may be utilized, including hard disks, CD-ROMs, optical storage devices, magnetic storage devices, and/or any combination thereof. In addition, various signals representing data or events as described herein may be transferred between a source and a destination in the form of electromagnetic waves traveling through signal-conducting media such as metal wires, optical fibers, and/or wireless transmission media (e.g., air and/or space).
Thus, apparatus, methods and media for providing disaster-relief services according to the invention have been provided. Persons skilled in the art will appreciate that the present invention can be practiced in embodiments other than the described embodiments, which are presented for purposes of illustration rather than of limitation, and that the present invention is limited only by the claims that follow.
Number | Name | Date | Kind |
---|---|---|---|
4841897 | Claflin | Jun 1989 | A |
5726430 | Ruggirello | Mar 1998 | A |
5793882 | Piatek et al. | Aug 1998 | A |
6179358 | Hirayama et al. | Jan 2001 | B1 |
7007761 | Johnson, IV | Mar 2006 | B1 |
7280038 | Robinson | Oct 2007 | B2 |
7312712 | Worrall | Dec 2007 | B1 |
7377835 | Parkulo et al. | May 2008 | B2 |
7391298 | Campbell et al. | Jun 2008 | B1 |
7460020 | Reyes et al. | Dec 2008 | B2 |
7475809 | Romary | Jan 2009 | B2 |
7634361 | Levesque et al. | Dec 2009 | B2 |
7735726 | Bjoraker et al. | Jun 2010 | B2 |
7783316 | Mitchell | Aug 2010 | B1 |
7809595 | Breslin et al. | Oct 2010 | B2 |
7817982 | Chu et al. | Oct 2010 | B1 |
7909247 | Bonalle et al. | Mar 2011 | B2 |
8009035 | Vallaire | Aug 2011 | B1 |
8011578 | Bjoraker et al. | Sep 2011 | B2 |
8013733 | Vallaire | Sep 2011 | B1 |
8045455 | Agronow et al. | Oct 2011 | B1 |
8224285 | Sennett et al. | Jul 2012 | B2 |
8274897 | Pons et al. | Sep 2012 | B1 |
8280364 | Sennett et al. | Oct 2012 | B1 |
20020077137 | Akhteruzzaman et al. | Jun 2002 | A1 |
20020171552 | Tate | Nov 2002 | A1 |
20020184150 | Wong et al. | Dec 2002 | A1 |
20020188522 | McCall et al. | Dec 2002 | A1 |
20030069002 | Hunter et al. | Apr 2003 | A1 |
20030093789 | Zimmerman et al. | May 2003 | A1 |
20030125998 | McKenney et al. | Jul 2003 | A1 |
20030212494 | Alexander et al. | Nov 2003 | A1 |
20040023635 | Impson et al. | Feb 2004 | A1 |
20040070515 | Burkley et al. | Apr 2004 | A1 |
20040102178 | Williams | May 2004 | A1 |
20040192353 | Mason et al. | Sep 2004 | A1 |
20050001720 | Mason et al. | Jan 2005 | A1 |
20050060211 | Xiao et al. | Mar 2005 | A1 |
20050165633 | Huber | Jul 2005 | A1 |
20050197775 | Smith | Sep 2005 | A1 |
20050201527 | Meer et al. | Sep 2005 | A1 |
20050240378 | Smith et al. | Oct 2005 | A1 |
20050264412 | Levesque et al. | Dec 2005 | A1 |
20050273330 | Johnson | Dec 2005 | A1 |
20050282518 | D'Evelyn et al. | Dec 2005 | A1 |
20060089893 | Joseph et al. | Apr 2006 | A1 |
20060103154 | Berry | May 2006 | A1 |
20060144598 | Johnson, IV | Jul 2006 | A1 |
20060158329 | Burkley et al. | Jul 2006 | A1 |
20060265489 | Moore | Nov 2006 | A1 |
20070048710 | Olson | Mar 2007 | A1 |
20070103292 | Burkley et al. | May 2007 | A1 |
20070108270 | Bjoraker et al. | May 2007 | A1 |
20070124144 | Johnson | May 2007 | A1 |
20070139182 | O'Connor et al. | Jun 2007 | A1 |
20070216572 | Schnabel | Sep 2007 | A1 |
20070219814 | Moore | Sep 2007 | A1 |
20070219818 | Duthler et al. | Sep 2007 | A1 |
20070228145 | Diemer | Oct 2007 | A1 |
20070275690 | Hunter et al. | Nov 2007 | A1 |
20070296575 | Eisold et al. | Dec 2007 | A1 |
20080017709 | Kennedy | Jan 2008 | A1 |
20080053992 | DeBord | Mar 2008 | A1 |
20080088428 | Pitre et al. | Apr 2008 | A1 |
20080120639 | Walter et al. | May 2008 | A1 |
20080165949 | Hancock | Jul 2008 | A9 |
20080270208 | Kuczun et al. | Oct 2008 | A1 |
20080278311 | Grange et al. | Nov 2008 | A1 |
20080311894 | Klein et al. | Dec 2008 | A1 |
20080313087 | Joseph et al. | Dec 2008 | A1 |
20080318547 | Ballou et al. | Dec 2008 | A1 |
20080320572 | Connell et al. | Dec 2008 | A1 |
20090018869 | Greischar et al. | Jan 2009 | A1 |
20090018875 | Monatesti et al. | Jan 2009 | A1 |
20090093952 | Lassiter, Sr. | Apr 2009 | A1 |
20090099874 | Moncrease | Apr 2009 | A1 |
20090124232 | D'Arcy et al. | May 2009 | A1 |
20090196234 | Greene et al. | Aug 2009 | A1 |
20090233623 | Johnson | Sep 2009 | A1 |
20090239497 | Sennett et al. | Sep 2009 | A1 |
20090295560 | Koliopoulos | Dec 2009 | A1 |
20090325538 | Sennett et al. | Dec 2009 | A1 |
20100049485 | Lee | Feb 2010 | A1 |
20100057502 | Arguelles et al. | Mar 2010 | A1 |
20100150122 | Berger et al. | Jun 2010 | A1 |
20100250378 | Bjoraker et al. | Sep 2010 | A1 |
20110003576 | Sun et al. | Jan 2011 | A1 |
20110081884 | Sennett et al. | Apr 2011 | A1 |
20110117878 | Barash et al. | May 2011 | A1 |
20110130636 | Daniel et al. | Jun 2011 | A1 |
20110181408 | Greenis et al. | Jul 2011 | A1 |
20110181443 | Gutierrez et al. | Jul 2011 | A1 |
20110215985 | Kaplan et al. | Sep 2011 | A1 |
20120028600 | Vallaire | Feb 2012 | A1 |
20120030124 | Cronkright et al. | Feb 2012 | A1 |
20120046822 | Anderson | Feb 2012 | A1 |
20120047187 | Daus | Feb 2012 | A1 |
20120066139 | Guzman et al. | Mar 2012 | A1 |
20120076134 | Brownrigg | Mar 2012 | A1 |
20120078787 | Mehew et al. | Mar 2012 | A1 |
20120150783 | Jung et al. | Jun 2012 | A1 |
20120282875 | Park et al. | Nov 2012 | A1 |
Entry |
---|
Wireless/Portable Internet Data Center Facility; IBM technical Disclosure Bulletin, Nov. 2001, UK; 2-pages. |
Number | Date | Country | |
---|---|---|---|
20130211859 A1 | Aug 2013 | US |