KR100958918B1 - Subscriber database server system and method of providing backward compatibility - Google Patents

Abstract

The present invention relates to a subscriber database server system, and more particularly, to a subscriber database server system having backward compatibility to which a lower version of a program can be applied while improving the performance of a subscriber database server system for providing subscriber customer information in a mobile communication system. And a method for providing backwards compatibility.

The subscriber database server system in a mobile communication system according to an embodiment of the present invention includes a first processor server supporting a higher version, a second processor server supporting a lower version, and a management server storing subscriber customer information. The management server may include a subscriber database storing the subscriber customer information, a first service daemon for allowing a first processor server to access the subscriber database, and a second processor server for accessing the subscriber database. 2 Include a service daemon.

Subscriber Database Server, Backward Compatibility

Description

Subscriber database server system and method of providing backward compatibility

The present invention relates to a subscriber database server system, and more particularly, to a subscriber database server system having backward compatibility to which a lower version of a program can be applied while improving the performance of a subscriber database server system for providing subscriber customer information in a mobile communication system. And a method for providing backwards compatibility.

The demand for communication services is rapidly increasing, including the generalization of information and communication services, the emergence of various multimedia services, and the emergence of high quality services. In mobile communication, the demand of subscribers of mobile communication voice call service is saturating, but the number of subscribers is increasing as various additional services are developed continuously.

The mobile communication system utilizes a wide range of infrastructure devices such as base stations and core networks to send and receive individual contents such as pictures, videos, music, and games to users and perform various services. In particular, in recent years, as well as voice call service, which is a major service of mobile communication systems, hundreds of thousands of additional services have been developed to satisfy user needs.

For example, these supplementary services provide users with various supplementary services such as ring-to-yu, phone messenger, terrestrial or satellite DMB broadcasting, video chat, video ring-to-yu, video mailbox, and video conferencing.

When these additional services are newly developed, they may be sequentially applied to the mobile communication network. A new server is added for the new additional service, and along with this, other servers in the existing mobile communication network are required to update the database according to the new service.

Existing servers that update programs for additional services to increase the version of the program package sometimes have a risk of failing to interwork with other servers. This is because, while updating the servers that work before being updated as a whole, they cannot continue to operate, and bugs can accumulate, causing the server to stop working. This phenomenon can be a serious problem in a mobile communication network where reliable service provision is important.

On the other hand, as the number of mobile communication subscribers and mobile communication services are diversified, the load on a core network performing call processing is increasing. Accordingly, such subscriber database servers may cause resource contention by simultaneously performing database operations such as updating a database or moving data in a database, and call processing that performs a mobile communication service as a component of a communication network. Can be.

Therefore, there is a need for a method of providing a compatibility of a system with different versions while improving the performance of a subscriber database server in mobile communication, and a server system having such compatibility.

The present invention has been made in view of the above problems, and an object thereof is to provide a subscriber database server providing backward compatibility and a method of providing backward compatibility.

In addition, it is intended to improve the performance of the subscriber database server system by separating the database work and the call processing work.

The objects of the present invention are not limited to the above-mentioned objects, and other objects that are not mentioned will be clearly understood by those skilled in the art from the following description.

Subscriber database server system in a mobile communication system according to an embodiment of the present invention for achieving the above object comprises a first processor server for supporting a higher version; A second processor server supporting a lower version; And a management server for storing subscriber customer information. The management server includes a subscriber database in which the subscriber customer information is stored; A first service daemon that allows the first processor server to access the subscriber database; And a second service daemon that allows the second processor server to access the subscriber database.

A subscriber database server system in a mobile communication system according to another embodiment of the present invention for achieving the above object is at least one processor server for providing subscriber customer information to the core network; At least one management server for storing the subscriber customer information in a database; And a switching unit connecting to the management server from the processor server. Some of the processor servers are higher version processor servers and others are lower version processor servers, and the management server includes a service daemon that controls the lower version processor servers to access the database.

In order to achieve the above object, there is provided a method for providing backward compatibility in a subscriber database server system according to another embodiment of the present invention, the processor server accessing a management server; Identifying a version of the processor server and activating a service daemon suitable for the version; Acquiring, by the processor server, subscriber customer information stored in the management server; And providing, by the processor server, the subscriber customer information to a core network.

According to an embodiment of the present invention, even when a version difference occurs due to the addition of a new service or the update of an existing service, the subscriber database server system is stably operated by providing backward compatibility, and thus, in the entire mobile communication network The risk of new service or service renewal can be reduced to increase the stability of mobile communication system.

In addition, by separating the subscriber database server into a processor server and a management server, it is possible to reduce the load of each of the processor server and the management server, and improve the performance of the subscriber database server system by efficiently processing the data of each server. have.

The effects of the present invention are not limited to the above-mentioned effects, and other effects not mentioned will be clearly understood by those skilled in the art from the description of the claims.

Specific details of other embodiments are included in the detailed description and the drawings. Advantages and features of the present invention and methods for achieving them will be apparent with reference to the embodiments described below in detail with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but can be implemented in various different forms, and only the embodiments make the disclosure of the present invention complete, and the general knowledge in the art to which the present invention belongs. It is provided to fully inform the person having the scope of the invention, which is defined only by the scope of the claims. Like reference numerals refer to like elements throughout.

Preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram illustrating a UMTS communication network according to an embodiment of the present invention.

Referring to FIG. 1, a UMTS communication network according to an embodiment of the present invention is connected to a terminal 10, a radio access network (UTRAN; UMTS Terrestrial RAN, 20), and a wireless access network, and responds to a connection with an external network 40. It may include a core network (Core Network, 30). Such a UMTS communication network is called a public land mobile network (PLMN).

The terminal 10 may include personal digital assistants (PDAs), computers, and the like capable of wireless communication as well as user equipment used for wireless communication. The terminal 10 may be fixed or mobile and may be called by other terms such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), and a wireless device.

The terminal 10 identifies a mobile device (ME) 13, which is a wireless terminal used for wireless communication, and a subscriber through a Uu interface, performs an authentication algorithm, and performs authentication and encryption keys required by the terminal. It includes a subscription authentication module (USIM: UMTS Subscriber Identity Module) 17 that stores subscription information. Here, the Uu interface is a radio interface in WCDMA mobile communication.

A radio access network (RAN) 20 includes a base station 22 and a base station controller 24 that accommodates a 3GPP standard radio access standard to support WCDMA. The radio access network 20 transmits a call request signal or the like from the terminal to the core network.

The base station 22 sets a wireless physical channel necessary for data exchange with the terminal 10 according to the control information transmitted from the base station controller 24, and transfers the data transmitted from the upper layer protocol to the terminal 10 according to the wireless environment. send. In addition, the data received from the terminal 10 is transmitted to the upper layer protocol of the base station controller 24. The base station 22 supports various radio access technologies such as channel coding, interleaving, modulation, and demodulation for data transmission in a radio section. The base station 22 generally refers to a fixed station that communicates with the terminal 10, and in other terms, such as a node-B, a base transceiver system (BTS), and an access point. Can be called.

A base station controller (Radio network controller) 24 dynamically allocates radio resources of the wireless communication system and controls the base station 22. The base station controller 24 includes wired and wireless channel management, protocol matching of the mobile communication terminal 10, and protocol matching of the base station. Soft handoff processing, protocol matching with Core Network, General Packet Radio Service (GPRS) access, fault management, system loading, etc. The base station controller 24 serves as an access point for services provided through a core network.

The mobile switch center 31 transfers incoming or outgoing signals from the base station 22, and provides a function for exchanging mobile subscribers with each other, and for exchanging mobile subscribers with fixed network subscribers such as PSTN and ISDN. . The circuit switch 31 processes basic and additional services, processes an incoming signal of the mobile communication terminal 10 in association with an existing network or another network, and processes location registration and handoff.

The circuit switched gateway (GMSC) 32 is a gateway at the point where the circuit switched 31 is connected to the external network 40. All circuit switched connections are made via circuit switched gateway 32.

The circuit switching unit 100 may be referred to as a circuit switching unit 100 including the circuit switch 31 and the circuit switching gateway 32. The circuit switching unit 100 establishes a communication path with the terminal 10 through a circuit switching connection. .

The Serving GPRS Support Node (SGSN) 35 (SGSN) is a mobile station for managing GPRS services, an outgoing / outgoing call processing procedure, and a session management, authentication and billing function for handling transmission and reception of packet data. And so on. It also has a routing processing function of packet data.

A packet switching gateway (GGSN) 36 is a serving node of an IP (Internet Protocol) based packet network that provides a high speed packet data service for GPRS data service. It manages the network data, handles routing of packet data, and provides an interface for connecting the WDCMA network to the Internet.

The packet switching support node 35 and the packet switching gateway 36 may be referred to as a packet switching unit 200. The packet exchange unit 200 transmits and receives data in packet units in data transmission and reception of a terminal.

The external network 40 is a network connected to the outside through the circuit switching unit 100 or the packet switching unit 200. The circuit switching unit 100 is related to the transmission and reception of circuits such as voice calls. The circuit switching unit 100 may be a public switched telephone network (PSTN), an integrated services digital network (ISDN), or a public land mobile network (PLMN). The packet exchange unit 200 is related to the transmission and reception of packets. The packet exchange unit 200 may be an Internet Protocol (IP) network such as the Internet.

The subscriber database server 50 stores or manages the subscriber's static subscription information and security related information. The subscriber database server 50 may include, for example, a home location register (HLR), an authentication center (AuC), an equipment identity register (EIR), and the like. Servers may include a database that stores subscriber customer information.

The subscriber customer information may include various information such as location information and identification information in the user's terminal. The subscriber customer information may include location information of the current subscriber, profile information indicating the subscriber's information, and the like. In particular, it may include the main plan used by subscribers and additional service information currently subscribed to customers. In addition, the subscription information may include history information of the plan or the additional service. Or, it may include personal information about the subscription customer. Personal information of the subscriber may include the date of birth, address, social security number, the date of registration.

The subscriber database server 50 may include a processor server 300 and a management server 400. The processor server 300 delivers information requested by the core network to the core network or instructs the management server 400 to perform a task. The management server 400 performs database operations such as storing or updating subscriber customer information.

Figure 2 shows a block diagram of a subscriber database server system according to an embodiment of the present invention.

2, a subscriber database server system 50 according to an embodiment of the present invention may include a processor server 300, a management server 400, and a switching unit 500.

The management server 400 stores the subscriber customer information and allows the processor server 300 to access the subscriber database to obtain subscriber customer information necessary for call processing. The management server 400 manages subscriber customer information in a database and stores subscriber customer information in a large amount of storage. Storage may consist of a collection of disks in a plurality of arrays. The management server 400 may be configured in a pair to stably provide subscriber customer information.

Accordingly, the first management server 410 stores subscriber customer information in the first subscriber database and the second management server 420 stores subscriber customer information in the second subscriber database. The first subscriber database and the second subscriber database may in principle store the same subscriber customer information. The second management server 420 has a second subscriber database that replicates the first subscriber database in real time or at regular time intervals. Thus, even if one of the first or second management servers 410 and 420 is stopped or either the first subscriber database or the second subscriber database is damaged, the subscriber customer information can be provided through the other management server. Can perform stable service.

The processor server 300 provides customer information necessary for data call or call connection by interworking with the core network of the mobile communication. The processor server 300 may be linked with the management server 400 to query and change necessary data. The processor server 300 may include a plurality of 310, 320, 330, and 340. The processor server 300 may access the database of the management server to obtain subscriber customer information and provide the subscriber customer information to the circuit switch or packet switched support node. In addition, the processor server 300 may issue a work command to the management server to store and update data of the management server 400. In order to request subscriber customer information from the circuit switching unit 100 or the packet switching unit 200, one of the plurality of processor servers 310, 320, 330, and 340 may be called by a round robin method. Can be.

The switching unit 500 serves to connect the processor server 300 to access the subscriber database of the management server 400. The switching unit 300 connects the processor servers to one of the first or second management servers 410 and 420 when they are configured in pairs. The switching unit 500 may be configured as a hub, a router, or an Ethernet switch.

As described above, the performance of the subscriber database server 50 can be improved by separating the subscriber database server system into the processor server 300 and the management server 400. The management server 400 processes the subscriber customer information data to store or update the subscriber database, and the processor server 300 plays a role of delivering information for call processing. Contending for data transfer can prevent the performance of the subscriber database server from degrading.

In addition, while increasing the subscriber database of the management server 400, the number of subscribers accommodated by one management server may be increased, thereby reducing the relocation work of subscriber customer information. In addition, the subscriber database can be duplicated to perform stable service even if the subscriber database is damaged.

3A illustrates an example of a table structure of subscriber customer information of a subscriber database server system according to an embodiment of the present invention, and FIG. 3B illustrates a table structure of subscriber customer information of a subscriber database server system according to an embodiment of the present invention. Show the example changed by the new program.

First, a table storing subscriber customer information in FIG. 3A may include an R_IMSUB_DATA table 301, an R_SERPRO_DATA 302, an R_PUBID_DATA 303, and an R_FILCRI_DATA 304. However, FIG. 3A shows a part of a table field containing subscriber customer information, and may actually have a much wider table structure.

The R_IMSUB_DATA table 301 is composed of the subscriber's unique identifier, Private ID, as the priority key, and consists of a nibble-type IMSI field for the subscriber's authentication and an IMSUB primary key field for the neighbor table index. Can be. Subscribers with one private ID can subscribe to multiple services and thus can separate the R_SERPRO_DATA table 302. The R_SERPRO_DATA table 302 includes an IMSUB Primary Key field, a SERPRO Primary Key field, a Number of Public ID field, and a Number of Filter Criteria field. can do.

The R_PUBID_DATA table 303 is a public ID table and may include a SERPRO primary key field, a public ID field, a private ID field, and a barring indication field. have.

The R_FILCRI_DATA table 304 is the Initial Filter Criteria table for one service profile, which includes the SERPRO Primary Key field, the FILCRI Primary Key field, and the Number of Trigger SPI. Field, a priority field, a condition type CNF (Conjunctive Normal Form) field, and an application server ID field.

For example, a program package applied in the subscriber database server system when the table structure of the subscriber customer information as described above is referred to as 'version 1.0'.

Meanwhile, while operating a subscriber database server system in 'version 1.0', it is necessary to add a subscriber database for a new service or to update a subscriber database of a subscriber database server system while updating a program package serving a conventional service.

Referring to FIG. 3B, an R_APPSER_DATA 305 table is further added as compared with FIG. 3A. This is because, as a new additional service is added, additional server information about the additional service is added, thereby adding the R_APPSER_DATA 305 table.

For example, a program package applied to a subscriber database server system in the case of having a table structure as shown in FIG. 3B is called 'version 2.0'.

As such, when a table of subscriber customer information is added or deleted while adding a new service or updating a conventional service, the table structure in the subscriber database storing the subscriber customer information may be changed.

Therefore, in the subscriber database server system, in principle, it is necessary to update the table structure of the subscriber database and match the program version for the updated service to all the subscriber database server systems.

On the other hand, in adding a new service in the mobile communication system, it is common to perform partial replacements instead of the entire facility replacement or program addition and update.

For example, assume that the subscriber database server system is composed of four processor servers and two management servers as shown in FIG. In this case, since the first subscriber database and the second subscriber database of the two management servers 410 and 420 store the same data, the table structure of the subscriber customer information to which the updated 'Version 2.0' is applied as shown in FIG. Have

However, it is assumed that a program package for a new service or a program package for an updated service is applied to only some processors among the plurality of processor servers 310, 320, 330, and 340. This is because program packages are sequentially applied at regular time intervals to ensure the stability of new or updated services in a general mobile communication system.

In this case, the subscriber database is updated to a new higher version in the management server, but only a part of the processor server may be subjected to a new program package, thereby causing compatibility problems. In particular, it is called 'backward compatibility' to make it work backwards compatible with the existing lower version even though it has been changed to a higher version.

4 is a block diagram of a subscriber database server system having backward compatibility according to an embodiment of the present invention.

Referring to FIG. 4, a subscriber database server system having backward compatibility according to an embodiment of the present invention includes a first processor server, a second processor server, and a management server, wherein the management server includes a subscriber database, a first service daemon, and It may include a second service daemon.

The first processor server 510 is a processor server supporting a higher version. The first processor server may be composed of one or more. When a table of subscriber customer information of the database is changed by adding a new additional service or updating an existing service, the processor server linked thereto is updated to become the first processor server 510 supporting the higher version.

The second processor server 520 is a processor server supporting a lower version. The second processor server may be configured in plural. When the table of the subscriber customer information of the subscriber database is changed by adding a new additional service or updating an existing service, the processor server linked to this is not updated so that the second processor server 520 supporting the lower version is supported.

For example, in the subscriber database server system having the first and second processor servers as shown in FIG. 4, each processor server 510 or 520 may include clients 513 and 523.

The first processor server 510 includes a first client 513, which accesses the management server 400 to obtain subscriber customer information from the subscriber database.

The second processor server 520 includes a second client 523, which accesses the management server 400 to obtain subscriber customer information from the subscriber database.

The management server 400 may include subscriber databases 418 and 428 that store subscriber customer information, agent servers 412 and 422, a first service daemon 450 and a second service daemon 470. The management server 400 may include a first management server 410 and a second management server 420 having the same subscriber database in order to dually store subscriber customer information.

When the subscriber customer information of the first subscriber database 418 is updated, the second management server 420 replicates the same in real time or at predetermined time intervals. Therefore, even if one of the two management servers is damaged, it can continue to perform services reliably.

Agent servers 412 and 422 become targets for clients of processor servers 510 and 520 to access, and agent servers 412 and 422 manage subscriber databases 418 and 428 that store subscriber customer information.

When the service daemons 450 and 470 access the management server 400 to access the subscriber database and process the subscriber customer information, the service daemons 450 and 470 can access the subscriber database in accordance with the version of the processor server. To help. Therefore, when a table of subscriber customer information of the subscriber database is changed by adding a new additional service or updating an existing service, the first processor server 510 and the lower version of the upper version (for example, 'version 2.0') ( For example, the second processor server 520 of version 1.0 may access the subscriber database.

Therefore, the service daemon supporting the higher version may be referred to as the first service daemon 450, and the service daemon supporting the lower version may be referred to as the second service daemon 470. Here, the processor server of the lower version updates the processor server in conjunction with this when the table of the subscriber customer information of the subscriber database is changed due to the addition of a new additional service or the update of an existing service, but the service is stable as in the past. The processor server has not been updated with the program package in order to continuously execute the higher-level processor server refers to the processor whose program package has been updated to support the new service or the updated service.

For example, it is assumed that among the plurality of processor servers 510,..., 520, only the first processor server 510 is applied with a program package for a new service, and the second processor server 520 is the program package. Assume that did not apply. Accordingly, the first processor server 510 is a processor server supporting a higher version, and the second processor server 520 is a processor server supporting a lower version.

Assume that the tables of subscriber customer information have been updated in the databases 418 and 428 so that the structure of the table has changed from FIG. 3A to FIG. 3B. Accordingly, when the first processor server 510 and the second processor server 520 access the management server to access the subscriber customer information, the first processor server 510 and the second processor server 520 access the subscriber customer information using different service daemons.

Since the first service daemon 450 may support the first processor server 510 which is a higher version of the processor server, the first processor server 510 is connected to the management server to control the subscriber under the control of the first service daemon 450. Access customer information.

Since the second service daemon 470 can support a lower version of the processor server (eg, the second processor server), the second processor server 520 connects to the management server to control the second service daemon 470. Access subscriber customer information.

The second service daemon 470 supporting the second processor server 520, which is a lower version of the processor server, is configured to add or delete a table structure of subscriber customer information due to an update of a program package. Has change information.

Accordingly, the second service daemon 470 allows the lower version processor server to access the management server to access the subscriber database. Even if the lower version processor server accesses the updated database, the second service daemon 470 recognizes this as a table structure of the lower version so that subscriber customer information can be obtained. Thus, even if there is a change in the table structure of the subscriber customer information due to the application of a new supplementary service or the application of a program package for updating an existing service, the processor server operating in the previous lower version accesses the management server to access the subscriber customer information. It can be obtained easily.

As described above, even if the table structure of the subscriber customer information in the subscriber database is changed due to the introduction of a new supplementary service or the update of an existing service, the service daemon is connected to the management server by a processor daemon operating in a previous lower version by the service daemon. By acquiring subscriber customer information, it provides 'backward compatibility' so that the subscriber database server system operates stably.

5 is a flowchart illustrating a method for providing backward compatibility in a subscriber database server system according to an embodiment of the present invention.

Referring to FIG. 5, the first processor 510 or the second processor server 520 is connected to the management server 400 (S500). The first and second processor servers 300 may use clients 513 and 523 connected to the management server 400.

The management server 400 determines the version of the processor server according to the connection of the first or second processor servers 510 and 520. However, the meaning of the version of the processor server is that when changing the table structure of the subscriber customer information in accordance with the addition of a new service or update of the existing service, the table structure of the subscriber customer information is also recognized by the processor server accessing the management server. Should be updated as necessary. Therefore, the updated processor server is referred to as a first processor server 510 supporting a higher version, and the processor server not updated is referred to as a second processor server 520 supporting a lower version. In the mobile communication system, the upper and lower devices can be used simultaneously by sequentially applying program packages to existing facilities to ensure stability in adding new services or updating existing services.

The management server 400 determines the versions of the processor servers 510 and 520 and activates a service daemon suitable for this (S530). Since there is at least one processor server, when a plurality of processor servers are connected at the same time, the service daemon may be activated according to a version for each processor server.

The processor server 300 obtains subscriber customer information from the management server by the service daemon (S570). In the management server, the program package has already been applied, and thus the table of the subscriber customer information may be added, deleted, or updated. The processor server of the lower version may need the subscriber in the changed table of the subscriber customer information by the service daemon. Customer information can be obtained.

The processor servers 510 and 520 provide the acquired subscriber customer information to the core network in operation S590. Components requesting subscriber customer information in the core network may include a circuit switch 31, a circuit switched gateway 32, a packet switched support node 35, and a packet switched gateway 36.

Accordingly, it is possible to increase the stability of the mobile communication system by ensuring backward compatibility between servers in the core network due to the introduction of a new additional service or update of an existing service.

On the other hand, the components or '~' used in this embodiment is software such as tasks, classes, subroutines, processes, objects, execution threads, programs, or FPGAs (field-) that are performed in a predetermined area on the memory. It may be implemented in hardware such as a programmable gate array or an application-specific integrated circuit (ASIC), or may be a combination of the software and hardware. The component or 'unit' may be included in a computer readable storage medium, or a part of the components may be distributed and distributed to a plurality of computers.

Although embodiments of the present invention have been described above with reference to the accompanying drawings, those skilled in the art to which the present invention pertains have various permutations, modifications, and modifications without departing from the spirit or essential features of the present invention. It is to be understood that modifications may be made and other embodiments may be embodied. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive.

1 is a block diagram illustrating a UMTS communication network according to an embodiment of the present invention.

2 is a block diagram of a subscriber database server system according to an embodiment of the present invention.

3A is a diagram illustrating an example of a table structure of subscriber customer information of a subscriber database server system according to an embodiment of the present invention.

3B illustrates an example in which a table structure of subscriber customer information of a subscriber database server system according to an embodiment of the present invention is changed by a new program.

4 is a block diagram of a subscriber database server system having backward compatibility according to an embodiment of the present invention.

5 is a flowchart illustrating a method for providing backward compatibility in a subscriber database server system according to an embodiment of the present invention.

* Description of the main parts of the drawings *

100: circuit switching unit 200: packet switching unit

300: processor server 400: management server

500: switching unit

Claims (16)

A first processor server supporting a higher version; A second processor server supporting a lower version; And A management server for storing subscriber customer information; The management server A subscriber database in which the subscriber customer information is stored; A first service daemon that allows the first processor server to access the subscriber database; And A second service daemon that allows the second processor server to access the subscriber database, The upper version or the lower version is a version of the program package applied in the management server, the upper version is an updated version of the lower version program package, subscriber database server system in a mobile communication system. The method of claim 1, wherein the first and second processor server A subscriber database server system in a mobile communication system for providing subscriber customer information of the subscriber database to a core network. The method of claim 1, wherein the first processor server A subscriber database server system in a mobile communication system, which is a processor server to which a new supplementary service is added or an existing supplementary service is updated. The method of claim 3, wherein the second processor server Subscriber database server system in a mobile communication system, which is a processor server to which the higher version program package is not applied. The method of claim 1, wherein the second service daemon is And a processor server supporting the lower version to access the subscriber database using the change information on the table structure of subscriber customer information of the database. The method of claim 1, wherein the first and second processor server And a client connecting to the management server. The method of claim 1, wherein the management server A first management server for storing the subscriber customer information in a first subscriber database; And And a second management server for storing the same data as the subscriber customer information stored in the first subscriber database in a second subscriber database. The method of claim 7, wherein the second management server And synchronizing data of the first management server in real time to store the subscriber customer information in a second database in a redundant manner. The method of claim 1, wherein the subscriber customer information A subscriber database server system in a mobile communication system including location information of a called party or information of a called party's service profile. At least one processor server for providing subscriber customer information to the core network; At least one management server for storing the subscriber customer information in a database; And It includes a switching unit for connecting from the processor server to one of the management server, Some of the processor servers are higher version processor servers and others are lower version processor servers, The management server includes a first service daemon that controls the processor server of the higher version to access the database and a second service daemon that controls the processor server of the lower version to access the database. , The upper version or the lower version is a version of the program package applied in the management server, the upper version is an updated version of the lower version program package, the processor server of the higher version is a processor server supporting the higher version And the lower version processor server is a processor server supporting the lower version. The method of claim 10, wherein the switching unit A subscriber database server system in a mobile communication system, which is one of a hub, a router, and an ethernet switch. 11. The method of claim 10, wherein the lower version of the processor server A subscriber database server system in a mobile communication system, wherein the server does not have a higher version program package for adding a new additional service or updating an existing additional service. The subscriber database server system of claim 10, wherein the processor server and the management server serve as a home location register. Connecting the processor server to the management server; Identifying a version of the processor server and activating a service daemon suitable for the version; Acquiring, by the processor server, subscriber customer information stored in the management server; And Providing, by the processor server, the subscriber customer information to a core network; The processor server version is a version in which the processor server supports a program package applied by the management server, and the processor server supports a first processor server supporting a higher version of the program package and a lower version of the program package. And a second processor server, wherein the higher version is an updated version of the lower version program package. 15. The processor of claim 14, wherein the processor server is A method for providing backward compatibility in a subscriber database server system including a client connecting to the management server. 15. The system of claim 14, wherein the service daemon is And causing the processor server to acquire the subscriber customer information using the table change information of the subscriber customer information.

Images