KR100818164B1 - How to automatically set network interworking information and its network system - Google Patents

Abstract

A method for automatically setting network interworking information and a network system thereof are disclosed. The method for automatically setting network interworking information according to the present invention includes storing, in a BOOTP server, an IP address table including a vendor identifier of the client, an IP address, and an IP address of at least one interworking node; Broadcasting a boot request message including a vendor identifier of the BOOTP server, searching whether the vendor identifier included in the boot request message is in the IP address table, and the vendor identifier included in the boot request message is If the IP address table is present, the BOOTP server broadcasting a boot reply message including a vendor identifier included in the boot request message, an IP address of the client, and an IP address of the at least one interworking node; And setting, by the BOOTP client, the IP address of the client included in the boot reply message as its IP address if the vendor identifier included in the boot reply message matches its vendor identifier.

Description

Method for setting automatically networking information and network system there-of}

BRIEF DESCRIPTION OF THE DRAWINGS In order to better understand the drawings cited in the detailed description of the invention, a brief description of each drawing is provided.

1 is a view for explaining a network address setting method according to the prior art.

2 is a view for explaining a method for automatically setting network interworking information according to an embodiment of the present invention.

3 is a flowchart illustrating a method for automatically setting network interworking information according to an embodiment of the present invention.

4 is a table illustrating a function before a change and a function after a change of a field used in a BOOTP message according to an embodiment of the present invention.

The present invention relates to a network system, and more particularly, to a method and a system capable of automatically setting network interworking information (for example, an IP address) through communication with another server.

The telephone company has various kinds of service providing systems and EMS (Element Management System) systems for managing the service providing system. In general, whenever a network manager adds a new device (eg, a service providing system), the network manager should access the device to set a local IP address and set an IP address of the EMS to be interworked with.

It is never easy for a network administrator within a telephone company with hundreds of such equipment to assign and set the IP addresses of all EMSs and service delivery systems. In addition, if you manually set up the network address, you can set the IP address incorrectly so that the unique IP address overlaps with other devices or set the wrong IP address of the EMS to be linked. In some cases.

In some cases, it is necessary to change the IP address of the EMS due to network construction. In this case, the network administrator must reset the IP address of the EMS to be connected to all service providing systems in the telephone company. This not only burdens the administrator, but also causes frequent mistakes in accessing dozens of devices in a short time and setting the IP address of the EMS. Also, setting up an IP address by connecting to an individual system can be time consuming.

1 is a view for explaining a network address setting method according to the prior art.

1 shows a plurality of HLR devices 11-1 to 11-99 installed in a telephone company, an HLR EMS system 13 for managing a plurality of HLR devices 11-1 to 11-99, and a plurality of SMSCs. Devices 12-1 to 12-99, an SMSC EMS system 14 for managing a plurality of SMSC devices 12-1 to 12-99, and the plurality of HLR devices 11-1 to 11; -99) shows the switch hub 15 for the connection between the HLR EMS system 13, the plurality of SMSC equipments 12-1 to 12-99 and the SMSC EMS system 14.

Among these devices, the first to the 98th HLR devices 11-1 to 11-98, the HLR EMS system 13, the SMSC devices 12-1 to 12-99 and the SMSC EMS system 14 and the switch It is assumed that a case where the 99th HLR device (99th HLR device, 11-99) is additionally installed in the situation where the hub 15 is already installed.

In this case, according to the prior art, the network operator directly set the network interworking address (that is, the local IP address of the equipment to be added and the IP address of the EMS to be interworked) when the 99th HLR system 11-99 is installed. The setting procedure is as follows.

First, the operator accesses the console of the 99th HLR system 11-99, sets an IP address after inquiring a network administrator of the 99th HLR system 11-99 IP address. Next, after inquiring the IP address of the EMS (i.e., HLR EMS 13) to be interworked, the network manager records the IP address in the configuration file of the 99th HLR system 11-99. Inquire the network administrator of the IP address of the other interworking node (server or system), and record the information in a configuration file of the 99th HLR system 11-99. Finally, it is checked whether the interworking between the 99th HLR system 11-99 and the HLR EMS 13 is performed.

As described above, when the operator manually sets the interworking information between devices, a mistake may occur in the process of setting the IP address of the EMS by accessing dozens of devices in a short time as well as placing a load on the manager.

Therefore, the technical problem to be achieved by the present invention is to automatically set the network interworking information between the equipment, a method for automatically setting the network interworking information that can reduce the workload and the possibility of interworking error for the administrator or operator, for executing The present invention provides a recording medium recording a program and a network system capable of performing the method.

The method for automatically setting network interworking information according to an embodiment of the present invention for achieving the above technical problem includes a vendor identifier, an IP address of the client, and an IP address of at least one interworking node in a BOOTP server. Storing an IP address table; The BOOTP client broadcasting a boot request message including its vendor identifier; The BOOTP server searching whether the vendor identifier included in the boot request message is in the IP address table; If the vendor identifier included in the boot request message is in the IP address table, the BOOTP server may include a vendor identifier included in the boot request message, an IP address of the client, and an IP address of the at least one interworking node. Broadcasting the triple-live message; And setting the IP address of the client included in the boot reply message as its own IP address if the vendor identifier included in the boot reply message matches the vendor identifier of the BOOTP client.

The method may further include: setting, by the BOOTP client, the IP address of the at least one interworking node included in the boot reply message to an IP address of its interworking node; And the BOOTP client may further comprise the step of attempting to access the IP address of the own interworking node.

The at least one interworking node includes an EMS system for managing the client.

The network system according to an embodiment of the present invention for achieving the above technical problem includes a BOOTP client and a BOOTP server.

The BOOTP client broadcasts a boot request message containing its vendor identifier. The BOOTP server stores an IP address table including a vendor identifier of the client, an IP address, and an IP address of at least one interworking node, and searches whether the vendor identifier included in the boot request message is in the IP address table. If the vendor identifier included in the boot request message is in the IP address table, the BOOTP server may include a vendor identifier included in the boot request message, an IP address of the client, and an IP address of the at least one interworking node. Broadcast a triple lie message. When the vendor identifier included in the boot reply message matches the vendor identifier of the BOOTP client, the BOOTP client sets the IP address of the client included in the boot reply message as its own IP address.

The BOOTP client may set an IP address of the interworking node included in the boot reply message as an IP address of its own interworking node, and attempt to access the IP address of its own interworking node.

The BOOTP client is any one of a home location register (HLR), a short message service center (SMSC) and a multimedia message service center (MMSC) for a mobile communication network, and the BOOTP server is the home location register (HLR) and the short message. It may be a device for managing any one of a service center (SMSC) and the multimedia message service center (MMSC).

In order to fully understand the present invention, the operational advantages of the present invention, and the objects achieved by the practice of the present invention, reference should be made to the accompanying drawings which illustrate preferred embodiments of the present invention and the contents described in the accompanying drawings.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. Like reference numerals in the drawings denote like elements.

2 is a view for explaining a method for automatically setting network interworking information according to an embodiment of the present invention.

Referring to FIG. 2, an operating network system according to an embodiment of the present invention includes a plurality of home location register (HLR) devices 21-1 to 21-99 and a plurality of HLR devices 21-1. HLR EMS system 23 for managing ~ 21-99, a plurality of SMSC (Short Message Service Center) equipment (22-1 ~ 22-99), and a plurality of SMSC equipment ( And a SMSC EMS system 24, a switch hub 25, and a BOOTP (IP / UDP Bootstrap Protocol) server 26 for managing 22-1 to 22-99.

The operating network system can be installed in one telephone company.

The switch hub 25 has a plurality of SMSC devices 22-1 to 22-99 and an SMSC EMS system 24 between the plurality of HLR devices 21-1 to 21-99 and the HLR EMS system 23. It physically connects each other.

The BOOTP server 26 is a bootstrap protocol (BOOTP) based server and provides a predetermined service in response to a request of a BOOTP client. It also stores a table of IP addresses for BOOTP clients.

Here, the BOOTP client is a BOOTP-based device, and the plurality of HLR devices 21-1 to 21-99 and the plurality of SMSC devices 22-1 to 22-99 correspond to BOOTP clients, respectively.

Among these devices, the first through the 98th HLR devices 21-1 through 21-98, the HLR EMS system 23, the SMSC devices 22-1 through 22-99, the SMSC EMS system 24, and the switches It is assumed that the 99th HLR device (99th HLR device, 21-99) is additionally installed in the situation where the hub 25 is already installed.

3 is a flowchart illustrating a method for automatically setting network interworking information according to an embodiment of the present invention.

2 and 3, first, an IP address table of BOOTP clients is stored in the BOOTP server 26.

Table 1 is a table showing the IP address table of the BOOTP server 26 according to an embodiment of the present invention.

Referring to this, the IP address table includes a vendor ID field, an EMS IP field, a client IP field, and an interworking node address field. The vendor ID field is information for identifying a client (a unique name of the client device) in addition to the IP assigned to each client, and may be set by an operator. For example, the vendor ID may include a client device name (eg HLR) and a serial number (eg 1, ..., 99). For each vendor ID, the corresponding EMS IP, client IP, and interworking node address are set. In this case, the EMS IP is the IP address of the EMS device managing the client, the client IP is the IP address of the client itself, and the interworking node address is the IP address of another network node (server or device) to which the client should interwork. When there are a plurality of different network nodes, a plurality of interworking node addresses may be set.

Referring to Table 1, for each of the first to 99th HLRs 21-1 to 21-99, different vendor IDs (HLR # 1 to HLR # 99) and client IPs (eg, 192.168.10.1, ... , 192.168.10.99) is set. In this embodiment, since EMSs (that is, HLR EMSs) managing the first to 99th HLRs 21-1 to 21-99 are the same, the EMSs for the first to 99th HLRs 21-1 to 21-99 are the same. The EMS IPs are all set to the same value (eg 192.1.2.1). In addition, IP addresses (eg, GLR1 = 10.10.1.1, SG = 10.10.5.1) of the nodes GLR1 and SG to which the first to 99th HLRs 21-1 to 21-99 should interwork, are also set.

Also for the first to 99th SMSCs 22-1 to 22-99, different vendor IDs (SMSC # 1 to SMSC # 99) and client IPs (for example, for each SMSC device 22-1 to 22-99). 50.1.1.11, ..., 50.1.1.109) are set. In the present embodiment, since the EMSs managing the first to 99th SMSCs 22-1 to 22-99 (that is, the SMSC EMS 24) are the same, the first to 99th SMSCs 22-1 to 22-99 are the same. The EMS IPs for all) are set to the same value (eg, 50.1.1.2). In addition, IP addresses of nodes to which the first to ninth SMSCs 22-1 to 22-99 should interwork are set. For example, IP addresses (HLR1 = 192.168.10.1, HLR2 = 192.168.10.2) of nodes (HLR1 and HLR2) to which the first SMSC (vendor ID: SMSC # 1) should interwork are set.

When the operator first installs the EMS in the telephone company, the operator creates an IP table as shown in Table 1 and stores it in the BOOTP server 26. In Table 1, IP address tables are set for a total of 99 HLRs and 99 SMSCs, but enough IPCs for SMSCs and HLRs can be preset in consideration of scalability.

In addition, in this embodiment, the BOOTP server 26 is provided separately from the EMS devices 23 and 24, but each EMS device 23 and 24 may be the BOOTP server 26. As shown in FIG. That is, the BOOTP server function may be implemented by being included in the EMS device. In this case, an IP address table for each HLR may be set and stored in the HLR EMS 23, and an IP address table for each SMSC may be set and stored in the SMSC EMS 24.

As described above, it is assumed that the 99th HLR equipment (99th HLR equipment, 21-99) is additionally installed.

In this case, the system operator accesses the 99th HLR device 21-99 to be expanded to set up a local device, that is, its own vendor ID (eg, HLR # 99), and sets the extension of the 99th HLR 21-99 to be expanded. By starting the BOOTP client program, network interworking information can be set automatically. The BOOTP client program is a BOOTP-based program for interworking with the BOOTP server 26.

4 is a table illustrating a function before a change and a function after a change of a field used in a BOOTP message according to an embodiment of the present invention.

3 and 4, the method for automatically setting network interworking information according to an embodiment of the present invention will be described in more detail as follows.

Before the method for automatically setting network interworking information according to the embodiment of the present invention shown in FIG. 3 is performed, as shown in FIG. 2, the physical connection of the network is established, and the IP address table shown in Table 1 is a BOOTP server ( Assume that it is preset in (26).

When the BOOTP client program of the 99th HLR 21-99 is started, the 99th HLR 21-99 broadcasts a boot request message ("BOOTREQUSET" message) (S10). If the 'op' field of a message is set to 1, the message becomes a "BOOTREQUEST" message. At this time, the vendor ID (HLR # 99) of the 99th HLR (21-99) is set in the 'vend' field of the "BOOTREQUEST" message is broadcast (S10).

The BOOTP server 26, which has received the broadcasted "BOOTREQUEST" message, searches whether there is an IP address having a vendor ID of 'HLR # 99' in a preset and stored IP address table (S20).

If the search result is that the IP address whose vendor ID is 'HLR # 99' is not in the IP address table, the BOOTP server 26 does not respond to the corresponding "BOOTREQUEST" message. In other words, the received "BOOTREQUEST" message is discarded. On the other hand, if the IP address of the vendor ID 'HLR # 99' is found in the IP table, the BOOTP server 26 broadcasts a boot reply message ("BOOTREPLY" message) (S30).

If the 'op' field of a message is set to 2, the message becomes a "BOOTREPLY" message. The "BOOTREPLY" message includes a vendor ID field, a yiaddr field, a siaddr field, and a file field.

A vendor ID (HLR # 99) of the 99th HLR 21-99 is set in the vendor ID field, and a client IP (that is, an IP address of the 99th HLR, eg, 192.168.10.99) is set in the yiaddr field. In the field, the IP address of the HLR EMS 23 (eg, 192.1.2.1) is set. In the file field, IP addresses of the node to which the 99th HLR 21-99 should interwork (eg, GLR1 = 10.10.1.1, SG = 10.10.5.1) is set.

Receiving the " BOOTREPLY " message broadcast from the BOOTP server 26, the 99th HLR 21-99 compares the vendor ID of the received " BOOTREPLY " message with its own vendor ID (HLR # 99). "If the vendor ID of the message is different from the vendor ID (HLR # 99) of the local device (i.e., itself), the received" BOOTREPLY "message is discarded (S40).

On the other hand, if the vendor ID of the " BOOTREPLY " message is the same as the vendor ID (HLR # 99) of the local device (i.e., his / her), then the 99th HLR 21-99 is based on the yiaddr field of the " BOOTREPLY " message. Set the IP address (S50), set the IP address of the HLR EMS 23 (e.g. 192.1.2.1) based on the siaddr field (S60), and set the IP address in the file field (e.g. GLR1 = 10.10.1.1) , SG = 10.10.5.1) is extracted to set IP addresses (eg, GLR1 = 10.10.1.1, SG = 10.10.5.1) of nodes to which the 99th HLRs 21-99 should interoperate (S70).

In addition, an attempt is made to connect to the HLR EMS 23 and the other interworking nodes (not shown) by using the IP address of the HLR EMS 23 and other interworking nodes configured (S80).

As described above, according to the embodiment of the present invention, all systems in the telephone company using the BOOTP protocol are assigned the IP address of the local equipment (client equipment) from the BOOTP server 26, and at the same time the EMS and the interlocking server. Set up an IP address by extracting up to an IP address.

Therefore, according to the present invention, when the IP address of the EMS is changed or when the equipment is newly added, the operator does not need to change the network interworking information by logging in to the equipment.

Therefore, even if the operator installing the new system does not know the IP address of the EMS and the local equipment, it is possible to interwork all the operating networks.

In addition, as shown in Figure 4, by utilizing the fields defined in the BOOTP message can be used without changing the general BOOTP protocol.

In the above-described embodiment, the case where the BOOTP client is an HLR or SMSC is described. However, the BOOTP client may be another network component (eg, a multimedia message service center (MMSC)), and the BOOTP server may also be configured in another network. It may be an EMS device for managing an element (eg, multimedia message service center (MMSC), etc.).

The invention can also be embodied as computer readable code on a computer readable recording medium. The computer-readable recording medium includes all kinds of recording devices in which data that can be read by a computer system is stored. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disks, optical data storage devices, and the like, which are also implemented in the form of carrier waves (for example, transmission over the Internet). Include. The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

Although the present invention has been described with reference to the above embodiments, it is merely illustrative, and those skilled in the art will understand that various modifications and equivalent other embodiments are possible therefrom. . Therefore, the true technical protection scope of the present invention will be defined by the technical spirit of the appended claims.

As described above, according to the present invention, the network interworking information of the network equipment constituting the operation network can be set automatically. Accordingly, by installing new network equipment or automatically setting the network interworking information when the interworking information of the EMS equipment is changed, it is possible to reduce the workload and the possibility of interworking errors for the manager or the operator.

Claims (10)

Storing, in the BOOTP server, an IP address table including a vendor identifier of the client, an IP address, and an IP address of at least one interworking node; The BOOTP client broadcasting a boot request message including its vendor identifier; The BOOTP server searching whether the vendor identifier included in the boot request message is in the IP address table; If the vendor identifier included in the boot request message is in the IP address table, the BOOTP server may include a vendor identifier included in the boot request message, an IP address of the client, and an IP address of the at least one interworking node. Broadcasting a triple lie message; And And setting the IP address of the client included in the boot reply message as its own IP address when the vendor identifier included in the boot reply message matches the vendor identifier of the BOOTP client. How to set up automatically. The method of claim 1 wherein the method is Setting, by the BOOTP client, the IP address of the at least one interworking node included in the boot reply message to the IP address of its interworking node; And And the BOOTP client attempting to connect to the IP address of its own interworking node. The method of claim 2, wherein the at least one interworking node is Method for automatically setting the network interworking information, characterized in that it comprises an EMS system for managing the client. The method of claim 3, wherein The vendor identifier is in a predefined 'vend' field of the boot reply message, the IP address of the client is in a predefined 'yiaddr' field of the boot reply message, and the IP address of the EMS system is the bootley. In the predefined 'siaddr' field of the fly message, and the IP address of the interworking node, in addition to the EMS system, is automatically set in the predefined 'file' field of the boot-fly message. How to set. The method of claim 2, wherein the method Discarding, by the BOOTP server, the boot request message if the vendor identifier included in the boot request message is not present in the IP address table; And And discarding the boot reply message by the BOOTP client if the vendor identifier included in the boot reply message does not match its vendor identifier. The method of claim 2, The BOOTP client is any one of a home location register (HLR), a short message service center (SMSC) and a multimedia message service center (MMSC) for a mobile communication network. And the EMS system is a device for managing any one of the home location register (HLR), short message service center (SMSC) and multimedia message service center (MMSC). A recording medium having recorded thereon a computer program for executing the method for automatically setting the network interworking information according to any one of claims 1 to 6. A BOOTP client broadcasting a boot request message including its vendor identifier; And An IP address table including a vendor identifier of the client, an IP address, and an IP address of at least one interworking node, and searching for whether the vendor identifier included in the boot request message is in the IP address table. Is included in the IP address table, the BOOTP server includes a vendor identifier included in the boot request message, an IP address of the client, and an IP address of the at least one interworking node. Equipped with a BOOTP server for broadcasting the And the BOOTP client sets the IP address of the client included in the boot reply message as its own IP address if the vendor identifier included in the boot reply message matches its vendor identifier. The method of claim 8, wherein the BOOTP client is And setting the IP address of the interworking node included in the boot reply message as the IP address of its own interworking node, and attempting to access the IP address of its own interworking node. The method of claim 9, The BOOTP client is any one of a home location register (HLR), a short message service center (SMSC) and a multimedia message service center (MMSC) for a mobile communication network. The BOOTP server is a device for managing any one of the home location register (HLR), the short message service center (SMSC) and the multimedia message service center (MMSC).

Images