US20030182472A1 - Synchronization scheme - Google Patents
Synchronization scheme Download PDFInfo
- Publication number
- US20030182472A1 US20030182472A1 US10/102,169 US10216902A US2003182472A1 US 20030182472 A1 US20030182472 A1 US 20030182472A1 US 10216902 A US10216902 A US 10216902A US 2003182472 A1 US2003182472 A1 US 2003182472A1
- Authority
- US
- United States
- Prior art keywords
- management
- state
- device state
- management processes
- management process
- 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.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/04—Generating or distributing clock signals or signals derived directly therefrom
- G06F1/12—Synchronisation of different clock signals provided by a plurality of clock generators
Definitions
- This invention relates to synchronization schemes.
- Some electronic devices support device management interfaces that allow configuration, monitoring, and control of the devices. For example, users may directly interact with management interfaces through switches, menu, or command line interface. In other instances, software management programs interact with a management interface of the devices. In some cases, multiple users, either directly or via management programs, may simultaneously or alternately interact with the electronic devices.
- the invention features querying a managed device to obtain an initial device state, synchronizing the device state in a plurality of management processes, detecting a change in the device state, and maintaining a synchronized current device state between the managed device and the plurality of management processes.
- Embodiments may include one or more of the following.
- the plurality of management processes may reside in remote systems. Maintaining may include, for each management process, storing a current device state in the management processes. Storing may include integrating an incremental device state change into information stored in a management process.
- Synchronizing may include determining whether synchronization already exists between a managed device and a management process, and establishing a synchronization if synchronization does not already exist.
- Determining may include comparing a sequence number identifying a current device state with a previously stored sequence number.
- Establishing may include a device-dominant process that includes modifying information stored in a management process to match a current state of the managed device.
- Establishing may include a management process-dominant process that includes modifying a current state of the managed device to match information stored in one of the management processes.
- detecting may include receiving a device state change message from a managed device.
- the change may be in response to a remote user command, a local user command and/or a command from one of the management processes.
- Embodiments may have any of the following advantages.
- the method enables a management process to remain cognizant of the state of a managed device in the presence of management changes applied to the device by other management processes or users.
- the management process continues to possess up-to-date and synchronized information pertaining to a state of the device. This enables correct management of the device by the management process in the presence of the changes made by other management processes or users.
- management processes do not inadvertently overwrite changes to the device state made by other management processes or users.
- Each management process serves as redundant backups without requiring direct communication between each other.
- Each management process is made “aware” of changes to the device state via information and updates sent directly by the managed device itself to the management process. This eliminates software complexity that otherwise would result by a system lacking such features.
- FIG. 1 is a block diagram of a system.
- FIG. 2 is a flow diagram of a synchronization process.
- FIG. 3 is part of the flow diagram of FIG. 2.
- FIG. 4 is part of the diagram of FIG. 2.
- FIG. 5 is a diagram of a router synchronization system.
- a device synchronization system 10 includes a managed device 12 , such as a network switch, connected to computer systems 14 a - 14 b via communications channels 16 a - 16 b .
- Management processes 18 a and 18 b reside in computer systems 14 a , 14 b , respectively and are programs that support configuration, control, and monitoring of the managed device 12 .
- a local user 20 a and/or remote user 20 b can also provide support and control for configuring, controlling, and monitoring the managed device 12 .
- the users 20 a , 20 b can reset, configure, and input any information such as data commands into the managed device 12 .
- the remote user 20 b interacts with the managed device 12 via the communication channel 16 c and the local user 20 a interacts directly with the managed device 12 through a local user interface (UI) 24 .
- UI local user interface
- the user interface (UI) 24 may be a command line interface, a keyboard or mouse.
- the remote user 20 b and management processes 18 a - 18 b interact with the managed device 12 via a remote management interface 26 linked to the communication channels 16 a - 16 c.
- a synchronization process 30 residing in a management process 18 within the device synchronization system 10 features a feedback mechanism used to synchronize events such as configuration, set, reset, control, and monitoring events between the managed device 12 and the management processes 18 a - 18 b .
- the process 30 begins ( 32 ) at a start phase by establishing ( 34 ) communications between the managed device 12 and each of the management processes 18 .
- the synchronization process 30 is executed simultaneously and independently by any number of management processes 18 a - 18 b , for example.
- Device state information may include, for example, configuration information and control information.
- the synchronization process 30 continues by updating ( 38 ) the device state information in the management processes 18 a , 18 b .
- the management process 18 waits ( 40 ) to detect a device state change announcement from the device 12 .
- a device state change announcement For example, configuration and/or control information may change in the device 12 .
- the announcement may be via, for example, a network message.
- the state changes in the device 12 may have arisen from the management process 18 a itself or from any other source in the system 10 , such as management process 18 b or user 20 .
- the management process 18 a integrates ( 46 ) the state changes of the device 12 by process 30 into device state information residing in management process 18 a within the computer system 14 a . After the state changes are integrated ( 46 ), the process 30 waits ( 40 ) for a device state change.
- the management process determines ( 50 ) whether this management process 18 a has been in contact with the managed device 12 since the management process 18 a has been started. If the management process 18 a has not been in contact with the managed device 12 previously, the full current device state is retrieved and integrated ( 52 ) into device state information residing in management process 18 a within the computer system 14 a.
- a determination ( 54 ) of whether the device state has changed since the last communication is made. If changes have occurred in the device state, then the full current device state is retrieved and integrated ( 52 ) into device state information residing in the management process 18 a , as described above. This retrieval and integration ( 52 ) constitutes re-synchronization. If no changes have occurred in the device state, re-synchronization is suppressed and the process 30 continues ( 38 ) updating of the device state information in the management process 18 a.
- the device 12 can maintain a sequence number on the device state and increment the sequence number each time the device state changes.
- the device 12 can be subject to state changes brought about by not only various management processes such as management processes 18 a - 18 b , but users 20 a , 20 b can also directly subject device 12 to state changes, or state changes may occur not caused by management action.
- the device state sequence number when retrieved by the management process 18 a and compared to a value stored previously, allows the management process 18 a that has been out of contact with the device 12 to readily discover upon regaining connection with the device 12 whether the management process is still up-to-date with the current state of the device 12 .
- This discovery constitutes the determination ( 54 ) of whether the device state has changed since the management process 18 a last communicated with the device 12 .
- further optimization can allow the management process 18 a to retrieve only recent changes to the device state, rather than retrieving the entire current state.
- FIG. 4 another optimization of the synchronization process 30 described above in conjunction with FIG. 3 is shown.
- the re-synchronization determination stage 56 as described above is executed. If re-synchronization is required ( 52 ), the management process 18 a enters a mode optimization process ( 58 ).
- the mode optimization process ( 58 ) determines which of two re-synchronization modes, i.e., a device-dominant mode and a management process-dominant mode, was previously selected.
- the current state of the device 12 supercedes and overwrites any and all information held by the management process 18 a should any conflict arise between the information exchanged between the device 12 and the management process 18 a .
- the management process 18 a retrieves and integrates the full current device state.
- the management process 18 a puts the device 12 to the desired state, for example, by retrieving the full current device state, computing the changes to the device state to match the device state to the state that has been stored in the management process 18 a and then applying and forwarding those changes to the device 12 .
- the synchronization process 30 continues updating ( 38 ) of the device state information in the management process 18 a.
- the process 30 coordinates the various management processes that are modifying the device state. Further, whenever any relevant management operations are performed on the device 12 , or other state changes of interest occur to the device 12 , the device 12 reports this change to all management processes participating in the multiway synchronization.
- FIG. 5 illustrates an example of a managed device 12 in a router synchronization system 70 that includes a managed device 72 (e.g., an Internet Protocol (IP) router) and associated computer systems 74 a - 74 c and management processes 76 a - 76 c residing within the computer systems 74 a - 74 c .
- the management processes 76 a - 76 b employ the synchronization process 30 .
- the management process 76 c residing on computer system 74 c does not participate in the synchronization process 30 .
- a set of configuration parameters of the IP router device 72 constitutes device state information.
- the management processes 76 a - 76 c are coupled to the IP router device 72 via communications channels 78 a - 78 c , respectively, that link the management processes 76 a - 76 c with the remote management interface 80 .
- the IP router device 72 supports a command line interface (CLI) 82 that may be accessed locally by the user 84 , or remotely over a network 88 (e.g., the Internet) using, for example, the telnet protocol by remote user 86 .
- CLI command line interface
- the users 84 and 86 as well as the management processes 76 a - 76 c manipulate the IP router device 72 state, such as router configuration state, by issuing commands to the IP router 72 .
- the IP router device 72 provides a mechanism for determining whether the IP router 72 configuration state has changed, based on a sequence number assigned by the IP router device 72 to each version of that state.
- the management processes 76 a - 76 b use that sequence number to determine whether a device state has changed since the last communication between the management processes 76 a - 76 b and the IP router device 72 .
- the management processes 76 a - 76 b can also retrieve the full current IP router device 72 configuration state. Additionally, if a relevant management operation is performed on the IP router device 72 , or other state change of interest occurs in the IP router device 72 , the IP router device 72 reports the change to all management process instances 76 a - 76 b participating in the multi-way synchronization.
- Application of the synchronization system 70 enables the management processes 76 a - 76 b to correctly and robustly manage the IP router device 72 even in the presence of direct management actions taken by local user 84 or remote user 86 at the CLI interface 82 of the IP router device 72 , management actions taken by other management process 76 c not participating in the synchronization process 30 , and management actions taken by other independent instances of the management processes 76 a - 76 b participating in the synchronization process 30 .
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
- This invention relates to synchronization schemes.
- Some electronic devices support device management interfaces that allow configuration, monitoring, and control of the devices. For example, users may directly interact with management interfaces through switches, menu, or command line interface. In other instances, software management programs interact with a management interface of the devices. In some cases, multiple users, either directly or via management programs, may simultaneously or alternately interact with the electronic devices.
- In an aspect, the invention features querying a managed device to obtain an initial device state, synchronizing the device state in a plurality of management processes, detecting a change in the device state, and maintaining a synchronized current device state between the managed device and the plurality of management processes.
- Embodiments may include one or more of the following.
- The plurality of management processes may reside in remote systems. Maintaining may include, for each management process, storing a current device state in the management processes. Storing may include integrating an incremental device state change into information stored in a management process.
- Synchronizing may include determining whether synchronization already exists between a managed device and a management process, and establishing a synchronization if synchronization does not already exist.
- Determining may include comparing a sequence number identifying a current device state with a previously stored sequence number.
- Establishing may include a device-dominant process that includes modifying information stored in a management process to match a current state of the managed device.
- Establishing may include a management process-dominant process that includes modifying a current state of the managed device to match information stored in one of the management processes.
- In embodiments, detecting may include receiving a device state change message from a managed device. The change may be in response to a remote user command, a local user command and/or a command from one of the management processes.
- Embodiments may have any of the following advantages.
- The method enables a management process to remain cognizant of the state of a managed device in the presence of management changes applied to the device by other management processes or users. The management process continues to possess up-to-date and synchronized information pertaining to a state of the device. This enables correct management of the device by the management process in the presence of the changes made by other management processes or users.
- In the present method and system, management processes do not inadvertently overwrite changes to the device state made by other management processes or users.
- Multiple management processes serve as redundant backups without requiring direct communication between each other. Each management process is made “aware” of changes to the device state via information and updates sent directly by the managed device itself to the management process. This eliminates software complexity that otherwise would result by a system lacking such features.
- FIG. 1 is a block diagram of a system.
- FIG. 2 is a flow diagram of a synchronization process.
- FIG. 3 is part of the flow diagram of FIG. 2.
- FIG. 4 is part of the diagram of FIG. 2.
- FIG. 5 is a diagram of a router synchronization system.
- Referring to FIG. 1, a
device synchronization system 10 includes a manageddevice 12, such as a network switch, connected to computer systems 14 a-14 b via communications channels 16 a-16 b. Management processes 18 a and 18 b reside incomputer systems 14 a, 14 b, respectively and are programs that support configuration, control, and monitoring of the manageddevice 12. - In this example, a local user20 a and/or remote user 20 b can also provide support and control for configuring, controlling, and monitoring the managed
device 12. The users 20 a, 20 b can reset, configure, and input any information such as data commands into the manageddevice 12. The remote user 20 b interacts with themanaged device 12 via the communication channel 16 c and the local user 20 a interacts directly with the manageddevice 12 through a local user interface (UI) 24. - The user interface (UI)24 may be a command line interface, a keyboard or mouse.
- The remote user20 b and management processes 18 a-18 b interact with the managed
device 12 via aremote management interface 26 linked to the communication channels 16 a-16 c. - Referring to FIG. 2, a
synchronization process 30 residing in a management process 18 within thedevice synchronization system 10 features a feedback mechanism used to synchronize events such as configuration, set, reset, control, and monitoring events between the manageddevice 12 and the management processes 18 a-18 b. In particular, theprocess 30 begins (32) at a start phase by establishing (34) communications between the manageddevice 12 and each of the management processes 18. Thesynchronization process 30 is executed simultaneously and independently by any number of management processes 18 a-18 b, for example. - Once communication has been established, the
process 30 retrieves and integrates (36) a full listing of current device state information. Device state information may include, for example, configuration information and control information. - The
synchronization process 30 continues by updating (38) the device state information in the management processes 18 a, 18 b. In particular, during the updating (38), the management process 18 waits (40) to detect a device state change announcement from thedevice 12. For example, configuration and/or control information may change in thedevice 12. The announcement may be via, for example, a network message. The state changes in thedevice 12 may have arisen from the management process 18 a itself or from any other source in thesystem 10, such as management process 18 b oruser 20. Once a device state change has been communicated, the management process 18 a, for example, integrates (46) the state changes of thedevice 12 byprocess 30 into device state information residing in management process 18 a within thecomputer system 14 a. After the state changes are integrated (46), theprocess 30 waits (40) for a device state change. - Referring to FIG. 3, retrieving and integrating (36) full current device state information is optimized.
- After communication has been established (34), the management process, for example, management process 18 a, determines (50) whether this management process 18 a has been in contact with the managed
device 12 since the management process 18 a has been started. If the management process 18 a has not been in contact with the manageddevice 12 previously, the full current device state is retrieved and integrated (52) into device state information residing in management process 18 a within thecomputer system 14 a. - If the management process18 a has been in contact with the managed
device 12, a determination (54) of whether the device state has changed since the last communication is made. If changes have occurred in the device state, then the full current device state is retrieved and integrated (52) into device state information residing in the management process 18 a, as described above. This retrieval and integration (52) constitutes re-synchronization. If no changes have occurred in the device state, re-synchronization is suppressed and theprocess 30 continues (38) updating of the device state information in the management process 18 a. - Together the process of determining (50) whether the management process 18a has been in contact with the
device 12 since the management process 18 a has been started and the process of determining (54) if the device state has changed since the last communication, make up are-synchronization determination stage 56 where the management process 18 a determines if re-synchronization with thedevice 12 will be needed. - The
device 12 can maintain a sequence number on the device state and increment the sequence number each time the device state changes. Thedevice 12 can be subject to state changes brought about by not only various management processes such as management processes 18 a-18 b, but users 20 a, 20 b can also directlysubject device 12 to state changes, or state changes may occur not caused by management action. - The device state sequence number, when retrieved by the management process18a and compared to a value stored previously, allows the management process 18 a that has been out of contact with the
device 12 to readily discover upon regaining connection with thedevice 12 whether the management process is still up-to-date with the current state of thedevice 12. This discovery constitutes the determination (54) of whether the device state has changed since the management process 18 a last communicated with thedevice 12. In certain embodiments, further optimization can allow the management process 18 a to retrieve only recent changes to the device state, rather than retrieving the entire current state. - Referring to FIG. 4, another optimization of the
synchronization process 30 described above in conjunction with FIG. 3 is shown. After communication has been established (34) between the management process 18 a and thedevice 12, there-synchronization determination stage 56 as described above is executed. If re-synchronization is required (52), the management process 18 a enters a mode optimization process (58). The mode optimization process (58) determines which of two re-synchronization modes, i.e., a device-dominant mode and a management process-dominant mode, was previously selected. - If the device-dominant mode was selected, the current state of the
device 12 supercedes and overwrites any and all information held by the management process 18 a should any conflict arise between the information exchanged between thedevice 12 and the management process 18 a. Thus, the management process 18 a retrieves and integrates the full current device state. - However, if the management process-dominant mode was selected, the opposite occurs, namely, the desired device state as stored in the management process18 a supercedes and overwrites any and all information held by the
device 12. Thus, the management process 18 a puts thedevice 12 to the desired state, for example, by retrieving the full current device state, computing the changes to the device state to match the device state to the state that has been stored in the management process 18 a and then applying and forwarding those changes to thedevice 12. - If the
re-synchronization determination stage 56 determines that re-synchronization is not required after communication has been established (34) between the management process 18 a and thedevice 12, thesynchronization process 30 continues updating (38) of the device state information in the management process 18 a. - As described above in the
synchronization process 30 in conjunction with FIGS. 2-4, if more than one management process is connected to the manageddevice 12 or ifusers 20 are also accessing the manageddevice 12 together with one or more management processes, theprocess 30 coordinates the various management processes that are modifying the device state. Further, whenever any relevant management operations are performed on thedevice 12, or other state changes of interest occur to thedevice 12, thedevice 12 reports this change to all management processes participating in the multiway synchronization. - FIG. 5 illustrates an example of a managed
device 12 in a router synchronization system 70 that includes a managed device 72 (e.g., an Internet Protocol (IP) router) and associated computer systems 74 a-74 c and management processes 76 a-76 c residing within the computer systems 74 a-74 c. In this example, the management processes 76 a-76 b employ thesynchronization process 30. Themanagement process 76 c residing oncomputer system 74 c does not participate in thesynchronization process 30. A set of configuration parameters of theIP router device 72 constitutes device state information. The management processes 76 a-76 c are coupled to theIP router device 72 via communications channels 78 a-78 c, respectively, that link the management processes 76 a-76 c with theremote management interface 80. - The
IP router device 72 supports a command line interface (CLI) 82 that may be accessed locally by the user 84, or remotely over a network 88 (e.g., the Internet) using, for example, the telnet protocol by remote user 86. The users 84 and 86 as well as the management processes 76 a-76 c manipulate theIP router device 72 state, such as router configuration state, by issuing commands to theIP router 72. - In support of the synchronization provided by the synchronization system70, the
IP router device 72 provides a mechanism for determining whether theIP router 72 configuration state has changed, based on a sequence number assigned by theIP router device 72 to each version of that state. The management processes 76 a-76 b use that sequence number to determine whether a device state has changed since the last communication between the management processes 76 a-76 b and theIP router device 72. - The management processes76 a-76 b can also retrieve the full current
IP router device 72 configuration state. Additionally, if a relevant management operation is performed on theIP router device 72, or other state change of interest occurs in theIP router device 72, theIP router device 72 reports the change to all management process instances 76 a-76 b participating in the multi-way synchronization. - Application of the synchronization system70 enables the management processes 76 a-76 b to correctly and robustly manage the
IP router device 72 even in the presence of direct management actions taken by local user 84 or remote user 86 at theCLI interface 82 of theIP router device 72, management actions taken byother management process 76 c not participating in thesynchronization process 30, and management actions taken by other independent instances of the management processes 76 a-76 b participating in thesynchronization process 30. - Other embodiments are within the scope of the following claims.
Claims (18)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/102,169 US20030182472A1 (en) | 2002-03-20 | 2002-03-20 | Synchronization scheme |
US11/364,018 US8015268B2 (en) | 2002-03-20 | 2006-02-27 | Methods, systems, and computer readable media for synchronizing device state |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/102,169 US20030182472A1 (en) | 2002-03-20 | 2002-03-20 | Synchronization scheme |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/364,018 Continuation US8015268B2 (en) | 2002-03-20 | 2006-02-27 | Methods, systems, and computer readable media for synchronizing device state |
Publications (1)
Publication Number | Publication Date |
---|---|
US20030182472A1 true US20030182472A1 (en) | 2003-09-25 |
Family
ID=28040144
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/102,169 Abandoned US20030182472A1 (en) | 2002-03-20 | 2002-03-20 | Synchronization scheme |
US11/364,018 Expired - Fee Related US8015268B2 (en) | 2002-03-20 | 2006-02-27 | Methods, systems, and computer readable media for synchronizing device state |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/364,018 Expired - Fee Related US8015268B2 (en) | 2002-03-20 | 2006-02-27 | Methods, systems, and computer readable media for synchronizing device state |
Country Status (1)
Country | Link |
---|---|
US (2) | US20030182472A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080008115A1 (en) * | 2004-05-24 | 2008-01-10 | Alcatel Lucent | Transmission of Control Information After Optional Selection and Compression within a Radio Communication Network |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101494552B (en) * | 2008-01-23 | 2011-05-18 | 华为技术有限公司 | Method, system and apparatus for establishing business connection |
JP2009237843A (en) * | 2008-03-27 | 2009-10-15 | Brother Ind Ltd | File management system, mobile terminal, and mobile terminal program |
US20130311550A1 (en) * | 2012-05-17 | 2013-11-21 | Infinite Convergence Solutions, Inc | Multi-site Server and Client Resynchronization Process and Devices |
US9762532B2 (en) * | 2013-08-14 | 2017-09-12 | Coriant Oy | Method and network device for configuring a data transfer network |
US10402311B2 (en) * | 2017-06-29 | 2019-09-03 | Microsoft Technology Licensing, Llc | Code review rebase diffing |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6047004A (en) * | 1997-06-18 | 2000-04-04 | Mitsubishi Denki Kabushiki Kaisha | Synchronizing device with head word position verification |
US6088704A (en) * | 1996-10-18 | 2000-07-11 | Nec Corporation | Parallel management system for a file data storage structure |
US6493727B1 (en) * | 2000-02-07 | 2002-12-10 | Hewlett-Packard Company | System and method for synchronizing database in a primary device and a secondary device that are derived from a common database |
US6725281B1 (en) * | 1999-06-11 | 2004-04-20 | Microsoft Corporation | Synchronization of controlled device state using state table and eventing in data-driven remote device control model |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5544347A (en) * | 1990-09-24 | 1996-08-06 | Emc Corporation | Data storage system controlled remote data mirroring with respectively maintained data indices |
US6101497A (en) * | 1996-05-31 | 2000-08-08 | Emc Corporation | Method and apparatus for independent and simultaneous access to a common data set |
US6449622B1 (en) * | 1999-03-08 | 2002-09-10 | Starfish Software, Inc. | System and methods for synchronizing datasets when dataset changes may be received out of order |
JP3750504B2 (en) * | 2000-08-09 | 2006-03-01 | セイコーエプソン株式会社 | Data update method and information processing apparatus |
US6976087B1 (en) * | 2000-11-24 | 2005-12-13 | Redback Networks Inc. | Service provisioning methods and apparatus |
US6920491B2 (en) * | 2001-04-25 | 2005-07-19 | Sun Microsystems, Inc. | Fabric device configuration interface for onlining fabric devices for use from a host system |
US7386608B2 (en) * | 2002-07-30 | 2008-06-10 | Brocade Communications Systems, Inc. | Fibre channel switch that aggregates registered state change notifications |
-
2002
- 2002-03-20 US US10/102,169 patent/US20030182472A1/en not_active Abandoned
-
2006
- 2006-02-27 US US11/364,018 patent/US8015268B2/en not_active Expired - Fee Related
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6088704A (en) * | 1996-10-18 | 2000-07-11 | Nec Corporation | Parallel management system for a file data storage structure |
US6047004A (en) * | 1997-06-18 | 2000-04-04 | Mitsubishi Denki Kabushiki Kaisha | Synchronizing device with head word position verification |
US6725281B1 (en) * | 1999-06-11 | 2004-04-20 | Microsoft Corporation | Synchronization of controlled device state using state table and eventing in data-driven remote device control model |
US6493727B1 (en) * | 2000-02-07 | 2002-12-10 | Hewlett-Packard Company | System and method for synchronizing database in a primary device and a secondary device that are derived from a common database |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080008115A1 (en) * | 2004-05-24 | 2008-01-10 | Alcatel Lucent | Transmission of Control Information After Optional Selection and Compression within a Radio Communication Network |
US8891440B2 (en) * | 2004-05-24 | 2014-11-18 | Alcatel Lucent | Transmission of control information after optional selection and compression within a radio communication network |
Also Published As
Publication number | Publication date |
---|---|
US8015268B2 (en) | 2011-09-06 |
US20060200793A1 (en) | 2006-09-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7154862B2 (en) | Device control system, method, and apparatus for server-based or peer-to-peer network environments | |
US8015268B2 (en) | Methods, systems, and computer readable media for synchronizing device state | |
US7554931B2 (en) | System and method for remote dynamic network configuration | |
AU2003227207B2 (en) | centralized PLANT-monitoring controlLER and method | |
US8862697B2 (en) | Intelligent network management platform for IKVM servers | |
US20130191517A1 (en) | System, server and method for reproducing topological change using device events | |
US8176343B2 (en) | Method for providing information for power management of devices on a network | |
CN100474829C (en) | Device control system, method, and apparatus for server-based or peer-to-peer network environments | |
US6883169B1 (en) | Apparatus for managing the installation of software across a network | |
US6564245B1 (en) | Processing system and apparatus for performing an inquiry process in accordance with a type of shared operation and a target user | |
CN101005421A (en) | Telnet control method for realizing multiple network system by single network port | |
KR19990066368A (en) | Integrated operating device of distributed system | |
CN111696544A (en) | Control method of household appliance, household appliance and control device | |
CN115134229B (en) | NDN network management system and method based on overlay network | |
CN113626049B (en) | Program upgrading method and device suitable for hospital LAN environment | |
TWI693836B (en) | Method for controlling projectors and control system thereof | |
JP2004246679A (en) | Equipment monitoring control system, equipment management server, equipment monitoring control device, program, recording medium and equipment monitoring control method | |
CN113824710A (en) | Communication protocol conversion method and device and computer readable storage medium | |
JPH11252210A (en) | Changeover time setting system for communication equipment | |
KR20020014206A (en) | A method of db operation for pabx | |
JP2002374323A (en) | Cmip protocol test automating device and cmip protocol testing method | |
JPH05324292A (en) | Information management device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: QUARRY TECHNOLOGIES, INC., MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DUFFY, MARK;EZEKIEL, EPHRAIM;IDDON, ROBIN;AND OTHERS;REEL/FRAME:012723/0704;SIGNING DATES FROM 20020221 TO 20020225 |
|
AS | Assignment |
Owner name: HIROZON TECHNOLOGY FUNDING COMPANY LLC, CONNECTICU Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:QUARRY TECHNOLOGIES, INC.;REEL/FRAME:015788/0487 Effective date: 20040818 |
|
AS | Assignment |
Owner name: REEF POINT SYSTEMS, MASSACHUSETTS Free format text: CHANGE OF NAME;ASSIGNOR:QUARRY TECHNOLOGIES, INC.;REEL/FRAME:017379/0719 Effective date: 20050721 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: COLUMBIA PARTNERS, L.L.C. INVESTMENT MANAGEMENT, M Free format text: SECURITY AGREEMENT;ASSIGNOR:REEF POINT SYSTEMS, INC.;REEL/FRAME:020339/0879 Effective date: 20080104 |
|
AS | Assignment |
Owner name: NEXTPOINT NETWORKS, INC., MARYLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:REEF POINT SYSTEMS, INC.;REEL/FRAME:020741/0436 Effective date: 20080325 |
|
AS | Assignment |
Owner name: REEF POINT SYSTEMS, INC. F/K/A QUARRY TECHNOLOGIES Free format text: RELEASE;ASSIGNOR:HORIZON TECHNOLOGY FUNDING COMPANY LLC A/K/A HORIZON TECHNOLOGY FUNDING COMPANY LLC;REEL/FRAME:023486/0868 Effective date: 20091110 |
|
AS | Assignment |
Owner name: GENBAND US LLC, TEXAS Free format text: RELEASE AND REASSIGNMENT OF PATENTS;ASSIGNOR:COMERICA BANK, AS AGENT;REEL/FRAME:039280/0467 Effective date: 20160701 |