+

WO2001001300A1 - Systeme de commerce electronique par l'internet - Google Patents

Systeme de commerce electronique par l'internet Download PDF

Info

Publication number
WO2001001300A1
WO2001001300A1 PCT/AU2000/000730 AU0000730W WO0101300A1 WO 2001001300 A1 WO2001001300 A1 WO 2001001300A1 AU 0000730 W AU0000730 W AU 0000730W WO 0101300 A1 WO0101300 A1 WO 0101300A1
Authority
WO
WIPO (PCT)
Prior art keywords
iwn
transaction
property
engine
point
Prior art date
Application number
PCT/AU2000/000730
Other languages
English (en)
Inventor
Daniel Andrew Hilson
Original Assignee
Industry Wide Networks Pty Ltd
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 Industry Wide Networks Pty Ltd filed Critical Industry Wide Networks Pty Ltd
Priority to AU61391/00A priority Critical patent/AU6139100A/en
Publication of WO2001001300A1 publication Critical patent/WO2001001300A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/12—Payment architectures specially adapted for electronic shopping systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems

Definitions

  • the present invention relates to the field of Internet electronic commerce and. in particular, discloses a hyb ⁇ d e- commerce system having increased levels of functionality and operabihty Background of the invention
  • an electronic commerce system compnsing a se ⁇ es of point of sale terminals providing for point of sale information handling of a business, an interconnection network interconnecting the point of sale terminals to a central database facility, a central database facility tor stonng information about each of the businesses for access by the operators of the point ot sale terminals, and a series of service providers interconnected to the central database facility for meeting requests issued by the point of sale terminals
  • the system also comprises a senes of suppliers interconnected to the central database facility for meeting requests issued by the point of sale terminals
  • the suppliers can include at least one of an import/export agent, a warehousing agent or a producer
  • the service providers can include one of a third party information vendor providing information upon request, a financial transaction vendor providing financial transaction autho ⁇ sation upon request, or an order fulfilment vendor providing order fulfilment upon request
  • the point of sale terminals can include local database information and programs which are preferably downloaded on demand from the central database facility
  • the requests are preferably tranmitted in the form of XML documents or the like to and from the central database facility
  • the request implementation structure can be preferably provided by a software development kit applications programming interface
  • the system can also include a series of user mobile data entry devices which interact with the point ot sale terminals in the authonzation of a transaction
  • the mobile data entry device can include one of WAP enabled phones, mobile phones or bluetooth connected devices
  • a separate interaction unit such as a Web Browser for users to interact with the central database facility for the viewing of transaction statistics associated with the system
  • the viewing of transaction statistics preferably can include utilising OLAP facilities on the central database
  • Actions undertaken by the database facility are preferably in the form of workflow steps executed by the facility with the workflow can be spawned by the template structure of the request.
  • an interactive graphical database for interacting with the central database facility
  • multiple centralised database facilities are preferably peered and interact with one another to pertorm functions
  • Fig 2 illustrates the production of workflow in accordance with the first embodiment.
  • Fig 3 illustrates the process of execution of transactions by a merchant/consumer and IWN engine anangement.
  • Fig 4 illustrates an alternative arrangment of an embodiment of the invention.
  • Fig 5 illustrates the va ⁇ ous structures in an embodiment of the invention
  • Fig 6 illustrates the carying out of transactions in accordance with an embodiment of the invention
  • Fig 7 illustrates one software architectural structure ot the IWN engine
  • an interactive system for carrying out business transactions over the Internet in a simplified and automatic manner
  • the transactions can include electronic ordenng and distnbution.
  • proactive interaction such as faxing, e-mail and electronic funds transfer
  • the system allows business clients to maintain their own database and allows dynamic access to accounting procedures and management information systems including EFTPOS transactions
  • Fig 1. there is illustrated schematically the overall operational environment of a first embodiment
  • the first embodiment 1 is denoted the IWN network and includes va ⁇ ous entities interconnected over an Internet environment 2
  • the elements communicate with one another using XML messaging and CORBA (common object request broker)
  • CORBA is a general purpose communication protocol that allows transparent communications over a network That means that the network is invisible to the development programmer m that they program as if the network is not there
  • the object onented communications model is used for application interfaces within IWN engine pnvate processes
  • the IWN server clea ⁇ nghouse 30 requests transaction authorisation from a Payment Engine 36 via a CORBA RPC (remote procedure call)
  • CORBA RPC remote procedure call
  • the architecture allows distnbution of objects over the network Objects can be wntten in one language (say Java) and referenced using another (say C++)
  • a se ⁇ es of java applets and servlets on the web server provide references to objects on other servers through the
  • the local client entities e g 40 can be configured to run Java applets over an Internet browser type environment such as that provided by Microsoft's Internet Explorer or Netscape s Netscape Navigator
  • they may be a permanent Java application, integration into a third party point of sale or accounting package, or a currently hardware ot software device
  • Each of a se ⁇ es ot client side elements 41 - 44, 40, 34, 51 , 52 interact with an IWN engine cleannghouse 30 which operates as a cleannghouse for operations
  • the flexibihtv of the arrangement allows tor there to be a client and server relationship in all cases (even when only one machine it is client and server on the same machine)
  • the client has a reference to the server, but the client knows no difference between the local reference and server, as CORBA encoding allows for the whole system to operate in a transparent manner
  • the IWN engine cleannghouse 30 serves as a XML and CORBA switchboard for the entire system As noted previously, it consists of an message conversion engine 45. workflow repository 46. data object store 48 and a transaction- processing engine 47 The Cleannghouse interacts with all external entities via open protocols such as XML and WML, and internal entities via CORBA CORBA provides a high performance, yet scalable and open infrastructure tor IWN engine components to interoperate Rather than a purely peer-to-peer or purely centralised communications model. IWN engine operates in a hybrid manner
  • the data object store 48 can comp ⁇ se a relational database and OLAP(On line analytical processing) engine suitable for handling dynamic real-time E-commerce transactions and the OLAP of those transactions
  • the XML engine cleannghouse 30 provides a core clearinghouse application which interacts with a se ⁇ es of pe ⁇ pheral applications These include a consumer front end ASP 31. a merchant terminal 32, a merchant partner web frontend 33, an eCommerce brokerage type operation 34, general Internet access 35, a payment engine 36 and a messaging engine 38
  • the merchant terminal can compnse a point of sale (POS) terminal running via a browser 40 for operation by a merchant
  • This terminal can compnse java applets for allowing the terminal to connect to the IWN network by means of a TCP/IP interconnection
  • This component can be deployed to traditional POS developers as a "developers kit" which they can integrate to a greater or lesser degree into their software, to enable their users to connect to the IWN network
  • the POS terminal provides a facility for small to medium sized businesses looking to establish an ecommerce presence In its simplest form, the POS terminal offers a way to clear plastic and cash transactions via the Internet, superseding traditional EFTPOS However. NetPOS also allows Enterprise Resource Planning (ERP) point of sale, accounting, inventory management and order fulfilment to browsers.
  • the system uses the ubiquity of the Internet to cany out transactions
  • the relevant API can be implemented as a Java or VB based software application that uses encrypted Internet communications to exchange XML RPC with XMLMarket application services, with, for example, the IWN engine cleannghouse 30
  • the consumer webfront application service 31 automatically generates an Internet website presence for IWN engine or client's merchants using the information exchanged by devices on the IWN network
  • the website is a virtual representation of the business, autonomously reachable on the Internet Consumers can use the website and make purchases without any kind of prior association with an IWN engine cleannghouse 30 Integration between the POS and website transactions via the IWN engine clearinghouse 30 creates a seamless order entry and fulfilment process
  • the merchant/partner webfront application service provider 33 is provided to deliver the information to users of the IWN network through any (compliant) World Wide Web browser connected to the Internet Apart from cate ⁇ ng to the smallest enterp ⁇ ses.
  • the merchant/partner webfront ASP provides mobility, deployabihty and rapid growth capability to businesses of
  • Substitute Sheets Both the consumer and merchant/partner ASP are designed to enable conversion of the data to any format, so as to enable it to be viewed on ANY device de mobile phone, web TV, PDA. kiosk etc)
  • a brokerage facility 34 links websites together in a virtual community
  • the system enables the products of all merchants in the community to be quened in a consistent manner and provide for consumer dnven quenes which aggregate the data
  • the customer can specify the product and p ⁇ ce desired and the database will query all merchants to match the request Consumers expenence a shopping environment, consistent across all vendors within the IWN exchange system
  • IWN engine Businesses to business functionality enabled by IWN engine also allow merchants to collaborate tor competitive advantage with their major suppliers IWN engine eMall consumers enjoy an overlay or meta-search engine capable of finding products by multiple cnte ⁇ a across multiple vendors This is due to the fact that they are able to query not only the IWN engine held by the local client, but also nodes from all over the world
  • the IWN server cleannghouse contains the business logic (descnbed hereinafter) required to initiate and complete transactions, and can interact with any device which transmits standard message formats such as HTML, WML, XML, IMAP etc and is connected to the Internet It also frees the devices from the requirement to manage multiple connections to multiple parties
  • the IWN network preferably conforms to all relevant RFC and (where applicable) ISO standards
  • IWN engine is designed to mteroperate with the widest vanety of organisations possible To this end.
  • extensible Markup Language. XML. is often used to encapsulate all system-system transactions
  • XML provides a self-desc ⁇ bing document paradigm, these documents are transmitted via HTTP using the XML RPC (XML Remote Procedure Call) standard
  • IWN Engine HTTP application servers uses the Secure Sockets Layer (SSL) protocol to encrypt the data stream SSL provides strong encryption to protect the data in transit Participants in the market are pre-screened (to varying degrees depending on their user group) before admission, and authenticated using a non-propnetary protocol such as the RADIUS protocol Using RADIUS ensures a standards-compliant approach to person-to-business authorisation, and transparently provides the option of using strong cryptographic techniques like challenge-response or one-time password algo ⁇ thms
  • X 509 certification is used to authenticate automated users transactions, which are also SSL encrypted X 509 certificates are now available from a number of autho ⁇ tative sources both internationally and domestically IWN network centralised and distnaded subsystems are protected behind industry standard ICSA
  • IWN network distnaded subsystems are deployed for a given region is dependent on demand, bandwidth availability and commercial agreements From a purely technical perspective, there can be a minimum of one and an arbitra ⁇ ly unlimited number of each of these distnaded processing units This provides for extremely large-scale deployments.
  • the brokerage WebFront 34 provides a meta-layer on top of arbitrary groups of IWN engine merchants
  • An IWN engine brokerage differentiates itself from other web-mall offenngs by -Otfe ⁇ ng consumers a consistent shopping metaphor overlay, visually consistent across vendors This is achieved by overlaying a consumer shopping interface with communicates with any IWN engine compliant merchant
  • the IWN engine shopping experience features a customer service window tailored for shopping Services include gift tokens, lay-buys, recommendations, favounte merchants, and so on
  • the consumer interface travels with users regardless of the vendor entered This consistency builds trust, and thereby consumer confidence
  • a variety ot mall concepts is envisaged with visual, audio and product placement strig ⁇ os tailored to target markets Workflow operations
  • the overall operation of the system can be as follows
  • the network processes the request via its IP address and routes it towards the IWN system
  • the IWN system identifies the request using either "tags" in the messaging format (messaging formats may include XML. WML. HTML), IP address, or the port on which the message was received
  • the IWN engine cleannghouse 30 is directly connected to specific providers that are able to fulfil order requests, third party information vendors able to provide information, and service providers that are able to carry out financial transactions such as credit card transactions or the like 36
  • Also interconnected to the IWN network are suppliers who receive requests for goods, import export agents, warehouse storage facilities and producers Thereby, the IWN Network is designed to handle logistics and inventory management as well as information about business relationships etc
  • the data/object store is mtenogated by at least five different sets of user groups (Using the OLAP interface), including web base users, point of sale (NETPOS) users 3-6. product mediators 20-22 and product producers 23. consumers, and the client (telecommunications company or bank) When it is desired to query the database, an OLAP interface car ⁇ es out a database transaction, returning the results of the query
  • the number of servers 30 can be replicated IWN network can then include a se ⁇ es ot servers and can be thought of as a se ⁇ es of nodes of different sizes
  • These users may be a retail point of sale system, or a larger corporate client
  • the global portion de either the main network or a node situated at a 'client" is differentiated in that all data can be collated and made available through the application server as single source for output in various forms such as HTML, as well as other relevant forms (XML. CMI. WML VRML. SHTML, php. pwp, java objects, etc)
  • the IWN network is regarded as distnaded because clients have relevant and alterable data nodes local to their machines Hence relevant local and global database updating is required
  • the IWN network is dynamic because one local or global alteration might create several internal network related operations
  • the local server receives requests from its local user which will either be on the same machine or though the user's local network The server will then either get the information from its local data store or download it from the IWN server The user is able to simply request certain information and the server checks us cache if its there and returns it or otherwise downloads it from the application server (if available) and return and object representing the data
  • the local components are only relevant to an individual user and or user peer groups and is a subset of the larger client database s Local portions are regarded as local because the portion is local to the user's location
  • Non global information can be independently stored
  • the global portion has the largest subset of information which is ot interest to customers of clients or client peer groups (for example, ⁇ anous on-line web shoppers)
  • the global portion of the IWN network is kept up to date by pe ⁇ odically up loading local information (this is done when needed, for example, after local alteration)
  • the NETPOS data can be implemented having w ⁇ te through capability meaning that when a data update is requested by a NETPOS terminal the data will go straight to the main data source (if available) not just the cache
  • the global portion of the IWN Network also processes information and passes it back to the client, in order to update their local database (again done when needed, for example, after customer alteration) Users access the IWN network using an interface which performs all tasks local to the user
  • the XML engine 46 runs the quenes and return the results to the request source, either the web server or the POS server
  • the client is able to change a va ⁇ able in their inventory management system locally This in turn automatically updates the global portion of the IWN network which automatically alters relevant web page elements
  • An example is a change of price on the local machine which is then reflected on the web site
  • the IWN Network has the functionality to allow point to point real time order fulfilment by facilitating catalogue maintenance (though the inventory system dynamically updating the p ⁇ ce and the availability of the products) and offe ⁇ ng direct connection to a third party order fulfilment client (such as FedEx)
  • a third party order fulfilment client such as FedEx
  • Supplier A may set different terms of payment and delivery for each customer
  • the user interface will communicate this order fulfilment cnte ⁇ a and will establish and maintain relationships with each customer
  • Each user will also have the option of setting automatic re-order points There re-order points can be set to t ⁇ gger the dynamic and
  • IWN network has the capacity to provide summary information about the financial position of a client in real time These reports will be displayed in a number of ways and in accordance with the accounting conventions of the geographical area It will focus particularly in profits by item type and by supplier (which is a client)
  • the IWN network is able to give the various user groups (Merchants, clients, and consumers, etc) information about demographic factors of their customer base
  • OLAP technology enables unlimited number of views of the data, and resultant queries It also allows them to track the habits and preferences of consumers and uses intuitive search mechanisms of the network to build personal relationships with the consumer For example by tracking what a consumer has bought it may suggest other related items or similar items by the same supplier
  • the key aspect here is that the data can be viewed and modified by the user s customer representative
  • An application of this is the ability to transact with the on-line customer via chat and other communication means to give detailed information to the on-line customer This is all done directly from the users local IWN network interface
  • the IWN network will enable a variety of management information quenes to be parsed to the user
  • An advantage is that the user is able to access information in real time and access information for the local database which has been entered globally This includes order fulfilment information, information regarding the use and transactions on-line, and all this in combination with traditional point of sale data
  • the difference is that the information once entered in the local database then periodically updates the global database without any proactive re-ente ⁇ ng of information
  • VPN virtual pnvate network
  • Substitute She sets out a point of sale development tool-kit (SDK) called IWNcom which enables transmission of data from a traditional PC to the IWN network for clearance
  • SDK point of sale development tool-kit
  • the IWN Client SDK (Software Development Kit) is designed to enable third party to integrate their device or applications to take advantage of the IWN network functionality
  • These SDK ' s can be Java constructed and hence can readily be ported to the following devices Windows 95. Windows 98. Linux. Windows 2000. Mac OS. PalmOS. WAP compatible devices. Java Compatible devices. Smart Cards, and Java Cards
  • the fundament concept behind the SDK is that it initiates a common set of network level communications, secunty management, session management, and then transactions over this secure session Transactions may include (but not limited to) 1 Financial transactions, debit and credit
  • the SDK has three layers Communications. Network Secunty. and data transmission
  • the communications layer will typically initiate a network connection , detect status of that connection, and respond to va ⁇ ous events relating the connection
  • the secunty layer will establish the validity of the user, establish the validity of the server .and then establish a secure connection between both parties It may use SLL, DES. TLS. and other encryption and secunty processes and protocols
  • the most complex layer is the data layer, which translates information about the client device, and actions on the client device , into a standard document (usually XML or WML documents) for transmission over the secure network Information in this document may include information regarding a merchant, consumer, device, products, services, p ⁇ ces. geographical, loyalty
  • the client is able to send/receive e-mail using the same interface they use tor point ot sale transactions and all other group one or two functions
  • the client is able to send receive faxes using the same terminal
  • These faxes are sent to the IWN network at which point they are distnubbed to the appropriate recipient
  • Incoming faxes enter the IWN network and are filed using incoming CLI records (d) Accounting
  • Substitute Sheet The client is able to input accounting information and change the p ⁇ ce of any resource be it labour, stock item or other and this information is pe ⁇ odically updated to the IWN network Once in the database it can be selectively used for designated areas of the clients web site
  • the user (e) Customer Relationship Management
  • the user (local NETPOS terminal user) is able to input customer details and these are updated pe ⁇ odically to the global database for later retrieval if necessary
  • the local database can draw a se ⁇ es of summary reports from the global database or selected information can be stored locally Traditionally these queries are refe ⁇ ed to as CRM quenes
  • a user may take the CRM information and organise it in such a manner as to enable business rules which are particular to their organisation In such a case they have facilitated a MIS system
  • Vendors also uniquely gain synergistic connections with other IWN engine vendors T rough IWN engine, vendors can take advantage of shared warehousing and freight facilities, and economies of scale that they would otherwise not enjoy Essentially a vendor can automate their production chain using IWN engine as the glue This can be facilitated in two ways
  • the IWN engine connects to suppliers directly
  • the IWN client uses established B2B infrastructure and relationships to connect to suppliers An example is if a telecommunications company or Banking institution has a B2B system which communicated via EDI to a motor car company IWN engine would simply connect to the m-house application rather than establishing a new connection to the car company
  • the POS interface can be deployed in three distinct configurations A NC Cash Register Svstem 41. standalone NC/PC system 42, and Merchant Partner WebFront ASP 43
  • NC Cash Register System 41 and Standalone NC/PC System 42 can be identical technically, diffenng only in the number of processing units at a customer premises Inventory, p ⁇ cing and other operational data is stored locally Transactions (in both directions) will initially be made using XML, and pe ⁇ odic reconciliation transactions can be performed to ensure convergent views of data at both the clearinghouse and distnaded locations In the case 40 where a Merchant Partner is connected using a web browser rather than a dedicated piece of hardware.
  • the POS view of is deployed as the Merchant/Partner WebFront ASP 33
  • the local data for this vendor can be stored within the Merchant/Partner WebFront ASP 33, however this is completely transparent to both the user and the IWN server cleannghouse
  • the Merchant/Partner WebFront ASP 33 communicates with the IWN server cleannghouse 30 precisely as if it was an NC Cash Register System 41 or Standalone NC/PC system 42 utilising the attached SDK protocol
  • the WebFront provides all required functionality to run the point of sale, inventory, order fulfilment, debtors, and creditors functionality ot a SME merchant/partner Offline contingency capabilities can be provided in the case of dedicated hardware/software
  • a merchant may already be committed to a particular application that cannot interact with XML. and therefore IWN network Reasons for this can include
  • legacy applications 44 can be incorporated into the overall system by deploying a developers kit enabling third parties to develop IWN network extensions to their products creating IWN network Extended Applications dEAs) Such an anangement assists in building a critical mass until XML (or subsequent standards) become a common feature of ERP software
  • Vendor WebFront In an IEA. the functions of the Vendor WebFront are be adapted to the legacy application Inventory, pricing and other operational data can remain stored locally within the application Vendor Webfront transactions (in both directions) are made in (at this stage) XML with the IWN server cleannghouse 30 and periodic reconciliation transactions are performed to ensure convergent views ot data at both central and distnaded locations To the IWN server clearinghouse 30.
  • IWN network Extended Application provides all the required functionality to synchronise the point of sale inventory, order and fulfilment functionality of a merchant/partner Offline contingency capabilities are not provided by IWN network, that is they must be provided natively by the legacy application itself
  • the IWN network solves this problem b ⁇ abstracting the interface to multiple financial institutions and other payment transaction enablers via the Payment Engine 36
  • This subsystem provides a CORBA interface to the IWN server cleannghouse 30 through which all funds transfer, credit autho ⁇ sation. sales transactions and merchant payments and receipts can be processed
  • the Payment Engine 36 connects to the va ⁇ ous financial organisations via the multiple propnetary mechanisms and point to point links, and is able to leverage higher bandwidth connections and better transaction rates due to economies ot scale Financial transactions are simply another form of XML RPC.
  • the IWN engine can talk directly to the resident payment engine as apposed to the financial institutions
  • the IWN Messaging Engine 38 provides the IWN server cleannghouse 30 (again through CORBA) with instant capability to generate a message request to any number ot participants Initially.
  • Email 51 and automated facsimile 52 may be provided Over time, IWN network can introduce further services such as paging, voice synthesis and wireless notification services All notifications can be se ⁇ ahsed and time stamped, allowing a recipient to ve ⁇ fy message authenticity as required Email messages can be digitally signed where financial concerns exist
  • participants will be able to nominate prefe ⁇ ed mechanisms for contact/notification, increasing the convenience level of the system As a result, users will enjoy the convenience ot integrated messaging from a single point
  • CORBA Common Object Request Broker Architecture
  • the IWN server cleannghouse can be a singular entity for a given IWN eXchange, and multiple Exchanges can seamlessly interact using XML RPC The most immediate consequence of this is that inter-market e-fulfilment chains are entirely possible A worldwide chain of IWN exchanges serving country or continental regions can then be constructed, permitting global shopping with local supply
  • the cleannghouse elements include Data/Object store 48
  • the foundation of the IWN server cleannghouse 30 is a large scale relational database management system with an object o ⁇ ented paradigm overlay Consumer and vendor information is stored safely and securely within the Data/Object store 48. and is subject to inherent encryption and access control facilities Database design can accommodate international, multilingual information, incorporate audit trails and implement two-phase commit technology ensu ⁇ ng reliability of transactions Vendors, participating as merchants or partners can maintain their own local data stores These can be bi-directionally synchronised via XML with the Data Object store Because the Data/Object store is relational. IWN network otters deeply flexible reporting and analysis opportunities to participants
  • XML can be the p ⁇ mary messaging service used in the system As such a component which addresses this component is part of the architecture As new standards develop, this engine will be extended to include emerging standards
  • One of the p ⁇ mary benefits of XML is that it provides a common language for structunng documents that flow between business partners in a supply chain Since XML documents share a common structure, the process of transforming documents into new data representations is vastly simplified While XML offers far more flexibility and extensibility than either traditional messaging or EDI.
  • XML by itself does not deliver the level of integration required to implement the IWN network
  • the XML Engine 46 adapts other subsystems to communicate using XML. and insulates them from the processes of encoding and decoding XML It provides the infrastructure to manage the integration process over time, securely and reliably route requests, and translate between messages that conform to different Document Type Definitions (DTDs) It also provides the facilities for
  • the IWN network involves a mesh of information and transaction flows between market participants
  • the business rules for each transaction and participant type are encoded and stored within the Workflow Repository 45, a logical entity implemented on top of the data object store It combines rules, which govern the tasks performed, and coordinates the transfer of the information required to support these tasks
  • Workflow Repository tasks may be physically moved over the network between participants or maintained in the IWN server clearinghouse with the appropnate processes given access to the data at the required times
  • Triggers are implemented in the system to escalate exception conditions in the event ot problems within the system
  • the operation of the workflow is depicted in Fig 2 Data 60 sent to the IWN cleannghouse server, if not already in an XML format is forward to a translator 61 for translation into an XML format 62
  • the XML document is then queued 45 in the workflow repository
  • the workflow repository loops through a process of requesting document objects 64. matching the document against possible types 65, determining what
  • the first object that is requested is a "Profile” that matches the IWN exchange user with a profile This profile is then matched with elements in the data and from this a workflow is spawned This workflow is comprised on a number of unique “actions” that together form a "graph” that define a particular route for each workflow
  • the IWN network employs a standard 3-t ⁇ er client/server application model Server applications can be written as a set of interoperable, modular components using standard computer languages — such as C. C++, and Java The Transaction Processing Engine then runs them in its scalable, high-performance, secure, transactional environment
  • the Transaction Processing Engine 47 logically sequences interactions, using business rules from the Workflow Repository 45 to process transactions from the XML Engine 46. updating the Object/Data Store 47 along the way It ensures that the business transaction is secure and reliable, and is completed with integ ⁇ ty Some ot the capabilities the Transaction Processing Engine bnngs to the IWN Network include - Distnubbed Transaction Management - servers can participate in a distnubbed transaction that involves coordinated updating of multiple databases The Transaction Processing Engine's transaction management helps ensure that all databases are updated properly, or will rollback the databases to their o ⁇ gmal state, assunng that data mtegntv is maintained despite component failures
  • Event Brokerage allows for posting of system or application events that can be subsc ⁇ bed to by any authonzed application component in the system
  • the IWN server cleannghouse handles the following transactions Transaction ve ⁇ fication. Modify web-store information. Push / pull merchant website information. Modify inventory levels. Serving of ASPs. Issue Mime. SSL, Queue messages. Prepare reports. Transmit payment receipt numbers, Send lay-buy information to Netpos, Transmit purchase requests to POS
  • the IWN server clearinghouse deals with the following transaction interactions with the Payment Engine Credit card venfication, Cunency queries. Debit information
  • the IWN server cleannghouse processes information from the Consumer Web-Front ASP This includes sorting of information, building the various websites and payment methods
  • the IWN server cleannghouse assists in the operation of the E-Brokerage ASP in addition to the Consumer ASP in the following manner Provides an access point for a customer. Run intelligent queries. Store customer preferences. Allow dispute resolution, Payment methods
  • the IWN server cleannghouse also allows third-party data interpretation
  • the IWN server cleannghouse must be able to handle Product information
  • a consumer is simply defined as a person or party that initiates a transaction with a vendor or multiple vendors within
  • IWN network Internet consumers use an brokerage or a merchant site created by the IWN Webfront ASP 31 as a user interlace through which transactions are performed
  • IWN Webfront ASP 31 a merchant site created by the IWN Webfront ASP 31
  • consumers can also initiate transactions physically at the customer premises
  • Customers are also able to spawn their own personal IWN customer interface which is customised to their needs and allows them to conduct specified OLAP quenes of the database (see diagram x - peter ask me for the customer details screen)
  • a mediator is a merchant that sells to other merchants They may offer semi-finished goods or components (traditional supplier role), or services that complement or facilitate the production process
  • a freight company, insurance agent graphic designer, vegetable wholesaler or coffee bean supplier may be considered an IWN eXchange product mediator
  • Common mediators include distnbution. warehousing and import/export agents
  • An enabler provides services to consumers, merchants, and mediators by facilitating transactions as opposed to supplying the goods and services that compnse them Other arkets
  • the IWN network is based on the open, scalable, business-to-business standards such as XML Because of this, the IWN network can communicate with any other market or partv that also adopts open standards For example.
  • Microsoft is promoting a technology called "BizTalk", which consists of a set of XML DTDs for business-to-business transactions IWN network is automatically compatible with BizTalk as a result
  • Substitute Shee IWN server cleannghouse evaluates bandwidth availability Time stamp establishes the start time of use Fee is added to user account
  • the POS interface for can be a point of sale hardware device such as the Comm2000 device from Keycorp
  • the configuration at point of sale may include a cash register, customised keyboard and other typical point of sale devices
  • IWN network is based on a client/server computing environment
  • the necessary hardware device required to access the network is a Internet connection to connect to the IWN server cleannghouse server This can be implemented through a third party ISP
  • the software to be interfaced with the IWN network can be a Java client running on a Web browser (Netscape Navigator 3 x Netscape Communicator 4 x. Internet Explorer 3 x)
  • the operating system Windows 9x, Windows NT, Unix. MacOS
  • TCP/IP protocol IP protocol
  • any third party can interact with the system by integrating to it using the IWNCom s development kit as shown in the attached appendix A
  • the data communication protocol required to use the IWN Network can be the standard TCP/IP protocol
  • the type and speed of connections to the Internet will be va ⁇ ed amongst the different users and does not impact the design of the system
  • the POS device provides a direct translation into XML Initially, the POS device opens a TCP/IP connection with the
  • the credit or debit card data is then sent to the server
  • the process firstly involves the negotiation of connection and session's with the IWN engine
  • the process involved is slightly different for Credit and Debit
  • the steps include
  • Substitute Sheet 1 Merchant prompted to swipe card either by the third party software (such as Quicken or MYOB) or by the IWN client side component directly
  • IWN Client side Component collects the credit information converts it to AS2805 compliant XML data, and sends it to the server
  • the collection of information can also include (not limited to) product information , merchant information, and information about the terminal
  • product information is extrapolated from a local data store using either supplied APIs or via customised integration Alternatively the product information can be sent as a batch file at pre-determined intervals
  • the server sends a response back to the client side component which leads to receipt p ⁇ ntmg and other related retail business requirements
  • the debit solution may include more traditional pin key encryption devices (such as the Com2000 device from
  • the PIN number is encrypted with 3DES encryption and set back to the computer via an ECR Message
  • the message is either received by the third party application or the IWN client side component
  • the 3DES encrypted message is then sent to the IWN server along with other XML information regarding the transaction including (but not limited to) Product, customer, merchant, and terminal information
  • the IWN Server passes the PIN to the Acquinng institution (potentially via an internal gateway first) and then through to the issuing bank, the issuing bank then returns a response as to the funds available
  • An alternative method can compnse the following steps 1 Mercant Swipes card in POS terminal
  • Substitute Sheet It is also important to identify that information is only stored in the IWN server once the transaction has been approved (besides fault logging and invalid transaction logs)
  • the debit transaction can be extended to other anangements which utilise non traditional Point of Sale Hardware
  • debit card transactions can be conducted over a mobile phone interface using a WAP enabled phone having Key PIN encryption
  • the process, as illustrated in Fig 3 can proceed as follows
  • IWN Engine sends encrypted PIN to Acquirer Gateway 78 and Sends Merchant ID to the IWN Engine.
  • the system can operate to include consumer initiated transactions over WAP This can comprise the steps of
  • IWN Engine sends encrypted PIN to Acquirer Gateway 78 and Sends Merchant ID to the IWN Engine
  • the system can operate to include merchant and consumer initiated transactions a Bluetooth network
  • a Bluetooth network For example, where the merchant has a blue tooth interface and the user has a Bluetooth enabled phone with a Key PIN encryption device, the process for executing a sale can compnse 1 Sale completed
  • IWN Engine sends encrypted PIN to Acquirer Gateway and Sends Merchant ID to the IWN Engine
  • the transaction can be as follows 1 Sale completed
  • IWN Engine sends encrypted PIN to Acquirer Gateway and Sends Merchant ID to the IWN Engine
  • GUI Graphical User Interface
  • each transaction can be stored in the data/object store
  • a complete overview of each independent IWN Engine system can be made available from a GUI administration window
  • the views provided preferably include
  • the data in the data/object store repository can be quened using OLAP techniques (online analytical processing).
  • OLAP Relational Online Analytical Processing
  • MOLAP Multi-dimensional on-line analytical processing
  • OLAP Online analytical processing
  • OLAP uses a multi-dimensional data base where each data element is stored as a highly discrete piece of information OLAP can find the intersection of two to "n" relationships between the data
  • the IWN architecture uses the following techniques to extract information from the data-store 1 Any device or access point either compatible with or understood by the IWN engine (in terms of data and network compatibility) sends a query to the associated server (le WAP server. HTTP server) or connects directly to the IWN engine
  • Substitute Sheet 4 This spawns a connection to the IWN Servlet Engine which launches a servlet to mange the query
  • the servlet then sends all queries to the Workflow Repository Manager that protects the IWN data-stores from external tampenng
  • the Workflow Repository Manager connects to the data base and returns all relevant information to the Servlet 7
  • the Servlet then returns the response to the Engine and the transaction is processed and sent back to the appropriate device
  • the OLAP architecture is novel in that it deals with ubiquitous devices and multiple queries from any ot. but not limited to. the following Web Browsers. WAP Devices. WebTV Devices, Java enabled devices (le that can run a JVM), Kiosks. ATM's (Automated Teller Machines)
  • the OLAP architecture can be designed to accept queries from any device (Sending valid requests) and return response to that said device (using valid responses)
  • This process can be enabled via a secure socket connection between the engines and the ability for a OLAP query on one engine to access a business rule to query another engine/s and the IP address of the other engine/s Much like a search engine, the Servlet technology then opens a session with the foreign engine and awaits the complete query of all local and foreign engines before returning the response to the user
  • vanous modified embodiments and alternative representations are possible
  • Va ⁇ ous interactive devices for example shop front point of sale terminals 80, Internet device 81.
  • PDAs 84 and Web TV devices 85 are each equipped with an Sdk to convert transactions into an XML document in accordance with associated document type definitions
  • the XML documents are sent to the XML engine 86 for action and storage
  • the XML engine in turn provides a senes of modules for interaction with the data store These include an OLAP module 87. logistics module 88, client billing system 89.
  • the IWN engine 86 can be paired with other engines 94 and undertake other transactions with legacy applications and other internet system 95
  • Fig 5 illustrates an alternative architectual anangement
  • Fig 6 illustrates the processing of a transaction in accordance with the aforementioned p ⁇ nciples
  • Fig 7 illustrating an alternative view of the architecture of the IWN Engine
  • ENTITY ⁇ wn_elements login” > ENTITY logm_elements (request
  • IWN Users can login either by their email address or their IWNUserlD. example :
  • ⁇ -- ⁇ purchase> contains either ⁇ request> or ⁇ response> --> ⁇ i ENTITY % purchase_elements "request j response"
  • ⁇ ' -- ⁇ request> must contain ⁇ authent ⁇ cat ⁇ on> , and either purchase reversal children or purchase request children --> ⁇ !ELEMENT request (authentication, ( ( %purchasereversal_elements ; )
  • ⁇ cl ⁇ ent> specifies the customers IP address.
  • ⁇ server> indicates the IP address of the web server serving the request.
  • IP/FQDN are both valid.
  • Valid Types address, pos (point of sale)
  • lwnuser id may be looked up using the card number for other projects such as loyatly.
  • --> ⁇ payment> ⁇ card> ⁇ name>Card N. Holder ⁇ /name> ⁇ number>456400000000 ⁇ /number> month can be the following. 01, 02, ... , 11, 12 1, 2, ... , 11, 12 January, February, ... , November, December Jan, Feb, . , Nov, Dec year can be the following: 00, 01, . , 98, 99 (+2000) 2000, 2001, ... , 2998, 2999
  • ⁇ wnuser> can be used to lookup the credit details via the IWNUserlD or email
  • ⁇ ' -- cost tags are optional withm ⁇ quant ⁇ ty/> tags.
  • Cost names are arbitrary.
  • Costs withm the ⁇ quant ⁇ ty> tag refer to each unit, not to the group of products.
  • Cost tags here are also optional. Cost tags inside ⁇ product> refer to the pricing of the entire
  • This value is the actual value that will be passed to the financial switch for credit/debit.
  • SessionlD Property (Session Object) 55
  • CurrencvTvpe Property (Transaction Object) 64
  • SessionlD Property (Transaction Object) 69
  • This document is provided to assist a developer in utilising the IWN Transaction SDK in the development of a client application that is to perform transactions using the IWN Transaction System.
  • the IWN Transaction SDK consists of an ActiveX EXE containing several classes that are used to collect, format, verify and send transactions to the IWN Transaction System, and receive, parse and provide the results of those transactions to a calling application.
  • the IWN Transaction Classes communicate with the IWN Server over TCP/IP using specially formatted documents for transferring information.
  • Each Transaction type may perform any number of Transactions with the IWN Server.
  • For a Transaction the flow of information is as follows:
  • a TCP/IP Connection is established between the Client and the rWN Server.
  • the Client sends a Request Document to the IWN Server.
  • the IWN Server sends a Response Document to the Client.
  • the IWN Transaction Systems utilises Session management to provide tracking, reconciliation and to ensure the integrity of Transactions.
  • a Client When a Client creates an instance of the Session Object, it can call the Logon method which will request a Session from the IWN Server. Once the IWN Server has issued the Client with a valid Session, the Client can use that Session to send Transactions.
  • a Client uses the Merchant Details provided to identify and authorize itself to the IWN Server.
  • This section refers to code in the iwnEx ⁇ mple Visual Basic project distributed with the iwn component.
  • Substitute Sh The calling application will typically create an PNN session object when it loads or initialises.
  • the calling application may then ensure it has contact with the IWN engine and call the Session objects Login method, passing the Merchants Username and password.
  • the Login method should return true or false and set an error depending on whether the Login was successful.
  • the application may wish to rectify any problems and try the login again should the login have failed.
  • the calling application would execute the Session objects Transaction collections Add method, which will return a valid transaction object.
  • the Add method is called, the IWN transaction server is contacted for a valid transaction number to use. If this failed, then the Add method will return null.
  • the calling application should check the validity of the Transaction object returned by the Add method before it attempts to use it.
  • the calling application When it has obtained a valid transaction object, the calling application must then set the following properties of that transaction, before the transaction can be committed: o CardExpiryMonth o CardExpiryYear o CardName o CardNumber o Currency Type
  • the calling application can then create Product objects within the Transaction object to represent the difference products, prices and quantities for the transaction.
  • the calling application can then create Product objects within the Transaction object to represent the difference products, prices and quantities for the transaction.
  • Substitute Sheet application can add a Product object to the Transaction by calling the Transactions objects Products collection Add method.
  • the Add method will return Product object, whose properties can be set to indicate the desired product, quantity and unit cost.
  • the calling application can repeat this step to add any number of products to the transaction before it is commited.
  • the calling application can adjust the amount for the transaction by setting the Transaction objects Amount property. This allows for adjustments such as discounts, part payments or credits. If there are no products added, the calling application must explicitly set the Transaction objects Amount property or the Transaction will have the default value of 0.
  • the calling application When the calling application wishes to commit the transaction, it can simple call the Transaction objects Send method, which will send the transaction to the IWN engine, and return True if successful or False if the transaction failed.
  • the rWN Transaction Server The rWN Transaction Server.
  • the calling application in which objects of the IWN Transaction Classes are created.
  • a single network transaction Indication the sending of data to the IWN Server and the receipt of information from the IWN Server. This DOES NOT indicate a financial transaction.
  • a transaction is considered complete when a valid Request Document has been sent to the Server and a valid Response Document has been received from the IWN Server
  • the rvVN Transaction Classes use a special message format for transferring information between a Client and the ⁇ VN Server. As in a Transaction, a document is sent and a document is received. A document transferred FROM the Client TO the TvVN Server is a Request Document.
  • the Response Document is sent FROM the IWN Server TO the client after the server has received and processed a valid Request Document.
  • a Purchase is a type of credit transaction. Within the scope of the IWN Transaction SDK it is considered a virtual transaction. A Purchase may constitute several Transactions, depending on the requirements of the Purchase. (See Transaction)
  • a Reversal is a type of credit transaction. (See Purchase) Session
  • a single session object is created, it's parameters are set and the login method is called. Once a successful login has occurred the session object can be used to create transaction objects. Transaction objects cannot (read should not) be created if there is no current valid session, or if the session object is not connected to a valid session.
  • the Transactions Collection object exists within the session object and holds all the Transaction objects that have been created within the session.
  • the Transactions Collection object can be enumerated in For Each statements to retrieve each Transaction object in sequence.
  • a Transaction Object is created within the Transactions Collection object when there is a valid session present in the Session object.
  • a Transaction object is created, its properties set, and the send method is called. Transactions will exist until explicitly killed or until as session has ended.
  • the Products Collection object exists within a Transaction object and holds all the Product objects that have been created within the transaction.
  • the Products Collection object can be enumerated in For Each statements to retrieve each Product object in sequence.
  • a Product Object is created within the Products Collection object in a valid Transaction Object.
  • a Product object is created, its properties set. The product details are issued with the Transaction when the parent Transaction object is committed.
  • Substitute Sheet MerchantlD Property (Session Object, Transaction Object, Product Object)
  • the MerchantlD property contains the Merchant ID for the Session, Transaction or Product.
  • the MerchantlD property can be set before an active session. Unless explicitly set, MerchantlD' s for Transaction and Product objects will assume the value of MerchantlD in the Session object.
  • the Route property is used to specify a gateway IP address to use when sending transactions.
  • the Route property will modify the system routing table by adding a static route to the IP address or hostname specified by the ServerAddress property via the IP address specified in the Route property.
  • the Route property can be set any number of times during the life of an active session and the next Transaction to be commited will use the route specified.
  • the routing table will not be modified but the Route property will retain the IP address given.
  • the Route property will retain the IP address given.
  • This code will add a route to the system routing table specifying that all traffic for iwnengine.indwide.net should go through the interface 192.168.0.10 With objSession
  • Substitute Sheet ServerAddress Property (Session Object)
  • the ServerAddress property specifies the address of the IWN engine server that the Session should communicate with.
  • the ServerAddress property is required before the Session objects Login method can be called.
  • the ServerAddress property can (read should) only be set once before the session is validated. Setting this property during a valid session will not (read should not) take effect until the Session is terminated and a new Session is created.
  • Substitute Sheet ServerPort Property (Session Object)
  • the SessionlD property containts the Session ID for the active session.
  • the SessionlD property is automatically assigned a value when a session is created by executing the Login method. Functionality has been provided to set the SessionlD property of a Session object to support the future ability to resume sessions between invocations of the Session object. This functionality is not currently available and setting the SessionlD before or after a session login will not (read should not) affect any transactions that are committed within the scope of the session.
  • the TerminallD property contains the TerminallD for the session.
  • the TerminallD is required before a valid session can be obtained.
  • the Transactions Property returns a single Transaction object or a Transactions collection object.
  • a Session object objTr ⁇ ns ⁇ ctions
  • the Amount property contains the amount for the transaction.
  • the amount property is represented in base units of currency.
  • the amount property represents the amount for the transaction. This must be set by the application if the amount for the transaction is different than the amount calculated as the total of the associated product objects.
  • the Amount property will (read should) default to the total of the associated product objects when the transaction is commited.
  • the CardExpiryMonth property represents the 2 digit expiry month of the credit card specified by the CardNumber property.
  • the CardExpiryMonth Property accepts and Integer in the range 1 - 12 representing the 2 digit month of the expiry date on a credit card. If the value given when setting the CardExpiryMonth property is outside this range, then the property defaults back to 0 and the transaction will return an error indicating an invalid expiry date when an attempt is made to commit the transaction.
  • CardExpiryYear 0 End With See Also CardExpiryYear Property
  • the CardExpiryYear property represents the 2 digit expiry year of the credit card specified by the CardNumber property.
  • the CardExpiryYear Property accepts a year value as an integer in both 2 and 4 digit format. If the specified Integer is between 0 and 99 it is assumed that this represents a 2 digit date between the year 2000 and 2099. If the specified Integer is between 2000 and 2099 it is assumed that this represents a 4 digit date between the year 2000 and the year 2099.
  • the CardName property contains the full name of the card holder of the credit card specified in the CardNumber property.
  • the CardNumber property contains the card number of the credit card that is referenced by the transaction.
  • the CardNumber property is required before a transaction can be committed.
  • This example represents setting the credit card details for a transaction object.
  • the card details shown here would be from a card belonging to John Citizen with a number of 4502 0000 0000 0000 that expires on January 2000.
  • objTransaction With objTransaction
  • the Code property returns the response code received from the IWN Engine after a Transaction has been committed.
  • the CurrencyType property contains the the Currency type of the amount specified in the Amount property.
  • the value contained in the CurrencyType property represents a value from the iwnCurrencyType enumerator.
  • the Description property returns the description property received from the IWN engine after a transaction has been committed.
  • the Products property returns a single Product object or a Products collection object.
  • the following example would retrieve the Product object for a product with a product id of 131001 from the Products collection in the Transaction object.
  • the following example would iterate through all the products in the Transaction objects Products collection and display the Product objects ProductlD property.
  • Substitute Sheet RRN Property (Transaction Object)
  • the RRN property returns the receipt number of the response received from the r N engine after a transaction has been committed.
  • the SessionlD property returns the Session ID of the parent session under which the Transaction was created.
  • SessionlD Property (Session Object)
  • the SystemTrace property returns the system trace code of the response received from the IWN engine after a transaction has been committed.
  • the TransactionlD property returns the transaction id of the transaction object.
  • the TransactionlD property is automatically assigned by the IWN engine through the Session object when the Transaction object is created. After the transaction has been created, the transaction id cannot be changed.
  • the Item property is the default property of the Transactions object.
  • the Item property is the default property of the Products object.
  • the Login method contacts the IWN engine and requests a session in which to transfer transactions.
  • Email address also referred to as usemame. Password
  • the Login method contacts the IWN engine, requests a session and retrieves a session id. If the Login method is successful, the Login method will return True. If the Login method cannot obtain a session id for any reason it will return False and set an error.
  • SessionlD Property (Session Object)
  • the Logout method closes a session created by the Login method and clears any stored session information.
  • the Logout method will close a open session and clears all session related data.
  • Substitute Sheet Add Method (Transactions Collection Object) Adds a Transaction object to a transactions collection.
  • the Add method contacts the FNN server for a valid transaction id. If the Add method can obtain a valid transaction id, then it will return a valid Transaction object.
  • the Send method queues a transaction for sending to the IWN engine. If the Send method was able to successfully que the transaction, it will return True. If the Send method is unable to queue a transaction, it will return False and set an error.
  • the Send method is asynchronous, a return value of True does not indicate that the transaction was sent successfully, it only means that the transaction was successfully queued.
  • the Send method will raise the Response event in its parent Session object, indicating whether the transaction was successfully sent. If the Send method successfully transmits the transaction to the IWN engine and receives a valid response, it will set the values of the Code, Description and SystemTrace properties to those received in the response.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention concerne un système de commerce électronique comprenant: une série de terminaux de point de vente assurant le traitement des informations de point de vente d'une affaire; un réseau d'interconnexion interconnectant les terminaux de points de ventes à une installation de base de données centrale; une installation de base de données centrale permettant de conserver les informations concernant chacune des affaires auxquelles pourront accéder les opérateurs des terminaux de points de vente; et une série de fournisseurs de services interconnectés à l'installation de base de données centrale de façon à satisfaire les demandes émises par les terminaux de points de vente.
PCT/AU2000/000730 1999-06-28 2000-06-28 Systeme de commerce electronique par l'internet WO2001001300A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU61391/00A AU6139100A (en) 1999-06-28 2000-06-28 An internet e-commerce system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
AUPQ1235A AUPQ123599A0 (en) 1999-06-28 1999-06-28 An internet e-commerce system
AUPQ1235 1999-06-28

Publications (1)

Publication Number Publication Date
WO2001001300A1 true WO2001001300A1 (fr) 2001-01-04

Family

ID=3815424

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/AU2000/000730 WO2001001300A1 (fr) 1999-06-28 2000-06-28 Systeme de commerce electronique par l'internet

Country Status (2)

Country Link
AU (1) AUPQ123599A0 (fr)
WO (1) WO2001001300A1 (fr)

Cited By (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1229506A1 (fr) * 2001-01-24 2002-08-07 Ncr International Inc. Terminal libre-service
EP1237350A1 (fr) * 2001-02-20 2002-09-04 Siemens Aktiengesellschaft Procédé et système de tenue de compte pour le réglement de services fournis dans un réseau de télécommunications
WO2003003269A1 (fr) * 2001-06-29 2003-01-09 Anoto Ab Systeme et procede pour commerce electronique a partir de dispositifs informatiques portables
WO2003015043A1 (fr) * 2001-08-03 2003-02-20 Haltfern Limited Systeme de securite de carte de credit
WO2002082311A3 (fr) * 2001-04-09 2003-08-21 Liberty Integration Software I Procede et appareil pour serveur pilote par langage de balisage de documents
EP1353472A1 (fr) * 2002-04-08 2003-10-15 Hitachi, Ltd. Dispositif et système de communication
US6785685B2 (en) 2001-08-22 2004-08-31 International Business Machines Corporation Approach for transforming XML document to and from data objects in an object oriented framework for content management applications
WO2006135940A1 (fr) * 2005-06-15 2006-12-21 Milan Prokin Systeme de gestion de distribution securisee
JP2009505233A (ja) * 2005-08-09 2009-02-05 カーディナル コマース コーポレーション 支払処理のため加盟店契約会社に認証データの転送を支援するウェブ端末及びブリッジ
US7590980B1 (en) 2004-06-14 2009-09-15 Convergys Cmg Utah, Inc. System and method for a functional extensibility framework
US7668093B1 (en) 2004-08-05 2010-02-23 Convergys Information Management Group, Inc. Architecture for balancing workload
US7987492B2 (en) 2000-03-09 2011-07-26 Gad Liwerant Sharing a streaming video
US8489742B2 (en) 2002-10-10 2013-07-16 Convergys Information Management Group, Inc. System and method for work management
US8577795B2 (en) 2002-10-10 2013-11-05 Convergys Information Management Group, Inc. System and method for revenue and authorization management
US8793194B2 (en) 2002-02-28 2014-07-29 Hohyung Lee Direct distribution system for consumer goods and services
WO2018125808A1 (fr) * 2016-12-31 2018-07-05 Square, Inc. Acquisition et traitement d'objets de données partielles
US10102513B2 (en) 2014-07-31 2018-10-16 Walmart Apollo, Llc Integrated online and in-store shopping experience
US10225584B2 (en) 1999-08-03 2019-03-05 Videoshare Llc Systems and methods for sharing video with advertisements over a network
US10255464B2 (en) 2017-01-31 2019-04-09 Square, Inc. Systems and methods for determining clock rates for communicating with processing devices
US10318952B1 (en) 2015-05-23 2019-06-11 Square, Inc. NFC base station and passive transmitter device
US10380389B1 (en) 2015-12-11 2019-08-13 Square, Inc. Reading payment object upon detection of reader readiness
US10438189B2 (en) 2017-02-22 2019-10-08 Square, Inc. Server-enabled chip card interface tamper detection
US10621590B2 (en) 2017-02-22 2020-04-14 Square, Inc. Line-based chip card tamper detection

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1995031789A1 (fr) * 1994-05-11 1995-11-23 Visa International Service Association Systeme de commande automatise pour achats
WO1997009816A1 (fr) * 1995-09-07 1997-03-13 Wireless Transactions Corporation Reseau de traitement de transactions dans le reseau telephonique commute public (rtpc) mettant en oeuvre un concentrateur/unite de commande sans fil
WO1997049072A2 (fr) * 1996-06-17 1997-12-24 Verifone, Inc. Systeme, procede et article destines au traitement d'une pluralite de transactions a partir d'une architecture multicanaux, extensible, flexible a un seul point de declenchement
WO1999008218A1 (fr) * 1997-08-11 1999-02-18 Trivnet Ltd. Procede permettant des activites de detail sur un reseau longue distance
WO1999028830A1 (fr) * 1997-12-02 1999-06-10 Korman Bruce R Architecture de reseau multitransactionnelle

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1995031789A1 (fr) * 1994-05-11 1995-11-23 Visa International Service Association Systeme de commande automatise pour achats
WO1997009816A1 (fr) * 1995-09-07 1997-03-13 Wireless Transactions Corporation Reseau de traitement de transactions dans le reseau telephonique commute public (rtpc) mettant en oeuvre un concentrateur/unite de commande sans fil
WO1997049072A2 (fr) * 1996-06-17 1997-12-24 Verifone, Inc. Systeme, procede et article destines au traitement d'une pluralite de transactions a partir d'une architecture multicanaux, extensible, flexible a un seul point de declenchement
WO1999008218A1 (fr) * 1997-08-11 1999-02-18 Trivnet Ltd. Procede permettant des activites de detail sur un reseau longue distance
WO1999028830A1 (fr) * 1997-12-02 1999-06-10 Korman Bruce R Architecture de reseau multitransactionnelle

Cited By (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10362341B2 (en) 1999-08-03 2019-07-23 Videoshare, Llc Systems and methods for sharing video with advertisements over a network
US10225584B2 (en) 1999-08-03 2019-03-05 Videoshare Llc Systems and methods for sharing video with advertisements over a network
US7987492B2 (en) 2000-03-09 2011-07-26 Gad Liwerant Sharing a streaming video
US10277654B2 (en) 2000-03-09 2019-04-30 Videoshare, Llc Sharing a streaming video
US10523729B2 (en) 2000-03-09 2019-12-31 Videoshare, Llc Sharing a streaming video
EP1229506A1 (fr) * 2001-01-24 2002-08-07 Ncr International Inc. Terminal libre-service
US7711643B2 (en) 2001-01-24 2010-05-04 Ncr Corporation Self-service terminal
EP1237350A1 (fr) * 2001-02-20 2002-09-04 Siemens Aktiengesellschaft Procédé et système de tenue de compte pour le réglement de services fournis dans un réseau de télécommunications
WO2002082311A3 (fr) * 2001-04-09 2003-08-21 Liberty Integration Software I Procede et appareil pour serveur pilote par langage de balisage de documents
WO2003003269A1 (fr) * 2001-06-29 2003-01-09 Anoto Ab Systeme et procede pour commerce electronique a partir de dispositifs informatiques portables
WO2003015043A1 (fr) * 2001-08-03 2003-02-20 Haltfern Limited Systeme de securite de carte de credit
US6785685B2 (en) 2001-08-22 2004-08-31 International Business Machines Corporation Approach for transforming XML document to and from data objects in an object oriented framework for content management applications
US8793194B2 (en) 2002-02-28 2014-07-29 Hohyung Lee Direct distribution system for consumer goods and services
US7168043B2 (en) 2002-04-08 2007-01-23 Hitachi, Ltd. Apparatus and system for communication
EP1353472A1 (fr) * 2002-04-08 2003-10-15 Hitachi, Ltd. Dispositif et système de communication
US10360563B1 (en) 2002-10-10 2019-07-23 Netcracker Technology Solutions LLC Architecture for a system and method for work and revenue management
US8577795B2 (en) 2002-10-10 2013-11-05 Convergys Information Management Group, Inc. System and method for revenue and authorization management
US8918506B1 (en) 2002-10-10 2014-12-23 NetCracker Technology Solutions Inc. Architecture for a system and method for work and revenue management
US8489742B2 (en) 2002-10-10 2013-07-16 Convergys Information Management Group, Inc. System and method for work management
US7590980B1 (en) 2004-06-14 2009-09-15 Convergys Cmg Utah, Inc. System and method for a functional extensibility framework
US7668093B1 (en) 2004-08-05 2010-02-23 Convergys Information Management Group, Inc. Architecture for balancing workload
WO2006135940A1 (fr) * 2005-06-15 2006-12-21 Milan Prokin Systeme de gestion de distribution securisee
JP2009505233A (ja) * 2005-08-09 2009-02-05 カーディナル コマース コーポレーション 支払処理のため加盟店契約会社に認証データの転送を支援するウェブ端末及びブリッジ
US10956886B2 (en) 2014-07-31 2021-03-23 Walmart Apollo, Llc Integrated online and in-store shopping experience
US10102513B2 (en) 2014-07-31 2018-10-16 Walmart Apollo, Llc Integrated online and in-store shopping experience
US10318952B1 (en) 2015-05-23 2019-06-11 Square, Inc. NFC base station and passive transmitter device
US10380389B1 (en) 2015-12-11 2019-08-13 Square, Inc. Reading payment object upon detection of reader readiness
WO2018125808A1 (fr) * 2016-12-31 2018-07-05 Square, Inc. Acquisition et traitement d'objets de données partielles
US10402816B2 (en) 2016-12-31 2019-09-03 Square, Inc. Partial data object acquisition and processing
US10970708B2 (en) 2016-12-31 2021-04-06 Square, Inc. Predictive data object acquisition and processing
US10255464B2 (en) 2017-01-31 2019-04-09 Square, Inc. Systems and methods for determining clock rates for communicating with processing devices
US10438189B2 (en) 2017-02-22 2019-10-08 Square, Inc. Server-enabled chip card interface tamper detection
US10621590B2 (en) 2017-02-22 2020-04-14 Square, Inc. Line-based chip card tamper detection
US11113698B2 (en) 2017-02-22 2021-09-07 Square, Inc. Line-based chip card tamper detection
US11669842B2 (en) 2017-02-22 2023-06-06 Block, Inc. Transaction chip incorporating a contact interface
US12223507B2 (en) 2017-02-22 2025-02-11 Block, Inc. Line-based chip card tamper detection

Also Published As

Publication number Publication date
AUPQ123599A0 (en) 1999-07-22

Similar Documents

Publication Publication Date Title
WO2001001300A1 (fr) Systeme de commerce electronique par l'internet
US7533050B2 (en) Integration of computer applications and e-business capability
US7415715B2 (en) Transaction execution system interface and enterprise system architecture thereof
US6934532B2 (en) Communication systems, components, and methods operative with programmable wireless devices
US7831693B2 (en) Structured methodology and design patterns for web services
US8346929B1 (en) System and method for generating secure Web service architectures using a Web Services security assessment methodology
US8069435B1 (en) System and method for integration of web services
US20020178087A1 (en) Internet-based instant messaging hybrid peer-to-peer distributed electronic commerce system and method
US20030229590A1 (en) Global integrated payment system
AU2001241977B2 (en) Multifunctional mobile banking system
US20020069123A1 (en) Electronic commerce system
Huang et al. BulaPay: a novel web service based third-party payment system for e-commerce
AU2001241977A1 (en) Multifunctional mobile banking system
US20120253976A1 (en) Half-Graphical User Interface Order Processing Method and Web Service
Fonseca et al. Future of Wholesale Banking: The Portal
Succi et al. Supporting electronic commerce of software products through pay-per-use rental of downloadable tools
Data Extending Your SOA and Internal Applications Utilizing Commercial Web Services
KR20090032069A (ko) 실물상품 선이자 지급을 통한 예금(또는 적금)계좌 운용 시스템

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWE Wipo information: entry into national phase

Ref document number: 10019379

Country of ref document: US

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载