KR101023327B1 - Emergency network service system and method thereof - Google Patents

Abstract

The present invention provides an emergency network server for supporting an emergency network service for normalizing the main network connection of the network device when the main network does not operate normally on any network device, and an emergency network for executing the emergency network service. A service providing method of an emergency network remote service system including a network device having software, the method comprising: requesting an emergency network connection to an emergency network server when a main network problem occurs; The process of determining whether or not to join the emergency network service of the network, if the network device is a network device subscribed to the emergency network service, the emergency network server is an emergency through the network device and the emergency network communication network Includes a process, the process of emergency network server to remotely control a network device connected to the emergency network solve the main problem that the network connection to the work. Therefore, in the present invention, when the main network of the network device does not operate normally, the user can simply normalize the main network connection by executing the emergency network software.

Network system, emergency network, remote control

Description

Emergency network service system and its method {EMERGENCY NETWORK SERVICE SYSTEM AND METHOD THEREOF}

1 is a block diagram of an emergency network service system according to an embodiment of the present invention.

2 is a block diagram of an emergency network device according to an embodiment of the present invention.

Figure 3 is a block diagram of an emergency network server according to an embodiment of the present invention.

4 is a flowchart illustrating an emergency network service providing process of an emergency network service system according to an exemplary embodiment of the present invention.

The present invention relates to a network system, and more particularly, to an emergency network service system and method for solving the problems occurring when the network device is connected to the network.

At present, many mobile communication terminals and personal computers (hereinafter, referred to as "network devices") are connected to a network by wire or wirelessly, and the number is increasing exponentially. Accordingly, there are many problems that occur when network devices connect to a network by wire or wirelessly.

However, when a problem occurs that the network device is not connected to the main network (i.e., wired or wireless network), the network server cannot remotely manage the network device or transfer necessary files, so that the main network connection problem cannot be solved. do. Therefore, there is a difficulty in dealing with the main network connection problem unless the network device user directly solves the main network problem.

That is, when a network device such as a PC, PDA, mobile phone, and the like is normally connected and used, and a problem occurs in the main network, the user of the network device can solve the network problem alone or use a telephone to assist. This could only be done by receiving it, visiting the service center in person, or having a service technician come on a business trip.

Therefore, remote diagnosis, processing and service through the main network are impossible unless the network device is physically solved by the user. Therefore, users must bear extreme inconvenience to solve this problem. This is also a serious disadvantage for business development.

Accordingly, an object of the present invention is to provide an emergency network service system and method for easily normalizing network connection of a network device when the network does not operate normally on the network device.

In order to achieve the above object, the present invention provides an emergency network server supporting an emergency network service for normalizing the main network connection of the network device when the main network does not operate normally on any network device, and the emergency network. A service providing method of an emergency network service system including a network device having emergency network software for executing a service, the method comprising: requesting an emergency network connection to the emergency network server when the network device has a main network problem; Determining, by the emergency network server, whether to join the emergency network service of the network device that has requested the connection; and if the network device is a network device that has subscribed to the emergency network service, the emergency network server It is characterized in that it comprises the step of the process of connecting the network device and the emergency network with emergency communication network, and fix the main network issues the said emergency network server to remotely control a network device connected to the emergency network.

Preferably, the method for providing a service of the emergency network service system further comprises the step of the network device accessing the emergency network server and registering information of the network device user.

More preferably, after the emergency network server solves the main network problem of the network device, the method for providing a service of the emergency network service system disconnects the emergency network from the network device; It characterized in that it further comprises the step of setting to the main network state of the.

The present invention also provides an emergency network service system for normalizing the main network connection of the network device when the main network does not operate normally on any network device, and normalizes the main network connection when a problem occurs in the main network. A network device connected via an emergency network and an emergency network communication network for receiving an emergency network service to be provided, and having emergency network software for executing the emergency network service, and the network device and an emergency network through the emergency network software. And an emergency network server that remotely controls the network device to provide the emergency network service when connected.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the same elements in the figures are represented by the same numerals wherever possible. In addition, detailed descriptions of well-known functions and configurations that may unnecessarily obscure the subject matter of the present invention will be omitted.

In principle, the present invention is applied to a network device having means for supporting an emergency network service for normalizing the main network connection of the network device when the main network does not operate normally on any network device. The means for supporting the emergency network service means software required when the network device uses the emergency network service. Emergency network service can be performed by setting up an emergency network server and emergency network line by using preset Internet Protocol (IP) information when a network device executes emergency network software. The emergency network software includes emergency network information, main network interface control information, remote management, manual management, and status resolution functions.

1 is a block diagram of an emergency network service system according to an exemplary embodiment of the present invention.

The illustrated system includes a network device 100 having a wired / wireless LAN module 110 as a main network connection module and a communication module 120 as a separate emergency network connection module, a network 200, and a plurality of service providers 300. , A mobile communication network 400 and an emergency network server 500.

The network device 100 includes a PC, a mobile phone, a PDA, etc., and is connected to the service provider 300 by accessing the network 200 through the wired / wireless LAN module 110. A general example of the network 200 is the Internet.

In addition, the network device 100 is connected to the emergency network server 500 by accessing the network 200 through the communication module 120 which is a mobile communication network 400 connection module. This means an emergency network connection according to an embodiment of the present invention.

Although not shown in FIG. 1, the network device 100 may include a network interface unit for connecting to a main network (for example, a wireless LAN or a wired LAN), a storage unit for storing network information, and a memory for separately storing emergency network software. (Eg, a flash ROM), a display unit, an input unit, and a control unit for displaying network and IP information, etc., wherein the control unit is based on a main line (eg, a telephone line, an ISDN, a VPN, and a cable in the case of a wired LAN) of the network device 100. It is desirable to include a scan sensor which is a general device for reading information. The scan sensor checks network information stored in the storage unit so that the network information setting operation of the network device can be performed in the emergency network server 500. In addition, when the network device 100 is connected to the emergency network server 500 and the emergency network, it is preferable that the network interface unit includes a network connection adapter of a wireless communication network generally used when connecting to a wireless network.

When the user clicks an icon for running the emergency network software when the main network problem occurs, the network device 100 connects to the emergency network server 500 through the communication module 120 while operating the network connection adapter of the wireless communication network. The network device 100 is switched to a slave state that is remotely controlled from the emergency network server 500.

Subsequently, the emergency network server 500 reads main network information of the network device 100 by operating a scan sensor of the network device 100 to perform a network information reset operation of the network device 100, or a network problem. The main network information (IP, DNS, GATEWAY information, etc.) is scanned and stored before generation.

The emergency network server 500 diagnoses the read main network information and resets the erroneous main network information to the network device 100 to normalize the main network. Therefore, even if the user does not perform any network setting work separately for the network device 100, the emergency network server 500 may remotely perform the network information reset operation of the network device 100.

The emergency network service of the present invention executes the emergency network server of the network device 100 when the main network operation is not performed because of a problem in a storage unit for storing network information of the network device 100. In step 500, the emergency network server 500 is used as a master to remotely control and manage the network device 100. Therefore, the emergency network service solves a network problem related to software generated in the storage unit of the network device 100 and supports the normal operation of the main network of the network device 100.

2 is a block diagram of a network device according to an embodiment of the present invention.

The illustrated network device 100 includes a wired / wireless LAN module 110, a communication module 120, a system memory 130, and a flash ROM 140.

1 and 2, the wired / wireless LAN module 110 connects the network device 100 to the service provider 300 by connecting to the network 200 by wire or wirelessly. At this time, the wired / wireless LAN module 110 connects to the main network using an operating system (OS) and network software stored in the system memory 130, and the main network may be either a wired LAN or a wireless LAN. have.

When a problem occurs in the main network connection of the network device 100, the communication module 120 may operate a mobile communication network such as an emergency network communication network (eg, CDMA, GSM) when the emergency network software stored in the flash ROM 140 is driven based on a user request. The network 200 is connected to the network 200 through 400 to connect the network device 100 and the emergency network server 500 to an emergency network. The communication module 120 may be a CDMA module or a GSM module. The emergency network software is stored in a separate flash ROM 140 instead of the system memory 130 in order to safely store the emergency network software from initialization of the system memory 130 or virus infection.

The network device 100 scans network information at the first boot and stores the information in a separate RAM, and then transmits and stores the network information to the emergency network server 500 to be used when a main network problem occurs.

3 is a block diagram of an emergency network server according to an exemplary embodiment of the present invention.

The illustrated emergency network server 500 includes a user information manager 510, a user information storage 520, a network information manager 530, a network information storage 540, a remote control manager 550, and remote control information storage. The unit 560 and the input / output interface controller 570 are included.

The user information manager 510 registers and manages access control information for controlling a main network connection of each of the network devices 100. The access control information is a type of a predetermined network device. Network adapter and driver types and corresponding drivers, regional VPN and telephone modem access phone numbers, and built-in wireless network identification numbers. In addition, the user information management unit 510 uses the service subscriber information stored in the user information storage unit 520 (that is, the network device user information registered to receive the emergency network service) to request the emergency network connection. Determine whether to join the network service.

On the other hand, the access control information may be periodically received from the separate device and updated (Update), the network user information may be registered by the network device user access to the server.

The user information storage unit 520 stores the network device user information and the access control information registered to receive the emergency network service.

The network information manager 530 supports, updates, and manages accessible network information stored in the network information storage unit 540.

The remote control manager 550 diagnoses an error by remotely reading main network information of the network device when the network device and the emergency network are connected according to the determination result of the user information manager 510, and generates an error as a result of the diagnosis. The connection control information for normalizing the main network information is detected by the user information storage unit 520 and output to the input / output interface controller 570. The access control information may be stored in a separate database.

That is, the remote control manager 550 diagnoses a network problem (eg, network software and a wired / wireless LAN network adapter) of the network device 100 connected through the emergency network due to a main network problem, and if there is a problem, Remotely handle the solution. For example, if the remote control manager 550 diagnoses a main network problem of the network device 100 and the problem is that the telephone modem driver of the network device 100 is damaged, the remote control manager 550 may be stored in the user information storage unit 520. Information of the telephone modem driver (eg, driver type) is detected among the connection control information of the network device 100. Subsequently, the remote control manager 550 detects a driver corresponding to the detected phone modem driver information in a separate database or user information storage 520 and transmits the driver to the network device 100.

The remote control manager 550 releases the emergency network connection when the problem on the network generated by the network device 100 is resolved through the emergency network service (that is, the main network connection of the network device 100 becomes possible), and the emergency network service is released. To exit.

The remote control information storage unit 560 stores remote diagnostic information for remotely diagnosing main network information read from the network device 100 having a problem.

The input / output interface controller 570 transfers the access control information output from the remote control manager 550 to the network device 100.

4 is a flowchart illustrating an emergency network service providing process of an emergency network system according to an exemplary embodiment of the present invention.

1 to 4, when a main network failure occurs (S110), the network device 100 drives emergency network software stored in a flash ROM when a user request occurs (S115). The user's request for driving the emergency network software may be implemented by means such as an input means such as a key provided in an input unit (not shown) of the network device 100 or an icon on a display unit (not shown). In addition, the network device 100 may automatically run the emergency network software without a user request when a main network failure occurs.

When the emergency network software is driven, the network device 100 uses the preset Internet protocol information, scanned network information, or communication information for a separate communication connection through an emergency network communication network, for example, a mobile communication network 400. The emergency network server 500 requests an emergency network connection (S120). At this time, the network device 100 preferably transmits the user's information. The transmitted network device 100 user information is determined by the emergency network server 500 by comparing the emergency network server 500 with previously stored service subscriber information (ie, network device user information registered to receive emergency network services). Is used.

The emergency network server 500 compares previously stored service subscriber information with user information transmitted by the network device 100 requesting an emergency network connection, and if the network device 100 is subscribed to the emergency network service, the network device 100. In step S130, a signal for authenticating the request is transmitted.

The emergency network server 500 connects the emergency network with the network device 100 through the mobile communication network 400 (S135), and from the connected network device 100, a main network (for example, wired LAN or wireless LAN-based). The information is read remotely (S140).

The emergency network server 500 diagnoses an error of the read main network information by using previously stored remote diagnosis information (S145) and checks whether there is an error in the main network information (S150). In this case, diagnosing the main network information by the emergency network server 500 means diagnosing software information including whether the network device 100 is identical to a driver, whether virus is detected, or network initialization information.

If it is determined that there is an error in the main network information, the emergency network server 500 detects pre-stored access control information corresponding to the network device 100, and uses the same to determine main network information of the network device 100. Reset (S155).

The network device 100 normally connects to the main network through the reset main network information (S160).

The emergency network server 500 checks whether the main network problem of the network device 100 has been solved, and thus normal connection is possible (S165).

The emergency network server 500 releases the emergency network connection when the network device 100 is normally connected to the main network (S170).

Accordingly, the emergency network server 500 performs a remote control and management necessary for the network device 100 as a master, and solves a main network problem related to software generated in a storage unit of the network device 100. The main network of 100 may support normal operation.

Some examples of emergency network services that can be solved through the process as shown in FIG. 4 are as follows.

First, when a user wants to use the Internet by connecting a telephone line to a portable laptop at a hotel in a foreign country, the telephone modem software displays the message "No dialup".

When the user clicks the emergency network connection icon of the notebook (ie, the network device), the user accesses the emergency network server through a wireless IP set through the communication module built in the notebook. At this time, the emergency network server is switched to master and notebook to slave.

The emergency network server reads and diagnoses the main network information of the user's notebook (for example, information such as software), and finds that the notebook modem driver of the notebook is damaged.

The emergency network server detects the telephone modem driver from the connection control information of the notebook in a separate database and transmits it to the notebook.

The emergency network server remotely installs the driver sent to the notebook and sets modem commands.

The emergency network server attempts to access the phone modem by providing the virtual private network (VPN) phone number of the user's area to the notebook. If the notebook modem's phone modem connection is successful, the emergency network server terminates the emergency network service and disconnects the emergency network.

Second, if the user's laptop is infected with a virus, the solution is as follows.

When the user clicks the emergency network connection icon of the notebook, the user accesses the emergency network server through a wireless IP set through the communication module built in the notebook. At this time, the emergency network server is switched to master and notebook to slave.

The emergency network server reads and diagnoses main network information of the user's notebook (for example, information such as software) and detects that the notebook's operating system and software are infected with a virus.

The emergency network server downloads an antivirus program to the notebook to treat the virus infected operating system and software.

The emergency network server checks the repaired operating system and software to terminate the emergency network service and disconnect the emergency network when the virus treatment is successfully completed.

Third, if the user has incorrectly set up the wired network address information of the notebook and a problem occurs in the wired network connection of the notebook, the solution is as follows.

When the user clicks the emergency network connection icon, the user accesses the emergency network server through a preset wireless IP through the communication module built in the notebook.

The emergency network server reads and diagnoses the main network information of the user notebook and finds that the notebook network address information is set incorrectly.

Emergency network server supports the network connection of the laptop by setting IP, Sub Net, Gateway, Dns information necessary for connection with the wired network operator through remote control, and if the laptop network connection is successful, emergency network service Exit and disconnect the emergency network.

Meanwhile, in contrast to the above example, when the main network is a network device connected to a mobile communication network (CDMA, GSM, etc.), the network connection problem may be solved by accessing an emergency network server through a local network (wired / wireless LAN) module.

By solving the above-described various problems, a user can solve a network connection problem by simply clicking an icon of a network device configured to make an emergency connection to an emergency network server even if the network related knowledge is insufficient. In addition, network connection problems can be solved more efficiently by coding problems and solutions that may occur in the network devices described below. This is a basic premise that the problem is automatically solved by an emergency network server or remotely solved by an operator. Shall be.

Examples of the causes and solutions of the problems to be coded in the emergency network server are as follows.

1) Cause: The modem is not compatible.

Solution: If you access another computer through an Internet connection, check the Microsoft Windows Hardware Compatibility List on the Microsoft Web site (http://www.microsoft.com/) for a list of compatible modems.

2) Cause: The modem is not connected properly or turned off.

Solution: Make sure your modem is properly connected to the correct port on your computer and, if you are using an external modem, make sure it is turned on.

3) Cause: Unable to connect to the remote access server.

Solution: Ask your system administrator if the remote access server is running. If the server goes down, the administrator checks for errors and checks the logs to see why the service was stopped, and restarts the service when the problem is resolved. If the service is running, the administrator checks whether other remote access clients can connect properly, and if other clients can connect, the problem may be specific to the user's workstation.

4) Cause: You do not have a valid user account or you do not have remote access permission.

Solution: Verify with your system administrator that your user account is set up and that you have remote access permissions.

5) Cause: The user dialed the wrong number or forgot the outside line access number such as # 9.

Solution: Make sure the dialed number is correct.

6) Cause: The modem cannot communicate with the server's modem.

Workaround: Use the same type of modem as the server.

7) Cause: The telephone line does not accept modem speed in places such as hotel rooms.

Workaround: Choose a lower bps speed.

8) Cause: You are trying to connect to a digital line.

Solution: Most modems only work with analog phone lines, so make sure you have installed an analog phone line. Or if you have a digital phone line installed, make sure the server and client have a digital modem.

9) Cause: The modem is not compatible with the server's modem at high speed bps.

Solution: Adjust the speed of your modem to slow bps.

10) Cause: The remote access server is not running.

Solution: Ask your system administrator if the server is running.

11) Cause: The target server is not running properly.

Solution: If you try to connect to the same server from another workstation and have the same problem on another workstation, there is a problem with the server application or hardware. If not, the problem is specific to your workstation.

12) Cause: Poor line quality.

Solution: Contact your telephone company to check the line quality.

13) Cause: The line you are calling is affecting the speed.

Solution: If you can connect to the remote access server using multiple numbers, try using a different number to see if that speeds up.

14) Cause: The modem software needs to be updated.

Solution: Check with the modem manufacturer to see if a modem software update is available.

Cause: The connection is interrupted because of a call waiting.

Solution: Make sure your phone has a call waiting feature, and if so, turn off call waiting and try again.

16) Cause: The connection was lost because the remote access server was not used.

Workaround: Retry the call.

17) Cause: The modem cable is disconnected.

Solution: Make sure the modem cable is connected properly.

Cause: Your modem cannot communicate correctly with the modem on the remote access server or your computer's serial port cannot maintain the speed you have chosen.

Solution: Try connecting at a low initial port speed.

19) Cause: The modem is not working properly.

Solution: Test the connection by enabling the modem login.

20) Cause: The cable is not compatible.

Solution: If your modem is communicating through a terminal rather than a network and dial-up connection, you will need to install a compatible cable because it is incompatible.

Cause: The serial port is in conflict.

Workaround: Com1 and Com3 share interrupt request (IRQ) 4, and Com2 and Com4 share IRQ 3, so you can't use COM1 and COM3 simultaneously or use COM2 and COM4 simultaneously for a serial connection. That is, you cannot use Terminal on COM3 while using Network and Dial-up Connections on COM1.

22) Cause: There is a problem with the hardware.

Solution: Verify that your ISDN adapter is installed and configured correctly.

23) Cause: The telephone number is not configured correctly.

Solution: In some cases, each B channel on an ISDN line has its own number; in other cases, two B channels share a single number, so contact your telephone company to find out how many numbers your ISDN line has.

Cause: You did not specify to use line type negotiation or the connection could not be established with the selected line type.

Workaround: Specify to use line type negotiation.

25) Cause: There was a problem with the TCP / IP connection and could not connect with the PPTP server.

Workaround: Users or system administrators can verify the connection with the server by using the ipconfig and ping commands.

Cause: The Winsock Proxy Client is active.

Solution: VPN connections cannot work with an active Winsock proxy client and disable the Winsock proxy client for system administrators because the virtual network connection can only process packets for encapsulation after the Winsock proxy immediately redirects the packets to the proxy server. Request to specify

Cause: The name could not be converted to an IP address because of a name resolution problem.

Workaround: Specify the domain full name and IP address in the connection.

Cause: The server does not support LCP extensions.

Workaround: If you are unable to connect to the server using PPP or if the remote computer terminates the connection, remove the check from the Enable LCP Extensions check box in Network and Dial-up Connections because the server may not support LCP extensions.

Cause: The TCP / IP utility could not run because there was a problem with the IP header compression.

Solution: Turn off IP header compression and try to reconnect.

30) Cause: The wrong LAN network adapter is shared.

Solution: A computer with Internet Connection Sharing requires two connections. That is, make sure that you have Internet Connection Sharing enabled when you connect your home network to the Internet, because one connection usually connects to a computer on your home network as a LAN adapter, and the other connection connects your home network to the Internet.

31) Cause: TCP / IP is not installed on your home network computer.

Solution: The TCP / IP protocol is installed by default on computers running Windows 2000, Windows 98, and Windows NT version 4.0. If a user on the home network is running an operating system other than the ones listed, that computer will have TCP / IP Make sure it is installed.

32) Cause: A user on the home network cannot access the Internet.

Solution: Because TCP / IP is incorrectly configured on your home network computer, verify that the TCP / IP settings are set on your home network local area connection.

33) Cause: The Internet Connection Sharing Service does not start.

Solution: Use Event Viewer to verify that the Internet Connection Sharing service is started.

Cause: The Internet Connection Sharing computer is not properly configured for name resolution.

Solution: If a computer on a small or home office network cannot translate a name to an IP address, you can use the ipconfig command to check the name resolution configuration of the Internet Connection Sharing computer. Your ISP can configure name resolution in two ways:

Statically assigned name server: Because you must manually configure the TCP / IP protocol using the IP address of the name server provided by your ISP, if you have a statically assigned name server, you can use the ipconfig command to configure the IP address of the name server at any time. Can be imported.

Dynamically specified name server: No manual configuration is required, so the IP address of the name server provided by your ISP is dynamically assigned each time you call your ISP. If you have a dynamically assigned name server, you will need to run the ipconfig command after connecting to your ISP.

       As described above, the emergency network server analyzes various network-related problems, arranges solutions, codes them, and can perform more efficient remote diagnosis processing.

In the above description of the present invention, specific embodiments have been described, but various modifications may be made without departing from the scope of the present invention. Therefore, the scope of the present invention should not be defined by the described embodiments, but should be determined not only by the claims but also by the equivalents of the claims.

As described above, the present invention enables the user to run the emergency network software to normalize the main network connection when the main network does not operate normally while the network device is in use, thereby enabling remote service and network connection in an emergency situation.

In addition, the present invention can easily handle network problems difficult for the user by using the emergency network service, and even if the user lacks network-related knowledge, the emergency set in the network device to emergency access to the emergency network server provided by the present invention You can handle network problems by simply clicking on the network connection icon.

Claims (27)

Emergency network server for supporting emergency network service for normalizing main network connection of the network device, and emergency network software for executing the emergency network service when the main network does not operate normally on any network device. In the service providing method of the emergency network remote service system comprising a network device, Requesting an emergency network connection to the emergency network server when the network device has a main network problem; Determining, by the emergency network server, whether to join the emergency network service of the requested network device; If the network device is a network device subscribed to the emergency network service, the emergency network server connecting an emergency network through the emergency network network with the network device; And the emergency network server remotely controlling a network device connected to the emergency network to solve the main network problem. The method of claim 1, The emergency network software includes emergency network information, main network interface control information, remote management, manual management, and status resolution. The method of claim 1, The main network is characterized in that any one of a wired LAN (Lan) or wireless LAN. The method of claim 1,  The emergency network is a mobile communication network. The method of claim 1, And registering, by the network device, the information of the network device user by accessing the emergency network server. The method of claim 1, After the emergency network server solves the main network problem of the network device, disconnecting the emergency network; And setting the network state of the network device to a normal main network state. The method of claim 1, wherein the requesting process is Running emergency network software when the network device encounters a main network problem; Requesting an emergency network connection to the emergency network server using the IP information preset in the emergency network software. The method of claim 7, wherein the driving step Running emergency network software upon user request via input means provided in the network device. The method of claim 8, The input means is characterized in that the icon (Icon). The method of claim 1, wherein the requesting process is If the main network connection module of the network device is a module for accessing a mobile communication network, requesting an emergency network connection to the emergency network server through either a wired LAN or a wireless LAN. The method of claim 1, wherein the linking process is And wherein the emergency network server connects the emergency network with the network device through any one of a wired LAN and a wireless LAN. The method of claim 1, wherein the determining process And determining whether the server subscribes to the emergency network service by using the stored service subscriber information. The method of claim 1, wherein the linking process And the server notifying the network device after connecting the network device with the emergency network. The method of claim 1, wherein the solution process Remotely reading main network information from the network device connected to the emergency network; Diagnosing an error of the read main network information by using previously stored remote diagnosis information; And resetting the main network information of the network device by using previously stored access control information corresponding to the network device when it is determined that the main network information has an error as a result of the diagnosis. The method of claim 14, wherein the access control information is And information for controlling a main network connection of certain network devices. The method of claim 15, wherein the access control information is Type of a given network device. A method comprising a network adapter and driver type and corresponding driver, a regional VPN and telephone modem access telephone number, and a built-in wireless network identification number. In the emergency network service system for normalizing the main network connection of the network device when the main network does not operate normally on any network device, A network device connected via an emergency network and an emergency network communication network for receiving emergency network service for normalizing the main network connection when a problem occurs in the main network, and having emergency network software for executing the emergency network service; And an emergency network server that provides the emergency network service by remotely controlling the network device when the network device and the emergency network are connected through the emergency network software. The method of claim 17, The emergency network software includes emergency network information, main network interface control information, remote management, manual management, and status resolution. The method of claim 17, And said emergency network communication network is a mobile communication network. The method of claim 17, The main network is an emergency network service system, characterized in that any one of a wired LAN (Lan) or wireless LAN. 18. The network device of claim 17, wherein the network device is Emergency network service system, characterized in that it comprises a communication module for emergency network connection with the emergency network server. 18. The network device of claim 17, wherein the network device is When the main network connection module is a communication module for accessing a mobile communication network when a problem occurs in the main network, the emergency network connection request to the emergency network server through any one of a wired LAN or a wireless LAN. Emergency network service system. 18. The network device of claim 17, wherein the network device is And emergency network software in response to a user request when the main network problem occurs, and requesting an emergency network connection to the emergency network server using IP information preset in the emergency network software. 24. The network device of claim 23, wherein said network device is Emergency network service system characterized in that for running the emergency network software when a user request through a predetermined input means. The method of claim 24, The input means is an emergency network service system, characterized in that the icon (Icon). 18. The system of claim 17, wherein the emergency network server is A user information storage unit which stores access control information for controlling network access of predetermined network devices, and stores the emergency network service subscriber information; A user information manager for determining whether to join the emergency network service of the network device by using the service subscriber information when an emergency network connection request is received from a predetermined network device; When the network device and the emergency network are connected according to the determination result of the user information manager, the main network information of the network device is read remotely to diagnose an error, and if there is an error in the main network information, the corresponding information is reset to reset the information. A remote control manager which detects and outputs connection control information from the user information storage; And an input / output interface control unit for transmitting the outputted access control information to the network device to reset the main network information. The method of claim 26, wherein the access control information is Type of a given network device. Emergency network service system, including network adapter and driver type and corresponding driver, regional VPN and telephone modem access telephone number and built-in wireless network identification number.

Images