US20080043630A1 - Network device test system and method for testing network device - Google Patents
Network device test system and method for testing network device Download PDFInfo
- Publication number
- US20080043630A1 US20080043630A1 US11/617,759 US61775906A US2008043630A1 US 20080043630 A1 US20080043630 A1 US 20080043630A1 US 61775906 A US61775906 A US 61775906A US 2008043630 A1 US2008043630 A1 US 2008043630A1
- Authority
- US
- United States
- Prior art keywords
- module
- network device
- displaying
- recited
- test
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/50—Testing arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
Definitions
- the present invention relates to an electronic device test system and method, and particularly to a network device test system and method for testing network devices.
- An exemplary embodiment of the invention provides a network device test system.
- the network device test system includes at least one leasing module, at least one monitoring module, at least one saving module, at least one agent module, and a controller.
- the at least one leasing module is disposed in each of the network devices for leasing addresses for the network devices.
- the at least one monitoring module is disposed in each of the network devices for monitoring whether errors occur in the network devices, and capturing test data from the network devices.
- the at least one saving module is disposed in each of the network devices for saving the test data captured by the monitoring module.
- the at least one agent module is disposed in each of the network devices for modifying data in the saving module, and informing of a test status of the network devices.
- the controller comprises an address assigning module for assigning a unique address for each of the network devices according to requests sent by the leasing module.
- the connecting device connects the controller to the multiple network devices.
- the network device test method comprises providing at least one leasing module, at least one monitoring module, at least one saving module, at least one displaying module, and at least one agent module, disposed in the network device; providing a controller comprising a managing module and an address assigning module; the leasing module leasing addresses for the network devices from the address assigning module; the managing module sending test commands to the agent module via the leased addresses; the network device entering a test mode according to the test command, and the monitoring module monitoring whether errors occur in the network devices, and capturing test data from the network devices; and the network device entering a fail mode, if any errors occur in the network devices.
- FIG. 1 is a block diagram of a network device test system of an exemplary embodiment of the present invention
- FIG. 2 is a flowchart of a network device test method of another exemplary embodiment of the present invention.
- FIG. 3 is a flowchart of details of a step S 270 of FIG. 2 ;
- FIG. 4 is a flowchart of details of a step S 280 of FIG. 2 .
- FIG. 1 is a block diagram of a network device test system 100 of an exemplary embodiment of the present invention.
- a network device test system 100 for testing multiple network devices 200 includes at least one network device 200 , a controller 170 , a content provider 180 , and a connecting device 190 .
- the network device 200 includes at least one leasing module 110 , at least one monitoring module 120 , at least one saving module 130 , at least one agent module 140 , and at least one displaying module 160 . In this embodiment, only one network device 200 is shown in FIG. 1 .
- the network device 200 is a set top box, and the content provider 180 is a server using a Linux operating system for providing video data for the set top box.
- the connecting device 190 is a switch for connecting the controller 170 to the network devices 200 .
- the at least one leasing module 110 of the network devices 200 is for leasing addresses for the network devices 200 .
- the leasing module 110 is a dynamic host configuration protocol (DHCP) client.
- DHCP dynamic host configuration protocol
- the at least one monitoring module 120 of the network devices 200 is for monitoring whether errors occur in the network devices 200 , and capturing test data from the network devices 200 .
- the errors include the set top box hanging.
- the at least one displaying module 160 of the network devices 200 is for displaying the test status of each of the network devices 200 .
- the displaying module 160 includes multiple light emitting diodes (LEDs), which indicates test statuses of the network devices 200 by displaying different colored light.
- the controller 170 includes an address assigning module 172 , a managing module 174 , and a user interface module 176 .
- the managing module 174 manages the agent module 140 by sending a write request and a read request to the agent module 140 via the ID.
- the agent module 140 reads data from corresponding object of the saving module 130 according to the read request, and modifies data in corresponding object of the saving module 130 according to the write request.
- the managing module 174 is a simple network management protocol (SNMP) management system, and the agent module 140 is a SNMP agent.
- the agent module 140 also sends the read data and the modified data to the managing module 174 , and sends the test status to the managing module 174 via a trap packet.
- the agent module 140 if the network device 200 successful powers, the agent module 140 sends a trap packet including successful power, to the managing module 174 . If the network device 200 fails to power, the agent module 140 sends a trap packet, which includes failed, to the managing module 174 . If the network device 200 passes the test, the agent module 140 sends a trap packet including success to the managing module 174 .
- step S 200 the at least one network device 200 is power up. If the LEDs are unlit, the network device 200 has failed to power up, or the LEDs are defective, and the process stops. Otherwise, step S 210 is next.
- step S 220 the agent module 140 sends successful power up message to the managing module 174 via the leased addresses.
- the successful power up message is included in a trap packet.
- step S 230 the managing module 174 sends a status displaying command to the agent module 140 via the leased addresses.
- the status displaying command is the write request
- the write request includes the ID of a corresponding object of the network device 200 that successfully powers up.
- step S 240 the agent module 140 modifies data in a corresponding object of the saving module 130 according to the status displaying command, and the displaying module 160 displays the status of the network device 200 according to the modified data.
- the LEDs of the displaying module 160 blink to indicate that the network device 200 has successfully powers up, and is ready for receiving test commands.
- step S 250 the managing module 174 sends a test command to the agent module 140 via the leased addresses.
- the network device 200 is a set top box.
- the test command is the write request, which includes the ID of a corresponding object of the network device 200 .
- the network device 200 After receiving the test command, the network device 200 send a request to the content provider 180 to get video data and play it.
- step S 260 the network devices 200 enter a test mode according to the test command, and the monitoring module 120 monitors whether errors occur in the network devices 200 , and capture test data from the network devices 200 . At this time, if any error occurs in the network devices 200 , the monitoring module 120 records the error into the saving module 130 . If any errors occur in the network devices 200 , the process proceeds to step S 270 . If no errors occur in the network devices 200 , the process proceeds to step S 280 .
- step S 270 the network devices 200 enter a fail mode.
- the network devices 200 enter a fail mode.
- FIG. 3 please refer to FIG. 3 .
- step S 280 the network devices 200 enter a successful mode.
- the network devices 200 enter a successful mode.
- FIG. 4 please refer to FIG. 4 .
- FIG. 3 is a flowchart of details of a step of S 270 of FIG. 2 .
- step S 271 the agent module 140 sends error message to the managing module 174 via the leased address.
- the error message is included in the trap packet.
- step S 272 the managing module 174 sends a fail displaying command to the agent module 140 via the leased address.
- the fail displaying command is the write request, which includes the ID of a corresponding object of the failed network device 200 .
- step S 273 the agent module 140 modifies data in a corresponding object of the saving module 130 according to the fail displaying command, and the displaying module 160 displays fail message according to the modified data.
- the LEDs continuously emit red light to indicate that the test has failed.
- FIG. 4 is a flowchart of details of a step of S 280 of FIG. 2 .
- step S 281 the agent module 140 sends success message to the managing module 174 via the leased address.
- the success message is included in the trap packet.
- step S 282 the managing module 174 sends a success displaying command to the agent module 140 via the leased address.
- the success displaying command is the write request, which includes the ID of the corresponding object of the successful network device 200 .
- step S 283 the agent module 140 modifies data in corresponding object of the saving module 130 according to the success displaying command, and the displaying module 160 displays success message according to the modified data.
- the LEDs continuously emit green light to indicate that the test is successful.
Abstract
A network device test method is provided. The network device test method comprises providing at least one leasing module, at least one monitoring module, at least one saving module, at least one displaying module, and at least one agent module, disposed in the network device; providing a controller comprising a managing module and an address assigning module; the leasing module leasing addresses for the network devices from the address assigning module; the managing module sending test command to the agent module via the leased addresses; the network device entering a test mode according to the test command, and the monitoring module monitoring whether errors occur in the network devices, and capturing test data from the network devices; and the network device entering a fail mode, if any errors occur in the network devices. A network device test system is also provided.
Description
- 1. Field of the Invention
- The present invention relates to an electronic device test system and method, and particularly to a network device test system and method for testing network devices.
- 2. Related of Prior Art
- A run-in test is used to test stability of a network device, such as a set top box (STB). For example, it is necessary to test the STB, a server, a terminal, a video switcher, and a switch for ensuring stability thereof. The server serves as a network file system (NFS) server, a dynamic host configuration protocol (DHCP) server, and a content provider. The switch connects multiple STBs to the server, and the video switcher connects the multiple STBs to the terminal. The STB firstly obtains an Internet protocol (IP) address from the DHCP server, then receives data, such as movie files, transmitted from the content provider via the IP address, and decodes the movies. Then an operator employs the terminal to collect the decoded movies via the video switcher, and checks whether the STB plays the movies smoothly and records test results. However, if an operator is careless, the test results will be unreliable.
- Therefore, a heretofore unaddressed need exists in the industry to ensure reliability of the test results.
- An exemplary embodiment of the invention provides a network device test system. The network device test system includes at least one leasing module, at least one monitoring module, at least one saving module, at least one agent module, and a controller. The at least one leasing module is disposed in each of the network devices for leasing addresses for the network devices. The at least one monitoring module is disposed in each of the network devices for monitoring whether errors occur in the network devices, and capturing test data from the network devices. The at least one saving module is disposed in each of the network devices for saving the test data captured by the monitoring module. The at least one agent module is disposed in each of the network devices for modifying data in the saving module, and informing of a test status of the network devices. The controller comprises an address assigning module for assigning a unique address for each of the network devices according to requests sent by the leasing module. The connecting device connects the controller to the multiple network devices.
- Another exemplary embodiment of the invention provides a network device test method. The network device test method comprises providing at least one leasing module, at least one monitoring module, at least one saving module, at least one displaying module, and at least one agent module, disposed in the network device; providing a controller comprising a managing module and an address assigning module; the leasing module leasing addresses for the network devices from the address assigning module; the managing module sending test commands to the agent module via the leased addresses; the network device entering a test mode according to the test command, and the monitoring module monitoring whether errors occur in the network devices, and capturing test data from the network devices; and the network device entering a fail mode, if any errors occur in the network devices.
- Other objectives, advantages and novel features of the present invention will be drawn from the following detailed description of preferred embodiments of the present invention with the attached drawings, in which:
-
FIG. 1 is a block diagram of a network device test system of an exemplary embodiment of the present invention; -
FIG. 2 is a flowchart of a network device test method of another exemplary embodiment of the present invention; -
FIG. 3 is a flowchart of details of a step S270 ofFIG. 2 ; and -
FIG. 4 is a flowchart of details of a step S280 ofFIG. 2 . -
FIG. 1 is a block diagram of a networkdevice test system 100 of an exemplary embodiment of the present invention. - A network
device test system 100 for testingmultiple network devices 200 includes at least onenetwork device 200, acontroller 170, acontent provider 180, and aconnecting device 190. Thenetwork device 200 includes at least oneleasing module 110, at least onemonitoring module 120, at least one savingmodule 130, at least oneagent module 140, and at least onedisplaying module 160. In this embodiment, only onenetwork device 200 is shown inFIG. 1 . - The
network device 200 is a set top box, and thecontent provider 180 is a server using a Linux operating system for providing video data for the set top box. The connectingdevice 190 is a switch for connecting thecontroller 170 to thenetwork devices 200. - The at least one
leasing module 110 of thenetwork devices 200 is for leasing addresses for thenetwork devices 200. In this embodiment, theleasing module 110 is a dynamic host configuration protocol (DHCP) client. - The at least one
monitoring module 120 of thenetwork devices 200 is for monitoring whether errors occur in thenetwork devices 200, and capturing test data from thenetwork devices 200. In this embodiment, the errors include the set top box hanging. - The at least one saving
module 130 of thenetwork devices 200 is for saving the test data captured by themonitoring module 120. In this embodiment, the savingmodule 130 is a message information base (MIB), comprising multiple objects. Each of the objects has a unique ID. If errors occur in thenetwork devices 200, themonitoring module 120 records the errors into thesaving module 130. - The at least one
agent module 140 of thenetwork devices 200 is for modifying data in the savingmodule 130, and informing of a test status of thenetwork devices 200. - The at least one displaying
module 160 of thenetwork devices 200 is for displaying the test status of each of thenetwork devices 200. In this embodiment, the displayingmodule 160 includes multiple light emitting diodes (LEDs), which indicates test statuses of thenetwork devices 200 by displaying different colored light. - In detail, after the
network device 200 powers up, if the LEDs are unlit, then thenetwork device 200 has failed to power up, or the LEDs may be defective; if the LEDs blink together, then thenetwork device 200 has successfully powered up, and is ready for receiving test commands; if the LEDs alternately blink, thenetwork device 200 is in a test status, and no error has occurred in thenetwork device 200; if a steady red light is emitted form the LEDs, then the test has failed; if a steady green light is emitted form the LEDs, then the test has been passed. - The
controller 170 includes anaddress assigning module 172, a managingmodule 174, and auser interface module 176. - The
address assigning module 172 assigns a unique address to each of thenetwork devices 200 according to requests sent by theleasing module 110. In this embodiment, theaddress assigning module 172 is a DHCP server. - The managing
module 174 manages theagent module 140 by sending a write request and a read request to theagent module 140 via the ID. Theagent module 140 reads data from corresponding object of thesaving module 130 according to the read request, and modifies data in corresponding object of the savingmodule 130 according to the write request. In this embodiment, the managingmodule 174 is a simple network management protocol (SNMP) management system, and theagent module 140 is a SNMP agent. - The
agent module 140 also sends the read data and the modified data to the managingmodule 174, and sends the test status to the managingmodule 174 via a trap packet. In this embodiment, if thenetwork device 200 successful powers, theagent module 140 sends a trap packet including successful power, to the managingmodule 174. If thenetwork device 200 fails to power, theagent module 140 sends a trap packet, which includes failed, to the managingmodule 174. If thenetwork device 200 passes the test, theagent module 140 sends a trap packet including success to the managingmodule 174. - The
user interface module 176 receives user input, including a start input, a read input, a change input, and a stop input. In this embodiment, a user can press a start or an end button designed in theuser interface module 176 to start or terminate the test respectively. The user can also press a read or a write button designed in theuser interface module 176 to get the test status or modify data in a corresponding object of the savingmodule 130 respectively. After the above-mentioned buttons are pressed, theuser interface module 176 sends corresponding commands to the managingmodule 174 for changing the commands into the write requests or the read requests. If the test fails, theuser interface module 176 further generates a dialogue window to indicate the test has failed. -
FIG. 2 is a flowchart of a network device test method of another exemplary embodiment of the present invention. - In step S200, the at least one
network device 200 is power up. If the LEDs are unlit, thenetwork device 200 has failed to power up, or the LEDs are defective, and the process stops. Otherwise, step S210 is next. - In step S210, the
leasing module 110 leases addresses for thenetwork devices 200 from theaddress assigning module 172. In detail, theleasing module 110 broadcasts a DHCP discover packet for looking for a DHCP server; theaddress assigning module 172, receiving the DHCP discover packet, sends a DHCP offer packet including an un-leased IP address to theleasing module 110; theleasing module 110 broadcasts a DHCP request packet including the un-leased IP address to theaddress assigning module 172; theaddress assigning module 172 sends a DHCP ACK packet including the un-leased IP address and a subnet to theleasing module 110 to inform that theleasing module 110 can use the un-leased IP address. - In step S220, the
agent module 140 sends successful power up message to the managingmodule 174 via the leased addresses. In this embodiment, the successful power up message is included in a trap packet. - In step S230, the managing
module 174 sends a status displaying command to theagent module 140 via the leased addresses. In this embodiment, the status displaying command is the write request, and the write request includes the ID of a corresponding object of thenetwork device 200 that successfully powers up. - In step S240, the
agent module 140 modifies data in a corresponding object of the savingmodule 130 according to the status displaying command, and the displayingmodule 160 displays the status of thenetwork device 200 according to the modified data. In this embodiment, the LEDs of the displayingmodule 160 blink to indicate that thenetwork device 200 has successfully powers up, and is ready for receiving test commands. - In step S250, the managing
module 174 sends a test command to theagent module 140 via the leased addresses. In this embodiment, thenetwork device 200 is a set top box. The test command is the write request, which includes the ID of a corresponding object of thenetwork device 200. After receiving the test command, thenetwork device 200 send a request to thecontent provider 180 to get video data and play it. - In step S260, the
network devices 200 enter a test mode according to the test command, and themonitoring module 120 monitors whether errors occur in thenetwork devices 200, and capture test data from thenetwork devices 200. At this time, if any error occurs in thenetwork devices 200, themonitoring module 120 records the error into the savingmodule 130. If any errors occur in thenetwork devices 200, the process proceeds to step S270. If no errors occur in thenetwork devices 200, the process proceeds to step S280. - In step S270, the
network devices 200 enter a fail mode. For more details, please refer toFIG. 3 . - In step S280, the
network devices 200 enter a successful mode. For more details, please refer toFIG. 4 . -
FIG. 3 is a flowchart of details of a step of S270 ofFIG. 2 . - When the
network devices 200 enter a fail mode, in step S271, theagent module 140 sends error message to the managingmodule 174 via the leased address. In this embodiment, the error message is included in the trap packet. - In step S272, the managing
module 174 sends a fail displaying command to theagent module 140 via the leased address. In this embodiment, the fail displaying command is the write request, which includes the ID of a corresponding object of the failednetwork device 200. - In step S273, the
agent module 140 modifies data in a corresponding object of the savingmodule 130 according to the fail displaying command, and the displayingmodule 160 displays fail message according to the modified data. In this embodiment, the LEDs continuously emit red light to indicate that the test has failed. -
FIG. 4 is a flowchart of details of a step of S280 ofFIG. 2 . - In step S281, the
agent module 140 sends success message to the managingmodule 174 via the leased address. In this embodiment, the success message is included in the trap packet. - In step S282, the managing
module 174 sends a success displaying command to theagent module 140 via the leased address. In this embodiment, the success displaying command is the write request, which includes the ID of the corresponding object of thesuccessful network device 200. - In step S283, the
agent module 140 modifies data in corresponding object of the savingmodule 130 according to the success displaying command, and the displayingmodule 160 displays success message according to the modified data. In this embodiment, the LEDs continuously emit green light to indicate that the test is successful. - The description of the present invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiment was chosen and described in order to best explain the principles of the invention, the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.
Claims (18)
1. A network device test system, for testing multiple network devices, comprising:
at least one network device comprising:
at least one leasing module, for leasing addresses for the network devices;
at least one monitoring module, for monitoring whether errors occur in the at least one network device, and capturing test data from the at least one network device;
at least one saving module, for saving the test data captured by the at least one monitoring module; and
at least one agent module, for modifying data in the saving module, and informing of a test status of the at least one network device;
a controller, comprising an address assigning module for assigning a unique address to the at least one network device according to requests sent by the at leas one leasing module; and
a connecting device, for connecting the controller to the at least one network device.
2. The network device test system as recited in claim 1 , wherein the at least one saving module is a message information base, comprising a plurality of objects.
3. The network device test system as recited in claim 2 , wherein each of the objects has a unique identification (ID).
4. The network device test system as recited in claim 3 , wherein the controller further comprises a managing module for managing the at least one agent module by sending a write request and a read request to the at least one agent module via the ID.
5. The network device test system as recited in claim 4 , wherein the at least one agent module reads data saved in the objects according to the read request, and modifies data in the objects according to the write request.
6. The network device test system as recited in claim 5 , wherein the at least one managing module is a simple network management protocol (SNMP) management system, and the at least one agent module is an SNMP agent.
7. The network device test system as recited in claim 1 , wherein the network device is a set top box, and the connecting device is a switch.
8. The network device test system as recited in claim 7 , further comprising a content provider for providing video data for the set top box.
9. The network device test system as recited in claim 1 , wherein the controller further comprises a user interface module for receiving user input, and user input includes a start input, a read input, a change input, and a stop input.
10. The network device test system as recited in claim 1 , wherein the at least one network device further comprises at least one displaying module for displaying the test status of the at least one network device.
11. The network device test system as recited in claim 10 , wherein the displaying module comprises a plurality of light emitting diodes.
12. The network device test system as recited in claim 1 , wherein the at least one leasing module is a dynamic host configuration protocol (DHCP) client, and the address assigning module is a DHCP server.
13. A network device test method, comprising:
providing at least one leasing module, at least one monitoring module, at least one saving module, at least one displaying module, and at least one agent module, disposed in a network device;
providing a controller comprising a managing module and an address assigning module;
the at least one leasing module leasing addresses for the network device from the address assigning module;
the managing module sending a test command to the at least one agent module via the leased addresses;
the network device entering a test mode according to the test command, and the monitoring module monitoring whether errors occur in the network device, and capturing test data from the network device; and
the network device entering a fail mode, if any errors occur in the network device.
14. The network device test method as recited in claim 13 , further comprising:
the network device powers up; and
the at least one agent module sending a successful power up message to the managing module via the leased addresses.
15. The network device test method as recited in claim 14 , further comprising:
the managing module sending a status displaying command to the agent module via the leased addresses; and
the agent module modifying data in a corresponding object of the saving module according to the status displaying command, and the displaying module displaying the status of the network device according to the modified data.
16. The network device test method as recited in claim 13 , wherein the step of the network device entering a fail mode comprising:
the agent module sending an error message to the managing module via the leased address;
the managing module sending a fail displaying command to the agent module via the leased address; and
the agent module modifying data in a corresponding object of the saving module according to the fail displaying command, and the displaying module displaying a fail message according to the modified data.
17. The network device test method as recited in claim 13 , further comprising a step of the network device entering a successful mode, if no errors occur in the network device.
18. The network device test method as recited in claim 17 , wherein the step of the network device entering a successful mode comprising:
the at least one agent module sending a success message to the managing module via the leased address;
the managing module sending a success displaying command to the agent module via the leased address; and
the agent module modifying data in a corresponding object of the saving module according to the success displaying command, and the displaying module displaying a successful message according to the modified data.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
TW95130415 | 2006-08-18 | ||
TW095130415A TWI324458B (en) | 2006-08-18 | 2006-08-18 | Network device testing system and method therefor |
Publications (2)
Publication Number | Publication Date |
---|---|
US20080043630A1 true US20080043630A1 (en) | 2008-02-21 |
US7596095B2 US7596095B2 (en) | 2009-09-29 |
Family
ID=39101268
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/617,759 Expired - Fee Related US7596095B2 (en) | 2006-08-18 | 2006-12-29 | Network device test system and method for testing network device |
Country Status (2)
Country | Link |
---|---|
US (1) | US7596095B2 (en) |
TW (1) | TWI324458B (en) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2012467A1 (en) * | 2007-07-04 | 2009-01-07 | Nec Corporation | Network apparatus test system and network apparatus test method |
US20090059933A1 (en) * | 2007-08-28 | 2009-03-05 | Tellabs Vienna, Inc. | Validating customer in-home network connectivity using moca bridge mode |
US20090279439A1 (en) * | 2008-05-12 | 2009-11-12 | International Business Machines Corporation | Systems, methods and computer program products for controlling high speed network traffic in server blade environments |
WO2014138936A1 (en) * | 2013-03-14 | 2014-09-18 | Exfo Inc. | Pass-through test device |
CN104202215A (en) * | 2014-09-10 | 2014-12-10 | 上海斐讯数据通信技术有限公司 | Method for testing full load of electric ports of Ethernet switchboard |
CN105282292A (en) * | 2015-09-29 | 2016-01-27 | 武汉工程大学 | Testing system |
US10187288B2 (en) * | 2017-03-09 | 2019-01-22 | Caterpillar Inc. | Communicating data link information using a light source |
CN112235157A (en) * | 2020-09-30 | 2021-01-15 | 广州鲁邦通物联网科技有限公司 | Router equipment testing method and system based on two-layer network |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4600697B2 (en) * | 2008-06-24 | 2010-12-15 | 日本電気株式会社 | Network equipment test system |
TWI583349B (en) * | 2010-09-06 | 2017-05-21 | 福永生物科技股份有限公司 | Physiological measure device, health management system and method for operating the health management system |
US9977416B2 (en) * | 2012-06-20 | 2018-05-22 | Rockwell Automation Technologies, Inc. | Industrial hardware installation base reporting and failure monitoring |
TWI548236B (en) * | 2014-10-06 | 2016-09-01 | 研華股份有限公司 | Network apparatus with inserted management mechanism, system, and method for management and surveillance |
US9811072B2 (en) | 2014-10-09 | 2017-11-07 | Rockwell Automation Technologies, Inc. | Apparatus and method for analyzing a control network |
US10116488B2 (en) | 2014-10-09 | 2018-10-30 | Rockwell Automation Technologies, Inc. | System for analyzing an industrial control network |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5850386A (en) * | 1996-11-01 | 1998-12-15 | Wandel & Goltermann Technologies, Inc. | Protocol analyzer for monitoring digital transmission networks |
US6212563B1 (en) * | 1998-10-01 | 2001-04-03 | 3Com Corporation | Method and system for setting and managing externally provided internet protocol addresses using the dynamic host configuration protocol |
US6611868B1 (en) * | 1999-05-21 | 2003-08-26 | 3Com Corporation | Method and system for automatic link hang up |
US7010782B2 (en) * | 2002-04-04 | 2006-03-07 | Sapphire Infotech, Inc. | Interactive automatic-test GUI for testing devices and equipment using shell-level, CLI, and SNMP commands |
US20070162556A1 (en) * | 2005-05-19 | 2007-07-12 | Tp Lab | Method of one key test function in a consumer network device |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100461693C (en) | 2005-01-14 | 2009-02-11 | 日立通讯技术株式会社 | Network system |
-
2006
- 2006-08-18 TW TW095130415A patent/TWI324458B/en not_active IP Right Cessation
- 2006-12-29 US US11/617,759 patent/US7596095B2/en not_active Expired - Fee Related
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5850386A (en) * | 1996-11-01 | 1998-12-15 | Wandel & Goltermann Technologies, Inc. | Protocol analyzer for monitoring digital transmission networks |
US6212563B1 (en) * | 1998-10-01 | 2001-04-03 | 3Com Corporation | Method and system for setting and managing externally provided internet protocol addresses using the dynamic host configuration protocol |
US6611868B1 (en) * | 1999-05-21 | 2003-08-26 | 3Com Corporation | Method and system for automatic link hang up |
US7010782B2 (en) * | 2002-04-04 | 2006-03-07 | Sapphire Infotech, Inc. | Interactive automatic-test GUI for testing devices and equipment using shell-level, CLI, and SNMP commands |
US20070162556A1 (en) * | 2005-05-19 | 2007-07-12 | Tp Lab | Method of one key test function in a consumer network device |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2012467A1 (en) * | 2007-07-04 | 2009-01-07 | Nec Corporation | Network apparatus test system and network apparatus test method |
US20090013072A1 (en) * | 2007-07-04 | 2009-01-08 | Nec Corporation | Network apparatus test system and network apparatus test method |
US20090059933A1 (en) * | 2007-08-28 | 2009-03-05 | Tellabs Vienna, Inc. | Validating customer in-home network connectivity using moca bridge mode |
US20090279439A1 (en) * | 2008-05-12 | 2009-11-12 | International Business Machines Corporation | Systems, methods and computer program products for controlling high speed network traffic in server blade environments |
US7843836B2 (en) * | 2008-05-12 | 2010-11-30 | International Business Machines Corporation | Systems, methods and computer program products for controlling high speed network traffic in server blade environments |
WO2014138936A1 (en) * | 2013-03-14 | 2014-09-18 | Exfo Inc. | Pass-through test device |
CN104202215A (en) * | 2014-09-10 | 2014-12-10 | 上海斐讯数据通信技术有限公司 | Method for testing full load of electric ports of Ethernet switchboard |
CN105282292A (en) * | 2015-09-29 | 2016-01-27 | 武汉工程大学 | Testing system |
US10187288B2 (en) * | 2017-03-09 | 2019-01-22 | Caterpillar Inc. | Communicating data link information using a light source |
CN112235157A (en) * | 2020-09-30 | 2021-01-15 | 广州鲁邦通物联网科技有限公司 | Router equipment testing method and system based on two-layer network |
Also Published As
Publication number | Publication date |
---|---|
TWI324458B (en) | 2010-05-01 |
TW200812292A (en) | 2008-03-01 |
US7596095B2 (en) | 2009-09-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7596095B2 (en) | Network device test system and method for testing network device | |
US7682028B2 (en) | Image transmission system and image transmission method | |
KR101121778B1 (en) | Method and AV device for controlling peripheral device through wireless medium | |
US9565393B2 (en) | Communication terminal, teleconference system, and recording medium | |
JP4235460B2 (en) | Network device management method, network device management program, and network control apparatus | |
WO2010032483A1 (en) | Data processing device, method, and server to determine types of electric appliances | |
US20100097473A1 (en) | Device for connecting video cameras to networks and clients | |
EP1737196A2 (en) | IP address obtaining method | |
JP2006525771A (en) | System and method for communicating with a display device via a network | |
US8813146B2 (en) | Method and system for region-based monitoring of video assets | |
EP3032838A1 (en) | Message processing method, device, gateway, set-top box and internet protocol television system | |
US9706170B2 (en) | Communication apparatus, communication system, and communication management system | |
US20070239860A1 (en) | Information processing device, network connection method, and program recording medium | |
CN108769795A (en) | Video signal realizes system and method | |
WO2012083869A1 (en) | Testing method and system for set top box of internet protocol television | |
US20070245372A1 (en) | Management device, method and program for monitoring video data transmitted via network | |
US20150030012A1 (en) | Communication device | |
US20150215170A1 (en) | Network card with searching ability, monitoring device with the network card, and searching method used for the same | |
US20100057841A1 (en) | Thin client device and method of use | |
CN106303429A (en) | Remote configuring method and device | |
CN101557296A (en) | Method of quick recovery after break of multicast service, device and gateway device | |
US11412577B2 (en) | Electronic apparatus and control method thereof | |
CN105915893A (en) | Highway network image interconnection standard accordance test system | |
CN110830763A (en) | Monitoring video inspection method and device | |
KR20040082521A (en) | Method for transmitting media data in Home network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: HON HAI PRECISION INDUSTRY CO., LTD., TAIWAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHEN, CHIEN-HUA;LIN, HAN-TZUNG;REEL/FRAME:018690/0890 Effective date: 20061222 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
REMI | Maintenance fee reminder mailed | ||
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.) |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20170929 |