WO2007106243A2 - Device configuration and data extraction using a portable transaction format - Google Patents
Device configuration and data extraction using a portable transaction format Download PDFInfo
- Publication number
- WO2007106243A2 WO2007106243A2 PCT/US2007/002346 US2007002346W WO2007106243A2 WO 2007106243 A2 WO2007106243 A2 WO 2007106243A2 US 2007002346 W US2007002346 W US 2007002346W WO 2007106243 A2 WO2007106243 A2 WO 2007106243A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- transaction
- server
- data
- portable
- portable computer
- Prior art date
Links
- 238000013075 data extraction Methods 0.000 title description 10
- 238000000034 method Methods 0.000 claims abstract description 36
- 238000004891 communication Methods 0.000 claims description 30
- 238000013480 data collection Methods 0.000 claims description 4
- 230000004044 response Effects 0.000 description 17
- 230000008569 process Effects 0.000 description 13
- 230000015654 memory Effects 0.000 description 6
- 229920001690 polydopamine Polymers 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000007704 transition Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000010367 cloning Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005265 energy consumption Methods 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 238000004377 microelectronic Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003936 working memory Effects 0.000 description 1
Classifications
-
- 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/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
-
- 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
-
- 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
- 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
Definitions
- the inventive arrangements relate generally to methods and systems for device configuration and data extraction, and more particularly to portable data processing devices for interacting with a device to be configured or from which data is to be extracted.
- the equipment may be mounted in a vehicle or in a remote location.
- the computer can be transported to the site of the equipment so that the equipment can be configured or data extracted.
- PED personal electronic device
- PED personal digital assistant
- the invention concerns a method for performing a data transaction with a server using a portable computer.
- the portable computer can be a personal electronic device (PED) .
- PED personal electronic device
- the server can be any type of device that is configurable, or from which it can be desirable to extract data.
- the server can be any type of configurable radio equipment, another computer, a PED, a security system, or a data collection device.
- the method can begin by receiving in the portable computer one or more portable transaction files.
- Each portable transaction file can be provided in a predetermined portable transaction file format that includes a number of data fields.
- the data fields can contain transaction parameters.
- the transaction parameters can form a transaction parameter set that defines a type specific server protocol for a data transaction session.
- the type specific server protocol can define a data transaction session for a particular server type.
- the portable computer can perform a data transaction session.
- the portable computer can perform the data transaction session with any type of server for which the portable transaction file has been provided for defining the type specific server protocol, provided that the communication layer or transport type is available on the portable computer.
- the portable computer can advantageously include a generic data transaction engine.
- the generic data transaction engine can include a programmable microprocessor and a generic data transaction application software program.
- a transaction session executed by the generic data transaction engine can be universally configurable so that the transaction session can occur with any particular server type by using the information contained in the portable transaction file.
- the method for performing a data transaction with the server can be described as follows.
- the method can begin by providing the portable computer with a data transaction engine comprising a generic data transaction software application.
- the generic data transaction software application can be dynamically configurable for performing a data transaction session with any server.
- the method can further include providing the portable computer with one or more portable transaction files in a predetermined portable transaction file format.
- the portable transaction file format can include two or more data fields. Each of the data fields can be provided for specifying a transaction parameter of a transaction parameter set.
- the data field definitions are advantageously sufficient to accommodate a diverse set of data transaction parameters that are sufficient to define the transaction protocol for any data transaction between the portable computer and any server.
- the invention can also concern a portable computer for performing a data transaction with a server.
- the portable computer can include a data store containing one or more portable transaction files.
- the portable transaction files can each be arranged in a predetermined portable transaction file format. This format can include two or more data fields provided for containing two or more transaction parameters.
- the transaction parameters contained in each portable transaction file can collectively define a transaction parameter set as previously described.
- the portable computer can also include a generic data transaction engine.
- the generic data transaction engine can be universally configurable responsive to the portable transaction file. More particularly, the portable transaction file can define the type specific server protocol for performing any data transaction session associated with any particular server type.
- the portable computer can also include one or more data communication systems.
- the data communication system (or systems) can be chosen for establishing a data communication link between the portable computer and the server.
- the portable computer can perform the data transaction session.
- a data transaction session can be performed by the portable computer with any server for which the portable transaction file has been provided.
- the data transaction sessions referred to herein can include one or more activities.
- the data transaction session can include communicating a set of configuration parameters from the portable computer to the server.
- the configuration parameters can define a set of operating characteristics of the server.
- the data transaction session can include communicating stored data from the server to the portable computer.
- the data transaction session can include communicating stored data from the portable computer to the server.
- the transaction parameter set described herein can include one or more parameters that are sufficient to specify the type specific server protocol.
- the data fields defined by the portable transaction file can be defined to include sufficient parameters to accommodate any server protocol. It can be desirable for the transaction parameters to specify (1) a set of connection properties required for communicating with the server, (2) a set of commands for controlling the server, (3) a sequence or ordering of requests, (4) a set of pre-conditions that should be satisfied before each request occurs (5) a set of queries for obtaining information from the server, and (6) a set of error scenario parameters .
- Fig. 1 is block diagram that is useful for understanding how one or more portable transaction files can be loaded into the memory of a portable computer.
- Fig. 2 is a block diagram that is useful for understanding how the portable computer in Fig. 1 can perform a data transaction session with a server.
- Fig. 3 is a more detailed block diagram showing how the portable computer in Figs. 1 and 2 can perform a data transaction session with one or more different types of servers .
- Fig. 4 is a flowchart that is useful for understanding a method for performing a data transaction with a server using a portable computer.
- Fig. 5 is a diagram that is useful for understanding a format of a data transaction file.
- Fig. 6 is a drawing that is useful for understanding a hierarchical relationship among a plurality of parameters in the data transaction file of Fig. ' 5.
- Fig. 7 is a flowchart that is useful for understanding a process flow in a generic data transaction engine .
- the invention concerns a method and apparatus for performing a data transaction with a server using a portable computer.
- a portable computer 106 can be provided with one or more portable transaction files 104-1, 104-2, 104-3, 104-n.
- the portable transaction files can each be arranged in a predetermined portable transaction file format. This format can include two or more data fields provided for containing transaction parameters.
- the transaction parameters contained in a portable transaction file can collectively define a transaction parameter set.
- the portable transaction files 104-1, 104-2, 104-3, 104-n can be provided to the portable computer 106 by any suitable means.
- the portable transaction files are shown being communicated directly to the portable computer 106 from computer 102.
- the portable transaction files 104-1, 104- 2, 104-3, 104-n can be communicated to the portable computer 106 over any suitable data communication link.
- the communication link can be a wired or wireless communication link between the compute 102 and the portable computer 106.
- the communication link can also be formed using a computer network (not shown) . In this regard it will be appreciated that many portable computers have the ability to access internet resources by wired or wireless means.
- Such internet , communications can be used to deliver the portable transaction files 104-1, 104-2, 104-3, 104-n from the computer 102 to the portable computer 106.
- Those skilled in the art are well familiar with the various methods by which files can be loaded onto a portable computer 106 and all such methods are intended to be included within the scope of the present invention.
- the portable computer 106 can also include a generic data transaction engine.
- the generic data transaction engine is advantageously designed so as to be universally configurable for data transactions as described herein, with any type of server.
- one of the portable transaction files 104-1, 104-2, 104-3, 104-n can define a type specific server protocol for performing a data transaction session 200 associated with a particular type of server 108.
- the portable computer 106 can include one or more components or subsystems that are arranged in a manner similar to that in conventional portable computer systems.
- the portable computer 106 can include a processor 302, a user interface, a data store 304, and a communication system 306.
- the portable computer 106 can be a personal electronic device (PED) .
- PEDs Personal electronic devices
- PEDs are well known in the art.
- PEDs are known to include mobile handheld computers, which are sometimes called personal digital assistants or PDAs. These devices have the ability to store, process and communicate data.
- PDAs generally fall into one of several categories which can include handheld PCs, palm size PCs, smart phones, and handheld instruments.
- PDAs typically include some kind of microprocessor with a commercially available operating system such as Linux, Palm OS, or Widows CE (Pocket PC) .
- Many PDAs also have built in LCD displays, touch sensitive screens, and keypads for the human/machine interface.
- Some PDAs also include wireless networking capabilities. For example, many such devices can communicate with other devices using well known wireless networking. The foregoing capabilities make these compact devices highly useful for a various business and personal applications . If portable computer 106 is a PED, then processor
- microprocessor 302 can be any of a variety of commercially available microprocessor systems that are commonly used in PEDs.
- microprocessor 302 can be selected from the StrongARM or XScale processors (e.g., SA-110 or PXA270) available from Intel Corp. of Santa Clara, CA, the i.MX or Dragonball family of processors available from Freescale Semiconductor, Inc. of Austin, Texas, or the OMAP family of processors offered for sale by Texas Instruments of Dallas, Texas.
- Processor 302 can utilize any suitable commercially available operating system.
- processor 302 can be implemented as a microelectronic controller.
- Processor 302 can communicate respectively with data store 204.
- Data store 204 can be comprised of any suitable data storage system such as flash memory, read-only memory (ROM) , EE PROM and/or dynamic random access memory (DRAM) .
- the operating system for the processor can be stored in nonvolatile memory in data store 304 or in another memory location (not shown) . Still, those skilled in the art will appreciate that the invention is not limited with regard to the particular type of data store that is used for the operating system or application software of processor 302.
- One or more portable transaction files 104-1, 104-2, 104-3, 104-n can be stored in data store 304.
- the data store can also be used for storing the generic data transaction application 303.
- one or more of data transaction files and the generic data transaction application can be stored in another data store.
- Suitable data communication links can be provided between the processor 302, data store 304, user interface 305 and communication system 306.
- the data communication links can be any suitable type serial or parallel type data channels. For example, if the communication link is a parallel type data link then it can conform to any of a number of well known bus standards, including without limitation ISA, EISA, VESA, PCI, EMIF and so on.
- serial data channel can be an I2C, SPI, Microwire, Maxim or other type serial data bus.
- the data communication system 306 can be arranged for establishing a data communication link between the portable computer 106 and one or more servers 108-1, 108-2, 108-3, 108-n.
- the communication system 306 can include communications subsystems capable of performing data communications in accordance with any of a variety of well known communications standards. Without limitation, these can include subsystem 308 that conforms to conventional universal serial bus (USB) standards, subsystem 310 that conforms to the Bluetooth wireless communication standard, subsystem 310 that conforms to a conventional serial bus standard, and subsystem 314 that conforms to the 802.11 family of wireless standards. Still, it should be understood that the invention is not limited to any particular type of communication port. Any wired, wireless and/or optical communication system can be provided. Further, it can be advantageous to provide a number of different types of communication subsystems to facilitated communications with a variety of different types of servers.
- a data transaction session can be performed by the portable computer 106 with any server 108-1, 108-2, 108-3, 108-n for which a portable transaction file 104- 1, 104-2, 104-3, 104-n has been provided.
- the server can be any type of device that is configurable, which can be loaded with certain data, or from which it can be desirable to extract data.
- the server can be any type of configurable radio equipment, another computer, a PED, a security system, or a data collection device.
- the data transaction sessions referred to herein can include one or more activities without limitation.
- the data transaction session can include communicating a set of configuration parameters from the portable computer 106 to anyone of the servers 108-1, 108-2, 108-3, 108-n for which a portable transaction file has been provided.
- the configuration parameters can define a set of operating characteristics of the server.
- the data transaction session can also include communicating stored data from the server 108-1, 108-2, 108-3, 108-n to the portable computer 106.
- the data transaction session can include communicating stored data from the portable computer 106 to the server 108-1, 108-2, 108-3, 108-n.
- the portable transaction file or files 104-1, 104-2, 104-3, 104-n can each be arranged in a predetermined portable transaction file format.
- This format can include two or more data fields provided for containing transaction parameters .
- the transaction parameters contained in a portable transaction file can collectively define a transaction parameter set.
- the transaction parameter set can include one or more parameters that are sufficient to specify the type specific server protocol.
- the data fields defined by the portable transaction file can be defined to include sufficient parameters to accommodate a protocol for any type of server 108-1, 108-2, 108-3, 108-n.
- step 402 when the portable transaction file (PTF) is provided to the portable computer 106. Once received, the portable transaction file can be stored in data store 304 until needed.
- step 406 the process can continue by checking to determine if a request has been received to begin a data transaction session. Such a request can be initiated by a user by means of user interface 305 or any other suitable method. If no request is received, the process can loop back to step 406 and wait for further instructions. However, if a request for a data transaction is received, then the process can continue on to step 408.
- PTF portable transaction file
- step 408 the generic data transaction application 303 can be initiated if the application software is not already running. Thereafter, in step 410, the user can be prompted to identify the type of server 108-1, 108-2, 108-3, 108-n for which a data transaction session is to be performed. Based on this information, a determination can be made in step 412 as to whether a portable transaction file 104-1, 104-2, 104-3, 104-n is available for the type of server that has been identified. If not, the user can be notified in step 418 that the portable computer does not have the required portable transaction file for the selected server type. The user can then be offered the opportunity in step 420 to select a different server type in step 410 or the process can terminate in step 422.
- step 314 that file can be retrieved from data store 304 and loaded into working memory for the processor 302. For example, if the user identifies the server as type 3 server 108-3, then portable transaction file 104-3 can be selected from data store 304 and loaded into memory. Thereafter, in step 416 the data transaction session can be executed by utilizing the generic data transaction application 303 and the appropriate portable transaction file for the selected server. Upon completion of the data transaction session, the process can end in step 422.
- the format for the portable transaction file must accommodate a set of parameters that are sufficient to completely define the data transaction protocol for a particular server type. In general, this means that four basic types of information must be provided for the generic data transaction program. It can be desirable for the transaction parameter set to specify (1) a set of connection properties required for communicating with the server, (2) a set of commands for controlling the server, (3) a sequence or ordering of requests, (4) a set of pre-conditions that should be satisfied before each request occurs (5) a set of queries for obtaining information from the server, and (6) a set of error scenario parameters.
- the format of the portable transaction file should be generalized to include a wide range of transaction protocols, but also should allow for a sufficient level of detail to properly implement the data transaction. Similarly, the generic data transaction application should have sufficient flexibility to implement any such data transaction protocol.
- Fig. 5 there is shown one example of a format for a portable transaction file 108-1, 108-2, 108-3, 108-n. It should be understood that the example shown in Fig. 5 is not intended to limit the invention. Instead, the format shown is merely provided to illustrate one possible way in which the set of transaction parameters could be presented. Referring to Fig. 6, it can be observed that the portable transaction file format of Fig. 5 can be arranged in a hierarchical form. According to one embodiment, the portable transaction file can be provided in the form of an XML
- each portable transaction can generally include (1) Session Information 502, (2) Connection Properties 504, and (3) Request List 506.
- the Session Information 502 can include several parameters including the Version, Author name, a Description of the transaction session, and one or more Custom Descriptors 503 that can be used to record domain specific information. These parameters can be represented as text strings or in any other convenient manner.
- the Connection Properties 504 can include several parameters, such as the TransportType, PortNumber, and the PortSpeed.
- the TransportType parameter can represent the connection medium to be used (e.g. RS-232, PPP,- Ethernet and so on) .
- the TransportType and the PortSpeed can be represented as simple text strings.
- the PortNumber can be represented as an unsigned integer.
- One or more Custom Descriptors 505 can be provided for recording domain specific information.
- the Request List 506 can include one or more different types of Requests 508 that may be necessary as part of a transaction session.
- these Requests can include, without limitation, a request to transmit certain data, to accept certain data that is being transmitted, or to configure the server for the data transaction session.
- Information about each Request 508 in the Request List 506 can be provided.
- Such information can include command text, information including preconditions, timeout and transition path as described in more detail below.
- the Request List 506 can also include an EnableLogging parameter.
- the EnableLogging parameter can be a simple Boolean operator that can be used to determine whether logging should be performed in connection with a particular request.
- the request list 506 can also include a FinalRequest ID parameter that identifies the particular request in the Request List that links to no further requests and ends a particular transaction session.
- a transition path can be specified to identify (1) a sequential identifier ID number assigned to the Request, (2) a Timeout value that specifies the length of time in milliseconds to wait after issuing a request and not receiving a response before determining a connection failure has occurred, (3) a set of Preconditions upon which the execution of the request may depend, (4) a CommandText parameter that specifies the actual text of the command to send to the server, and (4) a TransactionPath parameter that dictates the next request to execute based on the response received after the current request is executed.
- Precondition and TransitionPath parameters are described in more detail below.
- the set of Preconditions 510 can include one or more parameters including a RequestID parameter that specifies a request identification number, which number can be used for comparison against a ResponseCondition parameter.
- the ResponseCondition parameter can be a text string or other expression that can be compared by the generic transaction engine to the response of the Request denoted by the RequestID. If the expression evaluates to equivalency, then the Request can be executed. Otherwise, the request denoted by the FailureRequestID will be executed.
- FailureRequestID can be an integer ID that links to no further requests and ends a transaction session.
- the TransitionPath 512 can include several parameters, including a NexRequestID, a ResponseCondition, and a Type.
- the ResponseCondition parameter can be a regular expression that the generic transaction engine will compare to a response received from a server.
- the NexRequestID parameter can be used to specify the next request to be executed if a response received from a server corresponds to the Response parameter.
- the Type parameter can specify a type of transition. This parameter can also be expressed as a text string. The text can specify whether the transition path should be recorded in the log file as a "failure" or "success".
- the information contained in the portable transaction file in Figs. 5 and 6 can be used by the generic data transaction application software 303. Specifically, the information can be used to perform a data transaction session as per step 416 in Fig. 4. The transaction session can be performed with one or more servers 108-1, 108-2, 108-3, 108-n.
- Fig. 7 is a drawing that is useful for understanding in greater detail a process flow of a generic data transaction application 303. Referring now to Fig. 7, it can be observed that the generic data transaction application can remain in an idle state in step 702 until it is provided with a portable transaction file in step 703. In step 704, the generic data transaction application 303 can determine if the file is syntactically correct. If not, the generic data transaction application can return to its idle state and can optionally generate a suitable user notification.
- step 706 the application can wait for a control input indicating that a transaction session is to be initiated. If a "start programming" control input 708 is received, then the transaction session can continue. If not, the system remains in the idle process 706.
- step 710 a first Request 508 can be loaded from the portable transaction file 500.
- processing of the first Request 508 can begin.
- the generic data transaction application 303 can determine if each Precondition parameter 510 that is associated with a particular Request 508 has been satisfied. If a particular precondition is not satisfied, the system can load the FailureRequest ID number in step 716. The FailureRequestID can specify an alternative Request 508 to be used if the preconditions are not satisfied. If all preconditions have been satisfied, then the
- CommandText associated with the particular request 508 can be transmitted to the server 108 in step 720.
- the generic data transaction application 303 can wait for a response from the server 108. The extent of the wait period will be determined by the Timeout parameter included in the
- step 736 If a timeout occurs in step 736, then the system will proceed to step 738 and notify a user that communication with the server 108 has been lost. Alternatively, if a response 726 is received, then the system will continue on to step 724.
- step 724 a determination will be made as to whether a response is an expected response.
- the response received from the server can be compared to a Response string specified by the portable transaction file 500. If the received response is not the expected response, the application can return to the waiting condition -in step 722. Alternatively, if the response received from the server properly matches the specified Response string from TransitionPath 512, then the application can continue on to step 728.
- the generic data transaction application 303 will determine whether logging is enabled. This determination can require an evaluation of the EnableLogging parameter in the RequestList 506. If logging is enabled, then the response will be logged in step 730 before moving on to step 732. Otherwise, the system can transition directly to step 732.
- step 732 the NextRequestID number from the TransitionPath 512 can be compared to the FinalRequestID number from the RequestList 506. If the NextRequestID is equal to the FinalRequestID, then this can be an indication that the data transaction is complete. Accordingly, the system can return to its waiting state in step 706. If the NextRequestID is not equal to the FinalRequestID, then the next Request 508 can be loaded from the RequestList 506. The system can then return to step 712 and continue processing the next Request.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Hardware Design (AREA)
- Mathematical Physics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Computer Security & Cryptography (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP07749409A EP1997016A4 (en) | 2006-02-28 | 2007-01-30 | Device configuration and data extraction using a portable transaction format |
CA002643751A CA2643751A1 (en) | 2006-02-28 | 2007-01-30 | Device configuration and data extraction using a portable transaction format |
JP2008557264A JP2009529162A (en) | 2006-02-28 | 2007-01-30 | Device configuration and data extraction method using portable transaction format |
IL193742A IL193742A0 (en) | 2006-02-28 | 2008-08-28 | Device configuration and data extraction using a portable transaction format |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/363,603 US8195805B2 (en) | 2006-02-28 | 2006-02-28 | Device configuration and data extraction using a portable transaction format |
US11/363,603 | 2006-02-28 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2007106243A2 true WO2007106243A2 (en) | 2007-09-20 |
WO2007106243A3 WO2007106243A3 (en) | 2008-08-21 |
Family
ID=38445359
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2007/002346 WO2007106243A2 (en) | 2006-02-28 | 2007-01-30 | Device configuration and data extraction using a portable transaction format |
Country Status (8)
Country | Link |
---|---|
US (2) | US8195805B2 (en) |
EP (1) | EP1997016A4 (en) |
JP (1) | JP2009529162A (en) |
KR (1) | KR20080103077A (en) |
CN (1) | CN101421712A (en) |
CA (1) | CA2643751A1 (en) |
IL (1) | IL193742A0 (en) |
WO (1) | WO2007106243A2 (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10044787B1 (en) * | 2013-11-20 | 2018-08-07 | Simon Frazier | File transfer in a multi-node network |
WO2015116155A1 (en) * | 2014-01-31 | 2015-08-06 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for managing workflows for communication network provisioning |
CN106346481A (en) * | 2016-11-17 | 2017-01-25 | 北京光年无限科技有限公司 | Intelligent robot system for achieving configuration information transplanting and information transplant method |
Family Cites Families (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6272341B1 (en) * | 1995-11-30 | 2001-08-07 | Motient Services Inc. | Network engineering/systems engineering system for mobile satellite communication system |
US6310888B1 (en) | 1997-12-30 | 2001-10-30 | Iwork Software, Llc | System and method for communicating data |
GB2367670B (en) * | 1999-06-11 | 2004-08-18 | Invensys Sys Inc | Peer-to-peer hosting of intelligent field devices |
US20060235945A1 (en) * | 2000-01-14 | 2006-10-19 | Frietas Nathaniel X | Software architecture for wireless data and method of operation thereof |
US7689510B2 (en) * | 2000-09-07 | 2010-03-30 | Sonic Solutions | Methods and system for use in network management of content |
US7035932B1 (en) * | 2000-10-27 | 2006-04-25 | Eric Morgan Dowling | Federated multiprotocol communication |
AU2002234258A1 (en) * | 2001-01-22 | 2002-07-30 | Sun Microsystems, Inc. | Peer-to-peer network computing platform |
US20030050070A1 (en) * | 2001-03-14 | 2003-03-13 | Alex Mashinsky | Method and system for dynamic spectrum allocation and management |
US20030018755A1 (en) | 2001-03-30 | 2003-01-23 | Masterson Robert J. | Online system that facilitates configuration and administration of residential electronic devices |
US20020176377A1 (en) * | 2001-05-22 | 2002-11-28 | Hamilton Thomas E. | Service platform on wireless network |
US20020176378A1 (en) * | 2001-05-22 | 2002-11-28 | Hamilton Thomas E. | Platform and method for providing wireless data services |
US20040093342A1 (en) * | 2001-06-27 | 2004-05-13 | Ronald Arbo | Universal data mapping system |
AU2002365257A1 (en) * | 2001-10-26 | 2003-07-24 | Zeosoft Corporation | Development, management of distributed clients and servers |
US7155479B2 (en) * | 2002-01-30 | 2006-12-26 | Microsoft Corporation | Increasing the level of automation when configuring network services |
US20060160543A1 (en) * | 2002-03-14 | 2006-07-20 | Alex Mashinsky | Method and system for dynamic spectrum allocation and management |
JP2003302899A (en) * | 2002-04-11 | 2003-10-24 | Sony Corp | Method and apparatus for encryption and decryption messages based on boolean matrix |
WO2003100647A1 (en) * | 2002-05-21 | 2003-12-04 | Russell Jesse E | An advanced multi-network client device for wideband multimedia access to private and public wireless networks |
US20050101309A1 (en) * | 2002-05-29 | 2005-05-12 | Martin Croome | Method and apparatus for selective configuration based upon expansion card presence |
EP1674998A3 (en) | 2002-06-21 | 2013-05-22 | Sharp Kabushiki Kaisha | Information processing apparatus, information equipment, information processing system, automatic backup method, data transmission and reception method, automatic backup program, data transmission and reception program, and record medium having the programs recorded thereon |
US6941310B2 (en) * | 2002-07-17 | 2005-09-06 | Oracle International Corp. | System and method for caching data for a mobile application |
JP2004334442A (en) * | 2003-05-06 | 2004-11-25 | Mitsubishi Electric Corp | Programmable indicator |
US20050038326A1 (en) * | 2003-05-30 | 2005-02-17 | Michael Mathur | System, device, and method for remote monitoring and servicing |
US6976253B1 (en) | 2003-07-30 | 2005-12-13 | Microsoft Corporation | Method and apparatus for configuring a mobile device |
US7571227B1 (en) * | 2003-09-11 | 2009-08-04 | Sun Microsystems, Inc. | Self-updating grid mechanism |
US7111102B2 (en) * | 2003-10-06 | 2006-09-19 | Cisco Technology, Inc. | Port adapter for high-bandwidth bus |
US8341700B2 (en) * | 2003-10-13 | 2012-12-25 | Nokia Corporation | Authentication in heterogeneous IP networks |
TWI238605B (en) * | 2004-07-27 | 2005-08-21 | Quanta Comp Inc | Method for transmitting and receiving blue-tooth data and its apparatus |
US20070061488A1 (en) * | 2004-09-20 | 2007-03-15 | Trilibis Inc. | System and method for flexible user interfaces |
EP1813063A4 (en) * | 2004-11-19 | 2009-08-12 | Stevens Inst Technology | Multi-access terminal wiht capability for simultaneous connectivity to multiple communication channels |
WO2006066052A2 (en) * | 2004-12-16 | 2006-06-22 | Sonic Solutions | Methods and systems for use in network management of content |
CA2513019A1 (en) * | 2005-07-22 | 2007-01-22 | Research In Motion Limited | A method for communicating state information between a server and a mobile device browser with version handling |
US8286089B2 (en) * | 2005-12-30 | 2012-10-09 | Research In Motion Limited | Representing new messages on a communication device |
-
2006
- 2006-02-28 US US11/363,603 patent/US8195805B2/en active Active
-
2007
- 2007-01-30 CN CNA2007800135755A patent/CN101421712A/en active Pending
- 2007-01-30 WO PCT/US2007/002346 patent/WO2007106243A2/en active Application Filing
- 2007-01-30 CA CA002643751A patent/CA2643751A1/en not_active Abandoned
- 2007-01-30 KR KR1020087022556A patent/KR20080103077A/en not_active Application Discontinuation
- 2007-01-30 EP EP07749409A patent/EP1997016A4/en not_active Withdrawn
- 2007-01-30 JP JP2008557264A patent/JP2009529162A/en active Pending
-
2008
- 2008-08-28 IL IL193742A patent/IL193742A0/en unknown
-
2012
- 2012-04-05 US US13/440,100 patent/US8392537B2/en active Active
Non-Patent Citations (1)
Title |
---|
See references of EP1997016A4 * |
Also Published As
Publication number | Publication date |
---|---|
KR20080103077A (en) | 2008-11-26 |
CA2643751A1 (en) | 2007-09-20 |
WO2007106243A3 (en) | 2008-08-21 |
US8195805B2 (en) | 2012-06-05 |
US8392537B2 (en) | 2013-03-05 |
US20120191822A1 (en) | 2012-07-26 |
EP1997016A4 (en) | 2009-06-24 |
US20070204053A1 (en) | 2007-08-30 |
EP1997016A2 (en) | 2008-12-03 |
CN101421712A (en) | 2009-04-29 |
IL193742A0 (en) | 2009-05-04 |
JP2009529162A (en) | 2009-08-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8433655B2 (en) | Software installation system and method | |
CN101997908B (en) | Application program method for down loading, application program supplying method, with its user terminal | |
CN108376079B (en) | Automatic application updates | |
US20130326502A1 (en) | Installing applications remotely | |
US20090183151A1 (en) | Obtaining Software for a Handheld Device | |
US8402151B2 (en) | Dynamic communication stack | |
CN110473104B (en) | Transaction processing method and related equipment | |
KR20120089000A (en) | Apparatus and method for providing application auto install function in digital device | |
JP2010198341A (en) | Authentication processing program and device | |
JP2012079061A (en) | Communication apparatus and management method | |
CN103294464A (en) | Apparatus and method for verifying operating system of host device in portable terminal | |
CN103685515A (en) | Method and system for downloading application | |
WO2023030265A1 (en) | Control method and electronic device | |
US8392537B2 (en) | Device configuration and data extraction using a portable transaction format | |
CN102937963A (en) | Template and server content download using protocol handlers | |
KR20070095530A (en) | Method for providing patch data to client terminals and game providing system of enabling the method | |
US20030140146A1 (en) | Method and system for interconnecting a Web server with a wireless portable communications device | |
JP7230951B2 (en) | Mobile terminal, information processing system, control method, and program | |
CN107535013B (en) | Service processing method and terminal | |
CN107229661B (en) | Payment method and device | |
US20160203009A1 (en) | Methods for emulating computing devices and devices thereof | |
CN113886047A (en) | Task processing method and device | |
Haque et al. | J2ME Enterprise Development | |
JP2011086016A (en) | Method of controlling program download | |
CN114911543A (en) | Data processing method and device, computer equipment and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2643751 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2008557264 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 193742 Country of ref document: IL Ref document number: 4570/CHENP/2008 Country of ref document: IN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020087022556 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007749409 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 200780013575.5 Country of ref document: CN |