[go: up one dir, main page]

WO2008150740A1 - Enregistrement de consommateur par l'intermédiaire d'un dispositif mobile - Google Patents

Enregistrement de consommateur par l'intermédiaire d'un dispositif mobile Download PDF

Info

Publication number
WO2008150740A1
WO2008150740A1 PCT/US2008/064675 US2008064675W WO2008150740A1 WO 2008150740 A1 WO2008150740 A1 WO 2008150740A1 US 2008064675 W US2008064675 W US 2008064675W WO 2008150740 A1 WO2008150740 A1 WO 2008150740A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
block
physical address
address
land line
Prior art date
Application number
PCT/US2008/064675
Other languages
English (en)
Inventor
Steven C. Roberts
Original Assignee
Shoptext, Inc.
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 Shoptext, Inc. filed Critical Shoptext, Inc.
Publication of WO2008150740A1 publication Critical patent/WO2008150740A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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]
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/4014—Identity check for transactions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42348—Location-based services which utilize the location information of a target
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Definitions

  • Exemplary embodiments of the disclosure are related generally to consumer registration via a mobile device.
  • Consumer registration via a mobile device may be tedious and time consuming given the complexities associated with providing address and/or payment information via text messaging, for example. If a user is forced into a complex interaction with a mobile device to register, the consumer may opt not to register.
  • the consumer may opt not to register.
  • Various exemplary embodiments of the disclosure provide a system including a communication module to receive a transmission associated with an identification number and including a number associated with a land line, an address determination module to determine a physical address based on the number associated with the land line, a confirmation module to confirm the physical address that was determined, and a user account module to associate the physical address with a user account, the user account being identified by the identification number.
  • Various exemplary embodiments of the disclosure also provide a method including receiving a transmission associated with an identification number and including a number associated with a land line, determining a physical address based on the number associated with the land line, confirming the physical address that was determined, and associating the physical address with a user account, the user account being identified by the identification number.
  • Various exemplary embodiments also provide a computer-accessible medium encoded with computer program code effective to receive a transmission associated with an identification number and including a number associated with a land line, determine a physical address based on the number associated with the land line, confirm the determination of the physical address, and associate the physical address with a user account, the user account being identified by the identificat i on number.
  • Figure 1 depicts an exemplary consumer registration system according to an embodiment of the disclosure.
  • Figure 2 depicts an exemplary integrated mobile application server according to an embodiment of the disclosure.
  • Figure 3A depicts an exemplary method of consumer registration according to an embodiment of the disclosure.
  • Figure 3B depicts an exemplary method of consumer registration according to an embodiment of the disclosure.
  • Figure 3 C depicts an exemplary method of consumer registration according to an embodiment of the disclosure.
  • Figure 4A depicts an exemplary method of consumer registration according to an embodiment of the disclosure.
  • Figure 4B depicts an exemplary method of consumer registration according to an embodiment of the disclosure.
  • Figure 4C depicts an exemplary method of consumer registration according to an embodiment of the disclosure.
  • Figure 5 depicts an exemplary method of obtaining an address of an intended recipient according to an embodiment of the disclosure.
  • Figure 6 depicts an exemplary screen display illustrating exemplary user account information according to an embodiment of the disclosure.
  • Exemplary embodiments provide systems and methods for consumer registration via, for example, a mobile device.
  • a mobile phone user may register to engage in a promotion or make a purchase using his or her mobile phone.
  • the user may first initiate contact with an integrated mobile application server by transmitting a request to the integrated mobile application server to engage in the promotion or make a purchase.
  • the integrated mobile application server may determine whether the user has an existing account. Upon a determination that the user does not have an existing account, the integrated mobile application server may initiate the registration process.
  • the integrated mobile application server may request that the user provide a phone number associated with a land line.
  • the integrated mobile application server may use this land line number to query a database to obtain a physical address associated with the land line number.
  • the integrated mobile application server may confirm with the user that the address is accurate. Once confirmed, the user may be registered and the integrated mobile application server may create a user account.
  • Registering via a mobile device in this manner may enable the user to register and engage in the promotion and/or purchase consumer products within a single interactive session.
  • a user may communicate registration information, including without limitation, a physical address and billing information to an integrated mobile application server to create a user account associated with the user and the integrated mobile application server.
  • FIG. 1 depicts an exemplary system 100 for consumer registration according to an embodiment of the disclosure.
  • System 100 may include a network 101, one or more users 104a- 104b associated with respective requesting devices 102a-102b and user systems 103a-103b, an integrated mobile application server 105, a land line public database 106, a zip code database 107, a carrier system 108, and a fulfillment system 109.
  • requesting devices 102a-102b user systems 103a-103b, integrated mobile application server 105, land line public database 106, zip code database 107, carrier system 108, and fulfillment system 109 may be coupled via network 101.
  • Network 101 may include an analog telephone network, a digital telephone network, a cellular telephone network (e.g., a code-division multiple access (“CDMA”) network, a time division multiple access (“TDMA”) network, a global system for mobile communication (“GSM”) network, a digital cellular or personal communication service (“PCS”) network, and/or an enhanced data GSM environment (EDGE) network), a public wide area network (“WAN”), such as the Internet, or, different connections, such as combinations of public and private WANs, local areas networks (“LANs”), wireless LANs, encrypted networks, body area networks, or other wired or wireless networks.
  • CDMA code-division multiple access
  • TDMA time division multiple access
  • GSM global system for mobile communication
  • PCS digital cellular or personal communication service
  • EDGE enhanced data GSM environment
  • Network 101 may be a packet- switched network and receive and transmit data via packets.
  • Network 101 may enable communication via the Internet.
  • Network 101 may also enable communication via short message service (“SMS”), enhanced messaging service (“EMS”), multimedia messaging service (“MMS”), electronic mail, instant messaging, and/or Wireless Application Protocol (“WAP”).
  • SMS short message service
  • EMS enhanced messaging service
  • MMS multimedia messaging service
  • WAP Wireless Application Protocol
  • network 101 may include one, or any number of the exemplary types of networks mentioned above operating as a stand-alone network or in cooperation with each other. Use of the term network herein is not intended to limit the network to a single network.
  • Requesting devices 102a- 102b may be any device capable of communicating with, for example, integrated mobile application server 105, via network 101.
  • requesting devices 102a- 102b may include, but are not limited to: e.g., any computer device, or communications device including, e.g., a personal computer (PC), a workstation, a mobile device, a phone (e.g., a cellular phone), a handheld PC, a personal digital assistant (PDA), a thin system, a fat system, network appliance, an Internet browser, a paging device, an alert device, a television, an interactive television, a receiver, a tuner, a high definition (HD) television, an HD receiver, a video-on-demand (VOD) system, a server, or other device.
  • PC personal computer
  • PDA personal digital assistant
  • requesting devices 102a- 102b may also include an interface to display information received from, for example, integrated mobile application server 105 and/or carrier system 108 over network 101.
  • requesting devices 102a- 102b may be a wireless device, such as a mobile phone or like device, that may be capable of communicating via the Internet, short message service (“SMS”), enhanced messaging service (“EMS”), multimedia messaging service (“MMS”), electronic mail, instant messaging, and/or Wireless Application Protocol ("WAP").
  • SMS short message service
  • EMS enhanced messaging service
  • MMS multimedia messaging service
  • WAP Wireless Application Protocol
  • User systems 103a-103b may also be any device capable of communicating with, for example, integrated mobile application server 105, via network 101.
  • user systems 103a-103b may include, but are not limited to: e.g., any computer device, or communications device including, e.g., a personal computer (PC), a workstation, a mobile device, a phone (e.g., a cellular phone), a handheld PC, a personal digital assistant (PDA), a thin system, a fat system, network appliance, an Internet browser, a paging device, an alert device, a television, an interactive television, a receiver, a tuner, a high definition (HD) television, an HD receiver, a video-on-demand (VOD) system, a server, or other device.
  • user systems 103a-103b may also include an interface to display information received from, for example, integrated mobile application server 105 land line public database 106, zip code database 107, and/or fulfillment system 109
  • user systems 103a- 103b may be computer systems that may be capable of communicating via the Internet.
  • User systems 103a-103b may include a web browser client installed on user system 103a- 103b, such as INTERNET EXPLORER, NAVIGATOR, or FIREFOX web browser programs, offered by Microsoft Corporation of Redmond, Washington, Time Warner of New York, New York, and the Mozilla Foundation of Mountain View, California, respectively.
  • Users 104a- 104b may interact with respective requesting devices
  • Users 104a- 104b may, for example, interact with their respective requesting devices 102a- 102b to transmit text messages via network 101 to integrated mobile application server 105 to engage in a promotion and/or purchase consumer products.
  • user 104a may interact with requesting device 102a to transmit a text message including the phrase "promo" to a number associated with a common short code (“CSC”) that may be associated with integrated mobile application server 105.
  • CSC common short code
  • user 104b may interact with requesting device 102b to transmit a text message including the phrase "buy” to a number associated with a common short code (“CSC") that may be associated with integrated mobile application server 105.
  • CSC common short code
  • a CSC may represent a special telephone number that may be used to address SMS and/or MMS messages from mobile phones.
  • Users 104a- 104b may also interact with respective requesting devices 102a- 102b to receive text messages from integrated mobile application server 105.
  • Users 104a- 104b may also interact with respective requesting devices 102a- 102b to interact with an interactive voice recognition (“IVR”) system that may be associated with integrated mobile application server 105.
  • IVR interactive voice recognition
  • Users 104a- 104b may, for example, interact with respective user systems 103a-103b to access user account information associated with integrated mobile application server 105.
  • users 104a- 104b may log into integrated mobile application server 105 to access and/or edit user account details such as, address information, payment information, gift recipient information, order history, and/or any other account information as will be described in greater detail below.
  • integrated mobile application server 105 may coupled to network 101 and may enable consumer registration via a mobile device as will be described in greater detail below.
  • Integrated mobile application server 105 may include an integrated mobile application server as shown and described in U.S. Patent Application No. 1 1/125,833, filed on March 17, 2005, now U.S. Patent No. ___ , the content of which is incorporated herein by reference.
  • integrated mobile application server 105 may be coupled to network 101 to communicate with users 104a- 104b via respective requesting devices 102a-102b and/or user systems 103a-103b, land line public database 106, zip code database 107, carrier system 108, and fulfillment system 109.
  • Land line public database 106 may include any data storage device or devices that may store physical address information and associated land line phone numbers.
  • land line public database may store an address 123 Any Street, Anytown, AnyState associated with land line number (111) 222-333.
  • Land line public database 106 may include software, hardware, and/or firmware that may receive a transmission including a land line number (e.g., (11 1) 222-3333) requesting the associated physical address and return the physical address associated with the land line number to the requestor, sender of the transmission, and/or entity accessing land line public database 106.
  • land line public database 106 may be physically separated from integrated mobile application server 105 as illustrated in Figure 1.
  • land line public database 106 may be integrated logically separated, but integral with integrated mobile application server 105.
  • Zip code database 107 may include any data storage device or devices that may store zip codes (e.g., postal codes) and associated city and state information.
  • zip code database 107 may store a zip code (e.g., 22222) associated with city Anytown and state AnyState.
  • Zip code database 107 may include software, hardware, and/or firmware that may receive a request including a zip code (e.g., 22222) and return the associated city and state information.
  • Carrier system 108 may include any system associated with a mobile service carrier.
  • carrier system 108 may include systems associated with mobile service carriers including, without limitation, Verizon Wireless, Nextel Communications, AT&T Wireless, Cingular Wireless, T-Mobile Communications and/or the like.
  • Carrier system 108 may store a user's carrier account information.
  • carrier system 108 may include one or more data storage devices that may store a user's mobile phone number and associated account information.
  • the associated carrier account information may include, without limitation, the user's billing address.
  • integrated mobile application server 105 may access a user's mobile phone account to obtain the user's billing address information.
  • carrier system 108 may include software, hardware, and/or firmware that may receive a request associated with a user's mobile phone number and return the user's billing address information.
  • Fulfillment system 109 may include any system associated with filling orders for consumer products, for example.
  • fulfillment system 109 may include software, hardware, and/or firmware that may enable fulfillment system to receive user, consumer product, and/or address information and fulfill the order.
  • a fulfillment system may receive a user's name, the user's address (e.g., 123 Any Street, Anytown, AnyState 22222), and consumer product information (e.g., a Stock Keeping Unit (SKU) and a quantity) to fulfill an order.
  • SKU Stock Keeping Unit
  • Figure 2 depicts an exemplary integrated mobile application server
  • Integrated mobile application server 200 may integrate one or more requesting devices and/or user systems with a fulfillment system to enable users to engage in a promotion and/or purchase consumer goods.
  • Integrated mobile application server 200 may provide an application server framework that may support multiple telecommunication channels.
  • integrated mobile application server 200 may include one or more of the following modules: a communication module 201, an address determination module 202, a confirmation module 203, a user account module 204, a database 205, an interactive voice recognition ("IVR") system 206, and a processor 207.
  • each module of integrated mobile application server 200 may interact and cooperate with the other modules to enable the integration of requesting devices with fulfillment systems, for example.
  • the various modules of integrated mobile application server 200 may be part of a single system, or may be part of a plurality of systems that maybe physically and/or logically separated.
  • Communication module 201 may include hardware, software, and/or firmware to enable communication between and among the modules of integrated mobile application server 200 and between of integrated mobile application server
  • communication module 201 may allow communication between user account module 204 and database 205, and/or between communication module 201 and interactive voice recognition system 205 and/or between confirmation module 203 and address determination module 202.
  • communication module may allow communication between of integrated mobile application server 200 and elements of a network including, without limitation, requesting devices, user systems, land line public databases, zip code databases, carrier systems, and fulfillment systems.
  • Communication module 201 may communicate with network elements via any number of protocols. Communication module 201 may also enable integrated mobile application server
  • communication module 200 to make requests to network elements.
  • communication module 200 to make requests to network elements.
  • communication module 200 to make requests to network elements.
  • communication module 200 to make requests to network elements.
  • communication module 200 to make requests to network elements.
  • communication module 200 to make requests to network elements.
  • communication module 200 to make requests to network elements.
  • communication module 200 to make requests to network elements.
  • communication module 200 to make requests to network elements.
  • communication module 200 to make requests to network elements.
  • communication module 200 to make requests to network elements.
  • Communication module 201 may enable of integrated mobile application server 200 to request a land line number and/or zip code from a requesting device.
  • Communication module 201 may also enable integrated mobile application server 200 to query external databases that may be associated with, for example, land line public databases, zip code databases, and/or carrier systems.
  • Communication module 201 may enable integrated mobile application server 200 to receive responses from requesting devices and/or other network elements (e.g., user systems and/or databases).
  • Address determination module 202 may include hardware, software, and/or firmware to enable integrated mobile application server 200 to determine a physical address associated with a land line number, for example. Address determination module 202 may also enable integrated mobile application server 200 to determine city and state information associated with a zip code. Address determination module 202 may also enable integrated mobile application server 200 to compile a physical address based on a zip code, city and state information, and a street address.
  • Confirmation module 203 may include hardware, software, and/or firmware to enable integrated mobile application server 200 to transmit and receive confirmations to and from requesting devices.
  • confirmation module 203 may include hardware, software, and/or firmware to enable integrated mobile application server 200 to transmit and receive confirmations to and from requesting devices.
  • Confirmation module 203 may enable integrated mobile application server 200 to transmit an address or PIN confirmation to a requesting device.
  • Confirmation module 203 may also enable integrated mobile application server 200 to receive confirmation responses from requesting devices, for example.
  • User account module 204 may include hardware, software, and/or firmware to enable integrated mobile application server 200 to create, update, and/or maintain user account information (See, Figure 6, for example). User account module 204 may interact with database 205 to store user account information associated with integrated mobile application server 200. User account module 204 may also determine user account information based on an identification number. For example, given a mobile phone number, user account module 204 may retrieve associated user account information from database 205. Also, user account module
  • address determination module 204 may cooperate and/or interact with address determination module to store addresses associated with user accounts.
  • Database 205 may include one or more data storage devices associated with integrated mobile application server 200.
  • Database 205 may store user account information, consumer product information (e.g., unique identifiers and associated consumer product information), land line number information, zip code information, carrier system information, and/or any other information that may be used by integrated mobile application server 200.
  • consumer product information e.g., unique identifiers and associated consumer product information
  • land line number information e.g., zip code information, carrier system information, and/or any other information that may be used by integrated mobile application server 200.
  • Integrated voice recognition system 206 may include hardware, software, and/or firmware that may provide interactive voice response via telephone systems.
  • IVR 206 may enable customers to interact with integrated mobile application server 200 to provide information to integrated mobile application server 200.
  • IVR 206 may call a requesting device to initiate an interactive voice response session during which a customer inputs land line number information, zip code information, payment information, and/or the like.
  • rVR 206 may cooperate with database 205 to store information received via IVR 206.
  • Processor 207 may include hardware, software, and/or firmware to enable the operation of integrated mobile application server 200.
  • processor 207 may include hardware, software, and/or firmware to enable the execution of instructions to perform the operations of integrated mobile application server 200.
  • Figures 3A, 3B, and 3C depict a flow chart 300 illustrating an exemplary method for consumer registration according to an embodiment of the disclosure.
  • a user e.g., a consumer
  • a request may be received.
  • an integrated mobile application server may receive a request from a requesting device.
  • This request may be associated with an identification number that may be associated with the requesting device.
  • the request may be associated with a mobile number of a mobile phone or like device.
  • the request may be transmitted from a requesting device to the integrated mobile application server in the form of a text message, SMS message, EMS message, MMS message, electronic mail, instant message, wireless web upload, WAP mini site link.
  • the request received may also include a unique identifier or code that is associated with a consumer product.
  • the request may include a unique identifier "BIC" which is associated with a Blue Bic® ballpoint pen.
  • a user of a requesting device may transmit a text message to a CSC associated with the integrated mobile application server.
  • a determination may be made as to whether the received request is related to a promotion or a purchase.
  • An integrated mobile application server may store information associating the unique identifier or code with the an indication as to whether the unique identifier is associated with a promotion or a purchase.
  • the integrated mobile application server may store information associating the unique identifier "BIC" with a consumer product promotion.
  • the integrated mobile application server may store information associating the unique identifier "BIC" with a consumer product being purchased.
  • an integrated mobile application server may query a database using the unique identifier as a key into the database. Upon a determination that the request is for a promotion, flow chart 300 may proceed to block 303. Upon making a determination that the request is for a purchase, flow chart 300 may proceed to block 324.
  • a user may be identified. For example, upon receiving a request for a promotion, in block 303, an integrated mobile application server may identify the user by determining the user's identification number, and if applicable, an associated carrier service. For example, where a request is in the form of a text message transmitted by the user from a mobile phone (e.g., (123) 456-7890), an integrated mobile application server may identify the user by determining the user's mobile phone number and, if applicable, the user's mobile phone carrier service (e.g., T-Mobile).
  • a mobile phone carrier service e.g., T-Mobile
  • a determination may be made as to whether the user has an account associated with the identification number.
  • an integrated mobile application server may store user accounts that may be identified by an identification number. Upon identifying the user in block 303, an identification number may be determined. This identification number may be used to query a user account database associated with an integrated mobile application server to determine whether the user has an account. For example, where a user's associated identification number is (123) 456-7890, an integrated mobile application server may query an associated user account database using a key such as 1234567890 to determine whether the user has an associated account.
  • flow chart 300 may proceed to block 315.
  • flow chart may proceed to block 305.
  • a user account may be created.
  • an integrated mobile application server may create account in an associated user account database.
  • This account may be identified by an identification number associated with the user and/or requesting device.
  • the account may be identified by the mobile phone associated with the user and/or requesting device (e.g., (123) 456-7890 or 1234567890)
  • the user account may store associated user account information as will be described in greater detail below with respect to Figure 6.
  • a land line number may be requested.
  • a land line number may be used to obtain physical address information associated with the user and/or a gift recipient.
  • an integrated mobile application server may communicate with the requesting device to prompt the user to transmit a land line number to the integrated mobile application server,
  • the integrated mobile application server may transmit a message (e.g., a text message) to the requesting device and/or a device associated with the identification number prompting the user to reply with a land line number.
  • an integrated mobile application server may interact with an IVR system to communicate with the requesting device and/or a device associated with the identification number to prompt the user to input a land line number into the IVR.
  • a land line number may be received.
  • An integrated mobile application server may receive the land line number from a requesting device and/or device associated with the identification number.
  • the land line number may be received in a text message transmitted to a CSC associated with the integrated mobile application server.
  • a mobile phone associated with the identification number may transmit a text message including "1112223333" in the body of the message as a land line number.
  • a user may input (e.g., speak and/or enter via a keypad associated with the requesting device) the land line number "1112223333" into the IVR.
  • the land line number may be transmitted to the integrated mobile application server.
  • a physical address associated with the received land line number may be obtained.
  • an integrated mobile application server may access a land line public database and query the land line public database for a physical address associated with the land line number.
  • the integrated mobile application server may communicate with the land line public database via a network.
  • the land line database may be integral with the integrated mobile application server.
  • a determination may be made as to whether a physical address was obtained from the land line public database. For example, if the land line public database is queried and a physical address is associated with the land line number, a determination may be made that the physical address was obtained. If the land line public database is queried and a physical address is not associated with the land line number or there is not an entry in the land line public database associated with the land line number, a determination may be made that a physical address was not obtained. Upon a determination that a physical address was obtained, flow chart 300 may proceed to block 310. Upon a determination that a physical address was not obtained, flow chart may proceed to block 319.
  • an address confirmation may be transmitted.
  • an integrated mobile application server may communicate with the requesting device to confirm that the physical address obtained from the land line public database is correct and/or accurate.
  • the integrated mobile application server may transmit a message (e.g., a text message) to the requesting device and/or a device associated with the identification number prompting the user to reply with a confirmation indicating that the physical address is correct and/or accurate.
  • the integrated mobile application server may transmit a text message to the requesting device prompting the user to reply "1" if the physical address is "123 Any Street, Anytown, AnyState 22222" or reply “2" if the address is not s "123 Any Street, Anytown, AnyState 22222.”
  • an integrated mobile application server may interact with an IVR system to communicate with the requesting device and/or a device associated with the identification number to communicate the address "123 Any Street, Anytown, AnyState 22222" to the requesting device and prompt the user to reply "Yes” or "No” into the IVR (by speaking a response or inputting a "1” for "Yes” or “2” for "No” into a keypad associated with the requesting device).
  • an address confirmation may be received.
  • An integrated mobile application server may receive the text message and/or IVR confirmation response from the requesting device.
  • a determination may be made as to whether the physical address has been confirmed. For example, if the user replies to a text message with "1" to confirm or inputs "Yes” or “1” into an IVR, the physical address may be confirmed. If, for example, the user replies to a text message with a "2" to confirm or inputs "No” or "2" into an IVR, the physical address may not be confirmed. Upon a confirmation of the physical address, flow chart 300 may proceed to block 313. Upon a failed confirmation of the physical address, flow chart 300 may proceed to block 319.
  • an account may be updated.
  • An integrated mobile application server may update an account identified by an identification number associated with a requesting device to include the physical address. For example, account 1234567890 may be updated to include a physical address "123 Any Street, Anytown, AnyState 22222.”
  • the physical address may be transmitted to a fulfillment system.
  • an integrated mobile application server may communicate with a fulfillment system via a network to transmit the address to a fulfillment system.
  • consumer product information e.g., one Blue Bic® ballpoint pen
  • the fulfillment system may ship one Blue Bic® ballpoint pen to "123 Any Street, Anytown, AnyState 22222.”
  • a zip code associated with a physical may be requested.
  • an integrated mobile application server may communicate with the requesting device to prompt the user to transmit a zip code to the integrated mobile application server, hi an exemplary embodiment, the integrated mobile application server may transmit a message (e.g., a text message) to the requesting device and/or a device associated with the identification number prompting the user to reply with a zip code. Also, an integrated mobile application server may interact with an IVR system to communicate with the requesting device and/or a device associated with the identification number to prompt the user to input a zip code into the IVR.
  • a message e.g., a text message
  • a zip code may be received.
  • An integrated mobile application server may receive the zip code from a requesting device and/or device associated with the identification number.
  • the zip code may be received in a text message transmitted to a CSC associated with the integrated mobile application server.
  • a mobile phone associated with the identification number may transmit a text message including "22222" in the body of the message as a zip code.
  • a user may input (e.g., speak and/or enter via a keypad associated with the requesting device) the zip code "22222" into the IVR.
  • the zip code may be transmitted to the integrated mobile application server.
  • a city and state associated with a zip code may be determined.
  • a zip code database may store information associating zip codes with respective city and state information.
  • a zip code database may store information associating zip code "22222" with the city "Anytown” and state "AnyState.”
  • a zip code database may be queried for the associated city and state information. This associated city and state information may be returned to the integrated mobile application server.
  • a street address associated with a physical may be requested.
  • an integrated mobile application server may communicate with the requesting device to prompt the user to transmit a street address to the integrated mobile application server.
  • the integrated mobile application server may transmit a message (e.g., a text message) to the requesting device and/or a device associated with the identification number prompting the user to reply with a street address.
  • the integrated mobile application server may transmit a text message to a requesting device prompting a user to reply with a street address located in "Anytown, AnyState.”
  • an integrated mobile application server may interact with an IVR system to communicate with the requesting device and/or a device associated with the identification number to prompt the user to input a street address located in "Anytown, AnyState" into the IVR.
  • a street address may be received.
  • An integrated mobile application server may receive the street address from a requesting device and/or device associated with the identification number.
  • the street address may be received in a text message transmitted to a CSC associated with the integrated mobile application server.
  • a mobile phone associated with the identification number may transmit a text message including
  • a user may input (e.g., speak and/or enter via a keypad associated with the requesting device) the street address "123 Any Street” into the IVR.
  • the zip code may be transmitted to the integrated mobile application server.
  • Other information including, without limitation, the user's name, email address, and/or any other account information to create a user account may be requested and received in a similar manner as described.
  • a user account may be updated in a similar manner as described above for block 313. Once the user account is updated, the physical address may be transmitted to a fulfillment system in a similar manner as described above for block 314.
  • an address confirmation may be transmitted in a similar manner as described above for block 310.
  • an address confirmation may be received in a similar manner as described above for block 31 1.
  • a determination may be made as to whether the physical address has been confirmed in a similar manner as described above for block 312.
  • flow chart 300 may proceed to block 306. Upon a determination that a physical address has been confirmed, flow chart 300 may proceed to block 318.
  • a physical address may be transmitted to a fulfillment system in a similar manner as described above for block 314.
  • flow chart 300 may proceed to block 324.
  • a user may be identified in a similar manner as described above for block 303.
  • a determination may be made as to whether the user has an associated user account associated in a similar manner as described above for block 304. Upon a determination that the user has an associated user account, flow chart 300 may proceed to block 339. Upon a determination that a user does not have an associated user account, flow chart 300 may proceed to block 326. x
  • a user account may be created in a similar manner as described above for block 305.
  • a land line number may be requested in a similar manner as described above for block 306.
  • a land line number may be received in a similar manner as described above for block 307.
  • a physical address associated with the received land line number may be obtained in a similar manner as described above for block 308.
  • a determination may be made as to whether a physical address was obtained in a similar manner as described above for block 309. Upon making a determination that a physical address was obtained, flow chart 300 may proceed to block 336. Upon making a determination that a physical address was not obtained, flow chart 300 may proceed to block 331.
  • a zip code may be requested in a similar manner as described above for block 319.
  • a zip code may be received in a similar manner as described above for block 320.
  • a city and state associated with the zip code may be determined in a similar manner as described above for block 321.
  • a street address associated with the city and state may be requested in a similar manner as described above for block 322.
  • a street address may be received in a similar manner as described above for block 323.
  • flow chart may proceed to block 336.
  • an address confirmation may be transmitted in a similar manner as described above for block 310.
  • an address confirmation may be received in a similar manner as described above for block 311.
  • a determination may be made as to whether a physical address has been confirmed in a similar manner as described above for block 312. Upon a determination that a physical address has not been confirmed, flow chart 300 may proceed to block 331. Upon a determination that a physical address has been confirmed, flow chart 300 may proceed to block 341.
  • flow chart 300 may proceed to block 339.
  • a determination may be made as to whether a physical address is associated with the user account.
  • a user account may be identified by an identification number.
  • a user account database may be queried using the identification number. If a user account has an associated physical address, the physical address may be returned in response to the query. If a user account does not have an associated physical address, a null response may be returned in response to the query, for example.
  • flow chart 300 may proceed to block 327.
  • flow chart 300 may proceed to block 340.
  • a determination may be made as to whether payment information is associated with the user account.
  • a user account database may be queried using the identification number. If a user account has associated payment information, the payment information may be returned in response to the query. If a user account does not have associated payment information, a null response may be returned in response to the query, for example.
  • flow chart 300 may proceed to block 341. Upon a determination that a user account has associated payment information, flow chart 300 may proceed to block 346.
  • payment information may be requested.
  • an integrated mobile application server may communicate with the requesting device to prompt the user to transmit payment information to the integrated mobile application server,
  • the integrated mobile application server may transmit a message (e.g., a text message) to the requesting device and/or a device associated with the identification number prompting the user to reply with payment information.
  • an integrated mobile application server may interact with an IVR system to communicate with the requesting device and/or a device associated with the identification number to prompt the user to input payment information number into the IVR.
  • payment information may be received.
  • An integrated mobile application server may receive the payment information from a requesting device and/or device associated with the identification number.
  • the payment information may be received in a text message transmitted to a CSC associated with the integrated mobile application server.
  • a mobile phone associated with the identification number may transmit a text message including "111122223333444 explOlO" in the body of the message as payment information.
  • this payment information may be securely transmitted using, for example, any number of various encryption techniques.
  • a user may input (e.g., speak and/or enter via a keypad associated with the requesting device) the payment information (e.g., account number and/or associated expiration date) into the IVR.
  • the payment information may be transmitted to the integrated mobile application server.
  • a personal identification number (PIN) associated with a user account may be determined.
  • an integrated mobile application server may randomly determine a PIN to be associated with the user account.
  • the integrated mobile application server may communicate the PIN via a text message and/or IVR system.
  • user may select the PIN and communicate the PIN to the integrated mobile application server. This PIN may be associated with the user account and stored within the integrated mobile application server.
  • a user account may be updated in a similar manner as described above for block 313.
  • a transaction may be processed.
  • a request may include a unique identifier "BIC" that is associated with a Blue Bic® ballpoint pen.
  • an integrated mobile application server may interact with a fulfillment system to transmit the request for a Blue Bic® ballpoint pen to be shipped to a physical address associated with the user account.
  • Integrated mobile application server may also interact with a payment interface to process payment of the transaction in accordance with the associated payment information.
  • flow chart 300 may proceed to block 346.
  • a PIN confirmation may be transmitted.
  • an integrated mobile application server may communicate with the requesting device to request the PIN.
  • the integrated mobile application server may transmit a message (e.g., a text message) to the requesting device and/or a device associated with the identification number prompting the user to reply with the PIN.
  • the integrated mobile application server may transmit a text message to the requesting device prompting the user to reply with the user's PIN if the user desires to purchase "one Blue Bic® ballpoint pen to be shipped to 123 Any Street, Anytown, AnyState 22222.”
  • an integrated mobile application server may interact with an IVR system to communicate with the requesting device and/or a device associated with the identification number to communicate the PIN via the IVR (by speaking a response or inputting the PIN into a keypad associated with the requesting device).
  • a PIN confirmation may be received.
  • An integrated mobile application server may receive the text message and/or IVR confirmation response from the requesting device.
  • a determination may be made as to whether the PIN has been confirmed. For example, if the user replies to a text message with the correct PIN or inputs the correct PIN into the IVR, the PIN may be confirmed. If, for example, the user replies to a text message with an incorrect PIN or inputs an incorrect PIN into an IVR, the PIN may not be confirmed.
  • flow chart 300 may proceed to block 345.
  • flow chart 300 the transaction may be cancelled in block 349 or the PIN may be re-requested and flow chart 300 may proceed to block 347 to receive the PIN and subsequently confirm the PIN.
  • Figures 4A, 4B, and 4C depict a flow chart 400 illustrating an exemplary method for consumer registration according to an embodiment of the disclosure.
  • a user e.g., a consumer
  • a request may be received in a similar manner as described above for block 301.
  • a determination may be made as to whether the received request is related to a promotion or a purchase in a similar manner as described above for block 302.
  • flow chart 400 may proceed to block 403.
  • flow chart 300 may proceed to block 429.
  • a user may be identified in a similar manner as described above for block 303.
  • a determination may be made as to whether the user has an associated user account associated in a similar manner as described above for block 304. Upon a determination that the user has an associated user account, flow chart 400 may proceed to block 425. Upon making a determination that a user does not have an associated user account, flow chart 400 may proceed to block 405. [098] In block 405, a user account may be created in a similar manner as described above for block 305.
  • a land line number may be used to obtain a physical address associated with the user.
  • Carrier account information may also be used to obtain a physical address of the user.
  • an integrated mobile application server may need permission from the user to access the user's carrier account information.
  • a carrier may refer to a mobile phone carrier service.
  • Carrier account information may be associated with a carrier system. With permission from the user, an integrated mobile application server may access carrier account information via a network.
  • an integrated mobile application server may determine the user's carrier service (see block 303) and communicate with the requesting device to request permission to access the user's carrier account information and prompt the user to transmit a permission response to the integrated mobile application server.
  • the integrated mobile application server may transmit a message (e.g., a text message) to the requesting device and/or a device associated with the identification number requesting access to the user's "T-Mobile" account, for example, and prompting the user to reply "1" if permission is granted or "2" if permission is not granted.
  • an integrated mobile application server may interact with an WR system to communicate with the requesting device and/or a device associated with the identification number to prompt the user to input a permission response into the IVR.
  • a permission response may be received.
  • An integrated mobile application server may receive the permission response from a requesting device and/or device associated with the identification number.
  • the permission response may be received in a text message transmitted to a CSC associated with the integrated mobile application server.
  • a mobile phone associated with the identification number may transmit a text message including "1" in the body of the message as a permission response.
  • a user may input (e.g., speak and/or enter via a keypad associated with the requesting device) the permission response "Yes" or "1" into the IVR.
  • the permission response may be transmitted to the integrated mobile application server.
  • a determination may be made as to whether permission to access the user's carrier account information has been granted. For example, if the user replies to a text message with "1" to confirm or inputs "Yes” or “1" into an IVR, permission may be granted. If, for example, the user replies to a text message with a "2" to confirm or inputs "No” or “2" into an IVR, permission may not be granted. Upon a granting of permission, flow chart 400 may proceed to block 418. Upon permission not being granted, flow chart 400 may proceed to block 409. [0102] In block 409, a land line number may be requested in a similar manner as described above for block 306.
  • a land line number may be received in a similar manner as described above for block 307.
  • a physical address associated with the received land line number may be obtained in a similar manner as described above for block 308.
  • a determination may be made as to whether a physical address was obtained in a similar manner as described above for block 309. Upon a determination that a physical address was obtained, flow chart 400 may proceed to block 420. Upon a determination that a physical address was not obtained, flow chart 400 may proceed to block 413.
  • a zip code may be requested in a similar manner as described above for block 319.
  • a zip code may be received in a similar manner as described above for block 320.
  • a city and state associated with the zip code may be determined in a similar manner as described above for block 321.
  • a street address associated with the city and state may be requested in a similar manner as described above for block 322.
  • a street address may be received in a similar manner as described above for block 323.
  • carrier account information may be requested.
  • an integrated mobile application server may communicate with a carrier system via a network to query the carrier system and/or a database associated with the carrier system using the identification number. For example, an integrated mobile application server system may query carrier a database associated with carrier server system to return a physical address associated with mobile number "(123) 456-7890).
  • the physical address associated with the identification number may be received by an integrated mobile application system.
  • an address confirmation may be transmitted in a similar manner as described above for block 310.
  • an address confirmation may be received in a similar manner as described above for block 311.
  • a determination may be made as to whether the physical address has been confirmed in a similar manner as described above for block 312.
  • flow chart 400 may proceed to block 413. Upon a determination that a physical address has been confirmed, flow chart 400 may proceed to block 423. [0116] In block 423, a user account may be updated in a similar manner as described above for block 313.
  • a physical address may be transmitted to a fulfillment system in a similar manner as described above for block 314.
  • flow chart 400 may proceed to block 425.
  • an address confirmation may be transmitted in a similar manner as described above for block 310.
  • an address confirmation may be received in a similar manner as described above for block 311.
  • a determination may be made as to whether the physical address has been confirmed in a similar manner as described above for block 312.
  • flow chart 400 may proceed to block 406. Upon a determination that a physical address has been confirmed, flow chart 400 may proceed to block 428.
  • a physical address may be transmitted to a fulfillment system in a similar manner as described above for block 314.
  • flow chart 400 may proceed to block 429.
  • a user may be identified in a similar manner as described above for block 303.
  • a determination may be made as to whether the user has an associated user account associated in a similar manner as described above for block 304. Upon a determination that the user has an associated user account, flow chart 400 may proceed to block 431. Upon making a determination that a user does not have an associated user account, flow chart 400 may proceed to block 433.
  • a user account may be created in a similar manner as described above for block 305.
  • a permission response may be received in a similar manner as described above for block 407.
  • a determination may be made as to whether permission to access carrier account information has been granted in a similar manner as described above for block 408. Upon a determination that permission is granted, flow chart 400 may proceed to block 437. Upon a determination that permission is not granted, flow chart 400 may proceed to block 442.
  • a land line number may be requested in a similar manner as described above for block 306.
  • a land line number may be received in a similar manner as described above for block 307.
  • a physical address associated with the received land line number may be obtained in a similar manner as described above for block 308.
  • a determination may be made as to whether a physical address was obtained in a similar manner as described above for block 309. Upon making a determination that a physical address was obtained, flow chart 400 may proceed to block 439. Upon making a determination that a physical address was not obtained, flow chart 400 may proceed to block 446.
  • a zip code may be requested in a similar manner as described above for block 319.
  • a zip code may be received in a similar manner as described above for block 320.
  • a city and state associated with the zip code may be determined in a similar manner as described above for block 321.
  • a street address associated with the city and state may be requested in a similar manner as described above for block 322.
  • a street address may be received in a similar manner as described above for block 323.
  • carrier account information may be requested in a similar manner as described above for block 418.
  • the carrier account information may be received in a similar manner as described above for block 419.
  • an address confirmation may be transmitted in a similar manner as described above for block 310.
  • an address confirmation may be received in a similar manner as described above for block 311.
  • a determination may be made as to whether the physical address has been confirmed in a similar manner as described above for block 312.
  • flow chart 400 may proceed to block 446. Upon a determination that a physical address has been confirmed, flow chart 400 may proceed to block 455.
  • payment information may be requested in a similar manner as described above for block 341.
  • payment information may be received in a similar manner as described above for block 342.
  • a PIN may be determined in a similar manner as described above for block 343.
  • an account may be updated in a similar manner as described above for block 313.
  • a transaction may be processed in a similar manner as described above for block 345.
  • a determination may be made as to whether an address is associated with the account in a similar manner as described above for block 339. Upon a determination that a user account is not associated with an address, flow chart 400 may proceed to block 433. Upon a determination that an address is associated with the user account, flow chart 400 may proceed to block 432.
  • a determination may be made as to whether payment information is associated with the user account in a similar manner as described above for block 340. Upon a determination that payment information is not associated with the user account, flow chart 400 may proceed to block 455. Upon a determination that payment information is associated with the user account, flow chart 400 may proceed to block 451. In block 451 , a PIN confirmation may be transmitted in a similar manner as described above for block 346.
  • a PIN response may be received in a similar manner as described above for block 347.
  • a determination may be made as to whether the PIN is confirmed in a similar manner as described above for block 348. Upon a determination that the PIN has been confirmed, flow chart 400 may proceed to block 459. Upon a determination that the PIN has not been confirmed, flow chart 400 may proceed to block 454 to cancel the transaction or re-request the PIN. If the PIN is re-requested, flow chart 400 may proceed to block 452 to receive a PIN confirmation.
  • FIG. 5 depicts a flow chart 500 which illustrates an exemplary method for registering consumer shipping addresses via a mobile device, for example.
  • a user may have a user account and associated account information.
  • a user may wish to purchase a consumer product using methods described above, and may intend that the recipient of the consumer product be a gift recipient and/or that the consumer product be shipped to an address other than the address associated with the user's account.
  • a user may wish to purchase a Blue Bic® ballpoint pen to be given to the user's mother.
  • the user may wish to purchase the Blue Bic® ballpoint pen to be shipped to the user's office address instead of the home address associated with the user account.
  • a request may be received in a similar manner as described above for block 301.
  • the user may be identified in a similar manner as described above for block 302.
  • a determination may be made as to whether a user account is associated with an identification number in a similar manner as described above for block 304. Upon a determination that a user account is associated with an identification number, flow chart 500 may proceed to block 504. Upon a determination that a user account is not associated with an identification number, in block 523, the user may be registered in a similar manner as described above. [0155] In block 504, a PIN confirmation may be transmitted in a similar manner as described above for block 346.
  • a PIN response may be received in a similar manner as described above for block 347.
  • a determination may be made as to whether the PIN is confirmed in a similar manner as described above for block 348. Upon a determination that the PIN has been confirmed, flow chart 500 may proceed to block 508. Upon a determination that the PIN has not been confirmed, flow chart 500 may proceed to block 507 to cancel the transaction or re-request the PIN. If the PIN is re-requested, flow chart 500 may proceed to block 505 to receive a PIN confirmation.
  • an integrated mobile application server may communicate with a requesting device and/or a device associated with the identification number to prompt the user regarding where to ship the consumer product. For example, to prompt the user, an integrated mobile application server may communicate with the requesting device to prompt the user to transmit an affirmative indicator if the user desires to ship the consumer product to the address on file (and may also communicate the address to the user) to the integrated mobile application server.
  • the integrated mobile application server may transmit a message (e.g., a text message) to the requesting device and/or a device associated with the identification number prompting the user to reply with "1" if the user desired to ship the consumer product to the address on file or a "2" if the user desires to ship the consumer product elsewhere.
  • a message e.g., a text message
  • an integrated mobile application server may interact with an IVR system to communicate with the requesting device and/or a device associated with the identification number to prompt the user to input a response regarding where to ship the consumer product into the IVR.
  • a land line number may be requested in a similar manner as described above for block 306.
  • this land line number may be requested to prompt the user input a land line associated with a physical address where the user desires the consumer product to be shipped.
  • This address once determined, may be associated with the user account and, for example, an identifier of the address so that the user may ship future shipments to this address.
  • a user may desire to ship the consumer product to the user's mother, whose land line number is (222) 333-4444 and the associated address is 456 Other Street, Othertown, OtherState, 11111.
  • a land line number may be received in a similar manner as described above for block 307.
  • an integrated mobile application server may receive a land line number (222) 333-4444.
  • an address associated with the received land line number may be obtained in a similar manner as described for block 308. For example, using (222) 333-4444 as a key, a land line public database may be queried to return an address associated with the land line number.
  • a determination may be made as to whether a physical address was obtained in a similar manner as described above for block 309. Upon making a determination that a physical address was obtained, flow chart 500 may proceed to block 513. Upon making a determination that a physical address was not obtained, flow chart 500 may proceed to block 518.
  • a zip code associated with the address of the intended recipient may be requested in a similar manner as described above for block 319.
  • a zip code may be received in a similar manner as described above for block 320.
  • a city and state associated with the zip code of the address of the intended recipient may be determined in a similar manner as described above for block 321.
  • a street address associated with the city and state of the intended recipient may be requested in a similar manner as described above for block 322.
  • a street address may be received in a similar manner as described above for block 323.
  • flow chart 500 may proceed to block 513.
  • an address confirmation may be transmitted in a similar manner as described above for block
  • the address confirmation may seek confirmation of the address of the intended recipient.
  • an address confirmation may be received in a similar manner as described above for block 311.
  • a determination may be made as to whether the physical address of the intended recipient has been confirmed in a similar manner as described above for block 312. Upon a determination that a physical address has not been confirmed, flow chart 500 may proceed to block 516. Upon a determination that a physical address has been confirmed, flow chart 500 may proceed to block
  • a user account may be updated.
  • the physical address of the intended recipient e.g., the gift recipient or an alternative shipping address
  • a identifier may also be associated with the physical address of the intended recipient as will be described in greater detail below with respect to Figure 6.
  • a physical address of the intended recipient may be transmitted to a fulfillment system in a similar manner as described above for block
  • Figure 6 depicts an exemplary screen display 600 of user account information 601.
  • a user account may be identified by an account number 602.
  • the account number may be associated with a requesting device and/or an identification number associated with a requesting device.
  • an account may be identified by a mobile phone number of a user.
  • Account information 601 may also include a user's personal information 603, payment information 604, shipping information 605, gift recipient information 606, and/or alternative shipping location information 607.
  • Screen display 600 may also include additional account features 608 that may enable a user to access and/or edit account information, for example.
  • Personal information 603 may include a user's name and address.
  • personal information may include a name, street address, city, state, and zip code.
  • Payment information 604 may include a billing address of the user, associated payment account information (e.g., credit card account information, debit account information, demand deposit account information, prepaid account information, Internet-based account information and/or other like account information). Although only on account is illustrated, payment account information may be associated with a user account and, during the purchase of a consumer product, for example, a user may select a payment method in a similar manner as described above for identifying a gift recipient or alternative shipping location for the consumer product. For example, an integrated mobile application server prompt a user via a text message or IVR to provide input as to which payment method the user selects.
  • payment account information e.g., credit card account information, debit account information, demand deposit account information, prepaid account information, Internet-based account information and/or other like account information.
  • payment account information may be associated with a user account and, during the purchase of a consumer product, for example, a user may select a payment method in a similar manner as described above for identifying a gift recipient or alternative shipping location for the
  • Shipping information 605 may identify the physical address where consumer products are to be shipped.
  • Gift recipient information 606 may include the personal information
  • the gift recipient's address may be obtained using the gift recipients land line number and/or zip code as described above.
  • Alternative shipping information 607 may include the personal information 607a associated with an alternative shipping address of a user, for example, and an identifier associated with the alternative shipping address (e.g., "WORK").
  • the alternative shipping address information may be obtained using a land line number and/or zip code as described above.
  • Additional account features 608 may enable the user to view the user's order history, edit user account information, add a gift recipient, and/or alternative shipping location.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Finance (AREA)
  • Databases & Information Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne des systèmes et procédés pour recevoir une transmission qui est associée à un numéro d'identification et comprend un numéro associé à une ligne terrestre, déterminer une adresse physique en se basant sur le numéro associé à la ligne terrestre, confirmer l'adresse physique qui a été déterminée et associer l'adresse physique à un compte d'utilisateur, le compte d'utilisateur étant identifié par le numéro d'identification.
PCT/US2008/064675 2007-05-30 2008-05-23 Enregistrement de consommateur par l'intermédiaire d'un dispositif mobile WO2008150740A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/755,419 2007-05-30
US11/755,419 US20080299970A1 (en) 2007-05-30 2007-05-30 Consumer Registration Via Mobile Device

Publications (1)

Publication Number Publication Date
WO2008150740A1 true WO2008150740A1 (fr) 2008-12-11

Family

ID=40088895

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2008/064675 WO2008150740A1 (fr) 2007-05-30 2008-05-23 Enregistrement de consommateur par l'intermédiaire d'un dispositif mobile

Country Status (2)

Country Link
US (3) US20080299970A1 (fr)
WO (1) WO2008150740A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8060555B2 (en) 2005-08-17 2011-11-15 Canada Post Corporation Electronic content management systems and methods

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130026232A1 (en) * 2011-07-18 2013-01-31 Tiger T G Zhou Methods and systems for preventing card payment fraud and receiving payments using codes and mobile devices
US8769706B2 (en) * 2007-07-26 2014-07-01 International Business Machines Corporation System and method for user to verify a network resource address is trusted
US8275097B2 (en) * 2008-08-28 2012-09-25 Ebay Inc. Voice phone-based method and system to authenticate users
US9112883B2 (en) * 2009-11-12 2015-08-18 Cellco Partnership Method of registering a mobile station with a social networking site
US10032239B2 (en) * 2010-06-10 2018-07-24 United Parcel Service Of America, Inc. Enhanced payments for shipping
US9047630B2 (en) 2010-10-15 2015-06-02 Cellco Partnership Using a mobile device to make a transaction
US8755670B2 (en) 2012-04-06 2014-06-17 Realtek Semiconductor Corp. Multimedia system, relevant multimedia information display device and multimedia information transmission method
US20130268857A1 (en) * 2012-04-06 2013-10-10 Realtek Semiconductor Corp. Multimedia content providing device, multimedia content providing method, and relevant computer program product
US9077932B2 (en) 2012-04-06 2015-07-07 Realtek Semiconductor Corp. Multimedia system, relevant multimedia information display device and multimedia information transmission method
US9830772B2 (en) 2014-04-04 2017-11-28 Mobile Gaming Technologies, Inc. Dynamic deposits and promotions for gaming systems
US10445815B1 (en) * 2014-06-13 2019-10-15 Amazon Technolgies, Inc. Maintaining privacy of gifts on shared account
US9830770B2 (en) * 2014-12-02 2017-11-28 Mobile Gaming Technologies, Inc. Secure remote gaming player registration
US10388282B2 (en) * 2017-01-25 2019-08-20 CliniCloud Inc. Medical voice command device
US12147278B2 (en) 2022-06-30 2024-11-19 Mitel Networks Corporation Method for providing a display apparatus for computer networking and telephony cables

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050064849A1 (en) * 2000-02-09 2005-03-24 Coppinger Paul D. System and method for deploying application program components having a service sector
US20050105701A1 (en) * 2001-01-02 2005-05-19 Tucciarone Joel D. Electronic messaging system and method thereof
US20050233735A1 (en) * 2004-04-16 2005-10-20 Jeyhan Karaoguz Enhanced caller ID information based on access device information via a broadband access gateway
US20060206709A1 (en) * 2002-08-08 2006-09-14 Fujitsu Limited Authentication services using mobile device
US20060240824A1 (en) * 2005-04-25 2006-10-26 Irvin Henderson Method for quick registration from a mobile device
US20070105548A1 (en) * 2003-11-13 2007-05-10 Thomason Licensing S.A. Integrated cellular/pcs-pots communication system

Family Cites Families (90)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5850599A (en) 1992-09-25 1998-12-15 Ecs Enhanced Cellular Systems Manufacturing Inc. Portable cellular telephone with credit card debit system
AU6380496A (en) 1995-06-07 1996-12-30 E-Comm Incorporated Handheld remote computer control and methods for secured int eractive real-time telecommunications
US5794210A (en) 1995-12-11 1998-08-11 Cybergold, Inc. Attention brokerage
US6314406B1 (en) 1996-06-26 2001-11-06 Telxon Corporation Customer information network
US5937391A (en) 1996-07-11 1999-08-10 Fujitsu Limited Point-service system in online shopping mall
US20040243478A1 (en) 1996-09-04 2004-12-02 Walker Jay S. Purchasing, redemption, and settlement systems and methods wherein a buyer takes possession at a retailer of a product purchased using a communication network
US6490567B1 (en) * 1997-01-15 2002-12-03 At&T Corp. System and method for distributed content electronic commerce
US6148331A (en) * 1997-04-25 2000-11-14 Parry; Rhys Evan Destination website access and information gathering system
US6799165B1 (en) 1998-07-28 2004-09-28 Eimar M. Boesjes Apparatus and methods for inventory, sale, and delivery of digitally transferable goods
DE59915075D1 (de) 1998-09-10 2009-10-22 Swisscom Ag Verfahren zum Kaufen von Waren oder Dienstleistungen mit einem Mobiltelefon
US6134548A (en) * 1998-11-19 2000-10-17 Ac Properties B.V. System, method and article of manufacture for advanced mobile bargain shopping
US6577861B2 (en) * 1998-12-14 2003-06-10 Fujitsu Limited Electronic shopping system utilizing a program downloadable wireless telephone
US6512919B2 (en) * 1998-12-14 2003-01-28 Fujitsu Limited Electronic shopping system utilizing a program downloadable wireless videophone
FR2790162B1 (fr) * 1999-02-19 2001-04-13 France Telecom Procede de telepaiement et systeme pour la mise en oeuvre de ce procede
AUPP996099A0 (en) * 1999-04-23 1999-05-20 Silverbrook Research Pty Ltd A method and apparatus(sprint01)
US6889325B1 (en) * 1999-04-28 2005-05-03 Unicate Bv Transaction method and system for data networks, like internet
US6345261B1 (en) * 1999-09-21 2002-02-05 Stockback Holdings, Inc. Customer loyalty investment program
US6609104B1 (en) 1999-05-26 2003-08-19 Incentech, Inc. Method and system for accumulating marginal discounts and applying an associated incentive
US20050075932A1 (en) * 1999-07-07 2005-04-07 Mankoff Jeffrey W. Delivery, organization, and redemption of virtual offers from the internet, interactive-tv, wireless devices and other electronic means
US20050071230A1 (en) 1999-07-07 2005-03-31 Mankoff Jeffrey W. Delivery, organization, and redemption of virtual offers from the internet, interactive-TV, wireless devices and other electronic means
US7103565B1 (en) 1999-08-27 2006-09-05 Techventure Associates, Inc. Initial product offering system
US6516056B1 (en) * 2000-01-07 2003-02-04 Vesta Corporation Fraud prevention system and method
US6912503B1 (en) * 2000-01-14 2005-06-28 Gilbarco Inc. Multistage data purchase with mobile information ordering and docking station receipt
ES2225471T3 (es) * 2000-01-28 2005-03-16 Fundamo (Proprietary) Limited Sistema bancario con identificacion de cuentas financieras mejorada.
US6970548B2 (en) * 2000-01-31 2005-11-29 Infonxx, Inc Communication assistance system and method
US6640098B1 (en) * 2000-02-14 2003-10-28 Action Engine Corporation System for obtaining service-related information for local interactive wireless devices
US20010037266A1 (en) * 2000-03-30 2001-11-01 Schroeder William D. UPC consumer product image server system for the internet
NZ519862A (en) 2000-04-07 2003-09-26 Cool 123 Ltd Marketing response recording using short message service text word comparisons
AU2001251634A1 (en) * 2000-04-17 2001-10-30 Emtera Corporation System and method for wireless purchases of goods and services
CA2337672A1 (fr) 2000-04-26 2001-10-26 International Business Machines Corporation Paiement de transactions commerciales en reseau, faisant appel a un telephone mobile
US20020002504A1 (en) * 2000-05-05 2002-01-03 Andrew Engel Mobile shopping assistant system and device
US20020016750A1 (en) * 2000-06-20 2002-02-07 Olivier Attia System and method for scan-based input, storage and retrieval of information over an interactive communication network
GB2364482B (en) * 2000-06-30 2002-10-09 Motorola Inc Server-based electronic wallet system
US20020104090A1 (en) 2000-08-10 2002-08-01 Stettner Armando Paul System and method for interactive advertising
US6663002B2 (en) 2000-08-15 2003-12-16 James B. Glaser Apparatus and method for facilitating credit transactions
US7392388B2 (en) * 2000-09-07 2008-06-24 Swivel Secure Limited Systems and methods for identity verification for secure transactions
ES2341845T3 (es) * 2000-09-13 2010-06-29 Stratosaudio, Inc. Sistema y procedimiento para solicitar y distribuir contenido mediatico utilizando datos complementarios transmitidos por señal de radio.
FI20002102A0 (fi) 2000-09-25 2000-09-25 Moom Solutions Ltd Oy Menetelmä tuotteen, palvelun, maksun ja/tai vastaavan lunastukseen/luovutukseen
US7774231B2 (en) * 2000-09-29 2010-08-10 Nokia Corporation Electronic payment methods for a mobile device
US20040143500A1 (en) 2000-10-06 2004-07-22 Lopez Kermit D. Processing negotiable economic credits through electronic hand held devices
US20020152179A1 (en) * 2000-10-27 2002-10-17 Achiezer Racov Remote payment method and system
US20020123359A1 (en) 2000-12-01 2002-09-05 Multiscience System Pte Limited Network for information transfer for mobile stations
US7613634B2 (en) * 2000-12-21 2009-11-03 Sony Corporation Method and system for performing electronic retailing
US7242922B2 (en) * 2000-12-29 2007-07-10 Vesta Corporation Toll free calling account recharge system and method
FI20010063L (fi) * 2001-01-11 2002-07-12 Suomen Posti Oy Menetelmä ja järjestelmä tuotteen tai palvelun tilaamiseksi
US20020111869A1 (en) * 2001-01-16 2002-08-15 Brian Shuster Method and apparatus for remote data collection of product information using a communications device
US6873968B2 (en) 2001-02-10 2005-03-29 International Business Machines Corporation System, method and computer program product for on-line real-time price comparison and adjustment within a detachable virtual shopping cart
FR2820853B1 (fr) * 2001-02-12 2003-04-11 France Telecom Procede et systeme de telepaiement
US7599855B2 (en) * 2001-02-13 2009-10-06 Lester Sussman System and method for a complete and convenient shopping experience
US6934529B2 (en) * 2001-02-20 2005-08-23 Sevket Ilhan Bagoren Replenishment of pre-paid wireless telephone accounts using short message service (SMS)
FR2821225B1 (fr) * 2001-02-20 2005-02-04 Mobileway Systeme de paiement electronique a distance
US20030009374A1 (en) * 2001-05-04 2003-01-09 Moodie Justin Charles Schemes employing mobile communications
DE10125052A1 (de) * 2001-05-14 2002-12-12 Siemens Ag Verfahren zum Abrechnen von in einem Rechnernetzwerk bereitgestellten Diensten
US20020194604A1 (en) 2001-06-19 2002-12-19 Sanchez Elizabeth C. Interactive television virtual shopping cart
US20030014327A1 (en) * 2001-06-29 2003-01-16 Kristofer Skantze System and method in electronic commerce from hand-held computer units
EP1428185A1 (fr) * 2001-09-06 2004-06-16 Nokia Corporation Procede et element de reseau permettant le paiement par un terminal mobile, par l'intermediaire d'un reseau de communication
US7840494B2 (en) * 2001-09-12 2010-11-23 Verizon Business Global Llc Systems and methods for monetary transactions between wired and wireless devices
US6681989B2 (en) * 2002-01-15 2004-01-27 International Business Machines Corporation Inventory control and point-of-sale system and method
US7127261B2 (en) * 2002-02-22 2006-10-24 Julian Van Erlach Enhanced telecommunication services
EP1514211A4 (fr) * 2002-05-21 2010-03-10 Tekelec Us Procedes et systemes de realisation d'une transaction de vente au moyen d'un dispositif mobile de communications
US7336973B2 (en) * 2002-10-30 2008-02-26 Way Systems, Inc Mobile communication device equipped with a magnetic stripe reader
US20040019564A1 (en) * 2002-07-26 2004-01-29 Scott Goldthwaite System and method for payment transaction authentication
US20040107170A1 (en) 2002-08-08 2004-06-03 Fujitsu Limited Apparatuses for purchasing of goods and services
US7571140B2 (en) * 2002-12-16 2009-08-04 First Data Corporation Payment management
US20040148226A1 (en) * 2003-01-28 2004-07-29 Shanahan Michael E. Method and apparatus for electronic product information and business transactions
US20040215526A1 (en) 2003-04-08 2004-10-28 Wenjun Luo Interactive shopping and selling via a wireless network
WO2004105405A2 (fr) * 2003-05-16 2004-12-02 M-Qube, Inc. Systeme et procede de translation et d'acheminement d'un code court de messagerie mobile
US20090015379A1 (en) 2004-05-19 2009-01-15 Einar Rosenberg Apparatus and method for context-based wireless information processing
US7110792B2 (en) 2003-05-19 2006-09-19 Einar Rosenberg Apparatus and method for increased security of wireless transactions
US20040249712A1 (en) * 2003-06-06 2004-12-09 Brown Sean D. System, method and computer program product for presenting, redeeming and managing incentives
US20050004840A1 (en) * 2003-06-23 2005-01-06 Wanninger Lester A. System and method for mobile telephone text message consumer promotions
US20050080683A1 (en) 2003-10-09 2005-04-14 International Business Machines Corporation Administering a virtual shopping list for a user
JP2005215808A (ja) 2004-01-28 2005-08-11 Nec Corp 価値情報管理システム及びその方法
US20050239448A1 (en) * 2004-04-12 2005-10-27 Bayne Anthony J System and method for the distribution of advertising and associated coupons via mobile media platforms
US20060015402A1 (en) * 2004-06-10 2006-01-19 Graves Phillip C Using multiple PINs for redemption through multiple distribution channels
US20060047568A1 (en) 2004-08-26 2006-03-02 Ian Eisenberg SMS messaging-based layered service and contact method, system and method of conducting business
US20060184625A1 (en) 2005-01-31 2006-08-17 Nordvik Markus A Short query-based system and method for content searching
US20060200385A1 (en) * 2005-03-01 2006-09-07 Bray William W Iii Electronic marketing system and method
US7472822B2 (en) * 2005-03-23 2009-01-06 E2Interactive, Inc. Delivery of value identifiers using short message service (SMS)
US20060258397A1 (en) 2005-05-10 2006-11-16 Kaplan Mark M Integrated mobile application server and communication gateway
EP1910957A4 (fr) * 2005-05-11 2010-06-02 Sennari Inc Systeme et procede s'appliquant a un programme de fidelisation de clients a la telephonie mobile
US20070056022A1 (en) * 2005-08-03 2007-03-08 Aladdin Knowledge Systems Ltd. Two-factor authentication employing a user's IP address
US8352376B2 (en) 2005-10-11 2013-01-08 Amazon Technologies, Inc. System and method for authorization of transactions
US20070123219A1 (en) * 2005-10-19 2007-05-31 Mobile 365, Inc. System and method for item identification and purchase
US20070218900A1 (en) * 2006-03-17 2007-09-20 Raj Vasant Abhyanker Map based neighborhood search and community contribution
US20070156517A1 (en) * 2005-12-29 2007-07-05 Mark Kaplan System and method for redemption of a coupon using a mobile cellular telephone
US20070255662A1 (en) * 2006-03-30 2007-11-01 Obopay Inc. Authenticating Wireless Person-to-Person Money Transfers
US20070265006A1 (en) * 2006-05-09 2007-11-15 James Edward Washok Interactive text messaging system for information distribution
US7653186B2 (en) * 2006-05-26 2010-01-26 Aeris Communications, Inc. System and method for event communication correlation
US8086254B2 (en) * 2007-05-18 2011-12-27 Tango Networks, Inc. System, method, and apparatus for using alternative numbers for routing voice calls and short messages in a communications network

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050064849A1 (en) * 2000-02-09 2005-03-24 Coppinger Paul D. System and method for deploying application program components having a service sector
US20050105701A1 (en) * 2001-01-02 2005-05-19 Tucciarone Joel D. Electronic messaging system and method thereof
US20060206709A1 (en) * 2002-08-08 2006-09-14 Fujitsu Limited Authentication services using mobile device
US20070105548A1 (en) * 2003-11-13 2007-05-10 Thomason Licensing S.A. Integrated cellular/pcs-pots communication system
US20050233735A1 (en) * 2004-04-16 2005-10-20 Jeyhan Karaoguz Enhanced caller ID information based on access device information via a broadband access gateway
US20060240824A1 (en) * 2005-04-25 2006-10-26 Irvin Henderson Method for quick registration from a mobile device

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8060555B2 (en) 2005-08-17 2011-11-15 Canada Post Corporation Electronic content management systems and methods
US8595292B2 (en) 2005-08-17 2013-11-26 Canada Post Corporation Electronic content management systems and methods

Also Published As

Publication number Publication date
US8948733B2 (en) 2015-02-03
US20130295893A1 (en) 2013-11-07
US20080299970A1 (en) 2008-12-04
US9749839B2 (en) 2017-08-29
US20150264555A1 (en) 2015-09-17

Similar Documents

Publication Publication Date Title
US9749839B2 (en) Consumer registration via mobile device
KR101352530B1 (ko) 인맥정보를 이용한 선물 발송 시스템 및 그 방법
US8068860B1 (en) Short message service (SMS) protocol gateway
US20110136516A1 (en) Text message paging and ordering system
US20110093949A1 (en) System and method for using symbol command language within a communications network via sms or internet communications protocols
US20130031001A1 (en) Method and System for the Location-Based Discovery and Validated Payment of a Service Provider
US9047630B2 (en) Using a mobile device to make a transaction
US8843161B2 (en) System and method to facilitate in-application purchases on mobile devices
CN101731000A (zh) 使服务供应商能够获得并使用用户信息的系统和方法
US20080103918A1 (en) Method and system for making a re-order of pre-designated items by establishing a session and by sending a single short message using short message service via a cellular communications network
US20140066110A1 (en) Valet Parking System and Method
US8380578B2 (en) Method and system for joint-use of electronic product using mobile communication network
US20180285963A1 (en) System and method for intelligent ordering between a user and multiple providers
CN113891260A (zh) 通信号码当前运营商的鉴别方法和鉴别设备
US8346601B2 (en) System and method for managing promotional savings using a communications platform
US20110117893A1 (en) Methods of Connecting A Phone User Telephonically By Text Keyword Using A Keyword Database
GB2376153A (en) Providing property details to a mobile.
CN101422026A (zh) 移动信息提供和交易系统
KR100818040B1 (ko) 이동통신단말기에서 지향된 모바일 서비스를 이용한 메시지전송 방법 및 그 시스템
EP2092762A2 (fr) Procédé et appareil pour messagerie de réponse
US20080052108A1 (en) System and Method for Activating a Communication Device at a Point of Sale
KR101018020B1 (ko) 모바일 메시지 전송 중계 시스템 및 방법
JP2008107932A (ja) 情報提供方法及びそのシステム
KR20220006329A (ko) 휴대폰 온라인 유통망을 구현하는 휴대폰 배송 시스템
KR20040048142A (ko) 네트워크 기반의 아파트를 중심으로 하는 배송 운영시스템및 그 방법

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: 08756183

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

122 Ep: pct application non-entry in european phase

Ref document number: 08756183

Country of ref document: EP

Kind code of ref document: A1