Classifications

• • 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
  • G06Q30/00—Commerce
  • G06Q30/06—Buying, selling or leasing transactions
  • G06Q30/0601—Electronic shopping [e-shopping]
  • G06Q30/0631—Recommending goods or services
• • 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/08—Payment architectures
  • G06Q20/12—Payment architectures specially adapted for electronic shopping systems
• • 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/306—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using TV related infrastructures
• • 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
• • 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/321—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wearable 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/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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
  • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
  • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
  • G06Q20/3224—Transactions dependent on location of 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/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/326—Payment applications installed on the mobile 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/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/327—Short range or proximity payments by means of M-devices
  • G06Q20/3276—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being read by the M-device
• • 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/386—Payment protocols; Details thereof using messaging services or messaging apps
• • 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
  • G06Q30/00—Commerce
  • G06Q30/02—Marketing; Price estimation or determination; Fundraising
• • 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
  • G06Q30/00—Commerce
  • G06Q30/02—Marketing; Price estimation or determination; Fundraising
  • G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
• • 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
  • G06Q30/00—Commerce
  • G06Q30/02—Marketing; Price estimation or determination; Fundraising
  • G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
  • G06Q30/0238—Discounts or incentives, e.g. coupons or rebates at point-of-sale [POS]
• • 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
  • G06Q30/00—Commerce
  • G06Q30/02—Marketing; Price estimation or determination; Fundraising
  • G06Q30/0241—Advertisements
  • G06Q30/0251—Targeted advertisements
  • G06Q30/0267—Wireless 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
  • G06Q30/00—Commerce
  • G06Q30/02—Marketing; Price estimation or determination; Fundraising
  • G06Q30/0241—Advertisements
  • G06Q30/0251—Targeted advertisements
  • G06Q30/0269—Targeted advertisements based on user profile or attribute
  • G06Q30/0271—Personalized advertisement
• • 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
  • G06Q30/00—Commerce
  • G06Q30/02—Marketing; Price estimation or determination; Fundraising
  • G06Q30/0281—Customer communication at a business location, e.g. providing product or service information, consulting
• • 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
  • G06Q30/00—Commerce
  • G06Q30/06—Buying, selling or leasing transactions
• • 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
  • G06Q30/00—Commerce
  • G06Q30/06—Buying, selling or leasing transactions
  • G06Q30/0601—Electronic shopping [e-shopping]
  • G06Q30/0639—Locating goods or services, e.g. based on physical position of the goods or services within a shopping facility
• • 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
  • G06Q30/00—Commerce
  • G06Q30/06—Buying, selling or leasing transactions
  • G06Q30/0601—Electronic shopping [e-shopping]
  • G06Q30/0641—Electronic shopping [e-shopping] utilising user interfaces specially adapted for shopping
• • 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
  • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
  • G06Q50/10—Services

Definitions

• the present innovations generally address apparatuses, methods, and systems for retail commerce, and more particularly, include TRANSACTION VISUAL CAPTURING APPARATUSES, METHODS AND SYSTEMS ("TVC").
• Consumer transactions typically require a customer to select a product from a store shelf or website, and then to check it out at a checkout counter or webpage.
• Product information is typically selected from a webpage catalog or entered into a point- of-sale terminal device, or the information is automatically entered by scanning an item barcode with an integrated barcode scanner, and the customer is usually provided with a number of payment options, such as cash, check, credit card or debit card.
• the point-of-sale terminal memorializes the transaction in the merchant's computer system, and a receipt is generated indicating the satisfactory consummation of the transaction.
• FIGURE 1 shows a block diagram illustrating example aspects of augmented retail shopping in some embodiments of the TVC
• FIGURES 2A-2D provide exemplary datagraphs illustrating data flows between the TVC server and its affiliated entities within embodiments of the TVC
• FIGURES 3A-3C provide exemplary logic flow diagrams illustrating TVC augmented shopping within embodiments of the TVC
• FIGURES 4A-4M provide exemplary user interface diagrams illustrating TVC augmented shopping within embodiments of the TVC
• FIGURE S 5A-5F provide exemplary UI diagrams illustrating TVC virtual shopping within embodiments of the TVC
• FIGURE 6 provides a diagram illustrating an example scenario of TVC users splitting a bill via different payment cards via visual capturing the bill and the physical cards within embodiments of the TVC
• FIGURE 7A-7C provides a diagram illustrating example virtual layers injections upon virtual capturing within embodiments of the TVC
• FIGURES 15A-15F provide exemplary user interface diagrams illustrating a user sharing bill scenario within embodiments of the TVC;
• FIGURES 16A-16C provide exemplary user interface diagrams illustrating different layers of information label overlays within alternative embodiments of the TVC;
• FIGURE 17 provides exemplary user interface diagrams illustrating in- store scanning scenarios within embodiments of the TVC;
• FIGURES 18-19 provide exemplary user interface diagrams illustrating post-purchase restricted-use account reimbursement scenarios within embodiments of the TVC;
• FIGURES 20A-20D provides a logic flow diagram illustrating TVC overlay label generation within embodiments of the TVC;
• FIGURE 21 shows a schematic block diagram illustrating some embodiments of the TVC;
• FIGURES 22a-b show data flow diagrams illustrating processing gesture and vocal commands in some embodiments of the TVC;
• FIGURES 23a-3c show logic flow diagrams illustrating processing gesture and vocal commands in some embodiments of the TVC;
• FIGURE 24a shows a data flow diagrams illustrating checking into a store in some embodiments of the TVC
• FIGURES 24b-c show data flow diagrams illustrating accessing a virtual store in some embodiments of the TVC
• FIGURE 25a shows a logic flow diagram illustrating checking into a store in some embodiments of the TVC
• FIGURE 25b shows a logic flow diagram illustrating accessing a virtual store in some embodiments of the TVC;
• FIGURES 26a-d show schematic diagrams illustrating initiating transactions in some embodiments of the TVC;
• FIGURE 27 shows a schematic diagram illustrating multiple parties initiating transactions in some embodiments of the TVC;
• FIGURE 28 shows a schematic diagram illustrating a virtual closet in some embodiments of the TVC;
• FIGURE 29 shows a schematic diagram illustrating an augmented reality interface for receipts in some embodiments of the TVC;
• FIGURE 30 shows a schematic diagram illustrating an augmented reality interface for products in some embodiments of the TVC;
• FIGURE 31 shows a user interface diagram illustrating an overview of example features of virtual wallet applications in some embodiments of the TVC;
• FIGURES 32A-G show user interface diagrams illustrating example features of virtual wallet applications in a shopping mode, in some embodiments of the TVC;
• FIGURES 33A-F show user interface diagrams illustrating example features of virtual wallet applications in a payment mode, in some embodiments of the TVC;
• FIGURE 34 shows a user interface diagram illustrating example features of virtual wallet applications, in a history mode, in some embodiments of the TVC;
• FIGURES 35A-E show user interface diagrams illustrating example features of virtual wallet applications in a snap mode, in some embodiments of the TVC; [ 0043 ] FIGURE 36 shows a user interface diagram illustrating example features of virtual wallet applications, in an offers mode, in some embodiments of the TVC; [ 0044] FIGURES 37A-B show user interface diagrams illustrating example features of virtual wallet applications, in a security and privacy mode, in some embodiments of the TVC; [ 0045 ] FIGURE 38 shows a data flow diagram illustrating an example user purchase checkout procedure in some embodiments of the TVC; [ 0046 ] FIGURE 39 shows a logic flow diagram illustrating example aspects of a user purchase checkout in some embodiments of the TVC, e.g., a User Purchase Checkout ("UPC") component 3900; [ 0047] FIGURES 40A-B show data flow diagrams illustrating an example purchase transaction authorization procedure in some embodiments of the TVC; [ 0048 ] FIGURES 41A-B
• UPC User
• FIGURE 44 shows a block diagram illustrating embodiments of a TVC controller; and [ 0052 ]
• the leading number of each reference number within the drawings indicates the figure in which that reference number is introduced and/or detailed. As such, a detailed discussion of reference number 101 would be found and/or introduced in Figure 1.
• Reference number 201 is introduced in Figure 2, etc. DETAILED DESCRIPTION
• TVC TRANSACTION VISUAL CAPTURING
• the TRANSACTION VISUAL CAPTURING APPARATUSES, METHODS AND SYSTEMS transform mobile device location coordinate information transmissions, real-time reality visual capturing, and mixed gesture capturing, via TVC components, into real-time behavior-sensitive product purchase related information, shopping purchase transaction notifications, and electronic receipts.
• the TVC may provide a merchant shopping assistance platform to facilitate consumers to engage their virtual mobile wallet to obtain shopping assistance at a merchant store, e.g., via a merchant mobile device user interface (UI).
• UI merchant mobile device user interface
• a consumer may operate a mobile device (e.g., an Apple® iPhone, iPad, Google® Android, Microsoft® Surface, and/or the like) to "check-in" at a merchant store, e.g., by snapping a quick response (QR) code at a point of sale (PoS) terminal of the merchant store, by submitting GPS location information via the mobile device, etc.
• the merchant may provide a mobile user interface (UI) to the consumer to assist the consumer's shopping experience, e.g., shopping item catalogue browsing, consumer offer recommendations, checkout assistance, and/or the like.
• UI mobile user interface
• TVC may utilize the TVC mechanisms to create new TVC shopping experiences for their customers.
• TVC may integrate with alert mechanisms (e.g., V.me wallet push systems, vNotify, etc.) for fraud preventions, and/or the like.
• alert mechanisms e.g., V.me wallet push systems, vNotify, etc.
• TVC may provide/integrate with merchant-specific loyalty programs (e.g., levels, points, notes, etc.), facilitate merchants to provide personal shopping assistance to VIP customers.
• merchants via the TVC merchant UI platform, merchants may integrate and/or synchronize a consumer's wish list, shopping cart, referrals, loyalty, merchandise delivery options, and other shopping preference settings between online and in-store purchase.
• TVC may employ a virtual wallet alert mechanisms (e.g., vNotify) to allow merchants to communicate with their customers without sharing customer's personal information (e.g., e-mail, mobile phone number, residential addresses, etc.).
• a virtual wallet applications e.g., Visa® V.me wallet
• the consumer may engage a virtual wallet applications (e.g., Visa® V.me wallet) to complete purchases at the merchant PoS without revealing the consumer's payment information (e.g., a PAN number) to the merchant.
• Integration of an electronic wallet, a desktop application, a plug-in to existing applications, a standalone mobile application, a web based application, a smart prepaid card, and/or the like in capturing payment transaction related objects such as purchase labels, payment cards, barcodes, receipts, and/or the like reduces the number of network transactions and messages that fulfill a transaction payment initiation and procurement of payment information (e.g., a user and/or a merchant does not need to generate paper bills or obtain and send digital images of paper bills, hand in a physical payment card to a cashier, etc., to initiate a payment transaction, fund transfer, and/or the like).
• a transaction payment initiation and procurement of payment information e.g., a user and/or a merchant does not need to generate paper bills or obtain and send digital images of paper bills, hand in a physical payment card to a cashier, etc., to initiate a payment transaction, fund transfer, and/or the like.
• the number of transactions that may be processed per day is increased, i.e
• a mobile wallet platform e.g., see FIGURES 31-43B
• a digital/electronic wallet e.g., a digital/electronic wallet
• a smart/prepaid card linked to a user's various payment accounts e.g., a user's various payment accounts
• other payment platforms e.g., subset and superset features and data sets of each or a combination of the aforementioned shopping platforms (e.g., see FIGURES 2A-2D and 4A-4M) may be accessed, modified, provided, stored, etc. via cloud/server services and a number of varying client devices throughout the instant specification.
• mobile wallet user interface elements are depicted, alternative and/or complementary user interfaces are also contemplated including: desktop applications, plug-ins to existing applications, stand alone mobile applications, web based applications (e.g., applications with web objects/frames, HTML 5 applications/wrappers, web pages, etc.), and other interfaces are contemplated.
• desktop applications plug-ins to existing applications
• stand alone mobile applications web based applications (e.g., applications with web objects/frames, HTML 5 applications/wrappers, web pages, etc.), and other interfaces are contemplated.
• web based applications e.g., applications with web objects/frames, HTML 5 applications/wrappers, web pages, etc.
• the TVC payment processing component may be integrated with an digital/electronic wallet (e.g., a Visa V-Wallet, etc.), comprise a separate stand alone component instantiated on a user device, comprise a server/cloud accessed component, be loaded on a smart/prepaid card that can be substantiated at a PoS terminal, an ATM, a kiosk, etc., which may be accessed through a physical card proxy, and/or the like.
• an digital/electronic wallet e.g., a Visa V-Wallet, etc.
• a server/cloud accessed component e.g., a server/cloud accessed component
• FIGURE 1 shows a block diagram illustrating example aspects of augmented retail shopping in some embodiments of the TVC.
• a user 101a may enter 111 into a store (e.g., a physical brick-and-mortar store, virtual online store [via a computing device], etc.) to engage in a shopping experience, 110.
• the user may have a user device 102.
• the user device 102 may have executing thereon a virtual wallet mobile app, including features such as those as described below with in the discussion with reference to FIGURES 31-43B.
• the user device 102 may communicate with a store management server 103.
• the user device may communicate geographical location coordinates, user login information and/or like check-in information to check in automatically into the store, 120.
• the TVC may inject the user into a virtual wallet store upon check in.
• the virtual wallet app executing on the user device may provide features as described below to augment the user's in-store shopping experience.
• the store management server 103 may inform a customer service representative 101b ("CSR") of the user's arrival into the store.
• the CSR may include a merchant store employee operating a CSR device 104, which may comprise a smart mobile device (e.g., an Apple® iPhone, iPad, Google® Android, Microsoft® Surface, and/or the like).
• the CSR may interact with the consumer in- person with the CSR device 104, or alternatively communicate with the consumer via video chat on the CSR device 104.
• the CSR may comprise an shopping assistant avatar instantiated on the CSR device, with which the consumer may interact with, or the consumer may access the CSR shopping avatar within the consumer mobile wallet by checking in the wallet with the merchant store.
• the CSR app may include features such as described below in the discussion with reference to FIGURES 4A-4M.
• the CSR app may inform the CSR of the user's entry, including providing information about the user's profile, such as the user's identity, user's prior and recent purchases, the user's spending patterns at the current and/or other merchants, and/or the like, 130.
• the store management server may have access to the user's prior purchasing behavior, the user's real-time in-store behavior (e.g., which items' barcode did the user scan using the user device, how many times did the user scan the barcodes, did the user engage in comparison shopping by scanning barcodes of similar types of items, and/or the like), the user's spending patterns (e.g., resolved across time, merchants, stores, geographical locations, etc.), and/or like user profile information.
• the store management system may utilize this information to provide offers/coupons, recommendations and/or the like to the CSR and/or the user, via the CSR device and/or user device, respectively, 140.
• the CSR may assist the user in the shopping experience, 150.
• the CSR may convey offers, coupons, recommendations, price comparisons, and/or the like, and may perform actions on behalf of the user, such as adding/removing items to the user's physical/ virtual cart 151, applying/removing coupons to the user's purchases, searching for offers, recommendations, providing store maps, or store 3D immersion views (see, e.g., FIGURE 5C), and/or the like.
• the TVC may provide a checkout notification to the user's device and/or CSR device.
• the user may checkout using the user's virtual wallet app executing on the user device, or may utilize a communication mechanism (e.g., near field communication, card swipe, QR code scan, etc.) to provide payment information to the CSR device.
• a communication mechanism e.g., near field communication, card swipe, QR code scan, etc.
• the TVC may initiate the purchase transaction(s) for the user, and provide an electronic receipt 162 to the user device and/or CSR device, 160.
• the electronic receipt the user may exit the store 161 with proof of purchase payment.
• Some embodiments of the TVC may feature a more streamlined login option for the consumer.
• the consumer may initially enter a device ID such as an Apple ID to get into the device.
• the device ID may be the ID used to gain access to the TVC application.
• the TVC may use the device ID to identify the consumer and the consumer need not enter another set of credentials.
• the TVC application may identify the consumer using the device ID via federation. Again, the consumer may not need to enter his credentials to launch the TVC application.
• the consumer may also use their wallet credentials (e.g., V.me credentials) to access the TVC application. In such situations, the wallet credentials may be synchronized with the device credentials.
• the consumer may see some graphics that provide the consumer various options such as checking in and for carrying items in the store.
• a consumer may check in with a merchant. Once checked in, the consumer may be provided with the merchant information (e.g., merchant name, address, etc.), as well as options within the shopping process (e.g., services, need help, ready to pay, store map, and/or the like).
• the consumer may capture the payment code (e.g., QR code).
• the TVC application may generate and display a safe locker (e.g., see 455 in FIGURE 4I).
• the consumer may move his fingers around the dial of the safe locker to enter the payment PIN to execute the purchase transaction. Because the consumer credentials are managed in such a way that the device and/or the consumer are pre-authenticated or identified, the payment PIN is requested only when needed to conduct a payment transaction, making the consumer experience simpler and more secure.
• the consumer credentials may be transmitted to the merchant and/or TVC as a clear or hashed package.
• the TVC application may display a transaction approval or denial message to the consumer. If the transaction is approved, a corresponding transaction receipt may be generated (e.g., see FIGURE 4K).
• the receipt on the consumer device may include information such as items total, item description, merchant information, tax, discounts, promotions or coupons, total, price, and/or the like.
• the receipt may also include social media integration link via which the consumer may post or tweet their purchase (e.g., the entire purchase or selected items).
• Example social media integrated with the TVC application may include FACEBOOK, TWITTER, Google +, Four Squares, and/or the like. Details of the social media integration are discussed in detail in U.S. patent application serial no. 13/327,740 filed on December 15, 2011 and titled "Social Media Payment Platform Apparatuses, Methods and Systems" which is herein expressly incorporated by reference.
• a QR code generated from the list of items purchased may be included.
• the purchased items QR code may be used by the sales associates in the store to verify that the items being carried out of the store have actually been purchased.
• the TVC application may include a dynamic key lock configuration.
• the TVC application may include a dynamic keyboard that displays numbers or other characters in different configuration every time.
• Such a dynamic keypad would generate a different key entry pattern every time such that the consumer would need to enter their PIN every time.
• Such dynamic keypad may be used, for example, for entry of device ID, wallet PIN, and/or the like, and may provide an extra layer of security.
• the dial and scrambled keypad may be provided based on user preference and settings.
• the more cumbersome and intricate authentication mechanisms can be supplied based on increased seasoning and security requirements discussed in greater detail in U.S. patent application serial no.
• the TVC may also facilitate an outsourced customer service model wherein the customer service provider (e.g., sales associate) is remote, and the consumer may request help from the remote customer service provider by opening a communication channel from their mobile device application.
• the remote 1 customer service provider may then guide the requesting user through the store and/or
• FIGURES 2A-2B provide exemplary data flow diagrams illustrating data
• various TVC entities including
• a user 202 may operate a mobile device
• 11 check-in mechanisms may be employed.
• 12 device 203 may automatically handshake with a contactless plate installed at the
• 16 wallet information For example, an example listing of a consumer check-in message
• a merchant 220 may optionally provide a store check-in information 206 so that the consumer may snap a picture of the provided store check-in information.
• the store check-in information 206 may include barcodes (e.g., UPC, 2D, QR code, etc.), a trademark logo, a street address plaque, and/or the like, displayed at the merchant store 220.
• the consumer mobile device may then generate a check-in request 208 including the snapped picture of store check-in information 206 to the TVC server 210.
• the store check-in information 206 may include a store floor plan transmitted to the consumer via MMS, wallet push messages, email, and/or the like.
• the store information 206 to the TVCconsumer substantially in the form of XML-formatted data, is provided below:
• the consumer mobile device 203 may generate a (Secure) Hypertext Transfer Protocol ("HTTP(S)”) POST message including the consumer check-in information for the TVC server 210 in the form of data formatted according to the XML.
• HTTP(S) Secure Hypertext Transfer Protocol
• the above exemplary check-in request message includes a snapped image
• the mobile device 203 extract merchant information 209.
• the mobile device 203 extracts merchant information 209.
• the mobile device 203 extracts merchant information 209.
• the check-in message 208 may further include
• check-in message 208
• biometrics e.g., voice
• mobile device identity e.g., IMEI, ESN, SIMid, etc.
• mobile device identity e.g., IMEI, ESN, SIMid, etc.
• trusted execution environment e.g., Intel
• TVC server 210 may query for
• 26 consumer profile query 218 may be performed at the TVC server 210, and/or at the
• the TVC database 219 may be a relational database responsive to
• the TVC server may execute a
• PHP hypertext preprocessor
• $query "SELECT offer_ID, offer_title, offer_attributes_list, offer_price,
• $result mysql_query ( $query) ; // perform the search query
• the TVC may obtain the query result including the consumer loyalty offers profile (e.g., loyalty points with the merchant, with related merchants, product items the consumer previously purchased, product items the consumer previously scanned, locations of such items, etc.) 220, and may optionally provide the consumer profile information 223 to the merchant.
• the consumer loyalty offers profile e.g., loyalty points with the merchant, with related merchants, product items the consumer previously purchased, product items the consumer previously scanned, locations of such items, etc.
• the queried consumer loyalty profile 220 and/or the profile information provided to the merchant CSR 223, substantially in the form of XML- formatted data is provided below:
• TVC may optionally provide information on the consumer's previously viewed or purchased items to the merchant.
• the consumer has previously scanned the QR code of a product "Michael Kors Flat Pants" and such information including the inventory availability, SKU location, etc. may be provided to the merchant CSR, so that the merchant CSR may provide a recommendation to the consumer.
• the consumer loyalty message 223 may not include sensitive information such as consumer's wallet account information, contact information, purchasing history, and/or the like, so that the consumer's private financial information is not exposed to the merchant.
• the merchant 220 may query its local database for consumer loyalty profile associated with the merchant, and retrieve consumer loyalty profile information similar to message 223.
• the merchant may determine a CSR for the consumer 212. For example, the merchant may query a local consumer loyalty profile database to determine the consumer's status, e.g., whether the consumer is a returning customer, or a new customer, whether the consumer has been treated with a particular CSR, etc., to assign a CSR to the consumer.
• the CSR 230 may receive a consumer assignment 224 notification at a CSR terminal 240 (e.g., a PoS terminal, a mobile device, etc.).
• the consumer assignment notification message 224 may include consumer loyalty profile with the merchant, consumer's previous viewed or purchased item information, and/or the like (e.g., similar to that in message 223), and may be sent via email, SMS, instant messenger, PoS transmission, and/or the like.
• the consumer assignment notification 224 substantially in the form of XML-formatted data, is provided below:
• the consumer assignment notification 224 includes basic consumer information, and CSR profile information (e.g., CSR specialty, availability, language support skills, etc.). Additionally, the consumer assignment notification 224 may include consumer loyalty profile that may take a form similar to that in 223.
• the consumer may optionally submit in-store scanning information 225a to the CSR (e.g., the consumer may interact with the CSR so that the CSR may assist the scanning of an item, etc.), which may provide consumer interest indications to the CSR, and update the consumer's in-store location with the CSR.
• the consumer scanning item message 225a substantially in the form of XML-formatted data, is provided below:
• the consumer scanning information 225a may be provided to the TVC server to update consumer interests and location information.
• the CSR terminal 240 may retrieve a list of complementary items for recommendations 225b, e.g., items close to the consumer's in-store location, items related to the consumer's previous viewed items, etc.
• the CSR may submit a selection of the retrieved items to recommend to the consumer 226, wherein such selection may be based on the real-time communication between the consumer and the CSR, e.g., in-person communication, SMS, video chat, TVC push messages (e.g., see 4i6a-b in FIGURE 4D), and/or the like.
• CSR may interact with the consumer 202 to assist shopping.
• the CSR 230 may present recommended item/offer information 227 (e.g., see 434d-3 in FIGURE 4F) via the CSR terminal 240 to the consumer 202.
• the consumer item/offer recommendation message 227 substantially in the form of XML-formatted data, is provided below:
• 29 227 may be used to provide a store map, and directions to find the product item in the
• 31 consumer is performing in-store scanning (e.g., see FIGURE 5C).
• the consumer may provide an indication
• the CSR may in turn provide detailed information and/or add the item to
• the consumer may submit a payment interest indication 231b (e.g., by tapping on a "pay” button), and the CSR may present a purchasing page 233b (e.g., an item information checkout page with a QR code, see 442 in FIGURE 4H) to the consumer 202, who may indicate interests of a product item 231 with a CSR, e.g., by tapping on a mobile CSR terminal 240, by communicating with the CSR 230, etc.
• the consumer may snap the QR code of the interested product item and generate a purchase authorization request 236.
• the purchase authorization request 236 may take a form similar to 3811 in FIGURE 38.
• the consumer may continue to checkout with a virtual wallet instantiated on the mobile device 203, e.g., see 444b FIGURE 4I.
• a transaction authorization request 237a may be sent to the TVC server 210, which may in turn process the payment 238 with a payment processing network and issuer networks (e.g., see FIGURES 41A-42B).
• the consumer may send the transaction request 237b to the merchant, e.g., the consumer may proceed to checkout with the merchant CSR.
• the consumer may receive a push message of purchase receipt 245 (e.g., see 448 in FIGURE 4L) via the mobile wallet.
• the TVC server 210 may optionally send a transaction confirmation message 241 to the merchant 220, wherein the transaction confirmation message 241 may have a data structure similar to the purchase receipt 245.
• the merchant 220 may confirm the completion of the purchase 242.
• the TVC server 210 may provide the purchase completion receipt to a third party notification system 260, e.g., Apple® Push Notification Service, etc., which may in turn provide the transaction notification to the merchant, e.g., buy sending an instant message to the CSR terminal, etc.
• a third party notification system 260 e.g., Apple® Push Notification Service, etc.
• FIGURES 2C-2D provide exemplary infrastructure diagrams of the TVC system and its affiliated entities within embodiments of the TVC.
• the consumer 202 who operates an TVC mobile application 205a, may snap a picture of a store QR code 205b for consumer wallet check-in, as discussed at 204/208 in FIGURE 2A.
• the mobile component 205a may communicate with an TVC server 210 (e.g., being located with the Visa processing network) via wallet API calls 1 251a (e.g., PHP, JavaScript, etc.) to check-in with the TVC server.
• wallet API calls 1 251a e.g., PHP, JavaScript, etc.
• the TVC server 210 may retrieve consumer profile at an TVC database
• merchant store clerks 230a may be notified to
• the TVC server 210 may communicate with the merchant payment system 220a (e.g.,
• the TVC server 210 may keep private consumer information anonymous from the
• 9 merchant e.g., consumer payment account information, address, telephone number,
• the merchant payment system 10 email addresses, and/or the like.
• the merchant payment system 10 email addresses, and/or the like.
• 11 220a may retrieve product inventory information from the merchant inventory system
• the sales clerk may assist customer in shopping and adding items to iPad
• Purchase receipts may be pushed electronically to the consumer, e.g., via
• TVC may
• ICE Integrated collaboration environment
• the ICE system 270 may comprise a web server 270a, an
• the consumer check-in messages may
• REST representational state transfer protocols
• the ICE environment 270 may generate virtual avatars based on a
• FIGURES 3A-3C provide exemplary logic flow diagrams illustrating
• the consumer 1 302 may start the shopping experience by walking into a merchant store, and/or visit a
• the merchant 320 may provide a store check-in QR code
• a user interface 304 e.g., an in-store display, a mobile device operated by the store
• the consumer may snap the QR code and generate
• the consumer device 8 purchase profile (e.g., loyalty, etc.) 312.
• the consumer device 8 purchase profile (e.g., loyalty, etc.) 312.
• the consumer device 8 purchase profile (e.g., loyalty, etc.) 312.
• the consumer device 8 purchase profile (e.g., loyalty, etc.) 312.
• 9 may extract information from the captured QR code and incorporate such merchant
• the consumer may include
• the consumer device, and/or the TVC server may adopt QR code decoding tools such as,
• 17 merchant 320 may receive consumer check-in notification 313, e.g., from the TVC server
• the consumer may similarly check-in with the merchant by snapping a QR code
• consumer may log into a consumer account, e.g., a consumer account with the
• a consumer wallet account (e.g., V.me wallet payment account, etc.), to
• the merchant may receive consumer information
• the CSR allocation may be determined
• one CSR may handle multiple consumers simultaneously via a CSR platform (e.g., see FIGURE 4C); the higher loyalty level the consumer has with the merchant store, more attention the consumer may obtain from the CSR.
• a consumer with a level 10 with the merchant store may be assigned to one CSR exclusively, while a consumer with a level 2 with the store may share a CSR with other consumers having a relatively low loyalty level.
• the CSR allocation may be determined on the consumer check-in department labeled by product category (e.g., men's wear, women's wear, beauty and cosmetics, electronics, etc.), consumer past interactions with the merchant CSR (e.g., demanding shopper that needs significant amount of assistance, independent shopper, etc.), special needs (e.g., foreign language supports, child care, etc.), and/or the like.
• product category e.g., men's wear, women's wear, beauty and cosmetics, electronics, etc.
• consumer past interactions with the merchant CSR e.g., demanding shopper that needs significant amount of assistance, independent shopper, etc.
• special needs e.g., foreign language supports, child care, etc.
• the TVC may expand the query to look for a remote CSR 321 which may communicate with the consumer via SMS, video chat, TVC push messages, etc., and allocate the CSR to the consumer based 322.
• a pool of remote CSRs may be used to serve consumers and reduce overhead costs.
• online consumers may experience a store virtually by receiving a store floor plan for a designated location; and moving a consumer shopper avatar through the store floor plan to experience product offerings virtually, and the remote CSR may assist the virtual consumer, e.g., see FIGURES 5D-5F.
• the consumer 302 may receive a check-in confirmation 324 (e.g., see 407 in FIGURE 4B), and start interacting with a CSR by submitting shopping assistance request 326.
• the CSR may retrieve and recommend a list of complementary items to the consumer (e.g., items that are close to the consumer's location in-store, items that are related to consumer's previously viewed/purchased items, items that are related to the consumer's indicated shopping assistance request at 326, etc.).
• the CSR may determine a type of the shopping assistance request 329.
• the CSR may conclude the session 333.
• the request indicates a shopping request (e.g., consumer inquiry on shopping items, see 427a-c in FIGURE 4E, etc.)
• the CSR may retrieve shopping item information and add the item to a shopping cart 331, and provide such to the consumer 337 (e.g., see 434d-e in FIGURE 4F).
• the consumer may keep shopping or checkout with the shopping chart (e.g., see 444a-b in FIGURE 4I).
• the CSR may generate a transaction receipt including a QR code summarizing the transaction payment 334, and present it to the consumer via a CSR UI (e.g., see 442 in FIGURE 4H).
• the consumer may snap the QR code and submit a payment request 338 (e.g., see 443 in FIGURE 4I).
• TVC server may receive the payment request from the consumer and may request PIN verification 341.
• the TVC server may provide a PIN security challenge UI for the consumer to enter a PIN number 342, e.g., see 464 in FIGURE 4J; 465a in FIGURE 4K. If the entered PIN number is correct, the TVC server may proceed to process the transaction request, and generate a transaction record 345 (further implementations of payment transaction authorization are discussed in FIGURES 41A-42B). If the entered PIN number is incorrect, the consumer may obtain a transaction denial notice 346 (e.g., see 465b in FIGURE 4K).
• the merchant may receive a transaction receipt from the TVC 347, and present it to the consumer 348 (e.g., see 447 in FIGURE 4L).
• the consumer may view the receipt and select shipping method 351, for the merchant to process order delivery and complete the order 352.
• the consumer may receive a purchase receipt 355 via wallet push messages, and may optionally generate a social media posting 357 to publish the purchase, e.g., see 465 in FIGURE 4N.
• FIGURES 4A-4M provide exemplary UI diagrams illustrating embodiments of in-store augmented shopping experience within embodiments of the TVC.
• the merchant may provide a check-in page 1 including a QR code via a user interface.
• a merchant sales representative For example, a merchant sales representative
• a mobile device such as an Apple iPad, a PoS terminal computer, and/or
• the consumer may instantiate a mobile wallet on a
• the consumer may instantiate the shop 402c
• 12 application may provide merchant information obtained from the QR code 405, and the
• the wallet may submit a
• the consumer may receive a check-
• FIGURES 4C-4D provide exemplary merchant UIs for augmented
• a merchant CSR may log into a CSR account 403 to
• the CSR may view a UI at a mobile PoS (e.g., a iPad, etc.) 401.
• the CSR may view a
• the CSR may view the consumer's
• the CSR may send
• 29 may tap a "MSG" icon 413 with the profile photo of a customer 412a, and enter a
• the CSR may communicate with
• the CSR may receive dialogue responses from consumers 1 416b.
• a consumer may receive messages from a
• 3 merchant CSR e.g., greeting messages upon successful check-in at a merchant store
• the consumer may interact with the CSR by entering text messages 422
• the consumer wallet may allow a consumer
• 9 may tap a camera icon 423 to snap a picture of an in-store advertisement, a front
• the consumer may express interests in
• a consumer may video chat with a CSR to
• the CSR 432 may
• 16 comprise a merchant sales clerk, or a virtual shopping assistant avatar.
• TVC may confirm the consumer's identity to prevent fraud via the
• an TVC 18 video chat, as further discussed in FIGURE 37B.
• an TVC 18 video chat, as further discussed in FIGURE 37B.
• an TVC 18 video chat, as further discussed in FIGURE 37B.
• 19 shopping CSR may communicate with the consumer 433 to provide a list of options for
• the consumer's TVC shopping assistance For example, a consumer may elect to meet a
• TVC may provide a floor map of brands, products locations 434b to the consumer wallet
• TVC may start an augmented reality
• 25 may capture a visual reality scene inside of the merchant store and view virtual labels
• TVC may provide a list of popular products 434d
• the consumer may elect to pay for an item when
• a CSR may operate CSR mobile device to
• the CSR may search a product by the stock keeping unit (SKU) number
• CSR may maintain a list of consumer interested products 439.
• the CSR may tap on a
• TVC may provide a payment amount summary for the items in the shopping cart 439.
• the TVC may generate a QR
• the consumer may operate the consumer wallet to snap a picture of the QR code 442 to
• the consumer may obtain payment bill details obtained from the QR code 443.
• the consumer may elect to continue shopping 444a, and be
• 18 consumer may elect to pay for the transaction amount 444b.
• the TVC may request a user to enter a PIN number
• TVC may provide a dynamic keypad UI for the consumer to enter pass code 465a, e.g.,
• the consumer's pass code entry may not be captured by malicious spyware, instead of
• the CSR may generate a sales receipt 447, showing the purchase item and transaction amount paid.
• the CSR may send the sales receipt to the consumer wallet (e.g., via wallet push message system, etc.), and the consumer may elect to either pick up the purchased item in store 445a, or ship the purchased item to a previously stored address 445b.
• the consumer may receive a purchase receipt 448 via wallet push message service, and may elect to continue shopping 449 with the CSR, and/or checkout 451. If the consumer elects to checkout, the consumer may receive a checkout confirmation message 454.
• a consumer may view the receipt of past purchases at any time after the transaction, wherein the receipt may comprise payment amount information 462, and purchase item information 463. In one implementation, the consumer may connect to social media 464 to publish the purchase.
• FIGURES 5A-5C provide exemplary UI diagrams illustrating aspects of augmented reality shopping within embodiments of the TVC.
• a consumer may edit a shopping list 502 within the wallet.
• the consumer may type in desired shopping items into a notepad application 503, engage a voice memo application 505a, engage a camera 505b to scan in shopping items from a previous sales receipt 507 (e.g., a consumer may periodically purchase similar product items, such as grocery, etc.), and/or the like.
• the consumer may scan a previous sales receipt 507, and TVC may recognize sales items 508, and the consumer may add desired product items to the shopping list by tapping on an "add" button 509.
• the TVC may determine a product category and a product identifier for each product item on the shopping list, and obtain product inventory and stock keeping data of the merchant store (e.g., a datatable indicating the storing location of each item).
• the TVC may query the obtained product inventory and stock keeping data based on the product identifier and the product category for each product item, and 1 determine an in-store stock keeping location for each product item based on the query.
• the TVC may automatically load a store
• TVC TVC check-in at a grocery store (e.g., in a similar manner
• the TVC may provide a store map 510 of the grocery store, and may
• tags 511a indicating locations of product items from the consumer's shopping
• the consumer may engage the mobile device to scan an in-store
• TVC may provide virtual labels overlay on top of the reality scene
• 14 labels may provide locations of "Apple Jam” 517 on the shelf, or provide directions for
• the virtual overlay label 517 may comprise a
• the TVC may receive the shopping list
• FIGURES 5D-5F provide exemplary UIs illustrating virtual shopping
• 25 may experience a store virtually by receiving a store floor plan for a designated location
• the virtual store may be comprised of stitched-together
• TVC TVC to stitch together a virtual and 1 continuous composite view of the store (e.g., akin to Google street view composite, etc.).
• a virtual and 1 continuous composite view of the store e.g., akin to Google street view composite, etc.
• a consumer may move
• the store may position cameras
• every aisle and shelving stack may
• a2 store map including tags indicating a distribution view of in-store cameras (e.g., 530a-b,3 etc.) and the visual scope of each camera (e.g., 53ia-b) may be provided to a consumer4 so that the consumer.
• such camera may be positioned to5 capture the view of an aisle and the shelves on both sides (e.g., see camera 530a and its6 visual scope 531a, etc.).
• the camera may be positioned to capture a front7 view of an opposing shelf (e.g., camera 530b and its visual scope 531b, etc.).
• the cameras 532a may be positioned in a9 grid such that the visual scope 532b of the cameras overlap, allowing TVC to stitch0 together images to create a panoramic view of the store aisle. 1 [ 00117]
• such cameras may provide a continuous2 live video feed and still photos may be obtained from the live video frame grabs, which3 may be used to generate virtual store maps.
• a motion detection4 component may be used as a trigger to take still photos out of a live videos when the5 motion detection component detects no motion in the video and thereby provides6 unobstructed views for virtual map composition.
• the consumer's view may then become filled with9 the live video feed of the camera closest to the consumer avatar's location.
• TVC may install1 robots 538 (e.g., Roombas and/or the like) in store, which are distributed among aisles 1 and stacks to obtain visual captures of the in-store scene using on-board cameras 539.
• robots 538 e.g., Roombas and/or the like
• the robots may comprise mobile intelligent robots (e.g., iRobot® Create
• the consumer may obtain a location of the robot 539a
• the robots may capture the in-
• the robots may comprise mobile intelligent
• the consumer may be navigating a merchant's
• the 18 CSR may place a link to the products. The consumer may click on the link provided by
• FIGURES 6A-19D provide example embodiments of an augmented reality
• the TVC may identify a card in the
• FIGURE 6 provides a diagram illustrating an example scenario of TVC
• 30 consumers e.g., user 611a and user 611b, receive a bill or invoice 615 for their
• the users 6na-b 1 may desire to split the bill 615 in different ways, e.g., share the bill equally per head
• cashier e.g., 617
• the cashier may split the bill 615 to generate separate bills for
• the users 6na-b may launch a TVC component
• the users 6na-b may view virtual overlaid labels on
• users 6na-b may facilitate payment from their
• user 611a may operate her mobile device 613a to capture a scene of the two
• the TVC component instantiated on the mobile device 613a may send an authorization
• users 6na-b may conduct a
• FIGURE 7A provides a diagram illustrating example virtual layers
• a TVC component may be instantiated at a consumer camera-enabled mobile device 713
• the TVC component may provide multiple layers of
• a consumer may select a merchant provided layer 715a to obtain product 1 information, product price, offers from the merchant, points options that apply to the
• a social layer 7 isd to obtain social rating/review information
• the different layers 7i5a-d may comprise
• 11 715b may provide information of related products based on user reviews from the social
• issuers, acquirers, payment gateway servers, and/or the like may bid for layer space in
• FIGURES 7B-7C provide exemplary UI diagrams illustrating consumer
• multiple information layers may be injected with
• a social layer 716a may provide information about
• a receipt layer 716b may provides detailed
• 24 wallet layer 716c may provide eligible account usage, e.g., healthcare products, etc.; a
• 25 merchant layer 7i6d may provide merchant information; a product layer 7i6e may
• the multiple virtual labels overlay may be overly crowded for the
• the consumer may check on information labels that are desired.
• FIGURE 8 provides diagrams illustrating example embodiments of
• virtual information layer overlays may be automatically injected based on
• the digital wallet 823 may be any suitable mobile device 813, e.g., "affordable wide-angle lens" 823, the digital wallet 823 may
• the TVC may automatically
• a consumer 811 may walk into a merchant store and
• the mobile device 813 may capture the consumer's GPS coordinates 826.
• the TVC may
• 19 mobile device captured in-store scenes, e.g., including retailer discounts, in-store map,
• FIGURES 9A-9E provide exemplary user interface diagrams illustrating
• a user may instantiate a wallet visual capturing
• a user may initiate a user's mobile device to capture views in reality.
• a user may initiate a user's mobile device to capture views in reality.
• a user may
• a user may move a sliding bar 907a to enable or disable a
• the TVC may capture a human finger point within a captured reality scene (e.g., see also
• the smart finger tip component 903a may engage 1 fingertip motion detection component (e.g., see FIGURE 20C) to detect movement of
• the TVC may generate visual frames from the
• a user may move the sliding bar 907b to enable or
• the TVC may automatically detect and identify whether any rectangular object
• a captured reality scene comprise a payment card, etc.
• 10 may move the sliding bar 907c to enable or disable facial recognition 903c, e.g., when
• the TVC may automatically recognize
• human faces e.g., including a human, a printed facial image on a magazine, a friend's
• a user may move the sliding bar 907d to enable or disable smart bill
• the TVC 17 may provide option labels based on a type of the bill.
• the TVC may provide options to facilitate tip calculation, bill splitting per actual
• a user may move the sliding bar
• the user may configure a maximum one-time
• 25 select a maximum amount of $500.00. In another implementation, a user may select to
• TVC such as a shopping cart 908a, a transfer funds mode 908b, a snap barcode
• a user may view a plurality of virtual labels
• the user may view a sliding
• the TVC may detect a human finger tip 912
• the TVC may determine the finger pointed rectangular object is a payment
• the TVC may determine whether the payment
• 11 account 913 The user may tap on the displayed option buttons 9i4a-b to indicate
• TVC may adopt OCR components such as, but not limited to Adobe
• the TVC may prompt a is message to inquire whether a user would like to add the identified card to the wallet,
• the TVC may provide a wallet icon 916 overlaid on top
• the smart finger tip component when the smart finger tip component is on (e.g., 910), the smart finger tip component is on (e.g., 910), the smart finger tip component is on (e.g., 910), the smart finger tip component is on (e.g., 910), the
• TVC smart finger tip component may capture the finger point movement.
• the user may tap and move his finger on the touchable
• an account 920 For example, the user may need to enter and confirm card information
• the TVC may automatically recognize card information 924 from OCR the captured scene, including card type, cardholder name, expiration date, card number, and/or the like.
• the TVC may request a user to enter information that is not available upon scanning the captured scene, such as the CW code 925, etc.
• the TVC may switch back to the visual capturing scene, with an overlaid notification showing the card is ready to use 926, and provide a plurality of overlaid option labels beneath the card 911, such as, but not limited to view balance 927a (e.g., a user may tap and see the current balance of the card), view history 927b (e.g., the user may tap and view recent transaction history associated with the card), transfer money from 927c (e.g., the user may select to transfer money from the card to another account), transfer money to 927d (e.g., the user may transfer money to the card from another account, etc.), pay shopping cart 927 ⁇ (e.g., the user may engage the card to pay the current shopping cart 908a), and/or the like.
• view balance 927a e.g., a user may tap and see the current balance of the card
• view history 927b e.g., the user may tap and view recent transaction history associated with the card
• transfer money from 927c e.g
• the TVC may prompt overlaid labels for fund transfer options, such as a few suggested default transfer amounts (e.g., $10.00, $20.00, $30.00, etc.) 928, or the user may choose other amounts 929 to enter a transfer amount 930.
• fund transfer options such as a few suggested default transfer amounts (e.g., $10.00, $20.00, $30.00, etc.) 928, or the user may choose other amounts 929 to enter a transfer amount 930.
• the user may move his finger to point to another card in the real scene so that the smart finger tip component may capture the payee card.
• the user may tap on the touchable screen to indicate a desired payee card.
• the TVC may capture the object the user has tapped on the screen 932 and determine it is a metro card. The TVC may then retrieve a metro card account enrolled in the wallet and prompt the user to select whether to transfer or re-read the card selection 933.
• the TVC may provide a message to summarize the fund transfer request 933 and prompt the use to confirm payment.
• Fund transfer requests may be processed via the payment transaction component as discussed in FIGURES 42A-43B.
• the TVC may provide a message notifying completion of the transaction 937, and the user may select to view the transaction receipt 938.
• the TVC may provide a virtual receipt 939 including a barcode 940 summarizing the transaction.
• the user may email 941 the virtual receipt (e.g., for reimbursement, etc.), or to earn points 942 from the transaction.
• FIGURES 10-14 provide exemplary user interface diagrams illustrating various card capturing scenarios within embodiments of the TVC.
• the TVC may detect the user's finger point via the smart finger tip in the real scene, and determine a human face is presented 1002 when the facial recognition component is enabled. In one implementation, the TVC may determine whether the detected face matches with any of the existing contact, and provide a message 1002 for the user to confirm the match. In one implementation, the user may confirm the match if it is correct 1004, or to view the contact list to manually locate a contact when the match is inaccurate 1005, or to add a new contact 1006.
• the TVC may provide a plurality of option labels overlaid on top of the reality scene, so that the user may select to call the contact 1008a, send a SMS 1008b, email the contact 1008c, transfer funds to the contact ioo8d, connect to the contact on social media ioo8e, view the contact's published purchasing history ioo8f, and/or the like.
• the TVC may retrieve a previously stored account associated with the contact, or prompt the user to enter account information to facilitate the transfer.
• a user may tap on the screen to point to a metro card 1111, and the TVC may determine the type of the selected card and provide a plurality of option labels, such as view balance 1112a, pay suggested amounts to the metro card ni2b-d, renew a monthly pass ni2e, and/or the like.
• the TVC may provide a plurality of option labels, such as view DMV profile 1114a, view pending tickets 1114b, 1 pay ticket 1114c, file a dispute request ni4d, and/or the like.
• the TVC may
• the TVC may be a store membership card 1220, e.g., a PF Chang's card, the TVC may
• 11 portion comprises an insurance card 1324, e.g., a Blue Cross Blue Shield card, the TVC
• 16 portion comprises a bill including a barcode 1326, e.g., a purchase invoice, a restaurant
• the TVC may provide a plurality of labels including is view bill details 1327a, pay the bill 1327b, request extension 1327c, dispute bill i327d,
• 19 insurance reimbursement 1327 ⁇ (e.g., for medical bills, etc.), and/or the like.
• 21 portion comprises a purchase item 1431, e.g., a purchase item comprising a barcode,
• the TVC may provide a plurality of labels including view product detail 1433a,
• 25 view social rating I433f, submit a social rating I433g, and/or the like.
• the TVC may provide a list of
• the TVC may
• 29 provide a list of shopping sites 1434b that lists the purchase item.
• FIGURES 15A-15F provide exemplary user interface diagrams illustrating a user sharing bill scenario within embodiments of the TVC.
• a user may place two or more payment cards with a restaurant bill and capture the view with the camera-enabled mobile device.
• the TVC may provide plurality of labels including view bill details 1504a, split bill 1504b (e.g., as there are more than one card presented, indicating an attempt to split bill), pay bill 1504c, calculate tip amount i504d, update bill 15046, and/or the like.
• the TVC may provide option labels such as equal share 1505a, prorate share 205b, share by actual consumption 1505c, and/or the like.
• the PVTC may provide tags of the consumed items i507a-b, e.g., by reading the bill barcode 1502, or by performing OCR on the bill image, etc.
• a user may drag the item 1507a, e.g., a "bloody Mary" 1508 into the "I Pay" bowl 1510.
• the user may tap on the plus sign 1509 to increase quantity of the consumed item.
• the user may tap on a card 1511 to indicate pay with this card for the item in the "I Pay" bowl 1510 as summarized in label 1512.
• the TVC may provide option labels for tips, including suggested tip percentage (e.g., 15% or 20%) 1513 or enter tip amount 1514.
• the user may manually enter a tip amount 1520.
• the TVC may prompt a message to the user summarizing the payment with the selected card 1521.
• the TVC may automatically prompt the message to inquire whether the user would charge the remaining items on the bill to the second card 1522.
• the user may drag items for payment with the second card in a similar manner as described in FIGURE 15A. 1 [ 00154] With reference to FIGURE 15C, if the user selects equal share, the TVC
• the TVC may tap on one card 1535, and the TVC may provide a plurality of labels including
• the user may enter a share for a selected card 1537, and
• 11 view a message for a summary of the charge 1538.
• the user may
• TVC 15 restaurant bill between two friends' credit cards, TVC may require authentication
• the mobile device/wallet that is used to instantiate TVC component may
• card *7899 the cardholder of card *7899
• card *5493 belongs to a different
• TVC may provide a message showing card *5493 is
• 26 consumer may proceed with card enrollment in a similar manner as 215 in FIGURE 2B.
• the consumer may elect to provide authentication
• the cardholder of card *5493 may optionally receive an alert message informing the attempted usage of the card 1551.
• the alert message 1551 may be a V.me wallet push message, a text message, an email message, and/or the like.
• the cardholder of card *5493 may elect to approve the transaction 1552, reject the transaction 1553, and/or report card fraud 1554.
• FIGURE 16A provide exemplary user interface diagrams illustrating a card offer comparison scenario within embodiments of the TVC.
• various payment cards such as Visa, MasterCard, American Express, etc., may provide cash back rewards to purchase transactions of eligible goods, e.g., luxury products, etc.
• the TVC may identify the item, e.g., via trademark 1605, item certificate information 1606, and/or the like.
• the TVC may provide a tag label overlaid on top of the item showing product information 1607, e.g., product name, brief description, market retail price, etc.
• the TVC may provide a plurality of overlay labels including view product details, luxury exclusive offers, where to buy, price match, view social rating, add to wish list, and/or the like.
• a user may place two payment cards in the scene so that the TVC may capture the cards.
• the TVC may capture the type of the card, e.g., Visa 1608a and MasterCard 1608b, and provide labels to show rebate/rewards policy associated with each card for such a transaction i6o9a-b. As such, the user may select to pay with a card to gain the provided rebate/rewards.
• TVC may categorize information overlays into different layers, e.g., a merchant information layer to provide merchant information with regard to the captured items in the scene, a retail 1 information layer to provide retail inventory information with regard to the captured
• a social information layer to provide ratings, reviews, comments
• TVC may provide a merchant information layer 1611a
• virtual overlays may include a
• TVC offers and discounts for the merchant 1612c, and/or the like.
• TVC is another example.
• 13 may provide a list of retail stores featuring the captured object 1605, e.g., a list of local
• a consumer may slide the information layer
• PVTC may capture a receipt
• a consumer may tap on the provided virtual label
• Cartier e.g., 1613, 1623, etc.
• store map including
• a store map may be used to store inventory information, e.g., as shown in FIGURE 5B.
• a store map may be used to store inventory information, e.g., as shown in FIGURE 5B.
• 30 may provide virtual labels indicating social reviews, ratings, comments, activities 1 obtained from social media platforms (e.g., Facebook, twitter, etc.) related to captured
• TVC may provide virtual labels of social comments related to the
• TVC may provide virtual labels of social ratings/comments related to the
• 9 information layer 1611c may further provide sample social comments, product reviews,
• TVC may perform a pattern
• pattern recognition may be correlated with other contexts within the scene to determine
• the captured object e.g., the ring shaped object 1630 may be a piece of "Cartier"
• the TVC may provide identified item information 1631 in a virtual
• the TVC may recognize it as a "Cartier" branded bracelet
• FIGURES 17 provide exemplary user interface diagrams illustrating in-
• TVC TVC
• a user 25 may facilitate a user to engage a restricted-use account for the cost of eligible items.
• 26 restricted-use account may be a financial account having funds that can only be used for
• 29 restricted use account may comprise Flexible Savings Accounts (FSA), one or more
• HSA Health Savings Accounts
• LOC Line of Credit
• the restricted-use account may comprise a food voucher, a food stamp, and/or the like.
• the approval process of payment with a restricted use account may be administered by a third party, such as, but not limited to FSA/HSA administrator, government unemployment program administrator, and/or the like.
• the TVC may automatically identify goods that are eligible for restricted-use accounts in a merchant store.
• the TVC may allow a user to place a camera enabled device at a merchant store (e.g., scanning), and view a camera scene with augmented reality labels to indicate possible items eligible for a restricted-use account.
• a camera enabled device at a merchant store (e.g., scanning)
• the user may also obtain augmented reality labels 1751 which identifies various products/items on the shelf, and show one or more possible eligible restricted-use accounts 1752.
• FIGURES 18-19 provide exemplary user interface diagrams illustrating post-purchase restricted-use account reimbursement scenarios within embodiments of the TVC.
• a user may operate a camera enabled device to capture a view of a receipt 1861, and obtain augmented reality labels 1862 indicating items that are eligible for restricted-use accounts.
• the TVC wallet component may perform an instant OCR to extract item information and determine items such as "Nyquil" is eligible for FSA/HSA/HRA 1864 usage, and grocery/food items are eligible for food stamp 1862 usages.
• the TVC may generate a virtual receipt and proceed to process reimbursement request with the selected restricted-use account. [ 00171]
• the TVC does not automatically determine an 1 item as eligible for any restricted-use accounts, e.g., an "Ester-C" supplement, a user
• 2 may tap on the screen to select it, and may view a list of accounts 1863 to select a user
• 3 desired reallocation account e.g., any restricted-use account, loyalty account, and/or
• the TVC may identify a payment account that
• the TVC may match the "*1234" Visa account with any
• the TVC may prompt the user to select other accounts for
• the TVC may generate a
• 17 user may indicate an account for depositing the reimbursement funds, e.g., the "Visa
• the TVC may generate a reimbursement
• FIGURE 20A provides an exemplary logic flow diagram illustrating
• a user may instantiate a TVC component on a camera-enabled mobile
• the user may point to an object (e.g., a card, a purchase item, etc.) in 1 the reality scene, or touch on the object image as shown on the screen 2004 (e.g., see
• the TVC upon receiving user finger indication, the TVC
• the TVC may detect fingertip
• the TVC may then perform OCR and/or pattern recognition on
• the TVC may start from
• the finger point and scan outwardly to perform edge detection so as to determine a
• the TVC may then perform OCR within the determined contour
• the TVC may determine a type of the card 2015 and the card number 2017. For
• the TVC may determine whether the card is a payment card (e.g., a credit card, is a debit card, etc.), a membership card (e.g., a metro card, a store points card, a library
• a personal ID e.g., a driver's license, etc.
• an insurance card e.g., a credit card, etc.
• the TVC may query the user wallet for the card information 2018 to determine whether
• the card matches with any enrolled user account, and may generate and present overlay
• the TVC may optionally capture mixed gestures within the captured reality scene 2029,
• the TVC may extract information from the barcode/QR
• the barcode information may be used to determine a type of the object 2023, e.g., the barcode information.
• the TVC may retrieve merchant information when the object
• overlay labels i327a-e for an
• the TVC may perform facial recognition to identify whether the
• the TVC may retrieve contact information if the contact is located from a contact list
• the TVC may then generate and present
• overlay labels for the detected human face e.g., see overlay labels ioo8a-f for an
• the TVC may proceed to transfer
• the TVC may send
• FIGURES 41A-43B performed in a similar manner as in FIGURES 41A-43B.
• FIGURE 20B provides an exemplary logic flow diagram illustrating
• TVC may inject a layer of virtual information labels (e.g., merchant
• 26 captured reality scene based on intelligent mining of consumer's activities, e.g., GPS
• a consumer may engage in user interests
• the TVC may parse the received activity record for key terms 2032, and generate a
• the TVC may store the generated record at a local storage element at the user mobile
• TVC may determine a type of the object in the
• the TVC may retrieve stored user interest record 2038, and obtain
• TVC may correlate the search term with product information 2044 (e.g., include
• the TVC may optionally capture mixed gestures within the captured
• 16 reality scene 2029 e.g., consumer motion gestures, verbal gestures by articulating a
• the user interests record comprise a real-
• TVC may insert a retailer layer of virtual labels 2046 to the consumer device.
• a retailer layer of virtual labels 2046 may insert a retailer layer of virtual labels 2046 to the consumer device.
• the TVC may parse the user activity record for user interests indicators
• 26 layer e.g., see i6na-d in FIGURES 16B-16C.
• FIGURE 20C provides an exemplary logic flow illustrating aspects of
• TVC 28 fingertip motion detection within embodiments of the TVC.
• TVC
• 29 may employ motion detection components to detect fingertip movement within a live
• Such motion detection component may be comprised of, but not
• LK Lucas-Kanade
• classes defined under iOS developer library such as AVMutableCompisition, UllmagePickerController, etc., may be used to develop video content control components.
• the TVC may obtain two consecutive video frame grabs 2071 (e.g., every 100 ms, etc.).
• the TVC may convert the video frames into grayscale images 2073 for image analysis, e.g., via Adobe Photoshop, and/or the like.
• the TVC may compare the two consecutive video frames 2075 (e.g., via histogram comparison, etc.), and determine the difference region of the two frames 2078.
• the TVC may highlight the different region of the frames, which may indicate a "finger" or "pointer" shaped object has moved into the video scene to point to a desired object.
• the TVC may determine whether the difference region has a "pointer" shape 2082, e.g., a fingertip, a pencil, etc. If not, e.g., the difference region may be noise caused by camera movement, etc., the TVC may determine whether the time lapse has exceeded a threshold. For example, if the TVC has been capturing the video scene for more than 10 seconds and detects no "pointer" shapes or "fingertip," TVC may proceed to OCR/pattern recognition of the entire image 2087. Otherwise, the TVC may re-generate video frames at 2071.
• a threshold For example, if the TVC has been capturing the video scene for more than 10 seconds and detects no "pointer" shapes or "fingertip," TVC may proceed to OCR/pattern recognition of the entire image 2087. Otherwise, the TVC may re-generate video frames at 2071.
• the TVC may determine a center point of the fingertip, e.g., by taking a middle point of the X and Y coordinates of the "fingertip.”
• the TVC may perform edge detection starting from the determined center point to determine the boundary of a consumer pointed object 2085.
• the TVC may employ edge detection components such as, but not limited to Adobe Photoshop edge detection, Java edge detection package, and/or the like.
• the TVC may perform OCR and pattern recognition of the defined area 2088 to determine a type of the object.
• FIGURE 20D provides an exemplary logic flow illustrating aspects of generation of a virtual label (e.g., 2030, 2049, etc.) within embodiments of the TVC.
• a virtual label e.g., 2030, 2049, etc.
• the TVC may load live video of the reality scene 2052. If the camera is stable 2053, the TVC may obtain a still image 2054, e.g., by capturing a video frame from the live video, etc. In one implementation, the image may be obtained at 2006 in FIGURE 20A.
• TVC may receive information related to the determined object 2057 (e.g., 2018, 2027, 2028 in FIGURE 20A), and filter the received information based on consumer configurations 2058 (e.g., the consumer may have elected to display only selected information labels, see FIGURES 1C-1D). For each virtual label 2059, the TVC may determine, if there is more information or more label to generate 2060, the TVC may retrieve a virtual label template 2061 based on the information type (e.g., a social rating label may have a social feeds template; a product information label may have a different template, etc.), and populate relevant information into the label template 2062.
• the information type e.g., a social rating label may have a social feeds template; a product information label may have a different template, etc.
• the TVC may determine a position of the virtual label (e.g., the X-Y coordinate values, etc.) 2063, e.g., the virtual label may be positioned close to the object, and inject the generated virtual label overlaying the live video at the position 2065.
• a data structure of a generated virtual label substantially in the form of XML-formatted data, is provided below:

Landscapes

• Business, Economics & Management (AREA)
• Engineering & Computer Science (AREA)
• Accounting & Taxation (AREA)
• Strategic Management (AREA)
• Finance (AREA)
• Physics & Mathematics (AREA)
• General Business, Economics & Management (AREA)
• General Physics & Mathematics (AREA)
• Theoretical Computer Science (AREA)
• Development Economics (AREA)
• Marketing (AREA)
• Economics (AREA)
• Computer Networks & Wireless Communication (AREA)
• Entrepreneurship & Innovation (AREA)
• Game Theory and Decision Science (AREA)
• Tourism & Hospitality (AREA)
• General Health & Medical Sciences (AREA)
• Health & Medical Sciences (AREA)
• Human Resources & Organizations (AREA)
• Primary Health Care (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)
• Cash Registers Or Receiving Machines (AREA)
• Information Transfer Between Computers (AREA)
• User Interface Of Digital Computer (AREA)
• Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Priority Applications (9)

Applications Claiming Priority (14)

Related Parent Applications (1)

Related Child Applications (3)

Publications (1)

Family

ID=49384995

Family Applications (1)

Country Status (8)

Cited By (58)

Families Citing this family (453)