WO2003005671A2 - Ameliorations concernant des dispositifs relies a internet - Google Patents

Ameliorations concernant des dispositifs relies a internet Download PDF

Info

Publication number
WO2003005671A2
WO2003005671A2 PCT/GB2002/003113 GB0203113W WO03005671A2 WO 2003005671 A2 WO2003005671 A2 WO 2003005671A2 GB 0203113 W GB0203113 W GB 0203113W WO 03005671 A2 WO03005671 A2 WO 03005671A2
Authority
WO
WIPO (PCT)
Prior art keywords
database
transaction
computing device
format
server
Prior art date
Application number
PCT/GB2002/003113
Other languages
English (en)
Other versions
WO2003005671A3 (fr
Inventor
Peter Fenelon
Andrew Davies.
Kenneth Tindell
Original Assignee
Livedevices Limited
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
Priority claimed from GB0116550A external-priority patent/GB2377287B/en
Application filed by Livedevices Limited filed Critical Livedevices Limited
Publication of WO2003005671A2 publication Critical patent/WO2003005671A2/fr
Publication of WO2003005671A3 publication Critical patent/WO2003005671A3/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
    • H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F5/00—Coin-actuated mechanisms; Interlocks
    • G07F5/18—Coin-actuated mechanisms; Interlocks specially adapted for controlling several coin-freed apparatus from one place
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F9/00—Details other than those peculiar to special kinds or types of apparatus
    • G07F9/002—Vending machines being part of a centrally controlled network of vending machines

Definitions

  • the present invention relates to a method and system for identifying an embedded device to a server system so as to provide an improved permission and billing relationship.
  • An embedded device is generally in the form of a microcontroller or the like adapted to interact with a larger server or servers, thereby allowing a device (such as a vending machine, domestic electric appliance, motor vehicle etc) to be remotely controlled and/or monitored from a central server by way of a standard protocol such as Internet Protocol.
  • a device such as a vending machine, domestic electric appliance, motor vehicle etc
  • a major difficulty with embedded devices is that they generally comprise microcontrollers or the like with very limited RAM and ROM. Communicating embedded devices are often required to take part in client-server transactions with complex permission and billing relationships.
  • a typical microcontroller for use as an embedded device may have 32kB of ROM and lkB of RAM, which is not enough to support the usual client-server protocols such as SOAP (Simple Object Access Protocol) or CORBA (Common Object Request Broker Architecture).
  • client-server protocols such as SOAP (Simple Object Access Protocol) or CORBA (Common Object Request Broker Architecture).
  • SOAP Simple Object Access Protocol
  • CORBA Common Object Request Broker Architecture
  • IP Internet Protocols
  • IP Internet Protocols
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • Embodiments of the present invention seek to provide techniques that enable such restricted devices to take part in complex permission and billing relationships and to interact with relational databases.
  • Communicating embedded devices are often required to take part in transactions with complex permission and billing relationships.
  • the present invention is not restricted to the use of embedded devices, but extends generally to any networked device.
  • server a computer system capable of authenticating and processing transaction requests
  • transaction type a type of work that a device may ask a server to perform on its behalf.
  • transaction types could include "serve a web page”, “send an SMS message”, “return the time in UTC”.
  • “stakeholder” an individual or legal entity that has some interest in the operation of a device (for example, the owner, the manufacturer, a retailer, a service organisation)
  • “device account” funds apportioned by a stakeholder to support payment for transactions made by that device on behalf of that stakeholder
  • certificate a data structure which when interpreted by the server determines whether a particular device acting on behalf of a stakeholder is entitled to carry out a transaction
  • the present applicant has invented a model in which simple identification of the embedded device to our server system then allows the permissions and a micro- payment billing system to be implemented within the server.
  • a method of enabling transaction activities by networked devices each device being connectable to at least one server and associated with at least one stakeholder, wherein each device and each stakeholder has a unique identifier, and wherein there is provided a plurality of electronic certificates each owned by a stakeholder or on behalf of a device, the certificates being held on the at least one server and comprising a data structure which, when interpreted by the at least one server, determines whether a particular device acting on behalf of a particular stakeholder is entitled to carry out a transaction.
  • a system for enabling transaction activities by networked devices comprising a plurality of devices each being connectable to at least one server and associated with at least one stakeholder, each device and each stakeholder having a unique identifier, and wherein there is provided a plurality of electronic certificates each owned by a stakeholder or on behalf of a device, the certificates being held on the at least one server and comprising a data structure which, when interpreted by the at least one server, determines whether a particular device acting on behalf of a particular stakeholder is entitled to carry out a transaction.
  • the present applicant has developed a permissions model by which stakeholders can grant and revoke permissions (to carry out transactions and certain other operations) to other stakeholders and to embedded devices in which they hold a stake (i.e. for which they have appropriate permissions). Permissions are implemented by "holding" certificates which themselves carry the permissions.
  • Certificates are held on the server and used on behalf of the embedded device or stakeholder to which they "belong”. This means that:
  • This model where the complex operations are contained within the server, allows simple symmetric security schemes to protect embedded device and stakeholder involvement in a powerful permissions and transaction charging structure. It is sufficient for the embedded device to authenticate itself to the server - which knows what operations it is permitted to request and how much it can afford; the device itself needs no such knowledge.
  • a certificate preferably includes the following data:
  • Root certificates Some certificates in the system may only be issued by the administrators of the server. These are “root certificates” and are distinguished by having no “backing certificate” and implicitly allowing all operations. Root certificates are held by administrators who are able to introduce new devices, stakeholders and accounts into the system.
  • a certificate may be held by either a stakeholder or "on behalf of a device.
  • no certificate may authorise more transactions than the certificate that backs it (for example, a certificate authorising one type of XYZco transactions may not back a certificate authorising all XYZco transaction types).
  • Embodiments of the present invention allow credit to be transferred between device and stakeholder accounts within the server system, in any amount and in either direction, determined by any characteristic of the transaction. This provides content- based and time-based billing.
  • the transaction mechanism may implement an "open" model for "plug-in” transaction content, allowing arbitrary end-user operations to be incorporated into the transaction tracking and billing framework. For example, this includes data storage: charge by data returned, etc.
  • Each transaction request for a billed transaction must include a reference to a valid account within the system and each billable transaction is linked to an account to receive payment.
  • the permission model may be extended to encompass billing with the following constraints:
  • each billable transaction type has associated with it a cost. • there must exist a certificate granting the device making a transaction request permission to draw payment from the referenced device or stakeholder account.
  • the referenced device or stakeholder account must contain sufficient funds to pay for the transaction at the time it is requested, (i.e. its balance must be at least the current cost associated with the transaction type). If it does, the necessary funds are "escrowed" within the transaction system until completion of the transaction.
  • a transaction provider may choose to refund some (or all) of the price of the transaction to the requesting device after completion of the transaction.
  • the advertised cost of the transaction that the requesting device must be able to pay can therefore be thought of as a maxmimum possible cost - sufficient funds must be available when requesting the transaction to cover this.
  • the transaction provider may ask the transaction server to return some fraction of the escrowed funds to the requesting device account and only collect the remainder.
  • a transaction type may exist that normally returns the 100 last temperature readings from a weather station, for a cost of $1.00. If only 50 readings are available, the transaction provider may choose to return the available data, and an indication of only partial success while also refunding a suitable (dynamically-determined) fraction of the cost to the requesting device account.
  • Transaction providers may have the facility to dynamically change the "maximum”/"advertised” price of transactions within the system based (for example) on criteria such as :
  • a prototype implementation of this permission and billing system uses tables within a relational database to hold the details of device and stakeholder accounts, transaction types and certificates.
  • a Transaction Manager process running on a server computer accepts transaction requests from devices and decodes relevant account and device information, presenting this to an Authentication Manager process that determines whether or not the transaction may proceed, and to an Infrastructure Manager process that determines what code should be executed to fulfil the transaction request. Finally, on completion of the transaction, the Infrastructure Manager process constructs the response (based on the data returned and the success or failure of the transaction) and manages the billing and logging of the transaction.
  • SQL Structured Query Language
  • SQL has the advantage that it is standard, portable (many relational database packages use it to define tables and construct queries) and may be integrated into many programming languages and tools.
  • APIs Application Programmer Interfaces
  • a method of accessing a relational database from an embedded computing device by way of an appropriate set of commands wherein the set of commands comprises an enumerable set of parameterised strings each of which is identified with a transaction ID, and wherein each transaction ID is identified with two format strings, one of which describes a mapping between data supplied by the embedded computing device and the set of commands, and the other of which describes a mapping between fields returned from the relational database and a format readable by the embedded computing device.
  • a data processing system comprising at least one embedded computing device, a relational database and a server, wherein the at least one embedded computing device is adapted to request database operations from the relational database by way of an appropriate set of commands, wherein the set of commands comprises an enumerable set of parameterised strings each of which is identified with a transaction ID, and wherein each transaction ID is identified with two format strings, one of which describes a mapping between data supplied by the embedded computing device and the set of commands, and the other of which describes a mapping between fields returned from the relational database and a format readable by the embedded computing device.
  • the third and fourth aspects of the present invention may be used in conjunction with the first and second aspects, or may stand alone.
  • the set of commands comprises a set of SQL templates.
  • Embodiments of the third and fourth aspects of the present invention seek to enable small embedded devices to interact with SQL databases via a Transaction Manager, as described hereinbefore, without the need for any knowledge of the underlying database language, implementation or design.
  • the set of SQL interactions a device may request with the server is limited to an enumerable set of parameterised strings each of which is identified with a transaction ID - for example: TransactionlD SQL template
  • Each transaction ID is identified with two "format strings".
  • a format string is a sequence of identifiers each one of which describes the way in which one data item may be represented.
  • One of these format strings may describe the mapping between data supplied by the device, and printable SQL representations that will be inserted into the transaction's template SQL statement.
  • the other format string may describe a mapping between fields returned by the SQL query and a format readable by the device. Examples of operators in the format string include, but are not limited to:
  • format strings and templates are "well- formed" with respect to each other - i.e. the same number of format identifiers.
  • a fifth aspect of the present invention there is provided a method of requesting database operations from a relational database by making transaction requests from an embedded computing device by way of a server, wherein:
  • each database operation is associated with a transaction identifier and a template, the template being held only the server and describing the database operation in a language acceptable to the database;
  • the template includes placeholders that may be filled in by variables derived from a transaction request;
  • each database operation is associated with first and second format strings held only on the server;
  • the first format string is an input format string containing a list of commands that are interpreted when a transaction request is received, each command in the list being an instruction to translate one field of data presented by the embedded computing device in its own native format into a representation that may be used to fill in the placeholders and thus to instantiate the template, which is then passed to the relational database as an executable command;
  • the second format string is an output format string containing a list of commands that are interpreted when data are returned from the database as a result of the executable command of step iv), each command in the list being an instruction to translate one field of data returned from the database into a format comprehensible by the embedded computing device;
  • each transaction request comprises a transaction identifier sent by the embedded computing device, followed by a set of parameters that are used to fill in the placeholders in the template.
  • a data processing system comprising at least one embedded computing device, a server and a relational database, wherein the at least one embedded computing device is adapted to request database operations from the relational database by making transaction requests by way of the server, wherein:
  • eadi database operation is associated with a transaction identifier and a template, the template being held only the server and describing the database operation in a language acceptable to the database;
  • the template includes placeholders that may be filled in by variables derived from a transaction request;
  • each database operation is associated with first and second format strings held only on the server;
  • the first format string is an input format string containing a list of commands that are interpreted when a transaction request is received, each command in the list being an instruction to translate one field of data presented by the embedded computing device in its own native format into a representation that may be used to fill in the placeholders and thus to instantiate the template, which is then passed to the relational database as an executable command;
  • the second format string is an output format string containing a list of commands that are interpreted when data are returned from the database as a result of the executable command of step iv), each command in the list being an instruction to translate one field of data returned from the database into a format comprehensible by the embedded computing device;
  • each transaction request comprises a transaction identifier sent by the embedded computing device, followed by a set of parameters that are used to fill in the placeholders in the template.
  • the fifth and sixth aspects of the present invention may be used in conjunction with the first and second aspects, or may stand alone.
  • the fifth and sixth aspects of the present invention are closely related to the third and fourth aspects, and the description in relation to the third and fourth aspects applies also to the fifth and sixth aspects.
  • the fifth and sixth aspects of the present invention will now be further described.
  • Each database operation is associated with a transaction ID and a "template” held only on the server describing the operation in a language acceptable to the database. This "template" contains placeholders that will be filled in by variables derived from the transaction request.
  • Each operation is associated with two “format strings” held only on the server.
  • the first of these contains a list of commands that are interpreted when a transaction request is received.
  • Each command in the string is an instruction to translate one field of data presented by the device in its own native format to a representation that can be used to fill in the placeholders in the template.
  • the data supplied by the device are decoded according to the "input format string" and used to fill in the placeholders in the template.
  • the instantiated template is then sent to the underlying database software running on the server as an executable command.
  • the second of these format strings contains a list of commands that are interpreted once for each row of data returned by the database operation.
  • Each command in the string is an instruction to translate one field of data returned by the execution of the database command into a format comprehensible by the requesting device.
  • a transaction request in this scheme consists of the device sending the transaction identifier followed by a set of parameters that will be used to fill in the placeholders - these may be sent in whatever data format is suitable to the embedded device as the Input Format String will translate these into a format usable by the database (for example, a two's-complement signed binary representation of the integer 123 would be translated to the string "123").
  • a transaction response in this scheme consists of the server sending the results of the query as a set of rows each encoded in a format comprehensible by the device - the Output Format String translates the results of the query from that returned by the database to one comprehensible by the device.
  • the request for data returned by device 123 would be:
  • the ⁇ 100> would be used to look up the template and format strings.
  • the output format string would be applied to each row to construct the response:
  • FIGURE 1 shows an example of a hierarchy of certificates
  • FIGURE 2 shows an example of transaction permission checking
  • FIGURE 3 shows an example of processing a database query transaction.
  • Non-root certificate 2 allows all transactions from all devices owned by company XYZ that are located in, say, the United States of America. Certificate 2 has a start date of 1 st February 2000 and an end date of 31 st December 2004.
  • Non- root certificate 3 allows all transactions from all devices owned by company XYZ that are located in, say, the United Kingdom. Certificate 3 has a start date of 1 st July 2000 and an end date of 30 th June 2004. It is to be noted that the transactions allowed by non-root certificates 2 and 3 are subsets of the global set of transactions allowed by the root certificate 1. Furthermore, the validity dates of each of non-root certificates 2 and 3 are within the range of validity dates of the root certificate 1. A global systems administrator will generally hold the root certificate 1, and will be empowered to issue non-root certificates 2, 3 to local systems administrators based, in this example, respectively in the USA and the UK, the non-root certificates 2, 3 each being backed by the root certificate 1.
  • the non-root certificate 2 is shown to be backing two second-layer non-root certificates 4, 5.
  • Non-root certificate 4 allows "write to temperature log” transactions from devices owned by company XYZ that are located in the USA, the certificate being valid from 1 st February 2000 to 31 st December 2004.
  • Non-root certificate 5 allows "read from temperature log” transactions from devices owned by company XYZ that are located in the USA, the certificate being valid from 1 st January 2001 to 31 st December 2003. It will be appreciated that the permissions granted by certificates 4, 5 are subsets of the permissions granted by certificate 2, which in turn form a subset of the permissions granted by the root certificate 1.
  • Further layers of the hierarchy may provide certificates permitting transactions with, for example, a particular subset of devices (e.g. vending machines) located within a given territory. Further examples will be apparent to the skilled reader.
  • devices e.g. vending machines
  • Figure 2 shows an example of transaction permission checking in accordance with an embodiment of the present invention.
  • a root certificate 1 allowing all transactions from all devices owned by company XYZ, the root certificate 1 having a start (i.e. "valid from”) date of 1 st January 2000 and an end (i.e. "valid to”) date of 31 st December 2005.
  • the root certificate 1 is backing a non-root certificate 2 allowing all transactions from all devices owned by company XYZ that are located in the United States of America, non-root certificate 2 having a start date of 1 st February 2000 and an end date of 31 st December 2004.
  • Non-root certificate 2 in turn backs a further non-root certificate 4 allowing "write to temperature log" transactions from devices owned by company XYZ that are located in the USA, the certificate being valid from 1 st February 2000 to 31 st December 2004.
  • Figure 2 also shows two devices 6 and 7 (shown here in terms of server descriptors).
  • Device 6 is certificated by certificate 2
  • device 7 is certificated by certificate 4.
  • a "read from temperature log" transaction from device 6 is allowed, since device 6 is certified by certificate 2 (allowing all transactions from devices owned by company XYZ in the USA).
  • FIG. 3 shows an example of processing a database query transaction (operation) in accordance with an embodiment of the fifth and sixth aspects of the present invention.
  • a database transaction request of type T (its transaction identifier) is received from an embedded device by a server.
  • the request contains request parameters encoded in a format understood by the embedded device.
  • a description of transaction request type T is located and selected from a library 12 of database transaction descriptions held on the server.
  • the description includes an input format string, and output format string and a database query template.
  • the transaction request parameters are decoded at step 13 according to the input format string, and the decoded parameters are then inserted into the database query template.
  • a query can be sent at step 14 to relational database 15, and results from the database are then returned before being encoded at step 16 in a transaction response according to the output format string. Finally, at step 17, the transaction response is returned to the embedded device in a format understood by the embedded device.
  • ROM Read Only Memory memory whose content may not be changed by program execution segment the unit of TCP/IP transmission; a packet of information containing host, destination and protocol information and a "payload" of data.
  • SQL Structured Query Language a means of describing and querying database systems
  • TCP Transmission Control Protocol - a reliable end-to-end protocol layered on top of the Internet Protocol (IP)
  • TCP/IP stack the suite of software allowing a computer to connect to the Internet

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

L'invention concerne des procédés et des systèmes permettant d'identifier un dispositif intégré auprès d'un système serveur, afin d'améliorer la procédure d'autorisation et de facturation. On permet ainsi le lancement d'activités de transaction via des dispositifs en réseau, chaque dispositif pouvant être relié au moins à un serveur et associé au moins à un intéressé. Le serveur et l'intéressé ont chacun un identificateur unique, et un certificat électronique renvoie à chaque intéressé ou authentifie l'action au nom d'un dispositif. Lesdits certificats sont en possession du ou des serveurs considérés: ils comprennent une structure de données qui, suite à l'interprétation par ce ou ces serveurs, indique si le dispositif concerné, agissant au nom d'un intéressé déterminé, est habilité à conduire une transaction.
PCT/GB2002/003113 2001-07-06 2002-07-08 Ameliorations concernant des dispositifs relies a internet WO2003005671A2 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
GB0116550.5 2001-07-06
GB0116550A GB2377287B (en) 2001-07-06 2001-07-06 Improvements relating to internet-connected devices
US31091601P 2001-08-08 2001-08-08
US60/310,916 2001-08-08

Publications (2)

Publication Number Publication Date
WO2003005671A2 true WO2003005671A2 (fr) 2003-01-16
WO2003005671A3 WO2003005671A3 (fr) 2003-05-08

Family

ID=26246288

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/GB2002/003113 WO2003005671A2 (fr) 2001-07-06 2002-07-08 Ameliorations concernant des dispositifs relies a internet

Country Status (1)

Country Link
WO (1) WO2003005671A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2403577A (en) * 2003-06-30 2005-01-05 Sony Corp A system for user and device registration
GB2412211A (en) * 2003-06-30 2005-09-21 Sony Corp Device and user registration

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999036854A1 (fr) * 1998-01-16 1999-07-22 Mediadna, Inc. Systeme et procede pour authentifier des composants homologues

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999036854A1 (fr) * 1998-01-16 1999-07-22 Mediadna, Inc. Systeme et procede pour authentifier des composants homologues

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
HOWARD M., SONTAG C.: "Bringing the Internet All Electronic Devices" 29 March 1999 (1999-03-29) , USENIX , PROCEEDINGS OF THE EMBEDDED SYSTEMS WORKSHOP XP002222880 section 1.0 The Problem section 3.5 The Object Model *
JOHNSTON W. ET ALL: "Authorization and Attribute Certificates for Widely Distributed Access Control" 28 June 1998 (1998-06-28) , IEEE , IEEE 7TH INTERNATIONAL WORKSHOPS ON ENABLING TECHNOLOGIES - WETICE 98 XP002215692 abstract page 3, right-hand column, line 6, paragraph 4 -page 5, left-hand column, line 39, paragraph 5 figures 1,2 *
JORDAN DAVID: "An object database for embedded environments" 1 April 2000 (2000-04-01) , JAVA REPORT , ODMG XP002222881 the whole document *
TAYLOR MARK: "Embedded Systems n-Formation" 1 October 1999 (1999-10-01) , CIRCUIT CELLAR , THE MAGAZINE FOR COMPUTER APLLICATIONS XP002222879 page 1, line 1 -page 4, line 3 figures 1-4 *
THOMPSON M. ET ALL: "Certificate-based access control for widely distributed resources" 23 August 1999 (1999-08-23) , USENIX , PROCEEDINGS OF THE 8TH USENIX SECURITY SYMPOSIUM, WASHINGTON XP002215691 abstract paragraph [0001] - paragraph [0004] paragraph [0007] - paragraph [0009] example 2 figures 1-3 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2403577A (en) * 2003-06-30 2005-01-05 Sony Corp A system for user and device registration
GB2412211A (en) * 2003-06-30 2005-09-21 Sony Corp Device and user registration
GB2403577B (en) * 2003-06-30 2006-02-22 Sony Corp Device registration
US8166531B2 (en) 2003-06-30 2012-04-24 Sony Corporation Device registration system, device registration server, device registration method, device registration program, storage medium, and terminal device
US8955085B2 (en) 2003-06-30 2015-02-10 Sony Corporation Device registration system, device registration server, device registration method, device registration program, storage medium, and terminal device

Also Published As

Publication number Publication date
WO2003005671A3 (fr) 2003-05-08

Similar Documents

Publication Publication Date Title
US11531981B2 (en) Digital contracts in blockchain environments
EP1388084B1 (fr) Mecanisme de comptage et de facturation pour services web base sur un protocole de communication soap
RU2732585C2 (ru) Шлюзовой уровень абстракции
EP1645987B1 (fr) Appareil, procédé et logiciel de traitement de données
US8626842B2 (en) Content transaction management server device, content-providing server device, and terminal device and control program
US20070067437A1 (en) Generation of customized client proxies
US20030028614A1 (en) Portable storage media and method of utilizing remote storage unit on network as auxiliary memory of local computer by using the same
US20040098706A1 (en) Component-based software distribution and deployment
GB2378780A (en) An arrangement for preventing the re-use of tokens in accessing pay-per-use software
KR20060048948A (ko) 권리 데이터 오브젝트들을 제공하는 방법
TW200917084A (en) Metered pay-as-you-go computing experience
US8321337B2 (en) Internet-connected devices
WO2003005671A2 (fr) Ameliorations concernant des dispositifs relies a internet
MX2012010055A (es) Metodo y sistema de gestion de operaciones en un terminal de telecomunicaciones con motor de estados.
MX2012010195A (es) Metodo y sistema de gestion de operaciones en un terminal de telecomunicaciones.
KR20060080318A (ko) 유무선 통합 컨텐츠 제공 시스템 및 방법
KR20060079816A (ko) 유무선 통합 컨텐츠 관리 시스템 및 방법
CN103546324A (zh) 智慧型元件库管理的方法与***
KR20070029224A (ko) 개방형 스마트 카드(또는 아이씨 카드)의 후발급애플리케이션 중계 방법
Ainsworth et al. Implementing a secure, service oriented accounting system for computational economies
WO2003036530A1 (fr) Procede et systeme de concession de licences pour utilisation de services et de ressources numeriques
KR101124262B1 (ko) 혼용카드용 애플리케이션 또는 서비스 코드 제작 및 중계방법
KR100934339B1 (ko) 티켓을 이용한 웹 서비스 이용 요금 처리 방법
KR100742022B1 (ko) 개방형 스마트 카드(또는 아이씨 카드)의 후발급 애플리케이션 제작방법
KR101013162B1 (ko) 혼용 카드용 애플리케이션 또는 서비스 코드 중계 시스템

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC 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 OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG US UZ VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LU MC NL PT SE SK TR BF BJ CF CG CI CM GA GN GQ 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

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

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP