CN1434942A - Abstract device driver model for the portability of device drivers across different operating system platforms - Google Patents
Abstract device driver model for the portability of device drivers across different operating system platforms Download PDFInfo
- Publication number
- CN1434942A CN1434942A CN00819068A CN00819068A CN1434942A CN 1434942 A CN1434942 A CN 1434942A CN 00819068 A CN00819068 A CN 00819068A CN 00819068 A CN00819068 A CN 00819068A CN 1434942 A CN1434942 A CN 1434942A
- Authority
- CN
- China
- Prior art keywords
- device driver
- operating system
- client
- interface
- terminal
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 claims description 20
- 230000008569 process Effects 0.000 claims description 4
- 230000006855 networking Effects 0.000 claims 1
- 238000004891 communication Methods 0.000 abstract description 8
- 238000006243 chemical reaction Methods 0.000 description 6
- 238000011161 development Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 4
- 230000001360 synchronised effect Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 239000012084 conversion product Substances 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000004886 process control Methods 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/10—Program control for peripheral devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/10—Program control for peripheral devices
- G06F13/102—Program control for peripheral devices where the programme performs an interfacing function, e.g. device driver
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Telephone Function (AREA)
- Computer And Data Communications (AREA)
Abstract
An abstract interface model for device drivers in a set-top terminal, such as for use in a cable or satellite television subscriber network. In a layered software architecture, a device driver abstract interface model allows communication between a client (112, 212) and the device driver (154, 254) regardless of the operating system (OS) under which the device driver operates. In a first embodiment, the architecture includes a dedicated (OS-specific) device driver interface (132), and a proxy uses a first abstract interface (122) to convert interface service requests from a client (112) into OS-specific calls to the device driver (154). For a client that directly accesses a dedicated (OS-specific) device driver interface (132), a second abstract interface (152) is used to convert the interface service requests into OS-specific calls to the device driver (154). Direct access to the OS-specific device driver interface (132) is therefore maintained.
Description
Background of invention
The invention relates to digital video switching software/firmware field, be used for the such user network of CATV (cable television) or satellite television.The device driver that it is in particular set-top terminal provides the abstraction interface model.
Recently, the appearance of digital set-top terminal has stimulated the growth of the such user's TV network of cable TV network/satellite television network.These terminals can make the layer of program service increase, and support many software applications and function, as electronic program list, stock or weather vertically hung scroll (banner), home buying and bank service, recreation or the like.In addition, this trend is expected to continue development, converges and promote the growth of computer network in the family with phone, TV and computer network.
Each terminal comprises multiple hardwares equipment, for example, tuner, detuner, MPEG-2 code translator (as audio frequency, video and data), video encoder, Audio mixer or the like, they are respectively by separately driving process control.
In addition, each terminal is used an operating system platform control terminal function.Operating system has a hierarchy (hierarchical structure), and function wherein is not both independently according to level of abstraction.In the bottom of structure, minimum level of abstraction (abstract level) or level (layer) are hardware layers.Last layer is a device driver layer.At the top of structure, typically the highest level of abstraction is a client layer.In addition, each layer-management one group objects (object) can be that item of hardware can be a software object also, and be defined in the operation of carrying out on the object.
But, must realize device driver respectively to each operating system platform (for example, different video conversion manufacturers, perhaps the different video transformation model of same manufacturer) traditionally.In addition, for supporting the different operating system platform may also can need an independent hardware platform.Even different terminals that might consolidated network will have different operating system.
The continuous change of operating system is normally caused by improvement, cost reduction, New Parent and second source manufacturer in the set-top terminal.Just there is a problem in this, even because each network all only uses single operating system platform, the different operating system that manufacturer terminal also is necessary for heterogeneous networks generates different device drivers.The device driver of the operating system of a network can not be transplanted (migrate) at an easy rate in the operating system of another network.
Exploitation also provides terminal device driver software/firmware meeting extra increase manufacturer terminal of renewal and network supplier's expense.
Specifically, the device driver of specific operation system combines very closely with operating system, this just means that driver has comprised the specific details of operating system in whole implement process, and therefore the exploitation driver all needs a complete construction cycle under each operating system platform.
Along with development of technology, terminal is constantly upgraded and is upgraded, and it is complicated more that this problem becomes.
Therefore, provide a device driver abstraction interface model to suit the requirements.This model makes us can develop the equipment user's code that compiles and carry out under single one group of device driver code (code) and the various video conversion operations system.This interface should allow the device driver under a plurality of operating systems and the video conversion platform only realize once.The suitable platform that the DCT5000 series terminal comes to this is by patent possessor general instrument Corp. (General Instrument Corporation) production herein.
Interface should allow the two-way communication between device driver and the client.
No matter which kind of operating system hardware device moves, and interface should guarantee hardware device looks it is identical (for example, no matter which kind of application program or other entity (entity) communicate with equipment) to terminal client.Similarly, no matter use which kind of operating system, for the physical device driver, the client looks it also should is identical.
Interface should make the architecture (architecture) and the code sharing of crossing over operating system platform and hardware platform.
Interface should can be used all operations system, and no matter whether this system has special-purpose (operating system is specific) device driver interface.
Interface should use object-oriented or processor-oriented programming language to realize.
Device driver abstraction interface model provided by the invention just has above advantage and other advantage.
Brief summary of the invention
Discussion of the present invention be the abstraction interface model of device driver in the set-top terminal.
The present invention makes driver core logic (core logic) only need exploitation once.Core need compile respectively at each operating system platform.
In a special embodiment, the invention provides the method that communicates between the device driver of a kind of client and terminal, here terminal has relevant specific operating system, and device driver operates under this system.This method comprises the step that first abstraction interface is provided, and this interface will have customer service request with the form of operating system independent and be converted to call (call) with device driver of being compatible with the specific operation system form.
Especially, first abstraction interface is adapted for can provide calling of any form (every kind of format compatible in corresponding operating system) separately for device driver.
Had after the device driver interface of special-purpose (operating system is specific), the device driver interface directly comes from other client's (having the form that is compatible with specific operation system) second and calls through revising to receive.Second calls not by the first abstraction interface transmission.Further, the device driver interface provides second to call by second abstraction interface to device driver.
(here terminal has relevant specific operating system to make a kind of correlation technique that can communicate between the device driver of client and terminal, device driver runs under this system) comprise the step that first abstraction interface is provided, the information (having the specific operation system form) that this interface will come from device driver is converted to the corresponding information (with the form of operating system independent) that the client uses.
First abstraction interface through modification can with information from any form (every kind format compatible in corresponding operating system) separately be converted to the client that use with form operating system independent.
The present invention also illustrates corresponding instrument.
Description of drawings
Fig. 1 example the device driver abstraction interface model that uses of the operating system that has the specialized device driver interface described of the present invention.
Fig. 2 example the device driver abstraction interface model that uses of the operating system that does not have the specialized device driver interface described of the present invention.
Embodiment
Discussion of the present invention be the abstraction interface model of device driver in the set-top terminal.
Famous Object-Oriented Design technology provides a kind of method of abstract establishment object.The deviser can create the object that abstraction interface is provided and the details that do not need to be directly acquainted with object illustration (instantiation).This dynamically takes place when running software.
The present invention extends in the following manner or has revised this notion.For all operating system is only created a USBDI.This finishes when compile source code and only carries out once (statically).
Therefore, when new operating system platform of exploitation, only need the supports of development and agency (proxy), operating system particular driver and operating system particular driver.In typical case this need the construction cycle 1/10th or still less, therefore can save a large amount of time and cost.
Specifically, all device driver logics all are arranged in control of device driver core or realization therein.This module (module) or subsystem near hardware device level and with the hardware device direct communication, perhaps under the operating system particular driver is supported the assistance of subsystem, communicate by letter with hardware device.Notice that core control comprises the most of code in this architecture.
The control of device driver core is implemented in the logic that defines in the device driver abstraction interface.The service that this interface definition driver must provide.Core control comprises need provide all of these services codes.
Fig. 1 example the device driver abstraction interface model that uses of the operating system that has the specialized device driver interface described of the present invention.This specialized equipment routine interface 130 may be the Windows CE of Microsoft (tm).
The device driver model 100 of layering comprises levels such as 110,120,130,140,150 and 160.Operating system only needs to realize a driver for its interface on one deck in typical case.Bottom 160 is minimum level of abstractions, and it comprises hardware device itself 162 in the set-top terminal.
Next level of abstraction 150 comprises the second device driver abstraction interface 152, the control 154 of device driver core and operating system particular driver support 156.Next level of abstraction 140 comprises that the operating system particular driver realizes 142.Next level of abstraction 130 comprises operating system device driver interface 132.
Next level of abstraction 120 comprises the first device driver abstraction interface 122 and device driver agency 124.
Next level of abstraction 110 is top, and it comprises the client 112 who uses device driver abstraction interface 122 and uses the user 114 of operating system device driver interface 132.
Notice that though only shown an equipment among the figure, the present invention is applicable to the equipment of any amount in the set-top terminal.
In the architecture of Fig. 1, operating system particular device driver 142 uses the second device driver abstraction interface 152 to control or driving arrangement driver core control 154.Especially, 140 these one decks device driver that operating system is specific that has operating system particular device driver 142 is called (combining with specific operating system), changes or is transformed to the abstract device driver of device driver abstraction interface 152 definition and call.
The USBDI 132 that operating system itself defines by operating system is called the service in the specific device driver of (invoke) operating system 142.For example, operating system may be Microsoft (tm) Windows CE.It is calling of " xxx_IOCTL " that this operating system is called the interior form of Windows CE device driver, and wherein " xxx " represents the WindowsCE device name.
Windows CE is an example about the driving invocation of procedure, and wherein proxy call " equipment input and output control " (" DeviceIoControl ") is called and transmitted Win CE device name.
For client 112, device driver agency 124 uses abstraction interface 122 to replace device driver 154, and this abstraction interface device driver interface 152 with device driver core control 154 realizations on function is identical.These clients comprise middleware (middleware) and application program or the like.Therefore, seem the client well as and if driver core itself between directly have interface.In addition, agency 124 will change or transform to the specific system equipment of the operating system related with it from client 112 interface service request.
In addition, abstraction interface 122,152 is handled by the communication data of driver to the client, and these data can be synchronous (synchronous), also can be asynchronous (asynchronous).For synchronous communication, driver 154 only provides data for it when client's 110,114 requests., in the communicating to connect of driver, stride across the operation system driver border as described in the data picture and transmit the client.
Asynchronous communication is in not request of client, and driver takes place when sending customer data (for example information) again.Note driver only notify the client it these data are arranged, client's retrieve data synchronously then.May be summarized to be following a few step:
1. driver will be to client's Data transmission.
2. driver sends signal to the client asynchronously by an incident.
3. the client sends synchronous operation and retrieves (retrieve) data or reading of data.
Say that briefly the device driver agency 124 abstraction interface requests that will come from client 110 are converted to the specific device driver system call of operating system.Operating system is then called (invoke) operating system particular driver then.Operating system particular driver 142 will ask to change back the USBDI request, promptly identical with calling of client's original execution interface interchange.In device driver core 154, carry out this request.
At last, the external client can select two interface paths when access driver.At first, abstraction interface 122,152 can use in internal customer's (for example client of video conversion manufacturer exploitation) mode, for example the client among Fig. 1 112.Secondly, can directly use the operation system driver interface, as the client among Fig. 1 114.
The external client is meant the outside of video conversion manufacturer.The external client comprises that needs use the entity of manufacturer's driver, for example middle unit development merchant as the SanCarlos of Liberate Technologies (tm), California, USA or the operating system developer as Microsoft.
Fig. 2 example the device driver abstraction interface model that uses of the operating system that does not have the specialized device driver interface described of the present invention.
Following one deck 210 comprises the client 212 who uses abstraction interface 252.
Especially, Fig. 2 refers to and comprises the not video conversion system of the operating system of carrying device USBDI.The VRTX operating system of the Mentor Graphics company of U.S. Oregon state Wilsonville for example.
When operating system did not need to use the special purpose operating system special interface, the architecture of this layering had been compressed (for example, the number of plies of Xu Yaoing still less).Here, be again that client 212 uses device driver abstraction interface 252 to inspect device driver 254.But the client directly is connected with driver core 254.It is available not having only abstraction interface 252 under the operating system with the specific drivers interface.
Similarly, device driver 254 is inspected (view) client by means of interface 252, realizes two-way communication.
Therefore as can be seen, the present invention provides an abstraction interface model for the device driver of set-top terminal.
Advantage of the present invention is as follows.For the client who uses abstraction interface, device driver looks it is identical.Do not need to develop the client again for each operating system.In addition, the client can not differentiate or see the difference (seeing Fig. 1 and Fig. 2) that two different operating systems are realized.Driver looks it is identical.Crucial problem is the abstraction interface that a client is only developed in the driver support, and can cross over operating system and use.
In addition, for the control of driver core, the client looks it is identical.Core logic can not differentiate use abstraction interface/agency the client, use not with the difference between the client of the client of abstraction interface/agency's operation system driver interface or direct access core, as Fig. 2.
Driver core control subsystem is to realize in the mode that is independent of operating system.In typical case, this subsystem needs a large amount of development (for example, all Driver Development need reach for 90% man-hour).But, use because driver core control subsystem of the present invention only needs exploitation once also can cross over operating system platform, so this abstract device driver model can shorten the time that the new video conversion products comes into the market widely.
In addition, the present invention allows the use of alternate device driver user interface.
Though about description of the invention is various specific concrete modes, those skilled in the art should understand, can be according to carry out multiple extra modification and correction in invention scope of illustrating and the essence in claim of the present invention.
For example, though what invention was discussed is about CATV (cable television) or satellite television broadband communication network, but it also can be used for other network, as Local Area Network, Metropolitan Area Network (MAN) (MAN), wide area network (WAN), Internet (internet), in-house network (intranet) and Internet (Internet) or their combination.
In addition, invention can use any known hardware, firmware and/or software engineering to realize.
Claims (15)
1. can method for communicating between the device driver that makes in a client and the terminal, wherein this terminal has relevant specific operating system, this device driver operates under this system, the method includes the steps of: first abstraction interface is provided, to have services request with the form of operating system independent from this client, be converted to calling device driver with the form that is compatible with this specific operation system.
2. according to the method for claim 1, comprise further step:
Use this first abstraction interface, this interface will come from the information that device driver has this specific operation system form, be converted to that this client uses one with the corresponding information of the form of operating system independent.
3. according to the process of claim 1 wherein:
This terminal is the user's television terminal in the network.
4. according to the process of claim 1 wherein:
This terminal is in the broadband connections networking.
5. according to the process of claim 1 wherein:
This first abstraction interface is adapted for to device driver provides this to call with any form of a plurality of forms of being compatible with separately corresponding different operating system.
6. according to the method for claim 1, comprise further step:
Provide this to call by this device driver interface to this device driver according to the specific operation system operation.
7. according to the method for claim 6, wherein:
This device driver interface is adapted for reception and directly comes from one of other client and have second of the form that is compatible with this specific operation system and call; And
This device driver interface provides this second to call by one second abstraction interface to this device driver.
8. according to the method for claim 6, wherein:
This first abstraction interface is adapted for by this device driver interface provides this to call for device driver with any form of a plurality of forms of being compatible with separately corresponding different operating system.
9. according to the method for claim 6, comprise further step:
One second abstraction interface is provided, will comes from the information that device driver one has the form that is compatible with specific operation system, be converted to client's corresponding information with form operating system independent that use.
10. according to the method for claim 9, comprise further step:
By this first abstraction interface provide this client that use with this information this operating system independent.
11. method according to claim 9, wherein: this second abstraction interface be adapted for will give this client information from being compatible with any form of a plurality of different-formats of corresponding different operating system separately, be converted to the client that use with form operating system independent.
12. one kind makes the instrument that can communicate between the device driver of a client and a terminal, this terminal has relevant specific operating system, device driver runs under this system, comprise: provide first abstraction interface to have services request with the form of operating system independent, be converted to the device that calls with the device driver that is compatible with this specific operation system form from this client.
13. one kind makes the method that can communicate between the device driver of client and terminal, this terminal has relevant specific operating system, device driver runs under this system, comprise following steps: provide first abstraction interface, to come from this device driver one and have the information of specific operation system form, be converted to client's corresponding information with form operating system independent that use.
14. method according to claim 13, wherein: this second abstraction interface be adapted for will give this client information from being compatible with any form of a plurality of different-formats of corresponding different operating system separately, be converted to the client that use with form operating system independent.
15. one kind makes the instrument that can communicate between the device driver of a client and a terminal, this terminal has relevant specific operating system, device driver runs under this system, comprise: provide first abstraction interface will come from the information that device driver has this specific operation system form, be converted to client's corresponding information with form operating system independent that use.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US46804799A | 1999-12-21 | 1999-12-21 | |
| US09/468,047 | 1999-12-21 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN1434942A true CN1434942A (en) | 2003-08-06 |
Family
ID=23858234
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN00819068A Pending CN1434942A (en) | 1999-12-21 | 2000-12-06 | Abstract device driver model for the portability of device drivers across different operating system platforms |
Country Status (7)
| Country | Link |
|---|---|
| EP (1) | EP1287436A2 (en) |
| JP (1) | JP2003521027A (en) |
| KR (1) | KR20020073481A (en) |
| CN (1) | CN1434942A (en) |
| AU (1) | AU4310001A (en) |
| CA (1) | CA2395468A1 (en) |
| WO (1) | WO2001046819A2 (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100343803C (en) * | 2004-07-26 | 2007-10-17 | 国际商业机器公司 | Method and syste mfor transplanting prsonalized computation environment from source platform to target platform |
| CN100351788C (en) * | 2005-05-18 | 2007-11-28 | 大唐移动通信设备有限公司 | Drive method for embedded apparatus |
| CN100454238C (en) * | 2005-04-28 | 2009-01-21 | 上海贝尔阿尔卡特股份有限公司 | DOHM software interface irrelevant with apparatus object |
| CN101163074B (en) * | 2007-11-12 | 2010-12-08 | 中兴通讯股份有限公司 | WiMAX terminal equipment mainframe driving method |
| CN101627377B (en) * | 2007-03-09 | 2011-12-28 | 微软公司 | Abstracting operating environment from operating system |
| CN102467381A (en) * | 2010-11-16 | 2012-05-23 | 北京中电华大电子设计有限责任公司 | Implementation method for wireless local area network (WLAN) driver |
| CN101615125B (en) * | 2008-06-24 | 2012-09-19 | 纬创资通股份有限公司 | Agent drive method of video device and module thereof |
| CN102707983A (en) * | 2011-03-23 | 2012-10-03 | 微软公司 | Automated generation of client/driver communication interfaces |
| CN106878467A (en) * | 2017-04-07 | 2017-06-20 | 同方威视技术股份有限公司 | The method and tele-control system of remote control equipment |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6139603A (en) * | 1989-02-22 | 2000-10-31 | L'air Liquide, Societe Anonyme Pour L'etude Et L'exploitation Des Procedes Georges Claude | Process for recovering oxygen |
| US7676814B2 (en) * | 2004-03-25 | 2010-03-09 | Globalfoundries Inc. | Four layer architecture for network device drivers |
| US20070067499A1 (en) * | 2005-09-08 | 2007-03-22 | Honeywell International Inc. | Systems and methods for satellite payload application development |
| US8046570B2 (en) | 2007-02-06 | 2011-10-25 | Microsoft Corporation | Supporting multiple operating systems in media devices |
| FR2930058B1 (en) * | 2008-04-14 | 2010-06-11 | Bull Sas | PORTABLE DEVICE AND METHOD FOR EXTERNALLY STARTING A COMPUTER INSTALLATION |
| CN103164207B (en) * | 2011-12-16 | 2016-09-07 | 深圳市快播科技有限公司 | The application development method and system across hardware platform based on Android system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5878237A (en) * | 1997-07-11 | 1999-03-02 | Compaq Computer Corp. | Apparatus, method and system for a comuter CPU and memory to PCI bridge having a pluarlity of physical PCI buses |
-
2000
- 2000-12-06 EP EP00992393A patent/EP1287436A2/en not_active Withdrawn
- 2000-12-06 JP JP2001547266A patent/JP2003521027A/en active Pending
- 2000-12-06 CA CA002395468A patent/CA2395468A1/en not_active Abandoned
- 2000-12-06 AU AU43100/01A patent/AU4310001A/en not_active Abandoned
- 2000-12-06 CN CN00819068A patent/CN1434942A/en active Pending
- 2000-12-06 WO PCT/US2000/042614 patent/WO2001046819A2/en not_active Application Discontinuation
- 2000-12-06 KR KR1020027007954A patent/KR20020073481A/en not_active Application Discontinuation
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100343803C (en) * | 2004-07-26 | 2007-10-17 | 国际商业机器公司 | Method and syste mfor transplanting prsonalized computation environment from source platform to target platform |
| CN100454238C (en) * | 2005-04-28 | 2009-01-21 | 上海贝尔阿尔卡特股份有限公司 | DOHM software interface irrelevant with apparatus object |
| CN100351788C (en) * | 2005-05-18 | 2007-11-28 | 大唐移动通信设备有限公司 | Drive method for embedded apparatus |
| CN101627377B (en) * | 2007-03-09 | 2011-12-28 | 微软公司 | Abstracting operating environment from operating system |
| CN101163074B (en) * | 2007-11-12 | 2010-12-08 | 中兴通讯股份有限公司 | WiMAX terminal equipment mainframe driving method |
| CN101615125B (en) * | 2008-06-24 | 2012-09-19 | 纬创资通股份有限公司 | Agent drive method of video device and module thereof |
| CN102467381A (en) * | 2010-11-16 | 2012-05-23 | 北京中电华大电子设计有限责任公司 | Implementation method for wireless local area network (WLAN) driver |
| CN102707983A (en) * | 2011-03-23 | 2012-10-03 | 微软公司 | Automated generation of client/driver communication interfaces |
| CN102707983B (en) * | 2011-03-23 | 2017-03-01 | 微软技术许可有限责任公司 | The automatically generating of client/driver communication interface |
| CN106878467A (en) * | 2017-04-07 | 2017-06-20 | 同方威视技术股份有限公司 | The method and tele-control system of remote control equipment |
| CN106878467B (en) * | 2017-04-07 | 2023-06-16 | 同方威视技术股份有限公司 | Method for remotely controlling equipment and remote control system |
Also Published As
| Publication number | Publication date |
|---|---|
| EP1287436A2 (en) | 2003-03-05 |
| KR20020073481A (en) | 2002-09-26 |
| JP2003521027A (en) | 2003-07-08 |
| AU4310001A (en) | 2001-07-03 |
| WO2001046819A2 (en) | 2001-06-28 |
| CA2395468A1 (en) | 2001-06-28 |
| WO2001046819A3 (en) | 2002-11-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1434942A (en) | Abstract device driver model for the portability of device drivers across different operating system platforms | |
| CN1142513C (en) | Dynamic content supplied processor | |
| CN1298151C (en) | Method and equipment used for obtaining state information in network | |
| CN100345415C (en) | Method and apparatus for perfoming boot, maintenance, or install operations on a storage area network | |
| CN1949731A (en) | Method and apparatus for providing home network device service to an external device | |
| CN1819576A (en) | Client / server application task allocation method and application serving system | |
| CN1716897A (en) | Be used to drive the client apparatus of remote user interface | |
| CN1720703A (en) | Session-return enabling stateful web applications | |
| CN101411146A (en) | Method for consuming heterogenous services on heterogeneous devices using script plugins | |
| CN1969280A (en) | Remote system administration using command line environment | |
| CN1703098A (en) | Methods, circuits and computer program products for syntax parsing | |
| CN1492352A (en) | System and method for far distance WEB service cloning and example | |
| CN1779634A (en) | Device and method for enhancing output display of portable apparatus | |
| CN1270229C (en) | Method of realizing cross address space establishing construction member target based on dynamic core | |
| CN1791105A (en) | Controlling execution of files transmitted to clients and data updating | |
| CN111625293A (en) | Terminal dual system based on linux kernel and hardware access management method thereof | |
| CN1714339A (en) | Layered architecture for mobile terminals | |
| CN1635781A (en) | A method for uniform processing of digital television receiver middleware messages | |
| CN1499774A (en) | Method for generating telecommunication network management interface | |
| CN1764187A (en) | The equipment and the method that are used for the socket communication between the application of operating system | |
| CN1863212A (en) | Implementing method of distributed middleware system based on IP data network | |
| CN100341270C (en) | Method for reflecting task progress of message based distributed platform client | |
| US20080134157A1 (en) | Approach and System for Process Execution of an Integrated Telecom Platform | |
| CN1251079C (en) | Method for realizing data interaction between different systems | |
| CN1525714A (en) | An ASN.1 protocol processor |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |