WO2015192298A1

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

Info

Publication number: WO2015192298A1
Application number: PCT/CN2014/079960
Authority: WO
Inventors: Yang Shen; Jidong Zhang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2014-06-16
Filing date: 2014-06-16
Publication date: 2015-12-23
Also published as: CN106462421A; CN106462421B

Abstract

The present application provides a telecommunication device and a method for updating software. The method includes: accessing, by at least one of the first service node and the second service node, data in a first format from a first storage section located in a memory of a telecommunication device; updating the software in the first service node to the second version; accessing, by the first service node installed with the software of the second version, data from a second storage section, the second storage section 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; and updating the software in the second service node to the second version after the software in the first service node is updated. Therefore, the first storage section and the second storage section enable the service node installed with the software of different versions to access data in a corresponding format. There is no need for the service node to pay attention to data compatibility, achieving easy implementation of lossless updating software in a telecommunication device.

Description

TELECOMMUNICATION DEVICE AND METHOD FOR UPDATING SOFTWARE IN A TELECOMMUNICATION DEVICE

TECHNICAL FIELD

[0001] The present application relates to the field of communications technologies, and in particular, to a telecommunication device and a method for updating software in a telecommunication device.

BACKGROUND

[0002] In a life cycle of software in a telecommunication device, the software needs to be constantly updated to adapt to new demands. In order to update software from an old version to a new version, the software of the old version is disabled at a certain time, and the software of the new version will be not open to the service until the updating process is finished. Therefore, the service is interrupted during the process of updating the software.

[0003] FIG. 1 illustrates a conventional method for lossless updating software in a telecommunication device 106. The telecommunication device 106 includes an active board (AB) 102 and a standby board (SB) 104. The software of an old version (OLD VER) is uploaded to both AB 102 and SB 104. The method includes: in step 11, the software of the old version in SB 104 is updated to new version ( EW VER); in step 12, the data for the software of the old version is backup from AB 102 to SB 104; in step 13, AB 102 and SB performs switchover so that SB 104 turns to AB 104' while AB 102 turns to SB 102', and AB 104', as a current AB, takes over service from SB 102'; and in step 14, the software of the old version in SB 102' is also updated to new version.

[0004] However, the data format may change in different version of software. Since a board performs service logics calculating as well as data storing in current system architecture evolution (SAE) system, to backup data in old format adopted by the software of the old version from AB 102 to SB 104 in which the software of the new version adopts new data format, data compatibility must be taken into account in the new version software. For example, the software of the new version should be compatible with different old data formats. Therefore, it is complex to implement conventional method for lossless updating software and put it into large-scale usage in practice. SUMMARY

[0005] Embodiments of the present application provide a telecommunication device and a method for updating software in a telecommunication device.

[0006] According to one aspect, a method is provided for updating software from a first version to a second version in a telecommunication device. At least a first service node and a second service node are included in the telecommunication device, and the first service node and the second service node are installed with the software respectively. The method includes:

accessing, by at least one of the first service node and the second service node installed with software of the first version before the software in the first service node is updated and the second service node installed with the software of the first version before the software in the second service node is updated, data from a first storage section, wherein the first storage section is located in a memory of the telecommunication device and stores data in a first format;

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 section when the first service node is installed with the software of the second version after the software in the first service node is updated from the first version to the second version, wherein the second storage section is located in the memory and stores data in a second format comprising those converted from the data in the first format stored in the first storage section;

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 section when the second service node is installed with the software of the second version after the software in the second service node is updated from the first version to the second version.

[0007] According to another aspect, a telecommunication device is provided. The telecommunication device includes:

a first memory, comprising a first storage section and a second storage section, wherein the first storage section is configured to store data in a first format and the second storage section is configured to store data in a second format comprising those converted from the data in the first format stored in the first storage section; and at least a first service node and a second service node, configured to be installed with software to be updated from a first version to a second version, respectively, wherein before the software in the first service node is updated, the first service node is configured to be installed with the software of the first version; before the software in the second service node is updated, the second service node is configured to be installed with the software of the first version; at least one of the first service node installed with the software of the first version and the second service node installed with the software of the first version is configured to access data in the first format from the first storage section;

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

wherein 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, when the second service node is installed with the software of the second version after the software in the second service node is updated from the first version to the second version, the second service node installed with the software of the second version is configured to access data in the second format from the second storage section.

[0008] These and other aspects of the invention will be apparent from the embodiments described below. According to the embodiments of the present application, the first storage section and the second storage section in the memory enable the service node installed with the software of different versions to access data in a corresponding format. Therefore, there is no need for the service node to pay attention to data compatibility, achieving easy implementation of lossless updating software in a telecommunication device.

BRIEF DESCRIPTION OF DRAWINGS

[0009] To illustrate the technical solutions in the embodiments of the present application more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments or the prior art. Apparently, the accompanying drawings in the following description show merely some embodiments of the present application, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0010] FIG. 1 illustrates a conventional method for lossless software updating in a telecommunication device;

[0011] FIG. 2 illustrates a flowchart of a method for updating software in a telecommunication device, according to one embodiment of the present application;

[0012] FIG. 3 A illustrates an example of how to create the first storage section and the second storage section in the memory, according to one embodiment of the present application;

[0013] FIG. 3B and FIG. 3C illustrate two examples of accessing, by the first service node installed with the software of the second version, data from the second storage section, according to one embodiment of the present application;

[0014] FIG. 3D illustrates an example of a flowchart for rollback software updating, according to one embodiment of the present application;

[0015] FIG. 4 illustrates a simplified block diagram of a telecommunication device, according to one embodiment of the present application.

DESCRIPTION OF EMBODIMENTS [0016] The following clearly describes the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application. Apparently, the described embodiments are merely a part rather than all of the embodiments of the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0017] FIG. 2 illustrates a flowchart of a method for updating software in the telecommunication device, according to one embodiment of the present application.

[0018] The telecommunication device refers to a device for realizing the functions as a logic network element in a telecommunication system, for example, the telecommunication device refers to a device for realizing the functions as a logic network element as defined in 3rd Generation Partnership Project (3GPP) protocol. The telecommunication device may include but not limited to a mobility management entity (MME), a serving gateway (SGW), or a packet data network gateway (PGW).

[0019] In one instance, the telecommunication device includes multiple service nodes and a memory. The multiple service nodes are configured to perform, but not limited to at least one of calculate service logics, process signaling and forward data. For example, a service node may include but not limited to a board, a process entity, or a virtual machine. The software aimed for one service is uploaded to at least a pair of service nodes, e.g., a first service node (SN1) and a second service node (SN2). In other words, the first service node and the second service node are installed with the software, respectively. The software may need to be updated from one version to another version according to requirement of service. The memory is configured to store data which is generated or received by the service nodes. At least a first storage section PI and a second storage section P2 are located in the memory.

[0020] Optionally, an operation and maintenance system is configured to manage the operation of the service nodes in the telecommunication device. In one instance, the operation and maintenance system can be implemented by a stand-alone system which is coupled to the telecommunication device. In another instance, the operation and maintenance system can be integrated inside the telecommunication device.

[0021] Before the software in the first service node is updated, the first service node is installed with software of the first version. And before the software in the second service node is updated, the second service node is installed with the software of the first version.

[0022] As illustrated in FIG. 2, in step 21, at least one of the first service node installed with the software of the first version and the second service node installed with the software of the first version accesses data in a first format from the first storage section PI . For example, data may include but not limited to service data, e.g., cell phone number data, corresponding serving cell data, or user equipment time limit data

[0023] The term "access data in a first format from the first storage section" herein refers to an operation of storing data related to a service into the first storage section, or an operation of reading data related to the service from the first storage section. In one instance, the first service node and the second service node undertake a part of the service, respectively. Thus, both the first service node and the second service node access data in the first format from the first storage section. In another instance, only the first service node or the second service node undertakes the whole service. Thus, only the first service node or the second service node accesses data in the first format from the first storage section.

[0024] The first storage section PI and the second storage section P2 are located in the memory of the telecommunication device. In one instance, the first storage section includes a first storage instance in the memory, and the second storage section includes a second storage instance in the memory. In another instance, the first storage section includes a first table in a storage instance in the memory, and the second storage section includes a second table in the storage instance. The first storage section stores data in the 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 instance, the first storage section and the second storage section are created in the memory. How the first storage section and the second storage section are created will be described in relation with FIG. 3 A.

[0025] 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.

[0026] In step 23, the first service node accesses data in the second format from the second storage section when the first service node is installed with the software of the second version 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 the second format including those converted from the data in the first format stored in the first storage section. For example, the data in the first format stored in the first storage section is converted to the 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 section.

[0027] The term "access data in the second format from the second storage section" herein refers 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 the service from the second storage section.

[0028] 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, the software in the second service node is updated from the first version to the second version after the software in the first service node is updated to the second version.

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

[0030] Therefore, during the process of updating the software in the first service node, the second service node installed with the software of the first version is still open to the service, and is able to access data in the first format from the first storage section. When the software in the first service node is updated to the second version, the first service node is able to access data in the second format from the second storage section. Thus, the service is not interrupted during the updating process and lossless updating is achieved.

[0031] Since the data format converting is performed inside the memory rather than inside the service node. As a result, a service node installed with the software of the first version is able to access data in the first format from the first storage section before updating, and the service node installed with the software of the second version is able to access data in the second format from the second storage section after updating. Advantageously, the first storage section and the second storage section in the memory enable the service node installed with the software of different versions to access data in a corresponding format. Therefore, there is no need for the service node to pay attention to data compatibility, achieving easy implementation of lossless updating software in a telecommunication device.

[0032] FIG. 3 A illustrates an example of how to create the first storage section and the second storage section in the memory.

[0033] Steps 311-316 are performed to create the first storage section in the memory.

[0034] In step 311, the operation and maintenance system sends an instruction indicating the first storage section to be created in the memory. After the first storage section is created in the memory, in step 312, the first storage section's identification is sent to the operation and maintenance system. For example, the first storage section's identification includes an address of the first storage section if the first storage section is a first storage instance in the memory, or the first storage section's identification includes a table number of the first storage section if the first storage section is a first table in a storage instance in the memory. Afterwards, in step 313, the first service node receives the first storage section's identification from the operation and maintenance system; in step 314, the second service node receives the first storage section's identification from the operation and maintenance system. Thus, in step 315, the first service node installed with the software of the first version is able to access data in the first format from the first storage section based on the identification of the first storage section; and in step 316, the second service node installed with the software of the first version is able to access data in the first format from the first storage section based on the identification of the first storage section.

[0035] Similarly, steps 321-323 are performed to create the second storage section:

[0036] In step 321, the operation and maintenance system sends an instruction indicating the second storage section to be created in the memory. In the meanwhile, the operation and maintenance system sends the first storage section's identification, an updating relation and a data conversion rule to the memory. The updating relation indicates that the software is updated from a first version to a second version. The data conversion rule indicates the conversion rule for the data. For example, as shown in Table 1, the conversion rule indicates that data A, B, C in first format is converted to data A, B', C in second format, respectively. And data D' in second format is set as default.

in second format A' B' C D'

Tab e 1

[0037] After the second storage section is created in the memory, in step 322, the second storage section's identification is sent to the operation and maintenance system. For example, the second storage section's identification includes an address of the second storage section if the second storage section is a second storage instance in the memory, or the second storage section's identification includes a table number of the second storage section if the second storage section is a second table in the storage instance. Afterwards, in step 323, the operation and maintenance system sends the second storage section's identification to the first storage section.

[0038] 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, the operation and maintenance system also sends the second storage section's identification to the first service node. Therefore, after the software in the first service node finishes updating, the first service node is able to access data in the second format from the second storage section according to the second storage section's identification. That is to say, before the process of updating, the first service node installed with the software of the first version accesses data in first format from the first storage section according to the first storage section's identification; after the process of updating, the first service node installed with the software of the second version accesses data in second format from the second storage section according to the second storage section's identification.

[0039] 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 the second storage section's identification to the second service node. Therefore, after the software in the second service node finishes updating, the second service node is able to access data in the second format from the second storage section according to the second storage section's identification.

[0040] FIG. 3B and FIG. 3C illustrate two examples of accessing, by the first service node installed with the software of the second version, data from the second storage section. FIG. 3B and FIG. 3C are described in combination with FIG. 2.

[0041] As illustrated in FIG. 3B, optionally, in step 221, 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. In one instance, data in the first format stored in the first storage section is converted to the data in the second format and the converted data in the second format is stored into the second storage section before the software in the first service node is updated, in step 222. In another instance, data in the first format stored in the first storage section is being converted to the data in the second format and being stored into the second storage section simultaneously with the software in the first service node being updated, in step 222'.

[0042] Then, steps 231-232 are performed to realize step 23 in FIG. 2.

[0043] For example, after the software in the first service node is updated to the second version, the first service node installed with the software of the second version is able to store data in the second format into the second storage section (not shown in FIG. 3B). Furthermore, when the first service node installed with the software of the second version desires to access data in the second format, e.g., first data, in step 231, the first service node sends to the second storage section a first request that the first service node installed with the software of the second version desires to access the first data in the second format. After the second storage section receives the first request, if the first data in the second format is available in the second storage section, in step 232, the first service node accesses the first data in the second format from the second storage section.

[0044] When the first data in the second format is not available in the second storage section, for example, when the procedure of converting data in first format to data in second format and storing the converted data in second format into the second storage section has not been finished and the first data in the first format hasn't been converted, the second storage section and the first storage section perform a real-time interaction in steps 233-234. More specifically, in step 233, the second storage section sends a real-time request to the first storage section. When the first data in the first format is available in the first storage section, in step 234, the first data in the first format is converted to the first data in the second format according to the updating relation and the data conversion rule, and the converted first data in the second format is stored into the second storage section. Then, in step 232, the first service node accesses the first data in the second format from the second storage section.

[0045] Therefore, by means of converting data according to a certain data conversion rule, the memory can realize data format converting, so that the memory can support updating software in the service node without updating the memory itself.

[0046] In one instance, after the step 24 (step 241 as illustrated in FIG. 3B) and 25 (step 251 as illustrated in FIG. 3B) are performed, the method further includes steps 261-263, which are performed to delete the data stored in the first storage section.

[0047] For example, in step 261 and step 262, the operation and maintenance system informs the first storage section and the second storage section that the updating process of the software is finished, respectively. Then, in step 263, the data stored in the first storage section is deleted.

[0048] In one instance, in a stage between the step 23 and 24, the service node may add or modify data in one format, e.g., in the process of calculating service logics. In this case, the method further includes: in step 280, in-time converting and storing data is performed between the first storage section and the second storage section. In one instance, the second service node installed with the software of the first version adds second data in the first format into the first storage section. The first storage section accordingly sends a real-time instruction to the second storage section. After the instruction is received by the second storage section, the second data in the first format is converted to the second data in the second format according to the updating relation and the data conversion rule, and the converted second data in the second format is stored into the second storage section. Therefore, the first service node installed with the software of the second version is able to access the second data in the second format from the second storage section. In another instance, the second service node installed with the software of the first version modifies third data in the first format stored in the first storage section. The first storage section accordingly sends a real-time instruction to the second storage section. After the instruction is received by the second storage section, the third data in the first format is converted to the third data in the second format according to the updating relation and the data conversion rule, and the converted third data is stored into the second storage section. Therefore, the first service node installed with the software of the second version is able to access the third data in the second format from the second storage section.

[0049] In yet another instance, the first service node installed with the software of the second version adds fourth data in the second format into the second storage section. The second storage section accordingly sends a real-time instruction to the first storage section. After the instruction is received by the first storage section, the fourth data in the second format is converted to the fourth data in the first format according to the updating relation and the data conversion rule, and the converted fourth data in the first format is stored into the first storage section. Therefore, the second service node installed with the software of the first version is able to access the fourth data in the first format from the first storage section. In yet another instance, the first service node installed with the software of the second version modifies fifth data in the second format stored in the second storage section. The second storage section accordingly sends a real-time instruction to the first storage section. After the instruction is received by the first storage section, the fifth data in the second format is converted to the fifth data in the first format according to the updating relation and the data conversion rule, and the converted fifth data is stored into the first storage section. Therefore, the second service node installed with the software of the first version is able to access the fifth data in the first format from the first storage section.

[0050] In the example shown in FIG. 3C, optionally, 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, in step 221. After the software in the first service node is updated to the second version, steps 235-237 are performed to realize step 23 in FIG. 2.

[0051] For example, after the software in the first service node is updated to the second version, the first service node installed with the software of the second version is able to store data in the second format into the second storage section (not shown in FIG. 3C). Furthermore, when the first service node installed with the software of the second version desires to access data in the second format, e.g., sixth data, the first service node sends to the first storage section a second request that the first service node installed with the software of the second version desires to access the sixth data in the second format, in step 235, to activate data format converting. Thus, after the first storage section receives the second request, the second storage section and the first storage section perform a real-time interaction in step 236. More specifically, when the sixth data in the first format is available in the first storage section, the sixth data in the first format is converted to the sixth data in the second format according to the updating relation and the data conversion rule, and the converted sixth data in the second format is stored into the second storage section while the sixth data in the first format is deleted from the first storage section. Then, in step 237, the first service node accesses the sixth data in the second format from the second storage section.

[0052] In one instance, after the step 24 (step 241 as illustrated in FIG. 3C) and 25 (step 251 as illustrated in FIG. 3C) are performed, the method further includes steps 261-265.

[0053] For example, in step 261 and step 262, the operation and maintenance system informs the first storage section and the second storage section that the updating process is finished, respectively. In step 264, the remaining data stored in the first storage section which has not been desired by the first service node installed with the software of the second version, is converted to data in second format and stored into the second storage section. Then, in step 265, corresponding data in first format stored in the first storage section is deleted.

[0054] In the example shown in FIG. 3C, software may be subjected to updating rollback. In other words, an updated software may be set to an earlier version, e.g., from the second version to the first version. In this case, an embodiment of the present application can be applied to. FIG. 3D illustrates an example of a flowchart for rollback software updating. In the example of FIG. 3D, for illustrative purpose, the first service node sets the software in the first service node from the second version to the first version. The first service node installed with the rollback software desires to access data in the first format. However, the application is not so limited; when the second service node sets the software in the second service node from the second version to the first version, the second service node performs similar operation.

[0055] When the first service node installed with the rollback software desires to access data in the first format, e.g., seventh data, in step 271, the first service node sends to the first storage section a third request that the first service node installed with the software of the first version desires to access the seventh data. If the seventh data in the first format is available in the first storage section, in step 274, the first service node installed with the software of the first version directly accesses the seventh data in the first format from the first storage section.

[0056] However, the seventh data in the first format may be unavailable in the first storage section, no matter it is deleted after the above-mentioned updating process is finished, or it just hasn't exist ever in the first data set. Therefore, the method further includes steps 272 and 273. In steps 272-273, the second storage section and the first storage section perform a real-time interaction to convert the corresponding data in second format to desired data in first format.

[0057] For example, in step 272, if the seventh data in the first format is not available in the first storage section, the first storage section sends an instruction to the second storage section. When the second storage section receives the instruction, the seventh data in the second format is converted to the seventh data in the first format according to the updating relation 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. Therefore, in step 274, the first service node installed with the rollback software accesses the seventh data in the first format from the first storage section.

[0058] It should be understood that the application is not limited to updating software aimed for one service, and that the application also applies to updating software aimed for multiple services. Multiple software can be updated simultaneously using the method as described from FIG. 2 to FIG. 3D, or be updated successively.

[0059] FIG. 4 illustrates a simplified block diagram of a telecommunication device 400, according to one embodiment of the present invention. FIG. 4 is described in relation to FIG. 2-FIG. 3D.

[0060] As described above, the telecommunication device 400 may include but not limited to a MME, a SGW or a PGW, and the telecommunication device 400 includes at least a first service unit 402, a second service unit 412, and a storing unit 401. The first service unit 402 and the second service unit can 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 not limited to a board, a process entity, or a virtual machine. The storing unit 401 can be implemented by a memory. The memory 401 may be read-only, like a read-only memory (ROM), or readable/writeable, like a hard disk or a flash memory, or may be a random access memory (RAM).

[0061] In one instance, an operation and maintenance system 403 is a stand-alone system coupled to the telecommunication device 400. In another instance, the operation and maintenance system 403 can be integrated inside the telecommunication device 400. The above elements of the telecommunication device 400 may be coupled with each other by a bus, such as anyone or any combination of a data bus, an address bus, a control bus, an expansion bus and a local bus.

[0062] The storing unit 401 includes a first storage section PI and a second storage section P2. In one instance, the first storage section includes a first storage instance in the storing unit 401, and the second storage section includes a second storage instance in the storing unit 401. In another instance, the first storage section includes a first table in a storage instance in the storing unit 401, and the second storage section includes a second table in the storage instance. The first storage section is configured to store data in a first format. The second storage section is configured to store data in a second format including those converted from the data in the first format stored in the first storage section.

[0063] For example, the first service unit 402 includes a first accessing unit 406, a first updating unit 407, a first receiving unit 408 and a sending unit 409. The second service unit 412 includes a second accessing unit 416, a second updating unit 417 and a second receiving unit 418. The first service unit 402 and the second service unit 412 are installed with software to be updated from a first version to a second version, respectively. In one instance, the first accessing unit 406, the first updating unit 407, the first receiving unit 408 and the sending unit 409 can be implemented by a processor in the first service node; the second accessing unit 416, the second updating unit 417 and the second receiving unit 418 can be implemented by a processor in the second service node. In another instance, 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 can be implemented by one processor in the telecommunication device 400. The processor is the controlling center of a service node, and provides sequencing and processing facilities for executing instructions, performing interruption actions, providing timing functions and many other functions. Optionally, the processor includes one or multiple central processing units (CPUs). Unless stated otherwise, a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. As used herein, the term "processor" refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.

[0064] Before the software in the first service unit 402 is updated, the first service unit 402 is installed with the software of the first version; before the software in the second service unit 412 is updated, the second service unit 412 is installed with the software of the first version. At least one of the first service unit 402 installed with the software of the first version and the second service unit 412 installed with the software of the first version is configured to access data in the first format from the first storage section. For example, the first accessing unit 406 enables the first service unit 402 installed with the software of the first version to access data in the first format from the first storage section PI, and/or, the second accessing unit 416 enables the second service unit 412 installed with the software of the first version to access data in the first format from the first storage section PI .

[0065] The first service unit 402 is further configured to update the software in the first service unit 402 from the first version to the second version. For example, the first updating unit 407 enables the first service unit 402 to update the software in the first service unit 402 from the first version to the second version. When the first service unit 402 is installed with the software of the second version after the software in the first service unit 402 is updated from the first version to the second version, the first service unit 402 installed with the software of the second version is configured to access data in the second format from the second storage section. For example, the first accessing unit 406 enables the first service unit 402 installed with the software of the second version to access data in the second format from the second storage section P2.

[0066] The second service unit 412 is further configured to update the software in the second service unit 412 from the first version to the second version after the software in the first service unit 402 is updated from the first version to the second version. For example, the second updating unit 417 enables the second service unit 412 to update the software in the second service unit 412 from the first version to the second version after the software in the first service unit 402 is updated from the first version to the second version. When the second service unit 412 is installed with the software of the second version after the software in the second service unit 412 is updated from the first version to the second version, the second service unit 412 installed with the software of the second version is configured to access data in the second format from the second storage section the second service unit 412. For example, the second accessing unit 416 enables the second service unit 412 installed with the software of the second version to access data in the second format from the second storage section P2.

[0067] Therefore, during the process of updating the software in the first service node, the second service node installed with the software of the first version is still open to the service, and is able to access data in the first format from the first storage section. When the software in the first service node is updated to the second version, the first service node is able to access data in the second format from the second storage section. Thus, the service is not interrupted during the updating process and lossless updating is achieved. The data format converting is performed inside the memory rather than inside the service node. As a result, a service node installed with the software of the first version is able to access data in the first format from the first storage section before updating, and the service node installed with the software of the second version is able to access data in the second format from the second storage section after updating. Advantageously, the first storage section and the second storage section in the memory enable the service node installed with the software of different versions to access data in a corresponding format. Therefore, there is no need for the service node to pay attention to data compatibility, achieving easy implementation of lossless updating software in a telecommunication device.

[0068] In one instance, the first storage section PI and the second storage section P2 are created in the storing unit 401 according to an instruction from the operation and maintenance system 403. The first service node and the second service node are configured to receive first identification of the first storage section and second identification of the second storage section from the operation and maintenance system after the first storage section and the second storage section are created in the first memory. For example, the first receiving unit 408 enables the first service unit 402 to receive the first identification of the first storage section PI and the second identification of the second storage section P2 from the operation and maintenance system, and the second receiving unit 418 enables the second service unit 412 to receive the first identification of the first storage section PI and the second identification of the second storage section P2 from the operation and maintenance system 403. Thus, the first service unit 402 installed with the software of the first version and the second service unit 412 installed with the software of the first version are configured to access data in the first format from the first storage section based on the first identification of the first storage section, and to access data in the second format from the second storage section based on the second identification of the second storage section. For example, the first accessing unit 406 enables the first service unit 402 installed with the software of the first version to access data in the first format from the first storage section PI based on the first identification of the first storage section PI, or enables the first service unit 402 installed with the software of the second version to access data in the second format from the second storage section P2 based on the second identification of the second storage section P2. The second accessing unit 416 enables the second service unit 412 installed with the software of the first version to access data in the first format from the first storage section PI based on the first identification of the first storage section PI, or enables the second service unit 412 installed with the software of the second version to access data in the second format from the second storage section P2 based on the second identification of the second storage section P2.

[0069] In one instance, the first identification of the first storage section includes a first address of the first storage instance, and the second identification of the second storage section includes a second address of the second storage instance. In another instance, the first identification of the first storage section includes a first table number of the first table, and the second identification of the second storage section includes a second table number of the second table.

[0070] Optionally, the first service unit 402 installed with the software of the second version is configured to send to the second storage section a first request that the first service unit 402 installed with the software of the second version desires to access first data in the second format. For example, the sending unit 409 enables the first service unit 402 to send the first request to the second storage section P2. Then, the first service unit 402 installed with the software of the second version is configured to access the first data in the second format from the second storage section. For example, the first accessing unit 406 enables the first service unit 402 installed with the software of the second version to access the first data in the second format from the second storage section P2. When the first data in the second format is not available in the second storage section P2, the first data in the first format stored in the first storage section is converted to the first data in the second format after the first request is received by the second storage section P2, and the converted first data in the second format is stored into the second storage section P2. Then, the first service unit 402 installed with the software of the second version is configured to access the first data in the second format from the second storage section P2.

[0071] Optionally, when the second service unit 412 installed with the software of the first version adds second data in the first format into the first storage section PI, the second data in the first format is converted to the second data in the second format and the converted second data in the second format is stored into the second storage section P2. Then, the first service unit 402 installed with the software of the second version is configured to access the second data in the second format from the second storage section. For example, the first accessing unit 406 may enable the first service unit 402 installed with the software of the second version to access the second data in the second format from the second storage section P2. When the second service unit 412 installed with the software of the first version modifies third data stored in the first storage section PI, the modified third data in the first format is converted to the modified third data in the second format and the modified third data in the second format is stored into the second storage section P2. Then, the first service unit 402 installed with the software of the second version is configured to access the third data in the second format from the second storage section. For example, the first accessing unit 406 may enable the first service unit 402 installed with the software of the second version to access the third data in the second format from the second storage section P2. [0072] Similarly, when the first service unit 402 installed with the software of the second version adds fourth data in the second format into the second storage section P2, the fourth data in the second format is converted to the fourth data in the first format and the converted fourth data in the first format is stored into the first storage section PI . Then, the second service unit 412 installed with the software of the first version is configured 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 installed with the software of the first version to access the fourth data in the first format from the first storage section PI . When the first service unit 402 installed with the software of the second version modifies fifth data stored in the second storage section P2, the modified fifth data in the second format is converted to the modified fifth data in the first format and the modified fifth data in the first format is stored into the first storage section PI . Then, the second service unit 412 installed with the software of the first version is configured 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 installed with the software of the first version to access the fifth data in the first format from the first storage section P 1.

[0073] Optionally, the first service unit 402 is configured to send to the first storage section a second request that the first service unit 402 installed with the software of the second version desires to access sixth data in the second format. For example, the sending unit 409 enables the first service unit 402 to send the second request to the first storage section PI . When the sixth data in the first format is available in the first storage section PI, the sixth data in the first format is converted to the sixth data in the second format after the second request is received by the first storage section, and the converted sixth data in the second format is stored into the second storage section P2 while the sixth data in the first format is deleted from the first storage section PI . The first service unit 402 installed with the software of the second version is configured to access the sixth data in the second format from the second storage section. For example, the first accessing unit 406 enables the first service unit 402 installed with the software of the second version to access the sixth data in the second format from the second storage section P2.

[0074] Optionally, software may be subjected to updating rollback, in other words, an updated software may be set to an earlier version, e.g., from the second version to the first version. For illustrative purpose, the first service unit 402 installed with the rollback software is configured to set the software in the service unit 402 from the second version back to the first version. For example, the first updating unit 407 enables the first service unit 402 installed with the software of the second version to set the software in the service node from the second version back to the first version. However, the 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 similar operation.

[0075] In this case, the first service unit 402 installed with the rollback software is configured to send to the first storage section a third request that the first service unit 402 installed with the software of the first version desires to access seventh data in the first format. For example, the sending unit 409 enables the first service unit 402 to send the third request to the first storage section PI . When the seventh data in the first format is available in the first storage section PI, the first service unit 402 installed with the software of the first version is configured to access the seventh data in the first format from the first storage section. For example, the first accessing unit 406 enables the first service unit 402 installed with the software of the first version to access the seventh data in the first format from the first storage section PI . When the seventh data in the first format is not available in the first storage section PI, the seventh data in the second format stored in the second storage section P2 is converted to the seventh data in the first format after the third request is received by the first storage section PI, and the converted seventh data in the first format is stored into the first storage section PI . Then, the first service unit 402 installed with the software of the first version is configured to access the seventh data in the first format from the first storage section PI .

[0076] A person of ordinary skill in the art may be aware that, in combination with the examples described in the embodiments disclosed in this specification, units and algorithm steps may be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software depends on the particular applications and design constraint conditions of the technical solution. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of the present invention.

[0077] It may be clearly understood by a person skilled in the art that, for the purpose of convenient and brief description, for a detailed working process of the foregoing system, apparatus, and unit, reference may be made to a corresponding process in the foregoing method embodiments, and details are not described herein again.

[0078] In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the described apparatus embodiment is merely exemplary. For example, the unit division is merely logical function division and may be other division in actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces. The indirect couplings or communication connections between the apparatuses or units may be implemented in electronic, mechanical, or other forms.

[0079] The units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one storage section, or may be distributed on a plurality of network units. A part of or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

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

[0081] When the functions are implemented in a form of a software functional unit and sold or used as an independent product, the functions may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of the present invention essentially, or the part contributing to the prior art, or a part of the technical solutions may be implemented in a form of a software product. The computer software product is stored in a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device, or the like) to perform all or a part of the steps of the methods described in the embodiments of the present invention. The foregoing storage medium includes: any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk, or an optical disc.

[0082] The foregoing descriptions are merely specific implementation manners of the present invention, but are not intended to limit the protection scope of the present invention. Any variation or replacement readily figured out by a person skilled in the art within the technical scope disclosed in the present invention shall fall within the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

CLAIMS What is claimed is:

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

accessing, by at least one of the first service node installed with software of the first version before the software in the first service node is updated and the second service node installed with the software of the first version before the software in the second service node is updated, data from a first storage section, wherein the first storage section is located in a memory of the telecommunication device and stores data in a first format;

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

3. The method as claimed in claim 1 or 2, wherein the first storage section and the second storage section are created in the memory according to an instruction from an operation and maintenance system, the method further comprising: receiving, by the first service node and the second service node, first identification of the first storage section and second identification of the second storage section from the operation and maintenance system after the first storage section and the second storage section are created in the memory;

wherein the first service node installed with the software of the first version or the second service node installed with the software of the first version accesses data from the first storage section based on the first identification of the first storage section, and wherein the first service node installed with the software of the second version or the second service node installed with the software of the second version accesses data from the second storage section based on the second identification of the second storage section.

4. The method as claimed in claim 3, wherein the first storage section comprises a first storage instance in the memory and the second storage section comprises a second storage instance in the memory;

wherein the first identification of the first storage section comprises a first address of the first storage instance, and wherein the second identification of the second storage section comprises a second address of the second storage instance.

5. The method as claimed in claim 3, wherein the first storage section comprises a first table in a storage instance in the memory and the second storage section comprises a second table in the storage instance;

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

6. The method as claimed in any one of claims 1-5, wherein accessing, by the first service node, data from a second storage section when the first service node is installed with the software of the second version 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, to the second storage section, a first request that the first service node installed with the software of the second version desires 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 section.

7. The method as claimed in claim 6, wherein when the first data in the second format is not available in the second storage section, the first data in the first format stored in the first storage section is converted to the first data in the second format after the first request is received by the second storage section, and wherein the converted first data in the second format is stored into the second storage section.

8. The method as claimed in any one of claims 1-7, wherein the method further comprises: adding, by the second service node installed with the software of the first version, second data in the first format into the first storage section, wherein the second data in the first format is converted to the second data in the second format and the converted second data in the second format is stored into the second storage section; accessing, by the first service node installed with the software of the second version, the second data in the second format in the second format from the second storage section;

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

9. The method as claimed in any one of claims 1-8, wherein the method further comprises: adding, by the first service node installed with the software of the second version, fourth data in the second format into the second storage section, wherein the fourth data in the second format is converted to the fourth data in the first format and the converted fourth data in the first format is stored into the first storage section; accessing, by the second service node installed with the software of the first version, the fourth data in the first format from the first storage section;

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

10. The method as claimed in any one of claims 1-5, wherein accessing, by the first service node, data from a second storage section when the first service node is installed with the software of the second version 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, to the first storage section, a second request that the first service node installed with the software of the second version desires to access sixth data in the second format, wherein when the sixth data in the first format is available in the first storage section, the sixth data in the first format is converted to the sixth data in the second format after the second request is received by the first storage section, and the converted sixth data in the second format is stored into the second storage section; and

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

11. The method as claimed in claim 10, further comprising:

setting, by any service node 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 which is set back to the first version, to the first storage section, a third request that the service node installed with the software which is set back to the first version desires to access seventh data in the first format; and

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

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

12. The method as claimed in any one of claims 1-11, wherein the first service node or the second service node comprises a board, a process entity, or a virtual machine.

13. The method as claimed in any one of claims 1-12, wherein the telecommunication device comprises a mobility management entity, a serving gateway, or a packet data network gateway.

14. A telecommunication device, comprising:

a first memory, comprising a first storage section and a second storage section, wherein the first storage section is configured to store data in a first format and the second storage section is configured to store data in a second format comprising those converted from the data in the first format stored in the first storage section; and

at least a first service node and a second service node, configured to be installed with software to be updated from a first version to a second version, respectively, wherein before the software in the first service node is updated, the first service node is configured to be installed with the software of the first version; before the software in the second service node is updated, the second service node is configured to be installed with the software of the first version; at least one of the first service node installed with the software of the first version and the second service node installed with the software of the first version is configured to access data in the first format from the first storage section;

15. The telecommunication device as claimed in claim 15, wherein the first data format in the first storage section is converted to the data in the second format according to a data conversion rule and stored into the second storage section.

16. The telecommunication device as claimed in claim 14 or 15, wherein the first storage section and the second storage section are created in the first memory according to an instruction from an operation and maintenance system;

wherein the first service node and the second service node are configured to receive first identification of the first storage section and second identification of the second storage section from the operation and maintenance system after the first storage section and the second storage section are created in the first memory; wherein the first service node installed with the software of the first version and the second service node installed with the software of the first version are configured to access data in the first format from the first storage section based on the first identification of the first storage section, and to access data in the second format from the second storage section based on the second identification of the second storage section.

17. The telecommunication device as claimed in claim 16, wherein the first storage section comprises a first storage instance in the first memory and the second storage section comprises a second storage instance in the first memory; wherein the first identification of the first storage section comprises a first address of the first storage instance, and wherein the second identification of the second storage section comprises a second address of the second storage instance.

18. The telecommunication device as claimed in claim 16, wherein the first storage section comprises a first table in a storage instance in the first memory and the second storage section comprises a second table in the storage instance; wherein the first identification of the first storage section comprises a first table number of the first table, and wherein the second identification of the second storage section comprises a second table number of the second table.

19. The telecommunication device as claimed in any one of claims 14-18, wherein the first service node installed with the software of the second version is configured to send to the second storage section a first request that the first service node installed with the software of the second version desires to access first data in the second format, and to access the first data in the second format from the second storage section.

20. The telecommunication device as claimed in claim 19, wherein when the first data in the second format is not available in the second storage section, the first data in the first format stored in the first storage section is converted to the first data in the second format after the first request is received by the second storage section, and wherein the converted first data in the second format is stored into the second storage section.

21. The telecommunication device as claimed in any one of claims 14-20, wherein when the second service node installed with the software of the first version adds second data in the first format into the first storage section, the second data in the first format is converted to the second data in the second format and the converted second data in the second format is stored into the second storage section; wherein the first service node installed with the software of the second version is configured to access the second data in the second format from the second storage section;

or, when the second service node installed with the software of the first version modifies third data stored in the first storage section, the modified third data in the first format is converted to the modified third data in the second format and the modified third data in the second format is stored into the second storage section; wherein the first service node installed with the software of the second version is configured to access the third data in the second format from the second storage section.

22. The telecommunication device as claimed in any one of claims 14-21, wherein when the first service node installed with the software of the second version adds fourth data in the second format into the second storage section, the fourth data in the second format is converted to the fourth data in the first format and the converted fourth data in the first format is stored into the first storage section; wherein the second service node installed with the software of the first version is configured to access the fourth data in the first format from the first storage section;

or, when the first service node installed with the software of the second version modifies fifth data stored in the second storage section, the modified fifth data in the second format is converted to the modified fifth data in the first format and the modified fifth data in the first format is stored into the first storage section; wherein the second service node installed with the software of the first version is configured to access the fifth data in the first format from the first storage section.

23. The telecommunication device as claimed in any one of claims 14-18, wherein the first service node is configured to send to the first storage section a second request that the first processor circuitry installed with the software of the second version desires to access sixth data in the second format, when the sixth data in the first format is available in the first storage section, the sixth data in the first format is converted to the sixth data in the second format after the second request is received by the first storage section, and the converted sixth data in the second format is stored into the second storage section; wherein the first service node installed with the software of the second version is configured to access the sixth data in the second format from the second storage section.

24. The telecommunication device as claimed in claim 23, wherein the first service node installed with the software of the second version is further configured to set the software in the service node from the second version back to the first version, and to send to the first storage section a third request that the first processor circuitry installed with the software of the first version desires to access seventh data in the first format;

wherein when the seventh data in the first format is available in the first storage section, the first service node installed with the software of the first version is configured to access the seventh data in the first format from the first storage section;

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

25. The telecommunication device as claimed in any one of claims 14-24, wherein the first service node or the second service node comprises a board, a process entity, or a virtual machine.

26. The telecommunication device as claimed in any one of claims 14-25, wherein the telecommunication device comprises a mobility management entity, a serving gateway, or a packet data network gateway.