WO2002007407A1 - Interface utilisateur pour applications en réseau - Google Patents

Interface utilisateur pour applications en réseau Download PDF

Info

Publication number
WO2002007407A1
WO2002007407A1 PCT/EP2000/006828 EP0006828W WO0207407A1 WO 2002007407 A1 WO2002007407 A1 WO 2002007407A1 EP 0006828 W EP0006828 W EP 0006828W WO 0207407 A1 WO0207407 A1 WO 0207407A1
Authority
WO
WIPO (PCT)
Prior art keywords
provider
end user
user device
request
eud
Prior art date
Application number
PCT/EP2000/006828
Other languages
English (en)
Inventor
Holger Roost-Macias
Siegfried Wilhelm
Original Assignee
Tresor Tv Produktions Gmbh
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 Tresor Tv Produktions Gmbh filed Critical Tresor Tv Produktions Gmbh
Priority to PCT/EP2000/006828 priority Critical patent/WO2002007407A1/fr
Priority to AU2000259854A priority patent/AU2000259854A1/en
Publication of WO2002007407A1 publication Critical patent/WO2002007407A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/30—Managing network names, e.g. use of aliases or nicknames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/30—Managing network names, e.g. use of aliases or nicknames
    • H04L61/301—Name conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/563—Data redirection of data network streams
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/75—Indicating network or usage conditions on the user display
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • the present invention relates to data communication in a network and, in particular, to the routing of requests from end user devices to providers in a network.
  • any product and/or service can be acquired via the Internet, including any kind of manufactured products (e. g. clothes, cars, books, ...), information services (e. g. stock exchange information), financial/economic services (e. g. telebanking, travel services ...) / and the like.
  • manufactured products e. g. clothes, cars, books, ...)
  • information services e. g. stock exchange information
  • financial/economic services e. g. telebanking, travel services ...) / and the like.
  • the overall network security demands include the confidentiality between end users and providers, the integrity of data communicated over the network, the unsurveillancability, liability and undeniability of transactions related to products/services provided and requested via the network, the accountability of end users and providers with respect to data communicated therebetween, and the anonymity of end users and providers as well as of product/service related transactions with respect to third parties.
  • end users For end users requesting/ordering products/services via a network, the end user devices and the end user software must be simple to use. Further, end users are interested in utilizing existing totalization (payment) methods/instruments providing an established financial transaction security standard such as bank account transfers and credit card based payments. Therefore, personal and private end user data, product/service request data and additional data requested/necessary for accomplishing a product/ service request must be protected with respect to unauthorized network users. Moreover, it is essential that product/service requests from end users result in a legally binding relationship with the respective providers such that requested providers are legally enforced to fulfill end users requests.
  • payment totalization
  • the network security demands of providers include the protection of end user and provider data as well as request/transaction data, a legally binding relation between requesting end users and requested providers resulting from end user requests and/or product/service offers of providers, and the like.
  • product/service providers are interested in immediate billing procedures related to requested products/services and minimized costs for offering, providing products/services, fulfilling end user inquiries and related transaction costs.
  • an end user operates his/her end user device to establish a network communication link to a specific provider of desired products/services.
  • the requested provider communicates product/service specific data to the end user device and, for ordering a product/services, requests end user specific data (e. g. name, credit card number, shipping address etc.) from the end user. Therefore, at least a part of end user specific sensitive confidential data has to be communicated over the network for each product/service order while such communicated data is insufficiently protected from abuse by unauthorized third parties, even using encryption techniques.
  • end user specific data e. g. name, credit card number, shipping address etc.
  • a further problem of the above conventional approach is that end users must know providers of the desired products/services and how to contact them.
  • end user devices used for contacting a provider are personal computers which are complicated to be operated, especially for inexperienced end users.
  • the complexity of such end user devices can lead to undesired, unintended network communication of sensitive confidential information due to an erroneous end user interaction with the respective end user device.
  • this approach to offer/order products/services via a network usually does not result in a legally binding relationship between providers and end users.
  • neither providers nor end users can be principally confident in the identity, credibility and solvency of the other party.
  • providers are required to take care for product/service related (financial) transactions, whereby the providers have the burden to prove that such transactions have been correctly and properly executed.
  • the end user is responsible to correctly communicate information to the provider necessary for such transactions.
  • US-5,960,411 (Amazon. Corn-Patent) teaches an internet-related method and system for placing a purchase order via a communication network.
  • the security of sensitive confidential information communication between an end user and a product/service provider is enhanced by transmitting an end user identifier to the provider.
  • the provider retrieves sensitive confidential information of the respective end user from a data base such as the credit card number and bank account of the end user.
  • a data base such as the credit card number and bank account of the end user.
  • the object of the present invention is to overcome the above-described problems of the prior art and, in particular, to provide an end user and provider friendly, secure and easy-to-use solution for requesting products and/or services via a network, preferably the Internet.
  • Solution according to the invention is to overcome the above-described problems of the prior art and, in particular, to provide an end user and provider friendly, secure and easy-to-use solution for requesting products and/or services via a network, preferably the Internet.
  • a method for routing a request from an end user device to a provider in a network including operating one of a plurality of input means of an end user device indicative of a request, automatically establishing a communication link to a provider in dependence on the request of the operated input means, communicating the request to the provider, and communicating a response to the end user device in dependence on the request.
  • the requests are assigned to the input means, the requests including data and/or information specifying the communication link, and/or data and/or information specific for the provider (an URL-adress) and/or data and/or information and/or service requests for providers accessible by the end user device, and/or a request for assigning functions to the input means remotely controlled by providers accessible by the end user device.
  • requests are re-assigned to the input means in dependence on the request of the operated input means by replacing requests previously assigned to the input means, and one of the input means indicative of a respective one of the reassigned requests is operated, whereby the communication link is established in dependence on the re-assigned requests of the input means lastly operated and the response is communicated to the end user device in dependence on the re- assigned request communicated to the provider.
  • an end user device ID uniquely associated with the end user device, and/or an end user ID uniquely identifying a user of the end user device is communicated by the end user device.
  • the communication security in the network can be enhanced, if a provider ID uniquely associated with the provider is communicated by the provider.
  • the communication link is established via a primary provider.
  • the assigning and/or the re-assigning of the requests is performed by the primary provider and/or the provider upon the establishing of the communication link and/or upon the communicating of the request and/or under control of the primary provider and/or the provider by establishing a communication link for communicating suitable data to the end user device.
  • the end user device ID or the end user ID is validated by the primary provider, whereas data being indicative of a result of the validation can be communicated to the provider in order to inform the provider of the validity of the end user device ID and/or the end user ID.
  • the provider ID is validated by the primary provider, whereas data/information indicative of a result of the validation can be communicated to the end user device in order to inform the end user device of the validity of the provider ID.
  • a communication link is automatically established to a further provider, preferably a provider of financial services, for initiating respective financial transactions related to the request.
  • the communication links can be established via an E-mail provider.
  • the communication link is established as a communication link specific for the end user device and the provider.
  • the request includes data and/or information being indicative of the specific communication link.
  • the established communication link can be routed to the network in an enhanced secure manner.
  • the invention provides a system for routing a request from an end user device to a provider in a network.
  • the system comprises a plurality of providers, each thereof being adapted to be operated in response to a request, an end user device for communicating the request to one of the plurality of providers, and a network for selectively connecting the end user device with one of the plurality of providers, wherein the end user device comprises a plurality of input means, each thereof being indicative of a request, and the end user device being adapted to automatically establish a communication link to one of the plurality of providers in dependence on a request of one of the plurality of input means upon an operation thereof for communicating the request to one of the plurality of providers.
  • the input means are associated with data and/or information specifying the communication link, and/or data and/or information specific for the requested provider (e.g. URL-adress), and/or data and/or information and/or service requests for providers accessible by the end user device.
  • the input means can be indicative of a request for assigning functions to the input means remotely controlled by providers accessible by the end user device.
  • the plurality of providers is adapted to communicate a response to the end user device in response to the communicated request.
  • the end user device can be adapted to assign the requests to the plurality of input means and/or to re-assign requests to the plurality of input means in dependence on a request of an operated input means by replacing requests previously assigned to the input means.
  • the end user device can comprise an end user device ID uniquely associated with the end user device, and/or an end user ID uniquely identifying a user of the end user device to be communicated by the end user device upon establishing the communication link and/or communicating the request.
  • the provider can comprise a provider ID uniquely associated with the provider to be communicated by the provider upon establishing the communication link and/or communicating the request.
  • An further security improvement can be achieved if the system includes a primary provider for establishing the communication link between the end user device and the provider.
  • the primary provider and/or the provider is adapted to control the assignment and/or re-assignment of the requests to the input means.
  • the primary provider is adapted to validate the validity of the end user device ID and/or the end user ID.
  • the primary provider can be adapted to validate the validity of the provider ID.
  • the system includes a provider, preferably a provider of financial services, being adapted to be selectively operated in dependence on the request.
  • a provider preferably a provider of financial services, being adapted to be selectively operated in dependence on the request.
  • the system can include an E-mail provider for establishing at least a part of the communication link and/or for communicating the request.
  • the communication link is a communication link specific for the end user device and the provider.
  • data and/or information being indicative of the specific communication link can be associated with the input means such that upon operation thereof the specific communication link is established.
  • Fig. 1 illustrates a network according to the invention
  • Fig. 2 illustrates an embodiment of a request routing according to the invention
  • Fig. 3 illustrates a further embodiment of a request routing according to the invention
  • Fig. 4 illustrates an end user device according to the invention
  • Fig. 5 illustrates a button application handling according to the invention
  • Fig. 6 illustrates a button routing according to the invention
  • Fig. 7 illustrates a button loading/reloading according to the invention
  • Fig. 8A and 8B illustrate different button architectures according to the invention.
  • Fig. 9A and 9B illustrate buttons according to the invention having different button levels.
  • a network N is used for connecting a plurality of end user devices EUD, a plurality of providers P and a plurality of financial service providers FSP with a primary provider PP. Further, a trust center TC can be connected via the network N to the primary provider PP.
  • the primary provider PP controls and monitors data/information communication between the end user devices EUD, the providers P and the financial service providers FSP, including product/service requests from the end user devices EUD, request related responses from the providers P and payment orders to the financial service providers FSP.
  • Each end user device EUD comprises an uniquely identifying end user device ID.
  • the end user device IDs are assigned to the end user devices EUD before delivery to and/or installation at respective end user premises.
  • the end user device IDs are stored in association with personal information for an end user of a respective end user device EUD.
  • personal end user related information is provided from the end users to the primary provider PP before the operation of the respective end user device EUD, for example upon ordering an end user device EUD or delivery/installation thereof.
  • an uniquely identifying end user ID is assigned to each end user.
  • the end user ID used by the primary provider PP for identifying the respective end users can be provided as a PIN number and/or in form of a token, SIM-card, smart card and the like including end user ID representing data/information.
  • the identification of an end user device EUD and/or respective end users is accomplished by transferring the end user device ID and/or the end user ID via the network N to the primary provider PP upon operation of the end user device EUD.
  • the end user device ID which is fixedly pre-installed and cannot be changed/modified by end users is automatically communicated to the primary provider PP under control of the end user device EUD when a respective communication link is established.
  • the current end user is required to input his personal end user ID into the end user device EUD.
  • a personal ID for example by means of a key pad, a touch screen, a mouse, a microphone and the like.
  • a part of an end user ID can be provided as a personal ID number whereas the remaining part of the end user ID is provided in the form of a device comprising respective end user ID data/information.
  • the end user is required to input his end user ID by means of the above input means and interfaces.
  • the end user device IDs and/or the end user IDs can be provided/assigned in cooperation with a trust center TC. Further, the security of the network N is enhanced if the primary provider PP validates received end user device IDs and/or received end user IDs by establishing a suitable communication link to the trust center TC.
  • a provider ID is communicated to and validated by the primary provider PP in order to inform the end user device EUD of the validity, authenticity, and integrity of the provider P.
  • a communication with the trust center TC will enhance the network security.
  • the providers P are registered at the primary provider PP, preferably by means of provider IDs.
  • the primary provider PP stores at least some information relating to the products/services of the providers P.
  • the primary provider PP For initiating financial transactions/payments possibly related to products/services requested by an end user, the primary provider PP retrieves respective personal information of the requesting end user and establishes a communication link to one of the financial service providers FSP. In line with data/information communicated by the primary provider PP, the receiving financial service provider FSP executes the respective financial transaction/payment with respect to the provider P providing the requested product/service.
  • the operation of the network N of Fig. 1 is described for one end user device EUD requesting a product/service from one provider P in connection with one financial service provider FSP.
  • the end user device EUD Upon start-up, the end user device EUD provides data/information relating to at least some of the products/services which can be requested over the network N to an end user.
  • An embodiment of the end user device EUD and the operation thereof will be described below in greater detail.
  • the end user operates input means (not shown) of the end user device EUD to select a desired product/service, a desired product/service category, or a desired provider P. Then, the end user device EUD automatically establishes a communication link to the primary provider PP and communicates its end user device ID, optionally in combination with the end user ID of the current end user, to the primary provider PP.
  • data/information uniquely assigned to the input means are accessed in order to establish the communication link to the primary provider PP and the provider P respectively.
  • data/information which are stored in the end user device EUD by means of a RAM, ROM, floppy/hard/optical memory a chip card, a smart cart, a magnetic strip card, and the like include e.g. the (URL-)address of the primary provider PP and/or of the provider P at least, such data/information a suitable to identify the primary provider PP and/or the provider P in a manner that the necessary communication link can be established.
  • the data/information assigned to the input means do not include the address of the provider P, the request must specify the provider P to the primary provider PP, which in turn establishes the communication link to the provider P.
  • the established communication link is specific for the end user device EUD and the provider P.
  • Such a predefinition of a specific communication link can be accomplished be assigning respective data/information to the input means.
  • the data/information of the input means specifying the communication link can be related to the communication link between the end user device EUD and the primary provider PP, only.
  • the communication link from the primary provider PP to the provider P can be any communication link or, in a similar manner, a predefined specific communication link in the network N.
  • the primary provider PP validates the end user device ID and/or the end user ID. If this validation fails, i. e. the received end user device ID and/or the received end user ID is not valid and/or not registered, the primary provider PP sends a respective response to the end user device EUD. Such a response can include information that the ID validation has failed and a request to input a correct, valid end user ID. In case no valid registered IDs are communicated to the primary provider PP, the communication link to the end user device EUD is interrupted.
  • the end user device EUD communicates a request to the primary provider.
  • the request is generated by the end user device EUD in dependence on the selected product/service (category) and provider, respectively.
  • the end user request is handled by the primary provider PP such that the request is communicated to the provider P providing the requested product/service (category), or to the provider P requested by the end user, respectively.
  • the request is communicated to the respective provider P via a communication link established under control of the primary provider PP.
  • the primary provider PP communicates further end user related data/information being stored at the primary provider as described above to the provider P.
  • Such further end user related data/information includes name, bank account/credit card number and/or limit, shipment address, etc. of the end user which are required by or necessary for the provider P to provide the desired product/service.
  • the provider P communicates a response to the end user device EUD via the primary provider or, as indicated by the dashed line of Fig. 2, directly to the end user device EUD.
  • a response can include a confirmation that the requested product/service is available to be provided to the end user.
  • a response can include data/information concerning products/services of the provider P, for example in form of an order list and/or a product/service overview for a selection of specific products/services.
  • the response from the provider P to the end user device EUD comprises the requested product/service itself. Examples for such products/services are software programs, data bases or parts thereof, acoustic and/or video data, any data/information of common interest (e. g. financial, economic, cultural, political information), and the like.
  • the end user requesting products/services from the provider P is charged for such orders.
  • the primary provider PP establishes a communication link to the financial service provider FSP responsible for financial transactions on behalf of the end user.
  • the financial service provider FSP can be designated by the end user at his/her registration at the primary provider PP, the delivery/installation of his/her end user device EUD, and/or in combination with the product/service request.
  • the primary provider PP communicates respective data/information to the financial service provider FSP.
  • the financial service provider FSP executes the financial transaction resulting from the end user device, i. e. transferring the amount of money to the provider P or a financial service provider FSP thereof necessary to pay for the requested product/service.
  • the primary provider PP ensures that only registered authorized end user devices EUD and/or end users are allowed to request/order products/services. Therefore, the providers P are not required to register end user devices EUD and/or end users and validate their identity/authenticity upon a request/order therefrom, as known in the prior art. Since the invention provides for a separation of product/service requests and (financial) transactions resulting therefrom, it is possible to control and monitor such transactions by the primary provider PP. Therefore, the providers P only have to provide the requested products/services but are not concerned with associated (financial) transactions. Moreover, the providers P are ensured to receive the money for provided/delivered products/services, since the primary provider PP initiates such financial transactions independently from end user devices EUD and/or end users.
  • end users are ensured of the credibility, authenticity and integrity of providers P and/or financial service providers FSP, since the primary provider PP guarantees that only registered, identified and validated providers P and/or financial service providers FSP are allowed to provide their products/services and to actively partizipate for accomplishing the request.
  • the communication links between end user devices EUD, providers P, financial service providers FSP and the primary provider PP can be established via an Internet service provider, preferably an E-mail service provider.
  • an Internet service provider preferably an E-mail service provider.
  • the end user device EUD should additionally comprise known E-mail features, such as an attachment capability.
  • a novel end user device illustrated in Fig. 4 is used. Beside conventional telephone and network capabilities, this end user device comprises novel features which will be explained in the following.
  • the end user device includes a key pad KP and a hand set HS for conventional telephone and network operation. Additionally, the end user device comprises a visual display VD and a plurality of input means which will be referred to as buttons B. When the end user device is operated to request products/services via a network, available products/services, available product/service categories and/or accessible providers are displayed on the visual display VD.
  • the visual information of the visual display VD is arranged in special relation to buttons B such that an end user can select a desired product/service (category) and/or provider by pressing a respective button B.
  • buttons B Upon pressing one of the buttons B, the above-described operation of the network of Fig. 1 and 2 is initiated.
  • this end user device provides for a very user friendly operation since the end user is only requested to press a button.
  • Fig. 5 illustrates the case wherein at least one visual information of the visual display VD associated with one of the buttons B is related to a product/service which can be provided via the network N, e.g. software programs, data bases, etc.
  • a product/service which can be provided via the network N, e.g. software programs, data bases, etc.
  • an action _1 is triggered.
  • the action _1 triggers a product/service request to the provider P.
  • the provider P generates a remote replay of the request product/service to the end user device EUD, preferably by a re-configuration thereof to execute the requested application.
  • this is indicated by an action _2 displayed on the visual display VD.
  • the end user device EUD provides for a so-called button routing, illustrated in Fig. 6.
  • the end user presses a button B routing him/her to a desired provider and/or to a provider of the desired products/services.
  • the provider P communicates a response to the end user device EUD including new data/information to be displayed on the visual display VD.
  • the new data/information is related to further products/services and/or providers which can be selected by pressing a respective button B.
  • This procedure allows for an automatic routing from one provider to another, and/or from one product/services category to another without any interaction of the user beside the pressing of the respective buttons B.
  • the information of the visual display VD associated with the buttons B is loaded and/or re-loaded under remote control of a respective provider P and/or the primary provider PP.
  • the end user device EUD can be configured and/or reconfigured under control of a provider P or the primary provider PP.
  • the provider P and/or the primary provider PP or in pre-defined time intervals Upon request from the end user device EUD, the provider P and/or the primary provider PP or in pre-defined time intervals, a communication link between the provider P or the primary provider PP and the end user device EUD is established. Then, the provider P or the primary provider PP, respectively, transmits data/information including data/information suitable to adapt and/or modify the visual information of the visual display VD to the demands of the respective end user.
  • buttons B are described to be real, physical buttons arranged adjacent to the visual display VD, it is contemplated to utilize so-called "virtual" buttons (not shown). Such virtual buttons are displayed on the visual display VD in special relation to product, service, and/or provider related information thereof, Here, the visual display VD must comprise touch screen capabilities for operating the virtual buttons. While the fixed arrangement of the real, physical buttons B requires a specific arrangement of the visual information of the visual display VD, the use of virtual buttons allows any arrangement thereof in relation to a respective visual information which can be realized on the visual display VD.
  • the functional structure of the buttons B can be a hierarchical structure and/or a star-shaped structure, as shown in Fig. 8A and 8B.
  • the operation of a button B results in a button associated information on the visual display VD for the next functional button level.
  • the visual display information for a button level 2 is at least partially indicative of providers for travel products/services. Examples for such visual display information for button levels 1 and 2 are illustrated in Fig. 9A and 9B.
  • the star-shaped functional button structure of Fig. 8B does not employ hierarchically arranged button levels, but a functional button structure where the operation of a button can lead to any button related visual information for which the end user device is configured.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un procédé et un système dans lesquels un utilisateur d'un dispositif d'utilisateur final peut accéder aux services proposés dans un réseau sans devoir passer par une interaction avec le dispositif d'utilisateur final, à l'exception des manipulations des moyens d'entrée pour indiquer une demande qui correspond au service désiré par l'utilisateur. On met en oeuvre ce procédé en utilisant un dispositif d'utilisateur final qui comprend des moyens d'entrée dont chacun indique une demande correspondant aux services proposés dans le réseau. Après manipulation d'un des moyens d'entrée, le dispositif d'utilisateur final établit automatiquement une liaison de communication avec un fournisseur respectif en rapport avec la demande sélectionnée par l'utilisateur. Comme les demandes sont attribuées aux moyens d'entrée sans que l'on doive établir une liaison de communication entre le dispositif d'utilisateur final et les fournisseurs du réseau, l'utilisateur sélectionne un service désiré et actionne des moyens d'entrée respectifs avant qu'une liaison de communication avec un fournisseur respectif ne soit établie. La demande est communiquée au fournisseur respectif qui, a son tour, est sollicité pour fournir le service sélectionné par l'utilisateur. Afin de garantir que seuls les utilisateurs autorisés accèdent aux services, la liaison de communication est établie via un fournisseur primaire. Le fournisseur primaire valide un ID de dispositif d'utilisateur final et/ou un ID de l'utilisateur, ce qui permet de refuser l'établissement d'une liaison de communication à un fournisseur désiré si la validation indique que l'ID de dispositif d'utilisateur final et/ou l'ID de l'utilisateur n'est pas valable. Après une validation positive, la liaison de communication peut être établie. Les mêmes règles s'appliquent dans l'autre sens à tout ID identifiant le fournisseur de façon unique. En outre, le fournisseur primaire établit une liaison de communication vers un fournisseur de services financiers pour obtenir un total des coûts qui résultent du service désiré fourni à l'utilisateur. Par conséquent, le fournisseur du service désiré par l'utilisateur peut s'assurer que les coûts relatifs aux services sont payés par l'utilisateur du moment que fournisseur primaire contrôle et surveille les transactions financières respectives.
PCT/EP2000/006828 2000-07-17 2000-07-17 Interface utilisateur pour applications en réseau WO2002007407A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/EP2000/006828 WO2002007407A1 (fr) 2000-07-17 2000-07-17 Interface utilisateur pour applications en réseau
AU2000259854A AU2000259854A1 (en) 2000-07-17 2000-07-17 User interface for networked applications

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2000/006828 WO2002007407A1 (fr) 2000-07-17 2000-07-17 Interface utilisateur pour applications en réseau

Publications (1)

Publication Number Publication Date
WO2002007407A1 true WO2002007407A1 (fr) 2002-01-24

Family

ID=8164027

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2000/006828 WO2002007407A1 (fr) 2000-07-17 2000-07-17 Interface utilisateur pour applications en réseau

Country Status (2)

Country Link
AU (1) AU2000259854A1 (fr)
WO (1) WO2002007407A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1429519A1 (fr) * 2002-12-12 2004-06-16 Alcatel Proxy graphic pour les terminaux moins capables
WO2006007038A1 (fr) * 2004-06-16 2006-01-19 Advanced Micro Devices, Inc. Systeme de traitement de donnees d'acces a un support polyvalent
WO2006007039A1 (fr) * 2004-06-16 2006-01-19 Advanced Micro Devices, Inc. Systeme de controle d'un dispositif de traitement de donnees d'acces a un support polyvalent
WO2006007030A1 (fr) * 2004-06-16 2006-01-19 Advanced Micro Devices, Inc. Systeme de gestion d'une pluralite de systemes de traitement de donnees d'acces aux supports multi-usages
US9710851B2 (en) 2000-02-15 2017-07-18 Jpmorgan Chase Bank, N.A. System and method for generating graphical user interface

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5465401A (en) * 1992-12-15 1995-11-07 Texas Instruments Incorporated Communication system and methods for enhanced information transfer
US5657378A (en) * 1995-04-11 1997-08-12 M Power Corporation Digital screen phone terminal with graphical user interface
WO1998056151A1 (fr) * 1997-06-03 1998-12-10 Infogear Technology Corporation Procede et appareil permettant d'organiser et d'afficher des informations fournies par le reseau internet et le reseau telephonique
US5995106A (en) * 1993-05-24 1999-11-30 Sun Microsystems, Inc. Graphical user interface for displaying and navigating in a directed graph structure

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5465401A (en) * 1992-12-15 1995-11-07 Texas Instruments Incorporated Communication system and methods for enhanced information transfer
US5995106A (en) * 1993-05-24 1999-11-30 Sun Microsystems, Inc. Graphical user interface for displaying and navigating in a directed graph structure
US5657378A (en) * 1995-04-11 1997-08-12 M Power Corporation Digital screen phone terminal with graphical user interface
WO1998056151A1 (fr) * 1997-06-03 1998-12-10 Infogear Technology Corporation Procede et appareil permettant d'organiser et d'afficher des informations fournies par le reseau internet et le reseau telephonique

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"INTERNET KIOSK TOUCH PANEL SHELL", IBM TECHNICAL DISCLOSURE BULLETIN,US,IBM CORP. NEW YORK, vol. 39, no. 8, 1 August 1996 (1996-08-01), pages 85 - 87, XP000638146, ISSN: 0018-8689 *
NEUMAN B C ET AL: "KERBEROS: AN AUTHENTICATION SERVICE FOR COMPUTER NETWORKS", IEEE COMMUNICATIONS MAGAZINE,IEEE SERVICE CENTER. PISCATAWAY, N.J,US, vol. 32, no. 9, 1 September 1994 (1994-09-01), pages 33 - 38, XP000476553, ISSN: 0163-6804 *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9710851B2 (en) 2000-02-15 2017-07-18 Jpmorgan Chase Bank, N.A. System and method for generating graphical user interface
EP1429519A1 (fr) * 2002-12-12 2004-06-16 Alcatel Proxy graphic pour les terminaux moins capables
US7110763B2 (en) 2002-12-12 2006-09-19 Alcatel Graphical proxy for less capable terminals
WO2006007038A1 (fr) * 2004-06-16 2006-01-19 Advanced Micro Devices, Inc. Systeme de traitement de donnees d'acces a un support polyvalent
WO2006007039A1 (fr) * 2004-06-16 2006-01-19 Advanced Micro Devices, Inc. Systeme de controle d'un dispositif de traitement de donnees d'acces a un support polyvalent
WO2006007030A1 (fr) * 2004-06-16 2006-01-19 Advanced Micro Devices, Inc. Systeme de gestion d'une pluralite de systemes de traitement de donnees d'acces aux supports multi-usages
GB2430517A (en) * 2004-06-16 2007-03-28 Advanced Micro Devices Inc System for controlling a multipurpose media access data processing system
GB2431552A (en) * 2004-06-16 2007-04-25 Advanced Micro Devices Inc System for managing a plurality of multipurpose media access data processing systems
GB2433007A (en) * 2004-06-16 2007-06-06 Advanced Micro Devices Inc Multipurpose media access data processing system
JP2008502994A (ja) * 2004-06-16 2008-01-31 アドバンスト・マイクロ・ディバイシズ・インコーポレイテッド 複数の多目的媒体アクセスデータ処理システムを管理するためのシステム
JP2008502995A (ja) * 2004-06-16 2008-01-31 アドバンスト・マイクロ・ディバイシズ・インコーポレイテッド 多目的媒体アクセスデータプロセッシングシステム

Also Published As

Publication number Publication date
AU2000259854A1 (en) 2002-01-30

Similar Documents

Publication Publication Date Title
US7478068B2 (en) System and method of selecting consumer profile and account information via biometric identifiers
US8412625B2 (en) System and methods for a multi-channel payment platform
US20050187901A1 (en) Consumer-centric context-aware switching model
US8626842B2 (en) Content transaction management server device, content-providing server device, and terminal device and control program
US20020194128A1 (en) System and method for secure reverse payment
US20030220841A1 (en) Method and system for merchant-to-merchant referrals and item brokering
US20010029485A1 (en) Systems and methods enabling anonymous credit transactions
JP2005512234A6 (ja) 顧客中心コンテキストアウェア切換モデル
JP7214000B2 (ja) 情報流通システム、情報流通方法及び記憶媒体
JP2002133324A (ja) ユーザ情報管理装置、ユーザ情報管理方法及び電子サービスシステム
WO2016024076A1 (fr) Système et procédé de stockage sécurisé de données
US20030187784A1 (en) System and method for mid-stream purchase of products and services
RU2303810C2 (ru) Способ персонального автоматического доступа к разнородным услугам электронной коммерции и система для его осуществления
TWI439105B (zh) 服務提供系統
US20220045862A1 (en) Secure digital information infrastructure
JP2003085493A (ja) 個人情報統合管理システム及びそのプログラム並びにそのプログラムを記録した媒体
WO2002007407A1 (fr) Interface utilisateur pour applications en réseau
JP7206075B2 (ja) 決済サービス連携システム、連携データ照合サーバ、決済アプリケーション端末、決済サービス連携方法及びプログラム
JP2020068032A (ja) 金融機関システム
KR20010044710A (ko) 인터넷망을 이용한 환전 방법
JP3819269B2 (ja) 電子カード利用認証システム
JP2002329143A (ja) 取引支援装置
JP7453179B2 (ja) 認証システム
JP3552098B2 (ja) 情報処理方法および情報処理装置
JP2001134531A (ja) 情報処理方法、および情報処理装置、並びに端末装置

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 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 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
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

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

Ref country code: JP