WO2018097830A1 - Blocs de conception d'architecture de système - Google Patents

Blocs de conception d'architecture de système Download PDF

Info

Publication number
WO2018097830A1
WO2018097830A1 PCT/US2016/063654 US2016063654W WO2018097830A1 WO 2018097830 A1 WO2018097830 A1 WO 2018097830A1 US 2016063654 W US2016063654 W US 2016063654W WO 2018097830 A1 WO2018097830 A1 WO 2018097830A1
Authority
WO
WIPO (PCT)
Prior art keywords
capability
blocks
functions
block
user interface
Prior art date
Application number
PCT/US2016/063654
Other languages
English (en)
Inventor
Akshay CHOPRA
Matthew Dill
Original Assignee
Visa International Service Association
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 Visa International Service Association filed Critical Visa International Service Association
Priority to SG11201903571PA priority Critical patent/SG11201903571PA/en
Priority to US16/349,902 priority patent/US10866709B2/en
Publication of WO2018097830A1 publication Critical patent/WO2018097830A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2203/00—Indexing scheme relating to G06F3/00 - G06F3/048
    • G06F2203/048—Indexing scheme relating to G06F3/048
    • G06F2203/04802—3D-info-object: information is displayed on the internal or external surface of a three dimensional manipulable object, e.g. on the faces of a cube that can be rotated by the user

Definitions

  • an electronic simulation environment allows various secure system capabilities to be displayed in block form and grouped by function for easy recognition. The environment then allows these various capability blocks to be selected and placed according to the requirements of a particular system to visualize dependencies and connections. Each block may have additional definition and design information visually available in the form of 'turning' the block in response to an event, such as a mouse over.
  • code modules associated with each function may be assembled for rapid prototyping of test systems according to their placement.
  • FIG. 1 illustrates a block diagram of system supporting system architecture design blocks in accordance with the current disclosure
  • FIG. 2 is an illustration of a simulated display showing system categories
  • FIG. 3 is an illustration of a simulated display showing capability blocks for a selected system category
  • Fig. 4 illustrates animation of a selected capability block responsive to a user interface event
  • Fig. 5 illustrates another aspect of animation of the selected capability block of Fig. 4 responsive to a different user interface event
  • FIG. 6 is an illustration of a simulated display showing a representative system architecture using capability blocks
  • Fig. 7 illustrates a detailed view of aspects of selected capability blocks shown in Fig. 6;
  • Fig. 8 illustrates an exemplary display for creating a capability block
  • FIG. 9 illustrates an exemplary process flow for using system architecture design blocks.
  • Fig. 1 generally illustrates one embodiment of a design platform 102 that supports system architecture design blocks.
  • the design platform 102 may include a processor 104 and memory 106.
  • the memory 106 may store both data and executable code.
  • the memory may store category information 108 related to various financial and service functions available for use in the design process.
  • the memory 106 may also include specific capability block data 1 10 that, in an embodiment, may be sorted according to the categories 108. The categories and specific capability blocks are discussed in more detail below.
  • Executable data stored in the memory 106 may include program and user interface executable code 1 12 used to implement the design process.
  • the design platform 102 may also include other executable code that supports an operating system and various utilities including boot programs (not depicted).
  • the design platform 102 may also include a simulation environment 1 14 used to support rapid prototypes built using one embodiment of the capability blocks.
  • the simulation environment 1 14 may include web services 1 16 that provide a framework for interaction with web services made available by the various capability blocks 1 10.
  • SOAP Simple Object Access Protocol
  • REST Representational State Transfer
  • a user interface 126 may include a display, which itself may include a touchscreen input, a keyboard, a cursor controller, such as a mouse, or other known user interface elements used to interact with a human user.
  • Fig. 2 illustrates a simulated screen 200 of the user interface 140 showing a variety of categories that represent various architectural functions available for use in a design. These categories may include, but are not limited to, product functions 142, risk management 144, core functions 146, value-added functions 148, payment enablement 150, ecosystem functions 152, and insights 154. Each of these categories will be discussed in more detail below. In various embodiments, each of the categories may be uniquely identified by coloring or shading and may be illustrated by the surface shading in Fig. 2.
  • a portion 200 of the user interface 126 is illustrated in Fig. 3, showing capabilities available in the risk management category.
  • Each of the capability blocks illustrated has the same color, or in the case of Fig. 3, the same surface shading as the parent category representation of Fig. 2.
  • the risk management category 144 is illustrated in Fig. 3, a description of representative capabilities available for the remaining illustrative categories follows the description of Fig. 3.
  • every capability block from every category may be available on the portion 200 of the user interface 126, for example using a scrolling window.
  • the color or surface shading may be used to help identify capability blocks associated in the same category.
  • Risk Management 144 may be directed to the broad concept of reducing danger or points of weakness in a secure network. In one embodiment, risk
  • Tokenization 202 May replace sensitive data such as card data with a secure token such as a token from a trusted party. Tokens may provide a domain-restricted digital credential for use in devices, apps, cloud services and more.
  • ID & Verification 204 May combine network risk scores with additional data such as bank data, purchase history, device ID, and biometrics to register customers and reduce downstream service risks.
  • Location Confirmation 206 May establish a network party's location location such as a cardholders location, via mobile device to validate overseas transactions, reduce declines or offer services.
  • Decision Manager 208 May include data sources which analyze big data into real-time approval decisions to keep businesses moving and reduce fraud.
  • Risk Based Authentication 210 May provide a multi-domain, multi-factor security capability, such as three domain secure (3DS), to help prevent the fraudulent use of branded cards online.
  • 3DS three domain secure
  • Takeover Protection 212 May defend network participants, such as cardholders and merchants, from fraudulent use of online accounts by identifying suspicious actors and monitoring account changes.
  • Cardholder Authentication 214 May authenticate cardholders through a secure network, such as VisaNet, at enrollment and during purchase transactions with a comprehensive set of tools.
  • a secure network such as VisaNet
  • AML & OFAC Checks 216 May leverage brand tools and government watchlists to identify suspicious behaviors and provide risk scoring on payors and payees.
  • Real Time Risk Scoring 218 May allow the network to analyze big data to provide advanced fraud screening and transaction scoring in real-time.
  • Threat Intelligence 220 May include threat intelligence which may help banks and retailers prioritize what threats to act upon, how to act, and may provides actionable tools.
  • Risk Replay 222 May allow 'replay of risk' decisions using historical transaction data to create 'what-if modeling scenarios.
  • Domain Controls 224 May provision a token and cryptogram tied to a mobile device, payment application or service category and eliminate out of band usage.
  • Fraud Alerts 226 May inform cardholders directly via SMS, messaging service, email or other out-of-band networks when unusual or high value transactions occur.
  • Risk Manager 228 May enhance decisioning capability with custom rules in Risk Manager or benchmark decisions against brand scores.
  • Address Verification 230 May confirm a customer's billing address or mail codes with stored records to reduce fraud and use of lost/stolen cards.
  • Biometrics 232 May identify or authenticate a user identity using biological identifiers (e.g. fingerprint, iris or palm scanners and facial recognition).
  • biological identifiers e.g. fingerprint, iris or palm scanners and facial recognition.
  • Core functions 146 may be those functions that are fundamental to to a network such as a financial processing network.
  • Credit Card May provide consumers the ability to "pay later" for goods or services wherever brand is accepted with a personalized credit facility.
  • Debit Card May provide consumers the ability to "pay now” for goods or services wherever brand is accepted by linking to a current account.
  • Co-Brand Card Custom May include credit or debit program offering special points or rewards from a leading consumer brand.
  • Prepaid Card May provide consumers the ability to "pay in advance” for goods or services wherever the brand is accepted by loading a prepaid account.
  • Private Label Card May leverage network to build a custom branded payment solution accepted at participating locations.
  • Gift Card May include a card pre-loaded with funds that can be gifted to others for use across the brand network or at a single merchant.
  • Proximity Acceptance May include physical acceptance performed at the retail POS by swiping, dipping, tapping or streaming.
  • 020 Acceptance May include purchase experiences which begin remotely and may end in proximity (e.g., order ahead, taxi service, delivery services).
  • Remote Acceptance May include eCommerce or Mobile acceptance performed end to end in a digital environment through card entry, card on file, subscription or pay button.
  • Product packages 142 may include higher level functions and utilities that facilitate end-to-end connectivity and security in transaction processing.
  • Verified Transactions May increase security of online card use using three domain secure (3DS) protocol and Cardholder Authentication System.
  • 3DS domain secure
  • Checkout May allow virtual wallets such as Visa Checkout to store card information securely and streamlines the payment experience for consumers and merchants.
  • Transaction processing May include a service which consolidates acceptance of card-based payments and alternative payments options for online or in-app services.
  • Direct processing May allow exchange value card-to-card or service provider-to-card over network.
  • Applications include P2P, bill pay, funds transfer, etc.
  • Communications Network May include an integrated network of retailers, financial institutions, offers, rewards and loyalty programs.
  • Developer May include a unified set of application program interfaces and software design kits providing partners and developers with a testing sandbox and powerful tools for commerce.
  • Mobile support May include a mobile-first payment and acceptance structure which extends retail acceptance
  • Token Service May include token vault and provisioning system integrated into network and connected to issuers, processors and third party platform providers.
  • Payment gateway May describe an API based payment gateway that enables digital merchants and developers to accept online payments easily and securely.
  • Value-add services 148 may include services that enhance the user experience or extend the capabilities of secure network processing architecture, such as a financial network, beyond simple point-of-sale card processing.
  • Fast Funds May allow issuers to configure Fast Funds to enable near-instant funds transfer to recipient account, as opposed to 2 days standard transfer which may be useful for push payments.
  • Card on File May store account details such as card details securely to simplify repeat purchases and/or enable aggregation, recurring or subscription services.
  • Aggregation May accumulate small card payments up to approved limits or time thresholds to simplify shopping or billing experience (e.g. music).
  • Micropayment May identify transactions by merchant, type and value to establish special categorization for low value transaction types.
  • Points May link a card or profile and allow consumers to accumulate and redeem points to drive loyalty or purchase behaviors.
  • Recurring Payments May include estanding instructions that allow customers to make card payments at regular intervals (e.g. bills, subscriptions).
  • Transaction Alerts May connect customers with purchases in real time through Network Alerts. Card purchases may be passed to connected apps or devices.
  • Card Controls May help consumers personalize card permissions through processor systems using limit, threshold, location or channel data.
  • FX Rate Check May allow easy access to daily currency conversion rates. Simplify user experience for cross-border transactions.
  • Real Time Redemption May offer redemption at the POS. Purchase amount reduced in real time as part of the authorization and consumers notified via receipt or SMS or other out-of-band communication.
  • Digital Receipt May include network Alerts which may be formatted as rich consumer receipts and delivered electronically via text or email.
  • Instant Issue May include real-time digital issuance of a new, purchase ready card in-app or online. Instant Issue may seamlessly connect consumers and card products in the digital environments where they shop and play.
  • Loyalty May allow merchants and issuers to create custom loyalty and rewards programs that are linked to Visa cards.
  • Real Time Offers May offer discounts to cardholders to drive purchase activity with real-time analytics, targeted discounts and support for third-party offer programs.
  • Transaction History May publish and update transaction history in real time to a website or mobile app. API allows permission based configurations.
  • Sourced Offers May display offers sourced on a partner website or mobile app and may provide incentive for activation or usage.
  • Card Link May link value to card usage. Whenever an electronic event such as a Visa purchase event occurs, it may trigger offers, loyalty, alerts or other third party services.
  • Account Updater May automatically update expiring/renewed cards without requiring users to enter information. May also reduce service interruptions or
  • Location-Based Alerts May tie mobile apps to Visa's geo-location offering and provide cardholders seamless service, related offers, fraud protection, etc.
  • Travel Notifier May be a tool for network users such as cardholder to inform bank about overseas travel plans via app or online which may helps reduce overseas declines and enables offers.
  • Payments Enablement May be a tool for network users such as cardholder to inform bank about overseas travel plans via app or online which may helps reduce overseas declines and enables offers.
  • Payments Enablement 150 may be functions that support the physical act of performing a transaction.
  • Swipe May include Magnetic Stripe Technology activated during purchase by swiping the reader of a merchant POS machine.
  • Dip May include EMV Chip technology activated during purchase through chip on chip contact with a merchant POS machine.
  • Tap May include using NFC to provide a secure tap to pay experience at millions of retail locations worldwide from card, wearable or mobile device.
  • Stream May stream low energy Bluetooth (BLE) or sound waves tied to a merchant location or purchase activity to initiate a payment or pass payment
  • Fund May include Account Funding Transaction (AFT) that may pull funds from sender's account, in preparation for pushing funds to a recipient's account.
  • AFT Account Funding Transaction
  • Scan May include a acan or Barcode tied to a merchant location or purchase activity to initiate a payment or pass payment credentials.
  • Push May exchange value card-to-card or service provider-to-card include P2P, bill pay, funds transfer, etc.
  • Ecosystem functions 152 may be electronic functions which may connect a transaction or financial process with the external world, such as social media, location services, smart phone operability and more.
  • Beacons / Sensors May include low-cost hardware devices that establish events (e.g. in proximity) or transmit messages that can be acted upon by applications.
  • Geolocation Services May include mapping technology coupled with application intelligence to identify people or events to enhance and/or deliver services (e.g. offers, fraud, etc.).
  • Mapping Services May include specialized map providers enabling other businesses to integrate/overlay service offerings via APIs.
  • Data Visualizers May include tools that enable the simplified graphic display of diverse data types. May be integrated into apps or webpages via APIs.
  • Messaging Platforms May include messaging platforms that enable individual or group based communication and have become a powerful platform for related services through API/SDK.
  • Social Media Platforms May include Social Media platforms that enable community based publishing, sharing and commenting features and have become a powerful platform for related services through API/SDK.
  • QR Code / Reader May include QR code (or bar code) which may be converted from machine readable format to text or data format.
  • Smart OS May include integration with proprietary operating system for mobile devices and other connected devices (e.g. Cars, TV, wearables).
  • other connected devices e.g. Cars, TV, wearables.
  • Blockchain May include a distributed database that maintains a continuously growing list of data records hardened against tampering and revision with timestamping and cryptography.
  • Internet of Things May describe a network of objects, devices, vehicles, buildings etc. that connect, collect and exchange data through the cloud with embedded technology and sensors.
  • Insights 154 may help make actionable business decisions based on analysis of thousands, if not millions, of individual transactions so that a business can better serve its customers.
  • Pricing Analytics May drive market studies and initiate limited trials to optimize pricing for new product or service categories.
  • Data & Analytics May receive insight from transaction data, ranging from simple batch data to dashboards or bespoke analytics programs.
  • Cardholder Analytics May use transaction data to understand consumer purchase trends and encourage or reward purchase activity.
  • Retail Analytics May use retail transaction data to understand purchase trends, benchmark among peers or acceptance locations, and encourage purchases.
  • Cardholder Segmentation May use data and market insights to segment cardholders into behavioral clusters and build product offerings.
  • Fig. 4 is a graphical illustration of a characteristic of a capability block, in this illustration, the capability block 240 representing tokenization is shown in a title view 241 .
  • the block may rotate as illustrated by partially turned capability block 242 to reveal a descriptive view 245 of the function as illustrated in rotated block 244.
  • each of the capability blocks described for any function in any category may have the ability to change its displayed shape in order to a descriptive view 245 about that particular capability block. This action is different from a "tool tip" that pops up over an object when a mouse hovers over the object, as found in some word processing or drawing applications.
  • another user interface event such as a shift-mouse over event, may cause the capability block 242 rotate in opposite direction, as illustrated by partially rotated block 246, to reveal representative executable code associated with that function as shown at block 248.
  • Fig. 6 illustrates a sample architecture 260 which may be shown on a second portion 261 of a user interface 126 illustrating how blocks may be added sequentially or by drag-and-drop to visualize both the capabilities required to implement a solution and how the various capabilities fit together in the course of transaction.
  • the sample architecture 260 of Fig. 5 shows how a smartphone enabled payment system may be architected.
  • a smartphone OS 262 may be taken from the Ecosystem category 152 and coupled to a payment enablement capability 150, specifically, a tap function 264, defining that the smartphone OS 262 may utilize near-field communication (NFC) for this proposed solution.
  • NFC near-field communication
  • a token service 266 selected from the product function category 142 may be used to add security to transactions by replacing a personal account number (PAN) with a token.
  • the token service 266 may interact with core functions 146 such as credit 272 and debit 274 functions to allow use of both of those payment vehicles in the token service environment.
  • core functions 146 such as credit 272 and debit 274 functions to allow use of both of those payment vehicles in the token service environment.
  • An extension of the ID and Verification capability 268 is biometrics 270, also from the risk management category 144.
  • the biometrics 270 may take advantage of the ecosystem functions of the smart phone available through the smartphone OS capability 262.
  • each capability block 264, 266, 272 may include a respective web service (WS) code module 280, 282, 284 including an appropriate interface to publish and request services.
  • WS web service
  • SOAP or REST protocols may be used to publish the services that are made available by a particular capability block so that the simulation environment 1 14 can manage data transfers between the various connected blocks.
  • the tap function may respond to a start of simulation command by returning a token and transaction details representing a customer tap at an NFC point of sale terminal. The token and transaction details may be transferred by the simulation environment 1 14 to the adjacent block, the token service capability block 266.
  • the token service web services module 282 may simulate the token service role in a transaction by de- tokenizing and interacting with the credit web services module 286 to generate transaction approval or denials based, in part, on other downstream services, such as ID and verification capability block 268, which is not depicted in Fig. 7.
  • ID and verification capability block 268 which is not depicted in Fig. 7.
  • different scenarios may be rapidly simulated by moving appropriate blocks to create connections.
  • graphical connectors may be used to simulate conditional data flows, branches, or other functions that are not necessarily performed in sequence, such as evaluating data with functions from the Insights category 154.
  • the results of a simulation may be in the form of "data on the wire," that is, the contents of the data flowing between blocks, including input data and output data. While the simulation provides valuable insights, an even more powerful extension of the system architecture design blocks is a fully configurable system that requires only verification of the external connection protocols and data formats to be able to build a production system using this concept.
  • Fig. 8 is a simulation of a user interface 288 illustrating an administrative screen for creation of new blocks as new capabilities become available.
  • text entry areas such as input area 294 entering a title and an input area 292 for entering a description.
  • the description may include a brief definition of the features and functions of the capability block being created, such as those listed above.
  • Input area 294 may be used to select a category with which to associate the newly created capability block. And ability to create a new category may also be provided with in the select category input area 294.
  • Input area 296 may be used to paste in
  • a simple link to a code repository may be used to associate the prototyping code with this block.
  • a preview area 298 may allow real time viewing of the capability block as it is being created. For example, as the title is entered at input area 290, the title may appear in the preview area 298. Similarly as description and prototyping code are available the preview area 298 may accommodate animations as described above to show the description and/or the prototyping code or link.
  • Fig. 9 illustrates a method 300 of modeling a system, more particularly, a financial system.
  • a representation of system categories 142-154 is stored in a memory 106 of a design platform 102.
  • the representation may include a title, descriptive data, and color or shading information used to distinguish the categories when displayed.
  • Block 304 shows a representation of each of a plurality of capability blocks may be stored at the design platform 102. Capability blocks may sometimes be referred to as system functions due to the nature of what each capability block represents. Each capability block may be assigned to a respective one of the system categories.
  • the representations for each of the plurality of capability blocks may include a title, a description, a code module used for simulation of the represented function, and a color or shading that associates a capability block with its respective system category.
  • a title view 241 of one or more of the capability blocks may be presented via a first portion 200 of a user interface 126.
  • a user interface event associated with a first of the presented capability blocks may be received at block 308.
  • the user interface event may be a mouse over event.
  • the user interface event may be selection of the first of the presented capability blocks via mouse click or screen tap.
  • the title view 241 may be replaced, at block 310, with a descriptive view 245 of the first of the presented capability blocks.
  • the descriptive view may be maintained until the user interface event is cleared, such as by moving a screen cursor off of the first of the presented screen functions.
  • a selection of a first capability block may be received via the user interface 126 and at block 314, the selected first capability block may be moved to a first location on a second portion 260 of the user interface 126 responsive to a user interface command.
  • Blocks 316 and 318 may cause the selection and movement of a second capability block to the second portion 260 of the user interface 126.
  • this process may be used to select and place capability blocks 264 and 266 on the second portion of the display 260.
  • this process of selecting and placing capability blocks may be repeated as many times as necessary to capture the system architecture of a proposed
  • the first capability block 262 may be caused to interact with the second capability block using a first code module 280 associated with the first capability block 264 and a second code module 282 associated with the second capability block 266.
  • the interaction may be in the form of a simulation of the functions and data transfers performed by and between the capability blocks or system functions represented in a particular architecture.
  • the methods or routines described herein may be at least partially processor- implemented. For example, at least some of the operations of a method may be performed by one or processors or processor-implemented hardware modules. The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processor or processors may be located in a single location (e.g., within a home environment, an office environment or as a server farm), while in other embodiments the processors may be distributed across a number of locations.
  • the one or more processors may also operate to support performance of the relevant operations in a "cloud computing" environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., application program interfaces (APIs).)
  • SaaS software as a service
  • the performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines.
  • the one or more processors or processor-implemented modules may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the one or more processors or processor-implemented modules may be distributed across a number of geographic locations.
  • any reference to “some embodiments” or “an embodiment” or “teaching” means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment.
  • the appearances of the phrase “in some embodiments” or “teachings” in various places in the specification are not necessarily all referring to the same embodiment.

Abstract

La présente invention concerne un outil d'architecture de système visuel qui utilise des fonctions de système financier représentées sous la forme de blocs de construction ou de blocs de capacité. Les blocs de capacité sont placés à proximité en vue de présenter des éléments d'une solution particulière à une exigence de conception de système. Les blocs de capacité peuvent comprendre des descriptions détaillées des fonctions qui sont accessibles graphiquement et peuvent également comprendre des modules de code pour le prototypage rapide d'une partie ou de la totalité du système qui est conçu.
PCT/US2016/063654 2016-11-22 2016-11-23 Blocs de conception d'architecture de système WO2018097830A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
SG11201903571PA SG11201903571PA (en) 2016-11-22 2016-11-23 System architecture design blocks
US16/349,902 US10866709B2 (en) 2016-11-22 2016-11-23 System architecture design having visual organization of business function blocks

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US29/585,320 USD825941S1 (en) 2016-11-22 2016-11-22 Display stand for visual organization of business function blocks
US29/585,320 2016-11-22

Publications (1)

Publication Number Publication Date
WO2018097830A1 true WO2018097830A1 (fr) 2018-05-31

Family

ID=62195319

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/063654 WO2018097830A1 (fr) 2016-11-22 2016-11-23 Blocs de conception d'architecture de système

Country Status (3)

Country Link
US (1) USD825941S1 (fr)
SG (1) SG11201903571PA (fr)
WO (1) WO2018097830A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
USD872489S1 (en) * 2018-05-23 2020-01-14 Herman Miller, Inc. Workspace divider
USD932655S1 (en) * 2020-01-29 2021-10-05 M. Arthur Gensler, Jr. & Associates, Inc. Partition wall
US11583111B2 (en) * 2020-12-22 2023-02-21 Specialty Store Services, Inc. Portable display stand having multiple configurations
USD980307S1 (en) * 2022-10-08 2023-03-07 Bcool Inc. Shimmer decorative backdrop panel
USD1013215S1 (en) 2023-06-26 2024-01-30 Weiwei Bi Pneumatic plate

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4931783A (en) * 1988-07-26 1990-06-05 Apple Computer, Inc. Method and apparatus for removable menu window
US20030009411A1 (en) * 2001-07-03 2003-01-09 Pranil Ram Interactive grid-based graphical trading system for real time security trading
US20130321340A1 (en) * 2011-02-10 2013-12-05 Samsung Electronics Co., Ltd. Portable device comprising a touch-screen display, and method for controlling same

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US314483A (en) * 1885-03-24 Manufacture of wire-cloth
US1567446A (en) * 1924-11-28 1925-12-29 Mcclure Edward Wire-mesh guard and the like
US3527004A (en) * 1965-11-19 1970-09-08 Jens Ole Sorensen Building board for building house models on a module system
US3592288A (en) * 1968-09-06 1971-07-13 Conwed Corp Acoustical panel for freestanding space divider
US3583466A (en) * 1969-12-17 1971-06-08 Polacoat Inc Adjustable screen frame for rear projection screen or the like
US3908320A (en) * 1974-12-06 1975-09-30 Packard Ind Inc Movable wall partition including shelf or similar object supporting brackets
US4115937A (en) * 1977-01-06 1978-09-26 Loomskill, Inc. Display frame
US4127196A (en) * 1977-06-13 1978-11-28 Melrose Displays, Inc. Adjustable display fixture
US4172334A (en) * 1977-10-05 1979-10-30 Nielsen Eigil K Display and stocking stands
USD256138S (en) * 1978-03-13 1980-07-29 Tesar Ian A Portable exhibit system
USD312282S (en) * 1987-12-07 1990-11-20 Angeles Nursery Toy, Inc. Toy building facade
US5255803A (en) * 1991-04-03 1993-10-26 Hamilton Fixture Company Merchandising system
USD367972S (en) * 1995-04-04 1996-03-19 Bausch & Lomb Incorporated Eyewear products display tray
US6206079B1 (en) * 1998-11-30 2001-03-27 Industrial Noise Control, Inc. Curtain barrier assembly
USD420223S (en) * 1998-12-23 2000-02-08 Landscape Forms, Inc. Wall structure
USD455503S1 (en) * 2001-05-01 2002-04-09 Heltzer Incorporated Panel
US20030197165A1 (en) * 2002-04-19 2003-10-23 Rubbermaid Commercial Products Llc Expandable and contractible barrier
US6701996B1 (en) * 2002-09-12 2004-03-09 Wen-Ling Chen Assembled and convertible decorating assembly
US7210277B2 (en) * 2003-04-30 2007-05-01 Lifetime Products, Inc. Partition system
USD500604S1 (en) * 2003-04-30 2005-01-11 Lifetime Products, Inc. Partition constructed from blow-molded plastic
USD541949S1 (en) * 2005-02-18 2007-05-01 Sicis S.R.L. Modular architectural component
USD646065S1 (en) * 2010-01-25 2011-10-04 Sunex International, Inc. Safety shield
US9187926B2 (en) * 2012-01-03 2015-11-17 L&P Property Management Company Partition assembly
US9271584B1 (en) * 2014-08-29 2016-03-01 Specialty Store Services, Inc. Portable display stand having foldable one-piece vertical support panel that is capable of tool-free assembly and disassembly
US9615678B1 (en) * 2016-02-08 2017-04-11 Streater LLC Multipurpose display fixture

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4931783A (en) * 1988-07-26 1990-06-05 Apple Computer, Inc. Method and apparatus for removable menu window
US20030009411A1 (en) * 2001-07-03 2003-01-09 Pranil Ram Interactive grid-based graphical trading system for real time security trading
US20130321340A1 (en) * 2011-02-10 2013-12-05 Samsung Electronics Co., Ltd. Portable device comprising a touch-screen display, and method for controlling same

Also Published As

Publication number Publication date
USD825941S1 (en) 2018-08-21
SG11201903571PA (en) 2019-05-30

Similar Documents

Publication Publication Date Title
US20220237661A1 (en) Linking a context environment to a context service
US11055692B1 (en) Application integration for contactless payments
US11727452B1 (en) Invoice financing and repayment
US9183480B1 (en) Using temporary data with a magnetic stripe card
CA2819936C (fr) Systeme de paiement securise
US10019698B1 (en) Merchant cash advance payment deferrals
US10419379B2 (en) Systems and methods to program a computing system to process related events via workflows configured using a graphical user interface
US20220076234A1 (en) Transaction identification by comparison of merchant transaction data and context data
US11238426B1 (en) Associating an account with a card
WO2018097830A1 (fr) Blocs de conception d'architecture de système
US11501297B1 (en) Blockchain agnostic token network
US20230410076A1 (en) Embedded card reader security
WO2023129459A1 (fr) Identification de menaces pour la sécurité par le biais d'indices de mesure entrés par l'utilisateur
US10866709B2 (en) System architecture design having visual organization of business function blocks
WO2023183363A1 (fr) Traitement de paiements à l'aide de messages électroniques
US10496973B2 (en) Reprogrammable point-of-sale transaction flows
US11823191B1 (en) Integration for performing actions without additional authorization requests
US11861590B1 (en) Identity verification using payment instrument(s)
US20240112188A1 (en) Integration for performing actions without additional authorization requests
JP2024507067A (ja) 組み込みカード・リーダ・セキュリティ

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16922180

Country of ref document: EP

Kind code of ref document: A1