WO2001065417A1 - Telegestion de donnees amelioree independante du dispositif - Google Patents

Telegestion de donnees amelioree independante du dispositif Download PDF

Info

Publication number
WO2001065417A1
WO2001065417A1 PCT/US2001/006534 US0106534W WO0165417A1 WO 2001065417 A1 WO2001065417 A1 WO 2001065417A1 US 0106534 W US0106534 W US 0106534W WO 0165417 A1 WO0165417 A1 WO 0165417A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
command
commands
language
execute
Prior art date
Application number
PCT/US2001/006534
Other languages
English (en)
Inventor
Chris H. D. Lin
Original Assignee
Idini Corporation
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 Idini Corporation filed Critical Idini Corporation
Publication of WO2001065417A1 publication Critical patent/WO2001065417A1/fr

Links

Classifications

    • 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/547—Remote procedure calls [RPC]; Web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1038—Load balancing arrangements to avoid a single path through a load balancer
    • 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
    • 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/565—Conversion or adaptation of application format or content
    • 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/10015—Access to distributed or replicated servers, e.g. using brokers
    • 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/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
    • 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 electronic devices used to interact with
  • the present invention provides
  • Networks include server devices which have
  • a given network device may at times act as either a client
  • server and client devices are retained, and those terms shall refer to devices which, although possibly capable of alternating between server and client modes, are
  • Typical networks contain a wide variety of client device types, ranging
  • PDA Personal Digital Assistants
  • Each different client device type typically has a different language
  • the server is required to understand the syntax of the commands sent to it
  • client application software which is available to interact with the server information often has functionality which is substantially reduced from that
  • subset of commands is available to those client device types.
  • FIGS. 1 , IB, and I C Examples of prior art networks are seen in FIGS. 1 , IB, and I C.
  • a first client device 10 is linked to server 12 which
  • a second client device 18 is linked to server 20 which
  • HTML hypertext markup language
  • a network 30 may contain a first client device 32, and
  • Server 36 contains files 38, 40,
  • File 44 is in text format, and may be a file which is incorporated at runtime into a display controlled by files 38,
  • files 38, 40, 42 and 44 may contain the same
  • server 36 must select file 38 for distribution to device
  • server 36 must select file 42 for distribution to device 34.
  • execution by a client computer are presented.
  • the client is connected through a
  • the client communicates with the first server
  • the first server uses a first language, and the first server communicates with each of the servers
  • the language used is determined using the operating environment
  • the first server consults a rule identify a set of server commands in a second
  • respective servers are then caused to execute one or more of the commands with
  • FIGS. 1A, IB, and IC are examples of prior art networks.
  • FIG. 2 is one example of a electronic system according to the present
  • FIGS. 3A and 3B are a flow chart showing a method for processing client
  • FIG. 4 is an example of a rule table according to the present invention.
  • FIG. 5 is a flow chart showing another method according to the present
  • FIG. 6 is an example of a capability table according to the present invention.
  • FIG. 7 is an example of a present invention server loading table.
  • FIGS. 8 A and 8B are a flow chart showing another method of the present
  • FIGS. 9A, 9B and 9C are a flow chart showing yet another method of the
  • FIGS.10A, 10B and IOC are a flow chart showing yet another method of
  • the present invention provides a method and apparatus for allowing client
  • a client device is connected to a second server through a present
  • first server Commands are issued by the client to the first server in a first command language such as WML. If the command relates to an application
  • the first server translates the command into the
  • the results are transmitted by the second server to the first server.
  • the first server may transmit the results to the client device.
  • a limited functionality client device may remotely cause
  • FIG. 2 is one example of a present invention electronic system wherein
  • client devices are linked to servers.
  • network 50 includes client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated with client devices 52 and 54 which are associated
  • adaptive server 56 and servers 58, 60, and 62.
  • server 56 includes an adaptive client interface 64, a personalization module 66, a
  • servers 58, 60, and 62 are typical prior art devices.
  • Server 58 is an example of a typical prior art web server.
  • Servers 60 and 62 are typical prior art devices.
  • servers 50, 60, and 62 use different command syntax and languages.
  • Client interface 64 receives input information from either of clients 52 or
  • Interface 64 is adaptive in that it is configured to determine the type of
  • a first device may
  • a second device may use HTML, but commands issued by either
  • interface may be attached to any type of device.
  • Personalization module 66 is configured to personalize each networking
  • Service routing module 68 determines the proper resources with which to
  • routing module 68 examines a rule table to identify the proper server commands to
  • routing module 68 Once the proper server commands are identified, routing module 68
  • the commands will be particularly structured and formatted for that server.
  • Application interface 70 is configured to transmit the proper server
  • API application program interface
  • Process manger 72 is configured to manage events and processes within
  • FIGS. 3 A and 3B comprise a flowchart showing a method of the present
  • first server a first server and a second server. It is intended that the term "first server" apply
  • server 56 (FIG. 1) through which client commands are passed
  • second server apply to those servers such as servers 58, 60, and 62 which
  • Such a command is not restricted and
  • the client device transmits that client command to a present
  • the first server receives the client command and consults a rule
  • commands 86 translates into a set of one or more commands in a second
  • client "compare" command 90 translates into a set of server commands including
  • the first server translates the chosen command into the
  • the second server executes the translated command
  • a client command is translated into a set of
  • server commands and those server commands are then processed in the order with
  • server commands identified as being equivalent to the client command may be
  • the first server Prior to the execution of block 84, the first server has received a client
  • the first server routing module chooses one of the server
  • each of the server commands will be chosen in the desired order
  • an alternate embodiment may cause the commands to be translated in
  • the first server routing module interrogates a capabilities list
  • column 140 of servers being configured to execute those applications.
  • the client command is to convert a file
  • the client command is transmitted
  • capabilities table shows two servers having IDs 129 and 135 configured to execute
  • a server loading table such as that depicted in FIG. 7 is interrogated
  • server 129 will be
  • module at block 154, identifies a server capable of being configured to execute
  • FIGS. 8 A and 8B are identical to FIGS. 8 A and 8B.
  • a client device such as device 52 (FIG. 2) initiates a document display
  • a first server of the present invention such as
  • WordPerfect application be executed on a server (its own, or a second server) with
  • the first server receives the block 1 0 request. It is assumed
  • the devices such as device 52 be transmitted with every document display request.
  • server 56 may assume a particular client device characteristic information
  • the specific device such as device 52.
  • the present invention first server identifies the language
  • the first server determines the content of the information
  • Examples of content types include images, text, graphics, etc.
  • the first server transmits overview details of each content
  • a preference setting shows that the client device associated with a given
  • login identifier prefers text over graphics, or summary information instead of
  • the client device displays details relating to the various components
  • the present invention first server compares information about
  • This subset may include any set of information within the content bucket which may be displayed in a single screen
  • the upper right region of the content bucket such as the upper right region of the content bucket
  • the selected subset of information selected for display is then transferred to
  • the client device and displayed. Once the information has been transferred, the client device and displayed. Once the information has been transferred, the client device and displayed. Once the information has been transferred, the client device
  • first server process manager awaits the receipt of the next client device command.
  • the client device may transmit windowing commands which cause
  • the first server to refresh the client device display to include different portions of
  • a nonwindowing command is transmitted by the client device
  • document is retrieved by the first server and then presented to the client device one display at a time, or may instead be a method wherein the document is left on the
  • remote server and that remote server is remotely controlled by the first server as
  • FIGS. 9 A, 9B, and 9C together are a flow chart showing a method of the
  • server 56 FIG. 2.
  • any necessary parsing of the client communication is
  • client communication received at block 200 contains a plurality of commands
  • client communication is parsed into a set of distinct first server commands.
  • a command to be processed is chosen from the set of first
  • this block 204 operation will take into account the commands available for processing, and the commands
  • a rule table such as
  • client communication will typically include information relating to the operation
  • the rule table as seen in FIG. 4, includes a command and its
  • a rule table For example, if the first server command is an edit command, a rule table
  • the second procedure may
  • Recursion is used when a command such as command 220 is also a rule
  • command 220 when command 220 is processed, there may be
  • procedures 208 and 210 are both "edit"
  • the priority indicator will indicate that procedure 210 is a
  • procedure 208 higher processing priority than procedure 208.
  • procedure 224 one of the procedures determined at block 206 is chosen for
  • procedure 208 would be
  • application servers are configured to execute the procedure command chosen at
  • application server is chosen to execute the chosen command, and that server is
  • chosen procedure comprises commands which have not yet been executed. If not,
  • At least one application server is configured to execute that command.
  • FIGS. 10A, 10B and IOC are a flow chart showing yet another method of
  • the method begins at step
  • server 56 FIG. 2.
  • the block 252 operation isn't performed.
  • the client communication received at block 250 contains a plurality of commands
  • client communication is parsed into a set of distinct first server commands.
  • a command to be processed is chosen from the set of first
  • a rule table such as
  • an intelligent decision may be made about which configured server to use to execute a given command, and which server(s) to
  • At least one server is configured to perform at least one equivalent
  • a server may be configured to also be executed on a different server, in order to

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Computer And Data Communications (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un procédé et un dispositif pour la commande à distance d'exécution d'instruction de serveur par un ordinateur client. Le client est relié par un premier serveur (58) à une pluralité de serveurs, et il communique avec le premier serveur (58) dans la pluralité de serveurs en utilisant le langage nécessaire pour accomplir la tâche voulue. Le langage est déterminé en fonction de l'environnement d'exploitation et de l'interface de programme d'application (70) recevant l'instruction.
PCT/US2001/006534 2000-03-02 2001-02-28 Telegestion de donnees amelioree independante du dispositif WO2001065417A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US18655400P 2000-03-02 2000-03-02
US60/186,554 2000-03-02
US70907000A 2000-11-08 2000-11-08
US09/709,070 2000-11-08

Publications (1)

Publication Number Publication Date
WO2001065417A1 true WO2001065417A1 (fr) 2001-09-07

Family

ID=26882203

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/006534 WO2001065417A1 (fr) 2000-03-02 2001-02-28 Telegestion de donnees amelioree independante du dispositif

Country Status (2)

Country Link
TW (1) TW493128B (fr)
WO (1) WO2001065417A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1376340A2 (fr) * 2002-06-19 2004-01-02 Robert Bosch Gmbh Appareil électronique contrôlé par un processeur
EP1557756A2 (fr) * 2004-01-23 2005-07-27 Microsoft Corporation Distribution déterministe d'objets vers un code de traitement d'objets basée sur des règles

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5524253A (en) * 1990-05-10 1996-06-04 Hewlett-Packard Company System for integrating processing by application programs in homogeneous and heterogeneous network environments
US5627996A (en) * 1992-08-19 1997-05-06 At&T Method and apparatus for accessing the same computer file using different file name formats
US5724503A (en) * 1995-03-31 1998-03-03 Sun Microsystems, Inc. Method and apparatus for interpreting exceptions in a distributed object system
US5960200A (en) * 1996-05-03 1999-09-28 I-Cube System to transition an enterprise to a distributed infrastructure

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5524253A (en) * 1990-05-10 1996-06-04 Hewlett-Packard Company System for integrating processing by application programs in homogeneous and heterogeneous network environments
US5627996A (en) * 1992-08-19 1997-05-06 At&T Method and apparatus for accessing the same computer file using different file name formats
US5724503A (en) * 1995-03-31 1998-03-03 Sun Microsystems, Inc. Method and apparatus for interpreting exceptions in a distributed object system
US5960200A (en) * 1996-05-03 1999-09-28 I-Cube System to transition an enterprise to a distributed infrastructure

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1376340A2 (fr) * 2002-06-19 2004-01-02 Robert Bosch Gmbh Appareil électronique contrôlé par un processeur
EP1376340A3 (fr) * 2002-06-19 2008-11-05 Robert Bosch Gmbh Appareil électronique contrôlé par un processeur
EP1557756A2 (fr) * 2004-01-23 2005-07-27 Microsoft Corporation Distribution déterministe d'objets vers un code de traitement d'objets basée sur des règles
EP1557756A3 (fr) * 2004-01-23 2006-01-18 Microsoft Corporation Distribution déterministe d'objets vers un code de traitement d'objets basée sur des règles
US7624141B2 (en) 2004-01-23 2009-11-24 Microsoft Corporation Deterministic rule-based dispatch of objects to code

Also Published As

Publication number Publication date
TW493128B (en) 2002-07-01

Similar Documents

Publication Publication Date Title
US10063618B2 (en) Remote browsing session management
EP0810524B1 (fr) Dispositif et procédé de traitement de "servlets"
US7254786B2 (en) System for transmitting and displaying icon resources group associated with remote application to a local computing system to facilitate virtualization of the remote application
US7269664B2 (en) Network portal system and methods
US9723067B2 (en) Prioritized content transmission
US6237005B1 (en) Web server mechanism for processing multiple transactions in an interpreted language execution environment
US7496641B2 (en) Computer system
US7526482B2 (en) System and method for enabling components on arbitrary networks to communicate
US20040204073A1 (en) Network technology augmented user device framework
JP2000322395A (ja) オブジェクト・レンダリングの分散配置のための協調プロキシ・システムの方法および装置
US20110191763A1 (en) Feature Manager System for Facilitating Communication and Shared Functionality Among Components
US10057320B2 (en) Offline browsing session management
WO2001065417A1 (fr) Telegestion de donnees amelioree independante du dispositif
JP2001331408A (ja) ワールド・ワイド・ウェブ・ドキュメント要求に埋め込むための必要な装置属性を指定する方法およびシステム
WO2001065393A1 (fr) Gestion amelioree de donnees a distance independante de dispositif
Cisco Updating the Mainframe Application Software
Cisco Updating the Mainframe Application Software
Cisco Updating the Mainframe Application Software
US7367029B2 (en) Method and system for handling data
WO2001065408A1 (fr) Gestion des donnees hors site independamment du dispositif
JP2001195240A (ja) データ操作方法及びクライアント・サーバーシステム並びにデータ操作用プログラムを記憶した記憶媒体

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): JP

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR

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)
32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: COMMUNICATION PURSUANT TO RULE 69 EPC (EPO FORM 1205A OF 030203)

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

Ref country code: JP