CN106462421B

CN106462421B - Telecommunication device and method for updating software in a telecommunication device

Info

Publication number: CN106462421B
Application number: CN201480079918.8A
Authority: CN
Inventors: 沈阳; 张继东
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2014-06-16
Filing date: 2014-06-16
Publication date: 2020-03-20
Anticipated expiration: 2034-06-16
Also published as: WO2015192298A1; CN106462421A

Abstract

The present application provides a telecommunications device and a method for updating software. The method comprises the following steps: accessing data in a first format from a first memory portion located in a memory of the telecommunications device through at least one of the first service node and the second service node; updating the software in the first service node to a second version; accessing data from a second storage portion, located in said memory and storing data in a second format, including those data converted from said data in said first format stored in said first storage portion, by said first service node installed with said second version of said software; and updating the software in the second service node to the second version after updating the software in the first service node. Thus, the first storage portion and the second storage portion enable the service node, in which the different versions of software are installed, to access data in corresponding formats. The service node is not required to be concerned with data compatibility, thereby achieving simple implementation of lossless update software in the telecommunications device.

Description

Telecommunication device and method for updating software in a telecommunication device

Technical Field

The present application relates to the field of communication technology, and in particular to a telecommunication device and a method for updating software in a telecommunication device.

Background

During the lifecycle of software in a telecommunication device, the software needs to be constantly updated to accommodate new requirements. To update software from an old version to a new version, the old version of software is deactivated at a particular time and the new version of software will be opened for service after the update process is completed. Thus, during the process of updating the software, the traffic is interrupted.

Fig. 1 illustrates a conventional method for lossless updating of software in a telecommunication device 106. The telecommunication apparatus 106 includes a main board (AB) 102 and a Standby Board (SB) 104. The OLD version (OLD _ VER) software is uploaded to both the AB102 and the SB 104. The method comprises the following steps: in step 11, the old version software in SB 104 is updated to the NEW version (NEW _ VER); in step 12, data of the old version software is backed up from the AB102 to the SB 104; in step 13, AB102 and SB perform switching such that SB 104 becomes AB 104 'and AB102 becomes SB 102', and AB 104 'which is the current AB takes over traffic from SB 102'; and in step 14, the old version of software in SB 102' is also updated to the new version.

However, the data format may change in different software versions. Compatibility must be considered in new versions of software, since the board performs business logic computations and data storage in current System Architecture Evolution (SAE) systems to backup data in the old format used by the old version of software from the AB102 to the SB 104, where the new version of software uses the new data format. For example, the new version of software should be compatible with different old data formats. Therefore, it is very complicated to implement the conventional method for lossless updating of software and to use the software in large scale in practice.

Disclosure of Invention

Embodiments of the present application provide a telecommunications device and a method for updating software in a telecommunications device.

According to one aspect, a method is provided for updating software in a telecommunications device from a first version to a second version. At least a first service node and a second service node are comprised in the telecommunication device and the first service node and the second service node are each provided with software. The method comprises the following steps:

accessing data from a first storage section located in a memory of the telecommunications device and storing data in a first format by at least one of a first service node and a second service node having a first version of software installed prior to updating the software in the second service node;

updating, by a first service node, software in the first service node from a first version to a second version;

when the first service node is installed with a second version of software after the software in the first service node is updated from the first version to the second version, accessing data from a second storage section, which is located in the memory and stores data in a second format, including those converted from the data in the first format stored in the first storage section, through the first service node;

after the software in the first service node is updated from the first version to the second version, updating the software in the second service node from the first version to the second version through the second service node; and

when the second service node is installed with the second version of software after the software in the second service node is updated from the first version to the second version, the data is accessed from the second storage section through the second service node.

According to another aspect, a telecommunications device is provided. The telecommunication apparatus includes:

a first memory including a first storage portion and a second storage portion, wherein the first storage portion is for storing data in a first format and the second storage portion is for storing data in a second format, including those data converted from the data in the first format stored in the first storage portion; and

at least a first service node and a second service node, which are used for installing software to be updated from a first version to a second version, respectively, wherein the first service node is used for installing the software of the first version before the software in the first service node is updated; before updating the software in the second service node, the second service node is used for installing the software of the first version; at least one of a first service node installed with the first version of software and a second service node installed with the first version of software is used for accessing data in a first format from a first storage part;

wherein when the first service node is installed with the second version of software after the software in the first service node is updated from the first version to the second version, the first service node is further configured to update the software in the first service node from the first version to the second version, and the first service node installed with the second version of software is configured to access the data in the second format from the second storage section;

wherein when the second service node installs the second version of software after the software in the second service node is updated from the first version to the second version, the second service node is further configured to update the software in the second service node from the first version to the second version after the software in the first service node is updated from the first version to the second version, and the second service node installed with the second version of software is configured to access the data in the second format from the second storage section.

These and other aspects of the invention are apparent from and will be elucidated with reference to the embodiments described hereinafter. According to an embodiment of the application, the first storage portion and the second storage portion in the memory enable service nodes installed with different versions of software to access data in corresponding formats. Therefore, there is a need for a service node to be concerned with data compatibility, thereby enabling simple implementation of lossless updates of software in telecommunications equipment.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for describing the embodiments or the prior art are briefly introduced below. It is to be understood that the drawings in the following description are merely exemplary of the application and that still other drawings may be derived from those drawings by one of ordinary skill in the art without inventive faculty.

FIG. 1 illustrates a conventional method for lossless software updates in a telecommunications device;

FIG. 2 illustrates a flow diagram of a method for updating software in a telecommunications device according to one embodiment of the present application;

FIG. 3A illustrates an example of how a first storage portion and a second storage portion in a memory are generated according to one embodiment of the present application;

figures 3B and 3C illustrate two examples of accessing data from a second storage portion by a first service node installed with a second version of software according to one embodiment of the present application;

FIG. 3D illustrates an example of a flow chart for rolling back a software update according to one embodiment of the present application;

fig. 4 illustrates a simplified block diagram of a telecommunications device according to one embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below clearly with reference to the accompanying drawings in the embodiments of the present application. It should be apparent that the described embodiments are only some embodiments of the present application, and not all embodiments. All other embodiments obtained by a person of ordinary skill in the art without any inventive step based on the embodiments of the present application shall fall within the scope of protection of the present application.

Fig. 2 illustrates a flow diagram of a method for updating software in a telecommunications device according to one embodiment of the present application.

The telecommunication device refers to a device for implementing a function as a logical network element in a telecommunication system, for example, the telecommunication device refers to a device for implementing a function as a logical network element as defined in the 3rd Generation partnership project (3 GPP) protocol. The telecommunication device may include, but is not limited to, a Mobility Management Entity (MME), a Serving Gateway (SGW), or a packet data network gateway (PGW).

In one example, a telecommunications device includes a plurality of service nodes and a memory. The plurality of service nodes are for performing, but not limited to, at least one of computing service logic, processing signaling, and forwarding data. For example, a service node may include, but is not limited to, a board, a process entity, or a virtual machine. Software targeted for one service is uploaded to at least one pair of service nodes, namely a first service node (SN1) and a second service node (SN 2). In other words, the first service node and the second service node are each installed with software. Depending on the needs of the business, the software may need to be updated from one version to another. The memory is used to store data generated or received by the service node. At least a first storage portion P1 and a second storage portion P2 are located in memory.

Optionally, the operation and maintenance system is for managing operation of the service nodes in the telecommunications device. In one example, the operation and maintenance system may be implemented by a separate system coupled to the telecommunications equipment. In another example, the operation and maintenance system may be integrated within the telecommunications device.

The first service node installs the first version of software prior to updating the software in the first service node. And the second service node is installed with the first version of software before updating the software in the second service node.

As illustrated in fig. 2, in step 21, at least one of the first service node installed with the first version of software and the second service node installed with the first version of software accesses the data in the first format from the first storage part P1. For example, the data may include, but is not limited to, traffic data, such as mobile phone number data, corresponding serving cell data, or user equipment time limit data.

The term "accessing data in the first format from the first storage section" refers herein to an operation of storing data related to a service into the first storage section, or an operation of reading data related to a service from the first storage section. In one example, the first service node and the second service node each perform a portion of the service. Thus, both the first service node and the second service node access data in the first format from the first storage portion. In another example, only the first service node or the second service node performs the entire service. Thus, only the first service node or the second service node accesses data in the first format from the first storage portion.

The first storage part P1 and the second storage part P2 are located in the memory of the telecommunication device. In one example, the first storage portion contains a first stored instance in memory and the second storage portion contains a second stored instance in memory. In another example, the first storage portion contains a first table in a stored instance in memory and the second storage portion contains a second table in the stored instance. The first storage section stores data in a first format. The second storage section stores data in a second format including those converted from the data in the first format stored in the first storage section. In one example, a first memory portion and a second memory portion are generated in a memory. However, the resulting first and second storage portions will be described with respect to fig. 3A.

In step 22, the first service node updates the software in the first service node from the first version to the second version. In other words, the software in the first service node is updated from the first version to the second version.

In step 23, the first service node accesses the data in the second format from the second storage section when the first service node installs the second version of software after the software in the first service node is updated from the first version to the second version. The second storage section stores data in a second format including those converted from the data in the first format stored in the first storage section. For example, data in the first format stored in the first storage portion is converted into data in the second format, and the converted data in the second format is included in the data in the second format stored in the second storage portion.

The term "accessing data in the second format from the second storage section" refers herein to an operation of storing data in the second format related to a service into the second storage section, or an operation of reading data in the second format related to a service from the second storage section.

In step 24, the second service node updates the software in the second service node from the first version to the second version after the software in the first service node is updated to the second version. In other words, after the software in the first service node is updated to the second version, the software in the second service node is updated from the first version to the second version.

In step 25, the second service node accesses the data in the second format from the second storage section when the second service node installs the second version of software after the software in the second service node is updated from the first version to the second version.

Thus, during the updating of the software in the first service node, the second service node, in which the first version of the software is installed, still opens the service and is able to access the data in the first format from the first storage section. The first service node is capable of accessing the data in the second format from the second storage portion when the software in the first service node is updated to the second version. Thus, no traffic is interrupted during the update process and a lossless update is obtained.

Since the data format conversion is performed inside the memory and not inside the service node. Thus, prior to the update, the service node installed with the first version of software can access the data in the first format from the first storage section, and after the update, the service node installed with the second version of software can access the data in the second format from the second storage section. Advantageously, the first and second memory portions in the memory enable service nodes having different versions of software installed to access data in corresponding formats. Therefore, there is a need for a service node to be concerned with data compatibility, thereby enabling simple implementation of non-destructive update software in telecommunications equipment.

FIG. 3A illustrates an example of how first and second storage portions in a memory are generated.

Steps 311 through 316 are performed to generate a first memory portion in memory.

In step 311, the operation and maintenance system sends an instruction indicating that the first memory portion is to be created in memory. After the first memory portion is generated in memory, an identification of the first memory portion is sent to the operation and maintenance system in step 312. For example, the identification of the first memory portion comprises an address of the first memory portion if the first memory portion is a first memory instance in the memory, or a number of tables of the first memory portion if the first memory portion is a first table in a memory instance in the memory. Subsequently, in step 313, the first service node receives an identification of the first memory portion from the operation and maintenance system; in step 314, the second service node receives an identification of the first memory portion from the operation and maintenance system. Thus, in step 315, the first service node, having the first version of software installed, is able to access data in the first format from the first storage portion based on the identity of the first storage portion; and in step 316, the second service node, having the first version of software installed, is able to access data in the first format from the first storage portion based on the identity of the first storage portion.

Similarly, steps 321 to 323 are performed to generate a second storage portion:

in step 321, the operation and maintenance system sends an instruction indicating that the second memory portion is to be created in memory. At the same time, the operation and maintenance system sends the identification of the first storage portion, the update relationship, and the data conversion rule to the memory. The update relationship indicates that the software is updated from the first version to the second version. The data conversion rule indicates a conversion rule of data. For example, as shown in table 1, the conversion rule indicates that the data A, B, C in the first format is converted into data a ', B ', C ' in the second format, respectively. And the data D' in the second format is set to a default value.

TABLE 1

After the second memory portion is generated in memory, an identification of the second memory portion is sent to the operation and maintenance system in step 322. For example, the identification of the second memory portion comprises an address of the second memory portion if the second memory portion is a second memory instance in the memory, or a number of tables of the second memory portion if the second memory portion is a second table in the memory instance. Subsequently, in step 323, the operation and maintenance system sends the identification of the second storage section to the first storage section.

The operation and maintenance system also sends an identification of the second storage portion to the first service node when the operation and maintenance system instructs the first service node to update the software in the first service node from the first version to the second version. Thus, after the software in the first service node has finished updating, the first service node can access the data in the second format from the second storage section according to the identification of the second storage section. That is, prior to the process of updating, the first service node, having the first version of software installed, accesses data in the first format from the first storage section in accordance with the identification of the first storage section; after the updating process, the first service node installed with the second version of software accesses the data in the second format from the second storage section according to the identification of the second storage section.

Similarly, when the operation and maintenance system instructs the second service node to update the software in the second service node from the first version to the second version, the operation and maintenance system also sends an identification of the second storage portion to the second service node. Thus, after the software in the second service node has finished updating, the second service node can access the data in the second format from the second storage section according to the identification of the second storage section.

Fig. 3B and 3C illustrate two examples of accessing data from the second storage portion by the first service node installed with the second version of software. Fig. 3B and 3C are described in conjunction with fig. 2.

As illustrated in fig. 3B, optionally, in step 221, the operation maintenance system instructs the first service node to update the software in the first service node from the first version to the second version. In one example, in step 222, the data in the first format stored in the first storage portion is converted to data in the second format, and the converted data in the second format is stored in the second storage portion before updating the software in the first service node. In another example, in step 222', data in a first format stored in the first memory portion is converted to data in a second format and stored in the second memory portion while updating software in the first service node.

Subsequently, steps 231 to 232 are performed to implement step 23 in fig. 2.

For example, after the software in the first service node is updated to the second version, the first service node, in which the second version of software is installed, can store the data in the second format in the second storage section (not shown in fig. 3B). Further, when the first service node, in which the second version of software is installed, wants to access the data of the second format, for example, the first data in step 231, the first service node transmits a first request, in which the first service node, in which the second version of software is installed, wants to access the first data of the second format, to the second storage part. After the second storage portion receives the first request, the first service node accesses the first data in the second format from the second storage portion in step 232 if the first data in the second format is available in the second storage portion.

When the first data in the second format is not available in the second storage section, for example, when a program that converts the data in the first format into the data in the second format and stores the converted data in the second format into the second storage section has not been completed and the first data in the first format has not been converted, the second storage section and the first storage section perform real-time interaction in steps 233 to 234. More specifically, in step 233, the second storage portion sends the real-time request to the first storage portion. When the first data in the first format is available in the first storage section, the first data in the first format is converted into the first data in the second format according to the update relationship and the data conversion rule, and the converted first data in the second format is stored in the second storage section in step 234. Subsequently, in step 232, the first service node accesses the first data in the second format from the second storage portion.

Thus, by converting the data according to specific data conversion rules, the memory may implement data format conversion so that the memory may support updating the software in the service node without updating the memory itself.

In one example, after performing steps 24 (step 241 as illustrated in fig. 3B) and 25 (step 251 as illustrated in fig. 3B), the method may further include steps 261 to 263, which are performed to delete the data stored in the first storage portion.

For example, in

steps

261 and 262, the operation and maintenance system notifies the first storage section and the second storage section, respectively, that the update process of the software is completed. Subsequently, in step 263, the data stored in the first storage portion is deleted.

In one example, in the table between

steps

23 and 24, the service node may add or modify data in one format, for example, in the course of computing the service logic. In this case, the method further comprises: in step 280, converting and storing data in time is performed between the first storage portion and the second storage portion. In one example, a second service node, having the first version of software installed, adds second data in the first format to the first portion of storage. The first memory portion thus sends real-time instructions to the second memory portion. After receiving the instruction through the second storage section, the second data in the first format is converted into second data in a second format according to the update relationship and the data conversion rule, and the converted second data in the second format is stored into the second storage section. Thus, the first service node, having the second version of software installed thereon, is able to access the second data in the second format from the second storage section. In another example, a second service node, having the first version of software installed thereon, modifies third data in the first format stored in the first storage portion. The first memory portion thus sends real-time instructions to the second memory portion. After receiving the instruction through the second storage section, the third data in the first format is converted into third data in the second format according to the update relationship and the data conversion rule, and the converted third data is stored into the second storage section. Thus, the first service node, in which the second version of software is installed, can access the third data in the second format from the second storage section.

In yet another example, the first service node, having the second version of software installed, adds fourth data in the second format to the second storage portion. The second memory portion thus sends real-time instructions to the first memory portion. After receiving the instruction through the first storage section, the fourth data in the second format is converted into fourth data in the first format according to the update relationship and the data conversion rule, and the converted fourth data in the first format is stored into the first storage section. Thus, the second service node, in which the first version of software is installed, can access the fourth data in the first format from the first storage section. In yet another example, the first service node, having the second version of software installed thereon, modifies the fifth data in the second format stored in the second storage portion. The second memory portion thus sends real-time instructions to the first memory portion. After receiving the instruction through the first storage section, the fifth data in the second format is converted into fifth data in the first format according to the update relationship and the data conversion rule, and the converted fifth data is stored into the first storage section. Thus, the second service node, which is installed with the first version of software, can access the fifth data in the first format from the first storage section.

In the example shown in fig. 3C, optionally, in step 221, the operation maintenance system instructs the first service node to update the software in the first service node from the first version to the second version. After the software in the first service node is updated to the second version, steps 235 to 237 are performed to implement step 23 in fig. 2.

For example, after the software in the first service node is updated to the second version, the first service node, in which the second version of software is installed, can store the data in the second format in the second storage section (not shown in fig. 3C). Further, when the first service node installed with the second version of software wants to access data of the second format, for example, sixth data, the first service node transmits a second request that the first service node installed with the second version of software wants to access the sixth data of the second format to the first storage part to activate data format conversion in step 235. Thus, after the first storage portion receives the second request, the second storage portion and the first storage portion perform real-time interaction in step 236. More specifically, when the sixth data in the first format is available in the first storage portion, the sixth data in the first format is converted into sixth data in the second format according to the update relationship and the data conversion rule, and the converted sixth data in the second format is stored in the second storage portion while the sixth data in the first format is deleted from the first storage portion. Subsequently, in step 237, the first service node accesses sixth data in the second format from the second storage section.

In one example, after performing steps 24 (step 241 as illustrated in fig. 3C) and 25 (step 251 as illustrated in fig. 3C), the method further comprises steps 261 to 265.

For example, in

steps

261 and 262, the operation and maintenance system notifies the first storage portion and the second storage portion, respectively, that the update process is completed. In step 264, the remaining data stored in the first storage portion that is not yet needed by the first service node with the second version of software installed is converted to data in the second format and stored in the second storage portion. Subsequently, in step 265, the corresponding data in the first format stored in the first storage portion is deleted.

In the example shown in fig. 3C, the software may undergo an update rollback. In other words, the updated software may be set to an earlier version, for example, from the second version to the first version. In this case, it can be applied to the embodiments of the present application. FIG. 3D illustrates an example of a flow diagram for rolling back a software update. In the example of fig. 3D, the first business node sets the software in the first business node from the second version to the first version for illustrative purposes. A first service node, having rollback software installed, wants to access data in a first format. However, the present application is not so limited; the second service node performs a similar operation when the second service node sets the software in the second service node from the second version to the first version.

When the first service node installed with the rollback software wants to access data in the first format, for example, seventh data, in step 271, the first service node sends a third request to the first storage portion that the first service node installed with the first version of software wants to access the seventh data. If seventh data in the first format is available in the first storage portion, the first service node having the first version of software installed thereon accesses the seventh data in the first format directly from the first storage portion in step 274.

However, the seventh data in the first format is not available in the first storage portion, whether the seventh data is deleted after the above-described updating process is completed or the seventh data never exists in the first data set. Thus, the method further comprises

steps

272 and 273. In steps 272 to 273, the second storage section and the first storage section perform real-time interaction to convert the corresponding data in the second format into the desired data in the first format.

For example, in step 272, if seventh data in the first format is not available in the first storage portion, the first storage portion sends an instruction to the second storage portion. When the second storage section receives the instruction, the seventh data in the second format is converted into seventh data in the first format according to the update relationship and the data conversion rule, and the converted seventh data in the first format is stored into the first storage section while the seventh data in the second format is deleted from the second storage section. Accordingly, in step 274, the first service node, having the rollback software installed, accesses the seventh data in the first format from the first storage portion.

It should be understood that the present application is not limited to update software targeted for one business and that the present application is also applicable to update software targeted for multiple businesses. Multiple software may be updated simultaneously, or continuously, using the methods described in figures 2 through 3D.

Fig. 4 illustrates a simplified block diagram of a telecommunication device 400 according to one embodiment of the present invention. Fig. 4 is described with respect to fig. 2-3D.

As described above, the telecommunication device 400 may comprise, but is not limited to, an MME, an SGW or a PGW, and the telecommunication device 400 comprises at least a first service unit 402, a second service unit 412 and a storage unit 401. The first service unit 402 and the second service unit may be implemented by a first service node and a second service node, respectively. For example, the first service node or the second service node may include, but is not limited to, a board, a process entity, or a virtual machine. The storage unit 401 may be implemented by a memory. The memory 401 may be read-only, e.g., read-only memory (ROM) or readable/writable, e.g., hard disk or flash memory, or may be Random Access Memory (RAM).

In one example, the operation and maintenance system 403 is a separate system coupled to the telecommunication device 400. In another example, the operation and maintenance system 403 may be integrated within the telecommunications device 400. The above elements of the telecommunication device 400 may be coupled to each other by a bus, e.g. any one or any combination of a data bus, an address bus, a control bus, an expansion bus and a local bus.

The memory cell 401 includes a first memory portion P1 and a second memory portion P2. In one example, the first storage portion contains a first storage instance in storage unit 401 and the second storage portion contains a second storage instance in storage unit 401. In another example, the first storage section contains a first table in a storage instance in the storage unit 401, and the second storage section contains a second table in the storage instance. The first storage section is for storing data in a first format. The second storage portion is for storing data in a second format, including those converted from the data in the first format stored in the first storage portion.

For example, the first traffic unit 402 comprises a first access unit 406, a first update unit 407, a first receive unit 408 and a transmit unit 409. The second service unit 412 comprises a second access unit 416, a second update unit 417 and a second receive unit 418. First service unit 402 and second service unit 412 are each installed with software to be updated from a first version to a second version. In one example, the first access unit 406, the first update unit 407, the first receive unit 408 and the transmit unit 409 may be implemented by a processor in the first service node; the second access unit 416, the second update unit 417 and the second receive unit 418 may be implemented by a processor in the second service node. In another example, the first accessing unit 406, the first updating unit 407, the first receiving unit 408, the sending unit 409, the second accessing unit 416, the second updating unit 417 and the second receiving unit 418 may be implemented by a processor in the telecommunication device 400. The processor is the control center of the service node and provides sequencing and processing facilities for executing instructions, performing interrupt actions, providing timing functions, and a number of other functions. Optionally, the processor includes one or more Central Processing Units (CPUs). Unless otherwise specified, a component such as a processor or a memory described as being used to perform a task may be implemented as a general component that is temporarily used to perform the task at a given time or as a specific component that is manufactured to perform the task. The term "processor" as used herein refers to one or more devices, circuits, and/or processing cores for processing data, e.g., computer program instructions.

Prior to updating the software in first business unit 402, first business unit 402 is installed with a first version of the software; the second business unit 412 is installed with the first version of software before updating the software in the second business unit 412. At least one of the first business unit 402 with the first version of software installed and the second business unit 412 with the first version of software installed is used to access data in the first format from the first storage portion. For example, the first access unit 406 enables the first service unit 402, in which the first version of software is installed, to access the data in the first format from the first storage part P1, and/or the second access unit 416 enables the second service unit 412, in which the first version of software is installed, to access the data in the first format from the first storage part P1.

First service unit 402 is further configured to update the software in first service unit 402 from a first version to a second version. For example, the first update unit 407 enables the first service unit 402 to update the software in the first service unit 402 from a first version to a second version. When the first business unit 402 has the second version of software installed therein after the software in the first business unit 402 has been updated from the first version to the second version, the first business unit 402, having the second version of software installed therein, is used to access data in the second format from the second storage portion. For example, the first access unit 406 enables the first service unit 402, in which the second version of software is installed, to access data in the second format from the second storage portion P2.

After the software in the first business unit 402 is updated from the first version to the second version, the second business unit 412 is further operable to update the software in the second business unit 412 from the first version to the second version. For example, after the software in the first business unit 402 is updated from the first version to the second version, the second update unit 417 enables the second business unit 412 to update the software in the second business unit 412 from the first version to the second version. When the second service unit 412 has the second version of software installed therein after the software in the second service unit 412 is updated from the first version to the second version, the second service unit 412 having the second version of software installed therein is used to access data in the second format from the second storage portion in the second service unit 412. For example, the second access unit 416 enables the second service unit 412, which is installed with the second version of software, to access the data in the second format from the second storage part P2.

Thus, during the updating of the software in the first service node, the second service node, in which the first version of the software is installed, still opens the service and is able to access the data in the first format from the first storage section. The first service node is capable of accessing the data in the second format from the second storage portion when the software in the first service node is updated to the second version. Thus, no traffic is interrupted during the update process and a lossless update is obtained. The data format conversion is performed inside the memory, not inside the service node. Thus, prior to the update, the service node installed with the first version of software can access the data in the first format from the first storage section, and after the update, the service node installed with the second version of software can access the data in the second format from the second storage section. Advantageously, the first and second memory portions in the memory enable service nodes having different versions of software installed to access data in corresponding formats. Therefore, there is a need for a service node to be concerned with data compatibility, thereby enabling simple implementation of non-destructive update software in telecommunications equipment.

In one example, first storage portion P1 and second storage portion P2 are generated in storage unit 401 according to instructions from operation and maintenance system 403. After the first and second memory portions are generated in the first memory, the first and second service nodes are operable to receive a first identification of the first memory portion and a second identification of the second memory portion from the operation and maintenance system. For example, first receiving unit 408 enables first business unit 402 to receive from the operation and maintenance system a first identification of first storage portion P1 and a second identification of second storage portion P2, and second receiving unit 418 enables second business unit 412 to receive from operation and maintenance system 403 the first identification of first storage portion P1 and the second identification of second storage portion P2. Thus, the first business unit 402 with the first version of software installed and the second business unit 412 with the first version of software installed are used to access data in the first format from the first storage portion based on the first identification of the first storage portion and to access data in the second format from the second storage portion based on the second identification of the second storage portion. For example, the first access unit 406 enables the first service unit 402, in which the first version of software is installed, to access data in the first format from the first storage part P1 based on the first identification of the first storage part P1, or enables the first service unit 402, in which the second version of software is installed, to access data in the second format from the second storage part P2 based on the second identification of the second storage part P2. The second access unit 416 enables the second service unit 412, in which the first version of software is installed, to access data in the first format from the first storage part P1 based on the first identification of the first storage part P1, or enables the second service unit 412, in which the second version of software is installed, to access data in the second format from the second storage part P2 based on the second identification of the second storage part P2.

In one example, the first identification of the first memory portion comprises a first address of the first memory instance and the second identification of the second memory portion comprises a second address of the second memory instance. In another example, the first identification of the first storage portion contains a first number of tables of the first table and the second identification of the second storage portion contains a second number of tables of the second table.

Optionally, the first service unit 402 with the second version of software installed is adapted to send a first request to the second storage section that the first service unit 402 with the second version of software installed wants to access the first data in the second format. For example, the sending unit 409 enables the first traffic unit 402 to send the first request to the second storage part P2. Subsequently, the first service unit 402, which is installed with the second version of software, is used to access the first data in the second format from the second storage section. For example, the first access unit 406 enables the first service unit 402, in which the second version of software is installed, to access the first data in the second format from the second storage portion P2. When the first data in the second format is not available in the second storage part P2, after the first request is received in the second storage part P2, the first data in the first format stored in the first storage part is converted into the first data in the second format, and the converted first data in the second format is stored in the second storage part P2. Subsequently, the first service unit 402, in which the second version of software is installed, is used to access the first data in the second format from the second storage part P2.

Optionally, when the second service unit 412 installed with the first version of software adds the second data in the first format to the first storage part P1, the second data in the first format is converted into the second data in the second format and the converted second data in the second format is stored in the second storage part P2. Subsequently, the first service unit 402, which is installed with the second version of software, is used to access the second data in the second format from the second storage section. For example, the first access unit 406 may enable the first service unit 402, in which the second version of software is installed, to access the second data in the second format from the second storage part P2. When the second service unit 412, in which the first version of software is installed, modifies the third data stored in the first storage part P1, the modified third data of the first format is converted into modified third data of the second format and the modified third data of the second format is stored in the second storage part P2. Subsequently, the first service unit 402, in which the second version of software is installed, is used to access the third data in the second format from the second storage section. For example, the first access unit 406 may enable the first service unit 402, in which the second version of software is installed, to access the third data in the second format from the second storage part P2.

Similarly, when the first business unit 402, in which the second version of software is installed, adds the fourth data in the second format to the second storage part P2, the fourth data in the second format is converted into the fourth data in the first format and the converted fourth data in the first format is stored in the second storage part P1. Subsequently, the second service unit 412, which is installed with the first version of software, is used to access the fourth data in the first format from the first storage section. For example, the second accessing unit 416 may enable the second service unit 412, which is installed with the first version of software, to access the fourth data in the first format from the first storage part P1. When the first business unit 402, in which the second version of software is installed, modifies the fifth data stored in the second storage part P2, the modified fifth data of the second format is converted into modified fifth data of the first format and the modified fifth data of the first format is stored in the first storage part P1. Subsequently, the second service unit 412, which is installed with the first version of software, is used to access the fifth data in the first format from the first storage section. For example, the second accessing unit 416 may enable the second service unit 412, which is installed with the first version of software, to access the fifth data in the first format from the first storage part P1.

Optionally, first service unit 402 is adapted to send a second request to the first memory portion that first service unit 402, having the second version of software installed, wants to access sixth data in the second format. For example, the sending unit 409 enables the first traffic unit 402 to send the second request to the first memory portion P1. When the sixth data in the first format is available in the first storage part P1, after the first storage part receives the second request, the sixth data in the first format is converted into sixth data in the second format, and the converted sixth data in the second format is stored in the second storage part P2 while the sixth data in the first format is deleted from the first storage part P1. The first service unit 402, in which the second version of software is installed, is used to access the sixth data in the second format from the second storage section. For example, the first access unit 406 enables the first service unit 402, in which the second version of software is installed, to access the sixth data in the second format from the second storage portion P2.

Optionally, the software may be subject to an update rollback, in other words, the updated software may be set to an earlier version, e.g., from the second version to the first version. For illustrative purposes, first business unit 402, having rollback software installed, is used to set the software in business unit 402 from the second version back to the first version. For example, the first update unit 407 enables the first service unit 402, which is installed with the second version of software, to set the software in the service node from the second version back to the first version. However, the present application is not so limited; when the second service unit 412 sets the software in the second service node from the second version to the first version, the second service unit 412 performs a similar operation.

In this case, the first service unit 402 with the rollback software installed is configured to send a third request to the first storage section that the first service unit 402 with the first version of software installed wants to access the seventh data in the first format. For example, the sending unit 409 enables the first traffic unit 402 to send the third request to the first memory portion P1. When the seventh data in the first format is available in the first storage portion P1, the first service unit 402, in which the first version of software is installed, is used to access the seventh data in the first format from the first storage portion. For example, the first access unit 406 enables the first service unit 402, in which the first version of software is installed, to access the seventh data in the first format from the first storage portion P1. When the seventh data in the first format is not available in the first storage part P1, after the first storage part P1 receives the third request, the seventh data in the second format stored in the second storage part P2 is converted into the seventh data in the first format, and the converted seventh data in the first format is stored into the first storage part P1. Subsequently, the first service unit 402, in which the first version of software is installed, is used to access the seventh data in the first format from the first storage part P1.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the examples disclosed in this specification may be embodied in electronic hardware or in a combination of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

It will be clearly understood by those skilled in the art that for the sake of convenience and simplicity of description, for the detailed working of the aforementioned systems, devices and units, reference may be made to the corresponding procedures in the aforementioned method embodiments and details will not be described herein.

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the described apparatus embodiments are merely exemplary. For example, the cell partitions are merely logical functional partitions and may be other partitions in actual implementation. For example, various elements or components may be combined or integrated in another system or certain features may be omitted, or not implemented. Further, the shown or discussed mutual coupling or direct coupling or communicative connection may be realized by some interfaces. Direct coupling or communicative connection between devices or units may be implemented electronically, mechanically, or otherwise.

Elements described as separate parts may or may not be physically separate and parts described as elements may or may not be physical elements, may be located in one memory part or may be distributed over a plurality of network elements. Some or all of the units may be selected according to actual requirements to achieve the purpose of the solution in the embodiments.

In addition, the functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist separately physically, or two or more units may be integrated into one unit.

When the functions are implemented in the form of software functional units and sold or used as separate products, the functions may be stored in a computer readable storage medium. Based on this understanding, the solution of the invention can be implemented substantially as or as part of the state of the art or as part of a software product. A computer software product is stored on a storage medium and contains instructions for instructing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present invention. The storage medium includes: any medium that can store program code, such as a USB disk, a removable hard disk, a Read-Only Memory (ROM), a Random-Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only a specific embodiment of the present invention and is not intended to limit the scope of the present invention. Any changes or substitutions that may be easily found by those skilled in the art within the technical scope of the present disclosure should fall within the protective scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A method for updating software in a telecommunication device from a first version to a second version, characterized in that at least a first service node and a second service node are included in the telecommunication device, the first service node and the second service node being respectively installed with the software, the method comprising:

accessing data from a first storage portion located in a memory of the telecommunications device and storing data in a first format by at least one of the first service node having the first version of software installed prior to updating the software in the first service node and the second service node having the first version of the software installed prior to updating the software in the second service node;

updating, by the first service node, the software in the first service node from the first version to the second version;

accessing, by the first service node, data from a second storage portion, when the first service node is installed with the second version of the software after the software in the first service node is updated from the first version to the second version, wherein the second storage portion is located in the memory and stores data in a second format, including those data converted from the data in the first format stored in the first storage portion;

updating, by the second service node, the software in the second service node from the first version to the second version after the software in the first service node is updated from the first version to the second version; and

accessing, by the second service node, data from the second storage portion when the second service node is installed with the second version of the software after the software in the second service node is updated from the first version to the second version.

2. The method according to claim 1, wherein the data in the first format in the first storage portion is converted into the data in the second format according to a data conversion rule, and the converted data in the second format is stored in the second storage portion.

3. The method of claim 1 or 2, wherein the first storage portion and the second storage portion are generated in the memory according to instructions from an operation and maintenance system, the method further comprising:

after generating the first and second memory portions in the memory, receiving, by the first and second service nodes, a first identification of the first memory portion and a second identification of the second memory portion from the operation and maintenance system;

wherein the first business node having the first version of the software installed therein or the second business node having the first version of the software installed therein accesses data from the first storage portion based on the first identification of the first storage portion, and wherein the first business node having the second version of the software installed therein or the second business node having the second version of the software installed therein accesses data from the second storage portion based on the second identification of the second storage portion.

4. The method of claim 3, wherein the first portion of storage comprises a first instance of storage in the memory and the second portion of storage comprises a second instance of storage in the memory;

wherein the first identity of the first storage portion comprises a first address of the first storage instance, and wherein the second identity of the second storage portion comprises a second address of the second storage instance.

5. The method of claim 3, wherein the first storage portion comprises a first table in a stored instance in the memory and the second storage portion comprises a second table in the stored instance;

wherein the first identification of the first storage portion comprises a first number of tables of the first table, and wherein the second identification of the second storage portion comprises a second number of tables of the second table.

6. A method according to claim 1 or 2, wherein accessing data from a second storage portion by the first service node when the first service node is installed with the second version of the software after the software in the first service node is updated from the first version to the second version comprises:

sending, by the first service node, a first request to the second storage portion that the first service node, having the second version of the software installed, wants to access first data in the second format; and

accessing, by the first service node, the first data in the second format from the second storage portion.

7. The method of claim 6, wherein when the first data in the second format is available in the second storage portion, the first data in the first format stored in the first storage portion is converted into the first data in the second format after the second storage portion receives the first request, and wherein the converted first data in the second format is stored into the second storage portion.

8. The method according to claim 1 or 2, characterized in that the method further comprises:

adding second data in the first format to the first storage portion by the second service node in which the first version of the software is installed, wherein the second data in the first format is converted into the second data in the second format and the converted second data in the second format is stored in the second storage portion; accessing the second data in the second format from the second storage portion by the first service node installed with the second version of the software;

or modifying third data stored in the first storage portion by the second service node in which the first version of the software is installed, wherein the modified third data in the first format is converted into the modified third data in the second format and the modified third data in the second format is stored in the second storage portion; accessing the third data in the second format from the second storage portion through the first service node in which the second version of the software is installed.

9. The method according to claim 1 or 2, characterized in that the method further comprises:

adding fourth data in the second format to the second storage portion by the first service node in which the second version of the software is installed, wherein the fourth data in the second format is converted into the fourth data in the first format and the converted fourth data in the first format is stored in the first storage portion; accessing the fourth data in the first format from the second storage portion through the second service node in which the first version of the software is installed;

or modifying fifth data stored in the second storage portion by the first service node in which the second version of the software is installed, wherein the modified fifth data in the second format is converted into the modified fifth data in the first format and the modified fifth data in the first format is stored in the first storage portion; accessing the fifth data in the first format from the first storage portion through the second service node in which the first version of the software is installed.

10. A method according to claim 1 or 2, wherein accessing data from a second storage portion by the first service node when the first service node is installed with the second version of the software after the software in the first service node is updated from the first version to the second version comprises:

sending, by the first service node, a second request to the first storage portion that the first service node, in which the second version of the software is installed, wants to access sixth data in the second format, wherein when the sixth data in the first format is available in the first storage portion, after the first storage portion receives the second request, the sixth data in the first format is converted into the sixth data in the second format, and the converted sixth data in the second format is stored in the second storage portion; and

accessing, by the first service node, the sixth data in the second format from the second storage portion.

11. The method of claim 10, further comprising:

setting, by any of the first service node and the second service node, the software in the first service node or the second service node from the second version back to the first version;

sending, by the service node installed with the software set back to the first version, a third request to the first storage section that the service node installed with the software set back to the first version wants to access seventh data in the first format; and

when the seventh data in the first format is available in the first storage section, the service node installed with the software set back to the first version accesses the seventh data in the first format from the first storage section;

or when the seventh data in the first format is not available to the first storage portion, after the first storage portion receives the third request, the seventh data in the second format stored in the second storage portion is converted into the seventh data in the first format, and the converted seventh data in the first format is stored into the first storage portion; accessing the seventh data in the first format from the first storage section through the service node installed with the software set back to the first version.

12. The method of claim 1 or 2, wherein the first service node or the second service node comprises a board, a process entity, or a virtual machine.

13. The method of claim 1 or 2, wherein the telecommunications device comprises a mobility management entity, a serving gateway, or a packet data network gateway.

14. A telecommunications device, comprising:

at least a first service node and a second service node for installing software to be updated from a first version to a second version, respectively, wherein the first service node is configured to install the software of the first version before updating the software in the first service node; before updating the software in the second service node, the second service node is configured to install the first version of the software; at least one of the first service node installed with the first version of the software and the second service node installed with the first version of the software is used for accessing the data in the first format from the first storage part;

wherein when the first service node installs the second version of the software after the software in the first service node is updated from the first version to the second version, the first service node is further configured to update the software in the first service node from the first version to the second version, the first service node installed with the second version of the software being configured to access the data in the second format from the second storage portion;

wherein when the second service node installs the second version of the software after the software in the second service node is updated from the first version to the second version, the second service node is further for updating the software in the second service node from the first version to the second version after the software in the first service node is updated from the first version to the second version, the second service node installing the second version of the software being for accessing the data in the second format from the second storage portion.

15. The telecommunications device of claim 14, wherein the data in the first format in the first storage portion is converted to the data in the second format according to a data conversion rule and stored in the second storage portion.

16. Telecommunication device according to claim 14 or 15, characterized in that the first memory portion and the second memory portion are generated in the first memory according to instructions from an operation and maintenance system;

wherein after the first and second memory portions are generated in the first memory, the first and second service nodes are configured to receive a first identification of the first memory portion and a second identification of the second memory portion from the operation and maintenance system; wherein the first service node having the first version of the software installed therein and the second service node having the first version of the software installed therein are to access data in the first format from the first storage portion based on the first identification of the first storage portion and to access data in the second format from the second storage portion based on the second identification of the second storage portion.

17. The telecommunications device of claim 16, wherein the first storage portion comprises a first stored instance in the first memory and the second storage portion comprises a second stored instance in the first memory; wherein the first identity of the first storage portion comprises a first address of the first storage instance, and wherein the second identity of the second storage portion comprises a second address of the second storage instance.

18. The telecommunications device of claim 16, wherein the first storage portion includes a first table in a storage instance in the first memory and the second storage portion includes a second table in the storage instance, wherein the first identification of the first storage portion includes a first number of tables of the first table, and wherein the second identification of the second storage portion includes a second number of tables of the second table.

19. Telecommunication device according to claim 14 or 15, characterized in that the first service node installed with the second version of the software is configured to send to the second storage section a first request for the first service node installed with the second version of the software to access the first data in the second format and to access the first data in the second format from the second storage section.

20. The telecommunications device of claim 19, wherein when the first data in the second format is not available in the second storage portion, the first data in the first format stored in the first storage portion is converted to the first data in the second format after the second storage portion receives the first request, and wherein the converted first data in the second format is stored in the second storage portion.

21. Telecommunication device according to claim 14 or 15, characterized in that when the second service node, in which the first version of the software is installed, adds second data in the first format to the first storage portion, the second data in the first format is converted into the second data in the second format and the converted second data in the second format is stored in the second storage portion; wherein the first service node having the second version of the software installed therein is operable to access the second data in the second format from the second storage portion;

or when the second service node in which the first version of the software is installed modifies third data stored in the first storage portion, the modified third data in the first format is converted into the modified third data in the second format and the modified third data in the second format is stored in the second storage portion; the first service node in which the second version of the software is installed is for accessing the third data in the second format from the second storage portion.

22. Telecommunication device according to claim 14 or 15, characterized in that when the first service node, in which the second version of the software is installed, adds fourth data in the second format to the second storage section, the fourth data in the second format is converted into the fourth data in the first format and the converted fourth data in the first format is stored in the first storage section; wherein the second service node having the first version of the software installed therein is operable to access the fourth data in the first format from the first storage portion;

or when the first service node in which the second version of the software is installed modifies fifth data stored in the second storage portion, the modified fifth data in the second format is converted into the modified fifth data in the first format and the modified fifth data in the first format is stored in the first storage portion; the second service node in which the first version of the software is installed is for accessing the fifth data in the first format from the first storage portion.

23. Telecommunication device according to claim 14 or 15, characterized in that when sixth data in the first format is available in the first memory portion, the first service node is adapted to send a second request to the first memory portion that a first processor circuit installed with the second version of the software wants to access the sixth data in the second format, after the first memory portion receives the second request, the sixth data in the first format is converted into the sixth data in the second format, and the converted sixth data in the second format is stored into the second memory portion; the first service node in which the second version of the software is installed is for accessing the sixth data in the second format from the second storage portion.

24. The telecommunications device of claim 23, wherein the first service node having the second version of the software installed thereon is configured to set the software in the service node from the second version back to the first version and to send a third request to the first memory portion that the first processor circuit having the first version of the software installed thereon wants to access seventh data in the first format;

wherein when the seventh data in the first format is available in the first storage portion, the first service node on which the first version of the software is installed is used to access the seventh data in the first format from the first storage portion;

or when the seventh data in the first format is not available in the first storage portion, after the first storage portion receives the third request, the seventh data in the second format stored in the second storage portion is converted into the seventh data in the first format and the converted seventh data in the first format is stored into the first storage portion; the first service node installed with the first version of the software is configured to access the seventh data in the first format from the first storage section.

25. Telecommunication device according to claim 14 or 15, characterized in that the first service node or the second service node comprises a board, a process entity or a virtual machine.

26. The telecommunications device of claim 14 or 15, wherein the telecommunications device comprises a mobility management entity, a serving gateway or a packet data network gateway.