Disaster recovery emergency switching method and device, equipment and storage medium

Abstract

The embodiment of the application provides a disaster recovery emergency switching method, device, equipment and storage medium, the method is applied to a base station, and the method comprises the following steps: when a first device on a core network side currently connected by the base station fails, switching the base station to a second device connected by the core network side; the first device and the second device belong to different resource pools; and the embodiment of the application can solve the problem that the success rate of the disaster recovery emergency switching method in the prior art is low.

Description

TECHNICAL FIELD

[0001] The present application belongs to the field of communication, and particularly relates to a disaster recovery emergency switching method and device, equipment and a storage medium. BACKGROUND

[0002] Disaster recovery refers to establishing two or more sets of IT systems with the same functions in distant places, which can monitor the health status and switch functions between each other. When one system stops working due to an accident (such as fire, earthquake, etc.), the entire application system can be switched to another place, so that the system function can continue to work normally, thereby realizing disaster recovery emergency.

[0003] The success rate of the prior art disaster recovery emergency switching method is low due to the limitation of the existing device resource pool configuration. SUMMARY

[0004] The present application provides a disaster recovery emergency switching method, device, equipment and storage medium, which can solve the problem of low success rate of the prior art disaster recovery emergency switching method.

[0005] In a first aspect, the present application provides a disaster recovery emergency switching method, which is applied to a base station, and the method comprises the following steps.

[0006] When a first device on a core network side to which the base station is currently connected fails, the base station is switched to a second device on the core network side for connection; the first device and the second device belong to different resource pools.

[0007] Further, in an embodiment, when the first device on the core network side to which the base station is currently connected fails, the base station is switched to the second device on the core network side for connection, which comprises the following steps.

[0008] When the first device on the core network side to which a plurality of base stations are currently connected fails, a geographical area to which the plurality of base stations belong is determined.

[0009] According to a preset corresponding relationship between the geographical area and a switching sequence, the plurality of base stations are switched to the second device on the core network side for connection in sequence.

[0010] Further, in an embodiment, when the first device on the core network side to which the base station is currently connected fails, the base station is switched to the second device on the core network side for connection, which comprises the following steps.

[0011] When the first device on the core network side to which the base station is currently connected fails, the communication parameters of the first device currently configured by the base station are modified to the communication parameters of the second device.

[0012] The base station is connected to the second device according to the communication parameters of the second device.

[0013] Furthermore, in one embodiment, the first device belongs to the first mobile management node function resource pool, and the second device belongs to the second mobile management node function resource pool; or, the first device belongs to the first SAE-GW resource pool, and the second device belongs to the second SAE-GW resource pool.

[0014] When the first device on the core network side currently connected to the base station fails, the communication parameters of the first device currently configured by the base station will be modified to the communication parameters of the second device, including:

[0015] Modify the current tracking area code and S1 interface IP address of the base station to the tracking area code and S1 interface IP address of the second device.

[0016] Furthermore, in one embodiment, the first device belongs to the SAE-GW resource pool, and the second device belongs to the mobile management node function resource pool;

[0017] When the first device on the core network side currently connected to the base station fails, the communication parameters of the first device currently configured by the base station will be modified to the communication parameters of the second device, including:

[0018] Send the PDN gateway resolution data and service gateway resolution data of the first device to the second device, so that the second device can connect to the base station based on the PDN gateway resolution data and service gateway resolution data of the first device;

[0019] Modify the current tracking area code and S1 interface IP address of the base station to the tracking area code and S1 interface IP address of the second device.

[0020] Furthermore, in one embodiment, the first device and the second device belong to different operators.

[0021] Secondly, embodiments of this application provide a disaster recovery and emergency handover device, which is applied to a base station and includes:

[0022] The switching module is used to switch the base station to the connection of the second device on the core network side when the first device currently connected to the base station fails; the first device and the second device belong to different resource pools.

[0023] Furthermore, in one embodiment, the switching module is specifically used for:

[0024] When the first device on the core network side currently connected to multiple base stations fails, determine the geographical area to which the multiple base stations belong;

[0025] Based on the preset correspondence between geographical regions and handover order, multiple base stations are sequentially switched to the second device connection on the core network side.

[0026] Furthermore, in one embodiment, the switching module is specifically used for:

[0027] When the first device on the core network side currently connected to the base station fails, the communication parameters of the first device currently configured by the base station will be modified to the communication parameters of the second device.

[0028] The base station is connected to the second device based on the communication parameters of the second device.

[0029] Furthermore, in one embodiment, the first device belongs to the first mobile management node function resource pool, and the second device belongs to the second mobile management node function resource pool; or, the first device belongs to the first SAE-GW resource pool, and the second device belongs to the second SAE-GW resource pool.

[0030] Switching modules, specifically used for:

[0031] Modify the current tracking area code and S1 interface IP address of the base station to the tracking area code and S1 interface IP address of the second device.

[0032] Furthermore, in one embodiment, the first device belongs to the SAE-GW resource pool, and the second device belongs to the mobile management node function resource pool;

[0033] Switching modules, specifically used for:

[0034] Send the PDN gateway resolution data and service gateway resolution data of the first device to the second device, so that the second device can connect to the base station based on the PDN gateway resolution data and service gateway resolution data of the first device;

[0035] Modify the current tracking area code and S1 interface IP address of the base station to the tracking area code and S1 interface IP address of the second device.

[0036] Furthermore, in one embodiment, the first device and the second device belong to different operators.

[0037] Thirdly, embodiments of this application provide a disaster recovery and emergency switching device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the aforementioned disaster recovery and emergency switching method.

[0038] Fourthly, embodiments of this application provide a computer-readable storage medium storing an information transmission implementation program, which, when executed by a processor, implements the aforementioned disaster recovery and emergency switching method.

[0039] The disaster recovery emergency handover method, apparatus, device, and storage medium of this application embodiment, when facing a failure of the first device on the core network side currently connected to the base station, performs disaster recovery emergency handover on the base station side. Compared to performing disaster recovery emergency handover on the core network side, since the core network is interconnected, a failure on the core network side would affect the normally functioning equipment connected to the core network, while the operation on the base station side only affects the base station itself. Specifically, this application embodiment switches the base station to the connection of the second device on the core network side; the first device and the second device belong to different resource pools. That is to say, this application embodiment actually adopts a cross-resource pool base station connection to the core network side equipment handover. Therefore, when facing a failure of all equipment in the same resource pool, compared with handover within the same resource pool, it can still ensure that the base station can normally connect to the core network equipment, realize disaster recovery emergency, and make the disaster recovery emergency handover success rate higher. Attached Figure Description

[0040] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0041] Figure 1 This is a flowchart illustrating a disaster recovery and emergency switching method provided in an embodiment of this application;

[0042] Figure 2 This is a schematic diagram of the structure of a disaster recovery and emergency switching device provided in an embodiment of this application;

[0043] Figure 3 This is a schematic diagram of the structure of a disaster recovery and emergency switching device provided in an embodiment of this application. Detailed Implementation

[0044] The features and exemplary embodiments of various aspects of this application will now be described in detail. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only configured to explain this application and are not configured to limit this application. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples of this application.

[0045] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0046] Disaster recovery and emergency response sometimes face the following scenario: all devices in the same resource pool fail. Due to the limitations of the existing device resource pool configuration during disaster recovery, existing disaster recovery and emergency switching methods will fail in this scenario, resulting in a low success rate.

[0047] To address the problems of existing technologies, this application provides a disaster recovery and emergency handover method, apparatus, device, and storage medium. In the event of a failure of the first device on the core network side currently connected to the base station, this application performs a disaster recovery and emergency handover on the base station side. Compared to performing a disaster recovery and emergency handover on the core network side, where a failure on the core network affects the entire system, impacting normally functioning equipment connected to the core network, the operation on the base station side only affects the base station itself. Specifically, this application switches the base station to a second device on the core network side. The first and second devices belong to different resource pools; that is, this application actually employs a cross-resource pool base station connection to core network side equipment handover. Therefore, even when all devices in the same resource pool fail, compared to handover within the same resource pool, it still ensures that the base station can normally connect to the core network equipment, achieving disaster recovery and emergency handover with a higher success rate. The disaster recovery and emergency handover method provided in this application will be described below.

[0048] Figure 1 This illustration shows a flowchart of a disaster recovery and emergency handover method provided in one embodiment of this application. The method is applied to a base station, such as... Figure 1 As shown, the method may include the following steps:

[0049] S110: When the first device on the core network side currently connected to the base station fails, the base station will be switched to the second device on the core network side for connection.

[0050] The first device and the second device belong to different resource pools.

[0051] In the current network, the provincial backbone packet transport network PTN layer has fully connected the transmission between equipment rooms, enabling cross-resource pool (POOL) disaster recovery. Before disaster recovery switching, the core network's ability to count users based on tracking area codes (TACs) is used to assess the number of users that need to be migrated during cross-pool switchover. Then, the service load of each POOL is assessed, such as: number of users... tens of thousands, capacity utilization...%, peak traffic... Gbps, bandwidth utilization...%. Based on the service load, the current POOL's capacity to support disaster recovery switching can be evaluated. A switching mapping relationship between the first and second devices during disaster recovery switching is constructed based on the disaster recovery switching capacity of each POOL. Taking Wuhan as an example, the service load of different POOLs is shown in Table 1:

[0052] Table 1

[0053] POOL name Device operator Carrying business city POOL3 Operator A Wuhan (Wuchang), Huangshi, Ezhou POOL4 Operator A Wuhan (Wuchang), Xianning POOL7 Operator B Wuhan (Hanyang), Xiaogan POOL8 Operator C Wuhan (Hankou), Huanggang

[0054] As can be seen from Table 1, if operator A's equipment experiences a complete outage for some reason, disaster recovery from pool POOL3 to pool POOL4 is meaningless. Therefore, considering factors such as different operators and geographical location, the final determined disaster recovery handover mapping relationship between the first and second devices can be:

[0055] 1) When the first device in operator A pool POOL3 fails, disaster recovery is performed on the second device in operator C pool POOL8;

[0056] 2) When the first device in operator A pool POOL4 fails, disaster recovery is performed on the second device in operator B pool POOL7;

[0057] 3) When the first device in operator C pool POOL8 fails, disaster recovery is performed on the second device in operator B pool POOL7;

[0058] 4) When the first device in operator B pool POOL7 fails, disaster recovery is performed on the second device in operator C pool POOL8.

[0059] In this embodiment, when the first device on the core network side currently connected to the base station fails, a disaster recovery handover is performed on the base station side. Compared to a disaster recovery handover on the core network side, where a failure on the core network affects the entire system, this approach only impacts the base station itself. Specifically, this embodiment switches the base station to a second device on the core network side. The first and second devices belong to different resource pools. In other words, this embodiment actually uses a cross-resource pool base station handover to the core network side device. Therefore, when all devices in the same resource pool fail, compared to handover within the same resource pool, it still ensures that the base station can normally connect to the core network device, achieving disaster recovery and resulting in a higher success rate for disaster recovery handover.

[0060] In one embodiment, S110 may include:

[0061] When the first device on the core network side currently connected to multiple base stations fails, the geographical area to which the multiple base stations belong is determined; according to the preset correspondence between geographical areas and handover order, the multiple base stations are sequentially switched to the second device on the core network side for connection.

[0062] Considering the limited capacity of the POOL, there may be situations where the disaster recovery POOL cannot support all the base stations that need to be switched. Therefore, according to the preset correspondence between geographical areas and switching order, multiple base stations are switched to the second device connection on the core network side in sequence, thereby ensuring that base stations in important geographical areas can be switched first. The preset geographical areas and switching order are that important geographical areas come first. Important geographical areas may include: key business districts, transportation hubs, and other corresponding geographical areas.

[0063] In one embodiment, S110 may include:

[0064] S1101, when the first device on the core network side currently connected to the base station fails, the communication parameters of the first device currently configured by the base station are modified to the communication parameters of the second device.

[0065] S1102, Connect the base station to the second device according to the communication parameters of the second device.

[0066] The communication parameters can include the Tracking Area Code (TAC) and the S1 interface IP address, or the Tracking Area Identifier (TAI) and the S1 interface IP address. After joint evaluation with wireless professionals, it was found that all modifications to the base station configuration on the wireless side are issued through the OMC. Modifications to the S1 interface IP address and TAC configuration can be done through batch command issuance. The above operations can be completed in just one minute, and the disaster recovery switchover time is extremely short.

[0067] In one embodiment, when the first device on the core network side currently connected to the base station fails, the S1 interface IP address of the first device currently configured by the base station can be changed to the S1 interface IP address of the second device. However, this will cause the second device to generate a large amount of TAC data. According to wireless testing and evaluation, it takes more than one hour, and the disaster recovery switching time is relatively long.

[0068] In one embodiment, the first device belongs to a first Mobility Management Node Function (MLM) resource pool, and the second device belongs to a second MLM resource pool; or, the first device belongs to a first SAE-GW resource pool, and the second device belongs to a second SAE-GW resource pool. S1101 may include:

[0069] Modify the current tracking area code and S1 interface IP address of the base station to the tracking area code and S1 interface IP address of the second device.

[0070] In one embodiment, the first device belongs to the SAE-GW resource pool, and the second device belongs to the Mobility Management Node Function resource pool. S1101 may include:

[0071] Send the PDN gateway resolution data and service gateway resolution data of the first device to the second device, so that the second device can connect to the base station based on the PDN gateway resolution data and service gateway resolution data of the first device; modify the tracking area code and S1 interface IP address currently configured by the base station to the tracking area code and S1 interface IP address of the second device.

[0072] In the current network, the Serving Gateway (SGW) and the PDN Gateway (PGW) are co-located and referred to as SAE-GW. Currently, the routing from the Mobility Management Node (MME) network element to the SAE-GW network element is interconnected through a dedicated Gn interconnection link. The transmission between different equipment rooms is fully connected, and cross-pool disaster recovery is possible. However, due to the configuration differences between the SAE-GW resource pool and the MME resource pool, directly modifying the current tracking area code and S1 interface IP address of the base station to the tracking area code and S1 interface IP address of the second device is insufficient to connect the base station and the second device based solely on the communication parameters of the second device. Gateway configuration for the second device is required first. Therefore, when the base station performs disaster recovery from the first device in the SAE-GW resource pool to the second device in the MME resource pool, it needs to send the PDN Gateway (PDGWay, PGW) resolution data and Serving Gateway (SGW) resolution data of the first device to the second device. This allows the second device to perform gateway configuration based on the PDN Gateway resolution data and Serving Gateway resolution data of the first device. Then, by modifying the current tracking area code and S1 interface IP address of the base station to the tracking area code and S1 interface IP address of the second device, the disaster recovery handover can be successfully ensured.

[0073] In one embodiment, the first device and the second device belong to different operators.

[0074] As can be seen from Table 1, if the operator equipment of operator A experiences a complete shutdown for some reason, disaster recovery from operator A's POOL3 to operator A's POOL4 is meaningless. Therefore, the first and second equipment in this application belong to different operators, thus avoiding disaster recovery failure.

[0075] In this embodiment, when the first device on the core network side currently connected to the base station fails, a disaster recovery handover is performed on the base station side. Compared to a disaster recovery handover on the core network side, where a failure on the core network affects the entire system, this approach only impacts the base station itself. Specifically, this embodiment switches the base station to a second device on the core network side. The first and second devices belong to different resource pools. In other words, this embodiment actually uses a cross-resource pool base station handover to the core network side device. Therefore, when all devices in the same resource pool fail, compared to handover within the same resource pool, it still ensures that the base station can normally connect to the core network device, achieving disaster recovery and resulting in a higher success rate for disaster recovery handover.

[0076] Figure 1 The disaster recovery and emergency switching method is described below, in conjunction with the appendix.Figure 2 and attached Figure 3 This application describes the apparatus provided in the embodiments.

[0077] Figure 2 This illustration shows a schematic diagram of a disaster recovery and emergency handover device according to an embodiment of this application. The device is applied to a base station. Figure 2 Each module in the device shown has the ability to implement Figure 1 The functions of each step in the process are defined, and their corresponding technical effects are achieved. For example... Figure 2 As shown, the device may include:

[0078] The switching module 210 is used to switch the base station to the second device on the core network side when the first device currently connected to the base station fails.

[0079] The first device and the second device belong to different resource pools.

[0080] In this embodiment, when the first device on the core network side currently connected to the base station fails, a disaster recovery handover is performed on the base station side. Compared to a disaster recovery handover on the core network side, where a failure on the core network affects the entire system, this approach only impacts the base station itself. Specifically, this embodiment switches the base station to a second device on the core network side. The first and second devices belong to different resource pools. In other words, this embodiment actually uses a cross-resource pool base station handover to the core network side device. Therefore, when all devices in the same resource pool fail, compared to handover within the same resource pool, it still ensures that the base station can normally connect to the core network device, achieving disaster recovery and resulting in a higher success rate for disaster recovery handover.

[0081] In one embodiment, the switching module 210 is specifically used for:

[0082] When the first device on the core network side currently connected to multiple base stations fails, determine the geographical area to which the multiple base stations belong;

[0083] Based on the preset correspondence between geographical regions and handover order, multiple base stations are sequentially switched to the second device connection on the core network side.

[0084] In one embodiment, the switching module 210 is specifically used for:

[0085] When the first device on the core network side currently connected to the base station fails, the communication parameters of the first device currently configured by the base station will be modified to the communication parameters of the second device.

[0086] The base station is connected to the second device based on the communication parameters of the second device.

[0087] In one embodiment, the first device belongs to the first mobile management node function resource pool, and the second device belongs to the second mobile management node function resource pool; or, the first device belongs to the first SAE-GW resource pool, and the second device belongs to the second SAE-GW resource pool.

[0088] Switching module 210 is specifically used for:

[0089] Modify the current tracking area code and S1 interface IP address of the base station to the tracking area code and S1 interface IP address of the second device.

[0090] In one embodiment, the first device belongs to the SAE-GW resource pool, and the second device belongs to the mobile management node function resource pool.

[0091] Switching module 210 is specifically used for:

[0092] Send the PDN gateway resolution data and service gateway resolution data of the first device to the second device, so that the second device can connect to the base station based on the PDN gateway resolution data and service gateway resolution data of the first device;

[0093] Modify the current tracking area code and S1 interface IP address of the base station to the tracking area code and S1 interface IP address of the second device.

[0094] In one embodiment, the first device and the second device belong to different operators.

[0095] In this embodiment, when the first device on the core network side currently connected to the base station fails, a disaster recovery handover is performed on the base station side. Compared to a disaster recovery handover on the core network side, where a failure on the core network affects the entire system, this approach only impacts the base station itself. Specifically, this embodiment switches the base station to a second device on the core network side. The first and second devices belong to different resource pools. In other words, this embodiment actually uses a cross-resource pool base station handover to the core network side device. Therefore, when all devices in the same resource pool fail, compared to handover within the same resource pool, it still ensures that the base station can normally connect to the core network device, achieving disaster recovery and resulting in a higher success rate for disaster recovery handover.

[0096] Figure 3 A schematic diagram of the structure of a disaster recovery and emergency switching device provided in one embodiment of this application is shown. Figure 3 As shown, the device may include a processor 301 and a memory 302 storing computer program instructions.

[0097] Specifically, the processor 301 may include a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0098] Memory 302 may include mass storage for data or instructions. For example, and not limitingly, memory 302 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. In one instance, memory 302 may include removable or non-removable (or fixed) media, or memory 302 may be non-volatile solid-state memory. Memory 302 may be internal or external to the integrated gateway disaster recovery device.

[0099] In one instance, memory 302 may be read-only memory (ROM). In one instance, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), an electrically rewritable ROM (EAROM), or flash memory, or a combination of two or more of these.

[0100] The processor 301 reads and executes computer program instructions stored in the memory 302 to achieve... Figure 1 The method in the illustrated embodiment achieves... Figure 1 The technical effects achieved by executing the methods in the examples shown are not elaborated here for the sake of brevity.

[0101] In one example, the disaster recovery switching device may also include a communication interface 303 and a bus 310. For example, Figure 3 As shown, the processor 301, memory 302, and communication interface 303 are connected through bus 310 and complete communication with each other.

[0102] The communication interface 303 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0103] Bus 310 includes hardware, software, or both, that couples components of an online data traffic metering device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 310 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, any suitable bus or interconnect is contemplated herein.

[0104] The disaster recovery and emergency switching device can execute the disaster recovery and emergency switching method in the embodiments of this application, thereby achieving... Figure 1 Figure 1 The technical effects of the disaster recovery and emergency switching methods described.

[0105] Furthermore, in conjunction with the disaster recovery and emergency switching methods in the above embodiments, this application embodiment can provide a computer storage medium for implementation. This computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the disaster recovery and emergency switching methods in the above embodiments.

[0106] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0107] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0108] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0109] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0110] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A disaster recovery and emergency switching method, characterized in that, The method is applied to a base station, and the method includes: When the first device on the core network side currently connected to the base station fails, the base station is switched to the second device on the core network side for connection; the resource pools to which the first device and the second device belong are different, the resource pools to which the first device and the second device belong are different operators, and the resource pools to which the first device and the second device belong are different regions.

2. The disaster recovery and emergency switching method as described in claim 1, characterized in that, When the first device on the core network side currently connected to the base station fails, the connection to the base station is switched to the second device on the core network side, including: When the first device on the core network side currently connected to multiple base stations fails, the geographical area to which the multiple base stations belong is determined; According to the preset correspondence between the geographical regions and the handover sequence, multiple base stations are sequentially switched to the second device connection on the core network side.

3. The disaster recovery and emergency switching method as described in claim 1, characterized in that, When the first device on the core network side currently connected to the base station fails, the connection to the base station is switched to the second device on the core network side, including: When the first device on the core network side currently connected to the base station fails, the communication parameters of the first device currently configured by the base station are modified to the communication parameters of the second device. The base station is connected to the second device according to the communication parameters of the second device.

4. The disaster recovery and emergency switching method as described in claim 3, characterized in that, The first device belongs to the first mobile management node function resource pool, and the second device belongs to the second mobile management node function resource pool; or, the first device belongs to the first SAE-GW resource pool, and the second device belongs to the second SAE-GW resource pool. When the first device on the core network side currently connected to the base station fails, modifying the communication parameters of the first device currently configured on the base station to the communication parameters of the second device includes: Modify the tracking area code and S1 interface IP address currently configured in the base station to the tracking area code and S1 interface IP address of the second device.

5. The disaster recovery and emergency switching method as described in claim 3, characterized in that, The first device belongs to the SAE-GW resource pool, and the second device belongs to the mobile management node function resource pool; When the first device on the core network side currently connected to the base station fails, modifying the communication parameters of the first device currently configured on the base station to the communication parameters of the second device includes: Send the PDN gateway resolution data and service gateway resolution data of the first device to the second device, so that the second device can connect to the base station based on the PDN gateway resolution data and service gateway resolution data of the first device; Modify the tracking area code and S1 interface IP address currently configured in the base station to the tracking area code and S1 interface IP address of the second device.

6. The disaster recovery and emergency switching method as described in any one of claims 1-5, characterized in that, The first device and the second device belong to different operators.

7. A disaster recovery and emergency switching device, characterized in that, The device is used in a base station, and the device includes: The switching module is used to switch the base station to a second device on the core network side when the first device currently connected to the base station fails. The first device and the second device belong to different resource pools, the resource pools of the first device and the second device belong to different operators, and the resource pools of the first device and the second device belong to different regions.

8. The disaster recovery and emergency switching device as described in claim 7, characterized in that, The switching module is specifically used for: When the first device on the core network side currently connected to multiple base stations fails, the geographical area to which the multiple base stations belong is determined; According to the preset correspondence between the geographical regions and the handover sequence, multiple base stations are sequentially switched to the second device connection on the core network side.

9. The disaster recovery and emergency switching device as described in claim 7, characterized in that, The switching module is specifically used for: When the first device on the core network side currently connected to the base station fails, the communication parameters of the first device currently configured by the base station are modified to the communication parameters of the second device. The base station is connected to the second device according to the communication parameters of the second device.

10. The disaster recovery and emergency switching device as described in claim 9, characterized in that, The first device belongs to the first mobile management node function resource pool, and the second device belongs to the second mobile management node function resource pool; or, the first device belongs to the first SAE-GW resource pool, and the second device belongs to the second SAE-GW resource pool. The switching module is specifically used for: Modify the tracking area code and S1 interface IP address currently configured in the base station to the tracking area code and S1 interface IP address of the second device.

11. The disaster recovery and emergency switching device as described in claim 9, characterized in that, The first device belongs to the SAE-GW resource pool, and the second device belongs to the mobile management node function resource pool; The switching module is specifically used for: Send the PDN gateway resolution data and service gateway resolution data of the first device to the second device, so that the second device can connect to the base station based on the PDN gateway resolution data and service gateway resolution data of the first device; Modify the tracking area code and S1 interface IP address currently configured in the base station to the tracking area code and S1 interface IP address of the second device.

12. The disaster recovery and emergency switching device as described in any one of claims 7-11, characterized in that, The first device and the second device belong to different operators.

13. A disaster recovery and emergency switching device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the disaster recovery and emergency switching method as described in any one of claims 1 to 6.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores an information transmission implementation program, which, when executed by a processor, implements the disaster recovery and emergency switching method as described in any one of claims 1 to 6.

Images