KR20190021852A - Method for upgrading of software and pbx for the same - Google Patents

Abstract

The present invention relates to a software upgrade method in a telephone exchange including one or more active servers and one or more standby servers, and a telephone exchange for the same. According to one embodiment of the present invention, the telephone exchange stores data including an attribute name identifier, a relation name identifier, and data size information by one or more active servers or one or more standby servers; receives data stored in the active server by a standby server corresponding to the active server from the one or more active servers; compares the attribute and relation name identifiers of the received data with the attribute and relation name identifiers of the data stored in the standby server wherein when the attribute name identifier or the relation name identifier of the received data does not exist in the standby server, the received data is not loaded to the standby server, and when the attribute name identifier or the relation name identifier of the received data exists in the standby server, the received data is loaded to the standby server; and upgrades software of the telephone exchange by using the data stored in the standby server. The present invention can prevent data or memory corruption in data synchronization when versions of each server are different in telephone exchange constructed with a multiplexed server.

Description

METHOD FOR UPGRADING OF SOFTWARE AND PBX FOR THE SAME,

The present disclosure relates to a software upgrading method in a telephone exchange comprising at least one active server and at least one standby server.

A telephone switching system consisting of a server multiplexing solution (active (ACT) - standby (STB) configuration or ACT-ACT configuration) or local survival solution (LCM) consists of several servers, In order to maintain the continuity of service during emergency operation, the DBMS (database management system) of the system is always implemented to be synchronized.

In general, a server multiplexing solution or a local survival solution is configured as a layer for a telephone exchange. In such a hierarchical structure, a DBMS of the system may be loaded at startup or a DBMS may be changed in real time.

First, each of the servers is dumped from the parent server to the file and loaded into the memory when the DB server is started. The DB manager STB server and the ACT servers of the CCM start from the DB manager ACT server, the CCM STB server, The ACT servers of the LCM are loaded from the CCM ACT server at startup, and the STB servers of the LCM load the DBMS from the LCM ACT server.

Second, if the DBMS is changed in the Admin User Interface, the DB Manager synchronizes with the DB Manager STB, ACT and STB of each CCM, ACT and STB of each LCM in real time.

When synchronizing from each DBMS parent server to the subordinate server, a unique ID is allocated to all DBMS Relations, and unique IDs are assigned to the attributes in each Relation, and DBMSs that are changed during DBMS synchronization are identified by these IDs.

FIG. 1 is an example of assigning IDs for real data configuration and DBMS synchronization, Relation ID is 103, and each attribute is sequentially allocated from 0 to 4.

If a change is made to the attribute called tone_index of a relation called TenantSystemToneType, in order to synchronize to the lower server, Attribute 1 of Relation 103 informs the HEX value message that the change occurred and the lower server receiving this message receives the received ID value To identify the data and apply the changes.

The algorithm of synchronizing messages using the ID of the conventional DBMS has three problems below when the version of the DBMS parent server is different from the version of the lower server.

First, there is no change of the Attribute ID between the two versions. However, if the size of the data is changed, 2 bytes information is unconditionally read from the data change HEX message received from the STB server, so an error of 1 byte is read to the next data.

Second, when the attribute ID is changed due to the data change in the new version, an error that completely different data is changed due to different ID of ACT and STB occurs.

Third, when the data size of the Relation is changed, the data is read from the data file dumped at STB restart according to the size of the STB and loaded into the memory, thereby reading the garbage data or reading the data beyond the area of the dumped data Is generated.

The above-described background art is technical information acquired by the inventor for the purpose of deriving the present invention or acquired in the course of deriving the present invention, and is not necessarily a known technology disclosed to the general public prior to the filing of the present application.

The present disclosure provides a software upgrading method and a telephone exchange therefor in a telephone exchange comprising at least one active server and at least one standby server.

A software upgrading method in a telephone exchange comprising at least one active server and at least one standby server according to an embodiment of the present disclosure comprises the steps of: a) providing at least one active server or at least one standby server with an attribute name identifier, a relation name identifier, and data size information; b) transmitting data stored in the active server from any one of the at least one active server to a standby server corresponding to the active server; c) comparing the attribute identification name and the relation distinguished name of the transmitted data with the attribute distinguishing name and the relation distinguishing name of the data stored in the standby server, and if the attribute distinguishing name or the relationship distinguishing name of the transmitted data does not exist in the standby server, Loading the transmitted data to the standby server when the attribute identification name or the relationship identifying name of the transmitted data exists in the standby server without loading the data into the standby server; And d) performing a software upgrade of the telephone exchange using data stored in the standby server.

Transmitting the data stored in the standby server to the active server when the property identification name and the relationship identification name of the data stored in the standby server do not exist in the transmitted data in the software upgrade method; And storing the transmitted data in the standby server in the active server.

Also, in the software upgrade method, in step a), storing data to include attribute identification names, relationship distinguishing names, and data size information using SQL (Structured Query Language) may be included.

Also in the software upgrade method, the at least one active server and the at least one standby server may be configured in the form of either a server multiplexing solution or a local survival solution.

A telephone exchange including at least one active server and at least one standby server controls to store data including an attribute name identifier, a relation name identifier and data size information, The control unit controls to transfer data stored in the active server from one of the active servers to the standby server corresponding to the active server and controls the attribute identification name and the relation distinguished name of the transmitted data and the attribute identification of the data stored in the standby server And if the attribute identification name or the relation distinguished name of the transmitted data does not exist in the standby server, the transmitted data is not loaded into the standby server, and the attribute identification name or the relationship distinguished name of the received data is stored in the standby If it exists in the server, Controlled to load it to the server, by using the data stored in the standby server control unit for controlling to perform a software upgrade of the telephone exchange; And a storage unit for storing attribute identification names, relationship identification names, and data size information.

Also, in the telephone exchange, when the attribute identification name of the data stored in the standby server and the relationship distinguishing name do not exist in the transferred data, the control unit transmits the data stored in the standby server to the active server, Lt; / RTI >

In addition, in the telephone exchange, the control unit can store the data to include the attribute identification name, the relationship distinguishing name, and the data size information using SQL (Structured Query Language).

Also in the telephone exchange, the at least one active server and the at least one standby server may be configured in the form of either a server multiplexing solution or a local survival solution.

According to the embodiment of the present disclosure, it is possible to prevent data or memory corruption in data synchronization when the versions between the servers are different in a telephone exchange configured by server multiplexing.

1 is an exemplary view showing the configuration of a DBMS structure, a relation ID, and an attribute ID.
2 is an exemplary diagram illustrating a configuration of a software upgrade environment according to an embodiment of the present disclosure;
3 is an exemplary view showing a configuration of a telephone exchange according to an embodiment of the present disclosure;
FIG. 4 is a diagram illustrating a configuration of data stored in an active server and a standby server according to an embodiment of the present disclosure; FIG.
5 is a flow chart illustrating the procedure of a software upgrade method in accordance with an embodiment of the present disclosure.

The embodiments of the present disclosure are illustrated for the purpose of describing the technical idea of the present disclosure. The scope of the claims according to the present disclosure is not limited to the embodiments described below or to the detailed description of these embodiments.

All technical and scientific terms used in the present disclosure have the meaning commonly understood by one of ordinary skill in the art to which this disclosure belongs unless otherwise defined. All terms used in the disclosure are selected for the purpose of more clearly illustrating the disclosure and are not chosen to limit the scope of the rights under the present disclosure.

As used in this disclosure, the terms "comprising", "having", "having", "having", and the like are to be construed as including the possibility of including other embodiments, unless the context requires otherwise Should be understood as open-ended terms.

The expressions of the singular forms described in this disclosure may include plural meanings unless the context clearly dictates otherwise, and the same applies to the singular expressions set forth in the claims.

As used in this disclosure, expressions such as " first ", "second ", and the like are used to distinguish a plurality of components from each other and do not limit the order or importance of the components.

The term "part " as used in this disclosure refers to hardware components such as software or an FPGA (field-programmable gate array), ASIC (application specific integrated circuit). However, "part" is not limited to hardware and software. "Part" may be configured to reside on an addressable storage medium, and may be configured to play back one or more processors. Thus, by way of example, and not limitation, "part (s) " may include but are not limited to elements such as software components, object oriented software components, class components and task components, Microcode, circuitry, data, databases, data structures, tables, arrays, and variables of program code. The functions provided within the component and the "part " may be combined into a smaller number of components and" parts " or further separated into additional components and "parts ".

As used in this disclosure, the expression "based on" is used to describe one or more factors affecting an action or an action of a decision, judgment, as described in the phrase or sentence in which the expression is contained, It does not exclude any additional factors that affect the decision, act of judgment or action.

In the present disclosure, when an element is referred to as being "connected" or "connected" to another element, it is to be understood that the element may be directly connected to or connected to the other element, But may be connected or connected via other components.

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. In the accompanying drawings, the same or corresponding components are denoted by the same reference numerals. In the following description of the embodiments, description of the same or corresponding components may be omitted. However, even if the description of the components is omitted, such components are not intended to be included in any embodiment.

2 is an exemplary diagram illustrating the configuration of a software upgrade environment 200 in accordance with an embodiment of the present disclosure.

As shown in FIG. 2, the software upgrade environment 200 includes at least one active server 210-1, 210-2, 210-3, 210-4, 210-5, 210-6, ..., 210 220-2, 220-3, 220-4, 220-5, 220-6, ..., 220-n corresponding to at least one active server, And may include an exchange 230. Each of the active servers 210-1, 210-2, 210-3, 210-4, 210-5, 210-6, ..., 210-n and each of the standby servers 220-1, 220-2 220-3, 220-4, 220-5, 220-6, ..., 220-n include attribute name identifiers, relation name identifiers, and data size information Data can be stored. Each of the active servers 210-1, 210-2, 210-3, 210-4, 210-5, 210-6, ..., 210-n and each of the standby servers 220-1, 220-2 , 220-3, 220-4, 220-5, 220-6, ..., 220-n receive data from the upper server at the time of startup, and load the data into the memory. Each of the active servers 210-1, 210-2, 210-3, 210-4, 210-5, 210-6, ..., 210-n and each standby server 220-1, 220-1, 220-2, 220-3, 220-4, 220-5, 220-6, ..., 220-n are operated in real time when data stored in a specific server (for example, 210-1) 210-2, 210-3, 210-4, 210-5, 210-6, ..., 210-n, 220-1, 220-2, 220-3, 220- 4, 220-5, 220-6, ..., 220-n.

According to one embodiment, any one of the active servers 210-1, 210-2, 210-3, 210-4, 210-5, 210-6, ..., 210- Corresponding to the active server 210-1 and the attribute identification name and the relationship distinguished name of the data transmitted from the standby server 220-1 (for example, 210-1) to the standby server 220-1 corresponding to the active server 210-1, If the attribute identification name or the relationship identification name of the transmitted data does not exist in the standby server 220-1, the data transmitted to the standby server 220-1 is compared with the attribute identification name of the data stored in the server 220-1, It is possible to load the transmitted data into the standby server 220-1 when the attribute identification name or the relational distinguished name of the transmitted data exists in the standby server 220-1 without loading the data into the standby server 220-1.

A standby server corresponding to each of at least one active server 210-1, 210-2, 210-3, 210-4, 210-5, 210-6, ..., 210- 220-2, 220-3, 220-4, 220-5, 220-6, ..., 220-n may be configured in any one of a server multiplexing solution or a local survival solution However, it is not limited thereto.

The telephone exchanger 230 is connected to any one of the active servers 210-1, 210-2, 210-3, 210-4, 210-5, 210-6, ..., 210- (For example, 210-1) to the standby server 220-1 corresponding to the active server 210-1 to the active server 210-1. In addition, the telephone exchange 230 can perform an upgrade of software used in the telephone exchange 230 using the data stored in the standby server 220-1.

3 is an exemplary diagram illustrating the configuration of a telephone exchange 230 according to an embodiment of the present disclosure.

3, the telephone exchange 230 may include a control unit 232, a storage unit 234, a transmission / reception unit 236, and a system bus 238, and may include a control unit 232, a storage unit 234 and the transceiver 236 may be connected to each other via the system bus 238 so that they can communicate with each other.

The control unit 232 includes at least one active server 210-1, 210-2, 210-3, 210-4, 210-5, 210-6, ..., 210- 220-1, 220-2, 220-3, 220-4, 220-5, 220-6, ..., 220-n. In one embodiment, at least one active server 210-1, 210-2, 210-3, 210-4, 210-5, 210-6, ..., 210- 220-1, 220-2, 220-3, 220-4, 220-5, 220-6, ..., 220-n, And may store the data to include the relationship identification name and data size information.

Also, the control unit 232 controls the operation of any one of the at least one active server 210-1, 210-2, 210-3, 210-4, 210-5, 210-6, ..., 210- And transmit the data stored in the server (for example, 210-1) to the standby server 220-1 corresponding to the active server 210-1.

The control unit 232 compares the attribute identification name and the relation distinguished name of the data transmitted from the active server 210-1 with the attribute distinguishing name and the relation distinguishing name of the data stored in the standby server 220-1, When the attribute identification name or the relationship identification name of the data does not exist in the standby server 220-1, the transmitted data is not loaded into the standby server 220-1, and the attribute identification name or the relationship identification name of the transmitted data is stored in the standby server 220-1. And may transmit the transmitted data to the standby server 220-1 when the data exists in the standby server 220-1. In this way, since the data transmitted from the active server 210-1 and the data stored in the standby server 220-1 are identified by using the attribute identification name and the relationship distinguishing name, when the data size is changed or the data itself is changed It is possible to prevent the occurrence of an error even when it occurs. In addition, the control unit 232 may perform the software upgrade of the telephone exchange 230 using the data stored in the standby server.

The storage unit 234 stores identification information of a plurality of terminals, information on call paths of a plurality of terminals, information of a plurality of terminals, Information about the available state, and the like. Also, the storage unit 234 includes at least one active server 210-1, 210-2, 210-3, 210-4, 210-5, 210-6, ..., 210- May store information for performing synchronization of data stored in the standby servers 220-1, 220-2, 220-3, 220-4, 220-5, 220-6, ..., 220-n. According to one embodiment, the storage unit 234 may store data to include an attribute identification name, a relation distinguishing name, and data size information using SQL (Structured Query Language). According to one embodiment, the storage unit 234 may be a ROM (Read Only Memory), a RAM (Random Access Memory), a CD (Compact Disc) -ROM, a magnetic tape, a floppy disc, (Optical Data) storage device, but the present invention is not limited thereto.

The transceiver 236 can receive a call request signal or a packet from a plurality of terminals so that the telephone exchange 230 can perform telephone exchange between a plurality of terminals, A call request signal or packet in which various processes have been performed can be transmitted to the target terminal. The transmitting and receiving unit 236 includes at least one active server 210-1, 210-2, 210-3, 210-4, 210-5, 210-6, ..., 210- It is possible to transmit and receive signals for performing data synchronization between the standby servers 220-1, 220-2, 220-3, 220-4, 220-5, 220-6, ..., 220-n have. According to one embodiment, when an error occurs in a specific active server 210-1, the transmitting and receiving unit 236 transmits the data stored in the active server 210-1 to the corresponding standby server 220-1 And compares the attribute identification name and the relationship identification name of the data transmitted from the active server 210-1 with the attribute identification name and the relationship distinguishing name of the data stored in the standby server 220-1 The data transmitted from the active server 210-1 to the standby server 220-1 when the attribute identification name or the relationship identification name of the data transmitted from the active server 210-1 does not exist in the standby server 220-1 , The data transmitted from the active server 210-1 is transferred to the standby server 220-1 when the attribute identification name or the relationship identification name of the data transmitted from the active server 210-1 exists in the standby server 220-1 220-1) A signal for locking can be sent.

FIG. 4 is a diagram illustrating a configuration of data stored in an active server and a standby server according to an embodiment of the present disclosure; FIG.

4, at least one active server 210-1, 210-2, 210-3, 210-4, 210-5, 210-6, ..., 210- (TenantSystemToneType) and an attribute identification name (tone_type, tone_lock, token_id, token_repeat, tone_repeat_pause, and moh_tone_index) of the data held in the SQL data are communicated to the data server 210-1 and the corresponding standby server 220-1 It is possible to identify and communicate with the meaning of the data having the identification name without depending on the ID value that can be different between the different versions.

According to one embodiment, when the size of data having the same identification name is changed (410) in the active server 210-1 and the corresponding standby server 220-1, the data size of the standby server 220-1 It is possible to load the data transmitted from the active server 210-1 on the basis of the received data.

According to one embodiment, data 420 newly added to the standby server 220-1 is automatically added to the SQL data of the standby server 220-1, but data added from the corresponding active server 210-1 The guidance message for changing the distinguished name is not received.

According to an embodiment, even if the size of the entire data is changed (420) at the time of restarting the standby server 220-1, the presence or absence of each data can be determined based on the distinguished name of each data. Since the data stored in the active server 210-1 and the standby server 220-1 are synchronized in the above-described manner, it is possible to prevent an error in the data stored in the standby server 220-1 have.

5 is a flow chart illustrating the procedure of a software upgrade method in accordance with an embodiment of the present disclosure. Although process steps, method steps, algorithms, and the like have been described in this flowchart in a sequential order, such processes, methods, and algorithms may be configured to operate in any suitable order. In other words, the steps of the processes, methods and algorithms described in the various embodiments of the present disclosure need not be performed in the order described in this disclosure. Also, although some of the steps are described as being performed asynchronously, some of these steps may be performed concurrently in other embodiments. Also, an illustration of a process by way of illustration in the drawings is not intended to imply that the illustrated process excludes other variations and modifications thereto, and that any of the illustrated processes or steps thereof may be used in various embodiments of the present disclosure Does not imply that it is necessary for more than one, and does not mean that the illustrated process is preferred.

As shown in Fig. 5, in step S510, data may be stored in the active server or the standby server, including the attribute identification name, the relation distinguishing name, and the data size information. For example, referring to FIGS. 2-4, at least one active server 210-1, 210-2, 210-3, 210-4, 210-5, 210-6, ... 210- And standby servers 220-1, 220-2, 220-3, 220-4, 220-5, 220-6, ..., 220-n corresponding to each of the at least one active server It is possible to store the data including the attribute identification name, the relationship identification name, and the data size information instead of the time ID value.

In step S520, the data stored in the active server may be transmitted to the corresponding standby server. For example, referring to FIG. 2 to FIG. 4, at least one active server 210-1, 210-2, 210-3, 210-4, 210 (For example, 210-1) of any one of the standby servers 220-1, 210-2, ..., 210-6, ..., 210-n.

In step S530, the transmitted data and the attribute distinguished name or the relational distinguished name of the data stored in the standby server can be compared. For example, referring to FIGS. 2 to 4, when the attribute identification name and the relationship identification name of the transmitted data do not exist in the standby server 220-1, the transmitted data is not loaded into the standby server 220-1 And if the attribute identification name and the relationship identification name of the transmitted data exist in the standby server 220-1, the transmitted data can be loaded into the standby server 220-1 (S550). The data having the attribute identification name and the relationship distinguishing name that exist only in the standby server 220-1 can be automatically added to the SQL data of the standby server 220-1 (S540).

Although the method has been described through particular embodiments, the method may also be implemented as computer readable code on a computer readable recording medium. A computer-readable recording medium includes all kinds of recording apparatuses in which data that can be read by a computer system is stored. Examples of the computer-readable recording medium include a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like, and may be implemented in the form of a carrier wave (for example, transmission via the Internet) . In addition, the computer-readable recording medium may be distributed over network-connected computer systems so that computer readable codes can be stored and executed in a distributed manner. And, functional programs, codes, and code segments for implementing the above embodiments can be easily inferred by programmers in the technical field to which this disclosure belongs.

Although the present disclosure has been described in connection with some embodiments herein, it should be understood that various modifications and changes may be made thereto without departing from the spirit and scope of the present disclosure as will be apparent to those skilled in the art to which this disclosure belongs. something to do. It is also contemplated that such variations and modifications are within the scope of the claims appended hereto.

200: software upgrade environment 210-1, ..., 210-n:
220-1, ..., 220-n: Standby server 230: Telephone exchange
232: control unit 234:
236: Transmitting / receiving unit 238:

Claims (8)

A software upgrading method in a telephone exchange comprising at least one active server and at least one standby server,
a) storing data including an attribute name identifier, a relation name identifier and data size information in the at least one active server or the at least one standby server;
b) transmitting data stored in the active server from any one of the at least one active server to a standby server corresponding to the active server;
c) comparing the attribute identification name and the relation distinguished name of the transmitted data with the attribute distinguishing name and the relation distinguishing name of the data stored in the standby server, and if the attribute identification name or the relationship distinguishing name of the transmitted data does not exist in the standby server Loading the transmitted data to the standby server when the transmitted data is not loaded in the standby server and an attribute identification name or a relationship distinguishing name of the transmitted data exists in the standby server; And
d) performing a software upgrade of the telephone exchange using data stored in the standby server. The method according to claim 1,
In the step c)
Transmitting data stored in the standby server to the active server when an attribute identification name and a relationship identification name of data stored in the standby server do not exist in the transmitted data; And
And storing the data transmitted from the standby server in the active server.
How to upgrade your software. The method according to claim 1,
In the step a)
Storing the data to include the attribute identification name, the relationship distinguishing name, and the data size information using SQL (Structured Query Language)
How to upgrade your software. The method according to claim 1,
Said at least one active server and said at least one standby server,
A server multiplexing solution or a local survival solution,
How to upgrade your software. A telephone exchange comprising at least one active server and at least one standby server,
Wherein the control unit controls to store data including an attribute name identifier, a relation name identifier, and data size information, and controls to store data from any of the at least one active server to the active server A standby server for controlling the data to be stored in the active server to be transmitted, comparing an attribute identification name and a relation identification name of the transmitted data with an attribute identification name and a relation distinguishing name of data stored in the standby server, If the attribute identification name or the relationship distinguishing name does not exist in the standby server, the transferred data is not loaded on the standby server, and if the attribute identification name or the relationship distinguishing name of the received data exists in the standby server, To the standby server A control unit for controlling the software upgrade of the telephone exchange using data stored in the standby server; And
And a storage unit for storing the attribute identification name, the relationship distinguishing name, and the data size information.
Telephone switch. 6. The method of claim 5,
Wherein,
And transmitting the data stored in the standby server to the active server when the attribute identification name and the relation distinguishing name of the data stored in the standby server do not exist in the transferred data and storing the data received from the standby server in the active server doing,
Telephone switch. 6. The method of claim 5,
Wherein,
Storing the data to include the attribute identification name, the relationship distinguishing name, and the data size information using SQL (Structured Query Language)
Telephone switch. 6. The method of claim 5,
Said at least one active server and said at least one standby server,
A server multiplexing solution or a local survival solution,
Telephone switch.

Images